yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Carlos_Manuel:
Errors are caused by old init, adbd and ueventd files. Tuna's init, adbd, ueventd files are Kikat's and Android L has newer ones and tuna's init doesn't regocnize some new lines in init*.rc files...

Errors are not kernel related

Yesterday I was too lazy to read the kernel log..
[Samsung Galaxy Nexus] JustArchi:
Of course not, errors are ramdisk-related :).
[Samsung Galaxy Nexus] Carlos_Manuel:
Yep. :)

Today I try to continue working on this port. My goal is try getting this to boot, so other devs who are better with porting, can make this working. :victory:

I am too interested to try Android L preview, so I am not going to wait months to get sources for Android L.. :cool:
[Samsung Galaxy Nexus] Ashutos1997:
Thanks for helping ;)
[Samsung Galaxy Nexus] Carlos_Manuel:
Gonna modify ramdisk again.. let's see if I get it fixed, this time N5 Android L will or should help me! :cool:
[Samsung Galaxy Nexus] Ashutos1997:
Go Carlos Go ! We are with you ;)
[Samsung Galaxy Nexus] samcortez:
Wow, I didn't see it coming. Anyway, good work, dude! I wish know android better and then be able to help you.
[Samsung Galaxy Nexus] KShion619:
Which kernel ramdisk are you changing? The Nexus 5's? or AOSP tuna? Mind you that we havent gotten a kernel that high to boot and it might be best to backport whatever the difference is, although im not sure if its possible without source. Just looked at this thread and not-so-shockingly you had better knowledge on what to do to port than my port in the toro forums which i kinda just threw together by your standards :eek:

Good luck and if theres any way i can help i can, and id reccommend you get last_kmsg logs as well, as this is possibly a kernel crash, gives more info to work with
[Samsung Galaxy Nexus] kezn715:
Thanks Carlos, all the best ! Sorry that I don't have any great knowledge about cooking rom, couldn't help much... But I do support you from deepest from my heart ☺
[Samsung Galaxy Nexus] Carlos_Manuel:
Tuna's KK Ramdisk with N5 L ramdisk changes...

Currently done:

Update tuna's init.rc For Android L

Add N5's sensorservice into system/bin/ (for now)

N5's sbin folder, init file, ueventd.rc, init.usb.rc, init.trace.rc

Modified:

init.rc, file_contexts_ seapp_contexts, property_contexts, default.prop ...

file_contexts must be re-modified for Tuna Android L, but I can't do that...

https://gist.github.com/manumanfred/ff1155d00109d830704d

Not tested myself yet
[Samsung Galaxy Nexus] IRX120:
This sounds interesting, I'm sure once sources are released in a few months then well have an aosp build that works, getting this to boot will require quite a bit of tweaking to the ramdisk. It'd be nice to see this boot tho.

Good luck.
[Samsung Galaxy Nexus] Carlos_Manuel:
In fact I don't like Android L, I didn't even like KitKat, but now KitKat is okay, but android L is ugly..

I am interested of trying andorid L dev prev. myself on my Nexus, so that's why I am trying to port it. :cool:

And Thanks! :)
[Samsung Galaxy Nexus] Carlos_Manuel:
no need to apologize.. in XDA and Google you can learn about cooking ROMs, etc. ;)

Thanks! :)
[Samsung Galaxy Nexus] armada786:
Well, that's a bit above my head, but I'm willing to throw myself into logs and track things down like this. I really can't say that helps much given the speed of the changes, but I like to do what I can. I think we are close too and it's a matter of time, but I can't blame Los for not wanting to waste the time and energy as a full AOSP drop is probably looming.
[Samsung Galaxy Nexus] sykopompos:
Full aosp drop won't be till after they debut the n6 which I think is around Oct so there is still some time to go and if they dropped L now I would be scared because there is still way too many bugs in just what is in aosp

Sent from my LG-D851
[Samsung Galaxy Nexus] los93sol:
Thanks for looking into this guys. To answer the conscrypt question, yes, using the one from AOSP's master branch does get us past it, but then, as Syko pointed out, it starts blowing up on GLES differences. The difference is down to the framework. If we can figure out how to get the right pieces in play, we'll be in the clear. ATM, I've been doing the exact opposite of what Syko is proposing, I've been patching the differences from AOSP into the L framework files. Both are valid solutions and I don't know which is more feasible yet.

