yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] krweby:
Bootloop this morning. :(

---------- Post added at 08:28 AM ---------- Previous post was at 08:11 AM ----------

Hmmm. I didn't try going into recovery this time. I just picked power off and then powered it back on. I'll have to see if I get the same results as you did.
[Samsung Galaxy Nexus] xiaoaxel:
this kernel have 4.3 version?...
[Samsung Galaxy Nexus] cujo6801:
It has this...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] krweby:
Just noticed there is no 1080p and after filming video there are issues with the camera until rebooting. Going back to 4/19 fixed this.

Looks like it is just the test kernel. DirtyV-UR 7/17 doesn't have this issue.

I'll add this before this just gets over looked because of unrelated posts. [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] KJW979:
Definitely one of the settings o changed caused purple tint, gone on stock settings. Have to wait until tomorrow to see which one, 5:30 for work isn't far off, gotta sleep.
[Samsung Galaxy Nexus] osm0sis:
With koush's you forgot to remove that dump image set perms line so it'll fail on latest cwm since dump image doesn't exist. :(

P.S. Send me a PM with the version you tried with my "AnyKernel 2.0" stuff and I'll see if I can figure out what the problem was. :good: :)
[Samsung Galaxy Nexus] metalspring:
same here
[Samsung Galaxy Nexus] bsmitty83:
Cool thanks man I'll do that as soon as I can
[Samsung Galaxy Nexus] bsmitty83:
I get a tiny slowness if my min is set to 230 , but at 350 its instant on
[Samsung Galaxy Nexus] Nephilim:
It's all good man! Much appreciated and enjoy the beer! I look forward to the next iteration of DirtyV tomorrow!!

Btw, might I suggest to keep them easier to differenciate by starting a number scheme. For example:

DirtyV_Lite420

DirtyV_SuperRam420

SmittyV420

And then with each new update increase the number by one i.e. 421 for next build. Then it will always be easy to find the exact version we want from your devhost on the fly and the only real addition you will have to add to the OP would be a notation letting everyone know all builds are made with Linaro 4.7.x and metalspring will be supplying Sabermod alternates when needed.

Just my 2 cents on making things a bit easier. Also, all you'll have to do with the thread title is update the release number as well. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
This thread is moving too fast to keep up lol

Doesn't help my pc is running pretty slow at the moment

I'm currently compiling a test build to see if I got things set up properly to get official omni builds for toro and toroplus going :p
[Samsung Galaxy Nexus] bsmitty83:
Yes each one will go up by v# in the op its v2 ,v3 etc . I'll set up folders on my devhost for all three kernels so its more "professional" lol . but yes I'll try to be more organized MOTHER . lolz
[Samsung Galaxy Nexus] fracama87:
I read only from Tapatalk...can't keep this speed from pc... O.o

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Damn straight. :p

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
You can always try my color settings, they are pretty nice (if I do say do myself lol)

Contrast -14

Gamma adjustment 6

Gamma offsets -6 red, 0 green, 8 blue

Color multipliers 200 red, 200 green, 265 blue

Content adaptive brightness off
[Samsung Galaxy Nexus] bsmitty83:
Those dsscomp errors in the log are gone too
[Samsung Galaxy Nexus] clnzx2:
Test kernel is working great. Only thing I noticed is a little lag while downloading but not bad. Westwood/row/interactive
[Samsung Galaxy Nexus] Nephilim:
Downloading always causes lag, its an android thing. Nothing can truly fix that. At least as far as downloading from play store.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] sd3993:
Weird. I don't get any lag while downloading. The only lag i get is when part store is installing the app
[Samsung Galaxy Nexus] wavedashdoc:
I think that's what he is referring to. The install lag.
[Samsung Galaxy Nexus] clnzx2:
Nope downloading a ROM through the browser no lag on sr2 but slight lag on test kernel. I was running fiops/hyper on sr2 now testing row/interactive on test kernel, assuming its the combo. And by no means is it bad but when things are running as good as they do with this kernel you start to notice the little things
[Samsung Galaxy Nexus] Charmacas:
The wake up lag is still there with the test kernel. Sometimes when waking up the device as normal and often when you turn the display manually off and right after trying to turn it on again.

