yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] fozzie:
No, they shouldn't be empty. Are you sure you've got Franco's kernel installed and not say flashed a ROM and overwritten it?

Try clearing f.Ku's data then reboot.
[Nexus 4 Original Android Development] stratosk:
Actually, watchdog is hardware (at least in our platform).

A kernel driver needs to pet (send a signal) watchdog periodically in order to tell the hardware that everything is OK and the kernel is in a good state.

If the kernel is unable to send the the signal within a specific period because something wrong is happening (a deadlock, for example, or a thread that blocks the CPU), watchdog will send an IRQ (bark).

Then, kernel will handle the hardware interrupt, will panic the kernel, and eventually will reboot the system.
[Nexus 4 Original Android Development] Remoteconcern:
That's really good knowledge, I've learnt something. Thanks!
[Nexus 4 Original Android Development] RootTheMachine:
This is the second time doing an auto-flash has gotten me stuck at the bootanimation. I guess Wednesdays are bad luck for me... What could have gone wrong twice? It's obviously /data related since a factory reset or nandroid data restore fixes it.

Happened to me two Wednesdays ago, and again today. I flashed it successfully a couple of times between though.

Reflashed 182, works fine. Hmm...

A miscellaneous request; since you recently implemented the filemanager, could you implement that for choosing kernel download location instead of having to type it in every time?
[Nexus 4 Original Android Development] jmudrick:
My casual observation that I was seeing no benefit from underclocking is consistent with findings of those who have done more rigorous testing. For example this test of the Optimus V a couple years ago found poorer battery life with underclocking.

https://www.google.com/url?sa=t&sou...h4DoDQ&usg=AFQjCNHwaQYEdVOYI5vy6tgJVZn5vhUj_g

The fact that I'm getting 6 hrs SOT with normal use and no underclock I would hope might challenge others to test your assumptions about the presumed benefits of underclocking.
[Nexus 4 Original Android Development] Sayonara123:
Breaking root on N4 and N7(new)

Hi Franco,

I ran into an odd issue using franco kernel since android 4.3. I'm loosing root on my N4 and N7 when using your kernel and I cannot regain root acces by flashing superSU.zip again!

It all started, when I applied the OTA Update to my N4 to upgrade to 4.3. I was not surprised of loosing root, but it surprised me, that applying superSU again did not bring back root access. I was thinking about something messed up with the OTA, so I did a full flash/wipe of the stock factory rom and tried again. Didn't work, so I did another wipe and this time I could managed it. :victory:

However, yesterday I flashed a kernel update (via your app) and after rebooting the issue came back and kicked out root. The latest superSU.zip was again not able to recover root.

Since your kernel is also available for the new N7 I gave it at try. The N7 was rooted but also lost root after installing the kernel! No way to get it back.

Today, I flashed the stock kernels for both devices with fastboot and voila, root is back!

Bot devices are running the latest stock rom, are unlocked and rooted and the recovery is replaced with TWRP; no other modifications. The filesystem is encrypted by using Android's default tools.

Please let me know, if you need any further information that can help to find a solution. I really would like continuing using your great kernel! :laugh:

Regards

Dennis
[Nexus 4 Original Android Development] japmeet:
Hi, can the milestone 3 be used with pa 4.2.2? I'm currently on milestone 1.
[Nexus 4 Original Android Development] franciscofranco:
You're not the first one that has root problems with the device encrypted. I don't have an answer for you right now because I don't know what to say. I'll investigate.
[Nexus 4 Original Android Development] ben_pyett:
I also have empty values in FKU ondemand control tunables, even after clearing apps data, I may have re-flashed a ROM but I also re-flashed the kernel afterwards.
[Nexus 4 Original Android Development] Sayonara123:
Ok, thank you for the quick response. The encryption really may be the point. Let's see what the reason is.
[Nexus 4 Original Android Development] ben_pyett:
Yes it can but you might want to try the last nightly #165 as that's improved (imo) over the M3.
[Nexus 4 Original Android Development] Bill Gamble:
It sounds like you didn't clear fKu data until after the boot problem. As a rule, I always clear fKu data before I flash a new kernel version; I've never had a problem rebooting afterwards.
[Nexus 4 Original Android Development] RootTheMachine:
Nope, still stuck using 182.
[Nexus 4 Original Android Development] Bobtehblob:
Anyone having problems restoring r183 from within the app after flashing the latest cm nightly?
[Nexus 4 Original Android Development] Testraindrop:
If you mean by "restoring" downloading and flashing it from the app then it might be related to the new nightly being JLS something I think, FKU only can differ between JWR and JSS for now as far as I know....

