yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] nokia-xxx:
I already had CM4.3 on my S2, but now also on my S4 and I love this platform!

Thanks for the continious hard work guys!
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
Indeed, messaging app looks dated, overall smoothness could still be better, multicore usage should be better, maybe an other way of multitasking, a new launcher maybe and I really need the option to swype down the notification bar when in a full screen app (like touchwiz).

But that's just a small wish list, I could easily add 100 more features for stock Android. But that's why we on Cyanogenmod ;).
[Galaxy S 4 i9505 Original Android Development] Neuron:
Plus gmail sync with full-res apps, not as it's done now
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Yeah gmail needs serious redesign/performance bumps. Also maps needs to be smoother and with the options the old maps had. Calendar is too basic, the Launcher should be smoother, new transition animations (the jelly bean ones are sooo laggy on EVERY phone).....

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] carmo2y:
cwm works

I tried with phil's cwm and it doesn't work (no baseband, no cyanogem boot logo). Flashed with CWM 6.0.3.6 and worked flawlessly.

I had to create .tar.md5 from .img ( downloaded from here http://www.clockworkmod.com/rommanager) with this tool:

[Tool][[windows] Make CWM Recovery .img's into .tar.md5 odin flash-able files 1 CLICK
[Galaxy S 4 i9505 Original Android Development] Hippoman13:
The latest nightly (9/7) wont boot. Clean installed/multiple kernels including stock tested. On CWM 6.0.3.6
[Galaxy S 4 i9505 Original Android Development] Fruktsallad:
I think you missed a few words here. Does it work or not?
[Galaxy S 4 i9505 Original Android Development] Hippoman13:
My bad, I typed incorrectly for some odd reason. It doesn't work. I am going to try 9/08 now, as it came out a few minutes ago.

Edit: Thankfully, 9/08 works fine. I cannot seem to locate the source of the problem for 9/07's build.
[Galaxy S 4 i9505 Original Android Development] marian3k:
Where is 9/08, can't find it on CM website?
[Galaxy S 4 i9505 Original Android Development] Hippoman13:
Download it on your phone under settings->CM updates. You can install it manually.
[Galaxy S 4 i9505 Original Android Development] marian3k:
Yep, obvious thing to do but it's not there yet...
[Galaxy S 4 i9505 Original Android Development] Hippoman13:
Odd... Give it half an hour.
[Galaxy S 4 i9505 Original Android Development] marian3k:
Will do, thanks.
[Galaxy S 4 i9505 Original Android Development] eak1080:
Guys it's been there for a hour
[Galaxy S 4 i9505 Original Android Development] edwardtobia:
Its not there for me either, tried the updater and also the web link, both show no update for today as of yet...
[Galaxy S 4 i9505 Original Android Development] islipfd19:
It's not finished being built yet. It only just started a little while ago.
[Galaxy S 4 i9505 Original Android Development] tapiov:
Check the last posts signatures: one of them is not I9505.. Different builds
[Galaxy S 4 i9505 Original Android Development] I9000bramgmail:
is it just me or does 10.2 (05-09-2013) consume considerable more then 10.1? I used to charge my phone after 3 days with light use(almost always on wi-fi, at night flight mode, and during the day just whatsapping, checking the news etc. no gaming.) now doing the same with the same apps i get a day and a half max...

I did the following to improve battery life:

-used autostarts to disable the startup of many applications that i dont regurarly use

-turned of the google location reporting and logging stuff

-have my screen brightness to auto with adjusted levels (I adjusted it to darker)

BetterBatterystats doesn't seem to find any problems,, the widget indicates a good ratio between awake and screen on.. (for example when 39m awake and then the screen on time is 36m)

any ideas?
[Galaxy S 4 i9505 Original Android Development] islipfd19:
Today's nightly finally finished being built, 20130908; just flashed it and can confirm that it boots.
[Galaxy S 4 i9505 Original Android Development] Milamber:
Just use cyandelta for updates will save you downloading the whole rom each night...
[Galaxy S 4 i9505 Original Android Development] marian3k:
I got it through CM updater and it boots and works ok so far. After two days of broken builds I really needed to update. Nightly updates are spoiling me!

Flashoholic
[Galaxy S 4 i9505 Original Android Development] om22:
still no focal exposure ring in todays nightly:( would be a really cool feature.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Focal is bad... They should reveal nemesis phase 2...

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] KOP1230:
no videocapture in last nightly
[Galaxy S 4 i9505 Original Android Development] I9000bramgmail:
videocapture works fine for me on the nightly of today,, battery drain is still high for me though ):
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
anyone having status 7 error in recovery, its the getprop lines that do the thing

in updater script it looks like this

" assert(getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" ||

getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" ||

getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" ||

getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "jgedlte" ||

getprop("ro.product.device") == "i9505g" || getprop("ro.build.product") == "i9505g" ||

getprop("ro.product.device") == "GT-I9505G" || getprop("ro.build.product") == "GT-I9505G")"

