yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] tobitege:
Running Tyr kernel v55(SM) on this rom edition in both a primary and a secondary ROM install.

The first one is just a barebones installed version as a "fallback" (boots fast; nandroid copyable via MTP; only apps like SuperSU/TB/Flashify/FX; nandroid 520MB).

The second is a fully configured install with all of my apps+data (nandroid 3.1GB).

In neither of those 2 installations I experienced random reboots in the past 12 hours or so. Just a datapoint.
[ONE Android Development] zaphodbeeb:
I think there are problems with ty55 with running on this rom as primary. Secondary works fine, but it doesnt swap to or run on primary. I think its to do with linux enforcing with cm12 now. Ty54 is good tho. Thats why i dropped it from the op.I will investigate further tonight. Maybe the latest version of the rom resolves the problem.
[ONE Android Development] mrdoubleb:
Correct! I installed AK0.65 last night and its much more stable just dirty flashed it works great.
[ONE Android Development] gd6noob:
Anyone else have mounting and unmounting when install in F2FS?

Iam using katinatez cm-12-20141222-UNOFFICIAL-temasek-bacon-v3.1.zip.

Also something about it was using old binaries when installing GApps and AK kernel...

Thanks for the help
[ONE Android Development] gnan10:
UPDATE

: AK kernel v65 prevented random booting issue. stable for now :):)
[ONE Android Development] anupsnair:
Fixed

AK 65 fixes the random reboot, as well as the deepsleep, or rather not coming out of the coma. :D [MENTION=3685904]ak[/MENTION] [MENTION=3874152]zaphodbeeb[/MENTION]
[ONE Android Development] zaphodbeeb:
Sorry for my lack of time on the thread. I have been doing some work with other kernels and getting Tyr working with CM12. All good now. Lots more f2fs lovelyness comng soon. 3.1 is running like a dream, any kernel now, unless you know different?

Ive got a much better toolset now for producing the roms, so lead times should be much shorter from release to these roms being published.
[ONE Android Development] Guido83:
my phone reboots every 10minutes on v3.1 with AK0.65

3.0 was much more stabele on my phone
[ONE Android Development] raybit10:
Hey [MENTION=3874152]zaphodbeeb[/MENTION] , thank's for 3.2... (just clean flashed now)

Is it on purpose that you didn't included AK 0.68? Is it beta or something like that and thats why its not on AK's thread? Can I dirty flash it?

One more thing and that's for all.....

Do you know why for the last 10 days my google backup is not being updated and when i clean flash, the play store downloads my old apps and then i need to update them as well?

The only thing i can remember i have changed during this time is un-checking the box that asks to keep sending reports to google for improvements... hhhh and i don't think they hold a grudge for that...

Edit: Maybe it's relevant... I also use PA Gapps Modular Nano (12-18-2014)
[ONE Android Development] ak0r:
where can i get proper guide to convert to f2fs? I did searched but couldn't find.
[ONE Android Development] mrdoubleb:
No guide needed really, in recovery u can reformat the partitions to f2fs and your done.
[ONE Android Development] DerRomtester:
There is a guide in general section.

Read it carefully it will wipe your hole data. But also follow rom instructions.

For non experienced users a guide is helpful.
[ONE Android Development] zaphodbeeb:
Hi mate, I didn't include Ak 0.68 because I hadn't had the time to install it even. Lol. I'll update to it in the next release. I also have noticed the restore probs. I do much flashing, and it is completely inexplicable to me. Sometimes the great god Google provides this, sometimes not. Make sure to zap everything including factory reset. I also think it helps to give the big g a little time when first setting up the account so that sync completes fully before restoring apps. It is a real pain. It is beyond me how hasn't managed to make this bullet proof Can't see it could be that difficult for them.
[ONE Android Development] zaphodbeeb:
PS I forgot to say. Just dirty flash ak0.68 onto this ROM. Works fine. No need to wait for me to update
[ONE Android Development] azsl1326:
Just flashed latest along with ak68 and got the sleep of death - phone won't wake up. Forced to do hard restart.
[ONE Android Development] raybit10:
Thanks for your reply.

Edit: Just noticed that google calander also isn't syncing. With you as well?

Sounds concerning... :rolleyes: ;)

