Related
This is my first port so there may be some issues but would love for any help squashing bugs once it gets going. I've built this similarly to how Android TV was ported to the OUYA in this thread.
Similarly I am using the following for this port:
His ADT-1 System dump from this post.
His Android L port to the 2012 Nexus 7 from here.
and last but not least
His CM11 Amp Build from here.
Working
Unknown
Not Working
Unknown
Git Repo
here
Builds
v1 Can be downloaded here
v1.1 Can be downloaded here
Changelog
v1 Initial Release
V1.1 Hopefully fixed bootloop issue, see commits
Installation
* Install CM11 first as per here
* Boot into recovery, install downloaded zip, wipe all, reboot
* Wait
* Enjoy
I haven't had a chance to install it yet, so it's very alpha right now but feel free to contribute to the repo.
As always only you are responsible for your device.
Just to let you know: you're not alone in this. I'll try to get this working in my free time as well.
Very excited for this. will install soon and give feedback. I'm not a developer but very experienced and own a nexus Q myself.
Thanks a lot for working on this.
I just saw this thread. Thanks for working on this. What's working/not working so far?
Has anyone flashed this yet? I want to try, but I won't be back home until next week. Just curious if anyone has had any success?
I've installed this just now ... unfortunately it doesn't look like its going to boot.
Followed all instructions ... bootscreen is moving but no load after 20 mins.
EDIT:
It did not boot and I am not sure why at this time.
Lifetrip718 said:
I've installed this just now ... unfortunately it doesn't look like its going to boot.
Followed all instructions ... bootscreen is moving but no load after 20 mins.
EDIT:
It did not boot and I am not sure why at this time.
Click to expand...
Click to collapse
Hopefully there will be some kind of fix. Nexus Q is the dream AndroidTV.
Still no progress past the boot animation sadly - even with the updated build. Does it matter which audio output version of CM11 you have flashed first? (edit: tried several & no joy)
Also, I tried to take a logcat to see if I could indentify where it was getting stuck during the boot proccess but sadly it would not let me as it is showing as "offline" which suggests that Android has actually booted and is therefore requiring an RSA key but has not made it as far as displaying any kind of interface.
Thanks for starting to work on this anyway. I would love to get Android TV working on this device.
I think I may know what the issue is with this. For the Ouya, using a 5.0 build for the N7 2012 made sense because they both use the Tegra 3. However the Nexus Q does not use the Tegra 3, internally it is almost exactly the same as the Galaxy Nexus and they both use the OMAP 4460, therefore using the Nexus 7 2012 base will not work.
If you use the latest Android 5.0 port for the Galaxy Nexus instead then things should (hopefully) work just fine. The CM12 port for the Gnex also includes some updated GPU drivers from Texas Instruments which give better performance and provide better compatibility with newer Android versions.
I hope this may help you create a working Android TV port. I may try and build something myself during late January if I get the time but I can't make any promises. I've only just got the Nexus Q so I'm just starting to play around with it.
I am excited to see the progress on this. If this works, the possabilities are endless. Thank you every in advance for their support. If we can get this up and going, I am definalty donating to the cause for someones hard work (i wish i knew how to do this!)
To the developer of this rom if you want help just pm me. I'm thinking of starting a hangout group for porting Android TV.
I am very interested in this project and would be interested in helping out. I have never done anything like this, and I would like to see the nexus q live on.
If the full android-tv functionality is not possible, it would still be interesting to me to turn it into a 'cast ready speaker' for cast audio. (obviously I would need to hook my own speakers to it)
It has an amp, the ability to hook up to wifi, and volume control. In my mind, it would need no other functionality other than the ability to cast to it.
If there are any suggestions or guidance, please throw them out there. I will do my best to run with it.
Really hoping to see this go somewhere.
So is development for this dead?
Is there anyway to get development spurred back up for this? I would gladly donate some $$$ for someone to put some time into it.....If I new how too, I would help in development. This would be the ULTIMATE Android TV player!!!!!
Kovs said:
Is there anyway to get development spurred back up for this? I would gladly donate some $$$ for someone to put some time into it.....If I new how too, I would help in development. This would be the ULTIMATE Android TV player!!!!!
Click to expand...
Click to collapse
The developers need to first get android L running on the device. The port is nearly impossible if your device doesn't have a fully function 5.0 port. The graphics HAL is the main thing I think will fail.
You all are welcome to give my AOSP 5.1 ROM a try, with the understanding it is in an extreme ALPHA state (first build, no 3rd party features implemented yet), and can tolerate restoring a backup if you encounter issues. I'm not sure how many still are actively using these on XDA, but the more testers the better so development can be expedited.
http://forum.xda-developers.com/nexus-q/development/rom-unofficial-cm12-nexus-q-t3023498
Awesome thank you for your work. Hopefully with that, this can take off!
We know that today OnePlus released the newest Android P Beta for the OnePlus 6 for both HydrogenOS and OxygenOS.It is a surprise to me because it now allows HydrogenOS devices install the preview version without wiping user data.However,when I try to open the "Sensors" page in AIDA64,my phone frozed and soon showed me some words including"Qualcomm Crash Dump".I soon reported this on the forum and knew that another person has the same problem.Now I just want to know why it happens and if the OxygenOS build has the same bug.I'm so worried about it and want to know whether it will do harm to my phone.
Yeah, I just installed the Android P Beta 3 on my op6, and whenever I even open up CPU-Z, my phone goes into Crashdump mode. I've had issues with apps such as CPU-Z and AIDA64 with Beta 2 as well. I'm guessing it has something to do with the app looking for certain data about the phone, and that not agreeing with the beta buids. I'm not surprised, it is a beta build anyways.
Edit: I put DP3 instead of Beta 3. Fixed.
Hey guys!
First, my apologies if I am in the wrong section posting. I was not sure where to post. Please move my thread if needed. Thanks!
Second, would someone recommend and/or suggest Android 9 over Android 10 or Android 10 over Android 9? For myself, I really do not like Android 10. When I am referring to Android 10 and I am referring to the original in September and the two updates in September where that last update has a C3 in part of the name, as well as the October Android 10 update. I just do not like any of the updates. Would I be better off going back to Android 9? It is not an issue because I can flash the factory images via ADB when the phone is powered on than Fastboot once the phone is in the flashing mode
Can you explain why you do not like the update?
I personally don't find that there is a lot of difference between 9 and 10, but offcourse 10 has the latest security updates, which might be a reason for you to stay with 10.
Personally I think the biggest noticeable difference between 9 and 10 is the gesture based navigation. However you can turn the Android 9 style navigation back on if you so desire (Settings/System/Gestures/2-button navigation) or even the older 3 button navigation.
Other changes - like dark mode - are also optional. I see little reason to stay on Android 9. Especially since it is not being updated with security updates.
It would be nice if we could continue to use a preferred version but that comes with considerable security risks. If your dislike is purely asthetics, you can try other launchers.
For the sake of security I'll stick with Q10 for now. I have yet to succeed with a direct OTA update even under full stock. If the pending November OTA updates without needing to sideload, I might then install Magisk.
Cool I w up - Micr
alliance1975 said:
For the sake of security I'll stick with Q10 for now. I have yet to succeed with a direct OTA update even under full stock. If the pending November OTA updates without needing to sideload, I might then install Magisk.
Click to expand...
Click to collapse
The majority of pushback comes from people USED to Android 9/Pie. I get it; I really do - when folks get comfortable, change scares the bejeebers outta them. Because I never ran Pie before the Pixel 3a came along (and Android 10 was halfway through its beta when the 3a arrived) I was able to go from 8/Oreo to 10 pretty much directly with only one migration issue; the gesture support. Simply not using them (even with Gboard) was an option, however - and one I adopted.
Launchers - Pixel Launcher was one I was already familiar with (from my Android 6 and 7 days); returning to it was therefore rather a relief.
The even bigger surprise is that I'm not rooted - or using a non-stock recovery; the first time I've done that on a smartphone (or any Android device since Android 5). TWRP was a certain install on a smartphone (as certain as doing tax returns every year); now - I could, in fact, care less. I follow TWRP development (and Magisk development as well); however, it's more a case of looking for a reason to install either - so far, nothing in Android 10 has given me a reason to move away from dead-stock. (Basically, it's a NEW sort of comfort - dead stock - for the first time in my Android phone history - IS actually good enough to run un-stepped-on.)
Dark mode requires neither; it's an option in Settings. Same with VoLTE/VoWiFi. Basically, so much for Magisk.
The thing is, you have to be comfortable with dead-stock; being as this is, after all, a developer/tweaker-targeting community, how many folks are actually comfortable running dead-stock?
If you CAN get comfortable running dead-stock, Android 10 on your 3a or 3a XL (or any Pixel, for that matter) makes a ton of sense.
Follow up - Due to Microsoft Launcher changing it's code base, I installed the beta on my Pixel 3a, replacing Pixel Launched as default. Due to new features, Pixel Launcher is in trouble! It is not the support for Dark Mode, third party launchers either have or are adding it. It is being able to use apps as plug ins; two I use now are Word (expected) and Google Calendar (unexpected). How many third party launchers let you use a system app - even Calendar - as a plug in directly. While Outlook for Android does, it is still nice to have Launcher do so as well. This very post is another example - I have added the XDA app as a plug in. Depending on how often you use an app, using it as a plug in May be faster than as a shortcut.
Im a new pixel user, i come from Nokia 7 plus (Android 9 - android one program, almost the same as pixel) and simply cant go back to 9...
Im glad my nokia also updated to 10 today , i really like the gestures. And i have been on 9 for 1 1/2 year now...
Nova launcher, gestures work fine on android 10, dark mode is not everywhere but its coming....
PGHammer said:
The majority of pushback comes from people USED to Android 9/Pie. I get it; I really do - when folks get comfortable, change scares the bejeebers outta them. Because I never ran Pie before the Pixel 3a came along (and Android 10 was halfway through its beta when the 3a arrived) I was able to go from 8/Oreo to 10 pretty much directly with only one migration issue; the gesture support. Simply not using them (even with Gboard) was an option, however - and one I adopted.
Launchers - Pixel Launcher was one I was already familiar with (from my Android 6 and 7 days); returning to it was therefore rather a relief.
The even bigger surprise is that I'm not rooted - or using a non-stock recovery; the first time I've done that on a smartphone (or any Android device since Android 5). TWRP was a certain install on a smartphone (as certain as doing tax returns every year); now - I could, in fact, care less. I follow TWRP development (and Magisk development as well); however, it's more a case of looking for a reason to install either - so far, nothing in Android 10 has given me a reason to move away from dead-stock. (Basically, it's a NEW sort of comfort - dead stock - for the first time in my Android phone history - IS actually good enough to run un-stepped-on.)
Dark mode requires neither; it's an option in Settings. Same with VoLTE/VoWiFi. Basically, so much for Magisk.
The thing is, you have to be comfortable with dead-stock; being as this is, after all, a developer/tweaker-targeting community, how many folks are actually comfortable running dead-stock?
If you CAN get comfortable running dead-stock, Android 10 on your 3a or 3a XL (or any Pixel, for that matter) makes a ton of sense.
Click to expand...
Click to collapse
I don't know that I had to, but I sideloaded the December update. However, the January update downloaded and installed w/o problem. I have had time to get used to full Q10 stock and it does many nice things. I don't think I'll do root until major changes happen.
Short version: What's the easiest/best way to make sure my (unlocked/Magisk-rooted) 7Pro does NOT upgrade to Android 10?
Long version:
New 1+ owner here after finally giving up on Google's ability to make a phone I like (I have had only Google phones since Nexus One, and just now retiring my Nexus 6) -
Before getting the 7Pro, I got/tried/returned the horrible Pixel 4XL - that I might actually have kept if Google had done a better job on the software - Android 10 and the new Assistant features. (*Shocking to me that out of the box, this brand new factory fresh phone is loaded with GAPPS that lack the features that Google advertises for the phone! Requires many updates, and still doesn't work properly.)
Since I don't want to effectively become a beta-tester for this new stuff, I really want to prevent the 1+ from updating to Android 10 and not quite sure how to make sure:
The phone came with a 9.x version, and did 1 system upgrade to 9.5.13, and it's now telling me another system upgrade is available. But, best I can tell, there is no way to know what build it is going to update to until after it's done?
Android 10 stable branch has been mostly fine. The only bug I've experienced was due to custom kernels and modules. I'd say avoid 10.3 until the wifi brain cpu issue is fixed.
relaxable said:
Short version: What's the easiest/best way to make sure my (unlocked/Magisk-rooted) 7Pro does NOT upgrade to Android 10?
Click to expand...
Click to collapse
xxxNoLimits can systemlessly debloat OPBackup if you select that as one of the available options. That will prevent auto updates.
Best as I understand, 9.5.3 was the last Pie Rom. Any further updates will be Q.
Hi guys,
after almost 2 years with MIUI, Android 10 and Android 11 with MIUI 12.5, I would like to try a custom Android 12 rom before selling the device after the summer and buy something new.
As usual, there's a lot of custom roms. Even with A12. Onestly I would prefer to focus on a specific rom avoiding to try all the possibilities, this phone is my daily driver at the moment.
So I can see CrDroid, Evolution, Aosp, Voltage, Arrow... etc etc. Maybe seems a newbie question but which could be not a best rom but the first one to be tried ? Mainly I'm using the X3 to make call ( of course ), surf the web ( of course ), take photos to my children ( so the quality is very important for me ) and use it for GPS ( Mapy CZ and Here Maps ). With an eye on the battery duration...
Which A12 rom could be a good initial attempt ? Not so hard to be installed, I don't want to spend hours in bootloops or issues eheheh.
PYCON said:
Hi guys,
after almost 2 years with MIUI, Android 10 and Android 11 with MIUI 12.5, I would like to try a custom Android 12 rom before selling the device after the summer and buy something new.
As usual, there's a lot of custom roms. Even with A12. Onestly I would prefer to focus on a specific rom avoiding to try all the possibilities, this phone is my daily driver at the moment.
So I can see CrDroid, Evolution, Aosp, Voltage, Arrow... etc etc. Maybe seems a newbie question but which could be not a best rom but the first one to be tried ? Mainly I'm using the X3 to make call ( of course ), surf the web ( of course ), take photos to my children ( so the quality is very important for me ) and use it for GPS ( Mapy CZ and Here Maps ). With an eye on the battery duration...
Which A12 rom could be a good initial attempt ? Not so hard to be installed, I don't want to spend hours in bootloops or issues eheheh.
Click to expand...
Click to collapse
If you want something stable with good long-time support, there's only Lineage, ArrowOS and maybe AospExtended
If you take lot of photos, ArrowOS offers you unlimited storage in Google Photos. In Lineage you can add that feature using a Magisk module.
I went with ArrowOS for the unlimited photo storage and a few pixel features.
I have found a phone app that automatically records all calls and a Gcam that makes great photos.
Everything is better than MIUI really
On other phones, I was happy using AOSP Ext and CrDroid. What about this last one? I can start trying Arrow maybe...
PYCON said:
On other phones, I was happy using AOSP Ext and CrDroid. What about this last one? I can start trying Arrow maybe...
Click to expand...
Click to collapse
CrDroid should be good as well.
The developer made a break of 2 - 3 because he gave the phone to his wife but now it continues to receive regular updates.
Noter2017 said:
If you want something stable with good long-time support, there's only Lineage, ArrowOS and maybe AospExtended
If you take lot of photos, ArrowOS offers you unlimited storage in Google Photos. In Lineage you can add that feature using a Magisk module.
I went with ArrowOS for the unlimited photo storage and a few pixel features.
I have found a phone app that automatically records all calls and a Gcam that makes great photos.
Everything is better than MIUI really
Click to expand...
Click to collapse
Could you provide the name of that phone app that records calls and gcam which makes great photos?
I am looking for exactly the same thing as the op. Right now on stock but it is so sloow
no1geek said:
Could you provide the name of that phone app that records calls and gcam which makes great photos?
I am looking for exactly the same thing as the op. Right now on stock but it is so sloow
Click to expand...
Click to collapse
Here you go
Mod Edit: Link Removed
AOSP dialer has to be installed in Magisk.
GPay SQLiteFix is a fix to make Google pay work, has to be flashed in Magisk as well.
After installing Aspen (GCam mod) create a folder called ConfigsSettings8 on your phone's storage and paste the aspen2.xml there.
Start Aspen, double click on the black area of the screen and select aspen2.xml
@Noter2017: I'm curious here about your setup, so a few questions?
Is Bluetooth working alright with external audio devices?
Does GPS work reliably?
Is general wireless connectivity stable?
Can advanced reboot be enabled easily?
Is button navigation possible and can buttons be reversed?
I see you have Magisk, so no questions about rooting...
pnin said:
@Noter2017: I'm curious here about your setup, so a few questions?
Is Bluetooth working alright with external audio devices?
Does GPS work reliably?
Is general wireless connectivity stable?
Can advanced reboot be enabled easily?
Is button navigation possible and can buttons be reversed?
I see you have Magisk, so no questions about rooting...
Click to expand...
Click to collapse
1) Bluetooth works fine for me. I use it with my Mi Band and a portable speaker. Personally I never had problems with Bluetooth, no matter which ROM I used.
2) I use GPS on a daily basis and it also works.
3) Works. With a speedtest get 400 Mbps on my 5 GHz WiFi at home (1 Gbps cable).
4) Can be enabled in Settings - Gestures
5) I use button navigation and didn't face any problems. You can revert the layout in Settings - Gestures - System navigation
Only problem I face after moving to ArrowOS 12.1 was that some backups made with Migrate didn't work. A few apps would crash immediately (Tailscale, for example) after starting (had to clear storage), my taxi app asked to verify my credit card again which didn't work. Had to remove and add the same card again.
Also customization is pretty much absent which might be a problem for some people.
I had a long free weekend, so I decided to spend a few hours upgrading. If the ArrowOS wouldn't have worked reliably, I would have changed ROMs to something else. ArrowOS 12 is EOL and I will stick with ArrowOS 12.1 till the end of the year. Really getting too old to do clean flashes all the time
I think CrDroid 12 (8.4) is superior. I use it with ANXcamera and Magisk