yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] icethegreat:
anything is possible when you believe :highfive:

:rolleyes:
[Nexus 5 Original Android Development] Tzfardaya:
Links or it didn't happen... :p
[Nexus 5 Original Android Development] ConMcCRay:
Its in this ROM, I have NO idea how he did this

http://xdaforums.com/showthread.php?t=2799573

[ROM][Android-L][SUNGSONIC HD >>> SSHD-ALV-1-Hammerhead]
[Nexus 5 Original Android Development] Tzfardaya:
I see... looks less like a complete custom rom and more like stock L with aftermarket bolt-on's....
[Nexus 5 Original Android Development] ConMcCRay:
I just wanna know how he changed the kernel fr tho
[Nexus 5 Original Android Development] fatspirit:
sungsonic = sampana (:
[Nexus 5 Original Android Development] wildestpixel:
kernel isnt modified, the boot image is, specifically a flag or two set in ramdisk to help root adb access.

kids stuff lol
[Nexus 5 Original Android Development] zephiK:
Hm I see on FKU, r55 is out.

No changelog just yet... flashed it just fine and about phone says #55.... imminent franco post maybe?
[Nexus 5 Original Android Development] franciscofranco:
Yeah, I was writing the change-log :)

Sorry for being absent in the last 1-2 weeks, I've been completely out of time and with the I/O and other events happening around here my free time was null. Finally was able to catch on stuff this weekend.

About r55 I'm very interested in battery results with it so give it a full cycle and let us know how it went.
[Nexus 5 Original Android Development] blueren:
Not going L's way unless there is a Google official release and a franco kernel running on it :D
[Nexus 5 Original Android Development] DesertVelo:
Looks like changelog has been posted in FKU:

- Improvement! Changed how the frequencies are calculated based on cpu load. The driver will now choose more fairly which frequency it will use, and it's much more sensible to low load scenarios so that you will feel your device as smooth as possible

- Improvement! Added unmerged ramdisk code from 4.4.3 which will improve Wi-Fi performance

- Improvement! Merged improvements from upstream
[Nexus 5 Original Android Development] jnr21:
Does this work with slimkat (latest weekly)?

Edit: yes
[Nexus 5 Original Android Development] 11wallace11:
Hi Franco,

I downloaded and flashed r55, and ran a few tests on performance. Since I've been playing a little bit with some custom themes, my interface became a little laggy. I tried the stock kernel that comes with Mahdi, and a couple of versions of this one (one of them is r34, which saved me a few times), however, with this version all the modified heavy transition animations, opening new apps, scrolling on heavy websites (oh it used to be a nightmare!) and even the worst of Android - the recents panel (I prefer Slim Recents, but I also tested the original one) - everything works perfectly.

For me, this version is considered as a milestone. I really hope that battery life will also stay loyal to my definition [emoji12]

Thank you very much, and keep up the great work you're doing!
[Nexus 5 Original Android Development] iPsychoGeek:
Does r55 use 300MHz frequency?

Отправлено с моего Nexus 5 через Tapatalk
[Nexus 5 Original Android Development] RobbieL811:
[MENTION=3292224]franciscofranco[/MENTION]. Is your hammerhead ramdisk on Got current? I saw in the r55 changelog that you made some WiFi changes in the ramdisk, but I don't see any commits?

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
What do you think?

Maybe I forgot, I'll re-push.
[Nexus 5 Original Android Development] fonephanatic:
Excuse my ignorance as I'm somewhat new and just trying to get used to some terminology

But does that mean that those latest WiFi changes didn't make it into build 55 or the commits were just not visible to public on your github?
[Nexus 5 Original Android Development] zephiK:
The wifi changes are already in r55. Franco just possibly didn't push the commit (or during the push it didn't include the commit for it so it didn't appear on source) on sources but during compilation of the kernel, the wifi change is in there.
[Nexus 5 Original Android Development] mhardyman:
Clear as mud...
[Nexus 5 Original Android Development] franciscofranco:
It's not really Wi-Fi specifically related but more about TCP, which affects any internet communication, just thought I would write in the change-log that is Wi-Fi to prevent users to be confused...
[Nexus 5 Original Android Development] DonXoB:
At first I want to thank franciscofranco for the great work on this kernel.

After autoflashing the last times with franco updater, all my paid apps were gone (including franco updater). If I flashed the kernel with TWRP directly the problem wasn't there. With the newest kernel/updater combination the problem doesn't exist anymore on my device. But I tried to logcat because I wanted to give feedback. The described problem was gone just in this moment :)

