Database Develop

[Q] SuperSU - Losing root every few minutes?

Hi,
I'm not sure if I'll explain this properly but here it goes:
Phone: AT&T HTC One
ROM/OS: GPE 4.3 (this one - link)
SuperSU Version: 1.65. I updated from the 1.51 on the ROM because I was getting 'binary needs updating' messages and it would never update.
Issue:
I have apps like QuickBoot and SnapCapture[Root] that seem to only work for a few minutes after initially opening the app (I see a small popup on the screen that states "*App* has been granted superuser permissions for an interactive shell"). After like 10 minutes, without a prompt, that access goes away. In the case of SnapCapture, it no longer captures my SnapChats. I need to manually go back into the app and it'll re-grant root access for another period of time.
How do I get SuperSU to give permanent root access so long as the phone is on?
Is this because the OS is killing the SnapCapture process?
Any help would be appreciated. Thanks!

Try SuperUser instead, version 1.0.2.1 by Koush Dutta and see if that makes any difference. If it works, uninstall SuperSU. Hope this helps.

Gr8man001 said:
Try SuperUser instead, version 1.0.2.1 by Koush Dutta and see if that makes any difference. If it works, uninstall SuperSU. Hope this helps.
Click to expand...
Click to collapse
Thanks, I installed it via recovery and I am getting the "Install Superuser - The su binary is out of date" message. When I try to update it from within the app via the recovery method, it fails. "There was an error installing Superuser. Please send a log of the error to the developer."
Also, it removed SuperSU by itself? I got back on the phone and root was lost and SuperSU was gone.
So I tried running the .zip again and did see it mention that it was updating the armeabi binaries. I'm guessing those are different...
As soon as the phone starts up, it brings up the # notification icon to update the binaries.
I'm back on SuperSU for now...
EDIT: I installed via the APK (instead of the .zip recovery method) and it installed. When I opened Superuser, it prompted me to update and I just did install (not through recovery) and got a successful message. I then rebooted and SuperSU was still there. Google Play store prompted me to update Superuser so I did. When I opened it post update, I was back to the beginning of this post.
I'm back on SuperSU yet again...

Check out the following thread:
http://forum.xda-developers.com/showthread.php?t=1538053
I also have a flashable zip that has always worked for me,
Not my creation but can't find the post where I downloaded from. If you send me your email, I can send you the zip file.Good luck.
---------- Post added at 11:12 PM ---------- Previous post was at 11:08 PM ----------
Also make sure busybox is installed and uptodate.

Gr8man001 said:
Check out the following thread:
http://forum.xda-developers.com/showthread.php?t=1538053
I also have a flashable zip that has always worked for me,
Not my creation but can't find the post where I downloaded from. If you send me your email, I can send you the zip file.Good luck.
---------- Post added at 11:12 PM ---------- Previous post was at 11:08 PM ----------
Also make sure busybox is installed and uptodate.
Click to expand...
Click to collapse
Thanks.
I had BusyBox 1.20.x installed but just updated to the latest. You think not having the latest BB is what was causing my apps to only gain root for 10 minutes at a time?
I'm on SuperSU 1.65 and the latest BusyBox now.

I think I fixed my own issue, for anyone that finds this. The problem was not with SuperSU or Superuser.
It was the fact that I have an application called 1Tap Cleaner installed which cleans my cache. I stumbled upon this by accident, but every time I clear the cache, and re-open the app, it would ask for root access. If I didn't, and re-opened, it was fine.
My cache was being cleaned every hour.

MultiROM Ubuntu Touch for Nexus 5 problems.

Hi guys,
I've been trying to install Ubuntu Touch to dual boot with Android on my Nexus 5, and I can't find any way to do it, even installing JUST Ubuntu Touch, it stucks on the Ubuntu splash screen. My only solutikn now is MultiROM, but I tried almost every channel available in there and none works. It all gives the same result: After selecting Ubuntu Touch option from the MultiROM boot menu, it reboots to the Google screen(I was expecting that it would boot into Ubuntu Touch). But after that, the screen goes black for a few seconds and reboots into the MultiROM boot manager again. Any solution for this is appreciated. I'm sorry I couldn't be more specific.

