yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Castro27:
I don't know if anyone posted about this before but here I go. I'm using the latest Dirty-v UR release and sometimes, after a system reboot (power button - reboot), my phone keeps looping at the google logo. After a battery pull everything works just fine. Has anyone experienced this before?

EDIT: Yeah, it's a known issue, my bad. Haven't had the time to keep up. Sorry
[Samsung Galaxy Nexus] crazyeats:
That bug has been around awhile. Some users are luckier than others but its known and being worked on. Hope that doesn't steer you away. Great kernel regardless.
[Samsung Galaxy Nexus] Castro27:
Nah, I can deal with it. Dirty-v is the best kernel that I've seen here in quite some time, I have no plans to steer away from it.
[Samsung Galaxy Nexus] Rushead:
Don't pull battery; just hold all the buttons on a bootloop.
[Samsung Galaxy Nexus] Charmacas:
Pulling the battery is the only thing that works for me. I don't know what's causing this but it is annoying. I would like to help in resolving but I have also no clue how.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] chongns:
Hi Guys, sorry for the too "short" post.

i should write as "the ROM Ram zip maybe is the problem"

as the FML changed some thing in the F2FS merging into the ROM, link here
[Samsung Galaxy Nexus] AgentSmith:
Just wondering. Do you plan to integrate the new GPU driver when [MENTION=2633638]Ziyan[/MENTION] has it fully functional?
[Samsung Galaxy Nexus] bsmitty83:
Probably if I can use his work and bring it over to my kernel . if not I'll have to use his kernel as a base and make a new kernel . I'm looking into both
[Samsung Galaxy Nexus] massoudsh:
I cant wait for next version of your kernel....?
[Samsung Galaxy Nexus] namtombout:
Its been a week plus without a gnex kernel from you, if you ever start going thru withdrawals or get bored can you try posting an any kernel zip or a 4.3 ram disk version since the latest is so stable. :smiles:
[Samsung Galaxy Nexus] iluvamk:
What is causing this kernel wake lock? Keeps awake over 50%of the time.
[Samsung Galaxy Nexus] Rushead:
If you're in a bootloop, holding the buttons will work (unless your buttons are broken) because the phone will detect the buttons being held as it goes through the loop and will enter bootloader. Just be patient. The idea that pulling battery is the ONLY thing that works (again, assuming that your buttons are functional) is false.

If you're having an SOD, you have to pull battery.
[Samsung Galaxy Nexus] osm0sis:
Read how to use BetterBatteryStats. PowerManager = Partial Wakelocks = Apps. Go to that. If you see AlarmManager there, then go to Alarms.
[Samsung Galaxy Nexus] Charmacas:
You're not right and not wrong. Holding the buttons is working but neither directly starting from the bootloader or going into the recovery and reboot from there results in another bootloop. Hmm...

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Rushead:
From my experience, you must boot into recovery first, then reboot system for it to work. Booting system from bootloader results in further bootloop.

You're saying that booting into recovery from bootloader also results in bootloop--not for me. Interesting. Could be your version / choice of recovery that makes the difference? :eek:
[Samsung Galaxy Nexus] IIEtCII:
السلام عليكم

اخي انت ليش زعلان ؟

الحادثة حصلت في الحقيقة ، وما في احد سب اللغة العربية ولا شيء

والكلمة المذكورة هي صحيح كلمة عامية ولكنها منتشرة في اكثر من دولة ولهجة ؛ وليست خاصة بدولة معينة

والحادثة طريفة ولم يستنقص من احد فيها

رمضان مبارك

lol

that word is not in original Arabic.. its like in slang Arabic

but every Arabic speaker know it :D

and yeah Urdu and Arabic have many words in common

but not the swearing words obviously like what you said lol
[Samsung Galaxy Nexus] lollipop:
:good:
[Samsung Galaxy Nexus] osm0sis:
This is pretty interesting! Looks like a different way to unify things. I tried doing "auto" in the fstab when we were trying to get encryption to work again and it caused hung boots, but this is a more complete way without copying files around. I'll definitely play around with it.

