[ROM][4.4.4] CyanogenMod 11.0 [OFFICIAL][NIGHTLIES]

Lanchon

Senior Member
Jun 19, 2011
2,703
4,455
203
Hello @herna and other developers involved.

Thank you for such an amazing Nightly (23 Feb 2015). It's been almost 8 days I'm using it as a daily driver.

  • No heating problem
  • No GPS problem
  • No Wi-fi Issue
  • No auto reboot
  • Not even a single fc, since installation.

It's time to declare it as STABLE (At least for me.) Thanks again :good:
are you using ART? which gapps? thanks!

---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------

So if I experience battery drains on the last two ROMs, should I switch to TRIM kernel to stabilise it?
kernel without trim can cause more battery usage if write amplification factor is high (ie: your emmc is needing trim). the energy usage on writes is proportional to that factor, so it can make a big difference IN FLASH WRITES. how much of an impact that has depends on how much energy flash writes take compared to the rest of the phone, a thing i don't know. for example, if flash writes typically use 0.01% of the used battery energy on your setup and usage, cutting that use 10 to 1 is an amazing technological feat on itself, but won't give you any measurable advantage on your setup. alternatively, if it uses 10% of the energy, cutting 9 of those 10 percent points surely is going to make a difference.

you should be using a trim kernel anyway, so just grab my trim kernel and try it. if that doesn't help, start shopping for alternate kernels. my kernel is exactly what you already have, plus trim. no other changes.
 
Last edited:
N

notauseranymore

Guest
are you using ART? which gapps? thanks!

---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------



kernel without trim can cause more battery usage if write amplification factor is high (ie: your emmc is needing trim). the energy usage on writes is proportional to that factor, so it can make a big difference IN FLASH WRITES. how much of an impact that has depends on how much energy flash writes take compared to the rest of the phone, a thing i don't know. for example, if flash writes typically use 0.01% of the used battery energy on your setup and usage, cutting that use 10 to 1 is an amazing technological feat on itself, but won't give you any measurable advantage on your setup. alternatively, if it uses 10% of the energy, cutting 9 of those 10 percent points surely is going to make a difference.

you should be using a trim kernel anyway, so just grab my trim kernel and try it. if that doesn't help, start shopping for alternate kernels. my kernel is exactly what you already have, plus trim. no other changes.
Thanks for the tip, it certainly looks enticing. I'll take a look-see on my free time, since I'm using another ROM right now.
One question though, is it safe even when my USB storage is messed up? http://forum.xda-developers.com/android/help/problem-internal-usb-storage-t3039855
 

Lanchon

Senior Member
Jun 19, 2011
2,703
4,455
203
Thanks for the tip, it certainly looks enticing. I'll take a look-see on my free time, since I'm using another ROM right now.
One question though, is it safe even when my USB storage is messed up? http://forum.xda-developers.com/android/help/problem-internal-usb-storage-t3039855
there is nothing messed up with your storage. and yes, it is safe. NEVER link sd cards, they are slow, use a lot of power, get corrupted and die. repartition your phone if you want 4, 6, 8GB etc of app storage. i recommend at least 6. if you dont want to repartition, move apps to the INTERNAL sdcard using standard android mechanisms.
 

stephendt0

Senior Member
Apr 9, 2012
1,437
368
103
QLD, Australia
Looks like the 9th March cm-11-20150309-NIGHTLY-n7000.zip release reboots my phone when using wallpaper ._.
Thanks for the heads up. :good:

I personally am having some serious issues with my Note... I don't use it every day but it stays on for a long time (use it as a dedicated car media/GPS device). What happens is that my device will randomly reboot and struggle to load Android... once it loads it'll probably randomly reboot again. On the 11th of Jan nightly with Lanchon's TRIM kernel. I'm a bit afraid that TRIM is killing my NAND - I entered recovery and the NAND was SLOW to copy a new nightly across... will flash now and see how I go.
 

stockuser

Senior Member
Mar 4, 2015
61
8
0
Kolkata
The nightly of 20150302 is fine. So was the previous week's. And the one before that.....actually since Lanchon's FPbug fix got merged into the CM kernel it has become a thoroughly stable ROM.

The various docs for going from Samsung JB 4.1.2 to CM are truly awful, being variously contradictory, out of date and just plain wrong (absolutely ignore eveything on the CM wiki).

Here's something extra to add to the confusion (sorry):

To install a CWM recovery on stock, using just your phone's recovery mode, you need a signed version as unsigned zips are rejected by the stock Samsung recovery and are not installable. For the GT-N7000 this means you need to find a PhilZ-cwm6 - Safe Stock Based Kernel (this will replace Samsung recovery with CWM recovery so you can then install unsigned zip). This must match as closely as possible your phone's Samsung kernel (this varies somewhat from region to region). See http://forum.xda-developers.com/showthread.php?t=1901191 . Post #2 will help you identify the specific version you need. Download the appropriate PhilZ kernel to your phone's internal storage. Also download the latest CM11 nightly onto your phone's internal storage. Now boot into recovery mode and flash the PhilZ recovery. On successful completion again reboot into recovery. You should now be in the new recovery. Do a factory reset/wipe and you are now ready to install the CM11 zip. After you have done this it will take a while to boot and start up. Be patient and don't panic.

CM11 includes its own CWM recovery and if you again boot to recovery you will now find that PhilZ recovery has gone and a rather more basic CWM recovery is in place. This is fine, it is all you need.

Assuming you install CM11 OK and you then want to get the best out of it then you can also consider installing one of Lanchon's TRIM enabled kernels, or (similar) the latest Raw kernel found at http://forum.xda-developers.com/showthread.php?t=2397000 There is no real performance difference between Lanchon's and Raw but the Raw kernel properly supports the illumination on the Note's hardware "back" and "menu" buttons.

I'm from India and I'm running stock firmware N7000DDLSC without any modifications/root. Downloaded PhilZ-cwm6-DDLSC-ODD-5.11.2-signed.zip from here. Flashed Philz in stock recovery, rebooted into Philz recovery and went to "Mounts and Storage" and formatted /system, /data, /preload. Then rebooted to recovery again by going to "advanced", "reboot to recovery". Downloaded Raw kernel from here previously and flashed it successfully. Rebooted to Philz again, now the background is black with green headers instead of the familiar pink background. Flashed CM zip downloaded from here and now midway through the flashing it gets installation aborted, Status 7 Error! WTF, what am I doing wrong? I checked the instructions thoroughly, tried numerous times, sometimes doing a factory reset before flashing CM but unfortunately to no avail. After all these, when I try booting I get stuck in bootloop and had to flash the stock rom through odin to recover my Note!

Please can someone help me? I very badly want to ditch this laggy TW and jump ship to CM11.

I followed this thread as a guide.
 

Lanchon

Senior Member
Jun 19, 2011
2,703
4,455
203
Thanks for the heads up. :good:

I personally am having some serious issues with my Note... I don't use it every day but it stays on for a long time (use it as a dedicated car media/GPS device). What happens is that my device will randomly reboot and struggle to load Android... once it loads it'll probably randomly reboot again. On the 11th of Jan nightly with Lanchon's TRIM kernel. I'm a bit afraid that TRIM is killing my NAND - I entered recovery and the NAND was SLOW to copy a new nightly across... will flash now and see how I go.
no, it's not killing you nand! trim is making it last longer, sparing its life due to less write amplification.

to have a faster device you need:
-free space in /data, the more the better (id recommend repartitioning to get 4 or 6GB /data partition)
-regular trims (on android 4.3+ these should normally be automatic each day, but may not be running in you case for whatever reason)
 

stephendt0

Senior Member
Apr 9, 2012
1,437
368
103
QLD, Australia
no, it's not killing you nand! trim is making it last longer, sparing its life due to less write amplification.

to have a faster device you need:
-free space in /data, the more the better (id recommend repartitioning to get 4 or 6GB /data partition)
-regular trims (on android 4.3+ these should normally be automatic each day, but may not be running in you case for whatever reason)
I used an app called Device Control to TRIM my device every 8 hours. I've now done a factory reset with the 23rd of Feb nightly, so far, OK. Not using your kernel at the moment though. However, still having problems. My SD card will still dismount at random intervals, not sure why. I'll try another SD card and report back. Otherwise it seems like my note is on the blink :(
 

Jack4L_

Senior Member
Oct 15, 2013
97
52
0
Have anyone tried the latest nightly(0309)? Is there any changes in the theme engine? Thanks in advance.

Sent from my GT-N7000 using XDA Free mobile app
Yaee, Doesn't work properly. When you change a theme to another sometimes you got a System.ui FC. All the rest works like a charm.
 

stephendt0

Senior Member
Apr 9, 2012
1,437
368
103
QLD, Australia
My note is being very problematic even after a factory reset. I just left it on a desk all day and when I got back it was lagging on the Cyanogenmod splash screen :( I'll do a full system wipe with latest Gapps and see if it behaves.
 

Toruk.Makto

Senior Member
Sep 16, 2011
644
312
0
New Delhi
My note is being very problematic even after a factory reset. I just left it on a desk all day and when I got back it was lagging on the Cyanogenmod splash screen :( I'll do a full system wipe with latest Gapps and see if it behaves.
Buddy, trust me last 3 nightly are stable for everyday use, I've NOT experienced any single problem on Feb 23rd Nightly other than few SystemUI FC that too after applying few themes. Other than this, I can say it's not nightly anymore but stable (atleast for me)

see here : http://forum.xda-developers.com/showpost.php?p=59193399&postcount=1654
 

stephendt0

Senior Member
Apr 9, 2012
1,437
368
103
QLD, Australia
Buddy, trust me last 3 nightly are stable for everyday use, I've NOT experienced any single problem on Feb 23rd Nightly other than few SystemUI FC that too after applying few themes. Other than this, I can say it's not nightly anymore but stable (atleast for me)

see here : http://forum.xda-developers.com/showpost.php?p=59193399&postcount=1654
I agree... it was stable until my device started malfunctioning. I think it must be something wrong with my device. I'll test and report back if things are OK with it.
 

androds

Member
Mar 5, 2015
46
6
0
For the last three nightly i am not been able to use either raw or forest kk kernel... always getting a boot loop... what may be the problem? is the ini script changed??? i need a kernel with s3cfb driver to get more vibrant display.
 

farhanzahinfj

Senior Member
Nov 14, 2011
340
103
0
Dhaka
For the last three nightly i am not been able to use either raw or forest kk kernel... always getting a boot loop... what may be the problem? is the ini script changed??? i need a kernel with s3cfb driver to get more vibrant display.
Re-download the kernel zip files. You might have had some data loss. I'm using raw kernel with the latest nightly. Everything is fine.

Sent from my GT-N7000 using XDA Free mobile app