yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] franciscofranco:
I don't really care if people are getting wet about issues on a test boot.img - what I care is getting valuable feedback, either good feedback, bad feedback or constructive feedback - its a test, simple. I'm not good take r32 and rename it to r33 and say "hey here's a fixed r33, enjoy", I want people to test it out and give me feedback. If the device explodes while using a test image, so be it, its the user responsibility, they know its a test so I couldn't care any less if users get all wet when they see 300mb free ram on their device. If they don't like it then they should flash the production release. This message is not directly to you, I know you're being a bit sarcastic, but I couldn't miss the opportunity to write this post :)
[Nexus 5 Original Android Development] ben_pyett:
My device is suffering from reduced RAM on latest kernel, should I RMA?:p

there's new drivers?;)
[Nexus 5 Original Android Development] Red5:
Is that a no then? I bet these new drivers will fix the broken Siri. :D
[Nexus 5 Original Android Development] JNewms:
So guys, have a look at what I just saw on the google master branch https://android.googlesource.com/platform/build/+/08d410f53249c18d752f56a881ed2335403080d4^!
[Nexus 5 Original Android Development] hanschke:
hope galaxy nexus and nexus 7 got a kernel update too :good:
[Nexus 5 Original Android Development] Red5:
Hi. Welcome to XDA. We hope you have a pleasant stay. :)
[Nexus 5 Original Android Development] Techimplant:
Alright I know this has been asked earlier..just searched the thread but I saw no clear reply to this..so here I go

Can we think of incorporating DT2W/S2W in the next build or next to next..I mean it will be useful..coz I think I will break my power button one day..I press it so many times during the day and night too(its not like I don't have other things to press)..so is it possible?..is there any harm in incorporating this due to which it is being avoided? ..Thanks
[Nexus 5 Original Android Development] jd1639:
Cool story bro
[Nexus 5 Original Android Development] Techimplant:
Omg..I think I have asked a super stupid question here..forget it people..sorry.. Ignore it please :banghead:
[Nexus 5 Original Android Development] dzaster89:
Search the android development forum I'm sure you'll find what your looking for.
[Nexus 5 Original Android Development] ben_pyett:
could you tell us what that actually is please?
[Nexus 5 Original Android Development] :
Hi,

Take a look here (kernels based on Francisco with what you want): http://xdaforums.com/showthread.php?t=2538441 or http://xdaforums.com/showthread.php?t=2527130...

You almost started a world war :D

:)
[Nexus 5 Original Android Development] Red5:
So how many beta tests are there of r33 so far?
[Nexus 5 Original Android Development] kmakiki:
Hey [MENTION=1363323]vomer[/MENTION], just wanted to say that your amoled color set up is wonderful. It'll take a little bit to get used to the ridiculously high contrast, but everything just pops! Thanks man!
[Nexus 5 Original Android Development] Ajseter:
Sorry for inconvenience sir.... make sure mistake will not repeat in future
[Nexus 5 Original Android Development] geunho:
I believe there were 5 in total. I have the 3rd and 5th ones
[Nexus 5 Original Android Development] Techimplant:
All right..thanks everyone..n sorry for the question..so it results in battery drain..although Phantomgamers has merged these functions ..but still I will stick to Franco's this kernel only..dont want to sacrifice performance n battery just for avoiding presses.. will get a new power button within warranty n will buy one after warranty is over :p
[Nexus 5 Original Android Development] JNewms:
It is Google making ART the default runtime. It's in the master branch so I would think that means it'll be default in the next update.
[Nexus 5 Original Android Development] nexusmaniac:
Nice! Glad to see art is becoming standard :) :good:
[Nexus 5 Original Android Development] vomer:
Glad you like it! :D
[Nexus 5 Original Android Development] ironjon:
Really good news! :)
[Nexus 5 Original Android Development] Seadra:
Nope. Xposed users are screwed. I hope we get an option to change it to Dalvik.
[Nexus 5 Original Android Development] Techimplant:
Well I have got a perfect wayout..Don't update..wait for Xposed to become compatible with ART and done!
[Nexus 5 Original Android Development] Red5:
Looks like rovo89 better start figuring out how to get xposed to work with ART. ;)
[Nexus 5 Original Android Development] The Gingerbread Man:
Sorry for those that actually understand what jnewms posted, does this mean art is ready for production now? A kernel update in the next OTA?
[Nexus 5 Original Android Development] Seadra:
Ofcourse I won't update. :good:
[Nexus 5 Original Android Development] aavvaallooss:
I need Xposed too, I'll staybon Dalvik until it work on ART
[Nexus 5 Original Android Development] ironjon:
Well I prefer an efficient runtime.
[Nexus 5 Original Android Development] misterviolinguy:
The commit he mentioned implies that Google will be using ART as the DEFAULT runtime in future releases of android. There will be the option to switch back to Dalvik, for those of you that need it for compatibility/xposed. See the link below for reference:

http://www.androidpolice.com/2014/01/31/recent-aosp-commit-indicates-art-likely-to-replace-dalvik-in-upcoming-release-of-android/

This, however, does not give a time window for the next release to happen. They may be committing it early in the development stage to help fix bugs, or committing it later in development since bugs have been fixed. We don't know. The arrival of the next android release could come at any time, but it should have ART as default.
[Nexus 5 Original Android Development] riDDimann:
Back then CM actually made sense. Now look what the project has become. They keep breaking kernel compatibility with almost every release for no apparent reason. They want you to create a CM account. They try to screw 3rd party app developers (Focal). Commercialization is everywhere.

Other projects have taken the place CM was at a few years ago. CM has changed, not the community.
[Nexus 5 Original Android Development] pkelly517:
Which part of the commit sets the runtime?

I didn't dig any deeper than the top of the tree. I see where you can override the runtime, but it's all commented out.
[Nexus 5 Original Android Development] gparmar76:
Who cares? If Franco hates CM, he should have never supported it to begin with...but at the time he did and it was absolutely the right decision because even with all the *****ing going on here, CM is still king...and their current ROM with their kernel works flawlessly... And after using just about every custom ROM available here for the N5, CM is still by far the best one overall...if Franco doesn't want to support CM, then he shouldn't have started in the first place because it was CAF injected then too... and he's letting this air of hatred and childish finger pointing go on in his thread...and there's simply no reason for it...either support CM or don't...there's no reason to play "in the middle" here...oh and you don't have to create a CM account to use their ROM and they didn't screw any app developer over...do a little research before pointing fingers...lastly, why would anyone hate CM for trying to earn a living off their incredibly hard work? I, for one, am happy as hell they are doing that...more money they get, more time will be spent on their ROMs....and I don't see any ROMs out there that are at CM level of performance or reliability on an overall scale.
[Nexus 5 Original Android Development] big_adventure:
What does ART have to do with the Kernel? I'm pretty sure you know the answer: Nothing.
[Nexus 5 Original Android Development] The Gingerbread Man:
Yeah I know its the run time but I just didn't understand exactly what people were talking about. My curiosity has been satisfied
[Nexus 5 Original Android Development] pkelly517:
I believe that issue is AOSP compatibility.

If a build is going to break compatibility with CM or AOSP, then CM will lose. It's not for/against CM, it's strictly FOR AOSP. The kernel will work for stock users. Everyone else is a bonus.

CM can collect all the money they want. Apparently, it's a great ROM. Apparently, it's also a moving target for kernel developers.

My question(s) to you is(are):

Why are you here in Franco's thread if you are truly using CM? You can't be using Franco's kernel. So why bother?
[Nexus 5 Original Android Development] 5FOOTER:
Google makes a pretty good ROM we all call it stock. It works great for a lot of people.

how many times have these questions been asked?
[Nexus 5 Original Android Development] big_adventure:
I didn't want other people misunderstanding the relation there: like I posted, I was sure that you (someone who has contributed roughly 6750 times as much as I have) knew that there was no link. :cool:
[Nexus 5 Original Android Development] Testraindrop:
Why don't you use it then with their kernel?
[Nexus 5 Original Android Development] Fluidification:
the main point isn't that you are supporting evil if you use it. In fact, they make a great ROM and kernel for that matter. The main thing is that CM has branched away from stock enough that things aren't compatible anymore. Rather than pointing fingers and blaming. Use what you want. CM is great, for those who want to use it. Stock based roms are great for those wanting to hold true to the true AOSP and Google nature. To be honest, you can blame google that N5 stock is quite divergent from AOSP. The point is that Franco kernel has to do extra work to be used with CM, which isn't the nature for most AOSP roms.
[Nexus 5 Original Android Development] gparmar76:
No...I'm actually not tied to any one ROM for the N5 yet...that's why I use them all...I am, however, very much tied to Franco's kernel...when it was working with CM, I felt I had the best combo...but since then, I haven't enjoyed any one ROM with Franco's kernel...and to me its because of the ROM, not kernel in any way...I'm hoping he continues support for CM because whether he personally likes it or not, its in his best interests in the end...its more end users for him and more people that may buy his kernel app...which by the way is the best kernel control app out there.

