yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] nomenore:
I do not think we'd be but I'll try Thanks for the help bro

---------- Post added at 04:54 PM ---------- Previous post was at 04:49 PM ----------

Damn the same error :((
[Galaxy S 4 i9505 Android Development] cosako63:
hi Phil3759, I´m glad to see you here...

I wanna ask? what diferent are in jfltexx and jflte kernel? I have a SGS4 GT-I9505 international

and this kernel I can use with the last stock rom 4.4.2 in orden too made root?

thank you..
[Galaxy S 4 i9505 Android Development] Phil3759:
Phone Health State Update

I ended up buying a new battery. They really suck. Phone is under warranty for 2 years, battery 6 months, and it is away by 4 days!

You were right, big thanks: the phone now is back to life. The battery was really swollen a lot

I also bought a 64Gb sdcard so that I can better debug storage issues

For now, it works perfectly under PhilZ Touch ;)
[Galaxy S 4 i9505 Android Development] Milamber:
I too have had to take my battery back die to swelling and heat. Apparently there are two variants of official Samsung batteries.
[Galaxy S 4 i9505 Android Development] Phil3759:
My new battery is dated june 2013 :eek:

How can I know if it is bad quality that will die again in 6 months?
[Galaxy S 4 i9505 Android Development] Phil3759:
My new 64Gb sandisk formatted to exfat is about 30% faster than my old sandisk 16 Gb card

3.6Gb with compression set to low are done in 8 mn vs 11 mn before

Internal storage, as expected (ext4) is much much faster (about 3 mn)
[Galaxy S 4 i9505 Android Development] Joery1983:
You can check the Serial Number of your battery. If the S/N starts with BD1D and the date is in the range of 401 - 529 (1st april - 29th may), it's probably a defective battery.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] Phil3759:
The new one is an LC1D and is dated 2013.06.04

So I assume it is fine, hopefully

Many thanks again for the quick support
[Galaxy S 4 i9505 Android Development] Joery1983:
It should be fine.

(disclaimer: no guarantee given :) )

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] Formhault:
What about the old one?
[Galaxy S 4 i9505 Android Development] Phil3759:
It is a BD1D in fact

Will be back to the shop to try to get a replacement

That way I have a second battery. Maybe they accept RMA if it was recognized as a defective series

Or, as usual, Samsung never did an official call back?
[Galaxy S 4 i9505 Android Development] Joery1983:
They will replace it . even over six months not by two years of course but a couple of days shouldn't be a problem

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] Milamber:
From what i was told there two types of battery: Chinese and Japanese, those manufactured in China are the problematic ones, also see this:

http://www.phonearena.com/news/Sams...attery-issue-offers-free-replacements_id48352
[Galaxy S 4 i9505 Android Development] Formhault:
I don't see any dates on my battery :eek:. I had the Galaxy Note and Galaxy Note 2 and they both had dates on the batteries :confused:.
[Galaxy S 4 i9505 Android Development] Phil3759:
thank you a lot, I will bookmark it and be back to the shop
[Galaxy S 4 i9505 Android Development] Formhault:
Oh, so they switched from printing dates on the battery to integrating them within the serial number... Much like what their modem/firmware naming scheme goes, huh? :silly:

This is what it says on my battery.

B600BE. S/N : AA1D424yS/2-B.

AA1D, so that's not defective? I had this phone since late August last year, and the battery is not swollen yet. I guess I'm safe :D.

424... I guess that too is within 1st April - 29th May. :eek:
[Galaxy S 4 i9505 Android Development] Joery1983:
Yours should be fine, but you'll find out soon enough :)

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] Formhault:
Well, I am near the 6 months milestone, I think, so the battery should have started to swell up a bit by now. Unless it is programmed to swell a lot at exactly X days... :confused:
[Galaxy S 4 i9505 Android Development] Joery1983:
There aren't any known issues with your serial number so your battery should be fine. That being said it's alway possible that you've got that one battery that does have issues, but I doubt it.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] Formhault:
Of course. There's always the possibility that 1 out of 1000 batteries from a good batch would develop issues. :p

So, BD1D's are bad. A friend of mine has a (endless family tree) that has a problematic Galaxy S4 battery (not even 4 months old). Bet that's BD1D, but will check. This should be interesting.

---------- Post added at 12:19 PM ---------- Previous post was at 12:17 PM ----------

The internal storage of the Galaxy S4 is EXT4? I thought it's FAT32, like it was on the Galaxy Note (if I remember correctly).

