yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] zaphodbeeb:
Great improvement in performance with the 4.6 special edition (out of the box) in f2fs-mixed mode over the other 4.6 versions. Time will tell from a battery viewpoint.:)
[ONE Android Development] azsl1326:
So, should I flash both the CM 12 modem and then the alpha modem or just the CM 12 modem?

---------- Post added at 04:37 PM ---------- Previous post was at 03:54 PM ----------

I might have to do this as I am getting FC for phone after installing the nightly modem and then the alpha modem. For the time being I went back to the previous modem 44s and I do get a signal - although as previously mentioned my proximity sensor is borked so that won't work for very long.

Just to confirm if I reformat data, this will wipe my SD Card, correct?
[ONE Android Development] tobitege:
Only one of the modem zips needed. Sorry for my unclear wording.

Yes, formatting /data will indeed erase your internal SD card (at least the part you can see via MTP for example).
[ONE Android Development] azsl1326:
No problem - I appreciate your insight. No matter which modem I try and flash, I get FC for phone along with no signal. Any idea as to why flashing the CM Nightly resolves the issue? Is my only solution to flash the CM Nightly and then reformat the file system and then flash 4.6?
[ONE Android Development] tobitege:
From what I've read, it may either be provider- or location/country-related issues with the modems OR that the CM-12 nightlies just flash more partitions in addition to those 2 files in the zips. Right now I'd also go with flashing the CM-12 nightly and right afterwards do the usual install. Good luck! :)
[ONE Android Development] raja_mastana:
Following the guides on page 46, I modified the v4.6 special edition ... to be more special - f2fs support and AK 0.8 kernel

No issues till now