Did you flashed the 0.68 straight after rom or you gave the rom first boot and then went back to recovery?
[ONE Android Development] azsl1326:
Wiped delvik and cache. Flashed ROM individually then flashed kernel. Wiped delvik and cache again. Back on AK 50 now with no problems.
[ONE Android Development] clutterking:
I'm getting a symlink error while trying to install via the latest TWRP. Can anyone help?
[ONE Android Development] azsl1326:
Try wiping cache and delvik first before flashing.
[ONE Android Development] tobitege:
That doesn't work for the symlinks in the updater-script.
[MENTION=3874152]zaphodbeeb[/MENTION]: having done a file comparison between your updater-script from yesterday's 3.1 ak version with the one from original temasek archive, there are quite a few differences regarding symlinks, iirc. I had the same issue as [MENTION=882115]azsl1326[/MENTION] reported and after some playing around with updater-script, it no longer threw errors in recovery.

What do you think, any ideas how to approach this?
[ONE Android Development] azsl1326:
So, I had the symlink issue and wiping the cache/delvik worked for me with the caveat that I only flashed the ROM by itself on TWRP. When I attempted to flash multiple zips, it would fail with the symlink error.
[ONE Android Development] tobitege:
Strange thing, I can't remember having had this issue since I started with 2.8.x versions.
[ONE Android Development] zaphodbeeb:
Im not getting all the info I need to help. For install problems I need to know:

If we are talking dirty install then

- What rom/version you had installed. Along with details of what else was flashed (at least kernel version etc)

- What version you tried to flash (there are 8 of them now and they change rapidly so please state the exact version), and how you tried to flash. Then I have a chance of helping. I also need to know what else was flashed (both for dirty or clean) i.e. gapps, super su etc.

I test all releases as follows when Katinatez releases a new version:

When 3.3 is released and I have produced the roms I will first try to install over a 3.2 install with the same kernel range. (i.e. AK, stock, tyr). If it fails a dirty install but installs correctly as a clean install, I will advise on this in the OP.

I dont(cant) do full regression testing i.e the latest version against all past versions. You can try to skip releases but I havnt tested for that. If it works, great, but if it doesnt then I cant really help other than to recreate and confirm that it doesnt work, and recommend a fresh install.
[ONE Android Development] zaphodbeeb:
Sorry but by multiple zips, do you mean you flashed the rom, them immediately flashed gapps and got the error?
[ONE Android Development] zaphodbeeb:
Yes thats not a rom in this thread. Temaseks roms are configured to install to ext4 not f2fs. The roms I provide work with f2fs (but not ext4).
[ONE Android Development] itsdacj:
This ROM is absolutely fantastic. Has all the features I missed in Lollipop and more. The only compromise from KitKat right now is battery life, all it needs is a little optimisation in CM12S to be integrated then we're done. Great job Temasek!
[ONE Android Development] zaphodbeeb:
Hi,

I just flashed this successfully. This is what I did.

1. started with a working (booted) AK0.65 installed rom with supersu installed.

2. went into recovery and flashed AK0.68

3. rebooted. All ok.

Did you do anything different to this?
[ONE Android Development] zaphodbeeb:
That could be the problem. Let the phone boot with AK0.65. Then go into recovery and flash AK0.68.
[ONE Android Development] temasek:
Let me do a correction

Whoever builds from my sources, so long the kernel fstab indicates multiple fs on a single mount point, my rom will support.

Example

Temasek Kernel for hlte supports both ext4/f2fs

Hlte ext4 user flash V3.2 (hlte) - works

Hlte f2fs user flash V3.2 (hlte) - works

So no matter ext4 or f2fs users can actually use the same rom build with the same kernel without any updater-script modifications. It works out of the box. It all depends on the kernel to include this feature. This excludes your device multirom feature though but I should work the same.

That's what I'm trying to get across this msg to [MENTION=3814731]katinatez[/MENTION]

Temasek rom is multiple fs on a single mount point ready.
[ONE Android Development] azsl1326:
I will try that and let you know.

Thanks.
[ONE Android Development] zaphodbeeb:
Really cool. So if I set it for both ext4 AND f2fs in the same fstab it will work on either? Does that also mean that if I had, say system partition as ext4 and data and cache as f2fs then it would still work with the same fstab? Thanks.
[ONE Android Development] temasek:
Frankly /system with f2fs is not really helping.

F2fs is beneficial for writes than reads.

I would suggest kernel dev to use f2fs for /data and /cache only so that no modifications to CM scripts are necessary.

See my extracted fstab

/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,noatime,nodiratime,data=ordered,barrier=0,nodiscard wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc,nodiscard,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nodiratime,background_gc=on,nodiscard,nosuid,nodev wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs	noatime,nodiratime,background_gc=on,nodiscard,nosuid,nodev wait,check

