yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] cobyman7035:
20% screen brightness, try r62 using conservative gov, lower max cpu to 1026mhz , i think with heavy 3g usage, max screen on time will be 4hours
[Nexus 4 Original Android Development] elzafir:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

I don't know what happened, but i flashed the new TWRP 2.4.1.0 and after reboot suddenly all four cores are active and lags like hell! Kernel info on Settings-About Phone still shows r62.

Help?
[Nexus 4 Original Android Development] Saiger:
what about a clean kernel reinstall?

use this script http://xdaforums.com/showthread.php?t=2121701 and flash the kernel again

but be careful!
[Nexus 4 Original Android Development] elzafir:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

That works flawlessly!

Thanks man!

Still don't know what went wrong though.
[Nexus 4 Original Android Development] calanizzle:
I can easily get 4hs+ of screen time; will try lowering max cpu
[Nexus 4 Original Android Development] airchie:
Which ROM?

I'm on Minco v6 with r62 and recently installed TWRP 2.4.1.0 using GooManager app with no issues?

Maybe try wiping cache and dalvik cache?

Maybe try dirty-flashing your ROM and/or kernel again over the top without any wipe? :)
[Nexus 4 Original Android Development] mjehan:
-> Yes to widget to switch between 3 power modes ( Saver, Normal, Performance)

Saver Mode: Max 2 cores on. 1 core when screen off (no hotplugging required)

Normal: screen off 1 core, screen on 2 cores, and possibility to go up to 4 cores if the load is that high ( some hotplugging required)

Performance: 2 cores on all the time. 4 cores when app is launched

-> Interactive is so far the best for me. Conservative lags. I favour a solution in which each core has its own governor. First 2 cores on interactive and last two on conservative (when on normal mode).

-> ROW is good when on normal use of phone. Deadline is better (no lags) when on intense apps like gaming. (R53)

-> UV with -150 mV has brough about 30 mins more 3G surfing time for me (R61). Underclocking core 1 & 2 to 1026 MHz without any UV (R62) gives me almost an 40mins more of 3G browsing (R62). Additional UVing maybe gave me 5-10mins more but somehow device starts lagging. The best mixture would be to underclocking cores to a speed of 1284 MHz and implement UV of -100mV.

-> Wakelocks are for still a problem me (back to R53). Worse on 3G as Wifi and I would like a version of your kernel with the HSIC patches since data drops for me were very rare.
[Nexus 4 Original Android Development] cobyman7035:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

2cores on with 4cores option
[Nexus 4 Original Android Development] calanizzle:
+1

If 3 cores is possible, I would like to try that!
[Nexus 4 Original Android Development] GJ123:
Exactly my thoughts!

Except your 'normal' mode should just be standard, we don't want fragmentation.
[Nexus 4 Original Android Development] iammudd:
I've never been on stock but kernel dev's (including franco) have said that the "smoothness" was achieved by raising the min cpu freq very quickly AND keeping it high (presumably for a long time) --- and ppl were not getting 5+ screen time like you.

If your question is why don't r61/r62 dynamically change the number of cpu's, franco explained that "hotplugging" cpu's is expensive in terms computing power and battery. (Monitoring with perfmon, hotplugging also coincided with micro-stutters.) r61/r62 were built to test whether performance and battery could actually improve by keeping all 4 or all 2 cores online -- eliminating hotplugging overhead.

r61 keeps all 4 cores online. r62 keeps 2 cores online -- but you can trick it into r61 4-core mode (until screen off) by using franco app to toggle a governor setting. Many (but not all) have reported that both performance and battery improved. (For me, I prefer a notification widget to online/offline cores over hotplug.)

Some reported that r62 (with less cores) actually responded better (e.g less lag) than r64. A possible explanation is that the 4 cores are not synch'd to the same (min) freq. Having 4 cores active can actually be a detriment. I've asked HOW tasks are assigned to WHICH cpu a couple of times without reply ... but if an interactive task (or one on the critical path) is randomly scheduled on a low load / low freq cpu, the actual delay is more. (edit: Perhaps that's why mpdecision on stock raises min freq so quickly. Perhaps the prob was that min freq didn't reset when only 1 core is online?)
[Nexus 4 Original Android Development] vomer:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

