yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] Phil3759:
Many thanks

I can now work on the stock kernel version for better exfat speeds support if needed

Just if anyone can confirm if this version is slow when backing up to exfat cards, it would spare me some energy
[Galaxy S 4 i9505 Android Development] PearLRoX:
Thanks for the update!

Everything just works fine like always..

but, i came from a i9300, just notice there is no "fix permissions" option anymore? (Sorry if this allready was report, just bought me a new s4, came from a s3 with same recovery ;) )
[Galaxy S 4 i9505 Android Development] Me Gusta:
No your fault! It has been removed from the cwm base in 6.0.3.4 I thought.

Me Gusta!
[Galaxy S 4 i9505 Android Development] Bejda:
I wanted to add confirmation to BillGoss report (and spread the good news ;) ) and indeed all seems ok. I used 5.10.9 version and it's "clean installation" option to install Carbon rom 4.3 build and all went fine.. bootanimation, network, no issues :)

But something went strange (at least seems to me) with gapps installation.

After reboot and checks I wanted to install gapps (standard goo.im ones, jb20130813 4.3). Zip install seemed complete but faster than it should and indeed after boot I noticed nothing was installed.

I tried a few times but still the same, I flashed a cwm 6.0.3.5 zip>reboot recovery and gapps installation went finally correctly.

Here's the recovery.log:

View attachment philz_recovery.log.txt
[Galaxy S 4 i9505 Android Development] BillGoss:
Computer? What's a computer? I do everything on my phone. :D

I find that backup times are slower on this version. Compare this recent backup (FAT32; 64 GB SD card):

Backup time: 04:46 mn

Backup size: 828.20Mb

Compression: 41.62%

with those I posted earlier: http://xdaforums.com/showthread.php?p=44493454

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Milamber:
Has anyone noticed that when selecting reboot, phone powers off?
[Galaxy S 4 i9505 Android Development] cdzo72:
Mine reboots just fine
[Galaxy S 4 i9505 Android Development] Phil3759:
in last 5.10.9:

- go to Mounts and Storage

- check status for /system: does it show mount or unmount?

- can you mount/unmount it?
[Galaxy S 4 i9505 Android Development] Tanis64:
5.10.9:

Installed over 5.10.0 CWM.

Timezone seems ok.

Reboot from Recovery - ok.

Looks good.

Thank you PhilZ
[Galaxy S 4 i9505 Android Development] iron@ss:
5.10.9 DjeMBeY Modified ROM

Reboots fine. No switching off.

Date is shown correctly on backup screen. Time = GMT (not BST)

Correct date & time for backup shown in ROM Manager, previously showed 31 December 1979.

Backup time, excl: sd.ext = 14 min's. Previously = 17 min's

Backup size = 3.37GB
[Galaxy S 4 i9505 Android Development] cbeckstein:
5.10.9 for 64GB exFAT ext SD slower than 5.10.8 (100%) on Stock ROM, everything seems to work except for final statistics (backup size and compression ratio are reported 0)
[Galaxy S 4 i9505 Android Development] Phil3759:
How long does it take?
[Galaxy S 4 i9505 Android Development] cbeckstein:
a bit more than 40 min for 4.3 GB (backup to external 64GB exFAT SD, low compression)

5.10.8 was at about 17 min for the same amount of data
[Galaxy S 4 i9505 Android Development] Phil3759:
Any answer about this:

in last 5.10.9:

- go to Mounts and Storage

- check status for /system: does it show mount or unmount?

- can you mount/unmount it?

I will work on a repack with stock kernel once above question answered. That should give back fast exfat backups

5.10.9 is more suited for cm/aokp users
[Galaxy S 4 i9505 Android Development] Bejda:
That's about it yeah, system status is mounted by default (shows unmount proposition) but nothing get installed, still Read-only issues, unless it tick it (no matter mount or unmount) or its status changes.

The gapps zip unmount system correctly at the end of his failed installation, mounts and storage>system shows mount proposition (changed then) and now if I flash again immediately it's ok.