Just dl. the JSS version yourself, someone said JSS version should be fine.
[Nexus 4 Original Android Development] Bobtehblob:
Yeah, flashing the JSS version in recovery works fine. Restoring the 183 image via the Backup and Restore function in fk.u didn't work either.
[Nexus 4 Original Android Development] Bill Gamble:
So you did delete fKu data before you flashed the kernel that led to the reboot problem? I'm sorry, that wasn't clear in your original post.
[Nexus 4 Original Android Development] RootTheMachine:
I tried deleting then flashing, same result. Flashed 183 in recovery, same result. Flashing 182 in recovery fixes it. Perhaps it's something with the latest CM nightly.
[Nexus 4 Original Android Development] Bill Gamble:
Apparently, the latest CM is labeled neither JSS nor JWR, so attempting to flash via fKu will download the wrong kernel. If you flashed the JWR version of r183 in recovery, that would explain it.
[Nexus 4 Original Android Development] mendozaram:
hey [MENTION=3292224]franciscofranco[/MENTION] can you have a look why your kernel isnt working on Slimrom Build 1 please
[Nexus 4 Original Android Development] agascon:
Hi team,

First all, thanks for your job Francisco. Are things like this what made Android a great platform better every day!

Well I have an issue. I have my N4 with stock 4.3 +super su 1.65 + FK r183 and right after flashing FK (replacing stock kernel) i lost root access.

I checked if supersu binaries were deleted or something, but not they were fine. Even if flash again the stock kenerl root is back.

Finally i identified an additional point. While trying to fix this, I detected that if I boot to the recovery (TRWP) and then boot the system, root is working fine with FK.

What could be the problem ? Is it possible that the ramdisk in FK was causing this issue?

Please let me know of any test or info you could need.

Again, thanks a lot! Great job!

Antonio
[Nexus 4 Original Android Development] japmeet:
Hi Ben, thanks for the suggestion, #165 was the last 4.2.2 nightly right?
[Nexus 4 Original Android Development] ben_pyett:
#165 was indeed Franco's final 4.2.2 kernel release!

Although rather than suggesting you flash it, I should really be suggest that you move to 4.3, and move to #183 whether that be stock or one of the many customs - move forwards....
[Nexus 4 Original Android Development] fozzie:
That's already in the file manager under 'options'.
[Nexus 4 Original Android Development] whitedragonz83:
Phone rebooted while screen was off.

Stock 4.3, SuperSU, r183 default, -100mV undervolt Fast Bin

Does not show it rebooted in the uptime, I know only because I saw the rebooting X logo.

Edit: I want to add that I am using Chrome Stable, not Beta.

Hopefully a useful /proc/last_kmsg

http://pastebin.com/cXzTyP41
[Nexus 4 Original Android Development] lutanica:
Same problem here. 183 doesn't work with the latest CM Nightlies since they are JLS36C I guess..
[Nexus 4 Original Android Development] Andre_Vitto:
JSS is supposed to work with JLS.. some other issue possibly
[Nexus 4 Original Android Development] Bill Gamble:
It does, but because CM is now labelled JLS, you just have to install the JSS version manually (fKu only knows about JWR and JSS and apparently defaults to JWR).
[Nexus 4 Original Android Development] franciscofranco:
[ 2515.658202] L1 / TLB Error detected on CPU 1!

[ 2515.658324] CESR = 0x00000001

[ 2515.658385] CPU speed = 1512000

[ 2515.658446] MIDR = 0x510f06f2

[ 2515.658476] D-cache tag parity error

[ 2515.658598] D-side CESYNR = 0x00002102

There's nothing I can do about that L1 error, its hardware related, I can't fix hardware.
[Nexus 4 Original Android Development] BlueFlame4:
You are an awesome person, stratosk! :) Thanks, I've learned something in this forum (again).

You said that it's an IRQ, so is it unmasked and can the kernel ignore it basically?

Sent from my Gameboy Color
[Nexus 4 Original Android Development] stratosk:
Thanks!

I don't recommend to do it, but the driver has the capability:

echo 1 > /sys/module/msm_watchdog/parameters/runtime_disable

If you'll do this, you can enable again watchdog only with reboot.
[Nexus 4 Original Android Development] Bobtehblob:
I know it's off-topic but what's your opinion on this Franco?

http://www.cyanogenmod.org/blog/a_new_chapter

