yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] ramjet73:
I merged the "most likely" files with the 5.9.6 ROM zip and flashed that with the Hellscore kernel (before booting) and cellular was working (see first screenshot).

Since that worked I went back and flashed the same ROM with the default kernel to see if that was still working and it was (see second screenshot).

We still need more testing for each configuration to make sure other things didn't break.

I guess that's progress. ;)

Edit1: I just tested the camera with Hellscore and the screen is flashing between the viewfinder image and a green screen. Superuser seems to work OK.

Edit2: I went back to the default kernel with the "most likely" files added (5.9.6.1) and the camera was OK.

I guess it's still not 100% compatible with KitKat kernels yet. Do you want me to merge the "maybe" files in too?

ramjet73
[Nexus 4 Android Development] manueltts:
I can edit photos, 5.9 build, clean install.

Sent from Nexus 7.2 Flo using Tapatalk.
[Nexus 4 Android Development] dougiefresh36:
I searched the thread and can someone confirm the maps is indeed broke? Using turn by turn navigation the arrow doesn't move as I progress. Thank you! Great build by the way, butter butter.
[Nexus 4 Android Development] googleygoggles:
Maybe... Maybe not...
[Nexus 4 Android Development] sykopompos:
Just woke up, that makes me happy, so it is definitely one of those that is killing the radio.

Give the maybe a try too.

Check out and see if battery saver mode will work once you try the maybe

Edit1 if this works, we will have to track down exactly which one it was killing the radio and test some more
[Nexus 4 Android Development] 0.0:
Update Google+. That happened to me once. I updates and it worked
[Nexus 4 Android Development] sykopompos:
Hey [MENTION=275009]ramjet73[/MENTION] should we rename the next series to wabbit season??

Rabbit Season, Duck Season trilogy.: http://youtu.be/17ocaZb-bGg

Pretty sure there won't be any more rabbits left to eat if we keep catching them
[Nexus 4 Android Development] ramjet73:
That's fine with me. I like Elmer Fudd. ;)

ramjet73
[Nexus 4 Android Development] sykopompos:
Any luck with the maybe files?
[Nexus 4 Android Development] sykopompos:
I'm hunting bigger game now, I'm looking for the elusive bigfoot
[Nexus 4 Android Development] sykopompos:
So qseecom is Qualcomm's secure communications environment and everything in the radio routes through that, then that routes through the qmi which is their interface. I don't think the qcril files did much of anything so the maybe files with all the qmi stuff should be the icing on the cake [MENTION=275009]ramjet73[/MENTION]
[Nexus 4 Android Development] ramjet73:
I merged in the rest of the files from /prop test/maybe (8 files in /vendor/lib) and now cellular communications is broken with the default kernel.

The ROM zip that had cellular working with your "most likely" files and Hellscore is uploaded here and I've attached the original lpv81c versions of all the files in your "prop_test.zip" file as "prop_test_lpv81C.zip". I've had enough flashing and testing for today but maybe another Nexus 5 user would like to try that ROM version with their favorite custom Kernel to see if it works for them and if they get the green screen on the camera or any other new problems.

Now would be a good time for the users that really want a custom KitKat kernel with the hammerhead ROM to jump in and give it a try. :good:

ramjet73
[Nexus 4 Android Development] psycho693:
I will test and verify for you. What version of hellscore did you flash so I can make sure we are testing the same thing and then after that I will test others and report. Thanks [MENTION=1050103]sykopompos[/MENTION] and [MENTION=275009]ramjet73[/MENTION]
[Nexus 4 Android Development] ramjet73:
Thanks!

I've attached the hellscore version I used but it might be better if you try code_blue or another kitkat kernel for the Nexus 5. I'm anxious to find out if other kernels have the camera "green screen" problem that I experience with hellscore because I know how hard those camera issues are to track down.

I was actually planning to try ElementalX next to satisfy my own curiosity but if you use that kernel you're welcome to try that.

