yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Seadra:
So,m using r32 now for a while. I remember using r33 and r34 test and both of em were giving me headphones issues. Is the latest r34 stable has headphones issues. Would like a reply from someone who had headphones issue in r33/34.
[Nexus 5 Original Android Development] P.Mobile:
sweet! i must have missed Franco's post about r35 being alomost ready! cant wait boss:good: get my first truck on the rode tomarrow and r35 is on its way!! now thats whats up!!!!!!!
[Nexus 5 Original Android Development] FAdrums:
There was one? ?

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] P.Mobile:
Look 3 posts up
[Nexus 5 Original Android Development] FAdrums:
My bad! Thanks!

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Tzfardaya:
what truck you getting? Honda Ridgeline? :P

thinking of trying to get franco to port his kernel to it? might cut your fuel use in half... :D
[Nexus 5 Original Android Development] abra5umente:
Is anyone else having trouble making UVs stick? Mine reset after reboot.

Sent from my Nexus 5 using PA 4.1 with franco kernel
[Nexus 5 Original Android Development] Tzfardaya:
you are using the "set on boot" toggle, right?
[Nexus 5 Original Android Development] abra5umente:
Of course I am, which is why I'm asking haha.
[Nexus 5 Original Android Development] Tzfardaya:
just thought I'd check, we've had people ask before who respond to that question "what set on boot toggle?" :P

all I can suggest right now is wipe the app settings and start over... my one undervolt stay stuck.
[Nexus 5 Original Android Development] abra5umente:
Done that, didn't work :(

Oh well no biggy I guess. I'll email franco and tell him.
[Nexus 5 Original Android Development] Tzfardaya:
are you setting the voltage first, or the toggle first?
[Nexus 5 Original Android Development] EvgeniX:
Installed CM11 and all my BT problem gone... :good:

will stay on CM11 for now...
[Nexus 5 Original Android Development] TrainNanpaMaster:
[MENTION=3292224]franciscofranco[/MENTION] - Hey Franco. You've probably heard this a dozen times already, but would you please implement frandom support in your r35 release? Virtually every newest AOSP rom nightly has switched to frandom, and it has pretty much rendered your r34 kernel null, void, and useless.>< It's causing many people to jump ship and flash Elemental .32 like hot cakes. = (

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] RobbieL811:
It is definitely not null, void, & useless to me! By far the BEST kernel I have found for my N5. What are you talking about!?!?!?

Sent from my Nexus 5
[Nexus 5 Original Android Development] armando_rod:
4 days of up time, heavy use during this time and the RAM is too high and getting redraws on the launcher.

Edit: using the r34
[Nexus 5 Original Android Development] Tzfardaya:
I guess not all the leaks were plugged then... still, 4 days to capsize is better than the 4 hours on some of the test 33's...
[Nexus 5 Original Android Development] TrainNanpaMaster:
Calm down. Take a deep breath. Know what you're talking about before you post something ignorant like this.

Try flashing any new AOSP rom nightly after 3/8 with r34. ;)

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] Rxpert:
I'd rather stay on an old build than not have Franco work :thumbup:
[Nexus 5 Original Android Development] shreddintyres:
Slim Kat which is an AOSP rom was built 10/03/2013 works perfectly fine... what are you talking about?? Which aosp roms are you trying and if they are having issues all of a sudden its something they are doing. Franco has always sought to maintain compatibility with AOSP and more importantly STOCK Android as shipped from google. If the rom was working fine with franco kernel and all of a sudden with out an update to the kernel on a new nightly it stops its the fault of the rom.

So far the only roms using frandom or atleast showing frandom in their threads from search are all CAF or CM based... Next time i think you might want to think a little harder before posting and telling others of their ignorance ...

- Cheers
[Nexus 5 Original Android Development] TrainNanpaMaster:
Ahh, you must not be familiar with frandom and it's benefits. Also, I never said it was Franco's fault. That's why i asked him to implement next release.

Flash Carbon, Vanir, Liquid with r34 kind sir. Then report back. :)

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] shreddintyres:
Carbon is a CAF rom / CM based - ie not supported

Liquid is a kanged rom which contains alot of commits from CM and as such its Liquids problem if they break AOSP kernel compatibility.

