yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Net.silb:
Afaik it's from 0 to 100 not 1 to 100, so if you want all 4 cores on all the time (screen on of course...) just set high load threshold to 0 and you're good to go. If you want only 2 cores on all the time just set it to 100. Otherwise, as [MENTION=4928198]Arstoien[/MENTION] said the higher that value is, the "harder" it will be for 4 cores to be online.
[Nexus 4 Original Android Development] santeana:
AOKP PUB June 6. That was a clean install. But the problem has been there since May.
[Nexus 4 Original Android Development] thederekjay:
Hmmmm.. What distro are you using? Do you have your packages for your build environment setup correctly??
[Nexus 4 Original Android Development] aventu:
everything like this: http://xdaforums.com/showthread.php?t=2224142 + ccache

export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=../arm-eabi-4.6/bin/arm-eabi-

make defconfig franco_defconfig
make -j8
[Nexus 4 Original Android Development] thederekjay:
Honestly I don't know. I do know that the first defconfig in your command line 'make defconfig franco_defconfig' is redundant. Should read as this 'make franco_defconfig'
[Nexus 4 Original Android Development] aventu:
ok thx, I changed it, but I still get: "ERROR: modpost: Found 3 section mismatch(es)." I don't know what this exactly means :(
[Nexus 4 Original Android Development] thederekjay:
It means exactly as the warning states. If you're using ccache try clearing it and building again. Do 'ccache -C' before you build.

Edit: also what toolchain are you exactly using?
[Nexus 4 Original Android Development] aventu:
"git clean -d -x -f" and "ccache -C" don't help, I use: "https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6"
[Nexus 4 Original Android Development] thederekjay:
I'm seriously at a loss.. I have never had that error before. Maybe someone with more insight on this issue can offer more advice.

Edit: maybe try to reset. 'git reset --hard franco/nightlies' replacing 'franco' with whatever the remote is titled. Just note that this will loose any commits you have made and inline with upstream franco
[Nexus 4 Original Android Development] aventu:
Can you compile the latest source form github? Is it just me? :silly:
[Nexus 4 Original Android Development] thederekjay:
I forked a while back, basically inline with upstream. I have no issues at all.
[Nexus 4 Original Android Development] franciscofranco:
Which commits did I delete? I rebase some times removing patches that I don't use anymore or if they are too silly.

Its as annoying for you as it is for me that MIUI thinks its cool to change the Device name.

What is the branch you're trying to compile?
[Nexus 4 Original Android Development] aventu:
nightlies branch
[Nexus 4 Original Android Development] Stretlow:
Feedback...

Still keep reverting back to 148 but decided to give 155 a few days as the overall feedback on here seems excellent.

Its definitely smoother than >148 but i'm still getting scrolling lag in apps like Falcon pro that aren't present if I revert back to 148.

Stret
[Nexus 4 Original Android Development] zephiK:
I use falcon pro and have no lag while scrolling. Very large list of tweets too.

On R155 it's something with your set up. Did you clear app cache?
[Nexus 4 Original Android Development] Stretlow:
Pardon my ignorance but why do you need to clear the cache? I flash 148 there's no scroll lag, I flash 155 and its there, irrespective of how many times I do it.
[Nexus 4 Original Android Development] pac213:
What does the "Boost" means in governor control?
[Nexus 4 Original Android Development] JNewms:
He's answered that many times, it isn't a priority for him at the moment.

Sent from a Paranoid N4
[Nexus 4 Original Android Development] yokuyuki:
-93 dBm here although I'm on wifi so I'm not sure how signal strength would make that much of a difference. R22 reduced my wakelocks by 60% which isn't bad but still no nearly the idle time I'm used to from my prior phones. I suspect that I may sync more than most though: I have everything on except Play Books, Play Magazines, Play Movies & TV, Photos, and Google+. In addition, I have Latitude on and Google Now mostly enabled.
[Nexus 4 Original Android Development] stocovick:
Is it normal for the phone to get so hot after 10mim browsing xda forums? Using r22. And I don't know if it makes any difference but I'm in Rio and it's 35 degrees celcius here!
[Nexus 4 Original Android Development] republicano:
try next time without chrome, its currently a battery killer,and it does improve after a few cycles
[Nexus 4 Original Android Development] drawde40599:
Oh ,I've never had WiFi drop out , I no in the past with other phones , deleting the WiFi network , reboot and reinstall it has fixed issues . worth a try ....
[Nexus 4 Original Android Development] Prod1702:
read the main FAQ on the OP. Also you have over 1k posts and you still don't know how to search. There is over 300 pages of posts on this thread don't you think someone would of asked that already.
[Nexus 4 Original Android Development] drawde40599:
486

