yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] :
franco.Kernel Updater 9.5.3 crashes every time I try to open the Governor Settings.

Also, the UV settings don't seem to stick between reboots even though I've it checked.

I was pretty happy with making my Nexus 4 dual-core, but the new r150 seems to have removed the necessary settings, why is that?

Here's what I was using:

CPU: 384 - 1024 MHz, Interactive
UV: -75 mV

Online all cores: 100
Online single core: 50
Offline single core: 49
Offline all cores: 10
Touch cores: 1
[Nexus 4 Original Android Development] Net.silb:
Yep, [MENTION=3292224]franciscofranco[/MENTION] tried fixing it in r150 but obviously the bug hasn't been squashed...

The only weird thing is that it only happens after a few hours...

I think he's sleeping now so we'll tell him about this later...
[Nexus 4 Original Android Development] Mercado_Negro:
Same here with r1111. My phone was really slow after I unlocked it. Only a reboot cured it.

Let's see how it'll behave tomorrow when I wake up.
[Nexus 4 Original Android Development] Net.silb:
Haha it's a shame computers don't really work that way... If there's a bug in the code, the code isn't going to change until it's fixed... ;)
[Nexus 4 Original Android Development] Bobtehblob:
Been on r150 for a good 6 hours or so and it's starting to bog down really badly whilst scrolling :(
[Nexus 4 Original Android Development] Net.silb:
Hotplug algorithm has completely changed, read here: https://github.com/franciscofranco/mako/commit/d03318c5548abf61887749982430d7b23072d123

The only variable now is high load threshold, all the rest are gone.

I'm gonna explain in general, in terms of load, if it's over High load threshold, all four cores will go online, otherwise only one core will be online.

On touch, two cores will be online (In FKU, cores online on touch input).

For a more detailed explanation check the link above.
[Nexus 4 Original Android Development] ferreinf:
Nice to see you again Francisco, props for your work :)

moved to the Nexus and loving it so far running your milestone 2, still getting used to the nexus development.... ;)

To all any rom advise?

Thanks
[Nexus 4 Original Android Development] Net.silb:
[MENTION=3292224]franciscofranco[/MENTION]

mako / arch / arm / kernel / mako_hotplug.c

if (is_touching)
{
if (!cpu_online(1))
cpu_up(1);
}

It seems to me the only possible bug here can be with the is_touching variable... I'll keep digging and hopefully I'll find the bug.
[Nexus 4 Original Android Development] nexusmaniac:
If by that you mean which ROM to choose, then any, just go with the one that has the features you need/want :)
[Nexus 4 Original Android Development] Redneck Trash:
So this is new. Wondering if anyone here has seen this before.
[Nexus 4 Original Android Development] ratcav:
Yeah, don't worry about it, they are the sensors if the phone
[Nexus 4 Original Android Development] Jiia:
Franco, could you add more contrast to the changelog view in your francoKernel app. I just tried reading the changelog in sunlight but couldn't see a thing because it's dark grey on black. That's the case in the dark themes
[Nexus 4 Original Android Development] trailblazerz11:
Think that code was replaced by one of the latest commits, reimplemented cores on touch
[Nexus 4 Original Android Development] Net.silb:
You're right.

[MENTION=3292224]franciscofranco[/MENTION]

This is the code:

mako / arch / arm / kernel / mako_hotplug.c

if (is_touching)

{

for_each_possible_cpu(cpu_boost)

{

if (!cpu_online(cpu_boost) && cpu_boost < stats.cores_on_touch)

{

cpu_up(cpu_boost);

/* we're interacting with the device, online cores are boosted
to hispeed_freq at least for a sample */

cpufreq_get_policy(&policy, cpu_boost);

__cpufreq_driver_target(&policy, DEFAULT_CORE_ONLINE_BOOST,
CPUFREQ_RELATION_H);

}

}

}

I just don't have enough knowledge to know what this code does exactly... I'll try to understand exactly what this does later when I have more time.
[Nexus 4 Original Android Development] italia0101:
Woke up today. ... my device is stuttering as well in r150 :( , was smooth before ! Damn
[Nexus 4 Original Android Development] Net.silb:
A temporary fix that will give you a few smooth hours is rebooting.
[Nexus 4 Original Android Development] trailblazerz11:
Seems it occurs after an extended period of deep sleep, anyone confirm?

I've been waiting for it to happen again but so far working fine, quite odd.
[Nexus 4 Original Android Development] Net.silb:
I don't think its related to deep sleep.
[Nexus 4 Original Android Development] Cantacid:
If charger would have been the reason it would have gone to deep sleep after that! But no. Its just going into deep sleep for some reason.

Edit: CPU spy suddenly refreshed and changed the timings. My bad! Will report battery life at the end of the day!
[Nexus 4 Original Android Development] trailblazerz11:
Not saying deep sleep is causing it but in my case and his, it was only after an extended period of not using the phone that the issue appeared.

I haven't seen the bug since I rebooted earlier perhaps because I've been using my phone constantly now. Just speculation
[Nexus 4 Original Android Development] drawde40599:
Go to the GNex thread and start reading all the crap / and unnecessary issues ( user error ) that came with lower slots and UV when he added it there , thats my GUESS y he not adding it ;)
[Nexus 4 Original Android Development] Artius89:
Hi franco, i just bought your app, and I saw the disable fsync feature, most kernels now implements the dinamyc fsync option (deferred when screen is on), could you implement this feature in a next release? I don't really want to risk to totally disable the sync, but it give a noticeable boost to smoothness!

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] Vangelis13:
Potential risk of: loss of signal, reboots, sod, instability in general. Plus, the ever so famous race to idle. ;)
[Nexus 4 Original Android Development] kyokeun1234:
Does media server have to do with the wake lock? After 22 nightly, media server have been using lot less battery on my battery usage thing.
[Nexus 4 Original Android Development] franciscofranco:
:)

Nope, thats faux code, I don't use his stuff.
[Nexus 4 Original Android Development] BRKotucs:
@ Francisco, I just got a random reboot on r22 while listening to Google music.

Here's the last kmsg for you to take a look at it.

http://db.tt/lG8MIKXp

Running Paranoid Android 2.99 beta 9 with stock settings.
[Nexus 4 Original Android Development] Vangelis13:
Straight & to the point. ;)
[Nexus 4 Original Android Development] alcurtis93:
Does this kernel support the faster binning CPU or will it just use same voltages as fast like stock?
[Nexus 4 Original Android Development] republicano:
lowering the clock is not a priority, stability is then undervolting etc.

since the lowest clock is at 384mhz it might not be efficient to have to at 200-250mhz if it has the same power requirements or its so minimal that the phone becomes instable SOD, then you would have noobs thrashing this thread.

what you want is more cpu controls so it wouldn't jump to 1500mhz so easily,(go hispeed load)

I have been testing the cpu speeds with prefmon and have the core at 1000mhz, its alot better at idle its mostly 2 cores and 4 when loading apps or running in the background and 1-2 cores idle, but if you have it at 1500mhz it jumps from 384 to 1500 when idling, it peaks easily when core is at 20-30% load.so change the hi speed frequency to something like 810-1000mhz
[Nexus 4 Original Android Development] drawde40599:
vibrate

@Franco is it possible u can raise the 100 limit on vibration control ? I still don't find 100 to be enough
[Nexus 4 Original Android Development] franciscofranco:
Thanks. I will check that log when I am back home, currently sitting in Burbank Airport waiting for my flight.

All that jazz is stock.
[Nexus 4 Original Android Development] franciscofranco:
Its just a IO scheduler from Qualcomm that prioritizes READs over WRITES since we spend more time reading bytes from somewhere rather than writting.
[Nexus 4 Original Android Development] Ballastatuz:
My man Franco. I am pretty impressed with r22. Everything is stock. Just screen is set to 223 223 223.
[Nexus 4 Original Android Development] n7of9:
serious question: how is that any different to 255 255 255? isn't it just duller?
[Nexus 4 Original Android Development] alcurtis93:
It will be 8) ha
[Nexus 4 Original Android Development] JNewms:
Hey guys, gonna go off topic real quick. I just did something that I haven't done in years. I'm in the Midwest and we've been getting hammered by snow. Anyway, i just managed to sign my name in the snow, first and last. Now guys, you know how hard it is to cut off the flow. Yes, I'm 28 and I can still sign my name in the snow.

Sorry to go off topic, just had to brag. Let's get back to talking about how we have the best kernel Dev out there! Thanks for listening :)

Sent from a Paranoid N4
[Nexus 4 Original Android Development] co0kie:
Reading through the last 100 posts here (amazing to see how many times a question repeats itself), I'm still clueless as to how people actually get ~4hours of screen on time.

