yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] sykopompos:
Did you get the n6 fixes yesterday for play movies, screencasting and Netflix?
[Nexus 7 (2013) Android Development] Scott:
No, can you link them?
[Nexus 7 (2013) Android Development] sykopompos:
The fix for screen casting, Netflix and google play movies

https://github.com/Ayysir/android_build/commit/50fc20a72717b924243d03e9741826486e4af39f

Thank beanstown for figuring out exactly what was needed and you might want to search the aosp gerrit for rro and cherry pick the commits from Sony there that were merged (5 from November) to fix rro so you can play with my project

https://plus.google.com/118195502410326243266/posts/JPdEBJdrKdF which is like cm's theme engine but a lot lighter and simplier (more commits coming to expose resources to be themed)
[Nexus 7 (2013) Android Development] Scott:
Very cool!

I just implemented the first commit. Building now! :fingers-crossed:
[Nexus 7 (2013) Android Development] sykopompos:
I posted in your n6 thread, why didn't you tell me you had audio and YouTube issues, I could have given you the fixes weeks ago lol
[Nexus 7 (2013) Android Development] Scott:
I was determined to find them on my own, lol. But there were some political reasons, where as I was pissed off at someone and sort of abandon the ROM... But then realized that was lame and just got back to it, lol
[Nexus 7 (2013) Android Development] sykopompos:
Hey I understand. I knew about missing libs from other devices so I knew they were missing from the n6.

Don't abandoned your ROM though, keep doing it as a learning experience
[Nexus 7 (2013) Android Development] Scott:
Your right. Like I said I realized it was lame.

Now check this out... The DRM fix... Fixes Youtube! The extra lib is not needed.
[Nexus 7 (2013) Android Development] sykopompos:
Hmmmm, that is interesting. You still need the audio stuff though otherwise you get low volume.

Speaking of Roms though, I might drop mine when 5.1 comes out so I can concentrate on other development
[Nexus 7 (2013) Android Development] Scott:
Right... Now to be clear I am speaking of Shamu, not Flo...

Check out the installed files from "out" folder...

https://dl.dropboxusercontent.com/u/31360541/XDA/installed-files.txt

Now on to fixing the Audio issue... That will be another day though... Its already 1:30amCST here
[Nexus 7 (2013) Android Development] sykopompos:
I would probably still add it, it is a stock file and it is for memory allocation so the implications could be seen elsewhere down the line
[Nexus 7 (2013) Android Development] Scott:
No dude, look at line 795 in the installed-files.txt file from the out folder. Its there by default on Shamu. I did not manually add it.

But once I made the DRM fixes youtube started working.

On your ROM is it missing by default?
[Nexus 7 (2013) Android Development] Scott:
Oh, and sorry to bug...

Could you link me to your Shamu auido fix. I cant find the link.
[Nexus 7 (2013) Android Development] sykopompos:
The blobs were missing it as far as I know but maybe that was just the 5.0 blobs and it made it's way into the 5.0.1 ones
[Nexus 7 (2013) Android Development] Scott:
Ahhh, very true!
[Nexus 7 (2013) Android Development] mjb152:
I'm using lrx22g (deb), but getting bad stuttering through Bluetooth playback. Think I've tried 3 or 4 of these builds, but this is the first time I've had Bluetooth issues, is there a fix for that ?

And many thanks for this, these builds are excellent
[Nexus 7 (2013) Android Development] GROGG88:
I've had bluetooth issues on hammerhead and flo ever since moving up from 4.4.4. Intermittent stutter on occasion. This occurred even on factory releases for me. I have not looked into it yet, but I am aware of it.
[Nexus 7 (2013) Android Development] mjb152:
Thanks for the fast response, I've got multirom and stock 4.4.2 installed as well, so I'll boot that when I need to.

Thanks again for sharing these builds, superb work.
[Nexus 7 (2013) Android Development] nottoosmart:
Just got everything to build and got it all set for the Nexus 6. But Im stuck at the Google loading screen with the unlocked padlock on it. then it sits there and never loads. Think its the kernel but not sure.
[Nexus 7 (2013) Android Development] drewski_1:
have you tried an ADB LogCat to get more detail on what's going on?
[Nexus 7 (2013) Android Development] nottoosmart:
can you do a logcat while its trying to boot?
[Nexus 7 (2013) Android Development] Scott:
THis happens to me all the time on a fresh repo... I forget the vendor blobs.

Did you download and install the 3 blob files?
[Nexus 7 (2013) Android Development] nottoosmart:
If you talking about the drivers, yes I did.
[Nexus 7 (2013) Android Development] Scott:
These? https://developers.google.com/android/nexus/drivers

