Under http://droid.cs.fau.de/Official_CM_Builds/xt897/ you can find CM 13.0 builds.
Chrome started to crash for us after it has been updated from 54 to 55 at the beginning of December 2016. The EGL context initialization slightly changed and exposed an error in adreno EGL blob from JB which we are using. Chrome devs know about the issue and Chrome contains a workaround for older GPU blobs, but the assert is done by checking whether the android version where Chrome 55 (or newer) is running is older than KitKat, which doesn't work for us. ( https://chromium.googlesource.com/chromium/src/+/3f80f942c662cf8777d794375640d42cce93408d )
I've pushed the blob fix here: https://github.com/TheMuppets/propr...mmit/00c08be8fb201397d4ab77fc163df1b8f200f7fa
All you have to do to stop the Chrome crashes is to replace the /system/lib/egl/libEGL_adreno200.so file with the hexedited version downloaded from https://github.com/TheMuppets/propr...ommon/proprietary/lib/egl/libEGL_adreno200.so
I'd like to get the new LineageOS xt897 builds started ASAP, I just need to spare some "free" time for it, that's all.
its not working for my atrix hd phone. it freezes out my phone or stuck at boot logo. i think it will only work for Motorola Photon Q 4G LTE.
hey guys, im running the latest nightly that was last available from cyanogenmod. ive noticed that when using the keyboard, if i type fast enough some letters dont register, even though the button was pressed. anyone else notice that? really hoping it's not hardware related...
hey guys, im running the latest nightly that was last available from cyanogenmod. ive noticed that when using the keyboard, if i type fast enough some letters dont register, even though the button was pressed. anyone else notice that? really hoping it's not hardware related...
This is hardware problem and solution is changing your keydome. Sometimes, just cleaning your mainboard where is under the keydome pad might be a good solution. You can clean mainboard by alcohol or pcb cleaner.
pardon my ignorance, but whats a keydome??
Chrome started to crash for us after it has been updated from 54 to 55 at the beginning of December 2016. The EGL context initialization slightly changed and exposed an error in adreno EGL blob from JB which we are using. Chrome devs know about the issue and Chrome contains a workaround for older GPU blobs, but the assert is done by checking whether the android version where Chrome 55 (or newer) is running is older than KitKat, which doesn't work for us. ( https://chromium.googlesource.com/chromium/src/+/3f80f942c662cf8777d794375640d42cce93408d )
I've pushed the blob fix here: https://github.com/TheMuppets/propr...mmit/00c08be8fb201397d4ab77fc163df1b8f200f7fa
All you have to do to stop the Chrome crashes is to replace the /system/lib/egl/libEGL_adreno200.so file with the hexedited version downloaded from https://github.com/TheMuppets/propr...ommon/proprietary/lib/egl/libEGL_adreno200.so
After switching to my Droid 4 for a while (because I thought it's a hardware issue) I am back on my Photon Q. Works great againI've pushed the blob fix here: https://github.com/TheMuppets/propr...mmit/00c08be8fb201397d4ab77fc163df1b8f200f7fa
All you have to do to stop the Chrome crashes is to replace the /system/lib/egl/libEGL_adreno200.so file with the hexedited version downloaded from https://github.com/TheMuppets/propr...ommon/proprietary/lib/egl/libEGL_adreno200.so
Oh that would be greatI'd like to get the new LineageOS xt897 builds started ASAP, I just need to spare some "free" time for it, that's all.
A few questions please if someone doesn't mind answering.
If I remove the first "assert" line from updater-script, will I be able to flash this on a Razr M (XT907) with JBBL without any other changes (like a different TWRP) required?
Is the 121916 nightly the latest one available?
Do I need kabaldan's fixed boot.img and if I do, can I replace the one in the 121916 zip with it prior to flashing?
Thanks a lot!
Lookslike photon q hasbeen update to 14.1, can i dirty flash to razr hd? Because till now i'm still using cm13 to my xt926
Use at your own risk, responsibility is all yours, provided as-is, no warranties...
You know the drill.
su
setprop persist.log.aplogd.enable 1
Enabled SELinux enforcing
Reverted to old-style keyboard backlight behaviour: it won't be brighter than screen but it also won't completely turn off kbd backlight on very bright conditions (I shoud really put some effort into it...)
Using Flo's PowerHAL
Updated interactive governor in kernel
Enabled Motorola memutils in kernel (should improve memory operations)
Quite a bit of other updates/changes/fixes
I can't resist asking what I feel is the natural followup question - Will there be an official release [soon/ever]?
I so want to upgrade but with only one Photon Q as my daily driver I'm concerned about leaving the official update path.
Regardless, props to you for proving it can be done. :good:
Any news about porting cm14 for Photon Q?
Enabled SELinux enforcing
Reverted to old-style keyboard backlight behaviour: it won't be brighter than screen but it also won't completely turn off kbd backlight on very bright conditions (I shoud really put some effort into it...)
Using Flo's PowerHAL
Updated interactive governor in kernel
Enabled Motorola memutils in kernel (should improve memory operations)
Quite a bit of other updates/changes/fixes