[ROM][4.4][noobdev] CM 11.0 with app2sd, glove mode, dual boot for all S4 variants

Please check the stability of the nightlies before flashing or updading: http://tinyurl.com/noobdevFebruary CM has been merging some problematic commits lately.

The noobdev team is proud to present its noobdev CyanogenMod nightlies! This ROM is pure unmodified CyanogenMod with additional useful features, such as IR and app2sd support, as well as other device specific fixes and features. If you want me to add a specific commit or feature, just leave a post here.

Huge thanks to all the developers that made this possible and also the donators for supporting this ROM!

Enjoy!

Donators:

• [MENTION]WoodburyMan[/MENTION]
• [MENTION]corkythetard[/MENTION]
• [MENTION]BillGoss[/MENTION]
• [MENTION]marvi0[/MENTION]
• [MENTION]bhtm[/MENTION]
• Benjamin Benichou
• [MENTION]Buster99[/MENTION]
• [MENTION]Tjoffe66[/MENTION]

Features:

• Dual boot!
• Open-source Google Dialer
  • http://xdaforums.com/showpost.php?p=48953638&postcount=4439
• Moving apps to SD card
  • http://xdaforums.com/showpost.php?p=44990642&postcount=1656
• Facebook sync with native app (with phone numbers!)
  • http://xdaforums.com/showpost.php?p=45508480&postcount=1918
• Glove mode / high touch sensitivity
  • http://xdaforums.com/showpost.php?p=45023111&postcount=1676
• Delta OTA updates

Instructions:

1. Flash CM 11.0 and the gapps below.
2. Clear /data and /cache if you are coming from another ROM.
3. Reboot.

Dual boot instructions:



Downloads:



Source code:

Anyone is free to use my patches in their ROM However, I will not be submitting any more non-critical patches to upstream CM. I can't accept that my code could potentially be sold for a profit or distributed as closed source.



How do I...?



Todo



Who's in the noobdev team?

• chenxiaolong (me!)
• WoodburyMan

XDA:DevDB Information
[ROM][4.4][noobdev] CM 11.0 with app2sd, glove mode, dual boot for all S4 variants, a ROM for the Samsung Galaxy S 4

Contributors
chenxiaolong
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod

Version Information
Status: Stable

Created 2013-09-14
Last Updated 2014-02-02

I just merged the 4947-line mega patch for the feature I hinted at earlier https://github.com/chenxiaolong/hud...e-dialer/0001-Open-source-Google-Dialer.patch

I spent the last two days reverse-engineering the Google Dialer and I'm happy to say we now have a working open-source implementation of it! Because my implementation is open-source, it is built into the CyanogenMod dialer, meaning you don't lose any features, like call blocking.

Prerequisites:

You need to have a Google Apps package installed for the Nearby Places and Caller ID features to work. For those who don't use Google Apps, the dialer will continue to work as before.

Screenshots:



Source code:

Java code: https://github.com/chenxiaolong/hud...e-dialer/0001-Open-source-Google-Dialer.patch
Auto-merged translations: https://github.com/chenxiaolong/hud...1-Auto-merge-Google-Dialer-translations.patch
Re-add LoaderCallback (CyanogenMod-specific): https://github.com/chenxiaolong/hud...d-LoaderCallbacks-to-CyanogenMod-dialer.patch

iamnotkurtcobain said:

Will the cra**y webview/chromium performance with aosp browser, instagram, google now,... ever be fixed? Why did they ditch the smoother and faster webkit?

Gesendet von meinem SGH-M919 mit Tapatalk

Click to expand...

Click to collapse

WILL YOU FINALLY ANSWER MY QUESTION AND RESPOND, PLEASE!! WHAT ARE U COMPARING YOUR EXPERIENCE TO? WHAT IN THE HELL ARE YOU COMPLAINING ABOUT???? WHAT LAG, WHAT STUTTER!?! WHAT KIND OF DEVICE ARE YOU COMPARING YOUR EXPERIENCE TO!?

You really have to start to elaborate on what it is you are CONSTANTLY complaining about. You, the man on top of all cherry picks and commits should know that we have an in rom screen recorder now....

SHOW US WHAT YOU'RE CONSTANTLY *****ING ABOUT. SHOW US THIS LAG, THIS HORRIBLE, LIFE RUINING, MUST HAVE BETTER, MIND BLOWING, BUTTERY SMOOTH THING YOUR SAD, CLOSED LIFE DESIRES.

Your immature, feed me attitude is ruining the experience for other users.

PRODUCE SOMETHING. A log cat, definitive evidence, A DONATION, anything!!!!!

If you can't, just stfu, this isn't a complaint thread for the inept. This is a development thread. If you have some OCD or some kind of perfectionism issue, see a therapist. Leave KT and this thread alone, you contribute ZERO.

An hero, please.

To clarify the problem and hopefully ease tensions....

In Android 4.4 just about everything is a improvement. The only main issue that we've noticed is that Google basically screwed over the stock browser and webkit. They plan on phasing it out soon and using Blink most likely or switching Android to include Chrome by default. Because of that, there are many new issues and performance issues with Stock Browser / Webkit. As far as if there's anything that can fix it, there is most likely nothing any dev's for CM or maintainers of this ROM can do, as it's a upstream problem with Google. Maybe they'll fix it in the upcoming 4.4.1 release that's been spotted across the web. May not. Either way it's out of their hands. If this is really such a huge issue that makes your phone unusable, then Android 4.3.1 is the way to go, or earlier. Given also CyanogenMod11 / 4.4 is still in pretty much Alpha form, and the fact that CyanogenMod lost many developers for Samsung between both Samsung's policy against modding, and the larger drama involved with so call "commercialization" of CyanogenMod, our devices are not as well maintained as they once were, so it will take longer for 4.4 to become stable on these vs 4.3 and 4.2. (Reason why I'm selling my S4 and just picked up a Nexus 5...)

Now. Onward to your specific case @iamnotkurtcobain You've been helpful in this thread. However, constantly complaining about the lag does not help when others cannot reproduce it. Most people here use Chrome, and what stock browser experience they have seems normal. We would need a logcat of this issue, or better yet with screen recording a option now, a video or something of this behavior. I understand you're complaining about Google, and being nice to everyone in this thread and not blaming the dev's or anything, but it creates a somewhat negative vibe about something no one can do anything about (Perhaps overall because of a upstream issue, most definitely nothing without a logcat or a video). If you show me something specific I can even test it on my Nexus 5 to see if it's a specific problem with the S4 or not as well. Just we need _something_ to go on. The reason why everyone here seems to be "jumping out" at you is because of their frustration. They want to help you, after all that's what this thread and XDA is all about in general. Helping. They just need the tools/details from you to help figure it out or at least try to. I am sure if you posted a video detailing the problem with a logcat everywhere would be fine and happy.

Got everything working! Nightlies coming soon