Develop Bugs

[Q] Low And Slow Cellular Signal With CM10.0.0 Rom

I have a Samsung GS3 AT&T version with CM10.0.0 ROM.
I noticed that since I flashed 10.0 ROM, the cellular signal level seems always low, most of time, only 2 or 3. but with original stock rom, it shows at least 4 bars most of the time. Another problem I have experienced is that the cellular signal gets lost from time to time and it takes quite a while (at least a few seconds) to regain the connection.
One last problem is there is no LTE signal since 10.0 ROM. I believe this might be an known issue already. Is this true? Has anybody experienced the similar problems as I stated in above? Any solutions? Or I'd expect these issues will be fixed in the upcoming 10.1 ROM?
Thanks!

hazelinelee said:
I have a Samsung GS3 AT&T version with CM10.0.0 ROM.
I noticed that since I flashed 10.0 ROM, the cellular signal level seems always low, most of time, only 2 or 3. but with original stock rom, it shows at least 4 bars most of the time. Another problem I have experienced is that the cellular signal gets lost from time to time and it takes quite a while (at least a few seconds) to regain the connection.
One last problem is there is no LTE signal since 10.0 ROM. I believe this might be an known issue already. Is this true? Has anybody experienced the similar problems as I stated in above? Any solutions? Or I'd expect these issues will be fixed in the upcoming 10.1 ROM?
Thanks!
Click to expand...
Click to collapse
Flash many nightlies and even the stable ROM and more often than not I'd have the same problem as you and that's a huge battery killer. CM hasn't been verybstae in reference to data connection even with their stable release its still been a problem for me and a few others that I know whom tried running it all in separate carriers. Try a different cm10 based ROM in the original android development section. There are dozens that are great fast and stable with no data issues.

DamageSource said:
Flash many nightlies and even the stable ROM and more often than not I'd have the same problem as you and that's a huge battery killer. CM hasn't been verybstae in reference to data connection even with their stable release its still been a problem for me and a few others that I know whom tried running it all in separate carriers. Try a different cm10 based ROM in the original android development section. There are dozens that are great fast and stable with no data issues.
Click to expand...
Click to collapse
Thanks for the info. Do you have any CM10 based ROM that you'd particularly have experienced and recommend? I don't want to keep flashing ROMs and trying them out one by one. My simple goal is to find a stable and least buggy ROM and stay with it at least for quite a while.
Thanks!

hazelinelee said:
Thanks for the info. Do you have any CM10 based ROM that you'd particularly have experienced and recommend? I don't want to keep flashing ROMs and trying them out one by one. My simple goal is to find a stable and least buggy ROM and stay with it at least for quite a while.
Thanks!
Click to expand...
Click to collapse
I used this one from release to a few weeks ago I went back to stock so I could lean about ROM cooking so. This gave me the best battery life on a cm10 based ROM and its real lightweight and just all around awesome.
http://forum.xda-developers.com/showthread.php?t=1965641

DamageSource said:
I used this one from release to a few weeks ago I went back to stock so I could lean about ROM cooking so. This gave me the best battery life on a cm10 based ROM and its real lightweight and just all around awesome.
http://forum.xda-developers.com/showthread.php?t=1965641
Click to expand...
Click to collapse
Hey, thanks for the info. I checked out that link but unfortunately, the ROM image is not available for downloading any more. I'll do some search to see if I can get that liquidsmooth ROM that you recommended. Or I can find an similar one to try out.

hazelinelee said:
Hey, thanks for the info. I checked out that link but unfortunately, the ROM image is not available for downloading any more. I'll do some search to see if I can get that liquidsmooth ROM that you recommended. Or I can find an similar one to try out.
Click to expand...
Click to collapse
http://goo.im/devs/liquidsmooth/d2att/deprecated/Liquid-JB-v2.0-RC9-d2att.zip
Here you go. Its on the goo.I'm as stated in their forum post. Let me know how you like it and if it works for you

[Q] Current ROM with OC compatibility

Hi all,
I've scoured the forum for quite some time now and have tried a number of newish ROMs (those posted in May) but have not found any that are compatible with Ktoonsez's latest kernel. A lot of people have advised against overclocking but my GS3 certainly performs better with OC enabled. I flashed one of Jamison's nightlies months ago and it has been the most stable/reliable out of any ROM I've tested since. I either got lucky and found the perfect ROM for my phone or I just haven't found a solid new ROM that supports OC'ing. I've had random reboots, force closes, etc. with all the new ROMs I've tried so I was hoping someone could give me some ideas on a ROM/kernel combination that might work for me. The only reason I even want to change my current ROM is because many of my Google apps report that an update is available, but when I go to update, my "device doesn't support this version." It's quite frustrating and a pretty sad reason to switch ROMs when literally EVERYTHING else works flawlessly, but it is a problem for me and I'd like to be able to stay up to date. Sorry for the long post, but anyone with advice would be wonderful. Thanks!

