CF.lumen updated to v2.66 - 5.0 and 64-bit support
Posted on 2014-11-05, 26 comments, 197 +1's, imported from Google+/Chainfire

NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.

I've just uploaded version 2.66 of CF.lumen to the Play store, which should start redistributing it in a few hours. If you're impatient you can grab the APK right now from the XDA thread here: http://forum.xda-developers.com/showthread.php?t=2711912

A few fixes were needed for L retail, which surprised me a bit as it worked fine on the last preview.

Additional fixes were needed for 64-bit support. My previously untested 64-bit build was close, but aside from a bug or two, the GUI/installer didn't cope with different location and scripts needed for 64-bits devices.

There have also been some (minor) performance improvements. Might be noticable, might not.

Interesting note for other developers, Android lies about library locations on 64-bit 5.0. /data/data/<package>/lib is still a symlink, but it points to a non-existent location if you provide 64-bit libraries (the link is correct if you provide only 32-bit libraries). The best solution I could come up with on short notice was casting Context.getClassLoader() to BaseDexClassLoader, and using it's findLibrary() method to find the correct library location.

Changelogs

  • Android 5.0 fixes

  • 64-bit fixes

  • Performance improvement

+1197
SeFo Kadirov commented on 2014-11-05 at 22:03:

Android 5 . 0 ? Im with kit kat .. and I cant upgrade my android after rooting .. anyone help me ? ^_^

Mike Fougere commented on 2014-11-05 at 22:04:

+SeFo Yee you mean a system update?

SeFo Kadirov commented on 2014-11-05 at 22:05:

+Michael Fougere yeap bro :/

Mike Fougere commented on 2014-11-05 at 22:06:

Are you running the stock rom?

SeFo Kadirov commented on 2014-11-05 at 22:07:

Nope

Mike Fougere commented on 2014-11-05 at 22:08:

In don't think any phones other than the Nexus line have received a 5.0 over the air update.

Alan Armstrong commented on 2014-11-05 at 22:18:

Nothing has received an OTA for 5.0 yet.

Jason Efstathiou commented on 2014-11-05 at 22:31:

+Alan Armstrong this is true. There aren't even factory images yet, apparently the roll out has been postponed until Wednesday next week due to bugs.

Robert Christopulos commented on 2014-11-05 at 23:20:

At this point, the very latest OTA updates are for 4.4.4. No one has received 5.0 except the new NEXUS Player, NEXUS 6 and NEXUS 9 yet. In fact, these OTAs were released today for the NEXUS Player and NEXUS 9. OTA updates for other NEXUS hardware should start rolling out probably around mid to late November.

Other brands may take awhile.

rritambhar chakraborty commented on 2014-11-05 at 23:28:

As far i read it seems like 5.0 is still at least 2-3weeks away from now if not even further,same for nexus devices..

Rolando Reinosa commented on 2014-11-06 at 01:22:

Ey tu sabes poner buses en gta san andrea para pc

Eros De matteis commented on 2014-11-06 at 09:07:

I brick my lg g2 about uor lumen app.....

Jason Efstathiou commented on 2014-11-06 at 09:07:

+Eros De matteis probably not the fault of the app.

Sinan Çetinkaya commented on 2014-11-07 at 00:10:

I watched your video and I did like your accent #LOL  

Robert Christopulos commented on 2014-11-07 at 02:56:

I'd been reading on the "Android Police" widget yesterday, and found that

the first upgrades to bring devices up to Android 5 had been sent out to

the NEXUS Play and NEXUS 9 had been released.

Other devices should follow soon.

On Nov 5, 2014 4:28 PM, "Google+ (rritambhar chakraborty)" <

*@*> wrote:

Robert Christopulos commented on 2014-11-07 at 03:10:

I just finished reading this on SD NET:

Android Lollipop rollout delayed due to battery drain bug

Summary: Android fans will have to wait another week to get their hands on

Android 5.0 as Google fixes a bug that was causing severe battery drain.

By Liam Tung | November 6, 2014 -- 11:15 GMT (03:15 PST)

In news that will come as a mixed blessing for Android fans, the rollout of

Lollipop has been put on hold due to bugs that were causing severe battery

drain.

If you were wondering why your Nexus or Google Play Edition phone hadn't

received an over the air (OTA) update delivering Android 5.0, the answer

appears to be that Google is ironing out some serious bugs that would have

made it unwelcome in the first place.

Read this

Six licks of Google's Android Lollipop

Read more

The good news is that the issues are now fixed. The bad news for Android

users is that Google has pushed the Lollipop rollout back as a consequence,

from its originally scheduled date of November 3 to November 12.

News of the delay arrived yesterday via Artem Russakovskii, founder of

Android Police. According to Russakovskii, the first OTA updates were moved

to November 12 due to "some outstanding bugs".

Google hasn't provided a statement on the new rollout schedule or the

source of the delays. However an Android engineer did publicly acknowledge

"significant" battery drain when wi-fi is enabled on a Lollipop device.

"Android Engineering is aware of an issue affecting Nexus 5 users running

Android 5.0 which causes significant 'Miscellaneous' battery usage while

wi-fi is enabled. This appears to be caused by an abnormally high number of

IRQ wakeup events," Trevor Johns, a Google engineer for the Android Open

Source Project, wrote yesterday.

As Android Police pointed out, Johns has later confirmed the issue has been

fixed in the latest build.

Arguably the last thing Google would want is to annoy its millions of users

with a battery drain issue, given that one of the headline features of

Lollipop is a new battery saving feature that extends

kecco Mattioli commented on 2014-11-07 at 18:19:

It is saving my eyes +Jonathan Donini

Jonathan Donini commented on 2014-11-07 at 18:40:

Mine too +kecco Mattioli

Alex Abdo commented on 2014-11-08 at 14:19:

Great program. Unfortunately I'm no longer able to use it given the absence of root on the Verizon Note 4.

+Chainfire​​ - Any interest in "fixing" the Verizon Note 4? 

Robert Christopulos commented on 2014-11-08 at 21:39:

I'm sure that Chainfire will be able to do this. Go to it my friend. I'm sure that there are a lot of people who will need your help.

Bjørn commented on 2014-11-11 at 08:33:

+Chainfire​ is there a reason why it nags me to install driver again after reboot?? I install driver, it reboot and need to install driver again...

Timotheus Schmid commented on 2014-11-15 at 15:05:

It softbricked my Nexus 10 running Lollipop and TWRP Recovery when it wanted to install the driver. I tried both possibilities, Recovery and Normal, same result. 

kane mouhamadou commented on 2015-04-17 at 18:29:

Tres satisfaisant efficace

kane mouhamadou commented on 2015-04-17 at 18:29:

Tres satisfaisant efficace

Jan-Stefan Janetzky commented on 2015-06-29 at 11:33:

+Chainfire i know you will most likely never read this at all but.. did you think about adding support for franco kernel? this way my screenshots would not be affected by this tweak.

Robert Christopulos commented on 2015-07-08 at 06:50:

I'm excited. Today July 8,2015, I downloaded and installed an Alpha version of Omnirom 5.11 {a variant of Lollipop 5.11} on my four year old Motorola Xoom. So far, everything is working beautifully. I'm putting it through it’s paces and it's functioning flawlessly. This is wonderful. I'll let you know how well it functions, but this appears to be extremely polished for an Alpha version (Hear me Schischu-You've done a superb job-Thank You so much for all you do.) So far there's nothing that isn't working perfectly.

This post is over a month old, commenting has been disabled.