Me too. Can anybody find a solation?
Sent from my HAMMERHEAD

Same problem.....
Sent from my Nexus 5 using XDA-Developers mobile app

Matrixians 14 said:
Hi guys,
I've been trying to install Ubuntu Touch to dual boot with Android on my Nexus 5, and I can't find any way to do it, even installing JUST Ubuntu Touch, it stucks on the Ubuntu splash screen. My only solutikn now is MultiROM, but I tried almost every channel available in there and none works. It all gives the same result: After selecting Ubuntu Touch option from the MultiROM boot menu, it reboots to the Google screen(I was expecting that it would boot into Ubuntu Touch). But after that, the screen goes black for a few seconds and reboots into the MultiROM boot manager again. Any solution for this is appreciated. I'm sorry I couldn't be more specific.
Click to expand...
Click to collapse
Have you used the build of multirom that switches the server to use the ubports builds instead?
I had the latest stable build from them, and hammerhead builds are more frequently updated.

Please send the links if possible. It would be highly appreciated.

Ubuntu Touch doesn't boot from MultiROM
Did this ever get solved? I have exactly the same problem. MultiROM to install Ubuntu Touch. Reboot, then bootloop at the Google screen until MultiROM intervenes.

marksentesy said:
Did this ever get solved? I have exactly the same problem. MultiROM to install Ubuntu Touch. Reboot, then bootloop at the Google screen until MultiROM intervenes.
Click to expand...
Click to collapse
I had the same issue. I found this post and am currently giving it a go. Use this apk though, as the other isn't signed.
I uninstalled the MultiRom app; went into recovery, and using the file manager, copied the modified 1.apk into /data/app/; I then went to /data/app/, clicked on it and chose the option chmod 644. I then followed his method. I'm currently downloading 'Stable' - 13.
Hopefully this helps.

Thanks... Finally installed UT on my nexus 5
Mini tuto
Install mod multiform apk
Once done follow instructions from multirom and install requires files. Your will Reboot.
Once reboot go to UT card
Select ubports-utoch ( flavor )
Then. Legacy
And version 1 ( for some reason I have problems installing the latest version )
When finish phone must reboot, select Legacy rom and enjoy.
P.S. Once UT is running go to settings and update to the latest version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:38 PM ----------
I had the same issue. I found this post and am currently giving it a go. Use this apk though, as the other isn't signed.
I uninstalled the MultiRom app; went into recovery, and using the file manager, copied the modified 1.apk into /data/app/; I then went to /data/app/, clicked on it and chose the option chmod 644. I then followed his method. I'm currently downloading 'Stable' - 13.
Hopefully this helps.
It is possible to mod multirom to install Plasma Mobile?
I already have Stock Android,Sailfish OS, and Ubuntu Touch...... ! and to complete happy need PM on my device.

Mod for Bacon
spoofykid said:
I had the same issue. I found this post and am currently giving it a go. Use this apk though, as the other isn't signed.
I uninstalled the MultiRom app; went into recovery, and using the file manager, copied the modified 1.apk into /data/app/; I then went to /data/app/, clicked on it and chose the option chmod 644. I then followed his method. I'm currently downloading 'Stable' - 13.
Hopefully this helps.
Click to expand...
Click to collapse
Can you mod this APK or create a new one for Oneplusone ( Bacon )
Work wonderful on N5, but on Bacon can't install UT, all version give errors.

Sharpie23 said:
Can you mod this APK or create a new one for Oneplusone ( Bacon )
Work wonderful on N5, but on Bacon can't install UT, all version give errors.
Click to expand...
Click to collapse
The Plasma Mobile website says multirom install is possible, however, I struggled to install it even on it's own. I may not have been able to install it in multirom due to my other roms being marshmellow, and the base rom for PM needing to be lollipop. I found PM too unusable to have as a daily driver, so I didn't try much harder.
Regarding your oneplus one, I'm no developer unfortunately; so best look towards the oneplus forums. This thread may be able to help you.
Good luck.

