yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Setting.Out:
[MENTION=2253579]cn.fyodor[/MENTION]

Hey I found this mod/patch?.. http://xdaforums.com/showthread.php?p=47913794 ... I am using the CM variant with good results (consistently +200 in Antutu and +300 in Quadrant), I was wondering if you could look at them and maybe use/implement any of this in your rom for added gain?..
[Nexus S Android Development] rho57:
Flashed Devil kernel and Play Store keeps on crashing while on euroskank cm11 builds it doesn't happen.
[Nexus S Android Development] tobice:
Hey guys, I'm a proud owner of Nexus S, running CM 10.1.2. I've read that KitKat should be optimized for low-end devices with RAM as little as 512MB. So what is the real life experience with Nexus S running KitKat? Is there a noticeable difference when it comes to speed, responsiveness, fluidity, battery life...?
[Nexus S Android Development] dwielunski:
Devices like the Moto G should benefit from these optimizations. But for older devices like the Nexus S it's not ever going to be really great. The problem is that the Nexus S uses a single core processor made by Samsung for which there is no longer any "official" development happening, and so the graphics drivers might not ever work properly. People are doing good work here, but it is really for hobbyists only at this point.
[Nexus S Android Development] treesurf:
I'm using the Euroskank build of CM11 and it is just as responsive as CM10.2. As it is still in the early stages of development I expect it to get even better. There are a few minor bugs still, but it's already daily driver material, at least by my standards.
[Nexus S Android Development] OrbitGum22:
How come the status bar isn't transparent like on the Nexus 5?
[Nexus S Android Development] notbrodie:
if you guys didn't know, xposed framework is 4.4 stable, and combined with Gravity Box, this rom is now amazing!

Sent from my Nexus S
[Nexus S Android Development] cn.fyodor:
As the author said, the mod is optimized for QCOM based devices. I don't think it will help the performance for NS in reality.

I don't know both Devil kernel and euroshank builds. I'm also a kernel maintainer for years. Would you like to tell me why flash Devil kernel, more custom options?

It was disabled by me and will be enabled in next release. :P
[Nexus S Android Development] OrbitGum22:
Oh, alright. Thanks lol
[Nexus S Android Development] dwielunski:
If you're satisfied with the performance of the Nexus S, either on CM10.2 or CM11, that's great, but it's not what Google is talking about when they say KitKat is targeting great performance on low end hardware. They are actually hoping to deliver more than is achievable with our hardware.
[Nexus S Android Development] k-kuchen:
Do you have links for Gravity Box and Xposed? Any downsides to it?
[Nexus S Android Development] Setting.Out:
Well I've tested it, it's scoring higher benchmarks (more than I've ever got with any ROM I've tried).. I got just over 3000 in Quadrant and nearly 6400 in Antutu, video playback is smoother ( using MX player, I would get shudders and choppiness using standard settings, but now it's as smooth and fluid as when enabling their video accelorator, heavy apps seem a bit more fluid and I'm getting less lags...

Thought it might be worth a read through either way..
[Nexus S Android Development] rho57:
Yes. Especially the colors. What I dont like in stock kernels is that it makes the screen appear yellow. I flash other kernels in order to get rid of it.
[Nexus S Android Development] notbrodie:
http://xdaforums.com/showthread.php?t=1574401

you can install gravity box from inside xposed (check the modules section).

they only downside i can think of is: no ART

Sent from my Nexus S
[Nexus S Android Development] jc4gavejc:
Gravity box doesn't replicate the status bar gradient you get in kitkat. Its actually intentionally disabled in low end devices citing performance issues. I enabled it in my port following this guide: http://xdaforums.com/showthread.php?t=2510410

Performance doesn't seem to suffer at all and you get the full nexus 5 experience.
[Nexus S Android Development] notbrodie:
I couldn't care less about status bar opacity. I actually prefer it black.

Sent from my Nexus 5
[Nexus S Android Development] morrigan91:
Full kitkat experience

Hi, guys..

for those who want FULL KITKAT EXPERIENCE I have built this MOD for Traslucent statusbar Home+Lockscreen

ONLY AOSP 4.4 Build3

About Mod

Downlaod

Nandroid Backup

Install ZIP

Enjoy Kitkat.!!
[Nexus S Android Development] k-kuchen:
It works, thanks. But somehow the power button didn't turn off the screen the first 20 seconds after reboot ^^
[Nexus S Android Development] morrigan91:
mmh.. after reboot kitkat start all service.. on my device work well.. try after 3 min/daily use and report if iusses remains..

Many thanks
[Nexus S Android Development] michalurban:
Hi, its a great ROM and Im not trying to push anyone here, Im just curious - when should I expect a stable version of this ROM? :)
[Nexus S Android Development] k-kuchen:
It happens every time I reboot, but it could be related to something else, too. I just installed GravityBox a couple of days ago.

