yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] SubwayJrd:
I cannot express how much of a fallacy that is. FrancoKernel has always been fantastic for me on battery life (and I'm one of the people who has pulled 5 hours SoT w/ 14 hours battery life).

It's always true that battery life is subjective based on the workload the user puts the phone through, but take those erroneous claims elsewhere. Especially when you can give no evidence that your claims are valid.

Some poor new user is going to see your post and make all the wrong assumptions from it.
[Nexus 4 Original Android Development] lorolouis:
Does anybody know if the new hotplug driver settings are taken live while is running or you need to reboot after you change them?

For example, if you manually edit the conf files here: /sys/class/misc/mako_hotplug_control/ by a text editor -

will the kernel take them immediately when a given threshold is reached or you need a reboot?

What happens with the current state in regards of the very moment of saving a newly-submitted value if all this is so-hot-live-plugging thing as is sounds like?
[Nexus 4 Original Android Development] sirxdroid:
These are virtual files that do NOT survive reboots. You need an init.d script to write to these files on boot if you want persistence outside the fKu app.

You don't need a text editor to write to these files, from a terminal you can simply:

echo "value" > /sys/class/misc/mako_hotplug_control/...

Once you write to them the values are live (perhaps subject to a very small delay that you will not notice)
[Nexus 4 Original Android Development] bilguun1:
Wtf, I was just asking for some help, if u can't help, could u just stfu? This claim, that proof, wth is that? I m just posting a problem I am facing. I bought the Franco app to support Franco. I m not talking **** about him or his kernel. I have a problem, and I am asking for help. Can you give me a help? No? Then stfu.
[Nexus 4 Original Android Development] Paragon_X:
Sorry guys but I have to ask. What exactly is hotplug? I did a general search but obviously did not search hard enough. Can someone just give me a simple break down to as whether I should consider diving in?
[Nexus 4 Original Android Development] Testraindrop:
Simple: How to on/offline cores.

Don't change francos values if you have no problems...
[Nexus 4 Original Android Development] gharrrrrr:
LOL! Thank you so much. This just put a smile on my face and made my day.
[Nexus 4 Original Android Development] SubwayJrd:
The problem was you made that statement outside your asking for help. Without the context it sure looks like you're smack talking on Franco's Kernel.

Aside from that, as far as I know Franco uses stock settings for data (stock drivers, etc.). Though Franco himself has recommended the following settings for build.prop to enhance HSPA/HSPA+ Connectivity (they seem to work for me as well).

ro.ril.hsxpa=2

ro.ril.gprsclass=12

ro.ril.hsdpa.category=24

ro.ril.hsupa.category=7

There's no reason to flame at me, especially with how much your original comment lacked context. There's your help as well.
[Nexus 4 Original Android Development] Paragon_X:
Cheers. I have no problems whatsoever, just noticed from the last few updates it seemingly revolved around hotplug so thought I ask.
[Nexus 4 Original Android Development] nellisere:
Where abouts in the build.prop do I put these, it it ok to put them at the top of the additional settings, or do they have to be in a certain place?
[Nexus 4 Original Android Development] SubwayJrd:
It really doesn't matter, though for consistency's sake I would put them at the bottom.

I have both a batch file for Windows and a shell script for Linux that echoes them all into the build.prop (a reboot is required, though I have the batch file doing that automatically) if you're interested.
[Nexus 4 Original Android Development] ctfrommn:
Add them to the bottom. The last entries are the ones used.
[Nexus 4 Original Android Development] nellisere:
That'd be great, thanks!
[Nexus 4 Original Android Development] SubwayJrd:
This is correct, it executes in first to last order (forgot about that). Although, if none of those specs exist before in the build.prop it doesn't matter (because they're the only instance).

Besides that, yes. The bottom.
[Nexus 4 Original Android Development] ctfrommn:
Indeed, they are rarely there to begin with, just an old habit for me.
[Nexus 4 Original Android Development] SubwayJrd:
Here they are.

As a note, BOTH of these WILL reboot your device when you run them (after the build.prop tweaks are applied, which is necessary to have them actually take effect in the phone).

To stop this just remove "adb reboot" from the end.
[Nexus 4 Original Android Development] nellisere:
Just had a reboot, went to wake up the screen after the phone had just turned on, vibrated and Google logo. Small log.

te+0x40/0x78)

[ 31.106170] r8:00000004 r7:2a030fdc r6:ed4966c0 r5:00000000 r4:00000000

