yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Firewalker1980:
bsmitty83, have you tried to get or encountered multiple bootloops or freezes after a battery pull? Because even if I pull the battery after a freeze/loop upon rebooting, it sometimes takes several battery pulls to get it back to normal.

Could it be there is like a minimum interval that's needed after pulling battery before it will boot succesfull 100% of the time?

I normally leave the battery out for a at least 10 seconds, and then leave it "off" for a few minutes after inserting it, to be more lucky to have a good boot from the get go.

Really happy you're closing in on this issue and taking so much effort to fixing it. Hugely appreciated!
[Samsung Galaxy Nexus] Driver007:
Any suggestions why write speed is so slow? Using f2fs
[Samsung Galaxy Nexus] All-Star:
Try LagFixFree and start trimming /data /system and /cache.
[Samsung Galaxy Nexus] pvkiniyan95:
Change schedulers
[Samsung Galaxy Nexus] Driver007:
Nope, didn't helped, same story :(
[Samsung Galaxy Nexus] bsmitty83:
No , it rebooted normally after the first battery pull .

Still not sure what is causing it . trim runs after 24hrs but that's ROM side and I don't see how it could be the cause , I really don't know .

I don't even know where to begin looking for this bug so I'm still brainstorming , I might try some things this week but until then I guess its just gonna be there .
[Samsung Galaxy Nexus] bsmitty83:
Try wiping your cache and dalvik from recovery .

Lagfix won't work on f2fs , fstrim isn't supported ATM .
[Samsung Galaxy Nexus] dezful:
Mine 32Mb/s read; 10Mb/s write ;)

Ext 4, Latest LS, ART.
[Samsung Galaxy Nexus] Driver007:
Tried, same story, just thinking going back to ext4
[Samsung Galaxy Nexus] osm0sis:
You shouldn't battery pull. Just trigger the bootloader with the key combo and then select "Power off". See if that works better for you.
[Samsung Galaxy Nexus] Castro27:
Lets say I decided to convert the data partition to f2fs. Do I need to convert the rom to f2fs as well?
[Samsung Galaxy Nexus] osm0sis:
As long as you leave system ext4, then it's my understanding that no you wouldn't. :D

When I do finally go f2fs this is probably how I'll do it; our system partition is already too tiny before the f2fs overhead, so why bother? I might switch cache too, since we're not really using it for anything else and the speed boost could hypothetically help.
[Samsung Galaxy Nexus] Castro27:
Thats why I'm still using ext4, but I think I'll give f2fs a try now. Thanks man
[Samsung Galaxy Nexus] poo706:
You need to be careful of slimkat and a few other roms because they mount data specifically as ext4 as well and it results in a Google logo loop if it's f2fs.

[poo]
[Samsung Galaxy Nexus] Castro27:
Do you know if that happens on PA?
[Samsung Galaxy Nexus] poo706:
Don't think so, but I'd have to look at the updater-script to be sure.

[poo]
[Samsung Galaxy Nexus] Castro27:
I'll check it out

Edit: there's no mention to the data partition being mounted as ext4 but I could be wrong. If anyone more used to this could take a look I'd be grateful.
[Samsung Galaxy Nexus] osm0sis:
Ah yes, probably to do some "persistence" stuff. Good catch. :)

Stupid that they haven't all migrated to fstype independent zips, at least for data, considering busybox makes it so easy. Then my proposed changes would have made the zips work for both ext4 and f2fs on system as well.. :rolleyes: ;)
[Samsung Galaxy Nexus] bsmitty83:
So I just rebooted after 2 days uptime .... No bootloop . now I'm baffled . for real . wtf
[Samsung Galaxy Nexus] poo706:
All clear!

[poo]

---------- Post added at 10:01 PM ---------- Previous post was at 09:58 PM ----------

Yeah, it wasn't hard at all to make my unofficial ls builds universal when it comes to mounting and formatting. I don't know why more roms haven't done so.

[poo]
[Samsung Galaxy Nexus] Castro27:
Awesome. Thanks
[Samsung Galaxy Nexus] IIEtCII:
does this kernel support swapper2?

is there a kernel for maguro that support it ?
[Samsung Galaxy Nexus] osm0sis:
First I've heard of it, but it just looks like a sh*tty ad supported frontend for enabling zram..

Use Synapse and do it for free, like Smitty and I intended. ;)
[Samsung Galaxy Nexus] Jar3112:
Quick question. If I am on f2fs and I make a backup on my flashdrive using NO F2FS TWRP and then I flash back F2FS TWRP will the backup be valid?

I don't have enough space on the phone's sdcard to make a backup..

