yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] ramjet73:
Speaking of kernels, did anything change in the ramdisk or build.prop for 9002 that would affect init.d processing? I merged the ramdisks the same way I did for 9001, by copying the directories and files for this ROM over those of the default, but init.d processing doesn't seem to be working for Linear L 3.2 like it was for 9001. :confused:

ramjet73
[Nexus 5 Android Development] sykopompos:
Nope. A init.hammerhead.rc change and file_contexts only. The new stuff coming into aosp sepolicy, I didn't want to take cause they seemed like they might cause some serious problems for us in the root community so I just cherry picked a few things

Sent from my LG-D851
[Nexus 5 Android Development] ramjet73:
I found the problem.

Linear L 3.2 needs the following statement added to the init.rc file:

# Include vendor ramdisk
import /init.linear.rc

That additional init file starts sysinit to activate init.d processing among other things. I don't know how it could have worked with 9001 unless I didn't actually copy over your version of init.rc when I thought I did. :confused:

All is well now and the updated version of the Linear L 9002 compatible kernel, attached to this post and updated in the compatible kernels post, now processes /etc/linear.conf as intended.

ramjet73
[Nexus 5 Android Development] tomzefi:
Been running this ROM. Is everyone flashing su kuz kernel is breaking it or the one in the ROM is not good enough. Shipped Su been good for me
[Nexus 5 Android Development] ramjet73:
The included Koush version of superuser is fine for most things but some apps don't work well with it like (not surprisingly) Chainfire's Stickmount for USB OTG. Chainfire's version of superuser (SuperSU) has pretty much become the de facto standard.

ramjet73
[Nexus 5 Android Development] tomzefi:
Yes. I like chainfire...its what I always use. But if koush works the so be it. I asked kuz I no some kernels kill root then I just reflash 2.02. Like I said if it works gonna stick with till it don't. This ROM is smooth though. Noticeable difference from the original. Bout to flash the linear .....thanks bro

---------- Post added 5th October 2014 at 12:14 AM ---------- Previous post was 4th October 2014 at 11:58 PM ----------

Ooooookay. Linear just unleashed this beast
[Nexus 5 Android Development] sykopompos:
Koush's superuser is just easier to diagnose logcats because unlike SuperSU, superuser wasn't updated for selinux so while superuser might throw one logcat denial, SuperSU throws 10 every 3 mins

Sent from my LG-D851
[Nexus 5 Android Development] DrearierJester1:
does this have the same app bugs on the official preview? Like Viber or Facebook crashing?
[Nexus 5 Android Development] Maxx247:
guys im going to flash this rom but just a confusion. currently im using another rom based on cm11(mahdi).so to flash this rom i have to go back to aosp kk 4.4(stock image) and then this rom ? or i have to do full wipe n flash this?
[Nexus 5 Android Development] ramjet73:
Just do a factory reset in TWRP or CWM and flash the ROM.

ramjet73
[Nexus 5 Android Development] donnyp1:
Yes, seriously. You gain nothing and lose more in the long run. This ROM runs great, as-is
[Nexus 5 Android Development] tomzefi:
Yep. Just do a full wipe and flash as usual. Flash the 9001 then the 9002 patch....

---------- Post added at 12:39 AM ---------- Previous post was at 12:36 AM ----------

You are rite. Over clocking and under volting do it every time. This ROM runs great even with the shipped kernel untouched. But I do find that the latest linear kernel really pinches the ROM in the butt.
[Nexus 5 Android Development] rahulpat13:
What a metaphor! Lol.. Awesome!
[Nexus 5 Android Development] drali500:
I am running 9001 with stock kernel?

Should I reflash before the patch or flash the patch only then flash the compatible kernel?
[Nexus 5 Android Development] sykopompos:
The patch contains the stock kernel and ramdisk so just flash the patch and then you can flash a different kernel if you like to

Sent from my LG-D851
[Nexus 5 Android Development] Apocalypse~:
I am running 9001, with the Arkenstone Kernel. Should I flash 9001, then the patch and kernel? Or just the patch and then, the kernel?
[Nexus 5 Android Development] tomhtg90:
from what i read

1. Flash 9001

2. Flash Patch 9002

3. (Optional) Flash custom kernel that u like
[Nexus 5 Android Development] WizardBGR:
Which custom kernel is compatible with this build and has s2w or dt2w? Please advice... :)
[Nexus 5 Android Development] ramjet73:
The OP's for the kernels that cover their features are all linked from the beginning of the compatible kernels post which is referenced at the bottom of the OP for this thread.

