yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] tobitege:
[MENTION=3874152]zaphodbeeb[/MENTION]

Fyi: your current Tyr56sm-3.5 builds' updater scripts reference "gsiff_daemon" for "set_metadata" commands.

However, comparing to v3.4 that file no longer exists in the v3.5 archives and the original script in k's archive no longer has that line.

----------

Also, with newest 3.6.0 version there are again smaller differences in the set_metadata lines with regard to uid for:

/system/bin/ndc, /system/bin/rfs_access (new!) and /system/bin/wpa_cli

----------

Attached is an updated updater-script which works only for the multi-versions (and only tested with Tyr56sm kernel edition).

I copied the existing boot.img of the 3.5-multi archive into the original temasek 3.6 archive by katinatez as well as the attached newer updater script and I got my secondary Temasek rom updated to v3.6. :D

Edit: removed attachment, obsolete.
[ONE Android Development] zaphodbeeb:
Thanks mate, ill have a play this evening with this. I only had time to produced the 2 p roms this morning, so ill continue with the others tonight.
[ONE Android Development] gnan10:
Camera not able to focus on latest 3.5 rom. No matter what kernel installed, No matter what camera app used.. camera cant focus the subject at all.

reflashed old rom v3.2. works fine now.. please look into this once :)

PS: problem is when 3.5 rom with ak70 installed and also with other kernels
[ONE Android Development] katinatez:
Camera fixed in v3.6
[ONE Android Development] jcespi2005:
Nice ;)

Need more than ten shots to get this one...

Thanks

Sent from my OnePlus One ;)
[ONE Android Development] zaphodbeeb:
Hi mate, thanks fr the help with the script. Appreciated. Ive incorporated it into tonights uploads, which I have just started.
[ONE Android Development] darrie1:
Im on build v3.6 AK f2fs 2p, when I go to settings>display, the settings app force closes
[ONE Android Development] tobitege:
All working fine here (with Tyr installation). Try wiping data/cache for Settings app in Settings|Apps. Was this fresh install or dirty?
[ONE Android Development] azsl1326:
[MENTION=3874152]zaphodbeeb[/MENTION] - Just want to say thanks for the constant updates and keeping all of the files current. It seems like you have a lot of work on your hands and just wanted to let you know your work is appreciated!

Happy New Year!
[ONE Android Development] M5devil:
Does v3.6 come with dark UI?
[ONE Android Development] darrie1:
It was a fresh install, but cleaning data worked. Thanks!
[ONE Android Development] tobitege:
No.
[ONE Android Development] M5devil:
Can't wait... Screenshots look awesome
[ONE Android Development] phermey:
how long should i let this thing boot for. i tried yesterday... but my battery wasn't juiced up. so i went back to my cm12 dailies. i am at twelve minutes right now in the fridge. still on cyanogen boot screen.

edit: i stopped at 19 min and tried a reboot to see if it would boot like it will do sometimes. maybe i am doing something wrong here. i know i am dying to try this mixed rom out. i was all f2fs. using philz 6.59 i switched system to ext4. wiped for a clean install. installed 2p rom. installed gapps. rebooted.
[ONE Android Development] zaphodbeeb:
Way too long. I have had this problem if you dont also select wipe dalvik and wipe cache with Philz. To test a clean install I normally "wipe for a new rom" after formatting system to ext4, and the rest to f2fs. I then usually sideload the rom etc.
[ONE Android Development] katinatez:
Known bug, building v3.7 tonight will have the fix.

No, dark ui will be posted in my thread. It will be flashable when it's ready.
[ONE Android Development] phermey:
thanks. i really messed this thing up. i went ahead and re formated sys to ext4. and cache to f2fs (again). then did the new rom wipe. i reinstalled the rom and gapps. it took two minutes to boot. booted to anddroid password screen. after entering it would not decrypt. so got stuck in bootloop because recovery got corrupted. now all i have is fastboot. which takes hours on my machine to get the drivers right. oh well. at least this forces me to flash philz back on and then sideload your rom and do it right.