Still doesn't really reveal why my method in DirtyV would keep FML from booting.. [MENTION=3390093]MWisBest[/MENTION] any ideas bro? :)

Edit: I tried using MWis' method on DirtyV but it doesn't work, at least not with Carbon. Is there something ROM-side required to get the fallback method to work?
[Samsung Galaxy Nexus] HaRdC0r3:
This is a ROM related thing but I assume most of the gnex users use dirtyv kernel......for all you ROM devs....

https://github.com/rascarlo/android_vendor_rascarlo/commit/65404d3749c3943d9bfc69829ea1be1d06215546

Fix's wakelock on playstore.

Please remove my post if necessary....thanks.
[Samsung Galaxy Nexus] MWisBest:
https://github.com/MWisBest/android_system_core/commits/omni-4.4

I did get auto working in the fstab with this: https://github.com/MWisBest/android_system_core/commit/5134a1ed80c1fe37a420c67d2f98c79ca4a66f70

However, Motorola's fallback thing ( https://github.com/MWisBest/android_system_core/commit/32de24cb485de72a5449e89fe4ff154dea9cc84a ) allows for specifying different mount options for each filesystem type versus having to lump them altogether with using auto, which is nicer in my opinion, plus Motorola's stuff would have a good chance at being merged into AOSP should they choose to submit it so by supporting it now I'm prepared in the event that it does indeed end up right in AOSP.

I'm not sure what's going on with DirtyV and FML right now, I'll look at it soon but I got some other things on my plate at the moment too.
[Samsung Galaxy Nexus] chongns:
[MENTION=4699837]pvkiniyan95[/MENTION], did you Gnexus bootup now using dirty V?
[Samsung Galaxy Nexus] pvkiniyan95:
No, I went back to FML stock kernel
[Samsung Galaxy Nexus] poo706:
[MENTION=4278473]Hetalk[/MENTION], would you mind adding a link to my converter tool in post #2? http://xdaforums.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702

[poo]
[Samsung Galaxy Nexus] Hetalk:
Sure buddy. It's high time I do make a update. Lots of stuff has changed since.:good:

On a unrelated note, I'm thinking about flashing LS on my maguro. Will you be posting a new build for it soon?

Edit 1: Post#2 updated with more info on f2fs development.

Edit 2: BTW, I'm running latest paranoid with latest dirty on f2fs and it's working awesome. Thanks for dirty and f2fs [MENTION=4608636]bsmitty83[/MENTION] and [MENTION=4544860]osm0sis[/MENTION]
[Samsung Galaxy Nexus] osm0sis:
Thanks. Yeah, I tried the fallback method and it gets stuck at the bootani on Carbon, not sure why since that's well passed where the mount_all should be loading things.
[Samsung Galaxy Nexus] poo706:
I appreciate the shout out. And sure, I put out a toroplus yesterday because the last official was on 7/1. Might as well follow that up with a maguro today. Assuming no issues, it'll probably be up in 4 hours or so.

[poo]
[Samsung Galaxy Nexus] MWisBest:
If mount_all successfully mounts /system, but fails to mount /cache or /data, being stuck at the boot animation would be the result.

I was having the same problem before this commit: https://github.com/MWisBest/android...mmit/3dfe5fcc44aeb7a267017879ed21d4064acf7b8c

(that being with an ext4-formatted /system and f2fs-formatted /cache and /data.)

BTW, other ROM-side commits added related to F2FS were these:

https://github.com/MWisBest/android...mmit/4c7f14b4e3a5953c12d7688bacafa7df02b15139

https://github.com/MWisBest/android_system_vold/commit/9e04b8e56b6151ea1d148062019a2abf70371753

Also, for the TARGET_SETS_FSTAB := true change to have any effect, this commit is required: https://github.com/MWisBest/android_build/commit/f6453d6f971d594cef36dfa2ee3b66bae1e6a81d

^That TARGET_SETS_FSTAB thing was what resulted in the ability to flash the ROM on both ext4 and f2fs without any conversion junk.
[Samsung Galaxy Nexus] chongns:
Sorry for that.

i have get the smitty-v flash through.

my Gnex is a maguro

