yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] naveed:
Hi. My Nexus 6 got delivered today and all seemed well.

That was until I visited digitalspy.co.uk 's mobile website.

There is a white line that runs down the screen. Well, this is the problem - I don't know if it's the phone's display or the website. The line doesn't show on any other device I browse the site on. It's only happened on that site and one other so far.

I have attached an image.

Could anyone help me find out what is wrong? D:
[Nexus 6 Q&A, Help & Troubleshooting] americasteam:
Same here. Don't have it on anything else, so would assume its the website. Must be an issue with Android's version of Chrome.
[Nexus 6 Q&A, Help & Troubleshooting] hanano17:
You guys may want to keep an eye on it, and also check this thread out...the line seems very similar. The one in that thread doesn't look like it's an issue with software or Chrome, but it looks almost the same as the one here.

http://xdaforums.com/nexus-6/help/nexus-6-display-3-days-t2963786
[Nexus 6 Q&A, Help & Troubleshooting] PaisanNYC:
I can confirm this happens on this website, and no other sites that i have visited on my N6. See the attached screenshot. If there was an issue with the display, a screenshot wouldnt be able to show it, only a photograph of the display would.
[Nexus 6 Q&A, Help & Troubleshooting] Xileforce:
This! The screenshot takes a snapshot of what the software is pushing. Not what is physically being displayed. If your screen was shattered. A screenshot would still come out perfect. If the software is showing a line that means its the site. If that makes any sense...
[Nexus 6 Q&A, Help & Troubleshooting] hanano17:
Good point, the other thread is an actual photo of the phone though, like the OPs picture (though I know his of this particular website now)
[Nexus 6 Q&A, Help & Troubleshooting] Xileforce:
Yes that one looks like a hardware defect since it persists throughout everything. You are fine :)
[Samsung Galaxy Mega] QA Bot:
Q&A for (rom) zaizado gt i9152

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for (rom) zaizado gt i9152. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Samsung Galaxy Mega] mauryaprabhakar918:
after installing this or final rom made by u there is no change as u shows in the last of thread that it becomes S5 look.

may i know why?

im on GT-I9152 INU_DDUANK1 Firmware

happening cause of this?
[Samsung Galaxy Mega] sanndy147:
bro i want s5 toggles on my mega 5.8 gt-i9152...plzzzzzzzzz help
[ONE Android Development] jejemc:
Good evening or the changelog and the Roma? or is the screen? the thanks?
[ONE Android Development] latenightchameleon:
V1.7 already supports F2FS, don't see the point of an extra thread with minor insignificant modifications to the ROM imo.
[ONE Android Development] CWick4141:
Agree completely
[ONE Android Development] zaphodbeeb:
For a changelog, screens etc, see Temasek's /AK threads. The only change made to this rom from Temaseks rom is that I have modded the updater script so that it installs onto a F2FS filesystem and modded the boot img to embed the latest AK kernel. No more.
[ONE Android Development] zaphodbeeb:
Then this thread isnt for you two then. Others may want to install this if they have f2fs, as Temasek's rom doesnt install unless it is modified. I have done this modification for others that dont want to do this for themselves.:p
[ONE Android Development] latenightchameleon:
Sorry, absolutely didn't mean to come off as rude, your efforts will definitely be appreciated, even if its by a small number of people:good:
[ONE Android Development] störte:
I must admit i wondered as well because in changelog it say F2FS ready. But it failed. . It is a little misleading. Just flashing your rom now without problems. Thank you
[ONE Android Development] OmegaBlaze:
? I definitely appreciate it.

Facts. Hella misleading.

---------- Post added at 06:30 PM ---------- Previous post was at 06:15 PM ----------

Will you ever include multi ROM support
[ONE Android Development] EasyGoingXD:
Is there really a big different between ext4 and f2fs or is it just beause f2fs is a "newer"/technology? Please help me i never had any experiances with f2fs ^^ What are the differentes :)
[ONE Android Development] otisman:
Wow this combo is unreal together first time I've been able to use ak kernel and cm12 f2fs very slippery and responsive at the same time much alohas to all devs involved
[ONE Android Development] pogi1100:
Thank you for this. Was about to modify the ROM myself when I saw this thread. Thanks for saving me the trouble :D

Looking forward to future updates ;)
[ONE Android Development] fix-this!:
thanks for this. ill keep an eye on this thread for updated builds.
[ONE Android Development] otisman:
Man this thing is super solid this my DD for sure much aloha
[ONE Android Development] störte:
1.81 is comming in one hour for ext4

