yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] micku7zu:
lpv-79-mako-port-beta-2.zip mirrors

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

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

Androidfilesharing mirror: http://fs1.androidfilesharing.com/c7f0147d6feaa010

Mega mirror: https://mega.co.nz/#!SdFCDJ4T!qdt_T7fbiCK3xGSNFylHW_s-5IcDFEURps-XellLPiI

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

Dev-host mirror: http://d-h.st/4XQ

Firedrive: http://www.firedrive.com/file/4A1988FA91119CFB

[MENTION=1050103]sykopompos[/MENTION] you can put this in first link if you want.
[Nexus 4 Android Development] sasa_gm:
Is it just me, or they really improved screen colors calibration? It looks like the contrast is much better. Also, grey letters on white background were hard to read on KK stock calibration. Now they're fine.
[Nexus 4 Android Development] brsclkr:
awesome work, im downloading now. im following topic for 1 week and never think that everything works like this. after one day usage i wanna donate

can anyone give donate link for the devs???
[Nexus 4 Android Development] natzy85:
I can confirm it does work. Now I really won't go back to KK :))
[Nexus 4 Android Development] don_kamil:
Google Drive mirror? Any chance?
[Nexus 4 Android Development] m_usmanayub:
working perfectly with MultiROM.... :)
[Nexus 4 Android Development] simms22:
not a solution, since it fixes nothing for you. its a temporary fix. or, you can just keep it on and get annoyed watching it not disconnect. your choice. me it doesnt bug. i use a different custom kernel.
[Nexus 4 Android Development] rskyline:
[MENTION=1050103]sykopompos[/MENTION] already tell me what I wanted to know. If there was a fix or not. I don't get your point tho
[Nexus 4 Android Development] sykopompos:
A test build of 4.1.99 is coming in about 20 minutes with a lot of new proprietary files in it

Sent from my C6916
[Nexus 4 Android Development] hmillos:
I've got a weird bug when pin unlocking my phone (slide up), happens when I lock screen on twitter and my phone enters deep sleep, after I wake it up and introduce pin the phone shows twitter but then it locks again, and I have to slide and introduce pin again to successfully unlock phone, not an important bug tho.
[Nexus 4 Android Development] rskyline:
Waiting to flash an report back sir!
[Nexus 4 Android Development] Psichi:
I believe this is a known bug from the L Preview source. Not much that can be done until Google pushes a fix
[Nexus 4 Android Development] FatherD:
Yep .. got exactly the same - running beta 4, just updated to 4.1 hasn't yet happened again .. soon to 4.1.99 lol wonder if this is a common problem - the deep sleep thing that is, not the flashaholic tendencies!
[Nexus 4 Android Development] sykopompos:
The test is gonna need a full run through of tests since it is a lot of the proprietary bins and libs updated. Some egl drivers are actually upgraded too (the main ones in lib/egl/ were untouchable except for the egl tools because they crashed the display at the splash screen)

Most of the main functions are working but since I haven't played with L much or put it through it's paces myself, I am unsure about a lot of it.

Sent from my C6916
[Nexus 4 Android Development] rskyline:
Sure just tell us what do u want to test!
[Nexus 4 Android Development] sykopompos:
U will find crack flashing is a common thing when I'm involved in the project or if it is my own

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
Everything? Report back anything that was working before but is now broken, anything that was broken and is now working. WiFi not disconnecting will not be fixed in this because that is related to the port's kernel source and was not touched.

I made a small change to Bluetooth while I was in there (just changed a permission on a Bluetooth file)

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
Mako test build 4.1.99

Here is testbuild 4.1.99 for mako

http://www.androidfilehost.com/?fid=23578570567715695

This is a lot of updated qcom binaries so go through, see what does and doesn't work. Report back what was working fine before but isn't now, what wasn't working and is now, any new screwiness with it. Run it through every test you can think of for anything new fixed or broken

I haven't pushed any of it to github yet till I know if I broke the stability of anything that was working before with this test, if all is good, I will upload the changes to github tonight after work. Consider this a unofficial build and do not report anything on the issue tracker for it, when commenting something broke or is better, make sure you say it is the testbuild 4.1.99, test other kernels if you are inclined too also and make sure nothing broke with them also (defconoi's can be considered safe as far as the test is concerned)

Is NFC still a issue with not turning off? I see it doesn't turn off in the test build
[Nexus 4 Android Development] sykopompos:
It kinda looks like a hot wheels car....

