yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] scream4cheese:
I just realized that. lol
[Nexus 4 Original Android Development] VacTacks11:
Just had a reboot when I clicked a link in Bacon Reader, then on the YouTube icon to make it the default app.

Log attached
[Nexus 4 Original Android Development] avink:
Hi,

Bit of a noob here. I installed r20 on stock ROM earlier today. While I was installing WhatsApp, the device rebooted unexpectedly. Only noticed this once and will keep an eye out on it but I was wondering how I would be able to provide more useful information if it reoccurred.

Did some searching:

What would be more helpful?

A logcat as per: http://xdaforums.com/showthread.php?t=1378491

or last_kmsg log like the above user got?

http://code.google.com/p/tegraowners-ics-rom/wiki/How_to_get_logs

If i understand correctly, I cannot get a logcat unless I had it reporting prior to the crash?

Thanks
[Nexus 4 Original Android Development] JNewms:
In the op it lists the folder in your phone to go to in order to provide the info he needs.

Sent from a Paranoid N4
[Nexus 4 Original Android Development] kyokeun1234:
If you're having problems, not only give last kmesg but also ROM you are using and kernel settings. That'll help Franco a lot :)
[Nexus 4 Original Android Development] avink:
Thank you both for your response. I just always read about people asking for logcat but I apologize for not reading op.

Here's the info.

Stock ROM 4.2.1 running r20 at default settings.

Last_kmsg at pastebin.com/pgyBXshx
[Nexus 4 Original Android Development] franciscofranco:
I sent the logs to Google, but thats not caused by interactive this time. Thanks for the logs.
[Nexus 4 Original Android Development] franciscofranco:
r21:

* Merged 3 patches from Qualcomm, one of them reducing voltage on the lower slot (384MHz by 100mV)

* Improvements on the Hotplug driver:

- Add BOOSTPULSE function call to the touch driver so that the device keeps 2 cores up when the user is interacting with the device.

- Only call CPU offlining if avg_running < disable_load/2, online_cpus > 1 and if BOOSTPULSE is not up

- Decreased the BOOSTPULSE unpause timing to from 5 to 2 seconds.

* Should be way more smooth when interacting with the device than before due to less hotplug calls and using 2 cores when touching the screen.
[Nexus 4 Original Android Development] kioshi:
Smooth so far on r21. With r18 & r20, was it only single cores running always? I would check randomly and see 1 core running set around 1.1 GHz.
[Nexus 4 Original Android Development] franciscofranco:
I was dumb and I forgot I had to call hotplug_boostpulse function from the touch driver in function that detected touch events, so before it was a bit random if the device onlined a second core during interactivity - now its done properly.
[Nexus 4 Original Android Development] Ibsonic:
And that was the warning from the logcat right? "Unknown path or function"

Great tanks mate for 21 !

Edit:

Finally where I was waiting for ! That hotplog setting with second core helped a lot.. Lagging in app like in tapa talk completely gone.. O m g ! Thanks !!

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] superbobup:
Dang. Using 1 core, scrolling was already amazingly smooth. Interesting to see how 2 cores does. I wonder how two cores at low frequency vs 1 core at a higher frequency compares for performance/battery...or is that not how r21 works? Seemed like the single core/high freq was already great :p
[Nexus 4 Original Android Development] Ibsonic:
Its craaazzyy fast ! System tuner shows all 4 cores working now.. That wasn't the case in r20.. Dang this one is naaiiisss

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] thuynh022:
Xda app still runs like ****. Everything else is wonderful though! Glad I bought your app. Your kernel is the only kernel I've used on my gnex and n4.
[Nexus 4 Original Android Development] benblb:
I actually do have bad signal quite a bit, but I can't do anything about that. (Come on, At&t!) Facebook I use but I wish I didn't, and location services should not be waking up the device much. Maybe once in a while for Google Now, but no more than that. Maps still likes to turn itself on when I unplug the device, but after one or two force stops it goes away. Is Facebook taking significant battery life or just coming on to say hi every so often? Thanks so much for reviewing my log!
[Nexus 4 Original Android Development] trailblazerz11:
What is the default go_hispeed_load? I never touched it before and noticed it was 60, just wanted to make sure before I ask:

I notice oscillation from 384 to 1000mhz even when phone is idle and no touch. Not a big deal but for some reason really bothers me. From github commits, the interactive patches state that go_hispeed_load should be higher than the default target_load of 90 to prevent oscillation.

