(UPDATE- I searched and found this is a known issue: code.google.com/p/android/issues/detail?id=28133)
I9250 on ST
Radio XXLA2
North central US
I travel to a lot of very rural areas for work. Often while in these areas I will unlock my phone and see no service. A minute later I may have up to 2-3 bars showing and I'll receive vm and sms notifications. I've tried different kernels and ROMs with no change.
Sent from my Galaxy Nexus using Tapatalk 2
I had this problem when using Juice Defender. Any chance you are using it?
No juice defender or even any similar app running.
Sent from my Galaxy Nexus using Tapatalk 2
untruestory said:
I9250 on ST
Radio XXLA2
North central US
I travel to a lot of very rural areas for work. Often while in these areas I will unlock my phone and see no service. A minute later I may have up to 2-3 bars showing and I'll receive vm and sms notifications. I've tried different kernels and ROMs with no change.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i started noticing the same issue recently...no service when i press the power button (on the lockscreen)...shortly after i unlock my phone, service/data restores...not sure if its kernel related as i believe (not 100% sure) that it happened around the same time i switched from glados to popcorn
i am also on XXLA2....in NYC
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
msedek said:
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
ive tried different radios before...UGLC1 included...went back to XXLA2 which gives me the best signal
this issue has only recently started happening...like i said, maybe related to the kernel because it started happening around the same time...not sure
msedek said:
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
Its not the radios, I have seen some posts in kernel threads about minimum CPU clock speed.
If you are using 192mhz bump it to 384mhz and see if that helps if not then try 729mhz. I've seen people sort it by doing this.
Those are Franco clock speeds but you get the idea.
nodstuff said:
Its not the radios, I have seen some posts in kernel threads about minimum CPU clock speed.
If you are using 192mhz bump it to 384mhz and see if that helps if not then try 729mhz. I've seen people sort it by doing this.
Those are Franco clock speeds but you get the idea.
Click to expand...
Click to collapse
ive read that the min cpu speed and even low VOLTAGES can affect signal stability as well....but i didnt change any of that.. currently its at 384 mhz and the default voltages on the popcorn kernel...the problem just started out of nowhere..its been fine for the past 2 weeks or so...just started happening like 2 days ago
no signal on wake
jdiddy_ub said:
ive read that the min cpu speed and even low VOLTAGES can affect signal stability as well....but i didnt change any of that.. currently its at 384 mhz and the default voltages on the popcorn kernel...the problem just started out of nowhere..its been fine for the past 2 weeks or so...just started happening like 2 days ago
Click to expand...
Click to collapse
I too experience the same issue. I am currently running aokp_maguro_build-36and have tried various basebands and now currently back at I9250UGKL1 .
I have been installing AOKP builds with the same behavior in that it goes to sleep the radio stays sleeping unless I reboot. I have the min CPU set to 700 mhz.
I have been reading the forums for weeks but cannot find anything where someone has fixed this. I love everything about the Galaxy Nexus with exception of this.
I've tried several ROMs and kernels. They make NO DIFFERENCE at all, including using stock.
Sent from my Galaxy Nexus using Tapatalk 2
blanktree said:
I too experience the same issue. I am currently running aokp_maguro_build-36and have tried various basebands and now currently back at I9250UGKL1 .
I have been installing AOKP builds with the same behavior in that it goes to sleep the radio stays sleeping unless I reboot. I have the min CPU set to 700 mhz.
I have been reading the forums for weeks but cannot find anything where someone has fixed this. I love everything about the Galaxy Nexus with exception of this.
Click to expand...
Click to collapse
Try cm rom
Sent from my Galaxy Nexus using XDA
untruestory said:
I've tried several ROMs and kernels. They make NO DIFFERENCE at all, including using stock.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Try different radios. Ive noted that the radio is not changed when I flash different roms.
Sent from my Galaxy Nexus using XDA
jdiddy_ub said:
ive tried different radios before...UGLC1 included...went back to XXLA2 which gives me the best signal
this issue has only recently started happening...like i said, maybe related to the kernel because it started happening around the same time...not sure
Click to expand...
Click to collapse
Id say try a Stable rom(not nightly) like AOKP Milestone 5 or stock.. And see if the problem persist.
After flashing new roms do a wipe of everything.. Dalvik/sd/cache/system
Galaxy Nexus AOKP m5 Franco kernel m3
msedek said:
Id say try a Stable rom(not nightly) like AOKP Milestone 5 or stock.. And see if the problem persist.
After flashing new roms do a wipe of everything.. Dalvik/sd/cache/system
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
i am already on AOKP MS5...i flashed the stable jame bond kernel last night...havent seen the issue since...hopefully that solved it
Aite cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Since its not the radios, the kernels, or the ROMs, then what else (other than a hardware defect) could be creating this problem?
Anyone?
Sent from my Galaxy Nexus using Tapatalk 2
Me too experiencing the same issue. Currently I'm on AOKP B37, and the bug is still there. The funny thing, is that despite no signal icon on wake, the phone is still on air and accepts calls. I've installed the No Signal Alert app, which hasn't registered any signal loss so far, but I know it works fine (I used it before on my old Galaxy I5800, which was loosing service). Very strange...
That is odd. I've missed calls in areas I should have gotten them. I'm hoping they hurry up and release a fix.
Sent from my Galaxy Nexus using Tapatalk 2
Signal Loss
I've been having the same issues for about a week or two now. Actually sent a phone back in and had it exchanged out because of this. Yes, I tried all radios and tons of different roms. Same result for all. And I mean I tried ALL THE RADIOS, so quit suggesting that.
And I also swapped out a phone, redid my things, and now getting back to same issues again.
However, my observations.....
I never had issues from Dec thru about a month ago. Then had a Rez for two weeks, then back to GNexus. First thing I did was load most current CM9. Played well for the whole day I had it at that. Then I realized I had forgot to update radios. Before (month ago) it was still at leaked 4.0.4 radios, however when I looked em up, the official 4.0.4 radios were posted. So I dabbled with them instead. But I also saw the bootloader update and blah blah, so I did the whole shabang for official 4.0.4, then rerooted and cm9'd. This was where problems began....at this point is when I started having exact same problems as OP. So I went back to old radios. Same problems. Then different radios. Same problems. Then different roms. Same problems. Then rolled all the way back to completely stock 4.0.2 image file. Bootloader, radios, recovery, everything. SAME PROBLEMS STILL.
Thats when I swapped out the phone.
New phone comes. I redo everything again, but just use official 4.0.4 radios rather than the bootloaders and blah blah but still with CM9. All is good. Then I wanna play with the full official 4.0.4 OTA update. So I do all of it. All if fine but I realize hey, battery life sucks again now. Back to CM9. Then I reroot and rom. And holy ****, all the problems are back again now with signals. New roms, same problems. Literally everything I had problems with before is all back again.
So I'm wondering if this obviously has something with OFFICIAL 4.0.4 image/bootloader/recovery or whatever the hell is being written when I'm doing that flashing.
Thoughts?
Your case might have some other cause. Did you try swapping your sim card?
Meanwhile, I was able to find a workaround. Just raised the min CPU freq. from 350 to 525. Since then there was not a single signal loss so far. Battery drain increase in idle mode ain't registered as well. I'm on AOKP b37 currently.
Here are the steps to take at least on AOKP (other roms may have similiar settings available):
Go to ROM control in the settings menu.
Open the Performance
Set the Min CPU to 525
Ensure, that Scaling govenor is set to Interactive
Enable the Set on boot option
Hope, it works for you too. Good luck!
Отправлено с моего GT-P7500 через Tapatalk
Related
I got rooted using Odin and LostKernel. Trying to get the best SETCPU setup and profiles. Can anybody Share there setting and profiles. How much battery life are you getting? I just got this phone Tuesday. Help!!!
Another Thing is anybody having Bad Wifi reception? my phone can be right next to the router and still wont get all wifi bars. i go to my kitchen or room and forget about it and barely connects to my wifi.
Ok 80 views and no responses so I'll bite. There are so many variables here that I could type a page or two but I will start at the end. You may need to try out a few different kernels to see which works best for you. People are having the best stability/battery life and least issues on the stock based kernels. If you use one of the overclock kernels, you may end up having LOS issues. You really have to try them. Wifi no good, try another. I am grabbing Wifi signal from the tenant who lives in the apartment below me (I am the manager so its ok..lol) I don't have any profiles set up. I let the phone do its thing. I am using the EG30 Rev 5 kernel since I am on EG31 modem. Since you are currently on LoSt, try EG30 stock w/CWM5 or Rogue stock w/ recovery. If you want to overclock try the Rogue overclockable kernel
Sent from my SPH-D710 using Tapatalk
I have always been of the position that Samsung has probably already put a lot of thought into the clock speed, and you probably should juat leave it be. Setcpu came into being a few years ago when phones handled the comprimise between battery life and clock speed poorly, it really is not need is anymore.
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
I have always been of the position that Samsung has probably already put a lot of thought into the clock speed, and you probably should juat leave it be. Setcpu came into being a few years ago when phones handled the comprimise between battery life and clock speed poorly, it really is not need is anymore.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Yeah, if you want to overclock or undervolt then its useful but for profiles I just leave those be. I mean if I am not using my phone its in deep sleep or running at 200. The scaling seems really dialed in to me
Sent from my Nexus S 4G using Tapatalk
This is the first phone I have not used SetCPU on. The Samsung kernel seems to do every thing on its own. I would recommend not using it at all.
Is anyone else having reception problems? My cell connection keeps dropping. NO phone I've ever had before has EVER had reception problems where I am now... GAAHHHH
Yes, there are a lot of complaints about this. Mine seems to drop once or twice a week. You need to toggle airplane mode on and off to get signal back. Usually occurs when bringing the phone back from sleep mode.
This doesn't seem to be happening with the stock ROM, just custom ones. Something to do with radio firmware voltage. I've tried switching to the latest North America radio to see if that fixes the issue for me.
That's really frustrating. I might move back to AOSP for a while.
Some people have moved back to 4.0.3 until the issue is fixed.
zuberio said:
Some people have moved back to 4.0.3 until the issue is fixed.
Click to expand...
Click to collapse
4.0.3 custom ROMS? or 4.0.3 AOSP
4.0.3 customs
Tynen said:
Is anyone else having reception problems? My cell connection keeps dropping. NO phone I've ever had before has EVER had reception problems where I am now... GAAHHHH
Click to expand...
Click to collapse
I have an AOSP Galaxy Nexus with Bell in Canada and my connection drops at least a once a week... Used to have the N1 with Rogers and wherever I was on my daily routine, I always had full connection.
Triggering the Airplane mode sometimes work but it randomly just hang during the process of switching. When it get to that point, reboot is required and often I will get full signal after...
This last weekend, I was in a cottage and my friend would have full signal on her device while I would have no coverage at all... I had to get out the building to get 1 bar.
Starting to wonder if it's not simply an hardware problem since I kept the regional build on until now and that the carrier doesn't seem part of the equation.
Any thoughts?
I recently switched from the XXLA2 radio (international) to the UGLC1 radio (North America) and haven't experienced a drop yet - though it's only been a day or two.
One other thing I noticed, however, is that on XXLA2 my phone was on the Rogers Communication Network, but after UGLC1 it now says Fido.
Try either using the 7xx Mhz as minimum frequency or up the voltage by 25-50 on the 3xx frequency.
(I just replied that to another Q actually. Amazing how many people don't know / try that..)
Vangelis13 said:
Try either using the 7xx Mhz as minimum frequency or up the voltage by 25-50 on the 3xx frequency.
(I just replied that to another Q actually. Amazing how many people don't know / try that..)
Click to expand...
Click to collapse
I've actually never messed with voltages before. How would you suggest doing that? I'm on AOKP Build 4
Tynen said:
I've actually never messed with voltages before. How would you suggest doing that? I'm on AOKP Build 4
Click to expand...
Click to collapse
Aokp 4!? Why don't you update to 5 at least? That might be fixing your issue as well.
I think Aokp has a kernel tinker option built in somewhere, does it not? If not, try Franco's or Morfic's kernels & apps, they have it. Or search for SetCpu here on xda, it's free for members.
Flashing a new kernel might fix it.
I just had my first Black Screen of Death requiring a battery pull. I don't know if it's a ROM or Kernel problem. I just flashed Liquid Smooth 1.5RC1 and the latest trinity. Not undervolted. I did a search, didn't find anything. Any ideas?
Amphibliam said:
I just had my first Black Screen of Death requiring a battery pull. I don't know if it's a ROM or Kernel problem. I just flashed Liquid Smooth 1.5RC1 and the latest trinity. Not undervolted. I did a search, didn't find anything. Any ideas?
Click to expand...
Click to collapse
Does this rom come stock with trinity kernel? If it does not and you flash it.. then it is normal, you are supposed to let the kernel sit and reboot after the phone is settled. Im not entirely sure what it is but i have to do it everytime otherwise i get what we called it back in my epic fourms "the dead hooker syndrome" where the lights would come on but the phone would be unresponsive.
No I flashed Trinity separately and ran it after several reboots and s**t for like 3 hours then this happened. I ran trinity before and never had this issue. My guess is that it's Liquid. For now, I shall observe and see if it happens again.
The ROM doesnt control the CPU .. the kernel does.. my guess is its a bad download or something is keeping it from coming out of deep sleep..
What is your minimum speed of the CPU? Anything below stock can cause issues.
Sent from my Galaxy Nexus using XDA
I'm running 307. I run 180 on IMO and Franco with zero issues, which is what I had used for a month.
Amphibliam said:
I'm running 307. I run 180 on IMO and Franco with zero issues, which is what I had used for a month.
Click to expand...
Click to collapse
It could be the fact that your phone just doesnt like Trinity... although we all have the same chipset... they arent all built to withstand the same conditions. Some handle more than others.
ÜBER™ said:
It could be the fact that your phone just doesnt like Trinity... although we all have the same chipset... they arent all built to withstand the same conditions. Some handle more than others.
Click to expand...
Click to collapse
What he said. Having your lowest frequency set at ~100, 300 regardless if it works on one particular kernel. Your phone might not like that kernel and cause it to not wake back up.
Best way to workaround it is just to simply boost your lowest frequency.... or just flash another kernel.
I would except Franco (m4/nightlies), IMO overheats my phone, PBJT fails at performance and battery, Popcorn is good, but I haven't tried the latest.
Amphibliam said:
I would except Franco (m4/nightlies), IMO overheats my phone, PBJT fails at performance and battery, Popcorn is good, but I haven't tried the latest.
Click to expand...
Click to collapse
I think kernels for sprint work for Verizon try samurai kernel in our forums. Its what I use or you could just flash faux kernel his is based on that.
Sent from my Galaxy Nexus using xda premium
Hey guys just figured I'd post this as I was not the only one with the same problem. I kept having no signal with beta 2, to the point where I was having to toggle airplane mode every time i unlocked the screen. After I read the post below I changed my under voltage from 230MHZ to 350MHZ, and voila! Problem solved! OP below, I take no credit for this, just trying to help out other liquid lovers.
I have had issues with kernels that undervolt too much (or myself undervolting too much) where it can't process a 4g or 3g signal correctly. So it may be that whatever kernel works fine for most but you need a little more juice. Or just that when it goes to sleep it lowers the power too much and fundamentally screws something up. I have gotten the best battery life out of kernels that broke 4g I wonder why.
I am running stock jellybean that I finally broke down and installed lean kernel stable on everything working fine. Waiting for a stock stable version of Liquid Smooth before I jump in.
Sent from my Galaxy Nexus using Tapatalk 2
OP was by Yianaki, not sure why it didn't copy that as well
Sent from my Galaxy Nexus using Tapatalk 2
I haven't seen anyone post about this yet, so I am going to take the plunge. I have a finicky device. Regardless of what kernel I put on, if I overclock at all, I will eventually get an SOD. I have tried Perseus and Core, all flavors, and started various times all the way from clean, Triangle-Away'd stock via Odin...same thing. It is really frustrating. The best results I get seem to be when I don't mess with the voltages at all, but eventually, SOD strikes. Sometimes I can go days. Today, I tried overclocking the new Perseus to 1.8 with stock voltage (after running it vanilla for 2 days with no issues), and within 2 hours, I had an SOD. I am currently on Clean 4.5, but have had the issue in every ROM.
Anyone else have a super-sensitive Note II with kernel overclocking? Anyone else seen SODs at all, under any other conditions?
What are you max screen-off and phone-on speeds clocked to? That could easily be the issue--I leave mine at 500MHz.
T.J. Bender said:
What are you max screen-off and phone-on speeds clocked to? That could easily be the issue--I leave mine at 500MHz.
Click to expand...
Click to collapse
Oh man, I am embarrassed to say I don't know...I am using STweaks currently with Perseus, and don't see where to set these values. I know that I was able to use profiles in SetCPU...
Where can I check these values? Appreciate your help!
I switched to SetCPU for now and created a couple of profiles. We'll see what happens.
Sent from my CLEANed Note II
Can't say that I get the SOD, but if the weather gets TOO cold (which it has for the last few weeks), my phone would reset itself and will be stuck at the "Samsung Galaxy Note II" screen until I pull the battery. Unlike your situation, I'm an extreme underclocker so it's easy to fix my issue (just give it a bit more juice!).
meatlocker said:
I haven't seen anyone post about this yet, so I am going to take the plunge. I have a finicky device. Regardless of what kernel I put on, if I overclock at all, I will eventually get an SOD. I have tried Perseus and Core, all flavors, and started various times all the way from clean, Triangle-Away'd stock via Odin...same thing. It is really frustrating. The best results I get seem to be when I don't mess with the voltages at all, but eventually, SOD strikes. Sometimes I can go days. Today, I tried overclocking the new Perseus to 1.8 with stock voltage (after running it vanilla for 2 days with no issues), and within 2 hours, I had an SOD. I am currently on Clean 4.5, but have had the issue in every ROM.
Anyone else have a super-sensitive Note II with kernel overclocking? Anyone else seen SODs at all, under any other conditions?
Click to expand...
Click to collapse
Coming from the Galaxy Nexus (and yes, I did my share of undervolting and overclocking with it) I know some of the dice used in making the cpu/gpu are not the same for every Galaxy Note 2. For example, where you got SOD problems used Perseus and Core, I could flash Perseus and Core on mine and not have the same problems at all. Best thing to do is try a different kernel till you find one that does not give you the SOD. Also, it is better to not flash a different kernel when you flash a new ROM as the kernel that is in the ROM usually works the best with it.
yes sod
I get the sod periodically irritating at times
I kept the phone unrooted and stock for 6 weeks or more, and i got the sod even then
I''ve rooted and have been using scottsroms for several weeks now, and get the sod about the same
I'm now wondering if it is a defective unit?
Anyone getting the sod probably has a bad phone. I would return it to be fixed. I personally never had the sod on any rom I have been on.
Sent from the TermiNOTEr 2!