Related
Hi I have a Sony Xperia Z and it was rooted before I updated the software to 4.2.2 version. I wanted to root the 4.2.2 version too because i wanted to use light flow and make sure the leds all work properly with stamina mode. So I root my phone and copy super stamina.apk into the app folder and then when i next restart my phone, i keep getting the message, android updating apps. it then goes onto the home screen for about 5 seconds and reboots and does the same thing again, android updating apps, home screen for 5 seconds and reboot. any ideas whats going?
wasifraza said:
Hi I have a Sony Xperia Z and it was rooted before I updated the software to 4.2.2 version. I wanted to root the 4.2.2 version too because i wanted to use light flow and make sure the leds all work properly with stamina mode. So I root my phone and copy super stamina.apk into the app folder and then when i next restart my phone, i keep getting the message, android updating apps. it then goes onto the home screen for about 5 seconds and reboots and does the same thing again, android updating apps, home screen for 5 seconds and reboot. any ideas whats going?
Click to expand...
Click to collapse
Probably the wrong version of super stamina for your firmware, what Rom are you using? I would recommend removing super stamina, not sure why you need it, 4.2.2 is pretty good with battery life without stamina and obviously really good with the stock stamina mode
I have a MotoX on KK 4.4 rooted.
Recently (since it started bugging about the 4.4.2 OTA update) I notice that occasionally and seemingly randomly, the device with make the animation for switching apps. The active app (even the home screen) fill fade out, then back in again. it almost appears as if the App is switching to something else that is NOT displayed, then back again.
Apps react to this as if the app was suspended and reactivated (Games pause, emails and websites refresh, etc).
I thought it may be something I added from rooting, i.e. Xposed, but I uninstalled all root apps and the behavior persists.
Any advice?
I never had that, I have an rooted and bootloader unlocked Moto X, Gravity Box and other frameworks enabled, I thing the best you could do is to reset your phone, and maybe re-do de update.
Bumping thread.
Update: I tried resetting my phone back, and it went away, but as soon as it started trying to push the 4.4.2 update (which fails to install anyway) the problem returned.
Is anyone else experiencing this issue?
jaredtritsch said:
Bumping thread.
Update: I tried resetting my phone back, and it went away, but as soon as it started trying to push the 4.4.2 update (which fails to install anyway) the problem returned.
Is anyone else experiencing this issue?
Click to expand...
Click to collapse
Sometimes when there is modified system files, the OTA update will fail. And to restore this files, maybe the best option is returning to your Stock Android (the same version you are using at the moment), guide here, works flawlessly: (http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515)
And then trying to do the OTA update, remember that soon we'll get 4.4.3, so maybe this bug could be fixed.
Hi everyone, OK I've tried everything in other threads, here's the situation:
Note 4 Sprint
cf-auto-root worked fine, everything working well for a week (stock recovery, stock ROM, just root). Then installed xposed (accidentally used the experimental 2.7 version) and RootCloak module. This threw me into a boot loop.
I recovered from it by redoing cf-auto-root/odin. That got me out of the loop, but-
Ever since then:
- Phone lags for a few seconds every few seconds - making it hard to even type in a phone number, let alone watch a video,
- Fingerprint doesn't work - when launching the menu from settings I get an error that it's unavailable.
I've tried everything in the other threads:
- build.prop change (disabling securestorage)
- successfully installed 2.6 xposed and tried:
- wanam xposed to disable securestorage
- and the xsecurestorage module
- flashed stock rom from sammobile with odin
- even tried disabling selinux with wanam
No matter what, these same issues. I haven't tried anything other than the stock rom. Any ideas at all? Is there a different ROM out there I should try? Does that even have a chance of working?
I'm not sure I understand why flashing stock didn't fix it - even though it caused me to lose root...
Right now I have TWRP with root and stock ROM.
Any ideas or suggestions really appreciated.. I'm out of ideas. Thanks
I have the Same Problem
I had the same problem, haven't bothered installing it again since, don't suppose anyone has heard from the developers?
Hope maybe the devs can shed some light here. Is there anything else I can do? Flashing stock didn't even help. What's left?
So after not touching anything for about a week - things started running smoothly. Very odd - didn't change anything. Xposed was uninstalled for that time.
But, after SuperSU updated (and updated the binary/rebooted), the lag came back. So, this is telling me this may be related to root/SuperSU instead.
Q&A for [ROM][Lollipop][Z3C] Cyanogenmod 12 - Nightly
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][Lollipop][Z3C] Cyanogenmod 12 - Nightly. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ciao Guys,
actually I have rEctiFy ROM with clockworkmod recovery..do I have to flash anyway the cyanogen boot.img ?
mauroalpha said:
Ciao Guys,
actually I have rEctiFy ROM with clockworkmod recovery..do I have to flash anyway the cyanogen boot.img ?
Click to expand...
Click to collapse
I think you do. I tried it once in cwm and it failed, it could also have been a different issue but it works fine with the boot.img of the zip. Just keep in mind to store the zip on the internal storage before you flash the kernel and after wiping it.and that the recovery menu is very dim, you should avoid bright conditions.
Video or pictures
I would like to see how the cyanogenmod works on the Z3 Compact. Could you send me a video or some pictures?
Thanks!
Lukas
I have still some problems with my bluetooth headset. The connection and the controlls works, but often i dont get sound.
supermanlovers said:
I have still some problems with my bluetooth headset. The connection and the controlls works, but often i dont get sound.
Click to expand...
Click to collapse
My Bluetooth headset was acting up when i had the built in equalizer (AudioFx) turned on , try to turn it off and see if it helps.
I also installed viper4android instead which is way better.
Thanks, this worked for me
2mal16 said:
I think you do. I tried it once in cwm and it failed, it could also have been a different issue but it works fine with the boot.img of the zip. Just keep in mind to store the zip on the internal storage before you flash the kernel and after wiping it.and that the recovery menu is very dim, you should avoid bright conditions.
Click to expand...
Click to collapse
I've just installed with cyano recovery, everything was fine..
I want to report that somethimes the mic recorder loss some seconds while i'm using it..i've just updated now the nightly
need to test it again
anyway i'm really happy, the phone for me is now really faster than the stock rom.
Camera button
Anyone figure out how to remap the camera button yet?
So i'm kind of a noob here I guess but I thought to install this one would need to have their device rooted (like I had) and I have it on my device working perfectly, the only problem is the phone is telling me that it is not rooted and thus not letting me use titanium backup and greenify etc.
Is it just me, or is the Auto Updater not rebooting to recovery after downloading the cm-12-20150214-NIGHTLY-z3c -
I did extract and ABD'flashed the boot.img
And theres still an issue with the LED brightness and audio engine wakeup ( Sound seems dim at first, and sometimes notification audio is skipped, almost like it is in hibernation and cant always get out of it ) , cant seem to find it in the fixlog or changelog either
I just got cm12 setup on my galaxy tab 8.4, the only issue i notice thus far is that im finding it impossible to set a different wallpaper on my lockscreen from my gallery pics... If i want to use one of my personal backgrounds i have to use the same as my homescreen. The only way to change just the lockscreen background is to pick one from a theme i downloaded but that option sucks because i never use theme backgrounds... Anyone have a workaround or is that something well have to wait on in another nightly? I was able to do this easily in cm11, just had to go to lockscreen in settings and themes and i could pick it there
kiliimanjaro said:
So i'm kind of a noob here I guess but I thought to install this one would need to have their device rooted (like I had) and I have it on my device working perfectly, the only problem is the phone is telling me that it is not rooted and thus not letting me use titanium backup and greenify etc.
Click to expand...
Click to collapse
Go to Settings, Developer Options, then a few settings from the top you will see "Root access", click it and choose "Apps and ADB" or just "Apps only" (if you don't use ADB).
After root access is enabled you can install SuperSU from the Play Store (or just use the CM root access if you don't want SuperSU).....
Thanks that worked perfectly!
Another problem though (or else me just being silly and overlooking something simple) that when I boot to recovery it brings up the Cyanogenmod Recovery and there is no option to Backup my files. The only options I have are to wipe everything or reboot.
kiliimanjaro said:
Thanks that worked perfectly!
Another problem though (or else me just being silly and overlooking something simple) that when I boot to recovery it brings up the Cyanogenmod Recovery and there is no option to Backup my files. The only options I have are to wipe everything or reboot.
Click to expand...
Click to collapse
When you flash boot.img from the nightly .zip file you get the CM Recovery. You are correct in that there is no backup option. Use Titanium or some other app to back up your stuff. You can also use a different recovery but you may run into a different problem where the phone identifies itself as "aries" and won't flash the ROM. The CM Recovery takes care of that problem.
Anyone found a fix to the dim notification led issue? I think its related to the CM recovery. Anyone that can confirm this issue aswell?
I have a tab pro 8.4 running cm12 latest nightlies and i cant get adblock plus to work on it. Ive tried everything. It ran beautifully on cm 11 but on cm12 it FCs either right after u launch it or sometimes i can almost get done downloading the site block list. I have the wifi only version of the sm-t320 if that helps. Any ideas anyone? Either a way to fix it or an alternative app?
jflow36 said:
I have a tab pro 8.4 running cm12 latest nightlies and i cant get adblock plus to work on it. Ive tried everything. It ran beautifully on cm 11 but on cm12 it FCs either right after u launch it or sometimes i can almost get done downloading the site block list. I have the wifi only version of the sm-t320 if that helps. Any ideas anyone? Either a way to fix it or an alternative app?
Click to expand...
Click to collapse
try adaway (the newest dev build version) from this thread: http://forum.xda-developers.com/showthread.php?t=2190753
I think it worked for me when i was running cm 12.
firsty said:
Anyone found a fix to the dim notification led issue? I think its related to the CM recovery. Anyone that can confirm this issue aswell?
Click to expand...
Click to collapse
+1. Loving it but the notification LED is basically invisible compared to the stock ROM. Anyone know of a fix for this?
A couple of issues I've run into is sometimes bluetooth audio gets sped-up so my music sounds like it is playing a 2x speed (Google play music) and I'm unable to activate any accessibility services (I can get into the cancel or ok screen but can't click ok). Anybody else have these or know a workaround?
When I try launching the stock camera app on my rooted Pixel 5, the launch-screen is shown briefly (black background with camera icon) before the app crashes. Same thing with the stock recorder, but here, not even the launcher screen appears, there's just nothing happening. No error messages are displayed whatsoever.
I rooted my phone by patching the boot.img using magisk, and when flashing the stock boot.img in fastboot, both apps are working just fine. It's not the camera itself that is causing the issue, every other app taking advantage of the camera apart from the stock camera app is working as usual, I can take photos in Snapchat without problems for example. Does anyone know a fix for this or is there anything I can do to debug the apps? My research on this issue didn't lead to any results.
I installed the latest firmware version for my model from the official google site yesterday (RQ3A.210705.001), but the issues were already present before (on version RQ1A.210105.003). I installed it using the
Bash:
install-all.sh
script, removing the
Bash:
-w
flag from the last command to keep all my data, in case this is relevant.
Thanks in advance.
Update July 13:
Uninstalling the EdXposed Magisk Module and Gravitybox solved the issue.
Update July 13 #2:
Turns out I'm a moron, just blacklisting the two apps in the EdXposed Manager would've been sufficient. Welp, next time I'll research a bit harder.
littlegamer757 said:
When I try launching the stock camera app on my rooted Pixel 5, the launch-screen is shown briefly (black background with camera icon) before the app crashes. Same thing with the stock recorder, but here, not even the launcher screen appears, there's just nothing happening. No error messages are displayed whatsoever.
I rooted my phone by patching the boot.img using magisk, and when flashing the stock boot.img in fastboot, both apps are working just fine. It's not the camera itself that is causing the issue, every other app taking advantage of the camera apart from the stock camera app is working as usual, I can take photos in Snapchat without problems for example. Does anyone know a fix for this or is there anything I can do to debug the apps? My research on this issue didn't lead to any results.
I installed the latest firmware version for my model from the official google site yesterday (RQ3A.210705.001), but the issues were already present before (on version RQ1A.210105.003). I installed it using the
Bash:
install-all.sh
script, removing the
Bash:
-w
flag from the last command to keep all my data, in case this is relevant.
Thanks in advance.
Click to expand...
Click to collapse
are you using edxposed?
jons99 said:
are you using edxposed?
Click to expand...
Click to collapse
Yes I was and it was the problem's root, uninstalling Edxposed and Gravitybox solved the issue. Would've liked to keep Gravitybox but I'd rather have a working camera. I didn't have time to update my post yet. Thanks for your reply though!
littlegamer757 said:
Yes I was and it was the problem's root, uninstalling Edxposed and Gravitybox solved the issue. Would've liked to keep Gravitybox but I'd rather have a working camera. I didn't have time to update my post yet. Thanks for your reply though!
Click to expand...
Click to collapse
you can still use edxposed you just need to black list the camera app or better yet use white list or even better yet use lsposed good luck