yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] ramjet73:
How close are you to doing that between the N4, N7 deb and N7 flo? If the N5 is the only one with these kind of problems, which are mainly camera and custom kernels at this point, then it probably is worth continuing down that path. But if the concept isn't going to work across at least all the Nexus devices it may be time to rethink it.

I'm not giving up yet, just wondering if the same code base for four devices with different hardware is realistic. OTOH, that's pretty much what CM does so in theory it can, but they have lots of people working on their ports. I wonder if checking their repos for where they branch between the N4 and N5 would help any?

ramjet73
[Nexus 4 Android Development] sykopompos:
They are the same exact code base, n5 had all the preview libs back in it along with it's etc.

The real point as in code base is if I can base other devices off of it. It also gives me a point to track down what change was made and were because like I'm hitting on the m7, I have no clue what has been modified and what hasn't been. Restarting over so I can have a visual exactly where and how each device got to where they are helps me troubleshoot issues along with having a upgrade path for each device.

If I know this proprietary lib is good and that one is bad, it is normally the same proprietary lib causing the issues

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
new flo build [MENTION=2981094]bitstra[/MENTION] [MENTION=4756018]manueltts[/MENTION] https://drive.google.com/file/d/0By0vn8iv_zrVV2VILTMwX1ZiX2c/edit?usp=sharing

new deb build https://drive.google.com/file/d/0By0vn8iv_zrVRUhQT1FVSFVzWkE/edit?usp=sharing
[Nexus 4 Android Development] ph37rd:
Not to mention an excellent liar. PERFECT for politics ?
[Nexus 4 Android Development] ramjet73:
OK, so where do we go from here?

The Google Camera and Camera Zoom FX both work on the real preview and don't work on the port so I really doubt that it's the camera app, unless we need a different camera app to accommodate the common code base. We've tried swapping a lot of camera related files between the original test ROM and the preview and none of those swaps fixed it. I'm sure there are still more camera files to swap but is there any way to go about this more scientifically? If the logcats aren't giving anything specific enough to isolate the problem is there documentation somewhere for the camera "stack" so we can concentrate on the modules that would be likely to cause this problem.

As you've said a couple times already, it seems to be a sensor/HAL issue and that would be logical since there is no way those modules can be common across different hardware configurations.

Should we try taking all the camera related files from the preview at one time to make sure we can get the camera working at all, then back off those files a little at a time if we can?

ramjet73
[Nexus 4 Android Development] skiman10:
[MENTION=4876414]skiman10[/MENTION]
[Nexus 4 Android Development] sykopompos:
I also went looking for missing camera libs while I was at it and a couple sensor ones.

It is odd that the n5 doesn't have a sensors hal O.o but I got a test build that I went through and I also threw the aosp camera 2 apk in to see if that will work

Sent from my LG-D851

Changes not staged for commit:

(use "git add <file>..." to update what will be committed)

(use "git checkout -- <file>..." to discard changes in working directory)

modified: working/system/bin/mm-qcamera-daemon

modified: working/system/bin/sensors.qcom

Untracked files:

(use "git add <file>..." to include in what will be committed)

working/system/app/Camera2.apk

working/system/lib/Camera2/

working/system/lib/libjni_eglfence.so

working/system/lib/libjni_filtershow_filters.so

working/system/lib/libjni_jpegstream.so

working/system/lib/libjni_latinime.so

working/system/lib/libjni_mosaic.so

working/system/lib/libjni_pinyinime.so

working/system/lib/libjni_tinyplanet.so

working/system/lib/libsrec_jni.so

working/system/lib/libvideoeditor_core.so

working/system/lib/libvideoeditor_jni.so

working/system/lib/libvideoeditor_osal.so

working/system/lib/libvideoeditor_videofilters.so

working/system/lib/libvideoeditorplayer.so
[Nexus 4 Android Development] sykopompos:
I'm a terrible liar actually. I try to always tell the truth and if people don't like it blunt, oh well, they will get over it

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
Oh man, I was sleep away an hour (my wife too :) )

downloading Flo_Test6 now and will report back later ...
[Nexus 4 Android Development] ramjet73:
Did you upload that test build yet? I'm going out to pickup some dinner but I should be back in about 20-25 minutes.

ramjet73
[Nexus 4 Android Development] sykopompos:
alright [MENTION=275009]ramjet73[/MENTION] here is the next test https://drive.google.com/file/d/0By0vn8iv_zrVYjFiWTFTNWFsVDA/edit?usp=sharing