Also what does ROW from AK mean? Are the tunables just different or is the scheduler algorithm different?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] clnzx2:
Yeah after letting phone sit for a few minutes I also experienced wake up lag :(
[Samsung Galaxy Nexus] Charmacas:
I did set the min clock speed to 230 and did not mess with voltages.

Did you change anything?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] rajputrajat:
You must be second biggest reason why people are always wandering in this thread :D
[Samsung Galaxy Nexus] bsmitty83:
Sweet ! Finally an answer to the question lol , now that I know that didnt work , I believe it's synapse . only because it's the only way in my mind some people get it some don't . maybe its not , but right now it's my best lead. If it was in the kernel or ramdisk , Everybody would experience it. So if your NOT using synapse AT ALL and still get the reboot issue , let me know .

I don't want this issue to be there anymore , even though it dose not affect my phone , it drives me insane that I do not know why the bootloop on reboot happens . [emoji53]

So I'll keep looking as well , hopefully we can get this thing working properly for everyone
[Samsung Galaxy Nexus] Madsunable:
I use tricksterMod and get this bootloops :mad:
[Samsung Galaxy Nexus] bsmitty83:
$hit [emoji39] , well OK , scratch that I guess . .. It appears to be totally random , no matter gsm or LTE , ROM , whatever . I have no idea what the cause is .
[Samsung Galaxy Nexus] Madsunable:
I use paranoid android and your awesome kernel on my maguro. This bug is not the end. ;)
[Samsung Galaxy Nexus] krweby:
All I can say for sure is it is something that changed after the 4/19 kernel. I didn't have this issue until after that kernel.
[Samsung Galaxy Nexus] 7175:
7-19 Kernel is working great on Carbon. I don't use trickster or synapse, but I use Performance Control and my own scripts instead. I haven't had any boot problems or boot loop issues. Network is working great wifi and data. Performance seems up from the June kernel. Everything seems a bit quicker. :) Excellent job bsmitty83 and osm0sis.
[Samsung Galaxy Nexus] cujo6801:
Go and get it...

[MENTION=4183312]Droid_Life[/MENTION]: Download: Google Play 4.9.13 Rolls Out, Features New Design in Listings - http://goo.gl/Wsy0pt #android http://twitter.com/droid_life/status/491735903069814784/photo/1

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
I've gotten no bootloops in the 2 days I've used the newest SmittyV. Tried rebooting about a dozen times just to test and alls been good. Using trickster as always.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] sagara.sandaru:
[MENTION=1533050]bsmitty[/MENTION] can you go back to previous voltage settings please!? with cm voltages I have a huge battery drain. I tried uv to previous values but after that phone starts to lag.

