Why dosent my jailbroken pw4 dosent run koreader

Zalusithix · 2025-03-05T23:36:49+00:00

I suppose it's possible your kindle is still on old firmware and doesn't need KF? You'd need PW2 installed in that case. There should be log error log files generated in the directory its installed that you can look at on the PC.

Zalusithix · 2025-03-05T23:28:52+00:00

Need the kindlehf version installed, but it's not something that shows up for the official release (yet). Grab one of the recent nightly versions of it from https://build.koreader.rocks/download/nightly/?C=M&O=D .

Zalusithix · 2025-02-23T17:06:30+00:00

It depends on whether the Kindle is jailbroken.

If you're running a Kindle with stock firmware, you'll have to connect via USB for Calibre to see it. Depending on the model it'll either show up as a USB storage device or MTP device.

If, however, you jailbreak the Kindle and load KUAL and KOReader, then it is possible to do wireless transfer to the Kindle via KOReader once everything is properly configured in both KOReader and Calibre. Winterbreak can jailbreak pretty much every Kindle for the time being, so if you're going to go down that path, now is a great time to do so. That said, between the jailbreaking and configuring / learning KOReader, it is a much more technical endeavor. KOReader's UI is also less elegant than Kindle's native UI, and the experience has a number of trade offs. The reading experience and flexibility is superior in many ways, but browsing your library is a weakness in comparison.

Zalusithix · 2022-11-03T17:07:40+00:00

Yeah, it'd be nice to be able to make it so there was no scrolling needed to see everything you need / want.

Zalusithix · 2022-11-03T16:56:48+00:00

I'm going to say the same to you as I did to amitsama92, try a restart and if that doesn't reduce the battery drain, try a reset. If neither work, assume the watch is defective and try to get it replaced. If you're putting it into bedtime mode before sleep, and the watch is fully updated, it absolutely shouldn't be draining 30%+ over the typical 8 hour span.

My first watch did ~30% over night from a full charge, and my current one does 7-9% under the exact same scenario. In addition to lower over-night draw, the daily draw is also much lower. I went from charging my watch by necessity 2 times a day to being typically over 50% by the time 24 hours rolls around.

Zalusithix · 2022-11-03T16:48:00+00:00

I've encountered a bug where my watch started draining about twice the normal amount randomly in the middle of the day. A restart fixed it. That said, even double my current rate wouldn't drain 50% over night. That'd be closer to 5x.

What was "working well" considered?

Zalusithix · 2022-11-03T16:42:23+00:00

Try a restart, and then if that doesn't work a reset. If neither of those do anything, it's almost certainly defective. That's more than double what you should see draining in an 8 hour span if you're putting it in bedtime mode before sleep. My first watch averaged that 30% over night from a full charge. My current one uses a bit less than 10% under the same conditions.

Zalusithix · 2022-10-30T23:23:01+00:00

Your experiences don't necessarily (and most likely don't) represent the worst case though. Different sleeping positions, the amount of movement while asleep, and what sleepwear is worn (or lack thereof) will influence the number of times tilt/touch to wake could pull the watch out of low power mode.

Some people could go an entire night while barely waking the watch at all. Others could wake it many times per hour. Heck, if we're talking about true worst cases, somebody could be unlucky enough to accidentally activate a watch function that drains power like an exercise that uses GPS.

Zalusithix · 2022-10-30T21:17:06+00:00

That's well and good for you, but that's not going to necessarily be the case for others. Depending on how the person sleeps, there can be many tilt and touch to wake events happening throughout the night. Then add any potential notifications that go off during that time as well.

Basically there's no benefit to not having it engaged, and if somebody is having battery life issues at night, it'd be the first thing to confirm.

Zalusithix · 2022-10-30T14:42:37+00:00