Setting go_hispeed_load to 95 fixes oscillation, however so far definitely not as smooth obviously as 60 since it seems to simply stay around at 384 for general UI activity. And no response on frequency to touch. But will try these settings for a day or so

I assume BOOSTPULSE for hotplug(only control core online/offline) different than boostpulse for interactive:

BOOSTPULSE works fine, second core onlines on touch however a boostpulse on touch events(or input_boost?) for frequency would make sense to me for smoothness/interactivity rather than relying on a lower go_hispeed_load and having oscillations (though obviously you know more than me franco:)
[Nexus 4 Original Android Development] superbobup:
Try switching to edge if you have poor HSPA signal. Location services will turn on a lot especially since you use Google Now (I get something like 500 counts?) So it often polls your location. You can try setting it to "update location manual" or "do not update". Also, Facebook turns on its services (you can try disabling them, a few people mentioned apps other than autostarts) which seem to drain battery.
[Nexus 4 Original Android Development] techmatlock:
Turn off sync photos, vibrate, messenger location services, notification led, and lengthen refresh interval on Facebook. For network issues, enable 2g network only, turn off roaming, and try to use airplane mode. Turn off location reporting in Maps.
[Nexus 4 Original Android Development] Janne79:
Had that problem several times. Just keep on trying...
[Nexus 4 Original Android Development] aimcr7:
I don't have it, I even reduce hispeed to 1027 and touch boost to 702, and its still pretty smooth. :)
[Nexus 4 Original Android Development] xanthrax:
Chose the option to download only, reboot in recovery and flash it from there

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Planned.

There is an option to set voltages on boot since... ever.
[Nexus 4 Original Android Development] Cuzz1369:
Quick noobish question. If I dirty flash my ROM. Let it boot. Then flash a kernel through the app. Should I clear app data.

Edit: example, If I am one r139, flash rom w/stock kernel, then flash back to r139

Carbonized and francofied N4
[Nexus 4 Original Android Development] franciscofranco:
I think I nailed it. min_sample_time would get stuck in 500ms and that would do no good.
[Nexus 4 Original Android Development] :
I do it and it's ok. No need to clear app data.
[Nexus 4 Original Android Development] kara mustafa:
Almost all of the time everything is smooth but if I open an app after reboot it stutters, not always but sometimes. It is hard reproduce but this behaviour is present. With stock everything was fine. The kernel is smooth yeah with great battery but sometimes something stutters :P
[Nexus 4 Original Android Development] franciscofranco:
After reboot all the things you do for the first time will stutter, Android has to build back the caches...... Happens the same with stock Kernel. If you don't like this behaviour don't reboot that much.
[Nexus 4 Original Android Development] kerngehirn:
I mean delayed. Like trickster mod. When it loads the values on boot it's a little bit risky isn't it? When it's already booted, there's no risk anymore, right?

sent from my nexus4 with PA, not speaking English natively. so you're welcome to correct me anytime.
[Nexus 4 Original Android Development] Net.silb:
Awesome!

Forgive me if I'm wrong but it feels like you're kinda mixing the governor and touch boost Oo...

Shouldn't they be two separate or completely unified pieces?

I mean shouldn't it be that the governor controls its things and that the touch driver controls the touch boosting or that the governor controls everything?

And one more thing on my mind...

It seems that you've done some stuff that limits users to interactive governor like the dynamic scaling and the touch boost that only happen with interactive... If a user wants to use a different governor he would loose lots of the functionality of the kernel...

And one more thing, it seems that interactive governor has so many changes to it maybe it should be separate from the original interactive giving users the option to use it.

And one last thing, if values aren't actually configurable for example the scaling governor ones, shouldn't they be hidden and unchangeable for the user if they aren't actually configurable?
[Nexus 4 Original Android Development] franciscofranco:
r140:

* Merge a new patchset from Colin Cross to help on improving r138's Kernel Freezer patches

* Obvious optimisations in the Hotplug/Touch Boost path that I've been improving over time. Should save tons of CPU cycles (ditched constant multiplications for example)

* Fixed a bug where min_sample_time could get stuck with 500ms over time and that could lead to excessive usage of higher frets unnecessarily causing extra heat and extra battery drain

