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
Related
Ok so here's my situation, Last night i performed a backup of my current rom (AOSPA) and when it finished and booted back up my phone became unbearably laggy. This isn't a rom specific problem either because i've tried wiping and clean flashing several other roms that hadn't given me this problem. I've also tried the Lagfix (fstrim) app which doesnt seem to work (Gives an error message then grays out the button and says "Not Supprted").The only way to get rid of this lag is to completely unroot and install 4.0.4 then root again. I had this problem about a week or two ago also. i was just wondering if anyone else has had this problem. If so, Is there any way to get rid of it without unrooting? Thanks In Advance
have you tried to flash the stock image from google? I had the same issue for my nexus 7, flashed factory image and all lag is gone, feels like a new tab again.
So going to atock 4.0.4 fixes the issue correct? Id suggest wiping the entire phone system and all. If u search my profile i have a one click flash to stock tool. It deletes everything but will put u back on 4.0.4 the day it came out of the box. I think ur issue lies somewhere in storage.
If u have the gsm nexus then uncheck the radio flash boxes if u decide to use my tool.
Also my tool contains the stock image from google. No hackery of any kind.
GeeNex | Carbon nightlies | Rubiks
vabeachfc3s said:
So going to atock 4.0.4 fixes the issue correct? Id suggest wiping the entire phone system and all. If u search my profile i have a one click flash to stock tool. It deletes everything but will put u back on 4.0.4 the day it came out of the box. I think ur issue lies somewhere in storage.
If u have the gsm nexus then uncheck the radio flash boxes if u decide to use my tool.
Also my tool contains the stock image from google. No hackery of any kind.
GeeNex | Carbon nightlies | Rubiks
Click to expand...
Click to collapse
Thanks for your help. I seriously hope this is the last time it happens. I think I have narrowed down what the problem is. It seems that whenever my internal storage gets below 1gb this happens. I believe that was when it started last time. I guess I'll just have to use less internal storage to keep my nexus fast.
Sent from my Galaxy Nexus
I guess you still have the lagfix-issue. Normaly LagFix should be able to recover your speed. I sometimes have a problem with lagfix not getting the root-permissions from the superuser fast enough so it considers your phone unsupported. Try this:
1. start LagFix and click on Run!
2. Grant root-permissions to it and save the decision so superuser will not ask again.
3. if LagFix fails with the unsupported-device-error go on...
4. quit LagFix and clear its DATA from app-management
5. start LagFix again and click on Run!. Not it should run OK without asking for root!
It looks like CM11 nightlies have just started for our dear old (and by now loyal) P930s:
http://download.cyanogenmod.org/?device=p930
I am not sure what gapps one would install with this, and I assume a full wipe is recommended, if not necessary. Let's discuss problems here and encourage further development for a quickly stabilizing nightly!
Yeey I am so happy to hear that, I just hope it won't take a lot of time and that all the reboot and bug issues still found in the 10.2 version will be fixed properly.
I used these GApps with Navik's version of CM11 and they seemed to work out pretty good.
http://d-h.st/EIM
Is the 2012-12-22 version working for anyone else? I got an error when I tried to flash it. Wasn't sure if my download was corrupted or if it isn't quite ready for release.
SeriousGeorge said:
Is the 2012-12-22 version working for anyone else? I got an error when I tried to flash it. Wasn't sure if my download was corrupted or if it isn't quite ready for release.
Click to expand...
Click to collapse
Its working quite fine for me, for now the only glitch i have is that the camera isnt working, no bsods as of yet, flashing the latest version 12/23 right about now.
I did a full wipe - factory reset, wipe system, wipe cache, wipe dalvik, flash rom, flash pa stock gapps.
EDIT: Camera still not working in latest version.
just1nsama said:
Its working quite fine for me, for now the only glitch i have is that the camera isnt working, no bsods as of yet, flashing the latest version 12/23 right about now.
I did a full wipe - factory reset, wipe system, wipe cache, wipe dalvik, flash rom, flash pa stock gapps.
EDIT: Camera still not working in latest version.
Click to expand...
Click to collapse
I did end up getting it working. I had an extremely old version of ClockworkMod on my phone so I updated that. Re-downloaded the file and did the update through the CM updater. Worked fine second time. Performance was terrible, but that may have been from not doing a clean install.
just1nsama said:
Its working quite fine for me, for now the only glitch i have is that the camera isnt working, no bsods as of yet, flashing the latest version 12/23 right about now.
I did a full wipe - factory reset, wipe system, wipe cache, wipe dalvik, flash rom, flash pa stock gapps.
EDIT: Camera still not working in latest version.
Click to expand...
Click to collapse
I tried the 12/24 build and the camera was still broken, but I was able to replace the Camera2.apk with one from the latest pace build and it seems to work, although that version has it's own responsiveness issues.
nate1975 said:
I tried the 12/24 build and the camera was still broken, but I was able to replace the Camera2.apk with one from the latest pace build and it seems to work, although that version has it's own responsiveness issues.
Click to expand...
Click to collapse
Is video recording working with that cam apk?
Has anyone tried 12/25? I'm currently in Jellybam 9.2 and I'm scared to flash cm11. Any feedback on it?
mpsantiago said:
Is video recording working with that cam apk?
Click to expand...
Click to collapse
Yes, but its a little unresponsive - an issue already identified with the rom I pulled the camera package from.
You can try it here if you want:
http://hubbards.us/p930/cm-11-20131224-NIGHTLY-p930-mod.zip
But like I said, it isn't perfect or anything.
It looks like there is a bunch of commits for the next nightly related to the camera, so....let' hope that fixes the camera. Once someone can confirm a working camera, I may make the jump from 10.1.3. I still get 3-4 freezes a day (unresponsive to power, etc.) -- is 11 much better?
MRMNYC said:
It looks like there is a bunch of commits for the next nightly related to the camera, so....let' hope that fixes the camera. Once someone can confirm a working camera, I may make the jump from 10.1.3. I still get 3-4 freezes a day (unresponsive to power, etc.) -- is 11 much better?
Click to expand...
Click to collapse
fwiw, I'm on 10.1.2+Wind and was getting one BSOD per day- underclocking to 1.4ghz seems to have resolved it, and I don't notice any difference in performance. Antutu score is maybe 150pts lower. Maybe that will help on 10.1.3? I haven't really used it much because no Wind kernel.
mpsantiago said:
fwiw, I'm on 10.1.2+Wind and was getting one BSOD per day- underclocking to 1.4ghz seems to have resolved it, and I don't notice any difference in performance. Antutu score is maybe 150pts lower. Maybe that will help on 10.1.3? I haven't really used it much because no Wind kernel.
Click to expand...
Click to collapse
CM11 runs quite well even without WIND, havent had 1 single BSOD on it, as for the camera, you can just copy/replace using the one from pace44, change persmissions and reboot until CM resolve the camera issue.
Of course performance wise its not as good as CM10.1.3 stable + wind, but still, being that its the first nightlies, its quite a good rom. Not sure if lyfkevin will make a WIND kernel version for CM11 as there is no plan for a SU640 build anytime soon.
mpsantiago said:
fwiw, I'm on 10.1.2+Wind and was getting one BSOD per day- underclocking to 1.4ghz seems to have resolved it, and I don't notice any difference in performance. Antutu score is maybe 150pts lower. Maybe that will help on 10.1.3? I haven't really used it much because no Wind kernel.
Click to expand...
Click to collapse
10.1.3 stable *does* have a Wind kernel for it. But let's keep the discussion about CM11 here!
Flyview said:
10.1.3 stable *does* have a Wind kernel for it. But let's keep the discussion about CM11 here!
Click to expand...
Click to collapse
My bad, I was thinking 10.2 :silly:
Happy 2014, guys!!!
So, I gave CM11 a test drive today, and while it was solid and the camera suggested by Just1nsama worked great, my issue was related to the SD card -- for some reason it was having trouble reading/writing to it (couldn't move apps to SD, gallery only saw about a fifth of the files, and same with music player). It's not an SD card issue -- I checked the SD card for errors and, now that I've reverted to 10.1.3, it's working fine as well. Anybody else have this issue? It's a 64GB card.
I installed the latest nightly...did nothing extra regarding the camera as it now works out of the box. There is an issue with apps that install by default to the sdcard. When I tried to install Carbuzz, it failed with an error message "Couldn't install on usb storage or sdcard". Using File Explorer I can see and access all my files on the sd card, plus play music from the card using Apollo. Hoping next nightly will cure it. The ROM is very stable without any BSOD thus far. My recommendation to the CyanogenMod team is to skip 10.2 altogether and focus on 11.
Sent from my LG-P936 using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:04 PM ----------
Quick update...built in camera app is slow to start up, barcode scanner app still not fully functioning (loads but screen goes black within the scanner borders) and the sd card issue with car buzz are my only issues so far.
Sent from my LG-P936 using Tapatalk
Trialz Nexus One said:
I installed the latest nightly...did nothing extra regarding the camera as it now works out of the box. There is an issue with apps that install by default to the sdcard. When I tried to install Carbuzz, it failed with an error message "Couldn't install on usb storage or sdcard". Using File Explorer I can see and access all my files on the sd card, plus play music from the card using Apollo. Hoping next nightly will cure it. The ROM is very stable without any BSOD thus far. My recommendation to the CyanogenMod team is to skip 10.2 altogether and focus on 11.
Sent from my LG-P936 using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:04 PM ----------
Quick update...built in camera app is slow to start up, barcode scanner app still not fully functioning (loads but screen goes black within the scanner borders) and the sd card issue with car buzz are my only issues so far.
Sent from my LG-P936 using Tapatalk
Click to expand...
Click to collapse
Sounds like an issue with the new file system..
Sent from my LG-P930 using Tapatalk 4
Agreed. Hopefully an easy fix as while system not giving write permission for apps to install to sdcard, there are no problems with apps saving to or accessing data from the sd card
Sent from my LG-P936 using Tapatalk
Trialz Nexus One said:
....Quick update...built in camera app is slow to start up, barcode scanner app still not fully functioning (loads but screen goes black within the scanner borders) and the sd card issue with car buzz are my only issues so far
Click to expand...
Click to collapse
Same experience here. Third party camera apps including barcode scanner and Yelp are closer to working then in 10.2. Barcode no longer freezes the phone, I just got the same black screen with active borders as described in quote, and I can exit the barcode application. Yelp's "add a photo here" function comes up with garbled live image instead of the black screen with a few snow lines in 10.2.
Some applications seemed subjectively faster than in 10.1.3. Camera in 11 was slower to load but focused and balanced light levels more responsively.
Trialz, did you happen to root your device using the Korean KDZ file? Method of root apparently makes a difference in 10.1's camera tendency to freeze the phone if the screen is shut off while an image is live. Perhaps this camera issue is related?
Great work, but until the third party camera issue is fixed, I'm sticking with 10.1.3.
Sent from my LG-P930 using xda app-developers app
[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
kbfirebreather said:
Anyone having problems with torch on the beta build? Not turning on LED for me, and keeps force closing.
Click to expand...
Click to collapse
I'm having issues with it as well. Sometimes it sits there thinking it works, other times it waits a few seconds and then crashes. It worked for a day...not sure what I did past that to break it.
Is there anyway to overclock the latest update? I know I can't install a new kernel with this ROM.
Also, any option for Volume Rocker unlock? I'm new to this ROM, coming from CM. I kinda rely on that option, since my power button is kinda on the fritz.
Fml 4.4.4 beta
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
vicious01 said:
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
Click to expand...
Click to collapse
Which gapps package are you using? I'm using the modular mini. Try another clean flash (sorry) and use a different package than you are now.
aaa
nothing
I've tried a lot of KitKat ROMs, but each one with a lot of issues. So I came back to the 4.3, it surprised me for his stability (1 year with bugged ROM make you feel that your phone sucks more than it actually does [no, it doesn't, I love it!]) and I decided to don't try your FML. Now I can't wait for Lollipop, and even if I haven't tried your ROM, I trust in it and I think it will be the best choice. Good work and thanks!
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
Samsung Galaxy Nexus FML Lollipop
Hello. I hope this is the right place to post this. I have less than 10 posts so I have to post here...
I've tried to install your FML rom (the lollipop beta) on my Samsung Galaxy Nexus, but I seem to be having the same issue that coleburns is having. Namely, I flashed the rom from recovery, but when I reboot the phone, it shows the Google splash screen and then keep rebooting over and over again.
I understand that the first boot is supposed to take some time, but I've left it for over an hour and it still won't boot into the OS. Is there a step I'm missing?
I'm using the custom version of TWRP that you linked to in the first post. I also formatted all the partitions to ext4. Before flashing the rom, I performed the factory reset from recovery and also cleared the /system folder.
I've managed to load on the KitKat version of your ROM just fine...I can't work out what I'm doing wrong!
Anyway, if you need some logs or something to help debug the issue, let me know. Or, if I'm doing something wrong, could you please let me know? I'm very keen to try Lollipop!
Thanks.
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
lollipop build 2
Haven't seen anybody ask... In your changelog for lollipop you said the rom takes a VERY LENGTHY FLASH TIME. Are we looking at 5 minutes or more?
edit: VERY LONG... over 5 minutes for me
This is the best rom ever!
When you said, "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast." I was expecting junk, then I tried it. I was a big fan of your kit kat rom as well but once I tried this android l rom I fell in love. I have used this all day and it is extremly stable. The only bug I have to report that isnt even a need is the app drawer is the app drawer animation is very laggy. I tried enableing 2d gpu acceleration just in case that had something to do with it but it still didnt help. Any suggestions would be great. Oh and yes I have tried closing other apps, multitasking is no issue with this rom, the memory management is great. I thank you so much for such a great rom, keep up the amazing work.
Installing TWRP Problem
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Mondos said:
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Click to expand...
Click to collapse
Download the file in the OP for FML (twrp 2.7.1). Flash with Flashify. Reboot to recovery.
Don't worry too much about it not working. It's fully working for me but it's pretty slow when you actually need to use it. If you get it going it will pick up the pace, but it's far from usable, being in an app for longer than a minute and touching the home screen button will freeze it up for 10 seconds before it takes you to an empty screen that takes another few seconds to load all the apps and widgets back in. I'd wait for a newer release.
Feedback
Hello i have tried the older version and it was great but i really need my camera so i went back to 4.4 but i appreciate you so much thanks !
Please fix the camera asap and i will definitely install this rom ! and i tried to install the new version but it said Error Binary something in TWRP recovery what can i do thanks!
Q
Is the camera fixed yet?
Notification Light
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
TheIbanez97 said:
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
Click to expand...
Click to collapse
I don't think so.
I found that the miscellaneous section of the battery stats was taking up most of the battery usage. I don't have any apps installed other than the stock standard.
Q&A for [ROM][L900] Cyanogenmod 12.0 [12/14/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][L900] Cyanogenmod 12.0 [12/14/14]. 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!
keyboard ?
works Good to what i see but there's no keyboard . Any fix for that ?
Working great no issues with phone, gps or camera. Great job and I look forward to the updates. Seems great so far.
Thanks
I just installed the new build I am only wondering how do I turn off my mobile data. This ROM is amazing and everything works except for data turning off and front camera
Battery Life
When i flashed this rom onto my device, i noticed a significant drop in battery life. Has anyone else noticed this and is there a fix for this?
thnx
Thank you sooooooooooo much man ,,, its sooooooo cooool ROM
working Perfectly on my sprint Note 2 SPH-L900
camera works fine ,,, everything is cool ,,, downloading now gapps
So I'm relatively new to the forums, I mostly just read, learn and try to stay out of way. Just flashed latest nightly last night. So far very smooth and stable. I did some poking a prodding this morning to answer some questions I had coming from CM11 which I was also new to.
Nice to see Sprint carrier billing back in this version. I know I saw it posted that NFC was not working but everything but Tap & Pay seems to work fine for me. Beam and Tags all function okay.
On top of Netflix not working yet, Play Movies 3.6.16 FCs on launch and after reverting to 3.4.23 it waits until you press play to FC.
I did have the keyboard issue that has been mentioned but was prepared with SwiftKey apk on my sdcard just in case. After finishing setup ALL keyboards seem to function just fine.
BT and GPS both working great.
All in all very usable and I'm going to give it a go as a daily for as long as possible though I may have to revert back to CM11 just for the Netflix/Play Movies since we only stream in my household. We'll see.
Not sure if this thread was the best place to share (I can't seem to comment on the main thread) but if there's a more appropriate place to provide feedback that someone wants to point me at, happy to do it.
Nice work everyone who's contributing. Thanks for your efforts keeping my Note 2 relevant.?
GPS
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
k3v0 said:
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
Click to expand...
Click to collapse
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
So I've been following the change log for this Rom, and I can't understand much.
I'm still on the 1/5/15 non nightly version and it's pretty much functional as a daily driver. What I'm wondering is are there any major differences for the newer nightlies?
Perhaps in addition to being a Q&A on these nightlies, everyone can post which version they're on, how it is (what's broken/what's been fixed), and what's new if anything.....
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
The Commish said:
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
Click to expand...
Click to collapse
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
t4d73 said:
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
The Commish said:
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
Click to expand...
Click to collapse
Lol. Yeah I wouldn't get your hopes up too high for that. It might happen but I guess we'll see. I don't think any device has gotten a milestone just yet anyway.
Sent from my SM-N910P using XDA Free mobile app
Keeps restarting on cm12 boot screen
Hey guys,
I have a situation I've never come across and wanted to see if someone might be able to point me in the right direction. I have two Samsung Note 2(l900) and running on cm12 as of this morning. I installed the new nightly on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
It seems to work just fine if I flash to stock touchwiz but recovery seems to have issues.
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
The Commish said:
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
Click to expand...
Click to collapse
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
KAZETARO said:
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
Click to expand...
Click to collapse
Sorry, I'm probably not the most knowledgeable. If it wasn't for these forums I wouldn't know how to do any of it. I haven't had any issues flashing, but I followed the steps I quoted from the get go and do that every time. Currently I'm back on the last KitKat nightly because Netflix/Play Movies is still not working on CM12. Have you tried any of the CM11 builds? Im currently using:
http://download.cyanogenmod.org/get/jenkins/98444/cm-11-20150118-NIGHTLY-l900.zip
and I use the 20140606 GApps package found here:
http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
The Commish said:
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
Click to expand...
Click to collapse
Odd that Netflix and Play Movies don't work. Plex, Amazon Instant Video, MX Movie Player, and Chromecast all work.
Sent from my SPH-L900 using Tapatalk
Deleted
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs
Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be
I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.
arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.
@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.
thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.
Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.