Otherwise, is there another way to make a backup outside of the phone's memory?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GilGameshn1:
We have a good new here ... Tnx man .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thoiloidainhan:
No not good new. It's going from bad to worse lol. Smitty thought he pinned down the problem to long up-time and then he rebooted fine after 2 days
[Samsung Galaxy Nexus] aliesz:
Is there any version of this kernel for JB4.3 android system?!
[Samsung Galaxy Nexus] osm0sis:
This should still work! Maybe [MENTION=4278473]Hetalk[/MENTION] can add it to the FAQ? :)

http://xdaforums.com/showpost.php?p=52688739&postcount=9103
[Samsung Galaxy Nexus] Hetalk:
Done :o
[Samsung Galaxy Nexus] osm0sis:
Is it #12? The link seems to be broken. Points to page 882 but redirects to the OP. The post link I shared above should suffice. :)
[Samsung Galaxy Nexus] Hetalk:
LOL. I added to the top of the FAQ.

Didn't realize I had a #12 which talked about this issue. I'll update that one as well. Thanks man. :good:
[Samsung Galaxy Nexus] Castro27:
[MENTION=4544860]osm0sis[/MENTION]

I've been trying to run the latest PA with the system partition formated as ext4 and the data/cache partitions as f2fs but it bootloops. Are there any specific instructions to use your new kernel?

Edit: if I try to use data as f2fs and system/cache as ext4 i keep getting a message saying that a system encryption was not successful
[Samsung Galaxy Nexus] GilGameshn1:
Aaah ... I thrived to hear good new ... Stupid me ... He he ... But tnx anyway

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Hmm thanks for testing further. I'll look into it tonight. :)

Edit: [MENTION=4926715]Castro27[/MENTION] are you encrypted or is that just the message you get?

It's weird, because to test it I set the fsbase in the the script to f2fs, meaning that in order for my all-ext4 device to boot the script had to swap all 3 partition entries from f2fs to ext4, so I'm a bit surprised to learn that it might not be working in the opposite direction. :confused:
[Samsung Galaxy Nexus] Castro27:
My system is not encrypted and that's the weird part. I havent tried a full f2fs build but so far only a full ext4 setting will boot on PA.
[Samsung Galaxy Nexus] osm0sis:
Been experimenting for the last few minutes with just /cache as f2fs (using MWisBest's FML-TWRP :good:) and it was definitely swapping the entry correctly but still wouldn't boot. I just changed the fstab mount options from our:

/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache f2fs nosuid,nodev,noatime,nodiratime,errors=panic,flush_merge,background_gc=on,inline_data,inline_xattr,active_logs=2,discard wait,check

to the more simplified, basic:

/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache f2fs nosuid,nodev,noatime,nodiratime,inline_xattr,discard wait,check

And now it boots. ;)

So it's either a ROM thing where some don't support all our mount options, or we just got a little crazy and should use some less aggressive ones. I'm experimenting now to see which one(s) is(/are) the showstopper(s), then I'll have a new Unified2 test build up for everyone. :good: :cool: :cowboy:
[Samsung Galaxy Nexus] Castro27:
I'd be glad to test it :)

Edit: do you think that this is related to the encryption problem?
[Samsung Galaxy Nexus] osm0sis:
Nah I just think it's just a product of the mount options, like with cache. The way encryption works is actually a fall-back method where, when it can't mount the data partition normally it just assumes it's encrypted and then tries to decrypt. So it's easy to see how it failed and then thought you were encrypted instead, but of course you aren't so it didn't know what to do and failed altogether.
[Samsung Galaxy Nexus] Castro27:
I see. Well, looking forward for the next release :)
[Samsung Galaxy Nexus] osm0sis:
Just uploaded the fixed version: http://v.ht/osmod :good:

Turned out it was the errors=panic option I'd just added back. Really odd, considering that's a pretty standard filesystem option. I even tried changing it to errors=recover since that's what KToonsez uses on the SGS4 for f2fs, but still it wouldn't boot. :confused:

[MENTION=4608636]bsmitty83[/MENTION] Is there anything missing from our f2fs that would fix that? On the plus side, something you've added down the line fixed ext4 userdata fstab support for noatime+nodiratime and barrier=0+data=writeback, so I could finally remove that workaround from dvbootscript.sh which I've been using forever. :D

Anyway, long story short, I'm glad it was just the fstab options and not Unified v2 that wasn't working. :)
[Samsung Galaxy Nexus] Castro27:
It booted. Running data and cache as f2fs and system as ext4 and it looks good. I'll set everything back up and I'll be back soon. Thanks osm0sis
[Samsung Galaxy Nexus] osm0sis:
All this fun put me in the mood to finally convert data to f2fs now myself! ;) :cowboy:

Made a backup with FML-TWRP, now using my adbsync sdcard Backup Automation to pull my entire sdcard (including the backup) off-device. Then I'll format data f2fs, push my sdcard back, flash my sdcard Fix Permissions script and manually extract the data backup with the command "tar xzvf". No data loss! :cool:

Edit: Actually, even better than manually extracting - just rename the backup files for the partitions you changed to f2fs, e.g. cache.ext4.win to cache.f2fs.win, as well as the corresponding md5 file, then you're laughing. :D
[Samsung Galaxy Nexus] amd_h4x0r:
Thanks for mentioning your fix permissions script, it's exactly what I have been looking for. I had to figure out a way to put pictures/videos back on my phone without changing the last modified date, so I eventually did an adb push from recovery. You script is just the thing to straighten out the file permissions.
[Samsung Galaxy Nexus] aswinrulez:
I encrypted my phone a few days back to wipe my phone permanently. I read article I'm CNET where they told the best way to wipe a phone so no one can recover files was to encrypt the phone.. Delete the files then do factory reset. I was on vanir. I did it and now the encryption is not going even during factory reset. I even flashed a different rom, slimkat to be precise but encryption is still there. What can I do?

Link to thread:

http://xdaforums.com/galaxy-nexus/help/how-to-revert-encryption-t2832956

Im posting it here because i did not get any help in Q&A section till now.
[Samsung Galaxy Nexus] GilGameshn1:
I try to test some gov settings in kernel and I can't resist to use ondemandplus instead of intractive ... I can clearly see that the heat issue gone or lesser ... It is personal experience anyway but I feel better with it .

Sent from my Galaxy Nexus

---------- Post added at 02:57 PM ---------- Previous post was at 02:52 PM ----------

In TWRP , advance wipe , select everything and format ... The try to flash you ROM ... If you try to restore your backup I think your encryption will back . hope it help . ?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cujo6801:
I had to share this post with you guys

it's one of the best ones I've ever read

There is no changelog because there is no new code. At all. Its the same build over and over basically. But I do it because some people are crack flashers and really need to flash something.

It's from this thread

http://xdaforums.com/showthread.php?p=49568

Sent from the "DOG" pound
[Samsung Galaxy Nexus] osm0sis:
Interesting, I just noticed 720p video from the back camera is broken on DirtyV-SR using Google Camera. Front facing 720p and back facing 480p both work fine..

I'll see if there's something in the media profiles that needs fixing, since I thought only 1080p was supposed to be broken in SR.

[MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] ibnuasad:
Thanks very much for this kernel. Just flashed my Galaxy Nexus to CyanogenMod 11 and was looking for a stable kernel that would work with Touch Control (PGM) so I could use double tap to wake (dt2w) and slide to lock again. CM11 + SmittyV-UR-NoMeM (7-17-14) + Touch Control (PGM) = Awesomeness :)
[Samsung Galaxy Nexus] sergialess:
It would be cool to have these video recording issues fixed for the SR version. That's the reason why I'm not using it (I use the normal DirtyV).

Thanks!.
[Samsung Galaxy Nexus] Nephilim:
Don't mean to play devil's advocate here but with my settings, which include interactive gov, I've had zero wake lag on SR2 Linaro.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Btw [MENTION=4608636]bsmitty83[/MENTION] have you ever tried building the kernel with -ffast-math, -Ofast (which includes -ffast-math but everything else is probably useless for android) or any of the other cflags -ffast-math turns on?

From what I understand it could give a decent performance boost, I actually use funsafe-math-optimizations as one of the TARGET_thumb_CFLAGS I use in my rom builds without any issues

Just in case you dont know what I mean-

-Ofast

Disregard strict standards compliance. -Ofast enables all -O3 optimizations. It also enables optimizations that are not valid for all standard-compliant programs. It turns on -ffast-math and the Fortran-specific -fno-protect-parens and -fstack-arrays

-ffast-math

Sets -fno-math-errno, -funsafe-math-optimizations, -ffinite-math-only, -fno-rounding-math, -fno-signaling-nans and -fcx-limited-range.

This option causes the preprocessor macro __FAST_MATH__ to be defined.

This option is not turned on by any -O option besides -Ofast since it can result in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications
[Samsung Galaxy Nexus] paarthdesai:
i am having deep sleep issues :( 39percent at night...5percent in the morning...6hr sleep

wht launcher are you guys using?
[Samsung Galaxy Nexus] clnzx2:
You would be the only one.... test kernel helped but still something not quite right.

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

Use wake lock detector. Chances are it's a rouge app
[Samsung Galaxy Nexus] Nephilim:
Using GEL, sleeps like a baby, getting at least 97% deep sleep overnight minimum on SR2 Linaro 1/25.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
I don't want to apply your whole settings. But the main difference between them and mine is that you set the highspeed frequency from Interactive to 920. I will apply that and see how it works. If that does not help I am going to substitute other settings with yours to find out what can be the cause. Let's see how it goes. :)