Thanks [MENTION=4354560]Net.silb[/MENTION] for reporting that bug and how to reproduce it.
[Nexus 4 Original Android Development] markd0wn:
Working nice so far.
[Nexus 4 Original Android Development] stankyou:
What? Still no sandwich maker? Booo! :D
[Nexus 4 Original Android Development] ManOnTheMoon:
I don't know how but somehow r140 downloaded automatically and I don't even have auto download and flash enabled.
[Nexus 4 Original Android Development] franciscofranco:
Sorry, I'm trying :crying:
[Nexus 4 Original Android Development] Net.silb:
Thanks for the answers and I think it's a good idea to leave only interactive governor.

Loving how you phrased your commit - "mako_hotplug: obvious code path optimisations. Also fix a bug where min_sample_time could get stuck to 500ms and that sucks."

Made me laugh... :laugh:

Everything seems good here with r140 no excessive jumping of frequencies because of touches but still some jumping and I think that's because of timer rate being to low... I think it should be raised.
[Nexus 4 Original Android Development] Haomuch:
The server get down again.
[Nexus 4 Original Android Development] Krunk83:
I'm still experiencing strange touch issues when immediately waking the phone on r139. I don't use a lockscreen and when I wake the phone and touch the screen sometimes it's unresponsive. Touching it again works fine. Also, immediately after waking the phone and touch the nav bar I get the google now swipe up animation or the notification drops down. Usually clearing the data in the Franco app fixes this, but only for a short time. Also, it's very random. Reboots also seem to fix the issue sometimes. Is this just happening to me or is this a known issue? Anything I can do to fix this? Thanks in advance

Downloading r140 now and I'll try that version.
[Nexus 4 Original Android Development] Vangelis13:
r140 mirror: https://mega.co.nz/#!KtAxTbyR!NWTsHjjOiKCDuDdwsJyAWXRxcOBumbDG29BsP6hI_94

Please don't quote on reply so I can take it down later.
[Nexus 4 Original Android Development] Redneck Trash:
Guess I snuck in before the rush.
[Nexus 4 Original Android Development] franciscofranco:
Try 35k.

Sent from my device
[Nexus 4 Original Android Development] mr xombie:
Just got the notification of 140.. And Let me guess... Server is hammered? lol.

Go flasherrr gooo..
[Nexus 4 Original Android Development] Net.silb:
First I need to disable dynamic governor scaling, whats the command to disable and to enable it?
[Nexus 4 Original Android Development] mjehan:
Any chance you could add this patch to a r666 test kernel and let users test it out to see the if the notifications bug has been fixed. The feedback so far seems positive.

Patch: https://www.codeaurora.org/gitweb/quic/la/?p=platform/vendor/qcom-opensource/wlan/prima.git;a=commit;h=d2345a53b804ec451d131c899d0f9f7f353dc10a
[Nexus 4 Original Android Development] techtium:
Thanks again for your work Franco.

Just a question, I see, in other thread, that someone use your kernel and applies a fix to resolve wifi problems (notification delay).

Do you work on this too, or you let that job to Google ?
[Nexus 4 Original Android Development] :
Let's see how franco answers this. I mean it would be funny but how much funny?....
[Nexus 4 Original Android Development] RussianBear:
Franco, any chance you could look into this log, please?

I'm having issues hooking the phone up to my pc via usb (mtp). It works on the stock AOKP kernel, but not on yours (also tried faux kernels). I can hear the sound when I hook it up, but nothing shows up in "my computer." If i clear the media cache/data, the error goes away, but I can't see the phone still.

Much appreciated!
[Nexus 4 Original Android Development] nikeman513:
Hey Franco, been using your work since Galaxy Nexus days and of course have bought your app! I have a request, can you please make a dedicated download server for paid Franco update users? I've been having issues with downloading through the updater app for a couple weeks now.

Thanks
[Nexus 4 Original Android Development] Vangelis13:
That is not allowed according to xda rules. #edit#: I think at least.

Would also be unfair in my opinion. (P.S. I have bought the app)

Issues will be fixed, patience is a virtue.

P.S. There's always some mirror posted if there are problems with the minco server, just scroll up a few posts.
[Nexus 4 Original Android Development] dapsANDpoundz:
Still showing r139 as most recent nightly for me in fku.
[Nexus 4 Original Android Development] igalmarino:
I always clear FKU data after flashing FK to get the kernel default settings.