Just going through my pictures of what needs to be saved before I do a factory reset on my Sony

Damn it, it didn't upload the pic :(

Sent from my C6916
[Nexus 4 Android Development] SurlyDuff:
Right thread: Crap. I've been getting a ton of crashes on Beta 4 (and 4.1) again for no discernable reason. Very similar to the previous issue with database restore, except I even tried a fresh start just allowing Google Backup to run the restore (rather than using Titanium Backup at all) and still seeing it shut down upon unplugging, shut down when opening a game, etc. Looked through a few logcats of the crashes and apart from the shutdown service starting, there doesn't appear to be a common factor causing them. I'm going to give 4.1.99 a shot, but if that doesn't fix everything I might try reverting to Beta 3.
[Nexus 4 Android Development] ramjet73:
4.1.99 Update

I just installed 4.1.99 and it took me three tries to get it initialized but it's up and running now. :good:

The first time it locked up on me so I powered off and restarted. The second time I was able to get to the WiFi setup screen but couldn't get the keyboard to work. Powered off and rebooted again and the third time I was able to complete the WiFi configuration and I'm working on the setup now.

Mine was a clean installation with cache and data formatted before I flashed.

I'll continue to test after I finish my setup.

ramjet73
[Nexus 4 Android Development] ramjet73:
Is the 4.1.99 build supposed to have the original icons (see attached screenshot)?

ramjet73
[Nexus 4 Android Development] criminalzen:
first boot

first boot on test with a clean flash was as usual, except getting initial wifi sources took longer than usual and they all came at once instead of two then two more as usual at home.So far every thing else is usual for me. wifi-google play reload, etc. more later.. gotta mow lawn
[Nexus 4 Android Development] ahmedz_1991:
please help with wifi bug: when wifi drops, phone still shows as connected. I have to manually disable/disconnect, then connect or fall to mobile data. bug there from first beta till 4.1
[Nexus 4 Android Development] SurlyDuff:
If you're saying what I think you're saying, that's a known bug.
[Nexus 4 Android Development] sykopompos:
Yes. I haven't push the new ones in yet as this is just a test build of the new proprietary files

Sent from my C6916
[Nexus 4 Android Development] dodgebizkit:
So this has an updated kernel to the 1st page beta kernels?

...undervolted?

... ... If it doesn't work how we expect can we then flash beta 8 again?

Sorry for bombarding you - the illuminatí has not yet downloaded your mind into our database :)

----------------------------

I am the Illuminatí :)
[Nexus 4 Android Development] sykopompos:
No, defconoi's kernels are custom kernels based off the same source. They aren't included in the base port as this is a clean port with no extra features till the bugs are worked out

Sent from my C6916
[Nexus 4 Android Development] dodgebizkit:
OK cool - so if I flash beta 8 kernel with it it won't affect your test? Or should I stick with the base kernel while reporting on this beta?

----------------------------

I am the Illuminatí :)
[Nexus 4 Android Development] sykopompos:
Testing other kernels is part of the tests

Sent from my C6916
[Nexus 4 Android Development] criminalzen:
delete
[Nexus 4 Android Development] manulemaboul:
Just in case some would be wondering, you can dirty flash 4.1.99 over 4.1. So far, everything that used to work still work for me.
[Nexus 4 Android Development] sykopompos:
There is some new ril files in there too btw

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
That is what I was hoping to hear. I didn't think they would break anything but maybe improve things and maybe fix a few things.

I'm curious about Bluetooth BTW if it fixed the profiles issue, I doubt it but it is possible.

Video play back might be a bit smoother with a new stage fright lib and ardeno rs drivers. There is a new location and GPS libraries along with sensor libs, camera libs, and I can't remember what the other stuff was. It was about 20 new libs and bins that were merged in for the test build so that is why I was hesitant to put up as a regular build with so many new things all at once

Sent from my C6916
[Nexus 4 Android Development] Connor Baker:
Holy cow is that up on git yet!?

- Connor Baker
[Nexus 4 Android Development] dodgebizkit:
The new build didn't break WiFi exactly but it made it difficult to connect - trying kernel beta 8

----------------------------

I am the Illuminatí :)
[Nexus 4 Android Development] manulemaboul:
Can't test bluetooth, I don't have anything to pair with it.

Animations seems smoother to me by the way, but I've spotted a weird thing with system monitor. The GPU sits at 320mhz when it got 0% usage, just rendering a static tapatalk page for exemple, and actually down to 128mhz when I start scrolling and the usage rise to 1 or 2%. It should be at 128mhz for 0% load, not 320. Anybody can confirm this behavior ?

