Flash LED randomly turns on to random brightness level - 8125, K-JAM, P4300, MDA Vario General

I just got a Tmobile MDA today and it's a cool little device. However, the LED Flash is randomly turning itself on, does not randomly turn itself off, and the weird thing is that it doesn't always stay on at full brightness. I have found that if I manually toggle the flash in the camera app, it turns off the flash for a time.
Also it tries to light up kinda like the way a fluorescent bulb lights up, flickering and only going full blast if I turn it on.
I have checked the wiki, and the first three pages of the forum, and google, and no mention of this problem. Any ideas or maybe a fix that I missed??
Thanks!

Hi
Glad to know I am not the only one with this problem!
Mine started to happen about a year ago, exact same symptoms as you describe. I have not managed to find a fix and can tell you it is defo not software related.
O2 Xda Mini S is the model I have for your ref, O2 are of course saying it needs to be sent back under warranty.
If you do ever find a fix post a reply as I would be interested to know what it is!
Latz

ive been searching solution to this problem for almost 6 months now, still to no avail.

Related

Wizard wont turn on - however lights still flash?????

Im currently using the imate rom 2.16.9.1.wwe Rom date 2/6/06 extrom version 0 2.16.9.101
It has been working fine for the past few weeks and the performane increase has been much better. I was also using the oush mail which also worked well. Then a few days ago I started to have a few problems with the phone, basically it would look as if it was working the lights flashing, however when I went to turn it on it wouldn’t turn on. The only way to resolve this si to soft reset the handset. This problem is now occuring on average 2 times a day! I havent even installed any new software!! Thwe only major incident before this started happening was I used skype twice! But havent used it since! I have also stopped push mail cause I thought this maybe the issue but it didn’t solve it!
Its so annoying cause I think the device is operating normally cause I see the flashing lights however it cant do anything cause it has frozen!
Any ideas???
I was thinking of going for a hard reset but if I restore my backup ive taken with spb will this not just reintroduce the problem?
just to add for further info i have no apps running and the
program memory is total - 44.01mb
in use 19.67mb and Free 24.34
thats after a soft reboot!!
This might be a really silly suggestion, so appologies if it is, but could it be just the backlight turned off for some reason so it looks like the device is off when it is actually on?
No, I don't think that it is the backlight as I am also now experiencing this same problem ... approx 1 - 2 time daily. You think that the phone is functioning until you try to use it. Only option is soft reset.
Any help on this would be appreciated.
no at present a soft reset is the only cure and even then it may occur again later on! Bluey HK are you using the same rom as me??? the imate one?
its done it twice already today and its only midday! the last time i was just browsing the web, closed the browser, then switched it off and then couldnt turn it back on! Do you think it may be a memory leakage issue????
This happened to me yesterday on my T-Mobile MDA. I am running the latest T-Mobile_RUU_Wizard_2210401_221_20710_ENG_US image from xelencin.
What appears to have triggered the problem for me was attempting to connect to T-Mobile's My Email app to download mailbox settings while the signal level is too low or intermittent (Wi-fi and Bluetooth were disabled).
The backlight would not turn on and I could observe the My Email app trying to access the server.
it sounds as though it may be a bug connected with a GPRS connection???
ahh its done it again, this time i wasnt doing anything just died! I think i am gonnna have to do a hard reset cause this is making the phone unuseable!
if i do a hard reset and then install a back up is there a high possibility that this will reintroduce the bug???
its not the backlight
my 8125 is having the same damn problem. its nto a backlight issue, as it just stalls, and the past 4 times its done it, i've just removed the battery and turned it back on as a soft reset wont work, and i can't it to react to any commands. this is either a software issue all our phones are dying. i was having this problem with summitter's previous 2.17 rom, then updated to the recent 2.17.11 aku 2.2 rom... thinking the upgraded rom is what it needed...NOPE... still crashed. almost all instances i believe are when the wifi connection was active. but i could be making that up, i'm positive on 3 occasions it was with a wifi connection active. but not too sure about the 4th.
this is making me insane, and we need to figure out whats up~!
to expound on the problem:
one time i was in the middle of checking voicemail, then tried to delete, but the screen wouldn't light up, and it wasn't responding to my option 7 to delete command. the other time was in the middle of a phone call. something's up....
i am having the same issue with my 9100, its running the latest offical rom, mine does it whenever it feels i dont believe it is wifi or gprs related as i have the problem at time when i have been using neither.
there does not appear to be a link to any software i am using either
any ideas?.
yea- i get the same sometimes, i go to take my phone out of standby and it wont do anything, the power button doesnt work- the light just flashes. sometimes it freezes on the today screen, the power button dont work or anything. really need to sort this!
any ideas? any1 else get this? its where u put ur MDA in standby, and next time u press power button 2 turn on nufin happens, but the leds still flash at the top!
yep i still get the problem! still no cure!
I have exactly the same problem... I just pick up my device from my pocket to use it, I press on the power button once but the device won't wake up from the standby mode. I wish someone can give us a cure.
Low Battery...
I had this happen to me once recently...for me it was becuase my battery was too low. Freaked me out, because everything looked good, but I would power on and get nothing! Right after it started it powered on for a sec then quit. I had to put it on the charger and leave it for a couple hours to get a good solid charge, then everything was fine. Hope this helps....
thanks for the response, unfortunately mine is definately not related to the battery charge!
mine hasnt done it in the last day, ive been leaving it a while before putting it into standby. i used to exit my app (messaging or whatever) and shut it off straightaway, but i give it a sec or 2 to make sure its all good
and its doin ok so far!

