Google's serverside battery saver let my OPO bootloop? - ONE Q&A, Help & Troubleshooting

Hey, guys. Maybe you have been following this:
https://www.reddit.com/r/GooglePixe...r_saving_mode_turning_itself/?sort=confidence
Google confirmed, that the can activate the battery saver from their and accidentally had the test group set to big. A lot of devices over the whole range had the problem. And I suspect it made mine bootloop:
I was helping friends of family get their internet connection up and running around that time. I once used my bacon to check for the SSIDs in the area and then didn't touch it anymore, until the job was done approx 2 hrs later. So I pulled out my bacon and it was at the part, where I should enter the encryption password. No biggie, I though. Random reboots occur when you ROM. Entered the password only to have it boot for ages and finally bringing me to TWRP with "Rescue Party" tag. Up until now I didn't get it up and running. I flashed substratum rescue, removed every magisk module and then magisk alltogether. It still does not boot but brings me back to TWRP. I will try dirty flashing in order to get back into the device and securing everything again before factory resetting it. I hope that will be the end of it.
Anyway: i have a bacon running the latest LOS. Anybody experience something similar? Or would you consider this all to be a coincidence? Timing wise it'd fit perfectly to above battery saver issue. I'm taken aback, that something relatively harmless like activating the battery saver at the same time was a kill switch for my device. I was always confident enough to have a rooted and ROMed phone as my daily driver. But if this can happen, what else could?
device: bacon
ROM: latest LineageOS
rooted: yes (Magisk)

Related

Phone freezing more and not waking