Sent from my Nexus 4
[Nexus 4 Original Android Development] BlueFlame4:
Aight, I won't mess with the watchdog at all. Am I right when I say disabling it could lead to undefined behaviour in a bark situation?
[Nexus 4 Original Android Development] Lebo-Wog:
Having gaming lag issues with latest r183, i know its easy to fix if i use franco kernel updater, but i'm ON FULL STOCK, not even custom recovery, i use the boot-r183.img via fastboot, so i can't edit values and fix this :/

Franco please consider giving 2 version of the kernel, a gaming, performance, and benchmark hungry version.

and a smooth, battery friendly one.

Thanks.

Unless there is a way to edit kernel related values without root.
[Nexus 4 Original Android Development] franciscofranco:
Sorry, no comments on that.

I won't deliver different Kernel versions, however I'm holding out of r184 because I've been improving my GPU governor algorithm the last days to be more intelligent. More news soon.
[Nexus 4 Original Android Development] jjcandroid2012:
My phone froze and reboot on 27. Using xylon ROM here is last ksmg. Hope info helps.

http://db.tt/sh7ojgA6
[Nexus 4 Original Android Development] karanrajpal14:
Led notifications don't work for me after the latest update r27. I'm running CM10.1 please help me fix them
[Nexus 4 Original Android Development] jak3z:
Flashing r27 as I write this. Will perform the same tests I do always overnight, and let the device sleep for a while. :laugh:

BTW found a bug in the app, while being in portrait mode, and you select the Auto-Flash for the zip, the app goes into vertical mode and force closes some seconds later.
[Nexus 4 Original Android Development] djemgee:
A quick question for you guys, a few of us on the xlouder mod have come to a conclusion that francos kernel could be causing reboots because of a conflict with the mod. I'm just wondering before I unwillingly change from using the best kernel around to something lesser if anyone has experienced this problem thanks
[Nexus 4 Original Android Development] Mr. Steve:
Oh with Franco's kernel there is no lag at all, but I just wanted to know his opinion on the whole thing. I tried it on my N4 and N7. I saw no change on the N4 and very little (if any) on my N7.
[Nexus 4 Original Android Development] murdah204:
Flashed r27 and no more deep sleep.... Going back to r25, it was perfectly fine then
[Nexus 4 Original Android Development] Vangelis13:
You can control everything there is to control in the kernel (and continue getting new functions with ever app update), the way its creator meant it. Most importantly, you support the development of an amazing utility for your phone. Which you bought for +/- 350€. Well, for 1 or so procent of that (or less than a beer costs) you achieve all that.

You will not be a noob for too long, you've probably already unlocked & rooted and are about to flash a kernel. ;)

(You can also use trickster mod to control the kernel, free & easy. But then I wrote all the above for nothing.. :p)

---------- Post added at 08:55 PM ---------- Previous post was at 08:49 PM ----------

And how are you so sure that it isn't the mod that is causing the conflicts..? O_o We're a fair few of us here that are enjoying reboot-less (jebus, I created a word again..) phones, I'd say ~99% of us.

Remove the mod and see if you get reboots, then perhaps come back.
[Nexus 4 Original Android Development] Testraindrop:
Both work fine here.
[Nexus 4 Original Android Development] ceejay83:
Deep sleep works perfectly fine for me
[Nexus 4 Original Android Development] trismegistos:
No problems for me

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] drawde40599:
27

Data dropped out on 27 came back then showed full bars but couldn't get on to internet , never happened once on 26 . i rebooted , works agn i get u log if happens agn .
[Nexus 4 Original Android Development] Vangelis13:
Franco, a silly request on a cosmetic thing: on the download server, can you please change the r9 to r09 so that it moves up? :o
[Nexus 4 Original Android Development] jundii:
r26 had no data issues for me. Idle sleep on 3G was pretty good and idle on Wifi was insane. Flashed r27 at 76%. Will report any issues.

Still having whacky issues with Wifi and sleep. I don't remember having these issues with earlier nightlies of CM 10.1 and earlier nightlies of this kernel. Not sure if it is ROM related or not but I think it is a known issue. Even with Wifi Optmization off I have a delay on incoming notifications. As soon as I wake the phone, they flood in. One in particular is Gtalk. Gmail and the Email app do the same but not as bad. Sometimes they're fine, sometimes not.
[Nexus 4 Original Android Development] Mr. Steve:
Just flashed r27 ten minutes ago and deep sleep is working for me.
[Nexus 4 Original Android Development] :
Running r27 on CM10.1 nightly (4.1.2013), and Deep Sleep is working fine. :)