Raised min MHz to 486 . now were flying !! and Battery not taking a hit from it :) .
[Nexus 4 Original Android Development] Simer03:
Man... Vice city won't get past the loading screen any more!! Could this be kernel related do you think? Any way of me finding out?

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
It will go to max when there is enough load. I think its if the load is above go_above_hispeed_freq it will go to full.

Dunno if BLX is any worth here. I got so many things to see that I haven't got there yet.

I'll explain again: PGM is am proprietary module, its nothing to do with my kernel. When the developer has the module the app will inject the module into the kernel and load it up.

No S2W here. Its useless in my opinion and I'm not a troubleshoot centre if users would have problems ;)

During idle time cpu1, cpu2 and cpu3 are always offline because the hotplug driver cancels all the hotplug scheduled works. It resumes everything when the device comes out of idle (screen on).

UV comes later, not important to me at the moment.

Its just to make the governor a bit more aggressive I believe. I never used it though.

Yeah its only extra 25mV I believe so it won't drain anything really measurable :)

I don't see how it could possible be kernel related, thats all userspace stuff, I'm pretty sure Rockstar ****ed something up as usual. GTA3 was also a lame port.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Yea see I disable all that stuff I never use it. But I wish Google would just fix this in 4.2.2 already ya know.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2

---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------

Hmmm might try.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Vangelis13:
What's the worst thing that can happen if one only runs Performance governor..? For the rest stock values. It's flying nicely on that.. ;)
[Nexus 4 Original Android Development] Hrithan2020:
Sure, just wanted to bring it to your notice.

I know that, sorry if I didn't make myself clear. So, the main reason is that you just don't find it useful , plus to avoid unnecessary problems caused by adding the feature (similar to UV) and not because of the way it is implemented.

Thanks a ton for replying. :)

Sent from my GT-I9100
[Nexus 4 Original Android Development] cmikeh2:
Performance governor will keep your phone at max frequency at all times. Battery life will suffer and you'll probably hit thermal limits.
[Nexus 4 Original Android Development] drawde40599:
I'm at 594 min now , and its slamming into apps ,so fast , I ran gnex at 700 min instead the 350 so y not try here , ya no ;)
[Nexus 4 Original Android Development] Vangelis13:
Well, not really. Fairly cool & one core on max. That's not necessarily too bad I think. Race to idle and all that.

Don't know, I'll try it out. Phone is flying so if it's only some battery, who cares..
[Nexus 4 Original Android Development] drawde40599:
milestone

Franco once u hit a milestone u going to play with GPU over clocking ? I herd all bad about CPU oc but nothing on GPU . ( I no one thing at a time ;) just wondering)
[Nexus 4 Original Android Development] IAmAN00bie:
Race to idle doesn't really mean anything when your phone's screen is on... because the screen being on is a constant wakelock anyways.
[Nexus 4 Original Android Development] franciscofranco:
Nah, no need for any GPU overclock, this Adreno 320 is already pretty good, extra heat for some extra MHz is not worth it in my opinion :)
[Nexus 4 Original Android Development] Ballastatuz:
Right now I'm trying max 1350 min 369

Interactive

Go_high_load 75

Hispeed_freq 918

It feels pretty smooth. A little lag in the widget section of the apps screen. I wonder how the battery will last. I'll try shadowguns deadlzone in these settings.

Edit: was a little jittery so I put max back to normal.
[Nexus 4 Original Android Development] franciscofranco:
Hmm I build it everyday 0 problems.

This is the toolchain that I use: arm-linux-androideabi-4.6/bin/arm-linux-androideabi-

This is my build script:

make -j`sysctl -an hw.logicalcpu`

cp arch/arm/boot/zImage boot_img_dir/

cd boot_img_dir

mkbootimg_file=mkbootimg
cmd_line="console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677"
base="0x80200000"
ramdisk_params="--ramdiskaddr 0x81800000"