I think it was there in beta 4 already actually, I remember seeing 320mhz reported in synapse, but I thought it was just synapse. Apparently nope, it really sits at 320 for 0% load.

I guess it's kernel related, maybe something wrong with the GPU gov, he seems to think 0 is 50 or something. Go home GPU gov, you're drunk :P.
[Nexus 4 Android Development] dodgebizkit:
Works perfectly with kernel 8. Bluetooth has always been working for me with mouse and keyboard but I've just found the Bluetooth headset so when it's charged I'll test that :)

----------------------------

I am the Illuminatí :)
[Nexus 4 Android Development] sykopompos:
Not yet, I used 2 different sources, one for testing and one for commits, I'm gonna add the changes to the commit source and push so we know exactly what proprietary files can be changed for future new ones when I get home from work and confirm they didn't break anything

Sent from my C6916
[Nexus 4 Android Development] dodgebizkit:
Bluetooth headset works perfectly.

----------------------------

I am the Illuminatí :)
[Nexus 4 Android Development] Matsilagi:
Everything seems to work fine on my side on the new beta.

Also, what new icons are you guys talking about?
[Nexus 4 Android Development] 0.0:
When your Bluetooth headset auto connects, does it redial the last number called?

Sent from my Nexus 4
[Nexus 4 Android Development] ebart:
On top of the case, eh? [emoji12]
[Nexus 4 Android Development] manulemaboul:
Allright, it's just the reported gpu freq that's borked, confirmed by rendering some 3D, and doing a quite good 3d score at antutu with 200mhz reported, so nevermind.
[Nexus 4 Android Development] dodgebizkit:
Just reconnected it, nope. No dialing :)

----------------------------

I am the Illuminatí :)
[Nexus 4 Android Development] ramjet73:
These.

ramjet73
[Nexus 4 Android Development] martonimix:
I agree totally with this! The GPU has drunk too much.

It remains a lot of time in 320 mhz...
[Nexus 4 Android Development] manulemaboul:
That's just the reported freq who's borked actually. I ran antutu and it passed the 3d test at 200mhz reported, but with a normal score, so it'd runed actually at 400.
[Nexus 4 Android Development] criminalzen:
Yea both the stock kernel and the modified one (v9) report 320Mhz idle for gpu on 4.1.99 with synapse and android tuner. hellscore idles at 27Mhz.. Never noticed before... ;)
[Nexus 4 Android Development] sykopompos:
So is the borked count due to changes in the test or where they already there?

Sent from my C6916
[Nexus 4 Android Development] criminalzen:
no it has been reported for a while ..

first time reported was july 15 with kernel 9 ... others noted same on kernel 10.. I never noticed it till today .. could have been occurring since beginning :)
[Nexus 4 Android Development] martonimix:
They already there in past versions
[Nexus 4 Android Development] sykopompos:
So, so far everything is good with the test build? I would like to see more testing with Bluetooth if initial reports are saying it is cleared up

Sent from my C6916
[Nexus 4 Android Development] thebuga:
Was it from my zip? In what app did you experience problems?

I find it very hard to believe the font it self would be the cause for the trouble since it does not carry any value of color, foreground or background, but I am willing to investigate.

In my experience not a single time any text failed to appear or rendered incorrectly.

For the record my actual L installment was made from TRWP 2.7.1.0, formated data, system and cache, wiped dalvik and internal storage and then proceeded installing, in that order, L beta 4, defconoi's kernel beta 9, UKM 2.7.2, systemui_modded.zip (the first one that appeared) and finally my own Roboto_v1.2-Update.zip.
[Nexus 4 Android Development] :
One small bug, when the screen shuts off from locking it or from screen timeout, it show have a CRT monitor off effect. I'm on Beta 4.1 and the screen shuts off with no animation at all
[Nexus 4 Android Development] dravenSt0rM:
I started using Andoid L today, and as far as I can say, everything so far works perfectly. If I find something I will let you know.

Also, I read all 463 pages of the thread, got bored, but I did it somehow.
[Nexus 4 Android Development] dodgebizkit:
The animation is working for me - dirty flash too

----------------------------

