yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] rmead01:
Please keep the original. I've been back and forth flashing kernels because of data connections issues. Wouldn't drop but would take forever to connect and load data. Other kernels no issues, r151 issues.

After reading this I'm back on the r1222 and seems to be working. I had to download the older modem too which helped but didn't fix.

Thanks for the revert!
[Nexus 4 Original Android Development] vastac13:
I'm gonna test r1222 for sure :) flashing atm.. will observe it 2 hrs from now before I go to sleep... As always thanks [MENTION=3292224]franciscofranco[/MENTION] for the immediate revert...
[Nexus 4 Original Android Development] goTouch:
Franciscofranco, I read about it before, but are you boosting both core on r1222? I remember you said that you were going to do it?

If you are boosting only one, the app could choose the wrong one.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] aventu:
2 cores are always on, the first core is affected by touchboost. The app has no control over this.
[Nexus 4 Original Android Development] pikachukaki:
1222 its great no lags no major drain!
[Nexus 4 Original Android Development] franciscofranco:
Not yet. The one Im running has that logic, but not r1222. I pushed the code yesterday night though to allow who build from my sources to test. I will push a normal nightly later today.
[Nexus 4 Original Android Development] goTouch:
That is the problem. The app can choose the non boosted core to run. Kernel can't force the app to choose one core or another.

I just wanted to know if version r1222 is boosting both cores.

You already answered.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] manulemaboul:
Oh, so that's why they seem to be gone then :).

None in the last 2 hours. :thumbup:

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
The apps have no control over that, the thread management is done on the Kernel level by the Task Scheduler.
[Nexus 4 Original Android Development] kara mustafa:
I am perfectly fine with 151 :)

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] jamescable:
Ok, so im having wifi issues on r151. Anyone else have issues?
[Nexus 4 Original Android Development] kara mustafa:
What kind of issue?

I have made today a flash from scratch. CM 10.1 with r151 is superb. Great perfomance, no issues. Strong singal and wifi. People have problems because they change theirs kernels too often and then phone and the whole install is messed up.

Franco, 151 is great here. Everyone who has issue should make a new, fresh install. I always install factory image and then new rom and new kernel.

When can we expect a new bulid with dualcore magic?:D:D
[Nexus 4 Original Android Development] jamescable:
Well i try to turn wifi on and it says turning on but stays greyed out. So i will reboot phone, and wifi is on but signal styas grey instead of connecting. I used older version, no problems. Dis full wipe and still peoblems
[Nexus 4 Original Android Development] corwest:
The elephant in the room says "were you using prima drivers version prior?...' Must flash reset kernel if answer is yes.
[Nexus 4 Original Android Development] LibiSC:
I checked the code... I made a change for a personal build in mako hotplug ... Offline 1 core each time and not all at once...

edit:i meant offline and 0.1 seconds just when one core online otherwise 250 in timer
[Nexus 4 Original Android Development] franciscofranco:
Can you be more specific? Show us the code [co de]diff[/co de] (without the spaces in the code word) and explain us why did you make that change? Can't wait for more development discussion like this kind!
[Nexus 4 Original Android Development] LibiSC:
This ... My idea is when needed the cores should go online.. but i dont have a hurry to make then go offline in case i do something in between... and i'm setting cores on touch 3 but that is just because.

I think that is what that code does... I make than change to feel how it goes...

if (counter >= 10)
{
for_each_possible_cpu(cpu)
{
if (cpu && !cpu_online(cpu))
{
cpu_up(cpu);
}
}
timer = 250;
scale_interactive_tunables(0, 10000, 80000);
}

else
{
if (num_online_cpus() > 1 && !is_touching)
{
for_each_online_cpu(cpu)
{
if (cpu)
{
cpu_down(cpu);
break;
}

}

if (num_online_cpus() > 1){
timer = 250;
}else{
timer=HZ;
}
scale_interactive_tunables(20000, 30000, 20000);
}
}
[Nexus 4 Original Android Development] scottx .:
Just wondering why it won't work with the MIUI ports floating around? Something about the ramdisk I think I heard? Not asking you to support it, just curious.

I'm a long time user and won't use any other kernel. Thanks Francisco.
[Nexus 4 Original Android Development] franciscofranco:
Ah I understand now. Btw this

