yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] dzap:
And neither have I had any issues with boot loops. Ever. Until recently. After 13x this has been a problem.

I already said in the second follow up post, that I did originally attribute it to user error, but the fact that it happened the exact same time twice, means that it's likely to happen to someone else, that franko's kernel is the one causing the issue. As I am literally just stock rooted, and an older radio, but that's it.

You guys are way too brutal, and why everyone in general hates XDA poster. I am not a noob at this, and this is a genuine, legitimate problem, that I would like to troubleshoot, but you guys do nothing but blame the user.

If you guys have actual solutions, feel free to throw them at me. I have already detailed what I have tried to get it too boot back up, and what most people would try to get it to boot.
[Nexus 4 Original Android Development] thebryceee:
Try that emergency kernel
[Nexus 4 Original Android Development] farmerbb:
Yup, the exact same thing happened to me when I was on r143. Haven't seen it happen since updating to r145/r146 (knock on wood)
[Nexus 4 Original Android Development] dzap:
Thank you for an actual response.

By totally delete, what do you mean?? An overwrite of stock kernel would work? I can get into fastboot and try pushing the stock kernel, but I've done that before. I think he modifies something down on the system level as well with the app.
[Nexus 4 Original Android Development] drawde40599:
It dose not auto flash unless u tell it to, so if u dont want it to unchecked the box.... I dont have any of your issues and never had, no way it's just luck , franco kernel always gos on flawless, its 100% something on your end, something your doing or installed or your rom.
[Nexus 4 Original Android Development] dapsANDpoundz:
Played Candy Crush for maybe 10-15 minutes and my N4 rose to about 141° F. Dunno what settings you guys use that doesn't involve UV that is helping you guys get cooler temps.

SN: I've also never gotten any bootloops flashing this kernel but maybe you guys could quit it with smart ass remarks and actually help the guy. All I can suggest is a factory reset and start over, or flashing the stock kernel. Maybe that'd help.
[Nexus 4 Original Android Development] Mo'HAWK:
I'm not a total techie like some here but Franco uses something that is different from other kernel designers and when that part is not deleted or changed it will create a boot loop.
[Nexus 4 Original Android Development] Vangelis13:
Sorry, misunderstanding. I meant that people get all weird in the weekends..

No offence to you.
[Nexus 4 Original Android Development] thebryceee:
http://xdaforums.com/showthread.php?p=35648172
[Nexus 4 Original Android Development] simms22:
this was fixed a long time ago, the issue with the custom ramdisk. now flashing other kernels dirty over franco kernel doesnt cause bootloops.
[Nexus 4 Original Android Development] dzap:
Gave this a shot, and didn't work unfortunately. Thanks for the advice though. It was a good first step. osm0sis who made it did post some good advice though. I'll start digging around and see what might be causing this.
[Nexus 4 Original Android Development] thebryceee:
Ram disk
[Nexus 4 Original Android Development] Mo'HAWK:
Thanks that's what it was.
[Nexus 4 Original Android Development] 3c:
You don't get bootloop, but still many things fail to work because of this custom ram disk. I've tried many times and it's a real pain to try franco's kernel the "dirty" way. So I tend to have a specific backup for franco's kernel while I can switch between all other kernels the "dirty" way just fine.

EDIT: One of the things that fail is mpdecision and thermal. Not sure about others. Would be nice if franco would actually be more friendly to other kernels (and apps :D).
[Nexus 4 Original Android Development] franciscofranco:
I flash more than 50 Kernels a day, I never had a single bootloop on this device unless I test weird code. Instead of dissing me and this Kernel it would be helpful if gave us a bit more information, how exactly did you flash, what rom are you using, what Kernel were you running before flashing this one etc etc etc. If you want to be helped you have to help us understand your problem.
[Nexus 4 Original Android Development] simms22:
im guessing that mpdecision is disabled in the kernel, like in many other custom kernels.
[Nexus 4 Original Android Development] 3c:
I don't know, but after switching from franco's kernel to any other I verified that mpdecision binary was still there, however it was no longer running at all, same for thermal.

That and maybe a custom over-clocked config might explain why some users then experienced boot loops. In general it can be a pain to get out of franco's kernel. I never found a solution except flashing ROM again :(.

