yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Thanks mate ! Flashing the userdata.img wasn't a good idea btw, lol, I ended up with 32 gb size on my 64 gb phone ;) "fastboot format userdata" fixed that though ;)

Will try with gapps, would love to see the permission commits indeed.

Man, one would think that building an AOSP rom on Nexus would be a bit more straightforward eh. Building CM is easier :D
[Nexus 6P Q&A, Help & Troubleshooting] rustyjay:
https://github.com/zephiK/android_f...d/server/pm/DefaultPermissionGrantPolicy.java

Just use all these commits for permission. Also in aosp google account backup doesn't work out of the box that's another commit you'll need. Aosp isn't like cm where its all done for you. Its very stripped down and you'll even notice that some if the icons are old. But that's what also makes it so great, you mold it into what you want.
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
So I think I've figured out what my problem is. It seems you get that "There’s an internal problem with your device" if the 3 values in /vendor/build.prop dont match with /system/build.prop, as explained here: http://xdaforums.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347

then I realized that I built my ROM as 'userdebug', while vendor is 'user', so going to build the rom now as 'user' too and see if that helps, I think it will :)

*EDIT* So what I just did is just copy the build.fingerprint from /system/build.prop to the one in /vendor/build.prop and that at least fixed that damn error message ;) And you dont have to change all 3 properties in /vendor/build.prop, only the fingerprint needs to match.

Still my RIL is down but I think that's because I need to build the rom as user, trying that now ...

---------- Post added at 01:41 AM ---------- Previous post was at 01:06 AM ----------

Ok the reason my RIL is down is indeed that symlinking: somehow it doesnt link /vendor to /system/vendor which causes:

dlopen failed: dlopen failed: library "/system/vendor/lib64/libril-qc-qmi-1.so" not found

I find that very weird though, why is that not working ? Going to investigate that, I want to get to the bottom of this :)
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Ok, I think this is the missing key here: https://github.com/PureNexus/androi...mmit/a826b2af82e4d1f2b8fb7a969338b8aa0b4206aa

Building again with this, will try tomorrow, I have hope this will fix the problems :)
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
just tried it, still doesnt link /vendor to /system/vendor ...

Going to investigate this some more later today

*EDIT* Hmm actually the above seems a CM thing. But I think we might need it too. These are 2 patches that seem to use the flag:

https://github.com/BenzoRom/build/commit/a736f7ec279d40956e4c6e7b18e915ee8fd4d47f

https://github.com/BenzoRom/build/commit/c910210582aedad000c3f947a68d93c300f488f1

Although hmm looking at those patches, I doubt this is it, they just seem to make symlinking conditional (instead of forced). Damn, why is this not working ...

I'll need to research how this symlinking actually works in the factory build, will look into that today.
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Hmm so this is a bit of a mystery. I boot with the same kernel, so it doesnt seem to be the kernel that does the symbollinking. Then, I tried to deleted both 'mount' and 'ln' from the /bin dir. I checked, commands then failed. So I rebooted and guess what, it was still symbollinked.

So not sure what's going on here. But I'm now thinking to just do the same thing as you did and just copy /vendor into the /system dir manually.

---------- Post added at 01:06 AM ---------- Previous post was at 12:09 AM ----------

So, I saw that quite a few files from /system/bin were missing so I copied the missing files to my own ROM. Then I extracted the vendor partition and added it to /system/vendor. However RIL is still not up. Not sure if you had the same problem or if your RIL worked right away ?
[Nexus 6P Q&A, Help & Troubleshooting] rustyjay:
Ahhh know you say that yes I did, hold on driving.

https://github.com/Slayjay78/android_build/commit/f1216b46ec7091e02c2d455dd7643bd78b27ed56

https://github.com/Slayjay78/device_angler/commit/7d78f76871545a81a21eab685ac19b5ebe596b0d

https://github.com/Slayjay78/device_angler/commit/a33d8cfab633d41c56fde43139d3ca119f771a5d

Try those

