yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] BlazeForth:
[MENTION=4195844]show-p1984[/MENTION] am getting cannot copy error for usb 3.0 pendrives using otg. But i can with some other kernels. But your kernel is so awesome in performance. So can you fix this issue?

Or this problem is only for me.?!!
[Nexus 5 Original Android Development] show-p1984:
Mine work fine. I also doubt that a "cannot copy" error would go away on another kernel. Usually that's I/O related.

____________________________________________

Beta for L preview updated, compiled and uploaded.

It's a beta, so take it with the usual grain of salt.

KControl's rewrite is getting along just fine as well. Here is some Material-Design candy :)

As you can see from the version number, it just entered beta stage. (which will be available as beta through the optin-program soon)
[Nexus 5 Original Android Development] Citizen_Snips:
Glad to see you back around. Hope you're doing well. Thanks for the update, it is much appreciated.
[Nexus 5 Original Android Development] EdgA#1:
Really nice to See u
[Nexus 5 Original Android Development] Tylog:
Oh, Dennis is alive xD good to see you back :)

And just on Halloween, Dennis Mayers: D
[Nexus 5 Original Android Development] physwizz:
qi charging

Hi,

I really like this kernel.

I know I may be asking a lot, but is it possible to add the ability to do qi charging while a usb stick is plugged in. I would like to charge my N5 while I'm running a secondary rom located on the usb stick.
[Nexus 5 Original Android Development] show-p1984:
tbh: I don't even know if that is physically possible.

It would depend on the used internal charger and how the qi charging coil is connected to it. On some devices the qi charger is inside the battery, which would make it theoretically possible.

Either way: I strongly doubt the safety of this arangement. Charging the battery generates heat and the battery would essentially work as a buffer in this case, which means it would also heat up due to discharging.

Potentially there are a lot of things that can go wrong there. I will look into the used hardware and it's specs when I have time, but don't get your hopes up. If it's even remotely unsafe I won't include it.
[Nexus 5 Original Android Development] physwizz:
Thanks for your reply.

On my N7 there are some kernels which will allow charging via a powered otg cable while a Usb stick is plugged in.
[Nexus 5 Original Android Development] show-p1984:
Well that's pretty easy to do in comparison. The cable powers the phone and the USB device, the battery is completely out of the equation and idle. What you wanted is a whole different level :)
[Nexus 5 Original Android Development] physwizz:
The battery is showing that it is charging at the same time as the usb stick is plugged in but on the N7 I can't run an external rom and charge at the same time.

I haven't tried this on the N5 yet but I'll do it when I get home.

Edit: It Worked!!! The N5 will also charge the battery at the same time as running an external rom off the usb stick! yay!!
[Nexus 5 Original Android Development] SnoopHTC:
Please :)

[MENTION=4195844]show-p1984[/MENTION],

Hello, I don't know if you have read my post, if yes, sorry for re-ask,

Can you "re-add" the battery percentage when we recharge the phone "powered off", modify version of linux kernel (3.4.104 for example) and fix F2FS support? (I tested ok with big-bum v29-F2FS hybrid kernel too)

Very big thanks!

@++
[Nexus 5 Original Android Development] oneplus:
Can you bring bricked to OPO?
[Nexus 5 Original Android Development] RobbieL811:
Pretty sure that he is already working on it.
[Nexus 5 Original Android Development] show-p1984:
I never removed that. Since it is mostly RAMDISK dependent and bricked doesn't bring it's own, rather than using yours, I would argue that your RAMDISK is at fault.

I am quite unsure what you mean by that.

If you mean that I should patch upstream: Tell me why. Give me one good reason and I will do it.

I haven't found the slightest reason to do so, most of the stuff patched into upstream is x86 or x86_64 related and most of that is new hardware support or improved hardware support. Now guess what: We have a phone. We can't change the hardware, so there really is little to no point in doing so, is there? ;)

F2FS support is not broken and working fine. There is nothing to fix.
[Nexus 5 Original Android Development] garynych:
im found this answer about floods the logcat with errors: PowerHAL(653): touch_boost: failed to send: No such file or directory.

im compile kernel, and this flood annoying, get but if a decision to get rid?

redirect to logger.ko, do not like the same

if there is an option to disable these messages in the kernel sources, please point me

thank you
[Nexus 5 Original Android Development] show-p1984:
It's rom side.

