Everyone,
I tried to use one of the tricks I used on my Galaxy S5 to change the screen density without root, but I can't find one that works. When I change it to anything but 640, on bootup I get "System UI has Crashed." Anyone have ideas?
The method I use to do is
Command Prompt -> adb shell
"grep | wm density" to get the original density (which I found to be 640)
"wm density [New Density]" (tried 600 & 610 and fails to start)
The second screen is doing it. A more experienced dev is gonna have to start looking into how it ties into the system files.
Alright cool, I turned it off but I'm assuming it still probably checks it at boot and doesn't know how to interpret a density that small. Thanks! Hopefully it can be fixed because I really like having smaller density system wide.
Related
Hey gang,
I am trying to create a script (using GScript Lite) that will preview the boot animation currently loaded. I am running 2.1 leak v3 and don't have root yet. I made a script with only one line like this: "adb shell bootanimation" and saved it. When I try to run the script I get the "permission denied" error. I guess I need root to run the command locally on the phone. Odd though.... because I can run the command from my computer connected via USB and it works just fine. Can anyone explain why its not working locally when I run the script? Surely it does not trigger root access when running this command from a computer.... does it?
Curious....
Also, is there another way around this so I can accomplish previewing the boot animation on my phone without external input? I searched the market and installed the app called "Boot Animation Preview Lite". It required AndExplorer to be installed to work.... but it never did actually work. Only Force Closes on every attempt.
synaptyc said:
Hey gang,
I am trying to create a script (using GScript Lite) that will preview the boot animation currently loaded. I am running 2.1 leak v3 and don't have root yet. I made a script with only one line like this: "adb shell bootanimation" and saved it. When I try to run the script I get the "permission denied" error. I guess I need root to run the command locally on the phone. Odd though.... because I can run the command from my computer connected via USB and it works just fine. Can anyone explain why its not working locally when I run the script? Surely it does not trigger root access when running this command from a computer.... does it?
Curious....
Also, is there another way around this so I can accomplish previewing the boot animation on my phone without external input? I searched the market and installed the app called "Boot Animation Preview Lite". It required AndExplorer to be installed to work.... but it never did actually work. Only Force Closes on every attempt.
Click to expand...
Click to collapse
Have you tried
Code:
adb shell bootanimation
I doubt it needs root to be run but that will show you the boot animation and it will keep looping until you stop the command which on windows is control C
lol.... did you even read my post?
rofl
synaptyc said:
lol.... did you even read my post?
rofl
Click to expand...
Click to collapse
Lol probably not...
when running it from the phone where is it running from?
also if you are running it from phone it doesn't need the adb shell part
it should be
Code:
bootanimation
^^ I tried this from a terminal but it doesn't work unless I give the terminal su privilages.
so there might not be a way to do this on the phone without root privilages.
Sorry I couldn't be any help.
Its all good t2noob. Thnx for the info... food for thought.
Time to write an app for that =)
results so far:
I created a GScript called "bootscreen" (because I am using a bootscreen with sound and not a "bootanimation.zip"
I checked 'Needs SU?' because I now have root
Then I added the line: bootanimation
All goes well, and I can see/hear my bootscreen BUT I can't end it.
It continually loops like it is supposed to.
Can anyone tell me how to kill the bootanimation once it has been called via GScript Lite?
Things I have tried:
hitting the BACK, HOME, MENU, END/OFF buttons. really every button on the phone.
tapping the place on the screen where I have a "QuitIt" widget that will kill all running apps
The phone will accept screen input because I can tap where certain apps are and tell that they are launching. IE: phone, music player, etc.
I was even able to reboot the phone using Quick Boot just because I knew where the on-screen buttons were to make it reboot.
There seems to be no way to kill the bootanimation except to pull the battery.
Maybe I could create a GScrpit that will kill it, then just know where it is on the screen behind the animation?
Any tips?
EDIT: I created a script like this but it still didn't kill the bootanimation (it did run correctly with the sleep thing though)
Code:
bootanimation
sleep 10
pkill bootanimation
pkill boot1.gif
pkill boot2.gif
This is how I've done it through gscrip:
Code:
TIMEOUT=20
( bootanimation & sleep
$TIMEOUT; kill $! 2>/dev/null )
you can change the timeout duration to suit your liking (it's in seconds).
Regards,
Yahya
I have install and fought (and it has been a fight), to get Remix 2.0.205 installs in VMware and rooted , I actually wrote a script see the rooting thread to mount system rw to allow SuperSU to be updated. However when all is said and done yes it boots, but once rooted and if you update SuperSU as needed, the product is worthless as I'm unable to do anything without rebooting, for instance close chrome (reboot), install apk (reboot, also the app it is not installed), close settings, and click on some icons on the UI such as O.
So basically while you can configure and setup Remix in VMware and even root it, you can not use the OS once rooted, so it is basically useless, if you need root (who don't need root).
Tricks to getting it to work in VMware (that I've discovered):
Use a 32 freebsd as a base (not sure why that matters but it seems to)
use SATA drives, do not use GPT partitions.
Disable advanced graphics
I never could get Remix in VMWARE to run at anything other than 800x600 resolution, no matter what I tried changing DPI only changes text size did not for the display size used, I did not spend time fixing this as I can not used the rooted Image without it rebooting.
Can anyone explain why after updating SuperSU Remix OS fails to function, before updating SuperSU it had no issues, so it has something to do with updating the su binary (normal update as there is no recovery).
Thanks,
ERIC
did you replaced initrd.img with the modified one ?
looks like your system.img still has read-only
imadlatch said:
did you replaced initrd.img with the modified one ?
looks like your system.img still has read-only
Click to expand...
Click to collapse
Yes, I actually wrote a script to adjust the mounting of system.img, when read-only you can not even update SuperSU (fails), Also based on the use of the root prompt (F1) system is mounted read-write.
Actually it is not the OS that restarts, based on uptime but the Remix GUI.
Thanks,
ERIC
The firt U need Root your deives
The Su does not matter what happens
How to adjust the DPI screens
This index higher DPI interface will more loudly and more smooth, but not too big just as well as too large, then everything will be transferred to the interface of the phone should not be spending delectable . DPI is also to small too much content is displayed but text and icons are too small, so we can not see clearly, have pressed themselves into very uncomfortable eyes. Ideally for the middle in a bit tasty.
To change the DPI, the request must be root Remix OS, then you install the app on the Play Store TexdroidDPI about to reset. Extremely simple way of correction, simply enter your desired DPI on, then restart the operating system is finished.
Adjusting Screen Resolution:
Isn't there a way to adjust screen size or resolution, I feel the default image on the desktop gets cut at the bottom and was curious to see if I can play with resolution like we used to do on a windows desktop where we also adjust the icon sizes!!?
I used the DPI= kernel option for Remix OS. Without it I couldn't see my screen because it is 4k resolution, needed a magnifying glass. Think there are some apps in the play store that will allow you to adjust this. Not sure if they require root though. Now I am curious..........
Checked the Play Store and the DPI changer apps do require root.
erickh said:
I used the DPI= kernel option for Remix OS. Without it I couldn't see my screen because it is 4k resolution, needed a magnifying glass. Think there are some apps in the play store that will allow you to adjust this. Not sure if they require root though. Now I am curious..........
Checked the Play Store and the DPI changer apps do require root.
Click to expand...
Click to collapse
thanks very useful insight!
Hi Sany,
If you want a little more information on the subject you can go here http://technicalcultivation.weebly.com/android . I wrote a short article on the subject of changing your DPI on Android.
erickh said:
Hi Sany,
If you want a little more information on the subject you can go here http://technicalcultivation.weebly.com/android . I wrote a short article on the subject of changing your DPI on Android.
Click to expand...
Click to collapse
Your article is wrong you can set the resolution on android; via wm ie wm size 1204x768 and you can set dpi with wm density 140; and these don't require root afaik.
Thanks for the info, i'll look into it and update.
Alt+F1 to open the command console
wm density (dpi here), then enter
wm size (resolution here), then enter
Alt+F7 to close command window
(Note : This is very experimental. Be very cautious doing it inside open applications as well, and it does persist through reboots. You can easily muck up your display settings, and be forced into reinstalling a new data partition/full install, and it DOES have bearing on open applications, often leading into boot loops per few minutes).
HypoTurtle said:
Your article is wrong you can set the resolution on android; via wm ie wm size 1204x768 and you can set dpi with wm density 140; and these don't require root afaik.
Click to expand...
Click to collapse
How can I access those commands, wm size or wm density ??
chapa_9 said:
How can I access those commands, wm size or wm density ??
Click to expand...
Click to collapse
See post above.
Zeronomous said:
Alt+F1 to open the command console
wm density (dpi here), then enter
wm size (resolution here), then enter
Alt+F7 to close command window
(Note : This is very experimental. Be very cautious doing it inside open applications as well, and it does persist through reboots. You can easily muck up your display settings, and be forced into reinstalling a new data partition/full install, and it DOES have bearing on open applications, often leading into boot loops per few minutes).
Click to expand...
Click to collapse
Hello,
I get a permission error (java.lang.SecurityExcpetion: must hold permission android.permission.WRITE_SECURE_SETTINGS) if i use this command.
Do I have to root Remix OS for it?
G-DaX said:
Hello,
I get a permission error (java.lang.SecurityExcpetion: must hold permission android.permission.WRITE_SECURE_SETTINGS) if i use this command.
Do I have to root Remix OS for it?
Click to expand...
Click to collapse
I have the same error.
what should be done?
If you have installed GRUB, you can edit the start line (first tab, then follow the instructions so you can 'e' edit)
For an interactive choice you can add vga=ask, that will give an overview of the available modes.
If you want to add it permanently, you'll have to modify grub/menu.lst (using a live linux CD or so) and add vga=<your mode in decimal>
Only caveat is that vga=ask shows the mode in hex and you have to add it in decimal to menu.lst
flemlion13 said:
If you have installed GRUB, you can edit the start line (first tab, then follow the instructions so you can 'e' edit)
For an interactive choice you can add vga=ask, that will give an overview of the available modes.
If you want to add it permanently, you'll have to modify grub/menu.lst (using a live linux CD or so) and add vga=<your mode in decimal>
Only caveat is that vga=ask shows the mode in hex and you have to add it in decimal to menu.lst
Click to expand...
Click to collapse
and there is some or team to flip the image from portrait to landscape?
Has anyone been able to successfully change the DPI or resolution? I haven't actually tried any of the apps from the Play Store, I saw a few brick warnings; not for FHD6, but, just being cautious. Any ideas or suggestions about how to do this; safely? Apps you've used? Math used? etc., Im on the latest OS, rooted.
---------- edit ----------
I came across this approach which requires the Xposed Framework and a module called App Status; which can be used to change the dpi of a specific app.
Can anyone confirm if this is possible coming from the latest, rooted FireOS/Lollipop? I like the idea of changing the dpi per app oppossed to the entire device, so this would be ideal. Specifically using the @bibikalka 453 method?
Something like this?
# install xposed apk + app settings module
$ adb install de.robv.android.xposed.mods.appsettings_v29_70ccc5.apk
$ adb install XposedInstaller_3.1.1.apk
# get to twrp
453_key-images.zip method via @bibikalka
# flash xposed in twrp (is this correct file?)
xposed-v87-sdk22-arm.zip
# flash the 5.5.2 bootloaders in twrp and reboot back to Lollipop
5.5.2_1534_stock_recovery_uboot.zip
Thoughts?
Thanks!
@vvxx_
This dpi change will work, pretty uneventfully too. Just make sure you flash the correct FireOS5 bootloaders back after 453 bootloaders & TWRP !
This dpi change will work, pretty uneventfully too. Just make sure you flash the correct FireOS5 bootloaders back after 453 bootloaders & TWRP !
Click to expand...
Click to collapse
10-4; thanks. Going to flash that exact file listed; same one I used to get to the latest OS. I just need the dpi change to work for 1 game, so hopefully it does just that; not really concerned about changing dpi/resolution of anything else.
After getting so much frustrated by the ghost touches of my brocken screen tab, I googled the issue and found none of the guide was working for me. Most of them were quite old and some required to tweak system files which is a blunder on new android as most of the devices are now read only. So I made a script which uses magisk to run systemlessly with every boot and deletes the "event1" file to disable the touch.
For those who don't have root access can use touch blocker apps from playstore, even I used few but none of them were satisfactory so here we are..
"SO HOW DO WE DO IT" ?
First of all ofc, you have to be rooted with magisk.
Download the file and place it in data/adb/service.d/
Make it executable by running " chmod +x * " in root shell.
Reboot and Done!!
Some Imp. Notes:
In case of bootloop, malfuncting or you just want to revert back, just delete the file manually using adb shell or file manager.
Make sure you have a mouse or any solution before.
It may be possible it might not work for you because of change in device and os, for that you can try changing event 1 to even0 in the script.
Cheers