Database Develop

TP CM9 changelog and known issues?

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?

[Q] Bugs, bugs, bugs

Dear all,
it is my first try to run cyanogenmod (10.1 Rel 7) on my SGS+. But when using it, I immediately found plenty of issues:
- Navigation is only partially working. After a while the maps starts jumping around and dark semi transparent overlay sections appear so that one cannot see the full map. In the forum I found the hint to deactivate Dithering. Done. Only little improvement.
- Alarm clock is not working when the phone is turned off.
- Screen goes off after dialing a number (workaround: lift phone to the ear and lower it back down -> screen is on again).
- No FM radio app (in comparison to the stock rom).
- Skype video is still upside down (as with stock rom).
My colleagues were very enthusiastic about cyanogen mod. In contrast, I haven't really detected the advantages. Are the developpers still working on the issues? Is there anything I can do to support you guys?

To answer your queries:
-Navigation- use the bug reporting method on the CM10.1 forums and submit it as a bug report either in the S CM10.1 thread or on JIRA. More details are given in the CM10.1 thread OP.
-This feature doesn't work even on stock. Its not a bug, and its not just CM10.1. MIUI allows this apparently however.
-This is normal, not a bug either. When you call someone the screen goes off because you're going to lift it to your ear anyway. The 'workaround' is actually the proximity sensor, and a similar thing happens on stock roms. The only solution to this is to press a button when the screen initially turns off.
-FM Radio isn't included in CM builds by default, as the API needed for it needs some intense changes made to it. There's Spirit FM if you want to run the risk. Check out the thread for more information.
-Skype on CM10.x is a known issue
Try CM10.2 and see if that helps the first issue, if not, report it using the methods in the CM threads. Otherwise everything else is as normal/known.
Sent from my GT-P7510 using Tapatalk HD

Irrespective of a few bugs there are definitely a number of advantages to using CM.
Have you noticed how smooth CM10.1 is? For me it's smoother than stock. Definitely a plus.
The pre-installed applications are more polished/work better and you actually have control over them. Don't like one? You can remove it. Unlike stock where you are stuck with a lot of junk (unless you have rooted your phone).
Bugfixes! We're no longer stuck with a 2 year old version of an OS for which we don't receive any bugfixes.
Customizability. CM gives you a lot more features to have your phone just the way you want it.
Overclocking and undervolting.
Not everyone had this problem, but my phone took > 5 minutes to get a GPS fix on stock. It takes < 10 seconds on CM.
And that's just what I came up with in a few minutes. Yes, there will be a few bugs and features which you think are weird (like the screen turning off when you make a call) but you'll find that on any piece of software. If you personally feel CM is a downgrade then it's your right to think so and go back to stock ROM. That doesn't mean the average xda-user is going to agree with you though.
(I think there are also a few ROMs based on the stock 2.3.6 versions, but since I've never used them I wouldn't know which ones are worth trying.)

[Q] 4X HD lag issue

Hello,
For the last 6 months or so, I've experienced many lag issues with my device. At the begging, I had a CM11 ROM installed on my phone, so I decided to revert back to the V20B official european firmware because I thought those lags were related to the ROM. But nothing changed, and as of today I still have responsiveness issues.
This lag issue appears from time to time, and makes my device basically unusable. It feels like the whole CPU is hogged by an application, or like I underclocked my device to 53mhz on purpose. During these lags, trying to wake up my device will take up to 5 seconds, and navigating the main screen will be nearly impossible. Also, my phone will get very hot which would imply that my CPU is indeed used by an application. Sometime the issue will disappear by itself after a few minutes, but I usually reboot the device which temporarily fixes the problem.
I have tried to disable LG MLT, and I think it helped but the lag still occasionally occurs.
I don't really use third party applications either.
I think these lags might be related to the Google Chrome browser, but it doesn't make any sense as it is an official app.
Anyway if any of you have an idea on how to fix the issue or how to find the application/service/whatever hogging the CPU I'd be grateful
Thanks !

I did experience such lags in CM11 after a few days of usage.But talking about stock, these freezes sound bit weird.You might want to check your installed apps.Download watchdog lite from play store and let it watch on agressive mode.Also check if your phone is hot when these freezes occur, might be the throttling kicking in.
I also experienced this kind of lags due to bad gapps I had installed back in the day, though stock ROM comes with gapps so it's not that.

Thanks for your reply,
I installed Watch dog lite and I'm now waiting for an alert. I hope it will give me the name of the culprit

If you are rooted which i assume you are. You can try app from playstore called "lagfix" (fstrim)
Sometimes really helps. Sometimes it doesn't

Phone screen slow wake from sleep ocassionally (several minutes)

I've noticed it ocasionally on my Atrix HD for quite a long time but though it was just my phone. I got my SO the same phone and the same thing has been occurring. It doesn't happen all that often, but when it does, it's very frustrating. It still functions underneath: if it's in a phone call or playing sound, you can adjust the volume. Can take screenshots, or hold power button and it will vibrate (e.g. when the menu pops up).
We are both on CM11 M snapshots and running xposed with nlpunbounced. I believe I remember it occurring before we started using xposed. Also, we've been on CM11 since something like M3. Have run fstrim on all of the partitions (except for my /data partition since I encrypted it, and last I checked the fix for fstrim on dmcrypt wasn't ported to our phone). Anyways, does anyone else have this problem? If not, what could it be? Being an very occasional thing, it's hard to test and capture logcats from.

For anyone curious about this, it's been called the "I/O Stall" in the razr hd thread. They suggest a solution, which I'm trying out:
http://forum.xda-developers.com/showthread.php?p=57605249#post57605249
I have switched to the F2FS and it seems much less common, so we'll see how much the swappiness setting helps.

C6903 Xperia Z1, baseband 8974-AAAAANAZQ-10270045-39, random crashes, please help

Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.

SpGG said:
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
Click to expand...
Click to collapse
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...

optimumpro said:
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
Click to expand...
Click to collapse
I didn't change anything. Same thing when I went for a new nightly of cm12.1 I did nothing out of the ordinary. Since I did not have new problems since the above mentioned, I didn't delve any further. Today I had another, interesting issue. No one was able to call the phone and I wasn't able to call out, even though the network showed up as fine with full bars. This lasted for several hours. I went into flight mode and back out of flight mode and the issue was fixed. Several SMS arrived about calls missed. And again, I have no idea if this was caused by the hardware, an issue with the software or even the network.
And that is the frustrating thing: How can I find out who the culprit is? Are there good system crash diagnostic tools? Because so far I haven't seen anything.