Compile your own powerhal with the touchboost commented out, push it and reboot.
[Nexus 5 Original Android Development] RobbieL811:
[MENTION=4195844]show-p1984[/MENTION] I just flashed the latest beta on a build of SlimLP 5.0 that I just made for Hammerhead. Any idea why it may be getting stuck at SlimKat splash lol? I can't figure it out. I can't get a logcat. It doesn't get that far into boot. I used the latest kernel from your beta folder in the OP.
[Nexus 5 Original Android Development] show-p1984:
Beta is always cutting edge. At the moment that means beta = L preview 2
[Nexus 5 Original Android Development] RobbieL811:
OK. I will try a few other things.

Sent from my Nexus 7²
[Nexus 5 Original Android Development] EdgA#1:
I'm on simple aosp with The last beta, but cant geht root ...
[Nexus 5 Original Android Development] show-p1984:
That's your ram disk's issue, not the kernel's.

See here: http://xdaforums.com/showthread.php?p=56526706#post56526706
[Nexus 5 Original Android Development] EdgA#1:
Yes, I've noticed. The Franco runs
[Nexus 5 Original Android Development] RobbieL811:
Franco uses his own ramdisk. Show-p's kernel re uses the ramdisk that you had on the phone before you flashed his kernel. You need to check into the origional ROM's kernel.
[Nexus 5 Original Android Development] Tylog:
Work fine here

Before you flash the Kernel flash modified stock kernel, then bricked, then superSu :)
[Nexus 5 Original Android Development] RobbieL811:
T, link me to the modified stock kernel or tell me where I can find it please.

Sent from my Nexus 7²
[Nexus 5 Original Android Development] Tylog:
There are 2, one of Chainfire

https://www.androidfilehost.com/?fid=95747613655047375

one of

[MENTION=1050103]sykopompos[/MENTION]

https://www.androidfilehost.com/?fid=95747613655048458

I recommend the second had, so never difficulties. Is a permissive, but you can use the one from CF too and activate permissive with this app easy https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=de
[Nexus 5 Original Android Development] RobbieL811:
Ok. Thank you for the info. I will try the second one. Gonna flash over a fresh build of SlimLP!
[Nexus 5 Original Android Development] SnoopHTC:
Hello, Thanks for your answer, more details :)

Thanks, i will ask in good thread... sorry, Mahdi built his own kernel, all is explained :)

No no all is very good ! :), it's just a detail, see screenshot n°1 and 2, we see "3.4.104" and you, we see "3.4.0", this is just a detail, I find it cool to know which version of linux you are using. ;)

Ouah, so it's Mahdi RAMDISK too who have "problem" ?

With TWRP, I always wipe system, cache, dalvik and data before flash Mahdi ROM then Gapps then SuperSU then your kernel and reboot, the result is : screenshot n°3. It's ok with big-bum F2FS kernel so if i understood, big-bum F2FS kernel has it own RAMDISK ?

Thanks a lot to help me !! Very appreciated !!!
[Nexus 5 Original Android Development] show-p1984:
The linux kernel version is 3.4.0. (with lots of cherry picks and newly written stuff)

Since big-bum provides boot images it has to have a ramdisk included.

I don't provide boot.img because a ramdisk has to be included in it. Instead I slightly modify yours on the fly to fit my needs, but I will never just overwrite it with my own. That limits user choices and potentially erases modifications you have done.

So: Flash a boot.img with f2fs ramdisk modifications + flash bricked if you want to use f2fs on bricked.

Tbh: I wouldn't run f2fs, yet.

There are a few things that should be 99.999999999% stable on a computer system. That should optimally never break. That should have been years into testing, patching, bug fixing, etc...

The file system is at the very peak of that hill in my honest opinion.
[Nexus 5 Original Android Development] SnoopHTC:
Hello,

Thanks for the answer

Thanks for the answer, no bug ! :) but as you say, is not the original ramdisk and i like your philosophy (compatibility = stability)

After cleaning my eyes, i have a suggestion : can you add the missing code to your scripts who modify our original ramdisk ? :):):)
[Nexus 5 Original Android Development] show-p1984:
That would make it incompatible for everyone not going to use f2fs :)
[Nexus 5 Original Android Development] show-p1984:
Beta updated for Lollipop-Release
[Nexus 5 Original Android Development] nicob:
All settings I prefer are preserved in KControl after a reboot, except for the input event boost in ms. Setting it to 500, enable apply settings on boot & apply mpdec settings does not do the trick. It default to 1000 after a reboot. Any suggestions?

Using the latest beta, stock lollipop (loving it btw)
[Nexus 5 Original Android Development] show-p1984:
Thanks, already known though :)