echo "making ramdisk"
./mkbootfs boot.img-ramdisk | gzip > ramdisk.gz
echo "making boot image"
./$mkbootimg_file --kernel zImage --ramdisk ramdisk.gz --cmdline "$cmd_line" -o boot.img --base $base $ramdisk_params
[Nexus 4 Original Android Development] nachordez:
148 and 155 have different settings and, even more important, defaults. When you change kernel, it's a good idea to clear fku not to keep previous version settings, but new version defaults. And later adjust what you need to (color, UV, etc). That could be the reason of your worst performance in 155

Try it

Nexus4 / Stock / Franco / V4A
[Nexus 4 Original Android Development] jebatkun:
[MENTION=470754]Franco[/MENTION], i like to ask..is the lag in android is from the os system itself or poor coding of app by develepor? i heard you got friend from google.if there any news about next os update?
[Nexus 4 Original Android Development] zephiK:
Because if you didn't wipe Franco Kernel app cache (its in the settings of the app) it could contain old governor control settings for above_hispeed_delay etc as well as hotplug control. Franco changes these settings around each new kernel release.

So by not wiping the app cache, it would be using old values for those functions causing lag. Yeah those values may work on that specific nightly, but there was a reason why Franco adjusted the values in a newer nightly as defaults for a reason.

Try it. It should fix your problem. Especially when r148 is using the OLD hotplug, and r150 and newer series uses a new hotplug algorithm so your app is probably setting old hotplug values with a newer algorithm so your cores may be powering off/on at the wrong times. Ultimately, leading to scrolling lag :)
[Nexus 4 Original Android Development] aventu:
aaah maan wrong toolchain :o not my day.. -.-

arm-linux-androideabi

thank you for your patience
[Nexus 4 Original Android Development] Stretlow:
I definitely will, makes sense in theory.

Thanks for your help chaps ... :good:
[Nexus 4 Original Android Development] Floydfire:
155 is almost the best but I had a data drop in 2g connected to WiFi for 2/3 times between today and yesterday .54 modem... But I can't say that is franco or modem problem... Because maybe it's carrier and my place that goes ****ty. We don't even have a good 3g cover...

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] eluspo:
Is bt working on axiom? Tried it but no bt.
[Nexus 4 Original Android Development] Utini:
so whats the right way to do it ?

wipe FKU cache

reboot

update kernel

?
[Nexus 4 Original Android Development] realfelix:
You can set that in the app. Under Settings.
[Nexus 4 Original Android Development] thebryceee:
Yessss. Tapatalk 4 finally has search within threads.
[Nexus 4 Original Android Development] nachordez:
In apps settings you can check an option to clean cache in next reboot.

Mark that. And then just install kernel and reboot.

Nexus4 / Stock / Franco / V4A

GT-P5110 / PAC / Dohllmen / V4A
[Nexus 4 Original Android Development] Cuzz1369:
I still really think Franco should add a clear app data and flash button all in one. Streamline things a bit.

Carbonized and francofied N4
[Nexus 4 Original Android Development] franciscofranco:
Nope, then some users will complain that their settings don't apply on reboot because they'll click on that without knowing what it does, and I get 1000 emails and 1000 0 stars.
[Nexus 4 Original Android Development] defffizz:
Can't wait to flash m3 :) any news?

Nexus 4, Paranoid Francoid
[Nexus 4 Original Android Development] franciscofranco:
News of what?
[Nexus 4 Original Android Development] aventu:
[MENTION=3292224]franciscofranco[/MENTION]

I have a little suggestion for the boostpulse:

/* we want cpu0 to be the only core blocked for freq changes while
we are touching the screen for UI interaction */
if (is_touching && pcpu->policy->cpu == 0)
{
if (ktime_to_ms(ktime_get()) - freq_boosted_time >= 1000)
is_touching = false;

if (new_freq < input_boost_freq)
return;

With following scenario: is_touching = true, pcpu->policy->cpu = 0, new_freq < input_boost_freq, current freq > input_boost_freq

Now the current frequency will stuck above input_boost_freq, because the governor wants a lower new_freq than input_boost_freq. For example it stucks at 1,3GHz, because it wants 500MHz.

So I changed the return with new_freq = input_boost_freq

/* we want cpu0 to be the only core blocked for freq changes while
we are touching the screen for UI interaction */
if (is_touching && pcpu->policy->cpu == 0)
{
if (ktime_to_ms(ktime_get()) - freq_boosted_time >= 1000)
is_touching = false;

if (new_freq < input_boost_freq)
[COLOR="SeaGreen"]new_freq = input_boost_freq;[/COLOR]
}

This seems more effective to me.

I also have a question how to "boost" a specific cpu core. In lge_touch_core.c I found:

static struct cpufreq_policy *policy;

if (policy->cur < TOUCH_BOOST_FREQ)
{
__cpufreq_driver_target(policy, TOUCH_BOOST_FREQ,
CPUFREQ_RELATION_H);
}

//and far away

policy = cpufreq_cpu_get(0);

Please correct me if I'm wrong, but it seems like that 0 is the first core? So could you choose the second core with cpufreq_cpu_get(1)?
[Nexus 4 Original Android Development] defffizz:
News about m3 coming out:)