They all have touch wake options.

ramjet73
[Nexus 5 Android Development] WizardBGR:
Thanks! :) Now, another noob question - how to set those dt2w options via those kernels? I was familiar with hellcore and franco but they had dedicated apps... What's the deal here? Thanks in advance!
[Nexus 5 Android Development] ramjet73:
Again, that information is in the OP for each of the kernel threads.

For most of them you can use a tweaking app like TricksterMod or Kernel Manager, but for Linear L 3.2 only you need to edit the /etc/linear.conf file.

ramjet73
[Nexus 5 Android Development] turydios:
Great build for me, thank the work done, unless some application, everything works fine with 3.2 Linear, thank you very much.

<< Turydios >>
[Nexus 5 Android Development] ramjet73:
Test faux123 kernel

I'm not a big fan of [MENTION=3332811]faux123[/MENTION], since IMO he's too commercial for XDA, even soliciting donations in the updater-script for his kernels. However, I know there are some users here that like his work, and have invested in his apps.

There is a now a test version of the faux123 021 hammerhead kernel included in the compatible kernels post. It boots (see first screenshot) and that's about all I can say since that's all I've tested. I will try to answer questions in this thread since this is an unofficial version and support should not be requested in the faux123 kernel thread.

Don't forget to do a dirty flash of the 9001 ROM and 9002 patch if you want to try the faux123 test kernel and are currently running something other than the default (stock) kernel.

Edit1: NVM, cellular is broken, just like all the other KitKat kernels we've tried with this ROM. You can still use it with WiFi for testing and if anyone knows where there might be an L compatible faux123 kernel I can update it with the 9002 ramdisk.

Edit2: I found the L versions of the faux123 kernel here and the compatible kernels post has been updated with a version that works with the cellular radio (see second screenshot). The working kernel file is hammerhead-faux123-lpv-xxx_r7-9002.zip.

ramjet73
[Nexus 5 Android Development] mikkoc:
Do these apps work with this rom:

https://play.google.com/store/apps/details?id=com.tripadvisor.tripadvisor&hl=en

https://play.google.com/store/apps/details?id=com.ubercab&hl=en

They both crash for me, I believe due to this bug: https://github.com/square/okhttp/issues/967
[Nexus 5 Android Development] GzC:
There's L compatible kernel from faux123

faux.romhost.me/hammerhead/l/
[Nexus 5 Android Development] ramjet73:
Yea, I figured that out a few minutes ago. See the second edit to my post above.

I just updated the zip file in the compatible kernels post and now the test faux123 kernel has the 9002 ramdisk and working cellular. :D

The compile date is the same as the 021 KitKat version so I'm guessing the L kernel has the same features. I haven't been able to find an OP or changelog for the L kernels.

Edit: As much as I don't care for the commercial orientation of [MENTION=3332811]faux123[/MENTION], his L kernel seems to run well with this ROM, and I haven't found any issues with it yet. I'm using TricksterMod to activate DT2W.

ramjet73
[Nexus 5 Android Development] GzC:
Just saw that edit after I've submitted the post. Lol. :p

Faux's kernel always awesome and running well in any aosp roms, I've used it since Nexus 4.
[Nexus 5 Android Development] peecs121:
OK so I flashed back to stock so I can flash the newest patch cause I was on a diff kernel and I get a error every time I try to flash the newest patch. Do I need to flash the first patch you provided first then flash the newest patch or what?

Nexus 5 running Android L w/360 Launcher
[Nexus 5 Android Development] ramjet73:
You should be able to flash the 9002 patch on top of the 9001 ROM and get everything you need. Did you check the MD5 on the 9002 patch zip file (when it is on your phone) against the one on AFH?

ramjet73
[Nexus 5 Android Development] peecs121:
I tried to flash the patch and still a no go

Nexus 5 running Android L w/360 Launcher
[Nexus 5 Android Development] lets_zock:
Sorry if this question was already asked, I searched but the Tapatalk search engine is quite awful.

I'm currently running the L preview, can I dirty flash this on top?

I know, clean flash is the only one recommended and I don't have the right to report bugs without a clean flash, but Titanium Backup won't work for me since L.
[Nexus 5 Android Development] 33t:
guys I searched,...

the patch is giving me a status 7 error.

Appears my phone isn't being recognized as a hammerhead when i try to side load the patch.

i just flashed the latest rom also - side load, clean etc.