It's not a major problem anyway. Just something I noticed
[Nexus S Android Development] notbrodie:
What do you find unstable about the rom? along with xposed, I'm not seeing any deal-breaker issues. not really seeing any issues, actuallu

Sent from my Nexus 5
[Nexus S Android Development] Setting.Out:
Is cyanogen mod unstable? or Slim? yet they produce "stable" releases it is generally used as a term of non-alpha/beta where all the kinks are worked out.. Though this rom is fairly stable, I'm sure that as 4.4 moves out of its early stages and more work can be done for crespo, the rom will be dubbed "stable"...

;)
[Nexus S Android Development] sniperIT:
Update Superuser

I've been a little confused as to how to update the SU application in this ROM.

Is there somewhere I should be looking? Or is this something we have to wait for?

Nick
[Nexus S Android Development] notbrodie:
Just flash supersu through recovery. after that, it will update itself when the app gets an update through the play store
[Nexus S Android Development] Warren_Orange:
What should I try? This or cm?
[Nexus S Android Development] cn.fyodor:
I changed the layout a bit for the Keyguard, please test. :P

It was caused by a bug from original Superuser on non-embedded devices. I'm sure the Su binary has been updated to the latest version, anyway I've made a dirty work around for the warning issue. So it'll be 'fixed' in next release.

EDIT: deprecated attachment, deleted...
[Nexus S Android Development] Setting.Out:
With swype?
[Nexus S Android Development] notbrodie:
AOSP & Xposed w/ GravityBox. better than cm by a long shot
[Nexus S Android Development] k-kuchen:
That's how it looks now. Definitely better :D

Thanks!
[Nexus S Android Development] sniperIT:
Thank you very much.

BTW, I've been using your 4.3 AOSP+ ROM for months now and I have to say it's the best ROM I've ever used by far, and I've been an Android user for several years now and flashed many, many ROMs.

I'm not using the 4.4 yet as a daily driver, but I am really looking forward to your final release.
[Nexus S Android Development] k-kuchen:
Do we need this Dialer.apk in your new Alpha 4? :D
[Nexus S Android Development] cn.fyodor:
Nope, it's already included in Build 4. :P
[Nexus S Android Development] Setting.Out:
Does your kernel support init.d and vibration control?.. if not could you add it?? :)
[Nexus S Android Development] sniperIT:
The dailer doesn't seem to be syncing contacts?

Anyone else experiencing this issue?

I used the alpha 4 build with the current full install of PA Gapps.

EDIT: no worries I ended up fixing it will a reinstall.
[Nexus S Android Development] rakeshbro:
Rom is working fine, but the superuser apps sucks when i try to pin protection the app, It force close,

Just replaced it with supersu and now everything is good.

Thanks For The rom.
[Nexus S Android Development] asubiyyal:
Guys I have been reading and reading and then some these last few days. Still dont understand how this works. I first went to this thread http://xdaforums.com/showthread.php?t=2034264 which took me to a complete picture guide http://webcache.googleusercontent.com/search?q=cache:http://www.droidviews.com/nexus-s-guide-unlock-bootloader-root-install-custom-recovery-custom-roms/ for unlocking bootloader, root, custom install recoveries and custom ROMS.

As I understand this is a Custom ROM right?

I mounted the latest SuperSu v1.8 thru TWRP then went to install it failed. Then I just stopped didnt want to brick it. (my important stuff pix, music and miscellanous is all saved on computer m not really worried about the format) However the guide by DJBhardwaj uses SuperSU 0.98, so does that make difference

So my bootloader is unlocked, I know that. Can anyone help here. I understand completely this is developers forum but please m begging, If I can get what I am doing wrong or some other tutorial. I'm really frustrated because I've invested so much time into it researching. A little guidance would be nice.

My device is Nexus S unlocked (Tmobile GSM) version 3G.

Also this ROM by OP is the closest to thing to stock Android 4.4 that I will get? And the ROM on CM's website for NexuS is different then the one in OP?
[Nexus S Android Development] Setting.Out:
PM me, I will walk you through it.. :)

---------- Post added at 06:15 PM ---------- Previous post was at 06:12 PM ----------

