yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] franciscofranco:
Thats the userspace Java interface in the Android OS code that takes care of holding and releasing WakeLocks.

I have no issues with stuff sticking on reboot and I simply cannot reproduce.

My GPU is scaling up and down normally and is not stuck in any specific frequency. However for some odd reason the scaling is not starting right after the boot and I still don't know why but its probably some thing I did wrong. Just forget about it and after a few minutes it starts scaling normally. I'll investigate of course.

I have no clue what changes slim rom did on their ramdisk. If I can get a diff of what they did I can most likely take a look and implement it if it doesn't break something else. Why roms mess with the ramdisk is beyond my understanding and infuriates me.
[Nexus 4 Original Android Development] franciscofranco:
You didn't, I was asleep from 7am to 1pm and I did not wake up to release it because I'm not yet fully happy with FK for Flo, only just before I went to bed I found a small issue with thermald, sensor init and my thermal throttle solution - to make it all work fine I hacked around but I need to read some driver code to init the proper sensor instead of relying on thermald (which I disable) to do so.

The problem lies in roms, specially CM, that change the ramdisks in ways that I truly cannot comprehend instead of sticking to other solutions. Since I prefer to release Kernels in a boot.img format for several reasons I always need to find a way to make room for CM changes while keeping it compatible with stock and with all other roms. If roms change their ramdisks well... its not my damn problem - but I can always try to implement their changes to the ramdisk that I use. Why don't rom developers come to me and show me their ramdisk diffs? Slim rom developer would be very welcomed to come here and post it, and others as well in the future.
[Nexus 4 Original Android Development] jak3z:
That's the right attitude! :good:
[Nexus 4 Original Android Development] Waldos:
[MENTION=3292224]franciscofranco[/MENTION] I really want to know if you choose Weestwood for some reason :)

Thanks indeed bro!
[Nexus 4 Original Android Development] franciscofranco:
Hello.

I use Westwood because about an year ago I ran speed tests with all the algorithms and Westwood was the one that showed best and more consistent results. Even though speed tests don't cover all the user cases my knowledge in that area is a bit gray, but as it gave me the best results I kept using it as the default.
[Nexus 4 Original Android Development] sordna:
By default the app still boots automatically after a flash, you have to go into the settings to change this behavior. I changed the settings before I hit the autoflash button, and got a "Device is rebooting" notification or something, but the phone didn't actually reboot. So the new setting works, but having that notification is a bug since there is no reboot :)

Also, the issue where there is no feedback after you hit autoflash is still there. You'd hit autoflash, and nothing happens, and sometimes 1 minute later you see a notification that the kernel started downloading.

The servers are apparently very slow, but there should be some feedback to the user that the app is waiting for the download.
[Nexus 4 Original Android Development] franciscofranco:
Oh shoot, that "Device is rebooting" should NOT be there, how could I miss that?! Bollocks :)

I absolutely agree, it needs some visual feedback because sometimes the servers are so hammered that it takes a bit longer to start the download. I will add that today in a small bug fix release!
[Nexus 4 Original Android Development] CoolApps:
Franco, you may want to refer to Andre Saddler's post since it is regarding the storage on ParanoidAndroid 3.99 R1: https://plus.google.com/107979589566958860409/posts/7L6ft4w8JrH
[Nexus 4 Original Android Development] Kurre:
Here's diff, beta4 vs beta5 (b5 introduced JWR based kernel):

diff -ENwbur beta4/ramdisk/init.rc beta5/ramdisk/init.rc
--- beta4/ramdisk/init.rc	2013-09-14 18:32:39.719348787 +0300
+++ beta5/ramdisk/init.rc	2013-09-14 18:31:14.295348848 +0300
@@ -21,9 +21,6 @@

# create mountpoints
mkdir /mnt 0775 root system
- mkdir /storage 0050 root sdcard_r
- # Create mountpoint so Dalvik can mark as slave in zygotes.
- mount tmpfs tmpfs /storage mode=0050,uid=0,gid=1028

# Allow system UID to setenforce and set booleans.
chown system system /selinux/enforce
@@ -73,7 +70,6 @@

# See storage config details at http://source.android.com/tech/storage/
mkdir /mnt/shell 0700 shell shell
- # Ensure permissions are set appropriately after device early-init.
mkdir /storage 0050 root sdcard_r

# Directory for putting things only root should see.
Binary files beta4/ramdisk/sepolicy and beta5/ramdisk/sepolicy differ

