Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justin
Cry_Cry said:
Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justinhttps://www.youtube.com/watch?v=
Click to expand...
Click to collapse
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately
yldlj said:
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately
Click to expand...
Click to collapse
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?
Cry_Cry said:
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?
Click to expand...
Click to collapse
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.
yldlj said:
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.
Click to expand...
Click to collapse
So basically there is no fix for my problem?
Cry_Cry said:
So basically there is no fix for my problem?
Click to expand...
Click to collapse
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Are you SOFF? What's your CID?
yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?
Cry_Cry said:
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?
Click to expand...
Click to collapse
Nope flash RUU and that's it.
I get a lot of random crashes and power offs since I've upgraded to Oreo. It's really been driving me nuts.
Can't wait for the OP6 or U12+ to come out - I really need a new phone.
Related
I'm on 100% stock. just rooted. the boot times are really long. I got really worried, so I flashed firmware and everything 100% back to stock. But the long booting times are still there. Just to be sure, I tried rebooting even before rooting (in case rooting was the cause :silly: ) but that wasn't the case. And yes, I have fastboot on.
Other than that, there is no anomaly, phone is working 100% fine, no overheating, no battery drain, nothing. I only had the phone for nearly a month before getting the update, so it might be just me not noticing reboots took this long before too?
Anyone else experiencing it?
Not sure if it's the same thing but I seem to have very long boot times now aswell. I was testing a GPE Rom for a while and went back to sense. Booting now takes at least 5 minutes. Just sits at the white HTC bootscreen until screen turns off and then it works fine. Going back to a GPE Rom seems to fix the problem
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Update your firmware and it should work. I have sprint so i was able to find the updated firmware through their forums. I originally thought they were bad flashes, but let it wait one time, it took almost 5 mins to load up. After I updated my firmware to the latest, it worked normally again with fast boot up. On a side note on 4.4.3 roms, I used to think my old bluetooth keyboard didnt work on aosp or gpe roms, and only on sense. Once I updated my rom to a 4.4.3 sense rom, the bluetooth keyboard stopped working on that too. Getting a new bluetooth keyboard today so I will test it out.
duckysempai said:
Not sure if it's the same thing but I seem to have very long boot times now aswell. I was testing a GPE Rom for a while and went back to sense. Booting now takes at least 5 minutes. Just sits at the white HTC bootscreen until screen turns off and then it works fine. Going back to a GPE Rom seems to fix the problem
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same here. I don't think its a problem related to hardware or software. Just, the boot time is longer. Just that. It is a very huge relief to know that someone else is experiencing it too. I've checked everything I can, and there seems to be nothing wrong while it takes long to boot. It doesn't effect the usage at all too. It isn't a bug, just a little annoyance in case you like devices to speedily boot up.
@memekmek Did that too. I flashed firmware, and everything thoroughly checking my procedure. Nothing seems to be broken anyway, I just wanted to check if others have it too or is it me?
Jamal Ahmed said:
I flashed firmware, and everything thoroughly checking my procedure. Nothing seems to be broken anyway, I just wanted to check if others have it too or is it me?
Click to expand...
Click to collapse
How do you flash firmware when you're not S-Off and do you already have latest firmware for your region (vodap something as I read in other thread)
ckpv5 said:
How do you flash firmware when you're not S-Off and do you already have latest firmware for your region (vodap something as I read in other thread)
Click to expand...
Click to collapse
I used the firmware provided by mike1986 in this thread http://forum.xda-developers.com/showthread.php?t=2696282 ... It said that if I have S-ON, I should at least not be able to brick my device...
[I'm actually a 1000% noob in tech, and wrote only what I thought I was doing. I'm sure I must've been wrong. your reply just actually makes sense!]. I didn't want to ask each question on each step, and not bother with my lack of knowledge so I tried to write as much as I understood myself.
I guess it means that my firmware flash was a failure, and that itself is the culprit That clears out a million of my worries.
A little selfish favor to ask of you. Can you kindly direct me to any carrier-specific firmware download place (If there's any!). I'll check it whenever vodap001 firmware comes.
Thanks
Hello everyone I got the nextbit robin the other day, and seem to notice some things. wondering if its normal.
I get the fuzzy snowy screen for a few seconds whenever the device is locked and i go to open it and also when i unlock the screen from twrp. Does anyone have this?
Also I noticed on the latest twrp 3.1.1-0 that the time is off by like nine hours? cant seem to figure how to fix it. other than that i am running the latest aicp and loving the device.
thanks
the_rooter said:
Hello everyone I got the nextbit robin the other day, and seem to notice some things. wondering if its normal.
I get the fuzzy snowy screen for a few seconds whenever the device is locked and i go to open it and also when i unlock the screen from twrp. Does anyone have this?
Also I noticed on the latest twrp 3.1.1-0 that the time is off by like nine hours? cant seem to figure how to fix it. other than that i am running the latest aicp and loving the device.
thanks
Click to expand...
Click to collapse
The twrp thing is normal.
But i dont know about the "fuzzy snowy screen". Was that on stock too or is it just in the custom rom?
Cheers, Jim
the_rooter said:
Hello everyone I got the nextbit robin the other day, and seem to notice some things. wondering if its normal.
I get the fuzzy snowy screen for a few seconds whenever the device is locked and i go to open it and also when i unlock the screen from twrp. Does anyone have this?
Also I noticed on the latest twrp 3.1.1-0 that the time is off by like nine hours? cant seem to figure how to fix it. other than that i am running the latest aicp and loving the device.
thanks
Click to expand...
Click to collapse
jimandroidnerd said:
The twrp thing is normal.
But i dont know about the "fuzzy snowy screen". Was that on stock too or is it just in the custom rom?
Cheers, Jim
Click to expand...
Click to collapse
TWRP has a minor issue with the display showing a rainbow-grainy type screen before showing before it shows what it's supposed to.
Lineage OS (And based ROMS, AICP is based on LOS?, correct me if I'm wrong) have a bug where it shows a similar type of screen (Only black and white [Fuzzy snowy screen]) before returning to normal. This issue is not present on OmniROM, AOSPA and I assume some other ROMS that I have not tested (Including stock, I hated stock ). We can only hope that is fixed in the future.
I wouldn't be worried about the problem/s Hope this helps.
jimandroidnerd said:
The twrp thing is normal.
But i dont know about the "fuzzy snowy screen". Was that on stock too or is it just in the custom rom?
Cheers, Jim
Click to expand...
Click to collapse
DECHTECH said:
TWRP has a minor issue with the display showing a rainbow-grainy type screen before showing before it shows what it's supposed to.
Lineage OS (And based ROMS, AICP is based on LOS?, correct me if I'm wrong) have a bug where it shows a similar type of screen (Only black and white [Fuzzy snowy screen]) before returning to normal. This issue is not present on OmniROM, AOSPA and I assume some other ROMS that I have not tested (Including stock, I hated stock ). We can only hope that is fixed in the future.
I wouldn't be worried about the problem/s Hope this helps.
Click to expand...
Click to collapse
ok that i did notice that i was on AICP and it did that. so to cancel out anything i returned it to stock and then flashed the 7.1.1 update just got giggles, and flash twrp all good. I am going to stay stock for a while.
Now is the time being off in twrp another bug?
the_rooter said:
ok that i did notice that i was on AICP and it did that. so to cancel out anything i returned it to stock and then flashed the 7.1.1 update just got giggles, and flash twrp all good. I am going to stay stock for a while.
Now is the time being off in twrp another bug?
Click to expand...
Click to collapse
I think so but I'm not sure. I think I managed to set it to the correct time at one point but forgot lmao (soz).
Keep an eye out to see if the Robin LOS maintainer has fixed the issue. Once done and LOS based roms update their sources you'll be able to flash AICP again without the bug
Guys I don't know if there's something wrong with my phone or not. Whichever rom or kernel I try, there is an abnormal shut down of my device. Like I'm using it and I leave it for a few minutes or so and it shuts down. I'm not sure if it had something to do with deep sleep or anything, but I need help. Please guys anyone
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
YasuHamed said:
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
Click to expand...
Click to collapse
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
promiscuss said:
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
Click to expand...
Click to collapse
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
YasuHamed said:
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
Click to expand...
Click to collapse
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
promiscuss said:
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
Click to expand...
Click to collapse
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
promiscuss said:
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
Click to expand...
Click to collapse
sir, which custom ROM + kernel + anrdoid version are you on ?
YasuHamed said:
sir, which custom ROM + kernel + anrdoid version are you on ?
Click to expand...
Click to collapse
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
promiscuss said:
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
Click to expand...
Click to collapse
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
YasuHamed said:
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
Click to expand...
Click to collapse
Thanks for all your effort, the problem seems to have resolved on its own. I'm not sure what it was.
now it's happening to me but it's much more severe. First it started slowly now it's so frequent that the phone might shut down even on boot. This is really frustrating.
I had the same problem with my redmi note 7, flashed stock rom with MI flash tool, fixed everything for me
I'm wondering if it's a good idea to do a factory reset/clean install of the official firmware when Pie is released.
I would think it would help prevent issues as it's a full version difference.
1031982 said:
I'm wondering if it's a good idea to do a factory reset/clean install of the official firmware when Pie is released.
I would think it would help prevent issues as it's a full version difference.
Click to expand...
Click to collapse
For Oreo from Nougat (May 2018), I did Upgrade via LGUP.
But it never hurts to do a clean install.
I'll probably have to edit the WTF INSTRUCTIONS after that to include Pie KDZ...
Sent via open market LG US998 V30/V30+
Ok. I know rumors put the pie release outside the US this or next month, I'm trying to decide on what way to go.
This way I have time to prep.
1031982 said:
I'm wondering if it's a good idea to do a factory reset/clean install of the official firmware when Pie is released.
I would think it would help prevent issues as it's a full version difference.
Click to expand...
Click to collapse
Yeah. Factory resseting is generally a good for major android updates.
PS: Next time please post in appropriate thread. This is the development thread and a question shouldn't be posted here.
tech_infinity said:
Yeah. Factory resseting is generally a good for major android updates.
PS: Next time please post in appropriate thread. This is the development thread and a question shouldn't be posted here.
Click to expand...
Click to collapse
Sorry I must have been in development instead of Q&A. If a mod wants to move it, that would be appreciated.
1031982 said:
Sorry I must have been in development instead of Q&A. If a mod wants to move it, that would be appreciated.
Click to expand...
Click to collapse
No problem
I think pie is very far for us right now. Maybe just upgrade to pie when it comes and reset if you've any issues.
tech_infinity said:
No problem
I think pie is very far for us right now. Maybe just upgrade to pie when it comes and reset if you've any issues.
Click to expand...
Click to collapse
Well, AT&T just got Pie on the V35, so I can't imagination we are too far behind.
Funny thing is, I already have a couple issues. Nothing serious, but they are annoying.
1. Do not disturb does not abide by it's set schedule. It will turn off, but not turn on without me either restarting my phone, or manually turning it on.
2. (May not be a bug, but I haven't found anything about it so eh...) Every so often, pressing the volume buttons causes it to jump by 5 points instead of one. This is from both on the phone, and using the headphones that came with it that have volume buttons.
There are times I press volume up and it starts blaring, so I quickly turn it back down and use the screen to change the volume until I reboot my phone to correct it. I have verified that I am not double pressing or holding the volume button.
They both started when I upgraded to US998 20H. To be clear, I used the following KDZ images to upgrade in order : A, E, F, G, and finally H.
Instead of wiping my phone now, I figured that I would just wait until Pie is out for little bit and then so a clean install. Hopefully it will fix those issues, and prevent any others from arising for that update.
i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone
musatbz said:
i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone
Click to expand...
Click to collapse
uh oh.. i didnt notice that. I switched to crdroid 9.2 immidiately after installing the update. i'll extract system.img from the firmware and see if it is an actual issue here too. i faced it on one ui 4.1 before. Otherwise since downgrade isnt an option, consider switching to a gsi?
Captain_cookie_200 said:
uh oh.. i didnt notice that. I switched to crdroid 9.2 immidiately after installing the update. i'll extract system.img from the firmware and see if it is an actual issue here too. i faced it on one ui 4.1 before. Otherwise since downgrade isnt an option, consider switching to a gsi?
Click to expand...
Click to collapse
just flashed one ui with dsu. tried speedtest on data 4 times. seemed fine. try a fw reflash maybe?
Captain_cookie_200 said:
just flashed one ui with dsu. tried speedtest on data 4 times. seemed fine. try a fw reflash maybe?
Click to expand...
Click to collapse
yeah actually maybe it was because i upgraded from android 12 but im not sure
musatbz said:
i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone
Click to expand...
Click to collapse
just make a full wipe and done, but make a full backup first
musatbz said:
yeah actually maybe it was because i upgraded from android 12 but im not sure
Click to expand...
Click to collapse
try a fw reflash and lmk how it goes
im wiping rn