no sure, what is your side problem, but my setup was full F2Fs, i use pa gapps 4.4.4 (not sure is this a concern)

and i wipe again using FML recovery on system and cache before flash the rom
[Samsung Galaxy Nexus] osm0sis:
I tried using your exact fstab from that commit with all ext4 and it still hung at the bootani. Isn't unified f2fs support fun? :p

It doesn't seem like it should rely on the ROM for fallback but I'm not sure what I could be doing wrong. I'll get your boot.img and see if it'll load on Carbon; if so I'll run a diff, if not, we'll have our answer about ROM support. :)
[Samsung Galaxy Nexus] chongns:
Maybe you can try swap the vold file with FML, Not sure 100%
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=4608636]bsmitty83[/MENTION] i just figured out why i cant flash dirtyV in latest FML , coz dirtyV isn't compatible with system being ext4 while data and cache being f2fs...

i can boot up if all partitions are f2fs or ext4

---------- Post added at 05:12 PM ---------- Previous post was at 04:54 PM ----------

just found out, dirtyV not compatible if system is ext4 and data, cache in f2fs...

only works if all are f2fs:good:
[Samsung Galaxy Nexus] osm0sis:
Well there's one mystery solved! Now to figure out why I can't seem to adapt MWis solution over to DirtyV. :)
[Samsung Galaxy Nexus] MWisBest:
Well... it will require this for sure: https://github.com/MWisBest/android_system_core/commit/32de24cb485de72a5449e89fe4ff154dea9cc84a

If the ROM isn't built with that, the fallback thing isn't going to work.

I thought you were building the ROM from source with that change cherry-picked in or something.
[Samsung Galaxy Nexus] osm0sis:
:good:

Ah damn! Add that to the list of required commits for F2FS. ;)

Fallback is a such an easier way to unify things. Great find, and thanks for the help. :D

[MENTION=2765426]styr[/MENTION] [MENTION=2633294]DHO[/MENTION] [MENTION=4015637]rkpeterson[/MENTION] [MENTION=4328678]metalspring[/MENTION]
[Samsung Galaxy Nexus] MWisBest:
Actually [MENTION=2838735]aosp[/MENTION] was the one who first pointed me towards Motorola's stuff and [MENTION=4243514]Hashcode[/MENTION] was the one who separated out some really Motorola-specific stuff from the fallback thing ( http://review.cyanogenmod.org/#/c/65480/ ) :)
[Samsung Galaxy Nexus] amd_h4x0r:
I have tried every combination of rebooting without pulling the battery (holding buttons to get to the bootloader and then trying Restart bootloader, Recovery mode, and even Start) but nothing will let me bypass these damn bootloops except a battery pull or shutting the phone completely off and then turning it back on :mad:
[Samsung Galaxy Nexus] p34rp34r:
Same. I've resorted to using shut down instead of reboot.
[Samsung Galaxy Nexus] Oehr:
Got a strange issue with the new build:

After using my phone for a while (~1 week), i tend to initiate a full reboot (not hotboot). for some reason however, it is stuck in a bootloop, where it restarts the boot process before the actual boot animation of the rom starts playing.

Removing the battery, reinserting it and manually booting breaks the loop and lets me use my phone again.

the reboot issue doesnt always happen though, and it never happens on a cold boot.

P.S. using encryption and ext4
[Samsung Galaxy Nexus] p34rp34r:
Um, not to be a **** or anything, but the previous 2 posts (and many, many, many of the previous pages in this thread) were talking about just this issue. It's being looked into, but since it happens so early in the boot sequence, there usually aren't logs so it's difficult to track down the cause.

You can also try holding Vol up + Vol down + Power while it's boot looping to get to bootloader mode, reboot to recovery mode, then reboot to system if you don't feel like pulling the battery. YMMV. Some of us can't even get that to work.
[Samsung Galaxy Nexus] Oehr:
ooops. you have the right to be a **** and bash me for being a **** myself: I didn't want to bother with all the posts before mine (too many and difficult to locate), so i went with the lazy "ill just throw that info in here. its not a deal break (no brick), so its not that important imo. kernels still teh best in da bizz an' da hood, ya know wat im sayin~?"