Just got my Nexus 4 on thursday and this is the setup I went with.
[Nexus 4 Original Android Development] karanrajpal14:
Hmm I wiped dalvik cache and everything is fine now. Sorry. Something must have gone wrong with light flow.
[Nexus 4 Original Android Development] zephiK:
same here. their posts dont really make any sense as it doesnt provide much details.
[Nexus 4 Original Android Development] evostevo1:
R27 works fine for me
[Nexus 4 Original Android Development] kyokeun1234:
+1

Or make it so that it is sorted by date if possible
[Nexus 4 Original Android Development] drawde40599:
It dose that on stock kernel also . 1 of the first things I noticed when I got this phone . someone posted the link some pages back on how its normal
[Nexus 4 Original Android Development] ben_pyett:
IMO It would be much simpler if when pressing on Settings->Custom Download Path it fired up the File Explorer as otherwise the option is hidden away, I have no need to use the file explorer once downloads default to my default location. Although now I know the option is there it will be useful.
[Nexus 4 Original Android Development] lorolouis:
Only Chuck Norris could ignore such serious things :) not sure if the "kernel" can.
[Nexus 4 Original Android Development] Lebo-Wog:
Thanks mate, i do care about battery, but i'm waiting for the champions league now, so killing time with heavy gaming like real racing 3... and i hate lag...

Only reason i went fully stock, so that when kitkat comes in a few weeks, i only flash the stock boot.img and get the official update, then flash back franco when its set to go with 4.4 so i have a huge thanks for you for providing a .img file of your kernel.

If you need a tester, specially in the GPU, i'm always ready.
[Nexus 4 Original Android Development] lorolouis:
Franco, would your next r184 play better with OTG/Settings->Storage on PA 3.99.1-RC-1 ?
[Nexus 4 Original Android Development] franciscofranco:
No, I don't and I won't add OTG.
[Nexus 4 Original Android Development] sordna:
+1

Back when I was evaluating between the different custom kernels I chose franco partly because of the .img availability and because it leaves /system alone (apart from renaming a .so file, which FKU now can undo for an OTA). It is a very stock-friendly kernel !

After playing with some ROMs I decided I'm better off with: stock android, latest google updates, Nova Launcher, and Franco Kernel.
[Nexus 4 Original Android Development] Lebo-Wog:
HAHA i have the same set up.... :good:
[Nexus 4 Original Android Development] stratosk:
Kernel will work just fine without watchdog. But if you hit a bug or something your device will remain in abnormal state for ever (until you reset it).
[Nexus 4 Original Android Development] lorolouis:
Nevermind ....

There are enough quotes of this.

Sorry for the question.
[Nexus 4 Original Android Development] superbobup:
Clearing app data and rebooting doesn't help.

Kernel was flashed a few days after I reflagged RBJ. Definitely not overwritten as I can control everything else

Manually setting the value in governor control does nothing either

Yes, reflashed supersu after flashing the kernel. Other SU apps working fine (greenify, root explorer)

I think ben_pyett is having the same issue (sorry, can't multi-quote on tapattalk app for some reason)

Any other suggestions?
[Nexus 4 Original Android Development] Andre_Vitto:
Calm down son.. The issue with franco is he does not always explains properly and his replies may seem a bit confusing to a user who does not follow the N4 dev scene.. Aptly because we want him coding kernels for us rather than answer questions which has been answered multiple times. The FC with storage issue will be resolved by PA team.. Its a nom issue.. Not of franco kernel..
[Nexus 4 Original Android Development] franciscofranco:
That was... friendly.

I already talked with moles about that, they will revert the OTG business because its hacky and hacky... and hacky?

Reason why flashing this will **** with PA's storage settings is because they added OTG into the Kernel and then added the usb0 path to the Settings without even checking if the file existed, so boom.

Research first, complain later.
[Nexus 4 Original Android Development] The Gingerbread Man:
Same on my gnex and n7 but with apex launcher :good:
[Nexus 4 Original Android Development] lorolouis:
Deleted ...
[Nexus 4 Original Android Development] Waldos:
Hi [MENTION=3292224]franciscofranco[/MENTION] and xda members :)

Hi have a doubt about ROW vs noop. I know ppl using ROW and ppl using noop, almost 50/50.

ROW is the default, why? most responsive? the updated settings of ROW? any other reason? :confused:

Thnx for this great kernel!
[Nexus 4 Original Android Development] lolbazor:
JSS version for the new JLS right?

Sent from my N4
[Nexus 4 Original Android Development] sNoxious:
Yep, should work fine.

