yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] sykopompos:
Not gonna be able to get it ins the settings most likely so gonna have to use a script or something with radio options or someone make a quick app that does the same function and reads the apns.

Radio is gonna have to be figured out in the ramdisk. Flo actually has lines to start the ril but turns it back off, deb uses the same function except for the turning it off part. I thought I got that but I might have missed something there since it is still reading WiFi only when it shouldn't.

Camera should be alright unless I accidently added that stupid sensor1.so in when I was doing deb which is probably the case
[Nexus 4 Android Development] :
Didn't even see that, it's in Synapse. Thanks
[Nexus 4 Android Development] ramjet73:
MTP Access

Anyone else having issues with MTP access on the latest N4 build(s). I can use the same cable and USB port with my Nexus 5 and MTP works fine, and ADB/fastboot both seem to work with the Nexus 4, but I can't get it to show up as an MTP device even after unticking and ticking both the MTP and USB debugging settings or disconnecting/reconnecting the USB cable. :confused:

Edit: Correction, ADB doesn't work for me with this ROM, but I tested with TWRP and that worked and fastboot does work with the N4 in bootloader mode so I think the cable and USB port are fine. I'm gonna restore the BNB 5.9 build and check it there.

ramjet73
[Nexus 4 Android Development] sykopompos:
And now you get to test it on the n5 :D
[Nexus 4 Android Development] :
MTP is perfect here on my Hackbook, latest test build and defconoi kernel
[Nexus 4 Android Development] sykopompos:
That will be hell to track down if I did indeed somehow break it
[Nexus 4 Android Development] :
You didn't, it was working for me on the stock kernel and is still working on defcon 81u-r1
[Nexus 4 Android Development] sykopompos:
We are actually using kit kat's adb drivers on these builds since it is more stable then L's anyways
[Nexus 4 Android Development] sykopompos:
BTW, that is the last full builds of the night. Getting late and I'm getting lazy. Anything that comes in the latest test builds of mako or hammerhead will be fixed on github and will be tested when we come back out of the ramdisk tomorrow
[Nexus 4 Android Development] 0.0:
Regarding the Bluetooth redialing bug, I gave up on testing that and accepted it as a bug with the port for mako users. But if you want me to test it again, I can

Sent from my Nexus 4
[Nexus 4 Android Development] ramjet73:
Checked my Nexus 4 when it was connected via USB in the Windows Device Manager's "Android Phone" section and it was showing as "Acer Compatible Device" even though I've never had an Acer manufactured device connected to this computer. :confused:

I wonder if this has anything to do with sharing code between the Nexus 4 and Nexus 7?

Anyway, I deleted the device and checked the option to delete the drivers, then re-installed it with the Google drivers and MTP and ADB are working again.

Strange. :eek:

ramjet73
[Nexus 4 Android Development] sykopompos:
That is actually very odd and even more so because the n7 is an Asus :confused:

Maybe those were just the drivers that windows installed because it is screwy :what::screwy:
[Nexus 4 Android Development] ramjet73:
Yea, could have happened on another test build but since I deleted those drivers hopefully it won't come back again. I'm guessing they would had to have been downloaded from Windows update since I haven't owned an Acer device in ages. I'm pretty sure it said "Acer" but I can't swear that it wasn't "Asus".

I'll certainly let you know if it happens again. :)

ramjet73
[Nexus 4 Android Development] sykopompos:
I don't think I have ever owned or worked on a Acer device in years tbh.

I blame windows for being screwy though
[Nexus 4 Android Development] a g bell:
This has been happening to me for awhile running windows 8 it shows Acer composite device in device manager like you said it will only work with fastboot have rebooted PC without reinstalling drivers and it worked don't get it?and it still says Acer composite device??
[Nexus 4 Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION]

mako-gapp-test-4 - clean flashed - runs nearly perfect!

no issues found - waiting for test test-5 or v6 :):good:

BTW:

- flo-prop-test-1 also clean flashed - also nearly perfect! :good:

- ro.buid.host in flo-prop-test-1 is still different from the other device's builds:confused:

(not att-Shores ???)

thanx mate
[Nexus 4 Android Development] tontolos:
How about Bluetooth??
[Nexus 4 Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION]

did some more tests:

flo-prop-test-1 - unfortunately the camera bug is back "Can't connect to camera"

---------- Post added at 01:28 PM ---------- Previous post was at 01:23 PM ----------

BT works - but tested only file transfer MacbookPro/N4 - vice versa...

---------- Post added at 01:31 PM ---------- Previous post was at 01:28 PM ----------

[MENTION=4756018]manueltts[/MENTION],

did you test the camera with' flo-prop-test1'? - having here the camera bug 'Can't connect to camera'...
[Nexus 4 Android Development] [zozi]:
On beta4 camera is working
[Nexus 4 Android Development] bitstra:
nice shoes:)

beta4 on the flo? :confused:
[Nexus 4 Android Development] [zozi]:
Ehehe its my child shoes :)

No beta4 on mako
[Nexus 4 Android Development] googleygoggles:
noo! Do not buy this!!! I bought one from the same seller for the same price and didn't work at all! Get a different one!!! You have been warned!
[Nexus 4 Android Development] gregbrooker:
Results

Clean flash of test v4

-Camera works fine

-BT turns off/on (don't any devices that use BT really)

-NFC at first was ON by default, when checked to turn off it just faded & no change, if you left NFC settings and came back it would still be ON, rebooted phone and now it works fine,

-FaceUnlock works perfectly, instantly detects and unlocks. Though, when i tried pointing it at random stuff and the first check failed it didnt give the option to use Faceunlock again, but instead to use the code, I dont use it often so not sure if this is how it's supposed to be.

-Firefox crashes but dunno if that's FF's fault

As far as I have tested all works great! very speedy!
[Nexus 4 Android Development] manueltts:
Didn't test the camera before. Your are right, it's broken again.
[Nexus 4 Android Development] ramjet73:
SMH :rolleyes:

Just because it doesn't work for you doesn't mean that it doesn't work.

See attached photo for mine (same adapter from same vendor) in action with my Nexus 4.

You know it needs a good external power source to work properly, right? The cable and adapter that came with the phone should work fine.

Read the eBay reviews if you don't believe me.

ramjet73
[Nexus 4 Android Development] manueltts:
Same seller, same adapter, but mine works on some TVs and doesn't needs the external power source. Sadly it doesn't work on my TV, but it does on my girlfriend's.
[Nexus 4 Android Development] ramjet73:
Interesting...

Even if the power source isn't needed for the HDMI interface to work, it does charge the phone while using the adapter which is pretty important if you are watching a two hour movie. I also think the image may be more stable with external power connected based on my experience with it.

The genuine SlimPort adapter from Analogix Semiconductor is available here but it's quite a bit more expensive.

ramjet73
[Nexus 4 Android Development] sykopompos:
[MENTION=2981094]bitstra[/MENTION] [MENTION=2215798]maune[/MENTION]ltts it carried over to deb too so now we gotta trace down what file it is again since it is probably a new one this time.

Try rolling back bin/sensors.qcom to the 5.9 version like was done on hammerhead for broken sensors
[Nexus 4 Android Development] sidnoit22:
PLEASE [MENTION=275009]ramjet73[/MENTION]
[Nexus 4 Android Development] ramjet73:
LOL!

I guess you flunked the eye test. ;)

Image has been re-sized in the original post.

