Hello! I've searched quite a bit but have been unable to find anything to address the frustration I'm having. Recently I have been having an issue where my phone will restart itself at random intervals. The best way to recreate the issue is to use a streaming media app like Spotify/YouTube/Google Play Music/etc but it does happen at other times as well. This will occur on all ROMs I've tried including AOKP, CM10.1, Carbon, etc.
I believe I have narrowed the issue down to the 3.4 kernel as all the ROMs I've flashed in recent weeks have been using 3.4. If I use an older ROM (such as the stable release of CM10 with the 3.0 kernel) I do not have the issue.
It gets even stranger...I have found that LeanKernel is the only 3.4 kernel to work and has been stable for about 3 days on my device. So apparently I am stuck with reflashing LeanKernel after each ROM update if I want to run the latest and greatest.
My question is two-fold....
Is this a known issue for the AT&T GS3?
Any suggestions to fix this problem?
For the record, I have reverted to the stock, unrooted ROM and do not have the issues there.
Thanks in advance for any guidance!
Issues and bugs with 3.4 kernels are known. This is not specific to you.
I am running tasks 4/23 with the packaged kernel. No issues. Full wipe is key
xBeerdroiDx said:
Issues and bugs with 3.4 kernels are known. This is not specific to you.
I am running tasks 4/23 with the packaged kernel. No issues. Full wipe is key
Click to expand...
Click to collapse
Thanks for the feedback. I may look at Task's ROM in the future.
Related
Hi,
I've only got my Galaxy Nexus earlier this week. I tried out the stock rom for a day, then decided to switch to CM10.
It looks like whenever I flash CM10 based Roms, I experience lags when opening applications, reading/writing files to the system, however I am not experiencing these issues in any AOSP based roms.
For example, when I restore SMS by an app called SMS Backup & Restore, on AOSP based roms, the restore happens A LOT quicker than CM10 based roms.
I've tried CM10 nightly from 10/10 as well as JellyBro. I've done complete wipe (format /system /data /cache, clear dalvik, delete Android folder from internal SD). I've also tried different kernels (Franco and Trinity seemed to be populat in the forum) but didn't make any differences. I am still getting the annoying lags in CM10 based roms.
Is this normal for CM10 based roms? or is there anything I can do to fix the issue?
kamp said:
Hi,
I've only got my Galaxy Nexus earlier this week. I tried out the stock rom for a day, then decided to switch to CM10.
It looks like whenever I flash CM10 based Roms, I experience lags when opening applications, reading/writing files to the system, however I am not experiencing these issues in any AOSP based roms.
For example, when I restore SMS by an app called SMS Backup & Restore, on AOSP based roms, the restore happens A LOT quicker than CM10 based roms.
I've tried CM10 nightly from 10/10 as well as JellyBro. I've done complete wipe (format /system /data /cache, clear dalvik, delete Android folder from internal SD). I've also tried different kernels (Franco and Trinity seemed to be populat in the forum) but didn't make any differences. I am still getting the annoying lags in CM10 based roms.
Is this normal for CM10 based roms? or is there anything I can do to fix the issue?
Click to expand...
Click to collapse
FYI, CM10 is an AOSP based ROM.
I've experienced nothing but smoothness from CM10. Have you been checking the MD5 sum? Could be a bad download, I've actually had to download a ROM more than once from the CM servers because the sums didn't match up.
I'm on latest paranoid droid 2.21 with trinity kernel alpha 67. oc to 1.3ghz/384gpu interactive. I've had paranoid droid since 1.6 and i've been experiencing similar lag OP described. Mainly opening google now, camera app, settings. Have not tried stock 4.1.2 rom yet... although I'm really tempted to flash back to stock since it seems to solve the lag problem for some people. I've played with all the settings but to no avail. It's frustrating seeing how people are saying their jellybean galaxy nexus is so smooth and flies while mine stutters intermittently all the time
Here's a quick video i made demonstrating some of the lag
http://www.youtube.com/watch?v=Tq7mhqmKZtA
would like to know if others have a similar experience as me. Whether this is normal behavior or is there something I need to change/tweak?
lcambriz said:
FYI, CM10 is an AOSP based ROM.
I've experienced nothing but smoothness from CM10. Have you been checking the MD5 sum? Could be a bad download, I've actually had to download a ROM more than once from the CM servers because the sums didn't match up.
Click to expand...
Click to collapse
Thanks. I have checked all the MD5 sums - they all match up. I've tried a lot of roms based on CM10 - CM10 nightlies, JellyBro, Paranoid and Paranoid dark, but still the same issue.
I should have clarified what I meant by AOSP based rom. I meant any roms that doesn't have too much changes from pure AOSP (Eg. stock rom, Android Revolution and the roms by Team EOS)
When I flash CM10 based roms, even the initial setup seems to be lagging (I've been doing clean installations - format cache/system/data, clear dalvik). For example, on the initial setup screen, upon selecting the language and hit next, it takes a lot longer (probably around 10 seconds or so) to progress to the next step whereas anything based on stock takes me to the next screen within a second.
I'm not too sure if my perception of lag is different from others. I've actually come from using Galaxy S2 (I've decided to try GN after accidently dropping my S2 in the washing machine). I've never had this sorts of lags on any of the CM10 based roms on S2.
It looks like some of these lags go away if I disable fsync in the kernels, but not all the lags
maniaxzero said:
I'm on latest paranoid droid 2.21 with trinity kernel alpha 67. oc to 1.3ghz/384gpu interactive. I've had paranoid droid since 1.6 and i've been experiencing similar lag OP described. Mainly opening google now, camera app, settings. Have not tried stock 4.1.2 rom yet... although I'm really tempted to flash back to stock since it seems to solve the lag problem for some people. I've played with all the settings but to no avail. It's frustrating seeing how people are saying their jellybean galaxy nexus is so smooth and flies while mine stutters intermittently all the time
Here's a quick video i made demonstrating some of the lag
http://www.youtube.com/watch?v=Tq7mhqmKZtA
would like to know if others have a similar experience as me. Whether this is normal behavior or is there something I need to change/tweak?
Click to expand...
Click to collapse
Yeh, i'm having similar lags on my phone on any CM10 based roms (including Paranoid). One thing that sort of helped me was disabling fsync (on Franco's kernel). Or try flashing the stock rom and see if it gets better. At least stock rom seems to be very smooth in my case.
kamp said:
Hi,
I've only got my Galaxy Nexus earlier this week. I tried out the stock rom for a day, then decided to switch to CM10.
It looks like whenever I flash CM10 based Roms, I experience lags when opening applications, reading/writing files to the system, however I am not experiencing these issues in any AOSP based roms.
For example, when I restore SMS by an app called SMS Backup & Restore, on AOSP based roms, the restore happens A LOT quicker than CM10 based roms.
I've tried CM10 nightly from 10/10 as well as JellyBro. I've done complete wipe (format /system /data /cache, clear dalvik, delete Android folder from internal SD). I've also tried different kernels (Franco and Trinity seemed to be populat in the forum) but didn't make any differences. I am still getting the annoying lags in CM10 based roms.
Is this normal for CM10 based roms? or is there anything I can do to fix the issue?
Click to expand...
Click to collapse
Yeah, I'm basically having the same problem. When I went back to stock, it seemed to be a lot faster. Granted, I did reinstall all my apps at that point. When I get a minute, I'll probably reinstall cyanogenmod 10 to see if it is still slow or not with a fresh install.
kamp said:
Thanks. I have checked all the MD5 sums - they all match up. I've tried a lot of roms based on CM10 - CM10 nightlies, JellyBro, Paranoid and Paranoid dark, but still the same issue.
I should have clarified what I meant by AOSP based rom. I meant any roms that doesn't have too much changes from pure AOSP (Eg. stock rom, Android Revolution and the roms by Team EOS)
When I flash CM10 based roms, even the initial setup seems to be lagging (I've been doing clean installations - format cache/system/data, clear dalvik). For example, on the initial setup screen, upon selecting the language and hit next, it takes a lot longer (probably around 10 seconds or so) to progress to the next step whereas anything based on stock takes me to the next screen within a second.
I'm not too sure if my perception of lag is different from others. I've actually come from using Galaxy S2 (I've decided to try GN after accidently dropping my S2 in the washing machine). I've never had this sorts of lags on any of the CM10 based roms on S2.
It looks like some of these lags go away if I disable fsync in the kernels, but not all the lags
Yeh, i'm having similar lags on my phone on any CM10 based roms (including Paranoid). One thing that sort of helped me was disabling fsync (on Franco's kernel). Or try flashing the stock rom and see if it gets better. At least stock rom seems to be very smooth in my case.
Click to expand...
Click to collapse
EnderTheThird said:
Yeah, I'm basically having the same problem. When I went back to stock, it seemed to be a lot faster. Granted, I did reinstall all my apps at that point. When I get a minute, I'll probably reinstall cyanogenmod 10 to see if it is still slow or not with a fresh install.
Click to expand...
Click to collapse
I can attest to having annoying lag in CM10 based roms such as ParanoidAndroid. It's always smooth in the beginning but as I install more apps, it just slows down considerably.
I just wiped my entire phone last night and started over running Rasbean Jelly 10.16 Build(AOSP Based) with Trinity A67 1344/307 and it's as smooth as it can get. I have about 130 apps installed and it's still fast as ****. Google now/ google search takes about 1 sec. to start versus it can take up to 5-6 seconds before on CM based roms. All apps are responsive and starts super fast.
Don't know why this occurs but it seems that some galaxy nexus' like ours just dont like the CM10 Builds..
So if anyone is having lag problems, I'd recommend the rasbean jelly + trinity combo before looking for a new phone..
Do you guys see "lags" on stock rom? Yes? Then return the device.
maniaxzero said:
I can attest to having annoying lag in CM10 based roms such as ParanoidAndroid. It's always smooth in the beginning but as I install more apps, it just slows down considerably.
I just wiped my entire phone last night and started over running Rasbean Jelly 10.16 Build(AOSP Based) with Trinity A67 1344/307 and it's as smooth as it can get. I have about 130 apps installed and it's still fast as ****. Google now/ google search takes about 1 sec. to start versus it can take up to 5-6 seconds before on CM based roms. All apps are responsive and starts super fast.
Don't know why this occurs but it seems that some galaxy nexus' like ours just dont like the CM10 Builds..
So if anyone is having lag problems, I'd recommend the rasbean jelly + trinity combo before looking for a new phone..
Click to expand...
Click to collapse
Thanks, glad to see I'm not the only one. I'd check out Rasbean Jelly + Trinity, but I'm using this as an excuse to dump VZW and go with the Nexus 4 next week.
Hi Folks
On my device the lag is connected to how full the file system is.
If I copy lot of music on the phone then it becomes laggy
If I delete it, it is still laggy.
To recover its full smmothness I have to do a full wipe and then restore the FW.
Did anyone find the same problem?
thnx
lollonet said:
Hi Folks
On my device the lag is connected to how full the file system is.
If I copy lot of music on the phone then it becomes laggy
If I delete it, it is still laggy.
To recover its full smmothness I have to do a full wipe and then restore the FW.
Did anyone find the same problem?
thnx
Click to expand...
Click to collapse
This can be fixed with fstrim. Here is a cwm zip that runs fstrim as a script upon each boot and places a fstrim.log file in /data/local to verify it worked. It trims /system, /data and /cache.
https://www.box.com/shared/l5afni1mxe1wpb2ubw3s
Edit:
*Important* There are some emmc cards that have a so called "brick bug". Use this app to check and use the fstrim at your own risk.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Sent from my Galaxy Nexus using Tapatalk 2
Hello I hope you are doing well. I have tried to flash Liquidsmooth and Cyanogenmod nightly 3/16 and both of them will freeze during a phone call and or after a phone call. I tried the sonic TW rom and have had no issues. Can someone please let me know what the issues might be and how I can fix them. Thank you so much I need a very stable ROM as I use my phone for work.
Were those 4.2.2 roms? Those arent quite stable yet, theyre still working on them
Flash a 4.1.2 / MB1 / MA6 ROM if you're looking for as much stability as possible
acesup_11 said:
Hello I hope you are doing well. I have tried to flash Liquidsmooth and Cyanogenmod nightly 3/16 and both of them will freeze during a phone call and or after a phone call. I tried the sonic TW rom and have had no issues. Can someone please let me know what the issues might be and how I can fix them. Thank you so much I need a very stable ROM as I use my phone for work.
Click to expand...
Click to collapse
I believe for Liquidsmooth that error was caused by the most recent release (titled STABLE). I know that RC2 didn't have the same issues with freezing on phone calls. The RC2 is available on their goo.im page.
But, like CNexus said, 4.2.x Roms will inherently be a less stable than TW-based Roms. That's just the way it is when you're developing something that's not been officially released for your device. In the 4.2.x Roms that I tried, it was stable enough for my (non-business) needs.
Seems like I've been hearing this issue on various threads since the new CM kernel was released. CM is still in nightlies so it is not 100% stable. But it could be a lot of different things.
Sent from my SPH-L710 using Tapatalk 2
I appreciate all the help is there any good roms that are not TW that are stable MA6? If you could point me in the right direction. I tried searching MA6 and got kernels?
acesup_11 said:
I appreciate all the help is there any good roms that are not TW that are stable MA6? If you could point me in the right direction. I tried searching MA6 and got kernels?
Click to expand...
Click to collapse
Well, I don't know exactly what you mean by non-TW-based MA6 Roms. As far as I know, MA6 Roms are inherently based off of touchwizTW (since it's a build of Samsung's Sprint Rom). I assume you mean Roms based off Android version 4.1.2, which is the version that came with MA6.
I know freeza has gone and removed a lot of TW features from his Galaxy S fre3 Rom. It's currently on MB1, which is only a minor upgrade from MA6.
But for the most part, the MB1- and MA6-based Roms are pretty solid in terms of stability. I'd recommend going to the Rom Wiki created by Hamspiced. I have no idea when it was last updated (maybe a week or two ago), but it has a lot of links to MB1 and MA6 Roms (as well as a lot of AOSP, etc. Roms)
Hey guys,
I've noticed recently that when i flash any kernel that is compatible with my rom, it results in black screen on reboot. But its as if the phone is active in the sense that i can hear the phone make the unlock sound when i pretend to unlock it. so its all there but the screen is black.
Rom i am on currently: Carbon 4.2.2 stable release
Kernels Ive tried: BMS, KT both of which are 3.4 version needed for the rom i use.
I've cleared cache, fixed permissions, factory reset and started from scratch with installling the rom and then flashing the kernel with the same issue.
Ended up doing a restore of nandroid for phone to work. But still cant flash any kernels that I know for sure are compatible with any rom. This doesnt seem to be a rom or kernel specific issue because i've tried different combinations. Like for example i tried the aokp tasker with KT with same symptoms pr for example liquid smooth with BMS etc.
Any suggestions?
Thank you in advance.
What's the release date of your rom? Try using a kernel release of that date or earlier.
xBeerdroiDx said:
What's the release date of your rom? Try using a kernel release of that date or earlier.
Click to expand...
Click to collapse
the latest version of carbon rom 1.61 is what is I use regularly. I've tried older versions of this and other roms but the issue persists.
gutlessmerc said:
the latest version of carbon rom 1.61 is what is I use regularly. I've tried older versions of this and other roms but the issue persists.
Click to expand...
Click to collapse
the release date of that rom is 3/29. i would try a 3.4 kernel with a release date of 3/29 or earlier to see if this corrects the issue.
gutlessmerc said:
the latest version of carbon rom 1.61 is what is I use regularly. I've tried older versions of this and other roms but the issue persists.
Click to expand...
Click to collapse
You need to use an older version of a kernel. Either 4/15 for BMS or 4/11 for KT747. The most recent builds have display commits that are required on the ROM for the display to work.
ktoonsez 4/11 release: http://forum.xda-developers.com/attachment.php?attachmentid=1916103&d=1367068269
Thanks for the response guys. I've tried flashing the older version of KT kernel as suggested. Thanks for the link man. Unfortunately, the same issue again: On boot, it goes all black. The difference though is that this time while the screen is black, there is no sound response by tapping on the screen. I tried increasing the volume to see if there was any difference but still nothing.
I guess i'll be fine. The only reason i tried flashing a different kernel was so i could enable fast charge.
Thanks for the help guys.
Cheers
flash tasks 4/23 build. its stable, bug free (for me) and has the fast charge feature in addition to amazinf battery life. cheers
Ive been using the dark flo version if cm10.2 since I got my nexus 7, however when ive tried to install a custom kernel, I get a blue/turquoise screen upon reboot. Ive tried both CAF and normal versions of various kernels, but all with the same results. I tried using the AOSP kernel setting in the aroma installer, then installed some AOSP kernels, which do boot but it has the worst lag ive ever seen since my iPhone! Anyone else experienced this and know a solution? Ive searched the forum but couldn't find anything relevant
Same here: installed CM10.2 unofficial, GApps, rebooted and everything´s fine.
After installing any of the Faux-Kernels (es/m/u) and wiping Dalvik etc., I have the same screen problems and lags, which make the device unusable.
I´m searching for an overclock kernel, btw.
Thanks for your input!
im after the same thing, just an oc kernel. I even tried one with no mods, just the cpu speeds increased and had no luck
UPDATE - I read somewhere that some kernels wont work with CM versions released after oct 2nd. I tried installing a copy of dark flo from the end of September, then tried faux123's latest mainline kernel abd it booted fine! Im assuming its an incompatibility with the latest CM, so I hope the kernels get updated soon!
Thank you for the info!:good:
It´s waiting time again...
how did you get out of the turquoise screen?
Easy fix:
Uninstall CM
Install AOSP based rom
Profit
Seriously, CM has gone to crap since they moved away from aosp and started with CAF. Kernel devs shouldn't have to do extra work just for one rom, especially when said rom is going from bad to worse
Nexus 7 LTE
Stock rooted KRT16S
Faux Kernel
Anyone else experiencing problems and/or general instability with the new nameless ROM builds
div9013 said:
Anyone else experiencing problems and/or general instability with the new nameless ROM builds
Click to expand...
Click to collapse
Afraid your question isn't specific enough to elicit directly helpful responses. Did you flash a custom ROM and are now experiencing problems with your phone after this? If so, what kind of problems? There are far too many custom ROMs out there for a generic solution to apply and, needless to say, a good deal of personal research and caution needs to be exercised before one proceeds with a custom ROM installation.
Larry2999 said:
Afraid your question isn't specific enough to elicit directly helpful responses. Did you flash a custom ROM and are now experiencing problems with your phone after this? If so, what kind of problems? There are far too many custom ROMs out there for a generic solution to apply and, needless to say, a good deal of personal research and caution needs to be exercised before one proceeds with a custom ROM installation.
Click to expand...
Click to collapse
Well yes, I did specify the ROM name. It is quite literally called Nameless ROM. The problems that I am experiencing are with the latest nightlies and this instability specifically affects the the dialler applications, sometimes it works but most times whenever I get a call on my phone I just get the pop up "Unfortunately the dialler app has stopped"
I have wiped cache and dalvik cache, reflashed the ROM and the Gapps to no avail.
div9013 said:
Well yes, I did specify the ROM name. It is quite literally called Nameless ROM. The problems that I am experiencing are with the latest nightlies and this instability specifically affects the the dialler applications, sometimes it works but most times whenever I get a call on my phone I just get the pop up "Unfortunately the dialler app has stopped"
I have wiped cache and dalvik cache, reflashed the ROM and the Gapps to no avail.
Click to expand...
Click to collapse
Apologies. I was also being too general in my response. I checked a few Nameless fora on the web and it would appear such instabilities are not uncommon with nightly builds as is often the case with all custom ROMs still undergoing development. Your best option might be to flash a stable version or, if not out of your preference, revert to stock.
Larry2999 said:
Apologies. I was also being too general in my response. I checked a few Nameless fora on the web and it would appear such instabilities are not uncommon with nightly builds as is often the case with all custom ROMs still undergoing development. Your best option might be to flash a stable version or, if not out of your preference, revert to stock.
Click to expand...
Click to collapse
Yes I would prefer to not reverting to stock. I guess I shall be looking at other ROM's that have similar features. Thanks for your help.