Send by Hyperdrive on one+One
[ONE Android Development] otisman:
Seem that too bradah storte! something about f2fs that keeps me here on can't explain it lol
[ONE Android Development] zaphodbeeb:
Multirom Terasek 1.7, AK 035 F2FS version.

Hi,

thanks for your feedback. Had a play with a mulirom friendly version today and this seems to be working as a secondary install. This is a further mod on the 1.7 Temasek, AK035 rom I produced previously. I havnt had a chance to check as a primary install yet on multirom but it seems to swap from secondary after install to primary correctly. Any help testing it would be appreciated. I think a new version of Temasek may be available soon so, with positive feedback I'll produce a new version with the multirom changes embedded and update the OP.

Try it here.
[ONE Android Development] zaphodbeeb:
Thanks for the heads up. I'll try to update the F2FS roms when its released.
[ONE Android Development] störte:
Great so i can update after my work

Send by Hyperdrive on one+One
[ONE Android Development] otisman:
Nice thanks for building and making it less of a headache for the f2fs users and now multirom users too
[ONE Android Development] zaphodbeeb:
I will get around to providing a replacement for mega, but am really pushed for time ATM. It will be done as soon as I can. Apologies. I got no problem with you setting up mirrors, but I will be continuing with mega for the mo, until a replacement is sorted.
[ONE Android Development] zaphodbeeb:
There should be no need to mount anything. As long as your system, cache and data partitions are formatted to f2fs. Flashing mounts and unmounts as is necessary. If you are updating from the previous release of this rom then you should need only to dirty flash. In the unlikely event that this doesnt work, then try a clean install.
[ONE Android Development] raybit10:
[MENTION=3874152]zaphodbeeb[/MENTION], today's build says 17/12/2014 (v2.8) in OP and today is 18th ;)

Thanks for that and see you back after flashing...
[ONE Android Development] zaphodbeeb:
Doooh!, sorry. Corrected.
[ONE Android Development] beatbrot:
Where is Audiofx in the newer builds? Oo
[ONE Android Development] zaphodbeeb:
Now changed new downloads to androidfilehost.
[ONE Android Development] Mash87:
Dirty flashing (just the ROM on top of the old one, no wipe whatsoever) usually works. In case it doesn't and you wan't to clean flash you can just do an advanced wipe, TWRP detects what FS is currently used and formats again in the same FS. So f2fs stays f2fs. At least it does for me.

I know it doesn't make too much sense because mounting and unmounting is done in the update script... But this seams to always work for me. When the first try of flashing the new version fails I unmount all partitions and try again and usually it works fine then (not wiping anything, just unmounting the partitions). Don't know, maybe it's placebo and the second time it would work without unmounting anyway but it has become my routine when updating the ROM. Just sharing experience.
[ONE Android Development] jcespi2005:
Hi...

im a bit lazy to format internal SD (data/media) to F2FS cause much data there... can i test F2FS just on system and data partitions?
[ONE Android Development] Mash87:
Formatting your /data partition to f2fs WILL WIPE YOUR INTERNAL STORAGE!

You can format your /system partition to f2fs without loosing data but I don't know if that brings any benefit.
[ONE Android Development] jcespi2005:
Anyway i edited the script from latest 2.9 version from Katinatez to F2FS compatible, and will give a quick test formatting system cache an data and report back...

EDIT: Your're totally right, formating /data wipes the INTERNAL too ;) Installing now to see how much better is F2FS...

EDIT2: Anyone having troubles to restore using Titanium? seems not working restoring to F2FS...

EDIT3: Reboot solved the titanium issue... now restores fine

Thanks
[ONE Android Development] raybit10:
+1 for the EDIT, EDIT2 and EDIT3...

I liked the updates :good: :)
[ONE Android Development] jcespi2005:
Holly Grail, this F2FS is really fast, restoring large app/data from titanium takes less time then before on ext4... I like this...

Sent from my OnePlus One ;)
[ONE Android Development] Ideas4ya:
Kernels

Zap I know you are knowledgeable about all things F2FS...

