yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] ShimaMiku:
I can confirm it works. I just pulled the Titanium backup of the most recent version of Watch On (6.1.2) from my stock Galaxy S4 Active and put it on my S4 Google Edition running CM11 nightly 01/12 and found it works. I unchecked the notifications panel for it in the settings though because it doesn't play nicely.

I'd upload the backup here for you to just install via Titanium Backup, but it totals about 22MB, which exceeds the upload limit. Sorry!
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Hi Guys,

anyone have this problem? http://xdaforums.com/showthread.php?p=49418767

someone know how fix it?

Thanks
[Galaxy S 4 i9505 Original Android Development] Steyux:
Same problem here!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] knirirr:
Is anyone who is using an exFAT formatted sdcard able to let me know whether they also see the following problems?

Rsync fails to read some (but not all) files on the card, claiming it is out of memory.

Scheduled Titanium backups occasionally fail, claiming that there is no space on the sdcard (>40GB free in reality, though).

The Android File Transfer on OSX is not able to read or access some folders on the card.

Perhaps it is something wrong with my card, or device, but if anyone else has seen something similar then it may not be.
[Galaxy S 4 i9505 Original Android Development] pavelcheto:
I use a exFat 32GB card. Haven't used any of the things you do but when I try to create a folder with ES File Explorer it says there is not enough memory. Writing and reading files, however, work fine.
[Galaxy S 4 i9505 Original Android Development] knirirr:
Thanks - that sounds as if it's a similar problem, which makes me wonder if the driver is dodgy.

I don't fancy reformatting to FAT32 as I would rather like to be able to have large files on the card (it's 64GB), and so I wonder whether it could be reformatted as ext4. Presumably the phone would try to mount that as /sd-ext rather than /storage/sdcard1 and there might be permissions issues as well, though.
[Galaxy S 4 i9505 Original Android Development] jcespi2005:
I have 0 problems with my 64Gb extFat, using Root explorer or the one included in CM11. Also using FolderMount with success to link TomTom data golder and some obb games data.

Cheers

Enviado desde mi GT-I9505 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Flashed the today nightly, the problem is still here :(
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Wait for tomorrows nightly.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] |_dan_|:
yep, in the next should be fixed by [MENTION=2682982]noobnl[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Phrost:
Sorry for being an ignorant twat and not searching the thread, but does anyone else have a problem with the proximity sensor?

IE screen dont turn on during call and prox sensor test apps dont register changes?

Thanks :)

(pre-post edit: yes i have the jan 14 nightly installed)
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
i see the changelog, i hope will be really fix :fingers-crossed:

Thanks for your reply:highfive:
[Galaxy S 4 i9505 Original Android Development] om22:
The problem is known and a fix is in progess. Have a look into the cm jira bugtracker many fixes are in progress for the jf line of devices.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
:good:

Thanks
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
The jira is not visible without account... :/

Gesendet von meinem Nexus 7 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] om22:
You can also see the changes that are being processed in code review: http://review.cyanogenmod.org/#/q/status:open+branch:cm-11.0+jf,n,z

Look we've got fix gps and fix network modes there :)

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Thanks

Please ceck also the problem of network for italian netwok :fingers-crossed:

Thanks again
[Galaxy S 4 i9505 Original Android Development] SP33DY89:
Seems I am finally in the right spot...

Hi all, I'm new to xda... Not new to rooting and flashing. I'm aware that random freezing is a current issue. I also have poor battery life. I'm using a 7000mah extended battery and can't get 12hrs out of it. Everything runs pretty smoothly and everything seems to work fine. The random freezes for me can be in any app. Mainly being launcher3 FC .
[Galaxy S 4 i9505 Original Android Development] jasunto:
1-14 nightly same thing, wont boot past CM logo with spinning arrow
[Galaxy S 4 i9505 Original Android Development] Swizzy88:
Small issue with the latest nightly.

I've set my WiFi to keep on during sleep only when plugged on, so that it turns off when the phone enters sleep.

However the WiFi doesn't turn back on once I wake the phone up. If I then try to turn wifi off and on again and sometimes the button seems to freeze and it takes 1-2 minutes to react. Really strange problem.

