yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Android001:
r18 working nicely over here. Battery life is outstanding and overall performance is very fast.

There is a slight choppiness to the scrolling in most apps though, agreed.

MiNCO = ? + Franco's kernel?

Edit -- Hah, flashed and found out. Very nice ROM.
[Nexus 4 Original Android Development] Ballastatuz:
Yeah I can also report choppiness
[Nexus 4 Original Android Development] SubwayJrd:
As I understand it hispeed_freq is what the kernel will jump a single (or the online?) CPU core(s) to when there is a certain load on the CPU. It allows the governor to skip the transition states between where it was idling the CPU, and go straight for some power.
[Nexus 4 Original Android Development] Martin_Ro:
Love your new hotplug driver.

Have had a look into your source.

Maybe some suggestions for further optimizations:

What about enable/disable count of cpu's based on the difference between currentload and the given levels:

Example:

One CPU is running, and the Load raises to 80%, Secondlevel is 40%. Normaly you now would enable one CPU, wait for next check and, if needed enable an additional cpu. Maybe in such a situation it would be better to directly enable 2 CPU's in time, wouldn't it ?

Parameterwise I would suggest:

High_Load (Current firstload) : 90 (Still enable all cpu's because of very high load)

Raise_Load (Current secondload) : 30

Raise_Multi(Multiplicator for count of cpu prediction on enabling cpu's): 20

Drop_Load(Current thirdload) : 60

Drop_Multi(Multiplicator for count of cpu prediction on disabling cpu's) : 20

Normally I'm a vb.net programmer, but maybe it would work like that for example:

static void second_level_work_check(unsigned long temp_diff, unsigned long now)
{
unsigned int cpu = nr_cpu_ids;
if ((now - stats.time_stamp) >= temp_diff)
{
[COLOR="Blue"] unsigned int cpu_up_count = (load - firstload) / Raise_Multi;
if (cpu_up_count+stats.online_cpus) > stats.total_cpus)
{
cpu_up_count=stats.total_cpus - stats.online_cpus;
}
unsingned int enabled_cpus = 0;[/COLOR]
for_each_possible_cpu(cpu)
{
if (cpu)
{
if (!cpu_online(cpu))
{
cpu_up(cpu);
pr_info("Hotplug: cpu%d is up\n", cpu);
[COLOR="Blue"] enabled_cpus=enabled_cpus + 1;
if (enabled_cpus >= cpu_up_count)
{
break;
}
[/COLOR] }
}
}

stats.time_stamp = now;
}
}

I would love to test it myself, but I haven't a linux or a mac machine and there is currently no solution for windows to compile it myself :(

Maybe someday I will setup a vm with linux to compile that kind of test myself :good:
[Nexus 4 Original Android Development] Luigiesin:
Dude.. Just clean Data on Franco's app.. That will hard reset the app including the colors and then you can set it up anyway you want ;)

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.1 (Mar07)

Kernel: Franco r120

T-Mobile
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks for your suggestion but that doesn't really solve the problem we're experiencing. In fact, it doesn't have anything to do with it. Please read about it again.

Cheers
[Nexus 4 Original Android Development] leets4uc3:
I'm using 90/35/65 (H/M/L) and it is super snappy. I don't really notice the micro lag that miasmic is reporting. I used to see before I switched to these settings.

Edit. Bumped up to 90/40/70.
[Nexus 4 Original Android Development] noonecanhide:
Hi,

I have the following set-on-boot settings at the FKU app:

- governor: interactive, max freq: 1188 MHz

- -50mV UV for all freqs (shouldn't be a problem, had 125-150; too)

- gamma profile, the recommended one from obsanity

I do not turn off the screen after the reboot, it happens after a few seconds when the screen goes off (timeout 30sec) before entering PIN / unlock code.

Thanks for your effort, i really appreciate the perfect support :)
[Nexus 4 Original Android Development] fozzie:
I don't see this at all (when opening Google Chrome); running stock settings.
[Nexus 4 Original Android Development] Mercado_Negro:
Could you please read my post here and share your thoughts? We're probably experiencing the same issue and Franco already explained it a few pages back.

http://xdaforums.com/showpost.php?p=40090647&postcount=23406

Cheers
[Nexus 4 Original Android Development] noonecanhide:
Shame on me, didn't see that post from franco...

http://xdaforums.com/showthread.php?p=40052401

That's the issue i reported, but as i described before i don't turn the phone off manually. I don't know if that is possible within an init script tp prevent the screen turning off while gamma settings are applied ?
[Nexus 4 Original Android Development] franciscofranco:
Doesnt matter if you turn it off manually, as long as it turns off while loading the gamma values it goes kaboom. I dont know how to solve it for now, need to think about a solution.
[Nexus 4 Original Android Development] franciscofranco:
That small piece of code would not work by the way, but I understood the logic. Why would we want to online 2 cores with just medium load? Seems a bit overkill to me. Explain!
[Nexus 4 Original Android Development] PunkOz:
I'm sure this has been asked many times but I can't find the questio/answer.

Are you planning to make a dualboot version of your kernel? like Siyah kernel has dualboot o: Siyah kernel's app had so many options but I'm not sure if it was due to Sgs2's sources being broken. This kernel is simply amazing, I love Nexus 4 cause it just works! and so smooth but will it affect the perfomance/battery if you add tweaks like "scrolling cache" or "entropy fix, entropy seeder, entropy code aurora" "disable gentle fair sleepers" "gpu touch boost" "cpu touch boost" or it's useless on nexus 4and they use that on S2 cause it's broken?

Thanks for your amazing work btw!

And NO, I'm not saying that Siyah kernel is better in any way, I'm just asking if those tweaks would work on us, and maybe if people see more "options" more people will find the app useful enough to buy it :D more $ <3 *I bought already*

Edit: I remember it also had touch sensivity control I don't know if that's even useful on nexus 4 but some people like the screen really sensible.
[Nexus 4 Original Android Development] visceralpsyche:
I've had this happen many times as well. The 'fix' for me is that on boot up when the lock screen appears, I simply unlock the device and let the boot sequence complete before turning the screen off. It's actually kind of cool to watch the colors change one by one as the kernel updater app configures the color preset :) Hope this helps!

Cheers,

Paul :)
[Nexus 4 Original Android Development] visceralpsyche:
I don't normally post battery stats etc, but I thought this was interesting. Here's a screenshot of my phone.

