Database Info

[ROM] [4.3] [ No-name CM10.2 nightlies ] [TF101 / TF101G]

No-name CM10.2 nightlies
NOTE: THIS IS A WORK IN PROGRESS. CONTRIBUTIONS ARE WELCOME!
(see build setup detailed below)
With that said: Welcome to the No-name CM10.2 nightlies ROM.
Who is this ROM for?
This is a ROM for people who are so eager to try bleeding edge software that they are willing to test-drive it, all bugs included, while it is being developed.
If you value a stable daily-driver with a minimum of issues over everything else, this ROM is probably not for you. There will be bugs. CM10.2 is still in early phase of development, after all.
What's working:
Wi-Fi
GPS
Headphone
All docking stuff
CM Features
AOSP Keyboard
Bluetooth
Micro SD Card & Internal storage
Launcher
Lockscreen
Auto rotate
Camera (99%)
YouTube HD playback
Unresolved, confirmed issues
Front facing camera in Camera app (works in Skype etc)
CM Focal (OMX Codec issue)
Installation:
If coming from any non-4.3.x/CM10.2-based ROM, a factory reset is very much recommended.
Although CM does have official instructions for just upgrading from 10.1.
(0. Backup your existing ROM)
1. Download latest nightly to device.
2. Download special TF101 4.3 gapps linked below.
3. Boot into recovery. TWRP is recommended over CWM.
4. Flash ROM. (This also wipes /system and any mods you already have.)
5. Flash special TF101 Gapps.
6. Reboot.
Basically, the normal procedure for any ROM.
No-name parts with extra features can optionally be installed from market.
If you feel like donating, you can install Straitjacket which is my paid app with some extra features. Plus it might give you a warm fuzzy feeling for being a good guy.
Downloads
TF101 (Wifi only) ROM is available here:
- nexfiles
TF101G ROM is available here:
- nexfiles
4.3 Gapps available here:
- Special TF101 gapps by dlumberg & josteink.
- dlumberg's mirror
Thanks to:
- The Cyanogenmod team, for all the goodies they keep on delivering, across devices.
- RaymanFX, for a CM-compatible device-tree for the TF101.
- Timduru, for KatKernel which keeps this thing stable and functional.
Issues?
Probably plenty. Help us out by reporting them here in this thread. Leave the github issue-tracker alone for now.
If you think you can fix anything, feel free to contribute. We're nice people and open to contributions.
Sources:
Android is open-source. This is an open-source project.
Cyanogenmod:
https://github.com/CyanogenMod/
Noname projects:
https://github.com/NonameROM
Kat-kernel:
https://github.com/timduru/tf101-katkernel
Build-setup:
https://github.com/josteink/android_multi-build
https://github.com/josteink/simba
Current contributors:
- dlumberg
- TheMrcool212
- ShevT
- Jostein Kjønigsen (josteink)

Changelog:
2013-08-12: Initial (preliminary) thread posted, with preliminary build instructions.
2013-08-17: Added tabletUI mods.
2013-08-17: Added TF101G build to setup.
2013-08-20: Youtube HD and Camera fixes.
2013-08-20: Added Noname top-level project on github.
2013-08-21: No longer considered experimental.

(Preliminary) Build instructions:
If you want to contribute, it's probably a good start to get your own build working.
See the instructions here:
https://github.com/NonameROM/android/wiki/Building-Noname-ROM

TheMrcool212 said:
I'm using Ubuntu 13.04 64-bit too. Maybe you had unmerged commits that causing the error.
EDIT: They had fix it:
https://github.com/CyanogenMod/andr...mmit/9de697245289afc7bb88b8e71301e2fab17a0a31
Click to expand...
Click to collapse
I can second that this issue is no longer present, but now I get things related to bionic/libc (for NetBSD!!!) instead...
Don't think it's really realated, but I just want to make sure we don't have any differences which can affect the result. What version of Java are you running?
This is mine:
[email protected]:/mnt/build/android/tf101/4.3$ java -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Click to expand...
Click to collapse

Great to see this!! Thx Josteink.
Been fooling around with Katkiss 4.3 on a spare tf101 I have, if No-name will be like that then our beloved tf will keep on living!!!!!
Thx to all devs
Sent from my Transformer using xda premium