here is audit2allow output on your elemental dmesg. I think I see why those custome kernels aren't working. Kernel modules are blocked and I gotta fix rmt storage for hammerhead

#============= init ==============

allow init fuse:dir search;

allow init fuse:file { write getattr open };

allow init shell_data_file:dir { write add_name };

allow init shell_data_file:file { create open ioctl append };

#============= init_shell ==============

allow init_shell devpts:chr_file { read write getattr ioctl };

allow init_shell fuse:dir { write remove_name search add_name };

allow init_shell fuse:file { write create unlink open };

allow init_shell kernel:system syslog_read;

allow init_shell self:capability dac_override;

allow init_shell tmpfs:lnk_file read;

#============= netmgrd ==============

allow netmgrd kernel:system module_request;

#============= rmt ==============

allow rmt self:capability dac_override;

#============= sdcardd ==============

allow sdcardd system_data_file:dir { read write open add_name remove_name };

allow sdcardd system_data_file:file { write unlink };

allow sdcardd unlabeled:dir { read getattr open };

allow sdcardd unlabeled:file getattr;

#============= untrusted_app ==============

allow untrusted_app apk_tmp_file:file write;

allow untrusted_app init:unix_stream_socket connectto;

allow untrusted_app su_exec:file { read open execute_no_trans };

#============= vold ==============