I saw another entry in the log wich could be kernel related: I get lots of errors concerning auditd:

build.board: hammerhead
build.bootloader: HHZ11k
build.brand: google
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: hammerhead
build.display: carbon_hammerhead-userdebug 4.4.4 KTU84P 5d40c83939 test-keys
build.fingerprint: google/hammerhead/hammerhead:4.4.3/KTU84M/1158763:user/release-keys
build.hardware: hammerhead
build.host: nas
build.id: KTU84P
build.manufacturer: LGE
build.model: Nexus 5
build.product: hammerhead
build.radio: unknown
build.serial: 034280a3251d47fe
build.tags: test-keys
build.time: 1403941596000
build.type: userdebug
build.user: arrrghhh
version.codename: REL
version.incremental: 5d40c83939
version.release: 4.4.4
version.sdk_int: 19

06-30 10:33:22.132 I/auditd (13611): Starting up
06-30 10:33:22.132 E/auditd (13611): Failed on audit_set_pid with error: Protocol not supported
06-30 10:33:22.132 I/auditd (13611): Exiting
06-30 10:33:27.142 I/auditd (13615): Starting up
06-30 10:33:27.142 E/auditd (13615): Failed on audit_set_pid with error: Protocol not supported
06-30 10:33:27.142 I/auditd (13615): Exiting
06-30 10:33:32.142 I/auditd (13618): Starting up
06-30 10:33:32.142 E/auditd (13618): Failed on audit_set_pid with error: Protocol not supported
06-30 10:33:32.142 I/auditd (13618): Exiting
06-30 10:33:37.162 I/auditd (13622): Starting up
06-30 10:33:37.162 E/auditd (13622): Failed on audit_set_pid with error: Protocol not supported
06-30 10:33:37.162 I/auditd (13622): Exiting
06-30 10:33:42.182 I/auditd (13625): Starting up
06-30 10:33:42.182 E/auditd (13625): Failed on audit_set_pid with error: Protocol not supported
06-30 10:33:42.182 I/auditd (13625): Exiting
06-30 10:33:42.642 I/dalvikvm(10722): Jit: resizing JitTable from 4096 to 8192

As I mentioned earlier: Thank you for your hard work. I hope the log is useful for u.
[Nexus 5 Original Android Development] granets:
Had the same issue on Mahdi rom. Bet you are using it, that's why you had that issue.
[Nexus 5 Original Android Development] armymax:
When I play for a while the cpu goes throttling. And it' s ok. But when temperature goes down and iven if the phone is in deep sleep for the night, the cpu will not return to standard frequencies. I have to reboot. Is it normal?
[Nexus 5 Original Android Development] Mr.Jay:
The vibration amp by default in Android it's 63, but in this kernel it's 100, what's the different between this two parameters? More or less battery life maybe?

Nexus 5 || Android 4.4.4 || Paranoid Android
[Nexus 5 Original Android Development] californicated:
It's pretty simple. A higher value gives you a stronger vibration
[Nexus 5 Original Android Development] Mr.Jay:
And a stronger vibration gives me more or less battery life? ?

Nexus 5 || Android 4.4.4 || Paranoid Android
[Nexus 5 Original Android Development] fredfox_uk:
Weaker or stronger vibration seems more likely.
[Nexus 5 Original Android Development] eddiehk6:
You can solve this question by logic...

A stronger vibration...requires more energy...therefore uses more battery...

How much it really affects your actual overall battery life is likely very minimal though, unless your device is vibrating constantly all day.

As with any battery life optimising, proper things like your screen brightness and how you actually use the device are more important than worrying about whether your vibration strength is 63 or 100...;)
[Nexus 5 Original Android Development] Chaplan:
Flashed r55 and both core 1 and 2 never stay on 300MHz. Back to r54 and it does stay on 300MHz. Is this an improvement or should it not be this way at all?
[Nexus 5 Original Android Development] WatsonDue:
Well, r55 is definitely smooth! Very nice improvement, thanks Franco!
[Nexus 5 Original Android Development] Bluewall:
Experiencing the same here, maybe it's on purpose, we have to wait for Franco's answer :P
[Nexus 5 Original Android Development] Technecium:
I'm gonna go out on a limb here and not wait a full cycle and say that since flashing r55 the cpu seems to suffer from hyperactivity and since it cannot seem to sit at 300MHz for more than a second, the battery results will be quite bad.