end of transmission.. :)

PS. afaik PA is also implementing same kind of approach..basicly JSS based rom but some hardware commits which caused deadlocks are reverted. Thus JWR kernel.
[Nexus 4 Original Android Development] Waldos:
Thank you very much for your anwser.

Is awesome a DEV like you that really knows what is doing :)

I'm sure rigth now that i make the rigth choice buying this device.
[Nexus 4 Original Android Development] jmartino5920:
That's why I've been using AOKP. those devs don't change the ramdisk. And because of it i get great battery life with this kernel.

LTE Mako
[Nexus 4 Original Android Development] Kurre:
if you're referring to slimbean compatibility..
[Nexus 4 Original Android Development] jamesst20:
Sadly it is not working with latest version of JellyBAM 10.2. and Yes I did flash the JWR version :S

Edit :

It is very long to boot and once it boots, I get

com.android.phone has stopped working

Same for NFC Service

Edit 2 :

Tried wiping whole device plus reflashing ROM + kernel and samething happen :(
[Nexus 4 Original Android Development] dmourao:
Got 3 reboots (full ones) today while using Facebook. On jwr with default settings.

Anyone else having the same issues?

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] jak3z:
Not a kernel issue, it's a ROM issue. Try deleting the APN list that the rom includes, you can get to near that menu part in airplane mode, once there turn it off, and get to the APN list, and toggle airplane mode ON, once you delete all the apn from the list, turn airplane off and see what happens.
[Nexus 4 Original Android Development] sordna:
Ok, not even did you forget to provide any logs, but you didn't even state your kernel version ! Please say your kernel version folks, ALWAYS ! There's people here on 176, 178, 182, 183. Most are on 176 and 182 at this time is my wild guess.
[Nexus 4 Original Android Development] dmourao:
Oops, I forgot to mention the version, sorry! Latest one, r183. I manually rebooted after it so I think I lost the logs. I will provide them if it happens again.

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
Whos that Andre Saddler? I'm not merging any OTG patch thats for sure. I'm gonna have a talk with moles.

Ok thanks. I'll see what I can do.
[Nexus 4 Original Android Development] CoolApps:
He is one of the developers from the ParanoidAndroid team, all that code obviously is to do with USB Host.

Yeah maybe Moles knows what to do.
[Nexus 4 Original Android Development] Redneck Trash:
Reading the last 8 pages or so makes me thrilled I'm not on some janky ass JSS ROM.
[Nexus 4 Original Android Development] LaboDJ:
Andre solution doesn't work, I compiled my Linaro franco.kernel build with that commit, it doesn't solve the issue.