ramjet73
[Nexus 4 Android Development] bitstra:
trying that in half an hour - some friends are hanging around in my living room - will kick out them :)
[Nexus 4 Android Development] sykopompos:
Everyone is hanging out in the cabin in the woods :eek:
[Nexus 4 Android Development] sykopompos:
I'm getting a case of the lazy and waiting to see if a horror story happens at [MENTION=2981094]bitstra[/MENTION] 's cabin because isn't that how so many horror movies begin
[Nexus 4 Android Development] ph37rd:
Are there sorority girls there?
[Nexus 4 Android Development] sykopompos:
Good point. Most horror movies have them in the cabin too so he might be safe
[Nexus 4 Android Development] ph37rd:
BTW using #4 and haven't come across anything new. Apps seem to all be functional as intended.

---------- Post added at 01:02 PM ---------- Previous post was at 01:01 PM ----------

Or getting lucky, safe is relative.
[Nexus 4 Android Development] sykopompos:
I can always get lucky another day vs getting chased through the woods by some maniac and possibly dying or getting maimed.
[Nexus 4 Android Development] ph37rd:
I thought we were talking about [MENTION=2981094]bitstra[/MENTION]

---------- Post added at 01:10 PM ---------- Previous post was at 01:08 PM ----------

Bake to making some fresh salsa... Picked everything this morning from the garden. It's amazing the difference fresh makes. Having my own supply of tomatillos just adds to the deliciousness.
[Nexus 4 Android Development] sykopompos:
But I like bitstra and do not wish him to be killed or maimed because he is getting lucky with a sorority girl.

BITSTRA, QUICK!!!! TAKE HER TO A HOTEL ROOM INSTEAD!!!!!

YOUR LIFE DEPENDS ON IT!!!!
[Nexus 4 Android Development] sykopompos:
I'm still trying to get motivated enough to get out of bed.

I went and got caffeine and somehow magically I'm back in my bed. It is like a vacuum or something
[Nexus 4 Android Development] bitstra:
He,he:laugh:

- now I lost some of my friends:laugh:

O.K. tried it with sensors.qcom - NU LUCK!

#same error msg 'Can't connect to camera'
[Nexus 4 Android Development] sykopompos:
Wait a minute....

We had it all wrong!!! [MENTION=2981094]bitstra[/MENTION] is the killer!!!!!!

Eh, as long as he doesn't kill me, we can still be buddies
[Nexus 4 Android Development] sykopompos:
Try replacing sensor service also. I think I updated it on the n7, I did with the n4
[Nexus 4 Android Development] justthefacts:
True

That could end up as a horror story too
[Nexus 4 Android Development] sykopompos:
http://en.m.wikipedia.org/wiki/Teeth_(film)
[Nexus 4 Android Development] ramjet73:
It was an updated camera.hammerhead.so in /lib/hw that caused the same problem on the Nexus 5.

ramjet73
[Nexus 4 Android Development] sykopompos:
I remember that one but I'm able to use the updated camera hal on the n4 with no problem so I would assume it would carry over onto the n7
[Nexus 4 Android Development] bitstra:
Nope - with both replaced -> 'Can't connect to camera' :(
[Nexus 4 Android Development] sykopompos:
You can try what [MENTION=275009]ramjet73[/MENTION] suggested with the hal library
[Nexus 4 Android Development] bitstra:
if I replace lib.camera.flo in lib/hw/, then I can start the camera app w/o error msg - but have a green capture screen:confused:
[Nexus 4 Android Development] ramjet73:
Probably more a thriller than horror movie but that reminds of the opening scene from Basic Instinct.

[YOUTUBE]RNPH66tYqrY[/YOUTUBE]

ramjet73
[Nexus 4 Android Development] bitstra:
I meant camera.flo.so...
[Nexus 4 Android Development] ramjet73:
We had that problem on the N5 too but never figured out what was causing it. It had to be one the files [MENTION=1050103]sykopompos[/MENTION] updated to try to get KitKat kernels working with the N5 but when we got several custom L kernels working we dropped that.

ramjet73
[Nexus 4 Android Development] sykopompos:
That is starting to sound like what we ran into with the qmux libs in hammerhead and the custom kernels
[Nexus 4 Android Development] sykopompos:
Working on several devices is seeming to have a payoff across all the devices when something learned on one device translates over.

