yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] pjkiener:
Hey guys, I'm running dual boot with Wanamlite for my touchwiz ROM, however I wanna switch that with Echoes Slim so I can get the new firmware. How do I do this? TIA!
[Galaxy S 4 i9505 Android Development] dikime:
Wipe primary /data, cache and dalvik cache with the Utilities.zip, then flash Echoe 4.3, then the dualboot-nightly, then dualboot-gapps and u'll be fine.
[Galaxy S 4 i9505 Android Development] pjkiener:
Thanks! Will I lose my current 10.2 settings?
[Galaxy S 4 i9505 Android Development] dikime:
As long as you don't wipe the whole /data partition or /data/dual, it'll be ok.
[Galaxy S 4 i9505 Android Development] Stevemeister:
The problem still occurs now and then. Easiest way to trigger it seems to be after flashing a build.
[Galaxy S 4 i9505 Android Development] WoodburyMan:
No 10/27 builds today either :(

Applying /hd2/android/hudson/roms/cm-10.2/high-touch-sensitivity/0001-Add-preferences-for-high-touch-sensitivity.patch (with git) ...
Applying: Add preferences for high touch sensitivity
error: patch failed: src/com/android/settings/DisplaySettings.java:68
error: src/com/android/settings/DisplaySettings.java: patch does not apply
Patch failed at 0001 Add preferences for high touch sensitivity
[Galaxy S 4 i9505 Android Development] chaoticoz:
Has anyone bot call recording to work on this rom?

Gesendet von meinem SGH-M919 mit Tapatalk
[Galaxy S 4 i9505 Android Development] wmc90:
This app works fine for me: https://play.google.com/store/apps/details?id=com.nll.acr
[Galaxy S 4 i9505 Android Development] chaoticoz:
Trying now. Seems good thanks mate

Gesendet von meinem SGH-M919 mit Tapatalk
[Galaxy S 4 i9505 Android Development] tomurbanowicz:
How to change the setting LED notification of full charged, becouse native setting couse that full notification is at 90%?
[Galaxy S 4 i9505 Android Development] pitastrudl:
try lightmanager

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] tomurbanowicz:
I know that, but I want native.
[Galaxy S 4 i9505 Android Development] WoodburyMan:
FYI EMJ6 baseband works fine with current daily builds of CM.
[Galaxy S 4 i9505 Android Development] pitastrudl:
well I dont see any reason to change it. It's not like you're going to miss out anything on those 10%. If you charge with the samsung charger from a socket it will fill in like an hour or hour and a half. the battery on our S4 will last a long time.
[Galaxy S 4 i9505 Android Development] tomurbanowicz:
FULL is FULL, and no almost full...
[Galaxy S 4 i9505 Android Development] pitastrudl:
As far as i've read, its a feature from aosp so its also in CM and it is supposedly used to lenghten the longetivity of battery life, so people don't overcharge it. Thats why there is a notification at 15% because draining the battery to 0-15 is bad for it over time.
[Galaxy S 4 i9505 Android Development] tomurbanowicz:
I want to change manually, but where to find the strings to change? SystemUI?
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Third day without a nightly? :/

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] pjkiener:
+1 ... I'm surprised.
[Galaxy S 4 i9505 Android Development] pitastrudl:
no idea.
[Galaxy S 4 i9505 Android Development] WoodburyMan:
Yep. Glove mode patch is breaking the builds currently.
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Then why keep the patch?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] WoodburyMan:
Most likely just needs a edit. If I'm reading Jenkins right on why the builds are breaking it's because upstream CM changed something in the Settings>Display menu. It's a matter of just updating it quick or disabling the patch, but I assume OP is currently flooded with homework and classes. If you aren't using dual boot you can actually flash official Cm nightlies no problem and switch back when new builds are available.
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
I'm on carbon rom now as it has all the cm changes and other stuff like transparent status bar and floating window and other things.. But I go back to this rom.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] ninjazin:
Maybe this could be implemented in order to get the transparent status bar? http://xdaforums.com/showthread.php?t=2364184
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Oh crap I didn't notice the builds are failing. I'll definitely fix that before tonight's build.
[Galaxy S 4 i9505 Android Development] chenxiaolong:
That's for the signed user builds only :)
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Oh :(. 50% transparency is so great...

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Haha, I was trying to prove/derive the centrifugal and coriolis fictitious forces to prepare for a presentation in my physics class. (Still can't do it lol)
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Huh? That patch is about fixing broken JNI libraries
[Galaxy S 4 i9505 Android Development] ninjazin:
You could install xposed framework + gravitybox module for the transparency. I just did and it works great.
[Galaxy S 4 i9505 Android Development] pitastrudl:
last time i tried gravitybox i got continuous systemui FC

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] yashar013:
Hi, i have wanamlite ad primary ROM and this one as secondary. How can i share the same installed apps between these two roms? Thanks in advance.

Inviato dal mio GT-I9505 usando Tapatalk 4
[Galaxy S 4 i9505 Android Development] dikime:
Use Titanium Backup since both have root. Just point the app manually to the same folder twice.
[Galaxy S 4 i9505 Android Development] swavab:
Whether work with I9500?

s4 the legend..!!
[Galaxy S 4 i9505 Android Development] yashar013:
But do they take double the space?

Inviato dal mio GT-I9505 usando Tapatalk 4
[Galaxy S 4 i9505 Android Development] pitastrudl:
lol, latest nightly 29.10 made my recovery go fruity xD

i can still use it normaly though. there was a commit named "clean all the things" on android_bootable_recovery.

OK, nevermind, reflashed recovery after i booted the phone and flashed the recovery again, dont know if a reboot fixed that or the reflash did lol
[Galaxy S 4 i9505 Android Development] AndroidUser00110001:
[MENTION=4277844]chenxiaolong[/MENTION]

When I had my S4 I used your ROM since the start. I currently switched over to the LG G2 AT&T model (d800). I was wondering if you can build your CM based ROM for it with IR support or would you share the IR code if it will work on G2 so I can build a similar ROM as yours. Also can we try to port over the dual boot too. I will help out in anyway I can.

Thanks so much!
[Galaxy S 4 i9505 Android Development] chenxiaolong:
lol what kind of bug would make Python 2 crash in such a spectacular way?

http://jenkins.cxl.epac.to/job/Android/797/console

EDIT: Tonight's first build will be the 800th build of this ROM :)
[Galaxy S 4 i9505 Android Development] Stevemeister:
Thats the special easter egg lol! Not a broken recovery :cyclops:
[Galaxy S 4 i9505 Android Development] pitastrudl:
not sure if i would take that post serious
[Galaxy S 4 i9505 Android Development] chenxiaolong:
He's right :) It is a feature: https://github.com/CyanogenMod/andr...mmit/af5f065b1f94a43bdd1a586127443e298459783b
[Galaxy S 4 i9505 Android Development] Stevemeister:
I wonder how to trigger it though. Any idea [MENTION=4277844]chenxiaolong[/MENTION]?
[Galaxy S 4 i9505 Android Development] dikime:
Lol swipe to reveal statusbar might be the toughest thing to do in CM. :D

After briefly appearing, then going away for several weeks, now the feature is up again... but works only on a clean install. Slap a few apps, change the kernel and suddenly it only detects one out of every 15 or so attempts to trigger it.

Maybe I'm just holding it wrong :)
[Galaxy S 4 i9505 Android Development] davidep85:
[MENTION=4277844]chenxiaolong[/MENTION] is that possibile to add support for S-View Cover like in GE roms??
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Soon there'll be cm11

Hope very soon...

Google release kitkat sources...

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
[MENTION=4277844]chenxiaolong[/MENTION]

KitKat Android 4.4.1 sources being pushed to aosp right now!!!

Who wants to build a kitkat rom? :)