Thanks
[ONE Android Development] zaphodbeeb:
Cool but you could have downloaded the special edition version from this thread and just flash AK over it. However, I guess you have produced an All-in-one style rom with embedded AK0.80? AK uses anykernel to flash, so it reads the environment its being installed into and sets up the fstab to that automatically. Just thinking about producing an anykernel version of Temasek stock kernel and how to implement it in these roms. Pleased the post was fit for purpose. Thanks for the feedback.
[ONE Android Development] azsl1326:
So I ended up using this method and it worked well - albeit it definitely took me more than 20 minutes :( I am sure that there are some shortcuts I could have taken that would have sped up the process. All is working well now with phone/modem.

Thanks for the insight.
[ONE Android Development] zaphodbeeb:
No problem. I think the solution here is in the fact that other partitions are also flashed with cm12. Sorry it took longer than I suggested. Producing these roms each night means that I am an expert in high speed flashing. Just watching the last two roms for 4.7 uploading now, so I can put the kettle on then.
[ONE Android Development] papajonpizza:
I was also one of the people having problems flashing the OPO_L5_alpha-modem (FC's, no cellular data/LTE, etc.) and kept having to go back to the CM-28112014-modem.

The CM12 nightly was the solution. These are the steps I followed and I agree with zaphodbeeb that it is possible it could take only 20 minutes.

No wipes!

Flash the CM12 nightly ROM (which formats /system as ext4 and loads the new modem)

Reboot (and expect a boot-loop or stuck boot)

Power-VolumeDown to go to TWRP

On TWRP, format /system as F2FS. /cache and /data should never have changed format

On TWRP, flash Temasek F2FS 3P (it's been normal for me to do it twice as it errors the 1st time)

Flash gapps and SuperSU 2.42

reboot to system and arrange icons, but all settings should be intact

profit. (new modem installed and proximity sensor working)

Thank you very much, zaphodbeeb, for this F2FS version of Temasek ROM for the bacon.
[ONE Android Development] Criton30:
CM12 nightly modem is the same as alpha modem? Because the size and md5 is the same.
[ONE Android Development] papajonpizza:
I downloaded OPO_L5_alpha-modem from several places; and always checked the MD5, and flashed the .zip on TWRP, and also tried flashing using fastboot (after extracting NON-HLOS.bin) and also using different version of Temasek. All the same results, FC's and no cellular data, but about phone shows it installed. CM12 nightly flashed the modem and I don't have the problem. Dunno why...
[ONE Android Development] zaphodbeeb:
correct. However, following the above fixed it for me. I dont know why, but Im pleased it did;) I had similar problems in the days of stock 33 rom and modem update. Flashing the full stock rom worked for me then. I suspect its a change implemented in one of the other partitions with the full flash.
[ONE Android Development] nico53laval:
For me, coming from 3.8 dirty flashing 4.6 and the cm12 modem worked
[ONE Android Development] smint86:
Am I getting it right? You had system, data and cache f2fs, then flashed CM12 nightly on top. This resulted in updating modem and necessary files and formatted system to ext4, while data and cache were not touched at all.

This would mean there is no need to save data/media and formatting it to ext4 in prior to flash CM12 nightly?

For example if using 2p version (system as ext4 anyway):

- nandroid

- flash CM12 nightly

- restore nandroid

- flash back ROM of your choice

- have all advantages from updated baseband and stuff ;)

This would save a lot of time for f2fs users, needs confirmation though.
[ONE Android Development] phermey:
same. coming from 2p 3.9 ak to 4.6 sp.ed., i dirty flashed the rom, cm12 modem, and then ak 8.0. no issues.

edit: i thought it was fast before. just trimmed another half to full second off the time. i wish i wasn't rebooting when trying antutu.

stopwatch/settings/about phone/play music/calc/maps/youtube/play store/hangouts/load convo/chrome/load espn and wait for 'ticker'/gmail/phone/phone keyboard. in under 35 secs.

this could be faster. the load times are much much better. but the touch response and animation speeds seem a bit slower. for instance... calc is fully loaded by the time i am able to see it. it is a good quarter second longer to load.

---------- Post added at 08:16 AM ---------- Previous post was at 07:32 AM ----------

i am on the same. only i am using 2p. it took a minute though for me to get antutu to fully run. it booted on me three times. then after i ran my speed tests... it just worked. 50,193

http://img.photobucket.com/albums/v383/needajoint/Screenshot_2015-01-09-08-03-55_zps0b4c46b8.png
[ONE Android Development] papajonpizza:
Yes, that is correct :D

Nandroid backup & restore takes too long, but it's safer... I probably didn't need the reboot to bootloop step, but I wanted to fully commit the CM12-flashing. I probably could have had TWRP reboot to recovery and continue the steps.

[On TWRP; if you flash the CM12 nightly and go to advanced wipe and change the file system

but not doing the very last step

; you will see /system is ext4; /cache is f2fs; and /data is f2fs (if you were all f2fs and Temasek 3p). With /data still mounted; you can actually browse and see your files with TWRP file manager.]

What the CM12 nightly does is modify 2 partitions. /system and /modem. The /system needs to be restored by flashing Temasek f2fs ROM but you have to format /system with F2FS (per step 5). The gapps and SuperSU were taken out by the CM12 nightly (I'm sure about the gapps, not certain about the SuperSU).

I've just flashed 4.7 F2FS3P last night. No wipes. No gapps or SuperSU flashing. reboot and after the initial screen Android updating 125 apps... profit! nothing changed except a newer & better OS :D

[If I was on 2P; I'd flash the CM12-nightly; reboot TWRP to recovery/TWRP; format /system as F2FS; format /system as EXT4; and then flash the Temasek F2FS 2P. I would want to clear the /system completely. That's just me, though...]
[ONE Android Development] steijn0:
What are actually the improvements on this new modem?
[ONE Android Development] mmcneil:
Reports have been that LTE is working much better/more reliably, and it fixes the proximity bug. Two big pluses in my book.

Thanks,

Mike
[ONE Android Development] tobitege:
Users reported e.g. better reception (3 instead of 1 bar) and faster band switching.
[ONE Android Development] bundysoat:
Please help buddies.

I format to F2FS Data partition, but after install v4.7, I recived a message in the boot rom that says that the ROMs it's encripted.

I can't continue, recives the same message continuosly. If I re-formating the data partition and intalle the ROM all it's OK.

I realiced it from TWRP 2.8.3.0 and 2.7.0.1.

Thanks.
[ONE Android Development] phermey:
the rom for the first time needs to be sideloaded through adb.
[ONE Android Development] bundysoat:
Aaaahhhh......ok, ok, I don't know this....OK. For the momento I renounced to do this.
[ONE Android Development] phermey:
I went through the same thing. On the main page it just says we should. Not that we have to.
[ONE Android Development] DerRomtester:
[MENTION=3874152]zaphodbeeb[/MENTION] i updated my kernel to V70 and i am not using anykernel anymore. I only wanted to inform you and the other users that they have to modify fstab.bacon on my boot.img. And for multirom use V71-multirom-fix-kernel and not V70 because on V70 i forgot to activate multirom in the defconfig
[ONE Android Development] gnan10:
Is anyone having issues with proximity sensor while in phone call.

When i called/received the phone call, phone's screen goes blank and wont let us to interact until that call ends. Is someone facing the same?
[ONE Android Development] zaphodbeeb:
Hi mate,

you need to format both data and cache for f2fs-mixed, or data, cache and system for f2fs-all. I think your problem is down to not formatting the cache partition. You should be able to flash the rom directly from sd, as well as sideloading. Sideloading isnt mandatory for a first install, just an option.
[ONE Android Development] zaphodbeeb:
This is a problem occurring on many cm12 devices, including users of the ext4 version of this rom. Try flashing the 1/6/2015 CM12 nightly. This flashes a new modem, along with other changes, then restore/re-install this rom. It seems to have worked for me, and others.
[ONE Android Development] black.ic3:
One question to you as a kernel developer

I need modify kernel source (for example CM12 nightly kernel) to use f2fs? Or simply repack the ramdisk with new fstab?
[ONE Android Development] zaphodbeeb:
Repacking cm12 doesn't work as it doesn't have f2fs implemented. It is possible, but you will need to do serious surgery on the kernel. Tyr kernel does have it, but you just need to change the fstab settings. See FAQ in the op for link on how to do this for Tyr.
[ONE Android Development] gnan10:
if i flash only modem, wont it be sufficient?

if yes, please provide me the link of modem
[ONE Android Development] black.ic3:
So, i need rebuild kernel with f2fs enabled in defconfig, or how?

Or i can relax and use your kernel+rom... Your kernels are from katinatez's build with modded fstab?
[ONE Android Development] zaphodbeeb:
Apparently not. Many tried this but it didn't fix the problems. No one (to my knowledge) seems to know why flashing the ROM works. I'm just pleased it worked.
[ONE Android Development] tobitege:
OPO Alpha LP Modem == CM-12 nightly modem == https://www.androidfilehost.com/?fid=95887005526787630
[ONE Android Development] azsl1326:
Can you link to method to change fstab. Not sure which one it is.

Thanks.
[ONE Android Development] zaphodbeeb:
This ROM works with f2fs, as I already made the fstab changes and updater script changes to Katinatez kernels. The method is in an earlier post. See FAQ from op.
[ONE Android Development] azsl1326:
Sorry if I wasn't clear I am running 4.7 of this ROM. I want to upgrade to the latest version of Tyr kernel and it looks like it needs to have some changes made to fstab.
[ONE Android Development] tobitege:
[MENTION=882115]azsl1326[/MENTION]: download TyrV71-multirom-fix.zip from the kernel thread (2nd post).
[ONE Android Development] DerRomtester:
If you use multirom and ext4 download TyrV71-multirom-fix.zip and flash it.

If you are on f2fs unpack the kernel.

Just follow the steps in the link here:

Like here: http://xdaforums.com/showpost.php?p=57921263&postcount=453

Than edit fstab.bacon

repack the kernel.

Put it back in the zip and flash it.
[ONE Android Development] gnan10:
Thank you for the link. But i have installed the modem from this link. working perfectly.

https://www.androidfilehost.com/?fid=95887005526788406

:)
[ONE Android Development] tobitege:
They include the same modem files. :)
[ONE Android Development] zaphodbeeb:
The tyr kernel will need updating. This shows you how. ie FAQ from the op.;)
[ONE Android Development] azsl1326:
Thanks but it doesn't boot. I am not running multirom version.
[ONE Android Development] zaphodbeeb:
f2fs Tyr 70 Kernel versions