[ 31.106872] [<c01241ac>] (sys_write+0x0/0x78) from [<c0010b80>] (ret_fast_syscall+0x0/0x30)

[ 31.106964] r8:c0010d28 r7:00000004 r6:00000001 r5:00000004 r4:00000003

[ 31.107666] Code: e3a0ad0d e08fc00c e50bc030 e79c8003 (e5943000)

[ 32.042297] get_prop_batt_capacity: low battery charge = 8%

[ 32.043670] get_prop_batt_capacity: low battery charge = 8%

[ 32.046142] get_prop_batt_capacity: low battery charge = 8%

[ 32.051513] get_prop_batt_capacity: low battery charge = 8%

[ 32.060760] get_prop_batt_capacity: low battery charge = 8%

[ 34.602569] ---[ end trace 58a0c19351686aa9 ]---

[ 34.602691] Kernel panic - not syncing: Fatal exception

[ 34.602996] wcnss_8960: crash shutdown : 0

[ 38.209381] Rebooting in 5 seconds..

[ 43.217651] Going down for restart now

No errors detected

Boot info:

Last boot reason: kernel_panic

---------- Post added at 10:18 PM ---------- Previous post was at 10:06 PM ----------

Thanks, have just added them but it seems to make my internet slower, surely this isn't the effect it should have? Gone from 2Mbps down to 0.5Mbps down
[Nexus 4 Original Android Development] ctfrommn:
The numbers have to coincide with speeds your network actually supports. So if those dont, that could happen. Try removing them and testing again. If it improves these are not for you.
[Nexus 4 Original Android Development] SubwayJrd:
I test out speeds at about the same as without the edits, my data is just far more stable. It's probably a network/signal problem. Give it several tests and see what happens.
[Nexus 4 Original Android Development] franciscofranco:
Whats the kernel version? Thanks.
[Nexus 4 Original Android Development] nellisere:
My network (Three) Don't have 2G so the GPRSClass is not needed, but they support DC-HSDPA (42Mbps) and HSPA+ (21Mbps) so they look about right, I shall give it a few days.

---------- Post added at 10:36 PM ---------- Previous post was at 10:35 PM ----------

Sorry, I'm using r120. Conservative 1350/384 -125mV UV.
[Nexus 4 Original Android Development] ctfrommn:
Yep, those are correct for that network. Sometimes all is well though and they dont improve speeds. They definitely shouldnt make it slower though.
[Nexus 4 Original Android Development] gharrrrrr:
Not sure why you quoted my post. But OK. I was just laughing at his passionate response. Cheers and if you need a hug to make you feel better I'll try my best to send you a virtual one.
[Nexus 4 Original Android Development] hospital349:
For the first time in a long time, I haven't noticed anybody complaining about/reporting 'stuttering/lag'.

Let the good times roll. :highfive::highfive:
[Nexus 4 Original Android Development] eep2378:
So what are you guys using for hotplug settings? I'm on 111 because of lag with kernels utilizing the new hotplug driver. I'd give 120 a go if there is no lag :D

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] Arstoien:
To be honest, I even increased my timer to 40k, decreased hi_speed to 700 MHz and set the second level threshold to 60 and I don't see any stuttering. With defaults I even get anti-stuttering – my phone gets randomly faster and acts before I do 0.o
[Nexus 4 Original Android Development] vickpick:
it might be just effects of a recent e-haunting of your phone that you havent suspected yet.
[Nexus 4 Original Android Development] hospital349:
Make a backup of r111 and then flash r120. Clear the app data after flashing the new version and then reboot and you'll have all the new settings included... apart from the new Hotplug values, that Franco forgot to include.

They are:

High: 90

Medium: 25

Low: 50

If you don't like r120 (which you will ;)), you can always restore r111, from the backup you made earlier. :good:
[Nexus 4 Original Android Development] resynx:
To me, 120 feels smoother than 111 :victory:
[Nexus 4 Original Android Development] ngkongArm:
My battery lost almost 20% at night when i fall asleep. Using r120 with no change. Any idea how i configure to saves battery more when it's idle?

Another question, which one is better to affect battery life, Hotplug / Governors value?

Thanks in advance.
[Nexus 4 Original Android Development] resynx:
Use BBS to figure out what's draining your battery. It's not the kernel I can assure you, probably a rogue app or something along those lines.
[Nexus 4 Original Android Development] Hanny:
Procedure of my microstutter test:

open system monitor, no live wallpaper, idle at homescreen, at the very moment you see there is only cpu0 running at 384mhz, press on whatsapp / google chrome shortcut on homescreen. transition animation is slowed down / teared to 2 or 3 parts during that 0.5 second.

90-50-30 interactive - exist

90-25-50 interactive - exist

90-50-30 ondemand - exist

90-25-50 ondemand - exist but minimal

while these are true on r120, im running on a test version without sec_threshold between cpu0 and cpu1. things improved, but unfortunately these results are still true.

i went back to r111 mpdecision and did a triple confirm with my eyes, found one thing - take the black empty areas (bottom right corner) on my navigation bar to test, when I put my finger on, core 1 simply goes on no matter what. it does not stay for so long though - when I rest my finger at the same place for some seconds, core 1 goes back off. this touching-screen-cpu1-online-for-some-sec behaviour is not observable on franco hotplugging.

my guess is, on franco hotplugging, even without sec_threshold, core 1 goes online DURING the load call from opening whatsapp from 384mhz idle. but mpdecision already kicks in core 1 when finger touches the screen and BEFORE the app threads power from the cpu. that millisecond difference! thus the transition animation is smooth.

try two things:

1) my microstutter procedure on r120

2) the behaviour of mpdecision on r111

and tell me if my findings are correct :)
[Nexus 4 Original Android Development] dapsANDpoundz:
I'm kinda having a similar issue. With r111, after a full day GSAM reported that I lost 0% of my battery while the screen was off, idled well. r120 is great performance wise but GSAM says I've lost 23% while the screen was off. Don't know what could be causing that if not the kernel because I have not installed any new apps since I've been using r111. This happened a bit with r119 too as well if that helps.
[Nexus 4 Original Android Development] ngkongArm:
Thanks, :)

But i have no idea what is BBS? lol.

Does it related to mobile data? Because i still turn it on at night.
[Nexus 4 Original Android Development] blitzzz3434:
BBS= betterbatterystats, an app in the play store to help you diagnose your battery drain.

Sent from my Nexus 4
[Nexus 4 Original Android Development] resynx:
Better Battery Stats, it's an app you can download from the market. It'll tell you what apps / wakelocks are draining your battery :highfive:
[Nexus 4 Original Android Development] Haomuch:
Just made the app loading tests but I have different feel. Both r111 and r120 have delay in loading whatsapp at the first time after reboot. And the delay gone in the second loading for both builds. I think the lag is more due to first time loading memory reading/writing delay.
[Nexus 4 Original Android Development] Underground_XI:
Where are those H M L values you told him to change? Franco app?
[Nexus 4 Original Android Development] DesertVelo:
Easiest in the Franco app via the Frequencies/Hotplug Control menu.

You can also create a script with the following values/files:

echo "90" > /sys/class/misc/mako_hotplug_control/first_level

echo "25" > /sys/class/misc/mako_hotplug_control/second_level

echo "50" > /sys/class/misc/mako_hotplug_control/third_level
[Nexus 4 Original Android Development] Underground_XI:
Version 9.0 of the app? Because mine does not any hotplug control...i have frequencies/voltages then governor control
[Nexus 4 Original Android Development] vickpick:
9.1, hotplug control is in fre/vol
[Nexus 4 Original Android Development] scream4cheese:
Update the application.

The latest is v9.1.
[Nexus 4 Original Android Development] franciscofranco:
I agree, if its after a reboot the app is not even in cache, I would bet its what Miasmic is seeing.
[Nexus 4 Original Android Development] franciscofranco:
Doesn't seem kernel related at all, something is keeping the devices awake and not in deep sleep mode. I don't see the kernel doing that to be honest because if it was everybody would be reporting the same thing.
[Nexus 4 Original Android Development] noonecanhide:
I am still on r111; and still have a problem with kernel panics causing a bootloop. The kernel panic happens randomly while (re)booting the device, causing a bootloop which settles after a few reboots. Last_kmsg is not complete, it only contains 946 byte - everytime.

How can i debug this, i really want to know what is wrong there...
[Nexus 4 Original Android Development] Underground_XI:
Find the app that is not letting your device go into deep sleep. Wakeup detector from playstore might help you find it.
[Nexus 4 Original Android Development] sirxdroid:
What are the correct sysfs virtual files for reading the CPU min and max freq? I found these:

/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq

/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

Can these be set on a per core basis or cpu0 values really drive all the cores?
[Nexus 4 Original Android Development] blade_:
nice shot:D
[Nexus 4 Original Android Development] scream4cheese:
:confused:
[Nexus 4 Original Android Development] Vangelis13:
3.999