I went back to 6/15 and everything's good.
[Samsung Galaxy Nexus] KreNtal:
I use trickstermod and i have bootloops :(
[Samsung Galaxy Nexus] Punkiderma:
Also here trickstermod
[Samsung Galaxy Nexus] fleckdalm:
Thanks for your hard work!

Unfortunately I don't use neither synapse nor trickster mod so this can't be the issue! Could it be related to charging? I suppose that it happens more often when it's currently charging... Im on stock Vanir Rom.
[Samsung Galaxy Nexus] KreNtal:
Maybe Xposed could be the problem of bootloops...
[Samsung Galaxy Nexus] cujo6801:
I use xposed on every ROM

W/smittyV no bootloops here

Sent from the "DOG" pound
[Samsung Galaxy Nexus] angourakis:
Today I experienced this reboot issue. My phone became very slow and hot and suddenly a reboot and it still on Google logo until it again rebooted to Google logo, so the only way was to pull out the battery so the phone started normally.

I do not use synapse or Xposed or anything else. Just CM ROM + TricksterMOD + DirtVURSR

One thing that comes to my mind as I haven't experienced this problem while using Dalvik. Yesterday I've changed to ART and today the problem happened...

Are the guys who has this problem, using ART?

Regards
[Samsung Galaxy Nexus] oman0123:
I use trickster. I also get the Google bootloop.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] EAK128:
Noticed the micro lags were more noticeable in the latest kernel, also got a sod in the car.
[Samsung Galaxy Nexus] mrgnex:
Yep, had this too. I use vanir f2fs and 15-6 smittyv. I didn't pull any log since they were gone (on reboot they disappear right?). Also I had a notification with the led on and that still flashed while it was rebooting. Let's see if it happens again. Tip for [MENTION=2850718]angourakis[/MENTION] try to raise the mpu voltage by 25 mV.
[Samsung Galaxy Nexus] angourakis:
The funny part is that I've left the voltages kernel stock and if I am not mistaken, [MENTION=4608636]bsmitty83[/MENTION] already raised the voltages a bit, I think he left it as Google stock. Might be something else.

Maybe some commit implemented previously (I remember to have this problem for, at least, two different versions of the kernel) as other kernels I do not have this reboot issue, but others has some micro lags which I have rarely with this great kernel, and I do believe it is something memory related (maybe it cannot manage effectively as it should and the apps are becoming more ram consuming...)

Anyway, just a guess. I cannot take logs as well because it happens when I am at college =(
[Samsung Galaxy Nexus] krweby:
I don't use Xposed and have bootloop issue. I also use trickster.
[Samsung Galaxy Nexus] bsmitty83:
The only time I've ever had this issue (and I've had it on other kernels too ) is when trickster mod gets borked , I hit recovery and wipe cache and dalvik . usually it resolves it .

I did push the volts up to stock . but since there is no "stock" settings for the oc frequencies and non stock freq , I made them as close to what I thought they should be . so there still is room to improve I'm sure .

I'm still looking into the reboot bootloop issue , just haven't had time to sit down and do anything . my shop has a lot of work from Honda that is on a deadline that is rapidly approaching , and my wife and 2 kids take up the rest lol . hopefully in the next few days I can get something out .
[Samsung Galaxy Nexus] bsmitty83:
OK here's another test kernel for the reboot bootloop issue , if your experiencing them please flash this and let me know if the problem is still there