Nexus 4, Paranoid Francoid
[Nexus 4 Original Android Development] Taxiback:
If they're to thick to understand that they shouldn't be flashing a phone. :P
[Nexus 4 Original Android Development] JNewms:
Why does it matter if there's an M in front of it? By being on nightlies you will get the same kernel. Just updated more often.
[Nexus 4 Original Android Development] defffizz:
I know, just want to rest from flashing stuff this summer, I've been flashing every single nightly until now

Nexus 4, Paranoid Francoid
[Nexus 4 Original Android Development] Cuzz1369:
Fair enough. I'd rather get a little frustrated Cuz I forgot to clear data than have you get frustrated and leave.

Carbonized and francofied N4
[Nexus 4 Original Android Development] franciscofranco:
Thats a good suggestion. We don't want the freq to be stuck at > input_boost_freq during touch interactivity if its not needed. Thanks, will add!

There are some other ways to get the policy from individual cpus rather than what I use, but this one is simple and doesn't require too much mumbo jumbo. To boost cpu1 you just have to create a new policy pointer like this:

struct cpufreq_policy *policy_cpu1;

then

policy_cpu1 = cpufreq_cpu_get(1);

And then repeat that if bla bla bla check for boosting.

Maybe in a week or something.
[Nexus 4 Original Android Development] Shano56:
Hi Franco, tried to get a logcat of the so called data drops. Happened 3 times, 4 bars mobile signal then none for a couple seconds. Interesting stuff should be near the end around 10:40 let me know if this link doesn't work

https://docs.google.com/file/d/0B0GEjZZe9zzyaUhRejJfYzdqcmM/edit?usp=docslist_api

Edit: that's on 154 without the patches. Maybe better on 155? Might not even be a kernel problem, who knows :p
[Nexus 4 Original Android Development] franciscofranco:
Thats pretty useful. Funny thing that happened with stock HSIC/modem/whatever drivers. What it seems to me s that the ks_bridge driver might've confunded a zero length package with a hardware disconnection or something then to correct itself it restarted the modem interface. Try r155.
[Nexus 4 Original Android Development] BakaPhoenix:
Franco will you add usb otg support in the future? (yeah i know that it needa y usb cable)
[Nexus 4 Original Android Development] franciscofranco:
Neps, can't risk problems coming out from that.
[Nexus 4 Original Android Development] :
Can anybody tell me what o3 optimizations and prima drivers are? I seem to have missed something.
[Nexus 4 Original Android Development] Shano56:
1) not sure probably different compiler/buzzword

2) some hacks/patches to help WiFi bugs. Causes issues for some/not official so its best to wait for a fix from google
[Nexus 4 Original Android Development] Raza Qadri:
Whenever I flash kernel on stock sometimes it suddenly stops receiving signals but kernel works well on custom ROMs it doesn't have this problem on them. Does that means I shouldn't play with kernels in stock ROM?
[Nexus 4 Original Android Development] franciscofranco:
1 - Second highest level of compiler optimisation flag. It tries to optimise the code during compilation time based on a set of flags inherent to the -O3 flag being checked. Read more: http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html It doesn't mean it will produce better or faster code, but it sure does increase the code size. From all my testing its a bit irrelevant compiling with -O3 or -O2, its more buzzwordy than anything else for Kernel compiling.

2 - Its the name of the Wi-Fi drivers for Mako.
[Nexus 4 Original Android Development] leets4uc3:
If I find a girl with a nexus running Franco kernel I am going marry her right there and then.
[Nexus 4 Original Android Development] psubadger:
Franco,