I produced modded Tyr kernels so they work with f2fs. I WONT be doing this on an ongoing basis, and they have not been tested. However here they are.

I suspect they are will not work with multirom. Just flash over an existing install. Do a nandroid first.
[ONE Android Development] zaphodbeeb:
Please do not flash v71 tyr. It is for ext4 devices to work with multirom, not f2fs roms
[ONE Android Development] zaphodbeeb:
But they dont flash the same things:silly:
[ONE Android Development] tobitege:
The files in katinatez's misc folder OPO_L5_alpha-modem-flashable.zip and cm-12-nightly-modem-flashable.zip do flash the same files; at least I was referring to those files in my previous post. :D
[ONE Android Development] zaphodbeeb:
Oh cool, I misunderstood and got confused. It doesnt take much. Im from Essex.
[ONE Android Development] bundysoat:
Thanks a lot. But if I don't understand good the instructions and not have more time to try more times.

Enviado desde mi OnePlus One.
[ONE Android Development] DerRomtester:
Uploaded some f2fs kernels on amdroidfilehost if anyone want them :)
[ONE Android Development] zaphodbeeb:
Are yours different from the ones I posted above? I just modded the fstab.
[ONE Android Development] DerRomtester:
They should be the same. I used V71 with multirom support.
[ONE Android Development] zaphodbeeb:
ok cool. I used the 0.70 versions and just changed the fstab. I havnt tested them other than the sm 0.70 which runs fine. Which toolchain was used for the 0.71 version? I only produced them because some users in my thread wanted them and you previously said you were not going to.