allow vold kernel:system module_request;
[Nexus 4 Android Development] bitstra:
Flo_Test6: NO SUCCESS :(

- WiFi can't be switched ON!

-BT can't be switched ON!

attached logcat...

(Wish I could help more here - but ATM my skills seem to suffice only for Testing :( )
[Nexus 4 Android Development] sykopompos:
Does the camera work?

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
Wanna hear a derp moment [MENTION=275009]ramjet73[/MENTION] ?

There is a new sensor hal for the nexus 5, it is in vendor/lib/hw and I completely did not see that there :banghead:

So while we are all setup for aosp hal files, we had one missing. Derp

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
Feedback for N5-L-Breadcrumbs-Bunnies-and-Witches-5.3-TEST-3.zip

The L camera app still gets "Can't connect to the camera" and the AOSP camera app gets "Unfortunately, camera has stopped", right after boot without opening it and every time it's opened.

Flashed ElementalX kernel and still not showing any APN's in settings and both voice and data cellular are not working.

ramjet73
[Nexus 4 Android Development] sykopompos:
I figured it was a long shot on that one.

Grab me the dmesg avc so I can run it and see if there is anything specifically related to wifi in it being blocked

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
Yes the camera on FLO_Test6 works fine here - took 3 shots and a short video!...
[Nexus 4 Android Development] sykopompos:
That tells us for sure that it is a sensor then and not a missing lib then.

I haven't made the new sepolicy yet, that in itself is time consuming to open up each socket, wait for it to complain in the never allow rules, hunt down which one is being blocked and then do it again till each one is worked out

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
I thought about it. I think I know why Bluetooth is borked. I will take a look at that soon. As far as wifi, I'm not sure why that one is dying (I know why in test 6) I will have to look into that a bit more

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
here is the missing new aosp sensor hal, [MENTION=275009]ramjet73[/MENTION]. it goes in vendor/lib/hw and replaces the old L preview one
[Nexus 4 Android Development] sykopompos:
[MENTION=2981094]bitstra[/MENTION] can you try the test 4 or 5 bbw boot.img (latest will be busted for sure) on the official preview and see if the WiFi problem carries over to there? Trying to isolate if it carries over and is in the ROM or the ramdisk

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
O.K. I pull the boot.img from Test5...

Edit should I test it with lpv79 or lpv81c???
[Nexus 4 Android Development] sykopompos:
Either or will be fine. I think it is a boot.IMG problem on the n7

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
Replaced that file in the test 3 for hammerhead zip file and did a clean flash. Both camera apps are now getting the "Unfortunately, camera has stopped" error.

ramjet73
[Nexus 4 Android Development] sykopompos:
Can you try back on test 2. Apparently changing the hal made something fun happen

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
O.K. took lpv79 - flashing right now...
[Nexus 4 Android Development] sidnoit22:
Guys don't flash these test images on Mako. I tried nothing happened. :cyclops:
[Nexus 4 Android Development] bitstra:
lpv79 official preview with boot.img from Flo_Test5 WiFi DHCP works fine! + BT works fine! :confused:

---------- Post added at 09:12 AM ---------- Previous post was at 09:10 AM ----------

So it seems, its a ROM issue???

But wait I'm on secondary multirom - will have a Test as single ROM - with that lpv7 official - to be sure...
[Nexus 4 Android Development] sykopompos:
That allowed me to isolate where it is and now it looks like flo has some leftover bunny stew with a permissive boot.IMG now like hammerhead got so the original intent on those have been achieved. Now it is a matter of getting them to work on the official versions.

It might be getting to the point of going back to the drawing board and starting over like [MENTION=275009]ramjet73[/MENTION] suggested and use the preview images as the bases for these because somewhere it the converting over, it got borked.

Apparently it really was some ancient magic that we did on mako that doesn't seem to wanna be replicated

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
Test 2 with the newer sensor file gets "Cannot connect to camera" with the L camera. There is no AOSP camera in that ROM, and I think that app might have been taking over both camera shortcuts when I did a clean flash of the test 3 ROM.

I still think we should try to get the L camera working with all the camera related files from the N5 preview. If we can't do that it may be necessary to use the preview itself as the base for the N5. I'm sure N5 users aren't going to be interested in an L ROM without a working camera.

ramjet73
[Nexus 4 Android Development] bitstra:
understood - shouldn't we start from lpv81c then???

---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------

made sure - lpv79 with Test5_boot.img works with WiFi and BT also as single ROM!

- getenforce gives me PERMISSIVE

I give it a go with lpv81c too...
[Nexus 4 Android Development] ramjet73:
I agree.

I tested the N5 version of lpv81c with the boot.img from bunny and everything seemed to work fine except superuser and [MENTION=1050103]sykopompos[/MENTION] seemed pretty sure he knows how to fix that.

We can still merge in as much AOSP as possible once the ROM's are working.

ramjet73
[Nexus 4 Android Development] sidnoit22:
[MENTION=1050103]sykopompos[/MENTION] There are some stuff which causing Random reboots on the ROM. I was using Stock kernel and i was using Camera and suddenly Hanged and rebooted. :( Will try defconoi's kernel now.
[Nexus 4 Android Development] sykopompos:
We can start back over with 79 and merge the new proprietary files in, it segments this way we can isolate blocks of it at a time instead of 100 new files to try to track down the one screwy one.

On flo it should just be a matter of rebasing. And then merging them all in at one time since we know exactly which proprietary files are good to be upgraded so we can do that in one fell swoop, then come back do the aosp.

It might also be a good time to restructure mako too while we are at it. It is too much of a hybrid at this point between n5, n7 and aosp which means there is a lot of extra files that don't need to be there along with a bunch of other junk that might have been fine for the original booting but it really is time to clean house on it.

Actually maybe it is a good idea to use 81c if we are rebasing from the beginning too on mako. We can carry over some things like the modified systemui and framework-res.apk but since it is such a hybrid, maybe that is why I'm running into problems with updating with aosp too

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION], [MENTION=275009]ramjet73[/MENTION]

What does that mean in consequence for the whole SELinux stuff and for AOSP base project by sykopompos?
[Nexus 4 Android Development] ramjet73:
My understanding is that the selinux mods can be done with the boot.img and security files in the ROM and the AOSP stuff that works can still be merged into each ROM version. I think that's essentially what [MENTION=1050103]sykopompos[/MENTION] has been doing with the N4 ROM.

ramjet73
[Nexus 4 Android Development] sykopompos:
The base aosp and selinux stuff carry over with it because the whole boot.imgs is everything I did with aosp and selinux.

That's my baby right there and has been from the beginning.

All the other aosp stuff merged in can also carry over, it is just rebasing all the ports at once to get rid of any excess crap (mako has a lot) and solving some issues on them all

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
The n4 is such a hybrid right now that my issues with merging in aosp might have been getting stalled as a direct result of that. I might have been trying to merge in something aosp and hitting against something that was a hybrid n5 file which broke some of my efforts (actually it was on some things and I know that for sure now that I went back up through it and seen everything and know exactly how much of a hybrid that it is)

This will be a good thing to basically start over and the title for the current version I have been working on with breadcrumbs will allow us to do that. I might even get Bluetooth working correctly like this because that is a huge hybrid in itself.

I like this idea a lot actually even though it means a lot more work for me to do so and pushes back the g3 and 1+1 ports but everything will be a lot lot cleaner going forward.

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
So, that should be way - start from lpv81c + latest functional bunny-kernels.

But sykopompos has to sort/merge all the aosp stuff from the beginning a second time - How can we support this???
[Nexus 4 Android Development] sykopompos:
Not so much. I have a list of the proprietary files that are good and I have all the files aside so I start with mako, wipe it clean on github, download 81c for flo and work it up. I can do flo and mako at the same time then. Then jump over to the n5

Sent from my LG-D851
[Nexus 4 Android Development] Jakkumn:
Its working fine on mine. Just swapped between USB on my computer and a wall charger I have. Was able to tell the difference between AC and USB.
[Nexus 4 Android Development] bpear96:
Awesome work guys! Running great.

Uploaded some mirrors :D.

https://www.cubbyusercontent.com/pl/lpv-79-mako-port-beta1.zip/_4158d3ceb6fa4000b173d0dfa4ff502d

Androidfilehost mirror uploading now.
[Nexus 4 Android Development] Hikari:
The other one was just a temporary thread opened without the knowledge of the actual devs in order to deal with all the Dev talk and mess that was going around in the rumors and discussion thread in general forums. Some people accused the OP for trying to steal credit but the devs (sykopompos mainly) said it was OK to keep the thread up until he himself created a thread (which is this one). The other one should be closed around now I think.
[Nexus 4 Android Development] ramjet73:
Here you go, including a couple of screens I haven't seen until this build. ;)

ramjet73
[Nexus 4 Android Development] micku7zu:
lpv-79-mako-port-beta1.zip mirrors

Google drive mirror: https://drive.google.com/file/d/0BxktHhMrAobWT2VHNmZYaXVsQlk/edit?usp=sharing

Copy mirror: https://copy.com/q7eqFD7uDwhR

Dropbox mirror: https://dl.dropboxusercontent.com/u/24395823/lpv-79-mako-port-beta1.zip

Androidfilesharing mirror: http://fs1.androidfilesharing.com/0228524b0417b406

Mega mirror: https://mega.co.nz/#!6dk2hDbY!ERvSwDhx_fU83RFdwguFe1--zrsEvdLs3jl6jf0rZJ8

Romcook mirror: http://romcook.com/?d=53B9CAE216

Dev-host mirror: http://d-h.st/1hV

Cubbyusercontent: https://www.cubbyusercontent.com/pl/lpv-79-mako-port-beta1.zip/_4158d3ceb6fa4000b173d0dfa4ff502d (thanks to [MENTION=3007198]bpear96[/MENTION])

Firedrive: http://www.firedrive.com/file/678CE0DC9726BC3D (thanks to [MENTION=4653674]hardrockk[/MENTION])

[MENTION=1050103]sykopompos[/MENTION] you can put this in first link if you want.
[Nexus 4 Android Development] sykopompos:
I figured out the problem while I was driving and posted how to do the fix on here but couldn't implement it so I asked someone to try it because [MENTION=1316336]defconoi[/MENTION] was busy at the time

Sent from my C6916
[Nexus 4 Android Development] Clayfree:
Exchange email working :highfive: Thank you devs for all the hard work and little sleep! This has been an exciting 4 days.
[Nexus 4 Android Development] bravovn:
tks. It said need 6 hours to full charge. OMG
[Nexus 4 Android Development] wong.izzat:
http://www.androidheadlines.com/201...android-l-preview-thanks-successful-port.html
[Nexus 4 Android Development] iH8ra!n:
Thank you for clearing this up again! :)

Here is another comment/statement on that topic by me which explains the complete situation again once more! :)
[Nexus 4 Android Development] sykopompos:
Damn it, as soon as I walked away from my computer