3.99

:confused:
[Nexus 4 Original Android Development] franciscofranco:
Do you have Gamma values being set on reboot? Do you turn off your screen right after rebooting?

/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

in this chip they have to be set on all cores, because the cores are asynchronous.
[Nexus 4 Original Android Development] danthepan124:
Trickstermod works with this kernel right?
[Nexus 4 Original Android Development] mbh87:
Isn't it possible to delay init.d scripts? I don't know much about them, but maybe delaying it a few seconds might help things.
[Nexus 4 Original Android Development] Vangelis13:
Yes, it does. I'm fairly sure most do.
[Nexus 4 Original Android Development] Hanny:
Naw, because I did the microstutter tests for many repeated times to ensure my observations are correct. The first launch after reboot, has definitely been passed. Haomuch did you press the shortcut exactly at the time where its only cpu0 at 384?
[Nexus 4 Original Android Development] sirxdroid:
It does but you won't be able to set all the options you can through the fKu app.

Edit: the app has been updated to fully support Franco kernel, including Hotplug settings and all the gamma settings.
[Nexus 4 Original Android Development] Luigiesin:
Finally updated from 111 to 120! Me likey! :)

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.1 (Mar07)

Kernel: Franco r120

T-Mobile
[Nexus 4 Original Android Development] gparmar76:
This is with r120/Cyanogen 4-8 nightly with battery at 78%...shaping up to have awesome battery life.
[Nexus 4 Original Android Development] bradm23:
Anyone having a high suspend back off kernel wake lock with 120? Been a big battery hog when I didn't have it on 119 or earlier.
[Nexus 4 Original Android Development] pyr0sphere:
All on wifi I presume? Still pretty impressive nonetheless

Edit: your screen shot shows 5% and not 78%?
[Nexus 4 Original Android Development] Nocturnal86:
Whats the difference or is there a differences between the Governor control "hispeed_freq" and The actual Maximum CPU Frequency selection? They have me a bit confused. Sorry if its a dumb question.
[Nexus 4 Original Android Development] danthepan124:
So Trickster supports franco now?
[Nexus 4 Original Android Development] sirxdroid:
Looks like it does a very nice job in its latest version.
[Nexus 4 Original Android Development] ngkongArm:
thanks, already installed now. i think need time to watch the battery right? i'll report and post some screenshot later maybe.
[Nexus 4 Original Android Development] blahblah13233:
Awesome work ! Battery life boosted from R111 to R120. Will post a pic later !
[Nexus 4 Original Android Development] TaintedByte:
EDIT: Whoops, this was meant to go in the Nexus 7 thread. Stupid Tapatalk.

To at least stay on topic though, the latest couple of releases have been buttery smooth and awesome on battery life over here!
[Nexus 4 Original Android Development] kyokeun1234:
Been looking through about 10 pages of this thread and seems like no issues on r120 so finally decided to flash it on my phone :)

Can't believe I waited soooo long to finally flash Franco but whatever. I used to be obsessed with Franco kernels so I am expecting so much from Franco on Nexus 4 too ;)

As always, thank you so much for your work!
[Nexus 4 Original Android Development] Polv89:
OT. Font used?

Thanks

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] Underground_XI:
Nothing impressive about it to be honest.
[Nexus 4 Original Android Development] gravitysandwich:
@gparmar76

3 hrs 15 min sot. Yet my jaw drops when I seen people with 9 hours sot.
[Nexus 4 Original Android Development] thebryceee:
What's impressive is the SOT with the 6,400 mAh battery for the Note 2. Over 11 hours!!!
[Nexus 4 Original Android Development] Underground_XI:
Noote 2 gets boring after a while, but i have seen others get 6 hours + on nexus 4 that's why i told him those screenshot weren't impressive.
[Nexus 4 Original Android Development] FaithCry:
what font are you using? :)
[Nexus 4 Original Android Development] vickpick:
This is what I got.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
I'm running standard r120 settings and my CPU doesn't even drop below 500mhz on my launcher....

Edit: Nm finally got it. Sow hat am I looking for? It lags in the transition?
[Nexus 4 Original Android Development] Cuzz1369:
Have to say the hot plug driver has come a long way Franco. I don't know enough about this stuff yet to know how much work it is but appreciate the every minute you put in to this so far. Let me know when you change phones cuz I'm coming with you.

