yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] franciscofranco:
I feel the contrary!

No its not easier... I would not have fun at all if I went that route. As I said, I'm fine with this while having tons of fun.

When you short swipe it every pixel difference from the original position calls the function so imagine, if you move 10 pixels from the original position the driver sends 10 requests to the cpufreq layer to boost the cur freq to 1GHz, so even if cpufreq decides to decrease the frequency in between if ramps it again to 1GHz and thats enough time for the apps to pick up the frequency differences. We're talking in milliseconds, its really really fast.
[Nexus 4 Original Android Development] Net.silb:
Got it. Out of curiosity, what are the advantages of implementing your way and why is it funner? :)

How long is the cpu ramping on touch boost for?

And is there a way to test this properly and know for sure?
[Nexus 4 Original Android Development] yokuyuki:
Shouldn't it be more like this?

if (x_pos > init_x + 100 || x_pos < init_x - 100 || y_pos > init_y + 100 || y_pos < init_y - 100)
online cpu1
ramp cpu0 to 702MHz
else if num_online_cpus() < 2
ramp cpu0 to 1026MHz

If there is a swipe in any direction, online cpu1 if not already on and ramp cpu0. Otherwise, if only 1 cpu is online, then ramp cpu0 for touch boost.
[Nexus 4 Original Android Development] franciscofranco:
1 - Because I like to play with the Kernel and I learn a lot along the way.

2 - It ramps then it stays ramped for a sample time (min_sample_time from Interactive)

3 - Yes, Kernel debugging using prints everywhere.
[Nexus 4 Original Android Development] calanizzle:
Back to flash franco m2 + cm 10.1 rc, will revert with comments!

I've been using old versions since I can get easily 4hs SOT, but I'll try the new features!
[Nexus 4 Original Android Development] franciscofranco:
Yeah that will shorten code up, thanks!
[Nexus 4 Original Android Development] Net.silb:
So you're saying that even on a single touch (no swipe at all) the cpu is ramped up to 1026 MHz but the app can't detect it?

Can you test this as you said in answer 3?
[Nexus 4 Original Android Development] pikachukaki:
While reading some random article on the web about gpus i read this...

"Nvidia realized that more cores running at a slower speed are more efficient for parallel workloads than fewer cores running at twice the frequency."

maybe this could give you an thought!!i dont know just saying!!Keep up!! :fingers-crossed:
[Nexus 4 Original Android Development] Net.silb:
Yea, but we bump the cpu0 frequency to 1026 MHz because it handles the UI thread which can only run on one core. When there are two cores running, we only need to bump cpu0 to 702 MHz because there are less threads that need to be run on that core but the UI thread is still gonna run only on that core. All this ramping is done in response to touch because that is when the UI thread is most active and needs to be processed fast for a buttery smooth user experience.
[Nexus 4 Original Android Development] pikachukaki:
Thats how android works or kernel??
[Nexus 4 Original Android Development] Net.silb:
Android.
[Nexus 4 Original Android Development] pikachukaki:
And its unchangeable??
[Nexus 4 Original Android Development] Net.silb:
Unless you have the time and knowledge to completely overhaul the entire Android UI management than yes.
[Nexus 4 Original Android Development] franciscofranco:
<6>[ 91.682983] CURR_DATA 0: 1 <-- touch detected

<6>[ 91.691772] CUR_FREQ: 1026MHz

<6>[ 91.761688] CURR_DATA 0: 0 <-- touch released

If there are parallel workloads. If there isn't, that point is moot.
[Nexus 4 Original Android Development] pikachukaki:
So ppl paying 600-700euros for phones that can use properly their 4+cores??thats nice!!

Just trying to give some help franco... ;)
[Nexus 4 Original Android Development] Net.silb:
Awesome!

I guess the next step is to make the parameters user configurable, or do you still have any ideas for more improvements?
[Nexus 4 Original Android Development] franciscofranco:
Ahh now I'm very happy, no more stupid online/offline during swipes, had to re-work some things.
[Nexus 4 Original Android Development] Net.silb:
No, just the UI thread, other threads can run on other cores...

---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------

Please elaborate...
[Nexus 4 Original Android Development] stratosk:
Sorry for interference.

If I understand correctly, do you need to catch a single touch event?