I am the Illuminatí :)
[Nexus 4 Android Development] kdellea:
Guys please don't flame me. I'm giving this phone to my wife since I just bought myself a new n4 and I need to put this one back to stock for her. What is the best way to do this? I have no nandroid BTW.
[Nexus 4 Android Development] hmillos:
Today I was unable to unlock my phone using PIN, no matter how many times I tried, It re-locked again and again and again, also saw a weird thing, my wallpaper changed automatically, I'm using Nova Launcher BTW, I suppose that's the reason, I had to restart the phone.
[Nexus 4 Android Development] Raiden350:
Do you guys know if UnleashTheGoogle works on L ?
[Nexus 4 Android Development] kittuboy:
Not a bug. Try reflashing. I'm on 4.1 too and i have no problem.

None, you are permanently stuck with us, hahahaha!!

(Simple way out. Download Wugfresh's NRT, download factory image for whichever version you want and follow the instructions in NRT.)
[Nexus 4 Android Development] kdellea:
Thank you. I I'm not leaving. My n4 will be rocking this port. My wife likes her lame apps though.
[Nexus 4 Android Development] defconoi:
Specifically synapse had no text
[Nexus 4 Android Development] kdellea:
I also had an issue customizing the Poweramp widget with the new font.
[Nexus 4 Android Development] kittuboy:
It doesn't, yet.
[Nexus 4 Android Development] Rohit02:
Ditto.. :( Hope some one helps.. I have changed the lock style to pattern now, np from yesterday.
[Nexus 4 Android Development] clefebvre81:
Anyone else noticing ghosting going on. I keep seeing what looks like burn in when ever I change screens I still see what was on the last screen lightly in the back.
[Nexus 4 Android Development] anandbhat:
I flashed this ROM as my primary rom and then installed Multirom Manager which wont work with the kernel provided with this Rom. I flashed the 4.4 kernel that Multirom Manager needed with the kexec-hardboot patch but then my WiFi stopped working. I tried flashing the WiFi fix zip but no dice.

Is there a way to flash this rom as my primary rom and then install Multirom manager and still have WiFi work ?
[Nexus 4 Android Development] IndianKarmas:
not sure what unleashthegoogle might be, but think u are referring to OK Google anywhere.....it does work on L Preview (I am already using it)....but the way I enabled it....

very silly way....but to enable ok google everywhere....all u do...

in google search on ur phone....search for "Ok google everywhere"....then go into settings for google search>voice>turn on audio history> go to ok google detection n choose where u want it to be active.....ONLY requirement....language needs to be US English :)
[Nexus 4 Android Development] xDroid4Lifex:
So I decided to come back to the port after running LiquidSmooth for a bit, all is well except one thing.

Did a clean flash of beta 4.1, having issues with NFC not turning off like in the first betas. Tried clearing the nfcservice apps data and it still won't turn off. Should I attempt the update to the 4.199 test build?
[Nexus 4 Android Development] googleygoggles:
Or.. Go to the Google settings app→hotword detection→OK google everywhere option

Sent from my butt running Android L
[Nexus 4 Android Development] sykopompos:
If you read the post on the test build, I specifically asked if NFC is still staying on because it does on the test build. Says broken pipe to sensor1.so in the logcat when I tried it.

Now sensor1.so is a also a new proprietary lib but if I put it in, the camera breaks, I think I might know what is causing this so when I get a chance I will look at it

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
Unleash the google enables the debugging menu in google settings

Sent from my C6916
[Nexus 4 Android Development] N3V3RS3TTL3:
I've experienced the same
[Nexus 4 Android Development] IndianKarmas:
thanks for the info :)
[Nexus 4 Android Development] jodiac:
Playstore crashes

Help.... playstore crashes everytime.... after I try to flash the moob kernel... I flashed it after updating process to beta 4.1
[Nexus 4 Android Development] googleygoggles:
Sorry no ghosting here tested it for a while.. Beta 4

Sent from my butt running Android L

---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------

Moob kernel didn't work for me at all and sent me to a bootloop

Just reporting my experience

Sent from my butt running Android L
[Nexus 4 Android Development] mightybrick:
I will test it in the morning on my way to work. I have a headunit in my 4Runner with bluetooth.
[Nexus 4 Android Development] ramjet73:
You can download the factory image you want to restore from this page and follow the instructions at the top to install it and lock the bootloader

or

you can download the WugFresh Nexus Root Toolkit and do it all with a few mouse clicks.

Your choice. ;)

