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.
Related
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
MarkMRL said:
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
Click to expand...
Click to collapse
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Aronuser said:
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Click to expand...
Click to collapse
My phone is completely stock and I still have these weird reboots. Before I do another factory reset I'm trying to understand if other people have them (and then not bother with a factory reset because that would mean it's a firmware issue) or if I'm the only unlucky one who keeps getting them. Anyway, I was considering getting my phone serviced, I noticed the glass is a bit misaligned and I have a dead pixel, I called the service center and they said both issues are covered by the warranty. Might as well add random reboots to the list, maybe they'll get me a refurbished phone, mine has a few marks on it.
I factory reseted my phone and then sent it in for repairs, most likely got a refurb too since this one looks brand new, and I still have those "system incidents" happening early in the morning when the phone is just resting on my table.
I don't like begging for replies but please if you stumble upon this thread just drop a line saying if you have them or not. At this point I can't be the only one.
Also I'd like to know if there is any way to consult a log or something that would tell me why it happened.
I used to have them on kk, but they stopped. Mine would only happen at work, which led me to believe it was network related somehow... As if a spotty signal was heating up the phone or something. They stopped as randomly as they started.
Sent from my SM-T700 using XDA Premium HD app
I factory reseted my phone again after messing with the concept rom, and guess what, not even one day passes and the piece of crap reboots out of nowhere like always. I'm so mad right now, I only have 3 thirdparty apps installed, poweramp, the app from my mobile data provider and waze. I will start to try and get rid of this phone now, this is absolutely ridiculous.
I have exactly the same problem. Started after installing LP. Had someone found a solution?
Sam
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
robogo1982 said:
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
Click to expand...
Click to collapse
Dude, read the post again. It's happening on stock lollipop with literally no mods installed. I kept the concept rom for 5 days and it was absolutely stable for those 5 days. Stock lollipop reboots at least once every 10 days, but usually twice.
Here's a recap: I had the phone for quite a while now, I don't remember if I had reboots on KitKat, but I definitely have had them for the past 2 months or so. Meanwhile I got my phone refurbished because I had a dead pixel, it was already rebooting when I sent it in, got it back factory reseted and hardware refurbished and the reboots continued once I started installing all my stuff. Now I installed the concept rom to check it out, went back to stock lollipop with a full factory reset via PCC and after a day with pretty much nothing installed I had another reboot. The only thing that was kept during all this time is my 16Gb Class 3 SanDisk SD Card and my WIND (IT) nano sim card. I've decided to buy another SD Card anticipating the Android M memory unification feature, so I bought a Class 10 uhs3 32Gb SD Card from Kingston (which by the way isn't reaching anywhere near the declared speeds of 80/90mb/s, it only reads and writes at around 35 on the phone, I made a thread about it, maybe the phone itself can't read that fast), and I've been using it for a day now. I had no reboots yet but I had some weird app incidents under diagnostics, one from photo analyzer service and one from backup and restore (I hope they happened when I was still messing with the memory card in and out, because I didn't use any of those apps).
Here's a thread I made on the official forum:
https://talk.sonymobile.com/t5/Xper...oubleshoot/m-p/1057964/highlight/false#M26160
By the way, I still don't know if these reboots are rare or if everyone has them. Too few people have commented on whether they have them or not, while this thread has 447 views. If even 10 people commented saying if they had reboots or not I'd be able to rule out glitchy firmware. A friend of mine has the Z3C and he said he has no system incidents and his phone never rebooted.
Still getting soft/stealthy reboots
After doing a complete repair via pcc, I did not put a SD card back in my phone and only installed my google account and apps... No 3rd party apps. It goes for a couple days and then starts doing a reboot usually once every charge and mostly in the morning. The battery usage graph shows a pretty significant gap as if the phone was off but not completely off. Then I find system incidents in the diagnostic app but it only gives me the date and time of when it happens. No other information. Kind of useless if you ask me. This has all started after updating the official LP build . 200 firmware. Sony needs to investigate this became it's happening more and more for people on 5.1.1
I have a locked bootloader, stock kernel, rooted, xposed, dual recovery, tricked out rxz experience ROM with 85 apps (it includes 17-19 xposed add-ons) in addition to 102 system apps, no random reboots at all. I keep an eye on phone diagnostics, system status (temperatures, etc.) like a hawk.
So guys if this happens at you at stock rom , my suggestion is ask the service for replacement maybe.
Sent from my D6603 using Tapatalk
I am currently doing a test after repairing via pcc, installing a new Google acc, only important updates to apps I use that come pre-installed. So far it's been 5 days and no soft boots or incidents in diagnostics. Although it means nothing because usually after about a week or so is when the issues come back after doing a full repair or factory reset. I guess time will tell. Otherwise everything seems to be working great, especially battery life.
Hello great people of XDA,
About one month ago, my digitizer cracked, and I ordered a new screen & digitizer combo from ebay.
Two days ago the replacement arrived and the whole process went smoothly! Everything was working fine, except one thing. The Battery Percentage went crazy. It shows the remainder percentage in thousands.
eg. 3603 % and it always appear full! As soon as i put the phone to charge it appears as "Charged" but thankfully, the battery does indeed charge.
Check the screenshots in the attachments below.
The last screenshot (from the app Battery Stats Plus) says "Charging" but the phone is unplugged. Actually it's pretty obvious that all readings all wrong!
A friend of mine has also a Nexus 5, I tried replacing my battery with his, but the problem remains. Even with a different battery, the readings and percentage are wrong!
It's pretty frustrating. I tried solving one issue, then another came along. Do you have ANY ideas? Oh and one more thing. The "Battery" option from Settings is nowhere to be found!! I have to tap in the battery icon in notification drop-down to enter Battery settings.
Thank you in advance for your time!
Are you running a custom kernel on a stock ROM?
audit13 said:
Are you running a custom kernel on a stock ROM?
Click to expand...
Click to collapse
Hey audit13. Thank you for your reply.
I'm running Stock rooted ROM 6.0.1 (MMB29V) & stock kernel
Hmm, weird that a screen change would cause this. Try the following: (1) clear cache from recovery mode; (2) clear data from recovery mode (this will wipe your data, apps, etc.); or (3) flash a stock ROM without flashing the userdata.img partition or erasing data.
audit13 said:
Hmm, weird that a screen change would cause this. Try the following: (1) clear cache from recovery mode; (2) clear data from recovery mode (this will wipe your data, apps, etc.); or (3) flash a stock ROM without flashing the userdata.img partition or erasing data.
Click to expand...
Click to collapse
I'm afraid that a factory reset/re-flash rom has crossed my mind, but it's something that I do not have time to do right now. I'm pretty sure that it's a software-related issue. Not a hardware one.
I was purely asking for something quick.
Thank you for your suggestion though (and of course your time) If anything else pops in your mind, i'm eager to hear it.
I also think it is software related which is why I suggested flashing a stock rom. If it was hardware related,flashing would not fix the issue.
Gonik said:
I'm afraid that a factory reset/re-flash rom has crossed my mind, but it's something that I do not have time to do right now. I'm pretty sure that it's a software-related issue. Not a hardware one.
I was purely asking for something quick.
Thank you for your suggestion though (and of course your time) If anything else pops in your mind, i'm eager to hear it.
Click to expand...
Click to collapse
It only takes like 60 seconds to flash a stock rom and ten more to log into your google account once its booted and everything it restored for you pretty much. Its the easiest way to fix software issues for the most part.
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?