edit: well that was a bit more of a fiasco than i was wanting. got your rom booted and everything looks good.
[ONE Android Development] zaphodbeeb:
Sorry to hear you had a hard time, glad you got it sorted
[ONE Android Development] zaphodbeeb:
3.8 tonight with ak latest

Please note there is no 3.7
[ONE Android Development] zaphodbeeb:
Hopefully, I'll get to it once I've cooked dinner. My turn tonight.
[ONE Android Development] otisman:
Life first! And believe good things come to those who wait!
[ONE Android Development] zaphodbeeb:
Hi,

useful f2fs background info here.

http://www.cnx-software.com/2013/01/15/f2fs-a-new-flash-file-system-for-mobile-devices-elce-2012/

http://www.xda-developers.com/android/f2fs-put-to-the-test-against-ext4/

Personally, I have been using fsf2 for sometime problem free. I have yet to do any form of objective testing for a comparison but its always been really smooth and responsive for me, for the many roms I have used. One problem in doing this is only having a single oneplus one at my disposal. Ideally I would like a ext4 and f2fs version, but have been unable to convince my wife of the benefits of this yet.;)

But I keep trying.
[ONE Android Development] davideelde:
Hi guys

Is here anyone who knows how to add the menu button in the nav bar?

Regards david

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Android Development] zaphodbeeb:
No problem mate.
[ONE Android Development] fix-this!:
new build is out now.
[ONE Android Development] störte:
Just saw the link in op. It is still 1.7 right. I mean the standard version

Send by Hyperdrive on one+One

---------- Post added at 01:58 AM ---------- Previous post was at 01:34 AM ----------

Now i have the right Version. Great

Send by Hyperdrive on one+One
[ONE Android Development] zaphodbeeb:
Hi,

sorry my bad. Corrected this now.
[ONE Android Development] OmegaBlaze:
Working great as secondary rom my guy. Thanks for being swift ?
[ONE Android Development] störte:
Just flashed it dirty. All fine

Send by Hyperdrive on one+One
[ONE Android Development] otisman:
Just about to flash thx for that fyi much alohas for update op
[ONE Android Development] magic.hand:
[MENTION=222011]@zaphodbeeb, by formatting

system, cache and data, data/media to F2FS, will it wipe my internal storage as well?
[ONE Android Development] pogi1100:
Yes, you will have nothing on your phone afterwards. You can install .zip files using USB OTG or ADB sideload.
[ONE Android Development] zaphodbeeb:
Yes it will, so backup first. If you are already using the rom on ext4 then you can take a TWRP nandroid first, copy to to your pc and copy it back after the install. You can then use TWRP to restore your data (but only data). Once your on f2fs it seems to dirty flash pretty good, but this depends on what happens to Temaseks/cm12 builds I guess. I expect that some future updates will need the full zap treatment.
[ONE Android Development] magic.hand:
[MENTION=4414119]pogi1100[/MENTION] [MENTION=3874152]zaphodbeeb[/MENTION] thanks for the reply. I will make necessary arrangements for this ext4 to f2fs conversion.
[ONE Android Development] otisman:
Well worth it to me f2fs
[ONE Android Development] störte:
It is getting fast . V1.9 is out :)
[ONE Android Development] fredzen14:
Temasek v1.9 F2FS + Multirom Compatible:

https://mega.co.nz/#!dcImiajT!U0Evt_yIbMDJzNbE0CdSX-GfulI8g60QUW50A5-HEew
[ONE Android Development] Sun_Dancer:
don't work, installation aborted
[ONE Android Development] otisman:
2.0 coming soon I heard I'm stating on 1.8.1 for now then flash 2.0 lol 1.8 is deep sleeps like a pig unreal
[ONE Android Development] dexxa05:
Hi All,

