• October 2019
 

Pete

Forum Replies Created

 
 
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Moto G LineageOS 14.1, Nougat 7.1 ROM #12543

    Pete
    Member

    So, the eventual upshot of all this is that I’ve spent the day backing up all the important data and factory resetting so I can get back to a working state (CM13).
    It turns out the Moto G 1st gen doesn’t have enough space in the system partition to get open gapps anything higher than micro. The nightly builds aren’t stable (freezing and rebooting) and the experimental version has “cm to lineage migration” water marked on the screen, and suffers from similar instabilities.

    The most notable difference is the lack of customizability of the notification area. I couldn’t find a way of toggling the lock screen, like in CM13. Also selecting which Launcher was difficult/impossible to find (I prefer Apex rather than Trebuchet).

    Lesson learnt, make a complete backup of the data and system partitions before attempting to flash Lineage again.
    Hope this helps other Moto G users, in knowing (at least) what not to do.

    in reply to: Moto G LineageOS 14.1, Nougat 7.1 ROM #12487

    Pete
    Member

    Well, it seems I can’t go back to CM13, I get stuck in another boot loop:

    02-07 22:50:18.681  1493  1493 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider com.android.providers.downloads.DownloadProvider: android.database.sqlite.SQLiteException: Can't downgrade database from version 110 to 109
    

    🙁 I was trying to avoid a complete wipe to preserve my app data.. having re-read the install guide for CM14.1 I should have guessed I wouldn’t able to go back. Alas.
    I’ll do a factory reset and see how it goes.

    EDIT: Managed to get to CM14 via the CM-Lineage experimental image 😀
    Still getting some weird freezes, though.. sometimes long presses cause the main UI to become unresponsive.. when pressing the power button the screen doesn’t come back on.. both require a restart..
    Shall keep trying.

    in reply to: Moto G LineageOS 14.1, Nougat 7.1 ROM #12480

    Pete
    Member

    @shibaa987 Thanks for your reply.
    I was trying to flash it manually, and had placed it in the /sdcard/cmupdater folder.
    I did try it with the system partition mounted and unmounted. I was using TWRP v2.8.6.0.
    The problem seemed to be the lack of directory /dev/block/bootdevice/
    I did find a work around though. Through adb shell with working system:

    root@falcon:/ # ls -la /dev/block/bootdevice/by-name/system                                                                     
    lrwxrwxrwx    1 0        0               21 Apr 11  1970 /dev/block/bootdevice/by-name/system -> /dev/block/mmcblk0p34
    

    Then using adb shell in TWRP:

    mkdir -p /dev/block/bootdevice/by-name/
    ln -s /dev/block/mmcblk0p34 /dev/block/bootdevice/by-name/system
    

    This allowed the path looked for by the script to find the system partition.
    It worked for lineage-14.1-20170119-UNOFFICIAL-falcon.zip, but not lineage-14.1-20170131-nightly-falcon-signed.zip. Screenshots attached.

    However, this method didn’t seem to work. Judging from dmesg, it seem to be stuck in a loop before booting completed:

    [   65.855977,0] init: Starting service 'netd'...
    [   65.857085,0] init: Starting service 'media'...
    [   65.858006,0] init: Starting service 'zygote'...
    [   66.362293,3] MSM-CPP cpp_load_fw:876 MC Bootloader Version: 0x312e3176
    [   66.367687,2] MSM-CPP cpp_load_fw:888 CPP FW Version: 0x1002000a
    [   66.479033,3] msm_cci_ioreg_enable failed to get regulator
    [   66.479481,3] ar0543_set_lsc: Setting module LSC!
    [   66.486794,2] msm_sensor_config:1732 sensor state 1
    [   66.694318,0] msm_post_event : timeout cannot be negative Line 715
    [   66.837148,2] msm_sensor_config:1760 sensor state 0
    [   66.877654,3] MSM-CPP cpp_load_fw:876 MC Bootloader Version: 0x312e3176
    [   66.882302,3] MSM-CPP cpp_load_fw:888 CPP FW Version: 0x1002000a
    [   66.905687,2] msm_cci_ioreg_enable failed to get regulator
    [   67.033778,1] msm_post_event : timeout cannot be negative Line 715
    [   69.469949,3] type=1400 audit(1486504071.698:35): avc: denied { setgid } for uid=0 pid=3276 comm="debuggerd" capability=6 scontext=u:r:debuggerd:s0 tcontext=u:r:debuggerd:s0 tclass=capability permissive=0
    [   69.503345,0] init: Service 'zygote' (pid 3028) exited with status 0
    [   69.503491,0] init: Service 'zygote' (pid 3028) killing any children in process group
    [   69.503727,0] init: write_file: Unable to open '/sys/android_power/request_state': No such file or directory
    [   69.503946,0] init: write_file: Unable to write to '/sys/power/state': Invalid argument
    [   69.504145,0] init: Service 'media' is being killed...
    [   69.504521,0] init: Service 'netd' is being killed...
    [   69.506511,0] init: Untracked pid 3278 killed by signal 9
    [   69.506958,0] init: Service 'netd' (pid 3026) killed by signal 9
    [   69.507152,0] init: Service 'netd' (pid 3026) killing any children in process group
    [   69.511720,0] init: Service 'media' (pid 3027) killed by signal 9
    [   69.511931,0] init: Service 'media' (pid 3027) killing any children in process group
    [   69.512684,0] init: Starting service 'thermal-engine'...
    [   69.534134,3] type=1400 audit(1486504071.761:36): avc: denied { setgid } for uid=0 pid=3280 comm="debuggerd" capability=6 scontext=u:r:debuggerd:s0 tcontext=u:r:debuggerd:s0 tclass=capability permissive=0
    [   69.535820,0] init: Service 'thermal-engine' (pid 3279) exited with status 0
    [   69.535969,0] init: Service 'thermal-engine' (pid 3279) killing any children in process group
    [   70.537865,0] init: Starting service 'netd'...
    [   70.538885,0] init: Starting service 'media'...
    [   70.539952,0] init: Starting service 'zygote'...
    [   70.994324,2] MSM-CPP cpp_load_fw:876 MC Bootloader Version: 0x312e3176
    [   70.998966,3] MSM-CPP cpp_load_fw:888 CPP FW Version: 0x1002000a
    [   71.109072,0] msm_cci_ioreg_enable failed to get regulator
    [   71.109627,0] ar0543_set_lsc: Setting module LSC!
    [   71.116800,0] msm_sensor_config:1732 sensor state 1
    [   71.318995,3] msm_post_event : timeout cannot be negative Line 715
    [   71.466730,0] msm_sensor_config:1760 sensor state 0
    [   71.504336,1] MSM-CPP cpp_load_fw:876 MC Bootloader Version: 0x312e3176
    [   71.508952,2] MSM-CPP cpp_load_fw:888 CPP FW Version: 0x1002000a
    [   71.535677,1] msm_cci_ioreg_enable failed to get regulator
    [   71.658819,3] msm_post_event : timeout cannot be negative Line 715
    [   74.099000,3] type=1400 audit(1486504076.325:37): avc: denied { setgid } for uid=0 pid=3530 comm="debuggerd" capability=6 scontext=u:r:debuggerd:s0 tcontext=u:r:debuggerd:s0 tclass=capability permissive=0
    [   74.127230,0] init: Service 'zygote' (pid 3283) exited with status 0
    [   74.127453,0] init: Service 'zygote' (pid 3283) killing any children in process group
    [   74.127762,0] init: write_file: Unable to open '/sys/android_power/request_state': No such file or directory
    [   74.128029,0] init: write_file: Unable to write to '/sys/power/state': Invalid argument
    [   74.128186,0] init: Service 'media' is being killed...
    [   74.128816,0] init: Service 'netd' is being killed...
    [   74.131260,0] init: Untracked pid 3533 killed by signal 9
    [   74.131806,0] init: Service 'netd' (pid 3281) killed by signal 9
    [   74.131952,0] init: Service 'netd' (pid 3281) killing any children in process group
    [   74.138334,0] init: Service 'media' (pid 3282) killed by signal 9
    [   74.138463,0] init: Service 'media' (pid 3282) killing any children in process group
    [   75.140240,0] init: Starting service 'thermal-engine'...
    [   75.160590,3] type=1400 audit(1486504077.388:38): avc: denied { setgid } for uid=0 pid=3537 comm="debuggerd" capability=6 scontext=u:r:debuggerd:s0 tcontext=u:r:debuggerd:s0 tclass=capability permissive=0
    [   75.162303,0] init: Service 'thermal-engine' (pid 3536) exited with status 0
    [   75.162486,0] init: Service 'thermal-engine' (pid 3536) killing any children in process group
    [   76.164380,0] init: Starting service 'netd'...
    [   76.165540,0] init: Starting service 'media'...
    [   76.166524,0] init: Starting service 'zygote'...
    

    I reset and managed to upgrade to TWRP v3.0.2.2. This time I still could install lineage-14.1-20170119-UNOFFICIAL-falcon.zip, but still not lineage-14.1-20170131-nightly-falcon-signed.zip. Screenshots attached.

    Unfortunately it seems to enter a different boot loop, where the watchdog kicks in after loading the screen lock.. If I manage to unlock it before it resets, then the Privacy Guard dialog box kicks in, asking if the Dictionary and Gmail can read my contacts.. It eventually hangs, then the watchdog kicks in and another reboot loop occurs:

    02-07 22:09:34.562  3155  3678 W Watchdog: *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in monitor com.android.server.am.ActivityManagerService on foreground thread (android.fg), Blocked in handler on main thread (main), Blocked in handler on ActivityManager (ActivityManager)
    02-07 22:09:34.562  3155  3678 W Watchdog: foreground thread stack trace:
    02-07 22:09:34.563  3155  3678 W Watchdog:     at com.android.server.am.ActivityManagerService.monitor(ActivityManagerService.java:21869)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at com.android.server.Watchdog$HandlerChecker.run(Watchdog.java:182)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.os.Handler.handleCallback(Handler.java:751)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.os.Handler.dispatchMessage(Handler.java:95)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.os.Looper.loop(Looper.java:154)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.os.HandlerThread.run(HandlerThread.java:61)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at com.android.server.ServiceThread.run(ServiceThread.java:46)
    02-07 22:09:34.563  3155  3678 W Watchdog: main thread stack trace:
    02-07 22:09:34.563  3155  3678 W Watchdog:     at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:18710)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.app.ContextImpl.sendBroadcastAsUser(ContextImpl.java:1063)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.app.ContextImpl.sendBroadcastAsUser(ContextImpl.java:1052)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at com.android.server.DropBoxManagerService$3.handleMessage(DropBoxManagerService.java:173)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.os.Handler.dispatchMessage(Handler.java:102)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at android.os.Looper.loop(Looper.java:154)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at com.android.server.SystemServer.run(SystemServer.java:376)
    02-07 22:09:34.563  3155  3678 W Watchdog:     at com.android.server.SystemServer.main(SystemServer.java:233)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at java.lang.reflect.Method.invoke(Native Method)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
    02-07 22:09:34.564  3155  3678 W Watchdog: ActivityManager stack trace:
    02-07 22:09:34.564  3155  3678 W Watchdog:     at com.android.server.am.ActivityManagerService.setRenderThread(ActivityManagerService.java:12831)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.ThreadedRenderer$ProcessInitializer.initSched(ThreadedRenderer.java:919)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.ThreadedRenderer$ProcessInitializer.init(ThreadedRenderer.java:911)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.ThreadedRenderer.<init>(ThreadedRenderer.java:364)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.ThreadedRenderer.create(ThreadedRenderer.java:266)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.ViewRootImpl.enableHardwareAcceleration(ViewRootImpl.java:878)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.ViewRootImpl.setView(ViewRootImpl.java:595)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:342)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:94)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.app.Dialog.show(Dialog.java:322)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at com.android.server.AppOpsService$AskRunnable.run(AppOpsService.java:2571)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.os.Handler.handleCallback(Handler.java:751)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.os.Handler.dispatchMessage(Handler.java:95)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.os.Looper.loop(Looper.java:154)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at android.os.HandlerThread.run(HandlerThread.java:61)
    02-07 22:09:34.564  3155  3678 W Watchdog:     at com.android.server.ServiceThread.run(ServiceThread.java:46)
    02-07 22:09:34.565  3155  3678 W Watchdog: *** GOODBYE!
    

    Think I’ll just stick with CM13 for now 😉

    in reply to: [OFFICIAL] Moto G CM14.1 (CyanogenMod 14.1) Nougat 7.1 ROM #12323

    Pete
    Member

    Hi,
    Thanks for the guide.
    (I have already left this comment on the UNOFFICIAL page, but since this is where I got the ROM from, I thought I’d repost it here.

    Moto G Lineage 14.1, Nougat 7.1 ROM


    I’m afraid I’ve encountered a problem when trying to flash CM14.1 on my MotoG XT1032.
    I tried to update from cm-13.0-20160723-NIGHTLY-falcon to cm-14.1-20161218-NIGHTLY-falcon, which failed, then to freshly downloaded lineage-14.1-20170131-nightly-falcon-signed, which also failed. I’m using TWRP and the problem appears to be with trying to mount the system partition. It looks like it’s looking at a path in /dev but can’t find the block device. I took a screenshot to show what the problem was.
    I’ve had to settle for upgrading to cm-13.0-20161220-SNAPSHOT-ZNH5YAO3XK-falcon for now. I managed to build CM13 myself in July, and again around Christmas (just as CyanogenMod shutdown down its servers) and have only just come back. Haven’t done a repo sync yet, since I’m not sure if the git servers are all there.
    Anyway, just a heads up, things don’t seem to be working out of the box at the mo.
    Cheers,
    Pete

    in reply to: Moto G LineageOS 14.1, Nougat 7.1 ROM #12320

    Pete
    Member

    Hi,
    Thanks for the guide. I’m afraid I’ve encountered a problem when trying to flash CM14.1 on my MotoG XT1032.
    I tried to update from cm-13.0-20160723-NIGHTLY-falcon to cm-14.1-20161218-NIGHTLY-falcon, which failed, then to freshly downloaded lineage-14.1-20170131-nightly-falcon-signed, which also failed. I’m using TWRP and the problem appears to be with trying to mount the system partition. It looks like it’s looking at a path in /dev but can’t find the block device. I took a screenshot to show what the problem was.
    I’ve had to settle for upgrading to cm-13.0-20161220-SNAPSHOT-ZNH5YAO3XK-falcon for now. I managed to build CM13 myself in July, and again around Christmas (just as CyanogenMod shutdown down its servers) and have only just come back. Haven’t done a repo sync yet, since I’m not sure if the git servers are all there.
    Anyway, just a heads up, things don’t seem to be working out of the box at the mo.
    Cheers,
    Pete

 
 
Viewing 5 posts - 1 through 5 (of 5 total)