Develop Bugs

CM6.0.1 issues

I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.

You should be using the CM6 kernel only. I'd guess that's the source of your woes.
Sent from my Incredible using XDA App

@rmaccr
Only use the kernal that comes with the rom. CM6 is very picky when it comes to custom kernals. I tried to flash hydra and kingx kernals and no go. Just use the original kernal and u should be good.
Sent from my Incredible using XDA App

Make sure you're wiping data/factory reset and wiping the cache partition in Recovery before you install a different ROM.
There's also an alternate kernal you can flash if the stock CM6 kernel is giving you problems - search the RC3 thread to find it.

Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.

rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.

rmaccamr said:
I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.
Click to expand...
Click to collapse
Its not the SDCard that requires formatting. It is the internal phone storage. If you view it via Astro, it should appear ok.

whewstoosae said:
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.
Click to expand...
Click to collapse
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.

bippy_b said:
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.
Click to expand...
Click to collapse
I think that 6.0.1 is defaulted to 1GHz, but you can o/c it if you want to with SetCPU or similar.

The kernel that comes with cm6.0.1 is already great. i get the best battery life i have ever had on my incredible. It can be overclocked to 1.15ghz

When I downloaded it defaulted to 1.15 so I guess YMMV.
Sent from my Incredible using Tapatalk.

rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Slow down and read everything over a bit better.
Hydra and King usually state somewhere SPECIFICALLY that they DON'T work with/support CM6. You don't need to find any kernel, just WIPE your device properly ( wipe data/cache/dalvik) before you flash it. Once flashed don't try any kernels.
Also understand there are known issues with it. One is that BT music streaming doesn't work at all. The other is that the OS doesn't scan the built in 8gb of memory. The third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi. It may happen in 30 minutes, it may take 12 hours. It may not happen at all. It's not even close perfect yet.

The only issue I have seen so far is random reboots and yesterday when I booted up my Phone all my widgets were brown boxes and said they were not compatible, a reboot fixed that.
Android Version 2.2
Model Number - Incredible
Baseband - 2.15.00.07.28
Kernel Version - 2.6.32.15......koush
Mod Version Cyanogen 6.0.1

When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.

AndroidBruce said:
When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.
Click to expand...
Click to collapse
Thanks for the pro-tip, I could see myself having done this.

I've had multiple lock ups and reboots but the first day was good.
Sent from my Incredible using XDA App

seanmcd72 said:
third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi.
Click to expand...
Click to collapse
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.

ardax said:
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.
Click to expand...
Click to collapse
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed

ncwildcat said:
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed
Click to expand...
Click to collapse
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.

jratzo said:
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.
Click to expand...
Click to collapse
Exactly what I experienced. I went half a day with it seeming perfect, then out of the blue I pick up the phone and it's just off and nothing I do will get it to come on. It's either pull the battery or wait several minutes and suddenly it finally reboots on it's own. It doesn't happen to everyone, but it happens to enough people to say it is a definite unresolved issue. It's very good otherwise, as soon as these little issues are cleared up It will be the ROM for me.

Camera permanently frozen in MIUI ROM

I've got MIUI ROM 1.6.10 installed on my HTC Desire and I really like it, but I've got a big issue with the camera: it's in a constant state of being frozen.
So to clarify, I open the camera app, and it's straight away frozen. I try to press buttons but all I get is the Force Close / Wait dialogue. If I wait, nothing happens. If I force close and open it again, it's frozen still/again.
It used to happen to me in MIUI 1.2 as well and when I upgraded to MIUI 1.4 after a wipe, surprisingly it was exactly the same, but then I tried pressing the Clear Data button for the Camera application and it started working again.
A little bit after it started getting frozen again. Clear data didn't work anymore, neither did a wipe, SD card format and upgrading to 1.6.10, as mentioned above.
The only thing I can think about the might cause the problem is this: before miui I used to have cyanogen ROM. When I look at phone information it says I've got the cyanogen kernel. is that something that could cause problems to the miui ROM? Should install a different kernel?
Can anyone please help? I really like this ROM and I don't want to have to start getting used to something else!
Thanks for reading!

I'm not sure if this is useful/helpful at all but i gather that since it says that you've got cm kernel you didn't perform a full wipe when you installed miui... try doing a full wipe and reinstalling it...

Save important user data and apps, perform a full wipe and flash again.

Does a full wipe erase the previous kernel?
What kernel will I have then?
Can anyone actually explain what kernel is exactly?
Also, how do I do a FULL wipe?
Because I've already done:
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache
What am I missing?
Cheers

