yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Foxnov1990:
Fast and Faster both have the same voltage settings. It's nominal that standard has a higher default voltage.

But the reason if you browse this forum a bit have been given several times. It's to avoid being blamed for random reboots due to undervolting, some devices show glitches on pictures taken from the camera, camera is very sensible for UV and may not even boot or go very slow if UVed too much.

Besides from this I can't recall any issues but I think 700mv is just put there to be on the save side ;)

His words

Not given a real explanation, but if he says so you better believe he knows it best :p
[Nexus 4 Original Android Development] omer7:
Sorry for this stupid question.

But can anyone plz tell me whenever i restart my phone the values in color control are to some extent changed. Like in Gamma Settings, i have set the "grays" as 0 for all RGB. But when i restart my phone, the grays value is set to 114, though the slider remains at 0. Why is this so?

And another question that i read in the previous pages that some user had a reboot and someone (i think franco himself, not sure tho) replied that u switched off the screen after changing color so phone rebooted. I had a similar issue, when restarted my phone, the color settings were changed/applied by franco app to my profile and then screen auto switched off (what happens when u reboot ur phone) and phone rebooted. What s the way to get out of this issue, shd i prevent my screen from switching off when the colors r being changed automatically after (manual) restart?

Thanks in advance :)
[Nexus 4 Original Android Development] Steven08:
what fku do you use?update to the last and the values from color control won't change.i have fku 9.3.5 and don't have this problem
[Nexus 4 Original Android Development] omer7:
Thanks for ur response.

Sorry i forgot to tell u abt some more info.

I m using PA rom 3.15 - 26 apr build

Franco kernel M2

And what is fku?

In franco app every setting is on default except for color profile.

---------- Post added at 03:18 PM ---------- Previous post was at 03:13 PM ----------

By fku u mean "franco kernel updater" app?

And i m on 9.4.1 i think. The latest.
[Nexus 4 Original Android Development] PetritH:
fku is franco kernel updater, anyways try clearing data reboot then set the settings the way u want and reboot again see if it changes the values... btw don't greenify fku.
[Nexus 4 Original Android Development] bradm23:
You are correct, both version of axiom work very well. I find the odex version to run a little smoother imo
[Nexus 4 Original Android Development] steviewevie:
Yeah it's a known bug. The greys value seems not to be set on a reboot, so it goes to the default of 114. 114 is an invalid value for Franco's app so the slider stays at zero. Reset it to zero for each of red/green/blue after each reboot (or restore a saved profile) and you will be OK.

Sent from my Nexus 4
[Nexus 4 Original Android Development] omer7:
Thanks for this.

Yeah i have cleared the app data, rebooted, again changed color settings to my profile. Rebooted again and again the grays r set to 114.

I ll set it to zero.

And after clearing the apps data the mob auto rebooting (after auto color change by franco app) issue seems to be gone.

And is it normal that when u reboot ur phone, it takes a bit long to connect to wifi when u r using franco app (sorry if it is not like that)
[Nexus 4 Original Android Development] Foxnov1990:
It's just a little malfunction in the viewing of the digits. Don't worry about it, nothing has changed ;)

This "error" is / was known and got fixed in either F.Ku v9.3.5 or v9.4, not sure. Just clear app data and reboot ;)

So update your app and you won't have it anymore (I don't at least :p)

If you don't want to or can't update, just do stuff till you see the colors have changed, then allow it to switch off the screen, simple as ^^

Not with me tbh, might be that something is delaying it of some sort.. I can always instantly go on wifi... even tried it last night rebooting phone and it immediatly recognised VLC remote :p

[Edit] damn this topic goes fast :D
[Nexus 4 Original Android Development] steviewevie:
Sorry but that's not right. The greys setting really is set to 114 after a reboot. I know this because when I look at the test images (particularly the fourth one with the greyscales) I can see they are wrong after a reboot , and when I correct them back to zero it looks good again.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Foxnov1990:
Weird, I have no such problems..

I've tried this on green, red and blue and I notice no difference when changing the 114 to 0
[Nexus 4 Original Android Development] steviewevie:
That might just be because of your colour/gamma setup though, i.e. the difference between 114 and 0 is negligible for you and your settings. Doesn't necessarily mean that's the same for everyone though ;)

P.S. if you want to see this bug, try the pre-loaded 28_halluci293 profile and do a reboot.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Foxnov1990:
Just tried on 28, rebooted, 100% brightness.