Tyr Kernel is what I was using, but the dev says he will stop making the F2FS version. Can I use the regular version? Can I only use F2FS kernels on F2FS? (I know it

sounds

like a dumb question lol but I'm hoping for an unexpected answer!)
[ONE Android Development] jcespi2005:
You need a kernel with f2fs support, I'm using AK...

Sent from my OnePlus One ;)
[ONE Android Development] störte:
Same here. I use Ak one kernel for both
[ONE Android Development] Rycon33:
His kernel still has the F2FS patch, so you still can use it as long as you edit first the fstab.bacon file in its ramdisk. I did it on his v54 and it's fine on F2FS ROM.
[ONE Android Development] DerRomtester:
I stopped uploading f2fs version. But you can still use my kernel on f2fs. You have to unpack my kernel. Than edit fstab.bacon and after that repack kernel and flash it.
[ONE Android Development] zaphodbeeb:
Hi,

Unfortunately it has to be a F2FS kernel if your phone is f2fs, else it will just bork at flashtime.

I was thinking about adding a few additional kernel options to this thread, and Tyr was top of the list. Ive been using Tyr for a while but only stand alone (i.e. not with other kernels). See what I can come up with.... Hopefully over the next few days. It would be good to keep the Tyr f2fs thing spinning...
[ONE Android Development] byAidan:
Thanks for creating the F2FS version of the Temasek ROM i can't wait to try it! :D

Just a quick question, what toolchain is used to compile this ROM?

Thank you in advance :good:
[ONE Android Development] HamsterHam:
ak 0.60 randomly reboots. Hopefully he'll fix it asap.
[ONE Android Development] nico53laval:
Could you maybe share your Synapse profile or do you think it depends on everyone's device which voltages and frequencies and such are actually stable?
[ONE Android Development] Ideas4ya:
Thanks for clarifying things guys. Kernel options would be great zap.
[ONE Android Development] azsl1326:
Hi All,

Looking to switch to an F2FS ROM and decided I would give this one a go. As my system is currently formatted EXT4, I had a couple of questions. The other post by katinatez for Temasek's ROM - I am assuming that it hasn't been modified for F2FS and could be installed normally (EXT4)? Also AK's v.60, which is included in this ROM gives random reboots. I am assuming that I can flash v.50 without any problems? Finally, has anyone noticed if battery life is improved when using F2FS?

Thanks, in advance, for the assistance.
[ONE Android Development] dan96815:
I had random reboots with ak60 flashed ak50 seems better and faster
[ONE Android Development] störte:
Try the new ak 61. It solves it for me.

[MENTION=222011]Zaphod[/MENTION]heeb

What is causing that a rom formatting the F2fs back to ext4 during flash ?

There is nothing in the updater-script. Any idea where to look for it ?
[ONE Android Development] Criton30:
On stock 44s and with ak061 or with ak060 I have no issue, so thats not a kernel problem.

Sent from OnePlus One via Tapatalk
[ONE Android Development] Rycon33:
Just wanted to say my experience here. I remembered last time, block-based(.dat files) ROM type do that. Then I converted my build to be on the old-type zip format(those that contains the actual apks inside the ROM) then the issue is gone.
[ONE Android Development] störte:
How did you do that ? Would be great if that will work then
[ONE Android Development] Rycon33:
You have to ask your ROM maker.

Did you confirmed the ROM your trying just now is on .dat files? It won't work with F2FS.
[ONE Android Development] störte:
Yes the Roms i like to try are all blockbased.

Thank you for the info about that
[ONE Android Development] tobitege:
I totally ran against the wall today after successfully installing this ROM with full F2FS (all clean) and then trying to restore any of my previous different rom backups as secondary and none of them booted (stuck at skull logo). Swapping with primary didn't help either. I chickened out and went back to all-ext4 after hours of trying... :crying:

Though I was impressed with F2FS with apps loading etc., definitely a noticeable improvement over ext4.
[ONE Android Development] nirmik379kale:
Cannot get it booted as secendory rom

I downloaded the latest secondary version of the rom , also got it installed as secondary rom but it does not boot... goes into a bootloop.

My primary rom is stock rom with multirom kernel ( ak kernel ).

Please help.
[ONE Android Development] Rycon33:
Those ROMs you want to install as secondary must have a kernel that supports F2FS also.
[ONE Android Development] tobitege:
I think I restored them in MultiRom and afterwards flashed AK50 on top as I thought that was compatible... I just messed up. :D
[ONE Android Development] Rycon33:
AK is F2FS ready. I'm guessing in the previous kernel, you didn't edit he fstab.bacon file before flashing ak kernel on top. AK uses the current ramdisk of your current ROM. The fstab.bacon file is on the ramdisk and you need to edit it to be F2FS-compatible.

Maybe confusing but you can visit the thread in the general section for converting F2FS for more info about it.