http://www.androidpolice.com/2013/10/31/android-4-4-source-is-being-pushed-to-aosp-right-now/

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] tomurbanowicz:
Don't You any problem with RingtonePlayer wakelock in SystemUI?

my logcat:

https://db.tt/uGFknsx6
[Galaxy S 4 i9505 Android Development] Braulio00:
This ROM can be installed with new bootloader knox?
[Galaxy S 4 i9505 Android Development] chenxiaolong:
http://jenkins.cxl.epac.to/job/Android_ZOMG_I_WANT_KITKAT_NOW/ :D

The build server will try to make a CM 11 build every six hours. Let's hope CM merges Android 4.4 soon!
[Galaxy S 4 i9505 Android Development] WoodburyMan:
LOL. Love the project name.

CM said they'll be pushing it in the coming week to their sources once Google finishes pushing it.

Also odd question, anyone else having odd issues. Every since I tried Goldeneye 9.1 (Samsung-based Android 4.3 firmware) and it updated my Camera firmware, I've been getting hard lock up and reboots whenever I record in 1080p on Camera. 720p is fine. Anywhere from 4 to 14 seconds into a video, and only about 50% of the time. Does it when source is set to Internal and my microSD. I haven't tried it with today's build quite yet... saw they changed some things with with camera blobs for today in changelog.