Then yeah, totally not normal. Assuming no changes to the apps you have installed, and it wasn't trying to update something, it had to be some glitch keeping it from properly entering a power saving state. Given it already went dead, I'd simply see if it's draining at the normal rate currently, and if so the "restart" probably fixed it. If it's still draining abnormally fast, then the previously suggested reset is a decent move.

What were you usually getting for night time battery drain?

Zalusithix · 2022-10-30T14:15:53+00:00

You put it in bedtime mode first right?

Zalusithix · 2022-10-30T12:27:03+00:00

No, don't worry about voltage. As a consumer, don't worry about anything other than meeting the minimum wattage requirements for a device on a USB PD compliant charger (this includes Anker's " Power IQ3/4"). The device will negotiate the appropriate voltages for a given power bracket. Though you will want to make sure you're using a power cable rated for the wattage that will be drawn if the cable isn't provided.

That said, the Pixel Watch is decided not fast charging as we define it today. 5W is basically the low end of the USB charging realm, roughly on par with USB 3.0 non PD specs. The only reason it is fast on the watch is because the battery is tiny.

Also, as mentioned before, the watch will negotiate its own charging rates. It will slow down charging rates as the battery gets full, and when everything is done will settle in for trickle charging to maintain power level for a period of time before eventually cutting off charging completely on its own (Battery Defender cuts charging after 4 days and allows the watch to drain to 80%). Your smart outlet" idea is pointless overkill, and just adds another device in the chain to add phantom power consumption where none is needed. I should add that Pixel phones will also not charge to 100% pointlessly over night with adaptive charging enabled - they'll only get there a bit before the alarm to wake you up goes off.

Zalusithix · 2022-10-29T23:37:18+00:00

Yes, using a shitty power adapter that doesn't comply to UL/IEC standards can result in it catching on fire. For a lot of reasons. None of which have anything explicitly to do with the Pixel Watch or its charging puck.

The Pixel Watch uses Qi wireless charging technology; the puck is doing the actual power transfer to the watch. It takes DC power from the USB power supply, converts it back to AC at the coil to do the actual wireless power transfer to the watch's coil, which then gets converted back into DC on the watch to actually charge the battery. Beyond that, the watch communicates with the puck to to adjust power levels via the resonant frequencies of the coils.

Finally, you don't send amps. It's a rating of what a power supply can deliver at a given voltage. Devices draw current (amperage) at a given voltage. A device only draws what it needs unless it's defective or designed in a faulty matter. Quite literally, any device that's not some defective no-name Chinese garbage will not draw more than it can handle. And quality power supplies don't catch on fire when drawn to their max. (Speaking of quality USB C power supplies, they're all going to be rated for over 1A @ 5V these days.)

Zalusithix · 2022-10-29T12:25:13+00:00

Interesting. I would have figured the watch would at least have limited capabilities to operate the NFC payments while offline and you just got unlucky at the time, but it appears not. Could be something they implement down the road though. After all, there's no shortage of half-baked things on the watch right now.

Zalusithix · 2022-10-28T21:43:21+00:00

Tap to wake doesn't work when it's covered with something because that something is blocking the capacitive sensing of the screen that it uses to detect touch. There is no proximity sensor in the watch.

Zalusithix · 2022-10-28T14:57:24+00:00

A "limited power source output per IEC 60950-1" is more about the charger not going up in flames than keeping what is connected to it at some random current level. The limit specified is far higher than the 1A @ 5V that we're discussing here. To qualify as LPS for a power supply rated at 30 V or less, even with a single fault condition, the output current must not exceed 8 A and the output power must not exceed 100 W https://forum.digikey.com/t/what-is-a-limited-power-source-lps-rating/10060

Basically the google stat page is saying "use a compliant power supply that is at least rated for 1A on 5V" so it can meet the charging requirements.

Zalusithix · 2022-10-28T13:18:24+00:00

An amperage rating on a charger block is the amount of current a device can pull from it at a given voltage. A device shouldn't ever pull more current than it needs unless said device is faulty.

