yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] xunair:
OK I installed os monitor

Gona install other two apps

And I'm gona flash back to xxjvp
[Galaxy S I9000 General] xunair:
And I deleted everything in my sd card? Before
[Galaxy S I9000 General] torrentship:
ok; excellent.

If you need help turning on the "monitor" mode of system panel let me know. Otherwise just turn it on and then use your phone normally for a while (i.e. allow time for it to be left with screen off as well) after that stats will be collected to show how the CPU has been used over that time.

Also check CPU Spy and make sure that the CPU isn't "stuck" in 1000Mhz
[Galaxy S I9000 General] xunair:
I tried cpu spy
[Galaxy S I9000 General] xunair:
Cpu spy

http://db.tt/EsS20rcu
[Galaxy S I9000 General] xunair:
Check this

It's weird I switch off ma cell to remove battery

When I turned on

It drained from 48% to 30

And den it started increasing

Without any power source

http://db.tt/TL206ROJ

http://db.tt/ik2w8ueP
[Galaxy S I9000 General] torrentship:
Hi

The same thing happens to most batteries when they have been subjected to heavy load and then released from that load.

The voltage "sags" slightly when under load.

The percentage measurement you see is just a calculation based on the current voltage reading of the battery. The voltage will be slowly dropping off as the battery discharges.

Think of voltage as pressure and current as the speed of water flowing from the hose. (it might not help at all!)
[Galaxy S I9000 General] xunair:
SO what should I do?
[Galaxy S I9000 General] xunair:
Battery isn't calibrated!
[Galaxy S I9000 General] Sinistr0:
I think that is better reset the battery cache data in advanced options in recovery mod (below the "Clean Dalvik Cache").
[Galaxy S I9000 General] torrentship:
Have you ever actually let the phone run out of battery?

The mapping between voltage and percentage might be wrong - even though it says 30%, you might find that it stays on 30% for ages...

Try letting it run out of battery completely.

You can try the battery reset option in CWM, but afterwards, just let it run completely out first.

Let us know how you get on.
[Galaxy S I9000 General] xunair:
1st charge to 100%

Den wipe battery stats

And let it drain and power off and den full charge

Yea that's it na?
[Galaxy S I9000 General] Sinistr0:
Yup that'll do.
[Galaxy S I9000 General] madmattyboy:
OK, not a H/W problem for me (pfew) :cool:. I ended up going back to 2.What ever, reseting the battery stats and then flashing ICS Docs Semaphore v3.1. So far so good.

Maybe Glitch had a Glitch or somthing, but I was get constant 40% CPU usage on the System in OS monitor.

Anyway 5 hours and still at 82% :), for me it is good and will last the day hopfully.
[Galaxy S I9000 General] xunair:
Mine still sucks