You need a kernel that support OC, its not ROM specific.. You do however, need to check kernel's description to which base it works with.. Sometimes they will have one for just touchwiz or touchwiz and aosp, thats pretty much the main thing to look for and just try different ones.. It should also say if its OC able or not
Sent from my SGH-T999 using Tapatalk 4 Beta

cyanogenmod-10.1-is-not-perfect

does anyone know, or have a reason, or encounted in a problem with CM 10.1 cuz i recently installed CM 10.1 stable on my ATT S3 and it keeps restarting itself after 20/30 minutes tops, maybe longer but once in a while it randomly restarts itself
installed everything perfectly, no reason to be acting crazy since its from CYANOGENMOD TEAM but ROMS are not perfect or as good as STOCK ROMS (that come pre-installed on your device)
any issues, bugs, any kind of thing you have noticed with cm 10.1 yu can post it here
new upcoming features, fixes, what should be there or shouldnt be there, whats missing everything
HELPING EACH OTHER SOLVE SIMPLE/SERIOUS with CM 10.1 and above ISSUES
am currently running Synergy ROM 4.1.2 Stock rom with ZIGGY KERNEL (clocked at 1.3 Ghz) and its pretty sweet, stable, good battery, perfomance is top notch for a stock based rom that come with all samsung boatload
SO DUMP ALL THE PROBLEMS/SOLUTIONS IN THIS NEW THREAD FOR CM 10.1 AND ABOVE - ATT S3 I747
ANYTHING YU THINK IS COOL/AWSOME ABUT CM 10.1 ON YOUR AWSOME S3 GET IT HERE

Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

Domoo said:
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE

winosxbuntu said:
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
Click to expand...
Click to collapse
First and foremost, no OS or software, including android, is perfect. Secondly starting a new thread does not mean it will not get "cluttered" either. The ROM thread for CM is not as bad as you make it out to be. The idea is that the newest material covers the most recent nightlies. It is not that difficult to go to the end and work backwards. In regards to you random reboots, look on JIRA as it exists for this very reason. Take a logcat and report on JIRA if not already covered. JIRA gives you all the bugs reported and their current status towards a fix. This is a wasted thread for this very reason.
As far as ROMs being different...that is the point. Each developer(s) put their own spin on it. That is what makes these development threads so great. You can look for a ROM that you like best. Some ROMs are more universal (but you still need your device specific version), such as CM, while others are device specific.
And phones are not created equal. They may look the same, have the same hardware specs, and all else seemingly equal, but slight manufacturing imperfections make them different. Two people can have the exact same phone from the same carrier, manufactured on the same day, but due to some ever so slight differences from imperfections, ROMs will work differently on each. For instance, in your case CM reboots randomly. For others, such as myself, this is no longer an issue. However, it is possible that another ROM will work great on your phone but not on mine.
While you say CM is not perfect like the stock rom, the stock rom is not perfect either. I have AT&T and the stock rom has several issues. The lockscreen securities can be bypassed, the alarm likes to not work at random times (software bug), and every now and then I get a battery plummet after a phone call when the phone switches between 4G and 4G LTE. Others may or may not have these issues but they seem to be rather common (the security bypass affects all S3 phones that were on 4.1.1 that I am aware of). For this reason I stick to custom roms because I do not have these problems which I personally view as severe for me (Aside from protecting my data and enjoying battery life, I rely on my phone as an alarm clock). Now that 4.2.2 has come as far as it has, it is stable enough that I can use it as a daily driver. I knowingly accept any bugs that are there because typically the ones that exist do not have a large affect on me, if at all, unlike the stock rom.

[Q&A] [ROM][GEE/B] UNOFFICIAL CyanogenMOD 11 [10-13-14]