And it was 114, so had to slide it to 1 and then back to 0. The only change that I saw was when it changed to 1, but sliding it back to 0 made it look rather equal to 114 (standard setting)

Of course, it might just be in my head or I must be tired, both are viable options :p But I thought it has been said before that the 114 vs 0 is just a graphical "issue" in the app. If not, my apologies.
[Nexus 4 Original Android Development] steviewevie:
You did reboot, right? I see a big difference on the fourth test image (the greyscales).

Sent from my Nexus 4
[Nexus 4 Original Android Development] malukiz:
On the r136, the cpu have raise the temp of 71°c just by browsing internet :o
[Nexus 4 Original Android Development] steviewevie:
For anyone doubting the bug where grey gamma values are reset to 114 on a reboot, have a look in /sys/class/misc/gammacontrol and the files ending in "greys" ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Danny.ns:
Isn't that very hot? I browsed the web for ~30 minutes (on wifi, if it matters) straight using chrome with no undervolting done and my CPU temperature was 46°C. Also on r136.
[Nexus 4 Original Android Development] Bobtehblob:
I swear the whole greys resetting thing got fixed a while back now?
[Nexus 4 Original Android Development] Net.silb:
[MENTION=3292224]franciscofranco[/MENTION]

It still doesn't look or feel like the cpu is being boosted to 1026 MHz on a single touch...

Does

if (likely(ts->ts_data.curr_data[0].state == ABS_PRESS))

include every single touch of the screen or can it exclude some touches?

---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------

Happens to me too on a reboot...

Really annoying...
[Nexus 4 Original Android Development] franciscofranco:
Its boosted, I guarantee you. I'm a special version of System Monitor with 0.1 seconds refresh and I can see it easily every time I touch the screen.

I need that check because I need to know when the touch has been released to clear some variables.

I already shown you what happens: when the screen is touched that function is called and it changes a struct var to 1, then when its released that struct var changes to 0 and that function is not called again until touching again.

I'm going to check that grays **** again.
[Nexus 4 Original Android Development] franciscofranco:
Ah I'm a ****ing moron, in the Gamma class I was adding a key called red_grays, and in the bootservice I'm checking for red_greys... shoot me please.
[Nexus 4 Original Android Development] Net.silb:
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------

Another thing, did you change something on screen on?

In the past few builds I noticed a lag in the lock ring animation...
[Nexus 4 Original Android Development] franciscofranco:
Weird, didn't change anything.
[Nexus 4 Original Android Development] tlf55:
Yeah feeling this lockring lag too :/ but I'm still voting for a single touch have to enable the second core too ! At least at 500mhz or something like that .. That would be a big improvement in UI smoothness ! :)
[Nexus 4 Original Android Development] Net.silb:
[MENTION=3292224]franciscofranco[/MENTION]

I was thinking that we should try and mimic mpdecision's behavior and then make its behavior user configurable, what do you think?
[Nexus 4 Original Android Development] Hanny:
ive got that suggestion a long while ago when the hotplug baby is born... its not his approach, and we would not be possible to observe & follow closely how mpdecision behaves just with our eyes, at least not worth the effort

the first and easiest thing about mimicking mpdecision is to online 2 cores both @ 1026 immediately on every touch, and this is not favorable to both the temperature and battery

though, a lower frequency might be feasible, but that means every single touch is forced to have such cpu boost. Sometimes we just touch some **** for no apparent reason, and that is not opening an app, opening an notification or anything but just a touch. In the case of onlining 2nd core every small touch, the battery is consumed unnecessarily in those events.

my (and crimsonsmear's) approach back in a few pages is to make use of the go_hispeed_load and focus on utilizing the performance given by frequencies instead of the no. of cores. the question is - will a "touch-boost" be more responsive than a "boost after calculation of load", in order to minimize stutter especially during animations which is happening immediately after a touch? yea we are talking in milliseconds...

if the calculation of load can join the party, then those unnecessary touches will not use up extra battery, while achieving our goal of putting more resource (and hence smoother) on just-a-small-burst-of-load UI interactions here and there.

EDIT: sorry user "1026" if i brought u here... stupid auto mention function lol.

EDIT2: wow, I see something there ;) https://github.com/franciscofranco/mako/commit/ddbd16add92f0347b332ad57b3705a6587fee9b1