I've been using Franco's kernel on Stock, Modaco and now running on Romann's AOKP and with all of them never managed to go over 3 hours (to be precise, the record was 2:45hours).

I'm using auto-brightness, all sync is off except for Google's accounts (no photos/music sync) + Whatsapp, underclocked to 1.25GHZ and no special apps or heavy game usage (barely if not none of gameplay), mainly 3G data usage, good reception overall.

Any ideas?

P.S, for the record, the N4 delivers the best battery life i've ever had on a smartphone but reading through the posts i feel like i'm missing something? Do people just disable the sync all over to get such figures?
[Nexus 4 Original Android Development] derPianist:
And even that does not prevent you from supporting us. That is what I call a AWESOME Developer. :)

via Google Nexus 4
[Nexus 4 Original Android Development] JNewms:
I came from a Razr Maxx to the N4, left Verizon to get it. I'm getting amazing battery life off of this kernel. The only thing I've changed from my normal usage is that I don't have Google now enabled. The reason I brought up my Razr is because I'm getting close to the same life on my Nexus as I was in that using Franco's kernel. Don't know how we got lucky enough to land a genius that devs for our phones, but he truly is a miracle worker.

Sent from a Paranoid N4
[Nexus 4 Original Android Development] jhericurls:
So why are you repeating it again.
[Nexus 4 Original Android Development] Net.silb:
Give it 4-6 hours from boot and then no matter what you're doing it will happen, that's what I think.
[Nexus 4 Original Android Development] steviewevie:
On 148, this morning I had no signal until I rebooted my phone. Airplane mode on/off didn't help. It wasn't a network issue, the signal comes from a femtocell in my house (i.e. a mini 3G base station connected to my broadband, an official one from Vodafone), and the femtocell was working normally.

Sent from my Nexus 4
[Nexus 4 Original Android Development] trailblazerz11:
We shall see :) though it makes it ridiculously annoying to debug... Compiled kernel with some more messages, opened up adb kmsg and just watching the office til it borks heh.

Franco will probably figure it out faster but I still wanna learn and experiment more with Linux now that I have time.
[Nexus 4 Original Android Development] pikachukaki:
Its only me or at the latest versions the great battery life has gone?
[Nexus 4 Original Android Development] Net.silb:
Wanna bet on it? ;)

LOL Franco is like a god with these stuff, he'll figure it out without even debugging! :silly:

It's pretty funny because I also have plans to learn Linux and Linux Kernel, so far I've been learning from Franco and from reading his code, In a month or two I'll have much more time and I'll be able to really start doing things. You wanna work together and help each other with learning and stuff?
[Nexus 4 Original Android Development] ChongoDroid:
Very fast, also noticed a bit of a microstutter however it seems to have passed. Also during the little bit of time playing with 150 I can tell it runs VERY cool and very light on battery.
[Nexus 4 Original Android Development] konfuzed:
the kernel god :good::good::good:
[Nexus 4 Original Android Development] trailblazerz11:
I don't mind a friendly wager ^^

Yeah I followed Stratosk on i9000 for awhile, then franco on Gnex&Nex4 got me pretty interested in Linux but I mostly ended up reading some code and cherrypick/compile. Now with some free time figured I'd try to go deeper, do some more reading started messing with kernel on desktop. CompSci major, I found myself far more interested in Linux and Android then anything taught in class, hopefully helps in the future :)

Lol, I get busy in a month or two but that sounds fun.
[Nexus 4 Original Android Development] thuynh022:
I was also getting a bunch of lag and stutters on 150. Flashed 1111 a couple hours ago and now the stutters are starting up again.
[Nexus 4 Original Android Development] jarayn:
How odd. I would say almost exactly the opposite.

Hot and worse battery with consistent micro stuttering.
[Nexus 4 Original Android Development] Net.silb:
Great we'll keep in touch! :)

By the way, the lag has returned two hours since my last reboot... Going down for another reboot...
[Nexus 4 Original Android Development] zellleonhart:
Going back to r142 for now. r1111 was really smooth at first but after few hours it stutters.