apparently, the posts directly before mine covered the issue flawlessly... yeah im with stupid today... off to bed. better not be on the net any longer today!

that said: glad im not the only one affected and it goes beyond my previous encrypted phone issue :)
[Samsung Galaxy Nexus] osm0sis:
Yup. Power off from the bootloader should definitely work if Recovery -> Reboot to System somehow isn't for you. :)

Hmm so my carrier just offered me early renewal, waiving my remaining device balance and giving me $100 toward my new device, but I have to do it before Sept. 30th. Only good option they have is a N5 (already at $0) and I doubt the N6 will be out before October.

Do it or hold out until the contact legit ends in Feb. then get the N6? ;)
[Samsung Galaxy Nexus] Rushead:
I've been off contract for 3 years now. Unlimited data is just too good to give up. I'd say hold out...there's always another deal.
[Samsung Galaxy Nexus] DR3W5K1:
+1 V can have my unlimited when pigs fly
[Samsung Galaxy Nexus] xzilem:
Get it now and join our N5 community :p
[Samsung Galaxy Nexus] p34rp34r:
+1. I'll get a phone on contract when they inevitably take my unlimited away from me. until then, i'll be bringing my own device.
[Samsung Galaxy Nexus] DR3W5K1:
They are forever trying to get me to upgrade.. The latest attempt was a free iphone5.. Guess they think I'm dumb or something¿

How about you guys any attempts at getting you to upgrade? All of mine have been via email BTW
[Samsung Galaxy Nexus] bsmitty83:
N6 looks amazing if they put a 64 bit chip in it . I'd wait for that or get an s5 developers edition
[Samsung Galaxy Nexus] Rushead:
I ignore pretty much everything from big red.
[Samsung Galaxy Nexus] demlv:
When flashing this today I saw a message in recovery advising me to "update to the newest binary". Can anyone explain what that's about? Thread search led me to nothing. Thanks . . . :fingers-crossed:
[Samsung Galaxy Nexus] p34rp34r:
how did you flash it? the only binary i can think of is the su binary. sometimes apps like titanium backup complain about koush's superuser not having the latest su/busybox/whatever binary, but recoveries typically don't care about that.
[Samsung Galaxy Nexus] pattyboi:):
no,its the binary inside the zip,it wont cause problems
[Samsung Galaxy Nexus] poo706:
Didn't know if this would be of any help in the Google logo boot loop: xdaforums.com/showpost.php?p=54029309&postcount=98

Alkemix says he converted my 7/8 unofficial liquidsmooth to f2fs and had nasty boot loops with dirtyv, but not with my 6/30 LS. The link has details of what he did to make 7/8 play nice.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
Thats interesting , I'll make up a kernel zip for people with bootloops on reboot to test out .
[Samsung Galaxy Nexus] Hetalk:
Gimme Gimme !!!:D
[Samsung Galaxy Nexus] Jodsfk421:
Agreed. Still hanging on to my Toro (since 2?/2012) waiting for something to come out to switch to... possibly G3. I just want to make sure there are plenty of dev's...
[Samsung Galaxy Nexus] David 617:
I switched over into the HTC One back when Verizon had a buy one get one deal. We've got awesome dev support over here.

( and I kept my unlimited data... Was on the phone with Verizon for over two hours about it...)

I read that the LG G3 has poor battery life mostly due to its screen. It is a regression from the g2.
[Samsung Galaxy Nexus] crazyeats:
Ha. Wrong thread. Sorry for wasted space.
[Samsung Galaxy Nexus] poo706:
Is that directed at me, in reference to my converter tool?

[poo]
[Samsung Galaxy Nexus] crazyeats:
Yes it was. Thought I was still in your thread.
[Samsung Galaxy Nexus] osm0sis:
Check the Shiny maguro thread, 3rd post or so is me and has a Shiny GApps Remover "Add-on". :)
[Samsung Galaxy Nexus] crazyeats:
Thanks. Guess maybe I should have read that far. Ha.
[Samsung Galaxy Nexus] calebv2:
Yeah I'm sorry but I don't know where you get your info the G3 has amazing battery life.