[MENTION=2253579]cn.fyodor[/MENTION] So... Any plans on build 5??? .. :) 4.4.1 is out.. :D No rush, but it would be cool!!
[Nexus S Android Development] korro:
Hello.

Which radio do you use with this rom?
[Nexus S Android Development] mushan3420:
4.4.2 is out.
[Nexus S Android Development] cn.fyodor:
I'm testing 4.4.2. If everything rocks, the new build will be released in one/two days or this weekend. Also being testing the PVR crash issue. I still can't figure out why CM didn't have this bug as their users reported.
[Nexus S Android Development] CataHd:
Anyone notice that after 4.4 r1.1 we lost preview in panorama mode?this happened even on cm
[Nexus S Android Development] Setting.Out:
Yes, slim too..
[Nexus S Android Development] arpitsinghi:
Not able to install Alpha 4

Hi friends, i was using Alpha 3 previously and tried SlimKat ROM because in Alpha 3 there is a known bug of Random restarts. I had made a nandroid backup but was unable to restore it. It says unable to mount system I tried installing the Alpha 4 version but it says Unfortunately, the process com.android.phone as stopped. and keeps on restarting. I had already deleted Alpha 3 zip file. So i had to install SlimKat again. I want to switch back to this ROM as SlimKat has a additional RAM usage of around 50 MB.

Please help
[Nexus S Android Development] nelars:
Probably a bad download, try it again and do a new clean install.
[Nexus S Android Development] cn.fyodor:
Please test the latest build. The patch by Pawit has been already merged in. [MENTION=5165039]Setting.Out[/MENTION]
[Nexus S Android Development] Setting.Out:
;( ... I can't flash it because I'm going on vacation... But I wish I could.. :)
[Nexus S Android Development] abinash:
In the prev builds front camera issue was there.....i wondered if this has been fixed in build 5. downoading now

:)
[Nexus S Android Development] darkmentor25:
Hello,

There's difference in making a nandroid on CWM 6.0.4.x and on CWM < 6.0.4.x

I think it's related to the mounting of SDcard and CWM 6.0.4.x not mounting /system while creating a nandroid (Dont knw why is it this way)

But, if you have a nandroid backup on ur SDcard, then try restoring it with a Recovery that is old; like 6.0.2.7 or something..