Only 1 core running while touching it. Doesn't really stay at 384MHz most of the time (the CPU runtime was balanced between 384, 702 and 1350, al 30% +-).
[Nexus 4 Original Android Development] Net.silb:
You can reboot to fix that stuttering for a few hours if you want to stay on r1111.
[Nexus 4 Original Android Development] thuynh022:
My phone seems to be way hotter than usual too. Just listening to Pandora and I was hitting 63c. Never felt/seen my phone so hot before, and I use Pandora for about an hour everyday.
[Nexus 4 Original Android Development] Khaiyan:
I can confirm the lag also. Heck I'm getting from just scrolling my home screen (not a live wallpaper).
[Nexus 4 Original Android Development] Floydfire:
I have flashed the 1111 version four hours ago but I don't see any loss of smooth....

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] drakexpl:
How do guys know if Phone is more smooth or less? On every franco kernel version my gnex is buttery smooth, zero stutters etc. Im using it since r130

Wysłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] trillo69:
Sorry for the offtopic, it actually works, it's easy to see the difference on pages that load a lot of comments (like disquss board), they used to scroll really laggy and now it's smooth. On normal webs chrome v18 is still smoother than beta. Thanks.

Well, you just check some apps that use to be laggy like facebook or tapatalk, and also make some hours of your normal usage, and compare.
[Nexus 4 Original Android Development] lzy23:
Getting noticeable lag in r150.

r148 had insanely good idle/sleep batt drain (almost non existent), and was very smooth as well.

Running Jelly Beer Rom.
[Nexus 4 Original Android Development] Audioboxer:
The new test with ondemand seems smoother than 150.
[Nexus 4 Original Android Development] drakexpl:
For me r150 is like butter. Im on cm rc4

Wysłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] doublem75:
Same here
[Nexus 4 Original Android Development] sam razzy:
I don't see any problem after flashing r1111, I read 25pages and I see lots of feedback which says there is a problem with x or y side. But after flashing r1111 did your mobile face any problem ? Thank you so much Franco..
[Nexus 4 Original Android Development] alanwyl:
There is no problem for the first couple of hours after boot. Somehow, the device is laggy after certain point of time.

And many of us are discussing what causes the trouble. I am sure Francisco is looking into it now.
[Nexus 4 Original Android Development] goTouch:
I try every new build but always come back to r143.

It is part of the process. Keep up good work!

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] LaboDJ:
Hi Franco

I read you default config file, I compared it with Faux, Stratosk and Anarkia ones.

Here are my questions:

CONFIG_SWAP=y , Do we need swap with 2GB RAM?

CONFIG_EARJACK_DEBUGGER=y , Do we need it?

CONFIG_MSM_SMD_DEBUG=y , Do we need it?

CONFIG_MSM_IDLE_WAIT_ON_MODEM=500000 , Why 500000? Isn't it high? Default is 0

CONFIG_RADIO_ADAPTERS=y, Every radio in config is not set, why to use it?

CONFIG_DNOTIFY is not set, some applications may still rely on dnotify, android may not?

CONFIG_NTFS_FS=y , NTFS? why? we don't have usb otg and sdcard slot

CONFIG_NETWORK_FILESYSTEMS is not set, CIFS can be useful, don't you think?

CONFIG_FRAME_POINTER=y , it isn't better to use ARM_UNWIND=y?

Edit: another question, in lib/vsprintf.c you updated recently BITS_PER_LONG variable is used, anyway it's not defined.