If you are in touch_work_func you have a touch event. I suppose there is no need to check anything else (except if I'm missing something).
[Nexus 4 Original Android Development] Net.silb:
I think you are on to something... :D
[Nexus 4 Original Android Development] franciscofranco:
Thing is marketing gives people the wrong impression about having multi-core cpus. More cores are only useful to handle more than 1 thread in real-time. Other than that its kind of useless. We benefit from multi-cores because Android is now properly done and makes use of it. I blame poor marketing because people think a 12 core CPU running at 1.0GHz will be faster than a 2 core CPU running at 2.0GHz CPU, which is right and also false at the same time and it depends on the OS and what is running at certain point in time. Using 12 threads the system will be faster with the 12 core CPU, but while using 2 threads the 2 core CPU will be faster because of the increased frequency. There are a lot of other variables than this like L2 cache speed or the number of operations per second and the Kernel software implementation to handle everything. Reading Anandtech technical articles we can learn a lot about this low level stuff. Yes, I'm giving props to Brian, pun is intended :)

Yes I'm almost ready for pimping up more sysfs entries for proper release. I'm kinda excited to be honest :)
[Nexus 4 Original Android Development] Net.silb:
Thanks! I wish I could press the thanks button but XDA doesn't let me thank you more than 8 times a day! :p
[Nexus 4 Original Android Development] pikachukaki:
I wasn't expecting nexus to run like my 4cores amd cpu but i thougth that in 2013 OS's could really take advandage of the hardware at least 70-80% anyway...i can't say im not happy after a year with a single core 1ghz phone...but as i say before im having some small hangs on latest 666!!
[Nexus 4 Original Android Development] kecinzer:
I just compile latest version of kernel, flashed and now my LED is green (plugged).

Can I turn this feature off somehow?
[Nexus 4 Original Android Development] nexusmaniac:
Look at 5-10 pages back and there is a flashable .zip to disable the light :)

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] Net.silb:
[MENTION=3292224]franciscofranco[/MENTION]

What do you think of this?

Sounds good to me!
[Nexus 4 Original Android Development] elzafir:
Franco, I can provide Indonesian translation if you want. Bahasa Indonesia is not listed on your Crowdin page.

Sent from my Nexus 4 pimped with ParanoidAndroid and Franco.kernel
[Nexus 4 Original Android Development] hotnikkelz:
Ok I started from scratch. Flashed rassaber and my gapps. Problem persists. Trinity 125 doesn't play nice with your app. Back to your kernel as I don't get that problem with any other kernel. I think you rigged it hehe *joke*
[Nexus 4 Original Android Development] PetritH:
Here
[Nexus 4 Original Android Development] fozzie:
I must be mis-reading this. You're trying to use Franco's app with a different kernel? Surely not?
[Nexus 4 Original Android Development] nexusmaniac:
It's because Franco's was designed specifically for the Franco kernel so other kernels won't be compatible with it :)

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] franciscofranco:
Thats what I do, I capture the ABS_PRESS state in the struct.

Just added it.
[Nexus 4 Original Android Development] hotnikkelz:
Yeah. Why not ;) surely j can test others and it usually works. Not sure what's up with trinity 125
[Nexus 4 Original Android Development] fozzie:
Errrrm, because Franco's app has only been designed for Franco's kernel. The hint's in the name!

Any interoperability with other kernels is purely coincidental & may work or break at any time and without notice.
[Nexus 4 Original Android Development] Net.silb:
Can you please say what changes you did?

Really curious!
[Nexus 4 Original Android Development] jaggyjags:
I just wanted to say thanks, Franco. Never imagine to get this out of my phone from a normal day usage... r134 rocks!
[Nexus 4 Original Android Development] kecinzer:
Thanks, but LED is still light :)
[Nexus 4 Original Android Development] elzafir:
Nice. I'll get cracking this weekend.

This is so cool, I can finally contribute.

Sent from my Nexus 4 pimped with ParanoidAndroid and Franco.kernel
[Nexus 4 Original Android Development] CrimsonSmear:
To disable ALL System LEDs:

echo "none" > /sys/class/leds/blue/trigger

echo "none" > /sys/class/leds/green/trigger

echo "none" > /sys/class/leds/red/trigger

The following are the accepted values for LED trigger (functionality not tested/guaranteed):

none, mmc0, heartbeat, thermal, usb-online, pm8921-dc-online, batterty-charging-or-full, battery-charging, battery-full, battery-charging-blink-full-solid, wireless-online, rfkill0

For anybody that may be interesed, I have updated my init.d script to include System LED Control.

init.d script for franco.Kernel contains:

- Sound Control

- System LED Control

- Hotplug Driver Control