First part with faster battery drain is due to the data SIM I'm using here in Tokyo, that won't show the modem signal properly even though it has good reception.

Second almost flat section is once I got home and put it in airplane mode with wifi on. All this was build 119. CM 20130405.

The third and final part was after updating to build 120 and CM 20130408. After doing that I rebooted and went to sleep. Woke up to essentially zero battery drain overnight :D

All the Franco kernel settings aside from color were default values.

Just thought it was a nice clean delineation of how mobile signal and kernel changes can affect battery life.

Cheers!

Paul :)
[Nexus 4 Original Android Development] franciscofranco:
dual boot -> no

scrolling cache -> what? buzzword - Android by itself does all the needed caching

entropy -> another buzzword. Android doesn't use /dev/urandom as per indication of a Google employee in some googlegroup thread

gpu touch boost -> why on earth do I want to boost GPU frequency on touch? no logic

cpu touch boost -> thats already handled by interactive

:good:
[Nexus 4 Original Android Development] GFXi0N:
Many words I didn't heard of since I left the SGS2 forum..... :)

I have to agree: if you leave the phone, it doesn't consume battery almost.... But on heavy use for 1 hour, it will drain like crazy..... Real racing 3,frontline commando, etc.....

Nice kernel.....
[Nexus 4 Original Android Development] Martin_Ro:
Yeah, like I told, I'm "only" a vb.net programmer and not into C.

But if you got what I mean, it has done all it should :silly:

To your question:

Not on medium load, but on fast raising load. My values has only been an example.

The logic behind that should be extensive raise in load should lead to a faster enabling of cpu's.

So if the load raises by 20-39% it should only online one additional core, if it raises by 40-59% it should directly online 2 additional cores (if so many left offlined).

Also on the oposite direction: if load falls by 20-39% offline one core, if it falls 40-59% offline 2 cores directly.

I would think that could make the things more dynamic, don't you think ?

The values (20-39%, 40-59%) are only examples as I don't have a real feeling for the right numbers...
[Nexus 4 Original Android Development] PunkOz:
Ok that should answer all my questions, thanks a lot for taking the time to answer :)
[Nexus 4 Original Android Development] ergalle2:
For people using "old" versions:

What version is more smooth, r111 or M1?

Thanks.
[Nexus 4 Original Android Development] rocklee80:
R111 ;)
[Nexus 4 Original Android Development] rxmxsh:
Why not try it for yourself? You have nothing to lose.
[Nexus 4 Original Android Development] ergalle2:
Thanks.
[Nexus 4 Original Android Development] blueren:
I am running on r120 at the moment, CM10.1 and all stock franco settings. My touch screen seems to go unresponsive when I get an incoming call. Doesn't happen always, but happens once in awhile. Screen lights up but unable to slide to answer or reject unless I turn off the display and turn it back on again. Is this a known issue? Is it related to the kernel at all?