http://bgr.com/2014/06/09/lg-g3-blo...-in-battery-life-tests-despite-monster-specs/
[Samsung Galaxy Nexus] David 617:
http://www.anandtech.com/show/8169/the-lg-g3-review

"Here, the LG G3 has a major regression in battery life. While the LG G2 had around 11 hours of battery life on WiFi and was competitive with the Galaxy S5 and One (M8), the G3 is around the iPhone 5s (roughly 9 hours) in this test."

Also, if you read the BGR article you quoted, they source their information from PhoneArena

But if you look at PhoneArena's article they state on the bottom -

"Update (Jun 25, 2014): Due to a technical mistake, this article previously stated that the G3 has record battery life of almost 9 hours. We can assure that this mistake is an isolated issue and have updated our our stories to reflect the actual result. Sorry for the inconvenience. "

The new title of the article reads, "The LG G3 trails rival flagships in our battery test."

So basically, PhoneArena botched their original test but corrected themselvels later on. BGR got their news from the original article and didn't bother to make any correction once PhoneArena acknowledged their mistake.
[Samsung Galaxy Nexus] krweby:
Hope this fixs it. I've been on 4/19 forever now. :)
[Samsung Galaxy Nexus] osm0sis:
https://github.com/bsmitty83/DirtyV_tuna/commit/01623c5a6377ab5f374cd6bb6aeddf6bf57957c5 :cool: :good:
[Samsung Galaxy Nexus] a3361035:
How was that determined?

Claiming that the f2fs cleaner job, when it additionally issues trim commands, is not what the OS wants is rather odd.

f2fs cleaner job is prolly even more intelligent than IdleMaintenanceService's fstrim:

a) it's background-process gets triggered based on a cost-benefit algo, not just some idle timers like IdleMaintenanceService

b) it has on-demand process which IdleMaintenanceService's fstrim lacks, that gets triggered when actually needed based on a greedy algo

c) those trims are synchronized with the other f2fs cleanups

No idea why anyone would want to manually trigger trims. f2fs on-demand cleaner job does prolly know more than you.

Not having additionally fstrim, when the fs can already intelligently issues trims, does look like the cleaner solution.

For reference:

https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt
[Samsung Galaxy Nexus] Oehr:
I just tried the TWRP2 with F2FS support (TWRP-2.7.1.1-F2FS/EXT4-MAGURO), but unfortunately, encryption support is broken: "Password Failed, Please Try Again".

The password I entered (tried three times) is correct and works flawlessly with the official release 2.7.1.0
[Samsung Galaxy Nexus] AgentSmith:
[MENTION=5856785]a3361035[/MENTION] those numbers are both 0 in my case - it's actually a very large number and then 3 zero's in that file - suggesting no fstrim commands have been issued by Android so far. Not sure if there's a way to check if trim on delete is working but if it does then f2fs seems to behave quite nicely. Then ignoring the fact f2fs is still labeled experimental the only thing missing now is fsck support.

I just read f2fs.txt again. The cleaning process they talk about in the end is that something else than TRIM? Is the background cleaner not triggered by the OS?
[Samsung Galaxy Nexus] osm0sis:
The other 3 zeros mean you haven't enabled it. If you're on ext4 download Synapse, if you're on f2fs then don't bother (since fstrim doesn't work on f2fs, like we've been discussing). :good:

[MENTION=5856785]a3361035[/MENTION] In my mind, it breaking a function of Android was an issue, but you make very good points. :)