- Accuracy Filter Control

- Color/Gamma Control (including common requested profiles)

- other misc. adjustments
[Nexus 4 Original Android Development] PetritH:
Deleted, sorry.
[Nexus 4 Original Android Development] Net.silb:
I think he means, why do you need to even do that?

If you are already in the touch_work_func, it means the screen is being touched, you don't need to do anymore checks, just ramp up cpu0!

This way you can boost cpu0 even on a touch that has no change in x or y!
[Nexus 4 Original Android Development] espionage724:
Just for an example, I'm pretty sure (this was the case back on the Nexus 7 anyway) franco.Kernel and Trinity use different sys calls (right term?) to adjust fsync
[Nexus 4 Original Android Development] franciscofranco:
I already shown you that the boost is happening on a single touch.
[Nexus 4 Original Android Development] Net.silb:
Oh ya... forgot... :silly:
[Nexus 4 Original Android Development] Newlin:
You can load color profile presets from Franco's app and it is under there. Otherwise they are as follows:

Red: 255

Green: 255

Blue: 255

Grays: 32 32 32

Mids: 68 68 68

Blacks: 118 118 118

Whites: 64 64 64

Contrast: 25

Brightness: 4

Saturation: 66
[Nexus 4 Original Android Development] PetritH:
Thanks a lot dude (out of thanks sorry)
[Nexus 4 Original Android Development] franciscofranco:
So I'm about to push another r666 (hopefully the last one). Besides more improvements on the touch_boost routines tied to the touch driver and the Hotplug driver, now the LED trigger implementation will only display the RED color when the device reaches the user defined temp threshold - 5 and gets brighter on the way to 90ºC. It was also reading from the wrong sensor, so now it won't display the RED color as often as before, not even close.

Grab it, test it and have fun. This one plus customizable settings should be the next nightly.
[Nexus 4 Original Android Development] Net.silb:
I figured you weren't posting much because you were busy coding... :p

Thanks again!

Do you mind posting the diff?

Or at least say what the changes are to the hotplug and touch drivers?
[Nexus 4 Original Android Development] kyokeun1234:
now the led light will be much more helpful :) thank you franco!
[Nexus 4 Original Android Development] thebryceee:
Wow. Scrolling through all that code on Tapatalk was smooth as f.ku!
[Nexus 4 Original Android Development] asm19:
nice work franco, testing time! :D
[Nexus 4 Original Android Development] schmitzekater:
Totally agree. This is beyond awesomeness. This new kernel + rassaber is completely insane.

Smoother than butter in the sun and fluid as hell.

Oh and battery... :D :D :D :D :D

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Net.silb:
Looks like a new level of smoothness in the past two r666, really nice job Franco! :)

I think the way the hotplug and touch boost drivers currently work is the best way yet, and from now on only small changes and optimizations to the code and parameters need to be done!

Really congrats! :D

---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------

What's RasSaber?
[Nexus 4 Original Android Development] Savant:
Works fine with other kernels and I don't have problems using it..
[Nexus 4 Original Android Development] Net.silb:
Damn double post!
[Nexus 4 Original Android Development] 75markus:
here´s the zip for you girls & guys
[Nexus 4 Original Android Development] schmitzekater:
ROM: http://fitsnugly.euroskank.com/?rom=rasbeanjelly&device=mako-rassaber

Rasbeanjelly on speed. :sly:

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] spaceman860:
[MENTION=470754]Franco[/MENTION] so it won't show a green led when battery is fully charged? :(

Sent from my Nexus 4
[Nexus 4 Original Android Development] nexusmaniac:
I'm using the brand new r666 v5 and the green light still shows when fully charged :)

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] Slymobi:
Lol didn't even notice until I got to your post.

Sooooooooooo Smoooooooooth. ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] chosen14u:
Anyone who has been on the last couple of v666 in your opinion how has the battery been compared to 134? and please don't give me "go try it for your self" I just want a basic opinion better/worse/no-difference etc.
[Nexus 4 Original Android Development] stratosk:
I think the correct sensor_id = 7 (as in the original code). According to debug messages the temperature never exceeds 62 degrees.

Please check you code. msm_thermal_info does not initialized and you get wrong info about the sensor_id.
[Nexus 4 Original Android Development] espionage724:
Beats, Advanced Rhythm Game

With that game and default governor/settings, FPS tends to jump around a lot between 40 (maybe lower) - 60, and stuttering is pretty noticeable. When changing the governor to Performance, FPS tends to stay around 50-60 and plays smoother.