That's KControl Bug #71, fixed in the upcoming KControl v2.0.
[Nexus 5 Original Android Development] Tylog:
Thanks Dennis :)
[Nexus 5 Original Android Development] show-p1984:
SuperSU-working modified stock boot images for lollipop:

https://drive.google.com/folderview?id=0B1Tn7X59NcPxek1ZTENxbnBzRTA&usp=sharing
[Nexus 5 Original Android Development] SnoopHTC:
Thanks for the answer, and same thing with battery percentage when phone is powered off?
[Nexus 5 Original Android Development] show-p1984:
I probably could do it, but why? You can just flash the ramdisk with the features you want and then flash bricked.

Problem solved.

This has nothing to do with the kernel, so I don't see why I should include it. kernel = zImage(_dtb).

The few things I modify in the ramdisk are overrides (governor, etc...) placed there by someone who thought it would be a great idea to enforce this, which I largely remove completely.
[Nexus 5 Original Android Development] californicated:
When coming from stock with CF auto root. Do I need the modified image from above before I flash the beta kernel from OP? I assume the answer is no.
[Nexus 5 Original Android Development] shri_chanakya:
Flashed bixxie lollipop zip and then this kernel and SuperSU 2.16. Still no root. Will flash cf root and report back.
[Nexus 5 Original Android Development] show-p1984:
I don't know how many times I have to explain this, but here it goes again: The kernel has nothing to do with having or not having root on lollipop!

It's the ramdisk you want to patch for that. Would you like to know more?

And on this very page, in this post, I even did all the work for you...
[Nexus 5 Original Android Development] shri_chanakya:
Sorry for not reading things. Getting near midnight where I'm with very slow internet connection. Will check out the links. Thanks
[Nexus 5 Original Android Development] shri_chanakya:
So here is what I finally ended up doing.

Flash bixxie

Flash elementalx kernel

Flash SuperSU

Flash bricked

The reason is they are all flashable zip files. While using cf root or boot images would have required booting up computer which I didn't have.

Request: it would be good if you can change ramdisk to allow for SuperSU to work

Or put the stock not image as flashable zip.

Flashing one zip after another is pretty easy and doesn't involve computer and cable.
[Nexus 5 Original Android Development] Citizen_Snips:
What recovery do you use? If TWRP, find the Materialized themes (N5 themes and apps section). Follow the instructions of the thread to properly install the theme. Install Bigxie's ROM. Once flashed, go back to "Install" and on the top of the screen where it says "Flash ZIP", click that and you'll see the option to "Flash IMG". Now flash the boot.img that [MENTION=4195844]show-p1984[/MENTION] posted above. After that switch back to ZIP files and install Bricked and SuperSU. Works perfect, it's how I did it.

I wasn't near a computer and didn't feel like flashing another kernel before Bricked. Anyways, making a flashable ZIP is pretty easy, there's instructions on XDA. Google it if you can't find it.

Everything is running nice and smooth so far for me on Bigxie's ROM with Bricked kernel. Thanks again Show. Looking forward to KControl 2.0. :)
[Nexus 5 Original Android Development] Luigi_2:
Hi show-p, may i ask to you implement the sweep-to-sleep gesture because stock android feels lacking and installing an app just for it is too wasting space. Besides, it's doesn't affect battery like the sweep-to-wake and make a huge convenience in daily usage as it can turn the screen off at any screen without having to reach for the button.

This is the only thing that keeps me using elementalx kernel.
[Nexus 5 Original Android Development] californicated:
Should be implemented. You need to enable the feature using kcontrol or an echo command that I don't know. Would be interested in that, too.
[Nexus 5 Original Android Development] SnoopHTC:
battery poucentage

Hello, I thought it might cause stability problems when using a different ramdisk, it's wrong?

I agree with you on doing that this has nothing to do with the kernel, but it helps to know exactly when the battery is fully charged. ;)

@++^^
[Nexus 5 Original Android Development] estallings15:
Every time I come in here for the past several days all I see is talk about the ramdisk because, for whatever reason, this is difficult for some people. What is the deal? Show-p has made it crystal clear why he sets up the kernel the way he does to use the ramdisk that your device already had. He's answered your questions and still it doesn't stop.

This kind of stuff is why developers give up on us and quit sharing their work. He's an experienced developer who, not only has a lot more knowledge than most of us, but is likely smarter.

The answer to your question no. Now leave it, please.
[Nexus 5 Original Android Development] Citizen_Snips:
Well, ya see, when it's done charging... That battery bar... That shows up... when you press the power button... It's full.