Not sure about vanir but i have no desire to test for you, you are most welcome to test then pull logs but CAF and CM roms are presently not supported for Franco Kernel as per OP.

- Cheers
[Nexus 5 Original Android Development] TrainNanpaMaster:
ROFL. Carbon is based on Slim, Mr. Smarty pants.

Liquid is as well.

Vanir is mainly AOSP heavily patched with CAF.

But flash any other recent AOSP nightly besides Slim.

'Cheers'.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] shreddintyres:
From a Slim dev a few pages back. But if you are so sure then you are more than welcome to prove it.

Elemental works on those roms because there are two versions of elemental (from the elemental op)

Also thank you for the compliment :)

- Cheers
[Nexus 5 Original Android Development] RobbieL811:
I knew I read that somewhere! I was just trying to find it... Thanks! I still stand by my "ignorant" statement that the kernel is running good for me.

Sent from my Nexus 5
[Nexus 5 Original Android Development] TrainNanpaMaster:
LOL, Carbon did NOT switch to CAF. Slim Toolchain all the way, my friend. Check their gerrit. They did however, change to frandom, as I was stating before. You obviously don't know what that is, so please do your research on that. You seem to have a problem with comprehension as well.

Yes elemental does have two versions. But guess what. The AOSP version works on EVERY single AOSP ROM. And do you know why? Because Flar supports frandom. Along with the newest Hellscore, and Chet Kener's uber kernel. Franco r34 does not support frandom, which is why I'm asking him to implement it next release. :)

Oh and by the way, Slim uses LOADS of CAF patches and commits for every single release they put out.

Please know what you're talking about before you post ignorance.

'Cheers'.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] Technecium:
Asking doesn't hurt but the decision to use frandom is not about the advantages or what works with which rom. As a baseline Franco uses stock.

If frandom doesn't play well with the stock rom from Google then it probably won't get added.

I would suggest grabbing the source code and implementing it. You'll be someone's hero!

koeASOP 4.4.2 w/ Franco kernel + F2FS
[Nexus 5 Original Android Development] TrainNanpaMaster:
Nice suggestion;) Can't disagree with what you said. Frandom is the future, however.

BTW, how's F2FS? See any considerable speed improvement?

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] Technecium:
It doesn't appear to be detrimental. I'll just leave it at that.

koeASOP 4.4.2 w/ Franco kernel + F2FS
[Nexus 5 Original Android Development] Enddo:
wow. and you were just calling someone else ignorant in another post lol
[Nexus 5 Original Android Development] TrainNanpaMaster:
It seems YOU haven't been keeping up with CARBON, if YOU THINK it's CAF based. Slim Toolchain, broheim. Check their gerrit. Doesn't get much more AOSP than that.

A plethora of noobs have been flooding XDA forums claiming that Carbon switched to CAF because kernels like Franco wouldn't boot on it anymore. Well once again, that's due to FRANDOM.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] franciscofranco:
I tested on YouTube app, I saw a considerable gain boost of the speaker.

Thanks :)
[Nexus 5 Original Android Development] quiquegabriel:
That's a good attitude haha. Hard and good work is always rewarded.:D

I've been testing the auto-brightness of the screen and seems way too high, I have compared it with the Nexus 4, and the Nexus 5 in dark scenarios is way too bright. I don't know if this has anything to do with the kernel or anything you can tweak but its a battery drainer
[Nexus 5 Original Android Development] franciscofranco:
Its like that on stock. In fact with stock its even brighter.
[Nexus 5 Original Android Development] dazz87:
What value do you have your set to?
[Nexus 5 Original Android Development] TinTin:
I felt the same way. Got good results tweaking with Lux:

https://play.google.com/store/apps/details?id=com.vito.lux&hl=de
[Nexus 5 Original Android Development] quiquegabriel:
Yeah I meant that stock was really bright and I was hoping you could do some of your magic there haha

I have read somewhere that you are taking bug reports on the FKU if we send you an email, but I going to tell you here that when Im in the app and I want to exit by hitting the back button the app force closes and crashes.

Besides that, no other problems. You are doing a really good job
[Nexus 5 Original Android Development] franciscofranco:
I tested with 5, 10, 20, all boosted the speaker gain.