**EDIT** Yep still happens.

The CM Camera app really sucks... nothing with the rom just I've been getting very frustrated with it lately FC'ing and "Can't connect to Camera" issues.... And Focal has never worked right for me, even the one from Play..
[Galaxy S 4 i9505 Android Development] Stevemeister:
Well seems like we will be getting 4.4 stable in November since the Play Editions will be updated in November.

Hopefully Google didnt change too much and CM can easily port their extra features.
[Galaxy S 4 i9505 Android Development] WoodburyMan:
Hopefully they push it soon! Usually they'll do all Nexus devices first.. so Nexus 4, 7, 2013 7, 10, 2013 10 and such first, then the One and our S4. And our S4 will probally be last. The GE rom's don't come from Google... Samsung still has to push them, although they do it much quicker than they do normal roms.. hence they 4.3 is just coming out now, meanwhile AOSP has 4.4...
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Hmm, OmniROM, SlimBean, and AOKP are already merging Kit Kat. Looks like Time Warner Cable is going to have to deal with 50 GB of source code downloading tonight :)

EDIT: OmniROM first, the other two only created branches but haven't merged anything.
[Galaxy S 4 i9505 Android Development] WoodburyMan:
https://plus.google.com/117962666888533781522/posts/HpXkXU98R7q

They didn't merge over 4.3 I think till almost a week after 4.3 was pushed to AOSP as I remember. First 4.3 / 10.2 builds for S4 that didnt quite work right took about a week and a half to two weeks from AOSP push.
[Galaxy S 4 i9505 Android Development] gaww:
I just tried to flash 10.01.2013 modified duel boot TMo variant CM10.2 and it would not boot up - tried twice.

I then flashed a duel boot ROM from about a week ago and it came up with no problems (used same GAPPs) ??

Update - after fooling around some more, it looks like the nice smooth path of updating these ROMs with and without kernels like KT AOSP has become a very bumpy road. The newer patched ROMs after several identical tries sometimes flash - other time will not boot. The KT kernels which were pretty much in synch datewise with thees ROMs no longer are - cannot get KT 10-25 AOSP to flash and boot with any of the latest ROMs here.

For now back to mid-Oct ROM and KT AOSP kernel - working fine. I got to use the primary/secondary recovery tool - worked real good.

Maybe after new duel boot and kernel versions settle down it will again become an easy update path - sure hope so.
[Galaxy S 4 i9505 Android Development] dikime:
Hm.. I did some non-developer research on the "broken" statusbar swiping.

First of all, it works flawlessly on the 9/14 nightly.

Then CM source started changing and breaking the feature multiple times.

Now in the newest nightlies the swipe to reveal statusbar is here again, however... it's semi-broken. Here's what I found:

- it works 70% of the times a swipe gesture is performed ( = needs 2 swipes to activate sometimes).

- after restoring stuff to the phone, the feature "breaks" and detects less than 1 in 15-20 swipes.

- if a second quick swipe is made after a successful one, it also activates the feature.

- on TouchWiz, the gesture never fails.

I used a very good gesture-based app (GMD Gesturecontrol) to set-up a gesture to reveal the Notifications Panel.

- on touchwiz it works 100% of the times the gesture is performed

- on CM it never works.

- if set as to mimic the system gesture (1 finger swipe from top) - it boosts the success rate to 20%

- uninstalling GMD gesturecontrol has a "boost" effect, but only temporarily

- top swiping has around 50% success rate, side swiping (as when in landscape) has almost zero success (counted 50 swipes before activating)

From my observations and my inability to read source code :D here are my conclusions:

- there is something that detects the gesture

- upon detecting a gesture, it "activates" the statusbar, making it available for display in fullscreen. This activated mode stays on for a second or two. Hence the 2nd quick swipe activating the statusbar again

- the process of activation gets broken, because gesture detection obviously works fine.

- GMD has some interference, but it's not the only thing messing up, since it doesn't return the "clean install" state upon being removed.