Seriously how much time do you spend with your phone off that it makes that big of a deal? Show has already stated his intention several times now. Let it be please. How many times / different ways does he have to explain it?
[Nexus 5 Original Android Development] SnoopHTC:
Hello, not a big deal at all and sorry for the inconvenience caused here. Bye
[Nexus 5 Original Android Development] shri_chanakya:
Any idea why we not getting 3.10 kernel from Google?
[Nexus 5 Original Android Development] Citizen_Snips:
Google doesn't generally bump kernel versions with a new OS. IIRC, the only time they ever did was on the Nexus S.
[Nexus 5 Original Android Development] fbf2201:
Lollipop really seems to be more battery friendly than KK. Unless you did some super magic. (latest beta kernel 20141113)

Mostly browsing, Tapatalk and Falcon Pro - at home with wifi on.

But still much more than before.
[Nexus 5 Original Android Development] DroidIt!:
+++++1 Yep, much better :)
[Nexus 5 Original Android Development] parkson:
Stock 5.0?
[Nexus 5 Original Android Development] fbf2201:
Yes, just limited GPU and CPU frequencies a bit.
[Nexus 5 Original Android Development] DroidIt!:
I'm on SlimLP. I know show and kufi (main dev of slim) have been working together quite a bit. Two masters in their primes :)
[Nexus 5 Original Android Development] show-p1984:
Stable updated. Lollipop :cool:
[Nexus 5 Original Android Development] EdgA#1:
Flashed ☺...

Slim and bricked <3

Sent from slim'ed Hammerhead
[Nexus 5 Original Android Development] fbf2201:
Thanks!

What's the difference to the latest beta?
[Nexus 5 Original Android Development] show-p1984:
There is a link on my page for that :)

https://github.com/showp1984/bricked-hammerhead/compare/master...exp
[Nexus 5 Original Android Development] Tylog:
Nice one Dennis :) have a good weekend
[Nexus 5 Original Android Development] fbf2201:
Thanks, I know that. ;)

But that's all it shows.

So it's actually not much of a difference?
[Nexus 5 Original Android Development] show-p1984:
That's the issue with the word "latest".

The "latest" beta was uploaded today, after I merged everything from the exp branch to master. The only change was removing Android-Logger.

If you meant the previous beta: It's exactly the same as the current stable.

That's the way testing should be. You push stuff as beta, let ppl test it and then merge it to stable without changes. So asking: "What's the difference between stable and beta" after a new stable release will usually yield this result:

Nothing.
[Nexus 5 Original Android Development] fbf2201:
Sorry, didn't want to confuse you. :D

With "latest" I really meant latest.
[Nexus 5 Original Android Development] solfly7:
I see that the20140708 is the last stable. The 20141031 looks like the last beta for kk from looking at the changes. Am i looking at that correctly or is that for lolipop?

Best kernel hands down. Thank you.

Battery life is the best ive found.
[Nexus 5 Original Android Development] EdgA#1:
For lollipop the last stable is from 29.11

http://bricked.de/index.php?action=kdownload&device=hammerhead&release=stable&type=aosp

Sent from slim'ed Hammerhead
[Nexus 5 Original Android Development] Qwerty1208:
Any need to do anything else than just flash it?

(I believe there was some things needed earlier, that's why i ask)
[Nexus 5 Original Android Development] Tylog:
No, kernel, nothing more
[Nexus 5 Original Android Development] solfly7:
So the 31.10 in the beta is kk or lolipop?
[Nexus 5 Original Android Development] omvir:
Hi guys! Using showps hotplug in a one plus one kernel and I was wondering if you guys can give me the stock values of the hotplug ? Screenshots of kcontrol would help and also the boost values. Thanks!
[Nexus 5 Original Android Development] shri_chanakya:
Last version for KitKat was in July. After that lollipop.
[Nexus 5 Original Android Development] shizkoff777:
Download links are down can anyone provide a working one
[Nexus 5 Original Android Development] show-p1984:
Didn't get to updating all the threads with the new download format (you know Christmas...) when the HP changed on Christmas eve to a new design and download page.

This should work for you until I can update the thread tomorrow.

http://bricked.de/#down
[Nexus 5 Original Android Development] shizkoff777:
My bad.Merry Xmas.
[Nexus 5 Original Android Development] lmulli:
No updated kernel for the Nexus 5 though I noticed. New one running well on my Nexus 7 (2013).
[Nexus 5 Original Android Development] EdgA#1:
Stable and beta is from 29.11. And runs fine on 5.0.2... So it's up to date
[Nexus 5 Original Android Development] ek69:
Which ROM would ppl recommend to pair up with this kernel? It's for my wife nexus 5 I've heard about this kernel from AK in the one plus one forums

Cheers for any help :)
[Nexus 5 Original Android Development] parkson:
Try Cataclysm
[Nexus 5 Original Android Development] lmulli:
There are loads to choose from. I find that in the majority of cases they are all pretty much the same in all fairness - some have additional extras located in their own menu within settings, others have those same settings buried within the normal menu options from within settings.