---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------

It wasn't asked now...but for whatever reason, you chose to answer it anyway??
[Nexus 5 Original Android Development] Smallsmx3:
Stock and FK seem to be the best option for me, no matter what i use ive been coming back to stock because it's the fastest rom available, i do miss the little tweaks here and there from other Roms but it seems like when i need something to just work, it doesn't on custom Roms,
[Nexus 5 Original Android Development] Red5:
Guys, when is the update coming out for ART and the new Qualcomm drivers?
[Nexus 5 Original Android Development] mibtnt:
Summary of the last few pages

-constant cm compatibility woes and why hasn't Franco done something like buy over cm

-r33 memory leak. Is it real or not

-color profiles. Can I haz it. Where haz it. Y u no look good on all phones.

-just avoided nuclear fallout after someone asked about s2w and d2tw (mind you I myself wondered about it but remembered it was answered in FAQs)

And lastly...

-iPhone color profile is the best. If your phone becomes too yellow with it, then you need to buy a new phone.

:D:D:D

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] detdett:
In two weeks
[Nexus 5 Original Android Development] pkelly517:
Fair enough. During the day, I enjoy a quick Torch shortcut via SlimRom (in the moment) than the ongoing battery improvement.

However, when you take into account the number of kernels he builds (every current Nexus), doubling that for CM support is unlikely at best.

And, personally, as an owner of the Nexus 10, I would prefer that he spend time on that kernel before spending his efforts for the CM version of the N5/4. But I'm pretty selfish. And I stick to AOSP. And, since I do, I get both ROM and battery improvements.
[Nexus 5 Original Android Development] HenryDCase:
https://developer.valvesoftware.com/wiki/Valve_Time

Sent from my Nexus 5
[Nexus 5 Original Android Development] riDDimann:
They keep breaking compatibility on their end. From a software developer's viewpoint changing the kernel/userspace interface all the time is a fundamentally stupid thing to do. The only reasons I can think of why CM would do that is that they are either not competent enough to chose a proper design in the first place, or they do it to intentionally break compatibility. Both are very good reasons to not user their software.
[Nexus 5 Original Android Development] gparmar76:
I have to honestly say if you think CM developers are not competent, you don't know much about custom Android ROMS....yes they are implementing CAF....it hasn't caused their ROM any harm...their ROM is better for it...CM has raised millions for their efforts... They don't need to follow anyone's lead...that's up to kernel developers...they can follow or choose not to...pick one and stick with it...that simple.
[Nexus 5 Original Android Development] Langduscher:
I thanked you for that.

I own Nexus devices and stick with stock + FK on these devices. Stock Android has come a long way and is very sophisticated.

On my other devices (S4, TF300T) I am pretty much "bound" to CM and granted: works flawlessly as "stock Android" on these.

We have choices and have to be smart about those choices. Not whine about what can't be.

edit: just look at what we can do/ what options are available to us these days. It's just frikkin awesome!
[Nexus 5 Original Android Development] brooklyn718941:
Will this work on any ROM?
[Nexus 5 Original Android Development] PhantomGamers:
Not recent CM based roms.
[Nexus 5 Original Android Development] franciscofranco:
I'm running kmemleak to see if I find the memory leak of r33. No promises though, this may take a while.
[Nexus 5 Original Android Development] dodo99x:
Reminds me of when manta was having that nasty surfaceflinger memory leak
[Nexus 5 Original Android Development] franciscofranco:
In that case it was actually Google's fault :)
[Nexus 5 Original Android Development] PhantomGamers:
Well here we can just blame Qualcomm ;)
[Nexus 5 Original Android Development] RobbieL811:
Well, the guy said he ain't gonna support em anymore & he's sticking with it. Quit whining about not being able to use FK with CM. Tired of reading your posts. CM OBVIOUSLY doesn't want people using custom kernels with their ROM! Why don't you pick one & stick with it??? FK or CM?