After a full wipe you won't be able to start any rom.
You will get the kernel which is delivered with the rom you flash.
An explanation for the kernel:
http://en.wikipedia.org/wiki/Linux_kernel
Nothing is missing for a full wipe.
Search the miui thread for your problem.

MatDrOiD said:
After a full wipe you won't be able to start any rom.
You will get the kernel which is delivered with the rom you flash.
An explanation for the kernel:
http://en.wikipedia.org/wiki/Linux_kernel
Nothing is missing for a full wipe.
Search the miui thread for your problem.
Click to expand...
Click to collapse
If nothing is missing and I've actually done a full wipe, then why is my kernel still cyanogen?

liranh said:
If nothing is missing and I've actually done a full wipe, then why is my kernel still cyanogen?
Click to expand...
Click to collapse
Because cyanogen is the kernel which is delivered with miui rom.

MatDrOiD said:
Because cyanogen is the kernel which is delivered with miui rom.
Click to expand...
Click to collapse
Wicked thank you. So the kernel is not the problem.
Could I still have missed something from a full wipe? I remember reading in the guide that u need to format /data,or something. But I assumed the wipes I've detailed above were sufficient. Can anyone confirm that for me?
Or can anyone tell me otherwise why I'm having this problem?
Thanks.

Try to update radio on newest version (post #6):
http://androidforums.com/desire-all...sers-anyone-elses-camera-stopped-working.html

MatDrOiD said:
Try to update radio on newest version (post #6):
http://androidforums.com/desire-all...sers-anyone-elses-camera-stopped-working.html
Click to expand...
Click to collapse
Thank you. You reckon the radio might affect the camera?
Edit: Just had a quick look at the thread you gave me. Seems like that might fix the problem. I'll give it a go when I finish work. Thank you very much!

liranh said:
Thank you. You reckon the radio might affect the camera?
Edit: Just had a quick look at the thread you gave me. Seems like that might fix the problem. I'll give it a go when I finish work. Thank you very much!
Click to expand...
Click to collapse
DIDN'T WORK!
It's a shame. I really thought that was the solution, but it didn't work.
I've just downloaded and installed the recommended radio (5.17.5.23), even tried to clear the camera's data again, but it's still frozen.
ANYONE ...? :\

Did you try some other kernels like ManU or Tiamat?

guersam said:
Did you try some other kernels like ManU or Tiamat?
Click to expand...
Click to collapse
No. Do you reckon that might help? Which one would u recommend?

Okay I've tried a different radio, different kernels (Tiamat 3.3.8 and 4.0.5). Nothing helps!
Does anyone have a clue how to fix this annoying problem?
Another lead I had in mind: Could the fact that I have S-ON affect anything?

Update: I've tried pressing "Fix Permissions" in ROM Manager which didn't help either.

................?

The MIUI camera seems to be a bit buggy, I had to update the radio which helped me get rid of the worst crashes (suprise reboots) but it's still FC'ing and crashing the camera totally so that a reboot is necessary.
Try installing Camera360 from Market. It works for me, and at least you will know if it's just the MIUI Camera app that's broken or if you have bigger problems. In case Camera360 can't connect to the camera, reboot and try again.

enemix said:
The MIUI camera seems to be a bit buggy, I had to update the radio which helped me get rid of the worst crashes (suprise reboots) but it's still FC'ing and crashing the camera totally so that a reboot is necessary.
Try installing Camera360 from Market. It works for me, and at least you will know if it's just the MIUI Camera app that's broken or if you have bigger problems. In case Camera360 can't connect to the camera, reboot and try again.
Click to expand...
Click to collapse
I've already tried a different camera from the market and it does work with no problems at all.
It is the miui camera app that's malfunctioning.
If no one has a solution, all that's left for me is to hope the miui devs will fix this critical issue for their next build.

liranh said:
I've already tried a different camera from the market and it does work with no problems at all.
It is the miui camera app that's malfunctioning.
If no one has a solution, all that's left for me is to hope the miui devs will fix this critical issue for their next build.
Click to expand...
Click to collapse
Ah, then it's most probably the same problem that I have, only I get to shoot a few pics before it goes bye bye and then no camera app at all works until I reboot.
It's a shame because I really like the MIUI Camera, but I guess we'll just have to wait for a fix. If you have error logs, try posting them in the official forum for your MIUI build and maybe they can get someone in China working on a solution?

same problem for me but i am on 1.9.16 ported to X10 lol...
I seen somewhere that it was the auto focus that caused problems/ lags for ppl so if i could just get it to work once and maybe turn that off?

Galaxy S3 T-Mobile Problems. AOKP the reason?

My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks

Probably.

I'm running AOKP without any issue. What have you installed recently? Did you flash custom kernel, overclock cpu, change cpu voltages, etc...? Download OS Monitor app and see which processes are eating cpu and your battery. Maybe it's time to wipe everything clean: factory reset, wipe external sdcard, and reflash the ROM. An sdcard full of stuffs can cause the media scanner process to run long and eat up battery.
S-beamed from my GSIII via xda premium

I wouldnt go as fsr as blaming the rom right away, especially if its a milestone. More kernel related and or user error. Give us more info to help you solve this so you can use your the way you want to.
Sent from my SGH-T999 using xda premium

There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.

vx117 said:
There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.
Click to expand...
Click to collapse
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.

More like kernel related but yes aokp and cm10.1 can mess up your phone at times

Aerowinder said:
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.
Click to expand...
Click to collapse
Yes, but even with custom kernels it can get buggy. No kernel is one-size fits all since each chip is unique. You gotta pick and choose which kernel works best for your phone.

Kyle Chen said:
My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks
Click to expand...
Click to collapse
I was having that issu as well but it was with touch wiz roms and kernels it actually ended up being a dud phone and battery. .. I have done a warranty exchange and it fixed it I also got an anker battery too and its been doing good only gets hot when I have it on charge and use it.. so it would ight not be just the rom. Try a different kernel see if its the battery getting hot and go from there. Isolation is key bud:thumbup:
Sent from my SGH-T999 using Tapatalk 2

This morning my phone was stuck on the AOKP boot logo and it was overheated like crazy. I did a battery pull and waited for the phone to cool down. After that I booted it back up, but the battery drained pretty fast and the phone still heated up.
I did not flash any custom kernals or anything. Just AOKP milestone 1.
Maybe I will wipe the entire phone and reflash aokp.
OR
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.

+1
I've been running AOKP since 2 hours after I got my d2tmo, initially KAsp3rd's unofficial builds, and now the official "nightly" builds... I have been using a very stable build since January, but recent official developments have me flashing regularly again.
Every single build since JB 4.2.2 MR1 has been very unstable on my device, somewhat randomly rebooting quite regularly... I say "somewhat" randomly because there are a certain few actions I can perform which will cause reproducible immediate reboots on demand, including but not limited to trying to DISABLE* USB Debugging. I've noticed that the device is far more likely to reboot itself when attempting to run apps as superuser. I noticed that Koush's Superuser app/infrastructure is embedded/integrated in the ROM and when I installed the latest version from the Google Play Store, it said that my su binary was out of date, so I updated it... It didn't resolve the random reboots, but when the device did reboot next, it performed some additional setup steps, including prompting me for my first & last name which was really odd because the initial setup had, I thought, been completed, and the device had been rebooted (by itself mostly) at least a dozen times prior to this.
I suspect these issues might have something to do with the superuser integration in the ROM and I ask that you who are experiencing similar random reboots take note of any patterns such as whether it occurs more often when attempting to perform superuser privilege escalation.
Currently I'm testing whether setting "Superuser Access" to "Disabled" helps at all. I'll report my findings once a conclusion is established.
*I'm trying to disable it to troubleshoot why the device doesn't show up when I issue `./adb devices` on my PC running Ubuntu 12.10 Linux; it doesn't even show up in the list of connected USB devices when I issue a `lsusb` command which is weird. I've rolled back to my backup of the January AOKP 4.1.2 build and confirmed that the device is visible to adb, so it doesn't seem to be an issue with my hardware...
P.S. I've posted about it in the new official d2tmo AOKP Nightly thread on the RootzWiki Forum (linked above).
---------- Post added at 11:29 AM ---------- Previous post was at 10:50 AM ----------
Disabling Superuser didn't seem to help at all. It has still rebooted itself twice since then.

[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13

PM me for a modified SlimBean build I use if interested. No random reboots and I have had the same issue in the past. Also, you could try wiping 3 times (cache,dalvik, factory reset and system) and then install KT747. Its the most up to date kernel as far as the patches and drivers go.
Sent from my SGH-T999 running Chihuahua v1 ROM

re: acceptable
Ch4m3l30n said:
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
Click to expand...
Click to collapse
Why should any amount of crashes or random reboots be "acceptable" to anyone when there are so many
other roms in these xda forums to choose from which do not crash at all and are full of excellent features? LOL

Make a backup. Wipe cache and data. Then try another rom
Sent from my SGH-T999 using xda premium

My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.

Kyle Chen said:
My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.
Click to expand...
Click to collapse
did you try reformatting your sdcard(s), factory reset, format /system partition (via recovery), and reflash the ROM? maybe just reformat the sdcards first, and see if that helps.
S-beamed from my GSIII via xda premium

Kyle Chen said:
<snip>
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.
Click to expand...
Click to collapse
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.

bwb8771 said:
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.
Click to expand...
Click to collapse
I ended up flashing like a touchwiz galaxy s5 themed kitkat rom, which I have been using since September. Before that I used cyanogenmod 11. Haven't tried AOKP in a long time. When I get time I plan to flash some lolipop rom I guess.

Is there any activity on AOKP any longer, loved rom but it looks like 10/18/14 is the last build i can find.....

CM11 Discussion Here. [Links/Download/Info/Discussion/More]

Please discuss all CM11 related items here until we get official nighties / another thread from shellnut. Here I will link what we have so far.
******Backup EFS partitions using recovery/freegee!******
---------------
You need the latest clockworkmod recovery. Use Flashify from the Play store to flash. Be sure to READ the installation instructions.
---------------
Download Area. Do NOT forget to read installation instructions:
Clockworkmod Recovery Image (Go to page 4): Clockworkmod Latest Recovery! Click Me!
Flashify: Flashify Play Store Link. Click me!
Downloads (Unofficial from Shellnutt2): Shellnutt2 Unofficial CM11. Click me!
New Official updates; download.cyanogenmod.org
choose LS970
Gapps (Choose CM11): CM 11 Gapps. Click Me!
-----------------------------------------
Working:
Phone Calls
SMS/MMS
Camera (Autofocus Too!) (Camera is only 8 Megapixels though.)
UI
Pretty much everything
Bugs known so far: WiFi is hit or miss. Some people has it working, some do not.
Extra info:
To install, Do the normal.
1. Place Rom/Right Gapps on internal storage
2. Download recovery from link.
3. Use Flashify to flash the new recovery
4. Be sure to backup everything important to you.
5. Did you backup? Good.
6. Backup EFS partitions using recovery/freegee!
7. Wipe normal as you would. Be sure to not wipe internal storage. Wiping system may or may not help.
8. Install rom/gapps
9. Profit. Have fun!
MikeEx Posted:
Shellnut2 has said that we are slated to go for nighties when they officially start.
If your WiFi is giving you "Association rejected" please hop on IRC and get some logcats to Shellnut2
Server: irc.freenode.net
Channel: #lg-optimus-g
Click to expand...
Click to collapse
Also, how to use ART
MikeEx Posted (Couldn't quote or it wouldn't show red on XDA app):
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
-----------------------
Disclaimer!
No on here takes responsibilty for anything YOU do to YOUR phone. You can not blame us for anything that happens.
---------------------------
All credit here go to its respective Builders/Complilers/Owners. I am merely providing links until official support is given.

Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.

HdMsTrTeCh said:
Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.
Click to expand...
Click to collapse
Use CWM, I believe there's an updated version that someone built (it's in the cwm recovery thread towards the last couple pages). Flashify works on LGOG as that's what I used to flash the cwm touch img file. Wifi works on my end. I flashed the 11/30 build and then dirty flashed 12/03 build.

I realize this is probably buggy but is it worth the switch from 10.2 to use as a dd? What if I want to go back? All my backups are TWRP

Use online nandroid backup to make a CWM backup without CWM
Here: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Sent from my Bangin' LS970 on who knows what ROM

HdMsTrTeCh said:
Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.
Click to expand...
Click to collapse
WiFi is hit or miss for certain people. You must use clockworkmod recovery. I will add links to op here in a min. I use flashify and it worked just fine.
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."

Shellnut2 has said that we are slated to go for nighties when they officially start.
If your WiFi is giving you "Association rejected" please hop on IRC and get some logcats to Shellnut2
Server: irc.freenode.net
Channel: #lg-optimus-g

Links up. Thread cleaned up. Have fun.

jblazea50 said:
Use CWM, I believe there's an updated version that someone built (it's in the cwm recovery thread towards the last couple pages). Flashify works on LGOG as that's what I used to flash the cwm touch img file. Wifi works on my end. I flashed the 11/30 build and then dirty flashed 12/03 build.
Click to expand...
Click to collapse
Linked recovery in OP
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."

Whiplashh said:
.
Click to expand...
Click to collapse
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.

Wifi works fine for me at home but at work it will not connect.
Sent from my LG-LS970 using Tapatalk

Basically everything worked for me except video recording and playback. Try recording a video in snapchat and see what happens.
That said, the camera works better than on the other 4.4 ROMs. No autofocus issues and no weird coloration issues, no capture rate issues either.

MikeEx said:
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
Click to expand...
Click to collapse
Added it. Will add red letters tomorrow.
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."

Fresh bacon up!
Sent from my LG-LS970 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 09:34 AM ----------
Still can't connect to my work wifi after a dirty flash. Going to try clean here in a minute. Strange though how I can connect to some routers but not others.... They are both WPA security
Sent from my LG-LS970 using Tapatalk

Ran the 12/3 build all night last night - dirty flashed up from the latest 10.2 build just for kicks.
Initial boot the OS was just crawling (likely dirty flash issue) - 2nd boot brought everything back to life and been fine since.
Not running ART just yet - need to verify and trim down my 200 app list lol (plus I don't want to lose Xposed just yet)
3G/4G both work great
Wifi worked fine at 3 different locations
GPS worked great
Auto Focus of course works fine
USB Tether works (woot!) and no long kills my phones USB connection when un-tethering (double woot!)
BT worked fine
NFC Works
Audio book played without any audio distortions/glitches (issue in another KK rom)
Google Nav/Maps is still using the wrong voice - an issue I had in the 10.2 build which may have carried over due to dirty flashing. The other KK rom I use uses the correct voice.
Using the PA Gapps Mini-Mod package
Had to reset my battery meter setting since the 10.2 option doesn't exist (yet) in 11 - had me confused for a bit since I had >no< battery meter lol
Aside from having to use CWM, this is pretty dang slick so far.

has the updater been implemented? The one really cool thing I liked about CM

What is ART? Is it optional?

Here's the CWM -6.0.4.5.zip file for the LS970, Uploaded by shellnut
http://www.4shared.com/zip/jULzGS4j/cwm-6045-ls970.html
Here's the stock LG Optimus G camera zip (For AOSP/CM)
http://www.4shared.com/zip/6UeG0pi_/CamCM1018030.html
MMS zip
http://www.4shared.com/zip/ZMj_Eds5/Mms.html
Everything works great, even auto focus.
Today is my birthday, and I flashed my 12/5 birthday build, I couldn't be happier

MikeEx said:
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
Click to expand...
Click to collapse
i've never had these issues myself, but i can see why they would arise. i think a warning or piece of advice should be mentioned stating that if someone plans on using ART, they should enable it immediately upon rom installation, before other apps are installed. that way, optimization isn't as tedious of a process

Derp

[Q] Is there a stable version of Cyanogenmod for Xperia M?

Sorry if i make any errors or mistakes. I just spent the last 20 minutes on creating this thread and in the end, made me login again and guess what - everything i typed went away.
My phone is sony Xperia M C1904 single sim, running android 4.3 stock(latest).
This is the first time i am rooting.
I am doing it because
1) Low free space thanks to Sony's bloatware.
2) Expected them to atleast give Kitkat as they were supposed to.
3) Need app to sd
I need a stable version of cyanogenmod for my phone.
Does updating work like normal? Like, do i just use update center and download the new version updates(like perform all steps and install once, then use as usual), or do i have to flash again and again?
Is there any feature that i won't be able to use? It will only be better right?
Can the process be done on the phone itself via sd card after downloading everything necesary, or do i have to install/flash it while connected to pc?
Please explain in detail.