-- EDIT --

The raise of the highspeed frequency seems to solve it so far.
[Samsung Galaxy Nexus] ak:
Row scheduler is optimized ... I think if you want performance set your parameters high ... There are good feedback on g+ community about the new kernel version.
[Samsung Galaxy Nexus] vlc_marcos:
hello all, good morning. I just try to install the kernel, Linaro and the other with the recovery 6.0.4.7 and I get a failure 7 unable to set permission. I'm on slim kat rom. any ideias why? I download the kernel several times to be sure that is not a bad download
[Samsung Galaxy Nexus] metalspring:
Didn't work for me, the last time I tried to turn on the screen took about 5 tries to wake my phone up even with raising the highspeed_freq

One thing I notice though is the 512 GPU frequency works just fine without changing the voltages on it unlike the dirtyv-sr version

(Raising the GPU voltages by even 5 each results in an instant freeze and reboot)
[Samsung Galaxy Nexus] 91franz:
I have problems while using touch wake.. Sometimes the phone wakes up but then the touchscreen is unresponsive..

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] hepi_hape:
Delet
[Samsung Galaxy Nexus] Charmacas:
Then maybe you have something else different configured than Neph and I. Could you have a look?

I think you should mainly focus on an app which downloads and installs the kernel. I personally don't like FAQ apps and I don't think it's worth the work you would put in.

If you would like to make FAQs I suggest to install a mediawiki, optimize it for mobile viewing and provide the link anywhere you can. :)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] osm0sis:
It's a known derp in the zip. [MENTION=4608636]bsmitty83[/MENTION] (or you, in the meantime) just need(s) to have the set_perm(0, 0, 777, "/tmp/dump_image"); line removed, since dump_image doesn't exist and CWM catches that error now.
[Samsung Galaxy Nexus] büscher:
Happens to me too.

Also Touch wake with timed option does not work.

But thats a small thing compared to the speed we get with this beast!
[Samsung Galaxy Nexus] bsmitty83:
I knew I forgot something ..... :p
[Samsung Galaxy Nexus] bsmitty83:
Yea I sometimes get a pause . still not sure why , seemed like it went away for a while . besides that occasional pause on unlock , its running great
[Samsung Galaxy Nexus] vlc_marcos:
[MENTION=4608636]bsmitty83[/MENTION] - i dont want to sound lazy but can you fix this so i can install you kernel i be happy like the others :)
[Samsung Galaxy Nexus] bsmitty83:
Yea gimme a sec , I'll do it on my phone at work for ya
[Samsung Galaxy Nexus] Nephilim:
How is it I'm the only one that has normal screen wake? I seriously have no issues at all waking the screen on first try. Also, just checked, my deep sleep since hitting "warp counter" on trickster is 68%, thats only because i had almost an hour of screen-on time before I went to sleep. (1hr screen-on aka 180mhz, 525mhz and 4.5hrs deep sleep, pretty damn nice!)

Lolwut?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
Besides the fact that the devices don't want to wake up the kernel runs great.

No option which I configured solved the wake up problem.

+ Raise voltage by 25 (230 and 350)

+ Set min freq to 350

+ Set Hispeed freq in interactive to 920

+ Use GPU clock 512

+ Use CPU clock speed of 1400
[Samsung Galaxy Nexus] Punkiderma:
You just revolutioned my way of flashing :D

Also, you sync script is GREAT

Now running slimkat with system on ext4, data and cache f2fs.

Just for curiosity: why keeping system ext4? In other words, with wich criteria one should chose what to keep with ext4 and what to format with f2fs?
[Samsung Galaxy Nexus] osm0sis:
Thanks! Explained my reasoning a few days back, but here it is again. :)
[Samsung Galaxy Nexus] Castro27:
Funny thing, ever since I switched my data partition to f2fs my phone got really sluggish. Random things like downloading whatsapp messages keep crashing my phone like nothing before. I think I'll go back to ext4 for the time being. Worth a shot though.
[Samsung Galaxy Nexus] p34rp34r:
My understanding - and someone correct me if I'm wrong - is that f2fs is great on partitions that have a lot of writing going on, like data and cache. System doesn't have that much I/O so leaving it on ext4 isn't significantly detrimental.