You'll get faster replies if you hit me up on hangouts, let me know if you want me email.
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Thanks mate !! That solved the vendor symbollinking ! /vendor is now linked to /system/vendor, nice ! Still no RIL though, will investigate tomorrow
[Nexus 6P Q&A, Help & Troubleshooting] zelendel:
There are some things that need to be fixed. Mostly due to some closed sourced files that need to be fixed. It is not as simple as sync and build
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Hey ! Yeah actually I'm a bit surprised there, I thought that the whole idea of a Nexus device was that you could just build of google's repo and run it ! Not sure why Google puts a tutorial out there when the resulting image doesnt even yield a working RIL.

Anyway, what binaries need fixing and how to fix them, care to elaborate ? I kinda hate re-inventing the wheel so any help would be greatly appreciated ! I'm a bit surprised anyway that there wasn't a thread or tutorial on XDA on how to build Angler, so I think it would be nice to have all info in one single thread here to help jumpstart anybody who likes to contribute something to xda.
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Anyway, I figured I'll start myself anyway to try to get RIL up.

So just looked at the logs, I'd say this seems to be an interesting difference here. Stock does:

Where my cooked up version does:

No mention of that Qualcomm ril connecting. So what's happening here is that RIL.java connects to the ril daemon and it seems to do that succesfully in both cases (that 'Connected to rild socket' log is coming from RIL.java on connection). Yet then, why doesnt my cooked up version print that Qualcomm info ? So I just loaded up RIL in IDA pro and started reverse engineering it, to see what's happening here. So first thing I checked is to see if there's some kind of conditional logging, a log level maybe. That's not the case it seems, yet there is some kind of conditional check just before printing that string. So next up: figuring out what that condition exactly is ...

*EDIT* LOOOL what am I even doing reverse engineering, ril.cpp is included in the repo ;) hardware/ril/libril/ril.cpp ;) I should let go of the Samsung mindset I guess ;)
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Ok, so ril.cpp, in my cooked up version, *does* set the socket listener, like:

ril_event_set (socket_listen_p->listen_event, fdListen, false,
listenCallback, socket_listen_p);

Yet it never hits the callback. So next question is: why is that, need to look into that.

*EDIT* so, RIL.java does say it's connected, however RIL.cpp doesnt hit the callback. That's interesting, the socket is connected, why isnt it hitting the callback then ... Need to research into that event ...
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
LOL and I thought that Samsung was a mess, Google is arguably even more messy: WTF is the use of a /vendor partition if you dont put ALL the blobs in it ? Damnit Google. Anyway so it turns out that they also have blobs in the /system/lib64 dir which need to be copied, like the GPS blobs (libloc_*, libgps.utils.so etc). Also there are quite a few blobs in /system/bin that need to be copied otherwise important services like qmuxd wont even start. I did that yesterday but found out today that they didnt execute because of SElinux kicking in. Flashed a permissive kernel, copied those blobs and the log is starting to look better now, but still no RIL, I must still have missed something I guess. Will look into it tomorrow again.
[Nexus 6P Q&A, Help & Troubleshooting] zelendel:
Normally they are but the 64 bit set and the oem have made it a bit harder. With say the n6 you could sync and add the proprietary parts and build.
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
So our friends at CM made a nice repo of the needed blobs, BEYOND the vendor blob partition:

https://github.com/TheMuppets/proprietary_vendor_huawei/tree/cm-13.0/angler

Haven't tried it yet but I'd say that with those blobs RIL and GPS will work correctly. Will try later today.
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
And indeed, that fixed the problems : ) I've got working RIL and GPS now :) In fact *everything* seems to work, even fingerprint ! YIIHAAAA :)

You can just look at the blobs CM used, like I showed in my previous post or just flash them directly with the zip I created:

https://mega.nz/#!iMwhgS5L!XwZoIFQ-ceL8fE221K7IK1N9fBQACQjGk6Z7tfI2cQA

So, simply build AOSP like explained before and flash these blobs. Oh and you'll probably need a Selinux permissive kernel (or fix up the missing permissions for those blobs) and then it should work.