can i instal ubuntu in android 7.1.2 ? multirom ?

[MOD] Nougat_PlayStore_Rom_Addon_ADB_Install

Must Be on Nougat Rom!!!
I recommend Starting on freshly wiped rom but. This requires Package Disabler Pro Be Installed.
PlayStoreNougatMods.zip
Extract zip
Enable Usb Debugging
Disable Verify apps over USB
Enable all disabled apps
Plug phone into computer watch phone screen accept usb debugging key for computer
Run Install_PlayStore_Rom.bat
Follow Instruction On Cmd Screen
Once Install Is All Done
Select Pixel For Home Launcher
Open Settings/Application/Default Application under Calling Select Phone
Open Language and Input
Open Virtual Keyboards and click manage keyboards and turn on GBoard keyboard
Open Developer Options
Set Window Animation scale to .05x
Set Transition Animation scale to .05x
Set Animation Duration scale to .05x
Open settings goto accessibility
Enable all the servicesexcept talkback unless you want it
In settings open applications
Open applications manager
Goto menu select speciall access
In Phone Administrators enable all except android device manager unless you want that
Now click back button and open Draw over other apps and enable all
Click back button and open Modify system settings enable all
Click back button and open Notification access enable all
Open Rom Control and Everything Installed will be accessed there
Features
Pixel Dialer V8 With working Video Calling
Pixel Contacts
Google Camera
AOSP Browser
Google Messenger
Google Clock
Google Calculator
Call Recording Via BoldBeast
Rom Control Mods
DNS66 Ad Blocking
Status Bar Mod
Torchlight With Volume Buttons
Access To IMS Settings And Advanced Calling
Keylight Duration Settings
Battery Bar +
Status Bar Internet Speed
Recent Bar In Notification Panel
Button Remapping Via AIO Gestures
Volume Button Music Skip
Fingerprint Gesters
Led Control Via Light Flow App
Volume Panel Mod

View attachment 4048810View attachment 4048811View attachment 4048812View attachment 4048813View attachment 4048820View attachment 4048821

Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk

jonesj198 said:
Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Inquiring minds want to know

I guess you havent seen this thread https://forum.xda-developers.com/ve...din-stock-nougat-firmware-s7-edge-to-t3558313
It will work on stock beta 2 but I have the official tmobile nougat firmware working on our phones. Only thing that doesnt work is wifi calling and Visual Voice Mail but Volte and Video calling work. So you might want to look into that

Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Sent from my SM-G935V using Tapatalk

jonesj198 said:
Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Click to expand...
Click to collapse
Did you accept the adb key when prompted did it install anything

Here is the package disabler pro import script. You can also just istall all of the apks manually if you have to
View attachment PlayStore.zip

I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Sent from my SM-G935V using Tapatalk

jonesj198 said:
I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Click to expand...
Click to collapse
When you first start bat file does it show device as unauthorized

jrkruse said:
When you first start bat file does it show device as unauthorized
Click to expand...
Click to collapse
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Sent from my SM-G935V using Tapatalk

jonesj198 said:
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Here if you dont have those numbers before device its not recognized

Is usb debugging enabled and verify apps over usb disabled

Did you accept debugging key. If this never came up. In developer settings click revoke usb debugging the unplug and replug your phone into computet. If the below screen still doesnt come up start the bat file then it will pop up. Accept key close bat then reopen and start process

jonesj198 said:
Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Installing apps manually will work just fine. Then just copy the playstore.xml file from the zip of it I posted and import it with pacage disabler pro it should disable 126 packages

stud

Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.

CyanideHD said:
Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.
Click to expand...
Click to collapse
What build is your rom. Beta 2?

jrkruse said:
What build is your rom. Beta 2?
Click to expand...
Click to collapse
TMobile nougat.

CyanideHD said:
TMobile nougat.
Click to expand...
Click to collapse
If you have the rom control app open it under useful apps and open samsung info and tell me your csc version

