Database Users

So... Is there a single completely usable ROM out there?

I've flashed almost 10 different ROMS now ever since the Asus ICS update and I'm still getting issues with SOD, RR, rapid battery drain, and/or wifi crashing after deep sleep. I just want my TF101 back. I don't care about Google Now... I just want a usable tablet!!!

You are flashing roms to rid yerself of an issue caused by a kernel?......If the rom You flash doesnt have a custom kernel you won't be solving any kernel issues....
In Short, flash a different kernel.....

Stock has been great for the 3 transformers in our family..
Go back to GB and spend a week on it and see if it does the same.. If so. Then you really have problems
Sent from my PC36100 using Tapatalk

Team EOS JB Nightly's & KAT 47b Kernel = Very fast, very stable TF101
Easily the best experience I have had with my TF since I got it
No RR's no SoD, everything works 100% and super fast, highly recommend trying it out if you haven't already

Pretty happy with Team EOS JB with stock kernel :good:

Tried Megatron and Revolver, reboot and SOD. Now i use ARHD with Harmony ICS at 1.6ghz speed. Stop searching cause it work:good:

misteroh said:
I've flashed almost 10 different ROMS now ever since the Asus ICS update and I'm still getting issues with SOD, RR, rapid battery drain, and/or wifi crashing after deep sleep. I just want my TF101 back. I don't care about Google Now... I just want a usable tablet!!!
Click to expand...
Click to collapse
those trouble had been solve with a lot thread in this box...
SOD and RR only got in HC when update to ICS its been solve, no more.
Rapid battery gain when you turn on wifi and watch video with high bright
wifi crash will be off after deep sleep only got in some ROM not alot, and they had been solve them. If you used any rom u must follow other posts.
I didnt got any issue like that becos i update kernel usually and I follow someone instruction.
recently I used EnergyROM and its make me happiest so maybe no more change ROM... I used 20 or over and I did got those issues like u when i keep update ROM and Kernal...
PS used ES Task Manager when u done any work and click on its widget to clear memory its make RR rate lower

To me cm9 works best... I wanna upgrade to jb but all have problems... cm9 is close to jb.. since some jb features are ported to ics...
Sent from my MK16a using XDA Premium App

Android Revolution HD 3.4.2 is the most stable rom for me. Don't know if you can still get such an old version, though.