Something is not right.
[Nexus 5 Original Android Development] EnricoTFYKD:
It should be part of the new way the governor calculates the frequency required on the load. However, I think it is a little too aggressive on light loads (when on system monitor, just showing the CPU frequency graph, I see the CPU jumping all around from 346 to 730MHz on 1-4% loads, whereas on r54 it would stay dead on 300MHz).
[Nexus 5 Original Android Development] jfim88:
Installed r55 and FKU says the max freq is 1574... I need to change?

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] tacx:
I don't know if it's from the kernel but i can't activate ART. It reboot's but still Dalvik. I cleared cache and dalvik cache, but still i can't activate it. Any tips?
[Nexus 5 Original Android Development] EdgA#1:
do u use xposed!?
[Nexus 5 Original Android Development] choosetobelieve:
I noticed the same thing.
[Nexus 5 Original Android Development] HamsterHam:
Answered many times in this thread.

Thermal throttling. When your cpu cools it'll go back up.
[Nexus 5 Original Android Development] choosetobelieve:
Hi guys,

have you tried linaro kernel which is a modified kernel based on franco kernel?

I saw the post keeps updated as soon as Franco releases a new release. Some functions from that kernel are interesting.
[Nexus 5 Original Android Development] LeJolly:
Wrong thread, go to the linaro kernel thread :)
[Nexus 5 Original Android Development] bleuxeon:
I have had multiple time where CPU's max frequency stay @ 1574 and didn't return to stock value even with CPU was only 33°C for more than 20 mins.
[Nexus 5 Original Android Development] tacx:
Yes!? That's why... I just read more about xposed and ART, didn't think about that... :). Thanks for your support! ;)
[Nexus 5 Original Android Development] redsmith:
Same thing here too.
[Nexus 5 Original Android Development] Technecium:
I wanted to add that the kthread commit seems to be a definite keeper! Nice find.
[Nexus 5 Original Android Development] snorfu:
I' ve noticed this too!
[Nexus 5 Original Android Development] blueren:
I've had this multiple times before. Just sad that the root of this behavior was very difficult to get to. I've not seen it happen lately though (r50+)
[Nexus 5 Original Android Development] Mr.Jay:
Hey, I'm having reboots when playing videos on YouTube, what can I do for solve that issue? I'm running r53 and I'm on ART

Nexus 5 || Android 4.4.4 || Paranoid Android
[Nexus 5 Original Android Development] zephiK:
Upload a last kmsg... You should probably update your kernel as well.
[Nexus 5 Original Android Development] RobbieL811:
This is intended. If you look at Github, Franco has changed Interactive around a little bit. Supposed to make the device smoother with no cost to battery. He wants feedback on battery life. Run it for a few cycles and see how the battery life is & report back.

Sent from my Nexus 5
[Nexus 5 Original Android Development] jfim88:
The r55 is really smooth!!! Working great so far!

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Stevemeister:
[MENTION=3292224]franciscofranco[/MENTION]

All my recent recorded videos display a green line on the left of the screen. Could this be kernel related or is it ROM related (I'm on PA)?

Seems CM users have it too and myfluxi commited this fix: http://review.cyanogenmod.org/#/c/67136/.
[Nexus 5 Original Android Development] jfim88:
It is Rom related (PA)... You can fix it easily...search on the PA topic or their G+ community... Or wait to next release (today???)...

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] justibasa:
So seeing all the stupid questions asked in this thread over and over and over again, are we not supposed to use common sense in this thread anymore?
[Nexus 5 Original Android Development] redsmith:
Yep, that's what I noticed. When the screen is on, the CPU frequency fluctuates a lot, but I must say I really feel everything is smoother than usual. No lag anywhere, almost as if this thing were running on performance governor. So far battery life is holding well, but maybe because I have a Deep Sleep of 78% of total uptime.

Will report later when this cycle is over.
[Nexus 5 Original Android Development] RobbieL811:
Yeah. I'm using a little bit modified version of FK, but it's mostly the same. It's running really good for me too. No lag anywhere. Battery life for me also seems to be pretty close to what it was before. I might have lost a little, but not much.

Sent from my Nexus 5
[Nexus 5 Original Android Development] tlrsax54:
I'd echo that, every once in a while I would notice micro stutters when scrolling but haven't noticed it nearly as much since flashing yesterday. Tapatalk and facebook scrolling is very good and those are usually problem apps haha!
[Nexus 5 Original Android Development] Tzfardaya:
No, we are... But unfortunately common sense, like common courtesy, is no longer very common....
[Nexus 5 Original Android Development] Red5:
Its become common place to not use common sense, since awhile ago.
[Nexus 5 Original Android Development] Langduscher:
Doesn't work with AndroidL. Nor CM.

