CyanogenMod 12.1 for Photon Q (Android 5.1)

Search This thread

bmccrary

Member
Sep 3, 2014
40
14
I sent logs yesterday to kabaldan. Hopefully it will help! Now that I finally have nandroid working I can flip between the images pretty quick.
 
  • Like
Reactions: tzuba12

Dreamliners

Member
Jan 13, 2011
44
8
Hi.

Below you can find an unofficial cm13 recovery flashable zip. This primarily servers as preview only.
ALL credits go to kabaldan and CyanogenMod contributors (I only compiled the thing).

It includes all changes up to, and including, http://review.cyanogenmod.org/125925.

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...

Happy New Year.

MD5: 56eca73e3a1fe2b5883aac3e90ba7d4c (or use the attached to post md5sum file)
File size: 341,428,773 bytes
Download

Can someone reupload this? The link is dead.
Thanks.
 

rabinhood

Senior Member
Feb 16, 2009
396
74
Katowice
Interesting. I used CM11, I'm using latest build of CM12.1 now, but I never encountered any problems with unstable wi-fi connection. I even find PQ to catch poor wi-fi signal better then Droid 3 and Milestone 2, which I've used before.
 

Y_Yan_C

Senior Member
Jan 25, 2010
609
50
Waterloo
battery

what is the average screen on time for you guys on the latest 12.1 build? my battery gets bloated at times and the battery life is balls
 

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,926
Prague
android.doshaska.net
anyone know how to disable car mode?
one of the things that bothers me when i dock the q in the official cardock....uhg
as of now, i have Car Dashdroid installed, and when cardocked both applications open, however it then gives me the option to exit carmode.
I am just hoping to avoid this whole process, and never have anything open.

Not sure what you mean by "both applications open" - I have only Car Dashdroid opening upon docking as I marked it to be the default app for car dock.

Nevertheless, the easiest way to disable the dock detection is to remove (or rename) /system/bin/whisperd .
 

Shaker1978