I'm not very certain, but I've faced this with the previous couple of releases as well.

(PS: I don't have any touch to wake thingies installed)
[Nexus 4 Original Android Development] Utini:
quick question: What was the default govener on r111 ? I played around with the voltages and the stress test app changed the govener :/
[Nexus 4 Original Android Development] nachordez:
Interactive
[Nexus 4 Original Android Development] QUIETLYloud:
pretty certain it's interactive
[Nexus 4 Original Android Development] Utini:
Alright, well then:

Stock 4.2.2 with r111 and 1Volt at 1512MHz (that should be -150mV). Smooth and awesome :)
[Nexus 4 Original Android Development] nachordez:
Good!

Check your camera. For me -100mv was freezing my camera. -75 was OK. But perhaps your CPU is stable with -150!

Nexus 4, stock kernel, last Franco.kernel nightly
[Nexus 4 Original Android Development] :
It happened to me on r120 too an hour ago, I heard the ringtone and when I go to answer the screen doesn't respond had to turn it off and back on, I have no idea what causes it, its random, it was perfectly fine yesterday

I'll also add it happened while I was using Harsh kernel at random times
[Nexus 4 Original Android Development] BrandoHD:
What ROM and what MODs, if any, are you using?

@blueren are you using any MODs together with CM10?
[Nexus 4 Original Android Development] blueren:
No. No mods whatsoever. Stock CM + franco + no uv no nothing
[Nexus 4 Original Android Development] :
I'm on PA latest and no mods, its not ROM specific either its happened on different ROMS and kernel, I'm never in a position to get a logcat when it happens
[Nexus 4 Original Android Development] Utini:
Nope, no camera lags :)
[Nexus 4 Original Android Development] mefistos:
What's best IO Scheduler? Deadline or row?
[Nexus 4 Original Android Development] rgawenda:
Neither TouchControl/PGM?
[Nexus 4 Original Android Development] steviewevie:
It's not lags you're looking for in the camera, it's photo artefacts (e.g. random corruption).

Sent from my Nexus 4
[Nexus 4 Original Android Development] Cantacid:
I dont think this has anything to do with the kernel! I remembr i faced this a long time back when i had just got the phone! Im not sure if i was on cm10.1 back then or nof but the kernel was definately stock!
[Nexus 4 Original Android Development] nachordez:
Great!

Nexus 4, stock kernel, last Franco.kernel nightly
[Nexus 4 Original Android Development] CamoGeko:
Hahah, it was just enlightening.

Before I read that post I kinda forgot that it happens to devs as well lol
[Nexus 4 Original Android Development] renegadedj:
I hope this gets answered too, as for my old Vibrant I went between CFQ and SIO, but with the Nexus 4, I'm not so sure what is best?
[Nexus 4 Original Android Development] Karlo666:
Just had my first screen freeze whit r120 undervolted and gov. conservative.Phone was on charger all day until i came home then this happend.

Forgot to logcat the thing.
[Nexus 4 Original Android Development] Utini:
Oh okay, I will have to check that later :)
[Nexus 4 Original Android Development] mitchdickson:
Just stick with default.

Sent from my iPad 4
[Nexus 4 Original Android Development] franciscofranco:
If I set X as default which do you think I recommend at this point?
[Nexus 4 Original Android Development] CamoGeko:
ROW = smooth UI

SIO = smooth UI and gaming performance

CFQ = all round decent performance

Deadline = best gaming, worst battery
[Nexus 4 Original Android Development] Shano56:
Well, clearly Y in this case.
[Nexus 4 Original Android Development] 75markus:
if you were a girl, i would say .... Y :p

but since you´re a guy, i´ll take your word for X ;)
[Nexus 4 Original Android Development] franciscofranco:
Stop undervolting :cyclops:
[Nexus 4 Original Android Development] sirxdroid:
The default the kernel comes with. Why would Francisco pick a default that's not optimal for the majority of users? Depending on how you use the phone you might prefer a different one, but there's no point changing it if it's not broken.
[Nexus 4 Original Android Development] renegadedj:
Is there a way to reset undervolting back to voltages default?

Also, regarding the I/O scheduler, I had changed it a few times and so I forgot what your default was in the first place anyways. Haha