josteink said:
I can second that this issue is no longer present, but now I get things related to bionic/libc (for NetBSD!!!) instead...
Don't think it's really realated, but I just want to make sure we don't have any differences which can affect the result. What version of Java are you running?
This is mine:
Click to expand...
Click to collapse
This commit was the cause of the bionic/libc error. I got this before too, so i skipped that commit. I recommend to use my android_bionic repository, replace it with the current CM10.2.
https://github.com/TheMrcool212/android_bionic/tree/cm-10.2
For the java, i got the same version too:
Code:
[email protected]:~$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

What's working (Tested on my own stock CM10.2 build)
Bluetooth
Dock battery & keyboard layout.
USB Dock (Only tested with pendrive) & SD Card
Micro SD Card & Internal storage
Launcher
Lockscreen
Auto rotate
Confirmed issues
AOSP Keyboard crashes on certain time, even when not using it
Camera & CM Focal
Weird window animation bug when going to home screen.
Back button doesn't work, even on keyboard (I used pie instead)
Menu button, even on keyboard too.
What's not confirm yet to be working
Wi-Fi (due to keyboard issue)
GPS (No Wi-Fi access)
The build of mine and him are just the same, since we are using the same repositories.

TheMrcool212 said:
This commit was the cause of the bionic/libc error. I got this before too, so i skipped that commit. I recommend to use my android_bionic repository, replace it with the current CM10.2.
https://github.com/TheMrcool212/android_bionic/tree/cm-10.2
For the java, i got the same version too:
Code:
[email protected]:~$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Click to expand...
Click to collapse
Cool. Fixed it. Uploading build now

TheMrcool212 said:
What's working (Tested on my own stock CM10.2 build)
...
lots of useful info
...
Click to expand...
Click to collapse
Awesome. Copied to FP!

Added this ROM to the general build setup.
Will find out if it works tomorrow

i will still stick with your wonderful 10.1 rom but thank you for your hard work.
The tf 101 community despite some problems is legendary in its character.
Sent from my Transformer using xda premium

karapoutsoglou said:
i will still stick with your wonderful 10.1 rom but thank you for your hard work.
The tf 101 community despite some problems is legendary in its character.
Sent from my Transformer using xda premium
Click to expand...
Click to collapse
+1, but will follow this thread with more than average interest

Note top self/personal reminder:
- try flashing Google keyboard on top of AOSP keyboard.
- try building with non generic cpu variant which is not cortex-a9 from twrp device tree. Might be better than generic and still work.
Sent from my Galaxy Nexus using Tapatalk 4

josteink said:
Note top self/personal reminder:
- try flashing Google keyboard on top of AOSP keyboard.
- try building with non generic cpu variant which is not cortex-a9 from twrp device tree. Might be better than generic and still work.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Google keyboard works perfectly for me using banks gapps.

@josteink Just want to tell you:
I made a branch called " tf101g-jellybean_4.3 " , based on ShevT's TF101G device tree. I've merged all of 4.3 commits from TF101 branch to the TF101G branch as well. We'll start making this ROM for 3G version as soon as the ROM for TF101 version are quite stable.
diogo.sena said:
Google keyboard works perfectly for me using banks gapps.
Click to expand...
Click to collapse
Where's the banks gapps, can you give me the link for it?

TheMrcool212 said:
@josteink Just want to tell you:
I made a branch called " tf101g-jellybean_4.3 " , based on ShevT's TF101G device tree. I've merged all of 4.3 commits from TF101 branch to the TF101G branch as well. We'll start making this ROM for 3G version as soon as the ROM for TF101 version are quite stable.
Click to expand...
Click to collapse
Agreed.
I just think letting @ShevT open up his repo and give us commit access would be "cleaner". We'll see when he discovers this thread and wants in on the action
TheMrcool212 said:
Where's the banks gapps, can you give me the link for it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2012857
Should probably be added to FP. I'll get it done.

I know the original gapps (4.2 no-name ROM version) Google keyboard had some issues, but the newly released Google keyboard from the play store worked fully on the 4.2 no-name ROM. Not sure if there is a newer gapps which now contains that same keyboard or if it needs to be installed from the play store?
Sent from my Nexus 4

