When NS is connected to my car audio system, it randomly disconnects and then re-connects after a few seconds.
This does not happen with other android phones I have tried.
I'm running AOKP ICS Milestone 6 rom.
Is this related to the radio(modem) being used or is it ROM related ?
I couldn't tell you what the issue is but you could try bumping your minimum cpu speed up. I've found in the past that seems to help with stability issues with bluetooth and gps sometimes. I've gotten to where I've basically given up on using bluetooth after having a lot of problems with it on 2 different phone models and multiple versions of android on each. Some people seem to run it fine but I always have issues. You could try a different kernel too.
Sent from my Nexus S 4G using xda premium
Related
My 3g always goes away and I have to cycle it in the pull down bar. It's not a huge problem but its annoying because it will always log me out of googl3 talk. Does anyone else have that problem. I've had it with every Rom I've tried. My phone also does random reset for no reason. Again I've had this problem with every Rom I have tried. Are these just known issues with the current radio are is there a fix for these? Any help would be great thanks.
Sent from my ADR6400L using XDA Premium App
It's a problem with the original and the leaked radio. I have it happen fairly frequently along with my signal dropping for unknown reasons. The radio firmware in the TB leaves a lot to be desired.
My 3G drops out and comes back but no random reboots. I am overclocked to 1.2 GHz running Bamf 1.6.2 remix with Ad's latest kernel and the latest leaked radios. I think it's mostly due to issues here in my area though (I had no LTE problems at work on Friday afternoon when it came back up.)
I have 3g drops as well. It happens randomly.
My 3G has been wacky the last few days. Constant drops (when they didn't happen before), and it has just been awfully slow. Hoping they are performing some maintenece for a nice 4G upgrade in my area
Thanks for your replies. It's nice to know I'm not alone. I did do that ##778 thing o heard about on here and cycles rev a. To enabled and now my 3g seems pretty consistent. I don't know what that changes though.
Sent from my ADR6400L using XDA Premium App
I know there are countless threads related to G2x Problems but none of the threads are focusing on isolating the reasons of Freezing Issue. I have recently upgraded my phone from Galaxy S Vibrant to G2x and i have to say i love the hardware and performance. Only Issue for me is random freezing.
After using the phone for 2 weeks and trying 3 roms
1. Stock
2. EB 1.04
3. Dark Sinister 1.1
I have come to a conclusion that kernel and rom is not the solution. At least not for me.
So i will try to solve the problem using hardware testing.
From my past 2 weeks experience.
1. Phone Freezes at night during charging
2. Phone Freezes when ever i turn off/on wifi and bluetooth and gps and Data (4g/3g) (Still have to figure out which of them is the cause. Cause i usually turn all off when i need to save battery).
Test Day 1
For Reason 1
I am using SetCpu and have changed Min from 216 to 312Mhz. I am trying this because i think very low cpu usage in standby for a very long period causes the phone to freeze. Its a Hunch i am not sure.
For Reason 2
I will keep wifi, Bluetooth and GPS off.
I will keep 4g/3g Data On all the time.
To My Surprise its been 16 hours no freeze. It includes charging at night. Lets see how long i can go without a freeze. Upon freezing i will make some changes.
Update 31/5/2011 (Test Day 2)
Ok its been more than 40 hours and not a single crash...
I removed the following possibilities as well....
It wont crash upon excessive usage.
Also Normal Heat up does not cause the crash.
As i have been playing Samurai II Vengeance all day long... Until I ended it. Several times charging along playing. I even played it on TV using HDMI. Not a single crash. I used to have around 3 crashes a day on stock rom when i unboxed my new G2x.
I also started using GPS from today. So lets see how it goes. I will update it every 24 hour.
Update 3/6/2011 (Test Day 5)
Ok i am considering Random Freezing On standby as solved because i havent had a single freeze at night after setting CPU Clock at 312 MHz using SetCPU. There are also other comments that back up my solution. I am considering this the solution of one problem.
2nd Issue of freezing while using cell phone apps is because of certain applications that are either buggy or not compatible with tegra Platform. For that i will start another thread with individual application testing for all apps that can cause the system to freeze or crash.
Please Discuss apps System Bloat-ware/User Apps that cause your G2x to Crash or Freeze in the following thread i created:
http://forum.xda-developers.com/showthread.php?p=14399089
Thanks for all the feedback.
Luckily I dont get that issue, buy I think this is a good test :u
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
garrychau said:
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
Click to expand...
Click to collapse
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
mobilehavoc said:
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Do you or @kangxi remember what Apps gave you issues?
it has to be a driver issue, its virtually the only explanation for why devs have not hammered it out yet or even CM7 team for that matter... it has problems on pure AOSP which leaves drivers or overheating (unlikely)... LG has to come up with the fix because they know their drivers and hardware better than everyone else...
Well the obvious problem I see is that they are all based on the stock rom. Try using one build from AOSP or a CM variety.
I didn't stay stock long but I did have reboot using the leaked Gingerbread (which is what EB is built from). I don't follow it but one is based off the stock 2.2.2 rom and the other is based off the leaked 2.3.3 rom.
I had nothing but problems with the stock roms. Thus your problem I think. Move over to Bionic, CM7, Gigglebread, or something.
I tested my phone and I didn't have a reset in like 5 days (which then my battery died overnight because I forgot to plug it in). I usually crackflash the CM nightlies and haven't had any problems with reboots or any issues requiring a reboot (aside from the flashlight killing audio, but just don't use it).
There are definitely two problems - software and the battery. I used to way more problems until I exchanged the battery for a new one and that solved most of my issues. The issues that remain are definitely software based.
tackleberry said:
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
Click to expand...
Click to collapse
Thanks for this information/ Changing the minimum speed didnt affect the battery life but it has survived two nights without crashing. So i am planning to keep it at 312Mhz min.
kangxi said:
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I Completely Agree with you. Some Applications do cause system crashes. But I have removed all the t-mobile bloatware and i only have few games and GPS apps. All games are from tegra zone. So I am sure they are supported.
For GPS App i am using Copilot and it didnt crash on me once.
I just installed setcpu and set minimum to 312. I'm keeping everything else the same to see if this change has any difference. Will report back.
Sent from my LG-P999 using XDA App
Looks like you are gaining progress. Sounds like keeping the processor revved up a little more does the trick.
It would be a simple fix for people to try that have reboot issues. I can't get mine to reboot, so unfortunately I cannot help you. My contribution was to resist from flashing for as long as possible to test how long I could get my "uptime" to. I got up to 127 hours when I passed out without charging it.
I'm running 20 hours now because I forgot to charge it again (seems to be my only problem, lol).
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
jrwingate6 said:
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
Click to expand...
Click to collapse
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
mobilehavoc said:
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
Click to expand...
Click to collapse
Have you noticed any changes in battery usage? I haven't really played around with SETCPU much but can the clock speed be set lower and if it can, have you tried slightly lower settings than 312mhz?
y are u guys using setcpu? and its def cuz the min is too low faux has his at 400 and no problems morfic also has his a little higher then what is it i think 216?? thats too low thats y setcpu isnt supported yet.....pimp my cpu
Someone asked me a question earlier. Only app I had issues with was fring. Soon as I opened it and started playing around with it, phone rebooted.
I uninstalled and it never happened again.
Sent from my LG-P999 using XDA App
mobilehavoc said:
No clue what you're trying to say but setCPU works fine. At startup for first time I selected Tegra2 and it works great. I have max set to 1000 and min to 312mhz (default was min to 216mhz). I'm running stock ROM but with root. that's all.
Click to expand...
Click to collapse
well thats y it works for u, u cant overclock over a thousand mhz so in ur situation ur ok i guess it only applies for people running a custom kernel then setcpu doesnt work, then u would need pimp my cpu
Hello there everyone. I recently flashed seanzscreams sky ICS leak rom. Everything seems to be in working order.
However there are two problems for me at least:
1. The wifi indicator never indicates a strong signal even if I am standing right next to the router.
2. There are random vibrations occurring when the phone is asleep or when I unlock it to do something. I thought that this was just google music vibrating to tell me its switching songs, but It happens randomly as well as then.
Just wondering if anyone else is getting this issue, and if so, should I try re-flashing even though Im not getting and FC's. I will fix permissions and post results.
Phone stats:
Version: 4.0.3
Baseband: I727UCALC4
Kernel: [email protected]#1
Build number: SKy ICS 4.1A-3
HamDeli1 said:
Hello there everyone. I recently flashed seanzscreams sky ICS leak rom. Everything seems to be in working order.
However there are two problems for me at least:
1. The wifi indicator never indicates a strong signal even if I am standing right next to the router.
2. There are random vibrations occurring when the phone is asleep or when I unlock it to do something. I thought that this was just google music vibrating to tell me its switching songs, but It happens randomly as well as then.
Just wondering if anyone else is getting this issue, and if so, should I try re-flashing even though Im not getting and FC's. I will fix permissions and post results.
Phone stats:
Version: 4.0.3
Baseband: I727UCALC4
Kernel: [email protected]#1
Build number: SKy ICS 4.1A-3
Click to expand...
Click to collapse
I have the EXACT same problem. Both of them in fact...
Sent from my SAMSUNG-SGH-T989 using xda premium
I believe it is due to any specific program that hasn't been optimized for ICS or the ROM itself, because I don't experience it, but I've heard of such problems on all ICS roms
I think it's from things force closing in the background.
I've been having the same issue, but I'm pretty sure it's due to the AOSP lockscreen. If you can tell Play Music glitches on the lockscreen and incorporates its self with Samsung locks screen. So definetely some sort of glitch going on.
Sent from my SAMSUNG-SGH-I727 using xda premium
All of the ICS ROMs suffered from the same 2 things mentioned. My WiFi signals were much weaker than on any GB ROM unfortunately.
I removed AOSP lockscreen and am still getting the random vibrations. Mine seem to be coming from the CM9 music app.
Sent from my SAMSUNG-SGH-I727 using XDA App
Hey everyone, how about trying out a different kernel?
For me, I switched to Romracer's kernel for ICS and I have no random vibrations or apps FCing in the back ground. You can also try Mohan's kernel as it seems to be better suited for AT&T.
When flashing the kernel always do a nandroid, but wipe both cache and davlik (its under advance.) Then after the kernel flash is complete just let the phone sit for a couple of minutes to make sure that everything settles into memory properly.
Something else that I noticed yesterday, I was doing a ton of memory wipes, (taking screen shots for different themes...) but my data connection was patchy as hell. Random drops and disconnects even though I was in Downtown of my city. Any way long story short you just need to let your phone settle down its been about 12 hours since my last cache & davlik wipe and my data connection seems to be holding properly without any further adjustments.
~PsyCl0ne
(NOTE: I'm still not allowed to post in the appropriate Android Developers forum, as of yet.)
...tonyp's ParanoidAndroid JB so far, has been the go to ROM for my G2X; far smoother and slicker than the EB ICS I used to run. Aside from the foreseeable battery drain (I always keep a charged spare on me, but usually a single overnight charge lasts a full work day), this ROM is the closest thing to stable I've encountered.
But one question:
My G2X has always suffered from a Sleep of Death about two out of every three times, all and only during voice calls (incoming or outgoing); regardless of Android ROM used.
This makes it a headache retrieving voicemails (keypad not accessible), leaving voicemails (cannot end calls), or the inability to end calls with people (i.e., my dad) who do not manually hang up on their end. (Luckily, I'm more of a texter and people rarely call me; so I wouldn't know what would happen in a call waiting situation.)
My only recourse is to take apart my Trident casing, remove the back plate and take out the battery. Ugh.
After asking around XDA about an in-call SoD solution, a majority said to up the CPU processor to about 500-600 mHz. But alas, the minimum CPU configuration is greyed-out in Performance settings.
(I've flashed the new baseband file after the ROM installation because I'm using the V21y March 2012 kernel. As well, I've used the GetRIL app to match the recommended baseband, just to be sure.)
So how exactly can I configure the minimum CPU settings?
(Or am I just not allowed to?)
Again, this SoD during phone calls is universal to my G2X regardless of Android ROM. So any help (or plausible alternate methods and solutions) are more than appreciated.
Seasons beatings,
Francis.
Sent from my Nexus 7 using xda app-developers app
meatfest1974 said:
(NOTE: I'm still not allowed to post in the appropriate Android Developers forum, as of yet.)
...tonyp's ParanoidAndroid JB so far, has been the go to ROM for my G2X; far smoother and slicker than the EB ICS I used to run. Aside from the foreseeable battery drain (I always keep a charged spare on me, but usually a single overnight charge lasts a full work day), this ROM is the closest thing to stable I've encountered.
But one question:
My G2X has always suffered from a Sleep of Death about two out of every three times, all and only during voice calls (incoming or outgoing); regardless of Android ROM used.
This makes it a headache retrieving voicemails (keypad not accessible), leaving voicemails (cannot end calls), or the inability to end calls with people (i.e., my dad) who do not manually hang up on their end. (Luckily, I'm more of a texter and people rarely call me; so I wouldn't know what would happen in a call waiting situation.)
My only recourse is to take apart my Trident casing, remove the back plate and take out the battery. Ugh.
After asking around XDA about an in-call SoD solution, a majority said to up the CPU processor to about 500-600 mHz. But alas, the minimum CPU configuration is greyed-out in Performance settings.
(I've flashed the new baseband file after the ROM installation because I'm using the V21y March 2012 kernel. As well, I've used the GetRIL app to match the recommended baseband, just to be sure.)
So how exactly can I configure the minimum CPU settings?
(Or am I just not allowed to?)
Again, this SoD during phone calls is universal to my G2X regardless of Android ROM. So any help (or plausible alternate methods and solutions) are more than appreciated.
Seasons beatings,
Francis.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Are you using an app to change settings? Like SetCPU, or Pimpmycpu, or any other app?
Also what ROM are you currently using? From reading your post, is it CM7?
Sent from my LG-P999 using xda app-developers app
I'd like to mention, that every time I use GetRIL I always get a lot more battery drain and it gives me problems, if you're using CM7 like me (or anything else) don't change the RIL, because someone mentioned before that it makes it somewhat incompatible or whatever and I have noticed that it makes my battery drain faster and my phone run hotter, thats just my experience from GetRIL.
Sent from my Nexus 7 using xda app-developers app
... uh, it's CM10 and it's build 8 of Hackfest JB ParanoidAndroid v.2.24.
Insofar as the settings go, I've been using the Settings->Performance in trying to configure the CPU; which is greyed out.
I understand that wanting JellyBean on a G2X may be a bit too much to ask, but heck, it sure is fun to have.
Sent from my Nexus 7 using xda app-developers app
Has anyone tested out all the different CM10 versions that our out?
I've been using CM 10.1 unofficial nightly from 06-09-2013. It had all the features working that i use (wifi + BT audio for example) which is why I hadn't updated since.
But seeing the development that was made for 10.1 with 3.4 kernal, and 10.2, I was wondering if anyone had a suggestion of the most stable ROM
Thanks!
I'm using the "last stable" from here : http://forum.xda-developers.com/showthread.php?t=2180163
volume's a bit quiet on bluetooth HSP and Audio also in phone calls, i can't use half my chargers either but battery life, speed and stability are great.
you should carry on in this thread, though, as this one is in the wrong forum and I created this one 2 days ago asking the same thing.
... http://forum.xda-developers.com/showthread.php?t=2453657
WiFi + bt together broke when we changed kernels. If that's important to you, you may not want to upgrade.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
actually i discovered (which you may have already known) its just the 2.4ghz band. I have a 5.0ghz wireless N router which i can use with bluetooth no problem.