I had camera in use issue after updating cm13. I decided to wipe and try computerfreak stock cleaned ROM. Camera and everything works now but I have a persistent notification to revert my motorola sensor services firmware to previous version.
What's up with this?
Is it safe to proceed?
Daught said:
I had camera in use issue after updating cm13. I decided to wipe and try computerfreak stock cleaned ROM. Camera and everything works now but I have a persistent notification to revert my motorola sensor services firmware to previous version.
What's up with this?
Is it safe to proceed?
Click to expand...
Click to collapse
Your good to go there is a firmware change between marshmallow and lollipop. You go back to lollipop from a marshmallow ROM you will have too. It only takes a couple minutes then your phone will restart and you will be good to go.
Done it. No issues.
Related
I just flashed the Krypton rom and the security settings always crashes whenever I click on it. I have tried wiping cache/dalvik and factory resetting but still no luck. I searched this up and there isn't a clear solution.
Reflash system.img in fastboot
Projectno6 said:
I just flashed the Krypton rom and the security settings always crashes whenever I click on it. I have tried wiping cache/dalvik and factory resetting but still no luck. I searched this up and there isn't a clear solution.
Click to expand...
Click to collapse
What stock rom was on your phone before you tried Krypton?
And What Rom is Krypton based on?
Why do I ask? Well, when Stock Moto 4.4.2 came out, we saw some people try and downgrade by flashing only an older system (since GPT.BIN and Motoboot.img can't be downgraded) and they encountered the same issue... Settings -> Security kicked them back out. So I'm thinking you might be running into something similar. i.e. Krypton you are flashing is based on an older stock ROm than you had flashed on your phone. And since 3rd party roms generally only flash SYSTEM.IMG, its likely you have mismatched parts on the phone which has been shown to cause quirks and issues.
When I got the phone it came with 4.4.4 and 5.0.2 lollipop ready to download. I went ahead and let it download and install 5.0.2 . The battery performance was really disappointing so i decided to unlock the bootloader and restore it back to 4.4.4
But now when i use 4.4.4, the rear camera is not detected by any camera app. To test if it was a hardware or software issue, i updated back to lollipop sure enough the rear camera starts working again. Not sure whats going on
What i have done so far:
Reflash the 4.4.4 images multiple times
Update to latest moto camera app
Delete the camera app update-clear data-clear cache
clear system cache
Still the rear camera is not detected.
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
A week passed and no response. Bump. Nobody has any idea how to get rid of this thing??
Koolstr said:
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
Click to expand...
Click to collapse
Is updating your custom rom to 5.1+ an option? Already many custom roms were updated to 5.1 even 5.1.1.
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Koolstr said:
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Click to expand...
Click to collapse
Don't even know what rom it is so its hard to answer. If you prefer a stable rom they yes, you should wait a little more.
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Click to expand...
Click to collapse
You should ask this one in your rom thread, sometime when the update is considered a major update, its recommend to do a full wipe, in some cases you are fine just updating without wiping. You could do a nandroid backup using your custom recovery (save it on your computer, not just on the phone) try to update without wiping. If its working fine, there is no problem, if not you can wipe your phone and restore your backup.
To disable the notification, I would try to go in settings --> apps --> all, search for the updater service, clear cache of that service and then disable it. Then find where the ota file is stored on your phone and delete it. Not sure if it will work, never tried myselef
Is there a way to do a nandroid backup directly to pc? Because I don't have room on my phone, and TWRP Manager only lets internal backups take place.
For some reason I can't search the apps in my ROM. The notification says it is from Google Play Services but I suspect that is simply routed requests from the actual updater service. Do you know what the name of the service is, so I can find it? I have a crazy number of apps and can't find it.
Hi Koolstr,
I know this thread is old, but wanted to let you know I am on an unlocked and rooted HTC One (m7) S-On. I am using TWRP and can backup to external storage using a Micro USB Powered Micro USB Host OTG cable, which I purchased from Amazon.
I am running:
Android version: 5.1
Rom: Google-Plus-Edition-LP_m7_v3.2_072915
Kernel: 3.4.10-NuK3rn3l-Lollipop_v8.00
I am getting a similar Android System Update: Android L upgrade for user/release-keys. I cannot get it to go away. I made a complete nandroid backup and then proceeded applying the update. It will reboot the phone into TWRP recovery and do nothing. The update goes away for a few days and then it comes back. I have tried to look for a way to disable the update, but I am at a stand still. If anyone knows that would be great.
Best,
manderson706
It's something that santod did. I believe there's a post in his topic with the fix. Or just flash the updated GPE from santod
As the title says the camera on my Z3 + does not work. Neither the back nor the front. I bought it today very economical, it is still submersible and the only problem that I indicated the previous owner was that the camera did not work since it updated to Nougat. I tried with Flashtool to upgrade to 7.1.1 and it did not do any good, the cameras do not work and the flash synonymous ideas?
Ju4n_ said:
As the title says the camera on my Z3 + does not work. Neither the back nor the front. I bought it today very economical, it is still submersible and the only problem that I indicated the previous owner was that the camera did not work since it updated to Nougat. I tried with Flashtool to upgrade to 7.1.1 and it did not do any good, the cameras do not work and the flash synonymous ideas?
Click to expand...
Click to collapse
As you mentioned it is having issues with Nougat, try flashing Marshmallow (Clean Flash). If you are flashing different version from the installed, it should be a clean flash, else so many issues will arise.
[email protected] said:
As you mentioned it is having issues with Nougat, try flashing Marshmallow (Clean Flash). If you are flashing different version from the installed, it should be a clean flash, else so many issues will arise.
Click to expand...
Click to collapse
I fix it changing the camera. Was hardware
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.