Here are some issues I encountered since I installed version 2.16.
Wifi doesn't work by itself, it has to be started with terminal wifical sh command. GPS also doesn't work. The only way to make everything work is to go in the boot menu, clear both caches, them upon boot, do the wifi command. However, if I turn off the phone none of them will work after reboot. I also noticed that the sound is gone, no sound for notifications, nor for the phone ringer.
Related
I did manual updates all through the Froyo pre-release process, and now I am seeing these bugs that others apparently see fixed with FRF91:
- WiFi disconnects from my home router randomly (was fixed in FRF83, broken again now for me in FRF91)
- Car Dock nightmares - it keeps forgetting the speakerphone settings, touchscreen unresponsive until off/on action, randomly uses N1 speaker instead of dock speaker for navigation directions
- Vibrate 2-step volume down option lost (this may be a feature but still I hope not)
Is there a SIMPLE way for me to just 'reinstall' or 'repair' the OTA FRF85B, much like you can reinstall Windows over the top of itself without losing all your settings?
Key: I don't want to lose my apps and settings at all!
If you're rooted you could use titanium backup and flash an earlier build.
If not, you probably would have to use a PASSIMG then update to 85B - but you'd lose your settings. The market sync will give you all your apps back once you sign in though.
________________________
N1 w/ XDA App
Thanks. Is it actually possible to have a botched install of FRF91, leading to the above possible issues, or would my Froyo update either 'work properly' or 'not at all'?
Just don't want to go through all the trouble of reinstalling from a clean factory build for no reason.
And if it is possible, can you clarify how Titanium Backup will help me? Will it provide a simple way to just 'install 2.1' in a few clicks?
not sure what you mean about the vibrating deal, but on my phone when i press down volume, it never shows a silent icon, the lowest i can get is the "vibrate" icon, its still silent but it reads like its on vibrate. I cant remember if this started at the initial unofficial froyo or one of the later versions. Does anyone else experience this, or maybe its supposed to be this way? i can live with it (not important enough to start a whole thread), its just annoying...
Well for some ridiculous reason Google removed the lovely 2-step vibrate option (where you would press volume down once for vibrate and again for silent), and changed the Sound settings area so that you can now only choose whether the phone vibrates in silent mode or doesn't vibrate in silent mode.
I loved this feature before. The iPhone had to have a dedicated switch for this, but Google solved it with ingenuity. Now in their infinite stupidity, they removed it completely. Doh.
Came home from dinner tonight and set my phone down on the nightstand, went downstairs. Came back up, phone is dead...plugged in, but now I can't do anything. Every time it boots (even in safe mode) I get process system not responding and the phone is stuck. I can't do anything from this point.
No issues at all up to this point...it's like the phone just randomly self destructed. What do I do? I'm still on 5.1, no recent backup because like I said I had been having no issues at all....I am rooted with xposed, amplify and greenify, if that makes a difference. Stock 5.1 otherwise...
I did try booting to recovery and wiping cache...no dice. Did the android is starting with upgrading apps thing, but then back to this nonsense again...
HELP PLEASE!
Install a ROM or flash factory image with fastboot.
Assuming you left USB Debugging and OEM Unlock enabled in Developer Options, your best bet is to flash a new ROM.
EDIT: @scryan beat me to it.
interestingly, i was able to get it to boot long enough this morning to (slowly, between all the 'not responding' messages) get it to disable everything in xposed and reboot again...now it seems to be working. seems something in one of the xposed modules completely borked the system. any idea how that could happen after running smoothly forever really?
also strange, it seems most of my settings have gone back to factory...for example, i use chomp for sms, but on the reboot it's bringing up both chomp and messenger notifications (even though i had chomp set as the default SMS client).
edit: it was amplify causing the issues, it seems. there must be something in the new version that fubar'd my phone. i turned every module back on except amplify, and the phone is good again...
crackers8199 said:
interestingly, i was able to get it to boot long enough this morning to (slowly, between all the 'not responding' messages) get it to disable everything in xposed and reboot again...now it seems to be working. seems something in one of the xposed modules completely borked the system. any idea how that could happen after running smoothly forever really?
also strange, it seems most of my settings have gone back to factory...for example, i use chomp for sms, but on the reboot it's bringing up both chomp and messenger notifications (even though i had chomp set as the default SMS client).
edit: it was amplify causing the issues, it seems. there must be something in the new version that fubar'd my phone. i turned every module back on except amplify, and the phone is good again...
Click to expand...
Click to collapse
Perfect chance to update to 6.0
My BT turning off after start. It happens at the very end of booting - BT disappear after all widgets are done (after calendar widget appears which is my last visible boot app).
I think it's has started since I enabled Shallow Hibernation and Aggressive Doze.
I tried everything - disable greenify, uninstall supersu, xposed and about 20 apps (which I might install lately).
It doesn't happen on my other TWRP backups - so it is software not hardware.
I cleared data of Bluetooth Share, too.
Bludroid_timer makes my bluesleep won't let device to go to deep sleep (37% in BetterBatteryStats)...
Is there any way to reset bt? in build.prop or delete some BT files? maybe flashing some BT reset zip in TWRP?
Is it possible to save a boot log and see what app/process disable BT after start?
My Pixel 4 XL has been acting since it froze and I had to force restart it. It was froze on the aod with a static looking block in the corner. After the reboot that seemed normal here's what's wrong:
-home button and app switch don't work, only back
-notifications ding but don't show and pulldown doesn't pull the second time.
-theres things missing from settings especially what is Google related
-assistant is broken
-calling and data are not working but have signal bars, rcs messages are working, haven't tested regular sms.
Currently I'm waiting on things to backup, I have disabled all tweaks I have and even pushed the Feb full ota from the computer, completed successfully but still the same issue.
Going to try pushing the regular firmware without wipe to see if that fixes anything before doing a factory reset.
Bluemgt06 said:
My Pixel 4 XL has been acting since it froze and I had to force restart it. It was froze on the aod with a static looking block in the corner. After the reboot that seemed normal here's what's wrong:
-home button and app switch don't work, only back
-notifications ding but don't show and pulldown doesn't pull the second time.
-theres things missing from settings especially what is Google related
-assistant is broken
-calling and data are not working but have signal bars, rcs messages are working, haven't tested regular sms.
Currently I'm waiting on things to backup, I have disabled all tweaks I have and even pushed the Feb full ota from the computer, completed successfully but still the same issue.
Going to try pushing the regular firmware without wipe to see if that fixes anything before doing a factory reset.
Click to expand...
Click to collapse
It's a known issue since nougat (at least, maybe even prior to that), where the phone thinks the initial setup wasn't completed.
There's an article here that explains how to fix this with 2 adb commands. After that it should prompt you the setup again, or it just fixes itself, I don't remember exactly.
TENN3R said:
It's a known issue since nougat (at least, maybe even prior to that), where the phone thinks the initial setup wasn't completed.
There's an article here that explains how to fix this with 2 adb commands. After that it should prompt you the setup again, or it just fixes itself, I don't remember exactly.
Click to expand...
Click to collapse
I'd assume using a terminal app, because there was no connection to the computer and dev options were missing.
I'd delete your cache and see if that does it, if not a full image with the wipe removed should bring it up just fine although you'll have to root again after.
Bluemgt06 said:
I'd assume using a terminal app, because there was no connection to the computer and dev options were missing.
Click to expand...
Click to collapse
Here is a guide if you don't have adb enabled or you cannot access adb
This might be the app itself but I didn't have any issue on my S20. Since I updated the phone it randomly cuts out. Any ideas? Never on WiFi though...
arknailed7754 said:
This might be the app itself but I didn't have any issue on my S20. Since I updated the phone it randomly cuts out. Any ideas? Never on WiFi though...
Click to expand...
Click to collapse
Is it when the screen is off? Check it's not been put to sleep in battery settings
it seems that latest ROM updates (I think I have this on all AUB* ones) is weirdly strict on background activities and cuts every one of them. my whole device acts strangely - apps not showing notification or showing them late (hours later than they were supposed to show), my apps are not updating: I have to repeatedly FC play store, then clear its cache so that currently installing app changes state from downloading to installing, than do it again to change state fomr installing to installed etc. worked fine on AUA* ones. it is really annoying. btw I tried to clear cache and dalvik/art cache from recovery, but that did not help. I have not tried factory seset yet...
It seems that it was data corruption during regular OTA. Factory reset seems to fix problems for me.
I'll try a reset.. thankyou
Let's be honest, the Spotify app has issues too begin with. On my S21 and Pixel 4 it can be playing songs to my earbuds then suddenly stop running in the background on its own! Unlock the phone and itis still open in the foreground.
Perhaps it's time for a new music app if this is a known Spotify issue... But if it's not a Spotify issue, then check in your battery settings (as others have mentioned) to see if your phone automatically started putting it into "Sleep Mode".