EDIT: Just tested again now while using Spotify, it works just fine.
[Nexus 5 Original Android Development] highend01:
I hope that "double tap to wake" get's implemented, too :) It's probably the most important thing that I'm currently missing on my Nexus 5 :)
[Nexus 5 Original Android Development] franciscofranco:
How can you miss something you never had on this device?
[Nexus 5 Original Android Development] stagius24:
Do you have a source to back this up. From what I read somewhere, location by wifi/network actually is less battery drainage compared to leaving GPS on.
[Nexus 5 Original Android Development] cc16177:
I don't mean to hijack but I can tell you that for me it's just because I had the feature on my Galaxy Nexus and it is one of the more convenient features i've seen added to kernels aside from the color adjustments you make to yours.

It's something so minor but when using a phone as large as the Nexus it's nice to not have to reach for the power button.
[Nexus 5 Original Android Development] mrimage:
When sound app going to release to adjust the sound?
[Nexus 5 Original Android Development] dandwhelan:
Cycled through 5, 10, 20. All sounded exactly the same on the handset
[Nexus 5 Original Android Development] yoyoz808:
*facepalm*

---------- Post added at 03:22 PM ---------- Previous post was at 03:19 PM ----------

You're not the only one. Franco says it works. It's strange,is it bc the speaker is mono and not even a good speaker that i can't tell? The i still cant hear my ringtones lol. The nexus 4 could go way louder than this with the boost.
[Nexus 5 Original Android Development] anaglich:
Are you sure? Maybe I should clarify with more detail. The radial animation that occurs after you use the power button to turn on your phone ( the animation showing you the direction to swipe the lock icon ) is smooth up until the very end where it does not smoothly fade out into complete transparency.

Look closely. Helps if you have a darker background.
[Nexus 5 Original Android Development] tonesy:
I can understand wanting it on a tablet as you don't walk around with it in your pocket, wouldn't double tap wake your phone constantly
[Nexus 5 Original Android Development] franciscofranco:
I dunno then, works on my device, its like night and day.
[Nexus 5 Original Android Development] Moh_Jay:
This was stated a few pages back. Franco knows about it but considering its a very minimal thing I assume its not a big priority right now.
[Nexus 5 Original Android Development] webvictim:
I have nothing much other than my own week and a half of experience with the device.

Location API documentation: http://developer.android.com/google/play-services/location.html

As you can see from the documentation, the most recent sets of Android APis allow app developers to specify whether they need a high-accuracy GPS location or whether they're happy with a rough estimate (to within a degree of tolerance) based on the information that the device got most recently. The point is that a well-coded app which only needs a rough idea of location should help to keep battery life low, because it will just use the most recent data rather than making the device wake up its location gathering stuff regularly. The difference between 4.3 and 4.4 is that previously, GPS would be used if it was switched on whereas now it's specifically cordoned off in the APi as a high battery operation which should only be done if absolutely necessary.

The long and the short of this is that leaving the location provider in "Device only" mode (GPS on, network/wifi off) will increase battery life, at the cost of no location being provided for things like Chrome which only requests a low-accuracy location fix when a website tries to find out where you are. I haven't experimented enough to find out whether Chrome would fire the GPS up to get a location in this instance, but when I tried this the other day with "Device only" on, the browser just hung in place trying to get my location, and the GPS icon didn't come on.

My experience has taught me that with "Device only" I can easily get two full days of battery life with about 3 and a half hours of screen on time on wifi at home, whereas if I switch this to "Battery saving" and use the same amount of screen on time, the battery would be dead sooner. That's all I can really say for now.

I personally found "Device only" to be a good compromise because it still allows me to use Google Maps without having to change the location settings every time and doesn't drain the battery when idling. It comes at the cost of no Google Now, though.
[Nexus 5 Original Android Development] PresidentMcCain:
Just nandroided back to an early state back when I still had stock kernel and reflashed r11. Antutu still reboots at 21% test.

I suspect it may have to do with the binning of the CPU and your thermal control algorithm being inconsistent as a result:

root@hammerhead:/ # dmesg | grep PVS
dmesg | grep PVS
<6>[ 0.549473] acpuclk-8974 qcom,acpuclk.30: ACPU PVS: 2