I made a clean install from the last nightly since I messed around with the kernel settings too much. Factory reset, then flashed the nightly, then gapps as always.

Just wondering whether I'm missing something.

baseband i9505xxuemk8

Also is there a way to backup CM settings between full wipes, like the lockscreen, display and sound settings etc?
[Galaxy S 4 i9505 Original Android Development] neunzehn77:
I`m a little confused.... some things i?m missing:

- How could i take a screenshot ( Vol down + power won`t work ) OKAY found it... Vol down + Power + Home

- How to start Screencast?
[Galaxy S 4 i9505 Original Android Development] !crazy:
Which GPS fix? I using navigation all the time with nightlies, and never noticed a problem with GPS...
[Galaxy S 4 i9505 Original Android Development] j_r0dd:
Battery life is definitely back to being awesome again. Last week I was charging 3 times a day.
[Galaxy S 4 i9505 Original Android Development] om22:
Compass is halfly broken since cm10.1. If you turn the phone around the various axes of itself while maps is open it will start working that's why I call it "halfly working"

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Jaco2k:
I have noticed using CPU-Z that there are some duplicated sensors - there is a version of compass and accelerometer that works but for instant the GPS status app doesnt see them at all...
[Galaxy S 4 i9505 Original Android Development] !crazy:
You said GPS. I have noticed that issue with compass. But it happens also with my wife's Note 3, which has unrooted stock 4.3.

It seems that compas every now and then nerds to be calibrated. I still do not know how often.

Regarding Maps, and GPS, all navigation apps I use (Maps, and Sygic.) work well. Didn't notice that the issue with compass affects them in any way.
[Galaxy S 4 i9505 Original Android Development] GalaxyS49505:
Still not included new Adreno 4.4.2 blobs?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
No :(. Ui/game performance is not their thing I guess.... Damn.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] dboechat:
Sygic seems to work because in 'car mode' it doesn't rely on compass too much, the arrow points to the direction you're moving. In 'walking mode' though it's completely broken.
[Galaxy S 4 i9505 Original Android Development] jonneymendoza:
Hi all.

Love the rom but the battery is not good on idle especially. Stays awake all the time due to a mixture of things such as a wake lock called ritl?

Anyways does anyone know how to create a print screen so I can post my battery stats? Thanks
[Galaxy S 4 i9505 Original Android Development] jd1001:
Volume down + power button
[Galaxy S 4 i9505 Original Android Development] jonneymendoza:
Ok thanks. Here is my screen shots of my battery usage. It was full before I went to bed and wanted to see how it fairs when in idle and I woke up and it was down to 80%
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Yes battery is bad now ...

I have been using nightly since Dec. 14 and battery on idle have been good until now!

No change in my setup. I think wake lock must have been introduced in one of the latest updates :confused:

! EDIT !

I'm using 2014-01-14 nightly
[Galaxy S 4 i9505 Original Android Development] jonneymendoza:
Ahh so it's not just me?
[Galaxy S 4 i9505 Original Android Development] om22:
Last nightlies were really bad at battery life for me. BUT on 20140114 it's perfect again I loose about 1% per 2h standby with wlan h+ on.

Just deactivate google now and location reporting/history in google settings.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
Thanks for your input. I never used sygic in walking mode, but I think I was using maps about week ago in walking mode, and it worked fine. I don't remember If I had calibrated compass before that, but it is quite possible.
[Galaxy S 4 i9505 Original Android Development] jonneymendoza:
Google location was disabled all night .

i am using the 11-20140112 NIGHTLY-jfltexx
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Same for me ... Google location disabled.

Not related to battery drain when idle I think
[Galaxy S 4 i9505 Original Android Development] jasunto:
Does 1/15 nightly actually boot now? I'm on 9505G gpe
[Galaxy S 4 i9505 Original Android Development] geomax45:
No problem for me.
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Flashed cm-11-20140115-NIGHTLY-jfltexx.zip

and this problem http://xdaforums.com/showthread.php?p=49418767 was partly fixed

here

now i see the correct name of my network

but instead here

still are numbers instead the correct letters name

Maybe the CM Team dont have this problem because have different Network than Italian Network?:confused:

Please Someone know how i can report the problem to CM Team?

