Is Airplane mode supposed to be on all the time?
Has anybody found a good wi-fi fix yet (lots of on/off when I take it out of sleep)?
I have an app that says it can't be played on an unstable platform, any idea why?
Is there an alternative to SetCPU for CM7 that works?
Thanks everyone
buffnutz1 said:
Is Airplane mode supposed to be on all the time?
Has anybody found a good wi-fi fix yet (lots of on/off when I take it out of sleep)?
I have an app that says it can't be played on an unstable platform, any idea why?
Is there an alternative to SetCPU for CM7 that works?
Thanks everyone
Click to expand...
Click to collapse
NO.
Not that i know, Some people have problems some don't
No idea. What app? I will try it on mine.
I have not hear of anyone using one, but there are several CPU tuners on the
Market try some out and let us know.
Someone reported success with "CPU tuner" from market (free). I did not try it yet myself. Note that CM7 has most of SetCPU functionality built in, the only thing missing in profiles support.
buffnutz1 said:
Is Airplane mode supposed to be on all the time?
Has anybody found a good wi-fi fix yet (lots of on/off when I take it out of sleep)?
I have an app that says it can't be played on an unstable platform, any idea why?
Is there an alternative to SetCPU for CM7 that works?
Thanks everyone
Click to expand...
Click to collapse
I turn airplane mode on, as a matter of fact.
Go into Settings > Wireless & Networks > Wi-Fi Settings > hit Menu > Advanced > Wi-Fi Sleep Policy > set to Never. This keeps Wi-Fi on, but it doesn't shut off every time the screen goes off or appears to the system to be idle.
Which app?
For now, I just use CM7 to set my governor to Conservative. Not having policies does suck, but I can deal with it for now. CM has much bigger fish to fry at this point.
My airplane mode is on all the time but my Wifi always works. Are you running nightly 8 or later? 12 is pretty good. Wifi does not seem to lag coming out of standby at all.
What app do you have that thinks you are unstable? It is probably possible to spoof it into thinking it is on a Nexus or something.
I am 99% sure that someone involved in CM development said explicitly not to install SetCPU, because CM has an internal clock speed controller. I can verify that it does scale the processor up and down on it's own but beyond that I do not have details.
The app is Homerun Battle 3d. My favorite game, but it just won't work.
Apparently I really fell behind, because I'm on Nightly 6. When I upgrade to the latest, what upgrades should I expect besides better Wifi?
Related
To my knowledge, there is no thread dedicated to the new numerical releases of CM. Let us start with the newest, CM 6.0.2.
Please post your anecdotal data, including benchmarking scores, bugs, and glowing experiences. Perhaps this will serve as an unofficial repository for issues that prove consistent.
Note: After modifying my WiFi settings, specifically disabling sleep mode while the screen is off, I've encountered no related instability.
Mail FC Fix: http://forum.xda-developers.com/attachment.php?attachmentid=394316&d=1283500340
Systemic issues yet to be addressed:
-LEDs do not work save for charging
-Outgoing calls initially drop before reconnecting
-Lockups or reboots, likely stemming from SetCPU
-OS does not recognize internal storage
Does this version fix the wifi not staying on?
Did you change your settings to Never sleep for wifi and just left the wifi on? Thanks...I want to try different settings and see if I can eliminate reboots/shut downs.
are we waiting for the nightly for the newest fixes like LEDs or is there gonna be a new release like .3?
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
seanmcd72 said:
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
Click to expand...
Click to collapse
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I would have to second the issue with SetCPU. As soon as I overclocked it and began using the rom I noticed the phone would get hot abnormally fast and would reboot a few times within the first few hours. Not sure what is going on here as it worked fine on the RC.
Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I didn't even notice setcpu till you said that. Phone was back to 998mhz
Sent from my INCREDIBLE using XDA app
My phone doesn't vibrate when I receive an incoming call when the phone is set to vibrate.
Has anyone else noticed the keyboard lag when using the Messaging app? Browser and this xda app seem to work fine with no lag..
Other than that, smooth.
dnoyeb said:
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
Click to expand...
Click to collapse
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
I get random reboots and freezes every thirty minutes if so on a fresh wipe of 6.0.3 I tried with setcpu and without but always with the built in hotspot running. Same issue since RC3
LED notifications dont work. LauncherPro Plus FCs on every reboot, other then those things im good with it, great wallpapers , great rom
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Panda Fuzz said:
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Click to expand...
Click to collapse
And you know the issue is the kernel because...?
mp3sum said:
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Click to expand...
Click to collapse
actually if you read the thread, you'll see koush himself is in there dealing with 6.0.2, offering up kernels and fixes...
he just hasn't updated the topic title.
Okay this may be a stupid question but how do I apply the mail fix?
mp3sum said:
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
Click to expand...
Click to collapse
Battery life was down to 81% 11 hours later, and the phone had been placed in Airplane mode while running Gentle Alarm and a few widgets (no auto task killer).
Breakdown:
System 0.6%
System Processes 0.3%
System Panel 0.3%
android.process.acore 0.1%
Plus several honorable mentions with 0.0%. I have yet to perform this experiment with Ruby or ID.
App: xtr50fix Android 2.1 only.
I made this app to try to help those with the 50% time without a signal issue. Learn more here ( http://forum.xda-developers.com/archive/index.php/t-647980.html)
The one trick that works with most 2.1 Eris ROMs is the airplane mode trick. All you do is put your phone in airplane mode for a little bit and turn airplane mode off and it fixes the issue.
Basically all this app does is upon boot, puts the phone in airplane mode then waits 12 seconds and then turns off airplane mode. Finally, it kills the service so it won't run again until the next reboot.
I know it's not elegant or anything, but it seems to do the job. There are no settings and there is no icon for the app. Just install the .apk and reboot your device.
Please let me know any feedback you might have... good or bad. Thanks!
2/2/2011 - v1 - Initial build. Seems to work fine on xtrROM and xtrSense.
Added some checks to make sure you are not already in airplane mode upon boot.
Sounds interesting, thanks! I just went back to xtrSENSE so this is perfect timing.
has anyone tried this app yet?
I went with this route and it helped me
[How-To] Better battery life, reduce Time Without Signal.
http://forum.xda-developers.com/showthread.php?t=651848
I read that some users report that the 'airplane trick' doesn't always work for them.
moos3y said:
I went with this route and it helped me
[How-To] Better battery life, reduce Time Without Signal.
http://forum.xda-developers.com/showthread.php?t=651848
I read that some users report that the 'airplane trick' doesn't always work for them.
Click to expand...
Click to collapse
Yes, that works as well, however, you still have to do that every time you boot up.
This seems to have worked on my optimus v. Thanks for your efforts!
Prior to this, I was constantly getting the 50% without signal mess...
Works perfectly on my Optimus V. Thanks so much for developing and sharing this fix.
Thank you lotus22! This has been included in the latest release of xtrSENSE http://forum.xda-developers.com/showthread.php?t=726467
Would this work on a Droid X? I get that bug and I'm rooted with stock 2.2.
chadw80 said:
Would this work on a Droid X? I get that bug and I'm rooted with stock 2.2.
Click to expand...
Click to collapse
I'm only replying so you don't feel ignored. No idea, myself, but can you do a nandroid on the X and try flashing this to see? You might be the first person to try, so you can let us know if it works!
For the record to everyone, this seems to work just fine with Gingerbread ROMs, too.
roirraW "edor" ehT said:
I'm only replying so you don't feel ignored. No idea, myself, but can you do a nandroid on the X and try flashing this to see? You might be the first person to try, so you can let us know if it works!
For the record to everyone, this seems to work just fine with Gingerbread ROMs, too.
Click to expand...
Click to collapse
Lol appreciate it! Unfortunately it didn't put my phone in airplane mode when it booted back up.
I don't have a Droid X to test on... however, I did compile the program with the Android 2.1 SDK so it should work on anything with >= Android 2.1
Note: Don't flash this program. Just install the .apk like normal.
zach.xtr said:
Thank you lotus22! This has been included in the latest release of xtrSENSE http://forum.xda-developers.com/showthread.php?t=726467
Click to expand...
Click to collapse
Thanks Zach! Glad you included it. I bought a Motorola Droid off my friend so I don't use an Eris for my main phone anymore. I'll have to test this out on my mom's Eris which uses xtrSense!
This app fixes the 3G drops with my Optimus V. If anyone is looking for automated reboots in order to automatically apply this fix every day, I use Phone Prioritizer.
Thanks for this. Hopefully my battery life increases.
Can someone tell me how to install the fix on an Optimus V? I tried downloading it directly and I get a message saying it is unsupported. I also tried installing it from gmail and it didn't work either.
I am about ready to return the phone if I can't get it to work.
Thanks,
Paul
Make sure in settings->Applications-> you turn on Installing Apps from Unknown Sources.
TWS/data drop fix
The fix50 app did fix the TWS problem on my optimus but didn't seem to do much for the battery or fix the data drop issue. I ran across this fix posted by greenmonster on an Android Central forum (http://forum.androidcentral.com/optimus-v/57943-excessive-battery-drain-even-standby.html):
To fix the issue, dial *#*#4636#*#* and it will load the testing screen. You do not have to press call. Select phone information.
My understanding of the bug is that even though the preferred network is set to "CDMA auto (PRL)", it is actually set to "GSM/CDMA auto (PRL)" because of a display bug.
The fix is to press Menu and then "Select radio band". The process will then force close. Go back to Phone info and select "CDMA only" and then select "CDMA auto (PRL)".
Click to expand...
Click to collapse
I'm going on day 3 now (no reboot) and have had a noticeable increase in battery life an no data drops that require an airplane mode toggle. Any way this might be made/incorporated into an app similar to fix50?
Data drop/TWS update
So I finally had a hiccup about 9:00 last night that caused a data drop- it was right after I lost a phone call & during a pretty serious storm, so don't know if that affected anything. I'm still pretty happy- I've never gone more than three or four hours without having to do the airplane mode toggle due to data drops- 60 hours without a drop is encouraging!
Time without signal also stayed in the single digits...
Installed and working on my Captivate running Froyo. Good stuff.
Sent from my Captivate
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?
Anybody know why Wifi is throttling down to about 500kbps when the screen turns off? Otherwise I get 30mbps. Is it the CPU governor?
xdadevnube said:
Anybody know why Wifi is throttling down to about 500kbps when the screen turns off? Otherwise I get 30mbps. Is it the CPU governor?
Click to expand...
Click to collapse
This has always been the case with Android devices, not sure about others. I believe it's the CPU speed being throttled.
There are various apps to work around it if you have to.. I just set it to leave the screen on for an extended period when I'm transferring stuff to it.
khaytsus said:
This has always been the case with Android devices, not sure about others. I believe it's the CPU speed being throttled.
There are various apps to work around it if you have to.. I just set it to leave the screen on for an extended period when I'm transferring stuff to it.
Click to expand...
Click to collapse
My Samsung Droid Charge and my HTC Rezound both transfer the same speed whether the display is on or off. They transfer around 15mbps and 20mbps, respectively. The Nexus 7 dropping from 30mbps to about 400kbps is pretty disappointing. It jumps right back up as soon as the screen is on. What workarounds have you heard of? I would like any hints or tips to get me started in the right direction to find a solution.
I encountered the throttling with BAMF and CM10 ROMs, with the stock and Trinity kernel. These are the only combos I tried.
xdadevnube said:
My Samsung Droid Charge and my HTC Rezound both transfer the same speed whether the display is on or off. They transfer around 15mbps and 20mbps, respectively. The Nexus 7 dropping from 30mbps to about 400kbps is pretty disappointing. It jumps right back up as soon as the screen is on. What workarounds have you heard of? I would like any hints or tips to get me started in the right direction to find a solution.
Click to expand...
Click to collapse
Set display to always on and turn brightness all the way down till u figure out what's doing it.
Sent from my ADR6425LVW using xda premium
AHOY!
I found a solution, credit goes to the gentleman who posted this thread:
http://forum.xda-developers.com/showthread.php?t=1625705
Check it out for interesting info.
The app that fixes the issue, WiFi High Performance Widget, is not compatible with the Nexus 7 according the Google Play store. However, I just downloaded it to my phone, then used Titanium Backup, sent the Titanium files for that backup to the Nexus 7, and restored with Titanium Backup.
I haven't noticed any problems with it so far.
App found here.
https://play.google.com/store/apps/details?id=com.ratcash.wifiperf
It's because a new API was introduced in Honeycomb, allowing the wifi chip to go into a lower power mode if compatible. Unfortunately, apps have to 'opt-in' to high performance wifi, which they often don't do..
I'm sure once the interface has been looked at by kernel devs, a switch will be included. Certainly morfic has one for his Trinity kernel on the Galaxy Nexus, and given time , he probably will do again
xdadevnube said:
AHOY!
I found a solution, credit goes to the gentleman who posted this thread:
http://forum.xda-developers.com/showthread.php?t=1625705
Check it out for interesting info.
The app that fixes the issue, WiFi High Performance Widget, is not compatible with the Nexus 7 according the Google Play store. However, I just downloaded it to my phone, then used Titanium Backup, sent the Titanium files for that backup to the Nexus 7, and restored with Titanium Backup.
I haven't noticed any problems with it so far.
App found here.
https://play.google.com/store/apps/details?id=com.ratcash.wifiperf
Click to expand...
Click to collapse
Thanks for this, I just installed it on my Galaxy Nexus, went into to data/app and sent the file to my Box account then installed it that way.
Since it is a free app HERE is the link to the file in my Box account, just download it and install it.
Hey guys,
at the moment I´m running up-to-date CM 12 Nightlies using stock kernel.
As stated in the title, my phone crashes when I select the "Performance" profile in the Performance Settings.
The phone does however NOT crash when I put the performance profile to "Balanced" or "Battery Saving"
The phone crashes a few seconds after I close every app and then put it into sleep.
I have got no changes made to any CPU settings.
I have not found any advice in making the settings work again properly by myself.
Not being able to use the "Performance" profile is not that big of a problem but at the same time it is pretty annoying, so I would be very happy if someone would share his knowledge about solving my problem.
Have a great day!