ramjet73
[Nexus 4 Android Development] sykopompos:
It could just be hellscore itself that breaks the camera or it could be I overreached on the most likely files and that screwed the camera up and one of those files derped us and it isn't even the radio killer (actually I had a first zip with just the most likely and then went back for the qmi files in the maybe) so now it is just finding out exactly which one kills the radio in the most likely files
[Nexus 4 Android Development] sykopompos:
So I was trying some things and each time I come down near libc it takes everything out and it is just chasing one thing after another. Maybe the answer isn't chasing mako in aosp, it is to chase flo since we are using that as our base
[Nexus 4 Android Development] psycho693:
I will test them all my friend and to be sure I will flash the ROM make a nandroid and test then erase and restore nandroid for each kernel I test that way there will be no conflicts between kernels

---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------

Well if you need anything specific tested like that let me know and I will be glad to test it out
[Nexus 4 Android Development] sykopompos:
I think using the zip that ramjet sent back, work the proprietary files backwards from the complete package and find out exactly which file is killing the radio because it is probably just one or 2 and the other files might have taken out the camera and are not needed to be swapped out
[Nexus 4 Android Development] ramjet73:
I just flashed ElementalX 2.0 over 5.9.6.1 and the camera has the flashing green screen with that too. Now would be the time to back off files from the "most likely" list to see if the camera can be fixed without breaking cellular, but I'll leave that to [MENTION=3754150]psycho693[/MENTION] if he is able to confirm that he gets the green screen in his tests with kitkat kernel(s).

ramjet73
[Nexus 4 Android Development] sykopompos:
If I had to take a guess from my knowledge, I would probably say it is qmuxd that is taking out the camera or qseecom but those might be the exact same ones that are making the radio work :banghead:
[Nexus 4 Android Development] kittuboy:
Another secret. If you look around in three advanced settings, you can configure lux to go to sleep when apk files are being sideloaded. That is a faster job than reinstalling. Also, that's what I did. :)
[Nexus 4 Android Development] ramjet73:
That's exactly what I was concerned about earlier today.

When you mix and match components at different levels you can fix one thing but break several others and when the new issues show up their dependency on the original change isn't always apparent.

If [MENTION=3754150]psycho693[/MENTION] is able to isolate the file that is borking the camera, I suggest freezing the hammerhead ROM there and have the Nexus 5 users in this thread test it for a few days before posting it as an official release. The 5.9.6 version is rock solid and it would be a shame to give your hammerhead version a bad reputation out of the gate.

Or maybe you could post 5.9.6 as the official release and 5.9.7 (or whatever you decide to call it) as experimental for users that want kitkat based custom kernels.

ramjet73
[Nexus 4 Android Development] sykopompos:
Oh I wasn't planning to release it out the gate as the official. Definitely a test version.

It might end up having to be a bit more work to get it to work properly but it can be done and had been done with mako to make some kit Kat play with L
[Nexus 4 Android Development] psycho693:
here is a logcat from hellscore, there is a lot of wierd camera issues. its long and i suggest you take a skim through it, im onto codeblue now.

all my logs will be going here.

https://drive.google.com/folderview?id=0B33hv82TaNETR0h1V25qZzJZaDA&usp=sharing
[Nexus 4 Android Development] googleygoggles:
Been gone for hours and only 2-3 pages are new... Other days I go for 5 minutes and I already have 10 pages to read
[Nexus 4 Android Development] sykopompos:
Can you grab a dmesg?
[Nexus 4 Android Development] psycho693:
lol derp yeah i can
[Nexus 4 Android Development] sykopompos:
Thank you. It is a socket not going through according to what I see in the logcat so that might be qsec
[Nexus 4 Android Development] sykopompos:
Its been a bit quiet today. I was trying to trade my car in for a better model and just kinda thinking about things to do
[Nexus 4 Android Development] psycho693:
so before you asked for the dmesg i tried code blue and it wouldnt boot at all and so i restored boot, efs partitions and tried to flash hellscore again but now mobile doesnt work at all. so im clean flashing everything again and i will get the logs for hells core and i will skip code blue till the end
[Nexus 4 Android Development] sykopompos:
Isn't code blue a full boot even on kit kat and not a anykernel format?

That's probably why it took it out
[Nexus 4 Android Development] sidnoit22:
I have those Mint Cigarette Toffee's if you want to trade it. :o
[Nexus 4 Android Development] psycho693:
oh yes your right my bad i forgot lol but the dmesg is in the folder i linked earlier on to another :)
[Nexus 4 Android Development] ramjet73:
But mako did not have an official preview release. The benchmark is a little higher for hammerhead.