I apologize to OP for the OT.
[ONE Android Development] tobitege:
Thanks [MENTION=4023029]Rycon33[/MENTION] for the tips, I'll investigate further and leave OT now. ;)
[ONE Android Development] zaphodbeeb:
Apologies, i posted an incorrect url for the stock multirom version. This is now corrected.
[ONE Android Development] zaphodbeeb:
H,

I would say better battery from feedback, but its a difficult question as its not possible to run both ext4 and f2fs versions at the same time, and I only have one one. I have never experienced random reboots with AK 60, but having sad that I havnt been on it for any period of tme. If you are more confident with v61 (out now) then you can flash straight over the version bundled in this rom. The roms n this thread have already had fstab/kernel changes necessary applied. They will not work on a ext4 oneplus one. Dont try.
[ONE Android Development] zaphodbeeb:
Its a rework of Temaseks/Katinatez fine work so I havnt had to use any toolchain to produce these roms.
[ONE Android Development] zaphodbeeb:
Be sure to exercise some patience. It takes a while for first boot. Also please note I made a **** up with the url for the secondary stock rom. Apologies, the correct url is now shown.
[ONE Android Development] tobitege:
No apologies needed, you did nothing wrong with regard to what I mentioned! :)

The initial install went fine all along, only the restore of secondaries caused issues for me because I did not know about the kernel requirements for them with F2FS (fstab etc). Keep it coming! :D
[ONE Android Development] cnrd:
I'm getting:

Error executing updater binary in zip on TWRP with latest AK kernel ROM. (AK.61)

Was an AK.60 before.

EDIT: PhilZ touch gives "Error symlinking"

And i have verified that MD5 matches.
[ONE Android Development] adojames:
f2fs and mounting in windows 8

For people who have difficulties making windows 8 seeing your device after changing to f2fs, please sideload the rom. Random reboots appear to be fixed on AK 0.61 :)

Excellent work by the way. Battery is noticeably better along with response rate. Smooth as butter!

Playing with synapse profiles atm for increased battery (not that we need it)
[ONE Android Development] zaphodbeeb:
Hi mate, yes you will get ths error if you dont wipe cache/dalvik when updating. Just zap cache and dalvik, reflash and all will be good. I just re-tested this both as a clean install and dirty over ak060 version on multrom successfully. You should also be able to download and flash ak0.61 version over the rom (I tested ths also)
[ONE Android Development] cnrd:
Thanks

Sorry didn't read OP properly :)
[ONE Android Development] zaphodbeeb:
Another update later tonight/tomorrow morning.:eek: Keep flashing f2fsers. If I get time Im also going to add a Tyr kernel version.
[ONE Android Development] zaphodbeeb:
Strange because I have never had a problem when switching between ext4 and f2fs versions impacting on win adb or fastboot. Is this a known problem in the AK or Temasek threads?
[ONE Android Development] tobitege:
[MENTION=3874152]zaphodbeeb[/MENTION]: so wiping caches is also required for kernel updates, just to confirm? I've updated kernels on "normal" ROMs (non-multirom/f2fs) without wipe. Thanks for any clarification or if I misunderstood.
[ONE Android Development] zaphodbeeb:
x58 kernal and synapse stuff

I made a x58 Temasek stock kernal zip. The stock x58 kernal can be flashed over AK0.61 but it will not support the same synapse functions. Anyhow its useful to have to play with

x58 kernel zip

If you flash the AK kernal over the stock kernel you will really notice the yellowing effect of AK. This is easily fixed by setting gamma to 1 for the AK kernel.

Both kernals can drop frequency (I drop mine to 1574Mhz usually) but the AK kernal doesnt seem to support undervolting, and you will note other differences.

Both AK and stock kernels did not require cache or dalvik zapping. I guess this is because its the same rom, apps etc
[ONE Android Development] iKrautDroid:
Hmm, I've wiped cache and dalvik a million times, still gives me the stupid symlink error? What do I do? Would hate to have to wipe...