Another cwm zip log says it fails to unmount system at the end (assert something),so mounts and storage>system still on default status mounted/unmount proposition (no changes)> still same Read-only error if I flash again immediately.

Sounds strange that the rom installation went fine then? Leads to think that this behaviour could come from the rom or at least something on my user's side I guess..
[Galaxy S 4 i9505 Android Development] Phil3759:
I will make small changes to this ****ing time daemon :crying:

Maybe that's the issue. Hope it doesn't kill the time back

Come one guys, a little more effort to donate so that I get this phone before I ditch any work for it like many devs did when not having the phone :p

Check $ USD counter in signature
[Galaxy S 4 i9505 Android Development] Phil3759:
5.11.0

http://d-h.st/users/philz_touch/?fld_id=16685#files

What changed for you:

time daemon implementation (making my life a ****)

Please report if

- gapps installing fixed

- time is still working as previously

- reboot to main system should not power off phone, but reboot to ROM
[Galaxy S 4 i9505 Android Development] bariz143:
Does this new update of your fix the black screen issue when flashing a cm10.2 rom? :)

Best regards!
[Galaxy S 4 i9505 Android Development] Phil3759:
That was fixed in 5.10.9
[Galaxy S 4 i9505 Android Development] bariz143:
Awesome :) thank you
[Galaxy S 4 i9505 Android Development] Bejda:
-Gapps: Fixed

-Time: Didn't really followed that matters don't know if that's the point but time zone etc..that i settled on 5.10.9 are still corrects.

-Reboot system: Works.

Thank you :)
[Galaxy S 4 i9505 Android Development] Phil3759:
Great :good:

Take this as final for cm/aokp/vfat users

Exfat users: be patient if you need faster backups until audism is back from holidays and fixes his kernel
[Galaxy S 4 i9505 Android Development] MRDOCA:
So 5.11.0 not for i9505?

Swyped on my Omega driven I9505
[Galaxy S 4 i9505 Android Development] bariz143:
Yes it is. Just flashed it!
[Galaxy S 4 i9505 Android Development] DroidRevenge:
why this question?

we are in a i9505 thread, i don't understand...
[Galaxy S 4 i9505 Android Development] lzk123:
Confirmation number: 53909208KY897893B

Even though it isn't much, hope it helps you in getting new phone.

Thanks for constantly providing updates.
[Galaxy S 4 i9505 Android Development] Tassos_i:
Backup on exfat 64 (stock tw) is desperately slow (2.5 times slower than with 5.10.0, same temperature, same compression, same data) .

Isn't it possible to have 2 separate versions, one for tw and one for cm?
[Galaxy S 4 i9505 Android Development] dave_p_b:
1 day old phone. So far install CF-auto root and philz touch 5.11.0 (both via odin)

Gapps appear to work ok.

Time in recovery set to London time zone, but is about 8 hours 15 minutes behind. However, unless I keep Automatic date and time enabled (in stock rom) it will reset itself to 02/01/1970 01:00 each time I reboot anyway. Not too much of a problem.

Reboot in to main system appears to work ok.

Thanks for all your hard work. :)
[Galaxy S 4 i9505 Android Development] The1nonly1:
Ive just flashed this in Odin but i cant get it to boot into recovery. i'm holding the volume up + power + home but it justs reboots the phone. When i shutdown and try i get a message saying recovery booting but that doesnt do anything and just powers on the phone. Any help?
[Galaxy S 4 i9505 Android Development] Phil3759:
5.11.0 is for cm/aokp and fat32 users

Read a few posts above
[Galaxy S 4 i9505 Android Development] Tassos_i:
Sorry, it was not very clear for me. By the way, actually all kernel developers try to integrate in their kernels exfat sources that Samsung just released, so do you still have to stick to ausdim kernel?
[Galaxy S 4 i9505 Android Development] Phil3759:
Any other kernel alternative you want to suggest?

I have no S4, so open to any suggestion
[Galaxy S 4 i9505 Android Development] Mr.AFK:
23L94329UT6178115