While I switch between faux123 and showp1984 kernels, I know mpdecision/thermal deamons are disabled in showp1984 (binary renamed), but it's easy to overcome by renaming the binaries back to their original name. No such thing after using franco's.
[Nexus 4 Original Android Development] dzap:
I did.

http://xdaforums.com/showpost.php?p=42091725&postcount=34043

I don't disrespect you franko, I have the utmost respect for you, and why I purchased your app to help support you some way. But this is the second time this has happened. I attributed it to user error last time, but now it's something with your kernel that's causing a conflict. Usuaally I can brush this off as an easy fix, but it hasn't been.

But I'll run through a series of events.

Info: Stock ROM. Rooted.

Changes to stock: None except radio, downgraded to .33.

1.) Received notification of r146 this morning. Successfully flash r145 and r143 without fault prior to this.

2.) As usual, I get MD5 mismatch errors about 5-6 times attempting to use the auto-flash option. This happens regardless if I am on Wifi or T-Mobile's network, so I have ruled out the network causing this issue. I usually attribute this to people hitting your servers hard and the speeds are sometimes slow.

3.) Downloaded zip instead. Saw the notification (usual) that your app was given SU permissions to proceed to reboot. (side note: Is this a lag of some sort where it takes the zip and auto-flashes anyway, if the auto-flash option was selected, but failed to download in that manner?) Phone reboots while apps are auto-updating from Googly Play

4.) TWRP confirms successful flash

5.) Bootloop.

Things I have tried to recover booting at this point.

1.) Flashed older franko kernel. r143. No change.

2.) Flash stock kernel. No change.

3.) Flashed emergency reset zip. No change.

I can get into recovery and use adb from there, but note that the Nexus 4 does show up as adb in my device manager on Windows, but does not appear in adb devices. It does in recovery, so something is stopping it from fully booting I suppose.

If you need app lists, or files that I can pull from adb etc. Let me know. I can pull what is needed through recovery. I just want it to boot again and not lose data again. This time it's not so bad, as I believe I'll only lose two days worth based on titanium backups, but I would prefer not to lose any data if possible.
[Nexus 4 Original Android Development] simms22:
reflash your rom to get back up, download the kernel(not using the franco kernel app), then flash the kernel in recovery.
[Nexus 4 Original Android Development] dzap:
Okay..well I'll be damned. It just booted after I reattempted to flash r146. Weird. I did get a "Unfortunately, Gmail has stopped" on boot and again. Interesting.

EDIT: Okay. Even weirder. After unlocking my device, I am now put into the Android first-time setup screen. Yet going into settings, my accounts and wifi are there connected. Really odd.
[Nexus 4 Original Android Development] simms22:
clear the data for the gmail app. in the phones main settings, apps, all, gmail..
[Nexus 4 Original Android Development] drawde40599:
Someone else had this issue other day and it was because he had trickster and franco app installed (just putting out there)
[Nexus 4 Original Android Development] dzap:
Yeah I'll look into that. Trying to figure out why it put me into the first-time setup screen though right now. I did NOT wipe data. Went ahead and rebooted it one more for good measure.

EDIT: I am very, very confused as to what happened here. Went past first time setup and my accounts everything is fine Text messages etc. All there.. My Nova Launcher has reset however. Not a big deal. I had a titanium backup for that. Everything else is still fine. Still getting the Gmail is crashing..
[Nexus 4 Original Android Development] 3c:
dissing ? what's that?

If I read dzap post correctly, he is trying some tips/help posted here by other users and still investigating. However IMO, sorting any problems caused by "dirty" flashing a kernel is a waste of time as much as providing detailed configuration would be. I usually try a few tricks (probably like dzap is currently trying) and then flash everything clean if things go too bad.

