first, sorry for my english
Camera Flash does not work with any ROM...
I tried all the ROMS available ... stopped working after the Chinese ROM Froyo 2.2, But now no longer works with any ROM, or 3.4.2 UK or Roms Eclair etc...
But I can not access the Developer Forum, I've put it here ... I know there are more users having the same problem
Repeat, sorry for my english and Thanks for the Help.
I have exactly the same problem. Since china 2.2 sbf and rom, every rom and firmware exhibits the flash either not working on apps, or is out of sync with a blue tinge. I've tried every combination of fixes out so far, but nothing works. Will keep trying things out and post here if I find anything.
Sent from my MB525 using XDA App
Foxhound.kl said:
I have exactly the same problem. Since china 2.2 sbf and rom, every rom and firmware exhibits the flash either not working on apps, or is out of sync with a blue tinge. I've tried every combination of fixes out so far, but nothing works. Will keep trying things out and post here if I find anything.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yes, I saw in the other section you had the same problem .. several days trying things and more things, and ROMS of all types, but does not work any ways ... will have been spoiled by Hardware? coincidence as the Chinese Rom
On me, the flash does not work none time, only a very small light blue-green
If you find anything, any minor detail, let me know please.
Thanks
I have to test more, but mine has low light and light borders are greeny.
Sent from my Defy using Tapatalk
Have the same problem. Flashed the chinese rom just a few days ago following a guide and the flash is now weak and greenish even when I'm back on my stockrom.
Whats strange is that I tried this rom following a guide several weeks ago, flashing only the 2.2 bootloader and using a nandroid backup. The flash just worked one time, so I went back to my stock rom, 2.21, again and the flash worked as before.
I think I have tried flashing the whole chinese rom and then gone back to stock with no prob before also. It was just this last time the flash stopped working as it should, no matter witch safe rom I now flash again.
I have tried the uk 2.2 with dowgradebility to get the flash working as explained by Higgsy but no go.
The only thing I can think of is that when you try to use the flash to many times when you are on the chinese froyo rom the flash gets damaged somehow.
Sent from my Defy
Did you guys notice that there's a black or dark yellow spot in the middle of the flash light? Many people who had this weak green light problem reported that their flash lights are like so because it's been burnt.
mimel said:
Did you guys notice that there's a black or dark yellow spot in the middle of the flash light? Many people who had this weak green light problem reported that their flash lights are like so because it's been burnt.
Click to expand...
Click to collapse
Looking at the LED, there's a slighty darker yellow spot in the middle, but not that dark, just a slight shade above the outer part. Not sure if its burnt out to be honest, becasue when the flash does work, its pretty bright and lights up what i'm pointing it at, but the moment the camera captures the image, the flash is already off, so its just not in sync with the image capture. The blue/green tinge comes after the bright flash, just as it ends. Can you tell me where the burnt out LEDs are being reported mimel?
I have it all yellow, I no see black spot.
Since the Chinese Rom, did not run the Flash, no weak, no strong, not be in sync, none of this, only not work, only shows a very very small light blue-green.
I would like to see a picture of a burned Flash.
Thanks for all the help and sorry for my English.
Yours probably is not burnt and might get back to normal by flashing the latest T-Mobile or uk sbf.
A burnt flash light can flash everytime but with very weak white light and ends with green/blue. It's unrecoverable even upgraded to the latest sbf or downgraded to 2.1.
Foxhound.kl said:
Looking at the LED, there's a slighty darker yellow spot in the middle, but not that dark, just a slight shade above the outer part. Not sure if its burnt out to be honest, becasue when the flash does work, its pretty bright and lights up what i'm pointing it at, but the moment the camera captures the image, the flash is already off, so its just not in sync with the image capture. The blue/green tinge comes after the bright flash, just as it ends. Can you tell me where the burnt out LEDs are being reported mimel?
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
mimel said:
Yours probably is not burnt and might get back to normal by flashing the latest T-Mobile or uk sbf.
A burnt flash light can flash everytime but with very weak white light and ends with green/blue. It's unrecoverable even upgraded to the latest sbf or downgraded to 2.1.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
It is not my case, I have tried all the ROMS and does not work .. do not see any white light, only a very very small light blue-green.
I tried all the ROMS, I have the UK currently 3.4.2, but I also tried the T-Mobile and earlier ones, spent several days doing tests ...
I had the similiar trouble, only first flash and then a reboot was needed. Finally I managed to have normal flash.
What I did?
It is not just sufficient to flash another rom, but to meticulously follow a recipe. In this case I went from 2.21 Stock Rom Central Europe to 2.34 JIT Version, flash still normal. Then Chinese 2.2 ROM, flash only at first time, then reboot needed. I went back to 2.34 JIT Version, flash normal again. Then after a while when the UK 2.2 version came out, I still waited till Higgsy found out how to circumvent the flash troubles: http://forum.xda-developers.com/showthread.php?t=934366
It is for all people who never flashed a non downgradable 2.51 UK Version.
Just follow meticulously every step in Higgsy thread. If flash is working, please inform us here we also need positive affirmation
vince89 said:
I had the similiar trouble, only first flash and then a reboot was needed. Finally I managed to have normal flash.
What I did?
It is not just sufficient to flash another rom, but to meticulously follow a recipe. In this case I went from 2.21 Stock Rom Central Europe to 2.34 JIT Version, flash still normal. Then Chinese 2.2 ROM, flash only at first time, then reboot needed. I went back to 2.34 JIT Version, flash normal again. Then after a while when the UK 2.2 version came out, I still waited till Higgsy found out how to circumvent the flash troubles: http://forum.xda-developers.com/showthread.php?t=937319 In the meantime, this thread is altered again, from a full stock 2.2 UK version do a deblured variant but I believe it still works as a remedy for flash troubles.
It is for all people who never flashed a non downgradable 2.51 UK Version.
Just follow meticulously every step in Higgsy thread. If flash is working, please inform us here we also need positive affirmation
Click to expand...
Click to collapse
This process of Higgsys has been followed many times by myself, and I still have this flash issue. Problem is that when 2.1 firmwares are flashed via RSD Lite, the flash issue remains, and not working as usual as you and Higgsy have described. I'm going to try to uninstall the windows drivers and RSD Lite, reinstall these fresh, and then start the whole process again to see if that makes any difference.
Sent from my MB525 using XDA App
In my case, I have the ROM 3.4.2 UK and this ROM is not "downgrade" but I followed the steps of Higgsy and I do not work, I think my case is different from yours and my Flash is Burnt ...
Thanks for you help...
I think it must be burnt as I have never used the camera flash fixes in some of the ROMS when the camera flash was dodgy and now I am higgsys 3.4.2 ROM and all is good. Cheers
Ok, so I'm still facing this problem on my phone where the camera flash is either out of sync, which flashes brightly too early before image capture, and takes the picture as if no flash was on at all. This occurs on all camera apps on all ROMS installed will all methods, and the flash doesn't work at all on any flashlight apps.
After doing some research, I have found similar issues on other motorola phones, which may or may not help in this regard.
There seems to be a cutoff to the flash reported on Droid phones, either disabling or weakening the flash if the battery threshold is below 30-40%. When the phone has a higher charge than 30-40% or is plugged in to charge, this has eliminated this problem. It seems the driver to the camera flash can determine what your battery level is, despite what your phone is reading out, so if your reading is inaccurate, the flash will cutoff or weaken if below this threshold.
To solve the battery indiactor inaccuracy, follow the steps in the link below using ADB or Clockwork recovery to reset battery stats. Instead of turning off the phone when instructed, take the battery out of the phone for 10 secs and put back in for good measure;
http://androinica.com/2010/02/11/tip-how-to-fix-your-androids-battery-issues-rooted-devices/
Don't know if this will work for people with the flash problem on the Defy, but its worth a try. I haven't tested this. I will later and report back.
I was thinking about the build prop as well, as this seems to feature some lines pertaining to the flash intensity, as quoted by mflich in another post;
mflich said:
hi
i have a defy with 2.21_UK.And when i saw this patch i decide tu up to 2.2_Chinese.
but when i finished it the flash just worked at the first time of reboot
so i want to patch it but i can't enter the custom recovery(at that time i didn't know it's because of USB debugging)
and then i flashed 2.51_UK. but the flash didn't work too.
at this time i can only recovery 2.2 or flash 2.51 and the flash works with low intensity in green light
i noticed that the flash fix is some file in system and i can't read the file with .so
but i found that in build.prop there was some line like this:
ro.media.capture.maxres=5m
ro.media.capture.flash=led
ro.media.capture.classification=classH
ro.media.capture.flip=horizontalandvertical
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
but in the same file in 2.21 there are the only two lines:
ro.media.capture.maxres=5m
ro.media.capture.flash=led
so i guess it's because of the differents in this file my flash doesn't work
and the num 41 25 means 41% and 25%?
and what does the classification and flip mean?
with this can i make my flash work again?
sorry for my poor english
Click to expand...
Click to collapse
Can anyone else with flash problems see what is stated in their bulld prop lines for the flash? Maybe we can alter some values to solve our problems?
My flash dont work on today, But I dont have problems synchronizing or low light intensity, light Does Not Work, That appears on the flash is so so small That Is Not Appreciated in a dark room completely.
I think there has been "melted" FlashLED, this strange yet it seems that happened to me when I put the Chinese ROM Froyo and since then no work with any other ROM.
If I indicate that I can do tests to try to fix it, I will.
EDIT: Where are these lines? as I can watch them?
Sorry for my english!!! ... and thanks for the help!
Darkcaptain said:
EDIT: Where are these lines? as I can watch them?
Click to expand...
Click to collapse
You need the PropEditor-0.3.apk from the follwoing link. Be really careful with this, you can modify your system files and possibly brick your phone. Make a backup of your .prop first in this app before making any changes.
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
I have the same issue with the flash that you, Foxhound.kl. I found a temporal solution to the desync. I turn on the led with the tesla app, and then i launch the camera with the auto-flash enabled.
After the first photo the led is turned off, but the tesla app keep running in the background and some way make the flash to be sync and work properly in the other photoes.
Sry for my english.
Appears to me the same thing:
ro.media.capture.classification=classH
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.flip=horizontalandvertical
ro.media.capture.maxres=5m
ro.media.capture.panorama=0
ro.media.capture.shuttertone=1
ro.media.capture.torchIntensity=25
Click to expand...
Click to collapse
ro.media.capture.classification=classH
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.flip=horizontalandvertical
ro.media.capture.maxres=5m
ro.media.capture.panorama=0
ro.media.capture.shuttertone=1
ro.media.capture.torchIntensity=25
I also have these same values.
Related
My camera stopped working after flashing Leedroid 2.2a! I have been using RCmixHD for the past 10 days and after reverting back to my old rom it doesnt work anymore! I've tried switching sd cards erasing everything, I also make sure to wipe before flashing. Any help on this? Everything works except the camera, I'm trying some other roms at the moment and will update asap.
*I've tried loading a different version of Leedroid and opendesire and it still doesnt work! Camera just initializes but I am greeted by a blank screen!
Anyone that can help me??? I am getting mighty desperate. Could it be a possibility that the camera is broken? Everything else is working just fine.
I’m not sure it's your ROM mate. I reckon the camera's gone. As long as you fully wiped and the camera isn't working on any ROM I cant see how it can be a software problem?
Have you retried flashing a new radio?
Tried reformatting the sd card and removing partitions. The last time my camera worked was before I tried out the new sense roms 2 weeks ago lol
Will try to flash a new radio, I guess that's the only thing I haven't done since I've tried with a new kernel.
Just my luck
I have a sneaky feeling it could be the radio? I can't see if you haven’t dropped it or anything, why the camera would suddenly break. I also can't see how a ROM could break it either but hey... fingers crossed.
Should be radio related. Flash the couple of radios
7pellc said:
I have a sneaky feeling it could be the radio? I can't see if you haven’t dropped it or anything, why the camera would suddenly break. I also can't see how a ROM could break it either but hey... fingers crossed.
Click to expand...
Click to collapse
Hmm, hope not...somebody will get a heart attack if we find out that custom HD roms can eventually break the camera : /
Sent from my HTC Desire using Tapatalk
OMFG! I just flashed 5.11.05.14 and it still doesn't work ( I am running out of ideas now. I was running .23 prior...
Please help
The phone is running perfectly except for the camera, no hitches whatsoever..
OMFG again! I just flashed 5.09.05.30_2 and it worked but only for one time and when I relaunched the camera it doesn't work again! Why the F is this happenin to only my desire?! Mine is amoled unbranded and unlocked! Does anyone have any idea how this could have happened after running the sense HD roms?
(
kingofthebraves said:
OMFG again! I just flashed 5.09.05.30_2 and it worked but only for one time and when I relaunched the camera it doesn't work again! Why the F is this happenin to only my desire?! Mine is amoled unbranded and unlocked! Does anyone have any idea how this could have happened after running the sense HD roms?
(
Click to expand...
Click to collapse
Try flashing an official RUU, it may fix all the problems.
I hope it's not caused by the HD rom, because a lot of people will cry, including me.
anko184 said:
Try flashing an official RUU, it may fix all the problems.
I hope it's not caused by the HD rom, because a lot of people will cry, including me.
Click to expand...
Click to collapse
I've been messing around with RCMixHD 0.9a, attempting to use the camera too. Flashed back to stock Froyo with no problems.
I hope you get it working. Good luck.
Can you post a logcat report of the bug?
Do you know how to do them?
the same thing happened to me a few weeks back except the camcorder worked but the camera app froze the phone and it was the same on most new roms but i flashed the oldest official firmware i could find and the corosponding radio that i would have had at the time, then all worked again, upgraded everything and it worked fine, still dont understand what happennned tho :S if that dont work then i would prob recomend to unroot and do an official ota upgrade then re root maybe
I've tried reformatting the system from the recovery still no go. The camera and camcorder now works but no image comes out, just a black empty screen. Tried multiple radio with multiple rom combinations now. Will try to flash an official rom now..
Thanks for the input guys, keep'em comin!
BTW how do you flash official roms?
http://forum.xda-developers.com/showthread.php?t=695667
the rom and radio are both .exe files
upgret the radio it will work i was it too
DJHP said:
upgret the radio it will work i was it too
Click to expand...
Click to collapse
please read, hes tried that many times.
to RUU just boot to fastboot and run the exe from windows and wait patiently
I'm sorry I'm a noob. Do I have to adb or stuff? So I connect my phone, go to fastboot and then just launch .exe? That simple?
and do I run the gsm wwe edition first and then run the OTA update? or go straight to the OTA? or do I forgo the OTA update?
thanks guys!
Ok now this gets even stranger..
I was about to ruu the phone and everything suddenly started working again! I just took out the batteries, swapped SD's again, reformatted my old SD (for the gold card), put back my other SD and powered on. Everything works! 10 outta 10! I did not flash any radio or new roms since last night!
This makes me wanna sell my phone and get a new one! Any idea how this could have happened?
Hi!
First, I would like to give thanks to this thread http://forum.xda-developers.com/showthread.php?t=1317394 for a quick guide on rooting my new Samsung galaxy GT-I8150.
My problem
Because my device is now rooted, I was able to uninstall the built-in Music app using Super Manager. But before that I managed to backup the installer using Norton Utilities, the file is Music_1.1.1.apk. I did it on purpose because I thought I could install it back without hassle like other app on the market. Now my phone does not allow it to be installed anymore.
Can anyone help me on this?
Thanks in advance
Hi, may i know are you using stock rom?? If stock rom,all the program is odexed, and it cant simply put back. You should look for "system app remover" to do this,as inside got backup function.
Sent from my GT-I8150 using XDA
I did the same thing before with MyFiles on stock ROM. My advice is don't you ever look back or you need to reflash you phone.
Hello jamestts!
Thank you for your reply!
I'm new to android technology so forgive me I don't know what a stock rom is. But you mentioned about odexed. I noticed that every apk file on my /system/app has a corresponding odex file. Will that make sense?
Yes...if you r using stock rom,all the file is odexed. If u wanna get back ur music.apk,the best way is flash with odin 4.43 ,lower version might brick ur phone. Do some research be4 flashing. Be patient. If u wanna know which firmware u using now,you can dial *#1234# at dial pad. Then you can download ur firmware from sammobile.com . If u interested in custom firmware which is faster,u can always go to developer forum.
Sent from my GT-I8150 using XDA
I tried to flash my phone using Odin 4.43 with ASIA ROMS, and it was successful. The music app has returned to its place. Seems like I really had a hard reset of my phone. Thanks to you jamestts. But a new problem arises. Sometimes when my phone has returned from Idle, the display is messy. There's an intense brightness with vertical stripes on it. If I turn the display off and then on then suddenly the display is back to normal.
And I think the device volume becomes weaker, android version has been downgraded from 2.3.6 to 2.3.5
Any Idea on how to resolve this issue?
baldz said:
I tried to flash my phone using Odin 4.43 with ASIA ROMS, and it was successful. The music app has returned to its place. Seems like I really had a hard reset of my phone. Thanks to you jamestts. But a new problem arises. Sometimes when my phone has returned from Idle, the display is messy. There's an intense brightness with vertical stripes on it. If I turn the display off and then on then suddenly the display is back to normal.
And I think the device volume becomes weaker, android version has been downgraded from 2.3.6 to 2.3.5
Any Idea on how to resolve this issue?
Click to expand...
Click to collapse
U can simply use odin to flash the latest ROM. They are available in our forum and http://samsung-updates.com/gt-i8150-galaxy-w/
baldz said:
I tried to flash my phone using Odin 4.43 with ASIA ROMS, and it was successful. The music app has returned to its place. Seems like I really had a hard reset of my phone. Thanks to you jamestts. But a new problem arises. Sometimes when my phone has returned from Idle, the display is messy. There's an intense brightness with vertical stripes on it. If I turn the display off and then on then suddenly the display is back to normal.
And I think the device volume becomes weaker, android version has been downgraded from 2.3.6 to 2.3.5
Any Idea on how to resolve this issue?
Click to expand...
Click to collapse
hi there, glad you make it!!!
try install cwm recovery and wipe cache n dalvik cache then reboot. Try to do it twice and see how is it!!! remember is wipe cache and dalvik cache. DO NOT WIPE DATA....else it will factory default again!!
if after restart and still got the same problem, then i suggest restore to default.
OR change wallpaper!!!
it doesnt matter whether you upgrade or downgrade the firmware version. cause i have updated to newest malaysia version which is 2.3.6 then downgrade to cow firmware first version 2.3.5 .
try and see will solve your problem or not. cause i never facing this kind of situation. good luck to you.
I Immediately followed the link provided by yewsiong and flashed the latest firmware. I think my phone is more stable now, it's good as new.
Thank you guys for helping me out. I really learned a lot.
Thank you so much!!!
This site is cool...
Baldz
Hi all, And my apologies if i am posting in the wrong section.
i've been searching for the solution for my problem, and so far i cudnt find one.
My HTC works fine, no screen flickering nothing at all.
what my unique problem is that, as my htc reaches to 80% charge, it starts acting like its in a red area zone. it crashes. I switch it one, and as it loads back to lock screen, it crashes again, and again and damn again , untill i put it on charge.
Initially i thought its a software bug so
i rooted my cell, installed custom rom ARHD 6.0, (didnt touch my kernal)
i was happy with the custom rom, battery got better, device became more smooth. but as it reached to 80%, bang. crashed, and crashed after every restart.
i installed LeeDroid rom and confronted the same problem again.
My uncle bought this from UK and i live in Pakistan, so replacement is out of the equation. I am not sure what should i do, even if i give this for repair, what should i ask for that? battery?
i made a video of this, please help me out.
http://db.tt/cpicQdWh
guys, anyone?
If the phone did it out of the box running stock s/w and no other apps it's h/w. Since you're rooted and have played with multiple ROMs it's hard to tell. If I were you I'd go back to the stock ROM, not load any apps, and see if the phone still has the problem. If it doesn't it's something s/w related that you've done to the phone.
Moix123 said:
guys, anyone?
Click to expand...
Click to collapse
I assume there is no official HTC service center available there (as there is non in Iran) in that case I suggest you do this two things before testing local unauthorized repair centers.
1- Flash the latest franco kernel (I suggest franco cause I've tested it myself, you can also use any other kernel)
2- let the battery charge up to 100% and then go to CWM recovery and wipe battery stat
BarryH_GEG said:
If the phone did it out of the box running stock s/w and no other apps it's h/w. Since you're rooted and have played with multiple ROMs it's hard to tell. If I were you I'd go back to the stock ROM, not load any apps, and see if the phone still has the problem. If it doesn't it's something s/w related that you've done to the phone.
Click to expand...
Click to collapse
i was facing this problem when i was on stock. My phone had Vodaphone UK RUU.
i contacted htc, got the following reply
With reference to your query, please kindly update your phone to the latest software version since we have released a recent update which optimizes system performance as well as battery performance.
Meanwhile, you can also follow below steps to set your phone under safe mode for monitoring:
First verify that Fast Boot is not enabled, Settings > Power > Make sure Fast Boot is not selected. To enable safe mode:
1. With the device turned off.
2. Press the power button.
3. Once the device turns press and holds the volume down, once you see the splash screen.
4. Press and hold thevolume down button (DO NOT RELEASE THE VOLUME DOWN).
You will know it has worked because the device will give a brief vibrate or 3 quick vibes. Once it loads you will see on the “Safe Mode” on the bottom left of the screen. This disables all 3rd party apps and drivers from launching. Use the phone normally for 24-48 hours like this. Do not use 3rd party apps or install from the market or the test will be inconclusive.
If the issue will not occur under safe mode, please uninstall the 3rd applications.
Should the problem still persist when your phone is under safe mode, please kindly back up your personal user data and follow below steps to set your phone back to factory default settings:
Settings> Storage> Factory Data Reset".
but this happened on Safe mode too, so i decided to go and get replace by the market guy, but he ..... nvm
After that i switched roms and faced the same issue
srashedian said:
I assume there is no official HTC service center available there (as there is non in Iran) in that case I suggest you do this two things before testing local unauthorized repair centers.
1- Flash the latest franco kernel (I suggest franco cause I've tested it myself, you can also use any other kernel)
2- let the battery charge up to 100% and then go to CWM recovery and wipe battery stat
Click to expand...
Click to collapse
yes indeed this is the main issue,
i actually couldnt find franco kernel for htc =/ can u help me out with this, ( Thanks)
Moix123 said:
yes indeed this is the main issue,
i actually couldnt find franco kernel for htc =/ can u help me out with this, ( Thanks)
Click to expand...
Click to collapse
You find it in
Home> HTC One X> One X Android development
btw is this possible that my stats are incorrect, reason for asking is that. it shut downs like its out of power. and it takes ages to charge up completely even if its on 86%. I install franco, and now its on charging, it will take almost 2 hours plus to get charge completely.
I will post update after wiping battery state
Moix123 said:
Hi all, And my apologies if i am posting in the wrong section.
i've been searching for the solution for my problem, and so far i cudnt find one.
My HTC works fine, no screen flickering nothing at all.
what my unique problem is that, as my htc reaches to 80% charge, it starts acting like its in a red area zone. it crashes. I switch it one, and as it loads back to lock screen, it crashes again, and again and damn again , untill i put it on charge.
Initially i thought its a software bug so
i rooted my cell, installed custom rom ARHD 6.0, (didnt touch my kernal)
i was happy with the custom rom, battery got better, device became more smooth. but as it reached to 80%, bang. crashed, and crashed after every restart.
i installed LeeDroid rom and confronted the same problem again.
My uncle bought this from UK and i live in Pakistan, so replacement is out of the equation. I am not sure what should i do, even if i give this for repair, what should i ask for that? battery?
i made a video of this, please help me out.
http://db.tt/cpicQdWh
Click to expand...
Click to collapse
You should flash every ROM's specific kernel.
Sent from my HTC One X using xda premium
theDroidfanatic said:
You should flash every ROM's specific kernel.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
yes sir i did try that out too,
I flashed the kernel and i charged my battery to 100%
and tried battery stats wipe, still i am having same issue.
After installing ICS my P935 now resets randomly, seems to do it most when trying to install apps from the Google Play store and when I make settings changes. I don't have an SD card installed if that makes any difference.
Did you do a factory data reset when you updated?
Sent from my LG-P935 using xda app-developers app
It's been doin the same for me (Telus P935), I also did a factory reset and it was still doing it so I took out the SDcard, swapped SDcards, etc. But it hasn't done it today yet.
Well I went to Telus and sent it in to see if they can repair or replace it, it rebooted again today and it then got very hot but when I pulled the battery and booted it up again, the graphics was all messed up and the colors were off, perhaps some damage to the GPU. I had no problems with this before updating to ICS... I wonder because I looked around the net and a few people are having problems too.
funny I have no problems. upgrade was flawless.
Sent from my LG-P935 using Tapatalk 2
I have also had problems with my nitro rebooting a few times a day ever since installing ICS.
I think reboots and other things are not problem of installing Android 4
I've also had this problem, except with my bell optimus Lte, and its quite annoying as it randomly happens while I'm doing something with my phone.
Sent from my LG-P930 using xda app-developers app
I have the same problem, try a hard reset, but the problem remains ...
Someone solved it? or how to do a factory reset to uninstall ICS?
There's no solution for this problem. And if you will flash another rom or another official software, no matter GB or ICS , the problem will stay. I don't know what happens, but updating creates some error, possibly in hardware.
And you know, I am really disappointed with that. I had tried every rom, and all kdz software, downclocking, disabling tons of functions & options. Nothing prevents reboots. It freezes for a while and then reboots. In some roms it can shuts off instead of reboot. And that's it. The last chance I think is jtagg reflashing.
Sent from my LG-P930 using xda premium
I had same random reboot & sleep death problem after performing unbrick.
I tried several times of unbricking to correct this and installed GB & ICS, almost every CWM Rom without sucess.
Finally, I tried v18f.exe version when my phone was in download mode.
After that, I havn't had any single reboot or sleep death. I'm currently using v20c without CWM.
What I did was:
1.Install V18f leaked version in download mode.
2.Root with TPSparkyRoot_ICS
3. you can stay with v18f if you like, but I prefer to go v20c using "dd if sdcard boot.img .....method.." with v20c img file.
In my opinion, unbricking with korean rom may have some compatibility problems in some area besides boot, recovery, firmware, band, system partitions at least in my phone.
Becasue before I perform unbrick with korean rom, I never had reboot or death problem with Ho-no bell rom, kernelpan1c, cm9 and p936 rom.
Anyway, after install v18f.exe, my phone is perfectly okay.
I hope this help some of you suffering from random reboot.
Edit: Content obsolete. My 'solution' is posted in reply #72 in this thread.
baseband?
normaaaan said:
When I upgraded my P935 to ICS the official way, the rebooting started.
Got annoyed and went through the (incredibly painful for me) unbricking process with the Korean ROM. Still rebooted.
Went to CM 10 nightlies. Still rebooted.
Went to CM 9.1 stable. Still rebooted.
Flashed the Bell v11a baseband from http://forum.xda-developers.com/showthread.php?t=1842763 . No more reboots!
I'm afraid to touch the thing now ...
Click to expand...
Click to collapse
What steps did you do exactly?
Edit: Content obsolete. My 'solution' is in post #72 in this thread
Problem Solved!!!
hhhmmk said:
I had same random reboot & sleep death problem after performing unbrick.
I tried several times of unbricking to correct this and installed GB & ICS, almost every CWM Rom without sucess.
Finally, I tried v18f.exe version when my phone was in download mode.
After that, I havn't had any single reboot or sleep death. I'm currently using v20c without CWM.
What I did was:
1.Install V18f leaked version in download mode.
2.Root with TPSparkyRoot_ICS
3. you can stay with v18f if you like, but I prefer to go v20c using "dd if sdcard boot.img .....method.." with v20c img file.
In my opinion, unbricking with korean rom may have some compatibility problems in some area besides boot, recovery, firmware, band, system partitions at least in my phone.
Becasue before I perform unbrick with korean rom, I never had reboot or death problem with Ho-no bell rom, kernelpan1c, cm9 and p936 rom.
Anyway, after install v18f.exe, my phone is perfectly okay.
I hope this help some of you suffering from random reboot.
Click to expand...
Click to collapse
You are right dude. I also had frequent reboot issue with ICS Roms. Then, I put the phone in download mode and installed v18f(exe). Amazingly, the phone is super stable now. Thanks a lot for sharing the info. Just a question : can I now flash CM10 over this? will it cause reboot?
still not solved: (
I try installing v18f on my Telus P935, this version: http://forum.xda-developers.com/showthread.php?t=1668476
looks good, but it follows restarting randomly, like the official version V20E.
anyone knows another possible solution? please
Rdelapaz said:
I try installing v18f on my Telus P935, this version: http://forum.xda-developers.com/showthread.php?t=1668476
looks good, but it follows restarting randomly, like the official version V20E.
anyone knows another possible solution? please
Click to expand...
Click to collapse
What Baseband is your phone showing in 'About phone?'
normaaaan said:
What Baseband is your phone showing in 'About phone?'
Click to expand...
Click to collapse
Baseband version
APQ8060/MDM9200
Sorry ...
Rdelapaz said:
Baseband version
APQ8060/MDM9200
Click to expand...
Click to collapse
Sorry, my apologies, I forgot how uninformative the stock display is.
You can get at what I was looking for by installing "System Panel Lite" (free) and looking under "Dev Info," and then the entry under "Fingerprint."
However, skip that and perhaps just go ahead and re-flash the baseband. I don't think it can hurt. Druminst has posted zips that install the basebands with ClockWorkMod at http://forum.xda-developers.com/showpost.php?p=30451467&postcount=1 You have to go to his "more extensive list" to get to the baseband_flashable_P930_ATT_V18f.zip file.
Hope this helps ...
normaaaan said:
Sorry, my apologies, I forgot how uninformative the stock display is.
You can get at what I was looking for by installing "System Panel Lite" (free) and looking under "Dev Info," and then the entry under "Fingerprint."
However, skip that and perhaps just go ahead and re-flash the baseband. I don't think it can hurt. Druminst has posted zips that install the basebands with ClockWorkMod at http://forum.xda-developers.com/showpost.php?p=30451467&postcount=1 You have to go to his "more extensive list" to get to the baseband_flashable_P930_ATT_V18f.zip file.
Hope this helps ...
Click to expand...
Click to collapse
A OK, thanks.
Well, I will try.
I'm on 100% stock. just rooted. the boot times are really long. I got really worried, so I flashed firmware and everything 100% back to stock. But the long booting times are still there. Just to be sure, I tried rebooting even before rooting (in case rooting was the cause :silly: ) but that wasn't the case. And yes, I have fastboot on.
Other than that, there is no anomaly, phone is working 100% fine, no overheating, no battery drain, nothing. I only had the phone for nearly a month before getting the update, so it might be just me not noticing reboots took this long before too?
Anyone else experiencing it?
Not sure if it's the same thing but I seem to have very long boot times now aswell. I was testing a GPE Rom for a while and went back to sense. Booting now takes at least 5 minutes. Just sits at the white HTC bootscreen until screen turns off and then it works fine. Going back to a GPE Rom seems to fix the problem
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Update your firmware and it should work. I have sprint so i was able to find the updated firmware through their forums. I originally thought they were bad flashes, but let it wait one time, it took almost 5 mins to load up. After I updated my firmware to the latest, it worked normally again with fast boot up. On a side note on 4.4.3 roms, I used to think my old bluetooth keyboard didnt work on aosp or gpe roms, and only on sense. Once I updated my rom to a 4.4.3 sense rom, the bluetooth keyboard stopped working on that too. Getting a new bluetooth keyboard today so I will test it out.
duckysempai said:
Not sure if it's the same thing but I seem to have very long boot times now aswell. I was testing a GPE Rom for a while and went back to sense. Booting now takes at least 5 minutes. Just sits at the white HTC bootscreen until screen turns off and then it works fine. Going back to a GPE Rom seems to fix the problem
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same here. I don't think its a problem related to hardware or software. Just, the boot time is longer. Just that. It is a very huge relief to know that someone else is experiencing it too. I've checked everything I can, and there seems to be nothing wrong while it takes long to boot. It doesn't effect the usage at all too. It isn't a bug, just a little annoyance in case you like devices to speedily boot up.
@memekmek Did that too. I flashed firmware, and everything thoroughly checking my procedure. Nothing seems to be broken anyway, I just wanted to check if others have it too or is it me?
Jamal Ahmed said:
I flashed firmware, and everything thoroughly checking my procedure. Nothing seems to be broken anyway, I just wanted to check if others have it too or is it me?
Click to expand...
Click to collapse
How do you flash firmware when you're not S-Off and do you already have latest firmware for your region (vodap something as I read in other thread)
ckpv5 said:
How do you flash firmware when you're not S-Off and do you already have latest firmware for your region (vodap something as I read in other thread)
Click to expand...
Click to collapse
I used the firmware provided by mike1986 in this thread http://forum.xda-developers.com/showthread.php?t=2696282 ... It said that if I have S-ON, I should at least not be able to brick my device...
[I'm actually a 1000% noob in tech, and wrote only what I thought I was doing. I'm sure I must've been wrong. your reply just actually makes sense!]. I didn't want to ask each question on each step, and not bother with my lack of knowledge so I tried to write as much as I understood myself.
I guess it means that my firmware flash was a failure, and that itself is the culprit That clears out a million of my worries.
A little selfish favor to ask of you. Can you kindly direct me to any carrier-specific firmware download place (If there's any!). I'll check it whenever vodap001 firmware comes.
Thanks