ramjet73
[Nexus 4 Android Development] jodiac:
yea... then I re-flashed the rom... this should revert back to original kernel right? But my play-store is still broken.
[Nexus 4 Android Development] 0.0:
[MENTION=1050103]sykopompos[/MENTION] auto connecting a Bluetooth device still redials a number on test 4.1.99. That's all I have for now

Sent from my Nexus 4
[Nexus 4 Android Development] sykopompos:
What bugs me is that people say this doesn't happen on the n5 yet there is a aosp commit recently that solves the behavior that we are seeing which makes me go hmmmm. I just can't roll that new commit in without breaking Bluetooth which erks me because I know what is going on and the fix yet I can't fix it properly

Sent from my C6916
[Nexus 4 Android Development] willy1980:
I love this Rom , it's a lot better than I thought it would be for a developer preview. Great work by all involved.
[Nexus 4 Android Development] 0.0:
What happens when it is merged? Bluetooth won't turn on or FCs? Maybe there are other commits that are associated with it. I'm just spitting out what I'm thinking

Sent from my Nexus 4
[Nexus 4 Android Development] sykopompos:
I forget exactly what it is, it was either bluedroid or bluez that had the commit. Tracking down the linking files is mako specific code in the device/lge/mako/bluetooth that gets rolled into it and I have tried pushing it in but reports back were FC's on Bluetooth.

Now that I'm actually up to date on my nexus and everything is slowing down I got time to actually debug and test things on my own.

What I did notice is a lot of the apps have changed on my latest aosp build vs the one I did about 2 weeks ago but I don't see any commits to them so I'm wondering if I can push aosp apps in now or not.

Figuring out what shared libs can be updated is gonna be a nightmare though and it might not me possible to merge any updated libs.

All I know is that I already learned a ton of what is different between L and kk so when the source hits, I will be an expert already

Sent from my C6916
[Nexus 4 Android Development] 0.0:
I've been Google searching, and it may not be a Bluetooth problem, but maybe a phone problem, meaning something in the Dialer, TelephonyProvider, or similar. Maybe frameworks. I'm not too sure. Could just be a permissions issue, but I feel like it goes deeper than that. I'm sure you'll figure it out

Sent from my Nexus 4
[Nexus 4 Android Development] Aashuk Mehta:
Any mirror for 4.1 please Android file hosting and github.com both don't work for me. Dev host will be good
[Nexus 4 Android Development] sykopompos:
As far as I know the Bluetooth profiles for hands free is screwy too and does the same behavior so I don't believe that it is a telephony issue

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
4.2 will be up in a couple hours (actually test build 4.1.99 is basically 4.2, it just needed testing first. Depending on how tired and interested I am when I get home, there might be more change but since I'm already at 9 and a half hours so far tonight, that is doubtful)

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
Also if you are on linux, you can git clone the source and be current with making your own and not have to worry about downloading. Everything is pushed up to github except test builds to make sure nothing is broken first

Sent from my C6916
[Nexus 4 Android Development] chewu.pg:
after flashing a custom kernel from thread and wiping cache in recovery, google apps start crashing all the time, anyone can help with this?
[Nexus 4 Android Development] 0.0:
That's some good news then. Should be easier to debug since the telephony part is not involved. Here is another log for the Bluetooth redial, just in case: https://www.dropbox.com/s/t5eh9s678z4wkkc/bluetooth_redial_bug.txt

Sent from my Nexus 4
[Nexus 4 Android Development] :
Search is your Friend

[MENTION=4829614]Aashuk Mehta[/MENTION] Mirrors here
[Nexus 4 Android Development] sykopompos:
Actually you just provided me the info I need to solve the MMS bug though. Since we are using the nexus 5 MMS service and hangouts, when it tries to read the APN config, it is spitting it back out because it doesn't match. Could be the same thing with Bluetooth

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
Regular gapps for kit Kat are the same as this and ones updated on the market are the same exact ones as ones for 4.4.4? It seems hangouts itself is the issue because that is being seen as n5 so if we can replace it with a n4 version then it would solve the MMS bug

Sent from my C6916
[Nexus 4 Android Development] sykopompos:
commit for the 4.1.99 test build https://github.com/Android-L-Portin...mmit/cf6d4ed5ceb533d43f6a0050ad10a6d87f942cde

I haven't made a new build yet since is what is up and I wanna take a look at a few other things first till I make the official 4.2
[Nexus 4 Android Development] flakinarist:
For me, Wifi still keeps sticking Ehen leaving the range in 4.1 :(

But no mac adress Problem anymore :)