Related
Hi,
sometimes the touchscreen of my defy stops working (but the phone is not frozen)
and the only way to fix it is to lock/unlock the screen...
does anyone have the same problem (and can help me)?
thanks
P.S
i've had the problem both with stock rom (2.2) and with cyanogenmod rc 1.5
When this happens, do the 4 buttons below your display still give you haptic feedback (little vibration) or do they react not at all?
Also, does this only happen when there's the normal launcher/standby screen active or when there's an other app active too ?
Did you undervolt ?
Edit: Also, this seems to be a hardware problem which seems to be well known in a certain German android forum but I cannot find much about it in here. In short, the digitizer unit seems to be broken for some people and locking/unlocking helps because it disconnects and connects power for the digitizer. The people there fixed the problem by replacing the digitizer (which isn't easy at all!).
It would be nice to have someone from XDA who had this problem before too, to confirm this problem!
First of all, thank you for the answer
When I have the problem, 4 buttons stop working too.
It usually happens after a period of stand-by, i don't undervolt or have some other application running than the launcher (ADWlauncher).
I bought the phone one week ago, if it is an HW problem, i can't repair it by myself...
I'd recommend to wait and see whether xda has other suggestions for you and if not, just check the Motorola hotline and ask whether they know something and if they do change it for free.
Also, what you describe fits perfectly to what I've read elsewhere (don't know whether I'm allowed to post a link here or if it were useful at all because it is in German). So it sounds like your digitizer could really be defect.
ok, even if i hope to solve the problem by myself...
News: They've changed the touch screen, but the problem is still present...
Can it be a sw problem??
Keep sending it back, they will replace it in the end.
Sent from my MB525 using Tapatalk
the whole phone?
Yes, the whole phone. They have two year warranties, but don't put up or make do, you should have a phone that works right
Sent from my MB525 using Tapatalk
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
I wonder when it happens ,are you charging?
nameite said:
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
Click to expand...
Click to collapse
What nightly version are you using?
The problem happens even if i'm not charging...
What's up guys, i'm new here . Three days ago, HTC sent back my phone after a checkup for a vibration problem. They said that they did a software update (false, it was already 1.29.401.11) and sensors calibration. Yesterday, the phone stopped vibrating again. What should i do now? I think that is a software problem (stock rom, never rooted). I'm sorry for bad english . Thanks
TidyGnu said:
What's up guys, i'm new here . Three days ago, HTC sent back my phone after a checkup for a vibration problem. They said that they did a software update (false, it was already 1.29.401.11) and sensors calibration. Yesterday, the phone stopped vibrating again. What should i do now? I think that is a software problem (stock rom, never rooted). I'm sorry for bad english . Thanks
Click to expand...
Click to collapse
Don't think you can do anything much other than give it back and ask for a replacement as it's the second time this has happened... Also, try doing a factory restore and see if it works.
Sent from my HTC One X using xda app-developers app
Asheel said:
Don't think you can do anything much other than give it back and ask for a replacement as it's the second time this has happened... Also, try doing a factory restore and see if it works.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I dit it, but this should be the third time that i send it to assistance. The first one was for a g sensor problem, resolved with a replacement of motherboard, but when i sent it the vibration worked perfectly, i suspect that they broken my phone.
TidyGnu said:
I dit it, but this should be the third time that i send it to assistance. The first one was for a g sensor problem, resolved with a replacement of motherboard, but when i sent it the vibration worked perfectly, i suspect that they broken my phone.
Click to expand...
Click to collapse
That's bad luck...I hope they are giving you a replacement instead of just fixing it...
Sent from my HTC One X using xda app-developers app
mine keeps vibrating every 30 min or so
i cant figure out what's causing it any suggestions what it would be ?
not a incoming email vibration notification , not a wi-fi drop out vibration notification.
TidyGnu said:
What's up guys, i'm new here . Three days ago, HTC sent back my phone after a checkup for a vibration problem. They said that they did a software update (false, it was already 1.29.401.11) and sensors calibration. Yesterday, the phone stopped vibrating again. What should i do now? I think that is a software problem (stock rom, never rooted). I'm sorry for bad english . Thanks
Click to expand...
Click to collapse
They actually scammed you by saying they updated it(when it was updated already like you say) You should go back, yell at them and take out some frustration if you wish =P
Don't root your phone to install another rom, try fixing it as is on stock rom.
I would try these:
1)Factory Reset
2)Update to latest FW
3)HTC Diagnostics Test (Has a vibration test)
4)Haptic Feedback On(To see if it vibrates on typing and tapping and such)
5)Phone Ringing with vibration
If any of the above work, then its definitely a software problem.
If they don't, either way you have to go back to HTC. Try getting a replacement. Say you're tired of coming back again and again to get your phone fixed, "Give me a replacement or My Money back"
I read another post a few weeks back where the user was experiencing these mechanical sounds on haptic feedback(I also have that problem) but his vibration stopped altogether. He got his HOX replaced.
Anyways Good Luck.
ICO187 said:
mine keeps vibrating every 30 min or so
i cant figure out what's causing it any suggestions what it would be ?
not a incoming email vibration notification , not a wi-fi drop out vibration notification.
Click to expand...
Click to collapse
I don't recommend hijacking the thread, create your own thread
Sorry I'm probably stepping on his thread too, but please point in any directtion before I have an inoperable phone and a hard time getting HTC to cover.
However, I an issue that will f-up this phone I'm afraid. I have on a daily basis what I would describe as an alarm of some sorts (can't duplicate) that runs about 15 seconds once to twice daily at full vibration. Not rooted and have reset 3 times.
If you've ever run a battery drain program with full vibration on. Not good for the phone. I'm at a loss in this one, really dreading tech support or my local store. Will run the HTC diags but any other ideas greatly appreciated
No receipt, no box and I traded for it on Craig'slist 2weeks ago..
Sent from my HTC One X using Tapatalk 2
My friend had the same problem with a HOX - it wouldn't vibrate at all. He tried doing a factory reset and playing with settings, but nothing worked, so he sent it back and got a replacement. I'm not sure you can do anything about it since it's likely a hardware problem.
Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
abubakr125 said:
Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No ideas other than to suggest that you do an RMA with ASUS. I just looked and I pre-ordered mine through Best Buy and it shipped July 26 of last year so you might still have time left on the one year warranty.
Hey, I hope this topic is still alive. Mine has exactly same issue as yours. It all started after I re- clean flashed Mahdi ROM (I messed up some stuff so I had to do it). Ive tried clean flash again, but it doesn't work. I've also tried different settings and apps but nothing helped. The only thing I found working is turning on lockscreen blur. For some reason, it makes the rotation work for a bit longer.
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!??
Hi All,
So I've just bought this TV and I've done all the updates I can, and even checked the website for any manual updates. I've done at least 3 full resets too.
As the title says, I'm getting random crashes or reboots - even when it's just sat on a menu screen doing nothing. Streaming anything such as Netflix seems to exacerbate the issue. I'm very lucky if I can even watch a single 40 min TV episode without it rebooting.
Any ideas? Has anybody else had this? Philips are being useless at the moment and simply referred me back to some instructions for 2014 Android TV's despite this one being a 2019 model, and then closed the support ticket before I could even reply.
Cheers,
James
Do you have any firmware updates?
Have you done any firmware updates on your TV?
Also did u check any auto-shut down feature?
Hello,
Thanks for the reply. As I stated I've done all updates already and also checked the website for any manual updates.
The TV isn't shutting down, it's rebooting randomly during viewing, and crashing when doing nothing requiring me to pull the plug to get it working again.
Any other suggestions?
james2k2 said:
Hello,
Thanks for the reply. As I stated I've done all updates already and also checked the website for any manual updates.
The TV isn't shutting down, it's rebooting randomly during viewing, and crashing when doing nothing requiring me to pull the plug to get it working again.
Any other suggestions?
Click to expand...
Click to collapse
Do you have any HDMIs, SATALLITES connected to your TV?
Please remove them and maybe re-installing the latest firmware would help
https://toengel.net/philipsblog/firmware-download/
Also,
http://philips-tvconsumercare.kxondemand.com/Portal/en/Faq/All/6595
Hello, my apologies I didn't see the notification for reply.
I've tried leaving it disconnected but unfortunately the issue still occurs. I will look at reinstalling the firmware.
Thanks for your help so far.
Hi all again,
I just wanted to provide a small update. So I think I've worked out that it's the remote causing the crashing. Which in turn suggests a Bluetooth issue. It isn't consistent, so I'm now monitoring but it seems when the remote gets moved and goes to reconnect it then crashes and reboots. I'll post another update if my findings seem true.
on my Phillips the Isuue came from firetvstick4k.
If i changed Always HDR i have massive problems with lag in UI of my Phillips 65PSU7310.
If i changed it in Firetv to Adaptive...all Lag was gone from my Phillips TV
https://www.4kfilme.de/wp-content/uploads/2018/12/Amazon-Fire-TV-Adaptives-HDR.jpg
Also AptoideTV app has given me much Bootloops.
After deinstalled AptoideTV and Gave Firetvstick only Adaptive HDR.All Problems has gone.no bootloop and no Lags anymore.
Perhaps it helps you !
greatz
I habe the Same Problems and Philip’s Support think That i am stupid“did. you try a firmware Update?“ and some other things like That. The Problem is since the Last Auto Update 6-8weeks ago most it happens After 1hour streaming youtube. First reboots android,than nothing Happens After That Philip’s bootlogo and then android Boot apears again all Bye its own.
TV.: 65PUS8602
Gesendet von iPhone mit Tapatalk
Hi,
when you are in a bootloop, try the upgrade_loader for your TV... see my blog - firmware archive + instructions
[email protected]
No Not in bootloop.
And your downgrade discription does Not work on my TV.
Gesendet von iPhone mit Tapatalk
james2k2 said:
Hi all again,
I just wanted to provide a small update. So I think I've worked out that it's the remote causing the crashing. Which in turn suggests a Bluetooth issue. It isn't consistent, so I'm now monitoring but it seems when the remote gets moved and goes to reconnect it then crashes and reboots. I'll post another update if my findings seem true.
Click to expand...
Click to collapse
Hi James2k2,
I know this post is a bit old but I have a Philips OLED with exactly the same random reboot as you get.
You just said it was maybe a Bluetooth issue, can you tell me if you could confirm that? and how did you resolve this please?
Thanks a lot
drgonzo69 said:
Hi James2k2,
I know this post is a bit old but I have a Philips OLED with exactly the same random reboot as you get.
You just said it was maybe a Bluetooth issue, can you tell me if you could confirm that? and how did you resolve this please?
Thanks a lot
Click to expand...
Click to collapse
Hey drgonzo69,
Unfortunately I never got the issue resolved. Philips support just asked me to reinstall the firmware, which I did and I still had the problem. In the end the supplier accepted it back and I bought an LG TV instead (should have gone with my gut and done this in the first place instead of trying to save some money).
james2k2 said:
Hey drgonzo69,
Unfortunately I never got the issue resolved. Philips support just asked me to reinstall the firmware, which I did and I still had the problem. In the end the supplier accepted it back and I bought an LG TV instead (should have gone with my gut and done this in the first place instead of trying to save some money).
Click to expand...
Click to collapse
Hi James2k2,
Thanks for your answer.
Unfortunately warranty is expired and I can't give the tv back... I'm just going to wait for new firmwares hoping that system will be eventually more stable.
drgonzo69 said:
Hi James2k2,
Thanks for your answer.
Unfortunately warranty is expired and I can't give the tv back... I'm just going to wait for new firmwares hoping that system will be eventually more stable.
Click to expand...
Click to collapse
Ah that's a shame! I have to say, for the money the display itself wasn't bad at all. Hopefully a fix will come out.