CrDrooid Android 7.1 test

https://yadi.sk/d/aDqvPskH3EaeFX
Based on the 3.10 kernel... (for the first revision, Android 5.1) Beta-try, chase, complain, correct.))
The same Resurrection Remix with the system settings
Features and changes:
Very fast firmware in the likeness of Resurrection Remix
The latest source code for AOSP/LOS
Combines various features from LOS, RR, Paranoid Android, SlimRoms, OmniRom, etc.
Support Substratum Theme Engine
There is a good feature called LTE. It disables only voice calls and WIFI works.Not to be confused with airplane mode
Fixed Offline charging
Root is built-in is enabled in developer options
Gapps sewn.

So this is android 5.1 or 7.1 ? I'm willing to try it on my elephone M2.

NLSteve said:
So this is android 5.1 or 7.1 ? I'm willing to try it on my elephone M2.
Click to expand...
Click to collapse
7.1.1.

I have a problem installing this.
Update: I think the problem is I encrypted phone before installing this using 9x9 grid. I will decrypt phone and try again.
I used TWRP 2.8.7.3 (megthebest) -> install crDroidAndroid-7.1.1-20170223.zip
FAILED
Updating partition details...
...done
" E:Resource (image)-(background) failed to load "
E:Error executing updater binary in zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip
Click to expand...
Click to collapse
Error flashing zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip'
Updating partition details...
...done

NLSteve said:
I have a problem installing this.
Update: I think the problem is I encrypted phone before installing this using 9x9 grid. I will decrypt phone and try again.
I used TWRP 2.8.7.3 (megthebest) -> install crDroidAndroid-7.1.1-20170223.zip
FAILED
Error flashing zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
TWRP 3.0 It is necessary to use

update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar

NLSteve said:
update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar
Click to expand...
Click to collapse
What is it?

NLSteve said:
update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar
Click to expand...
Click to collapse
You tried to link to

duffi200000 said:
You tried to link to
Click to expand...
Click to collapse
yes. This is working download link for TWRP 3.0
---------- Post added at 01:53 PM ---------- Previous post was at 01:14 PM ----------
To get working Wi-Fi set country Wi-Fi region code to Europe or Germany that did the trick.
So far so good. Nice OS you have here. All good still runnning.
I'm noticing this OS is faster compared to cyanogen
Android 7.1.1 has issues with:
- Gboard keyboard disappearing when typing.
Solution: Install keyboard app like swiftkey.
- File transfers USB: files to Windows or Mac (MTP) does not work.
Solution: use transfer photo (PTP) and copy files to DCIM folder, later move files with an explorer app on the phone.
- No support for Xposed framework as of yet. Read latest post by Rovo89

NLSteve said:
yes. This is working download link for TWRP 3.0
---------- Post added at 01:53 PM ---------- Previous post was at 01:14 PM ----------
To get working Wi-Fi set country Wi-Fi region code to Europe or Germany that did the trick.
So far so good. Nice OS you have here. All good still runnning.
I'm noticing this OS is faster compared to cyanogen
Android 7.1.1 has issues with:56
- Gboard keyboard disappearing when typing.
Solution: Install keyboard app like swiftkey.
- File transfers USB: files to Windows or Mac (MTP) does not work.
Solution: use transfer photo (PTP) and copy files to DCIM folder, later move files with an explorer app on the phone.
- No support for Xposed framework as of yet. Read latest post by Rovo89
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=678045&st=5240#entry52552870
Try that, that's what I was able to set the phone to the computer, everything works fine. And Yes the firmware is still a test, but she's really smart, the problem with the camera can't decide

Thank you, I will try that for usb connection to computer.
This is a nice rom overall. @duffi : Did you find 56 issues? i see you added this to my text "Android 7.1.1 has issues with:56 "
If anyone needs advice or a step-by-step guide to install on elephone M2, feel free to ask!

Hi NLSteve,
can I get a step by step guide for install 7.1.1 on M2? I use 5.1 latest rom and I have root on the prhone.