Thanks
[Galaxy S 4 i9505 Original Android Development] jasunto:
Just flashed and it worked. Finally!
[Galaxy S 4 i9505 Original Android Development] zeus85:
On the last nightly only one app failed whilst arting cmupdater since this update iv give it another try and everything is working so far with arting :) I'm new to s4 from hox+ and I'm loving it

S4 GT-I9505 Cm11
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
Because of this long lasting problem, i always flash jfletetmo ROMs instead of jfletexx. ALL jfletexx custom ROMs that i have tested so far have this problem, even the one from broodplank. The jfletetmo ones show the correct names...
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
before to stabilize to CM11 i flash too many rom, only one showed the correct name, but i not remember which one, maybe the Gummy, but im not sure :(

i hope the CM Team know this problem and can work to fix it :fingers-crossed:

Do you flash jfletetmo ROMs on jfletexx.device?
[Galaxy S 4 i9505 Original Android Development] exynoss:
I m in shame boat like you tried all nightly from 1st jan 14th even tried rc 2 but everything unable to paas cm bootloop logo. I posted here many times but not got the solution and see u r able to boot now I am very excited about will try it today :)
[Galaxy S 4 i9505 Original Android Development] slugthru:
https://jira.cyanogenmod.org/

It has been reported, search Jira for "network name".
[Galaxy S 4 i9505 Original Android Development] noobnl:
http://review.cyanogenmod.org/#/c/57574/

been fixed already, need arcee final approval.
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
good :)

Thanks for your reply :good:

Good News :laugh::laugh:

Thanks for your reply :laugh:
[Galaxy S 4 i9505 Original Android Development] exynoss:
Bad luck still boot loop forever :( i am tired now try everyday with every nightly.

Today my steps are :

Put zip file in external sd card

Boot to latest cwm recovery

Wipe data / factory reset

Wipe cache

Wipe dalvik cache

format system

format data

Flash nightly zip from external sd.

Then reboot then stuck on cm logo. Restarted many times.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
I know that your not a newbie, but did you try this:

Put ZIP inside folder named "cmupdate" located on your internal SDCard.

Then goto Settings --> About Mobile --> CyanogenMod Updates --> and flash the ZIP from here (push the icon).

Have experienced "stuck on cm logo" a lot of times, but not with recent 3-4 updates.

If this fails ... try to flash Clockwork-Touch-6.0.4.4 using "SGS4 Flasher" from Google Play ... it work fine :)

Then try again.

BTW

I haven't made any "Wipe data / factory reset" the last month ... no need ... just update from within the mobile :)
[Galaxy S 4 i9505 Original Android Development] MrJiM:
Try this if you havent done it.

1: backup needed stuff from external sd and internal sd to pc.

2: format external sd in recovery ( I use philz )

3: put nightly, latest banks gapps ( I use core ) and latest KT kernel on external sd

4: choose "install new rom", after that manual format system, data, cache, dalvik and internal sd

5: flash nightly and wipe cache and dalvik

6: flash gapps and wipe cache and dalvik

7: flash KT kernel and wipe cache and dalvik

8: reboot and hope for the best. it can take a few minutes for the rom to boot at first

I know some steps are "not needed" but it may help you with your issue. :)
[Galaxy S 4 i9505 Original Android Development] exynoss:
I m not updating mate. Currently i am on pa 4.3.1 so ho chance to have cm folder inside internal sd :confused::p

Also tried cwm touch recovery too.

---------- Post added at 10:13 PM ---------- Previous post was at 10:07 PM ----------

Thanks for your reply but why should I need to format external sd and need to flash Kt Kernel. Except these two steps I already tried all above.
[Galaxy S 4 i9505 Original Android Development] MrJiM:
Crap files can be on sd from apps. Cant hurt to try. :)

Btw.. what is your modem version?
[Galaxy S 4 i9505 Original Android Development] exynoss:
My modem /baseband is mj7
[Galaxy S 4 i9505 Original Android Development] ionutzvio:
After flash zip try wipe cache partition and dalvik cache and then reboot. For me it worked with phis's recovery.
[Galaxy S 4 i9505 Original Android Development] j_r0dd:
I created a script to enable the soft keys. This is persistent after every nightly flash. Just put in /system/addon.d https://docs.google.com/file/d/0B-DT2Bq_hbLuUXRXTGpxMGY2SnM/edit?usp=docslist_api