Fix plox, Francisco!!
[Nexus 5 Original Android Development] Tzfardaya:
Need to talk to cm about making themselves compatible with Francisco's kernel, and he is waiting on the kernel source from L to work his magic...
[Nexus 5 Original Android Development] simonarturo:
Sarcasm detected
[Nexus 5 Original Android Development] Langduscher:
He's too slow!! I paid for his app!!

---------- Post added at 07:29 PM ---------- Previous post was at 07:29 PM ----------

Nooooo ?

---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------

Nooooo ?

---------- Post added at 07:30 PM ---------- Previous post was at 07:30 PM ----------

Nooooo ?

---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------

Nooooo ? too bad.

---

Seriously. I can't drain my battery. What gives??

---------- Post added at 07:32 PM ---------- Previous post was at 07:32 PM ----------

Nooooo ? too bad.

---

Seriously. I can't drain my battery. What gives??
[Nexus 5 Original Android Development] Tzfardaya:
Heh, so you can complain about his app not working on L only cm, if you paid for his kernel you got scammed...
[Nexus 5 Original Android Development] myfluxi:
It's kernel related.
[Nexus 5 Original Android Development] Tzfardaya:
It's development related...
[Nexus 5 Original Android Development] Langduscher:
Really?

Luckily my Pro paid Tapatalk app sends my replies 100x

He'll know.

Scammed twice :|
[Nexus 5 Original Android Development] Langduscher:
So

How do I drain my battery? It's ridiculous.

Fix it!!
[Nexus 5 Original Android Development] Tzfardaya:
But, since L and cm are both off label use of his app, he'll probably just tell you to sod off.. (my words, he'll be a little more polite about it...)
[Nexus 5 Original Android Development] simonarturo:
Really? Why does it happen only on the latest PA stable version? (that I know of)

It's been acknowledge by the PA users on their thread, and you can also find a fix (which is only adding a camm file into system/lib) in there.

How is it kernel related?
[Nexus 5 Original Android Development] Tzfardaya:
Because he said it is... :P
[Nexus 5 Original Android Development] Langduscher:
I pay & he tells me to fcku off?

Come in [MENTION=3292224]franciscofranco[/MENTION]. I pay so fix AndoidL :D

I WANT TO DRAIN MY BATTERY

(yea I'll stop here - 0 complaints, pure awesomeness )
[Nexus 5 Original Android Development] Tzfardaya:
He'd be polite about it, so that's something...

Easy way to drain your battery, set min/Max CPU freq to 2ghz and leave the screen on with 100% brightness... Battery drains.
[Nexus 5 Original Android Development] Langduscher:
You're patient man! I was mocking about.

Only true complaint I have is that I can't have a test kernel showing off I have a release ahead off the original release :D
[Nexus 5 Original Android Development] Tzfardaya:
I know... ;) and yes, I am a patient man.... It's tolerance that I lack... :P
[Nexus 5 Original Android Development] myfluxi:
Ah, ok. Are you talking about this monster green line?

https://paranoidandroid.atlassian.net/browse/AOSPA-593

Because ours (CMs) is much thinner and kernel related.
[Nexus 5 Original Android Development] simonarturo:
Yup! that's the one! Only started happening after installing the 4.4.4 PA release and the fix was reverting a system/lib cammservice file to the stock version.

Didn't know it happened as well on CM. Since I'm not a user I wouldn't know, but its interesting to know that. Goes to show you that developers never have it easy.
[Nexus 5 Original Android Development] imageMaster:
The same problem on Mahdi, as usual.
[Nexus 5 Original Android Development] Tzfardaya:
Sounds like it might be time to take the issue up with a Mahdi dev...
[Nexus 5 Original Android Development] Mr.Jay:
I'm having random reboots, here's the last kmsg https://www.dropbox.com/s/80d5vz4s9vjs7h7/last_kmsg

Nexus 5 || Android 4.4.4 || Paranoid Android
[Nexus 5 Original Android Development] Arstoien:
With r55 compared to r54 the higher frequencies are used a lot more. 300 is almost not used (lowest most used is 345). And the highest frequency is used a lot more (about 50–100% more). Also when just sitting on the homescreen the frequencies are all over the place, very often ramping higher than hispeed freq – going often to 1.2 GHz, and sometimes to 2.0 GHz.