Sent from my Nexus 4
[Nexus 4 Original Android Development] snak3ater:
I also experienced this thing today.Saw 140 as latest nightly in my phone.I thought that it might be a mistake.But then confirmed it from xda.How it happened without me noticing it..No idea at all :D
[Nexus 4 Original Android Development] sigma392:
There's already a thread for this in the Android Development section.
[Nexus 4 Original Android Development] inzaghi75:
I want to update to r140 and the download is too slow.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] kara mustafa:
140 seems to be smoother than 139?

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] yethz:
Server hammered bigtime :confused:

I only get 6kb/s download.. Thankfully its only 5mb kernel.

And its really worth a wait.

Thanks franco.

° Sent via Nexus 4 with Tapatalk

° Rom: AXI0M (ODEX) / Kernel: Franco #138
[Nexus 4 Original Android Development] drawde40599:
Works just fine on 4 different computers i just tested for "u" just now, im on aopk and buikd 140 now but worked fine as sposed to on 139 also... Maybe it is the kernel but no issues here...
[Nexus 4 Original Android Development] kara mustafa:
Definitely 140 is smoother :D

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] RussianBear:
I find this very odd, indeed. Nothing changes, other than the kernel reflash. Thanks for checking!
[Nexus 4 Original Android Development] ki2luminati:
Im gonna wait a bit with 140. Damn the server is taking a beating!! ;)
[Nexus 4 Original Android Development] drawde40599:
Have u tried to FULL wipe, if i was u and out of ideas i would backup phone and full wipe install rom and this kernel and see if something changed.... If no change u could always reinstall your backup in few min like it never happend :P
[Nexus 4 Original Android Development] italia0101:
Agreed 140 is smoother
[Nexus 4 Original Android Development] RussianBear:
Good point. It doesn't bother me that much to do it yet lol just thought Franco might spot something right away in that log.
[Nexus 4 Original Android Development] ajayshah95:
r140 mirror:

http://www.mediafire.com/?tvl5uzqka713n7i
[Nexus 4 Original Android Development] Banished Angel:
I'll let you know how r140 runs next week when it finishes downloading ;)
[Nexus 4 Original Android Development] mammenj:
MD5: 8ec2b7a8b98cf2e7b1027838d97174c1
[Nexus 4 Original Android Development] fkrone:
Downloaded r140 via app (zip), chose flash and ... bootloop :(

Even flashing an older version or wiping cache/dalvik does not help.

So for now wish me a happy recovering.
[Nexus 4 Original Android Development] MonztA2:
Does franco store the MD5 hashes on his server somewhere (publically accessible)?
[Nexus 4 Original Android Development] exb0:
Strange. I flashed r140 the same way and its fine for me..
[Nexus 4 Original Android Development] madgooner2810:
Can anyone tell me what the hell just happened with my phones battery? It was showing 14 % when I put it on charging and 2 minutes later it is showing 100%. Is this kernel related?
[Nexus 4 Original Android Development] Banished Angel:
Reboot your device and try clearing battery stats.
[Nexus 4 Original Android Development] X DoZ3R:
Today i got a random shutdown. Using camera for a while and after usb for few min. I unpluged and and the phone completely shut doen and dont even turn on. I have to connect ac charger and after a minute of charging, the charging icon appear... Is it caused by -100 mV uv or its an other problem?

Ty

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] ceejay83:
Can't help you with no log
[Nexus 4 Original Android Development] italia0101:
Man a -100 makes a ton of diff....

I was playing beach buggy on the charger without uv , as I forgot to apply after a reboot.

Was keeping an eye on temp while playing, easily reached 75/80 ...

With -100 it reached 65
[Nexus 4 Original Android Development] Step-han:
Wipe battery stats is placebo.
[Nexus 4 Original Android Development] X DoZ3R:
I know its a noob q but how to make log ?:)

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] Dan53:
[MENTION=4354560]Net.silb[/MENTION]

To disable:

echo "0" > /sys/device/system/cpu/cpufreq/interactive/dynamic_scaling
[Nexus 4 Original Android Development] Vangelis13:
http://xdaforums.com/showthread.php?t=1726238

F maybe should stick it in the op..
[Nexus 4 Original Android Development] :
Google is your friend, search for logcat or search playstore for logcat apps
[Nexus 4 Original Android Development] Redneck Trash:
I should really just bookmark this. Clearing battery stats isn't going to help with anything.