Thanks again [MENTION=4711514] rustyjay[/MENTION] for the toolchain info he supplied earlier in this thread and the patches to link the vendor partition and the gapps permissions !

So I guess that's all there is to building and running AOSP, all needed info to build the kernel and the system gathered for you in 1 thread. Always happy to add some value to XDA, enjoy folks !!
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Something I'd like to add to this thread: To install the gapps correctly, do a factory reset after the gapps. Then if you still get FC's, follow this guide: http://www.ibtimes.co.uk/android-6-...oogle-play-services-force-close-error-1524431

Works perfectly for me, everything sailing smooth now on my home cooked ROM :)
[Nexus 6P Q&A, Help & Troubleshooting] flex360:
this is an awesome thread

i am learning alot

thanks for being verbose
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Thanks ! One thing I need to add: after flashing my blobs like explained, you need to chmod the /system/bin directory files to 777. Then everything should work.

Anyway been modding, building and flashing quite a bit the last few days, great fun. But 2 things I'm currently facing:

* Build process sometimes breaks with a GC out of memory error and the suggestion to increase the java heap size. However I've been googling but couldnt find *where* to increase the heap size. Probably a build script that you'll need to add an option to, but not sure which one. Maybe someone here knows ?

* Sometimes I want to just compile services.odex in the framework. So, I go to the the dir of the services, containing the android.mk, I issue "mmm ." and it builds services.odex, so far so good. However when I copy both services.jar and services.odex onto my device, it wont boot. So, in short: I flashed the whole system.img before, then modded services, pushed those 2 files and then it should work IMHO but it doesnt. Logcat error is something about a missing class in services.jar I think I remember. Maybe anyone knows how to solve that ? [MENTION=4711514]rustyjay[/MENTION] maybe ? And also, is there an easy way to push the resulting modification onto the device (instead of manually pushing services.odex and services.jar) ? On cyanogenmod one would simpy issue "mmp" but that doesnt work on AOSP it seems.

Thanks !
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
Hmm not sure why but this thread doesn't seem very popular. I figured a lot of people on the 6p would be interested in building. That's why I got a 6p in the first place, ultimate freedom to change the ROM in anyway you like :) But oh well, I'll just update this thread with info myself then, as I find answers to my questions, so people who are interested in building at a later time can just read this thread and it will contain all the info they need.

So, I just found an answer to that question of building just a module ! I found this great blog which contains the solution: http://blog.udinic.com/2014/07/24/aosp-part-3-developing-efficiently

Supposedly with 'adb sync' you can push the changed module to the device ! Haven't tried it self but I'm confident it works. He even makes his own 'mmp' script based on this command ! Quite nice indeed and a huge time saver comparing to having to build the whole ROM time after time !
[Nexus 6P Q&A, Help & Troubleshooting] zelendel:
The main thing is that most really dont bother building anymore. Most people here are what some would call leeches. They just come and download. The mojority of others just use someone elses sources like CM, Slim, AICO or DU. Those all you pretty much have to do is sync and build.

Dont get me wrong. We need more of these types of posts.
[Nexus 6P Q&A, Help & Troubleshooting] gekkehenkie11:
You're probably right. Anyway I just tested the building of 1 module and it worked ! So what I did, was just, change the module sourcecode you want, go to the frameworks dir and then into the module dir you want to push, containing the android.mk (in my case frameworks/base/core/res), then build and push it with:

adb remount

mm

adb sync

adb shell stop

adb shell start

which will build the module, push it onto your phone and restart the shell, so you have a change up and running in about 1 minute, that's really awesome !
[Nexus 6P Q&A, Help & Troubleshooting] xyge:
cant get ril to work

-built using the sources(no changes)

-flashed the zip

-flashed gapps

-flashed vendor.img(from the latest factory image)

-flashed the vendor build.prop fix

-flashed a permissive kernel and supersu

phone booted up but no sim detection or fingerprint

-did a factory reset

-flashed the cm blobs u linked

