I've had my HOX for about 4 months now, working like a charm, and doing what they say its supposed to do.. Now however, it has changed to an unusable brick..
I Rooted my phone about a month ago, and ran with a near stock ROM (I can't really remember what it is anymore), and about a week ago, I upgraded to the latest patches. The phone now has its own life, where it seemes like picture it tries to show, is distorted, unreadable, sometimes one of the three primary colors goes missing and it looks like it refreshes a small portion of the screen every second. The touch system still works fine, and if I could work it blind, it wouldnt be a problem.. I can get to recovery/fastboot without any problem, and if I reboot the phone, it works like it should from 10 seconds-1 hour. I've tried to restore to defaults, tried the Viper ROM, but nothing seemes to work. Also, if I lock the phone while it is doing the bug, I get the "dark screen" bug as well..
I suspect it must have something to do with the update, since the phone have been handled with great care, and not dropped on the floor/pressed hard on the screen. I'm now turning to you guys, since you know pretty much about this phone. I can take a picture with another phone to illustrate what its doing, if that helps, or my explenation is a bit vague.
so you actually tried to get the phone right back to stock? flashing a RUU?
matt95 said:
so you actually tried to get the phone right back to stock? flashing a RUU?
Click to expand...
Click to collapse
Yes, I tried that as well, but it didn't work as far as I could tell. It would last longer before it started to bug out, but it would happen still..
hmmm, well it could also be a HW issue...
matt95 said:
hmmm, well it could also be a HW issue...
Click to expand...
Click to collapse
It might be, but it would be so strange that it first came right after an update.. Might be some overheating that have caused bad connectivity on a lead, can be some plug that isnt right, but I have a sneaking suspicion that the update did this..
well if even the RUU didn't solve this then it could only be HW related... just one question, how could you run a RUU if there ins' any RUU for the latest update yet?
Hi all,
Having a strange issue with the accelerometer on my 2013 Nexus 7, wondering if anyone has experienced this.
I must admit I need to do one further test which is return to stock but I'm skeptical it'll make a difference.
Whilst running a custom ROM the accelerometer just cut out of its own accord. I assumed it was a software issue so I did a clean flash of the same ROM. It was working fine again. Great. Except a few hours later all of a sudden it stopped again.
I've since flashed another 2 entirely separate ROMs cleanly and the exact same thing has happened every time.
Can't think what it could be, I assumed it was software seeing as it works briefly but now I'm not sure at all. Will try stock as soon as I can but thought I'd ask while I wait until I have a chance.
Hi there,
Apologies if this may be a bit of a superficial post but the phone in Q isn't mine so I'm working on second-hand info here. A friend of mine got a G3 off ebay that's t-mobile branded and is supposedly the European model, I haven't checked. (She's using it in the UK nonetheless). Also it has "the latest software updates" (whatever those may be) installed. The phone is not rooted or otherwise tampered with.
Her problem is that occasionally, the phone restarts apparently randomly, though she noted that this happened more when she was in the countryside and the internet connection was coming and going. My guess is that this may have to do with the modem, but not sure. She did some googling and apparently the problem is relatively common but there's no good solution to it.
My two (three) questions are:
- has anyone else encountered this issue?
- any solution to the problem?
- is this a stock firmware issue, ie would installing CMod solve the problem or is this a hardware problem?
Thnx
If it's second-hand phone it's battery issue.
Rushing toward CMod isn't going to solve your problem.
I am also facing the same issue. This also occurs when I'm at my village home. Mostly happens at the same place.
So instead of installing CMod try to change battery because stock Rom is also best and therefore any problem in it means problem in hardware not in software.
But you can still try different techniques. Also tell me if you can solve it.
Installing CM brought no solution for me and still faced random reboots.
i have faced this problem, adter everything i tried then i decided it is battery issue.
i mean change your battery
imamalemdar said:
i have faced this problem, adter everything i tried then i decided it is battery issue.
i mean change your battery
Click to expand...
Click to collapse
Did it work? (Changing the battery...did it resolve the problems?)
wyco said:
Did it work? (Changing the battery...did it resolve the problems?)
Click to expand...
Click to collapse
of course it works now like a rock
I've been having the same issue. My I've used a new battery but my phone acts the same as it did before. Reboots randomly after the wifi, bluetooth, and 3g crash and attempts to recover. The reboot never succeeds and I have to physically pull the battery. Currently using the latest nightly of CM13.
I have had the same issue. I have a stock ROM, fully updated TMobile G3 phone and when i would go to europe, the phone would randomly crash. When it was in airplane mode it would not crash, so i kept it in airplane mode unless i needed to call and i used the wifi calling feature. I thought it was the battery but i have the stock battery and an anker battery and i have never had this problem in the US, it only happened abroad.
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?
Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.
Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.
Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals
Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz
Mail me i have that file..
[email protected]
There is issue while sending here
Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude
Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??
Checked around the internet and this problem seemed to be quite common.
WiFi could not be switched on. See the YouTube link below at 1:20mins.
Question: has anybody tried to Odin reflash it to the same/latest firmware. No rooting or anything fancy, just reflash the same firmware.
I had this issue after updating to the latest firmware but I don’t think the issue happened right after updating. Probably a few days later. I was hoping if this could fix the issue.
Thanks.
Update.
I tried it myself via Odin updates to the latest/same firmware for my region.
Problem not fixed. Same thing. WiFi still doesn't turn on.
Same situation here. Wifi not turning on.
it was working while phone was in folded mode.
As soon as open, wifi won't work. Then phone goes to restarting.
Did factory reset and no help.
Came here hoping to reflash old stock firmware to see if it will work, but you have answered above.
I read on some of forum and one guy sent in to Samsung and they changed screen and it is working like a new one.
Maybe some to do with wifi antenna built in to the screen or something?!
Coincidentally I have the person installed a new screen protection and that person didn't know well and rubbed hell out of screen. That was about a few days before my wifi went out.
????
What do you think? Maybe relate it, or not?
P.S. I have less hair on my head now and not cause of being old (66).
99% is software related.
anybody has installed oneui 5.1 and still facing this issue?
i bet no coz sammy is aware of this problem and pushed the fix with latest build.
AndrOmega said:
99% is software related.
anybody has installed oneui 5.1 and still facing this issue?
i bet no coz sammy is aware of this problem and pushed the fix with latest build.
Click to expand...
Click to collapse
updated today to 5.1 and I got the same issue. looking at the history of this problem it seems to me that samsung are not aware of it because after almost a month they still released the 5.1 firmware.
Do the Android said:
it was working while phone was in folded mode.
As soon as open, wifi won't work. Then phone goes to restarting.
Click to expand...
Click to collapse
This looks like a hardware problem to me. Something inside is disturbing the WiFi radio when you unfold the phone.