[ROM] CyanogenMod 13.0 for Photon Q (Android 6.x) [UNOFFICIAL]

Search This thread

Differset

New member
Nov 18, 2016
2
0
It will be great to get cm14.1 for Photon Q! My droid 4 has already received the update to Android N and working faster and more stable then on marshmallow. Waiting for porting Nougat to Photon Q, cause it has better hardware then Droid 4.
 

mifritscher

Senior Member
Aug 5, 2007
52
38
I sent you something to speed up building up the castle, which is very expensive as we all know ;)
Is this going to be a christmas gift? Nice idea!

Thanks for all the effort!
 

mifritscher

Senior Member
Aug 5, 2007
52
38
Somewhere between the last snapshot in August and later nightlies (30th of november), the chroot functionality got severly limited. In the snapshot, a full ubuntu 14.04 (16.04 isn't working because of the old kernel) is working flawlessly, while on the nightly, even a connection to a (successfully started) ssh server which is running in the chroot lets the complete phone hang and hard restart after a few seconds.
 
Last edited:

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,925
Prague
android.doshaska.net
Somewhere between the last snapshot in August and later nightlies (30th of november), the chroot functionality got severly limited. In the snapshot, a full ubuntu 14.04 (16.04 isn't working because of the old kernel) is working flawlessly, while on the nightly, even a connection to a (successfully started) ssh server which is running in the chroot lets the complete phone hang and hard restart after a few seconds.

Could you please retrieve and post the content of /proc/last_kmsg that's there after the hang/restart? Thanks.

PS: Thanks for the donation. Still in a slow mode, though, sorry for that. Let's hope it gets better soon :)
 

mifritscher

Senior Member
Aug 5, 2007
52
38
Here it is: http://pastebin.com/g0hGKYDr

2 things:
* there seem to be iommu problems.
[20284.027649,1] kgsl kgsl-3d0: |kgsl_iommu_fault_handler| GPU PAGE FAULT: addr = 1122C100 pid = 210
[20284.027771,1] kgsl kgsl-3d0: |kgsl_iommu_fault_handler| context = 0 FSR = 4001000A
pid 210 is /system/bin/surfaceflinger
* the Kernel panic - seems to be network/selinux related
[20290.881303,0] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[20290.881395,0] pgd = cb96c000
[20290.881487,0] [00000000] *pgd=83ff9831, *pte=00000000, *ppte=00000000
[20290.881731,0] Internal error: Oops: 17 [#1] PREEMPT SMP
[20290.881822,0] Modules linked in: tcp_westwood cfg80211
[20290.882036,0] CPU: 0 Not tainted (3.0.101-gff9641e #1)
[20290.882158,0] PC is at avc_has_perm_flags+0x178/0x1b0
[20290.882219,0] LR is at avc_has_perm_flags+0x114/0x1b0
[20290.882280,0] pc : [<c039dfa8>] lr : [<c039df44>] psr: a0000013
[20290.882280,0] sp : c38f9bf8 ip : 00000000 fp : c005f000
[20290.882463,0] r10: 00000000 r9 : c38f9c80 r8 : 00000004
[20290.882524,0] r7 : 00000122 r6 : 00000122 r5 : 00000000 r4 : 20000000
[20290.882616,0] r3 : 20000000 r2 : 00000000 r1 : 00000000 r0 : 00000000
[20290.882677,0] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[20290.882799,0] Control: 10c5787d Table: 9226c06a DAC: 00000015
...
[20291.346007,0] [<c039dfa8>] (avc_has_perm_flags+0x178/0x1b0) from [<c03a4f78>] (selinux_netlink_recv+0x8c/0xb8)
[20291.347990,0] [<c03a4f78>] (selinux_netlink_recv+0x8c/0xb8) from [<c014f378>] (audit_receive+0xc8/0xb50)
[20291.349944,0] [<c014f378>] (audit_receive+0xc8/0xb50) from [<c07eb47c>] (netlink_unicast+0x330/0x348)
[20291.351897,0] [<c07eb47c>] (netlink_unicast+0x330/0x348) from [<c07eb834>] (netlink_sendmsg+0x2d4/0x364)
[20291.353087,0] [<c07eb834>] (netlink_sendmsg+0x2d4/0x364) from [<c07a29c4>] (sock_sendmsg+0xdc/0xfc)
[20291.355041,0] [<c07a29c4>] (sock_sendmsg+0xdc/0xfc) from [<c07a5268>] (sys_sendto+0xf0/0x14c)
[20291.356963,0] [<c07a5268>] (sys_sendto+0xf0/0x14c) from [<c0065300>] (ret_fast_syscall+0x0/0x30)
[20291.358856,0] Code: e3590000 e0032001 0affffcb e5990038 (e5900000)
[20291.359863,0] Kernel panic - not syncing: Fatal exception
[20291.361602,1] CPU1: stopping
[20291.361694,1] [<c006cd24>] (unwind_backtrace+0x0/0x108) from [<c006b4bc>] (handle_IPI+0x1fc/0x234)
[20291.361816,1] [<c006b4bc>] (handle_IPI+0x1fc/0x234) from [<c005f554>] (gic_handle_irq+0xc4/0xe8)
[20291.361908,1] [<c005f554>] (gic_handle_irq+0xc4/0xe8) from [<c098f4d4>] (__irq_svc+0x54/0x80)
[20291.361969,1] Exception stack(0xc3d49f68 to 0xc3d49fb0)
[20291.362091,1] 9f60: b218b000 00000817 b4a1c078 800e0030 ffffffff 00000000
[20291.362182,1] 9f80: 00000001 00007c80 b4d43400 a0b3c1f4 a1b49600 a0b3c194 b6d5d668 c3d49fb0
[20291.362243,1] 9fa0: c098f650 c098f654 800e0113 ffffffff
[20291.362366,1] [<c098f4d4>] (__irq_svc+0x54/0x80) from [<c098f654>] (__dabt_usr+0x34/0x40)
 
Last edited:

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,925
Prague
android.doshaska.net
Here it is: http://pastebin.com/g0hGKYDr

2 things:
* there seem to be iommu problems.

pid 210 is /system/bin/surfaceflinger
* the Kernel panic - seems to be network/selinux related

Thanks.

The kgsl iommu faults are unrelated to your issue and known. I hope to be able to do something about it. I'm just hardly finding any free time for this stuff, but I still hope it will change.

The null pointer dereference in avc_has_perm_flags is the issue of immediate concern here.
It would help if you could reproduce the crash while running the kernel build whose build artefacts I currently have in the 'out' of my build server, so I could use addr2line to identify the exact spot where the null pointer dereference happens.
Please get this boot.img: https://drive.google.com/open?id=0B4F5il5451vad0czaVdqSi1FU28 , reboot to bootloader and flash it by
Code:
fastboot flash boot boot.img
, than post the last_kmsg after the crash again. Thanks.
 

mifritscher

Senior Member
Aug 5, 2007
52
38
Here it is: http://pastebin.com/7aj7sutj

Code:
[  362.814558,0] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[  362.814680,0] pgd = c3fb4000
[  362.814741,0] [00000000] *pgd=a6d1c831, *pte=00000000, *ppte=00000000
[  362.814985,0] Internal error: Oops: 17 [#1] PREEMPT SMP
[  362.815046,0] Modules linked in: tcp_westwood cfg80211
[  362.815321,0] CPU: 0    Not tainted  (3.0.101-12682-g81810084b62e-dirty #1)
[  362.815382,0] PC is at avc_has_perm_flags+0x150/0x198
[  362.815504,0] LR is at avc_has_perm_flags+0xdc/0x198
[  362.815565,0] pc : [<c031a988>]    lr : [<c031a914>]    psr: a0000013
[  362.815565,0] sp : c3f4bc00  ip : c3f4bc88  fp : c8ef9230
[  362.815717,0] r10: c3f4bd74  r9 : c3f4bc28  r8 : 00000004
[  362.815809,0] r7 : 00000124  r6 : 00000124  r5 : 00000000  r4 : 20000000
[  362.815870,0] r3 : 00000000  r2 : 20000000  r1 : 00000000  r0 : 00000000
[  362.815962,0] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[  362.816023,0] Control: 10c5787d  Table: 841b406a  DAC: 00000015
[  362.816114,0] 
[  362.816114,0]  Before flush cache...
[  362.816236,0] 
[  362.816236,0] PC: 0xc031a908:

....

[  363.516954,0] [<c031a988>] (avc_has_perm_flags+0x150/0x198) from [<c0320eac>] (selinux_netlink_recv+0x84/0xa0)
[  363.519029,0] [<c0320eac>] (selinux_netlink_recv+0x84/0xa0) from [<c0317ca8>] (security_netlink_recv+0x18/0x1c)
[  363.521104,0] [<c0317ca8>] (security_netlink_recv+0x18/0x1c) from [<c01181e8>] (audit_receive+0x7c/0x9c0)
[  363.523149,0] [<c01181e8>] (audit_receive+0x7c/0x9c0) from [<c06c4f4c>] (netlink_unicast+0x290/0x334)
[  363.525164,0] [<c06c4f4c>] (netlink_unicast+0x290/0x334) from [<c06c5348>] (netlink_sendmsg+0x2b8/0x350)
[  363.526384,0] [<c06c5348>] (netlink_sendmsg+0x2b8/0x350) from [<c06858f0>] (sock_sendmsg+0xc4/0xec)
[  363.527605,0] [<c06858f0>] (sock_sendmsg+0xc4/0xec) from [<c0687b9c>] (sys_sendto+0xe4/0x128)
[  363.529619,0] [<c0687b9c>] (sys_sendto+0xe4/0x128) from [<c0059a20>] (ret_fast_syscall+0x0/0x30)
[  363.531573,0] Code: e0023001 0affffd0 e59dc078 e59c0038 (e5900000) 
[  363.532641,0] Kernel panic - not syncing: Fatal exception
[  363.534472,1] CPU1: stopping
[  363.534533,1] [<c005f418>] (unwind_backtrace+0x0/0xf4) from [<c005e860>] (handle_IPI+0x1b0/0x1c4)
[  363.534655,1] [<c005e860>] (handle_IPI+0x1b0/0x1c4) from [<c0054490>] (gic_handle_irq+0x88/0xa8)
[  363.534777,1] [<c0054490>] (gic_handle_irq+0x88/0xa8) from [<c083d054>] (__irq_svc+0x54/0x80)
[  363.534838,1] Exception stack(0xd4a31f68 to 0xd4a31fb0)
[  363.534930,1] 1f60:                   a1619200 0000081f b5d82b16 20030030 ffffffff bea4f2b4
[  363.535052,1] 1f80: 00000045 a1619200 00000000 a1619318 00000046 bea4f3f8 b6ca9970 d4a31fb0
[  363.535113,1] 1fa0: c083d1d0 c083d1d4 20030113 ffffffff
[  363.535205,1] [<c083d054>] (__irq_svc+0x54/0x80) from [<c083d1d4>] (__dabt_usr+0x34/0x40)
[  367.055821,0] SMP: failed to stop secondary CPUs
[  367.056859,0] mbm_version=0x0000109b
[  367.057927,0] CPU type is ACPU PVS: Nominal
[  367.280329,0] Crash partition in use!
[  367.282374,0] wcnss_8960: crash shutdown : 0
[  367.384068,0] Rebooting in 5 seconds..
[  372.406592,0] Going down for restart now


 uname -a
Linux localhost 3.0.101-12682-g81810084b62e-dirty #1 SMP PREEMPT Wed Dec 14 00:32:02 CET 2016 armv7l
 
  • Like
Reactions: kabaldan

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,925
Prague
android.doshaska.net

fixed boot.img for testing: https://drive.google.com/open?id=0B4F5il5451vad0czaVdqSi1FU28

https://github.com/nadlabak/android_kernel_motorola_msm8960-common/commits/cm-13.0

The main fix for the crash is "security: remove the security_netlink_recv hook as it is equivalent to capable()", but the selinux code asked for a few more commits to be backported as well, in addition to the selinux stuff I pushed on September 9 and 11 (which caused the breakage for you).

Thanks for the report.
 

mifritscher

Senior Member
Aug 5, 2007
52
38
Yes, it works again :) Now I can do my heavy work (libreoffice, latex etc.) on my phone again - nobody speaks of playing widelands or manaplus, does anybody? *grin*
Many thanks for the fast fix!
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,853

enigma9o7

Senior Member
Jun 26, 2014
215
34
San Jose
My understanding is cyanogenmod is no more, and it's replacement (lineage) only supports 80 devices, ours not included...

Will there be any more builds for PQ, if so, where to look for them? Maybe here (xda)?
 

mifritscher

Senior Member
Aug 5, 2007
52
38
@ Lineageos: I think that just waiting for 1-2 months is the best thing ;)

I stumbled over another nasty thing in CM which I observed for long time (many months, if not years): In the "charge only" mode the Photon Q consumes about 2,5W - even if the battery is full and the display off. The phone gets quite warm, too. In normal "on" mode I don't see the problem. On normal power supplies, it is not such big problem (but wasting power is never a good thing), but when you charge it via battery or a solar backed supply it is a quite nasty thing.
I first blamed the HW, but I've the problem on 2 Photon Q...
 

amedeh123

Senior Member
Aug 5, 2012
268
65
Is kabaldan taking logs and/or bug reports for the RHD currently? Last I checked the devs deunified the ROMs because it was too hard to maintain.

Ive been using it on the RHD for quite a long time now, its very good but there are a few quirks that I havent seen mentioned here.
 

enigma9o7

Senior Member
Jun 26, 2014
215
34
San Jose
I recently wiped everything and flashed the 1219 (latest) rom and gapps. I have one issue I never had before, chrome won't ever load. Maybe I selected something wrong in the gapps install tho.

But I have one other weird issue for a while and maybe it's just settings related. The hardware keyboard is inconsistent with regards to shift. Sometimes, I have to hold shift to get a capital letter, sometimes I can just push shift first then the next letter is capital. At some point, I can't remember when (CM11 for sure) it always worked with shift first.
 

tobby88

Senior Member
Jul 4, 2012
231
58
Hanover
OnePlus 5
I recently wiped everything and flashed the 1219 (latest) rom and gapps. I have one issue I never had before, chrome won't ever load. Maybe I selected something wrong in the gapps install tho.

Are you getting something like "native crash"? I have the same issue. Also several other apps wont work correctly, like GMail, dict.cc, HVV, ... At some points in the apps they don't render correctly so the background of the app is there but the foreground is invisible.

Since I wiped everything on my phone and also reinstalled much older CM- and GApps-versions I thought this is a hardware related issue. But if you experience the same I am not sure anymore ^^

On my phone these problems started somewhere at the end of November or beginning of of december after an update of CM and Gapps. But since these problems also persist after a full wipe and flashing much older stuff (like the last snapshot of August and the Gapps of the same day) I don't know how to get rid of this problem. I flashed, wiped and tested for two full days with all possible combinations of CM and Gapps. Then I "threw my Photon Q away" and am using my old Droid 4 again :-/ But since I am not the only one anymore now I may try more stuff to fix this on my PQ.

Is there any hidden partition which may have been corrupted by a newer build of CM/Gapps?
 

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,925
Prague
android.doshaska.net
I recently wiped everything and flashed the 1219 (latest) rom and gapps. I have one issue I never had before, chrome won't ever load. Maybe I selected something wrong in the gapps install tho.

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.
 
Last edited:

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,925
Prague
android.doshaska.net
Is kabaldan taking logs and/or bug reports for the RHD currently? Last I checked the devs deunified the ROMs because it was too hard to maintain.

Ive been using it on the RHD for quite a long time now, its very good but there are a few quirks that I havent seen mentioned here.

Yes, please let me know about the issues you're experiencing, thanks. Despite the cracked screen I haven't bothered to replace yet, my xt925 is still functioning well enough, so I'm able to debug things on it (when I get to it).
 

ichbinsinaction

New member
Feb 16, 2014
2
0
Hello community,

I'm sorry that I have to ask this, but my system (last stable CM12.1) died yesterday (boot loop) after causing troubles for weeks and I need to set up a new one. I already deleted everything to make sure the new system doesn't cause the same troubles all over again, but trying to download a new CM13, I had to notice, that the download servers are unavailable.
I keep checking since yesterday afternoon and reloading all the time, but it's just not available.

So could somebody download a more or less stable cm13 for me, or tell me where I can download it?
Thank you in advance and sorry for the inconvenience...

EDIT: I just found an old install file on my old computer. I'm sorry.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    This is for CyanogenMod 13.0, Android version 6.0.1, unofficial builds whose primary purpose is meant as preview.

    Credits: All credits go to kabaldan, stargo and CyanogenMod contributors.

    Disclaimer
    Code:
    Use at your own risk, responsibility is all yours, provided as-is, no warranties...
    You know the drill.

    What has changed/is new can be viewed at cyanogenmod gerrit: http://review.cyanogenmod.org/#/q/status:merged
    Latest change for the January 30, 2016. build is at http://review.cyanogenmod.org/#/c/130563/
    Latest change for the February 13, 2016. build is at http://review.cyanogenmod.org/132753
    Latest change for the March 21, 2016. build is at http://review.cyanogenmod.org/127971


    • SELinux is disabled (if you care about security you'd might wan't to wait for an official build)
      • SELinux enabled in March 21. build
    • ART preopotimization is enabled: speeds up first boot after wiping dalvik cache: only some of framework, GApps (if present) and user installed apps need to be compiled. It also saves some space in /data as system apps odex/art/oat files are stored in /system partition instead of /data/dalvik-cache. This is the reason for the large size of the update package.
    • disabled GPU page faults logging in kernel as it only (unnecessarily) spams the logs
    • Included the new Snap camera app (the old AOSP Camera2 is still kept as a fallback): Both are called "Camera" but you'll be able to easily differentiate between them by the icon.
    • Keyboard backlight behaviour has been updated to resemble stock-like behaviour. Details can be read in the commit message of the change (Patchset 1, not PS2, or here). Feel free to test and share what you think.
      • Reverted to old keboard backlight behaviour in March 21 build
    All relevant changes (i.e. differences from default/stock CM13) can be viewed at my github repo

    Installation (first time install):
    1) Download the build
    2) Boot into recovery (power button + voulme up)
    3) Make a full nandroid backup
    4) Flash update package (install zip ...)
    5) Wipe data/cache (factory reset)
    6) Reboot to system

    Update (if you're updating existing cm-13.0 or upgrading from cm-12.1)
    1) Download newer update zip file and install it from recovery.
    2) Wipe dalvik-cache
    3) Reboot to system

    It might be useful to enable aplogd logging, especially if you come across some issues.
    You can enable aplogd in terminal or adb shell
    Code:
    su
    setprop persist.log.aplogd.enable 1
    Logs are saved in /data/aplogd/

    In case of a full system reboot include /proc/last_kmsg as well.

    NOTE !!! :
    Please do make a full nandroid backup! In case anything goes wrong or you simply wan't to go back, you should be able to recover/restore in a jiffy. If, by chance, you have issues restoring system when twrp claims it failed to mount system, a relatively simple workaround is to flash whichever CM update, flash GApps you used previously and then restore only data, wipe dalvik, reboot... hope for the best...

    Downloads

    March 21, 2016.
    Some of changes:
    Code:
    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
    All details can seen at CM gerrit and my github repo (not very practical but...)
    MD5: 96ce2fc03b43c0123fcdc559fb531761
    File size: 348,852,931 bytes
    Download

    February 13, 2016.
    MD5: 19d3cb88cdc9a1cf1857b3e263298b19
    File size: 348,081,995 bytes
    Download

    January 30, 2016.
    MD5: 454c62323c5e8f93f96ec6a9de580a2f (or use the attached to post md5sum file)
    File size: 343,989,482 bytes
    Download
    10
    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:

    Before I trigger the official cm-13.0 builds for xt897, the following requirements have to be met:
    - CVE kernel patches needs to be merged /* done today, finally */
    - SELinux policy issues needs to be resolved (so we can run enforcing) /* in progress */
    - an appropriate PowerHAL implementation needs to be used /* looking into it; the flo PowerHAL, used also by d2 looks promising */

    Yes, I'm very slow/busy/lazy, sorry for that, but moving forward nevertheless :) .
    8
    cm-13.0-20160213-UNOFFICIAL-xt897

    Uploaded new build (check first post) or directly download
    MD5: 19d3cb88cdc9a1cf1857b3e263298b19
    File size: 348,081,995 bytes

    Some of (more important) changes:
    - CVE patched kernel as kabaldan mentioned
    - Kernel updates to f2fs filesystem
    - Using simpler dialog during initial dexopt (first boot after wiping dalvik cache). More details here. (haven't measured but seems to improve dexopt times slightly)
    - Enabled call recording (actual support depends if call recording is legal in your country)
    - etc. (quite a bit changed/updated/fixed/improved in the past two weeks...)

    Latest sync point on cyanogenmod gerrit is http://review.cyanogenmod.org/132753
    Other/all differences from official cyanogenmod can be seen here.
    7
    Any news about porting cm14 for Photon Q?

    No time for Android when you're building a castle. But don't worry, only the roof, the ballroom, the cowshed and a few animals are left to do.

    Anyway, cm14.0 was going rather well the last time I messed with it, before I switched back to cm13.0 on my daily driver Q (to polish a few things that will be required by 14 anyway and can be done under 13 already). I'll get back to the work on cm 14.1 hopefully soon.
    6
    cm-13.0-20160321-UNOFFICIAL-xt897.zip

    Uploaded new build.
    All credits and thanks go to kabaldan, stargo and other CM contributors.

    NOTE:
    Build from March 20 has been invalidated in favor of March 21 as the previous update (March 20) introduced a bug in interactive governor where CPU frequency would be stuck at minimum (384 MHz) if io_is_busy set to 0.
    io_is_busy: sysfs flag that determines if waiting for IO should increase CPU utilization/bump up CPU frequency (performance vs. power). Glimpsed through it, seems to be used only by performace profiles (configurable under Battery settings). Not sure if these are toggled unless instructed/enabled by a setting (under Battery).
    Not fully functional yet, can't set Power save profile.
    Other partially fail with "E/PowerHAL( 762): Error opening /sys/kernel/cpufreq_limit/limited_[min/max]_freq: Permission denied" (Probably just needs to set group to system)

    March 21, 2016.

    Latest sync point: http://review.cyanogenmod.org/127971

    Some of changes:
    Code:
    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
    All details can seen at CM gerrit and my github repo (not very practical but...)
    MD5: 96ce2fc03b43c0123fcdc559fb531761 (check first post for md5sum file in the attachements)
    File size: 348,852,931 bytes
    Check first post or download here
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone