Related
[Warming up]
I've been having problems lately trying to figure out the problem..
So, first i suspected the SD card, doesn't seem like my original 16GB card was the problem, because i bought 2 new 32GB Micro SDHC cards already, same problem..
[Now the problem]
80% of the times when i reboot and go into recovery and flash a couple of roms, or reboots in general, i for the most part get stuck in Bootscreen, if i try to wipe Cache and Dalvik-Cache, it sometimes solves the problem and 20% of the times i can get into the system, the other 80% of the times that i actually succeed into getting the rom to load up, i mostly get stuck there aswell, untill it reboots the phone, and im back at the imfamous bootscreen...
So, i've figured, is there anyway for me to log the stuff that is happening at the boot screen? because im curious to what the problem might be..
[The things i've done already]
Everything is formated as EXT4, and has been so since Mike introduced it with his rom..
i've tried Mikes rom, Unity, Honey roms, Coredroid, RCmix, all the same on all of them.
I always wipe my phone fully before i boot the rom, mostly with Mikes Super Wipe Script, but sometimes with the wipe zip mentioned from the Rom Dev explicitly telling me to use that..
I always let the rom boot 2 times before i start flashing themes and stuff..
Just going Stock rom doesn't help either, i've tried that aswell, no change.
I've cleaned the phone, from top to toe.. (brushed and cleaned with special liquid)
I've tried different Micro SDHC cards, 1 of em was a counterfeit card, the newest one works just flawlessly, i've benchmarked, checked for errors and even done a Bluff check on it, all working 100% nominal.
CPU running at 998Mhz, just incase..
[Ending]
So, does anyone have any suggestions?.. Does anyone have any way for me to get logs of the Bootscreen (as its a wallpaper, i have no chance in actually seeing what is happening)
Are there any ADB commands i could use to check errors in bootscreen? Any diagnostics tests?
Maybe even a way to refresh the Bootloader with ADB commands?..
ANY help would be greatly appreciated!!
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Have to agree on that
Do you still have warranty?
drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Thanks man, very much appreciated!
I'll run some logs tomorrow and see whats up with the phone, i actually got the phone running optimal again with yet another fresh rom flash and it all seems to work, have only restarted the phone 2 times, as im afraid of restarting the phone and get stuck again..
If i do get stuck, im stuck forever, and have to try above mentions i've done before, wipe cache and dalvik-cache, sometimes this works, most of the times it doesn't, and i end up fully wiping a couple of times and reflashing roms untill it works.. (I know this might sound like an SD card problem, but its not, i've gone thrue this with a couple of programs)
Anyway, a thousand thanks for that link, will probably help me quiet some..
madmaxx82 said:
Have to agree on that
Do you still have warranty?
Click to expand...
Click to collapse
Aye, this phone i have in my hands right now has already been in for repairs before and they changed the PCB of the phone, got a new IMEI number and all that..
But i do have warranty left for it, but i have to iron out the problem before i send it in, don't wanna risk being sent back to me and i have to pay lots of $ for their trouble (you know how HTC 3rd party repair centers works).. Plus they might actually scratch my screen some more as they did when i last sent it in...
Well, i have another "minor" problem with the phone aswell, not sure if its my phone or a general new cosmetic problem occurring on phones sent in for repairs, as i haven't noticed it on my earlier phone (Well theoretically the same phone).. Is that when i look at the screen in pitch black moving screens, i can see a distinct line going from Top Right to Bottom Left corner, and the Top Left side of the screen is black, and the lower right part of the screen is black/grey, you can see the difference, but not noticeable when your actually booted up, only in the Bootanimation part is it visible, i've tried different Bootanimations and everyone that has a Black background has this cosmetically problem.
Aah crap, Wall of text..
Haha just gonna add that i installed both apps you mentioned earlier, and the phone feels more like a Dev phone now, but anyway, it all worked great, not sure if it logged anything yet, didnt find anything in the app yet if it does..
I noticed something strange though, Gsensor Enabled, then right before bootup, Gsensor Disabled..
Have no idea why it does that, have no problem with Gsensor though..
Edit:
6 successful restarts!! That's something new!
I have no idea why its behaving this good.. Well time will tell..
Does anyone's G-sensor work? i ran the htc function test and it's not working. Any solutions? I've try a factory reset but no joy.
http://forum.xda-developers.com/showthread.php?t=1586177
Mine stopped working last night.
When I tried the calibrator it failed saying "calibration aborted" the sensor checker also failed.
I went to the task manager and ended all tasks, I rebooted but no change so I switched off the phone then back on again and all was working
I will have to keep an eye on this
Bixx said:
Mine stopped working last night.
When I tried the calibrator it failed saying "calibration aborted" the sensor checker also failed.
I went to the task manager and ended all tasks, I rebooted but no change so I switched off the phone then back on again and all was working
I will have to keep an eye on this
Click to expand...
Click to collapse
this is indeed a very weird thing mate, it's happening to a lot of people...
I'm sure it's a tegra3 related issue. Probably fixed on the next update.
Now that i think about it...i don't remember to have turnned off my phone when i had that issue...LOL
in conclusion to this subject, my latest "possible" fix is, fully drain your phone out of juice untill it doesn't power up and charge it again.
it should work afterwards.
casca said:
in conclusion to this subject, my latest "possible" fix is, fully drain your phone out of juice untill it doesn't power up and charge it again.
it should work afterwards.
Click to expand...
Click to collapse
Didn't fix it for me...
Skickat från min HTC One X via Tapatalk 2
Have you drained it completly? To the point that the phone doesn't turn on?
Have you tried also killing all tasks in task manager?
Sent from my HTC One X using XDA
G-sensor not working
Tried everything I can think off aside from draining the battery flat. Does the 1.28 rom version fix this issue? Seems like my g-sensor has been dead for a while...
Anyone on 1.28 have this g-sensor issue?
I have the same problem. I wrote a mail to HTC in yesterday about the problem and hopes they got an answer for this iritating issue.
Sendt fra min HTC One X med Tapatalk2
Master-T2006 said:
I have the same problem. I wrote a mail to HTC in yesterday about the problem and hopes they got an answer for this iritating issue.
Sendt fra min HTC One X med Tapatalk2
Click to expand...
Click to collapse
They asked me to send it in for repair - will take up to 3 months....
casca said:
Have you drained it completly? To the point that the phone doesn't turn on?
Have you tried also killing all tasks in task manager?
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
alazarus said:
Tried everything I can think off aside from draining the battery flat. Does the 1.28 rom version fix this issue? Seems like my g-sensor has been dead for a while...
Anyone on 1.28 have this g-sensor issue?
Click to expand...
Click to collapse
Yup. Tried it all and the problem persists. Complete drain, factory reset, secure boot calibration, kill all tasks, ota update to 1.28 (from & to stock), superwiping and flashing a new rom (twice) , running htc's function test and getting "stuck" on the g-sensor test. And more.
Been there, done that.
The sensor doesn't react at all, so rotation won't work and in games like teeter, the ball just sits there no matter how I twist and turn.
And now HTC, via their chat, say that this might not be covered by the warranty since I have unlocked the bootloader. If I turn it in, they'll send it to a service centre, which may decide that the problem was caused by me (which is impossible since it was already there on stock), which would mean that 1) I'd have to pay for any repair or 2) I'd have to pay for "wasting their time" and cough up money for securely shipping it to/from the repair centre. Yay.
On the up side, the normal calibration aborts if I move the phone during the process, which to me would indicate that the sensor is working at SOME level, right?
Skickat från min HTC One X via Tapatalk 2
Fruktsallad said:
Yup. Tried it all and the problem persists. Complete drain, factory reset, secure boot calibration, kill all tasks, ota update to 1.28 (from & to stock), superwiping and flashing a new rom (twice) , running htc's function test and getting "stuck" on the g-sensor test. And more.
Been there, done that.
The sensor doesn't react at all, so rotation won't work and in games like teeter, the ball just sits there no matter how I twist and turn.
And now HTC, via their chat, say that this might not be covered by the warranty since I have unlocked the bootloader. If I turn it in, they'll send it to a service centre, which may decide that the problem was caused by me (which is impossible since it was already there on stock), which would mean that 1) I'd have to pay for any repair or 2) I'd have to pay for "wasting their time" and cough up money for securely shipping it to/from the repair centre. Yay.
On the up side, the normal calibration aborts if I move the phone during the process, which to me would indicate that the sensor is working at SOME level, right?
Skickat från min HTC One X via Tapatalk 2
Click to expand...
Click to collapse
My question is, was it working when you got it in the first place?
Mine unlocked itself after about 48hours...
The only thing I can remember doing, that I've never said before was that I dropped my phone several times in all possible directions on a very slim carpet as a desperate act...
My thought was, maybe if I drop it and shake it really hard, it might get loose eventually. (Yes I'm a bit crazy... )
It got back to work after 48 painfull hours and lots of failed attempts...
I had this problem, but it was fixed by a reboot. Dont know if that gives you any clues as to whether it is software/hardware related?
Yeah, it looks like some kind of hardware issue. I need to send this phone for repair. HTC has disappointed me - this will be the last HTC phone I purchase. Nothing but problems since day one. Stay people - you have been warned!!!
casca said:
My question is, was it working when you got it in the first place?
Mine unlocked itself after about 48hours...
The only thing I can remember doing, that I've never said before was that I dropped my phone several times in all possible directions on a very slim carpet as a desperate act...
My thought was, maybe if I drop it and shake it really hard, it might get loose eventually. (Yes I'm a bit crazy... )
It got back to work after 48 painfull hours and lots of failed attempts...
Click to expand...
Click to collapse
Actually I'm not quite sure if it worked in the first place, because I bought it used (from a guy who realized he hated Sense after three days). Nothing seems to get it to work, though I'm glad yours did.
Fruktsallad said:
Actually I'm not quite sure if it worked in the first place, because I bought it used (from a guy who realized he hated Sense after three days). Nothing seems to get it to work, though I'm glad yours did.
Click to expand...
Click to collapse
Hum... maybe that's why he sold it sorry to hear it mate...
Well, if you are brave enough to do it, do what I did... shake it a lot, and drop it (from low altitude obviously) into a soft carpet... it might sound crazy, but the shaking could be enough to unlock the sensor... corner drop it all around and good luck! going to google it to see if there is any sort of recent found fix...
in the meantime get the app "sensor list" from the market and tell me the brand of your sensors if you can read it.
I had this issue, 3 days after I got the phone. Tried everything I could think of
(fact resets, etc). Still no joy, so I sent it back to the shop.
When they tested it , it was all workign fine again....
However I have a couple of thoughts on this (not tried it out yet so give it a go).
First of all disable that HTC Gestures/3 Finger rubbish. Secondly ensure Fast Boot is off.
Then re-start phone.
Now , Although I did end up like that, I'm sure it didnt fix the problem immediatley following me disabling those options.
All in all there is definatley something screwing up the G-Sensor, which is seemingly fixable/can be disabled. Its just finding out what it is/how you do it!
Slim
I completely agree on you mate. The question is what.
My subconscious is telling me that it has something to do with the live wallpapers but I have no proof. It's just a stupid hunch, but it wouldn't be my first stupid hunch and I was correct so...
anyway, I've just red this...you guys might want to try and do it.
source: www.androidforums.com
"I just called my vendor, to complain about the auto rotation issue, and here's the step to fix, which worked for me.
Restart the phone, and go to safe mode (restart, and once you see the HTC logo, long press the volume down button), it'll restart again and go into safe mode.
Go to Settings, Display & gestures, G-Sensor Calibration, then calibrate, make sure to put the back of the phone on a level surface, this time, it shows calibration complete not aborted when I did it before in the normal mode.
Restarted the phone and it works fine now.
Thanks,
Mohamed El-Ghazaly"
when in safe mode, I would attempt everything from a "kill all tasks" in device manager to enabling and disabling auto-rotate in display settings.
Good luck guys.
casca said:
in conclusion to this subject, my latest "possible" fix is, fully drain your phone out of juice untill it doesn't power up and charge it again.
it should work afterwards.
Click to expand...
Click to collapse
I did that and i'm so happy now, because the method works for me... Thank you
sent from my HTC One X straight from Denmark
For what its worth I've no issues and have tried to recreate this as I consider whether to return the phone due to screen flicker. Panasonic Gsensor calibrates fine and Elixir gives steady accurate sensor feedback.
Running latest update 1.28.401.9
I have HTC 3 finger gestures off (except one middle one and a v-sign for launching a flagship product with so many issues.)
Sent from this place to that place using the power of shattered dreams and childrens tears.
Hello Forum,
seems that my DHD has an irreparable error.
But i've still a little hope that maybe someone of you guys out there can point me into the right direction to repair the phone again.
What happened:
on December, 20. for no apparent reason the Display started flickering approximately 2 cm from the top.
The upper Part (the first 2 cm from the top of Display) was showing the normal Picture, on the lower Part the Picture was flickering at irregular time intervals, but the touch gestures were still working without any Problems.
Setup at that Time:
- Latest 4ext Touch Recovery
- Latest MIUI.us Rom by bliind
- Custom DPI set to '190' (with ROM Toolbox)
- Max CPU Speed set to 1200 Mhz (with Set CPU)
(Had this setup working fine without any issues for approx. last 2 Months...)
Last change i did before the error occured: Set Custom Boot Animation with Rom Toolbox
The Flickering started not immediatly after setting the new boot Animation but i think 2 days and some reboots later...
Actions that i've already tried to solve the Problem:
1. Shut down the Phone, pull out the Battery, wait some Minutes, reboot the phone.
-> The flickering was gone and the Display looked normal after reboot.
2. After some time I took the Phone out of my pocket and the flickering was there again like before.
Tried to set DPI back to original value '240'
reboot the Phone
-> The Flickering still was there and it seemed to me that the responsiveness of the touch was slightly slower than normal.
3. Reboot into Recovery
Nandroid Backup all Partitions to SD-Card
wipe all partitions except SD-Card
new, totally clean flash of latest MIUI.us Rom by bliind
Reboot the phone
-> The flickering was gone; responsiveness of the screen normal as it was always before.
4. restore all apps; put the phone on the charger over night. everything worked fine again.
on the next Morning this strange flickering was there again; the Touchscreen was very slow responsive in the flickering area
Managed once more to reboot into recovery, but the flickering was now even in the Recovery and on the boot screen.
-> The Touch got more and more unresponsive.
Could no more start a new ROM flash out of Recovery.
5. Tried to access the phone via aahk tool and restored last stock ROM
-> After Reboot the DHD vibrates (like it usually does for startup)
the screen shows a bunch of black and white Stripes that chnge their Color when the Boot Animation should show up,
and later again when the lockscreen should appear.
It makes the boot jingle and i can send Commands via adb.
but Touch commands doesnt work, (tried to put in the Pin blind, but it shows no reaction)
Stupid, but I can't change it: my Warranty and the extra Insurance that i purchased for the DHD ended just 2 weeks before on 6. December.
6. Disassembled the whole phone with Help of you tube disassembling Guide, carefully cleaned all contacts and assembled it again.
-> nothing changed; same behavior like before disassembling.
What can I do? Any ideas except of small rasping and stirring into the soup? :crying:
Can it be only the display? Maybe the Graphic Chip?
Any other ideas?
thank you for reading this all and i appreciate any suggestion that might give my DHD a new spirit of life
Greetings from Cologne
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
bananagranola said:
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
Click to expand...
Click to collapse
Thanks for your reply!
That was the same what I thougt after disassembling and cleaning with no result.
Cause it seems to me that the Display is still working, but the Signal that's coming in is broken.
I alsready supposed that the Graphic engine is broken.
Just had a little Hope that someone might had the same Problem and got it solved,
before I start practice for mobile phone throwing competition...
i suggest another ROM JB used to cause my DHD flickering (earliear versions)
My DHD was with same problem 1 year a go, and that usually happen when i played games like Angrybirds or Asphalt, or when the device temperature was high.
I was worry at that time, thinking that the device was gone.
Take the same solutions that you had (except disassemble the phone) but they're only temporary.
By that time i decide root the device and install a new rom, (nothing to loose had i think) and Revolution HD was my choice.
After that my DHD didn't flick any more.
I didn't ever know what was the origin of that flickering but for me, that was the big solution.
I'm using Viper Venom 1.2.3 for now, and still with no flickering insues.
So, my advice for you is... give a try to other rom's and kernels, maybe you resolve your insue has i did.
Good luck with that.
Sent from my HTC Desire HD using xda app-developers app
Thanks for you Answers guys,
the Problem i have is, that my DHD does show only sripes even if I try to boot into Recovery, I can't see anything and am not able to start a flash process...
cause i have installed 4ext touch recovery i need the screen to wipe and flash a new ROM.
But i will try to flash an CWM - Recovery through ADB and then to start the flash Process blind by tapping the buttons...
let's see what will happen. There's nothing to loose...
For now, cause I was sitting without a mobile phone at all, I've ordered a cheep one from Amazon... - Huawei U8510 (Ideos X3) -
And oh WONDER!!!: I've got a fully functioning phone with CyanogenMod 7.2 and all the stuff i use my phone for is working without any Probs..
And the whole thing has 2 years of warranty at a cost of € 80,-
only the Display for my HTC would cost € 40,-
so I'm thinking of selling the broken phone on ebay and let anyone try to repair it who is able to....
but I will give it a try to flash another ROM.
Already downloaded the JellyTime R30...
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
It seems to be broken since today morning. I wiped the phone and restored the backup I made the afternoon before, and then the first vertical stripes occured. I wiped it and flashed the same rom (CodefireX 4.2.1) again. Same issues. Now I tryed to flash a GingerBread Strock Rom. Even the same issues, and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Stupid situation, today my Warranty ended.
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Thanks in advance!
daniel_DHD said:
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
[...] and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Click to expand...
Click to collapse
Seems to be the same like my DHD. But for me it ended up 2 Weeks after end of Warranty!
daniel_DHD said:
Stupid situation, today my Warranty ended.
Click to expand...
Click to collapse
The T-Mobile Customer Support told me, that they would have accepted the case as Warranty, if my DHD had ended up during the first week after End of Warranty. Don't know where you bought yours, but maybe there's a small chance for you to get Warranty Support through their obligingness.
If I were you I would try this...
daniel_DHD said:
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Click to expand...
Click to collapse
If your dealer don't accept your Warranty Call, I can't give you much Hope... Sorry for you...
... would imagine you should look for a new phone...
That's what I did....
Similar problem
I have also got a similar problem. Had my phone for two years and have also just hit the same problem. Flashed a new ROM, everything was working fine, then all of a sudden top half of the screen is displayed correctly, the bottom half is always flickering. This occurs in the bootloader as well. Anyone would think that HTC decided to make sure the phone only works for two years and a few weeks after the warranty expires to make sure it experiences problems.
Hi everybody! I open this thread because I have a problem that I can't resolve: months ago I switched to CM 10.1 from stock ROM and I had that since 2 days ago (when arco68 told that soon he wouldn't develop this ROM for this phone anymore). So I had CM 10.1 alpha1 to alpha6, but my problem started from alpha3: in fact when I installed this release my camera starts shutting down the phone when taking pictures with flash (no matter at what resolution pictures where taken or if the flash was automatic or permanent), but only with battery under about 80% and it didn't appened when the phone it was in charge. So I read a lot of posts where people said it was a battery problem: since mine was one year old and it was rounded I replaced it with a new original one. Unfortunately the problem persisted, so I posted this problem in the thread relative to CM 10.1 ROM and I realized that other people had this problem, except that a lot of them resolve it buying a new battery (LIKE I DID!). So I waited for other releases with the hope it was a ROM problem...since Alpha6, when I realise that it wasn't resolved. So I decided to change ROM to see if it was a ROM problem and I installed a GB-based ROM: Mission ROM. But when I went to camera to take a picture with flash it appened again. So I wanted to know if it was a custom-ROM problem and I reinstalled STOCK ROM from the NANDROID BACKUP I made before installing CM 10.1. Unfortunately the problem continues to persist and it's strange, because It didn't happen before in my stock ROM. The only thing I think It could be it's that the flashlight installed on CM 10.1 broke the LED circuit because I try the full power option (or something like this, I can't remember) and there was a warning. But the strange thing is that I tried with all the 3 ROMs to keep LED on with a widget and the phone never shut down, no matter what was the battery percentage. So I wrote this post to ask someone if there is a reason for this strange behaviour and if it is a solution.
Thank you all
yesterday, i faced this problem, but my rom isnt cm10 by arco, my rom is simplified GB with s3 looks v2
at first i was shocked, and then i try to flash back into stock rom, and the LED works fine
my advice is you must flash your w into another cusrom or even stock rom and wait for the dev's solve this problem
Sent from my GT-I8150 using xda app-developers app
Unfortunately I have already tried 2 custom ROM, and now I have recovered my stock ROM and the problem isn't gone...
me too sometime face same problem !! in more roms not one or too !
There are new develops! Today I noticed that the phone shuts down when taking pictures with flash only if the brightness of the display is over 50%: under this value taking pictures with flash don’t cause the phone to shut down. So my question is: how is it possible? It’s an hardware problem or maybe a firmware one?
Trying to answer this questions I have decided to make an hard reset of my phone, but I read that when the phone reboots after the hard reset it asks an unlock code. I have no idea of what code is this, so I want to know if this is true or not, and if it’s true how can I have this code before making an hard reset?
elettrotanzboy said:
There are new develops! Today I noticed that the phone shuts down when taking pictures with flash only if the brightness of the display is over 50%: under this value taking pictures with flash don’t cause the phone to shut down. So my question is: how is it possible? It’s an hardware problem or maybe a firmware one?
Trying to answer this questions I have decided to make an hard reset of my phone, but I read that when the phone reboots after the hard reset it asks an unlock code. I have no idea of what code is this, so I want to know if this is true or not, and if it’s true how can I have this code before making an hard reset?
Click to expand...
Click to collapse
using CM 10.1 Alpha 6 , i found ur right about taking pictures with flash will turn shut the phone down if the brightness is high , u shall report that problem at the cm10.1 troubleshooting thread to get more testers for it
If you already changed the battery, maybe it's the jack that link battery to the phone...I think so cause you said that when under charge the problemdoesn't happen (because the phone take energy from the charge and not from the phone)...take a look over there...surely it's a mechanicalissue, not roms issue...
jam90 said:
If you already changed the battery, maybe it's the jack that link battery to the phone...I think so cause you said that when under charge the problemdoesn't happen (because the phone take energy from the charge and not from the phone)...take a look over there...surely it's a mechanicalissue, not roms issue...
Click to expand...
Click to collapse
ok, but I don't know how to resolve this issue...I will try an hard reset...I think cyanogenmod wrote something in the firmware of the camera that is still present...with an hard reset maybe the firmware will be reset to stock...
mosta_9741 said:
using CM 10.1 Alpha 6 , i found ur right about taking pictures with flash will turn shut the phone down if the brightness is high , u shall report that problem at the cm10.1 troubleshooting thread to get more testers for it
Click to expand...
Click to collapse
I reported this issue in the tread, but many people answer to me that it may be a problem of mine only...
Ok, I think I'll do an hard reset. Is there something to know before doing it (like codes to reactivate the phone, etc.)?
i think is battery....because when the phone is fully charged (or with anoter battery) when shutting photo with flash it stay on
why?
while taking the picture (camera+cpu+ flash (more power than torch) +screen ecc..) the battery voltage drops suddenly if it is damaged and this drop can swich off the phone
darix96 said:
i think is battery....because when the phone is fully charged (or with anoter battery) when shutting photo with flash it stay on
why?
while taking the picture (camera+cpu+ flash (more power than torch) +screen ecc..) the battery voltage drops suddenly if it is damaged and this drop can swich off the phone
Click to expand...
Click to collapse
yes, but my battery is new and original...I can't explain this!
This is the weirdest behavior I have ever noted from my device. I am on the LG E975 with CyanogenMod 11 M7 release. I installed it the day it came out and it was working like a charm, no problem.
However, over the last three days I wake up every morning to find that my phone has a blue screen of death on. I am quite groggy at this point, os I haven't ever tried to read the BSOD (I'll try to tomorrow morning). I shut it down and it goes into the bootloader menu, where it asks me to choose between options like, Power Off, Fastboot, Recover Menu ... And then I can power on like nothing ever went wrong. I suppose its relevant to mention that while hitting the bed my phone is usually near a full charge (>75%) but not plugged in.
This hasn't happened during the day at all.
I do not remember installing any new apps over the last 2/3 days and the only thing that is different is that my phone is on roaming (in the same timezone).
I tried having a look a the logcat but I am no mobile device expert and the one I was able to get in the morning only contained logs from the reboot, so no information about the crash itself.. If anyone has any suggestion on how to locate the problem that would be great.
I really want to avoid a complete wipe. Thanks all.
[email protected] said:
This is the weirdest behavior I have ever noted from my device. I am on the LG E975 with CyanogenMod 11 M7 release. I installed it the day it came out and it was working like a charm, no problem.
However, over the last three days I wake up every morning to find that my phone has a blue screen of death on. I am quite groggy at this point, os I haven't ever tried to read the BSOD (I'll try to tomorrow morning). I shut it down and it goes into the bootloader menu, where it asks me to choose between options like, Power Off, Fastboot, Recover Menu ... And then I can power on like nothing ever went wrong. I suppose its relevant to mention that while hitting the bed my phone is usually near a full charge (>75%) but not plugged in.
This hasn't happened during the day at all.
I do not remember installing any new apps over the last 2/3 days and the only thing that is different is that my phone is on roaming (in the same timezone).
I tried having a look a the logcat but I am no mobile device expert and the one I was able to get in the morning only contained logs from the reboot, so no information about the crash itself.. If anyone has any suggestion on how to locate the problem that would be great.
I really want to avoid a complete wipe. Thanks all.
Click to expand...
Click to collapse
Leave a logcat here so i can help maybe.
Do you undervolt your cpu frequencys ? maybe you do it too much, or maybe overcock too much.
Also is a good idea check your app wakelock, maybe some wakelock is causing this, some app.
nch26 said:
Leave a logcat here so i can help maybe.
Do you undervolt your cpu frequencys ? maybe you do it too much, or maybe overcock too much.
Also is a good idea check your app wakelock, maybe some wakelock is causing this, some app.
Click to expand...
Click to collapse
Hey,
Can you tell me how to retrieve my logcat? The one I was able to get is from the reboot in the morning.
I haven't ever played around with any sort of overclocking so that can't be it.
Can you also tell me a little more about app wakelock?
Thanks
[email protected] said:
Hey,
Can you tell me how to retrieve my logcat? The one I was able to get is from the reboot in the morning.
I haven't ever played around with any sort of overclocking so that can't be it.
Can you also tell me a little more about app wakelock?
Thanks
Click to expand...
Click to collapse
With this you can get Logcat.
http://forum.xda-developers.com/showthread.php?t=1726238
Download wakelock detector from playstore and check how many times and what app are causing wakelocks.
Really without logcat of reboot is very hard to say.
Anyway a hard reset should fix this..