Member
Oct 7, 2014
20
0
www.satria.de
Can it be Android-/ Cyanogen related to have an extremely poor WLAN signal? Or must it be a hardware / antenna issue? I have 1 MBit/s when 2m away from access point... :( Have tried CM 12.1 (20151007) and CM 12.1 (20160323)
 

bmccrary

Member
Sep 3, 2014
40
14
I haven't seen CM have any affect on WLAN signal. On both CM 12.1/CM13 the performance was same as stock 4.1.2. With that being said the Photon Q has never been the best device as I have a tablet and laptop beside me that have a little better signal. But I'm seeing 36MBps about 50ft away through 4 sheetrock walls and 65MBps closer to the access point. So I'd say it's the antenna or the mainboard itself. If you have a spare back piece (the one with the flash and the speaker built-in to it) I would give that a try. If you need one PM me, I'm sure I have a few laying around! :)
 

palmwangja

Senior Member
Feb 20, 2008
437
28
xt897 is officially supported by CM 13.0: http://get.cm/?device=xt897&type=
It probably just downloaded the latest available update, despite release version change. Perhaps a bug/inconsistency in cm updater?
dirty flashing CM13 over CM12.1 was causing lots of errors after reboot in my case, and I had to factory-reset.
No biggie though. a couple of hours of efforts will get you a clean looking phone!
 

Shaker1978

Member
Oct 7, 2014
20
0
www.satria.de
I haven't seen CM have any affect on WLAN signal. On both CM 12.1/CM13 the performance was same as stock 4.1.2. With that being said the Photon Q has never been the best device as I have a tablet and laptop beside me that have a little better signal. But I'm seeing 36MBps about 50ft away through 4 sheetrock walls and 65MBps closer to the access point. So I'd say it's the antenna or the mainboard itself. If you have a spare back piece (the one with the flash and the speaker built-in to it) I would give that a try. If you need one PM me, I'm sure I have a few laying around! :)
Thanks, pal. I'm going to return the broken thing to the seller, since he said, it's technically 100% ok.

The problem is - I am in Germany and I need a Photon Q with SIM mod. The only problem left for me is getting the SIM chip removed. This is something I cannot do myself. I am able to do the rest of the work, but not removing the chip. I've just bought another XT897 mainboard from ebay and will try to find a solution. But this is getting off-topic ;)
Thanks for your offer.
 

enigma9o7

Senior Member
Jun 26, 2014
218
34
San Jose
F(x)tec Pro1-X
Where can I get the last CM 12.1 build? The only thing left on cyanogen downloads page is 7 October last year. I'm running a monthly from February and am not quite ready to try marshmellow (feels like I just started with lollipop) but may as well be as up to date as possible for 12.1 but missed it when it was available as I didn't know it was going to stop being available...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Official cm-12.1 nightlies for Photon Q have been enabled.

    Download link: http://download.cyanogenmod.org/?device=xt897
    Gapps for 5.1 (by dhacker29): https://t.co/bvegrEBSdY
    TWRP 2.8.6.2 recovery for xt897: https://dl.orangedox.com/Ajalit2rGIUYAO8Snc/TWRP-2.8.6.2-xt897.img

    Device specific source repos:
    motorola/xt897: https://github.com/CyanogenMod/android_device_motorola_xt897/tree/cm-12.1
    motorola/msm8960_jbbl-common: https://github.com/CyanogenMod/android_device_motorola_msm8960_jbbl-common/tree/cm-12.1
    motorola/qcom-common: https://github.com/CyanogenMod/android_device_motorola_qcom-common/tree/cm-12.1
    kernel: https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common/tree/cm-12.1

    Please note:
    Since CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead. Use xt897 specific builds when you go beyond CM11.

    GSM users (SIM card mod):
    Please switch the Settings>Mobile networks>Preferred network type to 'GSM/WCDMA auto' or 'GSM/WCDMA preferred' from 'Global' for correct modem functionality on GSM networks.

    What's new in cm-12.1 for xt897:

    Lollipop turned out to be very RAM demanding. 1GB RAM devices seem to be below the limit of what lollipop actually needs.
    To overcome this issue, 256MB of RAM has been dedicated to zram (compressed swap living in RAM). Zram can give us a bit more of effectively usable RAM space.
    To speed-up the zram operations, kernel has been updated to the latest zram code with support for the fast lz4 compression.
    Another new kernel addition is cpu-boost driver that can boost cpu frequency e.g. when input events are happening (touch screen interaction) regardless of cpu governor in use.

    Known issues:
    - USB audio output (analogue) via USB>audio Y-cable (Motorola Car Dock/EMU audio) is not working correctly yet
    - USB audio DACs/sound cards connected as USB OTG peripheral do not work correctly yet
    7
    cm-13.0 UNOFFICIAL (PREVIEW)

    Hi.

    Below you can find an unofficial cm13 recovery flashable zip. This primarily servers as preview only.
    ALL credits go to kabaldan and CyanogenMod contributors (I only compiled the thing).

    It includes all changes up to, and including, http://review.cyanogenmod.org/125925.


    • SELinux is disabled (if you care about security you'd might wan't to wait for an official build)
    • ART preopotimization is enabled: speeds up first boot after wiping dalvik cache: only 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 actually might be usefull option to be reviewed: with default cm13 install there is just under 440MiB of space left in /system and about 229MiB is saved in /data). This is the reason for the large size of the update package.
    • kernel includes tentative patch for Picture Order Count Type aparently needed to compile the build.
    Apart from those listed above there should be no custom changes present and the "attached" update file is default/stock CM-13.0.




    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...

    Happy New Year.


    MD5: 56eca73e3a1fe2b5883aac3e90ba7d4c (or use the attached to post md5sum file)
    File size: 341,428,773 bytes
    Download
    6
    Ok, just tried it. It failed:

    Code:
    target thumb C: libminzip <= bootable/recovery/minzip/SysUtil.c
    system/core/sdcard/sdcard.c: In function 'fuse_notify_delete':
    system/core/sdcard/sdcard.c:750:35: error: storage size of 'data' isn't known
         struct fuse_notify_delete_out data;
                                       ^
    system/core/sdcard/sdcard.c:756:17: error: 'FUSE_NOTIFY_DELETE' undeclared (first use in this function)
         hdr.error = FUSE_NOTIFY_DELETE;
                     ^
    system/core/sdcard/sdcard.c:756:17: note: each undeclared identifier is reported only once for each function it appears in
    make: *** [/home/tobby/android/cm13/out/target/product/xt897/obj/STATIC_LIBRARIES/libsdcard_intermediates/sdcard.o] Error 1
    make: *** Waiting for unfinished jobs …
    In file included from external/libcxx/include/limits:112:0,
                     from external/libcxx/include/memory:603,
                     from external/libcxx/include/algorithm:628,
                     from external/libcxx/include/string:439,
                     from bootable/recovery/voldclient.h:22,
                     from bootable/recovery/roots.cpp:39:
    external/libcxx/include/__undef_min_max:16:2: warning: #warning : macro min is incompatible with C++. #undefing min [-Wcpp]
     #warning: macro min is incompatible with C++.  #undefing min
      ^
    make: Leaving directory »/home/tobby/android/cm13«
    
    #### make failed to build some targets (12:33 (mm:ss)) ####

    And I don't have any knowledge how to fix that (and no time as well ^^). So we have to wait for someone else to fix this (kabaldan?).

    There are some commits on gerrit that I haven't merged yet:
    http://review.cyanogenmod.org/#/q/owner:pavel%40doshaska.net+status:open+branch:cm-13.0

    For the error above, you should cherry-pick this one: http://review.cyanogenmod.org/118386

    You'll also need to set selinux premissive. Add androidboot.selinux=permissive to cmdline at https://github.com/CyanogenMod/andr...-common/blob/cm-13.0/BoardConfigCommon.mk#L44

    Cm-13.0 for xt897 builds fine and also boots (eventually)...
    The main issue is that the system process is experiencing random mmap failures during boot...

    I'm looking into it (occasionally), but I'm unfortunately busier than ever with both real life and work at this time.
    6
    Just a status update regarding M/cm-13.0:
    http://review.cyanogenmod.org/123002 fixes the mmap failures that bothered me since the beginning of cm-13 bring-up.
    Next targets for fixes are:
    1. camera fails due to a parameter setting failure
    2. cell data not working in a strange way: e.g. a ping or wget from Android Terminal works just fine, but e.g. Chrome or Play can't connect to servers at all (no such issue on wifi)

    I hope to find some time to look into it during the coming holidays. Let's see...
    5
    Nice!

    So only camera is causing problems, the rest seems to be working fine?

    The camera can work immediately, if we break some NDK compatibility. The current problem is to find a viable non-NDK-breaking workaround for it. See http://review.cyanogenmod.org/125382

    I've already switched my last non-shattered-screen xt897@cm-13.0 to serve as my daily driver and it seems to do what I usually need rather fine (well, if you don't look at the logs to see the problems ;) - kgsl kgsl-3d0: |kgsl_iommu_fault_handler| GPU PAGE FAULT: addr = xxxxxxxx pid = 0 in dmesg asks for attention...).

    Besides the camera, there's still some selinux work to be done, so we can run it in strict mode (that's an imperative for starting the official CM nightlies).
    Gps navigation seems to be fine, I've been using waze and sygic, no issues.
    I expect a2dp to be broken, but I haven't got to testing it yet.
    And the CDMA support is expected to be broken as well, at this point.