but it should look like this

assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" ||

getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" ||

getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" ||

getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505");

so i edited it and uploaded todays nightly here

redownload :https://mega.co.nz/#!a9BgQKwR!QB9RBU9uljyXsIVb3HizDROwexFLkBAl74gCzZNFHb0
[Galaxy S 4 i9505 Original Android Development] aldreiaan:
Im using cm10.1 latest RC and I cant seem to make pie controls work, I followed the steps in post #2. Can someone help me with this?
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
Is today build safe to flash?
[Galaxy S 4 i9505 Original Android Development] felek73:
Yes , no problem with flashing today nightly
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Yes.

Gesendet von meinem GT-I9505 mit Tapatalk 2

---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------

Hope Android 4.4 will change some things.. Jelly Bean is so boring.. Been too long. But better than iOS lol. Been the same since forever..

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
What exactly videocapture?
[Galaxy S 4 i9505 Original Android Development] nokia-xxx:
Do you guys know the app Automaton? The functonality is great and would be a perfect addition in CM if you'd ask me.

Automaton locks the phone and disables the screen when my flip cover closes and enables the screen when I open the cover again....such a simpel thing, but what a fantastic addition.
[Galaxy S 4 i9505 Original Android Development] I9000bramgmail:
open camera app, switch to videocapture and capture a video,, It works just fine for me, but apperantly not for everyone..
[Galaxy S 4 i9505 Original Android Development] nokia-xxx:
+1 works fine here....coming from a Fresh installed CM v05/09 - v08/09
[Galaxy S 4 i9505 Original Android Development] idriline:
I've try the 12/06 build and need to flash 4 times for had an install quiet good (3 times errors 7 but seems to be normal)

No specific bug detected on main functions common use.

The only thing i've detected it's about the carrier name, it s doesn't show up by name but ID name (from database about carrier on the rom i think).

about the update directly from the rom, i think it's normal a this stage of developement that really not possible, cauz the base on the rom source code is not freeze (freeze on the way, the base of the rom is not complete and may change completly from build to other.

And specially from nightly source and milestone it's better to flash build to build from recovery ...

when the rom was going on RC or Stable release the updater from the rom should be working correctly without any fix on it. just cauz the base code of the rom will be freeze and stable.

About the issues with bluethooth it'sreally difficult to fix an bluethooth device cauz they are not really standard for this technologie

retro compatibilitie is not always working with all devices and some manufacturer use proper signal or transfert protocol

also i've already seen on one stable build BT working perfectly with an headset, update the phone ... and the same headset doesnt work anymore on BT . same issue may can be provide with car kit incorporated on the car... some times need to update the firmware of BT device for keep or become compatible with the os device. Had the driver of BT chipset on the firmware of the phone is one thing , the management of this chipset by the operating system is other. Bt has some standards right it's true, but not really strict in compare with the wifi for exemple.

one thing also possible but i know it's not on the mentality of android in general, but some trademark with an update os, may reduce the compatibility of accessory of the same brand (just for obligate people to purchase new model of accessory)

most of the time BT issue or not working it's due to a software issue on the side the operating system, not about the firmware of chipset (that s may be the case if the driver use on the firmware is a white common driver. Driver manufacturer may can contain more code, than a common driver, specific transfert protol used by manufacturer for exemple, or specific range to use the BT etc etc.