And to geko95gek: There is no SIO on my I/O settings, just deadline, row, cfq, and ?noop? Thank you though really for the the quick reply on the descriptions of each. :)
[Nexus 4 Original Android Development] michael_ta315:
yes, uncheck the set on boot option :silly:
[Nexus 4 Original Android Development] sirxdroid:
row, 512 read ahead
[Nexus 4 Original Android Development] CamoGeko:
Sorry, had a HTC One X flashback lol

Noop = best for battery

ROW = SIO + Deadline put together
[Nexus 4 Original Android Development] renegadedj:
Why do I forget the little things. Bahahahaha. Thanks! I'll do that for all settings to get the defaults. A duh! D'oh! :p
[Nexus 4 Original Android Development] sirxdroid:
Or you can delete the app data if you don't care for any of the settings and start fresh. This is where saved color profiles come in handy as you can easily set one after deleting app data and rebooting.
[Nexus 4 Original Android Development] renegadedj:
Damn I feel like a noob. Hahahaha Kinda feels like deleting the App Data would work better on getting undervolting back to defaults, just from how the app is designed and worded. I'll try both ways to be sure, haha, as I don't know the values of undervolting when it's at default anyways. haw haw haw

Thanks again!
[Nexus 4 Original Android Development] ChaosChris:
Im quite new to the n4 came from nexus s and i feel that the n4 goes really warm on the backside. When i am on Bad h+ signal and browse xda through tapatalk for an hour it had 50-55°C is that normal? Also idle temp on h+ is about 30-35°C on wifi 20-27°C. Currently on r120 an lastest pa and -100mV UV i have a fast binned CPU. Working for a week without problems. Thanks for your answers :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] franciscofranco:
I don't want to ruin your party, but thats... wrong. IO schedulers just manage inputs and output requests, they don't affect the battery life at all unless its a really dumb algorithm that ****s up, but thats not gonna happen.

What changes is IO performance. Most is placebo though, when moving around in the Android OS most content is cached and there won't be much IO.
[Nexus 4 Original Android Development] franciscofranco:
Well... thats a bit high if you're just browsing around. Although it depends on a lot of things, specially the temperature on where you are situated. Just use your device, don't be worried.
[Nexus 4 Original Android Development] ChaosChris:
Alright thank you, yes was in a train and it was very warm there :D

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] scream4cheese:
I think everyone needs to know this. The new Google Play store v4.0 just came out today.

Link for info and download link:

http://androidcommunity.com/google-play-store-version-4-0-available-now-download-20130409/
[Nexus 4 Original Android Development] CamoGeko:
I know mate, but in my personal experience the "placebo" is really noticeable.

I've tried all the schedulers you can think of on many android devices, and have always noticed a difference in smoothness.

Not trying to start an argument mate, just speaking from experience.
[Nexus 4 Original Android Development] Ed 115:
updated to the newest paid version of app, cant find user gamma presets anywhere...do i need to wipe app data? will i lose my kernel backups? thanks for any help
[Nexus 4 Original Android Development] ceejay83:
It's under the load color profile menu
[Nexus 4 Original Android Development] sirxdroid:
Anyone having performance problems with VOIP calls and the screen off? Not sure whether it's a CPU or wifi issue (wifi is set to never sleep). Calls are fine if I keep the screen on but they become choppy with the screen off (they don't get disconnected, just choppy).
[Nexus 4 Original Android Development] franciscofranco:
r121:

* Severe improvements and bug fixing on the hotplug driver. Noticeable improvement in interactivity with the UI

For more details check my github commits, I don't wanna get too technical in here on what I changed.
[Nexus 4 Original Android Development] ÜBER™:
Does this include the load levels or is this purely hot plug code?

Sent from my Nexus 7
[Nexus 4 Original Android Development] franciscofranco:
Both, but those load levels were already included in r120: 90/25/50.
[Nexus 4 Original Android Development] Shano56:
Testing r121 now! Will report findings :) thanks!
[Nexus 4 Original Android Development] Audioboxer:
Thanks boss!
[Nexus 4 Original Android Development] Gugus38:
Hehehe thanks franco, great work! :highfive:
[Nexus 4 Original Android Development] Ed 115:
UOTE=ceejay83;40112855]It's under the load color profile menu[/QUOTE]

I'm an idiot, thanks man
[Nexus 4 Original Android Development] sirxdroid:
Very nice. r121 (with its default settings) finally feels as smooth as the stock kernel or Trinity TF117 (with all 4 cores online). So far I've been able to tell the difference between the stock and Franco kernels in blind tests based on simple stock launcher smoothness, but it's very hard if not impossible now with r121. No scientific tests which I couldn't care less for, it's my personal feel that matters to me (and it should not matter to others :) )