-set chmod 777 to /system/bin

phone boots but no change

-factory reset

still no change
[Nexus 6P Q&A, Help & Troubleshooting] andrewnelson23:
Hey! I'm attempting my own build. Slightly confused by this thread though, there seems to be a lot of info scattered across several pages.

I currently have the build environment set up on my VM and the aosp repo sync'd. What other sources do I need to sync to build? Do I need to grab vendor source from the muppets and put it in a local_manifest?

If so, how do I link it to build with the ROM? Or do I? Are there any changes I need to make before building? Which build command do y'all prefer? There's only one main reason I want to do this; I want to remove hotspot restrictions(I might also implement a center clock for myself haha).
[Nexus 6P Q&A, Help & Troubleshooting] andrewnelson23:
Not sure if anyone even looks at this page anymore. with the help of rustyjay, I was able to build aosp for n6p!

Everything that I tested is working (ril, fingerprint, camera, wifi, hotspot, etc. etc.) I came back to pure nexus because for some reason I was unable to set google now launcher as my default home launcher. I'm guessing that if I installed it as a system app it would probably work, but I didn't test root either.

Will look into fixing that. It's so cool! I'm a very minimal person, so I'll probably just add a few changes as I get better at this (option for center clock, battery bar, expanded reboot menu).

if anyone needs or wants any help getting started, just ask! I can't promise that I'll be of any help, but I can try. :)
[Nexus 6P Q&A, Help & Troubleshooting] gubacsek:
Hi! I'm trying to build my own rom for my 6p, and I see some blobs in a git repo in this thread. I just don't know where to sync that. To which folder in the AOSP source tree ?

Can you please help me with that?

Thanks !
[Nexus 6P General] EVOme:
Every time I pick this phone up I am changing the volume....annoying!
[Nexus 6P General] pdtp:
Was having the same issue, ended up getting this case, http://www.amazon.com/gp/product/B015X90UJS not a problem anymore!
[Nexus 6P General] Despiadado1:
Got a case and that was the primary reason i did. the button placement logic... "put the buttons where you can easily reach them". I dont want to easily reach buttons that I dont use. Come on guys, right in the middle? Just a terrible decision.
[Nexus 6P General] dsmpampis:
Me too! But I think after a while you get used to it!
[Nexus 6P General] EVOme:
I ordered skins for it before I got it. Now I feel like I need a case due to this. I just ordered this. When I skins get here I may end up with both.

http://www.amazon.com/gp/product/B0168DHS1Q?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00
[Nexus 6P General] coolcat67:
Volume buttons should have been on opposite side from power button and not placed in the middle of the phone. Like the Nexus 5... Oh well..
[Nexus 6P General] galaxys:
Also use a case to eliminate accidentally pushing buttons.
[Nexus 6P General] DJ Sandman:
If you don't mind finger print smudges, the Spigen thin fit case has good separation between the keys and has decent grip without the bulk.
[Nexus 6P General] PieOfJustice:
Your left handed aren't you?
[Nexus 6P General] gahsan:
This is one of the biggest gripes I have with 6p. Just a bad usability flaw. That and the fact that the power button virtually has no resistance to it so it's easily pressed when you hit even a tiny piece of it. Any decent case with button covers fixes this, but it also increases the size of the phone.
[Nexus 6P General] [hfm]:
I agree with this but it's rare enough that I deal with it. I did almost think my phone was randomly rebooting until I realized the power button was getting held down at rare times in my pocket if the angle was just right

Sent from a 128th Legion Stormtrooper 6P
[Nexus 6P General] Soulfly3:
just got mine in the mail this morning.

it was literally MADE for this phone... it makes the device feel like it should. loving it
[Nexus 6P General] wwevoxnj:
As a lefty I feel like the button placement is great! I never inadvertantly hit the power or volume buttons
[Nexus 6P General] EVOme:
No... I'm right.
[Nexus 6P General] PieOfJustice:
Sorry meant to say right.
[Nexus 6P General] dastinger:
No, you're wrong.