For example, a friend of mine with the Nexus 5 and r11 can run Antutu perfectly fine, no issues. Mine reboots consistently during the test on r11.

What is your CPU PVS franco?
[Nexus 5 Original Android Development] RobbieL811:
Then shut the hell up & leave, g flash a kernel that supports FRANDOM! Damn!!!! Jesus Christ!!!

Sent from my Nexus 5
[Nexus 5 Original Android Development] TrainNanpaMaster:
Very informative and helpful, lol.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] Nucleotide:
It seems YOU are about the biggest tool I've ever come across on XDA... ever!

Definitely blocking you and your plethora of ridiculous posts. :rolleyes: :rolleyes: :rolleyes:
[Nexus 5 Original Android Development] TrainNanpaMaster:
No disrespect intended. Sorry if you feel that way.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] JaqaL06:
guys i want to switch faux from franco. so which one is smoothest? :) anybody can share his or her opinions who used both? :)
[Nexus 5 Original Android Development] TrainNanpaMaster:
Well, difficult to answer. Because faux has on-demand, which is undoubtedly smoother. Franco only supports interactive and performance. Hmm try flashing Franco, base your own opinion.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] Technecium:
This thread is so damn hostile. I took neutral ground so not to get anyone riled up. I just tried it for myself, others can debate its pros and cons.

koeASOP 4.4.2 w/ Franco kernel + F2FS
[Nexus 5 Original Android Development] :
Well to be honest with you Carbon isn't based on anything. It was originally a fork of Liquid in which Liquid was based on CM at the time. Now Carbon has come a long way from their beginnings and they aren't "based" on any particular rom. They pull a lot of code and features while making their own in house and modify and or change it up to fit their style to be a feature packed rom. :highfive:
[Nexus 5 Original Android Development] TrainNanpaMaster:
Carbon is based on Slim. I've been flashing Carbon since the beginning, when they were still Liquidsmooth. They forked their code to CM (CAF) after becoming Carbon. As of two months ago, they've once again based their code on mostly entirely Slim. Like any popular AOSP ROM (Slim included,) of course they always fork in code from CM/CAF and other sources in virtually every nightly.

Love your gapps btw! :thumbup:

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] tanjiajun_34:
Just tested the r34 but I find its more lag than even the stock kernel. Is everyone having the same problem?
[Nexus 5 Original Android Development] :
Being based on a particular rom and using and or modifying code is two different things. Being based on a particular rom means forking and starting clean with that rom's base. Using commits and code from another rom's source and modifying it to fit your rom's source doesn't mean it is based solely on that rom. Example my personal rom is based on Rastakat which is rascarlo's rom. I forked his source and went from there. Last time I checked Carbon never took Slim's base and modified it. JS.
[Nexus 5 Original Android Development] abra5umente:
Tried both :/
[Nexus 5 Original Android Development] 44-RON:
I'm using this kernel for a week by now, and I'm absolutely satisfied with the battery life.

On the other hand, my phone is overheating , when I play some bigger games like Asphalt 8, it even reboots itself sometimes.

Can I fix this issue somehow?
[Nexus 5 Original Android Development] baedaa:
no you get that wrong, it's called being 'direct' now ;)
[Nexus 5 Original Android Development] Enddo:
i dont experience this lag. then again I am using ART. franco any many others here use Dalvik though, so either one shouldn't be an issue
[Nexus 5 Original Android Development] nerotix:
Are u undervolting? If so increase it with +25 till the reboot dissapear.

And also, asphalt doesnt need all cores @ 2.2Ghz.. u can use per-app-module to set it for example to 1.5Ghz, which I do for all games and seem to run perfectly fine without draining to much battery and barely to no heating. Also u can underclock your GPU which helps alot with the heating, but u must decide for yourself if asphalt still runs smoothly when underclocking GPU, I do it all the time tho.
[Nexus 5 Original Android Development] TrainNanpaMaster:
Understood. Was just asking your opinion.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] Technecium:
My goal was to make it work. For better or worse... goal accomplished! Now, as someone mentioned frandom, it peaked my interest and the more I read about it, it might be something I will try to do.

However, I have a few projects related to my rom I'm trying to figure out.