See the above? It has 2 lines for /data and 2 lines for /cache. That will do and no modifications required for cm updater script.
[ONE Android Development] zaphodbeeb:
Cool, and thanks again. I think another varient is on the way. I'll have a play with this. I tested this with a couple of other kernels and it works also. Maybe a performance version(s)!:good: Thanks again
[ONE Android Development] azsl1326:
Followed your instructions. However, I also uninstalled Synapse and was going to do a 'clean' install from the market. However, I never got that far as I got the "Sleep of Death" again - phone doesn't wake up.
[ONE Android Development] zaphodbeeb:
Was ak0.65 installed by flashing my ROM from this thread. Also what recovery are you using?
[ONE Android Development] azsl1326:
Yes, flashed the latest version of this ROM with v .65. Left the phone unattended for a few minutes - no tweaks to Synapse as it wasn't installed and phone wouldn't wake up. Flashed v .68 and same thing...left unattended a few minutes and was unable to wake the phone. I went back to v .50 and everything is fine again.

I am using TWRP 2.8.3

Thanks!
[ONE Android Development] katinatez:
Soon no more editing fstab in kernel, with [MENTION=2332422]temasek[/MENTION] guidance I think I got it! Just waiting for temasek to give me the thumbs up on my commit. What this commit means users just have to convert file system with recovery and flash!

https://github.com/katinatez/androi...mmit/3f7d9046788d873728e41858fa72802dfad583db
[ONE Android Development] temasek:
V3.3 ready for building.

See PM for reply.

Good luck.
[ONE Android Development] raybit10:
Same thing that happened to me except i use Philz recovery.

I posted logs in ak's kernel thread.
[ONE Android Development] iVolcaNoz:
Where can i download g apps for this rom?
[ONE Android Development] tobitege:
PA gapps

gianton's gapps

BaNkS's gapps (lightweight)
[ONE Android Development] mudi12:
Hi

I have formatted my mobile to f2fs using philZ

Then I flashed your ROM along with gapps

zaphod-AK0.65-temasek-bacon-v3.1.zip

Slim_full_gapps.BETA.5.0.x.build.0.x-434.zip

Everything works fine but phone keeps restarting after sometime

Also sometime when i locked phone then try to unlock screen stays off and I had to do hars restart it happend 3 times

I tried flashing again by formating system cache and data and wiped dalvik cache still same result

I have flashed only two zip files mentioned above
[ONE Android Development] tobitege:
If applicable, try to disable any CPU related mods. Then also try to flash Tyr kernel v55, which is very stable on temasek.
[ONE Android Development] jcespi2005:
Happen to me also, seems AK 0.6x thing, using stock kernel on v3.1 and all is fine...

---------- Post added at 10:50 AM ---------- Previous post was at 09:57 AM ----------

Not sure its just me, but for mated system to ext4, installed v3.3 with data and cache on f2fs and bootloop on boot animation....

Back to f2fs on system and flashed v3.2 working again....

Sent from my OnePlus One ;)
[ONE Android Development] raybit10:
"Start download -> OOPS! No mirror found".

(When trying to download 3.3 ak 0.68)

Edit: It's all good now (one mirror found)
[ONE Android Development] gnan10:
Won't be there any changelogs available for this rom??
[ONE Android Development] zaphodbeeb:
Please read OP with regards changelogs
[ONE Android Development] zaphodbeeb:
Xmas day special ak

Hi all,

a xmas day special. Try this.

1. format cache and data to f2fs

2. format system to ext4

3. flash the zaphod-AK0.68-temasek-bacon-v3.3.1-2P-f2fs.zip.

In theory, this optimised configuration should give the best performance possible as it leverage’s the relative strengths of both ext4 and f2fs for the best use (and therefore greatest performance). All the roms in this thread are configured to support a pick and mix approach to enable the best performance (i.e cache, data and system can use ether f2fs, or ext4 type partions). Only AK's kernel is currently capable of capitalising on this capability, but Im sure other kernels will follow. Anyhow give it a try, and provide feedback. Gotta go, got a BIG turkey to cook, for a cast of thousands today! Happy xmas. I'll be maintaining (ie testing) this configuration as part of ths thread from now on.
[ONE Android Development] otisman:
Go eat up you deserve it zaphodbeeb! Merry Christmas too you and yours and the rest of the f2fs family much alohas Rob
[ONE Android Development] zaphodbeeb:
see op
[ONE Android Development] tobitege:
[MENTION=3874152]zaphodbeeb[/MENTION]: first, thanks for the latest 3.3.1 update, appreciated!

For my purposed I've re-done a file compare between the updater-script of the original 3.3.1 archive to the one included in your Tyr-Multi archive.