I dont get them on my nexus so I am relying on you guys to let me know if it works or not
[Samsung Galaxy Nexus] angourakis:
Take your time, it just happens sometimes and is just a matter of pulling the battery out (although I'd like to provide a log to help sorting this out)

I don't think it's voltages related as once it reboots, the phone will be in an infinite Google logo loop. But anyway, you're the developer. I'm gonna test this version and report to you.

Thank for your work!
[Samsung Galaxy Nexus] windfrenzy:
bsmitty, very much admire your persistence in working the reboot issue in the face of how random it appears to be. I've had it come and go as I flash new versions of the kernel. I use TWRP, Trickster mod and Omnimetal. I've seen it on Dalvik and ART. Thanks for all your hard work. I'll give the test kernel a try.
[Samsung Galaxy Nexus] thoiloidainhan:
Another thing i noticed with the reboot looping issue is that it happens after a long uptime, like 2 or 3 days. I just tried rebooting with usr latest official release with 10 hours uptime and it booted fine, whereas i rebooted the phone this morning (uptime approaching 72hrs) and bootloop galore. I bet that your gnex never has more than 10 hrs uptime with all your experiment ?
[Samsung Galaxy Nexus] angourakis:
In fact, this problem happens when I let my phone turned on during all the day and night (because I use the alarm app to wake me up). Seems like a reboot every morning would help the phone to keep running smoothly for a longer time.

Anyway, so far so good, no reboots with the test version (and I am using the same way as always)

Regards
[Samsung Galaxy Nexus] bsmitty83:
Surprisingly enough my gnex usually has at least 24hrs up on it . I do flash a lot of zimages but recently not as many
[Samsung Galaxy Nexus] Punkiderma:
Same here
[Samsung Galaxy Nexus] davidmi58:
Hey Smitty,

I have had the bootloop problem as well and really appreciate the time you are taking to try to find a fix for those of us who are having it. I tried the new test kernel and an sorry to report that it did not fix my bootloop issue. Rebooted today and it went right into the loop. Not only that but my phone does not seem to want to deep sleep very much at all. Battery ran down to 10% today in about 6 hours and the phone basically just sat next to me on my desk during that time. Battery stats said the phone spent most of it's idle time at 512 doing nothing. I have NEVER had this problem with any other one of your kernels They all sleep reliably and regularly. Went back to SmittyV 7-17.

Really appreciate everything you are doing to keep my old gnex going, though. Thanks again.
[Samsung Galaxy Nexus] bsmitty83:
It's OK , I need to know where this is coming from so I need to know failures , I'll get a new one out asap , thanks for testing and reporting lol .

And hey at least if you flash the test kernel you get to use the zzmoove governor [emoji39]
[Samsung Galaxy Nexus] davidmi58:
I dunno Smitty. My phone is really acting weird. Sending day old messages, really sluggish. I am going to wipe and reinstall everything. Might not have been the kernel. Will give it another shot after that and let you know.
[Samsung Galaxy Nexus] bsmitty83:
What kernel are you using ?
[Samsung Galaxy Nexus] davidmi58:
Well, after wiping and reflashing, I went back to SmittyV7-17 but I will try the new kernel after I finish setting everything back up.
[Samsung Galaxy Nexus] krweby:
Flashing your newest test version now.
[Samsung Galaxy Nexus] quickdraw86:
Are the bootloops possibly caused by filesystem or recovery issues? I.E. for those with the bootloops, are you running 4ext or F2FS? and which recovery version? This has probably been asked before, but just an idea since the posting of the test kernels to try and isolate the issue...
[Samsung Galaxy Nexus] büscher:
Its not ext4 or f2fs related, had it on ext4 days and now on f2fs.

Also with the filesystem change my recovery changed from PhilzTouch cwm to TWRP, still happens...
[Samsung Galaxy Nexus] seriousia:
I'm using synapse but still I also get bootloop.

So imo trickster is not the problem. :rolleyes::rolleyes::rolleyes:
[Samsung Galaxy Nexus] davidmi58:
After wiping and reflashing, the new test kernel seems fine so far. Rebooted this morning and no bootloop. Phone slept fine last night. Thanks bsmitty! You are great!
[Samsung Galaxy Nexus] dbh369:
Just got my new phone, lg g3. Loving it so far but miss all the tuning i had with dirtyV! Maybe someday smitty will try this phone out. Meanwhile still lurking because i learn so much here!

Thanks again got all your work
[Samsung Galaxy Nexus] Punkiderma:
Trying test 2, had another bootloop :(
[Samsung Galaxy Nexus] blmvxer:
I'm having no issues with 7-17 F2FS with my own CM11 build!!!
[Samsung Galaxy Nexus] krweby:
Bootloop on test2.
[Samsung Galaxy Nexus] bsmitty83:
Can you or someone do me a favor ? I'll post a zimage and I want someone to fastboot the zimage over whatever ROM your running . so the ROMs own ramdisk remains in place . I want to see if the problem is kernel or ramdisk . if you flash it it will break certain things like WiFi hotspot ,no synapse , and some governor tunables . so let me know if you or anyone with the reboot problem wants to do that .

Thanks [emoji106][emoji14]
[Samsung Galaxy Nexus] angourakis:
Count on me!
[Samsung Galaxy Nexus] Punkiderma:
Not at home today, but I can do it! Basic things (phone, mobile data)will work anyway?

Thanks!
[Samsung Galaxy Nexus] krweby:
If you still need someone Monday I can do it. Work on building a play area for the little one this weekend.
[Samsung Galaxy Nexus] cujo6801:
Nerd......

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Jar3112:
I'm not able to mount USB otg in twrp f2fs recovery, has anyone else experienced this?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pattyboi:):
i need to meet her..
[Samsung Galaxy Nexus] knuspertante:
made my day ;) ^^
[Samsung Galaxy Nexus] Punkiderma:
Also [MENTION=4608636]bsmitty83[/MENTION] , test 1 didn't resolve the bootloop issue,but on my phone I've got less loops. Instead, with test 2 I get them almost every time I reboot
[Samsung Galaxy Nexus] bsmitty83:
ok here's test kernel 3 for the bootloop on reboot issue . Hopefully it will take care of the problem but again i cant test it so it's up to you guys

let me know how it works ..........
[Samsung Galaxy Nexus] thecoolkid:
I have the same issue. I use my pendrives for backups ;) swiched to F2FS church recently... anyone able and willing to help?
[Samsung Galaxy Nexus] blmvxer:
Will you be making a bigmem version of F2FS kernel?
[Samsung Galaxy Nexus] Jar3112:
[MENTION=4608636]bsmitty83[/MENTION] can you tell me something about USB otg not mounting on f2fs twrp recovery?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] akhi24nick:
Carbon ROM latest nightly with latest 17-7 f2fs DIRTY V-UR