I think we can try it first before going wilder haha
[Nexus 4 Original Android Development] irishrally:
Well maybe you should have read a few posts back, no search necessary, and seen that four people already politely answered my question. useless post is useless.

I "came in here" and asked, "Franco kernel for S4GE?", no attitude. I quipped playfully at the person that responded and that was all. Then the noob tried to teach me a lesson, similar to you now. Maybe you guys will get your mod patch soon. Welcome to xda.
[Nexus 4 Original Android Development] franciscofranco:
Yeah scaling min_sample_time works fine. I will release r137 with that patch you linked.
[Nexus 4 Original Android Development] Hanny:
awesome :) does min_sample_time apply on the 2-core-702mhz boost after swipe as well? if not, what is the ms of that swipe-boost?
[Nexus 4 Original Android Development] trailblazerz11:
Hey Franco I was looking at the bundle of work queue commits on your github several days ago. Just curious, any reason they appear to be gone now?

Thanks

Sent from my Nexus 4
[Nexus 4 Original Android Development] LibiSC:
Bang
[Nexus 4 Original Android Development] manulemaboul:
It's only the lock screen that's sometime a bit laggy, no need for more touch boost, we maybe just need a lil' wake up boost IMHO. :)

Edit : nevermind, r137 should solve it anyway :)

Next time I'll read all unread posts before replying to someone :p.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Hanny:
we have had the wakeup boost for a pretty long time, its 4 cores @ max frequency for a really short period. :)

the occasional lockscreen ring lag (actually unrelated to touch boost as the original user suggests) - i didnt experience usually but i believe i've seen it once or twice during the past week - might be something else
[Nexus 4 Original Android Development] Shano56:
Soft reboot

http://pastebin.com/h0YPJdfj
[Nexus 4 Original Android Development] manulemaboul:
Noticed it once or twice, thought it was because of my custom icons on the ring actually, it's so little.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Arstoien:
It's there only when the phone wakes up from deep sleep but not all the time. It used to happen only if I lower the suspend frequency a lot but now I'm running with the default 700 and I see it every now and then when waking up the phone. Raising the suspend frequency to like 1.3 GHz seems to help but I'm not really willing to do that – not bothered that much.
[Nexus 4 Original Android Development] manulemaboul:
I removed the lockscreen, problem solved lol :p

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
I rebased and removed them to test something. I will re-merge them in the future as I like the changes that they made on those commits.

[ 0.000000] Linux version 3.4.0-perf-g85ba2bc (hudson@koushik-lion) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 13 14:32:59 PDT 2013
[Nexus 4 Original Android Development] ceejay83:
I use minimize lock screen challenge :)
[Nexus 4 Original Android Development] franciscofranco:
r137:

* Some improvements under the hood
[Nexus 4 Original Android Development] dark_ente:
*in before battery report*
[Nexus 4 Original Android Development] italia0101:
Flashed . Feels like sex in the morning
[Nexus 4 Original Android Development] steviewevie:
Server getting hammered lol, think I will try later.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Net.silb:
Slooooowwwww downloading....... That's how popular your kernel is!

Thanks Franco! :D
[Nexus 4 Original Android Development] :
Can't UV beyong -25mv (from 850 to 825mv) using the app, it gets stuck, but can UV manually by inputting values, anyone else having this issue?
[Nexus 4 Original Android Development] franciscofranco:
The server is being slaughtered, sorry guys. I need to get a more powerful machine, I hope its not too expensive.

Neps, I undervolt a 100mV to every step using -25 button and it works fine.
[Nexus 4 Original Android Development] jrxtepan:
Server is being hammered!! :laugh:
[Nexus 4 Original Android Development] rosswaa:
Yeh downloads are slow ATM but when it does download I always get md5 miss match. Its done it since the auto update thing has been implemented. I have to wipe cache to download kernel and flash it properly

Never use to happen :S
[Nexus 4 Original Android Development] nexusmaniac:
Thanks for r137 Franco, I've only had it for 3 minutes but already I've noticed that it's incredibly smooth compared to r136 :)

Edit: not sure if it's just a placebo :D

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] jrxtepan:
QQ

Hey Franco, do you go further than 100mV. I went to -125 yesterday and got some soft reboots and boot loop so I had to go back. Then I uv'ed to 100mV and all was fine...