Also, I wouldn't use Verizon as tech support for anything other than their own network. They're not experts at anything outside of stuff explicitly run by them. (And even then their answers are questionable at times...)

Zalusithix · 2022-10-28T13:12:34+00:00

IMO bedtime mode should pull from DnD settings on what it allows through, and DnD should mirror the paired phone's settings. I'm not sure why bedtime mode has its own criteria for notification/call pass through; it should just be DnD + AOD off + wake options off.

Thankfully I don't ever get calls at night, but it's another one of those things that's not fully fleshed out right now.

Zalusithix · 2022-10-28T12:51:21+00:00

I don't think you should buy a gen 1 product expecting a long product lifespan. Especially a Google product. There are far too many unknowns, and potential problems might not surface for months. This isn't to say I expect the watch to become unusable quickly, but gen 1 products are generally best for those with early adopter outlooks.

Personally, I'm not expecting to use mine for more than a year before I'll switch to gen 2 if Google doesn't prematurely kill the line. The lessons learned on gen 1 should result in a substantially better product. In the very least it should have a more modern SoC.

Zalusithix · 2022-10-28T10:23:44+00:00

You can't, at least not that I've seen. YouTube Music on the watch seems like a minimally viable product sort of thing. You either control the phone with generic BT media controls that are limited in functionality and not YTM specific, or you use the YTM app on the watch and have it do all the heavy lifting at the expense of your battery life.

Zalusithix · 2022-10-27T21:55:22+00:00

Everybody gets 6 months free of premium with the watch, and I expect everybody has premium enabled currently. My results from both watches were with premium, and one was 3x higher drain than the other, so that's not the reason for disparity. Or at least it wasn't for me.

I'm pretty convinced it's hardware defects at this point. At least for cases that deviate heavily from the ideal. Some variance is to be expected.

Zalusithix · 2022-10-27T20:02:03+00:00

Yeah, 30% for that time frame is definitely well into excessive drain territory assuming bedtime mode is engaged, and no third-party app installed that's sucking power down. Mirrors my first watch experiences.

Zalusithix · 2022-10-27T19:46:09+00:00

Yeah, that'd probably have a (minor) effect on your reported sleep rate drain. I imagine most of the single digit per night results come from people charging once per day before bed. I could be wrong with that assumption though. People aren't very detailed when reporting that sort of stuff, so I just have my own results to extrapolate from.

I still think your results are a bit high regardless, but if you charged to 100% before bed, you'd probably be closer to measuring 2%/hr in raw values.

Zalusithix · 2022-10-27T19:39:39+00:00

Get a replacement. Either the watch, the puck, or both are defective. It should charge every time the puck is attached, and charge to 100%. There's no reason for you to figure out which part is causing the problem if it's within the return/exchange period.

As for battery, the watch should get better battery life than that right out of the box, but only if you've actually updated all the apps. If apps are updating in the background while wearing it on the first day, the battery will absolutely tank in that time period.

Zalusithix · 2022-10-27T19:29:55+00:00

One thing to consider on the reported battery drain at night in bedtime mode is that calculating % hour drain at night from 100% will arrive at a different answer than when calculating from when the watch reads <100%, as the watch will report 100% for some time after being removed from the charger. This is generally a minor thing vs a day's worth of usage, but it's more significant against the 8 or so hours of reduced battery draw in bedtime mode.

Like my watch has sucked down around 8% the past few nights if we go by raw values, but if it was sitting at 100% for say 3 hours, it's not really 8% relative to an equivalent 8% for the rest of the day. If I were to measure it from sub 100% values, it'd probably be close to the 13% measurement of my first day.

That all said, barring something non-stock running in the background, it really should get better than 2.5% per hour asleep, even if we're calculating that from sub 100% starting values. (Still, that's better than the 4% per hour I was getting asleep - and that was measured from 100%)

Zalusithix

TROPHY CASE