I dont have bootloops on rebooting.

EDIT : I am using a Maguro
[Samsung Galaxy Nexus] poo706:
I use touch control and have the bootloop problem. Anyone NOT using TC have bootloops?

[poo]
[Samsung Galaxy Nexus] Hetalk:
I've never used TC or PGM and had bootloops.

So, that's not the issue here.
[Samsung Galaxy Nexus] poo706:
Easy come easy go. Couldn't remember if that idea had been thrown out in the past.

[poo]
[Samsung Galaxy Nexus] namtombout:
Congrats on getting a 1,000,000+ views in the thread [MENTION=4608636]bsmitty83[/MENTION]

Ive been using [MENTION=4544860]osm0sis[/MENTION] android image kitchen (still cant believe how easy it is to use) and i wanted to try dirty on 4.3 but i read over the beginning of the thread and realized your kernel started as anykernel and not 4.3 ramdisk version of the kernel. Im going to try to use Vanir kernel 4.3 ramdisk with the 7/17 version of dirty. Anyone know approximately how much optimizations would i be losing by trying this?

Edit: lost all optimizations because it wouldn't get through the boot animation.
[Samsung Galaxy Nexus] pvkiniyan95:
my short story....

went back to vanir 4.3 formatting to ext4....things aren't the way i thought.

came back to vanir 4.4 f2fs......feeling home...

its hard to use 4.3 without gpl, and mainly i found the kernels have evolved so beautifully specially ramdisk which lack in 4.3
[Samsung Galaxy Nexus] osm0sis:
Try making your own AnyKernel2 zip with the 7.17 zImage by adding it to the latest zip push: https://github.com/bsmitty83/DirtyV_tuna/blob/DirtyV-f2fs/AnyKernel2/UPDATE-AnyKernel2.zip

If that fails (though it shouldn't..) you could probably hybridize it with my 4.3 f.K ramdisk pretty easily. :)
[Samsung Galaxy Nexus] dlabadie:
Bootloop on restart with Test3 on OmniROM FML
[Samsung Galaxy Nexus] pattyboi:):
so guess whos rocking the latest dirty with FML ;)

my big sister handed down her gnex for me,but she wanted me to say thanks to [MENTION=4608636]bsmitty83[/MENTION] for helping her enjoy her phone alot more for the time she had it :)
[Samsung Galaxy Nexus] cujo6801:
Nice to have you back bro...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] namtombout:
I'll try the any kernel version tomorrow. I derped on it. I looked for an osmod 4.3 in your dev host and couldn't find it. I got the latest dirty working with franco's unmodified r395 ram disk.

