Do u think you could soft key button functions like hold back button to kill app?
That's built into CM
Just go to Developer Options and scroll all the way to the bottom.
[ROM][4.4][noobdev] CM 11.0 with app2sd, glove mode, dual boot for all S4 variants
- Thread starter chenxiaolong
- Start date
That's built into CM
Just go to Developer Options and scroll all the way to the bottom.
That's built into CM
Wow I never saw that! Thanks a lot man
It would be great to have support for the S-View cover
Check out this app, was on the front page a while back. I am using it - http://xdaforums.com/showthread.php?t=2433744
Works ok with glove mode but can be a bit weird in the pocket. I had to turn glove mode off because my leg would activate the screen.
hi chaps im dual booting with omegle roms but i cant get any network connection and camera keeps telling me that it cant connect ill pull some logs i currently have 16/9/2013 installed tried 17/9/2013 as well both same result
camera log http://pastebin.com/ERP3CyqM
network log http://pastebin.com/1suVCYjL when i switch to omegle rom i have full signal
network log 2 when i click choose automatically http://pastebin.com/FsrvcDKv
camera log http://pastebin.com/ERP3CyqM
network log http://pastebin.com/1suVCYjL when i switch to omegle rom i have full signal
network log 2 when i click choose automatically http://pastebin.com/FsrvcDKv
Last edited:
I really love the feature to swype the status bar down when in a fullscreen app. That's really the only thing CM missed compared to TouchWiz haha.
Good thing youve cherry picked it chenxiaolong! Works like a charm so they should really merge this one soon and put it on by default because I cant think of a reason why it should be disabled.
Good thing youve cherry picked it chenxiaolong! Works like a charm so they should really merge this one soon and put it on by default because I cant think of a reason why it should be disabled.
Hmm...are you using a custom kernel? According to the logs, the camera doesn't work because of this line:
Code:
E/mm-camera-intf( 332): mm_camera_open: cannot open control fd of '/dev/video0' (Invalid argument)As far as I know, that could only be caused by a bad kernel or a bad camera firmware.
Unfortunately not because glove mode requires changes to framework. You could theoretically copy the framework from my ROM to the one you use, but it is extremely likely that would cause FCs.
EDIT: If the ROM is open-source, I can help the developer incorporate the patches into his/her ROM.
Thanks!
That's actually one of my favorite features in TouchWiz. I'm really glad someone implemented it in CM
I really hate having to get out of a full screen app just to see the time or notifications.
Hi thanks for reply im not using any custom kernel just stock from ur cm10 its rather strange never come across issues with cm I thought I would provide logs as helps loads also did u notice anythink reguarding the network ????
Sent from my GT-I9505 using Tapatalk 4
Latest update lost all its smoothness.
Stock kernel? Yeah it seems not as snappy as it should be (for such a hardware) but I guess it isn't commit related as there is no special commit (just the one kernel commit but I'm using ktoonsez kernel).
Scrolling is choppy and overall snappiness isn't there. Can't explain why..
Gesendet von meinem GT-I9505 mit Tapatalk 2
Yes very choppy. Stock kernel. Can't believe this. Also charging can't keep up with me using the phone.
No problems here. This is the only commit I could find that got merged last night for our device: http://review.cyanogenmod.org/#/c/50569/
Btw chenxiaolong do you know which blobs cm uses for CM10.2 (by that I mean firmware version)?
I signed into google +. Normally when i do, my profile pic in messaging changes to Google plus one. Now its just blank and When I click my profile account pic in sms it says contact does other exist?
I tried Removing account and adding it again but no luck
Sent from my GT-I9505 using Tapatalk 4
I tried Removing account and adding it again but no luck
Sent from my GT-I9505 using Tapatalk 4
The blobs actually come from all different versions:
ril (jfltexx) - TouchWiz MGA
ril (jfltetmo) - TouchWiz MDL
ril (jflteatt) - TouchWiz MF3
ril (jfltespr) - TouchWiz MF9
ril (jfltecsp) - TouchWiz MFA
ril (jfltevzw) - TouchWiz MF9
Camera binaries (all) - Google Edition MH5
Camera firmware (all) - Google Edition MH5
mpdecision (all) - Google Edition version before MH1?
thermald/thermal-engine (all) - Google Edition MFD?
GPU drivers and libraries - Google Edition MH1 or the version before that
Broadcom wireless card firmware - Google Edition version before MH1
A huge mess, right?
The blobs actually come from all different versions:
ril (jfltexx) - TouchWiz MGA
ril (jfltetmo) - TouchWiz MDL
ril (jflteatt) - TouchWiz MF3
ril (jfltespr) - TouchWiz MF9
ril (jfltecsp) - TouchWiz MFA
ril (jfltevzw) - TouchWiz MF9
Camera binaries (all) - Google Edition MH5
Camera firmware (all) - Google Edition MH5
mpdecision (all) - Google Edition version before MH1?
thermald/thermal-engine (all) - Google Edition MFD?
GPU drivers and libraries - Google Edition MH1 or the version before that
Broadcom wireless card firmware - Google Edition version before MH1
A huge mess, right?
Just as I thought, a huge mess indeed
. They should be more consistant with those blobs (except ril), makes things easier.But I'm kinda bored with Android 4.3 now. I need something new like a Kit Kat flavoured Android
.
Just as I thought, a huge mess indeed
But I'm kinda bored with Android 4.3 now. I need something new like a Kit Kat flavoured Android
+1
Bored as hell with Jelly Bean. Since Ics it all seems the same.. Hope we get more performance and visual improvements with kitkat.
Gesendet von meinem GT-I9505 mit Tapatalk 2
I'm trying to flash this dual booting with Omega v10 and i'm getting a black screen after flashing the zip. I had about 900mb free on the /system partition, is it enough?
I've flashed a patched ktoonsez kernel and now it's loading, but it seems to be stuck on the "Android is upgrading..." screen...
Followed every step from the guide and still nothing...Primary works fine...LED lights up on second ROM and it connects to PC but I get a black screen
I've flashed a patched ktoonsez kernel and now it's loading, but it seems to be stuck on the "Android is upgrading..." screen...
Followed every step from the guide and still nothing...Primary works fine...LED lights up on second ROM and it connects to PC but I get a black screen
Last edited:
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
155Please 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
- Moving apps to SD card
- Facebook sync with native app (with phone numbers!)
- Glove mode / high touch sensitivity
- Delta OTA updates
Instructions:
- Flash CM 11.0 and the gapps below.
- Clear /data and /cache if you are coming from another ROM.
- 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-0229I 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.patch25
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.19To 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.18