So far the main selling points for your hammerhead version of L over the official preview are a completely functional superuser, smoother operation and fixes for some things that don't work well or at all on the official preview. But Nexus 5 users are not going to give up stability to get those things, especially when that means they are really no longer running the preview as designed by Google.

Once you allow for kitkat kernels with L on the Nexus 5 you are opening up a Pandora's box of questions about battery life, overheating, reboots and many other issues that may have nothing to do with the ROM. I know that's already happening with the Nexus 4 but I believe it will be worse with the Nexus 5 because some preview users will try your ROM just to get support for more custom kernels. And the kernel developers for the Nexus 5 aren't going to be sympathetic to users that come to them with problems trying to run their kitkat version on L, especially since the Nexus 5 already has kernels specifically designed for L. If you are committed to supporting kitkat kernels on your hammerhead ROM make sure that support is solid so you don't need to deal with all those issues or you won't have time left for development. :(

I know you want to prove that it can be done, but just consider the overall good and what most preview users are going to be looking for. You've done a great job so far and I'm sure things will only get better in the future. :good:

ramjet73
[Nexus 4 Android Development] sykopompos:
You know you got an extremely good valid point. Most kernel devs aren't gonna be that supportive. Plus you are right about opening a door that I really don't want to.

We kinda did prove that we can use them and can probably solve this no problem but that door being opened will be a major pain in the ass
[Nexus 4 Android Development] psycho693:
i just tested bricked and signal works fine camera is still broken. logs on in my drive folder
[Nexus 4 Android Development] sykopompos:
**** [MENTION=275009]ramjet73[/MENTION] why did you have to inject logic and intelligence into this!!!!
[Nexus 4 Android Development] psycho693:
should i stop testing?
[Nexus 4 Android Development] googleygoggles:
And I can trade a nexus 4 for a car... Then sell the car and by 20 nexuses!
[Nexus 4 Android Development] ramjet73:
You know you can make the L version of code_blue work with your ramdisk changes and the same is probably true for the L version of the Linear Kernel which is also flashed as a complete boot.img. If you can tell me exactly what you did to incorporate your ramdisk changes into code_blue I will try to create a flashable zip that will do that so that Nexus 5 users can download those kernels from their home threads and automatically modify them for use with your hammerhead ROM.

You could still keep a parallel version with kitkat kernel support (5.9.6K?) but clearly labeled as experimental and "as is" with no support for kernel related problems.

I'm anxious to hear what you and any other Nexus 5 users active in this thread think is the best approach to supporting this ROM on hammerhead.

And what do you think will make an official preview user change to/start with this ROM versus the official version?

ramjet73
[Nexus 4 Android Development] psycho693:
I totally agree with you. So far bricked and hellscore(the one you gave me) works if you have any other kernels you want tested let me know.
[Nexus 4 Android Development] sykopompos:
I would personally like to know exactly what is the one file causing the camera to break but an experimental version or a zip flash to use those kernels with no support might be a great idea.

Let's see what n5 users say

As for the boot.IMG, I just extracted the zimage and packed it right up in with my ramdisk. Is there a reverse any kernel option where instead of replacing the kernel, we can replace the ramdisk instead?
[Nexus 4 Android Development] psycho693:
Simply they need to try it. This beta/release is so much more stable then the official and that says so much. We need to get this ROM shared in the n5 thread and see what people have to say. I don't think we should support kit Kat kernels that are available now because we can't garuntee stability but we can leave the option open like you said.
[Nexus 4 Android Development] ramjet73:
Please don't throw any eggs or tomatoes!

I was just thinking that if the script for L kernel compatibility works we can call it the Energizer. ;)

ramjet73
[Nexus 4 Android Development] sykopompos:
Well [MENTION=275009]ramjet73[/MENTION] what we could do is 2 things.

1.) Just make a update.zip that pushes the likely good folder into the ROM so users can experiment with kk kernels and maybe an aspiring user can figure out exactly what is breaking the camera socket there.

2 a reverse anykernel where you can flash a full boot image then instead of packing back in the current ramdisk, it would pack mine in instead
[Nexus 4 Android Development] ramjet73:
#1 is easy, although it would be good if the actual file(s) required are identified first, but I thought you were merging your ramdisk with the developer's version rather than replacing it for #2. Since there may be some stuff in the original version that is important to the kernel is there any way to merge the two? I'm not really familiar with building a ramdisk.

