Please look in this thread for more complete details.
***** ***** ***** ***** ***** ***** ***** *****
For those of you looking to get terminal access on your webtop, here's a simplified set of instructions. You'll need:
A rooted Atrix.
Some kind of terminal access. I ended up using the Android Terminal Emulator that’s in the market; I would imagine that other terminals would work, as well as something like adbWireless.
Run the following commands on the terminal:
su
/usr/bin/sudo -u adas bash
export DISPLAY=:0
/osh/usr/bin/.lxterminal
And then, you too can end up with this!
{
"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"
}
P.S. I'm not responsible for any havoc you wreak after getting a terminal running.
P.P.S. droidbird has figured out how to add additional programs to the dock, so you should be able to add LXTerminal to the dock after that.
Thanks worked nicely, though still fuzzy with the link you posted to get the terminal icon on the dock any how to explained more clearly?
Please close in favour of this thread.
Related
I made this for people who use a Transparent Lockscreen (described here.)
There is this little bar in the default lockscreen that is some kind of annoying and doesn't match with the transparancy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I removed it, so it looks like this when unlocking your phone.
Installation:
Don't forget to do a nandroid backup before installing this!
Code:
adb remount
adb push *Your Directory*/HtcLockScreen.apk system/app/
reboot your phone and your done. Have fun!
** DOWNLOAD **
Hey, very cool.
OT on:
Do you live in "Waldsee"?
We're going for a few days of holidays from 31.12.09 - 03.01.10 to Speyer. Waldsee belongs to Speyer, right? I was in an Hotel in Waldsee before a few years called Hotel Oberst. Do you know it?
OT off.
Im sorry to disappoint you, but i dont live in waldsee. I live in Ketsch, a few kilometers from to waldsee. Sometimes my phone isnt that precise..
btw, the day you leave is my birthday
Cheers for this... quick question, do I have to carry out the steps in the transparent lockscreen thread first or does this apk do it all?
For a transparent lockscreen you need to follows the described steps here.
I followed the instructions on the Evervolv Touchpad Development forum to add additional users but ran into a bit of bother...
After entering:
su
setprop fw.max_users=5
at the terminal the 'Users' menu did appear and I then spent about an hour configuring my wife's account. Everything looked good, rebooted only to find that the second user was no longer on the home screen. Bummer.
I checked the build.prop and there was no sign of the fw.max_users=5.
I went ahead and edited the build.prop using an app (build.prop?) and added the following:
{
"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"
}
(You can manually edit the build.prop to add a line:
fw.max_users=5
...I didn't feel that comfortable with that)
I rebooted many times since and everything is nice and dandy. And the best bit?, when I rebooted the user I spent an hour adding was still there... class. Using for a while now and seems robust.
Some people are saying this is a bug with the Rom, to me (complete noob) it looks like an issue with rights to edit the build.prop through the terminal.
My Rom: http://evervolv.com/devices/tenderloin (May 11th nightly)
Sent from my Touchpad using XDA Premium HD app
I stumbled across this in the Viper4Android 2.7 thread. It was suggested for activating dark mode for that app, which it does, but I noticed that it also changed the playstore, photos, and chrome (kind of). There may be more but those are the only Google apps that I use beside Drive and messages which already have a dark theme option within the app.
Edit- I forgot about Gmail. It doesn't work for that one, at least not on my end.
This is only confirmed on Stock 6.0.1 firmware.
First you'll need a terminal app. I use Termux.
Open that app and type the following:
Code:
su
Press enter, then type (or copy/paste)
Code:
settings put secure ui_night_mode 2
Press enter, then reboot or type in the terminal
Code:
reboot
And press enter
Once your phone boots back up you should see dark mode on the above mentioned apps and possibly more.
{
"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"
}
Credit to this post by @dpEnd367
Hello, I hope I am in the right place for this question. As a new learner, I ask a question or two with reference to a how to page that seems to have become depreciated but very close to my desired goal of setting the default size of an android device emulator.
THIS page described how to manage the default size of the device emulator.
At 2:54 in the video it shows that activating "telnet server". That has however been disabled in the latest 21H2 version of Win 10.
So I an thinking the needed command is just slightly different rather than using at 6:24 the telnet localhost 5554 (which now requires authentication - no probs it tells how to do it on the new win 10 version).
There there is no "window" function to add the "window scale 0.2" command at 7:02.
So that is where I get lost.
I was able to do every thing but the cmd list i got did not have the "window" in the list. This is what my list looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope this is enough for a more experienced android studio user can help me out with.
So, to deflect the standard suggestion of resizing by simply click-dragging the emulator, not my best goal, I would like the default size be set so that is not required every time I open the emulator.
Thanks very lots. Cheers for any help.
CC
Hello
I am going to write a script that will run another script When the USB device is connected.
I used a rule called 99-my-usb-rule.rules in /etc/udev/rules.d
All the work I did and the error log are all in the attached image file
Can anyone help me?
{
"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"
}
debug your commands/scripts in shell first , to see if they run and do what you want them to.
bash -x ./script.sh ( for detailed debugging )
then running from udev script just like running from crontab
is a very sterile environment unlike a login shell.
do "/usr/bin/env > /tmp/udev-env.txt" from udev script to see what it set and what is not.
vs "env > /tmp/login-env.txt" from a login shell , which would have all sorts of things set besides paths that might be missing etc...
and you are also not specifying any devices ( do you want script to run on all usb device connections? )
lookup udev rules if you want something a bit more specific.
also you do not need /bin/bash if you have shebang #!/bin/bash as first line of your script
just execute your /path/to/script.sh ( make sure it is an executable )