That said, I'm using CM10.1 RC3 and I've only had to flash clean when switching away from your kernel.
[Nexus 4 Original Android Development] ansontyl96:
I have update to the latest nightly but this still happens.....any one got solution?
[Nexus 4 Original Android Development] 3c:
I've seen that before, and after investigating I found out that if the /data/data/<folders> ownership is set wrong, JB (maybe ICS too?) will erase the related folders data! so if you do something like this: chown 0.0 /data/data/*, every app data will be wiped out on boot! And you will get the first-time setup screen ;) but all apps will still be installed. However apps using native libraries will all fail (as the libraries has been erased too).
[Nexus 4 Original Android Development] simms22:
that could happen if you flash gapps without flashing a rom, or that could happen if you had fsync off.
[Nexus 4 Original Android Development] 3c:
Try uninstalling GMail and installing from APK (to internal memory), this will at least create the basic data GMail is expecting (maybe it has some specific native libraries, only installed during APK installation, didn't actually verify that).
[Nexus 4 Original Android Development] dzap:
But again..I don't have a custom ROM. I have no need to flash gapps.

However, it looks like all my defaults were reset too (opening links etc.)

And..it looks like all my Google apps were...reset? I am on stock 4.2.2 Google Play here now. v3.10.10

Also..franko's kernel app is gone. It is not in my app drawer. All my other apps seem to be present however. Does the emergency flashable zip remove the franko apk? This is so weird...
[Nexus 4 Original Android Development] LaboDJ:
[MENTION=3292224]franciscofranco[/MENTION]

He's right! In addition your mako_hotplug doesn't compile with gcc-4.7.

Linaro exists only for gcc-4.7 and 4.8.

I know you don't like things like Linaro (you don't even use Google 4.7 toolchan to respect Google standards), but why to troll?
[Nexus 4 Original Android Development] franciscofranco:
See, that bootloop is not related to the Kernel. Someone you got your data corrupted. Maybe fsync off?
[Nexus 4 Original Android Development] zellleonhart:
r146 is stellar. I never had such smooth experience for a kernel before. I feel even smoother than r142 which I felt could not be any smoother. Well done [MENTION=3292224]franciscofranco[/MENTION] :)

Scrolling in Robird and XDA premium is epic smooth.

Beamed from my Paranoid r146 Nexus⁴
[Nexus 4 Original Android Development] franciscofranco:
mako_hotplug.c compiles just fine with 4.7 adding __cpu_init in one or two function headers.

I was not trolling, I was just trying to see how many people would say r146 its maagically smoother just because I wrote that it was compiled with Linaro, which in fact is a lie, the Kernel is still compiled with Google's 4.6 toolchain.
[Nexus 4 Original Android Development] simms22:
sounds like you had fsync off
[Nexus 4 Original Android Development] DesertVelo:
I have had the same issue that you just experienced - first time setup, account information not preset but applications and some user specific setting are still in place. What seem to resolve my issue (and I know when to expect it) is when I flash a new ROM (CM10.1 nightlies), I always flash gapps as well. When I do not flash gapps, I have encounter the first time setup and enter my account information again. Yes, it is frustrating, but by flashing gapps, I have yet to encounter the issue.
[Nexus 4 Original Android Development] Mo'HAWK:
You sneaky troll...
[Nexus 4 Original Android Development] rxmxsh:
Check the OP for links. However, by reverting you're not actually helping the development of this kernel. What's wrong? Be specific and provide logs. THAT will be useful for kernel improvement.
[Nexus 4 Original Android Development] Allosaur:
dzap,

If all else fails there's always wugfresh's nexus root toolbox. You can get back to stock even if in a boot loop.

It's got me out of trouble in the past.
[Nexus 4 Original Android Development] dzap:
Yeah it seems some of my apps have data have reset and others haven't. Is f-sync something I should turn on? I usually kept the settings from your app stock, except changing the color profiles, to the values you set, since I presume you know best when it comes to your own kernel. I don't like to touch any other settings, for the fear of what I'm going through right now. That and USB fast charge. Everything else, I don't touch.

If it was off in your app on default, that's what may have caused it?

---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------

Yeah also at this point, maybe a hardware defect. Is there an equivalent to chkdsk for android? I'm scratching my head as to why some of my stuff reset, while the others stayed intact..
[Nexus 4 Original Android Development] LaboDJ:
I caught you!!!

LoL! ;)

Btw the placebo effect exists now and will always exist... The only way to find the truth is a double blind test...

My opinion is that Linaro with latest gcc can't do magic, in kernel stuff it could improve 1-5% performance in best case (in app it could improve performance a lot), any improvement is welcome.

Don't you think so?
[Nexus 4 Original Android Development] simms22:
if you didnt turn it off, and its on by default, than its very odd. if its off by default, then it would make sense.
[Nexus 4 Original Android Development] Testraindrop:
Fsync is on in Francos app by default, unless you are using a pretty old App version where I think it was off by default.