ramjet73
[Nexus 4 Android Development] sykopompos:
Not really, would have to modify each ramdisk of each kernel to do that if that if they are modifying the ramdisk in any way plus a lot of the magic here happens in the ramdisk itself.

Also most kernel devs are actually modifying the ramdisk anyway and are just putting out a whole boot.img because it is sometimes a bit simpler.

As for identifying the exact file, that is something that can only be done by trying to play with them and in the process you might find the one file need (it could just be the qcril stuff because that is Qualcomm ril files and the other stuff might be breaking the camera so we might not even need to worry about it) but I think even if we can nailed down what is breaking the camera and still keep the radio working in kk kernels, it would probably still be best to keep it as a no support thing
[Nexus 4 Android Development] groovepeppy:
i'm reading the last 10 pages and couldn't find any important bug by upgrading from 5 to 5.9

does it worth to upgrade since i felt the 5 is already useable for daily driver

thank's before
[Nexus 4 Android Development] ramjet73:
This looks promising as a possible tool for ramdisk modification. Can you tell me exactly what needs to be added to the kernel developer's ramdisk to support your requirements? Isn't [MENTION=1316336]defconoi[/MENTION] doing that already for his "L" version kernels? I know he uses the ramdisk for parameter initialization in that version versus an init.d script in the anykernel version.

[MENTION=3754150]psycho693[/MENTION] already indicated that he is willing to help with that. Maybe he can move on to that process of elimination while I try to figure out a way to merge the two ramdisks?

For the Nexus 4 it's a new base and might resolve some problems in B5, but if you're not experiencing any there's probably no need to upgrade. It's also a little smoother than B5.

ramjet73
[Nexus 4 Android Development] groovepeppy:
the first bold is ok

the second bold is turning me back to deep space lol

i guess i'll try to flash the 5.9 then haha

thank's for the super quick response :good:
[Nexus 4 Android Development] sykopompos:
That actually does look extremely promising and no, defconoi was packing up the entire ramdisk from the github source since it packs the boot image up with a kernel and the ramdisk.