:-( reset battery

Still its draining same help
[Galaxy S I9000 General] madmattyboy:
It didn't take long, but my drain issue has come back.

The phone seems to get really hot one the back?:mad:
[Galaxy S I9000 General] xunair:
THANKS TO HEADHOOD

Fix

Before you are connecting your phone to the charger done this:

1- open your dialer

2- enter: *#0228#

3- press: Quick start

Then you will see that your stats will dropped to real stats.

For example my stats were dropped from 53% to 33%.

And yeah, your rom may give you an excellent battery use but the faked stats are putting a **** on your face.
[Galaxy S I9000 General] torrentship:
There are two issues here though:

The incorrect battery level identification

Over-expected use of the battery

The first can be fixed in a number of ways - primarily by just ignoring it and after a few charge cycles it should go away by itself.

The second, which is most identifiable by the battery getting hot (which simply implies more current is being drawn for a greater length time) will NOT be fixed by the same thing as above. Some analysis of which apps / kernel / system is causing the over use of the CPU must be done.

Best thing to do is to completely wipe your phone and install a very close to stock GingerBread ROM (like JVT) and see how your battery does then.

When I say wipe, I mean use CWM (if you have it) and use the format option in the "Mounts" menu for all the different points:

/system

/apps

/data

/datadata

/sdcard

Be careful to backup everything you require on your phone. Do not wipe /efs directory though if it's there. Also the /boot directory I'm not sure about so be careful with that one.

This will wipe everything on your SDCARD including all your own i.e. non-android data.
[Galaxy S I9000 General] xunair:
Check this
[Galaxy S I9000 General] xunair:
Nothing improved :-(
[Galaxy S I9000 General] Vogie:
Best battery life rom for me is AOKP ICS,

Try it.
[Galaxy S I9000 General] xunair:
Should I replace battery :-(

Continous use is fine

1% percent dropping every 5min

Whether wifi bluetooth and brightness is 0%

:-( why it is draining like this and it goes into deep sleep and cpu usage is fine
[Galaxy S I9000 General] torrentship:
I still haven't seen a screenshot showing the app usage; the shots showing the battery stats are useful but only to a point. Try the free version of system panel? We need to see statistics for the apps you have running over a period of time.
[Galaxy S I9000 General] torrentship:
Replacing the battery may solve the problem though!
[Galaxy S I9000 General] xunair:
Here it is;

http://db.tt/1PNpU8sV

http://db.tt/DRsg9joG
[Galaxy S I9000 General] bralgei:
Get back to stock. I did the same and I have 1% over night with no data. Usual draining is 35-50 % over 24 hors with data 2g and whatapp running.

I use JVZ or JVU with Semafore kernel.
[Galaxy S I9000 General] xunair:
Where can I get that kernel?
[Galaxy S I9000 General] apple23:
From here

http://xdaforums.com/showthread.php?t=1112908

you can use sgs kernel flasher from market to flash it
[Galaxy S I9000 General] torrentship:
xunair,

Thanks for posting the SystemPanel shots;

Firstly you seem to have a custom ROM on there so please try to re-flash a stock ROM - if you need guidance with this let me know but here's the thread:

Ramad's Firmware Collection

You can use the Semaphore kernel as recommended above but you'll need to flash it after you flash the ROM from Ramad.

The system panel data shows a high usage of mediaserver which could mean you've been watching videos or listening to music - is that the case?

The kSwapD0 process is a linux internal which afaik controls page swapping in and out of memory - so if this is seeing high usage it's likely you're running out of ram regularly (think pagefile on windows). This is almost definately becuase of the custom ROM you are running and all the extra battery widgets and all that sort of thing.

Good luck, let me know how you do.
[Galaxy S I9000 General] xunair:
Thanks alot :-)

IM gona flash stock Rom

But which stock rom is best?
[Galaxy S I9000 General] torrentship:
Any of the Gingerbread Roms there from 2.3.6 or 2.3.5. You'll need to follow the instructions that have been given on that thread.
[Galaxy S I9000 General] xunair:
I have flashed before

It's the same

Thanks :-)
[Galaxy S I9000 General] xunair:
Repartition and using pit?

Does it matter?

And should I erase all the data format sd card?
[Galaxy S I9000 General] torrentship:
Please make sure you have a backup of any data including the efs directory.

Then use the PIT file becuase ICS may have re-arranged the partitions i'm not sure - but to be on the safe side use it as well.

As long as you have a backup of your data you'll be fine.
[Galaxy S I9000 General] xunair:
I couldn't find how to make Efs back up!

Easy Guide?
[Galaxy S I9000 General] Stealth316:
I had crazy battery drain myself, not quite like this though, 40%+ on Android os usage. The fix for me was to change the wifi policy to "only when plugged in". This had an immediate effect on my battery drain even though I hardly have wifi on. Thanks to BHuvan goyal for suggesting that in the thread for his AOKP ICS rom.
[Galaxy S I9000 General] torrentship:
The easiest way is to just make a copy (or a zip) of the /efs directory.

Use a file manager program like RootExplorer or ES File Manager.
[Galaxy S I9000 General] Rai1976:
The same problem here. I have tried everything. I flashed a couple of ROM´s Gingerbread, ICS. I have wiped battery statts. I have calibrated my battery. I have even bought a new battery. I can´t seem to loose this battery drain.

Suddenly my battery was empty in les then 18 hours. Before i could use the phone for two days. This was while i was using a ROM i didn't flash one.

Now i am at the point of buying a new phone :(
[Galaxy S I9000 General] torrentship:
It's quite tempting to blame hardware - I have to regularly check myself for that - but to be honest, the battery drain issue is almost certainly down to your use of the phone. The best thing to do is always start from scratch and isolate the problem that way.

Anyone that is getting "sudden" battery drain that will not go away must absolutely ensure that they have completely wiped everything in their phone and start again with a stock ROM.

I think people get confused as to what everything is! I mean /data /system /sdcard - evrything single thing you can format - format it.

The best way to do this is in ClockWorkMod.

The only thing that should be left is the kernel / recovery partitions!

I believe it's normally residual "stuff" on the memory cards that cause problems with drain.

Yes, sometimes a ROM can have a bug - that's for sure - infact, some of the stock ROMs had a battery drain - the Android OS drain - but that is gone by the JVT ROM.

Basically - don't blame the hardware - it's almost definately NOT the hardware :) !
[Galaxy S I9000 General] xunair:
Hi

Im on 2.3.5 stock

Kindly tell which file from. Semaphore thread should I download to flash kernel?

And It's 19 hours now till charge

Sometimes battery goes down fast sometimes it drain after 10 or 30 mins

And I did this code trick

*#0228#

My battery was on 41% and it reduced to 31 and stayed dere

From 3:25pm to 4:54pm

Sometime it goes down to 30 and den comes up to 31 it happend 4 times and

Den it started draining after 5pm

Wifi and background data was on

But screen was off mostly.
[Galaxy S I9000 General] Saimen2:
Can one tell me what this code does? (*#0228#)

THX

---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------

There are a few apps that backup your efs folder automatically.

For example: "nitrality" (its free from Market)
[Galaxy S I9000 General] xunair:
I'm using this charger

eta3u30ebe samsung

Travel adapter

Input :100-240

50-60Hz 0.15A

Output : 4.75v — 0.55A

Is this charger suitable for my sgs?

Thanks
[Galaxy S I9000 General] xunair:
Can anyone tell

Should I be using that charger?
[Galaxy S I9000 General] torrentship:
USB spec says 5V so it's slightly less but it should be fine. Try, see if the phone recognises it.
[Galaxy S I9000 General] xunair:
YEA phone recognize it easily and em using it since the day i bought...
[Android Apps and Games] glenn85:
I'm trying this on my rooted Galaxy Nexus (4.0.2) using connectbot, but I keep on getting "cannot execute - Permission denied" even though I'm using superuser prompt.

EDIT: I forgot to set permissions to the file, it works now, although the framerate seems a bit low and the colors are inverted...
[Android Apps and Games] knoxbrder:
I only get a couple frames per second. I don't think the snapshot code is very fast.

Try the command line switch -s to swap the red/blue colors.

-h shows all the options.
[Android Apps and Games] glenn85:
The -s switch does the trick with the inverted colors. Unfortunately I can not get keyboard and mouse input to work.

About the low framerate, I can see that "surfaceflinger" is taking up a lot of cpu usage when I start vncs, maybe that has something to do with it...

Please keep up the good work, I really like it already!
[Android Apps and Games] knoxbrder:
Did you try the -g option for the pointer? That format is what the Galaxy S2 uses. The Nexus may be the same.

If that doesn't help, read on.....

Since your device is rooted, do you have busybox installed?

If so, can you post the output of "which input"? I currently use that program to inject the keys and I have found it to work on several devices although it is a bit slow.

For the pointer, try using the -t option to specify different /dev/input/eventX options where X is usually 0 - 6. An "ls -l /dev/input/" will show you which ones are available. Different phones/tablets use different event devices and I haven't tried to figure out how to auto detect which is which.

If you run something like "od -x /dev/input/eventX", where X is 0 - 7, and touch the touchscreen you should get output on the one the touchscreen uses.

If you find the right -t option by using od, but still can't get the mouse to work over VNC, post the output of this:

- run "od -x /dev/input/event3" (or whichever event file works for you)

- carefully touch/release the screen as quickly as possible so you get one or two "touch" events outputting from the od command

- post the values (I would do this over adb so you can copy/past the output)

I will look at the output to see how it differs from the devices I have tested.
[Android Apps and Games] jdbower:
Also running a Galaxy Nexus with 4.0.2 (VZW, deodexed but otherwise stock ROM, rooted [as all Nexus devices should be]). The -s fixed the color inversion, with or without -g I can't use the touch or keyboard input (although I wasn't thorough about keyboard testing).

I would like to request a scaling factor or allowing 90 degree rotation since the 1280 pixel vertical resolution exceeds my 1080p monitor, but that's pretty minor as of now.

# which input
/system/bin/input

It looks like the touchscreen is actually on event1:

root@android:/ # od -x /dev/input/event1
0000000 00d2 0000 0f70 0001 0003 0039 001e 0000
0000020 00d2 0000 0f70 0001 0003 0030 000e 0000
0000040 00d2 0000 0f8f 0001 0003 003a 0081 0000
0000060 00d2 0000 0f8f 0001 0003 0035 01ca 0000
0000100 00d2 0000 0f8f 0001 0003 0036 0120 0000
0000120 00d2 0000 0fad 0001 0000 0000 0000 0000
0000140 00d2 0000 2d5c 0001 0003 0039 ffff ffff
0000160 00d2 0000 2d5c 0001 0000 0000 0000 0000

Here are the input devices:

# ls /dev/input
event0
event1
event2
event3
event4
event5
mice

Thanks for your work on this, I really miss having a VNC server on my phone!
[Android Apps and Games] knoxbrder:
New Version 1.1 up; see first post.

Added scaling and rotation.

Tweaked the input handling.

For Galaxy S2 try ./vncs -t /dev/input/event2 -s -g -x 480 -y 800.

Other devices let me know if this version works better.
[Android Apps and Games] glenn85:
The touchscreen indeed seems to be on event1. So I tried the following commands:

./vncs -t /dev/input/event1 -s -g -x 720 -y 1280

./vncs -t /dev/input/event1 -s

But mouse input still doesn't work, unfortunately.

I also found out when the phone goes to stand-by mode while running vncs, the touchscreen stops working at all. Had to take out my battery to restart the phone...
[Android Apps and Games] knoxbrder:
I forgot to actually attach the new version.

Check -h when you run it to make sure it says version 1.1.

See if this fixes the event problem.

I have never seen the device hang when it goes to sleep.

I will see if I can reproduce that.
[Android Apps and Games] jdbower:
Still no luck on the VZW Galaxy Nexus (but the scaling is much appreciated!). Please let me know if you'd like any additional debugging information from me.
[Android Apps and Games] knoxbrder:
jdbower:

Please try to capture a couple more touchscreen presses. I don't think there is enough information in your previous log.

I see the headers, and x/y movement. But I'm not sure I see the actual "finger down/release". Or I don't understand it.

Thanks
[Android Apps and Games] jdbower:
This was a quick tap on the home screen:

# od -x /dev/input/event1
0000000 0521 0000 13ee 000a 0003 0039 000c 0000
0000020 0521 0000 140c 000a 0003 0030 000b 0000
0000040 0521 0000 140c 000a 0003 003a 006e 0000
0000060 0521 0000 142b 000a 0003 0035 014d 0000
0000100 0521 0000 142b 000a 0003 0036 02e1 0000
0000120 0521 0000 142b 000a 0000 0000 0000 0000
0000140 0521 0000 5afa 000a 0003 0039 ffff ffff
0000160 0521 0000 5b18 000a 0000 0000 0000 0000

And another:

# od -x /dev/input/event1
0000000 0549 0000 a50e 0005 0003 0039 000d 0000
0000020 0549 0000 a52d 0005 0003 0030 000e 0000
0000040 0549 0000 a52d 0005 0003 003a 008f 0000
0000060 0549 0000 a52d 0005 0003 0035 0218 0000
0000100 0549 0000 a54b 0005 0003 0036 02f1 0000
0000120 0549 0000 a54b 0005 0000 0000 0000 0000
0000140 0549 0000 c280 0005 0003 0039 ffff ffff
0000160 0549 0000 c29e 0005 0000 0000 0000 0000

And a swipe in case it helps:

# od -x /dev/input/event1
0000000 0572 0000 3e50 000d 0003 0039 000e 0000
0000020 0572 0000 3e6e 000d 0003 003a 0079 0000
0000040 0572 0000 3e6e 000d 0003 0035 00f3 0000
0000060 0572 0000 3e8d 000d 0003 0036 02dd 0000
0000100 0572 0000 3e8d 000d 0000 0000 0000 0000
0000120 0572 0000 63fb 000d 0003 003a 007c 0000
0000140 0572 0000 6438 000d 0003 0035 0101 0000
0000160 0572 0000 6438 000d 0003 0036 02db 0000
0000200 0572 0000 6438 000d 0000 0000 0000 0000
0000220 0572 0000 88d1 000d 0003 003a 007e 0000
0000240 0572 0000 88d1 000d 0003 0035 011f 0000
0000260 0572 0000 88d1 000d 0003 0036 02d8 0000
0000300 0572 0000 88f0 000d 0000 0000 0000 0000
0000320 0572 0000 ada7 000d 0003 003a 007f 0000
0000340 0572 0000 adc6 000d 0003 0035 0148 0000
0000360 0572 0000 adc6 000d 0003 0036 02d5 0000
0000400 0572 0000 adc6 000d 0000 0000 0000 0000
0000420 0572 0000 d484 000d 0003 003a 0080 0000
0000440 0572 0000 d484 000d 0003 0035 0178 0000
0000460 0572 0000 d484 000d 0003 0036 02d2 0000
0000500 0572 0000 d4a3 000d 0000 0000 0000 0000
0000520 0572 0000 f91d 000d 0003 003a 0081 0000
0000540 0572 0000 f91d 000d 0003 0035 01a8 0000
0000560 0572 0000 f91d 000d 0003 0036 02ce 0000
0000600 0572 0000 f93b 000d 0000 0000 0000 0000
0000620 0572 0000 1e11 000e 0003 003a 0082 0000
0000640 0572 0000 1e30 000e 0003 0035 01d9 0000
0000660 0572 0000 1e30 000e 0003 0036 02cc 0000
0000700 0572 0000 1e30 000e 0000 0000 0000 0000
0000720 0572 0000 426d 000e 0003 003a 0081 0000
0000740 0572 0000 426d 000e 0003 0035 0207 0000
0000760 0572 0000 426d 000e 0003 0036 02cb 0000
0001000 0572 0000 426d 000e 0000 0000 0000 0000
0001020 0572 0000 6780 000e 0003 003a 007a 0000
0001040 0572 0000 6780 000e 0003 0035 0233 0000
0001060 0572 0000 679f 000e 0000 0000 0000 0000
0001100 0572 0000 8c75 000e 0003 003a 0050 0000
0001120 0572 0000 8c75 000e 0003 0035 0262 0000
0001140 0572 0000 8c75 000e 0003 0036 02cc 0000
0001160 0572 0000 8c75 000e 0000 0000 0000 0000
0001200 0572 0000 affb 000e 0003 0039 ffff ffff
0001220 0572 0000 affb 000e 0000 0000 0000 0000

Let me know if there's anything else I can provide. Thanks!
[Android Apps and Games] knoxbrder:
Just taking a stab in the dark with 1.2 for the nexus since I don't know anyone nearby who has one.

If it doesn't work, try running the od command while using vnc so I can compare the output with what it should be.
[Android Apps and Games] jdbower:
Here's the output of a click on the VNC window with -g:

# od -x /dev/input/event1
0000000 00e4 0000 0786 0008 0000 0002 0000 0000
0000020 00e4 0000 07a5 0008 0000 0000 0000 0000
0000040 00e4 0000 07e2 0008 0000 0002 0000 0000
0000060 00e4 0000 07e2 0008 0000 0000 0000 0000
0000100 00e4 0000 07e2 0008 0000 0002 0000 0000
0000120 00e4 0000 07e2 0008 0000 0000 0000 0000

And without -g:

# od -x /dev/input/event1
0000000 0144 0000 47d8 000b 0000 0002 0000 0000
0000020 0144 0000 47f6 000b 0000 0000 0000 0000
0000040 0144 0000 49fd 000b 0000 0002 0000 0000
0000060 0144 0000 4a1c 000b 0000 0000 0000 0000
0000100 0144 0000 4c41 000b 0000 0002 0000 0000
0000120 0144 0000 4c41 000b 0000 0000 0000 0000

Note that there's a pretty long delay between the click and the response, on the order of 5 seconds.

I'm not sure exactly what I'm reading, but it seems like lifting my finger from the screen produces ffff ffff in the second to last value, it seems like this is missing from the VNC mouseclick.

For whatever reason, the lockup behavior seems much worse with this build. The od command still shows response to touches, but the phone doesn't respond.

Hope this helps!
[Android Apps and Games] knoxbrder:
I forgot to tell you (it says in the -h) to use -n instead of -g for the Nexus.

I slowed the events down since they actually lag on my GS2 quite a bit.

I can turn that off it it makes the GN worse.

Maybe we can look at it this weekend if its still not working.
[Android Apps and Games] permai:
how to install this? after download the vncs.zip, there is no apk file.
[Android Apps and Games] knoxbrder:
At the moment there is no java gui to start/stop the program.

You need to start it from a shell prompt using adb or something like connectbot.

If you are not familiar with these methods of program control you might want to wait another week or two until I have time to put together a GUI or merge it back into another program that already has a GUI.
[Android Apps and Games] permai:
great...i am looking forward to the apk release soon...thank you.
[Android Apps and Games] jdbower:
Sorry, I didn't see the -n option in the help. Here are the od outputs from my VNC client with -n enabled:

Click:

# od -x /dev/input/event1
0000000 3b5f 0000 2942 0000 0003 0039 ffff 0000
0000020 3b5f 0000 2961 0000 0000 0000 0000 0000
0000040 3b5f 0000 f6e7 0004 0003 0039 000c 0000
0000060 3b5f 0000 f724 0004 0000 0000 0000 0000

Another click:

# od -x /dev/input/event1
0000000 3bd3 0000 4a79 0007 0003 0039 ffff 0000
0000020 3bd3 0000 4a79 0007 0000 0000 0000 0000
0000040 3bd3 0000 5006 000c 0003 0039 000c 0000
0000060 3bd3 0000 5025 000c 0000 0000 0000 0000

Swipe, left to right (looks like a click to my untrained eye):

# od -x /dev/input/event1
0000000 3bd3 0000 4a79 0007 0003 0039 ffff 0000
0000020 3bd3 0000 4a79 0007 0000 0000 0000 0000
0000040 3bd3 0000 5006 000c 0003 0039 000c 0000
0000060 3bd3 0000 5025 000c 0000 0000 0000 0000

Let me know if I can be of any more help.
[Android Apps and Games] frenccw:
Looking forward to it too. Missing this feature badly from Gingerbread :( Let me know if you need a noob beta tester for the apk version
[Android Apps and Games] hamiltro:
This is what I was looking for, had to mess around a little bit with it but was able to get in to adb and learn some more, thanks again.:D
[Android Apps and Games] knoxbrder:
I will add a widget to the todo list. Which looks something like this:

- stomp bugs

- decide which color method to use (I'm leaning towards specifying RGB order and nothing else; take out -s and change -c to RGB, BGR, etc)

- finish code/docs cleanup

- release code back to original projects or start new project

- connect to client in listen mode (helps with NAT and firewalls)

- better IPC (there really isn't any right now once vncs starts)

- other ways to start vncs: text message, email, widget

- better scaling (will slow down some, but may just cancel out the scaling speed advantage, and will look better while still taking up less room)

- icon on the notification bar to show if the server is running

- look at x86 version (at least to find out how much effort this will be)
[Android Apps and Games] Scotty1:
Ready by next week, then? :):)
[Android Apps and Games] frenccw:
How about an icon on the notification bar to show if the server is running? :)
[Android Apps and Games] BlackPit666:
would be nice!
[Android Apps and Games] Scotty1:
A status bar icon would be ok, but FWIW, I'd prefer a widget because that would have two functions: it would show the server's current status (just like a status bar icon) but ALSO it would allow one-touch on/off toggling.....
[Android Apps and Games] frenccw:
Why can't we have both? :D
[Android Apps and Games] knoxbrder:
It probably will be both eventually.

I like being able to turn the server on/off and see its status from the notifications menu.