At the moment, I am running SimpleAOSP but swap between the number of roms including Screw'd , RastaPop and one that's not listed in the Nexus 5 XDA section but can be found over in the Nexus 7 sections by a chap called Groggs which is based on Scroslers PureAOSP (http://xdaforums.com/showpost.php?p=56869492&postcount=1533). I have also tried the latest Purity rom found on G+ https://plus.google.com/communities/105581179951601265485 but it benchmarked a lot slower than the previous rom it replaced so reverted back.

Best to download a number of roms and give them all a try. Yes it will take time but at least you will get a feel for each rom.
[Nexus 5 Original Android Development] ajf64:
Got a question did you happen to do any thing special with battery saver mode like limit cpu freq or limit amount of cores in use or is just the stock shut down data services and what not
[Nexus 5 Original Android Development] show-p1984:
I am not quite sure what you meant with your question. (data services are rom side, yet this is a kernel)

There is a lot of genuine code in this kernel which purpose it is to micro-manage the CPUs online states, apart from that I am not limiting the CPU frequency or the amount of cores online.

That said, the fact that it's not in the default configuration of this kernel doesn't mean that you can't do that over sysfs on your own. (or via an app that's capable of setting those features)

This kernel doesn't have a special battery saver feature, because that's not supposed to be in a kernel. That has to be set in userspace and the kernel offers an API (sysfs) to allow userspace to accomplish this task. However this kernel is set up to allow as little overhead as possible, which ofc contributes to battery life.
[Nexus 5 Original Android Development] ajf64:
sorry i prob should of explained a little more Android 5.0 Lollipop has a battery saver mode that can be engaged either at 15% once you warned of low battery or by going in to your settings clicking battery and then going to settings in the battery tab and activated it this disables stuff like background data, notifications, vibrations, ambient display and other stuff like that with the stock configuration seems some kernels such as code_blue have expanded these settings like this

Lollipop Battery save ready (Enable Battery saver, turn screen off/on to enable dualcore @ 729MHz. To resume normal operation, Disable Battery saver, turn screen off/on again)

was wondering you had done any thing like this i know you already get wonderful battery life just this might squeeze out even more when you need it the most thanks for such a quick response

ill try looking at the api hooks in sysfs see if i can come up with something
[Nexus 5 Original Android Development] parkson:
Hoping for 5.1 goodness ?
[Nexus 5 Original Android Development] danyh_rrt:
link the compilation kernel use you?
[Nexus 5 Original Android Development] ranadroid:
That's trickster mod
[Nexus 5 Original Android Development] mjs2011:
Thanks. Using row scheduler or cfq?
[Nexus 5 Original Android Development] davy917:
UV -50 mV, and changed to Interactive governor. Didn't touch anything else.

I'm at 30% 14hrs uptime, 3 hrs SOT so far. I did about an hour of work on WiFi tether and 20 minutes of Sunday Ticket steaming today. Super impressed with temperatures during that usage :)
[Nexus 5 Original Android Development] globen:
Best kernel for nexus 5 hands down. Tried all of the kernels in development, this one gives me the smoothest experience as well as great battery life. I charged the phone up to 80% and now at 42% with 2.5 hrs of screen on time. Best by far. Tomorrow I'll do a full discharge. Thanks for a solid kernel!!
[Nexus 5 Original Android Development] toanau:
Do I need to wipe anything before or after flagging kernel
[Nexus 5 Original Android Development] shri_chanakya:
Am using noop
[Nexus 5 Original Android Development] fatappel:
609beac running great. Stock settings, heavy usage with multiple push mail accounts and about anything you can think of synced. Got over 6 hours screen-on time on first complete cycle....

Sent from my Nexus 5
[Nexus 5 Original Android Development] kydkupa:
Not sure if its been answered yet, but when I install this kernel on Cataclysm ROM I get boot loops. I even used flashify for the suggested boot.img in the op. Any advise?
[Nexus 5 Original Android Development] show-p1984:
Not without a log.

After the 'loop' go to recovery and pull /proc/last_kmsg