Well, the title is pretty self-explanatory: I'm on CM 10.1.2 stable since a month and a half and in the last week it started to lag is I've never seen before!
Now I'd like to know if there's something I can do without flashing anything, and if there isn't if in your opinion is better to go back to stock on 4.3, to flash again 10.1.2 or to try the last nighty.
Thanks
PS: if you suggest me to go back to stock can you also explain me how to do it? I'm not into rom flashing anymore and I don't remember how to do it
Flash the latest 10.2 nightly. Its 4.3 though so you need the 4.3 gapps.
Is it stable enough for a smooth daily use?
I dont think the Galaxy Nexus has "unstable" ROMs. Everything works.
I've had a Galaxy S before GN, so I'm used to bad working roms and various lags
The Galaxy S is a different story. You should have no problems with the Galaxy Nexus
Flashed the last nightly and everything is fine but one thing.
I can't send SMS anymore.
Looking over the net I found that it can be the SMSC, and in fact probably it is because I typed *#*#4636#*#* on the dialer and in Phone Information the SMSC was empty.
I found the right one for me (Wind Italy) which is 0791932350585800, I typed it and refreshed.
Then I rebooted the phone and tried to send and SMS and still nothing, but looking at the SMSC it was empty again...what should I do?
Related
I've searched, so please forgive me if there's something similar. I've found nothing that solves my issue. I have freshly installed cm9 a couple days ago, and then shortly after upgraded to 10. That is where my woes began. Friends and fam started telling me that my phone would ring onced and straight to vm. I get texts in huge batches, a lot of repeats, and very unreliably. I've installed a few other different roms and kernels to no avail. And yes I've wiped everything, every time. My 3g/4g/wifi are fine.. just texts and calls messed up. What's happeninggg =[[[[. Is my radio corrupted or something? How can I fix this?
First: This is a support question and should have been posted in the Q/A forum.
Second: You should probably not install the RC of CM9, since CM9 is now stable and has an official release. http://get.cm/?device=epicmtd&type=stable
Third: Before flashing CM, use Odin to go back to stock and test out SMS, MMS and calls. If all works well, then you can Odin flash CWM, pull the battery, 3-finger boot to CWM and then flash CM9 stable.
If testing SMS, MMS and calls do not work properly on stock, then you need to go to a Sprint store and get them to fix it. Just leave it on the stock rom to bring it in.
Moved
Sent from my SPH-L710 using xda premium
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).
So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
noahajohnson said:
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
Click to expand...
Click to collapse
Thank you !!!
it's Work !
Hey all,
At this point I'm under the impression that it's the CM Nightly that's giving me issue, but here's the rundown in case anybody has any ideas before I revert to a past CM nightly, or a full rollback to VenomROM.
I had the latest build of VenomROM, and yesterday decided to give the new CM 12.1 Nightly builds a shot as my buddy told me it was looking super slick and seemed to be pretty good.
I do the usual when switching custom ROMs, and while everything else is working just fine, my mobile data seems to not work. I can make phone calls and get text messages just fine. But anything related to data I currently have to be connected to WiFi to access.
As far as I know, my phone/carrier firmware is up to date, as the issue with "non-Lollipop firmware + VenomROM = no Wi-Fi" was a non-issue for me.
For the record, my carrier is Rogers. It looks like my APN list and settings are what they should be (according to Rogers), and I've tried some things their tech support asked me to earlier today "Restore Default Settings" for APN's, taking out and reseating the SIM card, turning off my phone while they reset things with my account/SIM from their end, and all to no avail, even a wipe and re-install of the CM Rom produced a no-go.
Anybody got anything else I can try before I revert back to VenomROM? As much as I liked it, I'm really digging the look and feel of the CM nightlies.
Cheers,
shutuppat