Related
Here's the thing:
- I love Greenify and I really update mine regularly...so I tried to update whilst on Android ART
- I have the xposed framework at my disposal with my stock (rooted) Nexus 7 2013 4.4
- I updated and then I installed/update the thing in the first menu of the xposed framework and then from there I pressed "soft reboot"
Now it doesn't want to proceed to my launcher or anything. It's a soft-brick.
Any help/tip is appreciated.
Can you get into Safe Mode? If so you can try and remove the app, etc.
Can't post the link so:
Reboot to safe mode
If you’re experiencing issues - such as apps crashing, reboots, or fast battery drain - on your device, they could be caused by a third-party app. To check if this is the case, you can start up your device in safe mode, which temporarily disables third-party apps that you’ve installed.
Ensure your device's screen is on, then press & hold the Power button.
Touch & hold the Power off option in the dialog box.
Touch OK in the following dialog to start safe mode.
Try using your device in safe mode to see if the problem persists. If it doesn't, restart your device to get it out of safe mode and uninstall recently installed apps to see if you can pinpoint the one that’s causing the problem.
Xposed doesn't support KitKat yet. Sure you might be able to install the framework but modules have no effect. The developer is waiting for his N5 to arrive before working on a fix so sit tight and keep an eye on this thread for updates: http://forum.xda-developers.com/showthread.php?t=1574401
AlderCass said:
Xposed doesn't support KitKat yet. Sure you might be able to install the framework but modules have no effect. The developer is waiting for his N5 to arrive before working on a fix so sit tight and keep an eye on this thread for updates: http://forum.xda-developers.com/showthread.php?t=1574401
Click to expand...
Click to collapse
Even installing the framework makes my n7 hang on boot.
lastdeadmouse said:
Even installing the framework makes my n7 hang on boot.
Click to expand...
Click to collapse
I haven't tried it on the N7 but on the N4 it installed but no modules worked. But the solution for now is just don't use Xposed until a 4.4 version becomes available.
AlderCass said:
I haven't tried it on the N7 but on the N4 it installed but no modules worked. But the solution for now is just don't use Xposed until a 4.4 version becomes available.
Click to expand...
Click to collapse
Well according to the play store page of Greenify, the reason why i wanted to update is because they released a supposed to be new xposed patch for 4.4 android art users which is what i used. Had to dirty flash the rom to get this running again ugh. :/
Sent from my Nexus 7 using Tapatalk
Use the old version of Greenify...that's what I'm doing.
I also had to flash the ROM again.....lost my progress of lots of games.........:-/
Hi there,
I got a refurbished otter at the beginning of the week. I followed the guides here to install FFF, TWRP and CM11 on it.
First, a big thanks to everyone involved.
I'm getting what look like UI crashes, which I've been able to reproduce with Firefox but it seems they are not limited to it.
To reproduce:
flash FFF, TWRP and CM11 M6
install FF from the Play Store
configure Firefox sync
browse to any page
I should note that I configured my Google account at boot, and that I use a Hebrew locale.
On my device, I get a blank screen, followed by a return to the launcher or previously opened app, followed by more crashes until the CM boot animation shows on top of the launcher. When it completes, a dialogue appears noting the system UI has stopped working. It returns after confirming the message.
Should I report this to Mozilla and/or CM? I'd like to collect more information, where can I find any relevant logs? If so, is it possible to increase the logs' verbosity?
Thanks in advance.
Idontwantausername said:
Hi there,
I got a refurbished otter at the beginning of the week. I followed the guides here to install FFF, TWRP and CM11 on it.
First, a big thanks to everyone involved.
I'm getting what look like UI crashes, which I've been able to reproduce with Firefox but it seems they are not limited to it.
To reproduce:
flash FFF, TWRP and CM11 M6
install FF from the Play Store
configure Firefox sync
browse to any page
I should note that I configured my Google account at boot, and that I use a Hebrew locale.
On my device, I get a blank screen, followed by a return to the launcher or previously opened app, followed by more crashes until the CM boot animation shows on top of the launched. When it completes, a dialogue appears noting the system UI has stopped working. It returns after confirming the message.
Should I report this to Mozilla and/or CM? I'd like to collect more information, where can I find any relevant logs? If so, is it possible to increase the logs' verbosity?
Thanks in advance.
Click to expand...
Click to collapse
I'm getting those same notification/notification bar/UI crashes on Nook HD+ using CM11 (nightlies and M6). I don't use firefox, so that is not your problem
I was actually getting them more in the previous nightly builds. CM11 M6 seems to have helped a little.
Mine happen seemingly randomly when I get notifications for a new email or hangout and I try to swipe down the notification bar to see what they are.
I've tried wiping the davlik, the entire cache, and even doing a factory reset. Nothing seems to work.
Anyone else have some advice?
_Boondock_ said:
I'm getting those same notification/notification bar/UI crashes on Nook HD+ using CM11 (nightlies and M6). I don't use firefox, so that is not your problem
I was actually getting them more in the previous nightly builds. CM11 M6 seems to have helped a little.
Mine happen seemingly randomly when I get notifications for a new email or hangout and I try to swipe down the notification bar to see what they are.
I've tried wiping the davlik, the entire cache, and even doing a factory reset. Nothing seems to work.
Anyone else have some advice?
Click to expand...
Click to collapse
I have the exact same issue for about 2 months i believe.
This happens usually when pulling the notification panel down. It think it happens when you chain a lot of actions one after other. Like unlocking phone and pulling down the notification than tapping another thing etc...etc...
Hope this will be fixed soon, it usually disturbs the usage a lot. I was hoping M6 would solve that.
Back to m5 guys, my Galaxy Nexus has the same problem here, so I revert back to m5 and everything works fine, except the stock browser has startup crash sometime
Does anyone know if the devs are aware of this issue?
I just reproduced this on today's OtterX CM build.
I'm having the same problem. Had been running one of the earlier nightlies without any notification bar problems at all. Updated to the M6 release and now this problem occurs every few minutes. System is now totally unstable with M6. Firefox crashes more frequently now too.
CYAN-4047, if anyone's interested.
Idontwantausername said:
CYAN-4047, if anyone's interested.
Click to expand...
Click to collapse
ARG! Sure wish I had seen this before spending the whole day restoring my Kindle to the older nightly after having to wipe it.
Idontwantausername said:
Hi there,
I got a refurbished otter at the beginning of the week. I followed the guides here to install FFF, TWRP and CM11 on it.
First, a big thanks to everyone involved.
I'm getting what look like UI crashes, which I've been able to reproduce with Firefox but it seems they are not limited to it.
To reproduce:
flash FFF, TWRP and CM11 M6
install FF from the Play Store
configure Firefox sync
browse to any page
I should note that I configured my Google account at boot, and that I use a Hebrew locale.
On my device, I get a blank screen, followed by a return to the launcher or previously opened app, followed by more crashes until the CM boot animation shows on top of the launcher. When it completes, a dialogue appears noting the system UI has stopped working. It returns after confirming the message.
Should I report this to Mozilla and/or CM? I'd like to collect more information, where can I find any relevant logs? If so, is it possible to increase the logs' verbosity?
Thanks in advance.
Click to expand...
Click to collapse
I followed your steps exactly and I am not able to get this problem to occur. Are there any other steps you you may have omitted? Any other apps you installed or any other actions you performed in addition to what you listed here? Also, are you sure it's "any page"? Is there a specific site you were trying to go to when this happened? I'm trying to work on a fix for this issue and was hoping I could reproduce the problem based on your information but my device is still functioning fine. The more information you can provide the better and ideally I'd like something that can be reproduced consistently.
0xD34D said:
I followed your steps exactly and I am not able to get this problem to occur. Are there any other steps you you may have omitted? Any other apps you installed or any other actions you performed in addition to what you listed here? Also, are you sure it's "any page"? Is there a specific site you were trying to go to when this happened? I'm trying to work on a fix for this issue and was hoping I could reproduce the problem based on your information but my device is still functioning fine. The more information you can provide the better and ideally I'd like something that can be reproduced consistently.
Click to expand...
Click to collapse
Since I have now reflashed back to my older nightly I can't give you exact steps but here is what I experienced. I also got a stock KF a while ago and since I didn't want the stock release, followed the instructions to reflash it. At that point I did the full device wipe and flashed the 20140407 nightly build. No problems at all, the system ran beautifully. This week, I got the notification that M6 was available for installation so I went to Settings->About tablet->CM Updates->Available Updates and clicked the download. It downloaded and installed without any problem. Rebooted and problems began immediately. Firefox was immediately unstable and began crashing frequently. The "UI" would hang and go black then crash and come back up in lock screen. Pulling the notification bar open would hang and then the system would crash. Things really became completely unuseable.
So today I tried rolling back to the previous nightly that had worked well. This time, I didn't wipe the device, just reinstalled the nightly and wiped the cache after installation. See my previous thread about how that turned out. The status bar was totally hosed, the quick settings panel didn't work, the home button didn't work, the extended power menu was gone. Just a complete mess. So... I wiped the device and reinstalled the nightly and brought everything back to life again.
Now I don't know if the issues were caused by a flakey M6 release, or the installation process which left some droppings behind as I didn't try installing the M6 release after a full wipe. But I do know that after a full wipe the 20140407 nightly is working without a problem. I can't say for sure but my expectation is that it had something to do with the installation process not doing a clean install rather than a bad M6 release.
I made a test build which reverts a change I suspect may be the culprit. If anyone cares to try it out, here is the link. Please do not go around sharing this will a lot of people since it is currently hosted on Dropbox and they will throttle it if too much traffic is received.
https://dl.dropboxusercontent.com/u/2151597/cm-11-20140511-UNOFFICIAL-otter.zip
md5sum: f9747d68e833bae9db12f548116f9551
Dropbox is still syncing so if you get an error 404 just try again in a couple minutes.
0xD34D said:
I followed your steps exactly and I am not able to get this problem to occur. Are there any other steps you you may have omitted? Any other apps you installed or any other actions you performed in addition to what you listed here? Also, are you sure it's "any page"? Is there a specific site you were trying to go to when this happened? I'm trying to work on a fix for this issue and was hoping I could reproduce the problem based on your information but my device is still functioning fine. The more information you can provide the better and ideally I'd like something that can be reproduced consistently.
Click to expand...
Click to collapse
I saw in the bug report you've already found a way to reproduce, but just in case, as I wrote there I've found it reproduces by installing Adblock Plus - I close the app completely in the app drawer to make sure FF restarts with the add-on installed. After it restarts it should show a quick configuration page where you can enable blocking of secondary things like tracking and malware. In the first paragraph is a link to another settings page. In this other page all I have to do is zoom in or scroll around and most of the time I'll get a crash within a minute.
0xD34D said:
I made a test build which reverts a change I suspect may be the culprit. If anyone cares to try it out, here is the link. Please do not go around sharing this will a lot of people since it is currently hosted on Dropbox and they will throttle it if too much traffic is received.
https://dl.dropboxusercontent.com/u/2151597/cm-11-20140511-UNOFFICIAL-otter.zip
md5sum: f9747d68e833bae9db12f548116f9551
Dropbox is still syncing so if you get an error 404 just try again in a couple minutes.
Click to expand...
Click to collapse
Downloaded, will be tested later today (in about 12 hours).
Edit: been testing this for about an hour now. The system seems very stable, even more than M5.
M6
I have this snapshot M6 build a week ago..I didn't notice any problem ...like firefox crashing.
I do a full wipe(clean) install...Data,system, cache, dalvik cache
0xD34D said:
Please do not go around sharing this will a lot of people since it is currently hosted on Dropbox and they will throttle it if too much traffic is received.
Click to expand...
Click to collapse
I hope you don't mind I took the liberty of submitting this to a public bt tracker:
URL deleted
Idontwantausername said:
I hope you don't mind I took the liberty of submitting this to a public bt tracker:
http://burnbit.com/torrent/289563/cm_11_20140511_UNOFFICIAL_otter_zip
Click to expand...
Click to collapse
Actually I'd prefer you not do that.
0xD34D said:
Actually I'd prefer you not do that.
Click to expand...
Click to collapse
It looks like there has been a fix for this problem. Has the fix been incorporated into one of the nightly builds or is it still only available as a patch?
mpuckett54 said:
It looks like there has been a fix for this problem. Has the fix been incorporated into one of the nightly builds or is it still only available as a patch?
Click to expand...
Click to collapse
Does anyone know if this has been fixed in one of the nightly builds? Has anyone tried any of the post M6 nightly builds yet?
cm-11-20140602-NIGHTLY- i9300
mpuckett54 said:
Does anyone know if this has been fixed in one of the nightly builds? Has anyone tried any of the post M6 nightly builds yet?
Click to expand...
Click to collapse
Had the same issue with M6 but now I thing they have fixed the issue, not sure which nightly build but build dated 20140602 fixed the issue for me.
I did a clean install.
Followed following steps.
1. Boot into recovery(CWM).
2. Factory Reset.
3. Cleared Dalvik cache.
4. Installed zip and run "defy_fullwipe_ext3.zip"
5. Installed "cm-11-20140602-NIGHTLY- i9300"
6. Installed Gapps for kitkat.
7. Reboot.
I have not faced the same UI crash issue so far will update if I face in future .
For "defy_fullwipe_ext3.zip" refer following link(I used the first one):
http://forum.xda-developers.com/showthread.php?t=1818520
I have tried several AOSP roms and have not gotten Netflix to work on any of them. I have tried liquidsmooth and PacRom but I keep getting Error (-9). Does anyone know of a fix for this? Please help..Thanks.
jmayer846 said:
I have tried several AOSP roms and have not gotten Netflix to work on any of them. I have tried liquidsmooth and PacRom but I keep getting Error (-9). Does anyone know of a fix for this? Please help..Thanks.
Click to expand...
Click to collapse
Using SELinuxModeChanger app, you can set to permissive and give it a go, it sometimes work.
Another method is to delete a lib file within
/system/vendor/lib
Liboemcrypto.so, you can rename or simply delete, then reboot the device.
Spark91 said:
Using SELinuxModeChanger app, you can set to permissive and give it a go, it sometimes work.
Another method is to delete a lib file within
/system/vendor/lib
Liboemcrypto.so, you can rename or simply delete, then reboot the device.
Click to expand...
Click to collapse
I personally didn't have luck with the permissive change and couldn't find the liboemcrypto.so file you spoke of. Is that specific to the Galaxy Note 4?
No sir, most ROMs don't have the lib, and what ROM are you using ?
Using liquid smooth on a moto xt926. I've noticed this problem on various cm12 ROMs I've tried. They had Netflix running for a while then it kind of stopped for recently then I think the last one I tried that I worked on was bliss pop 3.2. Jump over to liquid smooth because. Was pretty laggy and causing me a little pain. Back to a loading screen. Never comes up. I will say I thought it was a host file or ad block problem because I could get it going on WiFi. Just not on cellular data.
Think pulling and using the apk from a nexus device would change anything?
Beats me, I think that it probably is not an issue with the apk itself.
My best guess is that it is ROM related. Didn't cm ROMs have some DRM related issues a year or so ago? Wouldn't surprise me if it's something along those lines.
BTW, forgot to mention that you can't even get to netflix.com and browser. just more thoughts as to why I don't think it's actual program related it something in the ROM.
It is ROM/Kernel related for the Note 4 before I think @Mod57 fixed it but all it was is to change a build.prop line. Try and see if this works for you as well.
persist.hwc.mdpcomp.enable=false
If the value is already there and it says True, change it to false.
Did this on a previous build (cm12 5-8-2015 I believe), seems to work although more testing is needed to determine consistency. Failed first time worked second.
Sure hope that's it....!
Has anyone had better luck finding a solution for this? I came from DU's latest and now on CM12.1 6/25 nightly, everything is working great except for Netflix. I was never able to get it to work in DU so I won't be terribly heartbroken if I can't get it fixed, but I do not have Lyboemcrypto.so file or that specific persist line in my build.prop. Any other suggestions? I was getting a -504 error when attempting to install a couple apps, turning flight mode on/off took care of that, so I tried that as well as wifi on and off both for Netflix but cannot get it to initialize, all I get is the constant red spinning circle of the first screen. Thanks
Workaround
Install the module xposed cm10.1 Netflix workaround under xposed framework. Works perfectly on t0lte.
Edit: working on cm12.1
Netflix fix
Deleted
I just bumped my lollipop rom and install xposed then I noticed that my phone shows out "android is upgrading" on every reboot. Is there any way to fix this as it is a little annoying...:crying:
Sorry for my broken English
+1 !
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' is better than, well you know.
kp_q said:
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' and better than, well you know.
Click to expand...
Click to collapse
This activity tends to get lengthier after every reboot. I've found that once it "seems" to loop in the "Android is upgrading" screen, to remove the battery, boot into recovery, wipe the Dalvik cache, and reboot. It will go through the lengthy procedure of updating software, but will boot a WHOLE lot faster after that.
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
alqoshi4life said:
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
Click to expand...
Click to collapse
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
abbey666 said:
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
Click to expand...
Click to collapse
Which Xposed version did you use? I'm on v68 right now which is the latest. I had v67 and it did the same thing.
V66. I tried2 later versions but this one worked for me.
I have a Oneplus One but I have the same issue. Every damn boot. Android is starting. optimizing app 1 of 121.
I also have the latest version of xposed.
I know not the forum for the OPO but just thought I'd let you guys know other phones face it too and hopefully find a solution to this.
I had to make a really important call and my phone restarted all on its own. That's bad enough but add to the random restart sitting for 5 minutes to wait for android to finish optimizing
abbey666 said:
V66. I tried2 later versions but this one worked for me.
Click to expand...
Click to collapse
I tried v66 like you recommended and the same thing happened. So it must be something else that solved your problem. I guess I can live with it though.
have the same problem with my g3.. everybody have data backup ? )
BlackGodRaven said:
have the same problem with my g3.. everybody have data backup ? )
Click to expand...
Click to collapse
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
alqoshi4life said:
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
Click to expand...
Click to collapse
l solved it too ) l transfer backup to sd card )
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
Trying this now...my G3 crashes for whatever reason from time to time after my Tasker that disables bluetooth as soon as the USB power is disconnected from the car.
Currently on version 79. Patched it with Lucky Pater and removed all odex; rebooted (got stuck but battery out & booted normally).
I'll report if there are any further issues
Okay it's very odd it seems like there's an issue with my LG G3 disconnecting bluetooth from the stock head unit in '13 WRX. If I try pushing the power button off on the radio then shut off the engine (Tasker shuts down bluetooth) then I don't seem to have this issue with the phone crashing. I've yet to have the phone crash if it's on A/C power and Tasker performs the same function.
Developer Preview is up if anybody wants to try it
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Holy Moly.
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
DoobyDroid said:
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
Click to expand...
Click to collapse
Seems like for now, most UI and user facing changes in general are hidden behind flags, this one is meant for the devs, so it's to be expected. The beta, on the other end, will be aimed at users, and then we will see what changes
I upgraded last night. Had to reboot twice after restart. Then everything was stable. First time it rebooted after install, nothing seemed to want to work and kept FCing. Second reboot, everything is fine now. Sometimes, Nova needs to be indicated when I press the home button that it's default, otherwise, everything is working fine.
Is it me or does the Android version still say 11 but the build is "S"?
I downloaded the 12 DP1... and it just isn't ready yet (understandably so) for the daily driver use I need.f
Rooting it requires disable verity and verification. You'll need magisk 23 or canary to patch boot.img as well. Not disabling verity/verification, it will only boot back into fastboot and list the reason as something like, "unable to load boot image".
Once rooted, I moved on to installing edxposed --- using riru, riru edxposed, and edxposed manager. Everything installs without problems. Final reboot, and reboots as normal. But then about 90 seconds later, you'll start getting FC after FC after FC. All apps too, and background apps, and systemui, etc.
Removing the riru components and edxposed manager, doesn't correct this problem.
Did fresh format and reinstall of the DP1... rooted again... and then tried Viper4Android. I use a very simple version. You just flash it, and its done (no manual driver install either). Rather than the 3 reboot, AML, driver install, etc.
V4A installs with good logs. Reboots without a hitch. But I noticed the v4a icon in the status bar is missing. I open it up manually, and start getting freezes and fc's. Within 5 minutes, I get kernel panic reboots -- and non-bootloop freezes on the working G screen.
Reboot manually with long press power, get it loaded back up and immediately remove V4A. Reboot and now I'm back to stock.
Get FC's every hour or two. Random reboots too. Battery life is struggling.
I decided to wait until a better version drops, perhaps the beta or at least a DP2.5 or 3.0. As of right now, having Android S is mostly just a status thing -- to show people how cool we are to have access to it as such an early stage. But unless you are dedicated to helping improve the ROM through daily use and reporting... I highly recommend that you stick with Android R.
Just flashed the 1st public android 12 beta bramble-ota-spb1.210331.013-3c294b13.zip with adb sideload. Listed as android S atm, surprised 5G was enabled as this wasn`t the case with android 11 in the Netherlands. All apps working fine so far and still finding out the new stuff.
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
ekowwillis said:
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
Click to expand...
Click to collapse
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
galza said:
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
Click to expand...
Click to collapse
Clean wipe and follow the OP instructions in this Pixel 5 thread. Make sure you use the images for 4a5g where needed
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com