Small question if i use mixed rom wich one do i need?! 2p or 3p?!

Tx in advance
[ONE Android Development] tobitege:
2P variant = "mixed"
[ONE Android Development] zaphodbeeb:
2p (2 f2fs partitions)
[ONE Android Development] Lo4eath:
Hello all,

I must say I like your ROM, very well done!

There's one thing I hate though (mind you, its not related solely to your ROM). I noticed that whenever I use the F2FS format, I get these phantom touches. I can make a video of it if needed. What it does is basically whenever I play around with the phone, once every minute or so there's like 10-15 phantom touches that just press anything. Did any of you encounter/fix this problem ?
[ONE Android Development] dexxa05:
Thx [MENTION=4877142]tobitege[/MENTION] and [MENTION=3874152]zaphodbeeb[/MENTION]
[ONE Android Development] zaphodbeeb:
Thank for the, info above, for keeping us all happy flashers, and for a great rom AND kernel. Have a good new year.
[ONE Android Development] tobitege:
[MENTION=4238642]Lo4eath[/MENTION]: that sounds spooky, haven't seen something like that on any of the last 3 weeks' roms. :confused:
[ONE Android Development] zaphodbeeb:
I recall cm11s had this problem, but not on this ROM. Is it only on this ROM? Sounds as though it could be hware related. Also what flavour of this rom (kernel, f2fsall, primary?).

Does this occur on the ext4 version?
[ONE Android Development] Lo4eath:
Yes, as i said, its not related to this ROM entirely, its the whole F2FS thing... oh and right now the phone just rebooted :/

---------- Post added at 01:45 PM ---------- Previous post was at 01:19 PM ----------

As I said, it occurs for me on all F2FS ROMs, not on ext4. I converted system, data and cache to f2fs. I used the latest AK kernel.
[ONE Android Development] tobitege:
[MENTION=3874152]zaphodbeeb[/MENTION]: updater script in v3.8 is the same as in v3.6, so should be less work for you. :)
[ONE Android Development] zaphodbeeb:
[MENTION=4238642]Lo4eath[/MENTION] Ak 72, or 70?
[ONE Android Development] zaphodbeeb:
[MENTION=4877142]tobitege[/MENTION] Cool. Ty.
[ONE Android Development] Lo4eath:
72
[ONE Android Development] jcespi2005:
Tyr56 or stock is stable for me... aK give me reboots since AK 0.60 and temasek 3.0

Sent from my OnePlus One ;)
[ONE Android Development] phermey:
are either one of those faster than the other? i am quite surprised, and 100% impressed, that this build on ak will hang step for step with the new moto x. if tyr is a bit more responsive than cm i would rather use that. tired of the reboots though. at least turning off ambient stopped most of it.
[ONE Android Development] tobitege:
Running for 2 weeks with Tyr and no random reboots.
[ONE Android Development] f41lbl0g:
I see the 2p v3.8 with ak is not up yet. Can I install the Ty version, then install ak kernel over it? Or would I need to get the ak version from you?
[ONE Android Development] tobitege:
You could flash ak kernel over the Tyr build, yes.
[ONE Android Development] raybit10:
[MENTION=3874152]zaphodbeeb[/MENTION] 3P files are in the 2P folder.

Missing ak and stock 2P files.

Easy on the liquor tonight... ;)
[ONE Android Development] phermey:
so i just did my normal speed test of my home apps on the 2p tyr saber build, side by side with my brother's lollipop x. i got a 43s. he got a 42s. not too shabby zaphod. on the cm 12 full f2fs dailies i hit 50secs.
[ONE Android Development] vonkarayan:
Play Store error 492

Hello zaphodbeeb,

I'm using your ROM since the first release and I'm very happy with it but recently I tried to update Sygic (the navigation app) from Play Store receiving a 492 error.