The only time I had what you had is when I jacked up the files. Maybe re-download to make sure you have good copies then make sure you actually decompress each one because sometimes I type "i accept" instead of "I ACCEPT" and it just closes with out decompressing...
[Nexus 7 (2013) Android Development] nottoosmart:
OK I'll do it again. I am making brand new repo with only change being the apns file.
[Nexus 7 (2013) Android Development] Scott:
Good luck and let us know how it turns out! :highfive:
[Nexus 7 (2013) Android Development] nottoosmart:
Its working now. Its interesting. I guess my blobs needed to be added after sync rather than during
[Nexus 7 (2013) Android Development] Scott:
Yes... After! glad you got it going!!!
[Nexus 7 (2013) Android Development] nottoosmart:
Its working amazingly. I just wish I could get the screen recorder working. Its funny, never needed it before and now that its there I want it to work lol. Thanks guys for your help. Im still messing with it though.
[Nexus 7 (2013) Android Development] iwebsource:
I implemented the changes from the following https://github.com/Ayysir/android_build/commit/50fc20a72717b924243d03e9741826486e4af39f

Compiled for Flo but Netflix is still giving me the error that the Time / Date is not not working (-3).

Does anyone else have issues with netflix for flo on custom AOSP?
[Nexus 7 (2013) Android Development] GROGG88:
That commit is targeting shamu not flo. DRM for flo is fixed in vendor by adding missing blobs.

No problems here.

You can use my vendor repo, but it's modified to include bootanimation, adaway, and a fstrim init.d script:

https://github.com/grogg/platform_vendor
[Nexus 7 (2013) Android Development] iwebsource:
Awww. That makes more sense.

Anyways this is what I have in my "device-partial.mk" file for flo:

I'm pretty sure that is correct here as I have the "vendor/asus/flo/proprietary/libdrmwvmplugin.so:system/vendor/lib/drm/libdrmwvmplugin.so:asus"?

Or am I missing something else?
[Nexus 7 (2013) Android Development] GROGG88:
Looks like you're using my vendor tree. That should include everything. Excuse me for covering basics...

- Clean install?

- What gapps?
[Nexus 7 (2013) Android Development] iwebsource:
Correct, I'm using yours as a baseline to start.

Yes, Clean install, usually wipe system, data, and caches before installed a new build.

Gapps I'm using in my latest build is Banks; gapps-L-minimal-signed-1-19-15.zip

Though, if you have it working correctly, then the only thing I can think of which is causing this issue for me is that I'm using unblock-us.com service. (To get American Netflix and Hulu)

I will do some testing around that.

Thanks man
[Nexus 7 (2013) Android Development] GROGG88:
Ah, yes that may be the missing variable... Is that required for Canuck-a-nucks? :p
[Nexus 7 (2013) Android Development] iwebsource:
Heh. Ya, unfortunately as you probably already know, the American Netflix has a ton more movies and TV series. Plus Hulu is only available in the US.

All other computers, roku and media server have no issues with this but I'm quite sure now it has something to do with the unblock-us services.
[Nexus 7 (2013) Android Development] GROGG88:
I actually was unaware. I used to spend a bunch of time up in Ontario, but that was more than a decade ago before I moved to the SW.
[Nexus 7 (2013) Android Development] portezbie:
Thanks! That seemed to fix the issue.
[Nexus 7 (2013) Android Development] exgenmeikoj:
moding system files

hello, so i am wondering can i modify smali code and then sign with test keys? .

basically what i am asking is i want to port some features from different os types. and i was modding services.jar which compiled and booted but then gave force closing afterwards. the reason i am disabling signature check in services.jar is cause i only know how to deal with smali code porting and not source code. " which i am downloading right now as we speak."

im not new to porting as i have done many mods for sgh-t599n aka samsung exhibit.,

color ink effect.,toggle porting and even made a stock based rom. this was all samsung. this is the first stock android device i owned and its a mess to get working. which each had its faults lol. just a nudge in the right direction would be helpful :D:D:D:D:D
[Nexus 7 (2013) Android Development] portezbie:
I had a little confusion with this as have some others, so I wrote some excessively explicit instructions in case it helps anyone:

1. Download Terminal for Android: https://play.google.com/store/apps/d...roidterm&hl=en

2. You must have super user installed and be rooted.

3. Open Terminal and type "su" (without the quotation marks) and press enter.

4. Super user should pop up and ask you to grant permission. Do it. the screen should now have a new line that says "root@flo:/ #