My phone gives me "Unfortunately, the process android.process.media has stopped.", I can't access internal memory from PC and if I go to settings/storage it FC﻿
[Nexus 4 Original Android Development] franciscofranco:
He doesn't know what he's talking about, it has nothing to do with OTG for sure. Its something on the ramdisk. Growing tired of this JSS thingy and changes on the ramdisks just for the sake of changing.
[Nexus 4 Original Android Development] turkobr:
Updated through FKU and my phone was stuck on boot showing the google logo, had to sideload the kerne. I got a feeling the app tried to flash the kernel before completing the download. Anyway, now I learned not to update on my crappy 3g.

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] Shardzmi:
Also, franco, we were using JSS for b4 and now we are trying to use JWR for b5. I heard that the ramdisks between f.Kernel JSS and JWR are different, so that might be the case too :)
[Nexus 4 Original Android Development] franciscofranco:
Its because of this: https://github.com/ParanoidAndroid/...mmit/ce19ad8fd5b97b8de59cbd9ff6ca4ddb712423b1
[Nexus 4 Original Android Development] LaboDJ:
Love u :good:
[Nexus 4 Original Android Development] MA-90@:
What settings do you recommend?
[Nexus 4 Original Android Development] jamesst20:
Thanks but it sadly didn't work. Airplaine Mode does fix the android.phone has stopped but doesn't fix thousands other popups :(

I really want to have Franco on JellyBam :( Please! :)
[Nexus 4 Original Android Development] CoolApps:
Franco, it seems that PA 3.99 R1 uses the USB OTG Patch.
[Nexus 4 Original Android Development] jak3z:
Nothing we can do about that, it's up to the ROM author and franco to work a way to make it work, don't hope for much since JellyBam author is banned from XDA afaik.
[Nexus 4 Original Android Development] mkfort:
Wanted to give an update on my deep sleep woes. r176 started doing it after about a day. I flashed stock boot.img, which seemed to work fine for a while but did the same thing by the end of the second day. So it's not just a problem with FK.

Checking kernel wake locks, it's listed under PowerManagerServices, so it should be under partial wake locks but is not. I've tried clearing data on Google services and play services, doesn't help. I've tried stopping all running services I could, doesn't make a difference.

So this has just been very hard to debug. Currently enjoying r183. I'll keep testing as best I can and hope for the best.
[Nexus 4 Original Android Development] fkrone:
To me it seems like devs does not talk. They're just working on their ROM/Kernel or whatever and less care about compatibility. And after you get into trouble with a certain combinations the users have to complain over and over again till someone fixes that or the devs start talking. I've learned at univerity that a good reason for projects failing is a lack of communication. So why not talking? I mean even in business you have to talk to your collegues especially if you work on a project with several dependencies.

About OTG: I hardly use it on my Nexus 10 (needed it about 2 times) and it is to my mind not quiet handy to use OTG with external power. But do not blame any dev for that, let's blame Google and LG for not powering our USB port ;)
[Nexus 4 Original Android Development] LaboDJ:
I confirm these 2 ramdisk changes are enough to solve problems...

Franco could you please push a ramdisk git? I have to extract it from your .img all the time to see if there is any change.
[Nexus 4 Original Android Development] CoolApps:
The ODM (Original Design Manufacturer) which would be LG decided to add Slimport BUT the problem that it uses up the data ports which passes power so that is most likely why you can't internally power via female micro USB.
[Nexus 4 Original Android Development] sordna:
+1

Franco kernel and Nova Launcher on stock rom beats custom ROMs (for me at least) and let's you easily enjoy google's OTA updates.
[Nexus 4 Original Android Development] franciscofranco:
I want to, but I have yet managed to make an universal ramdisk for JWR, JSS etc etc. I think I might've nailed it because I flash back to stock images and compiled JWR Kernel sources with a JSS ramdisk and it booted while I was typing this. If this is the case I'll push it in a few minutes.
[Nexus 4 Original Android Development] Jazavchar:
Finally someone has an answer! Thank you so much for this Franco, I've searched everywhere and noone seems to know what it represents. Do you, by any change have an idea how to get rid of that wakelock? I've noticed it primarily appears on some Wi-Fi networks, although I was not able to pinpoint the exact cause, since I do not have access to most routers' settings.
[Nexus 4 Original Android Development] jmartino5920:
Not sure what you are getting at here. I could care less about any ROM but the one I'm running. Just pointing out that AOKP doesn't mess with the ramdisk. So while AOKP is on JSS and hasn't yet fixed deadlocks (read: it's in preview stages right now), I know I can just flash and go with Franco.

That's why I stick with a stock ROM or AOKP. :)

LTE Mako
[Nexus 4 Original Android Development] Mantulis:
Number Uno :cool:
[Nexus 4 Original Android Development] franciscofranco:
Its not a Wakelock, as I said its the name of the Java class that takes care of the Wakelocks. You can't get rid of that class. You have to find out what app is acquiring and holding the wakelock, and for that I cannot help. Good luck.
[Nexus 4 Original Android Development] Ridho1:
Sorry wrong thread
[Nexus 4 Original Android Development] jamesst20:
You got an idea why the kernel isn't working with JellyBAM ROM ?
[Nexus 4 Original Android Development] mkfort:
You might be seeing the same thing I've been trying to track down. Unfortunately I don't have a better solution at this point than reboot.
[Nexus 4 Original Android Development] Kurre:
Sorry, I didn't mean to be rude or anything :)

There has just been some much "talk" about SlimBean's compatibility with Franco's kernel and someone's said that it was caused by changes in SB's ramdisk. Which actually isn't true because it's almost stock aosp ramdisk and there haven't been changes.

But anyway maybe this is enough about this topic..Franco knows the situation and so on :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
https://github.com/franciscofranco/ramdisk_mako
[Nexus 4 Original Android Development] BrandoHD:
My curiosity is getting the better of me here

I'm hoping that maybe Franco can explain, but his kernel boots on all other ROMs except yours, but yet it's not because of a change you guys made???

Sent from my Nexus 4
[Nexus 4 Original Android Development] jak3z:
I know the don't ask for ETAs thing, but how's the N7 kernel going? :)
[Nexus 4 Original Android Development] franciscofranco:
Good as far as I can tell, I brought it with me to my GFs house to test, then if nothing ****s up I will release it later at night.
[Nexus 4 Original Android Development] jak3z:
Good! Talk to you tonight? ;)
[Nexus 4 Original Android Development] franciscofranco:
Dunno I'll be pretty busy today.
[Nexus 4 Original Android Development] jak3z:
:highfive:

See you tomorrow :P
[Nexus 4 Original Android Development] Kurre:
It's not mine rom, I'm just a beta tester ;)

Well, what if I say that every other kernel boots with it (afaik, by reports of the users) but this one? I haven't personally tested others than stock..

But let's stop this here..I want to respect Franco's thread and I respect he so much as a developer that I'm not even trying understand everything what's happening under hood :cool: Best option would be that Google would fix their stuff :D but that most likely isn't happening..

Peace guys, let's just enjoy our devices and the stuff great devs are giving for us :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] edwardeutsch:
r183 runs solid and better than r182! Great! Stock JWR.

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] Shardzmi:
What do we lose if we replace the ramdisk? I'm just asking because I haven't read about them. Will read when I have some time but I'm curious now :D
[Nexus 4 Original Android Development] jak3z:
ramdisk is a small partition image that is mounted read-only by the kernel at boot time. It only contains /init and a few config files. It is used to start init which will mount the rest of the system images properly and run the init procedure.
[Nexus 4 Original Android Development] spider623:
Forget your kernel, give some attention to your gf
[Nexus 4 Original Android Development] Shardzmi:
And if we replace it with some other ramdisk, will anything related to the kernel not work or work bad?
[Nexus 4 Original Android Development] jmartino5920:
Blasphemy... lol!

LTE Mako
[Nexus 4 Original Android Development] jak3z:
It's up to the differences, can work, can fail or can't even boot.
[Nexus 4 Original Android Development] LaboDJ:
Franco thank you for ramdisk git... But your new ramdisk doesn't make my device boot... Mmm
[Nexus 4 Original Android Development] drawde40599:
I don't no anything about ram disk or bunk roms but 183 is badass on cyanogen jss and stock img of jwr. Noticeably faster, smoother, battery is bout the same as 176 so far (176 gave me better battery than 82) , no issues here.

Thanks for your time Franco!
[Nexus 4 Original Android Development] Shardzmi:
Figured :) well, as long as it works, I guess I'll just recompile it with that ramdisk until Franco comes up with a better solution :)
[Nexus 4 Original Android Development] dsbrohan:
Any reason why under FKU my current GPU clock always says 320mhz? I've wiped data for it, uninstalled and reinstalled and did a fresh flash of r183.
[Nexus 4 Original Android Development] drawde40599:
Mine says 128, and just stays there.... Not sure if its working correctly phone feels as fast and reliable as ever so maybe app issue. ? Is there a app to watch gpu frequency?
[Nexus 4 Original Android Development] zephiK:
because you aren't doing anything worthy for the GPU clock to be at 400 for battery purposes?
[Nexus 4 Original Android Development] dsbrohan:
That makes no sense. It should be at 128 unless I am doing something GPU intensive.
[Nexus 4 Original Android Development] drawde40599:
It used to move constantly within his app didn't it? , he did just change some gpu stuff most likely the reason its "stuck" there, is your phone getting hot? Did u change any settings from stock Franco setup. ?
[Nexus 4 Original Android Development] dsbrohan:
Nope, I just flashed it and reinstalled the kernel. No settings changed, and I normally undervolt by a 100. The phones not hit at all, FKU says its idling at 37c. I'll fully wipe and check back in in a few.
[Nexus 4 Original Android Development] drawde40599:
Ya dunno , i no mine hasn't moved from 128, i could have swore it used to fluctuate when looking at it within the app. But cant remember now
[Nexus 4 Original Android Development] yukkio:
Gpu is at 400 because it has performance governor. You can use trickster mod to change to on-demand.
[Nexus 4 Original Android Development] fozzie:
I don't think anybody said it was stuck at 400, did they?

Governors can be changed fine in f.Ku; no need for a 3rd party (and it's better to support the kernel developer).
[Nexus 4 Original Android Development] dsbrohan:
Yeah I never said it was at 400. I just said that initially it was at 320 after boot and it never seems to drop to 128 even after idling.
[Nexus 4 Original Android Development] samuelrf:
using simple governor for the GPU it stays on 400 always
[Nexus 4 Original Android Development] drawde40599:
Huh? Since when can u change the governor? Did i miss something?
[Nexus 4 Original Android Development] Nocturnal86:
Im stock rooted on r183 and mine is at 128 when nothing is going on.
[Nexus 4 Original Android Development] dsbrohan:
A full wipe seems to have helped. Flashed r183 through adb and installed FKU and its idling at 128 and fluctuating like it should between apps. I'm not sure what the problem was.
[Nexus 4 Original Android Development] jtwebfusion:
No go on stock ROM...
[Nexus 4 Original Android Development] hello_world.c:
Fast USB charging now working!

I am happy to report that with r183, fast charging works as advertised. I am charging off a USB 3.0 port with working data connection at over .8 Amps right now. Thanks Franco!
[Nexus 4 Original Android Development] drawde40599:
Your using Franco's kernel or that linaro build? Francos shows 128, linaro "Franco" shows 320

I seen your post u fixed it thought id ask anyways
[Nexus 4 Original Android Development] BrandoHD:
To all the guys going on about the GPU stuck at 320, as Franco stated a couple pages back in this thread, he coded his own solution for the GPU and it stays stuck at 320 for a few minutes upon first boot, but it goes back to normal operation after some time,, he also said that he would look into it

Sent from my Nexus 7
[Nexus 4 Original Android Development] drawde40599:
Were do u see that.? Maybe im blind but i don't see that post by him
[Nexus 4 Original Android Development] BrandoHD:
This is the link to the post here

http://xdaforums.com/showpost.php?p=45588169&postcount=46924

Sent from my Nexus 7
[Nexus 4 Original Android Development] Testraindrop:
Ehm the TCP algorithm has nothing to do with the GPU...

GPU is the graphics processor, TCP is for networking...
[Nexus 4 Original Android Development] franciscofranco:
Yes but it should not do that. I already fixed it on my build and pushed the change to git. Its supposed to scale from 128Mhz to 400Mhz normally.
[Nexus 4 Original Android Development] franciscofranco:
I sincerely laughed reading your quoted post.
[Nexus 4 Original Android Development] dsbrohan:
Indeed. I was quite misinformed and corrected myself after I did a thorough search. My problem doesn't seem to persist anymore, so sorry to cause trouble.
[Nexus 4 Original Android Development] drawde40599:
Naw, ive read every post in this form and missed it also :P
[Nexus 4 Original Android Development] dsbrohan:
Haha my last phone before I got my nexus is may was an old SGS2. Everything is different here.
[Nexus 4 Original Android Development] samuelrf:
my previous phone was an xperia u...so imagine the change...hahaha

PSX v6/ FK 183r/ V4A
[Nexus 4 Original Android Development] comminus:
Just had a random reboot while the phone was sitting idle at the lock screen. Stock rom, no uv or power profiles enabled, only gamma. last_kmsg posted http://pastebin.com/40V3kqrT
[Nexus 4 Original Android Development] svnhvn:
I read in another thread that there is such thing called franco.plus kernel. As far i know thats not from [MENTION=3292224]franciscofranco[/MENTION].
[Nexus 4 Original Android Development] franciscofranco:
r183? I see no error in the log :(
[Nexus 4 Original Android Development] comminus:
Yeah, 183. So far it's an isolated incident but I'll post back if I get a repeat. Just the same, thanks for looking at it.
[Nexus 4 Original Android Development] lalo20:
Me too haha

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] sordna:
thanks for bugfix FKU

Just got the bugfix FKU update, dowloading works much better, and I like the cool notification messages, thank you franco!
[Nexus 4 Original Android Development] svnhvn:
Yup, got that too. Thanks Franco.
[Nexus 4 Original Android Development] amruth kiran:
Hey guys!

Well I just recently rooted and stuffed in cyanogen 10.2 and of course Franco's (#182) and until today it worked fine with great battery life. , I charge it overnight so when I used the phone for like 15 mins to text the battery meter fell by 4%!

And even now it's falling at about 1% every ten mins or so.. Better battery stats shows I am running at 1.5 GHz most of the time, same goes for FKU.

Any suggestions?

Thanks.

NEXUS 4 / CYANOGENMOD 10.2/FRANCO(r182)!
[Nexus 4 Original Android Development] Armin_van_buuren:
Quadrant is a completely useless application that measures the actual performance or a rom or kernel.

If you want to live happier removes that application from your Nexus and enjoy the best kernel out there.