Can't say anything about battery life because my daily usage is too inconsistent to compare. Also I'm running ART and don't notice any lags so both versions for me look equally smooth.
[Nexus 5 Original Android Development] cubandanger05:
I went back to r53 after r54 was draining my battery a lot faster (granted I made no modifications to the CPU settings). Reversed placebo perhaps?
[Nexus 5 Original Android Development] simonarturo:
Seeing the same thing with frequencies, they used to sit a 300Mhz when idling and now are all over the place, minimum being 346 instead of 300. Is it by design?

Will have to give it a couple of days of use in order to compare battery life
[Nexus 5 Original Android Development] Tzfardaya:
Asked before, answered before, see following quote...

Seriously people, please search the thread/forum before posting questions...
[Nexus 5 Original Android Development] franciscofranco:
As I said on the changelog post I know exactly how the frequencies are behaving. The thing is the system monitor apps only show info every 1 second but frequencies change every 30ms. The idea with this calculation is that the device reacts faster to smaller load changes.

Just use it without thinking too much about how it's behaving.
[Nexus 5 Original Android Development] Laggalot:
I was always curious as to why we cant have this in the deeper settings like touch input ...... Is there any reason it cant?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Juzman:
Fresh flash of PA 4.4 final and r55. Battery is awesome. Only lost 5% overnight. :)
[Nexus 5 Original Android Development] franciscofranco:
Truthfully, because I'm a bit lazy :)
[Nexus 5 Original Android Development] Laggalot:
:D Thank you for being honest ! well many people might be just as lazy as me and typing those numbers is a pain in the ass , even though it isnt even close to what I'm expecting from you , was just letting you know that i miss such a feature ^^

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
I would have went with "too busy lately to implement across the board..."
[Nexus 5 Original Android Development] Playe:
Quick question: Recently I flashed furnace kernel to try out the gamma corrected brightness and noticed that its default max clock was 2.7ghz and my phone ran fine. However on franco, I can't get any higher than 2.4ghz or it reboots. Double checked and all frequencies were at the same voltage too. I have no desire to overclock but I was curious why this is if anyone knows.
[Nexus 5 Original Android Development] Laggalot:
it could be, because the kernel uses higher voltings ... only thing i can think of !

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
Do you compare the overclock voltages as well? I remember Franco saying he was just guessing with his overclock voltages and we would probably need to raise them further for stability...
[Nexus 5 Original Android Development] jfim88:
r55 is awesome in smoothness!!! Loving it!

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Playe:
That's what I thought too but I raised franco voltages to the same as furnace and still reboots. My wild guess it that maybe only core 0 could run at the higher frequencies but the rest could not.
[Nexus 5 Original Android Development] Tzfardaya:
Hmm, no all the cores should be able to handle the freq, try raising the Franco voltages 100 above furnace...

Also, is it an instant reboot, or does it run for a bit at the higher freqs? Perhaps you're blowing past a thermal cutout and the device is shutting down/rebooting to protect itself... Pastie/pastebin a last_kmesg for us to look at after the oc reboot.
[Nexus 5 Original Android Development] Arstoien:
I'm using the flying monitor with update frequency of 0.1s. But even ignoring the real time monitoring, the stats show that higher frequencies are used a lot more than before and the device now doesn't even go down to 300 MHz. Just doesn't seem too balanced to me, that's all. Btw battery life can't be unaffected by this – waiting for some reports from users with more consistent daily usage.
[Nexus 5 Original Android Development] Playe:
Yeah thats what I thought just a guess... Anyway tried raising the voltage even more still instant reboot. I have no desire to overclock just curious on why its happening. I can still post last_kmesg it you want tho.

Edit: http://pastebin.com/K41FadFT
[Nexus 5 Original Android Development] Tzfardaya:
Well, here's one report... 8hrs on battery, 3hrs 20 min sot. R55 kernel... Stock tunes, one of the better battery times I've seen considering my usage (currently at 13% bat)
[Nexus 5 Original Android Development] pkelly517:
You seem to be running the new kernel now.

Why don't you base your decision on YOUR report, after a few days of YOUR consistent usage (and not watching the flying monitor).

Seriously, a couple of charge cycles on your device will be far more telling than what anyone else claims.

If you need to charge more, then you know the latest won't work for you. Use the device. Figure it out.
[Nexus 5 Original Android Development] Arstoien:
Because I don't have consistent usage. Each day is different for me. And my posts in the thread only aim to help the better development of the kernel. I'm fine with it now. :)