I have tried EOS and 3 variations of CM10 (Raymans unofficial stable, Paranoid, LiquidSmooth). I like them all but EOS + KAT 47B gives me no issues to complain about (right now on 79 anyway). The others - last time I tried them - seem to have poorer wifi reception (and I don't mean just a matter of "bars"), occasionally lose wifi after re-awakening, and sketchy-to-non-existent GPS.
Truthfully, the EOS build works well enough for me that I could really care less if ASUS does an official JB upgrade at this point. Smooth, as robust as stock ICS when I left, stock browser working fantastic. I am on build 79 right now, probably upgrade to newer version if/when 4.2 features added.
I was set on getting myself a new tablet for Christmas, but after flashing EOS JB I have no more desire to upgrade to a newer tablet. It does everything I want it to, significantly better than when I bought it.

csb5731 said:
I have tried EOS and 3 variations of CM10 (Raymans unofficial stable, Paranoid, LiquidSmooth). I like them all but EOS + KAT 47B gives me no issues to complain about (right now on 79 anyway). The others - last time I tried them - seem to have poorer wifi reception (and I don't mean just a matter of "bars"), occasionally lose wifi after re-awakening, and sketchy-to-non-existent GPS.
Truthfully, the EOS build works well enough for me that I could really care less if ASUS does an official JB upgrade at this point. Smooth, as robust as stock ICS when I left, stock browser working fantastic. I am on build 79 right now, probably upgrade to newer version if/when 4.2 features added.
I was set on getting myself a new tablet for Christmas, but after flashing EOS JB I have no more desire to upgrade to a newer tablet. It does everything I want it to, significantly better than when I bought it.
Click to expand...
Click to collapse
Great, I'll check out Team EOS' rom and cross my fingers!

holy ****, that did it! EOS and KAT are rock solid!

there are many roms with cool features and stuff but in terms of stability i find stock asus rom the most stable.

If you want the tablet to just work, stick with stock based ICS ROM. That means.... the Energy ROM, ARHD or Revolver.

on your advice
*Detection* said:
Team EOS JB Nightly's & KAT 47b Kernel = Very fast, very stable TF101
Easily the best experience I have had with my TF since I got it
No RR's no SoD, everything works 100% and super fast, highly recommend trying it out if you haven't already
Click to expand...
Click to collapse
tried it... got to agree:good::good:

Im using Android Revolution HD 3.5.1. It has GPS problems, but everything else works well. I'd use a 4.1/2 rom but no flash.

Flash does work on jb roms.
http://forum.xda-developers.com/showthread.php?t=1774336
Using it on EOS 81 with KAT 47b. Best this tab has ever been.

Use raymanfx V6. cyo modded. Its JB but very stable and not all the issues ics have
Sent from my Transformer using XDA Premium HD app

I have tried all these ROMs and kernels and every time i pick up my tf101 it's dead. SOD constantly. I have to turn it off now everytime i finish using it so that i can use it the next time i come it. Very annoying.
Is there anything else that could be the problem other than kernel/rom (i have tried TeamEOS and KAT and CM10 with latest kat kernel with lidfix).
Thanks be to anyone that helps.

csb5731 said:
I have tried EOS and 3 variations of CM10 (Raymans unofficial stable, Paranoid, LiquidSmooth).
Click to expand...
Click to collapse
I've tried CM10 unofficial stable too and I really like it. Fast, stable, reliable.

[Q] Random reboots on CM-based roms

The past several days, I have been noticing random rebooting on both Official CM 10.1, and PAC-rom, which is CM based. The way it usually goes is: while interacting with the phone, the display will totally freeze for several seconds, then reboot.
Anyone else noticed this lately?

Mushroom. said:
The past several days, I have been noticing random rebooting on both Official CM 10.1, and PAC-rom, which is CM based. The way it usually goes is: while interacting with the phone, the display will totally freeze for several seconds, then reboot.
Anyone else noticed this lately?
Click to expand...
Click to collapse
They're both a work in progress and it's not unknown to get some rr's. They'll get better as the devs work on them. Keep trying the updates.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

CM is always a work in progress, then something better comes out, and dev for CM suddenly drops waaay off. Atrix 4G with CM7 had the same problem; endless reboots when i tried to play music, random stuff would work/not work with every update, and everything kept changing. I got sick of it pretty quickly, and i wont run CM anything again.

I've found I only get rrs when using KT's kernel and the ktoonservativeq governor. Using AOKP, CM, and Slim Bean on their stock ROMs, I have zero rrs and I've TRIED to reproduce all the conditions that cause them. What I've found is it appears to be tied into the GPU rendering as I get these rrs when either scrolling through long pages on Tapatalk or Twitter or using the AOSP camera. Haven't reproduced using any other process yet and it doesn't always happen at the same time or place (ie x seconds after boot or crossing x post).
Sent from my SGH-I337 using Tapatalk 4 Beta

Does this happen on a brand spanking new, untouched, stock copy of the rom your running?
Which is CM10.
These kind of problems are the exact reason I jumped off the aosp bandwagon. One thing after another. Just not worth it to me.

CM10.2 Discussion, General Talk, Q/A Thread

We can basicly use this thread for discussion, general talk, Q/A as long as its about CM.
Bugs:
Deadlocks (JSS15J bug)
Miracast & PTV3000
You tell me
F.A.Q
Enable root: Developer settings->Root Access->Apps and ADB. Also turn on USB-debugging.
Gapps: Photosphere is not included in standard gapps, use an alternative gapps package.
Links:
Download: http://get.cm/?device=flo (Wi-Fi)
GApps: http://goo.im/gapps
BBQLog: http://changelog.bbqdroid.org/#/flo/next

Whats a deadlock? Its obviously different from a wakelock? I have been on CM10.2 for a week now, surprising no noticable issues day to day. Good performance and battery life.

Just tested out Miracast last night using the Rocketfish receiver (RF-WFD301) from BB. Miracast worked for me although there were some pixelations and momentary screen freezes here and there. Of course, there's also the lag that you'd expect with Miracast at this stage.
Am on the latest CM10.2 nightly which was cm-10.2-20130819-NIGHTLY-flo.zip when I tested.
Planning to return the Miracast receiver though. Don't think the technology is quite ready for prime time yet and personally, was more of a urge to check it out but don't really have a need for it.

I mentioned this elsewhere, but I might as well bring it up here too since this will probably turn into a more official thread...
I've noticed here that my tablet isn't automounting USB drives (via OTG) on its own; I need an external app to do that, unlike my phone (d2att; both devices running 8/21 right now).
Is this intentional, a hiccup, or something else?

Deadlock is when it freezes, caused by a keyboard bug
Sent from my Nexus 7 using Tapatalk 4

I've only had one deadlock and I flash about 2 nightlies a week

CM Kanged rom is working great here. No more reboots and lots of options. Closest thing to the official AOKP rom there is until they start making AOKP 4.3 roms.
I did have one deadlock that recovered but I was updating some apps, which is expected from time to time.
I'm using a release from 8/8. Can't find a reason to update. I think there might be some issues with 8/20 because I tried many CM based nightly ROMs and all FC the AOSP keyboard on my Galaxy Nexus. Flashed a 8/18 nightly and it appears fine.
I'm happy with the CM Kanged rom until they mature enough to upgrade. Fast, smooth, no quirks, no random reboots like stock ROMs experience. Quite happy. It has the new HALO notification and SideBar built in. Probably has that weird navigation PA feature too that I don't use. HALO is weird but growing on me. Works good on a tab. Not sure about using it on my phone yet. I had to watch a video on how to use it before it really made sense.
Sent from my Nexus 7 using XDA Premium 4 mobile app

cowabunga said:
Just tested out Miracast last night using the Rocketfish receiver (RF-WFD301) from BB. Miracast worked for me although there were some pixelations and momentary screen freezes here and there. Of course, there's also the lag that you'd expect with Miracast at this stage.
Am on the latest CM10.2 nightly which was cm-10.2-20130819-NIGHTLY-flo.zip when I tested.
Planning to return the Miracast receiver though. Don't think the technology is quite ready for prime time yet and personally, was more of a urge to check it out but don't really have a need for it.
Click to expand...
Click to collapse
Might be ptv3000 issue then, removing it from bugs list.
smelenchuk said:
I mentioned this elsewhere, but I might as well bring it up here too since this will probably turn into a more official thread...
I've noticed here that my tablet isn't automounting USB drives (via OTG) on its own; I need an external app to do that, unlike my phone (d2att; both devices running 8/21 right now).
Is this intentional, a hiccup, or something else?
Click to expand...
Click to collapse
This is normal on nexus devices as far as I know.
Sent from my Nexus 7 using Tapatalk 4

Hey utacka ..lived your work on PA for the note !!
Planning to dev for the flo as well ??
Sent from my HTC One using Tapatalk 2

aamitabh28 said:
Hey utacka ..lived your work on PA for the note !!
Planning to dev for the flo as well ??
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Not planning going back to PA, maybe some gerrit patches to CM (mako, flo or whatever).
Sent from my Nexus 7 using Tapatalk 4

This is the first time I've ever run a CM rom. How long will it take them to incorporate JSS15Q now that its out?

Utacka said:
This is normal on nexus devices as far as I know.
Click to expand...
Click to collapse
Is this a hardware issue, then? That sounds implausible at best.

SalTNutz said:
This is the first time I've ever run a CM rom. How long will it take them to incorporate JSS15Q now that its out?
Click to expand...
Click to collapse
Yeah. How long will it take CM10.2 to pick the latest update changes up?

Should we expect overclocking options in the official CM in the future? I'm curious to see what my device can handle, but I prefer to stick with official CM builds where I can trust that code is the same as what's public.
Sent from my Nexus 7 using xda app-developers app

ragesoss said:
Should we expect overclocking options in the official CM in the future? I'm curious to see what my device can handle, but I prefer to stick with official CM builds where I can trust that code is the same as what's public.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You usually have to install one of the other developer kernels to get fancy with the kernel (ie. OC, UV, fancy governors, fancy schedulers, etc...).

cowabunga said:
Yeah. How long will it take CM10.2 to pick the latest update changes up?
Click to expand...
Click to collapse
I'm not seeing them yet. Give it some time.

8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.

cowabunga said:
8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.
Click to expand...
Click to collapse
I trust you mean 8/23
And no, the stock update fixes aren't in it.

I don't know if it's just me but, every time i launch the focal app the image that I get is always darker than with the stock camera app?
Sent from my Nexus 7 using xda app-developers app

cowabunga said:
8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.
Click to expand...
Click to collapse
They will be in the next build
Anyone successfully changed the CPU governor to Interactive? Mine reboots a few seconds after setting it to that

Nexus 7 on Cm 11

Hello guys, I currently own a nexus 2nd Gen it's rooted and running the latest cm 11 nightly build. Sometimes it make a buzzing noise while I'm listening to music or watching videos or it froze and restart itself that happen at least 3-4 times a day. I was wondering if that happens anyone else and how to fix it
Sent from my Nexus 7 using xda app-developers app

I've never had the buzzing but I don't use the speakers much.
The freezing and rebooting I have had both on stock and cm11. Best uptime I'd get was ~24 hours.
After flashing the latest Glitch kernel it's been up for ~106 hours. All location services turned on, syncing, google now, same apps etc.
Too soon to tell I guess but definitely an improvement.

I thought I was the only one it's getting really annoying, other roms are fine

I sometimes have buzzing sound for a short period of time. But I am using stock rooted 4.4.2.

I get this too, also happens in games

happened to me only on stock cm11

I ask this everywhere but does OTG work with latest cm11 nightly for flo? It is important for me since I cannot flash any other kernel to get it working
Sent from my Nexus 7 using Tapatalk

yosmokinman said:
I've never had the buzzing but I don't use the speakers much.
The freezing and rebooting I have had both on stock and cm11. Best uptime I'd get was ~24 hours.
After flashing the latest Glitch kernel it's been up for ~106 hours. All location services turned on, syncing, google now, same apps etc.
Too soon to tell I guess but definitely an improvement.
Click to expand...
Click to collapse
Can you tell all your glitch kernel settings?

Buzzing Noise fix
Flash the stock Android 4.4.2 ROM back on your Nexus 7 and the install Xposed.
Why would you need a custom version of 4.4.2 on your tablet that's already running 4.4.2 when the Xposed Framework works just as well.
EDIT - I've had no problems with buzzing noises or freezing on stock rom with unlocked bootloader and rooted.

Yup - same here. I've actually experienced this on both CM 10 and CM 11. The audio distortion out of the speakers is horrible. CM roms are the only ones that have this problem. I wonder if it has something to do with DSP Manager that's included with the CM Roms??
I agree with previous posters in this thread too - Stock rooted 4.4.2 is all you really need. Been flawless on my N7 2013.

I have the same issue
It usually happens when I watch a video from youtube or twitch. My tablet buzzes like kind of similar to someone getting an answer wrong in a game show.
I just need to go back to stock.

Can confirm that there's a buzz sound and a 1-3 second freeze using the CM11-M2 build.
After flashing the Jan 24 CM11 build, and the glitch kernel (using all stock settings except overclock to 1.7ghz cpu and 500mhz GPU), buzz sound is gone and all is well.

It happened to me with latest cm nightlies, and with all of them I had freezes and hangs. I went back to stock rom with elementalx kernel and i don't have any of these issues. I think cm overall is less stable and faster than stock rom. it's good for non nexus devices, but with nexus is better to stick to stock. I've tried other ROMs as well, nothing compares to stock in performance and stability.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Glitch kernel + cm nightlies = awesome mode
Still have more than 30% battery left

I have a problem with play store. It doesn´t load all the app images. Some of them are just blank while browsing apps.
I have tried latest nightlies, clearing app data and I have even tried a factory reset and I am still experienceing the same problem.
Anyone else having this problem?

[SOLVED][Q] Lag and stutter on (all) recent CM builds - what's going on?

EDIT: Solved - check CM11 discussion thread in the General section for @kabaldan 's fix. Fixed nightlies shoild start soon.
Hi all, I just received my RAZR M today and as usual, I flashed the latest CM nightly (20140301, unified) on it. To my surprise, there was heavy lag and stutter all over the system, even though I swear I did a clean install and didn't install anything afterwards (not even GAPPS). I posted this in the CM11 discussion thread:
AndyYan said:
...outfitted it with dhacker's TWRP 2.6.3.2, plus the latest unified nightly and @arrrghhh 's kernel, but to my surprise, animations stutter everywhere and items take a while to open. Reflashed without the kernel and the lag persists.
For reference, I flashed the same unified nightly on my Photon Q and things are still as smooth as ever. The RAZR M and Photon Q shares near identical internals, screen, etc. - they even share the same unified nightly.
Click to expand...
Click to collapse
I decided to try older nightlies to trace back the latest usable one, but again to my disappointment, out of the ones available on get.cm, only CM10.1 operates as smooth as it should, all builds from CM10.2 onwards lag heavily.
Then I came across this:
http://forum.cyanogenmod.com/topic/79209-major-lag-on-nightlies/
... which precisely described the issue I'm having, but without a solution.
Can anyone, especially those who claim to be using CM with "no problems", shed some light on this? Please don't advise me away from CM, I'm used to its feature set and don't want to get used to another unless necessary... Thank you in advance.
EDIT: Tried even more ways to ease the lag, only "disable HW overlays" seemed to help for a tiny bit. Also, testing with multiple benchmark softwares show that the device's performance is unaffected, so maybe the problem is on the graphics side...
Sent from Google Nexus 4 @ CM11

I can confirm the same behavior. CM 10.1 is soo smooth. I've been living with the CM11 problems for the additional features though. I just reloaded a CM10.1 backup to make sure I wasn't imagining things... It's definitely much smoother. I hour this gets fixed.
Sent from my Galaxy Nexus

BrandonL01 said:
I can confirm the same behavior. CM 10.1 is soo smooth. I've been living with the CM11 problems for the additional features though. I just reloaded a CM10.1 backup to make sure I wasn't imagining things... It's definitely much smoother. I hour this gets fixed.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Already fixed - see the CM11 discussion thread in the General section for details. A kernel is uploaded for flashing; also, the necessary patch is already pushed, so next nightly will hopefully include the fix.
Sent from Google Nexus 4 @ CM11

Perfect! It's working much better.
Sent from my DROID RAZR M