help
[Nexus 5 Android Development] lets_zock:
Did you try redownloading the patch?
[Nexus 5 Android Development] badboy47:
You can downgrade as usually and you will not lose your imei. Just download 4.4.4; copy it to your phone. Reboot to recovery. Wipe format system, cache partition and dalvik. Flash 4.4.4 ROM and reboot :). I hope that's helpful.
[Nexus 5 Android Development] 33t:
that isn't the problem. but no i didn't
[Nexus 5 Android Development] andreMusers:
ok thanks bro
[Nexus 5 Android Development] Eduardo C.:
Ringtone length

Is there a way to increment the ringtone length? I mean, letting the ringtone ring for about 1 minute...

Thx
[Nexus 5 Android Development] lets_zock:
How do you know without trying? As far as I know Status 7 can mean almost everything. For me, redownloading fixed the issue in most of the cases.
[Nexus 5 Android Development] 33t:
thats not it.

status 7 means my device isn't being recognized as a "hammerhead" and so the install script isn't executing.

I was coming from Slim and i guess somewhere along the line my phone lost the tags (or whatever) that say it's a hammerhead.

The weird thing is i went into the updater script in the zip file for the patch and deleted those asserts, but the script then failed for some other unspecified reason.

I gave up and just flashed back to stock with fast boot.

This is a great ROM but i need the patch to work to run it.

I bet if i went and put CWM back on my phone and reflashed everything it would work, now that I've fast booted back to bare bones stock... .but i've had enough android today for the next two weeks.

I don't know how you devs keep it up. much appreciated.
[Nexus 5 Android Development] lets_zock:
Did you see an error messege telling you that you have the wrong device? As far as I see in the script it should tell you the error.
[Nexus 5 Android Development] donnyp1:
Running just fine here after 9002 patch. No issues at all. Stayed with stock kernel
[Nexus 5 Android Development] peecs121:
Same here

Nexus 5 running Android L w/360 Launcher
[Nexus 5 Android Development] ramjet73:
What recovery version are you running?

Can you do an "adb pull /tmp/recovery.log recovery.log" right after the flash fails and post that file here?

Also, why are you guys sideloading instead of just booting into recovery and flashing the 9002 update?

And one last thing. Are you doing any formatting before flashing the 9002 update?

Not necessarily. We need to see your recovery.log file right after the flash fails.

ramjet73
[Nexus 5 Android Development] peecs121:
I'm on the newest CWM Recovery and all I'm doing is flashing the update and that's it

Nexus 5 running Android L w/360 Launcher
[Nexus 5 Android Development] Sad56:
Try to reboot recovery and flash again. Sometimes it work.

/\/5 $|¡/\/\ €||¡b€r@T°r
[Nexus 5 Android Development] ramjet73:
We need to see your recovery.log file.

It's not hard to pull that and post it here if you are sideloading already.

ramjet73
[Nexus 5 Android Development] 33t:
yes.

well.... the field was blank, but yes... wrong device.

this is for the patch, mind you, after flashing the hammerhead ROM.

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

i would post mine, but like i said i already went back to stock recovery / ROM.

---------- Post added at 06:54 PM ---------- Previous post was at 06:51 PM ----------

and yes... i was on newest CWM recovery
[Nexus 5 Android Development] lets_zock:
Can I flash this directly over the top of the L preview or will it mess up things?
[Nexus 5 Android Development] ramjet73:
They have a different base do you really need to do a clean flash ("factory reset") before flashing this ROM when coming from the official preview. Users that tried dirty flashing have run into issues like the soft keys not working properly.

ramjet73
[Nexus 5 Android Development] larwindcunha:
Even me. Status 7 error. Same problem here.
[Nexus 5 Android Development] ramjet73:
While I can appreciate that there is no way we can help resolve this issue without the appropriate documentation. Hopefully someone else who is experiencing this problem can and will provide it.

It really sounds like a bug in the current version of CWM to me. Specifically, I think the getprop statement in the updater-script is receiving an incorrect value from CWM.

My recommendation is to upgrade to TWRP 2.8.0.1 since it has many features that CWM doesn't include and is supported by a team instead of one developer so it tends to have fewer bugs.

:eek:

Please submit your recovery.log file so we can help identify and hopefully fix this problem.

It's easier to just report and complain about problems than to provide the documentation needed to resolve them but that's the only way they get fixed.

ramjet73
[Nexus 5 Android Development] sykopompos:
So a few people are having this status 7 issue? Is it just the latest cwm that is causing it or is it happening on twrp?