So that's why Mass Storage is problematic / doesn't even work... :p
[Galaxy S 4 i9505 Android Development] Phil3759:
Good morning and welcome to Android 2014 :D
[Galaxy S 4 i9505 Android Development] phil.o:
Pahahahaa...you made my day! ?

°°° tapatalked °°°
[Galaxy S 4 i9505 Android Development] Phil3759:
No bad feelings

Search for /data/media

Most new devices, except some low end models, use /data/media since 2 or 3 years I think

In Samsung range, i9100/n7000 were the latest ones using dedicated mmc block partition for internal storage

Since internal storage is part of /data partition, you cannot use it as USB device, at least practically
[Galaxy S 4 i9505 Android Development] Formhault:
Yeah, I know. Don't know how I could still think there's a possibility the internal memory is FAT32. Hence the ":(". :silly:
[Galaxy S 4 i9505 Android Development] nazfalas:
Just updated to 6.18.7 and noticed that transfer speeds for USB mass storage are now stuck at about 350KB/s. Before it was fluctuating between 350KB/s and about 3MB/s.

Edit: FAT32 formatted 32GB Sandisk mSD, was on 6.15.4 before.
[Galaxy S 4 i9505 Android Development] starbucks2010:
I noticed also this. I'm on latest version. There are also some glitched in Aroma when scrolling when I tried to install FH 4.4 ROM.
[Galaxy S 4 i9505 Android Development] timberwolf60:
Flashed 5.05.0, tested full rom backup/restore with success. Only one problems when I rebooted from cwm either from backup or restore. My phone can't detected my 64gb exFAT ext sd card. Also my phone freezed and can't run any programme. After 2nd reboot then my phone became normal. Thank Phil for your hard works and now you achieved a great improvement. Good.

Done customer backup on efs. I selected power off in cwm menu. Then on the phone, this time the above problems gone. My phone booted up normally. Cheers!

A coffee for you: Paypal donation 1LM61852SX0150633

Send via i9505 using XDA premium,

ROM: cf auto rooted ME2.

Phil CWM 5.05.0

superSU 1.30
[Galaxy S 4 i9505 Android Development] Phil3759:
Thanks for your generosity :good:

What do you mean by the reboot from backup?

You mean, you finish the backup then reboot phone?
[Galaxy S 4 i9505 Android Development] timberwolf60:
I selected reboot system in cwm menu. It boot up with errors. Can't detected my ext sd card also my phone freeze. If I selected power off options in cwm menu, then on my phone and everything worked perfectly. Thank!

Send via i9505 using XDA premium,

ROM: cf auto rooted ME2. CWM

superSU 1.30
[Galaxy S 4 i9505 Android Development] Phil3759:
I sadly cannot reproduce the issue

Make backup

Export log before you reboot

Reboot to main system

In your ROM, browse to /cache/recovery and attach here the last_log, last_install and the log you exported to sdcard

Many thanks
[Galaxy S 4 i9505 Android Development] -BioHaZard-:
Hi Phil, could you add "adbd insecure" to the kernel, at the minute I can't access the system partition via adb without entering shell su first.
[Galaxy S 4 i9505 Android Development] Phil3759:
Sadly, I use stock kernel, I am not recompiling it, only recovery and ramdisk I compile/edit
[Galaxy S 4 i9505 Android Development] -BioHaZard-:
Ahh okay, thanks anyway. :)
[Galaxy S 4 i9505 Android Development] Phil3759:
About 100 downloads already :D