Sent from my C6916
[Nexus 4 Android Development] Isus <3:
http://puu.sh/9ZMOu/36f3c5ecc6.png

What is taking so much space?!?!?!?
[Nexus 4 Android Development] WoodroweBones:
I've had a couple issues so far:

- The floating preview in the keyboard has a weird background

- Superuser doesnt appear to be working? The only app I've tried it with so far is Helium when trying to restore my apps. I get the prompt and allow it but then it fails
[Nexus 4 Android Development] Powereh:
I knew it was something like that! I couldn't fully recall.

Either way its great work!
[Nexus 4 Android Development] sykopompos:
Mostly because I hate making new thread op and we were all busy trying to sort the bugs out so I didn't want a new thread to be bombarded with this bug and that bug while we were working on them.

We wanted to get a stable release out first

Sent from my C6916
[Nexus 4 Android Development] johnb380:
Amazing guys thank you for the build now i will finally tast Android Ls sweet necture! [MENTION=1050103]sykopompos[/MENTION] and everyone involved are def living legends in the making!

Thanks a ton!

Download is done time to flash!
[Nexus 4 Android Development] criminalzen:
superuser working with titainium ..
[Nexus 4 Android Development] bpye:
There are some files that we might be able to remove.

The floating preview is actually a bug with the l preview keyboard, might be able to fix the padding if I decompile it. As for superuser, I don't know. Maybe the application isn't compatible with Android L yet? Get a logcat and we'll have a look.
[Nexus 4 Android Development] sykopompos:
[QUOTE=Isus

We need to clean it up some more and get rid of the extra stuff left over from the n7 and n5

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
Are you using koush's superuser?

Sent from my C6916
[Nexus 4 Android Development] Gu$houn*:
Experienced that too, I pulled it from purity, same results like you. I think Google force us to use that silly hangouts ... I replaced the mms app with 8SMS from playstore, it's almost the same.

P.

[sntfrmnxs4]
[Nexus 4 Android Development] ferrocene:
No, of course not
[Nexus 4 Android Development] Matsilagi:
I still wanna know why all of my games arent working, they get ran, executed, but they cant find the OBBs, did the directory change?

I dont wanna redownload the datas.
[Nexus 4 Android Development] concaopp:
Hangouts is very good...

Battery life is very good...

See SS, location high accuracy, WiFi on
[Nexus 4 Android Development] ferrocene:
I installed it from the play store

Edit: and then ran it.
[Nexus 4 Android Development] ramjet73:
That's the installer, but you need to run that app and do the actual installation of the BusyBox binary and symlinks or it won't actually be installed.

ramjet73
[Nexus 4 Android Development] Armin_van_buuren:
Battery life it´s awesome.

Very smooth rom and great job guys :good:
[Nexus 4 Android Development] AfroMetal:
Can OP add link to bugs list to the first post?? https://docs.google.com/spreadsheets/d/1-qK3JNngOgpitcy23CrAvLxLfXRbiOvI1RDTGMFAA60/edit#gid=0
[Nexus 4 Android Development] rakeshvskanna:
facing issue with mobile data connectivity

I have installed the beta 2 version.

Everything is good except for some issue with mobile data connectivity.

Of anyone facing the same or do we have any fix for this.

Thanks.... :):)
[Nexus 4 Android Development] Gu$houn*:
For me worked "busy box on rails" which was offered to me from Trickster after I opened it for the first time. I chose the recovery method and all is working fine now.

