Here is the thing
i have had changed wallpaper inside Keyguard.apk
set the permission to RW-R-R
move to root/system/priv-app second time flashed thru recovery
reboot
i did wipe cache/dalvik second time not
after that there is an error and i cannot use System UI, unless flashing stock Keyguard.apk and it will go back
question is how to change wallpaper of UPSM without having an error "android.systemui has stopped"
using S5 Sensation ROM
itsdonjuan said:
Here is the thing
i have had changed wallpaper inside Keyguard.apk
set the permission to RW-R-R
move to root/system/priv-app second time flashed thru recovery
reboot
i did wipe cache/dalvik second time not
after that there is an error and i cannot use System UI, unless flashing stock Keyguard.apk and it will go back
question is how to change wallpaper of UPSM without having an error "android.systemui has stopped"
using S5 Sensation ROM
Click to expand...
Click to collapse
This should be in Q&A Section not Developement section
Related
Hello all
First of all sorry if this question has been asked. Usually I can find my answers myself by searching but can't this time. First of all I'm using d3rpICS_DRAMA_DM2. Last I was playing with the leedroid tweaks under the profiles settings. I switched it to sense 3.6. Now since I did that I keep getting a popup every 30 seconds or so saying system ui has stopped. I hit ok and it let's me continue what I was doing. I finally found the rom I liked and got my phone set up how I like so I'm wondering if there is a way to fix it or do I just have to flash again.
Sent from my PG86100 using xda app-developers app
My first guess would be that the SystemUI.apk has the wrong permissions.
Either use the "Fix Permissions" in LeeDroid tweaks or do it by going into recovery and use Fix Permissions from there.
Or, if you know how, you can do it manually for just the SystemUI.apk and go into the /system/apps/ folder with Root Explorer or equivalent and chance the permissions to rw-r--r--
Be sure to reboot (i personally do a cold boot each time i mess with system files, meaning i shut it off, remove battery and then put it back together and boot up) after each time you fix permissions.
If that doesn't work, try and open the ROM.zip file with WinZip or similar and manually copy the SystemUI.apk (and SystemUI.odex if the rom is odex) from the .zip to the /system/apps/ folder. This is incase the SystemUI file(s) were somehow damaged/corrupted when flashed (very very unlikely, but can happen).
- Moon
I did do the reboot with the battery out. I'm gonna try that other stuff you suggested. I'll get back to ya. Thanks for the help.
Sent from my PG86100 using xda app-developers app
The topic is old, but I have the same problem. It happened suddenly two days ago and randomly I get the message. I have to press "OK", then the status bar restarts after few seconds.
I have yoda ICS v8 S-off.
Here's a log-cat, if it can help
I know this is probably a dumb question but I've been googling all over and can't find what I'm looking for >.<.
I want to install Resurrection Remix JB v3.0.2 on my S2 and change the DPI to 160. On previous versions of that room I would do that then simply copy a phone.apk file that I got from one of RR's FAQ and that would be it but that doesn't seem to work on the new JellyBean version.
I replace the phone.apk file with the one I used to use for 160DPI copying it into /system/app then check to make sure the permissions are the same and reboot the phone. As soon as it boots back up I get a FC for android.phone and the message keeps popping back up over and over again. Tried doing a fix permission on the recovery and it's the same result.
Any idea of what I'm doing wrong or what I can use to fix it?.
Thanks.
SOLVED! After a very hard(and also boring) process of clicking in ok button and doing one action per time, I finally got put the original copy of my SystemUI into '/system/app' folder
I was playing of "Let's mod this SystemUI to learn about it", but then i repaired that I had no idea of how replace the original SystemUI by mine... Then I had the stupid idea of convert the original systemui into a user app using ROM Toolbox...
Results: i lost my systemUI, everything opens fine, but status bar is gone and the worst, a error screen informing the "com.android.systemui has stopped" every 5 seconds, which forces me do one action before error screen appears
My question is, there's anyway to install my SystemUI or recover the old one(i have bkp of the apk) without factory reset?
Click to expand...
Click to collapse
Delete old systemui apk replaced with one that works then fix permission to rw-r-r and reboot. Or dirty flash no wipes. All else fails do a full wipe and reflash.
andrewwright said:
Delete old systemui apk replaced with one that works then fix permission to rw-r-r and reboot. Or dirty flash no wipes. All else fails do a full wipe and reflash.
Click to expand...
Click to collapse
The main problem was solved, I learned how to "install" SystemUI.apk, now I'm in trouble with my custom SystemUI.apk that crashs too. I just can't compile a single SystemUI that don't crash :/
However at least i can use my phone normally
Here is the thing
i have had changed wallpaper inside Keyguard.apk
set the permission to RW-R-R
move to root/system/priv-app second time flashed thru recovery
reboot
i did wipe cache/dalvik second time not
after that there is an error and i cannot use System UI, unless flashing stock Keyguard.apk and it will go back
question is how to change wallpaper of UPSM without having an error "android.systemui has stopped"
using S5 Sensation ROM
Solution for "Unfortunately, System UI has stopped" after instaling custom theme
After installing custom theme on CM13 got totaly blocked phone. This solution help me : go in TWRP advanced/ file manager/data/app. Now you need recognise folder with last instaled theme and delete all files inside . Reboot phone and should be all ok.
I use CM13 (20160120 now) and I can install themes without getting any error.
The "Liv" theme made my phone unbootable when i set its botanimation (the animation started, then screen turned off). I was able to boot it up by wiping dalvik cache (what?).
Now I set the theme without the bootanimation and works very well.
Switched off theme service, all work as usual
Tes