- landscape swiping is horrible, maybe the border is set as a precentage of height and gets stretched to undetectably tiny size, because that percentage is intended for portrait.

- TouchWiz is in always-"activated" mode, since GMD is able to trigger the statusbar

Hope this was even remotely useful. :)
[Galaxy S 4 i9505 Android Development] WoodburyMan:
Some patch for something from Omnirom caused todays builds to fail

omni/1122/PS2_0001-2-2-Settings-Add-lockscreen-ring-battery-setting.patch to be specific.. :p
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Thanks! It looks like this commit broke it: https://github.com/CyanogenMod/andr...mmit/b7d39529c17894e66b692504f5f43170ad1efd58
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Finally finished deriving the coriolis and centrifugal force equations :) Now, to fix the build...
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Waiting for kitkat builds lol ;p

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] Nasty_z:
Haha lol. Eagerly waiting here too :p

Btw, if I may ask, how is the build coming around? I mean, I've read around that the aosp sources are proving to be quite useful for the I9505. This is because the nexus 5 uses similar hardware. Is this true?
[Galaxy S 4 i9505 Android Development] chenxiaolong:
It really helped that the Nexus 5 is also a Qualcomm device, but the galaxy s4 is different enough to require quite a few changes to even boot. I didn't try pure aosp, but when I was building Slimbean and OmniROM yesterday, I was mostly fighting typos in the source code and some missing (ie. available but not yet merged) Qualcomm code. I got most of that fixed but the end result was... well... all the proprietary blobs crashed :D I'm going to try again after a couple days. Hopefully some of these early issues will be resolved by then.
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
THANKS! :)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] celtichazard:
how to make my ir blaster work i have CM 10.2 M1
[Galaxy S 4 i9505 Android Development] chaoticoz:
Install Samsung watchon it works fine for me.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Word of advice: NEVER try to compile Kit Kat on a laptop sitting in your lap.
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Why? :p

Omg I can't wait..

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Because my pants are going to catch on fire :p

SlimROM just made some commits related to qualcomm code that was failing earlier, so I'm trying to build again :)
[Galaxy S 4 i9505 Android Development] Nasty_z:
Haha. Good to see you dedicated.

What's your build setup like? How long does it take you to compile cyanogenmod?
[Galaxy S 4 i9505 Android Development] chenxiaolong:
:D

My nightlies are built on a slow server in the basement, but I do all the work on my laptop. If I don't pull in new code (ie. rebuilding to fix features), CM takes 6 minutes to compile. Otherwise, it takes about 15 minutes. The initial build before all the caches are filled is about 45 minutes.

(Multiply by 4 for the excruciatingly slow compile times on the server :D)
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
I thought so ;)

Yeah great! Hope you get it to boot!

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] Nasty_z:
6 and 15 minutes? Your laptop must be core i7 or i5. I get similar times as your old server :p about 2hrs 45 minutes per cm initial build.
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Yeah, I have the i7-2720QM, but I think having an SSD and a ton of RAM is more helpful :) I used to build on a spinning disk and I found that after the first build, it spent most of the build time reading cached files. Actually, I think Google recommends 24 GB + of RAM so the entire cache can be stored in it.
[Galaxy S 4 i9505 Android Development] Nasty_z:
Having that much ram, you can actually build cm inside the ram memory. That's gonna build it very quickly due to the amount of small files that are higher in quantity. May I know how much ram you have and I assume you're using an ssd. If so, which ssd?
[Galaxy S 4 i9505 Android Development] chenxiaolong:
That's exactly why I wish I had that much :) I actually have only 8 GB of RAM (the model is F3-10666CL9-4GBSQ) and I have the 128 GB Samsung 830 SSD.
[Galaxy S 4 i9505 Android Development] Nasty_z:
You and me both brother. :D

Number of cores affects the compilation greatly. Because the jobs get spread over the number of cores or so I've heard.. You've got a quad core i7. You've told me the results. It seems that the more cores = quicker compile has some truth to it. Anyway, I'll try not to clutter the thread. Thanks for the info :)

Just one last thing, what are your thoughts on ccache?
[Galaxy S 4 i9505 Android Development] chenxiaolong:
ccache is the best thing ever! Seriously ;) I'm currently using ccache version 2 that's bundled with the Android source code, but I've been experimenting with ccache v3, which can be set up so that the cache for one target device can be used for another. This is super useful for nightlies, since my jfltetmo cache can be used for jfltexx, jflteatt, etc so the code isn't built 8 times and the cache isn't 8 times bigger than what it needs to be.