Sent from my Nexus 7
[Nexus 5 Original Android Development] gparmar76:
I don't really give a **** what your tired of....if you don't like it, then don't take the time to post to me because that pollutes the thread further...and CM doesn't care what kernel anyone uses...when did they ever say this? Stupid posts are apparently becoming viral here....and I don't take the time to read every post in this thread...mostly because its full of people like you...so if Franco has officially said he's not supporting CM anymore, oh well....bad decision but understandable.
[Nexus 5 Original Android Development] dave2metz:
Ooh.. Oh snap!

NEXUS 5
[Nexus 5 Original Android Development] neriamarillo:
Haha haha haha haha :D
[Nexus 5 Original Android Development] jd1639:
Boys, stop the bickering. This is a development thread. Take it to pm
[Nexus 5 Original Android Development] detdett:
Girls are allowed to bicker then?

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

So we have to take the time to read yours?
[Nexus 5 Original Android Development] Circaflex:
in the end all I can say is there is a reason a lot of known and competent devs as you put it are jumping ship from CM to OMNI or pure AOSP. Just because CM does it, doesnt mean its correct/right/the best. CM isnt the end all of Android Roms or the "one"
[Nexus 5 Original Android Development] gparmar76:
You know how to read? Because your one liner nonsense leads me to believe you have comprehension issues.
[Nexus 5 Original Android Development] Circaflex:
they have been known in the past to break/block certain kernels on purpose
[Nexus 5 Original Android Development] detdett:
Yes, unless you admit you're being sexist and think that every user on this thread is a male
[Nexus 5 Original Android Development] The Gingerbread Man:
Its worth a shot, I can't promise they will accept. This is sort of why Franco was after people who knew fastboot as the chances of a mistake are much less and more savy users might be able to fix any soft bricks. I think yours is as dead as dodo I'm afraid. I don't agree lying but it is your only way to attempt any replacement.
[Nexus 5 Original Android Development] alanwyl:
I really don't know why I am interested in this thread.

I don't have a N5, I don't even know if I will buy myself a N5.:D
[Nexus 5 Original Android Development] timvdlinde:
It's the power of Franco.
[Nexus 5 Original Android Development] oediv:
can somebody say me how to boot with the kernel ones without flash ? and how i flash it when it boots ?

or i am wrong and this cant be able ?
[Nexus 5 Original Android Development] CaspaTheGhost:
Come again?

Sent from my Nexus 5
[Nexus 5 Original Android Development] Rico84:
"The power of Franco compels you!!"?
[Nexus 5 Original Android Development] Batfink33:
Does Franco wear sandals have a long beard and long hair?
[Nexus 5 Original Android Development] mrgold2505:
Problem resolved. Carphone warehouse will replace the nexus 5. Thats my lucky day. LOLOL
[Nexus 5 Original Android Development] PhantomGamers:
I'm confused as to why this bricked the device though... does FKU not flash to /dev/block/platform/msm_sdcc.1/by-name/boot?

I would think it would just boot to the bootloader and stop...
[Nexus 5 Original Android Development] Testraindrop:
Also curious how one could hardbrick a nexus...

I had accidentally (bad naming -.-) flashed a recovery on the kernel partition of the N4, still no hardbrick, booted just fine to the bootloader :)
[Nexus 5 Original Android Development] zephiK:
A wise man once said,

;)
[Nexus 5 Original Android Development] PhantomGamers:
It's possible Franco hardcodes the actual block number to the kernel and that the n5's bootloader number is the n4's kernel but idk, I can't imagine he would do that...

Is it possible the battery IS dead and he just needs to charge it? XD
[Nexus 5 Original Android Development] whiskerz:
Oh yay, Franco is here! I loved your kernels on my GNEX, and can't wait to get this on my N5. Oh wait... I have Verizon...... :(
[Nexus 5 Original Android Development] kuyam:
If you have to ask, this is not for you.

Just wait a bit for easy installation through the updater app.
[Nexus 5 Original Android Development] KennyDumah:
As soon as I get my Nexus 5, I'll flash franco's kernel on it.

Loved to use it on my Nexus 4 and hope to see this amazing battery life again :highfive:

Sorry for bad english :cyclops:
[Nexus 5 Original Android Development] oediv:
Well good idea but i read a Lot and now i did it :)