touchwiz for exemple is a specific code from samsung , and we need to porting it on cyanogen code if we want to expect touchwiz on CM (it's just an exemple) Ir fonction on the phone not present on CM ... it's not a bug it's normal cauz the code is also provided and developed by samsung and to be ported also if we want it on Cyanogenmod.

it's just a personnal minding, hope can be constructive for et accomplishment of a pure crazy rom as called Cm :p
[Galaxy S 4 i9505 Original Android Development] Greg1964:
Can this rom be ran on the tmobile Gs4
[Galaxy S 4 i9505 Original Android Development] ARieS_:
T-Mobile already has own builds. You can find here. http://wiki.cyanogenmod.org/w/Jfltetmo_Info and http://get.cm/?device=jfltetmo
[Galaxy S 4 i9505 Original Android Development] overon37:
great room but...

when i want to open any app, any, is the same, needs more time than stock rom.

So, without samsung launcher and all apps from them and.... needs more time to open and app?,

this rom is really good, but need time... i gonna back to stock rom

thx for all
[Galaxy S 4 i9505 Original Android Development] CarlDeanCatabay:
Issue(s) with cm-10.1-20130612-NIGHTLY

Issue(s) I noticed with this build: cm-10.1-20130612-NIGHTLY-jfltexx

1. Phone gets stuck on boot logo when selecting power menu > reboot > reboot device given that your phone is connected to a computer and USB debugging is enabled prior to rebooting the device.

To get out of boot logo:

-Remove USB cable (if connected) from PC

-Manually power-off the device and let it sit there for a couple of seconds

-Manually power-on the device and your phone should boot fine

EDIT:

Enabling Advanced Boot Menu in Settings > Developer Options causes the issue.

2. Settings force closes when rebooting device via root app (XposedFramework for example)

Everything is good as expected. Smooth and stable as daily driver specially if you tweak the configs in developer and performance options.
[Galaxy S 4 i9505 Original Android Development] MarciWoi:
Is there a 100% chance to flash this rom without error 7?

Everytime it doesn´t work for me and I don´t wannt to stuck on TW :crying:
[Galaxy S 4 i9505 Original Android Development] CostaTX:
Use CWM from their official site. seems to be working pretty decent in comparison to other recoveries out there.
[Galaxy S 4 i9505 Original Android Development] MarciWoi:
This one recovery-clockwork-touch-6.0.3.2-jfltexx :confused:
[Galaxy S 4 i9505 Original Android Development] emx_o:
no. best working is the latest philz CWM.

remove the format line from updater script gives you a 100% chance of a successful flash.
[Galaxy S 4 i9505 Original Android Development] wessel596:
New nightly is up! Downloading now will report in 10 min or so

Verstuurd van mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] thisisfraa:
Also downloading, gonna try it out later
[Galaxy S 4 i9505 Original Android Development] I9000bramgmail:
Yes, it supports ext3/4 although I would go for ext4 over ext3 anyday, it's just faster :)
[Galaxy S 4 i9505 Original Android Development] wessel596:
Just flashed the new nightly same error as always. A lot smoother as far as i can tell.

Verstuurd van mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] thisisfraa:
I just flashed the new build and it works, sort of. I'm having issues with certain apps crashing or not opening at all after I flash a new build. I had the same issue with the previous build, I fixed it by wiping the device clean, flashing the build and restoring only the apps themselves (without data) with Titanium Backup. Play store is one of them for example, it just closes immediately when it tries to open.

Am I doing something wrong? I restored back to the build of june 12 because of this, if someone has a fix for this, that would be great!
[Galaxy S 4 i9505 Original Android Development] Lazy79:
i cant sent hangouts with the new build lol and the mobile network settings.. whats EvDo? and why only LTE/CDMA? (I google EvDo.. it seems to always jump back to it)

ok found EvDo.. already imagined something like this. Mh.
[Galaxy S 4 i9505 Original Android Development] ginux_:
Have you reflashed gapps.zip after update? They need to be flashed each time, otherwise you get problems like the one you described.

I am running the new update and it seems to be working fine. Just formatted /System and Wiped cache before upgrading from 2013.06.10 so all my apps and settings remained intact :victory:

EDIT: I used Philz Recovery and had to play around with format, wipe and reboot before I could flash without Status 7.
[Galaxy S 4 i9505 Original Android Development] thisisfraa:
Oh I didn't know that, that's probably why it won't open. I'll try it again like you described, thanks for the tip!
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
Fix for the error in recovery:

1.Downlaod nightly

2.unzip the zip

3.open the updater-script file with notepad++!!

REMOVE ONLY THIS LINE: format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");

4.Save and repack the rom in zip file format!

5.put on sdcard and flash

the only bug im getting is a systemUI FC when i click the date in the statusbar
[Galaxy S 4 i9505 Original Android Development] cazxstan:
Flashed this about an hour ago on my i9505 (Telstra). Runs fine with no FCs.

Rom seems much smoother and more responsive than the previous build. Still having to flash gapps as well as the new ROM, and still getting status 7 error when trying to flash ROM, took 3 goes this time round to install the update. I've noticed a bit of lag in the camera app when changing orientation.
[Galaxy S 4 i9505 Original Android Development] beasty:
It is clearly too raw. I am not a fan of Samsung stock firmware but was literally forced to go back. Flashed Omega 5, removed bloatware and it smooth, stable, all hw features there. But most importantly battery life improved a lot. Will stay on stock until Google releases its firmware for i9505.
[Galaxy S 4 i9505 Original Android Development] Hippoman13:
I've also fresh installed from 05 to 08, and video capture does not work for me.
[Galaxy S 4 i9505 Original Android Development] Milamber:
Same video capture is stuffed, I also came from 05 to 08.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
I came from 05 to 08, too and video recording is working fine. Do you use 1080p or 720p? Because I'm on 720p as my phone hang up on 1080p for me since awhile

L
[Galaxy S 4 i9505 Original Android Development] gtizon:
Hi I installed the latest ROM. (4.3) however I got no signal and data. I came from a Samsung ROM. Full wipe. Tried re installing but no signal still. Any help please?
[Galaxy S 4 i9505 Original Android Development] Fruktsallad:
Use original CWM instead of Philz recovery. Search the thread for more info.
[Galaxy S 4 i9505 Original Android Development] Milamber:
Ahhh!!! it's 1080P thats rooted, 720P is fine! Kudo's to you sire!

---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------

Use this buddy, I uploaded the CM to use for i9505, flash it with current recovery.

http://xdaforums.com/showpost.php?p=45310243&postcount=2669
[Galaxy S 4 i9505 Original Android Development] gtizon:
Ill try this. Will report back. :)
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
[MENTION=2682982]noobnl[/MENTION] [MENTION=2385005]invisiblek[/MENTION]

I got two random reboots since I've flashed CM10.2 again last night on my brand new S4 (my old one got trashed so I got a new one from my insurance).

I've grabbed some logs. Maybe there is something usefull in there.
[Galaxy S 4 i9505 Original Android Development] Swizzy88:
Just noticed a weird issue with the september 5th nightly. whenever i use headphones I cant play music anymore. It works through the normal loudspeakers but then stops as soon as I plug in my headphones and music players start crashing, be it apollo or rocket player. Never had this issue before and can't figure out whats going on. Tried reinstalling, clearing cache etc...

Also the homebutton stops working?

E/09:43:06.904 AudioStreamOutALSA( 293)

pcm_write returned error -9, trying to recover

E/09:43:06.904 alsa_pcm( 293)

cannot prepare channel: errno =-9

E/09:43:06.904 ALSADevice( 293)

open: Failed to initialize ALSA device 'hw:0,0'

E/09:43:06.904 alsa_pcm( 293)

cannot open device '/dev/snd/pcmC0D0p', errno 22

D/09:43:06.904 ALSADevice( 293)

Device value returned is hw:0,0

D/09:43:06.904 ALSADevice( 293)

open: handle 0xb8d9c180, format 0x2

D/09:43:06.904 ALSADevice( 293)

close: handle 0xb8d9c180 h 0x0