I had an earlier message about data/3g/cell signal drops (whatever you'd prefer to call it) in the ~140s releases that was fixed when I returned to M2. r155 seems to be much better with the signal drops. I still see the open triangle outline a few times in places that I usually have signal, but I still seem to be able to pull data, and I haven't dropped any calls while running r155 (not that I've had a ton of them, but I figured that I'd chime in). Thank you for the fixes, whatever they might be.
[Nexus 4 Original Android Development] meanwhile:
That would be my sister haha

Granted she didn't installed herself, but nevermind that little detail

Sent from microwave
[Nexus 4 Original Android Development] vjales:
Google, where are you with 4.3 or even a 4.2.3 with the fix for delayed notifications?? I can't wait anymore :(
[Nexus 4 Original Android Development] The Gingerbread Man:
Your in luck I found you one!
[Nexus 4 Original Android Development] italia0101:
Franco any clues to when that system monitor update is coming ? Its got some awesome features I'm dying for ...
[Nexus 4 Original Android Development] Cuzz1369:
4.3 is a myth like the Boogie Man or Michael Jackson.

Carbonized and francofied N4
[Nexus 4 Original Android Development] kecinzer:
There were many commits between Jun 07 and May 27 and just disapear :).

I start fresh and it seems that kernel running better now :).
[Nexus 4 Original Android Development] djenis:
This is why l love to have franco's kernel on my device- mako, no UV, stock franco's settings, stock android rom. Rock stable for me. Thanks Franco!!

Edit : nightly #155
[Nexus 4 Original Android Development] franciscofranco:
I think its coming today, not 100% sure though.

EDIT: just asked him, not today, he has something to fix on the Widgets first.
[Nexus 4 Original Android Development] ratcav:
You should
[Nexus 4 Original Android Development] Krunk83:
I've never gotten 4+ hours of SOT and I see it posted all the time. Frustrating.

Sent from my Nexus 4
[Nexus 4 Original Android Development] nyyankees1237:
Wifi or HSPA+? makes a HUGE difference in usage time.
[Nexus 4 Original Android Development] Cuzz1369:
I wouldn't worry about it. I enjoy using my phone more than posting silly screenshots to boost my low self esteem.

Carbonized and francofied N4
[Nexus 4 Original Android Development] nyyankees1237:
It's not about self esteem, what is this middle school? I would be pissed too if I couldn't use my modern smartphone for more than 4 hours.
[Nexus 4 Original Android Development] Cuzz1369:
No disrespect meant but sometimes it seems like a pissing contest to see how much screen time on you can get. People turn the brightness all the way down and let their phone sit there doing nothing just to post a screenshot. Who cares I use my phone balls to the wall all I want. I don't worry about stuff syncing in the background or brightness. I take full advantage of my phone and I'm on the same kernel as everyone else here and I get right around 4 hours. Sometimes less sometimes more. Just look at the screenshot a few posts back. The only thing on there is Facebook at 6%. That's not normal use for a full day.

Carbonized and francofied N4
[Nexus 4 Original Android Development] pkelly517:
So, if you can't spend 25% of your day staring at your phone, it's a bad day?

You should look up more.
[Nexus 4 Original Android Development] nyyankees1237:
I forgot it was illegal to often utilize something that I paid $300 for. My bad!

---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------

Completely understand where you're coming from, but why do people such as yourself have to put down people complaining about subpar battery life when obviously something can be done to assist that person in terms of advice. I'm not saying it has to be right here in this thread or in any thread for that matter as a simple Google search would do the trick. But when did the simple notion of trying to help someone become a contest of proving who doesn't give a **** more about babying battery life. You're just as worse as the people who brag about their screen times. No offense man.
[Nexus 4 Original Android Development] zelendel:
Ok guys enough. Look battery life is all about how you use the device. Well 97% of it anyway. I can have my device last me a day or I can kill it in less then 3 hours. It is all about how you use it
[Nexus 4 Original Android Development] Krunk83:
Both. Maybe someone has some advice that can help me. In not very savvy in the kennel department so I run it pretty much stock. I use syrup brightness, I only sync gmail, calendar, play music, data backup, and all Facebook notifications turned off. Gnow is in but my location updating is off.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Cuzz1369:
I wasn't trying to put him or anyone else down. I was telling him not to obsess over it. ENJOY YOUR PHONE

Carbonized and francofied N4
[Nexus 4 Original Android Development] nyyankees1237:
Try a full wipe, wouldn't hurt to try! Also, watch what apps you got running into the background. Some (cough cough Facebook and Google now) drain our phones quick. Try googling some stuff and I'm sure you'll find a solution. Also different combinations of kernels and roms yield different results. Good luck.

Edit: uninstall Facebook, use the mobile site. Also greenify Google now and maps.