Just an FYI - I was investigating into the msim wake lock and it seems like some ROMs have this less than others. So it looks like that wake lock could be ROM related as well.

A week in and R62 running solid at -100 UV across.

Sent from my Nexus 4
[Nexus 4 Original Android Development] schizophrenia:
i am on MiNCO v6 and the msm_hsic_host wakelock is no less than 1/3 of the update when I am on 3G data connection. FYI
[Nexus 4 Original Android Development] bmbanker:
I like your thoughts. In my opinion, the "best kernel" is a kernel that the user can customize if he/she wants to, but doesn't have to customize for good performance and battery life. R53 + power modes (with a widget) + undervolt capability + those HSIC patches if possible would be an awesome setup that would deliver both good performance and battery life.
[Nexus 4 Original Android Development] Hanny:
guess most of you guys are focusing on cores these days and... is it only me or just you guys didnt notice something?

this is not a request of gamma control or such, this is a possible-bug report about RGB color control

These days i have noticed that occasionally my screen's white is having some little yellow tint as seen on my screen in stock 255,255,255

as i usually have modified them to 235, 228, 240 for like a month

after confirming in franco's updater by pressing "return to stock values" and notice zero changes, i know that my values was back to 255,255,255 by itself.

I didnt find out the cause until just now i accidentally found it. It is because of the proximity sensor turning off the screen during a cellular phone call.

reproduction procedures:

1) tune color control in franco kernel updater (i half the values of green, so the screen is totally purple tint, for easily noticing difference)

2) make a phone call

3) during the phone call cover the proximity censor with your finger for a few seconds and take off

4) bam, color back to default 255,255,255

Could anyone please try these simple steps and see if the problem is on my side?

I guess some code about the color control has been changed in newest update 8.5 on Jan28 according to the changelogs which was intended to fix some issues in the Gnex and I am not sure whether it is the cause or not, as I cant recall when did i start experiencing this problem.

What I have done to try to fix it:

- clearing app data and reboot and try

- clear cache and dalvik, reflash kernel and try

- clear app data, clear cache and dalvik, back to r53 and try

- uninstall touchcontrol as it may have something to do with the screen, reboot and try

all are still having the same problem that covering the proximity sensor would reset the color control values to stock until reboot / manually applied again.

UPDATE: the manual values are also back when the screen is turned OFF and ON. but before you turn it off, the values are 255,255,255 for sure.

Thank you very much for your attention :)
[Nexus 4 Original Android Development] iammudd:
With frequent cell handovers, I think some ppl would envy your battery life. You had 3 hours of screen on using 72% battery. That extrapolates to 4 hours of screen on. Prior to each cell handover, your phone notices a drop in received power (with the current cell) and increases its own transmit power.
[Nexus 4 Original Android Development] icepuente:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

Just my 2 cents. Franco has always been known to release a kernel that works efficiently out of the box without modifying any settings of course unless the user is advanced enough to tweak some final settings. Adding a widget to add or subtract active cores breaks this philosophy. I believe in order to keep the same functionality, the cores should be handled to have two active cores at all times. Use a very high threshold or activate the other two cores based on GPU activity. Franco is definitely known for flash and go and should keep that going.
[Nexus 4 Original Android Development] drawde40599:
Agreed , tell the truth I forget 62 only using 2 cores until I come here :P
[Nexus 4 Original Android Development] cobyman7035:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

Thx I did notice this too it wasnt just my eyes playing tricks
[Nexus 4 Original Android Development] m0h1t:
Hey guys

I'm getting brilliant battery life on wifi but its pretty bad on 3G (#53). BBS shows very high msm_hsic_host wakelock when I use 3G.

My neighbour who also owns a Nexus 4 and had the same issue tried this http://xdaforums.com/showthread.php?t=2102986 and is now getting great battery life, just as good as that on wifi. He is also apparently not facing any data drops.