One last point, I take it that the 0.7 versions will not work with multirom but 0.71 does?
[ONE Android Development] DerRomtester:
Yep V71 works on multirom. I forgot to enable kexec hardboot in V70 in the defconfig. Yeah V71 is linaro.
[ONE Android Development] phermey:
this rom does not need to be near the bottom of page two so.....

battery life on the 4.6 sp ed seems to be pretty good. much better than where i was at before on 3.9. there are a couple of little things here and there that i am sure are being deiscussed on the proper threads. thanks for putting it together zaphod.

quick question... what made it special?
[ONE Android Development] tobitege:
The special comes from being built with current Sabermod toolchain and additional compiler enhancements. To me it feels bit more responsive, like opening apps or updating apps from Play store. Stable as well.
[ONE Android Development] almostthere:
Managed to boot on Tyr V62 SM without any modifications, anyone here been able to boot up on v70 (single ROM) SM version?
[ONE Android Development] azsl1326:
V70 won't work. You have to use v71 or now there is v72 available.
[ONE Android Development] almostthere:
Booted on v72 SM? I'm having freeze at BL even after a clean wipe install
[ONE Android Development] zaphodbeeb:
What makes the whole katinatez/temasek thing special for me is because its the two most experienced rom developers/compilers playing with the opo and they are always pushing their development to the edge of whats available. f2fs is also part of that.
[ONE Android Development] zaphodbeeb:
V4.7 Temasek f2fs runs fine. Did you let V4.7 boot before flashing v72 Tyr kernel? If not then I suspect that this may be the problem. I havnt tried v72 Tyr myself yet but I am not aware of any problems of it running on f2fs. Which f2fs rom did you install? (f2fs-all or f2fs-mixed and what version 4.7/6, or a was it a multirom version).

How long are you waiting for the bl? First boot takes some time.

I assume v72 is a reference to a Tyr kernel.

Really need some additional info here before help can be provided.
[ONE Android Development] DerRomtester:
Bit more information would be helpful. Are you on f2fs ?
[ONE Android Development] ThiefZero:
I must be doing something wrong. I've formatted system/data/cache to F2FS and flashed the newest "zaphod-temasek-bacon-stock-4.9-3P-f2fs.zip". Using the recovery recommended in the OP, I flash the rom to have: "System ext4 formatted." as one of the first messages. The flashing finishes, I try to reboot into system and the phone just sits in the OnePlus screen (I've waited 10 mins). I've searched around the topic but I seem to be the only one having this problem. Any ideas would be appreciated.
[ONE Android Development] zaphodbeeb:
Try wiping cache and dalvik. Any gapps should work.
[ONE Android Development] DerRomtester:
Sry i am a bit confused now. You formated system to f2fs or is it on ext4 ?
[ONE Android Development] katinatez:
v4.9 had a bad commit in kernel causing a bootloop or hanging on boot screen, I stated in bold red letters to follow rom flashing with custom kernel.

Did you change the kernel? v4.9 release early in the day had to be flashed with a custom kernel right after rom.

I pulled the bad rom already and replaced with this file cm-12-20150112-UNOFFICIAL-ln-temasek-bacon-v4.9.zip new Toolchain Linaro 4.8 & 4.8 also v.4.9 sm is available also take a look here.

http://xdaforums.com/showpost.php?p=58133671&postcount=5171
[ONE Android Development] Shemploo:
So please explain to me stupid like...

I flashed zaphod-temasek-bacon-sm-4.9-2P-f2fs.zip and wanted to know, can I flash MultiROM Recovery, and then the MultiROM (bootimage inject magic zip) and use it as primary, and try other ROMs as secondary with this?

I'm sorry I've read the initial posts and I'm having a hard time understanding.

Thanks :)
[ONE Android Development] gnan10:
Everything is working fine and smooth. But i just found a bug. once you enter into the dialer app, speed dial contacts wont show up on the screen untill you scroll them up and scroll that down back. Just letting know the bug. Please check is there anyone getting this problem too. i found that this is the awesome rom that i feel like pretty stable.

and one more annoying thing i have noticed is, when we scroll the screen on the phone no matter what the app is i.e., literally every where i can see like content is fading in while we scroll. which is kind of annoying to me. I believe its a feature. for some reason it isn't looking good to eyes. and making the UI to look even more laggy(even it isn't)

:)
[ONE Android Development] Mash87:
The invisible speed dial is already known. Fore ROM Bug report please check and use the ROM Thread [ROM][Bacon][5.0.2]Temasek's UNOFFICIAL Build