Replace /system/usr/keylayout/ sec_touchkey.kl with this one to disable the capacitive keys. The home button still works though. https://docs.google.com/file/d/0B-DT2Bq_hbLuY2dWMGhmUUhvMlU/edit?usp=docslist_api

I probably could have made a flashable zip but I'm lazy. This only needs to be done once. I despise the capacitive keys on my S4.

Just flash this instead. Only needs to be flashed 1 time.

https://drive.google.com/file/d/0B-DT2Bq_hbLuQ2hmcDBXRjN6cEU/edit?usp=sharing
[Galaxy S 4 i9505 Original Android Development] Mittaa:
My Meny & Back buttons didn't work after SwiftKey update (4.2.2).

Re-boot didn't help so I have to restore back to prior version of SwiftKey and buttons are working again.

This bug is for sure related to SwiftKey!

Anybody to confirm this?
[Galaxy S 4 i9505 Original Android Development] BillGoss:
I flash the following zip file. It adds a /data/local.prop file and replaces /system/usr/keylayout/sec_touckey.kl

https://www.dropbox.com/s/b9hr7w0tbjbrns6/Navigation_keys.zip

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] j_r0dd:
No issues with the new swiftkey and CM11 here.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
OK I will try again. This uninstall totally before reinstall.

Thanks :good:

!!! Total re-install helped !!!!
[Galaxy S 4 i9505 Original Android Development] NZgeek:
There's pretty much no reason to wipe cache and Dalvik more than once in the same recovery session. It makes sense when you look at these areas from a technical viewpoint.

The /cache partition is there to hold temporary data. It's usually used by apps that pull stuff off the internet, to hold local copies of downloaded files so that they're not downloaded again every time they're needed. It's very rare that something in the cache directory will cause the boot to fail. And if you haven't rebooted since the error, nothing other than the recovery will have had a chance to write anything there anyway.

The Dalvik cache holds a copy of the executable portion of each app, extracted from the apk file. I'm fairly certain that this process also optimises (odexes) the app as part of this. The Dalvik cache is updated when the ROM boots (we've all seen that screen) and when an app is installed. Update zips almost never write these files because each ROM build could optimise then differently. It's not touched by the recovery either, so if you haven't rebooted since wiping it, there won't be anything there to wipe.

It makes a lot more sense to wipe these areas once, flash your zips, then reboot. If you have problems then you can boot back into recovery, wipe cache and Dalvik (and maybe data) and reboot.

For the record, I have never once wiped cache or Dalvik when installing new ROMs. I have never had a single issue because of this.
[Galaxy S 4 i9505 Original Android Development] Chahk:
Most ROMs wipe cache and dalvik-cache during installation automatically.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Exactly :good:
[Galaxy S 4 i9505 Original Android Development] exynoss:
Not worked.
[Galaxy S 4 i9505 Original Android Development] NZgeek:
This completely slipped my mind when I was posting. It's not 100% guaranteed that every ROM out there does these wipes, but it's uncommon to find one that doesn't.

The only time you should ever have to wipe Dalvik manually is when you're flashing a zip that updates deletes existing apks, or if you suspect that Dalvik become corrupt.

Wiping cache probably won't fix boot issues, but it can help to free done space if it's symlinked to somewhere in your /data partition. Wiping for any other reason is pointless.

So now that we've disproved the wiping thing, we need some other pointless ritual for people to do when they're flashing their phones. How about this one: When you flash you should always have your phone screen-side down, otherwise elections leaking from the screen could fall into the memory chips and cause a bad flash.
[Galaxy S 4 i9505 Original Android Development] om22:
This fixes the Operators shown as numbers Bug in the network list:

http://review.cyanogenmod.org/#/c/57574/

Will be included in next nightly.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Swizzy88:
Flashed the latest nightly (16) last night and saw this in the battery tab this morning.

It gained about 4% over 5 hours. Never seen this before.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Have had same experience with nightly (15) but it was related to app running wild.