Maybe we will finally figure that out :eek:
[Nexus 4 Android Development] googleygoggles:
How is it working for you :( :crying:

Also I never said it didn't work completely...

You see on Android 4.2.1 exactly ( what came with phone) the screen flashes for a sec as if it worked... But no picture or audio on either TV's I tried it on no matter what HDMI port I plug the cable into! I even tried different HDMI cables. :confused::confused::confused::confused::confused::confused:... On 4.2.2+ no screen flashing, not even recognized!:banghead::banghead: I can't test it on L since I threw the cable away... I don't know what to do..I seriously am considering a Chromecast now that it has mirroring... Not sure if it will even work so I didn't buy it.
[Nexus 4 Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION],

whats about libcameraservice.so in /system/lib ???
[Nexus 4 Android Development] sykopompos:
I should change the name of bbw when we get there drastically just to mess with people and for the lulz
[Nexus 4 Android Development] sykopompos:
It is possible but probably not
[Nexus 4 Android Development] ramjet73:
Go for the Chromecast, you won't regret it, especially now that it has screen mirroring. It works with many more devices and apps, and even Macs can cast from that version of the Chrome browser. Plus it's cheaper than the official SlimPort device that would give you more compatibility and reliability.

ramjet73
[Nexus 4 Android Development] ph37rd:
I bet that "film" won two handfuls of Oscars
[Nexus 4 Android Development] googleygoggles:
But what about lag? Wouldn't let's say games be too laggy? Let's just say I don't have the BEST wifi in the world... I might buy Chromecast 2 when/if it comes out since I'm saving for a smartwatch :D
[Nexus 4 Android Development] sykopompos:
It was a interesting movie to say the least....
[Nexus 4 Android Development] justthefacts:
You can't just change such a great name without going through the board of directors.

Maybe I should upload some more bbw bunnies. It just might change your mind.
[Nexus 4 Android Development] sykopompos:
So " it was [MENTION=2981094]bitstra[/MENTION] in the cabin with a pair of bear arms" is not a good name for b6????
[Nexus 4 Android Development] ramjet73:
It uses WiFi direct between the phone/tablet and the Chromecast for screen mirroring so it's not even going through your router. But if your Internet connection is slow, regardless of whether that is WiFi or cellular, that is going to make any kind of streaming difficult since Chromecast is still dependent on that.

If the game is installed on your phone/tablet you should be fine. Think of casting as Apple's Airplay for Android if you are familiar with that.

Don't forget the sorority girls. :good:

ramjet73
[Nexus 4 Android Development] googleygoggles:
I didn't even know android supported WIFI Direct! I guess YouTube streaming in HD is out the window..
[Nexus 4 Android Development] hazwheel:
People really still use MMS? [emoji12]

Sent from L
[Nexus 4 Android Development] ramjet73:
I don't unless I'm testing it. ;)

Most of my texting is done in Google Voice and I use other apps for MultiMedia messages.

ramjet73
[Nexus 4 Android Development] hazwheel:
What about the third party Chromecast copies? anyone tried one? Any good? They are half the price although I realise an original is not all that expensive

Sent from L

---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------

Indeed, most people I know use WhatsApp, so I do too, got the wife using it too now

Sent from L
[Nexus 4 Android Development] Zinken:
Clean flash of test 4 with included kernel - only issue so far is that it seems to think I'm charging with USB when I'm using the original charger. Batterystats shows 8h to full with USB :confused:

Newbie question: Is there any way to prevent device id to change every time I flash - hate that banking apps, play music etc. believe that I'm registering a new device every time?
[Nexus 4 Android Development] sykopompos:
I think I need a nap. I didn't get much sleep last night and laying down on either my bed or the couch keeps happening.

Plus it is storming pretty good so I'm waiting for the power to get knocked out and ruin any chances of being productive :(
[Nexus 4 Android Development] ramjet73:
There you go.