Also, as Syko pointed out, I've built the l preview branch and it really didn't help much at all...attempting to patch up the build enough to actually use libart.so from the preview, but I'm not sure that'll really help us much either.

EDIT: Here is conscrypt.jar from AOSP that'll get you past that error and onto the GLES issues https://drive.google.com/file/d/0B_q0CDQXX32nVURZYm1Vc0kxQ2c/edit?usp=sharing
[Samsung Galaxy Nexus] sykopompos:
I'm really thinking a flo/n7 build of the l preview branch, then split the framework jars open and diff the smali might be our best option to track down the changes and figure out how they hook into the libs. I use diff -yrqs to compare whole folders for different files and then diff -y to see the individual changes in each file. I know looking at the split open framework you sent me there is whole files that are new in there.

If we can then merge those changes into the L preview branch and then compile it against our current files, that would give us libs that would match up with the L framework files.

If you wanna compile the preview branch and split all the framework files open (since my computer doesn't wanna do it) , I will go through them and track down the changes if you send me full copies of all the framework files (all the jars in system/framework of both)

Sent from my LG-D851
[Samsung Galaxy Nexus] los93sol:
Okay, dug into this more....if you replace libstlport.so with the one from hammerhead it will just sit there, but if you manually run the dex command it completes successfully, allowing the entire oat file to be created. From that point on though...it just sits there...

The good news is it appears we have found the culprit, now we just need to take a closer look at that guy and see what needs changed in the code to make it boot.

EDIT: Upon looking at stlport in AOSP....I'm not sure this is really the culprit, honestly not sure what it does, but I don't see any references to the function causing the issue
[Samsung Galaxy Nexus] armada786:
I'm not so sure whatever is in AOSP is going to match the preview image, because a lot of the l-preview branches created are just copies of the master branch at the time,and it looks like platform/external/stlport hasn't moved on either branch since then. As for what it does, I'm assuming it's an implementation of the Standard Template Library for C++. I can't say whether it's the culprit in this or why it's messing up, though.
[Samsung Galaxy Nexus] los93sol:
I'm out of ideas, I've tried several things to resolve the GLES20DisplayList abort message, but so far nothing seems to work and I have no clue why. As much as I'd love to have gotten this working I think it's time to throw in the towel and wait for full sources to drop.
[Samsung Galaxy Nexus] sykopompos:
Nooooooooooooooooo.

Sent from my LG-D851
[Samsung Galaxy Nexus] Justice™:
It's only gonna be a few more weeks now, and it'll be worth the wait
[Samsung Galaxy Nexus] sykopompos:
I'm inpatient and that is why there is a n4 port lol

Sent from my LG-D851
[Samsung Galaxy Nexus] piterdemon:
Maybe we have to try port N4 port ? Xd

Wytapatano z Galaxy Nexus PA 4.5 beta2 [MENTION=280772]Dirty[/MENTION]Vkernel
[Samsung Galaxy Nexus] Carlos_Manuel:
Lol !!!
[Samsung Galaxy Nexus] piterdemon:
That was a joke :p

Wytapatano z Galaxy Nexus PA 4.5 beta2 [MENTION=280772]Dirty[/MENTION]Vkernel
[Samsung Galaxy Nexus] sykopompos:
Until you get around the egl drivers and the new open gl code that is closed source. Only current gen and last Qualcomm based phones can use the n7 and n5 bases.

Actually n4 is a hybrid of n5, n7 and aosp with the new ports I have been working on for the n7 and n5 carrying over being hybrids

Sent from my LG-D851
[Samsung Galaxy Nexus] peppin96:
Hope...
[Samsung Galaxy Nexus] marcovittori:
you need to wait 1 month and than you'll android L xD anyway for now the preview is pretty useless without material design app :) (i've used it on my nexus 7)
[Samsung Galaxy Nexus] sykopompos:
The preview is smooth and extremely quick .... Well my version of it is....
[Samsung Galaxy Nexus] nikodr:
Now that galaxy nexus has newer gpu and ducatti binaries does that mean that android l port can continue?:)
[Samsung Galaxy Nexus] ILA:
That wasn't the issue in the first place so if it was to resume, it wouldn't be because of that. I doubt that anyone would try to port it knowing that the release of the code is only days away. It would be a waste of time and patients...