After tweaking battery now is fine again. This night I only lost 2% over 8 hours so nothing wrong with latest (16) nightly :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Marcet:
Love that one!
[Galaxy S 4 i9505 Original Android Development] Swizzy88:
How did you tweak the battery? I know on stock rom there is a code, I think it was *#0228# or something that re-calibrated the battery but it doesn't work on CM.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Nothing fancy ...

Didn't re-calibrate battery ... no need for that.

After battery reset it's easy to spot drain using using Wakelockdetector (WLD).

Found a widgets updating things like weather even if I don't use that widget (deleted)!

Froze unused apps and change update behavior for Google Play, Exchange and a few other services.

If app supports "Quit Hours" like function, I enables that. So at the moment practically nothing happens between 11 PM and 7 AM.
[Galaxy S 4 i9505 Original Android Development] Swizzy88:
I know about wakelocks and tweaking battery life. What my initial question was about was the apparent INCREASE of 4% battery over a period of 5 hours WITHOUT charging.
[Galaxy S 4 i9505 Original Android Development] lixxus:
im having issues with sound on this rom. the microphone input is low and when recording etc on whatsapp and other voice recorder apps my voice is low.

also the dsp manager randomly crashes etc and sound is very flaky,

can someone confirm this or provide solution. i know this is nightly etc
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Ohh yes really like when my mobile recharge WITHOUT charging :laugh:

Maybe we can thank temperature and battery chemistry for that phenomenon (real increase) or maybe it's due to some OS algoritm? I don't now :)
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
+1 i can confirm :laugh:

Flashed the cm-11-20140117-NIGHTLY-jfltexx.zip the bug is fixed :laugh::victory:

great CM Team!!! :laugh::good:
[Galaxy S 4 i9505 Original Android Development] d0nate110:
S4 with 4.3 Stock rooted with CWM Touch

Sorry for noob question, but "search function" didn't show the answer.

I have S4 i9505 with this damn KNOX Update 4.3 Stock ROM.

I successfully rooted this phone with CF_Root by Chainfire and installed CWM 6.0.4.4 Touch with SGS4 Flash from Market.

My KNOX is now 0x1

My Question is:

Can I flash Cm11 on this KNOX 4.3 Stock Android ?

I'm asking cuz' Chainfire said on his homepage, that all phones with KNOX have locked bootlader and flashing another OS like CyanogenMod will brick the phone.

Please be patient with noobs :D

Thanks anyways !
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Do you mean S4 i9005 or S4 i9505 ??? This thread is about S4 i9505 !!!

I came from

Stock Samsung SGS4 i9505 (int)

and used PC and CM installer .. read more here ... very easy :good:

Get started her ... http://beta.download.cyanogenmod.org/install
[Galaxy S 4 i9505 Original Android Development] d0nate110:
sorry S4 i9505 !

I know how to flash CM11 on S4 with 4.2.2 on it ... but I have one with 4.3 AND KNOX bootloader !

Thats should be a different story...that was my question if KNOX has locked bootloader and this CM bricks my phone...
[Galaxy S 4 i9505 Original Android Development] jmjviana:
The option to set a ringtone to a specific contact isn't working properly. After I set the ringtone it shows the option I've selected but the phone only rings in the default ringtone.

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] petrus764:
You can still flash cm, knox does not lock your bootloader.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
KNOX bootloader takes part in detecting of any "illegal" changes have been made to your device ... like root and custom recovery. If changes have been made, KNOX "e-fuse" turns from 0x0 into 0x1 and you can't use KNOX secure container (app) anymore. Warranty is void ... but flashing CM also void Warranty (depending on where you life and how how the wind is blowing in service center that day!) ...

From CM FAQ ... link

Do I need to root my phone before installing?

No. You can have a rooted phone, or not. The installer doesn't care. However, to be in a supported configuration, you need to be running a stock ROM.

Do I need to unlock my bootloader first?

No, you don't. If your bootloader is locked, we'll unlock it for you.
[Galaxy S 4 i9505 Original Android Development] krz_ayman:
solved ;)
[Galaxy S 4 i9505 Original Android Development] Milamber:
I came from foxhound ROM which is a Samsung ROM, wiped everything and installed CM 11 - is that a bad thing? Because it says there you need to be running from stock