I have been having this issue for weeks now. Any time I try to turn on my bluetooth, it flashes on for just a split second, then turns right back off. I was able to pull some info from logcat, I don't know if it would be of any help but hopefully you all can help me figure this out. Thanks in advance!
Logcat seen here (quite long)
JustAk said:
I have been having this issue for weeks now. Any time I try to turn on my bluetooth, it flashes on for just a split second, then turns right back off. I was able to pull some info from logcat, I don't know if it would be of any help but hopefully you all can help me figure this out. Thanks in advance!
Logcat seen here (quite long)
Click to expand...
Click to collapse
What ROM and what kernel did you flashed?
FcoEnrique said:
What ROM and what kernel did you flashed?
Click to expand...
Click to collapse
That's the weird part, I'm only running stock right now. I was going to flash cyanogen later but this bluetooth thing started up and I'm not sire what caused it
JustAk said:
That's the weird part, I'm only running stock right now. I was going to flash cyanogen later but this bluetooth thing started up and I'm not sire what caused it
Click to expand...
Click to collapse
Rooted and unlocked bootloader? What method?
Freegee likes to mess with the bluetooth. There should be a bluetooth fix flashable zip in the freegee thread for the ls970. I don't know if you can flash it on stock so make sure you read thoroughly.
Rooted yes, unlocked bootloader no. I rooted with fiddy619's batch file.
I'll take a look at their fix. As far as bluetooth suddenly breaking, is there anything that typically causes this or that I can look into? I've checked over all my settings, and none of my apps seem to be interfering (as far as I can tell), and I can't make sense of the logcat, so Idk what else to look at.
JustAk said:
Rooted yes, unlocked bootloader no. I rooted with fiddy619's batch file.
I'll take a look at their fix. As far as bluetooth suddenly breaking, is there anything that typically causes this or that I can look into? I've checked over all my settings, and none of my apps seem to be interfering (as far as I can tell), and I can't make sense of the logcat, so Idk what else to look at.
Click to expand...
Click to collapse
Freegee is to unlock the bootloader, if you're not unlocked and did not use freegee then you have no need for the fix. Do you have a recovery installed? What one?
you should definitely read this thread and maybe complete the process. There are tons of roms out there an as long as you follow the steps in this thread, you shouldn't mess anything up.
http://forum.xda-developers.com/showthread.php?t=2050582
dopy25 said:
Freegee is to unlock the bootloader, if you're not unlocked and did not use freegee then you have no need for the fix. Do you have a recovery installed? What one?
you should definitely read this thread and maybe complete the process. There are tons of roms out there an as long as you follow the steps in this thread, you shouldn't mess anything up.
http://forum.xda-developers.com/showthread.php?t=2050582
Click to expand...
Click to collapse
Regarding Freegee, I saw that after responding and then felt quote stupid. But I'll probably be doing that soon now so I can get a properly working phone.
Thanks for the suggestion, I'll probably be doing this tomorrow and will update the thread when I do.
For those still subscribed to this, I solved the problem. I am using SmartApp Locker, and in the Settings menu under System Lock I had Bluetooth checked. This should only have been locked when the app locking service was turned on, but it was interfering with all usage of bluetooth with the app lock service on or off.
Related
This method is not perfect but if you need to return your phone then it should work. Once you do it, you will be 100% stock, but WiFi is broken as it causes power cycling. Not sure if the network issues I am having is from the restore either but signal seems good but won't let calls or texts come through as they should.
1. So what you do is take a flash-able ROM and remove the extras from the developer... sorry to all the devs but I am not knowledgeable in this department so I took one and stripped the zip.
2. Once you strip the zip of extras you take the system folder in the zip and delete contents... you just want to delete all folders except the system folder, leave anything else that ISN'T a folder then you take a system dump and paste it in the system folder inside the zip.
3. Now you boot into recovery and flash this just like you would if it hadn't been changed. Then you take the stock kernel and flash it via Odin... I did not let the phone power completely on until completing this last step, remember I am a noob so I have no idea if this is necessary.
4. Now you let it turn all the way on and you will see no yellow triangle on boot and you are at a completely stock ROM.
I hope this was helpful to get your phone returned
rayprobg said:
This method is not perfect but if you need to return your phone then it should work. Once you do it, you will be 100% stock, but WiFi is broken as it causes power cycling. Not sure if the network issues I am having is from the restore either but signal seems good but won't let calls or texts come through as they should.
1. So what you do is take a flash-able ROM and remove the extras from the developer... sorry to all the devs but I am not knowledgeable in this department so I took one and stripped the zip.
2. Once you strip the zip of extras you take the system folder in the zip and delete contents... then you take a system dump and paste it in the system folder inside the zip.
3. Now you boot into recovery and flash this just like you would if it hadn't been changed. Then you take the stock kernel and flash it via Odin... I did not let the phone power completely on until completing this last step, remember I am a noob so I have no idea if this is necessary.
4. Now you let it turn all the way on and you will see no yellow triangle on boot and you are at a completely stock ROM.
I hope this was helpful to get your phone returned
Click to expand...
Click to collapse
You're going to want to describe just a LITTLE bit more how you do #2 or else you're going to get a LOT of questions on how to do that...
My opinion, but this is going to cause a LOT of problems that you may not be prepared to help with.
jerdog said:
You're going to want to describe just a LITTLE bit more how you do #2 or else you're going to get a LOT of questions on how to do that...
My opinion, but this is going to cause a LOT of problems that you may not be prepared to help with.
Click to expand...
Click to collapse
Thank you for the advice i will fix that up when I have a chance
What is different about your "method" to the one offered on this thread: http://forum.xda-developers.com/showthread.php?t=1281287
Sent from my Samsung Galaxy S II Epic Touch 4G WTF BBQ
HondaCop said:
What is different about your "method" to the one offered on this thread: http://forum.xda-developers.com/showthread.php?t=1281287
Sent from my Samsung Galaxy S II Epic Touch 4G WTF BBQ
Click to expand...
Click to collapse
When I used that method I had the android splash screen no matter what, even when the phone was fully booted all you can see is that splash screen staring you in the face and taunting you telling you that you can't see anything on your screen but it.
This should not even be here.The other link above is better and way more eas for people.This should be removed.
With all due respect to the OP (who is genuinely trying to be helpful), I'm really concerned less-experienced users will wind up hosing their phones trying to follow this process.
If this breaks wi-fi and you cannot take calls or text messages why would anyone want to do this? Seems like you are giving up everything the phone is meant to do.
redram38 said:
If this breaks wi-fi and you cannot take calls or text messages why would anyone want to do this? Seems like you are giving up everything the phone is meant to do.
Click to expand...
Click to collapse
WiFi is broke... because it power cycles the phone. Calling and Texting works, just not like it should, it seems like the phone will only check for new stuff every 5-10 minutes. I only did this so that if you bring your phone back to sprint they don't question you if its rooted or not because as it sits, this way will not be detectable it just looks like your phone is messed up and they should replace it.
Deleted
sent from my SGSIISE4GT
rayprobg said:
WiFi is broke... because it power cycles the phone. Calling and Texting works, just not like it should, it seems like the phone will only check for new stuff every 5-10 minutes. I only did this so that if you bring your phone back to sprint they don't question you if its rooted or not because as it sits, this way will not be detectable it just looks like your phone is messed up and they should replace it.
Click to expand...
Click to collapse
Does your "method" resets the counter that indicates how many times the phone has been flashed with a custom kernel/ROM?
Will this method cure cancer?
sent from my Eptouch 4g
rayprobg said:
When I used that method I had the android splash screen no matter what, even when the phone was fully booted all you can see is that splash screen staring you in the face and taunting you telling you that you can't see anything on your screen but it.
Click to expand...
Click to collapse
Then you didn't do something right. Flashing the stock through odin brings your phone back to stock, no triangle at the boot, everything works. 100% stock, not 43% stock like your method.
geekaren said:
With all due respect to the OP (who is genuinely trying to be helpful), I'm really concerned less-experienced users will wind up hosing their phones trying to follow this process.
Click to expand...
Click to collapse
Thank you, I would have made this easier if I were a serious developer but I am a noob as I have been trying to make everyone aware, I only did it that way as an experiment to get completely stock and it worked to a degree so I hope someone can take what I did and run with it and make everything work
HondaCop said:
Does your "method" resets the counter that indicates how many times the phone has been flashed with a custom kernel/ROM?
Click to expand...
Click to collapse
Don't believe so, but as someone who works for sprint. No one should look there unless they are developers themselves
eagercrow said:
Then you didn't do something right. Flashing the stock through odin brings your phone back to stock, no triangle at the boot, everything works. 100% stock, not 43% stock like your method.
Click to expand...
Click to collapse
Again Me=Noob I am not a developer I was trying to be stock without having the "android" splash screen in my face when it shouldn't be because with the before mentioned method that is all I could see when booted up fully
Moving this to Q&A and closing. This is not needed and is not real development.
Hello all,
So I bought my HTC Wildfire S Virgin Mobile on black friday like everybody else. I waited a few days and then rooted. And then I had the brilliant idea to try installing the CM 7.1 Mod for it. And well, I didn't do a Clockwork Backup, and well, it didnt work very well. The phone got stuck on the HTC screen. So finally I installed a different ROM, JikantaruROM, and I managed to get past the bootscreen but I can't use my carrier anymore. So I was wondering if anybody could either tell me how to flash CM 7.1 Unoffical release to my phone, or if anybody knew a way I could get back to the original Virgin Mobile software. It seems that you have all the other stock roms, so I would REALLY appreciate if someone could share the Virgin Mobile rom too.
Thanks in advance,
Wieland959
Seconded. Although I think mine is in a slightly worse case; I kept flashing roms and ended up in a state where it turns on, screen remains black, then the phone vibrates three times and evidently does nothing. So Wieland959, I'd advise you to stop flashing until someone posts the ROM.
And if someone could let me know how to recover from my current state, I'd very much appreciate it.
thesnaz said:
Seconded. Although I think mine is in a slightly worse case; I kept flashing roms and ended up in a state where it turns on, screen remains black, then the phone vibrates three times and evidently does nothing. So Wieland959, I'd advise you to stop flashing until someone posts the ROM.
And if someone could let me know how to recover from my current state, I'd very much appreciate it.
Click to expand...
Click to collapse
Your in the same boat I was just in. My solution was to go back to radioshack with the receipt and tell them it just turned off and wouldnt turn back on. Just doing the 3 vibrations. I did spend hours trying to search about how to fix it, but I dont think theres a way unless you use a jtag hookup and some sort of fancy programmer.
@Wieland959, If you want. I just tried to do the OTA update through the settings on the phone itself. It would let me download the file(I believe it should be flashable through the cwm recovery), but when I tried to let the phone install the file, I would get the android with the exclamation mark after the reboot. Ill try to post here, if it will upload. But......
DISCLAIMER!!!!
I take no responsibility for anyone damaging their phone using the file here. This file, as far as I know, should only work with the Wildfire S Virgin Mobile USA CDMA model A510C as this is the phone the file was downloaded from.
Thank you for the file, but I couldn't flash it. What might work though, if you are willing is, if you have rooted your phone, to make a cwm backup and upload that here. From there I should be able to recover and then factory wipe my phone. But thank you anyways for the file. I will keep kicking until the phone doesn't boot.
How are you planning on restoring from backup if the phone doesn't even boot?
Sorry, I'm new to this...
thesnaz said:
How are you planning on restoring from backup if the phone doesn't even boot?
Sorry, I'm new to this...
Click to expand...
Click to collapse
from the recovery, by holding down the vol down button and power button. then select recovery.
also, im in the same boat as OP haha
Okay. I managed to boot my phone and am able to send/receive texts. The rom I used? http://forum.xda-developers.com/showthread.php?t=1367701] It seems to work pretty well. However, I would still like to have the original rom if someone could still upload it.
VM USA Stock Clockwork Backup
Well, I don't know much about stuff like this, but here is my clockwork mod recovery backup. It's just the stock VM USA w/HTC Sense. I have realized that I deleted the bloatware, so that's the only thing that isn't 100% stock. Hope it helps.
*Unzip the file before placing on you sd card. (Contains the clockwork folder, which contains the backup folder,and then the folder that contains the backup itself.)*
**!! Disclaimer! Please run the activate application upon installing as when you call voicemail, it will call my number. !!**
http://www.mediafire.com/?le6b07dwr865017
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Wieland959 said:
Okay. I managed to boot my phone and am able to send/receive texts. The rom I used? http://forum.xda-developers.com/showthread.php?t=1367701] It seems to work pretty well. However, I would still like to have the original rom if someone could still upload it.
Click to expand...
Click to collapse
Is this a good rom? I'm looking for some senseless roms that will work with our version of the WFS. will you post if you are able to go back to the Stock Virgin backup that I have posted? Also how much memory is on the rom that you posted?
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
BigChillin said:
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
Click to expand...
Click to collapse
Can I easily switch back to the stock rom via my backup? How do I install it. Sorry that i'm such a newbie. xD
BigChillin said:
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
Click to expand...
Click to collapse
I tried it and found my phone only had 75mb of internal storage available!!! Weird!!
Nevermind I figured out the problem. Ok. Just one question is there anyway I can get the nice clock back from the stock ROM?
Is anybody else having mms issues with the experimental ROM?
brandonhun said:
Can I easily switch back to the stock rom via my backup? How do I install it. Sorry that i'm such a newbie. xD
Click to expand...
Click to collapse
Thanks for the backup! It worked perfect for me!
would you mind if i posted the link on another forum? i know of a couple people looking for a backup aswell.
You should be able to switch back with the recovery no problem. Correct me if I'm wrong, but to install boot into recovery, install from SD, select specific, and select the zip of the rom. Also, I don't have my phone on me so the wording might be a little different.
MMS is a known issue with the rom from what I've read. I don't have it installed personally.
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Wieland959 said:
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Click to expand...
Click to collapse
Just a heads up wieland, when you get a voice mail and you try to check it from the notifications make sure it's your number, because I ended up giving brandonhun a call. Going through the activation app and rebooting fixed the problem.
djsquiggly said:
Thanks for the backup! It worked perfect for me!
would you mind if i posted the link on another forum? i know of a couple people looking for a backup aswell.
You should be able to switch back with the recovery no problem. Correct me if I'm wrong, but to install boot into recovery, install from SD, select specific, and select the zip of the rom. Also, I don't have my phone on me so the wording might be a little different.
MMS is a known issue with the rom from what I've read. I don't have it installed personally.
Click to expand...
Click to collapse
You can post it wherever you want. I'm glad I could help a couple of you!
ScottPomroy said:
Ok. Just one question is there anyway I can get the nice clock back from the stock ROM?
Click to expand...
Click to collapse
I haven't done this ROM change but if its the stock HTC Sense go to personalize and get HTC widgets (perhaps its get more HTC widgets) and you should find an update to the clock widget. That should give you the original clock plus a bunch more new ones.
Sent from my Transformer TF101 using Tapatalkd
Take another peek
Wieland959 said:
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Click to expand...
Click to collapse
Guess what just popped out of the Betty Crocker oven? As close as I could get to stock. Enjoy.
Rob
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.
mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!
cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:
cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.
g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks
abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
I have been using Cyanogenmod 11 Nightlies for my device for about as long as they have been out, so I know it is still a work in progress, and most of the issues I have faced have gone away as newer nightly builds have been released, so I have not reported any issues as of yet.
Within the last month or so, I have noticed a new issue. The mobile data has been randomly cutting out, allowing only emergency phone calls. It only goes out for about a minute or two, but it is still a huge inconvenience. It seems to happen randomly, except after I finish a phone call -- it almost always cuts out immediately after (very frustrating for when calls are dropped, because I need to wait a minute or two before I can call back).
Has anyone else experienced this or know of a fix? I just tried re-flashing the latest radio and that did not seem to help. I have also tried full system/data wipes as well and none of the Nightly builds for the last month or so have been able to fix it.
Thanks, everyone.
You need to flash any touchwiz rom in order reset your nvram.
Corvetrims77 said:
You need to flash any touchwiz rom in order reset your nvram.
Click to expand...
Click to collapse
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
pravus87 said:
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
Click to expand...
Click to collapse
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Corvetrims77 said:
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Click to expand...
Click to collapse
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
pravus87 said:
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
Click to expand...
Click to collapse
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Corvetrims77 said:
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Click to expand...
Click to collapse
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
pravus87 said:
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
Click to expand...
Click to collapse
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
mreadshaw said:
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
Click to expand...
Click to collapse
I actually did not use Odin at all. I was able to find a thread that posted a 4.1.1 stock .zip, a .zip to keep root, and a .zip to keep custom recovery. (I have tried searching for the thread to share with you but am unable to find it). I was definitely over-thinking it. Just install the .zips from TWRP or CWM as you would any other custom ROM -- just make sure you do not have the 4.3 bootloader installed. That's it.
Sorry for the delayed response!