I'm trying to figure out how use distcc too. That lets you use multiple networked machines to help with the compiling. The other machines don't even need to have the source code, just a suitable compiler :)
[Galaxy S 4 i9505 Android Development] Nasty_z:
Wow. I didn't realise ccache was such a big deal. I'm a novice when it comes to compiling but I am very interested in cooking up roms and generally fiddling around in Android. Though I have limited hardware, I do try to make the most of it. I'll try looking up ccache more, including ccache 3. Distcc sounds interesting although it doesn't apply to my situation :p

Ccache would only be useful in situations where the initial build had been completed, yeah? If so, what if I run a repo sync and the device tree is updated with changes and I want to rebuild cm, is ccache able to speed things up here too?
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Yeah, ccache does slow down the first build a lot, but the case you mentioned (repo sync) is exactly where ccache helps :p
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Looks like the swipe-to-reveal status bar feature is now in Kit Kat: http://www.androidpolice.com/2013/1...accessible-notifications-in-full-screen-apps/
[Galaxy S 4 i9505 Android Development] chenxiaolong:
CM 11.0 Kit Kat branch has been created! These are the repos you want to constantly press F5 on:

https://github.com/CyanogenMod/android_hardware_qcom_audio-caf

https://github.com/CyanogenMod/android_hardware_qcom_media-caf

That Qualcomm stuff is what's preventing us from having Kit Kat right now.
[Galaxy S 4 i9505 Android Development] WoodburyMan:
YAY!

Soooon.....

Also todays 10.2 just failed again :(. Dual boot patch this time.

And if we're talking CPU's

i7 4770K OC'd 3.9ghz. 16gb DDR3 2133 XMP. 2x240gb SanDisk SSD's in Raid0 almost 800mb/s read, 600mb/s+ write :D. Two GTX570's in SLI as well.. but that doesn't help compliling :P. (only with BF4 and COD:Ghost releases this week...)

My only thing is its on Intel ICH. Which uses "fake raid". Linux doesn't like that... so i cant dual boot onto the SSD.... some day ill buy a cheap 128gb for dual booting and throw ubuntu on it to try compiling again. I did some in VM's but not the same as native...

My laptops got a i7-3630QM though and 16gb ram, with a 256ssd. that would work nicely i suppose..
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Fixed and rebuilding now :D Hopefully, no other patches cause issues.

That machine would absolutely fly for compiling Android! Oh and speaking Intel's fake raid...well...I got Linux to work with that once...and *1* is exact the number of times the computer will boot after it's set up...
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Yeahhhh great! So what do we need to get these to work?

Edit: when do you expect a buildable cm11 build?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] chenxiaolong:
The real devs just need to update that Qualcomm code. I can figure out the rest :)
[Galaxy S 4 i9505 Android Development] WoodburyMan:
Ha! Yep. I did that once way back in the day when I had a FX-60 with a nForce4 chipset on nVidia's fake raid. Same thing. One boot then done. Screwed up the partition info and stuff completely. I swear after that Id never do RAID0 again. My next setup i had for 4 years was a 600gb raptor single drive. Then I went to SSD. Was going to do a single 480 or 512, but then the 240gb's i had now came up on sale so i had to get them...

Also I see you playing with the builds still lol. This time omnirom battery circle mod or something. I see those builds stopped and redoing again now :cool::p
[Galaxy S 4 i9505 Android Development] Justindail311:
Chen you're awesome and great work on this ROM so far been running it a few months now on my VZW s4 since I found it accidentally trying to figure out an ir patch. Can't wait to see what you do with kit kat.
[Galaxy S 4 i9505 Android Development] Stevemeister:
Yeah it is and it works great. Bought a Nexus 5 yesterday, great device! Bye bye ghosting/purple smearing and waiting for updates.

It really feels much faster than my S4 on AOSP.
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Perhaps placebo but wifi reception got worse with nightly 5.11.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] WoodburyMan:
Fine for me. I don't see anything that would have changed WiFi in the last few days of changelogs....

Also https://plus.google.com/117962666888533781522/posts/gFjZS7NcTNr
[Galaxy S 4 i9505 Android Development] kbello:
I have a question: I like when touch the screen phone, buttons (menu and back) do not light, like TW roms, how to have the same behavior in this rom??

Thanks and sorry for my bad english.