+1

ramjet73
[Nexus 4 Android Development] sykopompos:
That's actually much better [MENTION=275009]ramjet73[/MENTION]

People are gonna go who is [MENTION=2981094]bitstra[/MENTION] and what is he doing with bear arms and sorority sisters in a cabin and why is it named that??? :confused:
[Nexus 4 Android Development] sykopompos:
Or is "ilurveyecandy" for googlelygoogles a better name?
[Nexus 4 Android Development] ramjet73:
Not yet.

That can be the name for 7.0 when you customize the hell out of this ROM and it looks like something from the Barnum and Bailey Circus. :eek:

ramjet73
[Nexus 4 Android Development] bitstra:
Tried several lib/hw/modules and libs - no success with camera !

Now I made a logcat right after camera-crash (zip-file attached)

I'm curious about the first 2-3 lines in logcat-snippet:

[COLOR="Red"]E/mm-camera-intf( 194): mm_camera_open: dev name = /dev/video2, cam_idx = 2
E/mm-camera-sensor( 241): module_sensor_start_session:376 session 2
E/rmt_storage( 3019): Unable to change dir[/COLOR]
E/rmt_storage( 3019): Failed in getting the physical address for shared mem
E/mm-camera( 241): is_module_start_session: Enter
E/mm-camera( 241): is_module_start_session: Exit successful
E/mm-camera( 241): is_module_get_port: Exit successful
E/mm-camera( 241): c2d_module_start_session:246, info: starting session 2
E/mm-camera( 241): c2d_thread_func:39: c2d_thread entering the polling loop...
E/mm-camera( 241): c2d_module_start_session:284, info: c2d_thread created.
E/mm-camera( 241): c2d_module_start_session:306, info: session 2 started.
E/mm-camera-img( 241): module_imglib_create_msg_thread:202] E
E/mm-camera-img( 241): module_imglib_create_msg_thread:224] X
E/mm-camera-img( 241): module_imglib_msg_thread:61] abort 0
...
(see attached zip-file...)

no clue:confused:
[Nexus 4 Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION], [MENTION=275009]ramjet73[/MENTION],

I think, the green capture screen, that comes up when camera starts without error msg after injecting the camera.flo.so, is based on an read failure on /dev/video0 /dev/video1 - so the stream of internel usb-cam-device can't be captured!

I remember, that I've got the same behavior, when I've written a small android-app, that captures those /dev/vodeoX-streams for externel USB/OTG camera devices...

So I guess that the basic issue in that case could be a permission problem somehow... (maybe somewhere in the xml stuff???)

[MENTION=1050103]sykopompos[/MENTION] could you think about into this direction?
[Nexus 4 Android Development] googleygoggles:
You mean googLEYgoggles not googLELYgoggles

---------- Post added at 08:54 PM ---------- Previous post was at 08:54 PM ----------

That looks pretty good :D
[Nexus 4 Android Development] sykopompos:
I do and it is a pain in my ass :banghead:
[Nexus 4 Android Development] bongio94:
Can i use any aosp kernel with this L port?
[Nexus 4 Android Development] f4ll3n:
Defconoi kernel works

http://xdaforums.com/nexus-4/orig-development/kernel-ultimate-unleashed-kernel-series-t2845768
[Nexus 4 Android Development] ramjet73:
Only if it uses the anykernel installation method.

Open the kernel zip file, and if contains a "boot.img" file then it won't work.