Nice job Francisco!
[Nexus 4 Original Android Development] ÜBER™:
I'd post my battery life but according Brian at anandtech its not impressive so I'll refrain from posting images.

1day 5 hours

5.5hours screen time.

With flashing the updated kernels and my ROM.

Sent from my Nexus 4
[Nexus 4 Original Android Development] jlear3:
+1

Just came from t117 and it's just as fast but will still enjoy the perks of hotplugging :good:
[Nexus 4 Original Android Development] italia0101:
Is anyone running with 4 active cores all the time ?

Does it kill the batt a lot ?
[Nexus 4 Original Android Development] ctfrommn:
I do....it drains a bit quicker if you leave it at the default 384/1512, but lowering it to 1026 negates the drain and then some. Plus the system is much more responsive.
[Nexus 4 Original Android Development] JoeBananas_:
No
[Nexus 4 Original Android Development] Tortel:
Same for me. Thanks again.

PS : since r120 I'm able to run stable at 25 mV lower than before (now at 750mV at 384MHZ).
[Nexus 4 Original Android Development] CamoGeko:
I'll need to try EOS at some point on my Nexus devices. :D
[Nexus 4 Original Android Development] italia0101:
Cool thanks for answering .
[Nexus 4 Original Android Development] ÜBER™:
Rock solid ROM with useful customization. What more could you ask for? :)
[Nexus 4 Original Android Development] sirxdroid:
I'm surprised EOS is not more popular on the N4. A hidden gem, big fan of it, I run it both on the N4 and GNex.
[Nexus 4 Original Android Development] andyli1985:
Well, according to Brian at anandtec, it's really not that impressive. :silly:
[Nexus 4 Original Android Development] BrandoHD:
I think I see what you did there :)

Sent from neXus 4 using Tapatalk 2
[Nexus 4 Original Android Development] ÜBER™:
And before the guy writes an entire paragraph defending his point... its a joke. :silly:
[Nexus 4 Original Android Development] sirxdroid:
That's the strategy that Trinity TF117 uses by default: all 4 cores online, 384/1026, ondemand. You can also reduce the number of cores if you want to. I tried 2 online and it felt as smooth. Not sure though which is worse for the battery: switching the other 2 cores between offline/online possibly very often, or keeping them online all the time but at 384 when "idle".
[Nexus 4 Original Android Development] ctfrommn:
Thats where I got it from. I would rather have all online to fully negate hotplugging. I cant imagine using 2 or 3 as a min would make an impact on battery. I thought it was a ludicrous idea when I was told about it, but actually using that setup revealed its true genius. I wish all kernels had that option to be honest.
[Nexus 4 Original Android Development] CamoGeko:
Haha, I can see myself running it on both my N4 and N7 soon lol

Sent from my Nexus 4
[Nexus 4 Original Android Development] sirxdroid:
At least it's possible to do on Franco with all 4 cores online right now, finer control in the future.
[Nexus 4 Original Android Development] ctfrommn:
Agree....this is also an awesome kernel. Both great devs.
[Nexus 4 Original Android Development] Shano56:
Going back to android 2.2 froyo

Dis kernul suk
[Nexus 4 Original Android Development] eep2378:
The only thing to ask for is for goo.im to improve their glacial download pace :p:D

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] gparmar76:
Huh? How can the system be MORE responsive at a lower clock speed??
[Nexus 4 Original Android Development] starscream92:
Context, my friend. He was talking about having all 4 cores online all the time but underclocked.
[Nexus 4 Original Android Development] ctfrommn:
It is more responsive because all 4 cores are online all the time. In very few circumstances (gaming, benchmarking, etc...) are all 4 cores onlined. The lower clock speed keeps the heat down and battery consumption lower. You certainly could go 384/1512 all 4 on, but I saw no real gain and much more heat/battery drain.
[Nexus 4 Original Android Development] Dody83:
Hello guys! I'm on Makocolors ROM and Franco Kernel #121...I undervolt to -150 mV and got continuos reboot...is it normal?

P.S.: my N4 has Fast CPU...
[Nexus 4 Original Android Development] ÜBER™:
Dont undervolt that much then... no one but yourself should take responsibility for it rebooting.
[Nexus 4 Original Android Development] Gugus38:
Yes it is, reduce your undervolt!
[Nexus 4 Original Android Development] ceejay83:
Is this a serious question? I think we're being trolled
[Nexus 4 Original Android Development] ctfrommn:
Cmon guys, he's a brand new user. Cut him a little slack. It takes just as long to help as it does to reply with a snarky comment :)
[Nexus 4 Original Android Development] italia0101:
This normal for CPU ?