Sorry -_-
[Nexus 6P General] otariq:
I am and it's actually perfect for me lol. My palm rests along the left side of the phone and my finger is on the back and the rest sit right below volume down. Best phone ever lol
[Nexus 6P General] tkoreaper:
Can't remember the last time I used the power button except to turn off the device. I always turn it on via the fingerprint reader.
[Nexus 6P General] MalekoUK:
Also annoying placement when using a car holder....
[Nexus 6P General] keljai:
I am using the verus case. Helps alot to avoid miss click. If anyone is interested in the case, I have attached a link

http://www.amazon.com/Verus-Carrying-Case-Huawei-Nexus/dp/B015GHQGM2
[Nexus 6P General] dramake:
Since I got the phone (I've had it only for 3 days) I never had that problem.

I didn't think of that. This could be more troublesome indeed.
[Nexus 6P General] Baldilocks:
I'm using the Unicorn Beetle case. Great protection and the keys are a lot harder to push in. Screen shots work just fine too.
[Nexus 6P General] Neurom707:
I keep pressing the buttons two but its just getting used to where they are on a new device although I don't understand why there half way down instead of on the top half
[Nexus 6P General] EVOme:
Even talking on it my thumb wants to rest on the volume up button. Terrible design.
[Nexus 6P General] ddaub14:
People always find something to complain about smh its call adapt or return it.
[Nexus 6P General] EVOme:
Dude it's a legitimate complaint... What phone has the buttons in the middle?
[Nexus 6P General] wind784:
N6?
[Nexus 6P General] ddaub14:
Ahh well a phone that makes it easy to access all the buttons with your thumb without moving your hole hand to get to the buttons...
[Nexus 6P General] gahsan:
Did you ever hear about constructive criticism? I'm keeping my phone because, obviously, the positives over weighs the negatives. But, these are valid points about design shortcomings.
[Nexus 6P General] ReaperNY:
The only thing I don't like about the button placement is when I try to using most mounts like a car mount or controller mount. I have to mount the phone off center otherwise it will press onto the buttons.
[Nexus 6P General] Breezer23:
Not sure how this phone made it to production with this button placement. It's as if no one ever held the phone. Case certainly helps. Probably worth having a case on anyway given how slippery the phone is anyway!
[Nexus 6P General] MalekoUK:
They only had to move the buttons an inch up and would be fine. However, I don't accidentally press them, just a pain for the car holder for me.
[Nexus 6P General] EVOme:
I've had all intentions of running naked to show its beauty, but I caved and ordered a clear case.
[Nexus 6P General] kravguy:
Only gripe I have with this phone is the buttons. Coming from an m9, this is the second phone I've had with the power and volume buttons were on the same side. Being in the center definitely causes issues with most generic car mounts. My biggest issue is hitting the power button when putting the phone in my belt holster or the power button being pressed while in the holster causing either a reboot or worse, pulling it out and it sitting in recovery. It's only a matter of time before I pull it out and it's been wiped.

Other than that though, best android phone I've owned, this being my 8th. It really is close to perfect.
[Nexus 6P General] tkoreaper:
What's funny is if the buttons were placed anywhere else they'd complain about how they're too hard to reach and/or not ergonomic.
[Nexus 6P General] RogerPodacter:
I lucked out at frys and found a car mount cd slot. Forget the brand but it was 15 dollars. Any mount for an iPhone 6 plus will work and not hit the buttons.
[Nexus 6P General] WizeGuyDezignz:
But there are other phones available to choose from, no?
[Nexus 6P General] tpboi:
same problem, bought a case to fix it.
[Nexus 6P General] Clark Joseph Kent:
Thread Cleaned and addressed....
[P3300, MDA Compact III General] faun77:
Help me run DosBox emulator on Artemis. :(

I have Windows Mobile 5.0 (5.1.465) and I can't run DosBox.

I download emulator and install.

When I run program, my Task Bar make black color.

I can't see cmd, and I must reset my HTC for work.

Thanks

Tom