diogo.sena said:
Google keyboard works perfectly for me using banks gapps.
Click to expand...
Click to collapse
Can you confirm if wifi or GPS is working then? Will make the list on the first page easier for people to rate
And what version did you use? The 4.3 version?

I just flashed the banks' 4.3 Google Keyboard. Now i can have access to my Wi-Fi and here's the update:
Wi-Fi is working
GPS working too!
All dock functions are working when flashing the banks' Google Kayboard gapps
Back, menu and recents button are working (I'm not sure why this had been fixed, maybe due to the working keyboard)
No AOSP keyboard crashes.
New issue
YouTube doesn't play when HD is enabled, only when it's been disabled.
What's left
Camera & CM Focal
Weird window animation bug when returning to home screen.
YouTube player issue.
@josteink, I think we need to revamp the gapps, since some of the apps are not updated like the keyboard, PlayStore, Google Search etc.

TheMrcool212 said:
I just flashed the banks' 4.3 Google Keyboard. Now i can have access to my Wi-Fi and here's the update:
Wi-Fi is working
GPS working too!
Click to expand...
Click to collapse
Yes, only wifi droped one at restoring all the apps from Google, while loading the app store. After that no problems with wifi.
TheMrcool212 said:
New issue
YouTube doesn't play when HD is enabled, only when it's been disabled.
Click to expand...
Click to collapse
Is same as on KatKiss http://forum.xda-developers.com/showpost.php?p=44274292&postcount=2
Using TWRP 2.3.2.3
I did a cache, and system wipe, factory reset and flashed the rom with the Banks Gapps, just the core.
Main issue: lost root privilages. Otherwise: feels already as a matured rom
---------- Post added at 09:16 AM ---------- Previous post was at 09:09 AM ----------
pinkdot;44604445
Main issue: lost root privilages. [/QUOTE said:
Ah, got root back by changing the settings
Click to expand...
Click to collapse

[ROM] [Android 4.4 Kitkat] Unofficial Shiny ROM for Grouper with Built in Gapps

[TYPE][ANDROID VERSION][NAME][OTHER INFO][DATE]
This ROM is a fully AOSP build of Android 4.4 KitKat. The source was downloaded and compiled by me.
It is exactly what Google will release in “a few weeks” for the 2012 Nexus 7 when they release KitKat
This ROM is based off of Baldwinguy77's work on 'Shiny' for Toro, and uses his vendor. I did all the bring up for Grouper(with a ton of help from Baldwinguy77) The difference is that some of the changes he has made to the system aren't here, this is AOSP with a few modifications to make it run, Hence the Unofficial Tag.
There will be changes coming to fix bugs and remove redundancies between AOSP and Google Proprietary files. Also, changes will be made to the system to include some other small features in time. This ROM will branch out from baldwinguy's initial work to something a little bit different.
Google Apps are included in this build.
Bugs:
Boot Animation
You tell me
I, nor Baldwinguy77 is responsible for anything that goes wrong during the installation.
Special Thanks goes to Baldwinguy77 for helping me out and supplying his vendor files, as well as answering all my questions in the past 72 hours. Please consider donating to him as most of the initial bringup was his work: Paypal Donate Link for Baldwinguy77
Also, please note that this does not contain root. You are responsible for adding root at the moment.
Feel free to let me know if anything goes wrong. This is my first public posting of a ROM I have built from source.
Also note that the first boot is extraordinarily long.
Download links:http://d-h.st/DPJ
MIRROR: https://www.dropbox....ta-eng.neel.zip
Enjoy!
If you really like my work, and you haven't donated to baldwinguy77, consider donating to me: here on paypal

Reserved

does camera work on this build?

popup keyboard and rotating fixed ??
otherwise it's the same as all the other 4.4 roms / ports outthere

Forget keyboard popup, are you fixed rotation and gradient glitch problem ?

Let him feel special for releasing this, after all he did all the work. Who cares if there are 3 other similar ROMs
Sent from my Nokia Lumia 920 using Tapatalk

I tested ROM, everything is same with other similar ROMS...
Can you please add this bugs to your thread:
-Rotation
-GPS
-Camera
-Launcher Keyboard Popup

I will add those. I have an idea on GPS and should have it working be end of day. The keyboard issue seems proprietary, but I have ideas about it.
everesee said:
I tested ROM, everything is same with other similar ROMS...
Can you please add this bugs to your thread:
-Rotation
-GPS
-Camera
-Launcher Keyboard Popup
Click to expand...
Click to collapse

GPS is working for me.

MidnightNinja said:
I will add those. I have an idea on GPS and should have it working be end of day. The keyboard issue seems proprietary, but I have ideas about it.
Click to expand...
Click to collapse
If you fix them, you will be a hero

MidnightNinja said:
[TYPE][ANDROID VERSION][NAME][OTHER INFO][DATE]
Google Apps are included in this build.
Click to expand...
Click to collapse
Well, first, my understanding is that you should separate the GAPPS from the ROM, per Google's license... that being said, included or separate, can you deliver them ODEXED so we can try Art instead of Dalvik?
thanks,
jf

everesee said:
If you fix them, you will be a hero
Click to expand...
Click to collapse
+1
Sent from my HTC6435LVW using xda app-developers app

friedsonjm said:
Well, first, my understanding is that you should separate the GAPPS from the ROM, per Google's license... that being said, included or separate, can you deliver them ODEXED so we can try Art instead of Dalvik?
thanks,
jf
Click to expand...
Click to collapse
Please explain what you are talking about with regards to Art.
I include google apps for convenience, and several ROMs have done this same method. At the end of the day, I plan on providing what Google will eventually provide for the N7.

FWIW, the CM 11.0 source has dropped, and I've posted some quick stuff about it in the build thread.
My n7 is down for the moment (loose charger slot thing) but that doesn't mean y'all should have to wait
Good luck, we're all counting on you.

This ROM unrooted my N7 and is giving me constant acore.process issues. Think I'll go back to koko98's version, seems more stable.

PAULO76 said:
This ROM unrooted my N7 and is giving me constant acore.process issues. Think I'll go back to koko98's version, seems more stable.
Click to expand...
Click to collapse
Please provide more than constant acore issues. I also do not include root, as I state in the OP.

fattire said:
FWIW, the CM 11.0 source has dropped, and I've posted some quick stuff about it in the build thread.
My n7 is down for the moment (loose charger slot thing) but that doesn't mean y'all should have to wait
Good luck, we're all counting on you.
Click to expand...
Click to collapse
The source is downloaded....just trying the get the vendors set up for i605 and grouper .
I will see about getting a release out sometime today/tomorrow,when I know that its stable. I also don't know how to fix some of the binary issues,but I know they'll be fixed soon

MidnightNinja said:
Please provide more than constant acore issues. I also do not include root, as I state in the OP.
Click to expand...
Click to collapse
Ooops, my bad. Need to read a bit more thoroughly. Thanks for the instant reply.

MidnightNinja said:
Please explain what you are talking about with regards to Art.
Click to expand...
Click to collapse
ART is Google's runtime replacement for Dalvik - you can enable it under settings, but if you install 'normal' GAPPS, i.e., deodexed ones, it conflicts and they keep FC'ing
My understanding is that won't happen with odexed gapps; with them, we could try ART instead of dalvik.
jf

friedsonjm said:
ART is Google's runtime replacement for Dalvik - you can enable it under settings, but if you install 'normal' GAPPS, i.e., deodexed ones, it conflicts and they keep FC'ing
My understanding is that won't happen with odexed gapps; with them, we could try ART instead of dalvik.
jf
Click to expand...
Click to collapse
Now that I understand and have researched it, I'm going to take this idea for right now:
I will not be distributing a seperate gapps package that is odexed. This ROM, anyways is deodexed out of the box and as such, probably breaks all compatibly with ART.
Android ships with dalvik, and for now, I will not be offering support for something which requires me to redo the rom and provides no benefit. In fact, it appears to break many apps on the app store right now.
If in time, ART is shown to be stable and has all the issues ironed out, I will begin odexed builds and provide odexed gapps.

DashClock Update

It'd be nice if we had access to DashClock updates like anyone else. Today a new version of DashClock came out on the Play Store but we can't update it because it's inbuilt into Omni.

+1 for this

Delete /system/app/DashClock.apk of change its extension.
Reboot.
Install this apk - http://www10.zippyshare.com/v/33890457/file.html
Sent from my GT-N7100 using Tapatalk

UtkarshGupta said:
Delete /system/app/DashClock.apk of change its extension.
Reboot.
Install this apk - http://www10.zippyshare.com/v/33890457/file.html
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
i know, but the error was reported to be corrected in next build. :fingers-crossed:

Just tried updating on latest nightly and still getting the error. Even deleting the apk and rebooting I can't install from the Play store. Maybe remove DashClock from Omni altogether, it's easy enough to install from the store and we'll be able to get updates when they're released and not have to wait for a new hold of the ROM, this is far to much like a OEM/carrier restriction.

IIIIkoolaidIIII said:
Just tried updating on latest nightly and still getting the error. Even deleting the apk and rebooting I can't install from the Play store. Maybe remove DashClock from Omni altogether, it's easy enough to install from the store and we'll be able to get updates when they're released and not have to wait for a new hold of the ROM, this is far to much like a OEM/carrier restriction.
Click to expand...
Click to collapse
I removed the .apk that comes with OmniROM, rebooted, and installed the newest version from UtkarshGupta's link. Everything went fine.
Now for the .apk to survive between updates, all you have to do is add the DashClock.apk to an .sh script in the /system/addon.d directory. Works like charm on my manta (Nexus 10).

_Raziel666 said:
I removed the .apk that comes with OmniROM, rebooted, and installed the newest version from UtkarshGupta's link. Everything went fine.
Now for the .apk to survive between updates, all you have to do is add the DashClock.apk to an .sh script in the /system/addon.d directory. Works like charm on my manta (Nexus 10).
Click to expand...
Click to collapse
I'd rather be able to just update from the store and not have to worry about scripts. I'm also in the DashClock beta program which I don't get with it being included in the ROM. I know it's possible to do as you stated but I'd prefer to do it via the store and still be involved in the beta program.

IIIIkoolaidIIII said:
I'd rather be able to just update from the store and not have to worry about scripts. I'm also in the DashClock beta program which I don't get with it being included in the ROM. I know it's possible to do as you stated but I'd prefer to do it via the store and still be involved in the beta program.
Click to expand...
Click to collapse
+1.
There's something I don't really understand, though.
As far as I can tell from the changelog, Dashclock updates should have been added to Omni on 1/1-14. But even though I just tried removing the system APK and updating to the latest nightly build of Omni, it's still running Dashclock 1.5 build 26... Should that not be 1.6 build 30?

Yeah I'd noticed that as well. Will have to try and bring this up as a feature/bug request on their jira tracker if they have one.

nslr said:
+1.
There's something I don't really understand, though.
As far as I can tell from the changelog, Dashclock updates should have been added to Omni on 1/1-14. But even though I just tried removing the system APK and updating to the latest nightly build of Omni, it's still running Dashclock 1.5 build 26... Should that not be 1.6 build 30?
Click to expand...
Click to collapse
+1

IIIIkoolaidIIII said:
I'd rather be able to just update from the store and not have to worry about scripts. I'm also in the DashClock beta program which I don't get with it being included in the ROM. I know it's possible to do as you stated but I'd prefer to do it via the store and still be involved in the beta program.
Click to expand...
Click to collapse
+1

[APP][5.0.2][IR]LG QuickRemote for AOSP [1-13-15]

This zip installs the QuickRemote app and enables the IR blaster to work on AOSP Lollipop ROMs for the LG G3 (and G2). Not every device or rom has been tested, so flash at your own risk.
Credits go to @sefnap for the original G2 port, @RieGo for the original scripts, and @zzeneg for updating to the G3 versions.
WORKAROUND DETAILS:
The default SELinux policy for android was changed to enforcing mode in Lollipop to increase security. This restricts the functionality of some apps, so for QuickRemote to work we have to change the SELinux policy back to permissive mode until we have a better solution.
This zip installs an init.d script which runs at boot and sets the SELinux policy, as well as other permissions. It will also create the file /sdcard/QRemote.log, which records the SELinux policy at startup.
INSTRUCTIONS:
--Make a backup (or at least download the uninstall)
--Install the latest SuperSU (highly recommended)
--Wipe dalvik/cache (just in case)
--Flash zip in recovery (TWRP or PhilZ)
--Reboot--
--It may take a moment for device manufacturers to load, so be patient.
TROUBLESHOOTING:
First, make sure init.d is enabled:
-Check for /sdcard/QRemote.log. If the file isn't there, the init.d script did not run.
---Enable init.d support with this app
-If it still isn't working after enabling init.d and rebooting, verify that SELinux was set to permissive at boot in QRemote.log
---Try this app to set the SELinux policy instead.​If the QuickRemote app force closes when you open it:
-Make sure QuicksetSDK is installed. It won't be in the app drawer, so check Setting->Apps->All
-Clear QuicksetSDK data, delete /sdcard/Quickset Setup, reboot​
Thanks to everyone in this thread for helping figure this thing out!​

Working perfect on liquid smooth rom, thanks for posting this!

Thanks so much for posting this. Not being able to use Smart IR on AOSP has been killing me. I absolutely hate my LG TV remote. Will be testing on Beanstalk this evening.

confirm working for d855 on cm11... thanks

Any chance of a working QuickCircle port for AOSP?
It's the only thing that's holding me back from installing CM11. I refuse to give up on this case since I paid so much money for it god damn it

Thanks, it's work !
L10nH34Rt said:
Any chance of a working QuickCircle port for AOSP?
It's the only thing that's holding me back from installing CM11. I refuse to give up on this case since I paid so much money for it god damn it
Click to expand...
Click to collapse
I hope too. But I think on the G2 the quickwindow cover working on CM11 . Wait and see..

Quickset SDK has stopped.
Sent from my LG-D850 using XDA Free mobile app

Anyone tested this on CM12 yet?

if4ct0r said:
Anyone tested this on CM12 yet?
Click to expand...
Click to collapse
It isn't compatible with ART.

Joey43 said:
It isn't compatible with ART.
Click to expand...
Click to collapse
Sorry. I guess "- ART is supported" is a little misleading.

if4ct0r said:
Sorry. I guess "- ART is supported" is a little misleading.
Click to expand...
Click to collapse
I tried it on 5.0 and resulted in force closes and a broken app. Go ahead and download both files, if they work yippee, if not just flash the uninstall.

And let us know!
Sent from my LG-D851 using Tapatalk

if4ct0r said:
Sorry. I guess "- ART is supported" is a little misleading.
Click to expand...
Click to collapse
KitKat Art, and Lollipop Art, are two different creatures. I'd think that a port of the Lollipop version of this remote from the g3 leaks should work.

dictionary said:
KitKat Art, and Lollipop Art, are two different creatures. I'd think that a port of the Lollipop version of this remote from the g3 leaks should work.
Click to expand...
Click to collapse
Well, if it wouldn't, it wouldn't be a port, am I right?
I tried flashing it on Lollipop and using a different remote App and that didn't work either, even though the App recognized that the G3 has an IR-Blaster.

Guys, if you use a custom rom like CM12, you can make the flashable zip to work by doing the following.
First flash it normally, then grab from XDA the LGs lollipop version of QuicksetSDK, I think there should be a lollipop version, but I copied it from Android HD rom. Then replace the KitKat version with lollipop in in the System/app folder, set the correct permissions and voila it works. I have tested it on my Sony TV, it works like a charm. Good thing is that Smart Remote IR also works if interested to try.

Here's the Quickremote zip with the updated QuicksetSDK (For CM12!):
http://www.mediafire.com/?bbfbfefbnj7bj7k
I hope you don't mind me uploading this here @zzeneg, all credits are going to you! If you want me to, I'll take it offline immediately.
I think it should work on any 5.0 AOSP-Rom.
For some reason my IR-Blaster isn't working, the app launches, but the IR-Blaster just doesn't work.

Xerionius said:
Here's the Quickremote zip with the updated QuicksetSDK (For CM12!):
http://www.mediafire.com/download/bb...moteG3CM12.zip
I hope you don't mind me uploading this here @zzeneg, all credits are going to you! If you want me to, I'll take it offline immediately.
I think it should work on any 5.0 AOSP-Rom.
For some reason my IR-Blaster isn't working, the app launches, but the IR-Blaster just doesn't work.
Click to expand...
Click to collapse
Thanks mannnnnn. Now when it works I'll be happy. I wonder if it'll have a widget for pulldown
Sent from my LG-D851 using Tapatalk
---------- Post added at 12:57 AM ---------- Previous post was at 12:54 AM ----------
I wonder if the quick circle stuff can be added to cm
Sent from my LG-D851 using Tapatalk

Xerionius said:
Here's the Quickremote zip with the updated QuicksetSDK (For CM12!):
http://www.mediafire.com/download/bb...moteG3CM12.zip
I hope you don't mind me uploading this here @zzeneg, all credits are going to you! If you want me to, I'll take it offline immediately.
I think it should work on any 5.0 AOSP-Rom.
For some reason my IR-Blaster isn't working, the app launches, but the IR-Blaster just doesn't work.
Click to expand...
Click to collapse
link down?

rickriego said:
link down?
Click to expand...
Click to collapse
This is weird, the file wasn't down but the link changed.
I updated it, here's the new one: http://www.mediafire.com/?bbfbfefbnj7bj7k

Xerionius said:
This is weird, the file wasn't down but the link changed.
I updated it, here's the new one: http://www.mediafire.com/?bbfbfefbnj7bj7k
Click to expand...
Click to collapse
Getting a 38 kb file that won't flash? Tried downloading three times

[W.I.P] AOSP 7.1.1_r4 Nougat NMF26O [07.12.2016]

Builds of Android Nougat for our beloved Nexus 7 2013.
This is, again, a fork of @DevSwift1's original AOSP port (http://forum.xda-developers.com/nexus-7-2013/orig-development/p-aosp-n-7-0-google-shame-t3448008), for totally different reasons. This time because he is MIA and it would be a good idea to update with the October Security Update and beyond.
What works:
Audio
Brightness
GPU Acceleration
Bluetooth
Wifi
NFC
GPS
Location services
Camera and video recording
Video playback
MTP
Sensors
Bugs:
- Play TV and Movies DRM broken (Wildvine)
- poor 1080p video recording quality.
- Can't install Play Games (through Play. May work through opengapps aroma if you pick just that and what is in micro. Maybe one or 2 others) It can be sideloaded.
Change Log:
v0.10.0.1 (Flo only, not applicable to Deb)
- Fixed GPS.
v0.10 (0.8.9999 was "0.9")
- 7.1.1_r4, including December Security Patches (except items in the kernel)
v0.8.999
- Partial Nov Security Update. (Everything but the kernel)
v0.8.1
- Fix for CVEs: 2016-5195, 2016-5340, 2016-7117, 2016-3903, 2016-3934
- That should address all of applicable kernel patches from the Oct Security Update plus Dirty Cow.
v0.8
- Update to 7.1.0_r4 complete, and apparently fine. (well, as good as 07.2)
Download:
Flo: 0.10.0.1
Deb: 0.10.0
Old just in case, since 0.10 is a big jump:
Flo: 0.8.9999
Deb: 0.8.9999
Gapps: http://opengapps.org (micro version recommended)
If you have trouble installing Gapps, try rebooting (right back into recovery, not system) between flashing the ROM and Gapps.
Micro is a bit more than just recommended. It is the largest package that will fit in the system partition. This is basically a universal issue with Nougat that can't really be worked around without very risky tweaks to mess with the partition sizes which I'm not even sure are actually possible. (not happening)
You can install smaller packages, or "larger" using a custom config or the Aroma installer. And only slightly "larger" there. That is more useful to pick and choose to find a balance that works for you. You won't fit much more. (I do that on my Moto E which has the same issue.)
Sources: https://github.com/nbehary/manifest (the n-mr1 branch is 0.8. and master is basically untouched and still 0.7.2. I'll make master v0.8 later. )
Kernel Sources: https://github.com/nbehary/android_kernel_google_msm
Credit
@zaclimon
@DevSwift1

Two development things to mention:
- right now I'm forking as little of msm8960 as I needed to to apply the security patch. Only platform_frameworks_base and platform_system_core in my repos are current. (platform_build_core may or may not be, but it more or less is and doesn't matter for 99% of anything) I had forked them all before, but the rest aren't up to date. If you'd like to submit pull requests to help in any other repo, msg me first and I'll fork it first. (This will change over time. The manifest is the best guide for which I've updated. If I'm using mine there, it is current)
- I did ignore one of @DevSwift1's commits in system/core, since it was just pulling in my fork of it. No point, except to keep the history intact, but I was lazy. They were the same.
(ETA: oh, 3. The kernel sources are also up to date, and more current than the one in msm8960, even though the commits are backwards. He never merged the CVE patch. )

Is it possible to dirty flash over DevSwift1's version?

jerethi said:
Is it possible to dirty flash over DevSwift1's version?
Click to expand...
Click to collapse
Probably. Sorry, forgot to mention that in the OP.
I know that dirty flashing the test version I posted in the other thread a few days ago over that works, and this over the test does. So, it should work fine.

We don't have to flash gapps again if we are updating from .6 do we?
Sent from my Nexus 7 using XDA-Developers mobile app

gangrenius said:
We don't have to flash gapps again if we are updating from .6 do we?
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
You may. I always do, and didn't test without. My gut feeling is that you will need to. (I get mixed up though, the build I'm using on my Moto E always needs it, and I can't remember if here did too)

I know I don't when I flash an updated systemm of rr remix on my phone . hmmm guess we'll see
Sent from my Nexus 7 using XDA-Developers mobile app
---------- Post added at 06:01 AM ---------- Previous post was at 05:44 AM ----------
Can u add in that build prop edit they shared online into this so we can use google assistant?
Sent from my Nexus 7 using XDA-Developers mobile app

just in case i want to build using your trees and kernel sources, will it be a prebuilt kernel or from source?

simplyme2908 said:
just in case i want to build using your trees and kernel sources, will it be a prebuilt kernel or from source?
Click to expand...
Click to collapse
Prebuilt, but the one the manifest currently pulls, from my repos, is built from the sources posted here. It is entirely current. (despite the fact that I built it weeks ago.)

Is root lost after dirty flashing over 0.6?
Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.0) con Tapatalk 6