if (num_online_cpus() > 1){
timer = 250;
}else{
timer=HZ;
}

is redundant. You're already inside a if (num_online_cpus() > 1) condition, you don't need to add another if for that. You can do something like this:

if (num_online_cpus() > 1 && !is_touching)
{
for_each_online_cpu(cpu)
{
if (cpu)
{
cpu_down(cpu);
break;
}

}
timer = 250;
}
else
{
timer=HZ;
}
[Nexus 4 Original Android Development] LibiSC:
I have a doubt with that part if there are 3 up then I shut down one and I call it to see how many up already shows 2...so still >1...but it is only 2 and I shut down one when I call the function again will show =1 and then it's when I want it to be timer =HZ
[Nexus 4 Original Android Development] franciscofranco:
Thats exactly what I did, it only calls for timer = HZ if num_online_cpus() == 1.
[Nexus 4 Original Android Development] LibiSC:
Right I just saw the break I'm using lol... Well I hope with that the transitions are smoother... I have a live wallpaper I can see it slow down after a while I stop playing it with it :D
[Nexus 4 Original Android Development] franciscofranco:
No more of that problem with two cores always online. There are three paths to tackle that in my opinion:

1 - have the governor sample faster and ramp up with less load so it reaches max more easily (already tried this, derps battery life a little bit imo)

2 - have the cores jump up and down faster and more often (already tried this, I don't like the increase on thread migrations and context exchanges, plus hotplugging is costy as ****)

3 - have 2 cores always online, governor doesn't need to go crazy all the time and so easily so it balances on having 2 cores online. boost to 4 cores when load is really big, otherwise it stays nice and cold (trying this)

Its very debatable, this is just my view on things.
[Nexus 4 Original Android Development] pikachukaki:
Leave it as it is...on 1222 with two cores always on...add an option in your app to just when we want to use it as dual core or quad core....and its great...imo dont update hotpluging so often...even if one version is good we can't tell for sure cause after 1.5 charges theres an update...and noone can't resist to an update...add functions to the kernel..i dont know better sound..better camera..you are the boss to decide!
[Nexus 4 Original Android Development] admiez:
I suspected something like this or that at least you had rolled back many of the patches. I was noticing faster drain in 3G.

So you went back to 100% stock? What about what you had added until before r143? I don't quite remember but I think those previous builds had some patches too, and most users that started to experience issues did so with the new set after r143. Although I understand that with every change you've tried on this, someone or the other comes up with some problem.
[Nexus 4 Original Android Development] corwest:
My vote is on number 3. Seems like less status change would be needed in the CPUs and less on lining/ off lining would occur. It seems like peoples use is right on the edge of what one core can handle alone smoothly so theoretically keeping this second core online would help keep the lag and stutters to a minimum since the two cores can handle more threads without having to re allocate them when another core comes online.
[Nexus 4 Original Android Development] goTouch:
Agree. I would go for number 3. I don't know the impact on battery using this strategy. But if it's minimal, definitely number 3.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
I'll update as often as I feel its worth to update. I'm sharing here what I do for myself, anyone can flash or not to flash ;)
[Nexus 4 Original Android Development] pikachukaki:
Im not telling not to update..im telling not to update the hotplug only so often..a bit of change here a bit of change there...its the same to the end user...kernel gives you other abilities too..there isn't only for controling the cpu! ;) ;)
[Nexus 4 Original Android Development] Net.silb:
Haha agreed! Although I think you we are slowly closing in on the ultimate hotplug driver :D

I think it's a great idea to have minimum 2 cores online all the time and to boost both of them, saw the code and can't wait to test out the next build!
[Nexus 4 Original Android Development] z3r0_x:
I feel r1222 is the way to go - 2 cores is very performant and nice on the battery.

The r151 was a little better, but that's merely because of my special usage where it's on most of the time doing nothing, just waiting for a Whatsapp message to come and one core @ 384 Mhz is obviously slightly less taxing on the battery as two - but in general, I feel 2 cores and balancing things with the governor is the best solution.
[Nexus 4 Original Android Development] manulemaboul:
Never saw a regression so far :)

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] justibasa:
After having data drops on every kernel since 14_ without let up, including 1222, I decided to clean flash everything. Wiped every thing and haven't had a data drop since. If your having problems it might be the solution. Thanks for the great work you do Franco. My phone wouldn't be worth using without your kernel.

