Has anyone had any success installing gravity box on the latest stock 4.42 rom? After I installed it and rebooted, my screen showed up blank. It will light up, but there is no display. Something is going on with the operating system because when I hold down both buttons I hear a camera click sound like a screen shot or photograph has been taken. I cannot get adb to connect. I'm currently waiting for the battery to drain, so I can boot back into recovery and restore a backup.
I think I will avoid trying this again unless someone else confirms it to be working well with their watch.
In case anyone is wondering, I did use the 4.4 version of the apk.
Thanks
LaDamian said:
Has anyone had any success installing gravity box on the latest stock 4.42 rom?
Click to expand...
Click to collapse
Did you deactivate ART first?
I did not change between dalvik and art. I think the default setting would be dalvik, so it is probably set on that.
Edit: I got my backup restored, and the runtime was definitely set to dalvik.
Related
I had Viper 1.0.1 working. It wasn't broke but I tried to put Viper 1.1.0 on the phone. I keep getting the message "Unfortunately system UI has stopped " I have no status bar and no pull down for notifications.
I have dirty flashed, clean flashed, tried different kernels, fixed permissions, different download.
Any ideas?????
I have restored the previous version for the time being.
TIA
Dave
I had the same problem, and couldn't fix it until I updated to the latest version of CWM recovery. Even if you think that you have the latest version, find the thread for it and re-flash it anyway. Then, do a FULL wipe, install Viper, then install the suggested kernel and see if it works, only after that, then try other kernels if you want to.
RLGL said:
I had Viper 1.0.1 working. It wasn't broke but I tried to put Viper 1.1.0 on the phone. I keep getting the message "Unfortunately system UI has stopped " I have no status bar and no pull down for notifications.
I have dirty flashed, clean flashed, tried different kernels, fixed permissions, different download.
Any ideas?????
I have restored the previous version for the time being.
TIA
Dave
Click to expand...
Click to collapse
you need to be sure to do a full wipe, because that is what happens when you dont
CastleBravo said:
I had the same problem, and couldn't fix it until I updated to the latest version of CWM recovery. Even if you think that you have the latest version, find the thread for it and re-flash it anyway. Then, do a FULL wipe, install Viper, then install the suggested kernel and see if it works, only after that, then try other kernels if you want to.
Click to expand...
Click to collapse
I will switch recovery to CWM, even though I don't like it, even from T'bolt days. I DO realize that the recovery will affect the Rom installs
Bigandrewgold said:
you need to be sure to do a full wipe, because that is what happens when you dont
Click to expand...
Click to collapse
Overnight I decided a complete wipe was in order. I also noticed something with the quick settings and notifications that is different. The quick settings scroll across the top of the notification menu and the page is skittish.
Time to back up all storage items.
Thanks for the responses.
RLGL said:
I will switch recovery to CWM, even though I don't like it, even from T'bolt days. I DO realize that the recovery will affect the Rom installs
Click to expand...
Click to collapse
If this solves the problem, please post back. I've seen two instances of it so far (one from twrp, one an early version of cwm) and I'm interested to see if these were isolated events or actual problems with the recoveries.
CastleBravo said:
If this solves the problem, please post back. I've seen two instances of it so far (one from twrp, one an early version of cwm) and I'm interested to see if these were isolated events or actual problems with the recoveries.
Click to expand...
Click to collapse
I installed the latest version of CWM and reflashed Viper. So far all looks good. Also one other issue has cleared up, unmounting the USB drive no longer causes apps to stop. The only other change I made was from ES File explorer to Root Explorer.
The recovery causing issues also surfaced with the Thunderbolts. CWM was the villan in those instances.:fingers-crossed:
Hey guys here at xda!!
I've got a little problem and i'd like to know if someone can help me fix it
So, yesterday i used Rom Toolbox to disable some receivers for some apps....nothing too special, i just disabled the ones i though weren't really needed for those apps....also some notification ones or at boot time ones i think (also i don't remember touching any startup apps because i already had handled those with startup manager free)....anyway: now reboot is stuck...at, well, reboot (bootanimation)...
Does anyone know how i can restore Rom Toolbox changes, or reenable all receivers from recovery?
Or something else which might help?
Unfortunately, i don't have either a recent nandroid nor a recent titanium backup. So switching roms would be a pain...
MY ROM: Foxhound 0.1 for Galaxy S3 based on stock 4.2.2 (kernel is stock) and i have xposed framework, just in case that might help:good:
I really appreciate your help guys! PEACE!
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
boomboomer said:
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
Click to expand...
Click to collapse
thanks for the reply!
safe mode (which i had never even known existen on android) appears to not be working....i mean it keeps getting stuck at boot so who knows why,
i flashed the rom, rebooted, it booted (yay) and then the usual message popped up with "updating applications x out of x", and after having finished it appears to be stuck at the same message with "opening applications under way" (translation from italian). the title of the message is "updating/upgrading android os"...
i think i might be force to flash a new rom
After flashing a new version of CM11, i found myself in a loop upon startup where many of the core applications of android stopped working. When i reverted back to the old version that worked(I didn't have a backup saved but rather i flashed the older nightly of the rom again), I noticed that my home button, lock screen, and notification bar/toggle screen wasn't working any more. I looked into it and looked at my apps, and saw an unnamed app with the description "com.android.keyguard". upon looking this process up, i found out that when people disabled this process their home button, lock screen, and notification bar stopped working (coincidental eh?), and decided that this was the source of the problem.
Is there any way to load on a new, fresh version of "com.android.keyguard" or should i just do a factory reset? I would prefer to save my local data, but if i must do it in order to have a phone that does anything useful, i obviously will.
If I need to do a factory reset, what is the cleanest and smartest method of doing so? I know titanium backup can cause a lot of problems (and in this case i'm worried it will duplicate com.android.keyguard), but I assume there is some sort of method that makes a factory reset while retaining the bulk of user data very easy. am i correct?
Do a full wipe and flash again, check the md5 of your download.
Only use titanium for use apps, never system apps or settings. There is no easier way to change rom.
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Jahid4 said:
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Click to expand...
Click to collapse
Flash back to stock and start over.
Beamed in by telepathy.
Hey Folks,
So I got this Z2, running Existenz MM 5.6.5.
Today I installed the AccuWeather App via Google Playstore. A moment later the System UI FCed, but that's not really new, happens from time to time. But now the screen stays black. I can see the backlight, but the screen is still black. Tried the reset button under the left hatch. It's booting, but after all, black screen.
Got into recovery, backed everything up, recovered the backup - hoped to kick the faulty software back in line. Didn't work, think it was a naive idea.
So I want to keep all that SMS stuff and also the messenger stuff - if there's any chance.
Right now I'm downloading the .291 FTF and the 6.5.6 EXISTENZ Update.
So, I just tried to call the Z2, the screen wakes up, but the System UI keeps crashing.
Any suggestions for solving this problem are welcome, thanks a lot!
JackDCalloway said:
Hey Folks,
So I got this Z2, running Existenz MM 5.6.5.
Today I installed the AccuWeather App via Google Playstore. A moment later the System UI FCed, but that's not really new, happens from time to time. But now the screen stays black. I can see the backlight, but the screen is still black. Tried the reset button under the left hatch. It's booting, but after all, black screen.
Got into recovery, backed everything up, recovered the backup - hoped to kick the faulty software back in line. Didn't work, think it was a naive idea.
So I want to keep all that SMS stuff and also the messenger stuff - if there's any chance.
Right now I'm downloading the .291 FTF and the 6.5.6 EXISTENZ Update.
So, I just tried to call the Z2, the screen wakes up, but the System UI keeps crashing.
Any suggestions for solving this problem are welcome, thanks a lot!
Click to expand...
Click to collapse
I think you can do nothing about systemui
But for SMS back up your rom
Then reflash Existenz rom and restore messaging app data using titanium backup app(restore all things that related to SMS)
It may works
raminta said:
I think you can do nothing about systemui
But for SMS back up your rom
Then reflash Existenz rom and restore messaging app data using titanium backup app(restore all things that related to SMS)
It may works
Click to expand...
Click to collapse
So reflashing the the Existenz ROM may be the only Option left? OK.
So, backing everything up, then flashing Existenz (the latest update didn't do the trick), all it's updates and then, recovering a few apps, using the TWRP-Backup as a source? Nice Plan, gonna give that a try.
Thanks for your thoughts raminta.
JackDCalloway said:
So reflashing the the Existenz ROM may be the only Option left? OK.
So, backing everything up, then flashing Existenz (the latest update didn't do the trick), all it's updates and then, recovering a few apps, using the TWRP-Backup as a source? Nice Plan, gonna give that a try.
Thanks for your thoughts raminta.
Click to expand...
Click to collapse
i meant use clean installationthere is no need to flash all updates just flash v5.0.1 and then v5.6.5 and you will be fine
then use titanim backup
//use thanks button
long story short after full wipe, for the newest lineage os , ,gyroscope dosnt work anymore
ive tried with TWRP to go back to my last rom full backup (oldder lineage ver)
almost everything was there's (beside the gyroscope \screen rotation )
what can i do?
thanks
solve it (by flash stock ROM)
ok.. something weird.. after getback to any lineage still no gyro anymore
Superrman said:
ok.. something weird.. after getback to any lineage still no gyro anymore
Click to expand...
Click to collapse
Are you trying official or berni's?
Hi.
Have you found any solution? I am having quite the same problem.
All sensors (acceleration, compass, gyroscope, light, proximity) stopped working at my XZ5c.
Using Official LineageOS 14.1 latest version (14.1-20190207).
What I have tried:
Did an upgrade of LinOS, wiped dalvik and cache.
Even after a wipe of data all sensor are not working.
Tried something I found in the Xperia Z1 section
execute the following shell command (...):
kill $(pgrep sensors.qcom)
This kills the sensors.qcom process. ( It will restart automatically )
Click to expand...
Click to collapse
But it did not take any effect.
How do i know: Proximity sensor is not working when using telephone.app. Automatic screen brightness is not working. All other sensor readings only show up a "–" when reading out e.g. with SatStat.app.
Any ideas??
solve it (by flash stock ROM)
Click to expand...
Click to collapse
Did the same. Now sensors are working again.
Also see this Post.
Still: Someone knows how that happens? Would like to avoid all the flashing and restoring for the future if this is possible...
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
TheVan28 said:
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
Click to expand...
Click to collapse
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Son-Y said:
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Click to expand...
Click to collapse
My problem is that, even if i do a complete wipe, i still get the sensors issue
if i open an app like cpu-z they litterally don't exist, i get a blank page
I had the same problems and also persisting after a complete wipe.
My solution was:
Flashing Sony StockROM as descirbed in ( this post) .
This sorted my sensor issues. Check your sensors while in StockROM to make sure they are phyically OK
Then you can go back to whatever TWRP/CustomROM you like.
Hope that helps!
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Yep. I also cannot tell why it worked, could only tell you how...
Son-Y said:
Tried something I found in the Xperia Z1 section
But it did not take any effect.
Click to expand...
Click to collapse
I think pgrep no longer works on Nougat.
Code:
kill $(pidof sensors.qcom)
should work.
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
berbigou said:
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
Click to expand...
Click to collapse
Can you be more clear about the steps? how do you install stock kernel?