I recently posted a thread on here about how my HD2's accelorometor no longer worked under android after being repaired. My thread was moved however but that is not the point the point is that after searching for several hours I have found a few threads about this problem and it seems that I am not alone!
My Thread: http://forum.xda-developers.com/showthread.php?t=1094479
Other thread: http://forum.xda-developers.com/showthread.php?t=999597
There are more but the one below mine seemed to be the best. It seems that this is a development issue so hopefully this thread will not be moved as my other one was as I've now done the research which I needed to comfirm this. It seems that a lot of warrenty repaired HD2's have this problem so as this is most likely a driver issue I would like to ask any dev that can to possibly look into the WM and or WP7 accelorometor drivers and see if there is any code for a second sensor and maybe if there is someone could look into incorporating it into our current android driver for future kernels. I am not a dev my self really, not in linux or android anyway. However I can provide logcats etc if needed.
As I said before please do not move this thread as devs do not go to Q&A and this is now a dev issue I think.
Any info or progress devs can give I will do my best to update the first post to help others.
I have just done an adb logcat from clean boot, to unlock then opening the bubble app and moving the device around for about 1 min and no change in app. It is attached below.
I have also done an adb dmesg which is also attached.
I hope someone can help all with this problem and thanks in advance to any devs which help.
Update 1: It seems that there is more than just the G-sensor which is different on these HD2's it also seems the light sensor and GPS are different!
Update 2: After trying the oldest 1.48 ROM for the HD2 it seems that HTC had planned the changes as all the hardware seems to work (minus the compass) in that ROM also with old SPL and Radio. Which I guess means that these other drivers must have been overlooked in the porting process...
Update 3: On trying it for myself it just seems that a GPS lock takes a really long time compared to other HD2's but it seems the GPS works. G-sensor still seems the most important thing to fix as many apps rely on it.
not denying the existance of the problem, but i would have thought that it was a damaged sensor (i have heard stories about hd2 accelerometers breaking for no good reason [probably a hardware defect]). There are only 2 hardware models arent there? International and TMOUS. I also thought that each model set used the same hardware across each model (ie no sort of Leo rev.2 with improved or different internals.
Of course i am probably wrong though
1 more thing. I had a Sony PSP repaired (a failed update so it bricked). They repaired it and when i got it back the UMD drive didnt work. So just to say that just becasue it cam back from a repair center doesnt mean they didnt break something else (although i expect htc take more care than sony)
joshman99 said:
not denying the existance of the problem, but i would have thought that it was a damaged sensor (i have heard stories about hd2 accelerometers breaking for no good reason [probably a hardware defect]). There are only 2 hardware models arent there? International and TMOUS. I also thought that each model set used the same hardware across each model (ie no sort of Leo rev.2 with improved or different internals.
Of course i am probably wrong though
1 more thing. I had a Sony PSP repaired (a failed update so it bricked). They repaired it and when i got it back the UMD drive didnt work. So just to say that just becasue it cam back from a repair center doesnt mean they didnt break something else (although i expect htc take more care than sony)
Click to expand...
Click to collapse
Well the sccelorometor works in Windows Mobile and Windows Phone 7 so I doubt it's a hardware issue. It's all in the links above... But thanks anyway.
Hello
I don't know if is about service. I bought my HD2 from Vodafone (brand new) and I can't use G-sensor and proximity sensor in Android. And I tried more then 20 versions (SD or NAND). In windows 6.1, 6.5, and 7, everything is perfect; in Android it's not working ... If you have a solution, please tell me ... G-sensor is not so important, but proximity sensor is ... Especially when I need two hands on keyboard ...
I also risk myself to ask them about this issue. The answer was: "if you already tried that, you lost your warranty ..." Point. Yeah, sure ...
ctzctz said:
Hello
I don't know if is about service. I bought my HD2 from Vodafone (brand new) and I can't use G-sensor and proximity sensor in Android. And I tried more then 20 versions (SD or NAND). In windows 6.1, 6.5, and 7, everything is perfect; in Android it's not working ... If you have a solution, please tell me ... G-sensor is not so important, but proximity sensor is ... Especially when I need two hands on keyboard ...
I also risk myself to ask them about this issue. The answer was: "if you already tried that, you lost your warranty ..." Point. Yeah, sure ...
Click to expand...
Click to collapse
I think u mean g-sensor for rotating the keyboard... but anyway regardless of what HTC has to say... which will never be good... this really needs to be looked into by someone familier with WinCE like cotulla was, as he was the one that reverse engineered these drivers in the first place but maybe he might have not reverse engineered the drivers for the different g-sensor and prox sensors possibly disgarding them as junk, as HTC as far as I know did used to leave drivers for other devices in builds. Or maybe when the prox and g-sensor drivers were being fixed later down the line the code was streamlined by removing them. Whatever the cause though or at whatever point they were lost at, they have been lost and we therefore need, with dev help, to look at the wince drivers again so maybe this can be fixed.
Hope this helps.
P.S. If anyone still has access to cotulla's early kernels, and early builds, pre-git merge with g-sensor support please post them so we can try them on effected HD2's. Thanks.
this is definitely kernel/driver issue. i am stucked at this problem for a while now. and no dev is trying to help. please someone do something. i bought hd2 just to enjoy different roms of android.
I don't think this is limited to the accelerometer. Before I received my replacement HD2, GPS worked fine, even in gingerbread I could get a fix. Now my replacement phone doesn't pick up or takes forever to see satellites. I Haven't tried it in WM but I suspect different hardware.
mr_dilly said:
I don't think this is limited to the accelerometer. Before I received my replacement HD2, GPS worked fine, even in gingerbread I could get a fix. Now my replacement phone doesn't pick up or takes forever to see satellites. I Haven't tried it in WM but I suspect different hardware.
Click to expand...
Click to collapse
I have noticed also that the light sensor doesn't work in WP7 and I think it was also the same in android! I don't really use gps but I might try it to test. Btw what are you running on your HD2? You should try running older WM ROM's on your phone and see if things work. Because if they don't maybe would could convince HTC to replace our phones... Although they've likely included the new drivers in the 3.xx ROM's so that wouldn't really fix anything. However with dev help we really need to look into the drivers in WinMo and see what the new hardware is. After all if HTC has changed hardware due to it being more available maybe the new hardware is also present in some of their android devices... And if this is the case then it would be pretty easy to fix although this is just speculation but without some help I can't really make it more.
Also does anyone know of any app which can list what hardware is in a Windows Mobile device? If there were this would really be useful.
Thanks.
I spent the day flashing some roms and radios, and got different results. In WM, I do pick up satellites a little faster, this improved with an older radio 2.12. In android I eventually saw satellites, again this improved with radio 2.12. I tested against another HD2 both running Hyperdroid CM7 2.0.1; the signal was a lot weaker and I picked up fewer satellites total. This may be due to different/older hardware I'm not sure.
There was an app in the market which told you what hardware your phone was running but I can't remember the name of the app or if it said what version. I hope this info helps.
http://forum.xda-developers.com/showthread.php?t=1049170
looks like the devs are already in the works of fixing the g-sensor missing drivers/code
and will most likely be implemented in next builds/kernels...
btw i lost my hd2 recently.. a brand new one was sent to me thru the insurance company.. after installing an android nand rom i notice the screen auto-rotation wasnt working.. fashed WP7 and everything was fine.. so yea its for sure a driver related issue all we can do is wait for all these great devs to cook a new kernel with a fix...
With Phone Tester (by Miguel Torres) you can get good info about sensors and etc.
Also Phone Explorer (by Dave Truby)
Sorry this is not spam to advertise app. Just wanted itself know have difference on hardware on my two phones.
I have old and many many times asked and short or longer discussed light and proximity sensor problem. With last two roms, it started work little better. But lighting phone with some sharp light after call is very displeasing.
datas0ft said:
With Phone Tester (by Miguel Torres) you can get good info about sensors and etc.
Also Phone Explorer (by Dave Truby)
Sorry this is not spam to advertise app. Just wanted itself know have difference on hardware on my two phones.
I have old and many many times asked and short or longer discussed light and proximity sensor problem. With last two roms, it started work little better. But lighting phone with some sharp light after call is very displeasing.
Click to expand...
Click to collapse
Hi, all help is good I guess. Anyway are these WinMo or Android apps? Since if their Android due to the kernel problem it may give false reports but either way I'm interested in whether the results you got are different on the two HD2's?
P.S. I hope some kernel devs can help me with this soon as I haven't heard from any yet but wish to.
Me too. G sensor works only in WM, and in Android It doesn't work.
nhoc_tron36 said:
Me too. G sensor works only in WM, and in Android It doesn't work.
Click to expand...
Click to collapse
The drivers are written for and debugged using the hardware present in the device of the developer. ie. Cotulla prioritized the LEO100 a.k.a EU HD2 as he dint have the TMOUS version.
Well this is a leading problem in linux support, the drivers are available only for hardware which is used/produced/supported by good devs.
The only thing you could do here is check with kernel and android logs what happens when those specific hardware are switched on and/or accessed.
Google is your best friend. who knows you might just become jr.Cotulla trying to fix your Hardware problem.
Well, i started by fixing my Harddisk's MBR back in 1995 (god, those ol days. cant forget DOS, and 512MB HDD) and today im a Microsoft MVP
I get this issue too...
I have Euro HD2 on android... with WM everything was... hum I can't say "fine" ^^ but it was working anyway!
Yes, these two previously named apps are android. On winmo i dont had problems with proximity sensor. I didnt changed anything and moved to android. Then started these proximity sensor problems. And now i can assuredly say that it is proximity sensor side problem. Phone tester shows all time status "Near". When i give more light to phone then it shows "Far".
I ordered new flex cable ribbon which one have proximity and light sensor. It arrives at week or more. Then i can assuredly say is it broken proximity sensor or drivers (kernel) side problem. I opened my phone many times and cleaned sensor too, that some dust cant be problem.
Proximity sensor info:
Name: CM3602 Proximity sensor
Vendor: Capella Microsystems
Version: 1
Power: 0.5
Resolution: 9.0
Max Range: 9.0
Centimeters: 0
If someone needs or want some other info or test i can give or do it.
any update to this as I am experiencing the same problem on one of my HD2s. I realize its an old thread but maybe someone has results.
Devs help needed!
Still hope devs will see this
Related
Hi all,
I recently received a replacement Desire for my 'faulty' one. I tested all basic functions before walking away and everything checked out.
After I rooted it and installed Modaco r17 ROM, My proximity sensor sensitivity dropped dramatically. When I make or receive a call, the screen blanks as it should, but when I move the phone away from my face, it stays blank. I can't end the call or use speakerphone or keypad. The only way to bring the screen back is to hold it under a very bright indoor light, or direct sunlight...or pull the battery, of course.
I loaded a sensor test tool (SensorList) and it confirms that the sensor is reacting only to very bright light. I've checked that my cover doesn't obscure the sensor and tested that the behavior is the same with or without the screen protector.
I tried a couple of other ROMs, Modaco r19 and Shadowfrost v13. I un-rooted my phone and dropped a stock HTC ROM back onto it...and the problem is still there!
I'm waiting on a reply from HTC service about it...but in the meantime...any advice? I've seen a few posts around the web with this problem, but no definitive solutions or answers.
Question Added to Developers
I've noticed a smattering of people in various forums, with various of the newer android phones having proximity sensor problems. Perhaps these are not quite as finely calibrated as the other sensors, or not as reliable. Have any of you developers seen a way calibrating or adjusting the sensitivity? Perhaps a value in a system file we can change?
Thanks in advance.
Added question and bumped
Apols if this is pushy. I added a question to you developers, so giving this a bump.
phantomfisho said:
Apols if this is pushy. I added a question to you developers, so giving this a bump.
Click to expand...
Click to collapse
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Daelyn said:
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Click to expand...
Click to collapse
Images:
1. Holding hand over phone screen
2. Clear view of the screen in dimly lit room (it's quite cloudy )
3. While running FroYo
This does seem like Sensor List correctly detects and measures the proximity/light sensors in FroYo on an HTC Desire, or am I mistaken?
Ditto Issue
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
nayajoeun said:
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
Click to expand...
Click to collapse
Thanks John. I tried the same thing with the same result.
I ended up taking it in to HTC. Luckily I came across a good service rep. He said they'd seen some quality problems with the first batches of Desires and mine was not the first faulty proximity sensor they'd seen. My guess is the timing with the rooting was coincidental.
They would have replaced it, but they didn't have any replacement stock at the time...more evidence of early quality issues. They gave me priority and repaired it in 24 hours. It's been running fine under a number of ROMs since.
BTW I had problems de-rooting and reloading the stock ROM. Then I realised I just had to have the original goldcard in the phone and presto! One day I'll learn to RTFM properly.
Cheers mate and good luck with yours.
I have also this problem. When I make a phone call screen goes black immediately and there's nothing you can do. After the call is over I can wake up screen by pressing power button. I'm not sure when it started because there's been so many variables. I even destroyed my invisibleshield thinking it caused the problem.
Sensor list and sensor dump says that max value for proximity sensor is 1. Screenshots above there was at least 9. Also light sensor doesn't work at all.
I tried to unroot and go back stock but the problem still exist.
Have anybody found a way to control these sensors or do I have to send my phone to HTC to get it repaired?
Thanks in advance!
Hi, I have the same problem here with my proximity sensor since I have used a custom ROM (I don't remember wich one because I have tried so many Froyo ROM before the OTA).
I can't send my desire to HTC because my phone is out of waranty since I have installed all these ROMs.
Does anybody's got an idea, some help from devs ?
OK,
Maybe I'have found a solution to the proximity sensor's problem... At least my proximity sensor is working normaly now.
What I have done (you can found all in the xda posts) :
1. Going back to Hboot 0.80 => forum.xda-developers.com/showthread.php?t=741672
2. Rooting the desire and install the new recovery using unrevoked
3. Installing the OTA 2.2 without the Radio 5.09 (not a leedroid or djdroid or any other ROM, just a 2.2 rooted)
4. Configuring my phone
5. Installing the 5.09 Radio
I don't think that I have doing anything else, but now I can call someone even in the dark and my screen doesn't stay blank anymore !
Hope this could help someone.
My DHD has problems with the proximity sensor. I returned the device to the vodafone store (Netherlands), and they changed the device for a new one that worked.
Today, 1 day later, my second DHD is now having the exact same problem with the proximity sensor.
When I make a call, the screen immediately goes black, and the device no longer responds to any button (not even the power button on top). The ony way to get the device back to life is by removing and reinserting the battery.
Video of the problem
When I receive a call, the screen stays unlocked, even when the device is placed against my ear, so I end up with my ear pressing the active screen....
I've read more complaints about this exact problem on the tweakers.net forum. It is still unknown whether this is a hardware of software failure.
UPDATE
The problem seems to be related to the lightsensor, when holding a locked DHD in front of a bright light source, the device wil unlock (as long as you keep it in front of the light).
It might be, that when used in bright daylight a DHD will function properly.
Also, when calling using the headset, the problem does not occur. When inserting a headset in a "locked" DHD, it will wake up.
UPDATE2
Some facts, to "bust" some myths about the problem:
- It seems the problem can happen on all DHD's, not just devices with a particular S/N, software version, carrier (telco) or color.
- It has something to do with the light sensor (which is the same sensor as the proximity sensor) since the device unlocks when held in front of a bright lightsource, some users claim their device works well, as long as they are in daylight.
- The DHD uses a CM3602 proximity/light sensor, the same as a regular Desire
- The problem might not occur immediately after purchase, sometimes it takes a few days before it starts, thus switching your DHD for a new one might only solve your problem for a few hours/days (this is what happend to my second and third... yes third device)
Seems like the same kind of problem: http://forum.xda-developers.com/showthread.php?t=811282
Exactly the same post. Nice detail that I'm also a Dutch user bought it at a Vodafone store.
So, that's at least 3 devices reported with this problem.
Is there a way to turn off the proximity sensor? This would mean I have to turn the screen off manually when I make or receive a call, but that way, I don't have to reset the device every time I make a cell
Maybe you guys have found why it failed the google test ?
1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??
I wouldnt be very worried tbh, this is surely software related else they wouldnt release any batch of cellphones and delay the release for more than just a few weeks.
Can you make a Video and load it up on Youtube?
If we have a video it´s much easier to show HTC the problem... maybe we can load this video up on facebook to the HTC page...
Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Edit: Ah I see 2x LeonM1234 and 1x WizardX. Forget this post
liorra3 said:
1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??
Click to expand...
Click to collapse
Will try contacting HTC Netherlands tomorrow, today is Sunday...
name_th said:
Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Click to expand...
Click to collapse
This is my second DHD with this problem
P.S. Can any mod please remove the 1 post per 5 minutes limit, it is quite annoying... thanks!
A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D
HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
www . techeye.net / mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?
i think to cancel my DHD order until that issue will check.
Apache14 said:
A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D
Click to expand...
Click to collapse
the solution with the desire was an software update ?
Milini said:
HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
http://www.techeye.net/mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?
Click to expand...
Click to collapse
There you go proper link and welcome!
liorra3 said:
i think to cancel my DHD order until that issue will check.
the solution with the desire was an software update ?
Click to expand...
Click to collapse
Yep was solved with a S/W update
You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.
mach03 said:
You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.
Click to expand...
Click to collapse
Keep in mind, my device worked as it should the first day...
i don't understand how it can work fine one day and the following day it messes up lol
Apache14 said:
Yep was solved with a S/W update
Click to expand...
Click to collapse
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?
liorra3 said:
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?
Click to expand...
Click to collapse
s/w is software... you practically answered your own question
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?
Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..
Which ROM?
I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?
Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):
Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....
Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone
Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.
rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks
rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.
are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...
Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).
I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...
After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.
You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
wave1990 said:
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
Click to expand...
Click to collapse
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Protonus said:
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Click to expand...
Click to collapse
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
wave1990 said:
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
Click to expand...
Click to collapse
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Protonus said:
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Click to expand...
Click to collapse
I do not know if you develop .... but you could create a fix that recalibrates the driver every tap on the screen!
is an idea =)
Love my Note 4 but lately I have had nothing but problems with this damn thing. GPS NEVER stays locked for me use navigation or even check the weather if I changed cities. Saw the fix on where you take the back of the phone off and adjust the GPS contacts, long story short the LCD screen broke on me. I see nothing but problems people have on this phone about the GPS and Samsung will not hold there end. Anyone else have the same issue with there GPS?
Sending phone out to get repaired tomorrow.
Nick
i was on cm13 for a few days and i had horrible gps on google maps. when i returned to stock, gps was fine again. if ur having gps problem even on stock it may be a hardware issue.
avenged06x said:
Love my Note 4 but lately I have had nothing but problems with this damn thing. GPS NEVER stays locked for me use navigation or even check the weather if I changed cities. Saw the fix on where you take the back of the phone off and adjust the GPS contacts, long story short the LCD screen broke on me. I see nothing but problems people have on this phone about the GPS and Samsung will not hold there end. Anyone else have the same issue with there GPS?
Sending phone out to get repaired tomorrow.
Nick
Click to expand...
Click to collapse
If you have time, file an Android bug report: h t t p s://source.android.com/source/report-bugs.html
I have the same problem with stock ROM. I have also had the problem on 3 other completely different Android phones from different manufacturers - also running either with or without the stock ROM - mostly on Lollipop. This is probably not a hardware issue as another member has suggested, but a bug. I seriously doubt that the 4 different phones I've experienced this with all have hardware faults. If you file on that website, I'll join you. You are not alone.
notedroidbrokedroid said:
If you have time, file an Android bug report: h t t p s://source.android.com/source/report-bugs.html
I have the same problem with stock ROM. I have also had the problem on 3 other completely different Android phones from different manufacturers - also running either with or without the stock ROM - mostly on Lollipop. This is probably not a hardware issue as another member has suggested, but a bug. I seriously doubt that the 4 different phones I've experienced this with all have hardware faults. If you file on that website, I'll join you. You are not alone.
Click to expand...
Click to collapse
I appreciate the response. It was cheaper for me to purchase a new Note 4. I have the old one here if anyone is interested for parts. I have no GPS probs on the new phone.
avenged06x said:
I appreciate the response. It was cheaper for me to purchase a new Note 4. I have the old one here if anyone is interested for parts. I have no GPS probs on the new phone.
Click to expand...
Click to collapse
Sounds like you solved the problem with a new phone. If the problem ever arises with the new phone you may be interested in my post in http://forum.xda-developers.com/note-4/general/gps-close-to-unusable-t2948602/post67864418 (see post #339). I was able to fix my phone by partially disassembling it and removing corrosion on various contacts.