ramjet73
[Nexus 4 Android Development] sykopompos:
As long as it isn't a full boot image since we are using a custom ramdisk for L, any anykernel kernel should work in theory
[Nexus 4 Android Development] sykopompos:
I'm procrastinating today, don't feel like tracking the n7 camera problem or playing in the ramdisk or selinux yet
[Nexus 4 Android Development] sykopompos:
How is the gallery in test 4 working out? Everything working on it?
[Nexus 4 Android Development] avinab:
[MENTION=1050103]sykopompos[/MENTION] all working fine in gallery .just wanted to know what we will be having in beta 6?
[Nexus 4 Android Development] googleygoggles:
I was going to troll a little in this post but I felt too lazy... I'll edit this later...
[Nexus 4 Android Development] p4rot:
Is the heating problem fixed on this rom?
[Nexus 4 Android Development] sykopompos:
Still working on it. Been working through the n5 all day with [MENTION=3754150]psycho693[/MENTION]
[Nexus 4 Android Development] ramjet73:
USB tethering will work. ;)

ramjet73
[Nexus 4 Android Development] avinab:
[MENTION=275009]ramjet73[/MENTION] ha ha.. Still making fun of it:):):):)..it's ok.all working fine.. Now gapps have been updated.So what new we will be having in beta 6?
[Nexus 4 Android Development] sykopompos:
Beta 6 is just clean up work before we go farther. Get rid of all looping code and errors so it is running 100% efficient as possible
[Nexus 4 Android Development] avinab:
[MENTION=1050103]sykopompos[/MENTION] for immersive mode do we need to edit the frameworks which is not possible now due to its closed source code.
[Nexus 4 Android Development] sykopompos:
Most likely
[Nexus 4 Android Development] criminalzen:
the beta mako gapp test 4 (?)has run fine all day... basically same for me as prop 2 I ran yesterday .. both fluid and snappy, with good battery use over two days..
[Nexus 4 Android Development] sykopompos:
New test build uploading. Psycho tracked down a rogue new preview binary and reverted it so even less looping code. Took what changes I made to the hammerhead sepolicy and carried them over (they were in the main sepolicy and not the device specific things) so it should be quite clean of the base system avc denials (I expect a few still on mako) so overall this test should be nice and clean and if all checks out on it, I will start staging the rest of the things planned for b6.

https://drive.google.com/file/d/0By0vn8iv_zrVMkY5V1hhYWZvOFU/edit?usp=sharing
[Nexus 4 Android Development] CallMeAldy:
Wait.. In progress :silly:
[Nexus 4 Android Development] sykopompos:
it's up now
[Nexus 4 Android Development] sidnoit22:
you dirty boi :fingers-crossed:
[Nexus 4 Android Development] sykopompos:
Maybe that was tmi then, huh
[Nexus 4 Android Development] Tegra 4:
Ok... and i ask now... why googlechrome.apk recognize android JB version and specific 4.3.0???? on other forums on nexus 5 we see chrome recognize something like 4.4.99 or something....hmmmmmm....
[Nexus 4 Android Development] sidnoit22:
Is that one of those screenshot is from KK and one is from L? :/

Btw did you updated Chrome Beta from Play Store?
[Nexus 4 Android Development] sykopompos:
I replaced it with the current beta.

The built on google apps where marked high numbers so they didn't get overwritten with updates in the preview but now the current available google apps are ahead of the preview and will update as intended

The built on chrome was 1985.80 or serving like that
[Nexus 4 Android Development] Tegra 4:
No all is from "android L" i just pull in one of them the status bar to believe me :P yes i do...
[Nexus 4 Android Development] sidnoit22:
Well the battery icons and the whole status bar is changed in one screenshot. Not talking about the notification pull down.
[Nexus 4 Android Development] Tegra 4:
Dude all is from android L i havent 10 phones to play with you :P so what is the problem here?
[Nexus 4 Android Development] sykopompos:
I only have about 6 but 4 are pretty old especially the g1 and cliq.

Speaking of, I'm gonna go try to get L on the g1 now
[Nexus 4 Android Development] Tegra 4:
I have 4 LG

LG Optimus 4X

LG G2

LG G3

LG Nexus 4

i LOVE LG <3 :P
[Nexus 4 Android Development] sykopompos:
And yet you are missing the n5 :(

I has the g3 also though, too bad I can't get L on it because of the stupid display drivers