I pulled the get.prop lines directly from the ROM because I didn't want someone accidentally flashing the wrong device version and figured that be a safe bet measure

Sent from my LG-D851
[Nexus 5 Android Development] ramjet73:
I think everyone that has reported the problem is using CWM but haven't been able to confirm that since apparently no one is motivated enough to submit a recovery.log file. :(

The simple fix would be to upgrade to TWRP 2.8.0.1 since I haven't seen anyone reporting the problem using that version of recovery.

I did notice that the update-binary is older (by about a year) in the update zip than the one used in the ROM zip file so I've replaced the update-binary in the attached update zip with the one from the ROM zip and users having the "status 7" problem can try that but I'm not optimistic it is going to solve the problem.

ramjet73
[Nexus 5 Android Development] sykopompos:
I blame you on that then since I used your official bbw6 zip as the base zip and just fixed it for what I needed :p

Sent from my LG-D851
[Nexus 5 Android Development] ramjet73:
No way! :mad:

That worked perfectly for its intended purpose and seems to be fine for the update zip as long as people use TWRP. I really don't think the update-binary is the cause anyway (it's more likely the recovery itself) but I'm not going to hold my breath waiting for someone with the problem to test it. :rolleyes:

And there was no assert statement in the zip file that I gave you. ;)

ramjet73
[Nexus 5 Android Development] gtj0:
The update works in TWRP and Philz CWM 6.57. It does not work in CWM 6.0.4.4.

Log attached.
[Nexus 5 Android Development] gtj0:
The 'newer-binary' update also fails with CWM 6.0.4.4 but with a different reason.

EDIT: The 'newer-binary' doesn't work in TWRP either. The log just says 'Error executing updater binary'
[Nexus 5 Android Development] psycho693:
You might want to flash a multi DPI play store though I would assume it will eventually catch up and the play store will say incompatible.
[Nexus 5 Android Development] ramjet73:
Yea, I got it and couldn't decide what to respond at the time and then forgot to follow-up. :o

I'm not big on chat sessions but if they are focused on solving a particular problem I'd be happy to participate. Kind of like shopping, I tend to be very targeted. ;)

ramjet73
[Nexus 5 Android Development] robertm2011:
I also am using this ROM with multirom (it's my primary) and everything just works.I've put a handful of apps on and they're working fine. Thanks dev, great ROM!
[Nexus 5 Android Development] psycho693:
OK well I was thinking of starting a hangouts group for the multiple threads of this ROM? [MENTION=1050103]sykopompos[/MENTION] and ramjet73 what do you think? And anyone else? Would you all support this idea or am I crazy lol

And if your all for it sykopompos would you be willing to put the link in the op if not I understand its just easier for people to see and access. It would kind of be irc or something.
[Nexus 5 Android Development] sykopompos:
What had happened and a where?

Sorry, I went out and forgot my phone.

As for the files, I forgot to send them but they are the same ones ramjet posted up. I would start testing on seeing if we just need the ril stuff to fix the radio or if it is the qmux which is also involved with the radio and camera
[Nexus 5 Android Development] psycho693:
OK I will test the files out and let you know how it goes. It may not be till tomorrow afternoon though. Hopefully that's OK.
[Nexus 5 Android Development] sykopompos:
That's fine with me. I have been caught up with other things so I haven't come back round on it yet.
[Nexus 5 Android Development] hondajohn88:
Try using Textdroider DPI from Playstore, I use it for the ROMs I use on my phone, and it works perfect on this build too. :)
[Nexus 5 Android Development] ramjet73:
Just a reminder that I'm waiting to test a version of the Linear L kernel attached to this post with your ramdisk included. No rush, just whenever you can get to it.

I think that's our best bet to get the first working custom kernel with no conflicts for this ROM unless [MENTION=1316336]defconoi[/MENTION] wants to develop one for the Nexus 5. ;)

ramjet73
[Nexus 5 Android Development] sykopompos:
**** I forgot again, damn 1+1 is keeping me busy and trying things to get it to work. It is sucking up way too much of my time.

I'm gonna go run and get some caffiene and I will do that for you
[Nexus 5 Android Development] eluspo:
Anybody experiencing low call volume?