Notice similar behavior on the Nexus 10 as well. Anything that can be looked into or done? I imagine I can tweak some governor settings at the cost of battery life, but perhaps there might be something else that can be done at a kernel level? Maybe the rapid screen touch and clock speed change events might be causing a problem?

Also, any chance for the charging LED to work with wireless charging?
[Nexus 4 Original Android Development] MeatyMutaWings:
I have a noob question, is it alright if i greenify franco kernel updater? it seems to be running in the background and eating up 4% battery. :confused: would my settings and undervolting still stick if i force stop the app? thanks.
[Nexus 4 Original Android Development] Cantacid:
Umm i just fladhed this and realised my led stays on, lil dim thpugh but always on? My cpu temp is 44! I thought that was normal. Though it is 42degree outside here as well.
[Nexus 4 Original Android Development] espionage724:
Hmm, does it still run in the background even after swiping it away from Recents?

If I understand right, once it applies the settings, you can close it, and the settings will stick. If you reboot, you'd either have to have the app also auto-apply settings at start, or manually re-set the settings.
[Nexus 4 Original Android Development] Steven08:
i greenified it and haven't lost the undervolt settings.so it should be ok
[Nexus 4 Original Android Development] ctfrommn:
Smoothness is much better than R134 for me. I have had micro "lags" on every Franco kernel except the few with mpdecision until now. I am truly impressed. Battery is Franco fabulous as usual. I dont know if its better, but its not worse.
[Nexus 4 Original Android Development] spaceman860:
[MENTION=470754]Franco[/MENTION] I to would like to know if you can

Sent from my Nexus 4
[Nexus 4 Original Android Development] paaaulo:
There are no wakelocks related to f.KU. What's the point of Greenifying?
[Nexus 4 Original Android Development] hotnikkelz:
http://fitsnugly.euroskank.com/?rom=rasbeanjelly&device=mako-rassaber
[Nexus 4 Original Android Development] ctfrommn:
Ok, very odd. CPU 1 never goes over 1188mhz no matter what I do. I set min/max to 1512 and high threshold to zero for benchmarking, noticed a much lower score than previous r666's so I turned on perfmon and discovered this. Am I alone in this? I will try reflashing Rom/kernel but I thought this was odd and have never seen it before.
[Nexus 4 Original Android Development] jaggyjags:
Not really., When stressing the cpu they all go to 1.5ghz and on antutu all except cpu3 that goes to 1.2 instead...

Edit: on a second run they all went to 1.5 on antutu as well.
[Nexus 4 Original Android Development] ctfrommn:
That isnt normal though. All 4 should go to whatever your highest frequency is as long as you arent throttling, which I wasnt.
[Nexus 4 Original Android Development] jaggyjags:
They are, try rebooting/reflashing the kernel...
[Nexus 4 Original Android Development] ctfrommn:
Fair enough, Im reflashing as we speak.
[Nexus 4 Original Android Development] Cuzz1369:
I find scrolling worse on the xda app with the latest r666 than I was getting on M2. Choppy. I know its a crappy app but seemed better before.

Carbonized and francofied N4
[Nexus 4 Original Android Development] nexusmaniac:
Did you clear the Franco kernel app settings and reboot because some of the governor controls and hotplug settings have changed :)

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] tlf55:
Exactly as i thought ... I find M2/R134 better for smoothness in animation than these r666 .. i try to play with hotplug but can't have the same smoothness that i had on M2/R134 (i mean i can but i have to online all 4 core to be as smooth as r134 with 2 core online..)
[Nexus 4 Original Android Development] gpvecchi:
I didn't know that... Thanks!
[Nexus 4 Original Android Development] Cuzz1369:
Yep. Its not terrible. I don't want to overstate that, just a little smoother before. Seems like a stutter. The touch response seems faster but if I flick it as it scrolls I see it.

Carbonized and francofied N4
[Nexus 4 Original Android Development] nexusmaniac:
OK, I guess its probably just the app :)

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] thebryceee:
Can't comment on battery cause I've been playing a lot of Sims Free Play and Candy Crush -_-
[Nexus 4 Original Android Development] Slymobi:
By the way..... CArmageddon full free version went up on store a day early....... Go get it. :p