1. stable CM12 yet to be released, please go to cyanogenmod site and look for device Nicki
2. from my personal exp. updating work like normal update. you need to enable root and other feature from setting.
3. i am using link2sd and successfully managed to cap the space <800 MB. currently 1.2+GB is free on my XMS.
4. only thing i hate, after update you need to grant access to link2sd so that your app can comes back.
5. you can check change log in cm site for each nightly, i.e. 12-20150322 nightly has an issue on mobile network check/uncheck while using wifi.
6. you need to flash cm12 and gapps on each update.

debaxish said:
1. stable CM12 yet to be released, please go to cyanogenmod site and look for device Nicki
2. from my personal exp. updating work like normal update. you need to enable root and other feature from setting.
3. i am using link2sd and successfully managed to cap the space <800 MB. currently 1.2+GB is free on my XMS.
4. only thing i hate, after update you need to grant access to link2sd so that your app can comes back.
5. you can check change log in cm site for each nightly, i.e. 12-20150322 nightly has an issue on mobile network check/uncheck while using wifi.
6. you need to flash cm12 and gapps on each update.
Click to expand...
Click to collapse
How about stable CM11?

debaxish said:
1. stable CM12 yet to be released, please go to cyanogenmod site and look for device Nicki
2. from my personal exp. updating work like normal update. you need to enable root and other feature from setting.
3. i am using link2sd and successfully managed to cap the space <800 MB. currently 1.2+GB is free on my XMS.
4. only thing i hate, after update you need to grant access to link2sd so that your app can comes back.
5. you can check change log in cm site for each nightly, i.e. 12-20150322 nightly has an issue on mobile network check/uncheck while using wifi.
6. you need to flash cm12 and gapps on each update.
Click to expand...
Click to collapse
I can't get link2sd working on cm12, any advice? guide may be? What type of partition? I have FAT32.