5. Type "restorecon -FR /data/media/0" (without quotation marks, make sure you get all spaces) and hit enter. Give it a few seconds to run.

6. Your internal storage should now be accessible. It is in a slightly different place now though. Instead of just sdcard, it is in sdcard/0.
[Nexus 7 (2013) Android Development] GROGG88:
I've always transfered the original signatures for system apk and jar files. I'm no expert with smali though...
[Nexus 7 (2013) Android Development] exgenmeikoj:
That's what I've been trying to do but its not working as when I try to edit services.jar it doesn't load and I guess it just force closes all of them because when I tried to do it it boots up but then every application force closes and it keeps force closing afterwards I have used it before to edit small files during pior editing Android manifest XML doesn't actually allow that i must sign the apk the only thing I got is test keys so that's why I have downloaded the source code for 5.0.2 so I can use debug keys. So hopefully it will work this time. My main thing is porting inkeffect and a decent toggle set for our device and maybe some native gnome. Im trying to get a log cat to see what happens
[Nexus 7 (2013) Android Development] Scott:
This is not a smali editing thread... Its about building from source but I will give you some help...

I need you to do one thing, can you look in android.policy.jar and tell me if there is a classes.dex in there? If not then the entire ROM is not de-odex. Other issue could be your smali tools are out of date.
[Nexus 7 (2013) Android Development] exgenmeikoj:
if this isnt deodexed then your rom 4.4.4 isnt all the way deodexed

Well sir I thank you for the help. ive checked and yes there is a class dex inside android.policy.jar To disable signature check so I can sign android_manifest.XML so I can write different system ui things. This isn't a smali thread but its for this device using this exact os I'm using up to date tools. Thank you again and I'll take my issues else where so to be a bother
[Nexus 7 (2013) Android Development] htb2050:
Abyssplug V2

I am using abyssplug governer on my galaxy s5 and I would like to give it a try on my nexus 7 too but I have looked everywhere and I can't seem to find it. If anyone can link me to that then I would really really appreciate that.:confused:
[Nexus 7 (2013) Android Development] mjb152:
Does this ROM have USB otg built in? Or do we need an app ?
[Nexus 7 (2013) Android Development] GROGG88:
Aosp has USB otg, but mass storage is not included. My builds have fat32 included, but not NTFS, exfat, or ext4.
[Nexus 7 (2013) Android Development] mjb152:
so a fat32 usb stick should show up ? would it automatically mount if so ? I checked and can't seem to find the mount point. I can see under storage that it sees a stick, but it's kind of greyed out, I thought it might magically mount itself ?
[Nexus 7 (2013) Android Development] GROGG88:
Yes. It will mount itself at /storage/usbdisk. I use it all the time.
[Nexus 7 (2013) Android Development] mjb152:
strange, rebooted and all is well. :) thx probably going mad, was sure it wasn't working before.
[Nexus 7 (2013) Android Development] mjb152:
Is there a max capacity for USB sticks with fat32? It turns out that it can't read a 128gb fat32 stick, but it can read a 64gb stick.
[Nexus 7 (2013) Android Development] GROGG88:
I suppose there may be. I cannot confirm since mine are all 32gb.
[Nexus 7 (2013) Android Development] GROGG88:
To Everyone:

Anyone who has watched my git may have noticed this:

https://github.com/grogg/platform_vendor/commit/2472d81e2f9280313e0efc255b445e9d01acdc47

This means that my builds are no longer public. I have made a couple updates to source since the last release update. I will continue to post builds on AFH, but I will no longer be announcing new builds or providing links to them. This is something that I wanted to add very early on and resisted the urge, but I decided to move forward with the change a few days ago.

My source can still be used by others looking to build their own firmware, or looking to learn how (which is the primary purpose of this thread). I strongly encourage others to continue experimenting and learning. The beauty of AOSP is we can make it how WE EACH would like it. That is the soul of XDA and is what separates this forum from many others. That is why it is called XDA"Developers" and not XDA"Users".

This is one of the few TRULY USEFUL threads... So keep building, keep sharing, and keep asking questions along the way!
[Nexus 7 (2013) Android Development] alphahere:
Now the factory images are out is it okay to use the latest firmware for deb?

Thanks
[Nexus 7 (2013) Android Development] GROGG88:
I saw today those images were released. That means that binaries can be updated for aosp. I'm not sure exactly what it is you're asking though...

Are you questioning the use of deb binaries or whether its OK to update radio, bootloader, etc...?

