{
"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"
}
Most smartphones on the market do not have Daydream compatability. This locks them out of the usage of all Daydream virtual reality content and the use of the Daydream headset. To change that this thread provides you with the following:
1. How to enable Daydream compatibility for any phone, with or without NFC
2. Unlocks Pixel exclusive apps available in the Play Store
Requirements
Installation
______Variant 1. Phones WITHOUT NFC
______Variant 2. Phones WITH NFC
Troubleshooting
______How to reset the installation
______In General
______Bugs + Fixes
Tests
______Devices/systems
______Apps
Credits
______Old thread
______Our team
______Code
______Feedback
1. Controller from a Daydream headset
2. Magisk rooted device
Magisk
3. Daydream app (Not from Play Store! - it will not work!)
Daydream
4. Daydream Keyboard
Daydream Keyboard
5. Daydream unlocker
Android 9 or below
(Use the resolution which is the closest to youre phone.)
Daydream unlocker
Android 10 Beta
Daydream unlocker
BEWARE! Setup Instructions have to be done in that exact order!
1. Install Daydream and Daydream Keyboard
2. Open Daydream
->follow the setup instructions
If you get a black screen, hear sounds, see a flat image.
-> Close daydream
-> Open daydream again
3. Enter VR mode
-> Continue until you see "Daydream is not compatible with youre phone"
4. Install Daydream unlocker (one of youre chosen Magisk modules)
5. Reboot
6. If youre phone does NOT have NFC ×
-> proceed to variant 1.
If youre phone DOES have NFC √
-> proceed to variant 2.
Variant 1. Phones WITHOUT NFC ×
1. Open Daydream
-> Settings
-> VR Settings
-> Setup everything in Troubleshooting
-> NFC (just ignore it), headset (Daydream or Daydream 2017), controller
2. NFC workaround
-> Open VR settings
-> Developer options
-> Enable "Skip VR entry scenes" (otherwise you will always be asked to enable NFC)
3. Enjoy
Variant 2. Phones WITH NFC √
1. Open Daydream
-> Enter VR Mode
-> Follow the setup
2. Enjoy
How to reset the installation
BEWARE! Setup Instructions have to be done in that exact order!
1. Delete Daydream
2. Open Play Store
-> Delete Google VR Services (Can be done with Titanium Backup too)
3. Deactivate Daydream unlocker (one of youre chosen Magisk modules)
4. Reboot
5. If youre phone does NOT have NFC
-> proceed to Variant 1.
If youre phone DOES have NFC
-> proceed to Variant 2.
In General
1. Bluetooth has to be enabled for the Daydream controller to work
2. If you open a Daydream app you have to switch in the VR settings the headset to Daydream, or you can not use the Daydream controller
-> Daydream app -> Daydream headset
-> Cardboard app -> Cardbord headset
You can open the VR settings when you open a VR app by touching the white gear symbol and select VR Settings, or in the Daydream app.
Bugs + Fixes
1. Drift issue (the screen turns slowly to the left when in vr mode)
-> Place the VR glasses with the phone inside on a flat surface for 10-30 seconds (recalibrates itselve).
2. If you did something wrong when trying to follow the install process
-> Follow the instructions of "How to reset the installation"
3. After some usage of Daydream apps suddenly Daydream apps wont work anymore or crash
-> Follow the instructions of "How to reset the installation"
4. Device ID change to Google Pixel causes some apps to not work anymore (OnePlus apps for example)
Reported by @bschmidy10
Fixes by @jigs4wkiller
-> 1. Only activate Daydream unlocker if you want to use it
-> 2. Or edit the OnePlus apps and remove device check from them
5. Distortions in VR, stagger/smear on the edges
Reported by @Kleva94, @pbergonzi
Fixes by @Kleva94
-> Try a module with a different resolution
6. After putting the phone in the headset Daydream crashes
Reported by @masoodsuliman - OnePlus 7 pro
-> Follow the instructions of "How to reset the installation"
7. I installed it twice and it does not work!
Reported by @masoodsuliman - OnePlus 7 pro
-> Follow the instructions of "How to reset the installation"
-> Still does not work? -> Try a different resolution
8. The Daydream app might crash if open a VR app inside of it
Reported by @masoodsuliman - OnePlus 7 pro
Fixes by @masoodsuliman - OnePlus 7 pro
-> If you open a VR app from the app drawer instead it might work (or it will just be Carboard mode instead)
9. After activating the module and restarting phone is lagging/freezing, getting past it hungs up or reboots the phone randomly, trebuchted crashes
Reported by @pflatlyne - Nexus 6 - Lineage OS
-> No fix found yet
10. Setup tells you to install VR keyboard but when trying says "Device is incompatible", any other Daydream apps are also shown as incompatible
Reported by @simon_6162 -OnePlus 7 - OxygenOS
Fixes by @simon_6162 - OnePlus 7 - OxygenOS
-> Open Settings
-> Apps & notifications
-> Daydream
-> Force stop/close it
-> Open storage, clear storage, clear cache
11. Other VR applications (example iVRy) rotate 90 degrees on some axis, some directions are inverted
Reported by @CombineCrab - OnePlus 7 pro
Fixes by @CombineCrab - OnePlus 7 pro
-> Disable the Daydream module
-> Reboot
12. Unity Instand preview app crashed if the module is enabled, works without it but loses support for Daydream apps
Reported by @CombineCrab -OnePlus 7 pro
-> No fix found yet
13. While activating Daydream unlocker Magisk says "This is not a module"
Reported by @grandomegabosses - LG V40 - Android 9
-> Update Magisk (If it still does not work report it)
14. After activating Daydream unlocker vibration is disabled entirely
Reported by @grandomegabosses - LG V40 - Android 9
-> No fix found yet
15. Daydream unlocker on Android 10 causes bootloop
Reported by @The Jack of Clubs - Android 10
Reported by @adam3914 - OnePlus 7 Pro - Android 10
Fixes by @Czarmstrong - Android 10
Fixes by @adam3914 - OnePlus 7 pro - Android 10
Fixes by @jigs4wkiller - Xiaomi Mi 8 - Android 10
Boot TWRP
-> Mount system
-> Go to the file explorer and navigate to "data/adb/modules"
-> Delete the "daydream" folder and reboot
Tests
Devices/systems
Xiaomi Mi A1/Mi 5s/OnePlus 5t, Android 9, Daydream 2017 headset + controller
Apps
Daydream, YoutubeVR, Cardboard,Virtual Virtual Reality,
Fulldive VR, and many more...
Old thread
Old thread by @jigs4wkiller
Thread design
Inspiration
Cosmic-OS
Magisk
Syberia
Daydream logo by @jigs4wkiller
Our team
@einholzstuhl as a community and thread manager/editor
@jigs4wkiller for more technical questions
Code
@jigs4wkiller, [MENTION=][email protected][/MENTION]
Feedback
@r0drlgo, @bschmidy10, @Kleva94, @jigs4wkiller, @redpoint73, @pbergonzi, @masoodsuliman, @simon_6162, @CombineCrab, @grandomegabosses, @pflatlyne, @The Jack of Clubs, @adam3914, @Czarmstrong, @Czarmstrong, @Fla010101
:highfive: Thank you all for your support! :highfive:
Thanks for the takeover :highfive:
jigs4wkiller said:
Thanks for the takeover :highfive:
Click to expand...
Click to collapse
Oh my god,
such high prais from the gcam god himselve!
I'am fainting :crying:
UPDATE! 15.10.2019
-> Daydream unlocker Beta for Android 10 released
-> Quick fix for bootloop on Android 10 addet to bug list
UPDATE! 08.10.2019
A couple people addet to the feedback list.
Daydream unlocker marked as only Android 9 and below compatible currently
UPDATE! 16.09.2019
XDA randomly adds brackets to my linked pictures wh...es
[B]2.[/B] Manual has been redone entirely
Thank you so much for this works like a charm, but the module changes my device ID to a Google pixel, which causes apps particularly for my OnePlus to not function... Is there a way to fix this?
bschmidy10 said:
Thank you so much for this works like a charm, but the module changes my device ID to a Google pixel, which causes apps particularly for my OnePlus to not function... Is there a way to fix this?
Click to expand...
Click to collapse
The ID change is pretty much the point of the module which fakes a device that is Daydream compatible.
So I do not think that it would be possible for Daydream and youre One Plus apps to work at the same time.
(At least not with this method.)
Jigs4wkillers suggestion:
It could work if you edit youre One Plus apps and remove the device check from them.
My suggestion:
Only activate the Daydream module when you want to use Daydream and after use disable it.
Thanks for the feedback!
einholzstuhl said:
The ID change is pretty much the point of the module which fakes a device that is Daydream compatible.
So I do not think that it would be possible for Daydream and youre One Plus apps to work at the same time.
(At least not with this method.)
Jigs4wkillers suggestion:
It could work if you edit youre One Plus apps and remove the device check from them.
My suggestion:
Only activate the Daydream module when you want to use Daydream and after use disable it.
Thanks for the feedback!
Click to expand...
Click to collapse
In the past I have just edited the build.prop to add in the vr bits and it has worked. , The problem was that every rom update would undo my work lol. Is it possible to have a module only add/fix the build.prop file and permissions and not touch device ID? Or are they locked together?
I will search for the correct build.prop file to edit to see if I can get it working without the module enabled and reply back again.
If not I will happily follow your advice to enable and disable as needed.
Thank you ??
***Update***
After researching, I see what you mean about the device ID change. It seems that certain apps require it and others work with just the vr permissions edit. You definitely have the best solution, would there be any benefit to setting to to pixel 3 xl vs OG pixel? Or not important?
And I do not expect anything , but it would be pretty great if you could make a "lite" version of this module without the device ID change or if you could tell me where to look for how to edit it myself. I was unable to find the same "handheld.core" build.prop file I used back on my OnePlus 3 (running nougat/Oreo) to change so I wasn't able to make the edits myself.
Once again, thank you very much. I can't believe there isn't more of a demand for this!
Still so frustrating Google won't just let qualified devices work properly with daydream
bschmidy10 said:
In the past I have just edited the build.prop to add in the vr bits and it has worked. , The problem was that every rom update would undo my work lol.
Click to expand...
Click to collapse
That is because youre Build.prop got overwritten by the update propably.
bschmidy10 said:
Is it possible to have a module only add/fix the build.prop file and permissions and not touch device ID? Or are they locked together?
Click to expand...
Click to collapse
You can try it the way you think it would work and report back
bschmidy10 said:
Would there be any benefit to setting to to pixel 3 xl vs OG pixel? Or not important?
Click to expand...
Click to collapse
Well it is Google, they like to have exclusive features for their own devices, but I do not think that is the case for Daydream.
Iam not sure if that is still the case but (something similiar was implemented for cardboard which had resolution QR-codes):
Every Smartphone has a certain display size and resulution.
The Google Pixel has about the same size as the MiA1 so I chose that one for the module. (That was the thought behind it)
bschmidy10 said:
And I do not expect anything , but it would be pretty great if you could make a "lite" version of this module without the device ID change
Click to expand...
Click to collapse
The module was intendet to be univerally compatible with any phone. So I would have to make a module for every phone in existence which would not really be worth the amount of work.
So the lite variant should be done individualy if needet.
bschmidy10 said:
I... or if you could tell me where to look for how to edit it myself. I was unable to find the same "handheld.core" build.prop file I used back on my OnePlus 3 (running nougat/Oreo) to change so I wasn't able to make the edits myself.
Click to expand...
Click to collapse
The build.prop is located at:
/system/build.prop
You might also need to change the System.prop
You can compare the build.prop from the module directly with the one in youre device and make changes accordingly.
Once again, thank you very much. I can't believe there isn't more of a demand for this!
Still so frustrating Google won't just let qualified devices work properly with daydream
Click to expand...
Click to collapse
Daydream is very niche so that is the sad reality of it. There are almost no devices on the market which are Daydream compatible so that will probably not change any time in the future.
Thank you again for youre feedback, much appreciated!
einholzstuhl said:
That is because youre Build.prop got overwritten by the update propably.
You can try it the way you think it would work and report back
Well it is Google, they like to have exclusive features for their own devices, but I do not think that is the case for Daydream.
Iam not sure if that is still the case but (something similiar was implemented for cardboard which had resolution QR-codes):
Every Smartphone has a certain display size and resulution.
The Google Pixel has about the same size as the MiA1 so I chose that one for the module. (That was the thought behind it)
The module was intendet to be univerally compatible with any phone. So I would have to make a module for every phone in existence which would not really be worth the amount of work.
So the lite variant should be done individualy if needet.
The build.prop is located at:
/system/build.prop
You might also need to change the System.prop
You can compare the build.prop from the module directly with the one in youre device and make changes accordingly.
Daydream is very niche so that is the sad reality of it. There are almost no devices on the market which are Daydream compatible so that will probably not change any time in the future.
Thank you again for youre feedback, much appreciated!
Click to expand...
Click to collapse
Thank you ?
First of all, thanks a lot for the module.
I had some distortions in VR on my OnePlus 7 Pro.
So I changed the values in system.prop to "Pixel 3 XL" and "crosshatch" and it got much better. Most likely because of the similar screen ratio.
Kleva94 said:
First of all, thanks a lot for the module.
I had some distortions in VR on my OnePlus 7 Pro.
So I changed the values in system.prop to "Pixel 3 XL" and "crosshatch" and it got much better. Most likely because of the similar screen ratio.
Click to expand...
Click to collapse
It might be a good idea to release more version for different screen ratios.
Thanks for the input!
Edit:
A couple more screen resolutions addet
Kleva94 said:
First of all, thanks a lot for the module.
I had some distortions in VR on my OnePlus 7 Pro.
So I changed the values in system.prop to "Pixel 3 XL" and "crosshatch" and it got much better. Most likely because of the similar screen ratio.
Click to expand...
Click to collapse
How did you get the module working on the OP 7 Pro? I downloaded the 2960x1440 version (seemed closest to the phone's 3120x 1440 resolution). When flashing in Magisk (19.3), it says "installation failed".
I tried flashing in TWRP (sometimes works for modules that don't install straight from Magisk), but it says "invalid zip format". So maybe not meant to flash in TWRP.
Any info on how you did it would be appreciated.
redpoint73 said:
How did you get the module working on the OP 7 Pro? I downloaded the 2960x1440 version (seemed closest to the phone's 3120x 1440 resolution). When flashing in Magisk (19.3), it says "installation failed".
I tried flashing in TWRP (sometimes works for modules that don't install straight from Magisk), but it says "invalid zip format". So maybe not meant to flash in TWRP.
Any info on how you did it would be appreciated.
Click to expand...
Click to collapse
I will check the module maybe I made a mistake
Edit:
Zip reupload, please download again.
jigs4wkiller said:
I will check the module maybe I made a mistake
Edit:
Zip reupload, please download again.
Click to expand...
Click to collapse
That one worked. Installed the module anyway. Now to try the rest of the steps!
Thanks for your work.
Using either the Magisk module download from github or the 2160 x 1080 module from the list on google drive "This zip is not a Magisk module."
pbergonzi said:
Using either the Magisk module download from github or the 2160 x 1080 module from the list on google drive "This zip is not a Magisk module."
Click to expand...
Click to collapse
Try to update Magisk to the newest version and check if Magisk is working correctly.
einholzstuhl said:
Try to update Magisk to the newest version and check if Magisk is working correctly.
Click to expand...
Click to collapse
Silly me--the google drive re-zips the file to download it--I had to remove it from the initial zip to get to the folder that held the correct zip.
And the one I had downloaded from github needed to have the files removed from the unzipped folder and zipped.
Thanks for your help, and also wondering if you can make a 2340 x 1080 for the OnePlus 6t? Or if you'll tell me what to edit in one of your zips, I can make the edit myself.
pbergonzi said:
Silly me--the google drive re-zips the file to download it--I had to remove it from the initial zip to get to the folder that held the correct zip.
And the one I had downloaded from github needed to have the files removed from the unzipped folder and zipped.
Thanks for your help, and also wondering if you can make a 2340 x 1080 for the OnePlus 6t? Or if you'll tell me what to edit in one of your zips, I can make the edit myself.
Click to expand...
Click to collapse
It's not really necessary to use the props from a device with the same phone resolution we only added more device with different resolutions because of the user feedback.
jigs4wkiller said:
It's not really necessary to use the props from a device with the same phone resolution we only added more device with different resolutions because of the user feedback.
Click to expand...
Click to collapse
Thank you.
On testing different iterations of the enabler resolution some behaved erratically--one seemed to stagger a little on the edges of things while turning, one seemed to have slightly smeared edges but was more pixellated.
Nevertheless, the experience is overall a good one, and it sure was nice sharing a roller-coaster with Santa!
Where is system.prop file? And what is crosshatch setting?
Related
This module has been discontinued. Try Advanced Power Menu+.
{
"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"
}
ADVANCED POWER MENUXposed Mod
Original Xperia-specific thread
Advanced Power Menu is an Xposed Mod which adds advanced reboot options (reboot, soft reboot and reboot to recovery) and screenshot option to your power menu. It works on both AOSP and Xperia devices. For rebooting into recovery, a special implementation for Xperia devices is used, but it will also work on AOSP devices.
Features
[NEW] Anti-theft helper - Stop anyone from turning off your phone /enabling airplane mode when the device is locked. In this way no one can stop Android Device Manager from locating your phone by turning off the phone or disabling mobile data (removable battery not taken into account)
A dedicate first-level option for rebooting
Fully working reboot to recovery(no reboot wrapper required)*, bootloader and soft reboot
Screenshot function
Quick dial - call a predefined number directly from the power menu
Toggle mobile data from your power menu
High quality mdpi-xxhdpi icons
GUI for different configurations
Multi-language support
Thanks to Xposed framework,
Easy Installation. No flashing required.
Works both for odexed and deodexed ROMs
Quite future proof (should work for Android 4.3 if there is no big framework change from Sony)#
Should work for a lot of devices
* - For rebooting into recovery, a special implementation for Xperia devices is used, but it will also work on AOSP devices.
# - Unfortunately, there IS framework change from Sony, mainly caused by the new theming engine. Therefore the regular Xposed Installer doesn't work on Xperia 4.3 ROMs. You can download the special version here (released by rovo89):http://forum.xda-developers.com/showpost.php?p=48484642&postcount=6846
Screenshots
See the app in action
You can add items into the power menu like this:
Or remove items like this:
The reboot sub-menu:
Anti-theft helper: this is what a bad guy will see if he tries to turn off your phone while the device is locked:
Settings - great level of customization:
Prerequisites
All Xperia Phones with rooted stock 4.0+ ROM / Nexus devices / AOSP/ a number of other devices(see confirmed working devices below) (Please do test and tell me)
Xposed framework installed
Note: for Android 4.4 you need the latest version of Xposed Installer (2.4 Beta 1 or later)
A user has reported that sound options disappear when using this mod on HTC One. I currently have no idea why this happens, and I'm too busy to figure it out at this moment. Sorry.
Installation
You will need xposed framework and for this mod to work! See prerequisites above.
After you meet the prerequisites,
Download and install the apk in the next post
Go to Xposed Installer > Modules and enable "Advanced Power Menu"
Reboot and you are done! (Sometimes you might need to reboot more than once for all functions to work)
Disclaimer
I'm not responsible for any damage caused by this mod! Use this at your own risk.
User agreement
Once you use this software, you agree to the Copyright and Disclaimer statement.
Special Thanks
See file on github
Appeal
If this app helps you please press the Thanks button.
Note
The Change Network State and Internet permission is needed for toggling mobile data.
NOTICE
My app, as well as some other xposed modules, was placed on Google Play without my consent.
This Google Play entry (https://play.google.com/store/apps/d...ncedrebootmenu) was made without my knowledge and agreement, and I am by no means affiliated with the said developer on that entry.
Authentic releases, whether current or future, is only available on Xposed Modules Repository unless I make another notice.
Download
From now on, Advanced Power Menu is hosted on Xposed Module Repository. You may go to there to download, or directly download from Xposed Installer App.
Old versions on xda:
v3.0
v2.1r
v2.1b
v2.0r
v2.0b
v1.1r
v1.1b
v1.0 apk
Which version should I download?
Release(r): Disabled most of the logs. Use this if you have no problems with the app
Beta(b): With full verbose logging. Use this if you encounter problems. Logs can be found at /data/xposed/debug.log
What can you do if the app doesn't work / if issue happens?
Step 1: Try fixing it yourself
1. Make sure that you have read the prerequisites and installation guide thoroughly/
2. Reboot your phone TWICE (TWO TIMES)
For every single xposed mod, a reboot after installation is necessary. But that might not be enough as users have reported that the app doesn't work after a single reboot, but things get right when they reboot again. So rebooting TWICE is recommended
3. Disable all other Xposed Mod
Xposed framework do take care of mods that hook the same method, but sometimes conflicts can still happen. Try disabling all mods except mine in the Xposed Installer. Then reboot and see if things get right.
4. Clear app data/reinstalling my app
The settings may get messed up when my app updates, so try reinstalling and see if it helps.
5. Use an older version of my app
Try this and see if it helps. If so that means a new update breaks something old and please tell me about that!
If all the above doesn't work, you can then send me an issue report.
Step 2: Tell me and see if I can fix it
(Please don't do this before doing step 1)
Please send me an issue report including
1) a description of the issue
2) screenshots (if it helps explain the situation)
3) The device, ROM, Android OS version, and the app version
4) debug.log (Please enable verbose logging in my app first, then do something like long-pressing the power button)(you may obtain the log in xposed installer 2.4)
5) Anything else you think it's important
through one of the following means:
1) xda forum thread/PM (preferred)
2) e-mail (NOTE: please begin your subject with [APM] so I can better sort my emails. Thanks)
Please note that I can't solve the problem with insufficient information. I will also IGNORE any email with NO BODY TEXT (I use gmail)
Keep in mind that even with all the information I still may not be able to fix your problem because I do not own your device and I'm only a novice android developer. Sorry.
FAQ
Q: The mod doesn't work!
A: Other xposed mods might interfere with this mod. Disable them, reboot and try again.
Q: Rebooting into recovery doesn't work!
A: Flashing the DoomLorD's reboot wrapper MAY help. However, as the wrapper is intended to be optional, there might be something wrong. So it'd be nice if you could send me some logs
Q: There's something wrong with the mod...
A: Just disable the mod in Xposed Installer and reboot. Then everything should be fine again (Should this happens please tell me and send me the debug.log and debug.log.old files. This helps me to fix the issue)]
Q: I have a bootloop! What should I do now?
You can follow the following methods (quoted from xposed framework main thread) to disable the xposed framework
In case you get into a boot loop:
You can flash the attached Xposed-Disabler-CWM.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
You could also create a file /data/xposed/disabled, which causes Xposed to be bypassed as well.
Click to expand...
Click to collapse
Usage Warning
DO NOT press Vol-Down + Power while a screenshot taken by Advanced Power Menu is being saved! This will result in constant force-stop of System UI and you will need to reboot the phone to solve this!
Usage Tip
You can long-press the reboot option on the power menu if you wanna do a normal reboot. Then you can skip the reboot mode dialogue.
Changelog
From now on, all changelogs are on Xposed Module Repository.
Old changelogs:
v3.0
App name is changed to "Advanced Power Menu"
Updated app icon
GUI for configuring different options
options to hide/show reboot option and screenshot option
disable reboot confirmation dialogs
option to write full logs (effectively merging beta and release versions)
many small, under-the-hood changes.
v2.1
Add support for 4.0+ devices
Fixed Simplified Chinese/Traditional Chinese Translations
Changed implementation for rebooting so su permissions are no longer needed
Upstream changes from GravityBox
v2.0
New implementation for rebooting into recovery. Reboot wrapper is no longer needed.
Added screenshot function!
v1.1
Added more than 10 languages (some of them are from GravityBox)
Fixed soft-reboot function
Added drawable resources for xhdpi, hdpi and mdpi
Improved logging system
v1.0
initial release
Source and Permission of Use
Advanced Power Menu is on github.
Please ask for my permission before redistributing or creating derivative works of the app. However, as governed by GitHub's Terms of Service, forking the project on GitHub is permitted. Feel free to fork the project, add your own code, and send me pull requests on GitHub.
Multi-language Support
This app is translated into more than 10 languages.
But if you like to add a new language/ providing better translations you can download the XML files and do the modification. I would be grateful for you work!
Note: You don't need to send me the xml file if you'd like to add/change one or two strings only. Just drop me a post/message.
Suggestions/Feature Requests
Your suggestions can help me to improve the app. Feel free to post here.
Confirmed Working Devices/Firmwares
Nexus Devices
Galaxy Nexus 4.3
Nexus 4
Nexus 10
Nexus 5 4.4
Nexus 7 4.4
Sony Xperia Devices
Xperia Z C6603/C6602 .244/.67/.569 odexed
Xperia ZL .244 odexed
Xperia SP .245
Xperia ZQ
Xperia Z Ultra .475 .290
Xperia ZR 4.2.2
Xperia Tablet Z
Xperia S
Xperia U (stock ICS & AOSP)
Xperia UL
Xperia J
Xperia P stock JB
Xperia Neo V (stock ICS)
Xperia Tipo Dual
HTC devices
HTC One X 4.2.2 stock Rom with Sense 5
HTC Rezound with Vanir (AOSP Jelly Bean 4.3)
Other Devices
Moto X 4.4
Motorola Razr D3
LG Optimus G Pro stock 4.1.2 rooted rom
LG G2 (Omni 4.4, D802 (stock 4.4.2 v10c), VS980 (vs98012b stock), D801 4.4.2 stock)
Samsung Galaxy SII Chameleon ROM v3.0.3
Samsung Galaxy S3 w/ CM11
Samsung Galaxy Note 3 (N9005 stock)
Samsung Galaxy Note 3 N900T (4.4.2_r2 stock)
Micromax CANVAS HD A110
Lenovo p780
Don't be afraid if your device/firmware is not listed on the list. Xposed means high compatibility and ease to revert.
A user has reported that sound options disappear when using this mod on HTC One. I currently have no idea why this happens, and I'm too busy to figure it out at this moment. Sorry.
reserved
---Now you may post---
The Anti-Theft feature is quite a genius thing. The thief wont know about the "battery pull" of my Xperia Z ^^
May I request a feature to hide the "device locked" in the lockscreen power menu completely?
Amazing, keep up dev
Works fine on my LG g2, 4.4.2 omni. It seems almost to good tat a potential thief can't boot into recovery anymore. Great work!
Thanks all for your support and feedback!
Kocayine said:
The Anti-Theft feature is quite a genius thing. The thief wont know about the "battery pull" of my Xperia Z ^^
May I request a feature to hide the "device locked" in the lockscreen power menu completely?
Click to expand...
Click to collapse
Thanks for your suggestion. The feature has been implemented in the latest release v8.1.1
I have request for U
I want Wi-Fi switch and Bluetooth switch in power menu.
Please make it!!
It would be cool if the displayed text for quick dial was customizable.
harahara0121 said:
I want Wi-Fi switch and Bluetooth switch in power menu.
Please make it!!
Click to expand...
Click to collapse
I plan to make this, but this is more time consuming to implement it. I'll do that if I've ample free time (but I don't think I'll in near feature)
android404 said:
It would be cool if the displayed text for quick dial was customizable.
Click to expand...
Click to collapse
I've just done that so the feature will be available in the next version of release
A new version has been released. Grab it from xposed repo!
What's new:
Customizable display text for quick dial
New Czech translation (thanks jzak)
Updated Traditional Chinese translation
Updated the xda thread link
A quick question : you can still shutdown your device by long press the power button even your phone is locked?
If so, could you implement that the app could only force restart but not shutdown?
It depends on your phone. As far as I know, long pressing the power button of a nexus device causes it to reboot. For Xperia Z, long pressing it will neither power off nor reboot the device. I don't know about others though. However, this kind of force shutdown is usually implemented at hardware level / low level so I don't think I can do much to control this behavior
Sent from my C6603 using Tapatalk
Works great on LG G2 D802 (stock 4.4.2 v10c). Thanks a lot!
It works great at my razrd3 to, but I got a menu that leet the phone sleep, I dont know if this bottom is common on others android phone, so I ask if u can implement remove this from power menu while in lockscreen
I see this works on other lg g2 but has anyone tried on vs98012b stock rooted? I'd love to have a faster easier way to get into my twrp recovery
Sent from my VS980 4G using Tapatalk
---------- Post added at 06:01 AM ---------- Previous post was at 05:25 AM ----------
Nevermind LOL I went ahead and tried it confirmed working and boots into twrp just fine
Sent from my VS980 4G using Tapatalk
The anti-theft feature is useful, another way to prevent someone from turning off your phone. My Nexus 4 has a non-removable battery though the issue is that I believe a hardware feature of it is that if you hold the power button for 10seconds anyway it'll still shutoff (not sure but I think I read that somewhere). At the very least for the Nexus 4 this only leaves one option for the theif to shut it off.
Thanks for making this awesome module!! Working fine on Xperia Neo V (stock ICS) :good:
kennethso168 said:
# - Unfortunately, there IS framework change from Sony, mainly caused by the new theming engine. Therefore the regular Xposed Installer doesn't work on Xperia 4.3 ROMs. You can download the special version here (released by rovo89, mirrored because I've forgotten the original link):http://forum.xda-developers.com/attachment.php?attachmentid=2454695&d=1387049158
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48484642&postcount=6846
Hi, thanks for the great module ! Here's a suggestion an insta-wipe option followed by a personal code?
Advanced Power Menu has been featured on the xda portal!
Thank you for your support!
Toronadian said:
The anti-theft feature is useful, another way to prevent someone from turning off your phone. My Nexus 4 has a non-removable battery though the issue is that I believe a hardware feature of it is that if you hold the power button for 10seconds anyway it'll still shutoff (not sure but I think I read that somewhere). At the very least for the Nexus 4 this only leaves one option for the theif to shut it off.
Click to expand...
Click to collapse
Well I'm not sure but I believe that holding nexus 4's power button for that amount of time only reboots the phone (I think I read that somewhere too) Anyway, thanks for your comment. (and ya there's still a way to power-off the phone with anti-theft helper on, at least with my Xperia Z)
dionei said:
It works great at my razrd3 to, but I got a menu that leet the phone sleep, I dont know if this bottom is common on others android phone, so I ask if u can implement remove this from power menu while in lockscreen
Click to expand...
Click to collapse
I think in the future I can implement a feature that can remove any power option you like.
Titokhan said:
...
http://forum.xda-developers.com/showpost.php?p=48484642&postcount=6846
Click to expand...
Click to collapse
Thanks for pointing out the original link. I'll update that
flame360 said:
Hi, thanks for the great module ! Here's a suggestion an insta-wipe option followed by a personal code?
Click to expand...
Click to collapse
Thank you for your suggestion but I think the implementation of that feature may be beyond of my ability
____________________________________________________________________________
Sorry I think I'll be terribly busy then so I don't think I can implement any new features in the next 3-4 months.
Code:
Clarity is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Introduction
Clarity is an Xposed module and root Android application for increasing the size and quality of contact thumbnails in the Android contacts database. It's comprised of two components. An Xposed modification and a root-required Database Processor.
Clarity also increases the quality and size of locally stored album art.
Click to expand...
Click to collapse
Xposed Mod
Android stores two versions of contact images. The contact photo and the contact thumbnail. While both are downscaled appropriately from the original image, the two are very different in size. Contact photos clock in at around 720×720 pixels or so depending on the original image. Contact thumbnails are a measly 96×96 pixels. Contact photos are used in places where contact imagery is going to be distinctively large like the KitKat/Lollipop Phone app. Or when you receive an incoming call. Thumbnails are used for notifications, messaging applications, and other roles which the full contact photo is unnecessarily big. Unfortunately, as screen PPIs have skyrocketed since the 96×96 limit was put in place, contact thumbnails are now too small for their original purpose. Regardless, most applications continue to use contact thumbnails.
Clarity forces Android to use a user-defined size (defaulting to 256×256) when adding contact thumbnails to the database. While these new images are larger and look much better they will load slightly slower and increase memory requirements. For newer devices this should not be a problem. For reference, I have not witnessed any side effects on my Galaxy S4 using the default 256×256 setting. Since the size can be adjusted you can optimize it for your device.
In the name of simplicity, Clarity does not change the method Android uses to downscale contact thumbnails, just the final dimensions. However since Clarity allows you to increase the size of the thumbnail and consequently decrease the magnitude of the downscale, there will be noticeably fewer artifacts in your new thumbnails.
The Xposed module does not magically increase the quality of thumbnails already added in the database. It only affects newly added/updated contacts and images. To upgrade your entire contacts database either use the Database Processor detailed below or re-import the contacts. Re-importing may require you to deconnect/desync the account the contacts are associated with and then reconnect/resync the account. Some sync applications may have a force refresh option and that should work nicely. For instance, HaxSync has a Force redownload option under its contact settings.
When the Xposed module is activated, Clarity will also up the size of locally stored album art (for instance, MP3s on the external storage). Just like the contact thumbnail part of the module, existing album art is unaffected. To get Android to reprocess all the album art on your device you must delete all the files found in the albumthumbs directory. This is usually found somewhere on your external storage. Popular paths are /storage/emulated/legacy/Android/data/com.android.providers.media/albumthumbs and /storage/sdcard0/Android/data/com.android.providers.media/albumthumbs. Different devices and ROMs can have different paths but the last /Android/data/com.android.providers.media/albumthumbs bit should stay the same. Once that directory has been cleared out, higher quality album art will be regenerated by Android on demand (as they are needed). See Android issue 73635 for more information about the album art problem.
Click to expand...
Click to collapse
Database Processor
In addition to the Xposed-based modification described above, Clarity includes a Database Processor. This powerful feature forcibly updates every contact thumbnail in your database. It rips out the internal contacts database file, finds all your contacts with photos and puts in new thumbnails. It'll then replace the old database with the new one. It is highly recommended to immediately reboot after processing to avoid Android going berserk. It will if you don't.
While powerful, the Database Processor is also extremely dangerous. I am not responsible for any damage to your device as a result of using Clarity. It performs several operations as root and modifies core Android files that were never meant to be touched by anything other than Android itself. I highly recommend a full recovery-based backup of your device alongside the built-in backup feature. Please use the dry-run feature first (hell, multiple times even) to ensure the operation will succeed for your ROM. It is possible a successful dry-run could still fail when doing the real-deal so, as I mentioned before, backup your stuff. The built-in contact backups will be saved to a Clarity folder on your "primary" external storage. What primary means depends on your ROM and device. It could be your actual external SD card or it could be an internal storage location. Regardless, the current backup location will be noted, assuming backups are enabled, in the processor's log. As an added bonus, if the backup feature is on it will also save the log file alongside your backups!
The Database Processor has been tested on CM (CyanogenMod) 10 (based on Android 4.1.2), CM 11 (based on Android 4.4.4), CM 12 (based on Android 5.0.2), and CM 13 (based on Android 6.0.1). It should work on any AOSP-based ROM from Ice Cream Sandwich (4.0) to Marshmallow (6.0). For stock ROMs and anything created by carriers I have no idea. If it works for you please report back! If it doesn't, well, report that too.
Click to expand...
Click to collapse
Images
Settings
Database Processor
Raw Comparison
{
"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"
}
Google Messages Comparison
Google Hangouts Comparison
Android Wear Comparison
More!
Click to expand...
Click to collapse
Features
Simple lightweight Xposed modification
Powerful database processor for forcibly updating contact thumbnails
Also clarifies locally stored album art
Should work on nearly any AOSP-based ROM like CyanogenMod
Free and open-source software. No nags. No data collection. No secrets.
Click to expand...
Click to collapse
Known Issues
Does not appear to work with Google-synced contact photos.
May not work with all devices and ROMs. See the following post.
Click to expand...
Click to collapse
Installation
Make certain you have Xposed installed before continuing.
Install the app by a) searching for it in the Xposed Installer or b) manually through the APK provided on GitHub or the Xposed website.
Configure the app in its settings panel. It can be accessed through the module section of the Xposed Installer or by the launcher shortcut.
Enable the module in the Xposed Installer.
Reboot.
Done!
The Xposed module will only update contact photos that are modified or added to the database after it is turned on. The database processor will attempt to update the contact photos in place and right away. To avoid using the database processor your contact photos must be manually refreshed. How/if this can be done and how easily is dependent on how you sync your contacts. For instance, if you use HaxSync you can update all your photos by going to Settings app -> Accounts -> HaxSync -> Advanced Settings -> Contact Settings -> Check Force redownload. Hit back twice. Select your account name at the top. Click Contacts to uncheck it. Recheck it and wait for sync to finish.
Click to expand...
Click to collapse
Changelog
See the GitHub repository for the definitive changelog.
Code:
v1.2-cfad189 - 03 Jul 2016 - Stable
------------
This release introduces the following improvements:
* Added a Spanish translation
(thanks to Jose Artuñedo @ XDA)
* Fix a SELinux-related issue with the Database Processor
on Marshmallow
* Support Marshmallow's new permission system
* Added some additional debugging info to the processor log
* Tested on CyanogenMod 13 (Android 6.0.1)
Code:
v1.1-93b7945 - 03 May 2015 - Stable
------------
This release introduces the following improvements:
* The database processor will no longer fail if contacts2.db-journal
cannot be found. It will note the absence of the journaling file
in the log and proceed as normal
* Will now increase the size and quality of locally stored album art.
Suggested by @Karamvir Singh. See [url=http://forum.xda-developers.com/showpost.php?p=60499753&postcount=55]this post[/url] for more
information.
* An XXXHDPI icon
* Updated donation links
* Minor log bug fix
* Better shell usage
* Less condescending toast notifications
Code:
v1.0-917d899 - 25 Mar 2015 - Stable
------------
Initial release. Make sure to see the README or XDA thread!
Click to expand...
Click to collapse
Downloads
MD5 checksums are available on the Xposed Repo and XDA.
Xposed Repo (APK)
XDA (APK)
GitHub (HTTPS APK)
GitHub (sources)
Click to expand...
Click to collapse
FAQ
Q: Something went horribly wrong! How do I restore from one of the backups?
A: Ouch! Clarity stores backups on your "external storage." Depending on your device and ROM this could be an actual SD card or internal. If your device has two check both. It will be in a directory named Clarity. In the Clarity backup directory there will be sub-directories with dates. Select the one before everything went to hell. You'll find up to three files: contacts2.db contacts2.db-journal, and dbprocessor.log The .db file(s) are the actual contacts databases. The dbprocessor.log is your log file and has lots of great information for us to use. Now that we have located everything we need let's get restoring.
Method #1 - By hand
If your device still boots and you can navigate around (even if things are crashing every few seconds) try this. If you have a custom recovery that supports adb then this will work as well if you boot into it.
Grab the adb command line tool. For Windows check here. For Linux and Mac see here.
Now put your device in debug mode. Go to the settings app. Tap About phone. Keep tapping Build number until it says you are a developer. Go back and select Developer options. Turn the development options "on" if needed. Under Debugging turn on Android debugging.
Now connect your device to your computer. It should say something about debugging being enabled in the status bar. Make certain your phone is unlocked. If it says something about allowing the computer debug access to your phone please accept it.
Open up a command line or terminal. On Linux I'm going to assume you know what to do. On Mac it's the Terminal app. On Windows it's C:Windowssystem32cmd.exe
Type adb version and hit enter. If your get something about it being not found then adb isn't installed in your PATH or you're not in the directory in which adb was extracted. You can navigate to that directory with the cd command. So to navigate to the system32 folder on Windows, for instance, I'd type cd C:Windowssystem32 and hit enter.
Type adb shell and hit enter. This will dump us into a shell instance directly on your device.
Type id and hit enter. If the first bit is not uid=0 then unlock your device and type su and hit enter. If your device prompts for superuser access please grant it.
Navigate to the directory in which your backups are stored on your device. For me this would be something like cd /storage/emulated/legacy/Clarity/2015-Something
You should now see the backup files if you type ls and hit enter. Great. Now to move these into place.
Open your dbprocessor.log file on your device through a file manager or move it onto your computer to read its contents. You can read it through the command line if you wish but it's much more convenient to be able to copy and paste if needed.
Note the Contacts UID and Contacts directory. Mine is 10006 and /data/data/com.android.providers.contacts respectively.
Execute cp contacts2.db /your/contacts/directory/databases/contacts2.db and hit enter. For me this full command is cp contacts2.db /data/data/com.android.providers.contacts/databases/contacts2.db
If you have a contacts2.db-journal file do the same except with that file. For me this is: cp contacts2.db-journal /data/data/com.android.providers.contacts/databases/contacts2.db-journal
Now to correct the permissions. Type chown +UID:+UID /your/contacts/directory/databases/contacts2.db* and hit enter. For me this is chown +10006:+10006 /data/data/com.android.providers.contacts/databases/contacts2.db*
Reboot immediately by typing reboot and hitting enter.
All done. Your contacts database has been restored.
Method #2 - Recovery
Took a backup with your custom recovery before processing? Just restore from the backup to get your device back to normal.
Click to expand...
Click to collapse
Credits
rovo89 - Xposed
Chainfire - libsuperuser
Click to expand...
Click to collapse
Licensing
Copyright © 2015-2016 Kevin Mark. Clarity is licensed under the GNU General Public License, Version 3, which can be found in LICENSE.md
Click to expand...
Click to collapse
Clarity is developed in my spare time and will always remain free and open-source software. If you find this application useful please feel free to donate.
XDA:DevDB Information
Clarity, Xposed for all devices (see above for details)
Contributors
Kevin M
Source Code: https://github.com/kmark/Clarity
Xposed Package Name: com.versobit.kmark.clarity
Version Information
Status: Stable
Current Stable Version: v1.2-cfad189
Stable Release Date: 2016-07-03
Created 2015-03-25
Last Updated 2016-07-23
Clarity
ROM Compatibility
Clarity should work with CyanogenMod and other closely AOSP-based ROMs. Other ROMs like the stock ones found on most popular Android devices may not work with Clarity. If you have a device or ROM that Clarity works or does not work with (and is not already on the below list) please tell me!
LG G2
CyanogenMod 12
LG G3
SkyDragon (Lollipop)
Motorola Droid X2
CyanogenMod 10
Nexus 6
Temasek
OnePlus One
BlissPop 2.2
Temasek 5.0.2
Samsung Galaxy Note II N7100
CyanogenModX 5.0.2
Samsung Galaxy Note 4
CyanogenMod 12 (3/24 nightly)
Stock (doesn't work? try this)
Samsung Galaxy S4
CyanogenMod 11
CyanogenMod 12
CyanogenMod 13
Xperia J
Xperia Revolution ROM
Click to expand...
Click to collapse
ROM Incompatibility
Moto X (2013)
Stock (Android 4.4)
Click to expand...
Click to collapse
Looks Promising !!!!
M3gAtR0N said:
Looks Promising !!!!
Click to expand...
Click to collapse
Thank you. The application is now available.
Kevin M said:
Thank you. The application is now available.
Click to expand...
Click to collapse
Works fabulously with BlissPop 2.2 OPO !
Excellent wok
Looking forward to this project!...?
Testing after a while on XPERIA!
This is awesome, especially for Android wear!! Does it help with WhatsApp too? I fear not since it has different pictures...which are ugly because of an 8bit definition worth of MS-DOS "prince of persia"!!
So, that said, which apps are affected in addition to messenger and hangouts? Textra maybe? Others?
Cheers and keep up the good work!!
N7100 - CyanogenModX 5.0.2 @240 dpi
I've been waiting for this my entire life haha, thank you!
Fantastic! Works great. All I had to do was uncheck Contacts in sync settings and recheck it.
M3gAtR0N said:
Works fabulously with BlissPop 2.2 OPO !
Excellent wok
Click to expand...
Click to collapse
Thanks! Both the DB processor and the Xposed mod seem to be working well?
cyberpunk627 said:
This is awesome, especially for Android wear!! Does it help with WhatsApp too? I fear not since it has different pictures...which are ugly because of an 8bit definition worth of MS-DOS "prince of persia"!!
So, that said, which apps are affected in addition to messenger and hangouts? Textra maybe? Others?
Cheers and keep up the good work!!
N7100 - CyanogenModX 5.0.2 @240 dpi
Click to expand...
Click to collapse
It will help with any application or system software that makes use of the contact thumbnail stored in the database. From my personal experience this is a majority of applications. It's also why Clarity fixes contact imagery on Android Wear apps/notifications. It will not work for any apps that use their own contact system instead of the built-in Android one. A good example is Google Hangouts which will use its own contact photos for your Google+ contacts. Luckily the Google+ photos tend to be pretty decent quality-wise. Hangouts will fall back to your contacts database if that person does not have a Google+ profile and so Clarity will help there.
Kevin M said:
Thanks! Both the DB processor and the Xposed mod seem to be working well?
/QUOTE]
yes both are working smoothly ! This is something that should be done by Google themselves !
Tested on BlissPop and Temasek 5.0.2 Lollipop for OnePlus One !
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
Kevin M said:
Thanks! Both the DB processor and the Xposed mod seem to be working well?
Click to expand...
Click to collapse
Yes both are working seamlessly !
Tested on BlissPop and Temasek 5.0.2 Lollipop for OPO !
Click to expand...
Click to collapse
M3gAtR0N said:
Kevin M said:
Thanks! Both the DB processor and the Xposed mod seem to be working well?
/QUOTE]
yes both are working smoothly ! This is something that should be done by Google themselves !
Tested on BlissPop and Temasek 5.0.2 Lollipop for OnePlus One !
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
Yes both are working seamlessly !
Tested on BlissPop and Temasek 5.0.2 Lollipop for OPO !
Click to expand...
Click to collapse
Great, thanks again. The Xposed modification that Clarity makes to Android can actually be done by ROM devs (or of course Google). I'm assuming at least someone out there does this.
If you're a ROM maintainer consider adding Clarity's simple modification to your ROM. Reference the XClarity.java file for implementation details.
Click to expand...
Click to collapse
I've always wondered what the hell is going on when I get a new phone and some contacts images are blurry when they never were before in the previous phone. Happens everytime. Downloading now.
app seemed to work great on TMO Note 4 with CM 3/24 nightly . . . . until I pushed the Home button. I am then asked which launcher I want to use as Home and I choose Nova (which I already chose before). Then I get message that says "Unfortunately Android System has stopped." This happens every time I hit the home button. It happens if I choose Google Now Launcher too. This problem happened immediately after installing the mod and hadn't happened before. Still happens if I disable mod and reinstall Nova. Any ideas?
EDIT: if I go to settings - home and choose launcher there, it fixes it. Not sure why that is necessary. You should be able to choose default launcher when it ask you if you always want to use that launcher....
mcdavid said:
app seemed to work great on TMO Note 4 with CM 3/24 nightly . . . . until I pushed the Home button. I am then asked which launcher I want to use as Home and I choose Nova (which I already chose before). Then I get message that says "Unfortunately Android System has stopped." This happens every time I hit the home button. It happens if I choose Google Now Launcher too. This problem happened immediately after installing the mod and hadn't happened before. Still happens if I disable mod and reinstall Nova. Any ideas?
EDIT: if I go to settings - home and choose launcher there, it fixes it. Not sure why that is necessary. You should be able to choose default launcher when it ask you if you always want to use that launcher....
Click to expand...
Click to collapse
Quite odd. Did you reboot after running the DB processor?
Kevin M said:
Quite odd. Did you reboot after running the DB processor?
Click to expand...
Click to collapse
Like an idiot, I didn't read the entire OP. So, I just installed it and rebooted and had the issues I mentioned. In other words, I hadn't even tried the DB Processor yet. I have since read the OP and ran the DB Processor and had no issues. All is well. Still not sure why what I described happened. As long as others know they might have to assign home launcher via settings, it's not a big deal. Thanks for your fast response.
So, in theory, would you be able to install this and run the DB processor to create hi-res thumbnails and then remove the app? I ask because Xposed is not stable on my device (it works, but causes random reboots), so running this and getting it setup then removing Xposed would be ideal for me. Or I can just try and modify my ROM to get it to work without Xposed (I haven't read the implementation details yet).
EDIT: To answer my own question - YES, this works Made a nandroid, got everything setup, removed Clairty and Xposed, and restored my /system partition. Good to go!
Doesnt work on Lollipop TouchWiz on the Note 4. Expected but o well
What size are y'all using? 256 or increased it?
---------- Post added at 09:53 AM ---------- Previous post was at 09:49 AM ----------
It refuses to change detect contacts
Out of all, it only finds 1 photo and claims it's not even square
Any help?
I don't see any differences. LG G2 with CM 12.
ok it works now.
Hi to all, i'm an old and Retired XDA Rom developer, i hope someone remember me here recently i buyed a Mini M8S II, and i found some bugs, and i hate the customization so i looked into...
That's what i got... a superspeed rom, customized with all the new fixes and utility you need.
{
"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"
}
It's for Mini M8S II, but should work on any P212 Motherboard based TvBox, and some other with 2Gb of Ram, obviously i did not a test with all devices but you can read in forum.
Reported Working also on:
- Tanix TX5 Pro
- Mini MX + S905x 1Gb
- TX95
- TN95
- X96 this is the remote.conf
- Nexbox A5 2G/16G
- Nexbox A95x s905x 1g 8g
- and many others
Using a different device just remember to put the correct Remote.Conf in /system/etc ; in my custom rom /system/Media i gave to you a directory with some remote.conf i found around:
Code:
[B]REMOTE INCLUDED [/B][B]TO BE COPIED IN /system/etc/ (give permissions 644)[/B][B]:[/B]- Nexboxa5
- Nexboxa95x
- V88 Pro
- TanixTX5Pro
- X96
So this Rom is:
Code:
- Deodexed
- Zipaligned
- DeBloated
- Xposed Framework prebuilt in and activated
- Init.d support built-in
- Kodi bloated addon removed + Kodi/SPMC optimizations Built-in
- SuperSu updated to latest stable
- Many refinement and optimizations
- Selinux in Permissive mode
- SquareHome2 set has system launcher, you need to customize it by yourself, but i like it badly. ;)
App Removed:
Code:
- OpenWNN and relative libs
- PPPoe
- Filebrowser
- Browser
- Videoplayer
Bugfixes:
Code:
- USB keyboard ENTER bug corrected;
- RGB FIX go in Android settings/display/set colorspace choose RGB then Unplug and replug HDMI cable!
- Brightness bug fixed;
- R/W working;
- Wifi: i bougth a litte 6db gain antenna with cable(1,5 $) soldered it removing the ****ty antenna inside of the box.
- Passthrough Fix - Thanks Pharjister ![B]Passthroughfix.apk Instructions:[/B] You had to go to android settings/more settings/apps privileges and turn on storage privileges then notifications and give it priority. Launch the app and use reboot button ad approve root privileges for it. From then on after rebooting wait until you hear the notification sound and check if the app has received root privileges. Normally it takes few seconds after the system is loaded. Sometimes you should reboot several times to complete the procedure.
Preinstalled apps:
NOTE: none of the apps included in my ROM it's pirated or modded: all free versions!
Code:
ADAway You should not need to open it because hostfile is yet ready to block ADS
Chrome + Webview
Google Voice Search
SPMC 16
Netflix (Edit build.prop change service.bootvideo=0 for a unknown reason netflix in some country give error 0013 if that prop is setted to 1)
MxPlayer [B]In /system/Media there are the better codec from XDA Thread, just set it in preferences[/B].
Total Commander + 3 useful plugins
YouTube
Terminal Emulator
BootManager [B](to be activated in Xposed installer)[/B]
XposedInstaller 3.11 + BootManager plugin
Reboot app
If you're scared to lose OTA updates, don't worry, if a update will come out i'll upload a new upgraded mod.
WARNING:
I'm not responsible and nor the forum that hosts my ROM is, of any damage or malfunction caused on your device, during the flash or the use of my ROM.
You'll take the responsibility of what you do.
My Roms cannot brick your device, but you can flashing it improperly. I'm not a chinese box help center i hope you'll understand what i mean
To burn my Rom you need Amlogic_USB_burning_tool_2.0.8 and a male to male USB cable, 1 male to your pc, the other on the usb port near the HDMI.
you can follow this guide: http://androidpcreview.com/how-to-use-the-amlogic-usb-burning-tool-to-manually-update-firmware/3749/
Or you can use Sd cardMaker and on terminal type reboot update though i prefer you'll use Usb flashing:
Amlogic Usb Burning tool 2.1.2:
https://mega.nz/#!i8pxACKC!EIP9DucLY...7-j3r-NKDBEjFs
TF/SD Burn Card Maker 2.0.3:
https://mega.nz/#!SowFiSID!mEk8gp5qN...xYS5xviDNSUdE8
XTMOD EX 3.0 standard version
RELEASE NOTE/MODIFICATION FROM PREVIOUS VERSION:
- Updated Google Play Services;
- Updated Google Play (market);
- New app list: - Amazon Prime;
- Adaway
- Aptoide (very useful sometimes, but be careful);
- Google Chrome;
- Google Calendar;
- Google Play Music;
- Google Play Videos;
- Google Voice Search;
- Terminal Emulator;
- MX Player;
- Netflix;
- SPMC;
- Total Commander;
- XposedInstaller + Youtube Adaway + BootManager Modules;
- Youtube.
All the apps are at the last version available during compilation.
- Fixed a stupid bug in kernel, it was just a typo;
- Some automatic script revised or removed;
- Pre-Setted some apps (Mxplayer, Xposed Total Commander and SQHome Launcher);
- New Bootlogo, New Bootvideo, New Bootanimation, New Wallpaper;
- Many thing very important that i forgot to write down
(because pratically i ported my PERSONAL rom).
DOWNLOAD LINKS:
XTMOD 3.0 for TvBoxes with motherboard P212 with wifi chipset : AP62X2, AP4354, AP4356, AP6212, AP6212A, AP6255, AP6335, AP43458, AP6330, 8723xx (Bluetooth not working), 8188XX, 8189XX, 8192XX, 8812XX
If you have a 9377 wifi chip device flash the image, then after the first boot is complete, go to recovery and install this file:
- wifi 9377 twrp file
- XTMOD 3.0 for D4X16 Motherboard
Some new Mini M8SII comes out with a new motherboard, is green, there is a label D4X16, you can see that label just opening the device, for the one and just for the one with such motherboard, do not flash it on normal Mini M8SII.
- XTMOD 3.0 for NexBox A95x 2/16 (should work also for 1/8) repacked by ssarava9 with remote power functional.
(in message #1887 he posted a description of what he did to eventually try yourself)
For the users that got Google Play Bug i prepared a zip to be flashed trough twrp.
I tested myself but let me know if all it's ok
XTMOD3_MARKETFIX
NOTE: I WILL NOT REPLY TO STUPID QUESTION ABOUT WICH WIFI CHIP MY DEVICE HAS AND SIMILAR GOOGLE IT'S YOUR BEST FRIEND
PLEASE DO NOT USE THIS ON NORMAL MINI M8SII OR YOU'LL BRICK YOUR DEVICE. Enjoy!
If you like my works and would you like to offer me a beer or a coffe or simply a sign of appreciaton for me: SEND ME A DONATION
Hi, impressive job. well done. Is there a way to upgrade without a windows pc?
nowaard said:
Hi, impressive job. well done. Is there a way to upgrade without a windows pc?
Click to expand...
Click to collapse
Yes, i hope tomorrow i'll upload a zip version
Xannytech said:
Yes, i hope tomorrow i'll upload a zip version
Click to expand...
Click to collapse
My first cup of cofee has been sent to you!
nowaard said:
My first cup of cofee has been sent to you!
Click to expand...
Click to collapse
ZIP file added, let me know.
EDIT: better not to use the zip cause 1 user found an error in the updater script, i will investigate and i'll repost a zip file ASAP maybe next week, i have too much project opened now. sorry.
Xannytech said:
ZIP file added, let me know.
EDIT: better not to use the zip cause 1 user found an error in the updater script, i will investigate and i'll repost a zip file ASAP maybe next week, i have too much project opened now. sorry.
Click to expand...
Click to collapse
I have used it! and It works like a charm. The process takes some time but it ends well. I've used a USB instead of SD card.
Thanks a lot.
Thanks a lot for your support and your report
Zip version for twrp?
Workaround for Brightness bug
Click to expand...
Click to collapse
details can be?
DenisDeneck said:
Zip version for twrp?
details can be?
Click to expand...
Click to collapse
Few dirty tricks with the brightness, nothing more, it's a problem of colorspace unavoidable if your TV hasn't the right setting.
Some Updates:
I got some freetime today so i checked the zip... ok i understand what appened... 7zip for a strage reason used an old script that could cause some issue.
During that examination i add very nice (but untested) feature to my zipfile script. So now it copy the old (i hope working) remote.conf from /system/etc/ copying back at the end of the flashing.
But i removed the device chek so please if you flash that zip in a uncompatible device it's not my fault
TWRP:
I decided to add TWRP Recovery by default, work well but you need a wired mouse to operate with recovery...
Everything online!
Enjoy:good:
Update:
I checked v109Fw from VONTAR for MINI M8S+ it's IDENTICAL to V106 so it's a VONTAR custmization of the V106 fw it has just the USB Kb fix and a fix in Kodi setting yet in mine custom, so there is nothing new, and something in setting.apk that seem lightly different.
So i will not work on a custom rom of it, it has no upgrade in system, no upgrade in fixes.
I know that many users downloaded my custom Rom, could you just write me your impressions, or a feedback. Thanks.
Does this ROM have a fix for HEVC/x.265 files that are encoded in 10bit? My firmware displays those files in greenish garbage on the screen when using Kodi.
drdoolittle said:
Does this ROM have a fix for HEVC/x.265 files that are encoded in 10bit? My firmware displays those files in greenish garbage on the screen when using Kodi.
Click to expand...
Click to collapse
I personally had not problem to play X265 files with Kodi.
Unfortunately I have when not using amcodec acceleration. When I use it, HEVC 10bits play fine, but Kodi then crashes on me.
drdoolittle said:
Unfortunately I have when not using amcodec acceleration. When I use it, HEVC 10bits play fine, but Kodi then crashes on me.
Click to expand...
Click to collapse
Using my Rom or with your firmware? cause i never found a hecv file that gives me problem, and i'm using kodi 17 beta 6 so no amcodec
Some news on my work on this Custom Rom
Actually i have ready a new revised version of the Rom, but i'm waiting if someone can give me v107 firmware (if really exist).
What i did until today (not yet uploaded):
- Init.d Support Built in (without any external program);
- Removed Init.d Zipalign script pratically unuseful on 6.01;
- Added Sd speed optimization tweak:
- Fixed a unharmful and almost invisible linking bug caused by Amlogic Customization Tool that i used for fast customization process.
- Added in Kernel AutoRefresh Chmod Permissions;
- System Memory optimizations;
- Updated some apk;
- Removed some unuseful APK
- New DarkScreen fix Workaround (full/limited colorspace problem)
To do before release (i hope):
- Add Reboot Option on power menu - but it gave me many headaches.
- Chromecast Service
- Reworking on more elegant solution for some fixes.
After that release if all will be OK, i will just work on a Android TV Version, probably unaploadable on forums cause i should use so many dirty hacking to apks, but i hope i can find a more "elegant" way.
Wow sounds good. At first spare time will try it immediately. Just have to install TWRP on my box.
Изпратено от моят HUAWEI GRA-L09 с помощта на Tapatalk
TopperBG said:
Wow sounds good. At first spare time will try it immediately. Just have to install TWRP on my box.
Изпратено от моят HUAWEI GRA-L09 с помощта на Tapatalk
Click to expand...
Click to collapse
Why do you need TWRP? my rom will install TWRP by default.
Which device do you have?
And not to be misunderstood the list i just published it's a new version not uploaded yet.
For backup
I've got MINI M8s X905 2/16
Изпратено от моÑÑ‚ HUAWEI GRA-L09 Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰Ñ‚Ð° на Tapatalk
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation
- TWRP (I used 2.8.2.0)
- advanced wipe recomended (rom has gapps included)
- install as any other custom rom
- IMPORTANT : optimizing google play services can take some time ! took on my device 1-2 minutes.
- Initial bluetooth pairing can be skipped by using "ESC" key from keyboard or wait 2-3 minutes, the google setup via your smartphone is functional (worked for me )
bugs:
- Cast Receiver (youtube App) : sometimes it works, while it shouldn't (logcat indicates invalid certificate - as we don't have an official supported device i'm afraid I can't fix this) (removed)
- Bluetooth MOJO controller - doesn't always pair or re-pair after reboot - could be ROM related or controller related. Once paired it works quite good. more stable with lineageos 13 !
- Don't update the youtube app ! the App will crash as we currently don't support rastarization (OpenGL ES v3) https://www.chromium.org/developers/design-documents/chromium-graphics/how-to-get-gpu-rasterization
-If the installation get stuck on "finishing boot" -> wait 10 seconds, then hard reboot (pull the power) - this in only needed once.
changelog:
Code:
[B][U]lineageos-13.0-20180324-UNOFFICIAL-mojo-AndroidTV[/U][/B]
- Updated the sound config of the MOJO - HDMI sound stability is increased
- updated google assistent app to latest version
[B][U]lineageos-13.0-20180311-UNOFFICIAL-mojo-AndroidTV[/U][/B]
- Reverted the device drivers back to the ones from the initial release.
- removed google cast receiver as it continuously reports issues and as such uses resources.
- if you want cast support - I recommend installing [URL="https://play.google.com/store/apps/details?id=com.ionitech.airscreen"]https://play.google.com/store/apps/details?id=com.ionitech.airscreen[/URL]
- Default google App has been updated - to enable google assisent support - I'm testing stability.
[B][U]lineageos-13.0-20180204-UNOFFICIAL-mojo-AndroidTV[/U][/B]
New PowerHAL and AudioHAL from molly thanks to nono2loreze!
Android TV remote - voice search now functional due to new AudioHAL !
Included googlewebview by default
Other improvements from nono2loreze (ntfs support, new bluetooth config)
[B][U]lineageos-13.0-20180106-UNOFFICIAL-mojo-AndroidTV[/U][/B]
Update to match the configuration updates from nono2loreze
NTFS support is [B]NOT[/B] yet included
[B][U]lineageos-13.0-20180101-UNOFFICIAL-mojo-AndroidTV[/U][/B]
- Upgread to lineageos 13
- updated gapps to work in combination with 6.0.1 - borrowed from ADT-1 purenexus made by dhacker29
- synced bluetooth configuration from molly
- default media player plays more video formats then the one on cm-12.1
[B][U]cm-12.1-20171229-UNOFFICIAL-mojo-AndroidTV[/U][/B]
- First release :laugh:
- Leanback launcher 6.x
Location of the ROM:
Code:
File name : lineageos-13.0-20180324-UNOFFICIAL-mojo-AndroidTV.zip
[URL="https://drive.google.com/open?id=1TzuB1GcIMifW7CKYIhRwLEA90mE9i41A"]https://drive.google.com/open?id=1TzuB1GcIMifW7CKYIhRwLEA90mE9i41A[/URL]
File name : lineageos-13.0-20180311-UNOFFICIAL-mojo-AndroidTV.zip
[URL="https://drive.google.com/open?id=1Ov-uW_7s1JTk-EBa7yZxge1TFtPYtMf3"]https://drive.google.com/open?id=1Ov-uW_7s1JTk-EBa7yZxge1TFtPYtMf3[/URL]
File name : lineageos-13.0-20180204-UNOFFICIAL-mojo-AndroidTV.zip
[URL="https://drive.google.com/open?id=1ByPb9bk5rG2Hq6pX8-YMiTuqgCyh9CQG"]https://drive.google.com/open?id=1ByPb9bk5rG2Hq6pX8-YMiTuqgCyh9CQG[/URL]
File name : lineageos-13.0-20180106-UNOFFICIAL-mojo-AndroidTV.zip
[URL="https://drive.google.com/open?id=13gqJ2wiq4Z458JzW8so4DA77VMVL6oFR"]https://drive.google.com/open?id=13gqJ2wiq4Z458JzW8so4DA77VMVL6oFR[/URL]
File name : lineageos-13.0-20180101-UNOFFICIAL-mojo-AndroidTV.zip
[URL="https://drive.google.com/open?id=1pZILaAXGwQE_SJWn4QvSod5w1kL-AJnw"]https://drive.google.com/open?id=1pZILaAXGwQE_SJWn4QvSod5w1kL-AJnw[/URL]
File name : cm-12.1-20171229-UNOFFICIAL-mojo-androidTV.zip
[URL="https://drive.google.com/file/d/1mAWBJ-Unbb5PKTmO9wYeHcFGjuY4xAxd/view?usp=sharing"]https://drive.google.com/file/d/1mAWBJ-Unbb5PKTmO9wYeHcFGjuY4xAxd/view?usp=sharing[/URL]
Next step:
- fix the stuck at first boot
- Experiment more with newer gapps
- Port to lineageos 13
- port upgreads form github/Tegra4
Enjoy!
XDA:DevDB Information
Lineageos 13.0 AndroidTV, ROM for the Mad Catz M.O.J.O.
Contributors
carp_be, nono2lozere, Unjustified Dev
Source Code: https://github.com/dide0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: lineageos
Version Information
Status: Beta
Current Beta Version: 6.0.1_r81
Beta Release Date: 2018-01-06
Created 2017-12-29
Last Updated 2018-03-26
Frequently asked questions & Tips:
Thanks to minmao:
Q: Is it possible to add an option to change the display resolution as in the stock from? My TV is a 4k set and Mojo boots into 4k automatically, however, since it only supports 4k at 30 fps, everything seems so slow and games are impossible.
A: if you choose best framerate in developer options, it gives 1080p60. Now it is perfect. Thanks again!
Q: Are gapps pre-installed in this ROM?
A: Yes, all basic gapps for androidTV are available
Q: is SU enabled by defaults
A: No, but if you want to have SU, check the detailed install instructions below for more info
Q : Any detailed install instruction ?
A : https://forum.xda-developers.com/showpost.php?p=75093267&postcount=41 thanks to King_Dex (please note flashing gapps is not needed atm).
Other tips:
The google assistent can also be enabled by sideloading the following APP:
[url]https://www.apkmirror.com/apk/google-inc/google-app-for-android-tv-android-tv/google-app-for-android-tv-android-tv-3-2-0-187674027-release/[/URL]
Works quite OK, but cannot integrate with Google Home App - so no control from a google home speaker .
The nvidia games (versioin 4.X) can also be sideloaded if people are interested , but don't try the 5.X, this will NOT work.
[url]https://www.apkmirror.com/apk/nvidia/nvidia-games/nvidia-games-4-17-21865207-release/[/URL]
Cast support : as the official google cast app is not fully functional , this App has been removed in new builds.
I recommend using :https://play.google.com/store/apps/details?id=com.ionitech.airscreen as an good alternative
Carp_be, do you have any donation link, I would be pleased to donate some " as others" I think so
P.S. or make one with : nono2lozere
Wmapa said:
Carp_be, do you have any donation link, I would be pleased to donate some " as others" I think so
P.S. or make one with : nono2lozere
Click to expand...
Click to collapse
Hey Wmapa, it's nice to propose this but for me this is a hobby project I'm not going to accept donations (how strange this might sound). If you want to do a donation then donate something to UJD, nono2lozere or lineageos. I'm just using their work to build something without their effort I would not been able to produce my "rom"'s.
It is such a nice surprise for new year!
Thank you thank you thank you!!!
Hi carp_be,
Is it possible to add an option to change the display resolution as in the stock from? My TV is a 4k set and Mojo boots into 4k automatically, however, since it only supports 4k at 30 fps, everything seems so slow and games are impossible.
≠======
I figured out: if choose best framerate in developer options, it gives 1080p60. Now it is perfect. Thanks again!
hello, great job, gave me a couple of failures at the first start. to configure it, wifi networks did not appear. connected by cable all good. Install kodi and I think there is a problem when going out and entering that sound does not work. but still it is magnificent. we wait for a new compilation fixing faults. thanks again
New build is available thanks to the effort of nono2loreze
PS : still don't update youtube App - it will still crash :'( (busy checking for solution)
Scrash313 said:
hello, great job, gave me a couple of failures at the first start. to configure it, wifi networks did not appear. connected by cable all good. Install kodi and I think there is a problem when going out and entering that sound does not work. but still it is magnificent. we wait for a new compilation fixing faults. thanks again
Click to expand...
Click to collapse
During my "tests" I rarely had issues with WiFi , I do remember that 1 time during the setup 1 had to retry 2-3 times with connecting to my network before the M.O.J.O wanted to setup a connection.
Related to your sound issue,I installed kodi on the last build and I could not "reproduce" your issue. Please try out the latest build
carp_be said:
During my "tests" I rarely had issues with WiFi , I do remember that 1 time during the setup 1 had to retry 2-3 times with connecting to my network before the M.O.J.O wanted to setup a connection.
Related to your sound issue,I installed kodi on the last build and I could not "reproduce" your issue. Please try out the latest build
Click to expand...
Click to collapse
to reproduce the problem of kodi you have to exit the program with the exit button that has kodi up to the left (do not minimize) and when entering again the sound is not heard.
Let me share some experience that may help other users using this great rom:
1. The lastest xposed installed and worked on the latest version via recovery. As you might know, the anroid TV does not support mouse right click (the same thing on the shield tv). I was able to use 'xposed addition" module to map the menu key on my air mouse to exit key, so I could have total control of the mojo without using the controller, which is heavy and stiff. Although I still have to use it to wake the mojo from sleep, since my air mouse could not. Also long press the power button on the air mouse will bring out the shutdown/restart menu.
2. If you have a 4K tv and want to have higher resolution of youtube, you could sideload the mobile version of youtube APK and you could get 1440p video. I also used youtube+ in xposed to select 1440p by default. Although I could not really tell the difference from 1080p...I tried to tell myself it does look better...
Thanks again to carp_be for the great rom and quick updates. I almost feel silly to buy a shield TV, since the mojo now could satisfy most of things I did with a shield TV.
No luck this week, I ran again into the issue with not booting on first startup with my latest build. Next week I'm ski-ing holiday, so next update would be probably middle of February
Hi there! I just came here from the fb mojo group, because I have an (stock) mojo with some problems (the system upgrade is broken), and I'm trying to install the LineageOS using @King_Dex guide (thanks, by the way), and I'm stuck in TWRP, I'm not sure I'm following the instructions right...
First of all, I have all the files recommended so far, Installed Towelroot v1, and using flashify booted using the twrp mojo img (twrp_3.2.1-0_mojo.img), but, that is! TWRP doesn't show me my SD Card (32GB SD card in a basic cardreaderm in the USB 2.0 port)
So, TWRP has any option to mount my SD card? I really hope you can help me, I want to see what I can do with the MOJO :fingers-crossed:
Thanks in advance!
Al.
TheHardCL said:
Hi there! I just came here from the fb mojo group, because I have an (stock) mojo with some problems (the system upgrade is broken), and I'm trying to install the LineageOS using @King_Dex guide (thanks, by the way), and I'm stuck in TWRP, I'm not sure I'm following the instructions right...
First of all, I have all the files recommended so far, Installed Towelroot v1, and using flashify booted using the twrp mojo img (twrp_3.2.1-0_mojo.img), but, that is! TWRP doesn't show me my SD Card (32GB SD card in a basic cardreaderm in the USB 2.0 port)
So, TWRP has any option to mount my SD card? I really hope you can help me, I want to see what I can do with the MOJO :fingers-crossed:
Thanks in advance!
Al.
Click to expand...
Click to collapse
Hi!
While in TWRP Recovery Mode, the system can only read the internal storage (sdcard0) and the external storage (sdcard1, which is the SD card slot). It cannot recognize any USB devices connected to it, and you have to directly insert your SD Card (along with the files you need) inside the specific SD Card slot of the Mojo (near the HDMI port).
EdoNINJA93 said:
Hi!
While in TWRP Recovery Mode, the system can only read the internal storage (sdcard0) and the external storage (sdcard1, which is the SD card slot). It cannot recognize any USB devices connected to it, and you have to directly insert your SD Card (along with the files you need) inside the specific SD Card slot of the Mojo (near the HDMI port).
Click to expand...
Click to collapse
Thanks! worked just right... Just finished flashing lineage, but when I was flashing the gapps arm 6.0 (stock), twrp freezed, and I had to reboot... now is booting lineageos (looking good!), but missed gaapps and addonsu... can I install them from lineage? or do i need to start again?
Update: errr... I'm doing some basic test, and the google store (androitv, I think) is working just fine... I'm kind of a lost of what to do next, any sugestions? (do I need addonsu?)
Thanks!
TheHardCL said:
Thanks! worked just right... Just finished flashing lineage, but when I was flashing the gapps arm 6.0 (stock), twrp freezed, and I had to reboot... now is booting lineageos (looking good!), but missed gaapps and addonsu... can I install them from lineage? or do i need to start again?
Update: errr... I'm doing some basic test, and the google store (androitv, I think) is working just fine... I'm kind of a lost of what to do next, any sugestions? (do I need addonsu?)
Thanks!
Click to expand...
Click to collapse
Flashing gapps is not recommended on this androidTV rom. I've included the majority of google apps needed for AndroidTV. If you think this rom is missing a major gapp, you can sideload it via the file explorer. Please let me know which once you miss then I can check if I can include them in an next update.
Best what you could do is to wipe again all data (also system) and install the rom clean. Addonsu, if you really what this should be flashed once lineageos is flashed. You can always install this later via TWRP.
On my beta builds and own running build I each time install, VLC player, MX player, these give good codex support and DS video so I can stream video's from my synology NAS.
Hi carp_be,
I would like to report an issue I just noticed.
For some reason, the resolution trick I posted no longer work in the 0106 rom, even when "optimzed refresh rate" is selected, the Mojo is stuck at 4K30 instead of going to 1080P60.
I had to flash my mojo back to the 0101 rom to get back the 1080p60 mode.
Not sure what you did differently with the newer rom, but it would great if we could get the option working again in the future release. Of course, I am happy using the 0101 rom as is.
minmao said:
Hi carp_be,
I would like to report an issue I just noticed.
For some reason, the resolution trick I posted no longer work in the 0106 rom, even when "optimzed refresh rate" is selected, the Mojo is stuck at 4K30 instead of going to 1080P60.
I had to flash my mojo back to the 0101 rom to get back the 1080p60 mode.
Not sure what you did differently with the newer rom, but it would great if we could get the option working again in the future release. Of course, I am happy using the 0101 rom as is.
Click to expand...
Click to collapse
It should be due to new proprietary blobs. Maybe a build.prop trick exist, but I don't know it.
minmao said:
Hi carp_be,
I would like to report an issue I just noticed.
For some reason, the resolution trick I posted no longer work in the 0106 rom, even when "optimzed refresh rate" is selected, the Mojo is stuck at 4K30 instead of going to 1080P60.
I had to flash my mojo back to the 0101 rom to get back the 1080p60 mode.
Not sure what you did differently with the newer rom, but it would great if we could get the option working again in the future release. Of course, I am happy using the 0101 rom as is.
Click to expand...
Click to collapse
nono2lozere said:
It should be due to new proprietary blobs. Maybe a build.prop trick exist, but I don't know it.
Click to expand...
Click to collapse
I'm having mixed feelings with the new video drivers :/ my Sony surround system (bdv e880) doesn't properly work in combination with the mojo since the new drivers (flickering on 720p - 1080p is fine) . The original molly drivers didn't had this issue. So I'll revert the drivers in next build as i'm mainly viewing on 720p tv atm . Hope this solves the "optimized refresh rate".
Next week I have again some time to start building the improvements from nono2lozere :victory:
New update available ! thanks to the new audio HAL from nono2lozere, voice search in the androidTV remote app is now working! really cool
The google assistent can also be enabled by sideloading the following APP:
https://www.apkmirror.com/apk/google-inc/google-app-for-android-tv-android-tv/google-app-for-android-tv-android-tv-3-1-2-179594536-release/
Works quite OK, but cannot integrate with Google Home App - so no control from a google home speaker .
The nvidia games (versioin 4.X) can also be sideloaded if people are interested , but don't try the 5.X, this will NOT work.
https://www.apkmirror.com/apk/nvidia/nvidia-games/nvidia-games-4-17-21865207-release/nvidia-games-4-17-21865207-android-apk-download/
{
"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"
}
These Screenshots are from the Free version
CurveUI DarkOOS Theme for OxygenOS (OOS)This theme works with the latest Substratum
The theme currently supports any device running OxygenOS 11 (OOS 11)
Features:-DarkUI and Notifications
-Stylish Curved Corners in Notifications and some other areas
- Transparent StatusBar when pull down QS Panel/Notifications
- DarkBackgrounds
- Different Accent Colors available (Paid via PlayStore)
- Custom Accent Color options for Notification Icons and Title Texts available (Paid via PlayStore)
- Different Style Gradient Colors for Corners (Paid via PlayStore)
NOTE: To Enable Blur effect as shown in the Screenshots, you need to install this Magisk Module in Magisk Manager.
How to Install:1. Download and install this theme
2. Open Substratum and make sure no other theme is enabled
3. Open this theme and Select all
5. Reboot
6. After reboot open Substratum again and go to the manager
7. Tick all (this theme) and Enable selected.
8. Then Turn off Dark Mode and Turn it on again for the complete UI changes (And the same will be needed after every reboot)
Themed Apps:- Ambient Display (In Paid Version)
- Android System (Base)
- Calculator
- Calendar
- Call Management
- Contacts
- Google Drive (In Paid Version)
- Duo
- OP File Manager (In Paid Version)
- Gboard (In Paid Version)
- Gmail
- Instagram (In Paid Version)
- Messaging App
- Phone/Dialer App
- Settings
- SystemUI
- SystemUI Headers
- WhatsApp (In Paid Version)
Download from free version here -Latest v1.4-> AndroidFileHost < CurveUI DarkOOS Free
The same theme is available on Google PlayStore as Paid with more features as mentioned aboveCurveUI DarkOOS v2.4 <- Link to Google PlayStore [You can check screenshots below]
Few Screenshots from Paid Version-
=====
Changelogs for both (free/paid) are in the next post below
=====
If you Like my works or like this mod
- You can donate me by buy me a coffee of your choice
Or
- You can Donate me here - Playstore Link
Regards
Reserved for future
Clean install, never used substratum before
Installed with errors.
11.0.10.10 BA stock rooted, stock kernel.
Update: after reboot enabled all layers.
Ui is themed, but settings is an odd colour.
Yep seems to be Android system they won't install.
Shame as it looked alright..
Nvm
dladz said:
Yep seems to be Android system they won't install.
Shame as it looked alright..
Nvm
Click to expand...
Click to collapse
After installing the layers you want in substratum lite you reboot. Then you go back into substratum lite. Enable all layers. Reboot again for system to pick up theme. After you reboot from now on you will need to go into substatum lite then 3 dot menu hit restart system UI.
dladz said:
[Mod Edit] Post removed as requested by author
Click to expand...
Click to collapse
Normal doesn't work well with a11
dladz said:
[Mod Edit] (post removed)
Click to expand...
Click to collapse
At first, I am sorry for that happened to your device.
If you have Magisk (every rooted user have this now)
Substratum installs Magisk Module with overlays. So disabling/removing Magisk Modules will also disable/remove all overlays installed with Substratum.
The safe recovery was in your hands but may be you got panic so early.
If you had TWRP Recovery
You just needed to install Substratum Rescue zip file in recovery. That zip is placed in your device storage by Substratum itself.
But I gues you were not having TWRP (That I don't know how and why)
So Safeboot was fine for you. But.....Oops.
=======
It was just a theme, it was not playing with the system or affectinf the system.
UI crashes after enabling substratum themes means....theme doesnt get installed properly and etc.
When you changed from normal substratim tl lite one, did you disabled overlays from substratum?, Then uninstall overlays from substratum?, Then reboot system
After reboot uninstall substratum..
And then install lite substratum, then install theme, reboot, enable.
As you said, you are using Substratum first time so obviously, there should lack of knowledge because there are many changes after Android 9 but Substratum never got updated after that so its partially compatible with our latest software devices.
But lack of knowledge, thats fine. Its just not you only. But blaming someone or someone's work just because you are not having much knowledge its wrong.
For your extra knowledge- As of today, Lite version is more stable than the normal Substratum.
As in a first try when you installed theme, its get installed but incompletely as you have mentioned above and also we can see screenshots.
So them was compatible, but what I can guess is when you changed to lite one, you messed it by mistake and results are in your hand.
Regards
Mohitash
dladz said:
Cool it.
Earlier on I removed my posts and have requested a clean up... Way before you mentioned this.
I responded here because he did, I also contacted via PM.
Also you may want to clarify your instructions too buddy, first thing you see here is an APK. Nothing to do with magisk mentioned.
Just a thought
Click to expand...
Click to collapse
Any substratum theme is an Apk file
Substratum itself is an Apk file
Any android app is an Apk file
Substratum do install its Magisk Module and save overlays there that works systemlessly as Magisk works like that.
For an example, check screenshots below, this module is created by Substratum Lite.
Other OnePlus 6/7/8/9 Pro/Non-Pro users already using this theme without any issues.
I am responding very softly as I always do as I have patience obviuosly. Dont take my any word hard but please its already clear about your lack of knowledge about Substratum but its not a bad thing at all, its usual thing with many users including me in many cases. But not accepting the truth again and again is wrong.
And check first post again, instructions already given.
Yes You cleared all your posts. Thats really nice of you. Thanks.
When you posted your issue...
before it got resooved, you already messud up with the device.
Again sorry about your data loss.
Regards
Mohitash
Mohitash said:
Any substratum theme is an Apk file
Substratum itself is an Apk file
Any android app is an Apk file
Substratum do install its Magisk Module and save overlays there that works systemlessly as Magisk works like that.
For an example, check screenshots below, this module is created by Substratum Lite.
View attachment 5509929
Other OnePlus 6/7/8/9 Pro/Non-Pro users already using this theme without any issues.
I am responding very softly as I always do as I have patience obviuosly. Dont take my any word hard but please its already clear about your lack of knowledge about Substratum but its not a bad thing at all, its usual thing with many users including me in many cases. But not accepting the truth again and again is wrong.
And check first post again, instructions already given.
Yes You cleared all your posts. Thats really nice of you. Thanks.
When you posted your issue...
before it got resooved, you already messud up with the device.
Again sorry about your data loss.
Regards
Mohitash
Click to expand...
Click to collapse
It's cool, don't worry about the data, my important stuff is safe on cloud sync, it's just banking apps I need to set up again so will need to call them and work 2FA.
My knowledge with substratum is patchy.
In the past I've installed the app, obtained a theme from the play store and then installed overlays in substratum, then enabled and rebooted to finalize the changes.
Most themes worked but some didn't, there used to be a recovery from recovery (TWRP) but I wasn't at home so couldn't get it.
Also safe mode wouldn't load up as the phone would only say:
System has stopped working
Wait
Close
So I would not have been able to disable the module if that was the cause, that recovery method would have worked perhaps, however I needed my phone at the time so had to commit to wiping system, again my fault.
As I said before my OOS was stock, 11.0.10.10BA
One mod: center clock that alters OPSystemUI.apk
Could have been that perhaps, but nothing else was installed.
Your one did indeed work, it was just the colours on settings that was different.
I've used this opportunity to jump back to a custom ROM, I only came back to OOS so I could pull the boot image and patch it for my guide, so people can use them, has helped a good few people out.
[Mod Edit] (Derogatory comment removed) I posted my findings, not sure what else I could have done differently?
Anyway, my phone's nicely themed now so I'm all good.
Appreciate your work btw, it does look nice.
PS: maybe advise to use the lite version of substratum.
Disable any mods before installation
Might make the difference.
dladz said:
It's cool, don't worry about the data, my important stuff is safe on cloud sync, it's just banking apps I need to set up again so will need to call them and work 2FA.
My knowledge with substratum is patchy.
In the past I've installed the app, obtained a theme from the play store and then installed overlays in substratum, then enabled and rebooted to finalize the changes.
Most themes worked but some didn't, there used to be a recovery from recovery (TWRP) but I wasn't at home so couldn't get it.
Also safe mode wouldn't load up as the phone would only say:
System has stopped working
Wait
Close
So I would not have been able to disable the module if that was the cause, that recovery method would have worked perhaps, however I needed my phone at the time so had to commit to wiping system, again my fault.
As I said before my OOS was stock, 11.0.10.10BA
One mod: center clock that alters OPSystemUI.apk
Could have been that perhaps, but nothing else was installed.
Your one did indeed work, it was just the colours on settings that was different.
I've used this opportunity to jump back to a custom ROM, I only came back to OOS so I could pull the boot image and patch it for my guide, so people can use them, has helped a good few people out.
[Mod Edit] (Derogatory comment removed) I posted my findings, not sure what else I could have done differently?
Anyway, my phone's nicely themed now so I'm all good.
Appreciate your work btw, it does look nice.
PS: maybe advise to use the lite version of substratum.
Disable any mods before installation
Might make the difference.
Click to expand...
Click to collapse
Cool. But always remember to take these conversations to PM directly to the same person that is involved and avoid spamming in any thread.
And for any work/theme/mod you must always ask support/complain/feedback to that mod/theme thread or any group created by the same developer(s) of that theme/mod if that exists. Also avoid compaining to any other person, instead do ask support in that theme/mod thread
Now lets stop this topic
Peace
Regards
Mohitash
[Thread Cleaned] All that negative energy... On a Sunday no less! Let's just assume there was some steam that needed to be vented and let's hope the frustrations are behind us now. Remember that we're still all just people that share a passion for tech. And with such passion there inevitably comes a passionate discussion from time to time. It happens. I do heartily invite the involved parties to get in touch with one another to talk this out if needed. Just don't let it linger in here and please keep it polite and respectful.
Thank you and have a great remainder of your Sunday folks
Timmy
Forum Moderator
AFH keeps saying no mirrors found!
Can't download files
Dhanuawatade said:
AFH keeps saying no mirrors found!
Can't download files
Click to expand...
Click to collapse
They work fine . Try again
FreshlyBaked 420 said:
They work fine . Try again
Click to expand...
Click to collapse
Yeah tried again works now.
I think AFH was down that day