https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
[Nexus 4 Original Android Development] brian88:
Charging time too long in r139 and r140. Does it relate to the kernel ??? It takes me about 4h or more to charge fully

When I came back to r137 or r666 this issue disappear

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Net.silb:
The terminal isn't accepting this command :(
[Nexus 4 Original Android Development] Dan53:
To disable:

echo "0" > /sys/devices/system/cpu/cpufreq/interactive/dynamic_scaling

Sorry about that!
[Nexus 4 Original Android Development] franciscofranco:
App update will have all those options. Hope to have time to finish the code today, will have lots of cool stuff.
[Nexus 4 Original Android Development] kpyhere:
[MENTION=470754]Franco[/MENTION]

Do you need some server space for the kernel? I can supply if needed.

The download speed is terrible.
[Nexus 4 Original Android Development] pikachukaki:
Cant wait!!!
[Nexus 4 Original Android Development] Net.silb:
Just one problem...

I disabled the dynamic scaling to test if changing the timer_rate to 35000 will solve the jumpy frequencies but now the min_sample_time is stuck at 500000 making the frequencies jumpy anyways... Keep this problem in mind when adding that option in the app... Remember to ensure that the min_sample_time scaling isn't affected by this toggle...
[Nexus 4 Original Android Development] dapsANDpoundz:
Man. Sorry to say but as good as this kernel has gotten performance wise, which has been very noticeable, battery life has been underwhelming in the last few builds for me. Before I could say well at least it gets me through the day, but at this rate its not gonna even do that anymore. Dunno what it is because I have no significant wake locks and my usage patterns remain the same. Hope the battery life returns to what it was before because what I'm getting now is depressing. I do appreciate the work you put in though.
[Nexus 4 Original Android Development] nellisere:
I'm using the latest FKU but I'm still having issues with it taking ages to fetch the lastest kernel version, and also issues with downloading slow and MD5 mismatch, using a 12Mbps WiFi and also tried mu 7Mbps 3G both taking ages! Is this still a server issue?
[Nexus 4 Original Android Development] DvTonder:
Just a quick comment - to quote Steve Kondik, May 15 10:27 PM

We discovered the problem via a feature but reverting it was done as a result of Qualcom's actions with the same commit and had nothing to do with us trying to fix a userspace problem.
[Nexus 4 Original Android Development] franciscofranco:
min_sample_time doesn't scale anymore when the toggle of dynamic_scaling is off. Something is wrong there.

Initially I thought CM was just reverting it for some reason, but I already learned CAF reverted it, so I will do that.
[Nexus 4 Original Android Development] Net.silb:
I'll try again...

---------- Post added at 06:05 PM ---------- Previous post was at 05:57 PM ----------

That's the problem! It should continue to scale when the toggle is off. Otherwise it will remain 500000 until its set differently by the user. It should be separate from dynamic scaling, because its related to touch and not to the dynamic scaling. You should make a separate toggle for min_sample_time on touch event scaling. For example, I want dynamic scaling off but I still want min_sample_time to scale when I touch the screen and to scale back when I don't touch the screen...
[Nexus 4 Original Android Development] Dan53:
If I get what you're saying, I think the issue is just that the governor has already scaled the tunables, so when you disable dynamic scaling, the tunables stay where they are. So something simple like resetting the tunables to default when dynamic scaling is disabled should work?

Not sure if this is what you mean though..
[Nexus 4 Original Android Development] Net.silb:
That too but even if I disable dynamic governor scaling I still want min_sample_time to go to 500000 when I touch the screen and for it to go back down to my set value after, which doesn't happen now...

---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------

And I also found that with timer_rate at 50000 there are only load related jumps in frequency which is normal, unless of course the user is interacting with the screen...
[Nexus 4 Original Android Development] lowert:
Is there anyone who uses the latest r140 with lates(22) PA?How is it going?
[Nexus 4 Original Android Development] sir*mez:
I also turned off dynamic scaling and I found out I had to use a init.d file to input my values at boot up with "sleep 25" cause they wouldn't stick otherwise.
[Nexus 4 Original Android Development] PetritH:
Im gonna try now.. downloading the latest PA, but r140 with (may19 PA) is going snappy... doubt there will be any difference.
[Nexus 4 Original Android Development] habskilla:
Headset Gain value, in what file is the value stored?
[Nexus 4 Original Android Development] eddy4823:
Custom Kernel settings. if you're talking about the app.