Sent from my Nexus 4
[Nexus 4 Original Android Development] RootTheMachine:
Correct... JWR is the oldest.
[Nexus 4 Original Android Development] adrok76:
What a bell! It's his thread dude, show some respect...
[Nexus 4 Original Android Development] Pure Drive GT:
Wow this humongous amount of retardation is astonishing...
[Nexus 4 Original Android Development] lorolouis:
Come on guys ... I am still loving Franco kernel.

Latest PA didn't work fully with it, that's it.

Can Franco do something like the "linaro .... etc. based modifications of DJ..." in next release so I can use the original Kernel again.

The response seems to be "wait for next PA".

Instead it turned into (dis)respect questions and other things.

Regards.
[Nexus 4 Original Android Development] JNewms:
He has also answered the linaro question already. He has said he won't.
[Nexus 4 Original Android Development] SevansD:
#mantra
[Nexus 4 Original Android Development] franciscofranco:
I don't think Kernels compiled with Linaro toolchain are marginally better. I've ran a couple of tests with different toolchains in the past and its more placebo than anything. I also like to keep it the way Google compiles their stuff so I use their compiled toolchain from the NDK.
[Nexus 4 Original Android Development] namurt:
franco's kernel needs to work across a multitude of roms. that's his bread and butter. as a result, he will not (and should not) cater to a specific rom. if his kernel works on stock and it doesn't work on your rom of choice, that is ultimately the responsibility of your rom's dev(s).

in this particular case, the devs behind PA are aware of the issue, and they will fix it in an (as yet unannounced) upcoming release.

the reason you are being flamed is because of your attitude. you are coming off as a bit of a brat because you seem to be making demands of franco without first taking the time to fully understand the situation. it's human nature to frown upon such behavior, but especially here at xda... if you act like that, you're gonna get burnt to the ground with all sorts of flaming comments.

this has been an XDA PSA. thank you for your time and consideration!
[Nexus 4 Original Android Development] nuwan32:
[MENTION=3292224]franciscofranco[/MENTION] just wanted to know if we need to have musicfx.apk or any other audio effects app for the volume gain/volume boost to work?
[Nexus 4 Original Android Development] Poke_N_PDA:
I am experiencing the msm_hsic_wakelock issue with the 0.33 radio loaded. Battery is a big issue. I have to leave my phone in the car during work and it will be dead when I get out to it. Virtually no use in the mornings. So I'm basically getting 8 hours with no use. I was told this kernel would resolve it, but I have yet to experience any change. Thoughts?
[Nexus 4 Original Android Development] jmudrick:
Experiment with other radios including the hybrid. What % is this wakelock? If you're only getting 8 hours with phone at idle you have a problem way beyond the standard msm_hsic_wakelock.
[Nexus 4 Original Android Development] Poke_N_PDA:
Wake lock is 50%. I'm about ready to ditch LTE and just rely on HSPA+ till the new nexus hits.
[Nexus 4 Original Android Development] jimbohurt:
Just got a FKU update :good:
[Nexus 4 Original Android Development] lorolouis:
Very nice and complete explanation

However ... I'did not ask anything to be done for me especially.

I know it was incompatibility issue, mainly caused by PA developers.

I know this is Franco's thread.

I respect HIM and all of you, believe me.

I just asked, would next FK kernel work with no FC's on current PA rom, like the patched one does.

Also until all is fixed, the fact is that PA combination with official FK su**cks which basically is NOT good, right guys?

Wow man, all of you who click +1 on ANY Franco post regardless of the contents, what it is all about?

What did you find guys soo wrong on my "attitude"?

If Franco himself didn't comment this way, nobody will even notice my post ... at all, be honest at least.

Now WOW, how bad I was ... because I asked something, and I explained an obvious thing.

Alright, let's forget all this and look forward.

---------- Post added at 10:14 PM ---------- Previous post was at 10:09 PM ----------

Alight Franco, I've got everything you said.

One word of you will let some people to kill me, man.

Excuse me for everything bad I ever said!
[Nexus 4 Original Android Development] jmudrick:
Yeah that's crazy bad. I used the 27/84 hybrid radio for 4.3 on T-Mobile LTE last month when in California and didn't have major issues.
[Nexus 4 Original Android Development] CatsAreGods:
If you have to leave your phone in your car all day...why not just turn it off?

Problem Solved!
[Nexus 4 Original Android Development] drawde40599:
Deadline

Any1 that has been using this kenel (jwr 183 ) with its defult settings can u tell me if deadline gives a pretty noticed performance gain or if its just me... :P
[Nexus 4 Original Android Development] jmudrick:
I figured we'd just be polite and let that go....