jerethi said:
Is it possible to dirty flash over DevSwift1's version?
Click to expand...
Click to collapse
nbehary said:
Probably. Sorry, forgot to mention that in the OP.
I know that dirty flashing the test version I posted in the other thread a few days ago over that works, and this over the test does. So, it should work fine.
Click to expand...
Click to collapse
For me, dirty flashing this over DevSwift1's version works.
Thanks for keeping this tablet updated!

Thanks for continuing to update this rom

miki67 said:
Is root lost after dirty flashing over 0.6?
Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.0) con Tapatalk 6
Click to expand...
Click to collapse
Yes, I have to root again.

With your build the video recording doesn't work at all in any camera app. See screenshot below of google camera
Please note I dirty flashed this on top of DevSwift1's version.

Has anyone installed EX on this? How does it perform?

@nbehary
What I've found not working so far
When I try to add my google account to Google Keep, the app force closes.
When trying to install Google Play Games from the Play Store I get the following error message (see image below).
Device is reported as Google Nexus 7 2012 model when logging in with your Google account.
Other than that ROM is stable and smooth! Love Android 7.0
Great work! :good:
Edit: Installed from scratch (clean install)

Does it matter which version I currently have ?
I'm doing this for the first time, using this tutorial - http://androiding.how/how-to-install-a-custom-rom-using-twrp-recovery/

I tried to install gapps together with ROM, but GAPPS shows: "Incompatible device detected"
I downloaded ARM64 GAPPS
ERROR:
Camera error: Can't connect to the camera.
And photo quality is also bad, very grainy..

rudolph323 said:
I tried to install gapps together with ROM, but GAPPS shows: "Incompatible device detected"
I downloaded ARM64 GAPPS
ERROR:
Camera error: Can't connect to the camera.
Click to expand...
Click to collapse
Don't use Arm64, Nexus 7 is 32-bit. So you want Opengapps 7.0 arm gapps
And yeah same camera issue, hopefully it gets fixed.
Otherwise good ROM.:good:

Is the webview patch applied?
http://opengapps.org/blog/post/2016/10/06/nougat-webview/