P.

[sntfrmnxs4]
[Nexus 4 Android Development] klaust58:
Mobile data connectivity and speed was very awesome for me :)

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Android Development] ferrocene:
It's all you, buddy.
[Nexus 4 Android Development] slickw:
my proxymity sensor is dead so this bug is good for me.

"Proximity sensor not working."	-During Calls screen should timeout but it doesn't.-

any way i can get this bug back coz its good bug for me at least.

what files do i need to delete to reproduce this ?
[Nexus 4 Android Development] ed116:
anyone on beta 2 try the viber app? is it working?
[Nexus 4 Android Development] xDroid4Lifex:
Noticed that when I tried to play a video through chrome it won't play? It just re-pauses by itself every time you tap play. Anyone else have this issue?
[Nexus 4 Android Development] sykopompos:
That was the rest of the team's idea so we can get some versioning control in and they are still working on a lot right now so it is incomplete. there are more bug fixes in what is up there already though but more is being worked on along with tools to help other developers port a port of a developer preview to other devices. We already pointed the htc one m7 team working on it in the general direction in the mean time and they already got boot.

as far as beta 3, more and more and more fixes being worked on. We try to get as many bugs fixed between each release and not just a whole new version for one or 2 fixes unless they are major bugs
[Nexus 4 Android Development] tnp9008:
YouTube in Chrome is working fine for me. What site isn't working for you?
[Nexus 4 Android Development] Connor Baker:
You guys all rock! Thanks man for all the work you and the team have been putting in! I have been this excited since ICS!

- Connor Baker
[Nexus 4 Android Development] xDroid4Lifex:
Proximity sensor during calls is working fine for me, screen shuts off normally during call if its on speaker and not up to my head as well
[Nexus 4 Android Development] slickw:
i know it works in beta2. i want to break it again like it was in previous builds.