I've added more screen logging to mark several steps (with ui_print) and added several "set_metadata" lines from the original file.

The extra screen output logging might be helpful in case of flashing failures, which happened to me once where it stopped with some "symlinks missing" error and I had tried to trace back where it had stopped.

Attached is my updated version (only tested with Tyr-Multi 3.3.1 variant!) in case it is of any value to you. In case I shall remove it, please let me know.
[ONE Android Development] danhii:
Thanks! Amazing rom:laugh::laugh:
[ONE Android Development] zaphodbeeb:
e

Thanks mate. I'll have a play with this when producing the next batch of roms for release. There will be a Tyr update and possibly another 2 partition varient for Tyr. I havnt really started on multirom varients for these but when I have more than 1 option of kernel I may give this a shot also.

I really have not done much with the multi updater script since the last version of it was released (4th December) so ts about time I reviewed it. Thanks again for your work.
[ONE Android Development] rookawa:
Save images via browsers

Hi,

First of all, great work on what you have done for us, OP. Does anyone here have problem when saving images via browser? It's happen to me on both Firefox and Chrome. When try to save images it's saying download failed. I'm on 3.3.1 Performances with ext4 on /system(of course!) but also happen to me since 3.1 Standard.

Can anyone try it and let me know what you seeing? if it already documented somewhere please help to point me to it. plz!! Thanks.

Solved, Download folder was created in Recovery. Then having some permission access issues.
[ONE Android Development] azsl1326:
Got a random reboot on v3.3.1 with Ty55-linaro

Last_kmsg:

https://app.box.com/s/dbkd0lsq7ivsfjo16r66

Logcat:

https://app.box.com/s/ha37o9g202dmg7wigsj3
[ONE Android Development] tobitege:
Probably need to report this in the kernel thread instead together with governor/frequency details.
[ONE Android Development] azsl1326:
I did and he stated that it was a ROM issue - http://xdaforums.com/showpost.php?p=57764345&postcount=600

Not sure who is right...just trying to provide helpful information..
[ONE Android Development] DerRomtester:
I am not sure yet. I am currently testing cm11.

I will report back if there are any reboots.
[ONE Android Development] tobitege:
Had not one reboot with v55 and this Rom in the past days, feeling happy+lucky. :)
[ONE Android Development] amjath:
[MENTION=3874152]zaphodbeeb[/MENTION] please add gestures when the screen is off. It was very useful when running other lollipop ROMs.

Edit: I wanted to test screen pinning today, I cannot unpin the app now please help running AK performance ROM 24/12 build

Bug Report:

1. Screen Unpinning is not working with hard buttons [possible only with soft/onscreen button]

2. When I turn on On-Screen buttons, the hardware button also works
[ONE Android Development] raybit10:
Which other lollipop roms have screen-off-gestures?
[ONE Android Development] tobitege:
This is not the development thread, please report bugs here.

Probably meant Kitkat ones.
[ONE Android Development] amjath:
liquidsmooth has it

https://forums.oneplus.net/threads/rom-android-l-near-stock-liquidsmooth-install.185669/

Will do it
[ONE Android Development] zaphodbeeb:
Hi mate, please investigate/report rom bugs n Katinatez's thread.
[ONE Android Development] :
Are there different versions of the AOSP messaging app? I am finding some versions have a lot more features.
[ONE Android Development] zaphodbeeb:
3.4+ updates tonight. Family stuff today.

Ak, katinatez etc updates coming tonight (UK).
[ONE Android Development] M5devil:
guys do I have flash AK kernel too or the mixed F2FS/EXT4 Rom already includes it? It's not clear from the OP as it jumps from STEP 2 to STEP4. Is that just a typo?
[ONE Android Development] zaphodbeeb:
Already included. No need to flash Ak separately.
[ONE Android Development] M5devil:
Thanks! This is my first time trying F2FS version of this amazing ROM. Had an issue sideloading the ROM, but all good now. For some reason Location ICON is showing on the status bar, wasn't there before. I flashed SLIMS full gapps. I was using PAs version of gapps before.
[ONE Android Development] azsl1326:
Currently running 3P F2FS. I assume that if I want to switch to 2P F2FS / 1P EXT4, when I format system to EXT4, I will need to reinstall all my apps, etc - almost like a clean install?
[ONE Android Development] tobitege:
If you only reformat the /system partition you can just flash the rom again right after it.
[ONE Android Development] azsl1326:
[MENTION=3874152]zaphodbeeb[/MENTION], you have two files with the same name on the android file host download page, "zaphod-Tyr56lin-temasek-bacon-v3.4-2P-f2fs.zip". Assuming one of those is supposed to be 3P?
[ONE Android Development] tobitege:
There are several duplicates for 3.4, in case of "zaphod-Tyr56sm-temasek-bacon-v3.4-3P-f2fs" and "zaphod-Tyr56sm-temasek-bacon-v3.4-2P-f2fs" they are identical.
[ONE Android Development] M5devil:
Guys, already encountered 2 weird SODs.