Don't like me........BITE ME!!!
[Nexus 4 Original Android Development] lordvj:
number 3 sounds good. but doesn't keeping the 2nd core on all the time increase idle or sleep battery consumption ?
[Nexus 4 Original Android Development] franciscofranco:
CPU management is what I like the most, I only do this for enjoyment ;)
[Nexus 4 Original Android Development] Net.silb:
I'm 99.9% sure we're talking about screen on here...
[Nexus 4 Original Android Development] franciscofranco:
No........... During sleep all cores but cpu0 go offline.
[Nexus 4 Original Android Development] pikachukaki:
You know!!
[Nexus 4 Original Android Development] corwest:
He was talking about keeping the 2nd core from going offline. Not the screen on.
[Nexus 4 Original Android Development] Net.silb:
He was saying that having two cores online will increase sleep battery consumption...
[Nexus 4 Original Android Development] Karlo666:
[MENTION=3292224]franciscofranco[/MENTION] after ROM update paid version of your update app crashes but free one works fine.
[Nexus 4 Original Android Development] lordvj:
oops that was a nooby question lol and yeah I thought so too just wanted to be sure :D
[Nexus 4 Original Android Development] hospital349:
Interesting issue, if anyone might care to answer:

Was briefly using Trinity and was able to Overclock up to 1728MHz for days on end without any stability issues. 1728MHz was being used regularly using Ondemand. However, with franco.Kernel; even one or two frequency steps above default gives me random reboots and freezes. 1728MHz is a no go, also. Any ideas as to why this might be? - I know that my CPU is capable of higher frequencies, (I'm faster binned and down UV btw). I'm a little confused as to why it isn't possible for my device, using Franco?

P.S. I'm not even that interested in overclocking, as I'm more than happy with the speed of my phone without such function. I'm just interested in finding out why... that's all. :)
[Nexus 4 Original Android Development] nadavar:
After about 2 hours with r1222, with normal use - browsing, messaging and such, I find 151 to run cooler and also smoother. So far I think 151 is perfect
[Nexus 4 Original Android Development] drawde40599:
Try reinstall your rom... If u could do it on trinity then u should be able to do here, pretty sure exact same code. Im OC at that freq with no issues.
[Nexus 4 Original Android Development] kelah:
r1222 fixed battery derping for me.

With r151 battery percent stuck 3-4 times a day. With r148 too, about earlier versions I can't recall.
[Nexus 4 Original Android Development] hospital349:
Unfortunately, it's been the same occurring issue for weeks on end. During this time, I've been on two different ROMs (PA and cfX) - cannot OC on either using franco.Kernel. However, OC with Trinity was absolutely fine.

As mentioned, it definitely isn't really a concern. I'm more intrigued than anything.

Furthermore, it wasn't long ago that I made a full wipe of my External Storage. So I can't even suggest that it might be 'old settings left over', or similar rubbish reasonings/justification. Totally baffling.

Oh well... that's life! :cyclops:
[Nexus 4 Original Android Development] The Gingerbread Man:
[MENTION=4576221]hospital349[/MENTION] its probably a voltage issue is say, trinity could use a different value than Franco for that particular speed. Check to see if trinity's uses a higher voltage then you could 'over volt' that particular speed using Franco's app
[Nexus 4 Original Android Development] drawde40599:
Ya dunno , but here is link to post from franco so i think same code as trinity, Havent seen anyone else mention they cant OC

http://xdaforums.com/showpost.php?p=40833266&postcount=27323
[Nexus 4 Original Android Development] hospital349:
Thanks! I'll give it a shot. Strange though, as I have a faster binned CPU. Now I understand that all CPU's UV differently, though I cannot understand why mine won't OC with stock voltages. I'll try a little Overvolt and see if that does the trick. I'm real curious as to the reasons behind my lack of OC success. Let's see...

EDIT: Possibly fixed, after stability testing for 10 minutes using higher voltage values. Many thanks to those who replied. It never occurred to me that the stock voltages might've been the issue. Either way; totally satisfied my OC(D). :cyclops:

I can sleep now.
[Nexus 4 Original Android Development] 3dawg:
I have observed the exact same behaviour as you describe. I didn't check my voltages while on Trinity though, so they may be set higher by default. To get 1600+ stable on Franco, I had to up the voltages quite substantially.
[Nexus 4 Original Android Development] RootTheMachine:
It is quite normal for things like this to behave differently across different kernels. It can even happen between different updates of the same kernel.
[Nexus 4 Original Android Development] asprofridis:
Restarts with slim 4.2.2 bulit 6

Dear franko, I ve always been loading your kernel with slim rom and after latest build of their rom and your kernel I face some restarts.I ve attached the log to check if it is kernel related.I will post it also to slim thread.

regards

Miltos
[Nexus 4 Original Android Development] mgear356:
I can confirm that there is such issue with oc. 1620 and above will cause auto reboot. Didn't happened to 14x and below
[Nexus 4 Original Android Development] yokuyuki:
Performance? My biggest issue with Ingress is that it drains battery so fast. It really limits how much time I can spend playing it.

Force gpu rendering makes some apps that don't support hardware acceleration render really funny. An example would be Speedtest.
[Nexus 4 Original Android Development] Testraindrop:
That are Romlevel issues and a romlevel log, Facebook is derping as you can see there.

Get a last_kmsg if you think its kernel fault.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Do you have a battery pack for Ingress? Lol
[Nexus 4 Original Android Development] asprofridis:
thx for your reply.

here is my last_kmsg
[Nexus 4 Original Android Development] baza14:
Yep same here.
[Nexus 4 Original Android Development] 3dupunk:
It's been driving me crazy all day! I'll post my logcat In a bit as I'm out and about. At least I know that I'm not alone.
[Nexus 4 Original Android Development] Svid:
No issues so far, great job :)
[Nexus 4 Original Android Development] peikojose:
Is it OK to grennify Franco's app?
[Nexus 4 Original Android Development] The Gingerbread Man:
I can confirm the only bug here is some devices handle over clock or under volt or both better than others. Some silicone is simply just a little better than others, its a lottery when you get your device. Its nothing to feel bad about or embarrassed, these manufactures make these things so they are 99% stable for everyone with just a hardware defects slipping through the net occasionally. Sometimes instability can be solved finding the correct voltage, other devices just can't handle it, its as simple as that.
[Nexus 4 Original Android Development] nellisere:
I've found that using greenify, everything that you "Set On Boot" no longers sets on boot, so I don't greenify it. There's no need either.
[Nexus 4 Original Android Development] franciscofranco:
Why would you do such thing if my app doesnt waste any battery?
[Nexus 4 Original Android Development] noneabove:
The way you said "Why would you do such a thing" made me think he was like hurting a small innocent animal.. Well, I guess he would be freezing your baby that you've worked so hard on :P
[Nexus 4 Original Android Development] thracemerin:
Everyone who uses greenify seems to be obsessed with greenifying everything on their entire phone.
[Nexus 4 Original Android Development] ansontyl96:
That's so true, including me:D
[Nexus 4 Original Android Development] manulemaboul:
I was like that when I installed it the first time.

Now I only greenify maps and Gnow, so they don't use localisation services when I don't need them.

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] rmead01:
I use for a few basic things and leave it at that. Facebook/twitter and a few games that don't seem to properly end their task when my son is done playing them. Try not to get too crazy because when you screen on then a lot of those process will resume and start using batt to catch up
[Nexus 4 Original Android Development] Mercado_Negro:
Greenify is a nice concept but we should just use our phones and enjoy their capabilities. It's cool to learn about Android and take our phones to their limits but just make use of them is even cooler :)
[Nexus 4 Original Android Development] zephiK:
Thats not the point though.

Greenify is used (at least for me) in blocking out poorly coded apps like Facebook. I could be rebooting my phone and Facebook is automatically running in the background trying to get my GPS location and whatnot even when I never loaded the app and notifications is set to off for the sync interval.