(Even though a new installation of KitKat is not possible thru old recoveries, it's possible to restore nandroid of KitKat with these :rolleyes:
[Nexus S Android Development] marcosxp:
Where can i get the GApps? Sorry, noob q :D
[Nexus S Android Development] notbrodie:
Google "banks gapps xda"

Sent from my Nexus S

---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------

@cn.fyodor

would you be willing to implement dynamic fsync, or the ability to disable fsync?

Sent from my Nexus 5
[Nexus S Android Development] Setting.Out:
You can mod your build.prop and disable fsync.. Just get an editor at the play store..
[Nexus S Android Development] notbrodie:
didn't know that. what line to edit?

Sent from my Nexus 5
[Nexus S Android Development] Setting.Out:
Add a line.. I can't give you links as I'm in Singapore.. But it is easily searchable.. It is like " ro.disable_fsync=0 ". But not that exactly.. I can't remember... :)
[Nexus S Android Development] notbrodie:
my google-fu appears to be failing me. does anyone else have any info on disabling fsync?

Sent from my Nexus 5
[Nexus S Android Development] ej8989:
Install trickster-mod from playstore. Then toggle to disable fsync.
[Nexus S Android Development] notbrodie:
i have trickster installed. there is no such option when using the kernel that came with the rom.

the only option on that page is zRam, which appears to be not as necessary, now that 4.4 has the low ram feature (which means I usually have 160-180mB's free)
[Nexus S Android Development] _Nikon_:
The song name on the lockscreen Play Music widget doesn't update on music change. Is that an issue with the ROM or with the app?

Also, after rebooting all my installed apps were gone, it was like it had returned to "stock custom ROM".

Any of these problems on my end or is it a WIP related thing? If it matters, I'm using these gapps. Also, what's the difference between the ROM's launcher and the standalone one on the first post?
[Nexus S Android Development] HeroKhar:
Odd Gapps Issues...

Great work on the ROM so far you guys, but I'm having massive issues with Gapps.

4.4.2 PA Gapps and an unofficial 4.4.2 PA Gapps were used, as well as the CM 4.4 one.

The recovery I used was PhilZ's Touch Recovery 6.01.0 for Crespo.

***

They all flashed correctly, however with these issues:

Unofficial 4.4.2 PA Gapps - Flashes successfully, on the setup screen Phone, Hangouts, and a couple other Gapps FC'd.

CM 4.4 - Hangouts FC'd.

4.4.2 PA Gapps - Flashes successfully, go through Setup Wizard just fine. Once phone is setup (Tested both skipping and signing into Google), Setup Wizard will absolutely crash and will leave me with a black screen and a status bar.

I've tried wiping data/cache, wiping for a new ROM (an option in the recovery, essentially wipes data, dalvik, factory reset, etc) before and after Gapps flashing.

Even tried rebooting into Safe Mode, lead to boot loop!

Not really sure what else can be done, as it always leads to a boot loop. If anymore info is needed, let me know and I can test it/provide it. Thanks again.
[Nexus S Android Development] nexususer:
Download and flash PA mini modular gapps not the full package that will definitely help try and report back !! Happy flashing :D
[Nexus S Android Development] array81:
I have tested this rom until build 3. After I have removed it because I had problems and FC with dialer.

I'd like know if now these problems are solve before test it again.

Thanks
[Nexus S Android Development] cn.fyodor:
It's dangerous to disable fsync. You can't disable it in my ROM unless flashing other kernels.

Both AOSP Music and Google Music widgets work for me. Is that Google one? :P

If a function is working in progress, of course I'll write down the note in my releasing thread. I always flashed lots of times to make sure everything was working before releasing a new build. The launcher in the ROM is Launcher2 while the other one attached is Launcher3, the new launcher also released by Google in KitKat. Please search and read before asking.

To be honest, I never got FC even in alpha build 1. That sounds weird. What recovery did you use?
[Nexus S Android Development] notbrodie:
flash banks 4.4 gapps, standard package

Sent from my Nexus 5
[Nexus S Android Development] array81:
I use last clockwork recovery with a clear installation. with build 2 and 3 (I don't have test 1) When I receive a call or make a call sometimes (about 1 or 2 times for days) my device was reboot. Besides I had graphics problems with dailer. For these reason I have install cyanogenmod.
[Nexus S Android Development] cn.fyodor:
It's a known bug about PVR drivers, not kind of FC. And I did a work around for the Dialer app in Build 5, so it will not crash any more. But other app still has a little chance to crash the system. Luckily I haven't run into the reboot issue in Build 5 for several days.
[Nexus S Android Development] _Nikon_:
It's the Google one, I don't use AOSP music app. The way it happens is, when listening to any album, when the music changes, the widget doesn't update the song name, not even if I pause and resume. I have to either unlock and lock again (turning the screen off and on again doesn't work) or long press the pause button to switch to seek bar and long press again to revert to song name, and this time the song name will display properly.

The thing about rebooting seems gone for some reason, don't know what caused it.

About the Launcher, it's hard to find a specific subject within almost 60 pages of comments. Sorry about that. I asked because I noticed some major differences (like five apps row instead of four and no left swipe to Google Now) and wondered if it was a custom launcher.

BTW, is this and this supposed to be like this? It's been non-aligned since JB and I've always wondered why it wasn't fixed yet. Weirdly enough, if I change the system language to english it aligns. Seems to be just sloppy work.
[Nexus S Android Development] steven676:
I cannot stress this enough. "Disable fsync()" may sound innocent, but as an option it should really be relabeled "EAT MY DATA" in bright flashing red letters. (That's particularly true in the case where the host system has known crash bugs, such as those that all PVR-using devices suffer on 4.4 at the moment -- but even on a perfectly stable platform, running out of battery would be enough to cause data loss.)
[Nexus S Android Development] cn.fyodor:
Thanks for bug report. That's not weird as most users are using English and I using Chinese. The icon is not cut off with both languages. Sorry I can't read your language, Portuguese? :P
[Nexus S Android Development] _Nikon_:
Yes, it's portuguese.
[Nexus S Android Development] Zahih:
Hi [MENTION=2253579]cn.fyodor[/MENTION],

I've been run your latest build 5 for the last 3 days.

More smooth & stable than your previous version.

And runs great with GravityBox... :thumbup:

Thanks...
[Nexus S Android Development] arpitsinghi:
Hi [MENTION=2253579]cn.fyodor[/MENTION],

i was using Alpha 3 previously and tried SlimKat ROM because in Alpha 3 there was a known bug of Random restarts. I had made a nandroid backup but was unable to restore it. It says unable to mount system I tried installing the Alpha 4 version but it says Unfortunately, the process com.android.phone as stopped. I tried again with ALPHA 4, same error and keeps on restarting.

Please help
[Nexus S Android Development] notbrodie:
which recovery are you using? try philz recovery. perform a factory reset for a new rom (it will also wipe system), then flash rom, gapps, etc.

if that doesn't work, try performing a formatting system with fastboot, then immediately flashing rom in recovery.

also, ensure you are using the correct gapps. I recommend banks 12/14 gapps

Sent from my Nexus 5
[Nexus S Android Development] Miguun:
That "cannot mount X" is CWM is a bug/error, sometimes it gives me that error, sometimes not.

Just keep trying as many times you can (yesterday only worked after 5 times), sometimes cant mount system, other times data, its random.
[Nexus S Android Development] Zahih:
Why don't you try build 5, it's more stable and smoother than that both versions I thought.
[Nexus S Android Development] arpitsinghi:
Hi Zahih,

Thanks, I have now managed to switch to Alpha 5.Only 1 problem now exist. I am unable to erase my USB storage thru menu. I thought it would be better to clear all but its not working. I am able to mount the storage. Able to transfer and delete from PC. I tried from the apps menu in settings, i got message "USB storage is currently being checked" I am not able to format it via CWM recovery also. I tried troubleshooting it by USB Host Check app got the error "android.hardware.usb.host.xml not readable" Can anyone help for this

Regards,

Arpit
[Nexus S Android Development] steven676:
About those PVR crashes ...

Does https://android.googlesource.com/pl...+/2aff7025482cc40d2ebd45f81cdb318ac1c6f868^!/ (in AOSP master, but not in 4.4 or in CM EDIT: merged) help? I've been running it for several days now on tuna without seeing crashes, graphical glitches or loud PVR debug dumps in dmesg.

Given that those PVR debug dumps appear to correspond to these messages in the Android log:

W/GraphicBufferMapper( 748): registerBuffer(0x5dc22c88) failed -22 (Invalid argument)
E/GraphicBuffer( 748): unflatten: registerBuffer failed: Invalid argument (-22)

that suggests the following chain of events leading to the crash:

Registering a gralloc buffer fails (for unknown reasons, probably something to do with things that happen in the proprietary blobs).

GraphicBuffer::unflatten() returns an error, but (without the patch above) does not clean up after itself.

Something else comes along and attempts to use the GraphicBuffer object, which now contains a pointer to god-knows-what. This could cause memory corruption, leading to graphical glitches and (eventually, unpredictably) crashes.

With the linked patch applied, I still see those registerBuffer() failures in logcat output, but never screen corruption or the stack dumps in dmesg.

EDIT: One other patch of interest: https://github.com/CyanogenMod/andr...mmit/0f93dc6e231e915c82ede24bace1091a1c62569e appears to be a workaround for the garbage you see in the screenshot animation. (It probably shouldn't be called a fix, given that all it does is copy the contents of one bitmap to another.) Ignore me, that seems to be an OMAP4-specific problem.
[Nexus S Android Development] lagloose:
Off-thread...

have applied this patch in my Omni-ROM and will look if crashes and glitches are gone. Will report back here.

Greetz
[Nexus S Android Development] adm1jtg:
Have applied this patch on slim betas and so far everything is good no graphical anomalies and no reboots
[Nexus S Android Development] kwbr:
Good thing cn.fyodor you keep the Nexus S alive in 2014! Respect and a happy new year to all!
[Nexus S Android Development] tchaari:
I just wanted to give big big thanks to steven676 for finding the patch that fixes the graphics glitches and reboots on many devices.

Happy new year for all here :)
[Nexus S Android Development] CataHd:
Hi [MENTION=2253579]cn.fyodor[/MENTION] if the new patch solved the reboot issues will you remove the mods from slim/cm to be clean aosp?

Edit:I also found this on galaxy mini 2 forum persist.sys.force_highendgfx they added it to their cm11 to enable all kitkat options without losing the low ram enhancements.

Is it god for us to?
[Nexus S Android Development] cn.fyodor:
Thank you again, steven676. The patch works for me. No reboots after continuous two days use.

And I finally finished my paper work in last few months. Cheers! ：D
[Nexus S Android Development] velishka:
it's not rom, it's cwm related
[Nexus S Android Development] husty84:
One small bug

Thanks for great clean aosp rom for NS. I found only one "bug". BLN is enabled without chance to disable. I try BLN Control and NSTools, I dont see option for disable BLN.
[Nexus S Android Development] mr.haqeem:
should it have a restart option + recovery/bootloader?