- i've raised the volume for speaker and headphone via nexus 5 volume booster, idk if that may have caused.
[Nexus 5 Android Development] inspeckta_dek:
Volume booster worked?
[Nexus 5 Android Development] eluspo:
Yup!
[Nexus 5 Android Development] sykopompos:
I'll look over this tomorrow and see what is causing the lower volumes when they shouldn't be
[Nexus 5 Android Development] sykopompos:
Check your pm [MENTION=275009]ramjet73[/MENTION] I sent you over a test linear kernel boot.img with the his kernel and my ramdisk together. I sent hottix a pm and asked if he would mind if we made it an option to use his kernel modified to run on this so give it a try while we wait for a response
[Nexus 5 Android Development] razrlover:
I know Hottix is no longer building his linear kernel so hopefully it's a go. He seems like a really legit dude.;)
[Nexus 5 Android Development] SamEkinci:
Thanks for the replies.. I had to go back to PAC because radio and Wi-Fi were giving me troubles.. Including some apps not connecting to data.. Like Google play music wasn't connecting to data while had lte and chrome was working fine... Tried with both radios and did complete wipes including going back to stock..

Tonight I will try to get some logs while trying it one more time..
[Nexus 5 Android Development] sykopompos:
Alright guys, I gotta head to bed. Gotta be in tomorrow at 6:30 and I know on Thursday I will be working late so the game plan since I'm swinging back around to do b6 now that I relieved myself of my tie up is.

Tomorrow.

Gonna look at what gapps can be updated and/or removed to leave to the user to get from the play store.

Clean up the updater scripts on all the builds.

Look into the radio issue on deb (this is beyond due)

Look into the low sounds issue on hammerhead

Thursday, taking the night off to relax

Friday.

New prop testing so test builds for mako, flo and n5 \•/

Gonna try merging in some more flo when it comes to the props on mako to see if I can update libgsl and egl files that way.

New aosp ramdisk if there is anything new and also fresh sepolicies plus post up how to make it permissive when making a policy.

Gonna be going around for avc denials Friday night/saturday on this on each device to clean up the log spam.

Merge in the newer animations and res files from the SDK, fonts are already in.

Little bit more house keeping and then if test builds are good then we will make b6 out of it.
[Nexus 5 Android Development] sykopompos:
You can wait and see if hottix gives permission to use his kernel or not and give it a go from there. I'm also gonna be updating the props this weekend so that means new ril files and sometimes newer WiFi configurations
[Nexus 5 Android Development] SamEkinci:
:victory:

Yeah? Perfect.. Kind of drawing blank here.. :)
[Nexus 5 Android Development] sykopompos:
Yup, I had it there and it was easier then writing a new one and add the assert.get.prop and install boot.img

Sent from my LG-D851
[Nexus 5 Android Development] ohad129:
Recovery? What for?
[Nexus 5 Android Development] Ben36:
Works fine apart from the soft keys which I have the fix for. I didn't clean flash this over L release and never have ?
[Nexus 5 Android Development] ramjet73:
Thanks for providing the recovery.log. :good:

Here's are the relevant pieces:

In the initialization section:

ro.product.device=hammerhead

So CWM does recognize it as a "hammerhead" device which means you have the correct version of CWM for your phone.

Towards the end when it is actually attempting to flash the 9002 update zip file:

-- Installing: /sdcard/0/Download/hammerhead-n5-9001-to-9002-patch.zip
Finding update package...
I:Update location: /data/media/0/Download/hammerhead-n5-9001-to-9002-patch.zip
Opening update package...
Installing update...
[] is not an int
script aborted: This package is for "hammerhead" devices; this is a "".
This package is for "hammerhead" devices; this is a "".
E:Error in /data/media/0/Download/hammerhead-n5-9001-to-9002-patch.zip
(Status 7)
Installation aborted.

The value being return by CWM to the updater-script for getprop("ro.product.device") is actually null not blank but that is definitely the problem. I think it may be the "[] is not an int" that is the root problem but I don't understand what that is referencing. :confused:

Someone should probably report this bug to Koush but I gave up on CWM a long time ago so I'll leave that to someone who uses it. Part of the problem is that since Koush can't keep up with all the devices, he encourages other developers to port to the ones that he can't support, but I doubt that's the case with the Nexus 5.

Thanks again for the recovery.log file.

That was just an example.

Other users have reported different problems after dirty flashing over the official L preview and I really can't recommend that to new users coming to this ROM for the first time.

ramjet73
[Nexus 5 Android Development] gtj0:
Yeah, there's nothing you can do with this. I don't use CWM any more either. I just happened to have the images handy and it was easy enough to boot them from memory with 'fastboot boot'.