Just done a search about this prob and there is a couple of similar threads but they are not really same issue.
This has happened 3 times now with different roms over past month and not sure what is causing it. Phones screen seems to go bright white on wakeup, looks like a negative.
Is there any experts out there who could shed some light on it. Does it sound like a slow hardware failure or is it more likely a software issue. As I say its only happened a few times and a reboot brings it back to normal but it just concerning
Has anybody else had this same issue on wakeup before?
My first reply post here...
I have the same issue...reboot will recover it...but ones it recovered after normal stand-by upon wake up...I assume it is just some incompatibility of Android with HD2 graphic processor, minor issue.
Current ROM
Omega WM6.5.x v14
Current Android Build
NexusHD2 v1.8
I used to have the same problem and put it down to an incompatibility. Since moving to a Nand ROM it seems to have gone away.
TheATHEiST said:
Phones screen seems to go bright white on wakeup, looks like a negative.
Has anybody else had this same issue on wakeup before?
Click to expand...
Click to collapse
I used to have this issue, but only on SD builds, and very, VERY rarely. From about 5-6 months of SD Android, I probably had it about 4 or 5 times.
I agree with madmillsy that I've not seen it on a NAND build, but I don't think I'd seen it on recent SD builds either.
Is it an SD build you're running, and if so, how old is it?
Edit: Forget that last question - just saw your current ROM in your sig.
I saw this effect twice, never in WM, only in Android. First time with SD build, but second time, last week with gauner's HD NAND build.
As it was already described, there is probably some incompatibility regarding graphic, when waking up from idle mode. I do not think it is related to SD builds only, they handle graphic same way, with same kernels.
By the way in gauner's build I noticed also problem with activating sound from idle mode time to time. So maybe it is not directly graphic driver part, could be somewhere else and this is just consequence.
At the end, it is rare and minor issue, the only discomfort is because of restarting the phone.
Had a few times this issue, and didnt need to reboot to make it worn off. Just put it in a colder environment, and it will go away after 10 minutes orso. So I honestly thing is has todo with the temp of he device. Mostly it came up after a long phonecall I had, which maked the phone a little 'hotter'.
Just a speculation though, didnt have this issue since I use NAND. But I guess it can come-up randomly, but I don't worry it to be honest.
Its happened twice on SD builds and once on NAND build.
I was concerned that I was starting to get a hardware fault but im relieved to hear that others have had it so it must be simply a soft bug.
It rare anyway so no big deal.
Thnx for replies guys.
happened to me once with NAND - sorted with a reset. Scared the hell outa me
F-bone said:
happened to me once with NAND - sorted with a reset. Scared the hell outa me
Click to expand...
Click to collapse
same here, including the scared bit.
sodeknetters said:
same here, including the scared bit.
Click to expand...
Click to collapse
the weird thing is that since I posted in this thread it happened to me twice today!...total 3 times so far... Im getting worried...
Never happened to me with an SD build (after 3 months of use) but happened twice to me with DFT's NAND, reboot fixed it as stated and yes...it scared the **** out of me the first time lol
For anyone that might be debugging the issue - it might be connected with calls.
I receive a call. After I'm done with talking, i turn on phone and it's on negative. Alright, i restart it. After restart it works fine, until i call somebody. After call, again negative screen. It happened two times in a row.
Also i don't really need solution to this problem. Only some kind of workaround that will allow us to fix problem manually without restarting phone. Maybe a script that will reset display driver or something?
Related
Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
I'm experiencing avery annoying problem with my phone. It's been happening for some time now, and I've tried all sorts of different things to fix it.
The phone completely randomly restarts, or just powers off totally. This happens at least a few times a day on average, and sometimes has a crazy spurt where it restarts itself like, 5 times in an hour. This is very annoying when I get my phone out to check if I have any texts, and it's totally dead or sat on the ChuckyDroid Winmo screen. People text me 3 hours later, asking why I didn't reply to their messages, or they have been trying to ring me!
I have tried everything I can think of. I have tried at least 10 different Android ROMS, and a few different Winmo ROMS. I have tried every radio from 2.08.x to 2.15.x and I have also Task29'd the phone, then started afresh. It still does it.
Any got any ideas what could be causing it? Is it possible it's a faulty battery? I am beginning to think this as it never seems to do it if I have the phone plugged into charge, either from USB or mains. If people think the battery is probably knackered, I'll go onto Fleabay and buy a new one, but I don't want to do this if people don't think that's the issue.
Thanks in advance... I hope people can help, as this issue is totally unworkable for me.
Cheers
That doesn't seem like a battery issue to me, rather SD related.
As you have already tried about everything: full formatting your SD card should fix it. There are some more advanced ways of formatting, in case the Windows (full! not the default quick) format still doesn't do the trick.
Hm.. I'm pretty sure I've run a full format of the SD card before, but I'll certainly do it again when I get in and test out the theory.
Thanks for your reply mate
I also had this problem(s) with Froyo... suddenly my phone rebooted...
However.. since i'm on Gingerbread... the problem didn't occur anymore..
Maybe you can try a Gingerbread build to see if the problems still occur...
I can give that a try too. I know there's a lot still to be worked on the Gingerbread build, but if it's more stable then that's good.
The MDJ Gingerbread build is pretty stable.
Well, thanks for your efforts guys, but no joy. I full formatted the SD, flashed 2.15.50 to my phone, then ran MDJ Gingerbread... I think it lasted about 4-5 hours before it started restarting itself again. So screw this, I'm going back to Winmo until NAND is ready. Winmo might be crap, but at least it's reliable. Totally pissed off now, to be honest.
Hey,
I've got the HD2 running extremely smoothly with the NexusHD2-Gingerbread v2.2 build.
Since moving to android and trying out WP7 I have been experiencing an issue where after a whole day of running perfectly I will turn the screen on to find everything is washed in white - it's like the screen turns greyscale but in white so everything is still visible and works but in white.
i don't seem to be able to find this problem anywhere else but it has happened with all the android nand roms and the WP7 rom - a soft reset fixes the issue. I'm currently using radio Radio_Leo_2.15.50.14 and have switched around but haven't found one that fixes the problem...
Any thoughts on what could be causing the problem??
Thanks, Luke.
I have the same problem sometimes. Will be glad if someone can explain!
Ive also experienced this, disappears after reboot or sometimes if i turn the screen on-off a couple of times, kinda weird.
Glad to see others are having this problem - seems to be so rare but I cannot find a solution. Would be interested to see if it still occurs now with standard wm6.5.
Anyone else experiencing this or have some idea of a fix?
i too have this problem.many times screen just go off like greyscale.can anyone help?
One more with the same problem...
Never had it with my currentrom (Hyperdroid) until I've read this thread.
Bump for wisdom.
Are you morons really that stupid
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
ALL_XDA_MODS_R_C*NTS said:
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
Click to expand...
Click to collapse
Erm what the f*ck? No need for that. Any actually, it's not a screen issue, it's an issue in earlier ROM's (well from what I've experienced). Like flash Cotulla's Desire ROM and it happens a lot. I presume you don't really like XDA due to your username? Banned maybe? Why would you even bother making a new account and just trollin'? That's sad, lol.
I only had it when the first batch of ROM's came out. Never withing the past month and a half.
It's like the screen goes negative.
But yeah, there isn't a clear fix for it AFAIK, you should back-up everything on your ROM and try an up-to-date ROM and see if it's still happening. I doubt it.
having the same problem as well
usually happens after i wake up, so during its idle time which is kinda strange
i also noticed it started happening after i installed cracked widget locker, any of you using that?
It happenes to my phone quite regulary but only running android roms, i think around september 2010 it happened the first time. I suspeced my phone, but even after getting a new hd2 it happens sometimes. It usually just happens randomly, not after specific actions. Sometimes it stays only for some minutes and sometimes it can be only fixed with a reboot.
I'd really like to know when this bug will be fixed.
I was having exacly the same issues with my old build. But since im using CoreDroid this problem has dissappeard.
+1 I've only experience this twice, and not since December, but I found it weird both times. I think both times were during a phone-call. A reset worked.
ALL_XDA_MODS_R_C*NTS said:
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
Click to expand...
Click to collapse
Wow...another keyboard hero....you are so brave typing that, we are all in awe of how awesome and manly and strong and tough you are!!
ANYWAY......STFU...it's not a screen problem.
I too have this problem, and it is my 2nd HD2 and happens VERY rarely, but does happen and has happend on both of them.
OH, and Mr Tough Guy....I live in the UK...VERY rarely get warm weather over here, so it AINT the sun.
You, Sir = FAIL.
Matt
Same here happens once or twice a month no big deal though
Sent from my HD2
I'm currently running imilka's RAM Desire HD v2.0 since a month or so, the pale screen appears sometimes up to 2-3 times on one day and then not for several days. A reboot allways fixes it, sometimes it fixes itself after some minutes.
But i really find it annoying.
This happened to me in most desire/desire hd sense builds.
Now, I use the official hd2 MIUI and gingerbread seems to solve the issue.
Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?
Okay, An update
This is happening when I reboot the device.
Is there something in settings that I am missing, or is there a registry setting I can change?
do you have your "date & time" settings set automatically?
Yes
bleui said:
do you have your "date & time" settings set automatically?
Click to expand...
Click to collapse
Yes time setting is automatic, even tried setting it in the registry.
It got that bad yesterday my phone reset itself to Jan 1980.
It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?
h0ng said:
It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?
Click to expand...
Click to collapse
Truth is no matter what is causing this... TWO big issues for me when choosing a phone software set up.
The phone knows what freakin time and date itis
The phone nor the software on should destroy batteries
but thanks guys it really was fun to play with.
Don't use automatic, mine does the same if I set to automatic.
I thought it was something with Giffgaff as I would set automatic and the time would be right but later on during the day it would be some crazy time and date.
Set to manual and your clock will be fine
dunno about any of that but, i do know that if i boot in to MAGLDR is gets buggered up, doesnt matter if the time is manually set or auto set, it always buggers up, dont boot to it and all is good
, at least for me anyway
I'm having the same issues. Time and sometimes dates getting screwed up. Only started happening to me about a couple of weeks ago now. But it's frustrating at the least. I've switched mine to manual setting at the moment. Gonna see how it goes over the next week.
One thing though, it isn't happening to my wife's HD2. She is using the older version of WP7, I'm currently on Yuki's more recent NODO version...
as per my post above yours if you use magldr or even the bootloader it gets messed up, so dual booting droid may be a reason, or using bootloader / magldr to charge, other than that i dont have this issue
Not got dual-boot on my phone, neither do U boot to magldr to charge... But it's happening to my phone every few days so far. Today it was out by 28mins. I want to see if having it on manual time/date does any better...
i also have a problem with my hd2,
9 times out of 10 when i reboot the phone the time and date will be wrong with no pattern i can spot (started to do this out of the blue- no updates or new roms).
im currently running with a cooked win mo image and android on the sd card.
battery still has a respectable life although seems to run out quicker than it once did so i may purchase a new one. (the old one is just over 12 months old)
also my phone has started to freeze on pin request after receiving a text so im gonna try a new image too
if anyone else has seen problems like these and solved them drop a noobie a helping hand pleeeeaaasseeee....
It's not HD2 related
The same issue happens to me (phone jump approximately 36 hours foward randomly)
The phone was a LG Optimus 7 on official rom but never managed to fix this issue (automatic date or not)
ForgetfulGuru said:
Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?
Click to expand...
Click to collapse
I have the same issue! It happened some months after flashing xboxmods v. 1.11 Rom. It can't be a battery problem because I use 3 different batterys ^^