hope that helps to continue the development :)

greetz mr.AFK
[Galaxy S 4 i9505 Android Development] Joao Oliveira:
Hi,

I've just upgraded to the the latest version and backups to forever to do. Like 45m to backup to a samsung class10 32gb sd card. Fat32.

I was using 5.10.0 and it was already much slower than 5.07.5 but this one is amazingly slow !!!
[Galaxy S 4 i9505 Android Development] Phil3759:
Many thanks for your generosity :good:

You should have read before updating. It's just a few posts above...
[Galaxy S 4 i9505 Android Development] hawkerpaul:
After reading these last few pages I'm slightly uncertain now, so could I ask which version of recovery would be best to use for DjeMBeY MGA Samsung ROM please?
[Galaxy S 4 i9505 Android Development] Phil3759:
jfltexx---> cm/aokp and fat32 users

i9505---> exfat users

i9505 builds are for now not compatible with cm-10.2
[Galaxy S 4 i9505 Android Development] BillGoss:
I'd use 5.10 for all Samsung ROMs.

And if you are using, but not flashing, cm ROMs I'd also use 5.10.

It's only if you are flashing cm 10.2 ROMs that you have use 5.11.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] oliver005:
Dunno how you guys installing CM10.2 with latest Philz, but i'm getting error 7 all the time.
[Galaxy S 4 i9505 Android Development] Phil3759:
Anyone can suggest a tw 4.3 source based kernel with exfat modules for i9505

Until audism is back from holidays, I'm willing to try a new kernel to fix reboot issues
[Galaxy S 4 i9505 Android Development] Bejda:
Probably not related to recovery from a first guess but sure recovery's features can help to know more here.Try to export/show a log by going to advance menu right after status 7 error and use report error(file goes to sdcard/clockworkmod/) or show log options,it may state what's happening.
[Galaxy S 4 i9505 Android Development] oliver005:
Very strange, I tried to install cm10.2 without wipes on stock MGA (I thought it would fail again so I don't have to restore from backup) but it installed right away. I didn't change a thing. So I wiped for clean install and reinstalled cm10.2 again - everything went fine. It didn't want to install yesterday, it didn't want to install today but it did install right now lol ( but the rom didn't boot properly).
[Galaxy S 4 i9505 Android Development] friedrich420:
1. Thank you for EVERYTHING!!! (It's not much but i hope it will get you closer to the Goal... 2B031608HK771572P) :good:

2. What about ktoonsez's kernel: http://xdaforums.com/showthread.php?t=2297379
[Galaxy S 4 i9505 Android Development] Phil3759:
As far as I read, it doesn't support 64Gb exfat cardds. Only audism kernel seems to do so. Unless I am missing something

Problem with stock kernels is their too big size. I need something like wanam kernel, but sadly he doesn't own the device and stopped dev for i9505
[Galaxy S 4 i9505 Android Development] friedrich420:
We all know who to thank for that!! :(

Sorry Phil, my bad... You are right about ktoonesz kernel...
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I'm still getting time issues on latest 5.11 jfltexx sorry.

Incorrect time in recovery (8 hours fast) and my backup was dated 1921-01-01.
[Galaxy S 4 i9505 Android Development] Phil3759:
Probably stock rom users could have issues since it is mainly for cm/aokp

Wait for a version based on stock kernel
[Galaxy S 4 i9505 Android Development] kantjer:
Did you already look at Abyss 1.4.1? There is a 4.3 based kernel incl source code available. And from what I have read the exfat modules are included.
[Galaxy S 4 i9505 Android Development] Phil3759:
5.11.1

http://d-h.st/users/philz_touch/?fld_id=16685#files

Upload in progress

It is still based on audism 4.3 kernel and its exfat modules. However, I made some ramdisk edits to fix adb and some parts of code

Hope this will also fix the poweroff issue on reboot to main system. If not, then it is probably a kernel issue

Else, I'll look at Abyss kernel or revert to stock kernels and remove ntfs... modules
[Galaxy S 4 i9505 Android Development] kantjer:
WOW, your new phone donation counter is growing nicely :good:

Come on guys, keep on donating, and make sure our phones will be able to also use this magnificent recovery in the future :fingers-crossed:
[Galaxy S 4 i9505 Android Development] Tassos_i:
Sent

I don't know about the 4.3 based abyss kernel, but concerning the 4.2.2 one, I can definitely say that upon inserting an exfat formated usb stick in usb-otg mode, my S4 simply reboots...

In a similar configuration, under ktoonsez 's kernel the S4 does not reboot, but does not mount the usb exfat stick...

So, I think we must wait for the inclusion of official exfat sources in these kernels.
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Thanks phil.

Will this mean there may be separate recovery versions for aokp/Samsung rom users in the future?
[Galaxy S 4 i9505 Android Development] zvieratko:
I am unable to flash - everything seems to go fine but it doesn't flash anything - not MODS, not full ROMs either - no error to be seen apart from it finishing way too fast. I am on yesterday's version (5.10.9?)
[Galaxy S 4 i9505 Android Development] Phil3759:
For now, maybe

However, maybe 5.11.1 fixed flashing cm-10.2 roms as i fixed some issues in init filed

Waiting for feedback to see

Also, some devs are working to add a better exfat support to cm-10.2. If it is done, it would make my life easier as no more need to repack with stock kernels
[Galaxy S 4 i9505 Android Development] tata_brada:
For your S4

45J16058H5013661V
[Galaxy S 4 i9505 Android Development] Bejda:
Check two last pages ~ (3 or 4 actually,let's say a few),update to 5.11.0 jfltexx will fix this ;)
[Galaxy S 4 i9505 Android Development] Tanis64:
With 5.11.1

- Timezone mismatch is back

- Reboot to System doesn't work is back

I'm back on 5.11.0 now.
[Galaxy S 4 i9505 Android Development] Phil3759:
Thanks. Seems a kernel issue.

I will wait for audism to look at it. Meanwhile, i could try to fit things with a stock kernel
[Galaxy S 4 i9505 Android Development] spevil07:
same here!!!
[Galaxy S 4 i9505 Android Development] Phil3759:
Many thanks for your generosity
[Galaxy S 4 i9505 Android Development] kantjer:
Time zone is correct for me and also Reboot to system is working OK with recovery 5.11.1

Could this be because I'm also using audism's kernel for my ROM?
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Phil

Is the only reason you don't use the stock samsung kernel because of exfat support?

Just wondering how many of your users use this feature?
[Galaxy S 4 i9505 Android Development] v0dKa.mL:
Ausdim Kernel v13 and your 5.11.1 the reboot now function doesn't work anymore. :( but the Time is working

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] phil.o:
Hi, I am on Omega v9.0 and Abyss kernel v1.4.1 and reboot to system doesn't work here too with v5.11.1.

°° tapatalked °°
[Galaxy S 4 i9505 Android Development] Gotcher:
I very much liked your recovery, I had to switch to the 'normal' CWM though because I wanted to flash the P.A.C ROM on my device...

I just wanted to say that you are doing an awesome job and I hope that you're able to fix this ASAP -- I'll switch right back to your recovery. :)
[Galaxy S 4 i9505 Android Development] Bejda:
Already fixed ;)

Use 5.11 jfltexx
[Galaxy S 4 i9505 Android Development] Phil3759:
Yes, stock kernel has native in kernel exfat support. That way, I can use exfat kernel modules. This makes exfat support very fast

Using a cyanogenmod kernel needs fuse modules, which is currently very slow

Some devs are working over cm team to bring a better exfat support through fuse. I think for i9505 things will be still very slow until some caching is done like twrp. However, that's another big update to cwm code that will need time, if it ever comes

Any yes, many stock users use exfat since 64Gb is by default formatted to exfat in phone

Other reason for i9505, is that 4.3 sources fixed the format partition corruption. Stock 4.2 sources corrupt partitions on formatting and need a special handling.

However, only good 4.3 kernel with proper exfat support was audism kernel

Reboot issue is probably a kernel bug in audism v13. I will maybe revert to v3 until audism fixes it. Or maybe I try the lower versions until we find something working. Hopefully, he will fix it soon as I already contacted him

To sum it:

cm/aokap/fat32 users: you have a very good 5.11.0-

jfltexx

release

stock exfat users: use latest 5.10.x-

i9505

releases until it is fixed

Hope this clears things
[Galaxy S 4 i9505 Android Development] yhrn:
Samsung released their exFAT implementation under GPL a couple of days ago. Won't this mean that all kernels should be able to get native exFAT-support? Sorry if this comment is completely irrelevant.
[Galaxy S 4 i9505 Android Development] Tanis64:
They could not use it, cause part of it is still licensed to Microsoft, without paying for it.
[Galaxy S 4 i9505 Android Development] BillGoss:
[MENTION=4666971]Phil3759[/MENTION]: I've noticed that 5.11 renames old log files so that they don't get overwritten. How many old logs will it keep?

I'm hoping that there's a limit because I don't want to have to clean out /cache/recovery.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
6 files

It is a new feature in stock cwm
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Shouldn't be a problem at as approx only 10kb per log.

It may be an idea to include a "clear recovery logs" option in recovery though phil.
[Galaxy S 4 i9505 Android Development] claireth:
echoe 1.3.1 with ausdim v11...

just to report that reboot to system isnt working...time is correct

other than that,just fine :)
[Galaxy S 4 i9505 Android Development] DroidRevenge:
I think it would be better to write also which TWRP version you have
[Galaxy S 4 i9505 Android Development] claireth:
I'm sorry forgot to wrote it...its the latest 5.11.1!
[Galaxy S 4 i9505 Android Development] DroidRevenge:
10x
[Galaxy S 4 i9505 Android Development] Phil3759:
5.11.2 (19.08.2013)

http://d-h.st/users/philz_touch/?fld_id=16685#files

- report if reboot to main system menu is no longer turning off phone

- if flashing cm-10.2 roms is ok

Many thanks
[Galaxy S 4 i9505 Android Development] SunSide:
Reboot system is working here :)
[Galaxy S 4 i9505 Android Development] Tassos_i:
Is 5.11.2 suitable for tw-exfat? Because backup time is as slow as with 5.11.0, that is 2.5 times bigger than with 5.10.0.
[Galaxy S 4 i9505 Android Development] phil.o:
Reboot system is working here too with newest version 5.11.2 - running Omega v9.0 with KT kernel.

Greetz
[Galaxy S 4 i9505 Android Development] Phil3759:
5.11.2 should have good exfat support, at least in theory

If not, post tests with backup stats

Also, hope it flashes cm-10.2 correctly
[Galaxy S 4 i9505 Android Development] Tanis64:
With 5.11.2

- Timezone is OK!

- Reboot to System WORK!

:thumbup:
[Galaxy S 4 i9505 Android Development] Tassos_i:
(stock rom mga/mh2, odexed)

Backup times (in the freezer, low compression, 2.2GB, exfat 64)

5.10.0 : 9min30sec

5.11.0 : 25 min

5.11.2 : 24min30sec

Please notice that 5.07.6 was 15%-20% faster.
[Galaxy S 4 i9505 Android Development] BillGoss:
So sorry, but it reintroduced the problem with flashing cm 10.2 ROMs.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] loomis:
whatsapp time error after flashing..
[Galaxy S 4 i9505 Android Development] Phil3759:
Thank you

For now, use jfltexx for all cm/aokp things

I won't look at it until i get a new phone. Too much hassle

Hopefully, cm-10.2 is soon stable to be used as a recovery base
[Galaxy S 4 i9505 Android Development] kenzolo:
Hi guys,

I have a problem:

When I try to install a 4.3 based rom with full wipe(I tried different one: pacman,probam..) it flash correctly but when I try to reboot my phone I had a black screen without the bootanimation,after it the phone start without phone signal and imei so I need to restore a backup to fix it.

How can I solve it?

I tried different version of the philz recovery
[Galaxy S 4 i9505 Android Development] tylok:
Philz is great, but as I read in some other forums it is recommended to stick with the original cwm if you wanna flash a 4.3 rom.

I flashed slimbean with the touch-cwm and it is awesome!!

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] Bejda:
Tried 5.11.0?

5.11.0 is ok now if you want to get back using Philz recovery,spread the word ;)
[Galaxy S 4 i9505 Android Development] kenzolo:
yes I tried also this version
[Galaxy S 4 i9505 Android Development] Bejda:
Ah..sorry to insist but sure was the 5.11.0 jfltexx version?

It's a known issue but it went fine with this version for about 10 users i knew or met around here,with any aosp 4.3/cm10.2 based rom's (Slim and Carbon for me).
[Galaxy S 4 i9505 Android Development] DroidRevenge:
which version of recovery?

here all is ok, data and time is ok, i have data and time in auto mode from carrier
[Galaxy S 4 i9505 Android Development] Diabl0z:
I still have same issue even on original cwm
[Galaxy S 4 i9505 Android Development] DroidRevenge:
which issue?

You have to write:

- which issue

- with which version of recovery

if you want help from someone you have to write some info, you have provided nothing
[Galaxy S 4 i9505 Android Development] Phil3759:
As said, use latest 5.xx.x-jfltexx version for cm/aokp.

Stick to 5.xx.x-i9505 for exfat users

Sounds like there's an issue with cm-10.2 installers on stock kernels

When donations reach the counter in signature, i would buy an i9505 for dev to fix all glitches

Only 100$ usd missing, thanks to all supporters
[Galaxy S 4 i9505 Android Development] Diabl0z:
Same ur issues blackscreen without bootanimation and no signal, I tried philz recovery the new one 5.11.2 and I tried new cwm non touch by jamal

My device is I9505
[Galaxy S 4 i9505 Android Development] aka_gk:
Hey guys, I am coming from TWRP recovery, tryed to flash PhilZ with odin - if I leave Auto-reboot in Odin checked, it won't reboot into recovery, if I don't leave it and try to reboot into recovery manually - it's stuck on Samsung logo with blue "recovery booting" in top left.

Then I flashed back TWRP and decided to try to install from zip, flashed PhilZ recovery, rebooted manually into recovery and with quick flash of logo then black screen, phone vibrates and seems to reboot with no blue "recovery booting".

Any ideas what might be wrong?

Also how do you properly boot into recovery? Do you need to keep holding "volume up" up until recovery screen show up? Because I always was letting all the buttons go as soon as blue "recovery booting" appeared.
[Galaxy S 4 i9505 Android Development] friedrich420:
I think I can answer to a couple of parts of your question... but i dont think i can tell for now why you are having these issues... For the 2 parts I have in bold:

1. It shouldnt boot into recovery- it should reboot regularly. The "Auto Reboot" must be checked in Odin...

2. It's pretty much volume up and power and you let go of power as soon as it boots and volume up as soon as you see the blue letters saying recovery booting. Many users claim that you only need to press power and when it boots keep pressing the volume up button until it shows the "recovery booting" message (i actually tried it and it works for me too... less buttons to press all the time)

Maybe you want to try flashing it again via odin and let it reboot once it's done flashing? Im assuming you are getting the green PASS message when its done flashing the recovery?
[Galaxy S 4 i9505 Android Development] aka_gk:
friedrich420, thx for the reply

ah, yeah, you're right

Good point. The problem is, I am using ROM from this thread http://xdaforums.com/showthread.php?t=2348272 and all was fine until yesterday, when I realised that I haven't rebooted since flashed and as appeared phone can't boot back into system. Jamal advised to try PhilZ and here I am. So it won't reboot after odin flash.

May be I should try another ROM which can reboot, then, install Philz and then install 4.3 GE ROM from Jamal I want to use, is that correct?