search

AOSP-JF / issue_tracking_aosp

0 stars 0 forks source link

cache does not stay as f2fs, reverts to ext4 #4

Open jtash opened 9 years ago

jtash commented 9 years ago

I have observed that the cache does not stay formatted as f2fs. It reverts to ext4 after restarting the system. Using twrp 2.8.7.0 to format data, system, and cache as f2fs. Wiping dalvik and cache does not fix the problem. Have even tried doing total wipe of all these partitions, and reinstalling rom from scratch. after reformatting all to f2fs again.

AntaresOne commented 9 years ago

Hi Joe, I installed the latest available build and did not encounter this error. I rebooted many times, no matter of what I did more, after booting the recovery I checked /cache and it still was F2FS as well as other partitions. This was an old bug in the first public release, fixed in the beta 1.

Can you kindly provide more info?

Thank you in advance. Mattia

jtash commented 9 years ago

I have tried TWRP-2.8.7.0-F2FS.zip and the native twrp 2.8.7.0 recovery image.

I attached a screen shot of the about phone information. Best,

Joe

Joseph S. Tash, Ph.D. Professor Dept. of Molecular & Integrative Physiology Dept. of Urology Past-President, American Society for Gravitational and Space Research Mail Stop 3050 University of Kansas Medical Center 3901 Rainbow Blvd. Hixon 1000 Kansas City, KS 66160 office: 913-588-7421 Fax: 913-588-7180 E-mail: jtash@kumc.edu

"The information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer."

On July 18, 2015 7:35:35 PM AntaresOne notifications@github.com wrote:

Hi Joe, I installed the latest available build and did not encounter this error. I rebooted many times, no matter of what I did more, after booting the recovery I checked /cache and it still was F2FS as well as other partitions. This was an old bug in the first public release, fixed starting from the beta 1.

Can you kindly provide more info?

Thank you in advance.

— Reply to this email directly or view it on GitHubhttps://github.com/AOSP-JF/issue_tracking_aosp/issues/4#issuecomment-122608451.

jtash commented 9 years ago

Hi, I noticed that the kernel says allucard and not antaresone in the name. Is that the wrong kernel? I will redownload your twrp and try again. Can i just reformat the cache without having to wipe data and system, or do I need to do a clean install for f2fs to stick in the cache partition ? Best, Joe

Joseph S. Tash, Ph.D. Professor Dept. of Molecular & Integrative Physiology Dept. of Urology Past-President, American Society for Gravitational and Space Research Mail Stop 3050 University of Kansas Medical Center 3901 Rainbow Blvd. Hixon 1000 Kansas City, KS 66160 office: 913-588-7421 Fax: 913-588-7180 E-mail: jtash@kumc.edu

"The information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer."

On July 18, 2015 7:35:35 PM AntaresOne notifications@github.com wrote:

Hi Joe, I installed the latest available build and did not encounter this error. I rebooted many times, no matter of what I did more, after booting the recovery I checked /cache and it still was F2FS as well as other partitions. This was an old bug in the first public release, fixed starting from the beta 1.

Can you kindly provide more info?

Thank you in advance.

— Reply to this email directly or view it on GitHubhttps://github.com/AOSP-JF/issue_tracking_aosp/issues/4#issuecomment-122608451.

jtash commented 9 years ago

Hello AntaresOne, I did some more testing. I thought that converting the extSdCard to f2fs might be a problem. So I took another SD card in exFat and put your AOSP rom zip (AOSP-5.1.1-20150715-jflte.zip) and Gapps (open_gapps-arm-5.1-micro-20150614.zip) on it. I rebooted the phone into your recovery. Did a factory reset, formatted data to f2fs, formatted cache to f2fs, formatted system to f2fs. Went to the install window, selected your AOSP rom and the gapps, then let the install run. On the first boot the “dancing led” did not appear, but the install completed. I set up the phone and got to the home screen. I installed only these apps: diskinfo, titanium backup + prokey, and FX file manager + addons. I rebooted the phone. This time the dancing led was there. I opened diskinfo and it showed data: f2fs, system: f2fs, cache: ext4.

On other thing I noticed, if I select Zip file Signature Verification for the installs, then the “E:Zip signature verification failed: !” error appears and the install terminates. So I disable the verification for the installs.

So it doesn’t appear to be a problem with the extsdcard being formatted as f2fs.

I did the same sequence of tasks but installed one of the cm12.1 nightlies (20150714) and diskinfo showed that both cache and data stayed f2fs, while system was converted to ext4, as would be expected.

This is a sprint L720 phone on the sprint network.

This is frustrating. Do you have an actual jfltespr phone for testing purposes?

Any other suggestions? Kind regards, Joe

From: AntaresOne [mailto:notifications@github.com] Sent: Saturday, July 18, 2015 7:35 PM To: AOSP-JF/issue_tracking_aosp Cc: Joseph Tash Subject: Re: [issue_tracking_aosp] cache does not stay as f2fs, reverts to ext4 (#4)

Hi Joe, I installed the latest available build and did not encounter this error. I rebooted many times, no matter of what I did more, after booting the recovery I checked /cache and it still was F2FS as well as other partitions. This was an old bug in the first public release, fixed starting from the beta 1.

Can you kindly provide more info?

Thank you in advance.

— Reply to this email directly or view it on GitHubhttps://github.com/AOSP-JF/issue_tracking_aosp/issues/4#issuecomment-122608451.

jtash commented 9 years ago

Hi AntaresOne, I was looking at the profiles of members of the JDCTeam and, if I read the profiles correctly, there is no one on the team that is in the US or on Sprint. Since I have a jfltespr (SPH-L720) device and am on the Sprint network, would it be possible to be a tester for this device for your team? I am wondering if the SPH-L720 is different enough from the i9505 and other S4 variants that this underlies the problem with the f2fs for the cache? Kind regards, Joe

From: AntaresOne [mailto:notifications@github.com] Sent: Saturday, July 18, 2015 7:35 PM To: AOSP-JF/issue_tracking_aosp Cc: Joseph Tash Subject: Re: [issue_tracking_aosp] cache does not stay as f2fs, reverts to ext4 (#4)

Hi Joe, I installed the latest available build and did not encounter this error. I rebooted many times, no matter of what I did more, after booting the recovery I checked /cache and it still was F2FS as well as other partitions. This was an old bug in the first public release, fixed starting from the beta 1.

Can you kindly provide more info?

Thank you in advance.

— Reply to this email directly or view it on GitHubhttps://github.com/AOSP-JF/issue_tracking_aosp/issues/4#issuecomment-122608451.

jtash commented 9 years ago

Hello AnteresOne, I was able to make a temporary solution to the problem. I remembered that tkoonsez had an earlier version of twrp recovery (2.7.0.5) that forced f2fs in the cache and data partitions : twrp-kt.all-in-1.zip at this web site: http://forum.xda-developers.com/showthread.php?t=2729915 And the link to the twrp installer zip: http://goo.gl/HLz4al

I installed that recovery over your recovery, and just formatted the cache as f2fs. Nothing else. Since everything else is running fine. When I restarted the phone, AOSP-5.1.1-20150715-jflte was already installed, the cache stayed as f2fs!

If I keep that recovery installed instead of your version of 2.8.7.0, will it interfere with installation of new updates of the JCDTeam AOSP for jflte?

Best, Joe

From: AntaresOne [mailto:notifications@github.com] Sent: Saturday, July 18, 2015 7:35 PM To: AOSP-JF/issue_tracking_aosp Cc: Joseph Tash Subject: Re: [issue_tracking_aosp] cache does not stay as f2fs, reverts to ext4 (#4)

Hi Joe, I installed the latest available build and did not encounter this error. I rebooted many times, no matter of what I did more, after booting the recovery I checked /cache and it still was F2FS as well as other partitions. This was an old bug in the first public release, fixed starting from the beta 1.

Can you kindly provide more info?

Thank you in advance.

— Reply to this email directly or view it on GitHubhttps://github.com/AOSP-JF/issue_tracking_aosp/issues/4#issuecomment-122608451.

B--B commented 9 years ago

It's a really strange bug, my daily device is not affected, i' ve tried several times to format/convert cache and f2fs works... But in my test phone i get your same behaviour... Your solution works, switching to the recovery that you linked solves the problem, and even latest philz f2fs works without issue... But AntaresOne TWRP works well with all other roms.. However, the temporary solution to flash an alternative recovery works (i've added the zip in AOSP addons), but we keep this open until we found what's wrong and fix it.

jtash commented 9 years ago

Thanks

On July 29, 2015 5:09:01 PM B--B notifications@github.com wrote:

It's a really strange bug, my daily device is not affected, i' ve tried several times to format/convert cache and f2fs works... But in my test phone i get your same behaviour... Your solution works, switching to the recovery that you linked solves the problem, and even latest philz f2fs works without issue... But AntaresOne TWRP works well with all other roms.. However, the temporary solution to flash an alternative recovery works (i've added the zip in AOSP addons), but we keep this open until we found what's wrong and fix it.

— Reply to this email directly or view it on GitHubhttps://github.com/AOSP-JF/issue_tracking_aosp/issues/4#issuecomment-126111070.