How To Install CrDrooid Android 7.1 on Elephone M2
Make sure you save your contacts and essential info to SD card or computer.
If for any reason your phone is encrypted, change the unlock code to pin 4 numbers! if you use pattern larger than 3x3 or more complex pin you're screwed XD
For this guide, you will need:
Sp-flash-tool-v5-1648 (latest version)
TWRP M2 3.0 (megthebest)
CrDrooid Android 7.1
SR3-SuperSU-v2.79-SR3 (latest version)
Copy the ROM and supersu to External SD Card.
TWRP flashing with SP Flash Tool
1. Shut down your phone and Disconnect usb cable from pc.
3. Run SP Flash Tool and navigate to 3rd tab Download, load download agent MTK_AllInOne_DA.bin and load MT6753_Android_scatter-TWRP3.txt for your phone.
4. Only have recovery checked and keep the option Download Only.
5. Click Download button and connect your phone (which is off) with PC via USB cable. Process should start. After process (60 seconds or more) is finished you will see green circle on screen again. Unplug USB from phone.
6. Turn on by pressing Power and Volume +, hold for 10-20 seconds until boot into TWRP recovery mode.
Installing ROM
1. Go to Wipe. Go to Advanced Wipe. From here, tick the boxes next to Dalvik Cache, System, Data and Cache, then swipe the slider at the bottom to perform a full wipe.
2. Go back to Install and browse to the location where you saved the file and select the crDroidAndroid-7.1.1-20170223.zip file
3. When done tap Reboot to boot into Android.
4. After system done, shut down to recovery and install supersu.zip by browsing to the location of Supersu.zip and choose install.
This is it for now. Good luck!

Hi NLSteve, it works, Antutu 39965 Points. But camera is not working, Fingerprint is not working and Bluetooth is also not working, its flaky. Phone M2 works faster then stock ROM 5.1. What I do missing is the function for updates next time. Great work. Hall Sensor is also not working. Thx.

Hi @volobobo, sorry to hear to hear you miss many functions. For me the camera and bluetooth is working though. :S
Hall effect sensor is used to detect flip covers? I just use close proximity sensor on camera to turn off screen.

@NLSteve
NLSteve said:
Hi @volobobo, sorry to hear to hear you miss many functions. For me the camera and bluetooth is working though. :S
Hall effect sensor is used to detect flip covers? I just use close proximity sensor on camera to turn off screen.
Click to expand...
Click to collapse
Hi NLSteve, camera is really working? Bluetooth is also really working? I have paired with my bluetooth headphones. If so I will keep it a new try. Hall sensor was a misstake on M2, we have one proximity sensor.

Is SIM card working? My ports for other Phone works except sim card recognition.. Bad thing.. therefore I ask.. good to read that you make roms for the M2, which is not a current phone.
Gesendet von meinem SM-G900F mit Tapatalk

Ehy what about making an updated version?

What suprise - M2 isnt dead
Hi all,
since eragon give up because his broken phone, nothing is going forward with our M2,
always stuck on the old Android 5.
Now, we could make a jump to 7.1.
Only a test version by now, but nice to see, there are more options with this hardware.
Unfortunally, my camera changed from an resolution from 13 MP to 5,3 MP. The focus doesnt function (sharpness) in short distance under 50 centimeter.
I tried several camera apps in the last view days. But no one solved that problem.
I looked in the build.prop, but have really no idea, what i can do do rechange to 13 MP.
So, the camera is like dead, i cant get any acceptable pictures by now. :crying:
Have anybody an solution for this problem?
Thanks to all, spending so much time and energy, to keep this phone alive. :good:

Please anyone re-upload link.

[ROM][AOSP] Android 7.1 Nougat for Ouya