But I had data loss issues also when testing with Fsync off and sudden reboots by UV (my fault), now its always on on my device. :)
[Nexus 4 Original Android Development] meanwhile:
Which is why I still think #143 linaro version still smoother then any of #14*

Sent from microwave
[Nexus 4 Original Android Development] Haomuch:
Is the GSM radio/modem solution a hardware or software setting or both? Possible to be optimized?
[Nexus 4 Original Android Development] G4neStarT:
Dont get me wrong Nothing is wrong with this version i just fell that the #143 were smoother for me. Maybe because i had some custom setting on gov. But i do support the dev( we all love franco because this guy is amazing and we all know that) i did try the kernel and i did said what i felt about it. I will try the new for couple day to see then.
[Nexus 4 Original Android Development] italia0101:
Btw I have always had fsync on and I always clear defaults on a kernel update, ....

However, once I checked after a flash it was off, and I promise I didn't turn it off...

Maybe that happened in your case dzap
[Nexus 4 Original Android Development] dzap:
I'm going to restore the app right now with TB. Looks like TB did it's job last night and backed up all my apps at 2AM as usual.

Besides franko kernel, the following apps also were uninstalled.

Bluetooth connect and Play 1.61

franco.Kernel.updater 9.5.3

NFC Task Launcher 6.1.2

Reddit News 6.75

Other apps that are there (Grooveshark,Amazon Appstore etc.) have had it's data reset. I'll probably just run TB and restore everything.

I just find this strange personally, as I've never seen a half-assed data restoration like this. Usually it's all or nothing.

But let me restore franko.kernel right now, and I'll let you know if I had f-sync off. Maybe I inadvertently unchecked it. It's completely possible, in which case, I am sorry for my user error. I'll let you know in a minute.

EDIT: I'm sitting on 10 minutes now of the franco app trying to restore. Not happening. Hmm.
[Nexus 4 Original Android Development] franciscofranco:
GSM radio is inside the N4. That alone will always consume more battery than any device on Earth that doesn't have a radio. As I wrote before many times the N4 modem is a ****ty solution. The S4-Pro chip wasn't mean for phones so they just attached a USB modem to the board which goes through the HSIC bus. Unfortunately everything was a bit rushed so the initial software implementation that takes care of the communication between the physical part, the modem, and the software, Android OS, was very bugged. It still is, but its better than stock 4.2. I'm pretty sure that on the next Android iteration all of that will be much better in a combination of: better USB-HSIC stack code from Qualcomm and a better radio (the new .54 is much better than .48 for instance). There is no magic solution here, its what it is and we gotta live with it.
[Nexus 4 Original Android Development] LibiSC:
Felt just like always... You made a change in the hotplug and bam "smoother" "my device is flying".. "my SOT is... " :rolleyes:... But anyway linaro toolchain makes smaller image so smaller is faster as general rule for kernels if I don't remember wrong
[Nexus 4 Original Android Development] kyokeun1234:
R146 working perfectly :) the signal loss problem is gone completely which is good. Thanks Franco :D
[Nexus 4 Original Android Development] BrandoHD:
[MENTION=770731]dzap[/MENTION] I think you should move away from TB, flash all the stock images to your device, factory reset (with stock recovery) and then set up your device in your personal way again, I say this because you don't know where your data corruption is coming from and it's best to go back to stock from Google and build up again

Flashing the kernel may be just bringing data issues to the surface

Also, since you are on stock, maybe it's best to always have a reset kernel that includes thermald and mpdecision binaries on your sd card

When I want to change kernels, it's pretty easy since I am on a custom ROM, but if people are still having issues in this day and age to switch kernels away from franco, it's because they want to have issues, it is pretty easy and all the solutions have already been provided, I don't see how people can describe it as being a "pain" to switch
[Nexus 4 Original Android Development] 3c:
LOL, nice one ;)

Smoothness is so subjective, one word about it and many will experience it. Reminds me of the entropy buzz.
[Nexus 4 Original Android Development] dzap:
I would like to know where it is coming from though first. I can't restore the franco app at all for some reason. Won't work in TB (others apps restore fine), but here's the thing..I can't redownload it from Google Play either.

I get..

unknown error code during application install -24

