I'm having issues with DPI change, I used ADB to change the DPI using a simple adb shell wm density 460 && adb reboot, all good, only issue is a few things are.. weird.. For instance the "top apps" icon, little blue thinggy in the playstore is awkwardly big, it's larger then the font, but I didn't use the phone stock so I don't know if that's just how marshmallow is or if that's a dpi problem. I also noticed when loading The Sims FreePlay, the EA boot logo it extremely over scanned, the letters EA barely fit on the screen, the eBay app, the user display picture is cut off and only shows the bottom right corner on an icon that's huge and again over sized, as well as snapchat sending all of my snaps with extremely small font, yet on my screen before sending they look just fine.
So after looking into this further, the build.prop was never changed, it still says dpi 560, but I know for system files I need to mount /system in order to write to it without root. So I booted to recovery as that allows me write access to system, mounted system, says mounted /system at the bottom of the log, open adb, run adb devices, nothing comes up, it's not found, reboot phone, run adb devices, works fine. What's the deal? I can't get the 6p to work from recovery when mounting /system, it says it's mounted but on the computer end nothing is happening.
I also want to keep this phone as stock as possible, kind of a purist douche bag like that so I don't want to run TWRP, or at least I'm not committed to this DPI change being this important that I want a custom recovery.
So, anyone have any idea why I can't mount /system in the stock recovery? or rather, why I can mount it but why it's not working?
After a lot more work I found out I can't even mount /system without root. So I'm back to square one with the completely stock phone, and changing dpi. Does anyone know how to fix this?
I'll post pictures of the over sized icons. I'm not sure why it's happening, normally it would go the other way, it's almost as if anything lower then DPI 560 puts the phone into a table-esk ui preference so the icons go much bigger. all through it doesn't help at all when changing the dpi even smaller. I've gone to DPI 400 and a few random things screw up every time, I even tried dpi 540 and as soon as I go any lower then 560, the keyboard instantly goes huge, editors choice icons don't fit, and the profile pictures are random apps don't fit. There are also quite a few other issues I can't remember, I didn't sleep well, mind fading.. Anyway, it's more of an annoyance, a lot of apps don't actually work when the DPI is changed, and like mentioned in the first post, I'm not looking to root as a solution, mostly because the latest snapchat updates look for superuser access and block rooted devices.
This is actually why I bought the Nexus 6p was so I don't need root to get the clean AOSP look I wanted with a small but organised DPI that fits everything perfectly to use the most out of the larger screen on my old Note 4 (460 DPI, Google Music icons at the bottom for play, thumbs up or down and skipping tracks are all perfectly spaced apart), but after kernel issues with Samsung blocking root with 5.1.1 and then custom kernels and blah blah blah, I finally got Android 5.1.1 working with root, and then I find out snapchat blocked root so I went out that night and bought a Nexus 6p, now it's looking like I'm going to need root to get a proper DPI change unless someone has found a work around or maybe a DPI that doesn't trigger the UI to glitch out with those massive icons and keyboard. (just pointing out it's not all keyboards, it's just some of them, swiftkey the whole thing is huge, ginger keyboard only the suggested word box is huge, I also use an aftermarket keyboard because emoji is disabled in Marshmallow for anything other then sms apps, so I can't use emoji's in snapchat or instagram with the stock google keyboard)
This is when I try to use SwiftKey Keyboard
{
"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"
}
The editors choice icons are oversized and don't fit
Profile pictures on a few random apps (ebay app shown) are all over sized with a tiny photo inside off to the top left corner
flash TWRP then mount /system from within TWRP, then try using ADB, as far as I know stock recoveries never had adb enabled fully, only adb sideload. once you're done flash the stock recovery back.
Related
If you edit local.prop in /data/ to include the line "ro.sf.lcd_density=XXX" you can set the density size on boot without having to run an app or do a restart every time. Put whatever numbers you want for XXX, 160 is default and the higher the number the bigger the screen items will be. I personally like 120.
This works well with the button_bar off trick to make the notification bar the usual size while still having the buttons up top. Plus it lets you fit another 4 or so apps on the Zeam launcher bar.
{
"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"
}
I'm curious how this might affect the crappy way the archos uses wallpaper? (cutting off the bottom of of the wallpaper) Would this change the way the wallpaper is scaled?
To be honest I'm not sure if it would actually shift the wallpaper or if that is independent of the lcd density settings, but either way it won't fix the archos wallpaper issue. If you see an actual image of what a picture would have to look like for the archos to make it "fullscreen" you'd see that proportionately zooming out won't work.
http://forum.archosfans.com/viewtopic.php?f=74&t=46103&start=0
Your best bet for that is the multipicture app as much as it sucks to have to run an app just for wallpaper.
Yeah I know, I hate that damn app. Stationary wallpaper. Bleah. My favorite thing is to have scrolling wallpaper. I'm learning how to re proportion the wallpaper. I was hoping that might fix some of it. Oh well. I actually like crop wallpaper better. Just cuz I can still get my scroll on lol
p0rk burn said:
If you edit build.prop in /system/ to include the line "ro.sf.lcd_density=XXX" you can set the density size on boot without having to run an app or do a restart every time. Put whatever numbers you want for XXX, 160 is default and the higher the number the bigger the screen items will be. I personally like 120.
This works well with the button_bar off trick in local.prop to make the notification bar the usual size while still having the buttons up top. Plus it lets you fit another 4 or so apps on the Zeam launcher bar.
View attachment 530219
Click to expand...
Click to collapse
What code did you use to get the menu buttons of the top bar? how can that be done?
Cuzz Face said:
What code did you use to get the menu buttons of the top bar? how can that be done?
Click to expand...
Click to collapse
Courtesy of Jerry101 and this thread: http://forum.xda-developers.com/showthread.php?t=940198
"root gen8
create a file "local.prop" at /data/
add follow line.
ro.board.has_buttonbar=no"
You need root, obviously, and should install button savior. Do that and give it a shot, worst case scenario is you just delete the two "ro" lines from build.prop and local.prop and you are back to normal.
How where you able to edit the build.prod in the system fs.
I'm logged in as root but it keeps saying readonly file.
Please advice...
Try copying it to somewhere else, add the line, and paste it back in and replacing the old one.
That's not making any difference.
I su to root, superuser grants me root rights, but chmod, editing with vi, cp to /tmp edit en pasting back does not work.
Any other ideas?
Are you rebooting after you are done? To be honest, I copied it into my dropbox folder with root explorer, edited it on my linux box, threw it back in dropbox, and moved it back into /system/, but it shouldn't matter doing it another way.
In the market there are file explorers that grant root privileges. This should help you write and delete in /system/. Just remember to go into settings in the explorer and enable the root options.
XDA ICE GLACIER - THEMED / Never stock
I already have root explorer on my device, I will try this in the morning.
I tried to do it in a terminal emulator but that's what giving me te problems.
So, I tried using another file manager, but writing in the system fs is not going to happen on my archos 101.
Just to be clear I'm running the out of the box firmware/kernel that I rooted with Archangel.
When I get a chance I will start from scratch and note my steps to do this. If that doesn't work it would have to be something to do with archangel, i guess. By chance, you aren't in RO mode are you?
Just know I'm not blowing you off but it might be a day or two. I have a horrible feeling (in my mouth) I need a root canal.
p0rk burn said:
When I get a chance I will start from scratch and note my steps to do this. If that doesn't work it would have to be something to do with archangel, i guess. By chance, you aren't in RO mode are you?
Just know I'm not blowing you off but it might be a day or two. I have a horrible feeling (in my mouth) I need a root canal.
Click to expand...
Click to collapse
Good luck at the dentist , I will keep my eye on this thread.
Archos 70it, rooted with Archangel
I just added the line "ro.sf.lcd_density=130" to the the file "local.prop" at /data/ (tanks to Jerry101) after the line ro.board.has_buttonbar=no".
It is working like a charm.
All the best
starsee said:
Archos 70it, rooted with Archangel
I just added the line "ro.sf.lcd_density=130" to the the file "local.prop" at /data/ (tanks to Jerry101) after the line ro.board.has_buttonbar=no".
It is working like a charm.
All the best
Click to expand...
Click to collapse
I think you mean build.prop in /system/ ...?
zebrapad said:
I think you mean build.prop in /system/ ...?
Click to expand...
Click to collapse
Nope /data/local.prop does the trick. No need to change build.prop.
right,
follow jerry101 at "http://forum.xda-developers.com/showthread.php?t=940198" and add this line "ro.sf.lcd_density=130" to "local.prop" at /data/.
Cool, glad that you guys got it working but I did it using the build.prop on my 101. Odd.
Regardless, I'll edit the first post since local.prop works.
Originally posted in TMO Note 4, but it should work for your variant too
If you notice anything missing or you use an app I don't and would like it added jut let me know
OK, so I love changing the DPI of my phone and apps. so i thought why not share what I know with others.
These are the apps that I feel are needed to be changed , so if you think i missed one just tell me and I'll add it.
another note i don't use the touchwiz launcher and different roms can use one that's modded.
of course your phone needs to be ROOTED
you can use whatever app you like to change your DPI, I used xposed app settings and would suggest the same
NOTE 4 default DPI is 640
In xposed app settings to change your system DPI you turn on
android system & system ui
and change it to your desired DPI (320 for me).
(you can also change it using the build.prop)
I guess its necessary to say this:
IF YOU CHANGE YOUR DPI IN ANY WAY, DO AS STATED BELOW
These apps you will need to change back to stock: 640
camera
camera test
com.sec.android.gallery3d.panorama360view
com.sec.android.ofviewer
com.sec.android.sviewcover
com.sec.phone
contacts
gallery
incallui
com.android.mms
phone
photo studio
s health
samsung camera filter
touchwiz home
video trimmer
not changing some can cause it to not function properly or FC
These setting are recommended if you use them:
S-Voice
- you don't have to change the dpi to stock unless you want to but if you get a FC change the screen dp to 480x854
Samsung Keyboard
- you can leave it the same as your new DPI or change it to stock DPI if the secondary icons alignment bothers you, check the box 'apply res to widgets',
Lockscreen (com.android.keyguard)
- you don't have to change this one back to stock but if you use lockscreen security the bottom will look weird
- to change it to stock, enter the stock DPI (640) and check the box 'apply res to widgets'. A reboot will be requried
Smart Remote
-change dpi back to stock and change screen dp to 320x480
Calendar
-if you use it I recommend you change it back to stock because the on screen notification size will be off
Wink app
-it will think your using a tablet and causes issues so change to stock
Swiftkey
-resize using keyboards builtin resizer
PLEASE DON'T FORGET TO HIT SAVE ON EACH ONE AND REBOOT YOUR PHONE AFTER
IF I MISSED ANYTHING OR YOU WANT ANYTHING ADDED PLEASE TELL ME
THIS ARE MY PERSONAL SETTINGS AND IF YOU CHOOSE TO DO THE SAME ITS AT YOU OWN FREE WILL
{
"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"
}
The title/subject probably needs changing as it has nothing to do with what's in the post.
Disable lockscreen on trusted connection vs changing DPI.
_Dennis_ said:
The title/subject probably needs changing as it has nothing to do with what's in the post.
Disable lockscreen on trusted connection vs changing DPI.
Click to expand...
Click to collapse
I feel stupid, i put the wrong title.. auto input lmao
thanks for catching that, was gonna post a thread for that title too but today. working and posting lol
lockscreen on trusted connection link:.. http://forum.xda-developers.com/note-4-sprint/general/disable-lockscreen-security-connected-t3016459
I hate the stock DPI on this phone but I changed it using build.prop as I'm trying detox from using xposed. I want to be able to jump to lollipop right away and must pull myself away from the xposed tit since I don't see it coming to lollipop. Only issue I had changing it in build.prop is with camera. Didn't FC just didn't fill phone screen obviously. So I'll just use google camera for now. Boy do I miss that xposed though......
Sent from my SM-N910P using XDA Free mobile app
egodriver07 said:
I hate the stock DPI on this phone but I changed it using build.prop as I'm trying detox from using xposed. I want to be able to jump to lollipop right away and must pull myself away from the xposed tit since I don't see it coming to lollipop. Only issue I had changing it in build.prop is with camera. Didn't FC just didn't fill phone screen obviously. So I'll just use google camera for now. Boy do I miss that xposed though......
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
IMHO, lollipop is not worth it. Xposed is just too good and useful. I'm personally staying on Kitkat until Xposed comes to lollipop. And if it doesn't, then I'm not getting lollipop until I'm forced to with my next phone... in at least a year
Not sure why it took me this long to look into but this can be easily changed with a simple ADB command without root. This was my only concern for not having root access and I feel flat out dumb for not looking this up sooner. @PizzaSauce has a write up over in the Note 4 forums. This is a simpler install with a Motorola driver version.
1. Download and install the minimal ADB and Fastboot tool
2. Download and install the Motorola Drivers
3. Navigate to adb (Commonly in the C:// drive)
4. Hold shift and right click - "Open Command Window Here"
5. Ensure that you have enabled USB Debugging in the developer section of settings
6. On your phone, mark that you trust the computer
7. in the command window run the following command but replace *** with the desired DPI (Default is 640)
adb shell wm density ***
8. Reboot your phone for the changes to take place.
Issues I've Encountered at ALL DPI's:
- Instagram will not allow for proper cropping of pictures (Dealbreaker)
- Moto Display icons are fuzzy and or mislocated
- Random "tearing" of certain UI elements (seldom and not very noticeable)
Have fun and report back which DPI you like best!
Greetings!
I don't have the Note anymore but I do have a Turbo now, hopefully people can get some use out of this 2k screen now!
Hi!
I'm using native for Moto Maxx screen dpi (565), it's make icons and my swype keyboard more clearly.
To fix issue with Moto Display you need root and Xposed Framework installed, then set Moto Display DPI to 640 in App Settings module.
What is the benefit of messing with the DPI setting?
BlueWRXPride said:
What is the benefit of messing with the DPI setting?
Click to expand...
Click to collapse
Added screen real estate! Think of lowering the DPI as increasing the resolution on your monitor. Because our screens are so high resolution lowering the DPI won't affect clarity at all like it used to on qHD and below screens.
Comparison I found online...
{
"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"
}
Have any screenshots @ the new DPI?
Cobra04 said:
Have any screenshots @ the new DPI?
Click to expand...
Click to collapse
I didn't take any. Had to revert back to default. Instagram won't let you crop photos correctly with this method.
http://forum.xda-developers.com/droid-turbo/help/changing-wm-density-results-off-t3014610
Thread related.
if any mod could merge these two threads and move it to droid turbo development should be great.
avathar.noir said:
Hi!
I'm using native for Moto Maxx screen dpi (565), it's make icons and my swype keyboard more clearly.
To fix issue with Moto Display you need root and Xposed Framework installed, then set Moto Display DPI to 640 in App Settings module.
Click to expand...
Click to collapse
Native PPI is for our display is 565.
Factory (stock) DPI for Quarks displays is 640. Don't confuse the two terms.
PPI is hardware based and cannot be changed. The PPI is what the screen is manufactured with.
DPI is a software-based resolution spec and can be changed, but I don't like to do it. Some apps will not behave properly with lower than factory DPI.
there is an other way, no need computer:
1. install sunshire and run temp root
2. install resolution changer
3. Change resolution and DPI like the way u want
4. Restart your phone
ChazzMatt said:
Native PPI is for our display is 565.
Factory (stock) DPI for Quarks displays is 640. Don't confuse the two terms.
PPI is hardware based and cannot be changed. The PPI is what the screen is manufactured with.
DPI is a software-based resolution spec and can be changed, but I don't like to do it. Some apps will not behave properly with lower than factory DPI.
Click to expand...
Click to collapse
This thread is a year old.
Arthas92 said:
there is an other way, no need computer:
1. install sunshire and run temp root
2. install resolution changer
3. Change resolution and DPI like the way u want
4. Restart your phone
Click to expand...
Click to collapse
This is how to do it without root.
Aravindtop said:
This thread is a year old.
This is how to do it without root.
Click to expand...
Click to collapse
Yes, but people are still confusing hardware built in PPI (565) with factory DPI (640). Just wanted to set the record straight.
Hello,
Why reduce android screen resolution ?
- Reduce battery consumption of your xperia
- Increase game performances
Before starting, make sure that your device is rooted and download the next application : Screen Shift.
Note that the configuration described is especially for Xperia Z. If you use these values for other device, it will not work properly.
Instructions :
1. Install Screen Shift app
2. Give it root access
3. Change the resolution by type these values : 720 x 1280
4. Change "Density" value and type : 294
5. Activate the profil et and accept.
6. Reboot your device.
Your resolution is now in HD. It's normal that your icons are bigger than before. Sony's launcher has not been designed for that resolution. I purpose you to install Google Now Launcher if you want a clear interface without big icons.
Credit to aravindsagar
You should mention that some app after changing resolution can behave weird and draw part of their graphic in some weird way, the same with games, for example Minecraft PE, and Sudoku(only games that I have beside VR for goggles) look really weird one buttons are big other out of screen.
I always change DPI and res on devices, and I would recommend to do this after clean installation or before installing any major app.
Im not saying that its always like that but Im doing this for longer time and its just annoying sometimes when its happen, so be prepare for that.
Akinaro said:
You should mention that some app after changing resolution can behave weird and draw part of their graphic in some weird way, the same with games, for example Minecraft PE, and Sudoku(only games that I have beside VR for goggles) look really weird one buttons are big other out of screen.
I always change DPI and res on devices, and I would recommend to do this after clean installation or before installing any major app.
Im not saying that its always like that but Im doing this for longer time and its just annoying sometimes when its happen, so be prepare for that.
Click to expand...
Click to collapse
Thank for answering.
If you change only the resolution and not change the density, then your message is true.
It's important to change your density. The value depends of :
- your device screen size
- the default resolution
- the default dpi
The configuration that i described in first post is especially for xperia z.
Well yes, but some people, like me just hate this ugly big default DPI like all of new phones have, and for most of time I set DPI to smaller so I can fit more in it without making text too small
for example this is default 480 DPI and 360 that I use. It not only look better but text still look good on it.
{
"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"
}
For me DPI and res should be option in setting and every user should set it own like he want, because for now only real reason why I root my phone is because f that DPI... funny as hell...
What if we manually change the dpi by terminal or in built feature in custom rom ?
Maybe you'll find my question moronic but is it possible to restore default settings with the same tool? How, and what are they? I mean, what values of resolution and DPI are default ones?
Most of those apps have restore or backup option for restoring DPI.
DPI can be changed by any file manager with access to root, or any app that have option to change build.prop(like kernel adiutor) or DPI(custom rooms or aroma installer option)
you can manually change/revert DPI just by changing line ""ro.sf.lcd_density="" in bulid.prop file in system folder. Just make sure that after editing in properties of that file you have permissions rw- r-- r--
And of course make copy of this file just as a backup
The mad catz mojo is a powerfull little beast really even now it has a bit of kick for a tv box, the graphics are very good as are all tegra chips for each era. I got around to flashing the custom rom to mine of cyanogenmod 12.1 unofficial and before that clearly rooted and flashed a recovery twrp 2.8.2.0.
Any way here are some findings I had while playing since yesterday
Cons
1. The inbuilt browser works well until at some awkward moments cripples up and falls over, but when working 98% of the time is great, it can be remedied easily with alternate browsers none of which I have tried yet.
2. Screen recorders Just don't function on the mojo generaly being denied install or just plain don't work the choice is minimalistic at best.
3. Once you have flased this you can't go bck without an official rom backup before flashing
4. I have what I now called the blink of death in this rom twice now, once from installing legit screen recording software and secondly from trying root cleaner, what happens here is that it begins flashing on the screen and bizzare pop up messages about closed services appear, this was nothing to do with ay recognized ult here justmaybe chnges in bacground functions or file system that caused an irrevertable loop of blinkmessage blink itermitant screen with the pop ups, also at that stage trying to do a factory reset is futile, what I did was end up clicking in settings which ran well some options so I chose backup reset and then tried erase everything it went into the splash screen for the twrp menu and blinked like the desktop within android was doing, so I simply reflashed just the recovery then wiped and reinstalled the rom from a sd card and back to fresh os it was. In the time inside the os before fthe blink of death lol I basically changed the launcher at one point it kept stable for a while all activities and function enabled, so after a fresh recovery and rom flash I then added the Launcher<3 from the play store immediately and ever since it's perfect in the no blink of death senario.
UPDATE TO BLINK OF DEATH NEW FIX
So far this is working as a fix as the blink of death came back turn off google app otherwise known as google search in settings/apps click google and then disable and leave it this way prevents so far this problem for me using it a full day without the return of the endless blink of death! :laugh:
5. There is serious incompatability with the controller with this mad catz mojo android console unit although a lot work a lot don't making the amount of general controller supported games that should normaly be working from the google play store reduce compared to increase with what it should work with especially as mad catz make peripherals and had done for ages before making the mojo very confusing why it's not spot on for compatability there???
The silver lining gaming wise with the custom cm12.1 is the ability to install miles more games than before shame only a fraction work with this system and controller combo though [email protected] mapping it's some laborious [email protected] and quite technical for a none user or newbie. But if anyone wants to add to this later a really layman easy guide to mapping on android for various controllers please do so as it's none existent on youtube where it laymans that.
PRO'S
1. Stylish sleek and pretty rapid when in full working state
2. Way more play store compatability
3. Found a screen recorder that actually works below:
http://www.scr-screen-recorder.com/
you should use v1.0.5
Set the settings from the same as in the images below:
{
"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"
}
4. The GL to SD app still works with this custom firmware so you can transfer at least some games to an external usb hard drive but not all work that way.
5. You can install ouya everywhere on your cm12.1 mojo just download the ouya everywhere 4 apks from this thread page https://forum.xda-developers.com/ouya/general/sideload-ouya-store-android-device-t2812860/page6 and install them 1 by one in your ouya, afterwards reboot and a pop up message asking which launcher to use appears,.
Click the trbouchet launcher and choose allways, from now on click the ouya icon orange ouya shortcut to run ouya everwhere like on the custom rom, first time use requires either account setup for free choose skip if not using a credit card or payment option. And your in ouya back just like before.
6. This custom firmware is pre-rooted and is a flashable zip for use in twrp
And my final verdict 7.7 out of 10 on this rom had it had added usb app installing added some how maybe higher, but generaly better than being lumbered with stock 4.2.2 jelly bean yuck that jelly bean is one old sweet lol. It was probably the right flavor once lmfao.