Without knowing your answer I can only say that it is recommended to flash the 5.0.2 factory image before running any custom 5.0.x firmware.
[Nexus 7 (2013) Android Development] alphahere:
Sorry my question was not clear. I meant is it okay to use the latest firmware with your rom? I would assume the answer would be yes. I can flash only the radio and bootloader. Don't think I need to flash the entire rom and install a custom rom.

Thanks.
[Nexus 7 (2013) Android Development] GROGG88:
Flashing everything guarantees a clean 5.0.x slate. Others have reported misc issues when piecemeal was performed.
[Nexus 7 (2013) Android Development] alphahere:
I see. Thanks for the advice.
[Nexus 7 (2013) Android Development] GROGG88:
After further consideration I have decided that as a third party provider I am able to publicly release my builds despite the inclusion of google's apps. With that being said...

UPDATE IS AVAILABLE

**Changelog**

01/31/15

aosp terminal included in build

default wallpaper changed

deb binaries updated

minimal gapps included in build

If anyone objects then please refer to the following:
[Nexus 7 (2013) Android Development] |Logic|:
If we want full gapps can we just flash your gapps from before? Or would that not really do anything?
[Nexus 7 (2013) Android Development] Scott:
If they object tell them to talk to me first ;)

Great job BTW!
[Nexus 7 (2013) Android Development] GROGG88:
I've included the basics. Anything else can be installed through play store.
[Nexus 7 (2013) Android Development] pietropizzi:
Thanks for your latest built.

I flashed it but Calendar sync doesn't work. There is no Sync option in the Google-Accounts and Google Caleandar stays empty.

I flashed your latest gapps from previous release on top of it and calendar sync started to work properly.

Maybe something's missing in the included minimal gapps ?
[Nexus 7 (2013) Android Development] GROGG88:
Try clearing data on googlecalendar and on googlecalendarsyncadapter and reboot.

Working fine for me on clean install.
[Nexus 7 (2013) Android Development] pietropizzi:
OK, I'll try clearing googlecalendarsyncadapter next time, too (I cleared only googlecalendar).

I already got it working with your 01/17 gapps-package flashed on top, so I'll do that with your next release :)

Thank you !
[Nexus 7 (2013) Android Development] GROGG88:
UPDATE IS AVAILABLE

**Changelog**

02/04/15

cmfilemanager removed (available separately)

documentsui is now a standalone file manager

musicfx is now a standalone app

adaway modified to include xxxhdpi launcher icon
[Nexus 7 (2013) Android Development] tibere86:
Thank you for the great guide. One question, do I need to run the "make clean" command on subsequent builds before using "make -jX otapackage" command or there's no need to?
[Nexus 7 (2013) Android Development] joopsx:
Hi

I still like to stuck with 4.4.4, can you help let me know this ROM link is whether DEB or FLO?

http://www.scottsroms.com/downloads.php?do=file&id=564
[Nexus 7 (2013) Android Development] Scott:
No. Not really. Unless you changed someting in Vendor folder or other binary files. Otherwise you should be fine.

Sorry for the slow response.

Its KitKat 4.4.4 :good:
[Nexus 7 (2013) Android Development] joopsx:
Yes, it is KK 4.4.4, but it is for DEB/ Nexus 7 2013 LTE , or FLO/ Wifi version?

http://www.scottsroms.com/downloads.php?do=file&id=564
[Nexus 7 (2013) Android Development] Scott:
Flo
[Nexus 7 (2013) Android Development] alfick3:
[MENTION=426561]scrosler[/MENTION], so after I do this:

make -j8 otapackage

It just sits with the > prompt and a blinking curser. Is there anything I need to do from here? Or is it building and I need to let it sit?

Thanks,

Alfred

Edit: oh, is your avatar an Air Force patch?
[Nexus 7 (2013) Android Development] Scott:
It should start building. Depending on processor speed it may take a while but it should start scrolling up the screen in just a second or two.

I will forgive you for calling it an Airforce patch....

Read here about the crest: 160th Special Operations Aviation Regiment (Airborne)

NSDQ!
[Nexus 7 (2013) Android Development] alfick3:
Ok, sorry about the Air Force remark. :o Your location said Fargo, and I thought there was a AF base near there. I was in the Navy myself.

As far as my on-topic question goes, it's been probably 20 min and nothing has happened. I'm using an AMD Athlon II x2 255 dual core processor (older system, I know), with only 5 GB of memory. I'm running 64 bit Linux Mint 17.
[Nexus 7 (2013) Android Development] Scott:
Very strange!

