I tried to post this in the CM10.1 thread but apparently I need 10 post elsewhere first.
There seems to be a problem with setting the Maximum CPU Frequency option in cm-10.1-20130210-NIGHTLY-skyrocket. It will reset to default, or probably never sets, as soon as you leave the screen. The minimum frequency seems to work fine.
Unsure if the developers are aware of this but it would be cool if it could get looked at in the next release. I never game on my phone so I really have minimal reason to keep it above 1GHz.
Thanks.
Well it IS just about a week old..... Try using a different 4.2 kernel. I think there are 2 of them out there somewhere.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
this is a nightly non stable build. there is a bug report option somewhere on the cm site, i just forget where exactly. check the bug reports, and if its not there help the team by reporting it.
I have this same issue with with CM 10 Stable, the latest CM 10 nightlies, and CM 10.1 nightly. I am thinking its an issue that all of them have.
Related
I am on AOKP B31 without fast charge enabled but seem to have a problem with the phone charging when off. If I plug it into a USB or wall charger, both samsung, the initial battery screen will come on but after the screen turns off it will not turn back on. I left it there for 30 min turned it on and it showed 50% more battery. We all know with a samsung that is not possible. Just want to see if others are having this issue, or a fix.
Thanks in advance.
I am sporadically having this issue as well- Samsung charger, AOKP b31. I will play with it over the weekend and see if I can figure anything out. For the moment I am not seeing this behavior, but initially after flashing I did...
I have not had this issue on any other THS or AOKP build and I have used a lot of them. The last one I was on was milestone 4 and it was fine.
Sent from my AOKP ICS captivate using XDA
Hmm, still doing it. Setting the Min CPU to 200MHz has not helped, as I have seen posted elsewhere. Charging screen turned off at some point, and when I booted up it was at 64% (from 7%). I'm not super worried about it though, seeing as how I flash like crazy and will not be on Build 31 for any length of time. If I get this on other builds or other Roms I will update again.
Edit: Build 32 is out, so I am going to flash and see if that resolves the issue. I am wondering is this is a kernel issue, as the Glitch for Build 31 was the first time I had switched from Glitch version 14 beta 6. Maybe I'll try the Semaphore kernel if the issue remains.
I flashed 32 and it still is the same issue. Also tried the min CPU increase but nothing. Hopefully it will be fixed soon. My concern is that it will continue to charge after 100%.
Sent from my SGH-I897 using XDA
read the first post of AOKP. report bugs where it tells you to. they will not look here, or will they care if they do look here, if you do not follow their instructions for reporting bugs.
look to see if the bug exists, and if it is there, click the STAR to vote for the issue as that page says to do.
I have read the OP but I did not want to flood the bug tracker if it was a problem already found or known. I did not have the 10 posts needed to post in the development section, so I figured start this to see if anyone had an issue. I know how much everyone hates the development thread being diluted with dumb question after question. I did report it on the bug reporter site.
P.S. - Thanks for your essentials mod, makes everything much easier.
Just wonder - will disable fast charge help?
I have not enabled fast charge. I thought that only effects charging when on USB? I could be wrong though.
Sent from my SGH-I897 using XDA
I have been testing with both i897 and i9000 bootloaders. This may be a Glitch kernel issue, as I have flashed Semaphore ICS kernel 1.0.0 and have not seen this. Looks like there is already a bug reported in the AOKP page. Not a huge concern though, I think, because the phone seems to charge nevertheless.
I've searched high and low for this issue, and I've found hits, but nothing that seems to help me or fully answer my questions.
I flashed CM10 nightlies straight away when I got my new Galaxy Tab 2 10.1 last week. Whilst it's a great ROM like with all official CM's, the tab sporadically doesn't wake up after a sleep.
Now the known issues from http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-P5100:Nightly:Known_issues says:
Code:
The screen many a times does not respond to touches for unlocking, needed to reboot the tablet.
Which seems to be what I'm experiencing. All I would like to know if I'm the only one experiencing this issue and if not, do people know if the issue is being actively worked on and is there a workaround in the mean time?
Thanks in advance.
Are you overclocking?
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Are you overclocking?
Click to expand...
Click to collapse
Thanks for the response. I'm not overclocking running at the default 300MHz to 1008MHz from the stock CM kernel settings on the interactive govenor.
I did however install the kernel from the AOKP thread. Ran that over the weekend and never saw the screen wake problem again. As soon as I installed the latest CM nightly the screen wouldn't wake from sleep again so I re-installed the AOKP kernel and everything was working again.
(I also noticed that the AOKP kernel came with CPU settings of 300MHz to 1200MHz on the interactive govenor - I put that back to 300MHz to 1008MHz for safety but didn't see the screen wake problem during my testing with the higher clock speeds).
Has anyone got any info on this screen wake issue?
The amount of times I was having to reset the tablet when I was using the stock CM kernel meant it wasn't usable as a daily device until I installed the AOKP kernel. How can I get in touch with the CM guys to see if I can help with this screen wake issue?
You'll need to find a proxy to post for you in the dev forums in Codeworkxx's thread. You'll need a logcat of the issue.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
You'll need to find a proxy to post for you in the dev forums in Codeworkxx's thread.
Click to expand...
Click to collapse
Or you could just go to their irc channel #teamhacksung-support @freenode
ok thanks, will try to get a logcat and post is in the DEV forum
My POWERAMP, I did buy the unlocker. Keeps skipping like there's some major app usage going on. But I check and memory and CPU usage is MINIMAL! Any ideas? Going flash to most updated see what happens but wanted to let the community know deuces! EggyT
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Did you try clearing data?
The only issue I have with pa is the lock screen function is a bit wonky.
Im on ... TY I will reply with an answer ASAP Cheers
Well it is not happening as freq but it is just a matter of time before the data levels are where they were at again.
This is the first Nightly build this has happened on... I was planning on updating to 1211 right now let's see how that effects it.:laugh:
Ok so I did a clean everything and Flashed the most recent nightly and well Power Amp was Rocking I was waiting to see if something happened like last time and nothing... so then I went to multi tasking and still nothing so I am not sure what the problem was... let's give it 2 of 3 days on this nightly and see what happens.Cheers all. If any of this is helpful hit thanks
Good. I'm not a fan of dirty flashes myself. I also check the BBQ for nightly changelog and install accordingly. I'm still rocking 11-30. Issues = none
I currently have the OmniRom 4.4.4 insalled on my Xoom Wingray device. I poked around and saw the EOS Rom. I'm really torn if I want to go and re-wipe and rebuild my device on the EOS rom. What's the pros and cons of each rom based on opinions of the users running each one. Please no flames or fanboys, just honest things you like about your particular Rom.
AlphaW0lf2014 said:
I currently have the OmniRom 4.4.4 insalled on my Xoom Wingray device. I poked around and saw the EOS Rom. I'm really torn if I want to go and re-wipe and rebuild my device on the EOS rom. What's the pros and cons of each rom based on opinions of the users running each one. Please no flames or fanboys, just honest things you like about your particular Rom.
Click to expand...
Click to collapse
This whole section seems to be lacking people who are willing to or have experience with each releases. But what are your thoughts on Omnirom? Why did you choose that over CM 11 and now looking at EOS. Trying to get as much info as possible before i consider flashing this old tablet and squeezing more life out of it
I chose the Omnirom because it was the first I heard about. I wanted android 4.4.2 and it seemed all google searches pointed to Omni. Now after running it for a week or two I deal with bugs that I don't want to fight with forever. Volume control doesn't work, random chrome crashes and now tablet reboots. I tried to reach teamomni but no luck. And EOS has built and published nightlies more recently than omni. I know I'm pushing this tab!et beyond its years. I figure this is the end of the road for this device, so I want to squeeze every ounce out of it. I can't thank both teams enough for their work. It's more than I would be capable of ever doing.
AlphaW0lf2014 said:
I chose the Omnirom because it was the first I heard about. I wanted android 4.4.2 and it seemed all google searches pointed to Omni. Now after running it for a week or two I deal with bugs that I don't want to fight with forever. Volume control doesn't work, random chrome crashes and now tablet reboots. I tried to reach teamomni but no luck. And EOS has built and published nightlies more recently than omni. I know I'm pushing this tab!et beyond its years. I figure this is the end of the road for this device, so I want to squeeze every ounce out of it. I can't thank both teams enough for their work. It's more than I would be capable of ever doing.
Click to expand...
Click to collapse
This is what I'm doing as well. Hadn't used the Xoom in forever but figured I'd try to squeeze more life out of it at this point until Nexus 8 or 9 (whichever it's called) comes out. I was running Omni and kept getting "bug reports", so I've switched to EOS due to the fact that they are more actively publishing updates to the ROM.
Only been on EOS for a day or so, but so far so good. With No-frills CPU control installed the Xoom seems to be running fine with no bugs to report. Settings in no-frills:
CPU Max: 1.504 GHz
Min: 456 MHz
Gov: ondemand
i/o scheduler: row
I just want to restate that I value the time and effort of ALL of these developers who graciously give up hours of labor to do this work. I would hope no one is offended by any of my previous statements of issues.
Omni vs TeamEOS
At first I've installed Omni. I was very happy with it. But after some time I've got performance problems. Also Chrome was freezing many times while browsing around.
So I decided to switch to TeamEOS. I was a fan from EOS since the early days. They kept my Xoom alive. But unfortunenatly I got the same problems on TeamEOS with Chrome. It kept freezing.
Read http://forum.xda-developers.com/showthread.php?t=2738705 if you have the same problem.
At last I am also happy with TeamEOS and it's difficult to say which ROM is better. There are some differences in the preferences and Omni ROM seems to be a bit ahead but at last I'm ok with was TeamEOS offers.
fricklr said:
At first I've installed Omni. I was very happy with it. But after some time I've got performance problems. Also Chrome was freezing many times while browsing around.
So I decided to switch to TeamEOS. I was a fan from EOS since the early days. They kept my Xoom alive. But unfortunenatly I got the same problems on TeamEOS with Chrome. It kept freezing.
Read http://forum.xda-developers.com/showthread.php?t=2738705 if you have the same problem.
At last I am also happy with TeamEOS and it's difficult to say which ROM is better. There are some differences in the preferences and Omni ROM seems to be a bit ahead but at last I'm ok with was TeamEOS offers.
Click to expand...
Click to collapse
The chrome issue boils down to a tegra video driver. It's closed source and has not been updated since the last official release which I believe was 4.1.2
This issue effects many things video related some of it you may see most of it you'll never notice. Since its a closed source driver it's likely to be and issue we will just have to deal with
sent from space
runandhide05 said:
The chrome issue boils down to a tegra video driver. It's closed source and has not been updated since the last official release which I believe was 4.1.2
This issue effects many things video related some of it you may see most of it you'll never notice. Since its a closed source driver it's likely to be and issue we will just have to deal with
sent from space
Click to expand...
Click to collapse
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
After some days of using TeamEOS... The battery usage seems to be much more better!
On the other side TeamEOS freezes from time to time. Only a reset helps.
But hey, there's KK on my Xoom
AlphaW0lf2014 said:
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
Click to expand...
Click to collapse
Are you able to cast screen with chromecast ?
I have de Omni 4.4.4 on my xoom and the cast screen do not work, even with mirror enabler app.
Xoom won't be able to, doesn't matter which Rom, it's hardware level, even if I add all the required files to the make file and enable it as soon as you try it reboots. It's the same issue with screenrecord
sent from space
AlphaW0lf2014 said:
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
Click to expand...
Click to collapse
I've used each of the Kit Kat builds and I finally settled on TeamEOS. This ROM had the most updates and continued to have development after nightlies stopped for Omni and CM. I believe each of these ROM's are really great and each have given new life to our tired Xoom's. The only way you can really tell which ROM is best is to try them and see which you like the most. Hopefully, someday we'll be asking the same questions about which Lollipop version is best, or that may just be wishful thinking. TeamEOS is baked already OC'd to 1400 and you can tweak it higher if you want (I use 1600). I've downloaded Trickster MOD from Google Play and I use it to control governor and other settings. As far any SOD's, I believe you can really minimize the concern if you use Trickster MOD and adjust your CPU min to at least 312 or higher. I had an occasional problem with Chrome so I switched to Chrome Beta and it seems to cause less problems. Some folks will have problems while others seem to get by OK. The stock browser is still pretty decent and gives good performance. I also have the Dolphin Browser but don't tend to use it very much.
---------- Post added at 08:15 PM ---------- Previous post was at 08:11 PM ----------
fricklr said:
After some days of using TeamEOS... The battery usage seems to be much more better!
On the other side TeamEOS freezes from time to time. Only a reset helps.
But hey, there's KK on my Xoom
Click to expand...
Click to collapse
Try downloading Trickster MOD from Google Play and using it to set your cpu min to at least 312 or higher. This may help with freezes.
Q&A for [ROM][OFFICIAL][CyanogenMod 11.0 Nightlies for Skyrocket][TeamChopsticks]
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.
Before posting, please use the forum search and read through the discussion thread for [ROM][OFFICIAL][CyanogenMod 11.0 Nightlies for Skyrocket][TeamChopsticks]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Serious lag
Why is cm11 lagging so bad, dialer hangs like crazy. Been updating(not clean wipe install) for months now could that be the culprit?
calexil said:
Why is cm11 lagging so bad, dialer hangs like crazy. Been updating(not clean wipe install) for months now could that be the culprit?
Click to expand...
Click to collapse
idk as im not on it but clean install is usually where to start
Hi,
I recently installed CM11 on my skyrocket, and now the g sensor calibration is off, with no option to calibrate. Is there a way to calibrate on kitkat Rom?
Sent from my MI 3W using XDA Free mobile app
calexil said:
Why is cm11 lagging so bad, dialer hangs like crazy. Been updating(not clean wipe install) for months now could that be the culprit?
Click to expand...
Click to collapse
Try changing your governor. I use performance because I don't think interactive is working right almost always stays at lowest CPU speed. I've tried tweaking the parameters on interactive but didn't seem to help. Granted I'm no expert
Also keep an eye on ram. I'm regularly maxing out and trying to keep things closed. No lags coming back so far.
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
tommyjt24 said:
Try changing your governor. I use performance because I don't think interactive is working right almost always stays at lowest CPU speed. I've tried tweaking the parameters on interactive but didn't seem to help. Granted I'm no expert
Also keep an eye on ram. I'm regularly maxing out and trying to keep things closed. No lags coming back so far.
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
is it safe to force it into performance all the time, I would think that would mess with the battery life pretty bad
not to mention shortening the live of the processor....
I don't see any issue in performance. Battery life is negligible since I have to charge once a day anyway. The theory in performance (granted I don't know if I even really buy it) is that the phone goes back to deep sleep faster when using the performance governor. The battery life is probably only sacked if you have a lot of off screen activity that would not otherwise need performance. If someone knows how the values to tweak to get interactive to work better I would try it out. I've played with various values but really don't see it shifting.
So many Questions, so little time.
Is this device abandoned? It seems like the nightlies are slowing down. Is it a good time to move to another device? Is Cm12 coming to skyrocket?
There's an unofficial cm 12 available now. I'm using it! It's not perfect but it's very good. Sultanxda is the developer and he is updating it on a regular basis.
Hi, I don't know if this is the appropriate place to be posting this, but here goes:
I am currently running the CM 11 nightly 20150510 on an i727r. I've been having problems with my mic for the longest time (I will try calling other on VoIP and they wouldn't be able to hear me and vice versa, or I would pick up a VoIP call and I can hear them but they wouldn't be able to hear me), and it's come to a point where I need the call function.
I understand that if I flash the CM 12 custom rom, there seems to be an audio fix in place (correct me if I'm wrong about this); however, I am also in the middle of a 4 week exam period, AND I'm based in a different country, so I don't want to replace my current ROM with the stock firmware (which would unroot my phone and re-lock the SIM carrier), and at the moment, I don't have time to figure out how to switch over while keeping my notes, calendars, schedules, contacts, etc. intact.
I saw the audio _update zip that @bryan2894 has posted. I was wondering; can I take a shortcut, and just replace these files in the device folders with the updates from the zip?