Georgepaul said:
How about stable CM11?
Click to expand...
Click to collapse
CM11 seems to be quite stable.
Sometimes Google Play Services crash but it got better after I switched from dalvik cache to art. If you reboot your phone once or twice a week CM11 works great.
Battery life on the other side is really bad compared to stock 4.3 rom. (On Stock Rom I had to charge every 5 days, with CM11 every 2)
There are no updates for CM11 anymore, so no need for that.
If you want something that just works, go for CM11 and wait until CM12 gets a final realease. Otherwise you have to deal with bugs, even worse battery life and flash your stuff again after an update.

xa.fr said:
CM11 seems to be quite stable.
Sometimes Google Play Services crash but it got better after I switched from dalvik cache to art. If you reboot your phone once or twice a week CM11 works great.
Battery life on the other side is really bad compared to stock 4.3 rom. (On Stock Rom I had to charge every 5 days, with CM11 every 2)
There are no updates for CM11 anymore, so no need for that.
If you want something that just works, go for CM11 and wait until CM12 gets a final realease. Otherwise you have to deal with bugs, even worse battery life and flash your stuff again after an update.
Click to expand...
Click to collapse
to fix google play services just type in terminal:
Code:
su
pm disable com.google.android.gms/com.google.android.gms.droidguard.DroidGuardService
I don't see any battery life difference beetwen 4.3, 4.4.4 aosp, cm11 and cm12
btw it's preatty old thread