Discard is enabled in 6-28, so rest assured. ;)
[Samsung Galaxy Nexus] KiD3991:
If Germany wins I'll try build a rom using Velocity Rom's sources for GNEX!!!
[Samsung Galaxy Nexus] demlv:
Sounds great! But what sources will you use if Argentina wins?
[Samsung Galaxy Nexus] mangusZen:
On a side note, I switched to f2fs with the recovery linked and found that wiping data actually wipes /data/media too. Makes sense for formatting in f2fs internal storage also, but what if I want to make a dirty flash wiping all but /data/media ??
[Samsung Galaxy Nexus] KiD3991:
My friend builds his ROM for S3 I guess. Only if he wants to. Its a bet. Either way sooner or later I'll try building because I already own a HH so GNex can stay as dev device.
[Samsung Galaxy Nexus] fleckdalm:
WiFi doesn't work for me, whenever I turn it on, it turns itself off again after a few seconds! I'm using Vanir Rom with f2fs in conjunction with this kernel, any advice?
[Samsung Galaxy Nexus] osm0sis:
Are you using the latest version from the OP or did you get a modded version from somewhere else? I know people were doing that for awhile with Vanir.
[Samsung Galaxy Nexus] fleckdalm:
I'm using DirtyV ur from 28.06.14 and Vanir maguro from 09. 07.14 both original version from OP.

Here is a Logcat https://www.dropbox.com/s/80rynl8lctn009e/2014-07-13-21-50-47.txt I hope that helps ;)
[Samsung Galaxy Nexus] osm0sis:
A dmesg would be better, though there is some interesting stuff about wpa_supplicant in there.. Can anyone verify that 6.28 is broken on Vanir?

When's the last time you did a clean flash?

[MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] fleckdalm:
I always flash rom and kernel at once so I can't be entirely sure if it's the kernels fault. The last time I flashed was when the Vanir nightly came out but I'm no sure since when the wifi issue exists because I'm not using wifi very often... I will try to get a dmesg ;)

Edit: here is the dmesg https://www.dropbox.com/s/p0hj9sv3hty43yg/dmesg.txt ;)
[Samsung Galaxy Nexus] osm0sis:
Clean flash means wiped data though. Are you sure it's not just a ROM-side setting change breaking things? A clean wipe would rule that out.
[Samsung Galaxy Nexus] neilrl79:
I installed the recovery for Toro in the OP but don't have the option to format the portions to F2Fs under the advance menu.

[IMG="recovery pic"]http://i857.photobucket.com/albums/ab139/neilrl79/Mobile%20Uploads/IMAG0025_zpskfwyfzhy.jpg[/IMG]
[Samsung Galaxy Nexus] Castro27:
If I'm not mistaken it's under Advanced Wipe, in the wipe menu. Its called "repair or change file system"
[Samsung Galaxy Nexus] neilrl79:
Negative. Just checked to be sure, no option to " repair or change file system". :(
[Samsung Galaxy Nexus] rajputrajat:
Interestingly, I'm using the same combination of ROM - KERNEL - F2FS...

No problem what so ever...
[Samsung Galaxy Nexus] cujo6801:
If anybody feels like testing out a toro (rom) build

this gentleman would like you to

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

Sent from the "DOG" pound
[Samsung Galaxy Nexus] thenemis:
under SETTING , check "Force data and ... to use F2fs" and te sub-option "Include system partition" then the top line ot twrp must switch to red and write f2fs , not ext4.

go to wipe and go to format
[Samsung Galaxy Nexus] AgentSmith:
That's what I was saying actually. Apparently we don't want fstrim with f2fs so the indication that Android doesn't give the command is good news. As I understand this has nothing to do with discard though. We want either discard or fstrim. So now I just hope that discard is working as it should. I don't know how to check that.
[Samsung Galaxy Nexus] Ashtrix:
You can format your phone's filesystem from Ext4 to F2fs by following these simple steps...

1 - reboot to recovery 2.7.1.1

2 - go to settings tab there u find the last 2 options ( a -force data & cache wipe functions to use F2FS, b - include system partition )

3 - check both options

4 - go to wipe-> advanced wipe, here if u wipe u can see the message saying "formatting using mkfs.f2fs" . That means u have your system, cache, data in f2fs format.

And b4 u do this and flash an f2fs rom, go though OP's 2nd post by hetalk, there's a pretty good workaround which is simple and fast :good: !!
[Samsung Galaxy Nexus] RcrdBrt:
There's a problem with native WiFi tethering with this kernel.

It's not a big trouble since USB tethering works great but there must be something related to the bcm driver that can't enable properly the WiFi thether option.