[ROM][14-03-2014] AOSP KitKat 4.4.2 Mod for Nexus S - Final Build

cn.fyodor

Senior Member
Dec 31, 2009
324
495
103
Nanjing
Hi folks,

There seem already many AOSP builds for NS, but I'm just pleased to share my personal build with you. I took the Google source and CM kernel/vendor as a base and have done lots of optimization work. My changes for NS after forking CM vendor were listed in the changelog of the initial build. Devs can check out commits on my github. It may worth a note that it's AOSP so never request extra features. No doubt I will keep it as stock as possible.

Credits:
  • clearly go to CM Team and all worked for our NS
  • steven676 for SurfaceFlinger and other patches

Download:
Final Build | MD5: 47af680bd273732d751de65656f62f7e

I don't hold the Nexus S any more, so if something in the final build does stupid for you, fall back to Build 6. And at last thank you again for your support.

Issues:

android-4.4.3-r1.1 build can be found in this reply. Panorama issue has been fixed.

You can find out all changes on my Github. Remember that AOSP ROM doesn't include Gapps, you have to install/flash it yourself.
Cheers,

Changelog:

Final Build
  • android-4.4.2_r2
  • merged some fixing patches from CM etc

Build 6
  • fixed random rebooting issue
  • saved about 3MB memory from the Kernel, thanks to pawitp

Build 5
  • android-4.4.2_r1
  • added swipe the pull-down panel to switch between Notifications and QuickSettings, thanks to CM/Slim
  • speed up statubar/notification drawer, thanks to kufikugel
  • changed dalvik heap parameters to reduce memory footprint (CodeAurora)
  • used double buffering instead of triple buffering
  • disabled hardware Vsync completely
  • fixed Screen record function, but in landscape only
  • increased the extra free memory to 12MB (you can change it in build.prop at any time.)

alpha 4
  • increased EGL cache size
  • switched to SW-based Vsync implementation by Google
  • fixed Keyguard layout for some languages
  • added a workaround to suppress the SU binary deprecated warning
  • few patches in Kernel and other minor fixes in SurfaceFlinger

alpha 3
  • merge in AOSP 4.4_r1.2
  • WebView black square issue was gone. Thanks to klusark for the wonderful porting work.
  • fixed app to sdcard function
  • enable low RAM feature in 4.4
  • root access fixed in Superuser with ART enabled
  • add Emoji support
Changes from init alpha Build:
  • merge the extra free kbytes patch from 3.4 Kernel
  • enable Swap for zRAM and KSM in Kernel side
  • Kernel 3.0.101
 

Attachments

Last edited:

leap_ahead

Senior Member
Jul 2, 2009
3,223
618
0
Thanks for trying. :p But Superuser was fixed for weeks and works for me.
no my friend .. I flash 3 times to make it sure and no work :p

if you go to settings superuser then u will se that u cant change anything in superuser settings..

also check with root checker..

but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
 
Last edited:

cn.fyodor

Senior Member
Dec 31, 2009
324
495
103
Nanjing
no my friend .. I flash 3 times to make it sure and no work :p

if you go to settings superuser then u will se that u cant change anything in superuser settings..

also check with root checker..

but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.

OK, anyone else got superuser issue? xD
 

ej8989

Senior Member
Jul 8, 2012
1,719
574
143
Manila
no my friend .. I flash 3 times to make it sure and no work :p

if you go to settings superuser then u will se that u cant change anything in superuser settings..

also check with root checker..

but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.

OK, anyone else got superuser issue? xD
Works fine here.
 

leap_ahead

Senior Member
Jul 2, 2009
3,223
618
0
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.

OK, anyone else got superuser issue? xD
I don't know ..is not work here for that I flash the zip ..

sorry but is ok to flash the zip ? or I must try again without the zip ?

*now I remember that I get notification that su is out date and I forget to click ...
Downloaded and installed the latest superuser.zip and the su binary out of date notification is gone
 
Last edited:

velishka

Senior Member
Nov 20, 2010
128
44
48
Very good job. So happy to see the deveopment for our old phone continues.
Now, I can confirm Superuser doesn't work. Flashing SuperSU from recovery fixed the issue pretty fast.
Other than that the ROM is very solid and smooth. I tested SMS, Location services, Wi-Fi, left phone without a charge for a night. No problems so far. Will test bluetooth streaming later today in my car.
I have the same issue with calendar like any other non google build has, I have two of them, one is AOSP build another is Google's from the play store. That doesn't bother me.

Also, I still want to know what kind of "optimization" was done. Also, can anyone test MTP for me? I turned it on using USB Switcher, but my computer didn't recognize the device.

Great job, I hope the project continues.
 

cn.fyodor

Senior Member
Dec 31, 2009
324
495
103
Nanjing
@leap_ahead, velishka:
Let's rule out some exceptions about Superuser issue. Did you do factory reset before flashing? I hope the old Superuser app didn't make noise. Although you guys have fixed it manually, I still hope someone can paste the output of command 'getprop persist.sys.root_access' and check if the /system/xbin/su is running when you can't get root permissions. Thank you.
 
  • Like
Reactions: londho

lagloose

Senior Member
Feb 11, 2008
728
2,969
0
Hey,
just had a closer look at your build and found the interesting property 'ro.sys.fw.bg_apps_limit' in your build.prop which is set to 8. Are you sure this works in your build ? (I only ask because this was seen only in CM until now)...

Greetz
 
  • Like
Reactions: leap_ahead

cn.fyodor

Senior Member
Dec 31, 2009
324
495
103
Nanjing
Hey,
just had a closer look at your build and found the interesting property 'ro.sys.fw.bg_apps_limit' in your build.prop which is set to 8. Are you sure this works in your build ? (I only ask because this was seen only in CM until now)...

Greetz
Yeah, CM merged that commit from Codeaurora afaik. Bet you haven't checked out my github yet. xD
 
  • Like
Reactions: leap_ahead

leap_ahead

Senior Member
Jul 2, 2009
3,223
618
0
Very good job. So happy to see the deveopment for our old phone continues.
Now, I can confirm Superuser doesn't work. Flashing SuperSU from recovery fixed the issue pretty fast.
Other than that the ROM is very solid and smooth. I tested SMS, Location services, Wi-Fi, left phone without a charge for a night. No problems so far. Will test bluetooth streaming later today in my car.
I have the same issue with calendar like any other non google build has, I have two of them, one is AOSP build another is Google's from the play store. That doesn't bother me.

Also, I still want to know what kind of "optimization" was done. Also, can anyone test MTP for me? I turned it on using USB Switcher, but my computer didn't recognize the device.

Great job, I hope the project continues.
I connect the phone to car radio so it ok !
for root you can flash the superuser from koush too ...
use marmite kernel for mtp ...
I use other gapps so I don't have the problem with two calendar ..only one I get the green one ...

---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------

@leap_ahead, velishka:
Let's rule out some exceptions about Superuser issue. Did you do factory reset before flashing? I hope the old Superuser app didn't make noise. Although you guys have fixed it manually, I still hope someone can paste the output of command 'getprop persist.sys.root_access' and check if the /system/xbin/su is running when you can't get root permissions. Thank you.
yes I make full wipe and ofcource factory reset ! with twrp recovery !
 

leap_ahead

Senior Member
Jul 2, 2009
3,223
618
0
[*]Superuser fails (Workaround is to run '/system/xbin/su --daemon' via adb shell, then go to Superuser settings -> allow root access. Then it'll be fine even after a reboot. Thanks to leap_ahead for bug report)
[*]Gesture typing not working?


[/LIST][/HIDE]
or you can flash via recovery the superuser zip from here :http://download.clockworkmod.com/superuser/superuser.zip

for gesture I use other gapps that gesture is working without any problem
 
  • Like
Reactions: cn.fyodor

lagloose

Senior Member
Feb 11, 2008
728
2,969
0
Used this baby for 3 days now and have to say that it has the best memory management for 'low-memory' devices i've seen until now. Whatever you did cn.fyodor, very good work. !
I've noticed that CM has already reverted the commit for property 'ro.sys.fw.bg_apps_limit'. You should take care that this is not reverted in your sources because IMHO this is one of the essential things which gives us this better memory management. The relevant part can be found in line 105 of https://github.com/Juansheng/androi...s/java/com/android/server/am/ProcessList.java in your github.

Greetz
 
  • Like
Reactions: leap_ahead

cn.fyodor

Senior Member
Dec 31, 2009
324
495
103
Nanjing
Used this baby for 3 days now and have to say that it has the best memory management for 'low-memory' devices i've seen until now. Whatever you did cn.fyodor, very good work. !
I've noticed that CM has already reverted the commit for property 'ro.sys.fw.bg_apps_limit'. You should take care that this is not reverted in your sources because IMHO this is one of the essential things which gives us this better memory management. The relevant part can be found in line 105 of https://github.com/Juansheng/androi...s/java/com/android/server/am/ProcessList.java in your github.

Greetz
Thanks for your suggestion. Actually I once changed MAX_HIDDEN_APPS back the default value in Gingerbread for low memory devices nine months ago. Check this commit. ro.sys.fw.bg_apps_limit was just introduced by Codeaurora recently. And yeah CM have already reverted this prop and added a new prop for high memory (> 1.5GB) devices since more CM supported devices hold more memories nowadays. I'll ignore that commit. :p

Cheers,