Android 4.4 Released for all Onyx Books

[kkakosim]

Boxtor, you are referring to this [N96ML_2017-05-02_17-04_dev_fbc2cc2_user] ?
This is the one I installed. If I get it right, this [Update File V1.8.2 N96 ML] is still Android v4.0.4.

[EDIT]
I installed v1.8.2 and frontlight works, did again v4.4 and it doesn't

[Neru]

Hello, have anyone suceed in running 4.4 on I86ML without errors? Or are there any logcat apps that could work without root? (could not root because of systemui error).

[plusz]

Originally Posted by marssaturn

thanks a lot plusz - at least I am now sure that i still have 4.0.4 - it is black :-(

I have read that MfgTools can be used to return to 4.0.4. How can I control, whether 4.4 or 4.0.4 is installed by MfgTools ???

I have tried again. Here is exactly what I have done.

1. power off with no USB cable attached
2. press the power button + > + < buttons at the same time for 4 secs until the led flashes
3. connect USB cable
4. start MfgTools2.exe
it shows "HID-konformes, vom Hersteller definiertes Gerät"
and "Hub 3-Port 1"
5. press Start button in MfgTools2 - it runs through several steps
6. buttons in mfgtools turn green - device reboots and starts
device display flashes some times inbetween
this phase takes rather long time
7. rebooted device shows this message
"Connect device to a computer for USB storage?"
There is OK and Cancel - I say "Cancel"
Title bar still black and version number 4.0.4 :-(
8. I click on Stop button in MfgTools, then "Exit"
9. I disconnect device properly from Windows

So, no success - update does not work - readers, please help me.

Best Regards,

Hey, I may know where is your problem. If I remember correctly I also had no success at first when I have tried to "set up the device" then connect it to the PC.

Try:
1. Connect USB cable, Boox - PC
2. Power off Boox, with the cable attached
3. Use the special FW upgrade key combination to start Boox, usb cable attached all the time
4....

[lems1995]

Originally Posted by SnowRipple

Now I am waiting for comments like:

"I updated to 4.4 but lost all my books, how can I restore them?"

Just rebuild library and then scan for metadata.

That's it!
PRS-T2, PRS-T3, After Glow 2, N96ML, Max Carta,
The far best are Sony products, Sony hasn't Android e-ink reader.

[eReader fan]

I sadly have to say I had to move again to the 4.0.x android. The superfast firmware stop being that in less than 24h. Also the internet browser was fully unusable and the play store never got connected.

Hope the development of tthe 4.4.4 keep on going

[mstolars]

Originally Posted by kkakosim

Boxtor, you are referring to this [N96ML_2017-05-02_17-04_dev_fbc2cc2_user] ?
This is the one I installed. If I get it right, this [Update File V1.8.2 N96 ML] is still Android v4.0.4.

[EDIT]
I installed v1.8.2 and frontlight works, did again v4.4 and it doesn't

I have N96ML and have the same promlem.

Android 4.4 and front light doesn't work

But my BT Microsoft flotable keyboard work

[stardest]

Hi guys after upgrading Android 4.4 my frontlight doesn't work anymore! has anyone experienced this?! I have the N96ML Pearl version.... ugh did I do something wrong or j=should i go back to 4.0.4 instead....

Ok just read previous posts and I see I'm not the only one. Looks like I'll be going back to Android 4.04...

[stardest]

Ok I'm trying one last time. I reverted back to Anroid 4.04 and now I'm reinstalling Android 4.4. Hopefully it'll work...

[underscore]

Originally Posted by stardest

Ok I'm trying one last time. I reverted back to Anroid 4.04 and now I'm reinstalling Android 4.4. Hopefully it'll work...

So you had 4.04.
You installed 4.4 to notice that frontlight stopped to work.
You rollback to 4.04 and frontlight worked again.
You read that someone else found the same bug on 4.4

Why are you reinstalling that 4.4 firmware again if you need the frontlight?
How do you think it'll work ?
Those 4.4 files were released on may.
If they have that bug is peacefully still there...

[stangri]

Better late, than never...

Originally Posted by Hrafn

1. Is there any factual basis for your "expect[ation] that newer Android has native functions to force render apps in 2 colors (B/W)"? And how robust are these functions?

Yes, there is. Very robust.

[Hrafn]

Originally Posted by stangri

Better late, than never...

Yes, there is. Very robust.

Three months late meant that I had completely forgotten the context of the original question (which I would note was the third out of three, closely-related, questions relating to whether upgrading to Android 4.4 yields any practical benefits for eReaders).

Citations/details for their existence and robustness? Bald assertions are seldom helpful -- even less so when they're on a moribund topic.

Also (related to my first original question), what is the CPU load of these functions (remembering that the apps they are re-rendering may already be putting pressure on an eReader's slower CPU)?

[stardest]

figured I'd give it one last try just in case. There were other times in the past for some other problem where I did several tries and it worked. Anyhow, I'm back to 4.0.4.

Originally Posted by underscore

So you had 4.04.
You installed 4.4 to notice that frontlight stopped to work.
You rollback to 4.04 and frontlight worked again.
You read that someone else found the same bug on 4.4

Why are you reinstalling that 4.4 firmware again if you need the frontlight?
How do you think it'll work ?
Those 4.4 files were released on may.
If they have that bug is peacefully still there...

[stangri]

Originally Posted by Hrafn

Three months late meant that I had completely forgotten the context of the original question (which I would note was the third out of three, closely-related, questions relating to whether upgrading to Android 4.4 yields any practical benefits for eReaders).

You're welcome. I've addressed one of your very specific questions (which had nothing to do with 4.4), I regret that the answer wasn't to your liking.

Originally Posted by Hrafn

Citations/details for their existence and robustness? Bald assertions are seldom helpful -- even less so when they're on a moribund topic.

A simple "android monochrome" search would have yielded the wisdom you were looking for: http://www.trishtech.com/2016/02/how...en-monochrome/

Originally Posted by Hrafn

Also (related to my first original question), what is the CPU load of these functions (remembering that the apps they are re-rendering may already be putting pressure on an eReader's slower CPU)?

I'd speculate, that being part of the display driver it doesn't load CPU at all.

[Hrafn]

Originally Posted by stangri

A simple "android monochrome" search would have yielded the wisdom you were looking for: http://www.trishtech.com/2016/02/how...en-monochrome/

This simply forces the OS to emulate a monochrome display, which is redundant where the actual screen is already monochrome.

For the "force[d] rend[ition of] apps in[to] 2 colors (B/W)" to be useful, it would have to make intelligent decisions about contrast and readability (e.g. to prevent contrasting blue-on-yellow becoming non-contrasting grey-on-grey).

As I said, context matters.

[stangri]

Originally Posted by Hrafn

This simply forces the OS to emulate a monochrome display...

Is there a basis for this statement? Considering modes other than monochrome in "newer" android, I have a different understanding, yet too lazy to check for myself.