iks8 said:
Code:
su
pm disable com.google.android.gms/com.google.android.gms.droidguard.DroidGuardService
Click to expand...
Click to collapse
Thanks, but what exactly does this disable? No idea what DroidGuardService is and how it is needed....
Are you using your phone a lot of times during the day? If yes, there is not much difference for me either.
But often times during a busy week at work I barely use it and in this situations stock did last way longer than CM11.

xa.fr said:
Thanks, but what exactly does this disable? No idea what DroidGuardService is and how it is needed....
Are you using your phone a lot of times during the day? If yes, there is not much difference for me either.
But often times during a busy week at work I barely use it and in this situations stock did last way longer than CM11.
Click to expand...
Click to collapse
I don't know, it's Boonobo's guide but I think it's safe to discable since it's not working properly anyway. Yes, I use my phone a lot.

Okay, thanks. Do you have a link to your mentioned guide or something?

no, it's some old post and I don't know where it is, anyway I'm using this on my phone and I don't see any difference (except no fc ofc)

iks8 said:
no, it's some old post and I don't know where it is, anyway I'm using this on my phone and I don't see any difference (except no fc ofc)
Click to expand...
Click to collapse
So my experience so far. If you disable this, most apps can't get your location over Wifi anymore or if they do, it is not really exact.
Had some Llama rules with Wifi which are not working anymore and my weather app can't find my location when connected to Wifi.
Had to enable it again...

xa.fr said:
CM11 seems to be quite stable.
Sometimes Google Play Services crash but it got better after I switched from dalvik cache to art. If you reboot your phone once or twice a week CM11 works great.
Battery life on the other side is really bad compared to stock 4.3 rom. (On Stock Rom I had to charge every 5 days, with CM11 every 2)
There are no updates for CM11 anymore, so no need for that.
If you want something that just works, go for CM11 and wait until CM12 gets a final realease. Otherwise you have to deal with bugs, even worse battery life and flash your stuff again after an update.
Click to expand...
Click to collapse
about "red line"
for me just go to setting, apps, google play services, uninstall update. it's work fine for me