As for what is needed, the whole entire ramdisk. Everything is change from the ueventd to the sepolicy to the inits to the binaries (only one I can't change is healthd cause it is connected into the framework) but almost the entire ramdisk is different except for like maybe three files
[Nexus 4 Android Development] buru898:
By any chance do you have something like f.lux or a screen dimmer on? Those are known to not let you press the install button. Disable and overlays. Even lmk might cause that.
[Nexus 4 Android Development] ramjet73:
Okay, how can I view the contents of a ramdisk so I can compare yours to the one(s) included with the kernel(s).

Edit: These tools might work, but only on Linux. I might be able to use that injector tool in recovery if I can figure out exactly what needs to be done.

ramjet73
[Nexus 4 Android Development] sykopompos:
You would have to split the boot image with either split_boot or abootimg. All the ramdisk files for mine are up on github under boot
[Nexus 4 Android Development] ramjet73:
See the edit to my last post for another possible alternative.

ramjet73
[Nexus 4 Android Development] 0.0:
[MENTION=1050103]sykopompos[/MENTION] so I've been keeping up with some of the posts for mako and those files. So my question: is it possible to have Bluetooth fixed with those files? Or have you already concluded it isn't possible?
[Nexus 4 Android Development] ramjet73:
[MENTION=3754150]psycho693[/MENTION] are you still here?

I think [MENTION=1050103]sykopompos[/MENTION] might have given some suggestions for files to revert to the lpv81c versions to isolate the one(s) that fixed the kitkat kernels but do you need anything more specific to do that?

ramjet73
[Nexus 4 Android Development] sykopompos:
I think instead of merging them, we just use the straight up replace method and from that you can just use the ramdisk from the port and basically delete the old ramdisk and replace it.

We have init.d support built right in but most of everything there is either different from the official preview because it comes from current aosp or it is way newer than kit Kat which most devs would be using so it comes down to incompatible with other ramdisks anyway that you look at it
[Nexus 4 Android Development] psycho693:
Either I need the files or someone to pack them up for me. But I'm here for a little bit still. Whatever you need though just let me know. OT a little but what if we create a hangouts session so we can talk instantly.
[Nexus 4 Android Development] sykopompos:
I haven't tried it yet. I have been trying to go at merging in more aosp on my mako going after the egl. I already concluded this is gonna be a pain in the ass. Right now I'm trying it with flo compiled into mako since our base is flo
[Nexus 4 Android Development] sykopompos:
My hangouts is always open and available and is the same as my XDA name at gmail
[Nexus 4 Android Development] ramjet73:
The files you need to back out the kitkat kernel "patches" in the 5.9.6.1 ROM are attached to this post.

[MENTION=1050103]sykopompos[/MENTION] had some suggestions about which files to try first.

ramjet73
[Nexus 4 Android Development] psycho693:
OK no problem I will put it together and report back tomorrow. Is that OK? Its 2 am here and I need to get up at 7 lol

Edit: [MENTION=1050103]sykopompos[/MENTION] send me a list of the files you want tested and I will be sure to do it
[Nexus 4 Android Development] ramjet73:
OK, but I'd still like to take apart the boot.img files from code_blue and linear just to make sure they are not doing anything significant in their ramdisks. I wouldn't want to advertise those kernels as supported with your hammerhead ROM unless they behave exactly the same as flashing to the official L preview, which wouldn't touch their ramdisks.

That's great. Get some sleep.

Thanks for your help. :good:

ramjet73
[Nexus 4 Android Development] sykopompos:
It's 2 am here too and I'm hanging with my son all day tomorrow.

I'm getting the new device threads together and just gonna kinda boiler plate the op and have device specific stuff in the 2nd post plus a link to all the devices downloads in one folder for each build to keep then together

I'll put a package together for you before I go to sleep
[Nexus 4 Android Development] sykopompos:
Do you need me to unpack them for you and send them to you?

I should still have code blue unpacked
[Nexus 4 Android Development] psycho693:
That would be great and thank you. Have a great day with your son tomorrow! I'm going to sleep now. ;)
[Nexus 4 Android Development] ramjet73:
No, that's OK.

Finish what you are doing and get some sleep. I'll figure it out in the morning.

ramjet73
[Nexus 4 Android Development] sykopompos:
Hey ramjet? How do I make a block like I have in the op to separate things. Ih8ra!n let me use his template but I'm unsure how to do it.

Also how do you do the click to show more things?

Could you do a basic one for each of those so I can pull it from your post and use it

Edit.I'm gonna be up for a few more hours working on stuff. I'm not picking my son up till about noon and I had a Edison
[Nexus 4 Android Development] ramjet73:
This is an example of hide:

1. One

2. Two

3. Threee

I'm not sure what you mean by blocks but if it's the shaded areas those are just quotes without actually quoting:

And or course there's the code box that you are probably familiar with already:

this would normally be code or command line instructions

HTH

ramjet73
[Nexus 4 Android Development] bitstra:
BTW [MENTION=1050103]sykopompos[/MENTION] - I've requested a developer acces to Android File Host

- So 'Bubble Launcher' BBW Free Edition for this thread will go it's way -
[Nexus 4 Android Development] sykopompos:
thank you ramjet, my forum-fu is a bit weak
[Nexus 4 Android Development] sykopompos:
alright. I started with deb. gonna boiler plate it across to flo and hammerhead while also redo our op

deb

http://xdaforums.com/nexus-7-2013/development-lte/l-android-lpv-dev-deb-t2856915#post55016443+

flo

http://xdaforums.com/nexus-7-2013/development/l-android-lpv-dev-flo-enhanced-t2856920#post55016534

hammerhead http://xdaforums.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934
[Nexus 4 Android Development] ramjet73:
You're welcome.

Those quotes disappear when you quote another post (as opposed to editing the original post) but it's just the standard "(quote) text (/quote)" markup (substitute brackets for the parenthesis) to get the shaded boxes.

If you haven't already, make sure you check with the XDA moderator who is the OP for the master Nexus 5 preview thread before opening your development thread for hammerhead or he may close it.

ramjet73
[Nexus 4 Android Development] sykopompos:
I just sent him a pm to give him a heads up on what it is

I will do hammerhead in a few minutes once it is done reuploading to the generic folder to keep them all together.

Take a look at the new threads and tell me what you think of the op
[Nexus 4 Android Development] ramjet73:
I already checked out the flo and deb versions and they look great! :good:

ramjet73