Android Open Source Project 7.1
Nougat
for
Ouya​
Install Ouya Boot Menu before using this ROM. If you are not using Ouya Boot Menu then your device will be bricked. Dead forever.
Introduction:
The Ouya system partition is too small for Android 7 Nougat. The system partition is 512MB. The cache partitions is 768MB. The cache partition is large enough for Android 7. This ROM switches the two partitions. It installs the OS on the cache partition. It uses the system partition as cache.
The custom TWRP also switches the system and cache partition. The physical cache partition is mounted to the /system directory. The physical system partition is mounted to the /cache directory. I've named the TWRP version with "-SxC" to denote the "System / Cache switch".
Ouya Boot Menu looks for the boot.img on the physical (512MB) system partition. This ROM is installed on the physical (768MB) cache partition. If you ever need to wipe the /cache directory in TWRP SxC then the physical 512MB system partition is wiped. You must copy "/system/boot.img" to the physical (512MB) system partition which is mounted at "/cache". This can be done with the TWRP file manager in Advanced > File Manager.​
Recovery:
TWRP-3.2.3-SxC is a modified recovery which does not support other ROMS because of the system/cache partition switch. Use CWM for other ROMS.​
Remember: Use Ouya Boot Menu or risk bricking the device.
Installation:
Install Ouya Boot Menu
Install and boot TWRP-3.2.3-0-SxC
Wipe System, Cache, Data
Install the ROM
Install UNOFFICIAL-Magisk-v19.1-ouya.zip
Optional: Install Open Gapps
Downloads
Donate
Change log:
Code:
20190510
- Enable adoptable storage.
- Try to set resolutions by default.
Source:
https://github.com/Decatf/android_kernel_boxer8_ouya
XDA:DevDB Information
Android 7.1 Nougat, ROM for the Ouya
Contributors
decatf
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Ouya Boot Menu
Based On: AOSP
Version Information
Status: Testing
Created 2019-05-06
Last Updated 2019-05-10

Display Resolution:
This ROM should be able to run at any resolution that a display panel reports to the Ouya. Some display panels don't report their resolutions properly. There is no way to add more resolutions.
This ROM (like AOSP 5.0 for Ouya) uses the closed source Nexus 7 display drivers. The stock Ouya drivers are too old, buggy, and don't work right on Android 7.
To set a display resolution on this ROM, use the persist.ouya.resolution system property. This must be set in /system/build.prop. Reboot the device to use the new resolution. Some of the display and resolution system properties that were used on older Ouya ROMs don't work on this driver.
Find out what resolutions a display panel is reporting to the Ouya:
Install Terminal Emulator for Android
Type cat /sys/class/graphics/fb0/modes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take note of which resolutions are supported by your display.
Edit the build.prop:
Install BuildProp Editor
Click the edit button
Change persist.ouya.resolution to a resolution supported by your display.
Click the save button.
Some display panels don't report their resolutions properly. The example I've shown is from a 1920x1200 DVI display panel but it doesn't report all of its resolutions properly. There is no way to add more resolutions.​
Display resolution system properties:
Use this:
Code:
persist.ouya.resolution
Do not use these. They don't work:
Code:
persist.tegra.hdmi.resolution
persist.sys.hdmi.overscan
persist.sys.hdmi.overscan.val

There is code to handle bcm4334 wifi for the Anthracite model. It is untested because I don't have one. Let me know if it works.

Can't get this installed, tried cwm trying mlq boot menu won't install fails on 2 different zip, then installs in twrp but doesn't launch all I get is a black screen can you step by step exactly the guide to this please been waiting forever to get 6+ on ouya now we have 7.1 and I can't load it?

Ok got it running but the picture is tiny I have a 1920x1080 50" Panasonic TV don't understand if not rooted how I edit this build prop please help???

Find out what resolutions a display panel is reporting to the Ouya:
Install Terminal Emulator for Android
Type cat /sys/class/graphics/fb0/modes
Take note of which resolutions are supported by your display.
Edit the build.prop:
Install BuildProp Editor
Click the edit button
Change persist.ouya.resolution to a resolution supported by your display.
Click the save button.

Thanks for this got to recipe it now via sideload in twrp, then build off the official ouya root it flash Cwm then boot menu then the os, got my work cut out although have the ouya update in platform tools now so that bits easy.
Let you know how I get on but a big thanks for the guide mate. ?