This is a genuine question so don't shoot me. I'm wondering how come franco's kernel still suffers from this issue? Does the msm hsic fix cause other side effects or is not compatible with our kernel?

PS - forgot to mention that he went from stock to cm 10.1. I am still using the stock rom.
[Nexus 4 Original Android Development] iammudd:
You're correct about franco's philosophy but this is the exception. It was franco who initially proposed a widget to toggle between 2 and 4 constant cores (even though the functionality -- without the widget -- is already in r62).

For my usage pattern, 2 cores are enough (and smoother for some ppl) but I can see gamers potentially wanting a 4-core toggle.
[Nexus 4 Original Android Development] richteralan:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

I propose quad core on default and toggles to dual cores.
[Nexus 4 Original Android Development] cobyman7035:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

We should have a poll to chords verses for course I meant to course verses 4 cores

Google Voice via my NeXus⁴ using XDA Premium
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

This reminds me of faux kernel with eco mode. You toggle that and you turn on// the 2 cores. That would be interesting to see on this kernel. I doubt Franco will do this but let's see
[Nexus 4 Original Android Development] elliot.newnham:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

I'm confused why this is a talking point guys? Faux kernel is not a quad core dual core. Neither is Franco. Why on earth would you have a toggle between the two modes?

There are elements in place for cores to have independent governors and frequencies. And for them to turn on automatically without the user even knowing.

The only point for r61/r62 is to get down to the basics and test performance & battery.
[Nexus 4 Original Android Development] cobyman7035:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

Ultimate goal is 5 hours of screen times using 3g

Google Voice via my NeXus⁴ using XDA Premium
[Nexus 4 Original Android Development] richteralan:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

I'm confused why its a talking point for you.

I never mentioned anything about faux kernel.

So what's the big deal?
[Nexus 4 Original Android Development] Prod1702:
This is will most likely be something Franco brings to his app. He had it on the Galaxy Nexus where you could pick only having 1 core or 2. I am sure he will bring some kind of option for his kernel app to let you pick how many cores you want. It is still early in the game. He has way more to bring i am sure.
[Nexus 4 Original Android Development] lightosx:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

By microstutters I was referring to pre-r61 when hotplugging was still enabled. Most people seem to agree that r61-r62 are by far the smoothest releases so far and it was assumed that this is because hotplugging was removed for these releases. But what I noticed on stock is that hotplugging doesn't seem to create these micro lags even when setting my min to 384 MHz.

I don't like the idea of always having 2-4 cores on when mpdecision can manage to just use 1 core (if I'm reading without touching the screen) and the turns the second core on when touching the screen. I guess the issue here is the toll on battery from enabling/disabling these cores, but for me it seems nearly the same. I will be doing more tests during the week with stock, r61 and r62 to see if there really is that much of a difference.
[Nexus 4 Original Android Development] cobyman7035:
does anyone know if 'fast usb' enabled works in your car cig lighter with usb plugin adapter? if so i assume it needs a 2amp one right? not the crappy 1Amp ones

too bad when it says AC charging(when plugged into computer usb) it won't detect the nexus4 as a device (maybe franco can fix this?) have both usb N4 device recognized enabled and fast charging at the same time
[Nexus 4 Original Android Development] ran495:
hi just a question, if i buy your app, and i use it to install franco kernel then use it to restore my previous kernel(which is stock), will the back up/ restore feature also restore the changes to the ramdisk? thanks.
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

I know. I'm just saying what that is. I never said that's what I want. Like you said, this is testing.
[Nexus 4 Original Android Development] 1234568:
I have been using this kernel for some time and can vouch for the drastically improved battery life. Thank you Franco! However, I started to notice some lag in general use. I returned to stock for 3 days and while it is far snappier the battery is terrible.

Ideally I want something in the middle. I imagine the best way to achieve this is to carry on with Franco's kernel and tweak some settings via his app. Can some kind person please give me guidance as to what settings to play about with. Most the governor control options are alien to me. :o

Thanks for any help. Also, please don't take this as a dig against Franco and his kernel, I just want to tweak things more to my custom preference.