I've done some research about that: it seems to be related to cache or Dalvik cache (better to say ART cache?) writing problems (like corruption or no space). Not many people talk about this and the most of them find solution in wiping the cache partition, in cleaning Play Store and Google Service Framework data, or wiping Dalvik cache. Unfortunately that's not my case.

I had the same problem when updating a large game (Modern Combat 5) so it seems to me something related to installs working with OBB files. Even the internal update (that doesn't use Play Store network) fails but there's no error message to have any more clue.

Now I'm using version 3.5 (stock) but I'm in this trouble since version 3.0 (AK). Dirty and clean flash obtain the same result. Every partition has plenty of space to work with. No multi ROM stuff, just old friendly single ROM.

I tried to solve the problem by my own but without success (even google failed me) so now I ask to you and to other users with the same ROM if there is a known solution.

Thank you and happy new year! :victory:
[ONE Android Development] tobitege:
[MENTION=1021953]vonkarayan[/MENTION]: this is not the development thread for that rom. Please post your question in the Q&A section of the Temasek rom thread instead.
[ONE Android Development] vonkarayan:
Done, thank you.
[ONE Android Development] zaphodbeeb:
Added green 1.2.0

Hi all,

more f2fs lovliness to play with. Uploading now.
[ONE Android Development] zaphodbeeb:
I thought I was doing such a good job yesterday as well!! Just goes to show that vintage port and uploading roms dont mix. Sobriety and a sore head for me today. Apologies. All should be well now.
[ONE Android Development] M5devil:
Do I only format system on 2P flash or better to format data and cache as well?
[ONE Android Development] jcespi2005:
2P = data and cache on f2fs and system on ext4

3P = system data and cache all on f2fs

Seems system in ext4 is a good combination, as the system partition is read only...

Sent from my OnePlus One ;)
[ONE Android Development] M5devil:
Thanks for the reply! Can I dirty flash by only formatting system? I'm coming from v3.6. Or is it better to do full wipe? Don't feel like reinstalling all apps again
[ONE Android Development] tobitege:
It should work, yes.
[ONE Android Development] mmcneil:
Can't get the latest 2p version to boot with the green machine kernel. I also tried installing the stock version and the gm 1.2.0 kernel separately, but got the same results. Did a clean wipe both times. Am I missing something?

Thanks,

Mike
[ONE Android Development] zaphodbeeb:
Hi,

the "stock" green machine rom is configured to install to ext4. The versions in this thread have been modified to work with f2fs (f2fs-all and mixed configurations), so are not the same. If you try to install the stock kernel it will fail on a f2fs configured device. The green machine roms in this thread do install but not if you have multirom installed. I have published secondary rom versions of the green machine rom also, but they wont work reliably so I'll remove them. Strangely I did manage to get the primary roms to boot with multirom but they started to crash after a few minutes repeatedly and became inoperable.
[ONE Android Development] mmcneil:
Thanks for getting back. I'm not using multirom. When I flashed the version from this thread, my device kept rebooting itself right after the OnePlus One boot logo. I'm gonna try again from scratch and see how it turns out. I'll report back when I'm done.

Thanks,

Mike
[ONE Android Development] jcespi2005:
You can, but always is better a clean install... I use titanium to restore apps and data, quick and secure ;)

Sent from my OnePlus One ;)
[ONE Android Development] mmcneil:
Ok, I did a clean wipe, reformatted the partitions as:

/system --> EXT4

/data --> F2FS

/cache -->F2FS

Rebooted and got a bootloop. Installed the "stock" F2FS-2P with Sensei's kernel, and everything works fine.

Thanks,