Thanks Os and smitty
[Samsung Galaxy Nexus] rkpeterson:
If any one is interested...

http://www.mediafire.com/download/6xc4h2y2b3t5k8c/LS-KK-v3.2-F2FS-2014-07-28-maguro.zip

http://www.mediafire.com/download/q3yx1o2m93jbwal/LS-KK-v3.2-F2FS-2014-07-28-toro.zip

http://www.mediafire.com/download/oslfhe5zuei6h8c/LS-KK-v3.2-F2FS-2014-07-28-toroplus.zip
[Samsung Galaxy Nexus] windfrenzy:
No bootloop on Test3 after install, but just got it after 23 hrs uptime. Toro,

TWRP, Trickster, Omnimetal.
[Samsung Galaxy Nexus] danielstar13:
I have flashed DirtyV-URSR-7.17.14.zip to my F2FS PA with TWRP 2.7.1.1 and I wiped dalvik and cache, and now it doesnt reboot. What should I do and how should I flash DirtyV to a F2FS ROM? Please help. :(
[Samsung Galaxy Nexus] asteriosd:
Hello everyone. Does anybody has problems when trying to connect to 5 Ghz wireless networks? It seems like with version 7/17 I can no longer connect to them.
[Samsung Galaxy Nexus] krweby:
Bootloop on test3. Toro 32GB internal storage aokp.
[Samsung Galaxy Nexus] blmvxer:
Are you using ext4 or f2fs?

I'm running the latest kernel on my cm11 f2fs build with no issues.
[Samsung Galaxy Nexus] bsmitty83:
So as we all see by now , this issue seems to be only affecting some people and not others ..... No idea why . it has to be something some are using and others are not . idk what but I'm convinced its not in the kernels code . I've been racking my brain trying to figure out what it could be . I really don't know . maybe [MENTION=4544860]osm0sis[/MENTION] can offer up an opinion or anyone really . I know its not recovery related , ROM related , or filesystem . I really want to solve this so I can work on other things but really until this issue is solved..... I don't want to leave it like that and have some people not able to reboot properly .

As for otg not working in recovery , Its a know issue with the recovery . ill see about making a new one , but again the kernel comes first so I'll be concentrating on fixing the reboot bootloops some get .

( really it pisses me off more than anything , lol , that this problem is there and so random in appearance , and I haven't a clue for the cause .)

Hack the Tuna
[Samsung Galaxy Nexus] krweby:
ext4 but this issue existed before f2fs was introduced to the kernel.
[Samsung Galaxy Nexus] osm0sis:
Unfortunately it's never been a problem on franco.Kernel, which points to code and should rule out ramdisk, since they're both from me, and used to have pretty much the same stuff back when I was doing f.K osmods. :(

You've said at different times that the issue has been reported even on stock Vanir.. Maybe the base has always been the problem; something from before you even got started.
[Samsung Galaxy Nexus] krweby:
The problem doesn't exist in the 4/19 kernel or before that. If that helps any. [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] Oracle_Eldorado:
does it work with this rom ?

http://xdaforums.com/galaxy-nexus/development/rom-paranoidandroid-4-4-t1619582
[Samsung Galaxy Nexus] bsmitty83:
quite possible its in the code . I just don't know what would cause it on some phones and not others ? how is this possible ? I've yet to reproduce the bootloop on all kinds of test kernels

but I'll post a zimage to fastboot for those with the problem , fastboot it over your stock ROMs boot.IMG , use it as you would normally and see if it happens or not . that's about all I can think of to do .

Hack the Tuna
[Samsung Galaxy Nexus] DR3W5K1:
Have we tried to see if it could be different bootloader versions for the bootloop issue?