Ok so back in android 7.1 got terminal produce max of 1920x1080p 60hz but I get no root message in build prop editor and it doesn't show me a option to access persist.ouya resolution I've searched in build prop editor as shown but doesn't exist, so assuming it's due to no root yet???
Any idea how to root and what to do next please.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
---------- Post added at 10:37 PM ---------- Previous post was at 10:30 PM ----------
Ok figured it out but need root to edit it please, other question is do I add 60 after 1920x1080 to make it 60hz or simply put 1920x1080?
The main thing is getting root as lingo doesn't work for it on 7.1 so could you upload the zip if there is one to root the ouya on 7.1 Android please
Was able to adb pull but not adb push the build.prop file after editing in notepad++ in windows 10, it states read only file system, meaning has to be rooted i assume going around in circles waiting bricked it once rebuilt it 2-3 times allready trying 3 failed su zips online just can't understand it on a level to root it my self without a guide.

I think it's good had to load magisk after the 7.1 rom is allready installed not during install, basically load everything on get into the os, go back into the twrp recovery and reflash the provided ouya unofficial magisk zip and it is then in your apps it works as the root tool basically for those not knowing what it's for.
The prob is that it's still windowed in a tiny screen though after telling it to go 1920x1080 I'll try 1280x720 next and go through a lot I changed the dpi successfully though to 320 and writing is legable for now
UPDATE: changed the lot all different ways used changer apps to nothing modifies the screen size at all it's a panasonic tx-p50x50b 50 inch plasma 600hz with support for 720p and 1080p
Lowered the dpi again changed to 720p but still the same size screen it's not changing the resolution well frame size any way? May try a screen changer app hope it won't brick it?
So yeah I can change the density but not the resolution???????
---------- Post added at 02:48 AM ---------- Previous post was at 01:55 AM ----------
Then there was light, I finally figured it out, all I did was remove the # from line 57 before the word persist then placed the the cursor you write with that flashes behind the word persist hit delete until the word persist aligned to the hash above it in line 56 like this
And the finished result is awesome 1080p 60hz on a 50 inch tv, I'm getting a screen capture device soon hopefully so will then review it. For now I will be testing it as I'll be using it 24hrs a day pretty much it's cheap to run and now has full android 7.1.1 os wicked or what, it's been a long time coming and can't wait to test the functionality and compatability of the apps and games on it now, so for now peace out. Thanks to the op for all the help and making this possible.
Well I'm reinstalling ouya on it because I bricked it running xposed installer and the biggest problem no adoptive storage I can't install any games to internal storage not even dead trigger 2 it's too small storage, we need axposed to use any storage as internal via USB drives etc this has to be done before it's useable to be able to even install a game there needs to be some kind of work around for installation of large files sorry but as yet it's more or less unusable as a daily os for that one annoying reason, if you fix it can you let me well all of us know please.
I enabled it in developer options to install to external but every attempted install says no space available.

Uploaded a new version (aosp-7.1-ouya-20190510)
- Enables adoptable storage
- By default it will now try to pick a resolution so you probably don't need to set the system property anymore.