Any more feedback / logs?
[Galaxy S 4 i9505 Android Development] Tassos_i:
I was waiting to do a nandroid restore from my exfat sandisk 64, but postponed this for later today (not yet decided, but I'll do it, promise !).

For the time being, your latest version works just fine with my external sd.

In case anyone is interested, the same backup on my external sd took about :

22 minutes, 2.1 GB with Philz 5.05.0 (low compression)

12 minutes, 3.2 GB with chenglu 6.0.3.2-4 (uncompressed)

I still have 2 questions :

Why don't we have any longer internal sd support in usb mount ? It is a cwm limitation, or an I9505 one ?

I know you don't have a I9505, so you have to guess. But could you change the default values for character size and for touch sensitivity, to make them friendlier for people that are no more 20/30 years old ?

And "better late than never" (you know, since the time I've been using your recoveries), a cup of greek coffee for you (paypal : 1SD59598XS344650R).
[Galaxy S 4 i9505 Android Development] Phil3759:
Great it fixed the exfat 64Gb issues

Many thanks for your generosity. Much appreciated these days with all this work for i9505 :good:

22 mn is a bit long I find for just 2Gb. It is much faster on my i9100. Was it that way with previous versions? Can you try without compression?

About the values: can you be more explicit what exactly would you like? I am open to enhance it as I have not am i9505 and have no big idea how things look or feel on it
[Galaxy S 4 i9505 Android Development] Tassos_i:
I'll do several backups later and I'll let you know. There are curious things happening when backuping on external sd. For instance, with chenglu's cwm, it takes 4 times longer (yes) when backuping on external sd while charging !!!

1. Bigger font (I'd say, at least 30%)

2. Much much less sensitive, though here I can not quantify... I'll wait till you touch a I9505 with your recovery on board.
[Galaxy S 4 i9505 Android Development] Phil3759:
On my phone, i9100, and 16Gb exfat card, using low compression, it takes about 10mn for 2.4 Gb, same recovery version.

Font, will look at it later. Not sure we have bigger fonts in cwm sources and i am no competent to write my own.

About sensitivity, did you try to increase scroll sensitivity to max +100 value?

Else, can you describe touch gesture you do and how they act? At best, a video showing it would be great
[Galaxy S 4 i9505 Android Development] Tassos_i:
Just to give an idea of relative font sizes Philz vs Chenglu. For my eyes, Philz font is really too small.
[Galaxy S 4 i9505 Android Development] Phil3759:
Pics always help. I will look at it. Seems i was not using biggest font as i thought
[Galaxy S 4 i9505 Android Development] kantjer:
I hope you can find a bigger font, for me that was the only reason to go back to TWRP for now. The font was just to small for comfort.
[Galaxy S 4 i9505 Android Development] daibaron:
Backup time took 15min for 4.20 Gb job without compression on extfat in 32Gb Sandisk SDHC.

Write speed on my SD is about 8Mb and read speed is 17Mb. (tested with SD Tool)

Generating the md5 takes between 3 - 5 min
[Galaxy S 4 i9505 Android Development] Phil3759:
Now this is good timing :good:

I am quiet sure compression on low mode should make it faster. The reasoning is this:

Compression uses pigz: a multi-threading gzip compression that should make all cores working

In my tests and all over the web, with modern CPU, the time difference is very small to null, but you can achieve around 30% compression

On 4.2 Gb, this is 1.26 Gb less data to write to sdcard

At the end, it should make it faster then without compression

At least, in theory...
[Galaxy S 4 i9505 Android Development] Tassos_i:
Some backup times for "low compression" and 2.12GB compressed backup size:

1. On internal sd : <11min

2. On external sd SanDisk 64 exfat, while NOT charging : 12 min

3. On external sd, while CHARGING : 22min (1st time) , 18min (2nd time)!!!

Had similar experience on external sd with Chenglu's cwm : <12 min while not charging, 45 min while charging!!!

Is there a random component in cwm backup?
[Galaxy S 4 i9505 Android Development] Phil3759:
Interesting in fact

What's more strange is that with my recovery you get much faster speed over Chenglu, while we have same recovery base (my modifications shouldn't explain that difference)

Only real difference is the kernel base. He uses an older Chinese version if I am not wrong (at least on the first releases I looked at) while I am using EM2 europe. Now, to fix this exfat issue for big cards, we are loading exfat modules from /system, that is your main ROM

It could explain part of the issue. However, without a phone to test, this would take me ages to debug

In any-case, I am happy, at least for once, it is better with this version :D

Please, post this issue on [MENTION=3084245]Chenglu[/MENTION] thread. We owe him a lot for this port to i9505, and he would probably look at it, since at least he has an S4 to test
[Galaxy S 4 i9505 Android Development] daibaron:
I just tried low compression (35.36%) and It took 14.36 min which does not make any difference (see my previous post)

This also happened to me with Chenglu's CWM, It took 40 min while the GS4 was charging

Ty Philz
[Galaxy S 4 i9505 Android Development] elxufas:
Where is the link to the download on the recovery folder, I only see the latest version

philz_touch_6.15.4-jfltexx.zip

I do not see the version 6.18.7
[Galaxy S 4 i9505 Android Development] BillGoss:
Read the OP.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] elxufas:
Thanks friend not it had read, now this as Jflte.
[Galaxy S 4 i9505 Android Development] BrunoSlivar:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
[Galaxy S 4 i9505 Android Development] bubba949:
Jflte for all now. Read OP!

EDIT- tapatalk quoted wrong post ?
[Galaxy S 4 i9505 Android Development] MatteoB92:
It's also written in red..

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Android Development] Tanis64:
Newest Version is out,

Small cosmetic issue:

Version in File Names is 6.19.3

Version in Recovery is 6.19.2 (after flashing tar)

I think this is nothing to care about.

Send from the outback with my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
It is explained in main thread

No issues
[Galaxy S 4 i9505 Android Development] andreasy:
I try to download and after the ten seconds countdown, the download doesn't start but the page below appears. This never happened before. Has something changed?
[Galaxy S 4 i9505 Android Development] zukri90:
Maybe it is the browser that you're using that the download doesn't appear?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Android Development] andreasy:
Most probably because from pc I download just fine. I use chrome on my phone but this started when I upgraded to 4.4.2. I later noticed the same with other links as well but I don't know the cause
[Galaxy S 4 i9505 Android Development] Tanis64:
In 4.4 KitKat Google (silently) changed the way (permissions) for Apps to have write access to the external SD. So I didn't know if chrome app is already up to date with this new Permissions to write to the ext. SD.

Send from the outback with my GT-I9505
[Galaxy S 4 i9505 Android Development] ixomon:
I cannot write on external sd anymore, for about a week now. More precise, the data is written and visible and vanishes after a reboot... for nandroid backups the same as in CM11.

Did I miss something crucial?

Did I do anything wrong?

Sent from GT-I9505
[Galaxy S 4 i9505 Android Development] Milamber:
I'm a little confused, which link do we use for S4?
[Galaxy S 4 i9505 Android Development] zukri90:
Read the title. Use jflte.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Android Development] krinyo75:
hi

Is there any cache option in this recovery? I'm using TWRP which creates backup from my rom in 3 mins (with compression!), using Philz recovery to create a backup from the same rom it takes 7-8 mins (without compression!). So this recovery is a little bit slow :)
[Galaxy S 4 i9505 Android Development] zeus85:
My s4 has recently stopped charging whilst powered of is there anything in in philz I can wipe/format to stop it from freezing whilst turned of I'm on i9505xxufnb9 modem latest cm11 nighley using cm stock kernel

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Android Development] Phil3759:
no, cwm doesn't cache writes

TWRP comes with a custom tar code
[Galaxy S 4 i9505 Android Development] Technical:
Phil, thanks for your custom recovery. I'm a long journey with TWRP but yours seems much more flexible.

I'm just really missing the flash queue for multiply zip flashing. I really do not want to put all of them in the multi_flash folder... :(
[Galaxy S 4 i9505 Android Development] wizard83:
[MENTION=4666971]Phil3759[/MENTION] I have to thank you for efs backup/restore support.

Yesterday something went wrong flashing a rom, no imei, no signal, efs was corrupted.

I did not make a backup with your recovery, but with other apps found here on xda. Tried to restore with them, no luck: every apps said Ok, but still no imei after reboot.

So I put a .img backup on .efs_backup folder and try to restore with philz recovery.

Here is the log

Restore /storage/sdcard1/clockworkmod/backup/.efs_backup/efs.img to /dev/block/mmcblk0p10 (/efs)

Success!

And after reboot my imei was restored! Thanks thanks thanks, you Saved me, I will donate as soon as possible!
[Galaxy S 4 i9505 Android Development] txingu:
Hi Philz!

I want to suggest you something..... Is difficult to add a password for enter to recovery?

I think it could be a great option... Because if someone steal your device or something happend... You can search your device if the robber don't do a Factory reset...( with an App like cerberus, for example)

Sorry if this idea is a bit stupid... i was thinking that is a good idea, so i want to suggest you

Thank you so much for your time and your giant work!
[Galaxy S 4 i9505 Android Development] aHcVolle:
this has been suggested many times... the problem is that the recovery can be overwritten via odin and then all the pw protection of the recovery would be gone ...
[Galaxy S 4 i9505 Android Development] Formhault:
Hope any thieves that may be targeting your phone don't know what Odin is and probably gonna have a hard time installing USB drivers? :D

Regardless, I don't have any anti-theft software on my phone. If it's ever stolen, I'm pretty much screwed. Hopefully that never happens, though, to anyone.
[Galaxy S 4 i9505 Android Development] Technical:
You can use avast! Anti-Theft for free :cowboy:
[Galaxy S 4 i9505 Android Development] morris2003:
Please add default checking for option "Allow old binary Scripts", because some users getting this error when install ROM:

Thanks :)
[Galaxy S 4 i9505 Android Development] Phil3759:
There is a toggle but temporary

Hammer your mod rom to update his scripts
[Galaxy S 4 i9505 Android Development] morris2003:
When you will remove the compatibility with older scripts?
[Galaxy S 4 i9505 Android Development] Formhault:
I am not so sure that's the problem...

I did check "Allow old binary Scripts" and still wasn't able to install Danvdh's latest GE ROM. It didn't work with CWM, neither (as someone suggested :rolleyes:). Only TWRP did the job... :eek:
[Galaxy S 4 i9505 Android Development] Phil3759:
Post log error on install
[Galaxy S 4 i9505 Android Development] kenshiroSG24:
Faulty sd card. Had the same problem, it means it's gone into a write lock so you will have to contact the manufacturer and they will replace it for free if it's still under warranty.
[Galaxy S 4 i9505 Android Development] HaTrED_:
Strange, i've used Philz's latest recovery to install Danvdh's latest GE ROM without any problem! :confused:

I've done that uncheking the option available under flash zip menu!
[Galaxy S 4 i9505 Android Development] Technical:
Not really. I'm facing similar issues and I do not think it's a faulty sdcard as posted before.

http://www.gottabemobile.com/2014/0...ote-3-android-4-4-problem-hits-micro-sd-card/

http://android.stackexchange.com/qu...droid-4-4-not-being-able-to-write-to-sd-cards

http://www.androidauthority.com/galaxy-s4-gpe-android-4-3-sd-card-fix-254960/
[Galaxy S 4 i9505 Android Development] kenshiroSG24:
You can try the fixes but if it doesn't work then it means your card has locked. Also don't format to exfat. Always use Fat32.
[Galaxy S 4 i9505 Android Development] Formhault:
Can't right now. Hopefully will do so on Monday. Sorry... :(
[Galaxy S 4 i9505 Android Development] Technical:
In fact, I was not even able to find (download) the file...

Android does not work well with exFat. But, I would do anything, even use ext4, if this problem is circumvented and I'm sure I won't lose my files.

I could lose Windows share, but I can't live with this gun pointed to my head: will be my files safe when I woke up in the morning?

I can't understand why would the file system interfere in this "mounting" issue though.
[Galaxy S 4 i9505 Android Development] zeus85:
I had problems with exfat would be fine for a week or so then randomly stops writing data use philz recovery to format to NTFS format works great for me just make sure what ever ROM you have the kernel supports it

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Android Development] Phil3759:
Maybe cm11 and fuse bugs.

I never used other than exfat, no issues ever. PhilZ Touch uses kernel built in exfat support
[Galaxy S 4 i9505 Android Development] zeus85:
Could it possibly be to do with flaky compatibility with sd cards i use a sandisk extreme plus 64gb uhs1 without your recovery I would of been screwed

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Android Development] Phil3759:
I use same sdcard too
[Galaxy S 4 i9505 Android Development] SmartFreak:
Using Samsung 64Gb exFAT card, never had issues with it with any of Philz recoveries
[Galaxy S 4 i9505 Android Development] zeus85:
No idea what the problem was then maybe something to do with my phone itself s4 is said to dislike 64gb micro SD cards

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Android Development] ixomon:
Thx, I should have read that earlier. Found it out myself after quite some testing... I would have never thought of this as the reason. Sorry for thinking of the Recovery as a source for this behavior.

PS: Despite the write lock, the card reads fine... how can I erase my private data before sending it to the manufacturer? Delete, Format nothing works... They don't need to see my naked girlfriend...
[Galaxy S 4 i9505 Android Development] Riskytwin:
If your girlfriend is sexy send your sd to me, lol... Jokes apart, remove partition or low level format with a PC.

Risky's my name
[Galaxy S 4 i9505 Android Development] Technical:
You could use the wipe options of partition tools like EaseUS Partition Master Free Edition or MiniTool Partition Wizard Home Edition.

You can also wipe with 3rd party tools like CCleaner, Glary Utilities or even the bootable Darik's Boot & Nuke.
[Galaxy S 4 i9505 Android Development] KenHua:
Error Status 7

Dear Philz, the subject of "Error status 7" has been mentioned over and over again but many still don't get it! You suggested to people to tell developers to update their scripts but instead many are told to avoid Philz and use TWRP or CWM. It seems like a great waste to me that some people actually switched away from your great creation and even advise others to do so because it works. Just a suggestion: may be changing your default to support old script is an easy way to avoid such error, or better still if there is a way to detect the situation and switch to the appropriate mode as necessary.

Cheers, thanks again for your great recovery,
[Galaxy S 4 i9505 Android Development] kenshiroSG24:
Mine was SanDisk so I spoke to them about my private data and they said I could break the card and send them the pieces. Just express your concern about privacy. They will say that never happens and just tell them in the real world it does.