The new drivers give us a boost in performance so that the L, when the code lands, will be as smooth as possible. ;)
[Samsung Galaxy Nexus] nikodr:
So in two days the SDK will be available. With the new ducati and gfx drivers we shall have the first lolipop ROMs for maguro :)
[Samsung Galaxy Nexus] andreadec:
We have to wait for the source code to be published. Usually this is done some days after system images are made available for officially supported Nexus devices. So I think we have to wait more than two days...
[Samsung Galaxy Nexus] sykopompos:
The issues weren't with the drivers as I was working with los93sol as he was going through it so new preview images and some binaries aren't gonna magically make it work now.

As far as a few days, you got a few weeks. There is just new preview images coming and not official factory images yet.

You won't see those or source till at least one of the new nexus devices go to ship which is looking to be nov 9th

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
I thought the major issue was that the preview images had a lot of graphics things hardcoded in? There have been SDK ports in the past obviously, but I wonder if that same thing would still be a problem. Either way, at this point an SDK port isn't worth it with source drop being close.
[Samsung Galaxy Nexus] sykopompos:
That was for the 1+1 and g3 mostly were we needed updated code for the qhd screen but on the gnex, we didn't have the egl3.1 binaries to match up with L.

The bigger problem on the gnex was no code to use to support the chipset so it was practically impossible and I know [MENTION=3640085]los93sol[/MENTION] tried every way we could think of to get around it

Sent from my LG-D851
[Samsung Galaxy Nexus] ScardracS:
The moment is arrived! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
[Samsung Galaxy Nexus] sykopompos:
Good luck with building with that and enjoy your kit Kat :p

Sent from my LG-D851

---------- Post added at 02:19 AM ---------- Previous post was at 02:12 AM ----------

Wait. It is happening :eek:

Sent from my LG-D851
[Samsung Galaxy Nexus] ScardracS:
I won't try to build Lollipop because I have lots of exams at University so I'll expect other builds
[Samsung Galaxy Nexus] Carlos_Manuel:
After getting BT fixed or at least getting video graphics fixed from my new notebook running Ubuntu 14, then I'll start syncing LP sources (when the sources are completely pushed...)... :silly: :silly: :silly: :silly: :silly: :silly: :silly:
[Samsung Galaxy Nexus] Culex316:
Are there any major changes in Lollipop that would break compatibility with our current kernel? (3.0.x)
[Samsung Galaxy Nexus] Carlos_Manuel:
I don't know. 3.0.** should work just fine... :)

Edit: for compiling, we need some changes to the kernel headers...
[Samsung Galaxy Nexus] Omar1c:
Good thing I still got my rusty Nexus³
[Samsung Galaxy Nexus] croccio:
does the rom from download link boot??
[Samsung Galaxy Nexus] marcovittori:
No
[Samsung Galaxy Nexus] IRX120:
I wouldn't say its ugly, just "different" like in 2013 when apple went from iOS 6-7 and everyone hated the new look. I think L is going to take some time getting used to, but give it a year and everyone will be running it.
[Samsung Galaxy Nexus] Carlos_Manuel:
heh, yep! :D

______________________________________

Update:

With the new changes Nexus reboots all the time.. showing Google splash logo and then rebooting and again showing it... This should be caused by init. I can't take any logs
[Samsung Galaxy Nexus] nikodr:
Thumbs up :)

Though i still have the question regarding kernel,we all know the kernel 3.4 thread,if that kernel /or when it is completed,would that make the transition to Android L easier? Most devices running Android L official would not they also get an updated kernel for new features?

Now it is an aosp 3.0.72 tuna kernel?
[Samsung Galaxy Nexus] kirmaniarslan:
have u replaced bootclass path in init.environ.rc ??
[Samsung Galaxy Nexus] Carlos_Manuel:
Nope.. there's nothing to replace from it. I haven't touched framwork folder
[Samsung Galaxy Nexus] Carlos_Manuel:
Guys try to undertsand kernel version DOES NOT MATTER! We can use even 2.6.3x kernel with Android L. Nothing is stopping that!

Kernel 3.4 is not rready yet, hashcode and icepeda are working on it and half of the panel should already work.. (in recovery) as recovery uses framebuffer and not pvr...

Kernel 3.4 will give us newer pvr drivers which fixes most of the issues with kitKat on tuna. K3.4 has more chnages and fixes and features and it makes tuna a new phone.

but... Patience is needed...
[Samsung Galaxy Nexus] kirmaniarslan:
the problem is still in ramdisk..!!
[Samsung Galaxy Nexus] Carlos_Manuel:
I included this to init.environ.rc:

export LD_LIBRARY_PATH /vendor/lib:/system/lib
[Samsung Galaxy Nexus] Grarak:
New Android version means also new ramdisk

replacing bootclasspath won't help

I don't even think it's possible to port a different android version
[Samsung Galaxy Nexus] n1kolaa:
update those apps in framework reqvested

https://github.com/n1kolaa/android_device_samsung_tuna/tree/cm-11.0/overlay

you need that to system know our filesystem size and more :)
[Samsung Galaxy Nexus] Carlos_Manuel:
it is possible, but init is the problem. We could try to use old Tuna's init file and modify init.rc and *.rc files for the old init files, which may let to boot, but that won't be a good idea.

using N5 init:

rebooting all the time

using SDK's init:

Not doing really anything..

What do you mean with those?

This is Android L preview and not open sourced. you can't then modify those stuff..
[Samsung Galaxy Nexus] Ashutos1997:
So why people in N4 form are working so hard to port L to N4 ? Just saying .(Dont mind)

Update : Can u help him/us Grarak ?
[Samsung Galaxy Nexus] n1kolaa:
you can allways decompile app :)

those things need to boot proper :)
[Samsung Galaxy Nexus] Carlos_Manuel:
1. Thsoe things are not needed!

2. It's not that easy like decompiling and adding those

3. System apps and framework have not been modified and those doesn't need modifying

4. This is not cm11
[Samsung Galaxy Nexus] Grarak:
I've never heard that anyone ported a different android version to a phone

I don't want to messing around with porting anymore

Just a waste of time. Waiting for sources
[Samsung Galaxy Nexus] n1kolaa:
This can be usefull :)

http://xdaforums.com/showthread.php?t=1598713
[Samsung Galaxy Nexus] Ashutos1997:
Sources will not be up until fall /Sept-Oct 2014.
[Samsung Galaxy Nexus] Carlos_Manuel:
for me this isn't wasting of time.

I am not the only one who have ported another Android version

for e.g. I've ported Android 1.5, 2.0, 2.1, 2.2.x, 2.3.x, 4.0, 3.0 to Samsung Jét

https://code.google.com/p/android-for-jet/downloads/list

Everything is possible if you just know how to do it.

porting to tuna is new for me and I've never ported JB or newer android version. that's why I am here asking help from those who are interested and who can help

Waiting sources for the L takes a long time. I don't like that N5, n7 owners can enjoy of L dev. prev. and I can not even touch it.

unfortunately that really won't help me at all. but Thanks
[Samsung Galaxy Nexus] Ashutos1997:
I am with Carlos, u can boot it Carlos, just keep trying. ;)
[Samsung Galaxy Nexus] Grarak:
This is compiling from sources

Has nothing to do with porting
[Samsung Galaxy Nexus] IRX120:
If I rember correctly, isn't there a program that can decompile the ramdisk? Allowing for modification if anyone knew what to change.
[Samsung Galaxy Nexus] rajputrajat:
If i remember correctly, first kitkat ports which came for tuna devices were from nexus 5 images binaries...

So in my opnion this should be doable...
[Samsung Galaxy Nexus] IRX120:
Yeah, but google also dropped KitKat to AOSP before they even released the nexus 5 for sale. I had a nexus 4 at the time and did use a port of the n5 image.

I think the gnex got a CM build from source pretty quick tho
[Samsung Galaxy Nexus] Ashutos1997:
We need to wait for sources then to boot L on gnex.
[Samsung Galaxy Nexus] Carlos_Manuel:
I found nothing about KK port for Nexus.

It took long time for CM to make CM11.

I was one of the first three devs on maguro to build KitKat from sources. SlimKat was before me.. Slimkat devs were fast. My notebook downlaoded sources 2 days
[Samsung Galaxy Nexus] Ashutos1997:
Try to boot L if u can ;)
[Samsung Galaxy Nexus] IRX120:
My bad, my memory's not the best sometimes?
[Samsung Galaxy Nexus] ashclepdia:
once someone gets some darker themes and such for it, I imagine it could look really nice.

like with all the new layers and shadows, eclipse Rom could take a whole new meaning, could make it so that everything is dark and shadows are light, would look cool imho

I imagine some awesome things being done with this new version, cannot wait till source drops, and I can get brand new nexus device and watch it grow like I did on this one.

sorry for OT
[Samsung Galaxy Nexus] Carlos_Manuel:
Quick N5 Android L dev. prev. port (dirty port) for those who want to port this instead of SDK...

https://drive.google.com/file/d/0BxlYDVLp_RkMT0RKQkE2eFE3aE0/edit?usp=sharing

Removed hammerhread stuff (most of them)

Removed Gapps (most of them)

Added tuna's files...

vold, sensorservice from tuna..

Ramdisk:

same 3.0.72 kernel

Hammerhead's boot files

added tuna's init.tuna.rc, ueventd.tuna.rc, etc.

Same problem rebooting all the time form google splash logo to google splash logo.. (init file problem, no correct init)
[Samsung Galaxy Nexus] samcortez:
Is there some news? Thank you.
[Samsung Galaxy Nexus] Ashutos1997:
No ^, porting is stopped by the dev. You guys can try to boot though.
[Samsung Galaxy Nexus] Croc97:
So... The problem is the ramdisk, right?
[Samsung Galaxy Nexus] nikodr:
Yes
[Samsung Galaxy Nexus] Carlos_Manuel:
[MENTION=4649469]Ashutos1997[/MENTION] told me about n7 Android L sdk port and.. When I have free time, then I may try to port again.

Yes the problem is in the ramdisk, possibly only in init and adbd file. Also the pid excited in the log may be caused by tuna's egl files
[Samsung Galaxy Nexus] ashclepdia:
i was seeing lots of ril errors in log also, now i dont know lots about this really by any means,

but i for one wouldnt mind the removal of radio support except wifi only, like if you can get at least to boot by removing the startup of the lte/cdma(or for gsm just the radios) radios, if that makes it any easier, i'd just be happy seing how she looks on our device.

i really dont know wat im talking about here though so i shall keep on reading in hopes i may find something useful or be able to help out.

good luck to all trying.

by the way, anyone know of a thread where somemone has pulled most of the apps for L and ported them to kk in usable form?

i know i saw a thread for the material keyboard, just curios if any others got added to that list as i cant seem to locate thaqt damn thread again sorry

edit::

and if i remember correctly, i THINK what someone was referring to above was a 4.3 or 4.4 build made for the nexus4 that got ported and running via jakeday or something (JDX or something) before all source was initially pushed out. so it MIGHT be possible to backport these L dev preview builds to the Gnex, it's just not going to be "easy"...but then if it were easy, then wheres the fun in that? lol
[Samsung Galaxy Nexus] Carlos_Manuel:
I'm lazy to read the logs. Nice finding :)

Sure I can try porting again without replacing the files.. :)

At least to make it booting, nexus must have pvr files in the build and Wi-Fi+nfc files. Otherwise it won't boot, I may be wrong, maybe only pvr files are needed to boot, as without pvr files screen will be black or it wont pass Google logo
[Samsung Galaxy Nexus] sagara.sandaru:
Here is the all the apps,boot animation, fonts and system dump [emoji4] http://xdaforums.com/showthread.php?t=2796019
[Samsung Galaxy Nexus] Ashutos1997:
I tried to port L ROM to gnex by taking N7 (2012) L ported ROM , but is stuck at same google logo, I am uploading the ROM , can anyone give me the logcat ?

UPDATE : No need.
[Samsung Galaxy Nexus] Carlos_Manuel:
still can't get booting:

I/DEBUG ( 126): Build fingerprint: 'generic/google_sdk/generic:L/LPV81B/1242878:eng/test-keys'
I/DEBUG ( 126): Revision: '9'
I/DEBUG ( 126): pid: 524, tid: 524, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 126): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr

...

I/SurfaceFlinger( 543): SurfaceFlinger is starting
I/SurfaceFlinger( 543): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 543): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 543): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 543): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
E/IMGSRV ( 543): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 543): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 543): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 543): :0: Couldn't connect to services
W/libEGL ( 543): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
E/IMGSRV ( 543): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 543): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 543): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 543): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 543): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 543): :0: hal_open: Graphics HAL not initialized
I/DEBUG ( 126): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 126): Build fingerprint: 'generic/google_sdk/generic:L/LPV81B/1242878:eng/test-keys'
I/DEBUG ( 126): Revision: '9'
I/DEBUG ( 126): pid: 543, tid: 543, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 126): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr

...
[Samsung Galaxy Nexus] KShion619:
Looks like a pretty thick wall, but so close its already on surfaceflinger! Looking pretty good! By the way, are you using the SGX drivers from Pandaboard? if not id say see if those boot it up, those are much more updated, and could/should work with PVR