Q&A for [ROM][GEE/B] UNOFFICIAL CyanogenMOD 11 [10-13-14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

HALP !
I'm running the october builds of the cm11 gee version. And i've been experiencing battery drain when the phone is idle. For eg. Overnight my phone dropped from 56-49 % doing nothing. I'm running this build with the built in kernel (Matr1x) and gapps from cyanogenmod's website. I tried 9/26, 10/01, 10/06, 10/13....all with the same battery drain problem. The ROM is solid and the battery life under usage is amazing (especially with jolla kernel). But battery keeps draining when the phone is idle (even with jolla kernel). This is really frustrating. Any help would be appreciated

SpaceMonkeyK9 said:
I'm running the october builds of the cm11 gee version. And i've been experiencing battery drain when the phone is idle. For eg. Overnight my phone dropped from 56-49 % doing nothing. I'm running this build with the built in kernel (Matr1x) and gapps from cyanogenmod's website. I tried 9/26, 10/01, 10/06, 10/13....all with the same battery drain problem. The ROM is solid and the battery life under usage is amazing (especially with jolla kernel). But battery keeps draining when the phone is idle (even with jolla kernel). This is really frustrating. Any help would be appreciated
Click to expand...
Click to collapse
I noticed the same 1% per hour deep sleep airplane mode drain with both Matr1x and Jolla on my E975 running latest PA. I personally have found faust93's modified Franco to be solid. It gives good battery performance---no drain in airplane mode. You can find it here xep dot 8800 dot org slash e957. Latest version ends with 2010.

RubinCarter said:
I noticed the same 1% per hour deep sleep airplane mode drain with both Matr1x and Jolla on my E975 running latest PA. I personally have found faust93's modified Franco to be solid. It gives good battery performance---no drain in airplane mode. You can find it here xep dot 8800 dot org slash e957. Latest version ends with 2010.
Click to expand...
Click to collapse
Oh yeah sorry, i forgot to mention airplane mode. However, Jolla kernel is the best kernel i've used so far. I tried Franco once and the problem persisted, Will try again. Thankyou

SpaceMonkeyK9 said:
Oh yeah sorry, i forgot to mention airplane mode. However, Jolla kernel is the best kernel i've used so far. I tried Franco once and the problem persisted, Will try again. Thankyou
Click to expand...
Click to collapse
Welcome. One thing that we both implied but didn't spell out is that both the said Matr1x and Jolla are modified with the stock camera port. As far as I know, the modified Franco and UKS by faust93 are the only other kernels as of now that support stock camera driver. For me personally, as mentioned earlier, Franco worked out better when it comes to energy efficiency. On the other hand, the drain problem while sleep in airplane mode does not seem to exist with kernels using the Mako driver---AK, Matr1x, MiRaGe, etc---all seem to hold their juices just fine while idling away.. Have a good one.

Thankyou bud. Will give franco a go

RubinCarter said:
Welcome. One thing that we both implied but didn't spell out is that both the said Matr1x and Jolla are modified with the stock camera port. As far as I know, the modified Franco and UKS by faust93 are the only other kernels as of now that support stock camera driver. For me personally, as mentioned earlier, Franco worked out better when it comes to energy efficiency. On the other hand, the drain problem while sleep in airplane mode does not seem to exist with kernels using the Mako driver---AK, Matr1x, MiRaGe, etc---all seem to hold their juices just fine while idling away.. Have a good one.
Click to expand...
Click to collapse
Franco did nothing !! Battery drain still persistent. Went back to official cm11 and now everything is fine. I love the unofficial ROM ! But this problem is really frustrating

SpaceMonkeyK9 said:
Franco did nothing !! Battery drain still persistent. Went back to official cm11 and now everything is fine. I love the unofficial ROM ! But this problem is really frustrating
Click to expand...
Click to collapse
I hear you. Battery performance is one thing that I am sorta obsessed with in a phone. As I mentioned, I'm on the latest Paranoid Android (4.6 Beta 5) with faust93's Franco 2010 build. When I switch the phone to airplane mode, which is a bedtime routine, it wakes up the next day without losing any juice.
Personally, I think going with official CM11 is a good choice because of its more consistent level of development and support. Like you, I've tried a whole bunch of "private" Roms. At the end of the day, these are usually spare-time endeavors by one or two hobbyists. As a user, you are more or less at the mercy of the devs. Bigger teams like official CM11 and PA reduce this risk somewhat.
Have you troubleshot with Better Battery Stats, which could give you a hint on potential culprits? I've recently found another non-placebo battery saver app call Lion Tamer. You can download via Play and should be able to find a related XDA thread.
Rubin

The only thing i hate about official cm11 is that it's CAF based, which means i can't try all the awesome aosp/mako based kernels on cyanogenmod. Which is why this unofficial version of cm was the perfect solution for me. However the drain issue is just killing me. I get 5.40 hrs sreen on time in around 1 and 1/2 day of usage in official cm11, which is really awesome battery life. But i just don't know why the battery starts acting all crazy when i flash the unofficial build. Gotta give it one more shot.

When I get back tomorrow night I'll do some comparisons with the gproj base and see what I can borrow.
This is getting to me also.
Sent from my LG-LS970 using Tapatalk

ur having the same issue ??

Battery drain when idle
Battery drain when phone is idle is still persistent It actually happens with every gee based build. Only gproj based builds are holding their juices.

Hey @MikeEx what is the solution for the idle battery drain ??

Is there some known problem regarding device encryption?
I tried to encrypt my E975 device but it keeps replying "Bad Password" (which isn't wrong) or restarts before it comes to the pin screen.
Things tried:
- Whiping all partitons / Clean reinstall from scratch
- Stock Kernel / Jolla Kernel tested
Used version: cm-11-20141216-UNOFFICIAL-gee.zip

The latest build of this rom gives me very good battery in standby and usage with Matr1x kernel and ondemand gorvernor.
But the gpu is always scaling on highest freq... Any solution?

Anyone having issues using tethering on the latest version (January 25th build)? I had it working properly on the December 16th build. I did do a dirty wipe when upgrading but I wanted to make sure that tethering was working for others before clean flashing...

europys said:
Anyone having issues using tethering on the latest version (January 25th build)? I had it working properly on the December 16th build. I did do a dirty wipe when upgrading but I wanted to make sure that tethering was working for others before clean flashing...
Click to expand...
Click to collapse
So, I wanted to update people in case they had a similar situation. After not being able to tether initially, I lost GPS yesterday. GPS had been rock solid for about 2 months. The strange thing was that I never lost data.
I was able to fix the situation by using CWM to back up the 1/25th build, flashing back to stock, restoring EFS and getting a solid GPS lock, and then restoring back to the 1/25 build. GPS and tethering now work fine with the 1/25 build.
I hope this information helps someone.

CM 11 vs CM 12.1 for S4 mini

For those who tried them, which works better overall?
Do both have the Stagefright fix?
Does compass work on any of them?
Anything else that doesn't work on CM?
BTW, I have a GT-I9195

monitorer said:
For those who tried them, which works better overall?
Do both have the Stagefright fix?
Does compass work on any of them?
Anything else that doesn't work on CM?
BTW, I have a GT-I9195
Click to expand...
Click to collapse
Both work pretty much the same, though CM11 is probably that tiny bit more stable, bit faster, but more battery friendly. Lollipop has its bugs but "some" people don't seem to suffer the same bugs as others. It's still heavily in development but may work fine for you.
Compass was supposedly fixed in the latest build CM11 and also has latest stage fright fix. Think Lollipops compass works as I haven't seen any complaints, and as long as your using one of the latest builds should also have stage fright fixes.
Personally I'm a fan of CM11 but I use debloated stock as it has the original camera drivers. Just don't like the camera quality on custom builds. Though it's not terrible on either of them. Also some apps for me work better on stock.

In the mean time I installed 12.1.
Compass does not work.
The rest seems to work alright, but it's too early to say. I did have a couple of crashes, but not of the system itself. When I played music from two apps at once AudioFX crashed. And "Trebuchet" crashed once, don't remember how.
GPS might be taking a bit longer to get a fix than with stock, but I'm not sure.
Well, at least I hope to avoid the idle battery drain that I got on stock.
Overall the system seems fast enough, but the "fade to dark" effect after some idle time (and back to bright) is pretty choppy/slow. Not sure if that's intended or not.

Have you tried the kernel by SilviuMik for stock ROMS? Is meant to have battery fixes for standby. Though I have never suffered bad standby times, I do like this kernel.

Hi !
Yes...in reality ,objectively , there are only cm11(last release on 01/09/2015) and stocks who work fine .
At this time ,all Lollipop customs are not stable at all for daily use because umpredictables behaviors (maybe it work fine for some members but thes roms may have dysfunctions suddently with "majors big buggs)
With news big security problems ,all JB & KK customs roms are totaly "obsolete" (it's a pity because kk slim , pacman... work fine!) ,they are unusable because not secure...
-The best choice for a good daily use is a stock rom (or STE by ploiki ! Great buid !) with alexax's 0.9 kernel !!! Lighten by own debloating ...:good:
Good baterry life and good choice of parameters with "aduitor kernel"
And stock camera is good..
N5 foyr mini &S6 lollipop project seem good according to some members but i personnaly have had some problem...
-Second choice with cm11 but it's necessary to love customs and it need to replace some "poor" cm stock apps (camera...etc...)
I test the last release now but with recomended parameters , i generaly have found that the battery life is not as good as stock firmware kk&alexax kernel

I found cm11 more stable