One with h/w keys on and another everything is just dark. Nothing works and hard reset with all 3 buttons is the only way out.
[ONE Android Development] gnan10:
Can't open 3.4 version rom's link..

Please provide some other mirror

Thank you☺
[ONE Android Development] zaphodbeeb:
Hi, having much pain and woe uploading tonight. The files seem to be uploading now to the folder shown in the OP.
[ONE Android Development] zaphodbeeb:
Hi, please advise as to which rom.
[ONE Android Development] M5devil:
Mixed with AK
[ONE Android Development] zaphodbeeb:
Apologies, ive had some problems uploading tonight. Im uploading to a new folder to avoid any possible duplicates.
[ONE Android Development] M5devil:
After I hit send, phone rebooted by itself a minute after
[ONE Android Development] zaphodbeeb:
Yes, I think there are still reboot issues with ak70 unfortunately.
[ONE Android Development] M5devil:
I'm still on mixed with ak68. Hopefully ak finds the culprit
[ONE Android Development] raybit10:
Hey mate, just flashed "zaphod-AK0.70-temasek-bacon-v3.4-2P-f2fs.zip" and when looked in settings -> about, i see kernel is stock... :confused:

FYI

Format /system (ext4)

Format /Cache and /Data (F2FS)

Flash ROM

Flash PA Gapps

Flash UKM

Flash SuperSU
[ONE Android Development] :
Hi I am somewhat confused, the 2p or the 3p is the mixed partition one with ext4 for system and f2fs for the rest?
[ONE Android Development] tobitege:
2P has 2 f2fs partitions (data+cache), 3P has 3 F2FS partitions.

Edit: correction needed
[ONE Android Development] sax0406:
I have system as ext4 and rest as f2fs. So should I use 2p or 3p?
[ONE Android Development] tobitege:
2P then (system is ext4).
[ONE Android Development] zaphodbeeb:
2p(partitions=data & cache)
[ONE Android Development] zaphodbeeb:
Just a note. I havnt even tried to change any other partitions other than system, cache and data, so I dont recommend setting them all to f2fs.
[ONE Android Development] zaphodbeeb:
Yes, more apologies in order. I got a little too clever for my own good, tryng to automate the production of the roms. I have fixed now and both 3.4 and 3.5 are correct.:o
[ONE Android Development] tobitege:
No Problem, Zaph. Enjoying your builds.
[ONE Android Development] raybit10:
Do you mind clarify this note.

Is it the same recommendation as you noted in the OP?

I follow your suggestions throughout the thread but can you please explain the change that we did from 3P f2fs to only 2P f2fs... What are we gaining (or maybe loosing) with /system as ext4?

No need for apologies! hhh... ;) I knew it was an unintended mistake, just wanted to let you know.

I guess i downloaded the Stock kernel 2P so i went and also download AK kernel and flashed on top (seem to work well so far).

By the way... Love the new method of organizing the files.
[ONE Android Development] gnan10:
Man please try to explain in normal way. not even understanding what you are actually trying to xplain :(
[ONE Android Development] M5devil:
Any chance to add volume setting to the power menu? I'm seen it in some other CM12 ROM I think
[ONE Android Development] zaphodbeeb:
Hi, try requesting/researching in Katinatez's thread. Lots of really helpful people there. You may well find that they already have an answer to your request. I The roms in this thread will always be as true to Katinatez's roms as possible, just f2fs flavour.
[ONE Android Development] gnan10:
Red all the OP. couldn't find the changelogs. sorry if my mistake. pls post the link
[ONE Android Development] phermey:
giving this thing a shot. i hear great things about the temasek builds. the cm12 dailies that i have been on are quite good for early stages. hoping to see if the mixed dealio makes things even better. thank you for your efforts.
[ONE Android Development] zaphodbeeb:
Changelogs are in the AK, Katinatez, DeRRomtester threads. The roms here just pull these components together. There is a changelog for each thread.
[ONE Android Development] zaphodbeeb:
Check out with Antutu. I get a higher score on Antutu with system using ext4. This is because ext4 is better for reading smaller packages of data, which is exactly the scenario your system partition caters for. It makes about 1500 points score difference.