Edit: Forgot to mention, I am on the latest stable release, r53.
[Nexus 4 Original Android Development] vomer:
Quad core (r61) performed worse than dual (r62) for me, so I am not sure of the value there? Is it needed for games? :confused:
[Nexus 4 Original Android Development] strikelight:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

On 53, simply change io scheduler from row to deadline and you'll be flying.
[Nexus 4 Original Android Development] immunityx:
Give r62-test a try
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

Probably. :p I think its a decent idea to test.
[Nexus 4 Original Android Development] cocchiararo:
faux does have a mode for using just 2 cores (eco mode ?)
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

That's what I said a page or two back. But I'm not sure if Franco will have something similar.
[Nexus 4 Original Android Development] noneabove:
Slightly different than r62, faux still hotplugs but never allows cores 3 and 4 to come online, franco just always has cores 1 and 2 online and uses i think it's called power states
[Nexus 4 Original Android Development] richteralan:
Good to hear.

I paid for 4 cores and I would like to use 4 cores by default. And a choice to scale down to 2 cores active, of course.:good:

---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------

quad performed better than dual core for me. And yes, there's no apps/games need 4 cores NOW, but I'm certain there will be in the future.

And also like I said in previous reply, I paid for 4 cores so I would like to have 4 cores online by default, plus the choice to have 2 cores active. I don't look at things from one side only.
[Nexus 4 Original Android Development] derlotse:
AW: [KERNEL][GPL][N4] franco.Kernel - r53

I am really curious how you achieve this accuracy of 5min in your measurements..

What is it btw, screen on time or stand-by time?

How many times did you run each of the test scenarios?

Tbh, I don't trust any of these numbers..

Even testing with screen on all time, it would take 6 hours till battery is empty.. And I have seen sky changing from clouded to sunny within minutes.. Wheater can eg affect signal strength significantly (clouds reflect mobile signal).. And lead easily to 15 min more or less time on battery.

Moreover, there are more things to influence battery consumption.. Not every day is the same..not every day you receive the same amount of spam mail, having effect on the time spent on active sync. Maybe you even use your phone, like a real person..texting, browse the web..

Okay, I don't want to offend anyone.

My point is more: even benchmarks, which run in apparently well defined environment and parameters scatter a lot from run to run, user to user.. Numbers can easily give an apparent accuracy that is just not true..

You want to give numbers,then provide also all information on how you ..measured.. them.

Back to topic:

I'm happy with r62. I personally believe i experience the smoothest kernel since r28 when I started using this kernel.

Quad core or dual core? I don't care as long as it saves battery and phone runs smooth.

On my desktop (core i7 2600, 4 physical -> 8 HT cores) in 99.5% of the time only one core is used..usually not on full load. Only when doing a lot of multitasking, 3 cores may be active: one for the main app, one for the virus scanner and one to handle all the flash commercials in the browser.. Unless I run heavy calculations I just don't use or need more than 2 (fast) cores.. Until now I don't see where my smartphone needs more than 2 cores. Games? Most games are pretty simple, not much of AI or unit moves to be calculated. Graphic is what needs most power.. And this should be done by the GPU, right?

However, this will probably change when more and more devices are quad+cores and developers have a reason to program multi CPU apps, because they can sell them to enough users..

Until then a widget to switch or just 2 cores..are both fine - for me.

Q: Does anybody know an app similar to taskmanager on windows, where I can record CPU load on each core? Would be interesting to see what app creates how much load on how many cores and if I just wrote a lot of bull**** about not needing 4 cores :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] ben_pyett:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

did you use the recommended interactive tuned settings on top of 61 (which I believe come as default on 62)? And cfq io scheduler?

sent from my HTC OneSV while I wait for an RMA on my Nexus
[Nexus 4 Original Android Development] iammudd:
+1

Yes, be open minded. Results are user- and time-dependent. Test new revs for yourself -- preferably a blind test. If there are undesirable results with a particular strategy then report the details. IF in the end, you don't notice a difference (in either performance or battery or anything else), what difference did it make how many cores were online? All you should want are results, not the implementation details.