Mike
[ONE Android Development] zaphodbeeb:
Hi mate how long are you waiting on first boot? Are you sure your not giving up too early? I have no problems installing from a fresh install without multirom. You can try it on 3.9 Temasek now. Which recovery were you using?
[ONE Android Development] mmcneil:
Hi zaphodbeeb. After flashing, the phone just keeps rebooting itself. It never even gets to the temasek bootanimation. I'll give 3.9 a try. I'll let you know how it goes. Thanks again.
[ONE Android Development] zaphodbeeb:
ok thanks, I like the unix sig lol
[ONE Android Development] mmcneil:
LOL, well I can't take credit for it. I copied it from another user here on XDA.. I just couldn't resist. Ok, still cant get the green-f2fs-2p version to boot. Same issue, I flash it, reboot and it just keeps rebooting itself. I hate to ask this, but would you mind telling me the steps that you use to flash the green version? I've been running your ROM's on F2FS for over a week now and never had a problem.

Thanks again,

Mike
[ONE Android Development] zaphodbeeb:
No problem. Try this.

You will need. This rom. This recovery. This gapps. This Super SU. We will sideload for that very clean install feeling so backup.

So first off download the above to a folder on your pc.

Plug your phone in and copy the recovery to your oneplus. Flash it and reboot into recovery. Then.

Wipe and Format Options -- Custom format options -- toggle f2fs <->ext4 migration -- (should now be enabled). Then format system (select ext4), format cache (select f2fs) and last select data and data/media (f2fs also). I hope you backed up because your device is zapped completely (well almost).

Go back to Wipe and format and select Clean install for a new rom.

Now go back to the opening screen and select install rom, adb sideload (plug in your phone), open a terminal window on your pc.

Navigate to the folder where you got the downloaded files with terminal and type

adb sideload zaphod-green1.2.0-temasek-bacon-v3.9-2P-f2fs.zip in terminal

wait for the flash after upload to the phone. Then reselect adb install on the phone, and type

adb sideload katinatez_gapps-L-signed-11-23-14.zip into terminal, wait for flash

then reselect adb install on the phone, and type

adb sideload BETA-SuperSU-v2.42.zip n the terminal, wait for flash and then reboot.

It takes a little while to boot first time so I get the boot logo, then the screen goes dark (looks like the phone goes off for about 30 seconds, then I get the boot animation, for about 4-5 minutes, and then the phone boots. Be sure to make your settings and then reboot.

Let me know if it works.
[ONE Android Development] tobitege:
"...that very clean install feeling..." - that made my day! :D
[ONE Android Development] jcespi2005:
+1 i know the feeling LOL

Sent from my OnePlus One ;)
[ONE Android Development] gnan10:
Dont know whats happening. something eating internal memory like hell in this rom. Using 2p version. only 2.5gb occupied by apps. and 1 gb of junk files. but in storage and other apps showing like 11.8gb got used. anyone have the idea does what happening exactly ..:crying::crying:
[ONE Android Development] tobitege:
How many roms have you installed (if running MultiRom)?

Each rom gets it's own set of partitions, which takes a lot of GB's. With a root explorer go to /realdata/media/0/multirom/roms and let it calculate the disk usage to find out.
[ONE Android Development] gnan10:
I have installed onlly primary rom. no any secondary roms installed. and there is no multirom folder in the path you have specified
[ONE Android Development] tobitege:
Try free "DiskUsage" app from Play store, which will graphically show you the used data by folder and you can pinch-zoom in/out to see details.
[ONE Android Development] gnan10:
Yes see this
[ONE Android Development] tobitege:
I got seemingly a different app for that, which also allows root access to display /system partition. But anyway, this is only meant as a hint to how you could further investigate the issue and I gave a specific path to look for. Further questions should go into the Q&A section, however.
[ONE Android Development] zaphodbeeb:
F2fs uses memory differently for cache. It does use more than ext4 because it handles it in a completely different way. However that is cache, not internal. Possibly time for a clean install buddy? Especially if you are on multirom.
[ONE Android Development] phermey:
ak build seems stable. no reboots since i installed last night.
[ONE Android Development] zaphodbeeb:
Hi,