PHYSC-1 said:
Ok so back in android 7.1 got terminal produce max of 1920x1080p 60hz but I get no root message in build prop editor and it doesn't show me a option to access persist.ouya resolution I've searched in build prop editor as shown but doesn't exist, so assuming it's due to no root yet???
Any idea how to root and what to do next please.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
---------- Post added at 10:37 PM ---------- Previous post was at 10:30 PM ----------
Ok figured it out but need root to edit it please, other question is do I add 60 after 1920x1080 to make it 60hz or simply put 1920x1080?
The main thing is getting root as lingo doesn't work for it on 7.1 so could you upload the zip if there is one to root the ouya on 7.1 Android please
Was able to adb pull but not adb push the build.prop file after editing in notepad++ in windows 10, it states read only file system, meaning has to be rooted i assume going around in circles waiting bricked it once rebuilt it 2-3 times allready trying 3 failed su zips online just can't understand it on a level to root it my self without a guide.
Click to expand...
Click to collapse
decatf said:
Uploaded a new version (aosp-7.1-ouya-20190510)
- Enables adoptable storage
- By default it will now try to pick a resolution so you probably don't need to set the system property anymore.
Click to expand...
Click to collapse
WOW!!! your amazing putting it on right now I'll be getting that screen capture device, I might tweak it with classicboy as been researching it all, add some favourite apks take some less required ones for me out and I'll drop it, might try making some custom backgrounds and that sort of thing it may take me a while I'll use some canva tweaks to do it with let you have the link when done, but major thanks for this everyone should have 7.1 ouya's soon then lol. Over the moon mate. :angel:
---------- Post added at 12:27 AM ---------- Previous post was at 12:23 AM ----------
I ironically just went to attempt adding apks to it like xposed etc and found it wondered what it was and came here to find the followup, so what I'll do is make it a little more custom none basic android looking if I can make some canva images for backgrounds and add in some games and so on in the apps folder and so on and so forth see if I can make an app after to link to the ouya games available onine I'll make that simple. that's if I can knock one up it will be a seriously grueling task finding multiple game links and cataloging them in the app but it's on the cards now.
It should help keep the games for ouya available free online to be archived and added to as a list of page links, not sure how to make it so intricate but I will find a way I usually do.
Just found it's .da new folder not the normal type any idea or link to a extraction tool for windows to add apps and change the backgrounds etc then repack it please?

I'm getting MTP host hass stopped and MTP Host Keeps Crashing messages, it won't format on 2 differnt drive with two different caddies?
It only seems to be with hdd caddy's it does it over a usb hub
Ok now it works to the point of moving the data adoptively and say not enough space with any hard drive used?

" 6. Optional: Install Open Gapps"
Where GAPPS for this rom? All Gapps I put is writing a ERROR
PS: Sorry for my English

Romanych said:
" 6. Optional: Install Open Gapps"
Where GAPPS for this rom? All Gapps I put is writing a ERROR
PS: Sorry for my English
Click to expand...
Click to collapse
go to https://opengapps.org/
Choose
Platform: "ARM"
Android: "7.1"
Variant: Well as you prefer it, i prefer "Nano"
Worked fine for me
Good Luck

Wow, that's great. Any hope for Android TV Launcher? Does Kodi and/or Plex client work?
BTW, Ouya's services are going down soon. Just got a notification from them.

Hi,
First of all, thank you for your work! I am very happy to see OUYA being kept alive by the community!
In your ROM, is it necessary to make the flash ouya-keylayouts.zip that is used in the version of LineageOS KitKat?

Ok, I installed this ROM.
Apparently everything was right, but I had two problems:
1 - Bluetooth starts off at every boot and I need to use a mouse to turn it on before using the OUYA controller.
2 - The controller of OUYA is, as I say, very unstable. If I try to move the cursor using the d-pad, it keeps moving to the right. I installed Kodi 18.2 and can not choose the options using the driver. I switched to another bluetooth controller, an Ipega-9028, but the problem persisted.

I've installed the ROM and it seems to work pretty well but has anyone got Kodi working with this? I can get it installed and I try to play a movie and it just freezes every time which is driving me crazy any ideas?
Cheers
Ok so I have now tried Netflix and it froze and required a hard power off to get it back so I don't think it is me doing something wrong, is there any chance this is something you are aware of as it would be great to be able to use Netflix and Kodi on this device again?

I am also suffering from the Bluetooth not enabled on start-up. Everything else works just fine.
Netflix and Kodi both work for me, maybe try and wipe/reinstall the rom?

swindillon said:
I am also suffering from the Bluetooth not enabled on start-up. Everything else works just fine.
Netflix and Kodi both work for me, maybe try and wipe/reinstall the rom?
Click to expand...
Click to collapse
Well I can try but I have tried this on Two different Ouya's and it seems to have done the same thing, I will give it another go.
Cheers