I've been on Humble 1.42 for about a month now (please don't look down on me, haven't had time to switch since the drama) and I am starting to have some issues with my phone not waking. At random moments, my screen would refuse to turn on no matter what I do. It does, however, respond to me holding down the power button for a forced power off (hard reset?) Anyhow, has anyone else experienced this at all? I had a feeling it was my xfinity mobile app because I had been getting a lot of errors from it lately even though I rarely ever use it. Should I just switch to another rom or is there any other apps known to cause issues with this rom that I should be aware of?
On a side note, I have been on this forum and obsessed with android for the past year and been doing some serious thinking about making a career change into Android development. Been doing some java tutorials on youtube over the last few months and the such and think I'm about ready to start some real android app development. I credit some of the great developers on this site and the awesome experience at Dreamforce this week as the tipping point. Any ideas on additional resources I should look into?
There are a few things that could be causing this problem(that I'm aware of)
1) You may have sideloaded a "virus" app. I attempted to sideload an app once(will never do it again after what happened..) and it completely BROKE my phone. It made apps unable to isntall, the screen would take FOREVER to wake(if it ever did wake) and plenty of other problems. I tried rebooting and got stuck in a bootloop(boot animation would never end), did a factory reset and everything force closed on me so I was forced to flash the .md5/.pit to go back to bare stock and that finally fixed it.
2) Have you flashed Fuju Tweaks? This exact same thing happened when I flashed it on Gummy2.0, worked fine on Eclipse1.3.1 and even works for a lot of people on Gummy2.0 but it wouldn't work for me.
3) Try reflashing your ROM, that's how I fixed the Fuju Tweaks problem. It might fix whatever plagued your phone.
Just let me know of anything you've done recently and I'll try and diagnose the problem(if I didn't already).
Uh-Oh, a virus maybe? Yeah, I will just reflash later on, and change some passwords while I am at it.
I don't think it was that kind of virus but it definitely screwed up my phone.

[Q] Inspire thinks it's in a car dock with non-Inspire based kernels

Now, from what I can gather, this problem stems from a faulty or dirty Micro-USB port. I tried compressed air, but it did nothing for me.
I decided to do a complete unroot, S-ON, factory restore and call HTC to see if I could get it fixed. To my surprise, the problem vanished. Thinking I had lucked out and that fixed it, I re-rooted the phone and the problem still didn't reappear.
Then, thinking I would start small, I flashed a Sense kernel. As soon as I rebooted it went straight to Car Home and began answering in speakerphone. For laughs I went ahead and flashed MIUI then CM7, both of which exhibited the same behavior.
After all of this, I got to wondering just why the stock ROM and kernel worked but nothing third party would. Then it hit me that all the 3rd party stuff I had been using were DHD ports, and not based off the Inspire. I downloaded and flashed ClearDroid, which has an Inspire base, and the problem is once again dormant.
The only sense I can make from it is that HTC has implemented some kind of fix for shoddy USB ports in the Inspire kernel.
So now here's the question: Does anybody know anything about this, and would it be possible to implement said fix in, say, and AOSP kernel?
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Also Im pretty sure when your rooted this setting will take effect as to where a nonrooted phone doesn't allow the permission to execute the command.
Gizmoe said:
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Click to expand...
Click to collapse
I'll try that, but I can completely wipe my phone (cache, system, data, d-cache), flash CM 7.1.0, and without even logging into my Google account it happens.
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Agoattamer said:
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Click to expand...
Click to collapse
Both.
With the stock ROM and kernel, everything is fine. With the stock ROM and a DHD-based kernel it happens. With any AOSP ROM it happens.
Removing the Car Dock app keeps it from launching, but the phone still defaults to speakerphone for all calls (incoming and outgoing).
Gizmoe said:
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Click to expand...
Click to collapse
The problem about warrantying it is when it's in a stock state, it works fine.
I've never dealt with HTC, but I can't exactly see it going over well if I call up and say "My phone acts funky when I run CyanogenMod".
The airplane mode fix is something I haven't heard before. I guess I'll give it a go.

[Q] N8013 Random Reboots- Requesting Help

Device: Note 10.1 N8013 (Wi-Fi Only Model)
The Problem:
The device randomly reboots itself- it's happened while I was scrolling between pages on the launcher, connecting to a WiFi network, and sometimes even when the device was just sitting on its own.
So far, it's happened on every custom ROM I've tried (Omni, IOKP, IOAP and CM), and even Stock TW flashed via Odin with and without a PIT File.
The duration between reboots is inconsistent, but it's always a full reboot- suddenly back to the Samsung logo and then the ROM logo, beore the system loads up normally.
Probable Causes (my best guesses):
Apps are almost definitely not a cause, because I only install a handful (ES File Explorer, GoldenDict, AnyMemo, Mantano Reader, Skype, Manga Watcher, Opera Browser, MXPlayer, AdAway, Greenify and Helium backup).
***One particular event sticks out to me though: early on when I first got the device, the battery ran out, and I had to leave it as is for 2 weeks, due to some family issues.
My Questions:
1.) How would I go about diagnosing the cause of the random reboots?
2.) Could the extended Battery depletion described above be the cause of my instability issues?
3.) If my current battery is indeed the problem, should I buy a replacement from NewPower99? I am worried that since the Note 10.1 is a 2-year old device, a Li-Ion Battery sitting on a store shelf for such a long duration would be no better than the stock one I have now.
Note: Unfortunately, I waited too long and the tablet is beyond its Warranty Date, so sending it in for repair/replacement is not an option.
Thank you for taking the time to read this. I'd really appreciate any help/advice you can give!
same here
mowgli_writes said:
Device: Note 10.1 N8013 (Wi-Fi Only Model)
The Problem:
The device randomly reboots itself- it's happened while I was scrolling between pages on the launcher, connecting to a WiFi network, and sometimes even when the device was just sitting on its own.
So far, it's happened on every custom ROM I've tried (Omni, IOKP, IOAP and CM), and even Stock TW flashed via Odin with and without a PIT File.
The duration between reboots is inconsistent, but it's always a full reboot- suddenly back to the Samsung logo and then the ROM logo, beore the system loads up normally.
Probable Causes (my best guesses):
Apps are almost definitely not a cause, because I only install a handful (ES File Explorer, GoldenDict, AnyMemo, Mantano Reader, Skype, Manga Watcher, Opera Browser, MXPlayer, AdAway, Greenify and Helium backup).
***One particular event sticks out to me though: early on when I first got the device, the battery ran out, and I had to leave it as is for 2 weeks, due to some family issues.
My Questions:
1.) How would I go about diagnosing the cause of the random reboots?
2.) Could the extended Battery depletion described above be the cause of my instability issues?
3.) If my current battery is indeed the problem, should I buy a replacement from NewPower99? I am worried that since the Note 10.1 is a 2-year old device, a Li-Ion Battery sitting on a store shelf for such a long duration would be no better than the stock one I have now.
Note: Unfortunately, I waited too long and the tablet is beyond its Warranty Date, so sending it in for repair/replacement is not an option.
Thank you for taking the time to read this. I'd really appreciate any help/advice you can give!
Click to expand...
Click to collapse
I have the same problem The device randomly reboots itself
but the battery life is better that the stock ROM for me and the sound too
replace the battery that my advice for you
goodluck
"sorry for my bad english"
Thank you
badralamoudy said:
I have the same problem The device randomly reboots itself
but the battery life is better that the stock ROM for me and the sound too
replace the battery that my advice for you
goodluck
"sorry for my bad english"
Click to expand...
Click to collapse
Thank you, badralamoudy. It's nice to know I'm not alone with this problem. Two quick follow-ups though:
1.) Which ROM are you using right now?
2.) Have you replaced the battery on your device? If you have, did it fix the random reboot problem?
Thank you for trying to help.
I am a noooob
mowgli_writes said:
Thank you, badralamoudy. It's nice to know I'm not alone with this problem. Two quick follow-ups though:
1.) Which ROM are you using right now?
2.) Have you replaced the battery on your device? If you have, did it fix the random reboot problem?
Thank you for trying to help.
Click to expand...
Click to collapse
1- omni rom
2- no
my battery is good and still reboot randomly
I used Omega ROM before omni and it was stable
when you flash back to stock. Do you let google play reinstall your apps and data.
My Suggestion is flashing back to the latest Samsung full firmware . Then Do not let google play reinstall your apps or app data..
Install only one at one day See how it does . another the next day and so on
OHH After you flash the new stock firmware . Reboot and do a factory restore .
I have had this issue with my nexus and other devices when i flashed alot. I think its just left over data or something corrupt you are restoring