Sent from me to the world on my Nexus 4
[Nexus 4 Original Android Development] thebryceee:
Nexus 5 :cool:
[Nexus 4 Original Android Development] Nocturnal86:
Can anyone please help me with this question i have? It got lost in the mass of posts (Whats the difference or is there a differences between the Governor control "hispeed_freq" and The actual Maximum CPU Frequency selection? They have me a bit confused. Sorry if its a dumb question)
[Nexus 4 Original Android Development] gparmar76:
PKP

9 hours is achievable if your brightness it turned down and you down lock the CPU...I do none of that...ever...I didn't get to do a full 100% test...I just charged it a little to 78% when I set it up..from 100% it would have hit 5+ hours...with about 11-12 total...that's about as good as it gets with no down clocking or UV, etc etc.

---------- Post added at 12:38 AM ---------- Previous post was at 12:35 AM ----------

I use Robotic Condensed...kinda fell in love with it the first time I saw people using it.

---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------

From 100% battery, this kernel will get like 5 hours screen on with 10-12 total...that's awesome for a no tweak setup...my brightness stays at 50%..no down clocking or UV at all...people with better stats are tweaking for it...which isn't a realistic picture.
[Nexus 4 Original Android Development] Mercado_Negro:
I had to stop using your kernel because this is frustrating. I was using mbh87's color profile but as you mentioned when the application tries to set up gamma values on boot while the screen goes off it makes the phone reboot over and over again until it finally catches up. As mbh87 mentioned, isn't there a way to delay this? I think a couple of options in your application to delay the gamma set up on boot (maybe 10 or 15 seconds) would heal this. Or, if there's a way to hard set (an option in your application to make it user friendly) color profiles so the application doesn't have to load them every time they phone boots. Either would be fine, I think.

I'd like to use your kernel again, Franco. Its performance and benefits are extremely good, the best I've come across so far.

Cheers
[Nexus 4 Original Android Development] BRKotucs:
Just wipe both caches and re flash the Rom.
[Nexus 4 Original Android Development] syncopy:
V6 was released for public some hours back. But I guess Franco has been rocking it for the past two weeks or so.

MiNCO doesn't have a N4 thread yet though.
[Nexus 4 Original Android Development] catlog:
Flash the zip for CM again and it will overwrite the kernel.
[Nexus 4 Original Android Development] derPianist:
I don't know why but battery life is getting worse for me. :(

via Google Nexus 4
[Nexus 4 Original Android Development] mobilehavoc:
Installed R18 on stock rom and no issues here very smooth and good battery life

:D
[Nexus 4 Original Android Development] immunityx:
Can you share link
[Nexus 4 Original Android Development] fluffenforliberty:
I also have a very choppy scrolling experience on the latest build of this kernel. Running the latest CM10.1 nightly.

Anyone that has tested this kernel and faux's kernel? Big difference between the both?:confused:
[Nexus 4 Original Android Development] Vanhoud:
R18 here running paranoid android.....NO JERKINESS ALL SMOOTH

Sent from my Franco'd Nexus 4
[Nexus 4 Original Android Development] catlog:
R18 battery life is great. But the scrolling is sork of jerky here. Other than that, it's good.
[Nexus 4 Original Android Development] Mancubus99:
I'm running the CM nightly which includes the kernel. I'm not sure if you can get the kernel as a separate download but you can check their site for it.

---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------

Call me crazy but after experiencing this device at its best I prefer smoothness to battery life. As it is now the tradeoff with the CM kernel is worth it. I'll keep checking back here on newer versions to see if this gets fixed.
[Nexus 4 Original Android Development] nibrwr:
http://minco.mobi/downloads/mako.html
[Nexus 4 Original Android Development] bongostl:
running fine for me.

my guess it's a CM thing....

Edit....

Never mind...

I'm on aokp and setting done jittery ness, too
[Nexus 4 Original Android Development] calanizzle:
It happens to me too, since the first version, I think is something with N4, it appears later on.. At first boot, screen wouldnt even show in BBS
[Nexus 4 Original Android Development] estallings15:
I think we blew up the download server.
[Nexus 4 Original Android Development] Redmed427:
Can anyone find a link of it? I can't :(
[Nexus 4 Original Android Development] estallings15:
Dude. It was in the post I quoted.
[Nexus 4 Original Android Development] Ballastatuz:
Because some apps like Google wallet don't want to work correctly and I'm getting more download errors since obtaining root.
[Nexus 4 Original Android Development] nibrwr:
Try Germany. 500KB/s for me