I would step through the instructions again to make sure you did not miss anything.
[Nexus 7 (2013) Android Development] thethidie:
Could anyone help with the meaning of "Terminal"? I use "Terminal simulator for Android" but got the error message after input the command.

Please help, I'm not a developer. Thank you.
[Nexus 7 (2013) Android Development] GROGG88:
Terminal emulator is fine, but you must type 'su' before that command. Its a superuser required action.
[Nexus 7 (2013) Android Development] thethidie:
Ok, so my command is: "su restorecon -FR /data/media/0" and then after hit Enter, I've got the message: tmp-mksh: tmp-mksh: -F: unknown option

The problem is still there. My problem is that: after flashing the Clean ROM 5.1 from Clean ROM 4.4.4, some files and folders in sdcard are unreadable and un-deletable, they appear to be 0KB in size shown by ES file explorer, I cannot create new folder and the original camera app cannot take pictures due to "insert SDcard before taking pictures"

Please support me in this. Thank you!
[Nexus 7 (2013) Android Development] GROGG88:
su
restorecon -FR /data/media/0

Regardless, coming from 4.4.4 to 5.x.x it is recommended to flash the factory image first. Install recovery. Then perform a clean install of a custom ROM.
[Nexus 7 (2013) Android Development] thethidie:
Thank God and thank you GROGG88, my files came back.

For a record: it's actually a "su" typing in Terminal. Then, hit "shift + enter". Then, type the remaining command.

What can I do know after I flashed the ROM 5.x.x directly from the ROM 4.4.4 for risk-free future?

I have not encountered a problem yet after fixing the SDcard issue. The camera works fine afterwards.
[Nexus 7 (2013) Android Development] GROGG88:
A factory reset would be a start, but if performing a full wipe then flashing the factory image is still the top recommendation...
[Nexus 7 (2013) Android Development] alfick3:
Ok, at long last I was able to get back to this.

I followed your advice and went through it again. This time I realized that I was supposed to go to the link you provided to download the binaries (last time, I just put that web link into the terminal as a command (a little embarrased here :o )). It worked. Now, after its done, where do I find my zip that will be flashed in recovery?

Thank you for this guide.
[Nexus 7 (2013) Android Development] alfick3:
Oh, and I just noticed the above part says its Android 5.0.1 r1. Does that mean that I created a 5.0.1 ROM?
[Nexus 7 (2013) Android Development] BreckZeBoulay:
Questions for GROGG88 and/or scrosler concerning compiling AOSP.

5.1.0_r1 is synchronised on my computer, and I have made a rom AOSP 5.1.0_r1 for my device (hammerhead).

Now 5.1.0_r3 is out.

Do I have to delete all files of _r1 version and make an entire synchronised of _r3 ?

If not, what files/directories can I keep and what files/directories do I have to delete ?
[Nexus 7 (2013) Android Development] sykopompos:
Depends on any changes you made. The only changes were build id numbers in platform build. About 3 minor changes that merge in with no conflicts in frameworks base, one in settings.

If you don't have any files modified then just sync r3 instead of r1
[Nexus 7 (2013) Android Development] BreckZeBoulay:
I forgot sykopompos :D

Your answer is specifically for the example I give. And I modify nothing, just AOSP out of the box. I don't have the skill to play with that kind of stuff ^^

But generally, what's the good and sure method, total "wipe" ?
[Nexus 7 (2013) Android Development] sykopompos:
With as minimal as the changes were between r1 and r3, you can get away with just reinit your manifest to r3 tag instead of r1 and then repo sync. You can then just make otapackage after that without a make clean/clobber and should be able to dirty flash with no problem

Just a heads up though, hammerhead has updated 5.1 props from 47I, it is mostly camera related stuff though
[Nexus 7 (2013) Android Development] BreckZeBoulay:
but if there are more differences (and generally speaking), the best method is to erase all datas on the computer (?)

Thanks to pointing this. This morning the 47I binaries were not available.

Let's go for a fresh compiling of 5.1.0_r3
[Nexus 7 (2013) Android Development] sykopompos:
The I binaries were available since yesterday https://github.com/Chroma-Aosp/vendor_lge_hammerhead
[Nexus 7 (2013) Android Development] JamFan05:
Would it be possible to clone this into my source directory. Would I have to do anything extra to make it work. Sorry I'm new to all of this
[Nexus 7 (2013) Android Development] sykopompos:
I make my binaries so they are compatible anywhere and have redundancy in case things are missing. You can download it, clone it, add it to your vendor to fetch, just make sure that those _ end up being / folders
[Nexus 7 (2013) Android Development] JamFan05:
Would I clone it into the root of my source folder or into my vendor folder?