Got that from the logs. It's repeated endlessly...
[Galaxy S 4 i9505 Original Android Development] BillGoss:
Sound is fine (except for DSP) on 0908.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] demolientje:
So, I would like to install CM10.2 on my S4. I installed it and after the samsung logo the screen goes black. I've searched the thread about this problem and found out that's a corrupted nightlies problem? The strange thing is a lot of you guys say it's only happening with some of the nightlies, for example the 08th of september nightly. The strange thing is that I also ran into this problem with nightlies before the 8th of september one, also for example the 2nd of september nightly, which isn't mentioned anywhere for being a corrupted nightly. Now I'm using Philz recovery, and I want to try the original CWM recovery now, but I'm facing a problem here also. Every time I download the recovery that should work (the one from the begin post), my laptop says the file is corrupted and that it can not be opened. So as long as I can't install CWM, I can't install CM properly. Maybe you guys could help me out?
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
Use official CMW recovery and don't use the 6th or 7th of september builds.

Download SGS4 flasher from the market and download this recovery :http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.6-jfltexx.img. Flash the recovery via the app and after that flash the latest CM10.2 from here: http://get.cm/?device=jfltexx

Problem solved. (btw it is possible you get stuck on the splashscreen the first time but just hold to power button untill it resets and your good to go).
[Galaxy S 4 i9505 Original Android Development] demolientje:
Thanks for the reply! (: going to try this method, hope this will work!

EDIT: It works now, thanks alot!
[Galaxy S 4 i9505 Original Android Development] okgnew:
random reboots

I get a lot of random reboots when device sleeps (or going into sleep mode).

Log is attached.
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
I'm getting them when my device is going into sleep.
[Galaxy S 4 i9505 Original Android Development] eak1080:
+1 will attach a lastkmsg next time it happens
[Galaxy S 4 i9505 Original Android Development] kewinh0727:
could i do this... from stock rom

1. flash CF-auto root in odin

2. use sgs4 flasher to flash the official CWM 3.0.3.6.img or should i use the recomended cwm on this thread OP? (can i use sgs4 flasher in stock rom?)!!?!?!?!

[when i flashed a zip version of official CWM that someone made on xda i wasn't able to flash cm10.1 since it aborted it 7 error]

[so i flashed philz kernel in odin and then i was able to flash :) ]

3. install cm10.1 and flash latest gapps...

4. reboot

or which recovery do you recommend

also if i switch between recoveries will there be leftovers and stuff like that that will screw up other recoveries ?

since there is no brickbug, well i have seen some people say that there is not emmc bugg o something like that not much can go wrong right?
[Galaxy S 4 i9505 Original Android Development] NZgeek:
Which kernel are you using? The one that comes with CM, or a custom one? If custom, try using the standard CM kernel and see if it makes a difference.

(Sorry if the kernel is listed in your signature - sigs don't show in the mobile XDA app.)
[Galaxy S 4 i9505 Original Android Development] okgnew:
I'm using standard CM kernel
[Galaxy S 4 i9505 Original Android Development] kewinh0727:
when i had philz kernel and that recovery when i flashed cm 10.1 it didnt replace philz recovery with the cm recovery why :eek: ?
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
You know that it's kinda forbidden to mention bugs here with a non stock CM kernel right? So no I always use stock CM kernel.

I went back to the 5 september build but I got a random reboot on that build too so I'm trying 4 september now.

Because it's not meant to flash a recovery. It's just the ROM that get's flashed, the rest is up to you.
[Galaxy S 4 i9505 Original Android Development] kewinh0727:
soo how do i flash CM recovery :D ? cus i would like to use that :)

and where can i get my hands on CM recovery :) ?
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
Previous page, second reply.
[Galaxy S 4 i9505 Original Android Development] kewinh0727:
oh thnx hehe xD
[Galaxy S 4 i9505 Original Android Development] spocky12:
I also have random reboots since I flashed 02 September. Last nightly I had (august 26) was perfectly fine. Stock cm kernel of course. I'll try to get last kmsg next time it happens.
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
I'm tracking down the first build that got the random reboots so the dev can sort out which commit is causing it.
[Galaxy S 4 i9505 Original Android Development] PLUG313:
my network mode keeps changing itself back to WCDMA preferred instead of staying global

so I don't get any single most of the time

anyone else? is there a fix?
[Galaxy S 4 i9505 Original Android Development] eak1080:
I did a full wipe and clean flash with 9/8 build and so far i have had no reboots...it has only been 36+ hours though...

Just throwing this out as an idea for others to try a clean install.
[Galaxy S 4 i9505 Original Android Development] Milamber:
I've never had a reboot, I came from completely unrooting and reverting my ROM to stock.