I got reboots on 0.74 and Temasek 3.9 unfortunately so I think you may just have been lucky.
[ONE Android Development] phermey:
i don't mind being lucky. :) except now you have me feeling like i spoke too soon.
[ONE Android Development] zaphodbeeb:
It seems a bit mixed ATM. In the AK thread it seems some are reporting no probs, other still have them. I'll continue to update and include in this thread however, as Im sure AK will crack it, and anyhow, people that have their phones f2fs style may still want to try it or not have a problem with it, or just try to help investigate/solve it Fingers crossed wont be too long before its resolved.
[ONE Android Development] jcespi2005:
4.0 is out ;)

Go go go

Sent from my OnePlus One ;)
[ONE Android Development] M5devil:
In my case and few others have reported as well, reboots on AK are linked to Ambient Display
[ONE Android Development] katinatez:
Also v4.0 brings F2FS updates
[ONE Android Development] jcespi2005:
Nice dome mate ;) will test ASAP

BTW, back to 2.8.1.0, 2.8.3.0 reboots a lot...

If you need logs, catch me...

Sent from my OnePlus One ;)
[ONE Android Development] katinatez:
Yea, I will be updating recovery on my weekend.
[ONE Android Development] mmcneil:
Well, that did the trick!! It works bro. The difference between what I was doing and what you outlined was:

1. I wasn't re-formatting /data and /data/media. I was just formatting /system as ext4 and /data and cache as F2FS

2. I didn't install via adb sideload.

Now when it comes to updating to a newer version; should I dirty flash or wipe everything and flash from scratch? What I normally do is factory reset, then clean to install a new rom, using Philz Touch. Finally, for the Green Machine kernel, can I use UKM and Synapse or is there something else to use to tweak it? Thanks again for all of your help.

Mike
[ONE Android Development] phermey:
sideloading was my issue also. it worked like a charm once i did. i am also dirty flashing the dailies with no issues.
[ONE Android Development] zaphodbeeb:
Dirty flashing is normally ok, however, as per the ext4 equivalent, this can cause problems, so be prepared to clean flash if necessary. At least wiping cache/dalvik is a good idea before updating. If data is of value, nandroid it, and copy it to your pc. If your going from one kernel to another, just try it, it mostly works, but sometimes not. I keep synapse and trickster apps permanently installed on my phone. Some kernels work better with one or the other, as is detailed in their threads. Do however be aware that the AK special edition of UKM script is just that, for AK. Use the synapse script from the main support thread for other kernels.

ADB sideload is not mandatory, it was just easier for me to suggest that method to ensure a squeeky clean install. Please we sorted it.
[ONE Android Development] raja_mastana:
Guide - OnePlus One - How to Convert to F2FS filesystem

[YOUTUBE]8BWSf7yABXg[/YOUTUBE]
[ONE Android Development] mmcneil:
Thank you so much for all of the feedback and assistance. Keep up the good work on all of this.
[ONE Android Development] M5devil:
Is AK flavored 4.0 coming as well?
[ONE Android Development] zaphodbeeb:
Nope. Just flash the latest AK. It works on any f2fs/multirom combination now, as do Sensi, and Tyr kernels. If you want to flash f2fs for the first time to get AK install the applicable stock/green machine rom and then the AK kernel. I'll only be providing modified roms when necessary to get them working on f2fs with Temasek.
[ONE Android Development] zaphodbeeb:
Cool mate. Great work. I've added a link from the OP.
[ONE Android Development] M5devil:
Something is up with my TWRP 2.8.3.0

I try to boot to recovery and on TWRP logo all I see it says loading and after a little bit it just reboots back to Android. WTF?! how do I update the ROM? Could it be that my battery is less than 15% and it's a preemptive measure? Never had this before
[ONE Android Development] azsl1326:
I had a similar issue with TWRP. The logo screen would stay on a long time and then it would just reboot without going into recovery. Tried several times and couldn't get into recovery. Even reflashing TWRP didn't work. Flashed new recovery, Philz, and now I don't have any issues with recovery.