And [MENTION=4544860]osm0sis[/MENTION] is correct - the System partition is tiny...this means that some roms+gapps combos won't work at all because of the f2fs overhead. For example, I used to use Vanir, but then when they started to odex everything (early July, I think?) I wasn't even able to install the PA Gapps micro package, since I didn't have enough space.
[Samsung Galaxy Nexus] osm0sis:
Bingo! Same reason I left discard on ext4 for /system in the fstab, you're not doing a lot of writes so it's better to look at the long-term performance of the partition. :)

I've found it about the same, maybe a little quicker, but that could be placebo. On-device copies, writes across my home network and even that initial adb push back seemed a bit faster. People said the Play Store lag is improved and I guess maybe that's true too.
[Samsung Galaxy Nexus] HONG86:
Well.

I think...f2fs is fast than ext4.

but it's laggy and some bug.

In use LiquidSmooth,

ext4-dalvik fine

ext4-ART fine, too.

f2fs-dalvik good (include bug and laggy)

f2fs-ART bad (fast all the time... but stuck sometimes, and huge lag for me...)

I think, it is not an effect of ROM or kernel...

Just in my opinion...:o

I used f2fs about 3 months...

but I will get back to ext4 soon.:)
[Samsung Galaxy Nexus] sergialess:
I think ART is not for our GNex.

F2FS is working great for me.
[Samsung Galaxy Nexus] Jar3112:
Which bugs are you talking about?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] HONG86:
Freeze phone(need battery out-in), Termination of the application(some apps)
[Samsung Galaxy Nexus] Punkiderma:
I had some of these bugs while I was running with all f2fs,including system. Now that I have only data and cache f2fs,everything is running great
[Samsung Galaxy Nexus] poo706:
I tried f2fs out on my nexus 7 for quite a while and had the same experience. Never tried art either way, but I also had huge 20-second or so lockups that were never present on ext4. Since switching back, I haven't had a single one. To each their own, but for me, it was more hassle than what it was worth, even without the lockups.

[poo]
[Samsung Galaxy Nexus] osm0sis:
ART on KitKat is a waste of time.. It's alpha quality, even with the great fixes devs have provided. Now Android L's ART, which is almost completely different, will be exciting..
[Samsung Galaxy Nexus] osm0sis:
/system/etc/media_profiles.xml is fine. Even tried adjusting a few more things in it, like making the encoder max dimensions also cap out at 720x1280, and lowering the bitrates of the 720p presets but it still presents the same.

[MENTION=4608636]bsmitty83[/MENTION] I guess there must be a little too much reclaimed somewhere, any chance you know off-hand or could easily hunt it down? Rear 720p should definitely be working since it does on other SuperRAM kernels. :good: :)
[Samsung Galaxy Nexus] bsmitty83:
Its something with the new camera.apk , I still have the old cam on my phone and 720p recording still works on the front cam . I haven't changed anything ram related in months
[Samsung Galaxy Nexus] osm0sis:
Yeah front works. Rear doesn't. I assume it's because the framesize is larger on the rear so it pushes for too much memory. :confused:

I didn't think it was something you changed, just that Google Camera (or their new change?) must require more memory so maybe giving it a couple more to play with would make it work? I'm testing out DirtyV (ASRAM) now to verify.
[Samsung Galaxy Nexus] bsmitty83:
Strange ..... Idk , I can try doing a sr build with less ram reclaimed , but there's only a 20mb difference between sr and dirtyV

I'll look at the logs and see if I can figure out why its fc'ing
[Samsung Galaxy Nexus] bsmitty83:
Edit : I just went into the camera app and wiped cache and 720 recording works again [emoji6]

But only for the old camera , not the Google cam
[Samsung Galaxy Nexus] osm0sis:
Definitely no issues all the way up to 1080p with ASRAM. :good:

I noticed that leaving 720p selected for rear on the ASRAM and then flashing SuperRAM resulted in 480p being selected and a bottom CIF option being added like for the front camera. Tested and it is using the correctly selected profile though. 480p on SuperRAM after flashing does make a 480p vid.

Yeah the issue is definitely Google Camera here... Must just somehow be a bit more memory hungry with 720p than AOSP Camera is.
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4544860]osm0sis[/MENTION]

I'll see how much more ram it needs to function , could only be 5 MB or something .
[Samsung Galaxy Nexus] bsmitty83:
5mb was enough , I'm gonna see what the cutoff is tho

Turns out 1mb is enough . next build it will be fixed
[Samsung Galaxy Nexus] osm0sis:
Bam! Another win for Team Dirty! :D

I've noticed Unified v2 magically also fixed the increased boot wait we saw with Unified v1. :cool: