Related
I have slide that random reboots like once a day for no apperant reason . Beed doing it since cm6.1.1 and now I'm on cm7.1 so would like to know what mightt be wrong... info : rom- cm7.1 / hotboot- 0.52 / latest radio / s-on .. if anyone can help I'm open ears
Sent from my T-Mobile G2 using XDA App
Any one with info on this your insight will be very helpful
Sent from my T-Mobile G2 using XDA App
can you give us some more info? like whether your phone's overclocked? to what frequency? what apps were running? etc...
Well I had setcpu on the cm 6:1:1 and clocked 768 I beleave it would run right then it would reboot like 2 times a day so I took of the oc and set cpu and the reboots were now random like once a day or one at all .. so jumped to cm 7:1 everything is good so I set the built in oc to 768 and it was fine till like with in a few hours it would reboot again reboots are random but like once or twice a day so removed oc and back to the stock and only once a day on none at all ... apps that I use the most and leave runinf facebook, voice, talk , sd-booster at bootup set at 1024, music most of the time, also advanced task manager by rechild, ... if more specific info is needed I'm be glad to give to help me get closer to solve the problem .. thanx
Sent from my T-Mobile G2 using XDA App
how about battery temperature? how hot does it get when you're using/not using the phone? also, by randomly reboot, does it reboot when you're using the phone or just whenever it wants?
Battery doesn't heat up at all so normal temp ... by randomly I mean when it wants.. it in the pocket and u just feel the buzz of the reboot .. again no oc and just like 3 apps running at most also have cache clener ng runing at 12hour intervolts ... also ran permistion fix threw rom manager but not sure if the fix will stick since its s-on
Edit : forgot to say wifi alway on even when sleep since the phone does not have a data plane
Sent from my T-Mobile G2 using XDA App
hm... idk but perhaps it's the wifi that's causing those reboots. then again, if you don't have data plan, not using wifi will just turn your phone into paper weight.
Would having it s-on be a issue in any way?
Sent from my T-Mobile G2 using XDA App
Not at all, I have S-ON and only have reboot problem occasionally when I use wifi, battery gets too hot, or something.
Oh ok ... so would their be a fix for the wifi cuz this is getting annoying I have reflashed like 5 times in hopes it was a bad flash.. and don't really see a big library of roms that ain't sense roms ...
Sent from my T-Mobile G2 using XDA App
I have had this issue with CM7 as well. Some nightlies are better than others.
To reproduce just keep toggling your wifi. Eventually the phone will reboot. I use to see "kernel panic" messages in the logcat file but the last time I captured logcat for this issue I did not see any message about a kernel panic.
Where would we post a bug for this?
ovar said:
I have had this issue with CM7 as well. Some nightlies are better than others.
To reproduce just keep toggling your wifi. Eventually the phone will reboot. I use to see "kernel panic" messages in the logcat file but the last time I captured logcat for this issue I did not see any message about a kernel panic.
Where would we post a bug for this?
Click to expand...
Click to collapse
Oh ok so wat u are suggesting it might be cm rom related issue ... would the wifi fix flooting around here help with the issue or have u tried the wifi fix ?
Sent from my T-Mobile G2 using XDA App
I have not tried the WIFI fix. I would be curious if other can get the reboot to happen by toggling WIFI repeatedly.
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...
Only for CM9 and CM9 based ROM users :cyclops:Did your phone just switch off and wouldn't turn on completely when turning on the bluetooth one day? :crying:
Do you really need your data/messages/settings/alarms/call log back? :crying:
Do you really need to access the internet or call someone urgently? :crying::fingers-crossed:!! HERE'S THE FIX !! :fingers-crossed:OK, So, it's actually not a fix but a way you could get back your precious messages (if there were any), settings, alarms, call logs, etc.. everything!!
It has happened to me the third time while using AOKP Milestone 6 for the HTC One V..
So one day you just turned on bluetooth and your phone got switched off and got mad . It started getting switched off within 10 seconds as soon as it started. You have important messages, etc. whose backup you don't have. You're going mad, you just don't know what you should do within those 10 secs.. DO THIS -
First, of all, I'm not any big man to even give out a fix or something.. But what I did really helped me to get back my data..
I was using CM9 UnOfficial for the One V and there came a bad day on which my phone entered a bootloop and I was ruined with all my customizations..
I loved CM9 so I tried AOKP Milestone 6 then...
Again there came to be a day when my phone started switching off as soon as it started within 10 seconds..
I had my Airplane Mode ON 'cause I was in my class and when I turned on bluetooth, my phone went mad.
In those 10 secs for which the phone was on, it was laggy, just preparing to shut down.
I saw that bluetooth was turned off when I pull the notfication bar down. Tried to turn it on, asuming it would solve the problem, but all in vain.
Then it was really important for me to call home due to some reason.
When I tried to turn off the Airplane Mode, the phone immediately got switched off again.
Then I did this :
1. Opened the dialer app.
2. Typed *#*#4636#*#*
3. The 'Testing' menu appeared.
4. Tapped on the 'Phone Information' option. (10 secs were about to get over)
5. Scrolled down and pressed 'Turn on radio' button.
6. BOOM! The phone didn't switch off again! -The Airplane Mode was still on, BUT I was connected to my EDGE Network and could also access the internet!
Then I could call / use the mobile for a while till I reached home.. I made a backup of several things on my phone using JS Backup.. Didn't dare to mess with the airplane or bluetooth buttons them.. Then changed the ROM when I reached home.
Oops..
Ohh .. Sorry moderators..! I think I started this thread in the wrong section.. Someone please move it to the 'One V Q&A, Help & Troubleshooting' section.
I'm not a CM9 user but congrats that you've found out a workaround for it. Something smels fishy in your problem cause no one reported this kind of behavior before and I am 100% sure that maxwen's work on both bluetooth and cm9 was flawless.
1ceb0x said:
I am 100% sure that maxwen's work on both bluetooth and cm9 was flawless.
Click to expand...
Click to collapse
Umm.. what do you mean by that? Is the Bluetooth problem fixed....? I'm on CM10 now just because of the BT Prob in CM9..
Sent from my One V using xda app-developers app
i mean that the problem is at your end1
Yea I never had a problem check kernel....
Sent from my One V using xda premium
cybervibin said:
Yea I never had a problem check kernel...
Click to expand...
Click to collapse
It really happened to me three times using 201212251747 HELLBOY Kernel.. Is the problem fixed now? It won't happen if you use Bluetooth occasionally.. I use it everyday and it always happened within 6-7 days. Them I had to again reflash the same or change the ROM..
Sent from my One V using xda app-developers app
Paresh Kalinani said:
It really happened to me three times using 201212251747 HELLBOY Kernel.. Is the problem fixed now? It won't happen if you use Bluetooth occasionally.. I use it everyday and it always happened within 6-7 days. Them I had to again reflash the same or change the ROM..
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I'll check if ur using the proper kernel once I reach home...yea I use it in the car for music and sending images and stuff
Sent from my One V using xda premium
cybervibin said:
I'll check if ur using the proper kernel once I reach home...
Click to expand...
Click to collapse
Thanks I'll not even waste a single second in turning to CM9!
Sent from my One V
hey guys i just flash the latest build(13/10) cm10.1(teamcanjica) i got a problem where sometimes i can't wake up my phone but with only lighted up black screen and softkey backlight but sometimes it can wake up but the moment i off my phone then on it, i only got lighted up black screen and softkey backlight, to solve this problem i had to press home or on and off button several times then it'll wake up, if it won't wake up i have to reboot it then set the screen timeout to 30 minutes
i'm sure this is not this build problem but my phone problem,i already wipe data,cache and dalvik cache but still doesn't solve the problem.I even download the build again and tried to flash it with wipe data,cache and dalvik cache but still the same.i hope you guys help me because this is really important to me:crying:
Does it occur on 17/10 release too? Does it also occur when receiving a phone call perhaps?
Sent from my GT-I8160 using xda app-developers app
ledjo said:
Does it occur on 17/10 release too? Does it also occur when receiving a phone call perhaps?
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
yes it occur on 17/10 also occur on previous build except 8/10 and no it doesn't occur during phone call. i even go back to stock jb and flash the latest build again but still doesn't solve the problem..
this happens to me too on a once a day basis, so its pretty rare TBH. what i dont understand is why many other users dont experience this
i just put it to sleep again and wait around 10 seconds.. thatll usually do the trick, and i also confirm it doesnt happen during a call
littledude072 said:
this happens to me too on a once a day basis, so its pretty rare TBH. what i dont understand is why many other users dont experience this
i just put it to sleep again and wait around 10 seconds.. thatll usually do the trick, and i also confirm it doesnt happen during a call
Click to expand...
Click to collapse
i thought i'm only the one who having this problem,i'm having this problem also on cm10.2 by teamcanjica but not cm10.2 by ekim.tecul on the general section(which i'm still using it)but then i having again this problem after flashed polishvodka fix for this rom
but i think i know what's the problem? i think its because of the kernel on ekim.tecul's CM use rootbox kernel and teamcanjica's use cm stock kernel. Of course this just a guess, and i'm a noob and know nothing about rom development
Can you tell me which screen driver do you have ? /sys/devices and tell me if you see s6d... Or ws2401 folder
Sent from my GT-I8160
Rox said:
Can you tell me which screen driver do you have ? /sys/devices and tell me if you see s6d... Or ws2401 folder
Sent from my GT-I8160
Click to expand...
Click to collapse
well I have s6d
fict said:
well I have s6d
Click to expand...
Click to collapse
I have this problem too.. but i haven't folders (s6d or ws2401). I have pri_lcd_ws2401.0 folder
Sorry by my english.
So I see that ı am the not only one who has that black screen problem. :S ı have s6d screen driver. I can say that it occurs on cm 10.2 or even cm 11 too.
Screen seems black but it works. ı mean, you hear that phone unlock and when you touch you hear that an app opened.
(at last build of cm 10.2 , I haven't experience that yet)
is it solved yet? my samsung galaxy ace 2 CM 10.2 experienced this problem too and i haven't found any working solutions , please help
plsss i need the solution for this problem. it's still happening in my ace 2
Ok, straight to the point..
I have an issue in making a call exactly
When I am trying to call somebody, sometimes the dialing window won't appear.
Ok, it finnaly appear, but it takes a long time
Also, when typing, sometimes it wont type anything
I think there is an issue with the keyboard, but with different keyboard, the issue still exists
Clearing app data wont help, because those issue happen sometimes and it working again a couple minutes later
Those issues happen almost in all ROM i've installed.
I wonder what the problem is ?
Is there anyone having exactly the same issue with me ?
Any suggestion would be highly appreciated :beer:
Sent from my GT-S5660 using xda app-developers app
Hey!
I've been having the same problem on stock rom and the only way that seems to fix it is just rebooting your device. When I run cyanogenmod for example the problem doesn't occur anymore
Yea man, I have followed your suggestion and now I am on GingerDX ported by oldDroid, looking if the problems occur again
what is your daily ROM anyway ?
I mainly use maclaw's cyanogenmod for my gio
And does the problem still occur?
not for now..
is that CM 9 RC3 by maclaw ?
I used that rom a year ago, before i realised there is a problem with netd process taking high cpu usage when not connected to a wifi
I prefer to use gingerbread ROM
I've been using Jellybean 4.2.2 (CyanogenMod 10.1) from maclaw since it came out and I haven't had alot of problems with it!