What do you normally use?
[Nexus 4 Original Android Development] Shano56:
is that cm kernel? O.o
[Nexus 4 Original Android Development] Redneck Trash:
Auto flash works just fine.
[Nexus 4 Original Android Development] manulemaboul:
Can't even launch the download from the app at the moment, leave me some bandwith guys :p

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] MonztA2:
I think the default update check interval is way to often. Was it hourly?
[Nexus 4 Original Android Development] franciscofranco:
-100mV as I said :p

Not placebo!
[Nexus 4 Original Android Development] jrxtepan:
Great!

Thanks a lot buddy... Let me continue with my Advertising Campaign via twitter to this awesome kernel and it's app :highfive::good:

Thumbs up, thanks for the hard work.
[Nexus 4 Original Android Development] :
Reflashed the image and its working again, derped during flash or something
[Nexus 4 Original Android Development] Burlito:
Franco how much traffic does your kernel produce with downloads and stuff?

I have a server with good speeds and i could provide some ressources.

Maybe PM me if you are interrested.
[Nexus 4 Original Android Development] MPAI:
r137 can be downloaded from http://minooch.com/franciscofranco/Nexus4/4.2.2/milestones/zips/franco.Kernel-Milestone.2.zip rite?
[Nexus 4 Original Android Development] MikeRL100:
Yeah someone should mirror. Poor server! I'll stop trying to download until this is fixed if it helps.

Sent from my Windows XP machine using ie6
[Nexus 4 Original Android Development] Koraboros:
No, download from here:

http://minooch.com/franciscofranco/Nexus4/4.2.2/zips/
[Nexus 4 Original Android Development] MikeRL100:
Can someone that has release 137 mirror it via Mediafire or something? (Dropbox would run out of bandwidth). Thanks!

Sent from my Windows XP machine using ie6
[Nexus 4 Original Android Development] dapsANDpoundz:
Couldn't you just go to the original post and download it from there though?

EDIT: also, with r137 now my bars on data are grayed out. Didn't happen on r136. Rebooted and its still like that. I'm gonna try and flash r137 again and see if that fixes it.
[Nexus 4 Original Android Development] Step-han:
Here a mirror of a flashable .zip from R137:

http://www4.zippyshare.com/v/32683389/file.html
[Nexus 4 Original Android Development] MikeRL100:
Not exactly. I tried that, Franco's right. Server is being slaughtered. Cannot get it on my end at all. Update: Awesome! Thanks for the mirror!

Sent from my Windows XP machine using ie6
[Nexus 4 Original Android Development] blueren:
The wrath of the auto updater notification :|
[Nexus 4 Original Android Development] Step-han:
I have still blue bars with R137.
[Nexus 4 Original Android Development] tkalli:
Same here.
[Nexus 4 Original Android Development] ironjon:
Incredible smoothness in 137 :)

Thx francisco

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] murtezahu:
Anybody else having issues with really slow downloads thru the app for the last 2 nightlys? Like 5kbps slow.
[Nexus 4 Original Android Development] SleemLDJ:
Check out Franco kicking my ass here.
[Nexus 4 Original Android Development] dapsANDpoundz:
Reflashed r137 and I'm good to go now. Blue bars everywhere.
[Nexus 4 Original Android Development] JarGnex:
Same here. The notification about new updates was probably a bad idea lol :(
[Nexus 4 Original Android Development] Gorillazz:
Where to start???

Hi folks

I'm new to rooting and stuff. Today I hesitantly installed cyanogenmod rom on my nexus 4 and interested in franco kernal. but don't know which file to install:confused:

I somehow downloaded franco.kernel-nighty-r378.zip which is a 5.69 mb file. So my question is that whether its the correct file to install as its a very small file compared to the rom i just installed? please guide me as i'm a novice:eek:
[Nexus 4 Original Android Development] shankesh:
Hey guys I'm having scroll lag after installing cm10 and Franco 137... After that I flashed the factory original rom.. In that also I'm having lag... Anybody know what is the reason ... Plzz help me guys
[Nexus 4 Original Android Development] pughie:
That kernel is for the galaxy nexus not the nexus 4, latest nightly for the nexus 4 is r137 :) and yes kernels are very small in comparison to an entire ROM, my advice is read read and read some more before you do any damage to your lovely N4
[Nexus 4 Original Android Development] italia0101:
How do you get to that?
[Nexus 4 Original Android Development] murtezahu:
Just saw the post from Franco about the server...
[Nexus 4 Original Android Development] Net.silb:
there is no r378 for N4 yet...