Redownloaded the rom, still not working :(
[ONE Android Development] Deadpool253:
Will we get 3.0 today? I just logged on and saw they updated it for 5.0.2 and I didn't want to flash 2.9.1 and have to reflash again twice in the same day lol!
[ONE Android Development] tobitege:
It's already downloadable.
[ONE Android Development] Deadpool253:
I only saw 2.9.1 in the op.

Whoops.. I missed the current link. I'm so used to popping in here and seeing the version number in the op download sections cause I'm using the XDA app lol
[ONE Android Development] Ideas4ya:
I'll definitely be looking out for this zap!! Best kernel for this rom imo
[ONE Android Development] zaphodbeeb:
Try this. Do a TWRP backup of your old version. Then wipe dalvik, cache, data etc, and a fresh install of the new. Lastly try to restore, selecting only data. Dont know why you are having problems but this may help. If it doesnt you still have a backup.

Alternately try to flash Philz recovery. You can always flash TWRP back afterwards. I have found that Philz doesnt generate errors when TWRP does in the past.
[ONE Android Development] zaphodbeeb:
done
[ONE Android Development] zaphodbeeb:
Yes apologies for being a little slow off the mark with this. Ive been trying to expand the range of kernels available, as well as produce, test and update theroms and update the thread simultaneously. Mixed success! Anyhow I need my bed now so enough for today.
[ONE Android Development] tobitege:
[MENTION=3874152]zaphodbeeb[/MENTION]: thanks for your work (out of button-thanks), you're certainly not slow. Appreciated!

Which kernels besides stock/AK have you tried or plan to add, out of curiosity?
[ONE Android Development] katinatez:
He also added DerRomtester kernel his thread is here http://xdaforums.com/showpost.php?p=50653071
[ONE Android Development] tobitege:
Yeah, I was about to try Tyr as well, thanks [MENTION=3814731]katinatez[/MENTION].
[ONE Android Development] Deadpool253:
Anyone else getting random reboots?
[ONE Android Development] pedronunes:
Yup, all the time, restored my backup, Will wait for New version.
[ONE Android Development] tobitege:
FYI: [MENTION=5736293]fredzen14[/MENTION] posted yesterday F2FS-enabled Tyr V55 kernels in the Tyr V55 kernel thread by [MENTION=4804871]DerRomtester[/MENTION].

Using the Sabermod version right now and it works great (boots up fine, no bootloop). Flash it over e.g. a secondary, non-F2FS ROM and then it'll boot (startup may take a minute initially, though).
[ONE Android Development] mrdoubleb:
Same here, random reboots and sometimes doesn't want to wake from sleep.
[ONE Android Development] DerRomtester:
Which kernel ?

Go to the kernel specific thread and post last kmsg.
[ONE Android Development] Ideas4ya:
Great job!!! Small token of appreciation!! 8NJ33069TV581390G
[ONE Android Development] jarylw:
Is your Tyr version in OP SM or Linaro version?
[ONE Android Development] zaphodbeeb:
Its the f2fs-all version. Im working on the 55 linaro and sm versions at the moment, which are proving to be a little tricky! So, hopefully, will have some updates soon. Also looking at a couple of other kernels. Dont know if I'll include them in the thread yet though.
[ONE Android Development] zaphodbeeb:
Thanks, all donations go to charity, so feel good.
[ONE Android Development] zaphodbeeb:
both
[ONE Android Development] zaphodbeeb:
Tyr versions

Please note these can take a long time on first boot.
[ONE Android Development] crazykamui:
I'm 12/21 ty55sm standard mod install.

Why kernel is ty54?

Cheak plz.

Thank you for your work.
[ONE Android Development] Genericxx:
Waiting for Katinatez 3.1 that i can clean flash my bacon ;)
[ONE Android Development] tobitege:
Never flash your bacon in public, hurts on the eyes! :D
[ONE Android Development] Bumperboy:
Trying this rom now. Thank you for your work
[ONE Android Development] gnan10:
Full of random reboots
[ONE Android Development] tobitege:
Maybe for you. :silly:
[ONE Android Development] xarismat:
The same here:(
[ONE Android Development] thespeed:
Yesterday i had the same problem.

Don't know if someone is using the AK kernel.

With AK kernel 61 i had those problems.

So i flashed back AK kernel 60 and the phone went stable.

After that i have flashed again the AK kernel 61 and there where no problems anymore.

I also saw that some settings within Synapse were changed maybe that was a problem?

By the way the Temasek rom with the AK kernel works great.

Great job!! and thanks for all the hard work.

The only thing i found out is that sometimes the sounds stutters(bleeping) when using a headphone.

I am using this rom as a daily driver :)
[ONE Android Development] zaphodbeeb:
I think its the Ak kernal 0.61. I'll be updating this evening with 0.65. Maybe that will help. It also occurs on the ext4 version. Just flash Ak,s 0.65 version. It has native f2fs support. A dirty flash should do it.
[ONE Android Development] dexxa05:
Same for me! Lots of Reboots