For your second issue: Have you had a look into Settings -> Temasek spare parts -> Screen and animation -> ListView Animation?
[ONE Android Development] gnan10:
Thankyou very much that second issue was annoying . changed the ListView Animation from Alpha to Scale. ListView interpolation selected as accelerate and decelerate

now icons are just floating on the butter. very smoooth, SWEEET!!

Thankyou again
[ONE Android Development] zaphodbeeb:
V2 coming very soon
[ONE Android Development] Pipodi93:
Quote, it's just so unreal! :D I've just flashed this ROM, coming from the original ROM, and I think it's so ****ing amazing! :D
[ONE Android Development] otisman:
Agreed 100% only the kernel and file system are different but it just works match made in heaven for sure! Plus Rycon now adding ak in there also to his f2fs ROM so there is two beast to choose from much alohas
[ONE Android Development] störte:
I just flashed 2 Versions in the last 16 hours. It is fun but getting difficult to catch up. :)

Thanks for keeping us updated
[ONE Android Development] störte:
The Temasek Rom is so often updated that it is getting difficult to catch up. Just saw the v 2 ext4 up in the other thread
[ONE Android Development] otisman:
Bing ROMs updated

Not sure to updated unreal 50% numbers so far
[ONE Android Development] zaphodbeeb:
Sleeps for wimps. Keep flashing. I am working on a lollipop AOSP f2fs version also but its being a little difficult at the moment. Hopefully crack it for tomorrow.
[ONE Android Development] pogi1100:
Attached modified framework.jar file for v2.0 for smooth scrolling (disables scrolling cache) thanks to user fix-this!

Backup /system/framework/framework.jar, replace with this one, set correct permissions, and reboot. Reboot will take a while.

Cheers.
[ONE Android Development] störte:
And here we flash again ;)

Thanks a million mate

---------- Post added at 06:48 AM ---------- Previous post was at 06:48 AM ----------

Stupid Question

What does it do ?
[ONE Android Development] pogi1100:
Smoother scrolling when flicking in apps:

http://xdaforums.com/oneplus-one/de...asek-build-t2870743/post57327388#post57327388
[ONE Android Development] otisman:
Sweet keep us posted
[ONE Android Development] jarylw:
You labelled the date wrongly - december is 12. Also, not that it's important but I think it would be good to have the changelog in descending date (latest on top). Cheers~
[ONE Android Development] zaphodbeeb:
:o

Corrected. I cant believe I made that mistake. Thanks for pointing it out.
[ONE Android Development] zaphodbeeb:
Sorry but I wont include it. For the purposes of this thread I'll keep to Termasek vanilla, apart from the f2fs.
[ONE Android Development] jarylw:
Is anyone getting updater binary errors on latest build?
[ONE Android Development] störte:
Yes i did first time. I just try it again and then it worked
[ONE Android Development] Genericxx:
First time using F2FS with a ROM, works flawlessly. Although i feel no big differences at all, ext4 was smooth as well for me.
[ONE Android Development] Guido83:
I have flashed this ROM after using the unofficial Temasek ROM. With this I have also switched from EXT4 to F2FS filesystem. Everything went well, the only thing I have experienced is a very very slow acting camera app. The live view is really slowly and the shutter takes about 10 sekonds to take a photo
[ONE Android Development] MrPhilo:
Yo! Is v4.9 stock on your download, is that the linaro version or stock google toolchain?

EDIT: Flashed v4.90, was formatted to ext4, wished I backup, I can't see the red bold letter you indicated. Having to re-install everything :(

EDIT2: Fixed this, just re-formatted to F2FS system only as data and cache was already F2FS and reflashed previous 4.7 F2FS, everything is back to normal now :)
[ONE Android Development] esgie:
3p version of 4.9 rom has a bug in updater-script so it forces ext4 format of /system. Also, after flashing it wont boot.
[ONE Android Development] steijn0:
I noticed too also broke my efs partition upon restoring thank god for efs backups right:)
[ONE Android Development] steijn0:
Hi fellas I experienced the weirdest thing, when I flashed 5.2 (coming from 4.9) my launcher broke, and when I tried to install Google now launcher it fc'd... Anyone having issues too?
[ONE Android Development] azsl1326:
Does the 5.2 linaro 2P build have the dialer fix? I think it was just uploaded an hour ago and the one on the server looks to be older?
[ONE Android Development] gnan10:
I am still having that dialer issue just flashed latest linaro 2p build:crying:
[ONE Android Development] M5devil:
I just dirty flashed 5.2 2P from a link few posts up since OP link is not found and have the bugs present
[ONE Android Development] nico53laval:
Why are my usage statistics this bad even though I flashed the cm 12 nightly to get the new modem?