Go here http://xdaforums.com/showthread.php?t=2002782

u should download a file named franco.kernel-nightly-r137.zip and flash it in CWM
[Nexus 4 Original Android Development] Alex240188:
yep, i was only getting 3kb/s

so i downloaded from the zippy mirror

i have uploaded it to my personal ftp server

I have a 20MB/s Upload & a powerful PC so should be nice and fast

however i only have 600GB of bandwith per month so i will only leave it online for a couple of hours while franco's server catches up

http://goo.gl/IZ5R0
[Nexus 4 Original Android Development] Step-han:
Wipe everything, download latest CM10.1 nightly from here and flash it, after that flash franco kernel and it would be fine.
[Nexus 4 Original Android Development] shankesh:
Yeah I did that... I wiped cache dalvik cache and installed the ROM... but I can feel the sluggish even in my stock ROM and stock kernel... Do no what to do
[Nexus 4 Original Android Development] deltatux:
I think the app shouldn't constantly remind you that there's a new update. I find that rather annoying. If I swipe it away, it should stay away unless I turn on an option to constantly remind me...

deltatux
[Nexus 4 Original Android Development] Promsd:
r137 very smooth :)
[Nexus 4 Original Android Development] Alex240188:
sorry, for some reason it didnt like directly linking to the file, updated link to directory, should be fine now
[Nexus 4 Original Android Development] italia0101:
I have Franco in my circles... but doesn't appear for me :(
[Nexus 4 Original Android Development] juggies:
In the industry we like to call this load testing, lol...
[Nexus 4 Original Android Development] franciscofranco:
I dont really like mirrors, but I guess in this case its unavoidable. I will try to sort it out guys. Please bare with me.

And the notification thing is not a bad idea at all. It can use some improvements for sure, just bare with me, Im only one guy, takes time.
[Nexus 4 Original Android Development] deltatux:
That basically defeats the purpose of an automatic notifier, that's only the time it polls the data. Sometimes I get the notification 10 minutes after I swiped it even though it's set to an hour, so that means there seems to be a mechanism that springs the notification back.

Alright, thanks for the acknowledgement :)

deltatux
[Nexus 4 Original Android Development] franciscofranco:
Pwned. And thats not my best score, I had 35k before but I wiped the rom some months ago. Expect better scores soon :p
[Nexus 4 Original Android Development] SleemLDJ:
Probably maybe you don't play the same game.

The game is Beach Buggy Blitz.
[Nexus 4 Original Android Development] drawde40599:
Yep! No problemo :P

Ive only had installed for a few (137) but i really like so far . Going test stock franco settings for a day.....

Thanks for your time!
[Nexus 4 Original Android Development] SleemLDJ:
I didn't.

Either you update Beach Buggy Blitz or download it.

Sign in with G+ and go to achievement section or so.
[Nexus 4 Original Android Development] italia0101:
Yea i got beach buggy blitz ...
[Nexus 4 Original Android Development] deltatux:
Had to revert back to r136, r137 keeps crashing on boot while it's trying to change the gamma values when I turn on my screen within 30 seconds it boots to my lock screen.

deltatux
[Nexus 4 Original Android Development] .coomb.:
What game is that? I could try to play it and then maybe have a match with you :cowboy:

Nevermind, it's beach buggy blitz.
[Nexus 4 Original Android Development] Mercado_Negro:
Just had to do a factory reset :(

Received the r137 notification, hit it and it took me to the app, so far so good. Then I realized I was on Edge so I just left the application and decided to give it some minutes. About half an hour later I hit the notification again and boom, Google logo in all its glory. I couldn't get past the bootanimation then. Turned off the phone, booted in bootloader mode and went to the recovery. Wiped dalvik/cache and tried it again, nothing stuck at bootanimation... Factory reset.

I know this is useless without a log but I couldn't get one for you, sorry.

I wonder what went wrong there :(
[Nexus 4 Original Android Development] Dan53:
Factory reset only clears data not the last_kmsg? you might be able to get it! (AFAIK)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
Oh, that'd be great. Could you please tell me how to get it? I'd truly appreciate it.
[Nexus 4 Original Android Development] Arstoien:
You could have just reflashed the kernel? Probably would've fixed it.