..after attempting to reinstall it. Other apps from Google Play install fine. So I'm starting to lean to the fact that the app is causing the problem. Maybe not the kernel specifically since r146 runs fines for now.
[Nexus 4 Original Android Development] Mo'HAWK:
Typically when these kind of problems occurred to me. I will normally reset to factory data to the fact that there's so many things that can go wrong when you are deleting and adding different types of data to a phone.
[Nexus 4 Original Android Development] drawde40599:
Still feel 146 with stock settings is missing the "bang" of previous builds whether google or linaro, setting back to deadline gives back the feeling ive come to love (the " bang)

Thanks Franco
[Nexus 4 Original Android Development] Testraindrop:
Install Playstore 4.1.10 if you haven't already.
[Nexus 4 Original Android Development] drawde40599:
Erase it from data/data maybe? Reboot try agn
[Nexus 4 Original Android Development] BrandoHD:
It's not the app, it's data corruption, remember, there are others that are using stock ROM with the app and the kernel, with no such issues, so it won't be something externally (apps or kernel)
[Nexus 4 Original Android Development] dzap:
Sorry, just saw the second part of this post.

How would I go about having a reset kernel with thermald and mpdecision binaries? You don't have to explain if you don't want to..just point me in the right direction (link of some sort) and I can learn.

Also what do you mean by people wanting to have issues? Are you implying that franco's has more changes that would cause issues compared to other kernels, or are you just saying that the issues don't arise on custom ROMs?

EDIT: So definitely data corruption. I made a TWRP backup before all this just in case. Looking at the restore date though it dated it to 1969-12-31. First time that has ever happened, so it looks like something definitely went wrong with a reset to the infamous Unix time..
[Nexus 4 Original Android Development] franciscofranco:
Size has nothing to do with fast or slower.
[Nexus 4 Original Android Development] BrandoHD:
The link to the 4.2.2 reset kernel and components is here: _motley kernel thread It's about halfway down the very fist post

What I meant is that all the answers are already in the threads, it just takes some research and reading, it wasn't directed at anyone in particular, if the need arises where you want to flash another kernel and you're on stock ROM, just flash this, and then the kernel of your choice afterwards, easy as pie, on a custom ROM, all I would have done is dirty flash the custom ROM again before flashing a different kernel

Absolutely no difficulties there
[Nexus 4 Original Android Development] Testraindrop:
Hm Franco somehow I don't like your new approach in the newest nightly, my device is now using almost the whole time either 384 or the maximum speed.

While I'm sure its good for smoothness, max speed is bad for battery and temperature. (previous versions were already smooth for me anyway...)

You somehow described the new values yesterday that when the load reaches a certain level its automatically uses max speed.

Can you describe what the idea of this is in detail?
[Nexus 4 Original Android Development] thebryceee:
Had a feeling you were saying that to see if it was a placebo. Sneaky sneaky :cool:
[Nexus 4 Original Android Development] vickpick:
146 = M3

Wow. CRAZY battery life. Sitting at 60% batter 2hr 10 min SOT, most of that time was chrome and candy crush.
[Nexus 4 Original Android Development] franciscofranco:
Hmmm on my device hispeed_freq is used a lot. If the device is either single or dual core it needs at least 90% load to ramp directly to max freq. If its in the range of 50% and 75% (defaults) it goes to hispeed_freq. If none of these conditions are met it just rules out using a normal governor freq calculation like new_freq = cpu_load*policy->max / 99 (if this value is 100 it won't ever reach max freq unless the load is 100%). Its something like this, kinda hard to explain :(
[Nexus 4 Original Android Development] thebryceee:
Battery life haven't been this good

for me

since r111. I say "for me" because everyone probably doesn't experience the same.

I've got 19% left and I'm currently at 3h 38m of SOT on LTE all day with no WiFi mixed in.

Few games of candy crush, a lot of Tapatalk browsing, nothing too intensive, all Google services synced.
[Nexus 4 Original Android Development] Utini:
Hmm cant UV as much on r146 as i could on M2 :S
[Nexus 4 Original Android Development] republitarian:
Me too I had to up my voltage +25 because phone was shutting off randomly.
[Nexus 4 Original Android Development] tlf55:
Could you implement a function to have 2 core boost when touch please ? That would be very nice and a good update .. Let test it with a r666 :D