Greenify is a good app if used properly imo. But yeah, no point in greenifying Franco Kernel app, its already as green as it is :p
[Nexus 4 Original Android Development] Mercado_Negro:
I've also seen those apps running in the background here, mostly when syncing. Facebook, Maps, etc. But I can't really tell if they're doing more harm than good because my phone's deep sleep is solid and their impact on the system is zero, at least here. I've even monitored things with BetterBatteryStats and their wakelocks are something like 2 minutes in 8 hours or something like that. I think we worry too much about our phones and that's why I wrote my previous post. Being obssesed with a phone is not healthy, and that's what some people look like (not you, specifically).
[Nexus 4 Original Android Development] eddy4823:
Getting good battery life on r151.
[Nexus 4 Original Android Development] goTouch:
I would not do it!

It needs to run at system startup to apply your settings.

Besides that, you are not going to improve anything doing it.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] yokuyuki:
Of course, but it's annoying to use it. I have a massive one and I hate carrying it around.
[Nexus 4 Original Android Development] gharrrrrr:
I know how u feel :D

Sent from my Nexus 4 using a flounder.
[Nexus 4 Original Android Development] zephiK:
I agree with you on being obsessed with a phone. Most of us are phone enthusiasts and always want the newest and latest. I personally just dislike the people who are 'battery obsessed' and bragging about their on-screen time showing 4.5 hours+ when they disabled two cores, having maximum cpu frequency of 1GHz or something.

It's a phone.. just use the phone as how its intended. Like I said in the past, if the phone gets me past the day without dying then I call it a success. Anything extra is just a bonus.

Battery tip for you guys though..... Settings -> Google -> Maps & Latitude...... disable automatic reporting and those other things in there. Google Maps has it so it syncs your location by default ;) thats why its running in the background.
[Nexus 4 Original Android Development] manulemaboul:
just do like me: buy a Qi charger, remove every single battery level indicator and forget your device is battery powered :p

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] dapsANDpoundz:
If Maps isn't syncing your location in the background, won't that mess with Gnow or other services? For example, I like the "Leave now, get to X location in X mins" feature when I have an appointment or something. Will it still know where I'm at if Maps isnt updating my location?
[Nexus 4 Original Android Development] whitedragonz83:
Google Now uses location services which is cell towers and Wi-Fi. I always get the notifications you are asking about with latitude off.

Latitude is more about auto check in and Google+ location sharing with friends.
[Nexus 4 Original Android Development] Koraboros:
I'm still randomly getting signal being gone and my GPS randomly switches on sometimes. When I go back to R135, it's fine but after 148-151 it's been happening.

Any logs or something I can provide?
[Nexus 4 Original Android Development] franciscofranco:
Signal gone -> will be fixed in the next one.

GPS turning on by itself -> something else rather than the Kernel.
[Nexus 4 Original Android Development] manulemaboul:
Wait for the next nightly or use r1222.

It's fixed ;)

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] thebryceee:
https://support.google.com/websearch/answer/2819496?hl=en
[Nexus 4 Original Android Development] bleuwave:
What font is that and how did you apply it?

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
I'm very excited to announce that I officially released the new v10.0 of franco.Kernel updater. This is the official changelog:

* Upgrade to the new Navigation Drawer API from Google. Now its much easier to navigate through all the app sections

* Default Update Service refresh rate has been upped to 12h as a default

* New Status panel showing quick and informative info about the app and the phone

* New Support page with links to the XDA threads, my G+ profile and FK Community link

* Hopefully fix the md5hash fail on the N4

* Tons of bugfixes and smaller improvements

Trust me that there is a LOT planned for the next versions now that I'm quite happy with the overall look and design of the app (still not 100% happy as some dialogs are not themed correctly, but that will be worked on ASAP). I have a big list of new features for the future! I'd like to personally give my thanks to app the beta testers of this app, all the suggestions, remarks, constructive feedback and of course bug reports with logcats. I hope Google refreshes their servers ASAP, I want this update out for production as soon as possible :)

Here are some screenshots of the new app:
[Nexus 4 Original Android Development] mackster248:
Thank you Franco!
[Nexus 4 Original Android Development] Savant:
Being a beta tester is fun because you get to help be the guinea pig for a kernel genius. Nerdgasm anyone?
[Nexus 4 Original Android Development] Are.Two:
Glad to see that it's finally getting updated! Testing it has been awesome and its been fun to play with. Hope everybody enjoys it as much as I have!