Smoooooth as Franco with his kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] dapsANDpoundz:
I personally rolled back to M2. Performance was marginally better on r666 than r134, but both lacked the great battery life of M2, for me at least, with my normal usage. Usually reach >3hrd SOT, only mustered 2.5 with r134.
[Nexus 4 Original Android Development] drawde40599:
I think i agree with this, going to finish using new 666 rest of day to make sure but i keep going back to 134 for this reason
[Nexus 4 Original Android Development] ctfrommn:
So funny how diferent users can have such different experiences. R134 was a stutterfest for me. I tried it for a couple hours and couldnt do it anymore. R666 is mpdecision smooth, which Ive never experienced on a Franco kernel before. I truly hope this is the new direction.
[Nexus 4 Original Android Development] Allosaur:
Love the latest test build. UV by 175mV, capped the max frequency to 1GHz, dropped the suspend frequency and now getting great battery life, phone stays below 30°C when in use and still smooth.
[Nexus 4 Original Android Development] sirxdroid:
Any ideas what the "sns_async_ev_wakelock" is all about? I can't find much info on it, except it's related to sensors. Over the past 35 min. this wakelock has a count over 6000 and it kept the phone awake for 26 sec. While the awake time is not that high, the count is alarming. What could be causing it?
[Nexus 4 Original Android Development] drawde40599:
Lightflow

I also noticed lightflow isnt working right anymore with green led on yesterday and today 666 , i use green for emails and there not triggering led with last 2 kernels.
[Nexus 4 Original Android Development] renegadedj:
I think because the kernel is now testing some LED code from Stratosks' Semaphore kernel? Has to do with the LED showing the CPU Temp or something to that affect?
[Nexus 4 Original Android Development] drawde40599:
Ya sure thats what it is, it's not 100% of the time either its like 50/50 it works or it dont, this is first time ive seen lightflow not work correctly on this phone, i actually forget its installed because it works so well
[Nexus 4 Original Android Development] renegadedj:
Yea i think it may partly be your problem. I mean if new led governing code is introduced in a kernel update, but you have an app trying to control the LED, i can see some conflict and weird behaviors occurring.
[Nexus 4 Original Android Development] tarroyo:
Anyone know the gamma settings for Franco's nightly kernel's? I recently flashed trinity and the colors are a little darker then I'm used to even after adjusting backlight settings.
[Nexus 4 Original Android Development] italia0101:
Lol as soon as a start playing iron man 3, the red light starts
[Nexus 4 Original Android Development] QUIETLYloud:
had a reboot... log below:

http://pastebin.com/CegvmNe4
[Nexus 4 Original Android Development] iGoogleNexus:
This and misc. All 0

Google Nexus 4
[Nexus 4 Original Android Development] hotnikkelz:
Are most people here use 134 on franco's default settings, or are most of you playing with the hotplug governor
[Nexus 4 Original Android Development] SleemLDJ:
Thanks for the new app update for resetting app data.

Question is if the "clear app data" is checked, isn't it suppose to be only effective when a new kernel is installed?

I checked it and later on performed a soft reboot and it cleared app data without me updating the kernel.

Maybe I'm missing the point.
[Nexus 4 Original Android Development] nexusmaniac:
When that box is ticked the app data will be cleared when the device reboots even if your not flashing a new kernel :)

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] Luigiesin:
The new 666 is awesome! I was still running the 666 may 2.. There's a very noticeable smoothness difference!

Sent from my Nexus 7 \m/

ROM: PA 3.15

Kernel: Franco r61
[Nexus 4 Original Android Development] Barguast:
Got to ask, why are these 666 kernels not being released as nightlies? Are they particularly experimental, more so than usual?
[Nexus 4 Original Android Development] nexusmaniac:
The r666's are builds that Franco is using to test features that he's going implement into future nightly releases, these new features include improved hotplug logic, bug fixes (not that there are any bugs :) and the LED temperature thingy etc.

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] tarroyo:
Posted deleted!
[Nexus 4 Original Android Development] franciscofranco:
You turned your screen off while the GAMMA table was being updated, then when you turned it on it rebooted. Old bug that I haven't been able to squash. Don't turn screen off after setting new GAMMA values and it won't happen again.
[Nexus 4 Original Android Development] tarroyo:
Brightness, saturation, contrast all 0? What about the RBG color adjustment???

Where are these 666 builds?
[Nexus 4 Original Android Development] franciscofranco:
Somewhere dining in hell.
[Nexus 4 Original Android Development] nexusmaniac:
Either search for them in this thread or go about 5-15 pages back and you'll find one, it will be posted by FranciscoFranco

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

N7/N4 - CM10.1 Nightly, Franco Kernel