lib/vsprintf.c:127:28: warning: "BITS_PER_LONG_LONG" is not defined [-Wundef]
[Nexus 4 Original Android Development] xanthrax:
what i`ve have noticed is that the problems arise when various tweaking kernel apps are used in the same time

i would suggest that only one app to be used and the previous ones to be fully cleared before applying settings , delete data/cache/app , reboot and then ...

franco kernel best runs with its application !

btw , 150 has no issues since yesterday , heavy use
[Nexus 4 Original Android Development] Pure Drive GT:
Exactly what i did with my s3 ;) Exynos Source Code pissed me off...
[Nexus 4 Original Android Development] vjales:
I came back to r148 until franco "fix" some things, and the battery is a little better on 148 too

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] tr1cky1:
Every time I unlock my phone it asks me to enter my sim pin. That never happened before 150
[Nexus 4 Original Android Development] nachordez:
For me r1111 is working nicely, both in no lag and battery draining. And most of all, in connection with bad signal! Better than ever.

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] thebryceee:
R111 or r1111?
[Nexus 4 Original Android Development] trailblazerz11:
[MENTION=3292224]franciscofranco[/MENTION]

Did a bit of debugging on why the 2nd core isn't onlining after awhile. Had to wait a couple hours for the bug to appear.

So far from adding some kmsgs, I've found that in decide_hotplug_func(), the is_touching works fine and it does enter the boost portion.

The deviation from normal operation is that boost is constantly getting called during constant touch instead of staying boosted on constant touch, then only getting boosting after a period of no touch and the core1 offline. Here is the rough kmsg when buggy of just swiping constantly http://pastebin.com/2kL3dAga rather than normally where there would be one boost then touch would be spammed until I stopped touching.

I would guess that core1 is immediately getting offlined afterwards so boost is constantly taken so perhaps an issue with the counter(?) and that its entering cpu_down portion. Perhaps this switching is so fast that since system monitor isn't polling fast enough it think's its offline most of the time, only showing core1 online randomly every so often.

Compiled again with more pr_info to see whats up with counter. Gonna have to wait another couple hours (which is really weird but quite consistent)

:( Hope this helps, not really sure what I'm doing ^^
[Nexus 4 Original Android Development] noneabove:
Hey [MENTION=3292224]franciscofranco[/MENTION], I just updated to newest PA, and have installed your newest kernel (of course) but for some reason now, after 2 boots, it'll reboot immediately after displaying the lockscreen, but then after the boot be completely fine (until the next manual boot) and both times the last_kmsg says kernel_panic, i'll throw up both of them so you can check em out if there's anything interesting.. Again both times they had literally just finished booting and after the kernel_panic boot the phone's completely fine.

Thanks!
[Nexus 4 Original Android Development] BigDig:
MIUI??? WTF!? We are grown ups here!
[Nexus 4 Original Android Development] nachordez:
1111, sorry! I'm editing

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] X DoZ3R:
Hi, im following this thread long time ago and read every pages, but lots opinions. Im lost a bit. Some can recommend which version should i install? Because i saw some versions are lagging some not , its hard to find a good one. Ty :)

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] Net.silb:
It looks like you're on the right track, Franco is only going to see your messages when he wakes up which should be soon because its 7:30 AM in California.

Basically, you're saying that it onlines cpu1 as usual on a touch event even when the bug is present, but the bug is that it offlines cpu1 right after it onlines it. I think that's good progress in finding the bug! Now we just need to figure out what's causing the immediate offlining of cpu1...
[Nexus 4 Original Android Development] freddysam:
Try M2. It is stable.
[Nexus 4 Original Android Development] franciscofranco:
Thanks guys. I think the problem is that when doing ktime_to_us(ktime_get()) after a while the number gets seriously huge, and not even a long is enough to store the big number. I compared to what Google did with other variables that use ktime_to_us(ktime_get()) and they used u64 types for this problem. I managed to reproduce the bug after I woke up and I saw exactly what I was hoping to see. I know what to do to fix it so fix incoming in a few minutes after I had something to eat :) Thanks guys, that type of help is always seriously welcomed!! :)

Typical DMA panic because you turned your screen off while the app was setting the GAMMA values. I seriously gotta find a way to fix that.
[Nexus 4 Original Android Development] admiez:
So while you guys debate about the lag and stutters with the new hotplug solution I just set my governor to Performance for today, max frequency to ~1.7GHz and UV by 100mV all across. Let's see how long the battery lasts with my normal usage. It's even running cool, no heat. It's actually a good thing to experience the potential once in while to set the right expectations. For example, while almost everything is buttery smooth, some apps reveal that the bottlenecks are somewhere else and even all the CPU power can't get rid of their stuttery behavior(e.g. some lists with images, fast scrolling on Play store).

Eventually [MENTION=3292224]franciscofranco[/MENTION] will iron out any defects and find more ways to improve the hotplugging behavior, and which settings provide a good combination of performance and battery usage. Moving to a simpler solution is the right move and will enable that without having the complexity of too many variables. Let's just remember it's a brand new solution that was just released and will just get improved as the others in the past versions.
[Nexus 4 Original Android Development] Net.silb:
Glad we could help :)

Out of curiosity, what is ktime_to_us(ktime_get())?

Where is it, what is it and what is its job?

Is this related?

https://android.googlesource.com/kernel/msm/+/24e7f7267117554372280b849259893364cb47af^!/
[Nexus 4 Original Android Development] nachordez:
I have to correct myself. r1111 is again giving signal problems. My 3g connexion completely, and I have to connect flight mode on and then off, and I'm asked for pin again. Then, I have signal again.

Correction: while I was writing this words, I have been asked for pin again!

That's weird... :confused:

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound