yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Carlos_Manuel:
[MENTION=4576677]KShion619[/MENTION] Not sure if these auditd selinux things are the problem:

I/lowmemorykiller( 121): Using in-kernel low memory killer interface
--------- beginning of events
I/auditd ( 119): type=2000 audit(0.0:1): initialized
I/auditd ( 119): type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
I/auditd ( 119): type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
I/auditd ( 119): type=1404 audit(0.0:4): enforcing=0 old_enforcing=1 auid=4294967295 ses=4294967295
I/auditd ( 121): type=1400 audit(0.0:5): avc: denied { entrypoint } for comm="init" path="/system/bin/lmkd" dev=mmcblk0p10 ino=7028 scontext=u:r:adbd:s0 tcontext=u:object_r:system_file:s0 tclass=file
I/auditd ( 120): type=1400 audit(0.0:6): avc: denied { entrypoint } for comm="init" path="/sbin/healthd" dev=rootfs ino=1557 scontext=u:r:healthd:s0 tcontext=u:object_r:rootfs:s0 tclass=file
I/auditd ( 133): type=1400 audit(0.0:7): avc: denied { write } for comm="installd" name="logdw" dev=tmpfs ino=2092 scontext=u:r:installd:s0 tcontext=u:object_r:device:s0 tclass=sock_file
I/auditd ( 133): type=1400 audit(0.0:8): avc: denied { sendto } for comm="installd" path="/dev/socket/logdw" scontext=u:r:installd:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket
I/installd( 133): installd firing up
--------- beginning of crash
I/DEBUG ( 128): debuggerd: Jun 20 2014 22:25:40
I/auditd ( 123): type=1400 audit(0.0:9): avc: denied { write } for comm="vold" name="logdw" dev=tmpfs ino=2092 scontext=u:r:vold:s0 tcontext=u:object_r:device:s0 tclass=sock_file
I/auditd ( 123): type=1400 audit(0.0:10): avc: denied { sendto } for comm="vold" path="/dev/socket/logdw" scontext=u:r:vold:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket
[Samsung Galaxy Nexus] KShion619:
I'd assume Accessing the Vector Cache (AVC) is something to do with lack of those updated drivers, but when looking around i dug this up, might help as it practically shows that error in the page

https://wiki.gentoo.org/wiki/SELinu...ssion_denial_details#Disecting_the_AVC_denial

If its possible to remove/disable Selinux in this version, or set it to permissive id say try that as well
[Samsung Galaxy Nexus] Carlos_Manuel:
About disabling selinux.. I don't know, it would also need kernel modifications..

EDIT: I tried to set it enforcing, but didn't work. I also edied file _contexts and other files, but still same thing.

I'll give up now.
[Samsung Galaxy Nexus] rstat1:
Could you potientally upload your progress somewhere? I'd like to take a crack at getting it working.
[Samsung Galaxy Nexus] Carlos_Manuel:
I've already deleted all the files.
[Samsung Galaxy Nexus] times_infinity:
Android L Preview Source Code Posted to AOSP Via Android Police

and now we wait...
[Samsung Galaxy Nexus] Carlos_Manuel:
Yep and I am syncing the sources
[Samsung Galaxy Nexus] Brettbesa:
So can someone help me out a bit here? How much does this help you fine devs considering the Gnex isn't on there?
[Samsung Galaxy Nexus] Shadow Death:
Much easier than porting from one device to another.... usually..
[Samsung Galaxy Nexus] IRX120:
Well with source code its 1000% easier than without. Since all the gnex drivers/binaries are open source and available to download, its "relatively" easy to adapt them to the source code.

I built a few roms for some POS Samsung phone a few years back, and even with half the drivers closed source we ended up with usable roms (99% working). It did take us a good 6+ months and some talented devs tho.
[Samsung Galaxy Nexus] rstat1:
I don't think the posted code will be very useful to use just yet.because of this https://groups.google.com/forum/#!topic/android-building/R50i6JktFtI
[Samsung Galaxy Nexus] Carlos_Manuel:
Useful enough to get tuna ready for android L in the fall. :)

Btw. L-preview uses gcc 4.8 and requires java 7 to build.

It seems to be using the new art.. But nothing really useful changes tho..

At least this l-preview will help us to get tuna ready for android L.. ?
[Samsung Galaxy Nexus] ScardracS:
[MENTION=4022928]Carlos_Manuel[/MENTION] i think that post will help you. http://www.androidpolice.com/2014/0...osp-includes-support-nexus-4-5-7-2013-10/?a=1
[Samsung Galaxy Nexus] blmvxer:
The source code isn't complete but may give us enough to help us make a port but not to just build a ROM from the code.

Sent from my Samsung Galaxy Nexus 4.4.4 with F2FS
[Samsung Galaxy Nexus] Carlos_Manuel:
It won't help. :)

It isn't complete..

But I don't care is it complete or not... :)
[Samsung Galaxy Nexus] RevengeFNF:
Google said it did not release KitKat for the Galaxy Nexus, because it was older than 18 months.

They will release Android L to the Nexus 4 that is 18 Month old now, but it will be older at the time of official release.

It makes sense... none.
[Samsung Galaxy Nexus] IRX120:
Well, they probably wanted to get the gnex under the rug as to all the problems with the toro never getting **** updates and the lagg problems that many users expierenced on 4.2-4.3.

Plus TI quit making the chips and some other excuses.

But, there's always devs
[Samsung Galaxy Nexus] .B.0.W.:
sad to see that google "killed" the legend
[Samsung Galaxy Nexus] Shadow Death:
Any idea what's missing from the source?
[Samsung Galaxy Nexus] Oxirane:
Galaxy Nexus support wasn't dropped due to age. It was dropped as TI decided they were done with making mobile processors, and no longer intend to update the drivers for newer versions of Android.

The Galaxy Nexus uses a TI-OMAP 4460 processor.

The newer Nexus phones use Snapdragon processors made by Qualcom instead.
[Samsung Galaxy Nexus] ILA:
I hate that that switch happened. The omap processor was what nexus was all about. It is completely open with good documentation (unlike snapdragon procsesors). The only things that kept it from being the ultimate were and still are the PVR blobs. Sad that TI didn't manage to get those open source as well.
[Samsung Galaxy Nexus] RevengeFNF:
KitKat does not need newer drivers to work. Simple as that.
[Samsung Galaxy Nexus] KShion619:
When i unknowingly tried building it for grouper it broke in the last bit, right as kernel and drivers were supposed to build, prolly more than just that, but just what i noticed
[Samsung Galaxy Nexus] Carlos_Manuel:
Changelog from kk to l-preview https://funkyandroid.com/aosp-KOT49H-LPV79-nochrome.html (without chromium changes)
[Samsung Galaxy Nexus] matoushybl:
What do you need to try to port L? I'd really like to try the preview. I should have enough computing power to build from your updated sources. Would that be sufficient? Are the sources on your github?

Thanks for your great work

(I am not a rom nor kernel dev, rather app dev, but I've been able to build in the past)
[Samsung Galaxy Nexus] Carlos_Manuel:
There's no sources to my ports.

Android L-preview is not open sources.

L-preview in AOSP sources isn't the same...
[Samsung Galaxy Nexus] matoushybl:
I know. I was talking about your kitkat sources updated with L changes that were pushed to AOSP.
[Samsung Galaxy Nexus] Carlos_Manuel:
My ROM is pretty source closed. because I don't know how to use Git.

Device tree is here:

https://github.com/manumanfred/device-samsung-tuna
[Samsung Galaxy Nexus] matoushybl:
Yeah, using git can be pain but in the end it is quite usefull, so building the rom won't help at all?
[Samsung Galaxy Nexus] Carlos_Manuel:
It should help... but my notebook can't compile L-preview successfully because of libwebviewchromium. It needs more RAM memory to get built.
[Samsung Galaxy Nexus] KShion619:
I can compile it if you can walk me through the procedure :P
[Samsung Galaxy Nexus] Carlos_Manuel:
I am not interested of trying porting it anymore. I'm waiting for Android L sources and trying to port successfully glass's kernel to tuna. :)
[Samsung Galaxy Nexus] blmvxer:
Guys this is easy to port you're just not using your sonic screwdriver!!! Duh! ;)
[Samsung Galaxy Nexus] Carlos_Manuel:
If you think this is easy to port then go ahead. Port this from the scratch for xda users!

I'm waiting! ;)
[Samsung Galaxy Nexus] blmvxer:
Sonic screwdrivers broke and waiting on the Tardis to make me a new one! :p
[Samsung Galaxy Nexus] Carlos_Manuel:
what's tardis?

Btw. to port you don't need any "screwdriver".

You need a Nexus, a computer, brains and nothing else :cyclops:
[Samsung Galaxy Nexus] Justice™:
I think either you haven't seen Doctor Who before or you just didn't get the joke :P Anyway, on topic now: I think you're wise to hold off porting the emulator/preview images, code in L is bound to change before the september release and I think our efforts should be focused on Kernel 3.4 until the source code for L drops.
[Samsung Galaxy Nexus] Carlos_Manuel:
I've never watched doctor who. Never. It seems to be so boring. :laugh: and no I didn't get the joke. :good:

Hash and Ice are working on k3.4. We have to wait. ;)
[Samsung Galaxy Nexus] los93sol:
Porting to Toro

I've been attempting to port to Toro. So far I've had limited success, but hoping someone else with the right skillset is interested in working on this with me.

-I've used Shiny from 6/21 as base

-Modified ramdisk based on the mako port of the l preview

-Replaced system/apps, system/framework, system/media, and system/priv-app with the files from l preview (hammerhead)

-Replaced a ton of files in system/lib with files from the hammerhead l preview

-Merged a ton of files from system/bin of hammherhead l preview

Right now it doesn't boot, it loads up surfaceflinger and just hangs there indefinitely. No errors are present so I'm really stumped and hoping someone can point me in the right direction to get me moving again.
[Samsung Galaxy Nexus] Grarak:
Porting directly won't work

Only compiling from sources will work (maybe)
[Samsung Galaxy Nexus] darkmansd:
How did they manage to do it on the nexus 4?
[Samsung Galaxy Nexus] BestBrd:
Also on HTC m7..
[Samsung Galaxy Nexus] IRX120:
The limited source code released (ie device spesific files)
[Samsung Galaxy Nexus] Justice™:
And the nexus 7 (2013) system image
[Samsung Galaxy Nexus] poondog:
Mako and m7 benefitted from the qcom Nexus 7 having official support. Since the devices are all snapdragon, porting is way easier

Porting to Mako involved just merging the changes from flo L preview into mako hardware, a few hacks and it works (with stock kernel)

Porting to m7 was also merging a few changes, but in the kernel we needed a few hacks to get support for AOSP display drivers (since thats what we used from the other ports). So with a basically "AOSP" kernel it works, because the libs are basically compatible across mako, CM, m7 due to similar qualcomm hardware

However for gnex its different, you guys are TI. So I think most of the guys from the mako and m7 ports (me included) have limited knowledge

idk if you guys have ported from the sdk before, or ported from msm devices. but your best bet is when sources are released to compile from them, with TI specific changes

just my 2c
[Samsung Galaxy Nexus] los93sol:
What kind of modifications were required to the kernel to get it booting?
[Samsung Galaxy Nexus] poondog:
For m7 it was modifying stuff that related to the display, in order for it to work properly with the AOSP display drivers and frameworks in the preview that we used as a base. It was super glitchy because the display drivers on rom and kernel side didn't like each other. What I did was force them to work together :)
[Samsung Galaxy Nexus] Carlos_Manuel:
AOSP display drivers? Could you please give a link to the AOSP display drivers? I am not sure what drivers you are speaking of. hwc, surfaceflinger, etc in frameworks/native/ ?
[Samsung Galaxy Nexus] sykopompos:
Poondog used the cm kernel source and removed the caf video drivers so it went back to stock so it would boot up and display correctly

Sent from my C6916
[Samsung Galaxy Nexus] poondog:
I am talking about all of this

Do you guys have CAF/AOSP split like on newer nexus?
[Samsung Galaxy Nexus] Carlos_Manuel:
Never heard about caf on tuna... Caf on n4, etc. I've heard. I don't even know what is that caf..
[Samsung Galaxy Nexus] poondog:
ok so thats done and dusted :P
[Samsung Galaxy Nexus] times_infinity:
CAF is the Code Aurora Forum. Its basically like OMAPZOOM, but for QCOM SoCs
[Samsung Galaxy Nexus] sykopompos:
Caf's biggest contributor and main project goal is Qualcomm for the Qualcomm msm, always has been

Sent from my C6916
[Samsung Galaxy Nexus] Carlos_Manuel:
Sure I know code aurorora forum... That had some nice optimizations which I used... :laugh:
[Samsung Galaxy Nexus] sykopompos:
I have a question, what is lpv81b? I thought we only have 79

Sent from my C6916
[Samsung Galaxy Nexus] los93sol:
I actually have been wondering this myself, I assumed it was just Carlos_Manuel's way to version his efforts
[Samsung Galaxy Nexus] Carlos_Manuel:
Nope... My port is from sdk system armeabi-v7 and its build id is lpv81b
[Samsung Galaxy Nexus] sykopompos:
Huh, I did not know that. I thought everything was across the board lpv79. Any noticeable differences from 79?

Sent from my C6916
[Samsung Galaxy Nexus] Carlos_Manuel:
I don't know.

I've only seen android L preview on google I/O and pics of it. I don't know much nothing of Android L preview and its versions
[Samsung Galaxy Nexus] sykopompos:
It is possible that they are pushing out newer versions for the emulator.

I haven't played with L much even though I have it except in the logs and files

Sent from my C6916
[Samsung Galaxy Nexus] los93sol:
Well, I am stuck here with a healthd problem. It looks like Carlos had it resolved in his port at one time or another, but if anyone has a point in the right direction on this error I'd really appreciate it..

[ 28.323333] healthd: wakealarm_init: timerfd_create failed

[ 28.326538] healthd: BatteryPresentPath not found

[ 28.336914] binder: 195:195 transaction failed 29189, size 0-0

and here is more from kmsg

[ 23.303497] request_suspend_state: wakeup (0->0) at 23289217228 (2000-01-01 16:47:10.810823672 UTC)

[ 28.323333] healthd: wakealarm_init: timerfd_create failed

[ 28.326538] healthd: BatteryPresentPath not found

[ 28.336914] binder: 195:195 transaction failed 29189, size 0-0

[ 28.340667] init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting into recovery mode

[ 29.337951] binder: 195:195 transaction failed 29189, size 0-0

[ 30.339111] binder: 195:195 transaction failed 29189, size 0-0

[ 31.130706] SysRq : Emergency Remount R/O

[ 31.339752] binder: 195:195 transaction failed 29189, size 0-0

[ 31.858886] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)

[ 31.867584] EXT4-fs (mmcblk0p12): re-mounted. Opts: (null)

[ 31.870452] Emergency Remount complete

[ 31.938232] DSSCOMP: dsscomp_early_suspend

[ 31.940185] DSSCOMP: blanked screen

[ 31.940582] [MODEM_IF] cmc221_off()

[ 32.155700] [MODEM_IF] cbp71_off()

[ 32.155914] [MODEM_IF] cdma_ipc0 state changed: OFFLINE

[ 32.226470] Disabling non-boot CPUs ...

[ 32.228637] omap_temp_sensor_enable:get sync failed

[ 32.228942] CPU1: shutdown

[ 32.230194] Restarting system with command 'recovery'.

[ 32.230194]

[ 32.230194] Restarting Linux version 3.0.72-gb247a67-dirty (dan@Ziyan-PC2) (gcc version 4.9.1 20140529 (prerelease) (crosstool-NG linaro-1.13.1+bzr2665 - Linaro GCC 2014.06 - Cortex-A9) ) #1 SMP PREEMPT Fri Jul 18 18:30:28 CEST 2014

[ 32.230621]
[Samsung Galaxy Nexus] sykopompos:
You didn't tell me that service manager did it too

Sent from my C6916
[Samsung Galaxy Nexus] samcortez:
Oh, I wish I could do anything to help you guys but I am really newbie. I do so much want Android L, well, good luck for us, right?
[Samsung Galaxy Nexus] depinetnick:
It should be fairly easy to define some policies for those items, which should solve those problems. Have you tried turning SELinux off and seeing what we get to? If you post your progress so far for me (source and stuff), I'll take a look at it and see if I can help at all.

Come on people, don't give up yet! We can get the L preview running on the galaxy nexus if we work together on this.
[Samsung Galaxy Nexus] nickkral:
Init uses the file label on /system to determine the appropriate SELinux domain to transition into. In at least the case of lmkd above, it appears the file label is incorrect. It should be:

root:/ # ls -laZ /system/bin/lmkd
-rwxr-xr-x root shell u:object_r:lmkd_exec:s0 lmkd

If you're seeing system_file when you run ls -laZ, then it's likely an incorrect label.

The SELinux domains for "lmkd" and "inputflinger" are distributed as part of the AOSP SELinux policy. The other services are tuna specific and likely no SELinux policy has been written for those services.
[Samsung Galaxy Nexus] los93sol:
Thank you sir, got past those issues. I kind of cheated to get around the domains on the proprietary files, I mapped them to zygote_exec then just went back and added the rules to that domain. A hack, but it seems to have done the trick. Still not booting, but I believe that may be kernel related. From what I can tell, it appears there is a dependency on the updated IPC binder in the kernel. Carlos, does your kernel have the updated binder backported from 3.4?

Also, for anyone interested, I have an upload of my current progress going now, hoping some other people get interested in this and can help finish it off.
[Samsung Galaxy Nexus] los93sol:
Here is my progress so far https://drive.google.com/file/d/0B_q0CDQXX32nYm1kQjZNLWEzRGM/edit?usp=sharing

It's very quiet in here, hoping someone else is as serious about getting this working on our devices as I am
[Samsung Galaxy Nexus] sykopompos:
Chirp chirp

Sent from my Nexus 4
[Samsung Galaxy Nexus] los93sol:
I'm uploading my progress so far, link should be available when I wake up in a few hours.
[Samsung Galaxy Nexus] Carlos_Manuel:
I'm not sure but some of these may cause problems with booting:

<3>[ 7.811065] init: /dev/hw_random not found

<3>[ 7.834747] healthd: wakealarm_init: timerfd_create failed

<4>[ 7.838287] healthd: BatteryPresentPath not found

<6>[ 7.838623] binder: 119:119 transaction failed 29189, size 0-0

<3>[ 7.897735] HDCP: failed to load keys

<3>[ 7.907165] init: property 'sys.powerctl' doesn't exist while expanding '${sys.powerctl}'

<3>[ 7.908081] init: powerctl: cannot expand '${sys.powerctl}'

<3>[ 7.908264] init: property 'sys.sysctl.extra_free_kbytes' doesn't exist while expanding '${sys.sysctl.extra_free_kbytes}'

<3>[ 7.908416] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while writing to '/proc/sys/vm/extra_free_kbytes'

<3>[ 7.908538] init: property 'sys.sysctl.tcp_def_init_rwnd' doesn't exist while expanding '${sys.sysctl.tcp_def_init_rwnd}'

<3>[ 7.908691] init: cannot expand '${sys.sysctl.tcp_def_init_rwnd}' while writing to '/proc/sys/net/ipv4/tcp_default_init_rwnd'

<3>[ 7.910003] init: property 'persist.sys.tuna.off_mode' doesn't exist while expanding '${persist.sys.tuna.off_mode}'

<3>[ 7.910125] init: cannot expand '${persist.sys.tuna.off_mode}' while writing to '/d/pm_debug/enable_off_mode'

<3>[ 7.910278] init: property 'ril.modem.lte.powercontrol' doesn't exist while expanding '${ril.modem.lte.powercontrol}'

<3>[ 7.910400] init: cannot expand '${ril.modem.lte.powercontrol}' while writing to '/sys/bus/usb/devices/1-1/power/control'

[MENTION=3640085]los93sol[/MENTION]

Check these:

init: /dev/hw_random not found: https://bugs.launchpad.net/linaro-android/+bug/1266494

7.897735] HDCP: failed to load keys maybe init or firmware problem

healthd problems:

<3>[ 7.834747] healthd: wakealarm_init: timerfd_create failed

<4>[ 7.838287] healthd: BatteryPresentPath not found

<6>[ 7.838623] binder: 119:119 transaction failed 29189, size 0-0

Binder?
[Samsung Galaxy Nexus] los93sol:
Here is my progress so far if anyone else wants to dig in and take a look.

https://drive.google.com/file/d/0B_q0CDQXX32neGJGcWlfRXBZR1U/edit?usp=sharing
[Samsung Galaxy Nexus] whoshotjr2006:
los93sol, run the binaries in bin at an adb shell, you seem to still be missing some lib dependencies.

also, i might look dumb here, but I cant get a dmesg or remount system as read write. im using "adb shell dmesg > dmesg.txt" and get "klogctl: Operation not permitted" which seems kernel related according to this: https://lists.ubuntu.com/archives/ubuntu-devel/2011-May/033240.html

also when using adb shell mount -o remount,rw /system or even su and busybox with that command in the terminal i get constant permission denied errors. dunno how to fix that.
[Samsung Galaxy Nexus] sykopompos:
That's selinux blocking adb remount which is normal.

dmesg needs to be ran as root otherwise you get a permission denied

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
Tried to meet all the dependencies for libandroid_runtime.so, but got stuck at some issues with libinputflinger.so, which appears to be new in Android L. Someone with more time can look at this, but I wanted to share what I found.
[Samsung Galaxy Nexus] whoshotjr2006:
from the awesome rbheromax over at androidforums(talking about surfaceflinger with unmet dependencies, adapt for inputflinger):

http://androidforums.com/6645396-post13.html

hope that helps
[Samsung Galaxy Nexus] sykopompos:
Inputflinger as a bin is unneeded, it was a nexus 5 new bin in L but it seems it is specific to the n5. I removed it from the n4 port a little bit ago and it runs perfectly

Sent from my LG-D851
[Samsung Galaxy Nexus] whoshotjr2006:
hey i didnt realize you were the nexus 4 l port maintainer, ive been studying your work closely trying to get L running on the zte awe, and now trying to help here. thanks for all your hard work, we would really be lost without you.

im really just grasping at straws here now lol, trying to get anything to work
[Samsung Galaxy Nexus] sykopompos:
I'm a bit more than a maintainer, it was defconoi and I who got it booting in the first place.

Getting on other devices at this point is difficult because of things like the egl drivers and such, they are hardcoded in and I have been working hard to break those so I can update the drivers myself but since L brings open gl 3.1 (no current phone even supports it), where it ties in is closed source and wound through a few things causes it to break when you try to just change the drivers without everything else

Sent from my LG-D851
[Samsung Galaxy Nexus] whoshotjr2006:
sorry couldnt find the word i was looking for so i used maintainer

i noticed that pretty much every device that got the L preview ported over uses the adreno 320 chip like the N5 uses(and you mentioned the egl stuff is hardcoded in), i got the system pretty much running on the zte awe with somewhere in the ballpark of the same hardware, the only problem is it uses a 305 so the egl stuff just dies on me immediately. thats gonna factor in pretty big in the gnex port until source drops since we use powervr, wont it?

edit: i guess i should say, the work your doing trying to break what you need to, would that help us too?
[Samsung Galaxy Nexus] sykopompos:
That's why I have been trying to break the hard coding of that part to try to get it working on other devices

Sent from my LG-D851
[Samsung Galaxy Nexus] whoshotjr2006:
ok, makes sense

anything we can do to help?
[Samsung Galaxy Nexus] sykopompos:
I've been digging through the api reference and aosp to figure out exactly where it gets hardcoded in and unfortunely it seems like it is hardcoded into every new app and framework bit because they added the new shaders and such into everything

Sent from my LG-D851