Is this a hard-brick?

I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

H830 LG G5 - Too many problems to list in title

So I have a fairly large host of problems on my LG G5 H830. I've tried a total of 3 different roms, and most of the problems have persisted throughout each rom.
Resurrection Remix:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Magisk Manager periodically unroots; I have to reflash the MagiskManager zip in TWRP about twice a day.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
System Process sometimes stops responding, causing the lock screen to not show and allowing anyone to access my phone for a short time.
Whenever I try train my voice model for Google Assistant, the Google app stops responding before crashing. This means that I can't get the "OK Google" prompt to work.
My battery sometimes simply fails to charge. For example, I charged my phone overnight, and the battery graph shows that it charged to about 50% or so before dropping back to about 20% and staying there until I noticed in the morning.
AICP:
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(I haven't tested Google Assistant, and haven't had the System Process or battery drain issues - but I didn't have the rom installed long enough to truly test.)
Xenon HD:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(As with AICP, I didn't install the rom for very long and did not test for the Google Assistant, System Process, or battery drain issues.)
The one problem that persisted through each rom was the incorrect display of storage capacity and usage, but TWRP has no problems with this. It also has no problem with charging. In addition, I've tried resizing, repairing, and re-formatting to EXT4 on my system, Data, and cache partitions. I don't know what else to try at this point, but since TWRP doesn't work any differently than I'd expect, it doesn't seem to me like a hardware issue - but then, I'm not an expert by any means, which is why I'm opening this thread.
Gannondalf said:
So I have a fairly large host of problems on my LG G5 H830. I've tried a total of 3 different roms, and most of the problems have persisted throughout each rom.
Resurrection Remix:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Magisk Manager periodically unroots; I have to reflash the MagiskManager zip in TWRP about twice a day.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
System Process sometimes stops responding, causing the lock screen to not show and allowing anyone to access my phone for a short time.
Whenever I try train my voice model for Google Assistant, the Google app stops responding before crashing. This means that I can't get the "OK Google" prompt to work.
My battery sometimes simply fails to charge. For example, I charged my phone overnight, and the battery graph shows that it charged to about 50% or so before dropping back to about 20% and staying there until I noticed in the morning.
AICP:
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(I haven't tested Google Assistant, and haven't had the System Process or battery drain issues - but I didn't have the rom installed long enough to truly test.)
Xenon HD:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(As with AICP, I didn't install the rom for very long and did not test for the Google Assistant, System Process, or battery drain issues.)
The one problem that persisted through each rom was the incorrect display of storage capacity and usage, but TWRP has no problems with this. It also has no problem with charging. In addition, I've tried resizing, repairing, and re-formatting to EXT4 on my system, Data, and cache partitions. I don't know what else to try at this point, but since TWRP doesn't work any differently than I'd expect, it doesn't seem to me like a hardware issue - but then, I'm not an expert by any means, which is why I'm opening this thread.
Click to expand...
Click to collapse
Pretty much every issue you're having has been documented already, so it's not your phone.
1) NFC is completely broken on h830 in custom ROMs.
2) Magisk works fine, stop using magisk hide and built in magisk busy box, it will hide root from itself. This is a magisk issue not a ROM issue. If you need busy box download it from play store.
3) Storage size being incorrectly shown had been the case ever since cm 14.1 became available and therefore affects all Los based ROMs.
4) Don't use Google Assistant but others have stated there are issues with it.
5) Make sure after rebooting to unplug and replug your charger or it won't charge.
6) If it was a clean flash and you installed correct gapps, you shouldn't have system processes force closing. Make sure your using opengapps 7.1, arm64 and newest version available and nano or pick version.
The above issues affect basically every lineage os based ROM currently. Hopefully this helps
jeffsga88 said:
Pretty much every issue you're having has been documented already, so it's not your phone.
1) NFC is completely broken on h830 in custom ROMs.
2) Magisk works fine, stop using magisk hide and built in magisk busy box, it will hide root from itself. This is a magisk issue not a ROM issue. If you need busy box download it from play store.
3) Storage size being incorrectly shown had been the case ever since cm 14.1 became available and therefore affects all Los based ROMs.
4) Don't use Google Assistant but others have stated there are issues with it.
5) Make sure after rebooting to unplug and replug your charger or it won't charge.
6) If it was a clean flash and you installed correct gapps, you shouldn't have system processes force closing. Make sure your using opengapps 7.1, arm64 and newest version available and nano or pick version.
The above issues affect basically every lineage os based ROM currently. Hopefully this helps
Click to expand...
Click to collapse
Thanks a lot for clearing this up! I'll take those suggestions and see if I have any luck (especially with the battery charging issue, since I mostly figured the other ones out on my own). I just came from a Moto G3 with RR, which seems to be a lot more stable than the H830, so all this at once caught me by surprise a bit.
Again, I appreciate your help with this.
Gannondalf said:
Thanks a lot for clearing this up! I'll take those suggestions and see if I have any luck (especially with the battery charging issue, since I mostly figured the other ones out on my own). I just came from a Moto G3 with RR, which seems to be a lot more stable than the H830, so all this at once caught me by surprise a bit.
Again, I appreciate your help with this.
Click to expand...
Click to collapse
No problem. By the way, I think RR is probably the best custom ROM for our device overall, especially if you like customizations But, they're are still some issues. Another issue to be aware of is that on Los based ROMs the camera isn't anyways saving videos (messed up part is that this only started happening in last month or so, it worked fine before that lol).
Gannondalf said:
Thanks a lot for clearing this up! I'll take those suggestions and see if I have any luck (especially with the battery charging issue, since I mostly figured the other ones out on my own). I just came from a Moto G3 with RR, which seems to be a lot more stable than the H830, so all this at once caught me by surprise a bit. Again, I appreciate your help with this.
Click to expand...
Click to collapse
Just an honest opinion. You shouldn't have got a LG G5 if your intention was to use AOSP roms. You could get a Moto Z Play, or a Moto G5 Plus.
LG and Samsung phones would always have issues on AOSP roms.
suhridkhan said:
Just an honest opinion. You shouldn't have got a LG G5 if your intention was to use AOSP roms. You could get a Moto Z Play, or a Moto G5 Plus.
LG and Samsung phones would always have issues on AOSP roms.
Click to expand...
Click to collapse
I'm starting to realize that. I got it based off of the design (which I really like, especially with the rear fingerprint scanner) and the specs, and didn't do much more research than seeing that there were confirmed methods of installing custom roms. But, at this point, I can't return it and I'm more interested in getting it to work as best as I can.

Categories

Resources