Screen wont come on after Sleep

Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse

[Q] Phone turning off by itself and renders itself off ever since

Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!
franshu said:
Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!
Click to expand...
Click to collapse
Mine is happening the samething, glad Im not alone. My was running fine on rooted Modaco custom rom for a few weeks then all of sudden the phone auto shut down like it has its mind. I installed Cantonese keyboard and camera mod too and some other apps. Currently Im tracking down the source. Now I have franco kernel and madaco rom on clean install running with no other app install to see if it will shut down or not. If it does Im going back to stock to see if samething happen.
I have to boot it couple times until it doesnt shut down itself anymore. Sometimes it be stable for couple hours or couple minutes or instantly.
I have the same problem, Just got my phone from google everything is stock nothing has been changed and the phone just turns it self off and then i cant turn it back on for sometime.
Does anyone know what causing this problem?
Mine also turns off multiple times a day, sometimes by itself, sometimes during a call, often when taking a picture.
Today every single time I took a picture it would shut down.
I'm f*cking pissed at waiting 5 weeks to get a useless phone... and god know how long it will take to get a replacement if I ca get one.
Hi guys, I have the same problem too
I've used my Nexus 4 for 2 weeks without any kind of problem when suddenly it turned itself off. If I try to turn it on, the phone just turns itself back off again and I haven't solved the problem even with a reset.
But I've noticed that the battery doesn't charging even with the charging cable. I think the phone detects that hasn't enough battey level and for that reason turns itself back off.
Do you think it can be an harware or software problem?
Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium
kalipedia said:
Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.
Notorious544d said:
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.
Click to expand...
Click to collapse
You know, I'm looking at my battery history (using battery monitor) and i see the period that the phone was shut down and then when i powered it back up this morning and i notice the battery temp is extremely high so it probably has to do with the phone shutting down due to overheating, which obviously shouldn't happen. I wasn't using the oem charger, so I'll switch to that for the time being and keep an eye on temp. Hopefully it's a software bug and not a faulty battery because it should definitely be cutting off charging when it reaches 100%.
Sent from my Nexus 7 using xda premium

Nexus 4 stuck in standby - Hardware issue?

Hey guys,
I've bought my Nexus 4 end of January (first revision) and am having a major issue since I got it:
Sometimes (once a week, first two weeks even more often) it is stuck in standby. So when the phone is turned on, but the screen is off and I try to turn the screen on, it won't react at all. Most of the time, the notificationlight is blinking.
This is totally sporadically, but I think more often, when the timer is set, to get me up (or not^^) in the morning.
It won't even react on charging or attaching it to my PC. I logged it twice, but there was nothing special in the logfile (logged it with su; logcat > /sdcard/log.txt)
This can get quite annoying. All in all, this makes the Phone quite unusable, because, without trying to wake it up, you never know if it's still running and you are reachable or if it's already stuck...
First I thought, this would be, because of some softwareproblem, but I got this issue with every ROM I tried (even stock, where I got this problem the most...)
Should I send it back to Google for RMA or do you have any idea why this could be?
Thanks in advance,
acid_g
Same problem here. Also bought it at the end of January. At least once a week the screen won't turn on, and usually there is a notification light flashing. I've found lots of other people online with the same problem, but no solution. There's a ticket for it here:
code.google.com/p/android/issues/detail?id=52926
I called Google support, and they recommended doing a factory reset, but it didn't help; a couple days later the problem happened again. So yesterday I called them back and started the RMA process. I hope the new unit works. This problem is so annoying and frustrating. You never know if your phone is going to work when you pick it up.
its called sod, sleep of death. it can happen with undervolting, and some apps can bring it on

[Q] Blinking Red LED Notification

Hi,
I tried to change my file system from Dalvik to ART and when my phone was optimizing apps after reboot, my phone suddenly shut off and it wouldn't turn on. If I try to turn it on, it will show a solid red LED for 3 seconds or so and then start showing a blinking red LED.
I did manage to get into the bootloader and I flashed the whole factory image for Kitkat and erased my data through fastboot, but it didn't fix anything. Anyone know if there's anything else I can do? My phone is outside warranty because I bought it on release date last year :/
Look what this guy had: http://forum.xda-developers.com/showthread.php?p=47968382
Spoiler: it's the exact same issue, and he resolved it. Wouldn't it have been great if you just searched the forums for a similar thread before posting this? I can answer that. Yes, yes it would have been great. It would have saved you time waiting for an answer here. And it would have saved me time writing this rant. So next time, use search.
Sent from my Nexus 4 using Tapatalk
Oh thank you. What great luck that he had the same problem. Does anyone actually know why disconnecting the battery cable would solve the problem? It seems odd that this is caused by a software problem, but a physical fix returned it back to normal.
Problem solved, so i suppose we can close this thread now

Categories

Resources