koeASOP 4.4.2 w/ Franco kernel + F2FS
[Nexus 5 Original Android Development] TrainNanpaMaster:
Nice nice. Yeah, people don't understand what frandom is, lol. It makes apps fly open faster,

and drastically reduces UI lag.

Good luck on your rom building endeavours.~

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] Stevemeister:
No lag here, not on Dalvik or Art. I've uc'ed CPU to 1728MHz and GPU to 320MHz and boosted input_boot_freq to 1574000 and uv'ed -50mV across the board, rest is untouched.
[Nexus 5 Original Android Development] Tzfardaya:
Your phone is rebooting when you're playing asphalt 8 and overheating? Easiest way to fix that is to set a per app mode for that game and underclocking the cpu.
[Nexus 5 Original Android Development] floepie:
It does seem that she is more knowledgeable than many here who have spread and repeated things which aren't accurate. Why get so emotional about a request for a feature?

Sent from my Nexus 5
[Nexus 5 Original Android Development] TrainNanpaMaster:
He's a a good ol' boy from the south. Savannah JO-JA. yee haw~ Easy to get a little hot under the collar, lol.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] vomer:
Calm down people. No need to disrespect anyone...

Sent from my Nexus 5
[Nexus 5 Original Android Development] bikeryder007:
No doubt man. Never let some frandom chick come between you and your friends.
[Nexus 5 Original Android Development] Tzfardaya:
frandom = fast random number generator... generally considered to be approx 10 times faster than standard /dev/random... (I assume this is in regards to entropy regeneration rather than simple read speed)

not sure why app loads and UI lag would be affected by random number generation...

also, most implementations I've seen for it are mostly userspace, while it is a kernel module, it's only real interaction with the kernel is with the kernel random number generator to seed frandom/erandom
[Nexus 5 Original Android Development] TrainNanpaMaster:
lol. ok I'll admit it. That made me laugh.

sent from the back of a prancing, magical unicorn.
[Nexus 5 Original Android Development] vomer:
LOL! :good:

This frandom stuff is the new CM "question" now. Let's move on...

---------- Post added at 09:03 AM ---------- Previous post was at 08:55 AM ----------

[MENTION=3292224]franciscofranco[/MENTION] your new app got featured on AP: http://www.androidpolice.com/2014/0...droid-apps-from-the-last-2-weeks-22514-31014/ :good::good:
[Nexus 5 Original Android Development] gamerZ1:
My phone is reboots while transfering large file via Airdroid (4.5GB file) on 5GHz band.3 times rebooted.Can someone reproduce the test if this is a kernel problem?
[Nexus 5 Original Android Development] nerotix:
I'm wondering myself what it has to do with UI lag etc.. seems only good for generating random numbers?XD
[Nexus 5 Original Android Development] carlese:
Can anyone point me to a frandom post? I want to know more about it.. I thought it was a flashable thing but it clearly isn't :)
[Nexus 5 Original Android Development] blueren:
Quick question. Does using art affect battery life in any manner? At least keeping kernel in mind?

Sent from my Nexus 5
[Nexus 5 Original Android Development] Enddo:
no
[Nexus 5 Original Android Development] VoluntaryMan:
ART is slightly beneficial to battery life.
[Nexus 5 Original Android Development] Tzfardaya:
here you go
[Nexus 5 Original Android Development] carlese:
Too complicated but thanks!
[Nexus 5 Original Android Development] Savant:
How is that complicated you just read the readme file and it explains all of it.
[Nexus 5 Original Android Development] Tzfardaya:
The Readme is pretty good...
[Nexus 5 Original Android Development] Red5:
So this thread went form waiting on r35 to which roms are based on what branch, a few random ART questions and about frandom chicks.

Ive only been up for a few hours, but thats enough internets for me today.
[Nexus 5 Original Android Development] jmartino5920:
:confused::D;)

Sent from my Moto G
[Nexus 5 Original Android Development] outofthisworld:
Can you do a summary every day?

And throw in a link to the latest Franco test kernel while you're at it pls
[Nexus 5 Original Android Development] VoluntaryMan:
Next time on the franco kernel thread, tensions rise as sk8lord4 asks whether x device will get support, laughingdino calls the kernel buttery, and nimvader asks whether CM is supported.

*teaser animation*

I'd watch it.