And it works :)
[Nexus 5 Original Android Development] Audioboxer:
CPU manager FC's in your kernel app with test4 franco. Is there a beta version of the app I'm suppose to be using?
[Nexus 5 Original Android Development] Testraindrop:
No, as he hasn't the phone yet he won't be publishing an app version for the non-xda audience who could (soft-)brick their devices with TEST Kernels.
[Nexus 5 Original Android Development] timvdlinde:
Got some new news, my German friend told me it is shipped. He expects it Tuesday, so I could have it Wednesday. Can't wait :D when I got it I immediately flash Franco his kernel.
[Nexus 5 Original Android Development] oediv:
well in trickser i can see anything and change anything
[Nexus 5 Original Android Development] Datzi:
There is no difference between flashing the .zip or flashing the stand-alone .img, right?
[Nexus 5 Original Android Development] Nbsss:
lol the most viewed thread on this subforum - that says a lot!
[Nexus 5 Original Android Development] shawnaye:
franco kernel updater.

nope, but .img is flashed via fastboot, .zip is via recovery.
[Nexus 5 Original Android Development] arararagi:
Looks like the software update mode on other LG phones. Obviously we don't have any LG tools or firmware files for this phone, so maybe check on the Nexus 4 forum to see if anyone has a similar experience and whether there was any fix.

Fastest solution is probably to just RMA it.
[Nexus 5 Original Android Development] Batfink33:
Or flash .img via Flashify or FKU

Sent From My Nexus 5 Powered By Franco Kernel
[Nexus 5 Original Android Development] tuncan:
Is flashing over FKU the safest?
[Nexus 5 Original Android Development] ama3654:
It happened to me too, Hold power button plus volume up+down together for like 10 seconds and let go, allow like another 30 seconds, then do it again, thats how i brought mine back to life, i panicked seriously.

EDIT: make sure its not connected when you do that, i was thinking of taking mine back too, but with trial and error, i got it back.

Your bootloader is corrupted, so you have to adb flash bootloader again to function properly
[Nexus 5 Original Android Development] safendi:
my n5 is stock (factory image google), if would flash franco kernel 10 using fastboot, i have to do wipe cache/dalvik after flash? i don't use twrp or cwm
[Nexus 5 Original Android Development] shawnaye:
there's no dangerous way to do it AFAIK, just dont use fastboot if you don't know how.

IMO, best bet is either FKU or Recovery :good:

---------- Post added at 04:33 PM ---------- Previous post was at 04:33 PM ----------

Apparently i've been told you dont have too.

Are you even unlocked in the first place?
[Nexus 5 Original Android Development] safendi:
yes is unlocked and rooted
[Nexus 5 Original Android Development] ama3654:
Get flashify from play store and flash kernel, then get FKU app for kernel settings/configuration, but don't use FKU file manager to flash kernels as it will corrupt your bootloader /brick your phone

https://play.google.com/store/apps/details?id=com.cgollner.flashify
[Nexus 5 Original Android Development] catpunt:
Thanks, I got mine into the bootloader by following the steps in this N4 unbrick thread before I saw your post:

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

The trick seemed to be some magic combination of power for 15 seconds, power+downvolume for 15 seconds, power+downvolume+upvolume for 15 seconds, and holding upvolume+downvolume for 2 seconds then plugging in the USB cable to the Windows machine. The thing that finally got it into the bootloader was that last thing, holding volume up and down and plugging in the USB. Not sure how much of the other stuff was pertinent. Then I just did a full factory reset (erasing all the partitions too) and it's running fine now. Phew!
[Nexus 5 Original Android Development] ama3654:
I couldn't sleep, it was terrifying!
[Nexus 5 Original Android Development] cobyman7035:
any good UVing settings? Thx

Via my NeXus 5 on Tapatalk⁴
[Nexus 5 Original Android Development] kuyam:
I go with -75 overall.. no issues sofar.
[Nexus 5 Original Android Development] JNewms:
That's not something that anyone else can answer. Our chips aren't all made equally. If you want to UV just set an amount, if you start getting apps crashing or reboots, then decrease the amount you UV.
[Nexus 5 Original Android Development] :
Wow so does it mean that if I turn on the screen to look what time it is they will keep at 300Mhz. Thats awesome, because they don't need to jump to max freq everytime I want to know what time it is.

Does UV really save that much battery? Is it worth it?
[Nexus 5 Original Android Development] incredulous:
You'd be surprised how beneficial it can be to UV. Less power to the CPU means less power drawn from the battery :)