Related
I'm trying to get a window manager running under Debian. I'm using Xvfb and x11vnc. So far I've gotten the server up and running but I get a socket error on my vnc viewer after negotiating protocol. Anyone want to help?
Well, the clean way to display a X client on the phone would be IMHO to implement an x server in a windows. kind of like xming or xephyr. Too bad I don't know java
Anyway, using vnc looks like a smart idea. I worry about the performance, though.
I'll give it a try once I have re-installed debian on my ADP1 (trying to install it in a dedicated partition on the sd)
jusplainmike said:
I'm trying to get a window manager running under Debian. I'm using Xvfb and x11vnc. So far I've gotten the server up and running but I get a socket error on my vnc viewer after negotiating protocol. Anyone want to help?
Click to expand...
Click to collapse
Use X over SSH. Man I'll just write up a post.
I think he's trying to achieve X display on the phone, not on his computer.
Yes, I'm trying to get the display on the phone, not having to really on tunneling x11 over ssh.
I'm running a similar setup on my phone, in order to run X apps like xpdf. Works fine. Here's what you need:
In your debian chroot, apt-get install tightvncserver, and run it.
On the android side, run the android VNC viewer and connect to localhost:1 (or whatever display tightvncserver started). You'll get X on your screen.
You can apt-get and run a small window manager like twm if you need one. I generally use it without a window manager, with apps running in full-screen mode. For example, "xpdf -g 1024x768+0+0 some-file.pdf" to view a PDF. (at least until there's a decent PDF viewer for android).
Don't bother trying OpenOffice on it though. Too heavy - I actually tried it.
mod1 said:
I'm running a similar setup on my phone, in order to run X apps like xpdf. Works fine. Here's what you need:
In your debian chroot, apt-get install tightvncserver, and run it.
On the android side, run the android VNC viewer and connect to localhost:1 (or whatever display tightvncserver started). You'll get X on your screen.
You can apt-get and run a small window manager like twm if you need one. I generally use it without a window manager, with apps running in full-screen mode. For example, "xpdf -g 1024x768+0+0 some-file.pdf" to view a PDF. (at least until there's a decent PDF viewer for android).
Don't bother trying OpenOffice on it though. Too heavy - I actually tried it.
Click to expand...
Click to collapse
Are you telling me you got to run x app on the phone?
Yep, that's what I wrote. It was one of the first things I installed on the phone when I bought it. And performance is not as bad as I expected, as long as you don't try to run animation. Reasonable for reading a pdf.
Has anyone else tried this?
I cannot connect with android vnc viewer from my phone and tightvnc server running on debian showing "localhost:/#".
I am not using a password. I am trying to log in on vnc-viewer at 127.0.0.1 and have tried several ports including the default and 23.
mod1 said:
Yep, that's what I wrote. It was one of the first things I installed on the phone when I bought it. And performance is not as bad as I expected, as long as you don't try to run animation. Reasonable for reading a pdf.
Click to expand...
Click to collapse
Will i be abkle to run pidgin?
when i try to run vncserver it tells me that the USER envirioment variable i snot set
For the user variable error.Type su Again by itself before you start vnc. It has to do with now having set user in the enviroment set. I have an image that give you 2 gigs more of free space (uses up storage card) the current one only has 300megs free which limits you drastically and also a fixed script that you won't have to go into su again....
For the guys that can't get vnc working type localhost in the server field only and as for port use 5901... Use a password upon initial setup of vnc. Sorry about spekking errors but I'm half drunk and typing on g1
Okay I set up the password and stuff but when I go to the vnc viewer on the phone it does nto conect and the crash
When I go to vnc-viewer, I can log in but the window I get says--
Xsession:unable to start x session ---- no "/root/.xsession" ...no session managers,
Can someone please help me get this runing, my messenger is [email protected]
Okay I finally got it to run and get a grey screen, when i go t back to termina it is on android terminal not debian so I log back.
Now how to I run pidgin after I install it? just type pidgin?
I finally got pidgin runing!!!!
Rafase282 said:
I finally got pidgin runing!!!!
Click to expand...
Click to collapse
Now *that* would be a good reason to do this
JesusFreke said:
Now *that* would be a good reason to do this
Click to expand...
Click to collapse
I warn you it will be slow and still cant use the sub functions of the buttons form the keyboard to at least I don't know how. I'm trying to take a screenshot with the program from the windows manager, and i use twm
Okay I have tried with twm, vtwm, and icewm
So far I like icewm the most but still have vtwm for back up. It runs fine not as slow as before with twm. I have pidgin runing but still cant figure out how to run the screenshot program that comes with debian.
Can anyone tell me a way to get a screenshot in command line so I can show you the screen and prove that it works?
I've tried dropcap2 and ShootMe. I prefer ShootMe because it takes less steps to take a screenshot.
Can you recommend a better tool? iPhone's method is way better.
What do you mean you don't enjoy the process to install the Java and the Android SDKs, enable USB debugging, install drivers, then navigate to the SDK folder in command prompt/terminal and run a .bat?
Shame on you, sir.
lol @ grainysand
I use PicMe just start the app and connect to the address shown and snap away (works best over wifi)
FYI, I don't have a Nexus 5, but I've been following the Android L news for the past few weeks and have yet to see any reports on the battery historian developer tool. I'm really curious to see detailed battery usage reports for apps that are known to cause frequent wakeups from deep sleep (e.g. facebook). From what I can tell, you need 3 things to use this tool:
1.) adb
2.) The actual Python script: https://raw.githubusercontent.com/google/battery-historian/master/historian.py (just right-click and "Save as" to the directory from which you run 'adb')
3.) Also need to install Python 2.7 on your system (for Window users): https://www.python.org/download/
4.) Obviously, a browser to view the generated html.
There are some comments at the beginning of historian.py script that describe how to generate the required data with adb. Note for Windows users: open up the file in Wordpad, not Notepad.
Also for Windows users: assuming you have installed Python 2.7 in c:\Python27, use the following command line to run the script:
c:\Python27\python.exe historian.py [OPTIONS] [FILE]
Also note that this tool is NOT part of the built-in Android battery settings/stats and there is no native Android UI for it. It is meant to be a developer tool. However, this doesn't mean that users with access to 'adb' can't play with it...
I manage to get this work...even i have no idea about development...
First it need python 2.7 not 3.4
After that you have to mix some commands from the OT and the info inside the .py file...so what i do
After installing python 2.7 i use the command to get a bugreport from the phone...
Code:
adb bugreport > bugreport.txt
then i use the OT command to make the bugreport to an html file with a bit of change
Code:
c:\Python27\python.exe historian.py -a bugreport.txt > battery.html
Thats it...now..i don't know if it has the correct data...im just achived the html look of what we saw on I/O
I think first you need to use this command
Code:
adb shell dumpsys batterystats --enable full-wake-history
To let the phone start dumping stats...and then after some use time to gather the bugreport from your phone....anyone with better knowlage im sure it will figure it out!!!
On the attachment i use the command
Code:
adb shell dumpsys batterystats --reset
to reset my values cause im not using my L rom...
Oh btw this will work only on L....
I can't use "--enable" option.
I can't use this command.
Code:
adb shell dumpsys batterystats --enable full-wake-history
Please tell me how to use "--enable" option.
My phone is Android4.4.2.
("--enable" option is Android "L" only ??)
k-matoo777 said:
I can't use this command.
Code:
adb shell dumpsys batterystats --enable full-wake-history
Please tell me how to use "--enable" option.
My phone is Android4.4.2.
("--enable" option is Android "L" only ??)
Click to expand...
Click to collapse
This is only for Android L.
thomase00 said:
This is only for Android L.
Click to expand...
Click to collapse
How is it that we are a month after Google I/O, and no one with Android L has played with this yet?
IMHO, this is one of the most important new features.
Yep, i think this is the most recent problems the two guys from project Volta have. They have to be rely on the help of the programmers which develop the software.
Daimonion1980 said:
Yep, i think this is the most recent problems the two guys from project Volta have. They have to be rely on the help of the programmers which develop the software.
Click to expand...
Click to collapse
They have to rely on Developer to use JobScheduler API but not for finding you bad apps that are killing the battery. And to that effect, those guys are doing a terrible job with a botched tool.
It's amazing how there is NOTHING on the Internet about the Battery Historian tool. It's like no one has used it. In my case, I can't get the command to builds the html file from the bugreport. It keeps giving me a invalid html error.
Yep, I did ask chamonix from BBS if he can use the generated stats and he will take a look into it. I hope he will do it in the near future.
Using battery historian
After playing with this for a while I've figured out how to use the basic function (this is part of project volta, so it will only work on Android 5.0+)
enable full wake history and then output your batterystats to a text file
./adb shell dumpsys batterystats --enable full-wake-history
./adb shell dumpsys batterystats > batterystats.txt
navigate to wherever you placed historian.py and output the data to a html file (you need python 2.7)
./historian.py [location of batterystats.txt] > batterystats.html
open the batterystats.html file and you're done! For basic use at least. I'm still figuring out the rest myself.
So after having problems on lollipop with mobile radio active bug (https://code.google.com/p/android/i...id&colspec=ID+Type+Status+Owner+Summary+Stars)
i managed to get an dump from battery historian. But at the moment a see not the culprit in my log. The only thing i see is that my device although it was not heavily used this morning has a tons of wakelocks.... and an running par between 10:45 and 10:55 where i don't know it's coming from......
Have a look at it:
http://picture-diamonds.de/private/Thomas/Dumpsys.html
Is anyone able to interpret this chart?
I finally got 5.1 on my Verizon Moto X (1st gen). One of the first things I did was collect battery stats and run Battery Historian 2.0. The following guide was very helpful in getting this set up on Windows 7:
http://ph0b.com/battery-historian-2-0-windows/
Anyway, it turns out that while sitting untouched on my desk at work, the phone pretty consistently wakes up about once per minute (only for a second or 2), with the partial wakelock held by GOOGLE_SERVICES. Most of the time, it seems to be related to location reporting. This doesn't sound like a lot, but I think there is a relatively big cost associated with powering the up and down.
Other than location, the ONLY reason I can think of for waking up the phone periodically is for TCP keep-alive (to keep GCM push notifications working), but once per minute seems kind of excessive even for that. My theory is that there is an app using the Google Play Services Geofencing API, and I just happen to be parked near a geofence boundary. According to my understanding, the Google geofencing service adjusts location polling frequency according to your distance from a geofence. If I am correct, the problem is that it is not smart enough to understand that you are stationary and therefore avoid excessive polling.
I'll try to collect more stats from different locations.
I'm sure this ground has been tread before...
thomase00 said:
I finally got 5.1 on my Verizon Moto X (1st gen). One of the first things I did was collect battery stats and run Battery Historian 2.0. The following guide was very helpful in getting this set up on Windows 7:
http://ph0b.com/battery-historian-2-0-windows/
Anyway, it turns out that while sitting untouched on my desk at work, the phone pretty consistently wakes up about once per minute (only for a second or 2), with the partial wakelock held by GOOGLE_SERVICES. Most of the time, it seems to be related to location reporting. This doesn't sound like a lot, but I think there is a relatively big cost associated with powering the up and down.
Other than location, the ONLY reason I can think of for waking up the phone periodically is for TCP keep-alive (to keep GCM push notifications working), but once per minute seems kind of excessive even for that. My theory is that there is an app using the Google Play Services Geofencing API, and I just happen to be parked near a geofence boundary. According to my understanding, the Google geofencing service adjusts location polling frequency according to your distance from a geofence. If I am correct, the problem is that it is not smart enough to understand that you are stationary and therefore avoid excessive polling.
I'll try to collect more stats from different locations.
I'm sure this ground has been tread before...
Click to expand...
Click to collapse
Thanks for sharing ph0b's work here with Battery Historian.
When i go in application mamangement, it just shows running apps not processes to kill. How do i find the application processes running like Google Services etc.
First, manually killing individual processes is generally a bad idea, as Android does a fine job of managing them. Plus, some processes will simply restart themselves if they're stopped unexpectedly. I'm not sure why you'd need to do this, but if you must, you can do it via adb.
To see all running processes:
Code:
adb shell PS
To kill a process:
Code:
adb shell kill <pid>
With <pid> being the process you want to kill.
For a small internal company project I need a stick to run a soft of info screen type application. No user access to the hardware after setup.
My current thought process
- adb needed to be able to automate setup
- root needed to automate update
- internal render resolution of 1080p matching screen to avoid fuzzy text
What device would you recommend?