For those who DID notice microstutters or better perf with only 2 cores, I WILL report again that for me, the microstutters coincide with a new core being brought online or when 1 of the 4 cpu's is at the lowest freq. So neither hotplug nor 100% quad is necessarily the complete solution.
[Nexus 4 Original Android Development] drawde40599:
61

Just retesting 61 after being on 62 basicly all week I'm about 6 hours in , and its so noticeably not as smooth or fast , I don't like it all all in comparison to 62 . ID rather have 2 cores if 4 can't perform . I have to OC other kernels to get the "Bang" 62 is giving me only other version that gives same feel is 47 , Franco I think u should relook at 47 IMO :)
[Nexus 4 Original Android Development] Scottyfer:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

You could easily get accurate numbers by setting the screen to never time out and turning on airplane mode. No signal or syncing issues, and as long as the phone isn't being used, its battery drain should be the same about 99.9% of the time.
[Nexus 4 Original Android Development] immunityx:
im sure 61 will be faster then 62 with the same interactive tweaks that was put into 62
[Nexus 4 Original Android Development] calanizzle:
I think that may be noticeable on heavy tasks, not light usage..
[Nexus 4 Original Android Development] -JFK-:
I'm using R62 and can activate the 4 core via SystemTuner app.

But not really usefull finally...

Edit, just make two Bench and can't get regular result.

The overall score is the same but look at the CPU Integer and 3D graphic, how can we explaine that ?

Antutu is not a reliable benchmark ?
[Nexus 4 Original Android Development] Godaemon:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

Hey guys I noticed in my download folder that I had 2 files snakecharmer.bin and lggamma.bin .erased them both is this a problem ? Thought that I haven't tried faux kernel a long time now maybe it was from then.but what about the lg gamma.bin? Any ideas ? Thanks
[Nexus 4 Original Android Development] iammudd:
Yes, snakecharmer is from faux -- which can be used to limit the N4 to dual-core.
[Nexus 4 Original Android Development] kioshi:
i still haven't decided whether 4 cores or 2 cores is better for this phone.

Running one last test for me on the phone w/ r62 no UV at all.

r62 UV'ed on various mV settings i can get easily reach 4 hours on WiFi + some H+ speeds using the phone heavy (if i dont download a new build of PA rom and flash, etc.)

Lately I've been seeing my screen dim slowly and turn off but i can hear the noise when using the volume rocker. Have to hit power button to turn screen off and on again.

Trying no UV on r62 today.
[Nexus 4 Original Android Development] starscream92:
I love your kernel, but it'd be great if there's a version that allows undervolting with auto-hotplugging enabled. Device temperature is a pet peeve of mine, and having 4 cores all the time puts a lot of heat onto the phone. R62 is great but I want to be able to use the most of my device (quad-core chip).
[Nexus 4 Original Android Development] St4hli:
AW: [KERNEL][GPL][N4] franco.Kernel - r53

Hey guys, someone might have asked this already, but I'm not sure about the exact behavior of francos kernel updater app.

When I just install the app without flashing francos kernel, the app still adjusts some things like haptic feedback, or am I wrong?

What are these settings? I'm not really sure what happens if I update cyanogenmod nightlies..

Thanks for your help!
[Nexus 4 Original Android Development] joshnichols189:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

What? It will adjust settings that can be adjusted in other kernels.
[Nexus 4 Original Android Development] drawde40599:
Not exactly what u mean I no , but u can make 62 run on all 4 cores and its noticeably slower
[Nexus 4 Original Android Development] St4hli:
AW: [KERNEL][GPL][N4] franco.Kernel - r53

Thanks, now I think I understand. So if I would uninstall francos app and then update cyanogen nightlies, haptic feedback would be back to the normal 70? :S
[Nexus 4 Original Android Development] WastedJoker:
does this allow me to set the overall vibration level for notifications rather than just haptic feedback?
[Nexus 4 Original Android Development] AshtonTS:
Re: [KERNEL][GPL][N4] franco.Kernel - r53

You can just change it back to the normal 70 in Franco's app....

Sent from my Nexus 4