Related
hi everyone!
ok so last night I flashed franco kernel on my phone and I went to bed setting an alarm for 8. in the morning I woke up but not at 8, because my alarm didn't go off. why? because my phone was off. it got so unbelievably hot that you literally couldn't hold it for more than 3 seconds without seriously burning yourself. there's also the Google bumper case on it, that's how got it got. I have no idea how, or why it got so hot, but it did. the only thing I can think of is franco kernel, and how the vibrator frequency is set so high. but when I checked my battery graph app it showed no results from 3 to 8:40, or about 2 hours after I plugged my phone in and went to bed. by the time the phone finally turned on, the battery was at 40 percent, and I noticed that all my Wi-Fi access points got deleted, as well as my wallpapers on the launcher (the ones I set, not the built in ones). I didn't really think anything of this, until now when I went to use Google maps, and the location was off by a lot and there's a huge 5km wide blue circle around my location. I thought it was a maps problem and cleared data with no luck. I tried other location apps like transit with the exact same problem, so now I'm thinking... did the insane temperatures melt something? did it destroy my Wi-Fi location thing? why did it get so hot? like I've never had this problem before until I flashed franco kernel so I'm assuming it's a problem with that. anything I could do to fix my phone? thanks!
It's possible but I'm pretty sure the phone would shut off before damage happened (and that feature is in an area where the kernel can't touch).
This may or may not help but disable the Google Plus app.
For some reason it started glitching out and was continuously using 100% CPU even though I never used the app. Disabling it let my battery last more than an hour and stopped the heat issues.
Mine gets randomly hot.Try to restore a backup and see what happens. IF that doesn't work you might need to restore a factory Image. Can you use adb/fastboot?
mgear2 said:
It's possible but I'm pretty sure the phone would shut off before damage happened (and that feature is in an area where the kernel can't touch).
This may or may not help but disable the Google Plus app.
For some reason it started glitching out and was continuously using 100% CPU even though I never used the app. Disabling it let my battery last more than an hour and stopped the heat issues.
Click to expand...
Click to collapse
if it did then why was it blazing hot in the morning after 5 hours when it turned off? :/ and i was thinking of that, google plus shows up in the battery graph even though i never used it, but i use auto backup so wouldnt it stop working if i disable it?
habitformer said:
Mine gets randomly hot.Try to restore a backup and see what happens. IF that doesn't work you might need to restore a factory Image. Can you use adb/fastboot?
Click to expand...
Click to collapse
i dont have any backups and i restored a factory image, i restored the system, boot, radio, and cache, but its still broken... could it be possible that something bad happened to the hardware? because its looking more and more likely :/
NuckFuggets said:
i dont have any backups and i restored a factory image, i restored the system, boot, radio, and cache, but its still broken... could it be possible that something bad happened to the hardware? because its looking more and more likely :/
Click to expand...
Click to collapse
If you did all of that then it is possible there was some damage to parts inside the phone and RMA would be necessary. Although I imagine Google or LG would wonder how this happened
mistahseller said:
If you did all of that then it is possible there was some damage to parts inside the phone and RMA would be necessary. Although I imagine Google or LG would wonder how this happened
Click to expand...
Click to collapse
damn this will be my second rma.. but I'll just say that I plugged my phone in before i went to bed, set an alarm, and woke up to a blazing hot phone. that's not too far away from the truth
NuckFuggets said:
damn this will be my second rma.. but I'll just say that I plugged my phone in before i went to bed, set an alarm, and woke up to a blazing hot phone. that's not too far away from the truth
Click to expand...
Click to collapse
Do you use the original cable and charger to charge? Have you checked BetterBatteryStatts to see if an app is active when its not supposed to, i personaly think is unusal app activity that keeps the phone busy. Just flash the stock rom in fastboot and see if it improves or happens again.
gee2012 said:
Do you use the original cable and charger to charge? Have you checked BetterBatteryStatts to see if an app is active when its not supposed to, i personaly think is unusal app activity that keeps the phone busy. Just flash the stock rom in fastboot and see if it improves or happens again.
Click to expand...
Click to collapse
yeah I did, but no I haven't, it would be pointless because the phone turned off so the app wouldn't be to say what app went crazy. but yeah I flashed stock system and boot image with no luck, although the phone didn't overheat this morning lol
NuckFuggets said:
yeah I did, but no I haven't, it would be pointless because the phone turned off so the app wouldn't be to say what app went crazy. but yeah I flashed stock system and boot image with no luck, although the phone didn't overheat this morning lol
Click to expand...
Click to collapse
If it we`re me i`d factory reset and after that reflash the stock rom, there is an app/widget or setting that is borking you device.
gee2012 said:
If it we`re me i`d factory reset and after that reflash the stock rom, there is an app/widget or setting that is borking you device.
Click to expand...
Click to collapse
I was thinking of doing a reset, but I don't think it will work, I wiped dalvik and cache a number of times, and nothing worked. like nothing location related works anymore, so i don't think that a reset will do anything :/
NuckFuggets said:
I was thinking of doing a reset, but I don't think it will work, I wiped dalvik and cache a number of times, and nothing worked. like nothing location related works anymore, so i don't think that a reset will do anything :/
Click to expand...
Click to collapse
What went wrong when flashing the stock rom, i hope not a flash failure for remote device (or somethig like that)! Cause that would mean the internal memory got corrupted and is no longer available, repair or RMA.
gee2012 said:
What went wrong when flashing the stock rom, i hope not a flash failure for remote device (or somethig like that)!
Click to expand...
Click to collapse
I don't think anything went wrong with flashing the rom, I think that a component in the phone is just messed up cuz anything I did didn't help with the location thing :/
NuckFuggets said:
I don't think anything went wrong with flashing the rom, I think that a component in the phone is just messed up cuz anything I did didn't help with the location thing :/
Click to expand...
Click to collapse
That does have no effect on flashing a stock rom, look here for how to flash a stock rom (real easy) http://forum.xda-developers.com/showthread.php?t=2513701.
gee2012 said:
That does have no effect on flashing a stock rom, look here for how to flash a stock rom (real easy) http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
I did all that though, but minus the factory reset. still nothing :/
NuckFuggets said:
I did all that though, but minus the factory reset. still nothing :/
Click to expand...
Click to collapse
Then you have to send it in for repair. Maybe its hardware related.
Leaving your phone plugged in the power outlet overnight might be the cause, and I don't know how well franco kernel is optimized for such scenarios too. The auto shutdown prevented further damage to your phone.
ej8989 said:
Leaving your phone plugged in the power outlet overnight might be the cause, and I don't know how well franco kernel is optimized for such scenarios too. The auto shutdown prevented further damage to your phone.
Click to expand...
Click to collapse
I always do that, and never had a problem before :/ so Idk what happened
gee2012 said:
Then you have to send it in for repair. Maybe its hardware related.
Click to expand...
Click to collapse
yeah I guess. I'll call Google today and see what happens
If the phone shut down in the middle of the night and was still blazing hot in the morning even though the phone was off then that points at a charging issue that has overheated the battery. No custom kernel should be able to override the charging circuitry so I'd definitely say it's a hardware fault.
The overheated battery has probably damaged some of the antennae in your phone.
If I were you I would flash full stock and RMA your phone.
Sent from my Nexus 5 using xda app-developers app
I've read that overheating can damage battery or hardware..So Google will know better what's wrong with your phone.
Alex240188 said:
If the phone shut down in the middle of the night and was still blazing hot in the morning even though the phone was off then that points at a charging issue that has overheated the battery. No custom kernel should be able to override the charging circuitry so I'd definitely say it's a hardware fault.
The overheated battery has probably damaged some of the antennae in your phone.
If I were you I would flash full stock and RMA your phone.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I guess so. but then how come this all happened the night I flashed franco kernel? I've always used the same charger with no problems, it's only that night that everything went wrong.
I guess I'll have to rma it then, since this will be my second time I should be pretty good at it haha
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
Did you already tried to format your whole phone so also SD card / system/cache/ etc just make it completely clean and connect your phone to your PC while in recovery paste darkobas rom (or other rom ofcourse) on your sd-card and gapps flash it and start really clean.
Just my 2 cents
check ur phone hardware for damage as u had changed everything multiple time and still no profit which means problem is not on surface maybe its deep and i am irrational that any change of rom would help , that said maybe try to flash good firmware through fast boot ,take help from cc or more persons . i may be wrong but i had concluded this - it seems that the connection between gpu or cpu with os is kinda broken which doesn't make sense as u had changed it multiple times but still feels like it.
moneyvirus said:
Did you already tried to format your whole phone so also SD card / system/cache/ etc just make it completely clean and connect your phone to your PC while in recovery paste darkobas rom (or other rom ofcourse) on your sd-card and gapps flash it and start really clean.
Just my 2 cents
Click to expand...
Click to collapse
I have formatted everything and I believe I have removed everything useless from the memory. I have also flashed multiple roms and the issue is still there
IrrationalBanana said:
I have formatted everything and I believe I have removed everything useless from the memory. I have also flashed multiple roms and the issue is still there
Click to expand...
Click to collapse
Does the problem also occure when you have 0 extra apps installed so just rom and gapps?
It sounds like some background proces
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
Have you tried flashing the stock rom via fastboot? If that doesn't solve your problem, it might be hardware related. You can find the latest fastboot update here: link
Keep in mind that if you want the latest cos13, you'll have to update your device via the ota. This method will also completely erase your device, including /sdcard
If there is no background processes, try to install Cynogen OS 12.0.
If the phone have the same issue, then it is hardware.
Sent from my A0001 using Tapatalk
moneyvirus said:
Does the problem also occure when you have 0 extra apps installed so just rom and gapps?
It sounds like some background proces
Click to expand...
Click to collapse
Problem is there even after many completely fresh ROM installs (formatted all data from memory)
What are the files that re absolutely necessary for the phone to operate? Could there be some hidden junk in the internal memory Im not seeing?
yeah, NAND trimming is important. But not for a fresh install
eng_saad said:
If there is no background processes, try to install Cynogen OS 12.0.
If the phone have the same issue, then it is hardware.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Phone became stuck on bootlogo after installing CM 12 snapshot
IrrationalBanana said:
Phone became stuck on bootlogo after installing CM 12 snapshot
Click to expand...
Click to collapse
firmware
IrrationalBanana said:
Phone became stuck on bootlogo after installing CM 12 snapshot
Click to expand...
Click to collapse
The best solution in my opionion is to restore the stock ROM [COS 12.1 / 12.0]
Follow the steps in this thread
NOTE that your data will be deleted.
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
I had a similar problem on my lg g2. Some things to look out for before taking my advice:
-Is the animation/screen the only thing that's slow, but the background processes normal? (Like, if you type a bunch of letters, it registers all of them but the animation is slow).
-Prior to the problem, did you drop/bend your device, expose it to water, or take it apart?
If both (or one) of the top pertains to you, it's most likely a hardware issue. My g2 had the same problem, and it turned out to be a faulty flex cable that attached the screen output to the motherboard (I accidentally pulled too hard on it). Seeing how the OPO screen has a long black cable, that could possibly be the problem. If all else fails, and you have a bit of money to spend, get a replacement screen.
chikin said:
I had a similar problem on my lg g2. Some things to look out for before taking my advice:
-Is the animation/screen the only thing that's slow, but the background processes normal? (Like, if you type a bunch of letters, it registers all of them but the animation is slow).
-Prior to the problem, did you drop/bend your device, expose it to water, or take it apart?
If both (or one) of the top pertains to you, it's most likely a hardware issue. My g2 had the same problem, and it turned out to be a faulty flex cable that attached the screen output to the motherboard (I accidentally pulled too hard on it). Seeing how the OPO screen has a long black cable, that could possibly be the problem. If all else fails, and you have a bit of money to spend, get a replacement screen.
Click to expand...
Click to collapse
Thanks for the suggestions!! You are spot on with everything, the screen got cracked a while back and I bought a new screen for it. It was a bit dodgy and didn't fit well in the casing, so maybe a cable got pulled out lately?
On the background process thing; the typing thing is exactly as you described it. When writing my long WiFi password for example, I tap in all of the 18 characters and numbers of the password in 5 seconds, and then the screen spends the next 20 seconds doing the animation/typing in the characters, whilst I am not touching the screen. Does this mean the cables theory is solid? Or is it another hardware issue?
Stellar suggestions, I will probably spend an hour or two picking at the phone today, updates coming later
My OPO has never been slow on any ROMs. You can try to format your phone...
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
IrrationalBanana said:
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
Click to expand...
Click to collapse
send It to cc already
Traace said:
yeah, NAND trimming is important. But not for a fresh install
Click to expand...
Click to collapse
I have been reading trimming here but never found best or safe method. a link to best tutorial will be appreciated
#sychrome# said:
I have been reading trimming here but never found best or safe method. a link to best tutorial will be appreciated
Click to expand...
Click to collapse
Some roms trim by themself, others do not. It really difficult to tell which does and which not. U can test it if fstrim takes long time to run then your system usually didn't got trimmed anytime before.
Get Trimmer (fstrim) from Play Store. Its not necessary to trim system at all. Set your focus on partitions who have large amount of write processes like data or even cache.
IrrationalBanana said:
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
Click to expand...
Click to collapse
In my opinion, I still think it is a hardware error. Since you described some difficulty in replacing the screen, the cables might have been damaged, either during replacement or after. I suggest you buy a new screen, preferably one that comes already glued on to a frame.
Hey!
So, today my gf charged her OPO for 30 min, turned off. When she tried to turn it back on afterwards, the phone went into bootloader. She tried to restart it, but everytime it only restarts to bootlader. The first time there was also a picture of the android figure, but with an error message or sth like that, but she cannot remember exactly.
The phone is not rooted, stock firmware and stock bootloader, latest update of the official CM firmware (not oxygen OS).
We tried wiping cache only. No difference. We tried wiping all data. No difference.
Any other ideas?
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
zaoms said:
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
Click to expand...
Click to collapse
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Zigurat said:
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Click to expand...
Click to collapse
Wow good thinking back there. Most of users(including me) thinks software issue but you found it nice amd easily. Happy to know it is ok now.
Hi guys i am having a problem where my phone soft reboots after my screen is off.It happens on every rom.It stopped happening when i installed turbo rom for 2 days and then it came back.plz help
Arpan22 said:
Guys this has been a frustrating issue.When I turn my screen off my phone soft reboots.It happens on every rom.When i install the first 6.0.1 stock rom it freezes after every 5 minutes and reboots.Plz help me.This phone has turned useless,i am using aicp 12 and i have to keep my screen on and it doesnt last 5 hours.
Click to expand...
Click to collapse
Assuming you are flashing correctly, then this is a hardware problem...
Have you ever replaced your display panel? Bootlooping on Marshmallow and sometimes odd behavior on Lollipop that is display related could be because of a cheap or non-OEM display, we have definitely seen it before. If you are sure this is the original display then this is not the issue.
I would go back to the flashing process and make sure you are doing it correctly... including the factory reset in stock recovery before flashing.
acejavelin said:
Assuming you are flashing correctly, then this is a hardware problem...
Have you ever replaced your display panel? Bootlooping on Marshmallow and sometimes odd behavior on Lollipop that is display related could be because of a cheap or non-OEM display, we have definitely seen it before. If you are sure this is the original display then this is not the issue.
I would go back to the flashing process and make sure you are doing it correctly... including the factory reset in stock recovery before flashing.
Click to expand...
Click to collapse
I have not replaced my panel.I checked my battery health and it shows good.What hardware problem could cause it.Listen i was using cm13 for almost 6 months and i used a sound mod where my earpiece would work as a speaker.One day it stopped working and another day it just started rebooting aftet every 2 minutes.I dunno what happened
Arpan22 said:
I have not replaced my panel.I checked my battery health and it shows good.What hardware problem could cause it.Listen i was using cm13 for almost 6 months and i used a sound mod where my earpiece would work as a speaker.One day it stopped working and another day it just started rebooting aftet every 2 minutes.I dunno what happened
Click to expand...
Click to collapse
If you haven't replaced the display panel and you purchased the device new, then that isn't the problem.
The sound mod probably blew out the speaker or amp/dsp, likely not related to to the rebooting issue but possible.
Does it reboot in safe mode when turning off the screen?
I'll reply here. I am betting a very non clean install and would like to see you wipe advanced: dalvik, data, system, and cache, and flash only rom, gapps, and supersu if you want, but no additions, kernels, themes, mods, apps, fixes, or anything, and test in that state.
My Pixel 3 randomly restarts and gets stuck in long bootloops. The frequency is completely random, ranging from three times a day (rarely) to once a week or two (more common). There is no trigger, sometimes I have it in my hand, doing stuff, and it does that, sometimes it does it when it's sleeping.
The bootloop is always the same.
I see the bootloader message, then th Google logo, and the phone restars after about one second. I never counted to loops but sometimes it must be tens of them. There doesn't seem to be a way to stop them, or at least I am not awaer of any key combinations.
I presume the phone eventually boots into safe mode or something.
I've had it for several months, bought it used in good condition off Ebay, and other than this I never noticed anything off.
This is extremely frustrating and I have no idea what to do.
Does anyone have any idea?
I really hope it never been inside water. Try updating your OS, or change to Custom ROM. If it still occurs, then that's a big problem.
It's most probably an app that's causing this, try disabling/uninstalling some apps that you don't need.
Booting into safe mode is also an option, that way you can make sure if an app is actually causing this.
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
WalrusInAnus said:
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
Click to expand...
Click to collapse
It's highly unlikely for it to be hardware problem, unless you have water/dust/humid damage.
Or maybe your phone heats really fast and therefore some pin inside the motherboard gets shortened due to the heat. But what are the chances of this happening?
But just to be sure, what happens when you connect your device to a charger with output more than 2 amp?
Did you modify your device in anyway whatsoever? Anything the previous owner noted about the device?
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
WalrusInAnus said:
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
Click to expand...
Click to collapse
Yeah, just flash some different ROM on your device and we're good.
Make sure you backup everything through TWRP and that you're flashing your device specific ROM.
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
WalrusInAnus said:
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
Click to expand...
Click to collapse
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
XDHx86 said:
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
Click to expand...
Click to collapse
But I said I flashed the stock ROM before with no luck. You're suggesting I do the same again. That makes very little sense.
What about the Google camera and LOS btw?