yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] bsorli:
Hello and I know these questions get old, but figured I'd ask for some more clarification.

1. After last nights, 17.2 update...my audio LowMicFix was removed and curious if I need to apply these updates after every update (since probably the LowMIcFix...is only needed by those having problems)? Are these LowMicFix not becoming standard build items? Please note, I looked at github and sultanxda thread for clarification, but could not find what I needed.

2. CAF build may be a huge problem fixer for my Snapdragon device, but I'm still running EXT4 on all of my volumes since I had problems updating to F2FS that originally required changing only Data/Cache. Does CAF required F2FS or will it work with both? Do the latest builds support F2FS on all volumes?

3. Also presently running Philz Touch 6.59, and thinking about switching back to the latest Unofficial TWRP (prefer this interface), complete a new Backup, and then install the latest CAF build. Does it matter what Recovery I use to install the latest builds? (don't think so since you list basically all of the latest Recoveries in your MIsc/Recovery folder).

Hopefully, with Qualcomm build support provided in CAF most of my problems with Audio and Touchscreen will go away.

Any feedback would be appreciated and sorry if this information/reference is posted online already since I couldn't find it. Thanks Sorli...
[ONE Android Development] outkasted:
My OPO hardware as well as software keys namely home & menu key have stopped working after this update... Have a default kernel... Anyone facing similar issues or has a solution to offer?

Regards
[ONE Android Development] ashutoshmn:
[MENTION=2332422]temasek[/MENTION]

a few bugs I came across:

1. While charging, if you have enabled the charging led then you will notice glitching (flicker for a millisecond, randomly, very noticable if you pay attention for a while it is there I'm not making plain talk, it's annoying). I've tested a couple of roms on r18 sources, all of them have it, so maybe it is a Cyanogen's bug. (on your builds before r18 sources addition like v16.0 all is fine).

2. Whenever you restart your device, the core 0 of the CPU gets stuck at a frequency say 1.5ghz for a very long time, and this consumes a lot of battery (check using cpuinfo). Even in sleep the phone runs hot, drains battery because if this stuck cpu freq. (I'm talking about a fresh rom install(clean flash), no app no gapps nothing installed).

3. What are these services like cmsettings, cmresolver, cyanogenmod platform? Can I remove them?

As always, thanks for this ROM, appreciate your hard work!

Regards.
[ONE Android Development] temasek:
1 cm issue

2. Your kernel related. Nothing to do with rom.

3. Don't do that. Leave as it it.
[ONE Android Development] DerRomtester:
Yes actually it is possible but it does sometimes not work.

1. do a backup of your ext4 partition

2. edit files in the twrp folder from ext4 to f2fs

3. wipe system data cache and format them to f2fs

4. flash Rom and gapps

5. restore data only

(no guarantee)

But it should work

You are wrong it is possible

This methode is safer and works, too.
[ONE Android Development] Jole7:
Thank you for the correction didn't know that method.
[ONE Android Development] raj+1:
[QUOTE="temasek, post: 2332422, member: 1012560"] already mentioned it is a cm issue.

I had the charging problem since ages. From the first day I bought this phone. Switching to 3G/LTE eliminates this problems. Turning Off data during charging was also a solution. Its really strange that for last few temasek builds this problem seem to have disappeared for me...Running CAF 17...
[ONE Android Development] JkzsJk:
After looking and searching through a few pages here, I couldn't find any answer related to my question. I apologize if it was just my mistake, if I didn't try hard enough. If I wanted to try the CAF builds, can I just flash them over on top of the normal usual build?
[ONE Android Development] suaverc118:
Latest build with AK all caf has system ui crashes when I'm in an app and turn to landscape and back to regular. Anyone else?
[ONE Android Development] Kuoi:
I had the same problem after clean flash , but i thought it was the rom recovery i used (an app to recover your rom settings)

So i decided to do a new clean flash of rom , gapps , kernel ... and not to use this app.

Now my buttons work again.

BTW : i also use an "app recovery"-app , and that still works.
[ONE Android Development] Ejvyas:
1. Most fixes are to build.prop which get overwritten by new update/installation of ROM. So need to reflash

2. Quoting katinatez from earlier post : build would support system/data/cache on f2fs or ext4 without any modifications to updater-script.

3. It does not matter what recovery you use. Better to clean flash CAF if you are doing it first. However, firmware will need to be done using fastboot OR Philz or TWRP 2.8.6.0
[ONE Android Development] bsorli:
Thanks for the reply. I've already updated my phone to the last firmware released months ago when I unlocked my phone and required rooting to install Temasek's build. Actually, there may be a newer version firmware wise that I'll check before proceeding, but that should be good to go.

About re-flashing the Build.prop updates, I'm guessing I need to apply these fixes in CAF if I continue to have issues after my migration. I hoping the problems simply go away and appreciate the feedback. Sorli...
[ONE Android Development] ashutoshmn:
1. So, can you please look into what's causing this and fix it.

2. If I say, I was on stock kernel, will you believe me? (on v17 2nd, non caf)

3. Okay, I won't remove them, but what do they do?

Thank you!
[ONE Android Development] CoBfan1987:
I have the issue too but I thought it was related to the theme I am using. I'm not using AK CAF kernel
[ONE Android Development] suaverc118:
What theme and kernel are you using?
[ONE Android Development] CoBfan1987:
Tyr CAF

http://xdaforums.com/oneplus-one/development/kernel-tyr-caf-3-4-07-07-2015-t3151971

and

Deep Darkness // Overhauled

https://play.google.com/store/apps/details?id=com.blissroms.moelle.ddoverhauled

I started using Temasek CAF + Tyr + Deep Darkness all at once so I wasn't sure exactly what the problem was but I assumed it was the theme because uninstalling and reinstalling the theme after an update fixed the problem twice.
[ONE Android Development] aosimon:
Yes you can. Just need to wipe system, dalvik, and cache first. I did that and it works fine.

Sent from my A0001
[ONE Android Development] CoBfan1987:
[MENTION=3814731]katinatez[/MENTION] does the most recent CAF build no longer have the Mobile Radio Active work around commit? Just wondering because Google Play Services had the most radio active time it's had in the last couple weeks today.
[ONE Android Development] efattal:
Message from [MENTION=2332422]temasek[/MENTION] on Twitter:

NOTICE: V17.3 - Next build you may have to delete /data/data/com.android.settings again. This is due to changes in codes.

https://twitter.com/temasek71/status/647277238866472964?s=09
[ONE Android Development] temasek:
Aosp keyboard FC should be fixed. (Hopefully) :)
[ONE Android Development] lallolu:
To people using the caf version. Is that version really better than the non-caf? In terms of battery and performance. And is the camera issue fixed? Is it as stable as the non-caf?
[ONE Android Development] dev0lver:
Visually it should perform the same, probably a little bit smoother and faster, but normal user will probably not notice the change that much visually

Since most of the modifications are under the hood

Battery life, I can't comment on that, because I always do something with my phone, and can't let it to have normal stats for the battery

Only gripe I have with my phone is that it gets awakened regularly while I am connected on the Internet, and it won't sleep like a baby if I am connected, but when the connection is off during the night, phone sleeps like a baby and looses 1 to 2 %

And Google play services stopped responding, but I am waiting new caf build to try clean flash, maybe then I will fix that little issue
[ONE Android Development] Phazonclash:
Refresh rate

Hi, I noticed something interesting concerning our phone. In the past, the One display used a 63Hz refresh rate (still don't understand why they decided to use displays that work in that weird / non-standard refresh rate but anyway). Recently though, and I don't know when it started exactly, my phone started to report it has a 62Hz display (17.2 CAF + AK)

Any idea what's going on? Would it be possible to force a different refresh rate?! I mean, it would be awesome to be able to force the One to use a standard 60Hz refresh rate, it would eliminate all these little stutters the One suffers from when playing games capped to 60FPS
[ONE Android Development] lallolu:
Thanks for the ROM overview. It seems the battery life seems similar to the non-caf from your description. My phone does not go to sleep properly as well when connected which is why I automate wifi disabling when my screen is off for 7 minutes.
[ONE Android Development] fiz:ik:
I'm on the exact same setup than you but non-CAF and my screen refreshes with 63Hz according to about phone. Either it's a bug in the extra information section for you or CAF runs with 62Hz :silly:
[ONE Android Development] solar666:
CAF runs with 62Hz. Can confirm!
[ONE Android Development] guilhem_h:
Total noob question : I never flashed this ROM and wanted to know if I had to flash OnePlusFirmware_6-17-15.zip in order to flash the ROM ? I'm currently on 03/09/2015 CM nighlty.
[ONE Android Development] Phazonclash:
No need, the CM nigthly you're using is from early September so you're already using the latest available firmware
[ONE Android Development] DerRomtester:
I dont think that would made a difference. 60 or 63 MHz.
[ONE Android Development] Phazonclash:
The problem with a 63Hz display is that every 60 frames, 3 frames are duplicated and showed on the display. With games capped to 60FPS (so 60 frames per second), the 3 extra frames "generated" by the display to fill up the gap make it look like the game stutters.
[ONE Android Development] DerRomtester:
Yes the display shows some frames two times but that does not make the game laggy

If you have a 200 hz tv some videos are also capped at 24fps and you don't notice any huge lags or if you have a 144hz monitor and the game only runs at 100 fps you also do not recognize any lags or stutter etc. I don't notice them.
[ONE Android Development] Klewe:
Issue with Whatsapp

Fresh installed CAF version and changed to F2FS partitions. Now I'm getting issues with whatsapp. When whatsapp is not open but minimized I do not get any messages. When I open it, I get all the messages that people have written e. g. a hour ago. This is very annoying!

Anyone?
[ONE Android Development] nickporwal:
One thing i have noticed about caf version that "hw+" decoding works in mx player now. Earlier with non caf it was not working. Really happy with the caf version.
[ONE Android Development] tavito05:
Are you using battery saving mode ? Battery saving mode disables background data so save power and only refreshes when opening an app.

Also try using Disa. Is a messaging app that puts all your messaging needs in one place (fb messenger, texting and WhatsApp)
[ONE Android Development] UltraBoykj:
Trickster suitable for using for changing CPU frequencies? I flashed 17.2 CAF and Sultans disable unclock zip file and Im still unable to save frequencies higher than 1500. Resets everytime, even with freq locked.
[ONE Android Development] DerRomtester:
Thermal throttle?
[ONE Android Development] hamazoza:
Hi does anyone have wifi problems with the caf build? I dirty flashed and all is well except wifi ap handoffs. I have to reboot if I move out of range of an access point to switch to another or even mobile data.
[ONE Android Development] UltraBoykj:
Worked fine non-CAF. Doesn't feel hot in any way. Ive even tried disabling MP-Decision.
[ONE Android Development] Blak:
Hi every one

Have been away for some days have 16.9 and wanted to update to 17.- but cant have tryed all 3.

Can any one tell me what to do?
[ONE Android Development] phanitej:
are you trying to get the latest version installed or asking about which one is better to upgrade to?

Sent from Nowhere
[ONE Android Development] Blak:
Im trying to get it installed, have never had problems before.
[ONE Android Development] jdogzilla:
Confirmed that it did work for me. However, I only makde data and cache f2fs, and am not not able to install AK CAF kernel? Does AK CAF kernel require all partitions as f2fs? Also, is there an app like Synapse to control the kernel settings?

Thanks Temasek and Katinatez for your great work. Too early to give any feedback but will leave a note on how the system is performing after 3 days of usage (provided I don't flash anything in between)!
[ONE Android Development] Klewe:
Not using battery saving mode.
[ONE Android Development] DerRomtester:
Sultan is using a different thermal driver so it behaves different.
[ONE Android Development] UltraBoykj:
Switching to AK CAF fixed all. Thank you.
[ONE Android Development] DerRomtester:
Just hit the thx button :)
[ONE Android Development] suaverc118:
Flashed the latest caf Temaseks ROM with AK kernel and noticed my WiFi on in battery stats almost all the time and I haven't been around WiFi or had it on. I have it set not to always search. What else can be causing this? There are also a lot of screen wake ups. I went to bed at 100% and woke up 6 hours later to 89%. The culprit was Google app awake the whole dang time and I had just greenified it too. I disabled it and battery life has slightly picked back up, but still a good amount of drain.
[ONE Android Development] bsorli:
CAF and OTA updates

Got a notice today about 17.2 update in OTA, but it errors reporting present build is not supported by OTA. I'm guessing that this has not been enabled in the newer CAF builds or is simply left-over from my previous build that I upgraded to CAF?

Also, why is it reporting 17.2 that is already installed? Thx Sorli...
[ONE Android Development] pankspoo:
Have u not using our HEAVY BATTERY TWEAKS

> for deep sleep only use c3 krait state( power collapse) in synapse along with powernap mine only 2% battery drain over night

> regarding Google Apps : along with greenify app use privacy guard ( avoid wakeup and auto restart)

Mine more thant 30+hr battery with 7.30 hr SOT
[ONE Android Development] jesterpaul:
Bug where if you switch on option to launh apps from gesture anywhere in floating window not sticking, still happening (last 3 versions).

Here is a log from a clean install where I've toggled the setting, gone out of gesture anywhere, gone back in and toggle it on again. Hope it helps with a fix.
[ONE Android Development] UltraBoykj:
Switched back to non-CAF 17.2 ( will 17.3 later though ) as my phone would begin to fade a few mins into playing a game. 17.2 non CAF works fine.
[ONE Android Development] djha53k:
[MENTION=2332422]temasek[/MENTION] [MENTION=3814731]katinatez[/MENTION] : I'm not able to boot to TWRP anymore :( no idea why as I installed ROM normally before... TWRP 2.8.7.0 by katinatez... It stuck in Loading :(

Seems like conversion to f2fs was not good idea after all [emoji24]
[ONE Android Development] UltraBoykj:
This happened to me when I switched as well.

Try converting to 2.8.6.0. Also. You have to go into recovery right away from the adb recovery flash.

1. Goyo bootloader

2. Adb flash recovery 2.8.6.0

3. Reboot while holding the down volume ( this will actually write the recovery )
[ONE Android Development] wollax:
same here .. but official twrp 2.8.7.0 works perfectly, no theme but for the rest everything is fine ! only on backup there is an error on "persist" mount point !
[ONE Android Development] suaverc118:
Thanks. I didn't k ow what the c3 was and I found it. All of them were checked and am not sure what that meant, but I unchecked all but c3 now. I greenify and use PG too, but for some reason Nova was waking Google and keeping it up. [MENTION=5867207]vaisakh7[/MENTION] gave me rip and I'll see if this works.

Also, do you change your kernel settings before going to bed or do you leave hem alone?
[ONE Android Development] efattal:
I just want to say once again thanks so much [MENTION=3814731]katinatez[/MENTION] and [MENTION=2332422]temasek[/MENTION] for your work. Latest versions (CAF with stock kernel on F2FS, with pico tk Gapps and xposed) are just masterworks. They are smooth and snappy, stable and battery friendly. Snapdragon camera is so quick and giving nice pictures. Thanks guys.
[ONE Android Development] djha53k:
Thanks.

Flash TWRP 2.8.7.0 again... doesnt work

Flash TWRP 2.8.6.0 ... doesnt work

Flash CW convert to ext4

Flash TWRP 2.8.6.0 ...

Copy over ROM + GAPPS

Install...

Reboot and remove unwanted apps by my custom script...

Strange issues on the way:

1. I copied all my backups on SD in TWRP, after boot to OS it was not on /sdcard, but on /sdcard/0 ???

2. Some of TB backups not visible

3. Some apps were not restore by TB, I had to install them from GAPPS and then restore data only
[ONE Android Development] UltraBoykj:
A lot of work

Remember when you adb flash you *must* go to recovery on the first reboot or it will reflash your old recovery.
[ONE Android Development] djha53k:
Hmm, lot of work :(

I had to do it obce more [emoji33] because of that /sdcard/0 "folder"...

Wiped all again, copy only ROM and TK GAPPS via adb directly to /sdcard... What surprised me again that when I boot to OS these two files are nowhere on FS [emoji15] how come? Where did they go?

Again some of apps not able to restore via TB, I had to install them from GAPPS and restore only data. But even that I was not able to restore some of apps data :(

And also I found out that some of apps I used are not available anymore [emoji12]
[ONE Android Development] UltraBoykj:
Switching FS will wipe *everything*. Including TWRP and titanium backups stored on your phone. The only thing that's supposed to survive is recovery. Most complicate the issue by updating their recovery at the same time. That should, in my opinion, be done after the fact. The key thing to remember is that recovery updates, if done in adb have consequences that if not followed properly will make it appear like things are not working right.

In general, if you change FS, you must work from adb/boot loader to restore. Which means you need a backup on your computer because everything you can use in recovery will be gone. At least that's what I've found. Someone with more experience than I can comment on that.

Rough pseudo steps

1. Back up to computer

2. Covert / format

3. Put phone in bootloader.

4. Adb sideload rom

5. Restore

6. Update recovery ( optional )
[ONE Android Development] katinatez:
Much easier to convert when sdcard backups & rom,gapps are stored in usb-otg, and bypass the whole adb process.
[ONE Android Development] djha53k:
Suddenly, I dont have usb-otg :(

I made TB backup and copy all files from SD to PC...

Install TWRP 2.8.6.0 which didnt work, so I install CW, format system/data+media/Cache back to ext4, install TWRP 2.8.6.0 (recoveries install via fastboot)

Then adb push ROM+TK and install, both file "gone" when I boot to OS...

Copy all data back to SD in Win7, install TB... About 50% apps was not possible restore via TB...

Just now I tried "fix permissions" in TWRP, but still these apps not possible restore in TB [emoji23] ... no idea whats going on here [emoji45]

Before when I did clean install the TB always SAW all backups and it was possible to restore everything, basicaly I install only TB from GAPPS and then rest via TB... I did this way even when I convert to f2fs, but not possible now, why? [emoji15]

Edit: just check fstab... seems the back conversion did not went well:

/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,noatime,nodiratime,background_gc=on,nosuid,nodev wait
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,rw,inline_xattr wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid,nodev,rw,inline_xattr wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4
[ONE Android Development] Vortex1969:
Just dropped in to say what a great job your doing as always..... What a great contributor you are for the One Plus......:)
[ONE Android Development] djha53k:
[MENTION=3814731]katinatez[/MENTION] [MENTION=2332422]temasek[/MENTION] I dont understand two things:

1. I am absolutelly sure that I format /data and Cache by ext4, why they are still f2fs?

2. Why when I put install files on /sdcard via adb, they are not visible in OS on /sdcard. They have to be somewhere, because space occupied by them is missing?

Seems like last chance to fix it to me is install CM12.1 via fastboot image, install TWRP, install CM Nightly, boot and then finaly install your awesome ROM. Like this guide: webtrickz.com/how-to-flash-cm12-lollipop-factory-image-on-oneplus-one-using-fastboot/

What do your thing???

Thank you for advice.

Edit: btw there is no 12.1 fastboot img available? Cannot find anything :( seems I will have add oné more step: update from 12 to 12.1 of CM
[ONE Android Development] Suarezian:
I have a question. Is there any problem with the microphone? I'm using sultan' s built and in a call, my voice is not clear to the other person. So wanna know if the issue exists in this CAF ROM or not. Thanks.

Sent from my Oneplus One using NASA's encrypted network.
[ONE Android Development] katinatez:
Like every other flashing process on phone you need to read, read, and read. If your having so much difficulty trying out f2fs. I would say to forget it just stick with ext4. You keep mentioning twrp but never the official or unofficial version. My suggestion is switch to Philz recovery and use a usb-otg. But first read the official Philz recovery thread to understand the functions and options, and how to operate. Second if windows is not working and you want to tinker into android switch to linux OS.

To confirm which file system you have you neeed this app

https://play.google.com/store/apps/details?id=me.kuder.diskinfo

Last thing is you mention Titanium Backups. My question is why not make a flashable zip file of all your apps instead of trying to find the backups. It's a option in TB

No need to use fastboot to restore cm use fastboot to flash Philz and start over!

Best of Luck
[ONE Android Development] Az-one786:
I've used normal built of Temasek rom before..,but I decided to try dirty flash v17.2 CAF on my One and I'm so lucky bcoz it working without any issues at all... FYI.., I don't have mic issue and my friends can hear my voice clearly ...

BTW.... Amazing rom here Imo .... :good:
[ONE Android Development] katinatez:
Just an update on Google Pay

http://www.xda-developers.com/googl...-with-root-and-android-pay-in-the-xda-forums/
[ONE Android Development] Az-one786:
This should be big problem to people that only have 1 smartfone for all daily task ... But I have more than 2 device ( root/non-root ) ..

So.. no problem for me .. :D
[ONE Android Development] djha53k:
Thank you for.guidance ;)

Here is diskinfo... seems all ext4, but fstab stated different :(

I used always your TWRP version, also CW I have from your sítě as well ;)

Suddenly I dont have otg cable and till Tuesday not possible buy one :(

Ooh thats new info for me about TB, I never play too much with it as the "standard" backups always worked OK, so no need to use othewise...

I have use Philz yesterday, but One is still not OK, then I guess the fastboot img is the last chance