I have been trying to figure this out on my own through searching, and when that failed experimentation, but to no avail.
What I would like is that every time I run an application from eclipse, my android device will wake (screen on and all that). Additionally I want, though this is not as important, to be able to wake my device from the command line.
The reason I want this is simple. I don't like leaving my device on as I sometimes read code and tutorials or get some food, and I end up not touching the device for a half hour at a time. I don't want to leave it on when plugged in (which is most of the day), and I end up turning it on with the power button about thirty times each day, which seems excessive.
Sorry if this is something obvious, but I can't find anyone talking about it anywhere.
Any help is greatly appreciated.
Nobody else has ever wanted to do this? Noone has looked into this? Surely soneone has an interest in this if not knowledge of how to go about making it work.
moved to QnA, not dev related.
(probably why no one answered your question)
Solved!
Well, I've solved the issue on my own. I created an application called Wakey Droid that does what I want. Then all you need to do is set the command adb shell am start -a android.intent.action.MAIN -n bdjnk.android.wakeydroid/.Wakey to some convenient shortcut, and life is good.
Related
I wrote up instructions on my blog, and someone responded explaining why it works.
To translate: anything the user types on the keyboard is actually being fed into a console shell and potentially executed. So the easiest way to get root on your phone is to simply reboot it, and when it finishes rebooting, type "telnetd" and press enter. Your phone will start doing a contact lookup in your UI, but at the same time it is typing into a root shell.
This is basically a huge oops on Google's part! Looks like some debug related settings that they never took out.
So really, pTerminal was not necessary in this hack, but it it accidentally exposed it!
Edit: should have read the other post about this! Kudos to Jim!
http://forum.xda-developers.com/showthread.php?t=442857
Like the...
Yup, telnetd in essence was the carrot on the stick that led me on.... Further cementing the fact that someone was bound to find this one way or another... Much sooner rather than later.
Obviously this will need to be fixed, I only hope the platform can some how remain open (and be taken even further) even after said fix.
Wow, I will not be taking any updates until I have everything worked out just the way I want it....
forced updating rc30
you may not have a choice short of turning your g1 of and leaving it that way, it has been rumored that this update has a date at which it turn mandatory.
bhang
I have SE Xperia X2 with the latest MR2 upgrade.
My company enforces the phone lock every time I sync my emails with the Exchange server. The problem is that I'm not able to turn this off again from the menus.
This is a bit irritating especially when I use the phone in the car for navigation purposes, GPS tracking or GeoCashing as the screen turns off every 5 minutes and the phone lock turns on. Typing the pin code while driving is not very safe
I wonder if someone can make a .cab file that can deactivate the phone lock?
Yes, I know it will be turned on again next time I sync but that is okay.
From somewhere I downloaded a file ExchangePolicyPatch which removes this lock.
Search for it
ajhvdb said:
From somewhere I downloaded a file ExchangePolicyPatch which removes this lock.
Search for it
Click to expand...
Click to collapse
Typign the words "Search for it" and doing THIS: http://www.lmgtfy.com/?q=ExchangePolicyPatch took the same amount of time.
Good tip, but why don't people go the one extra step?
Nu
Well one reason is that noobs like me had no clue that it was called ExchangePolicyPatch . That's one reason why we ask all this stupid questions
When that is said, thank you very much for your help. After ajhvdb pointet out what the correct phrase was, it took me less than 2 minutes to find the file plus a couple more that does the same thing plus a description of which reg key to change.
Since I prefer learning things I ended up downloading a register editor for WinMo and editing the correct reg key myself.
For the moment I'm trying to generate my own cab-file (more new stuff to learn) that only changes this key so that I can easily do this again if it should change back again.
Glad you found it
hello,
as far i know the battery life on raph is that bad because of the LCD-driver. since nobody knows how to switch the LCD off - and back on again - the LCD is just dimmed - but stays on.
... of course this consumes battery a lot ...
i'd like to help - if i can ?
- i am a developer (but never developed for (xd)android so far)...
- i have a raph
- i have basic (xd)android knowledge
can somebody tell me, where to start ?
what exactly do we need ? the correct hardware registers / arm-code to handle it ?
Wouldn't it make sense to try on WM first - developing arm-code - without win-api of course.
WM has one advantage: i can test faster - since i don't have to reboot to android all the time.
so i need:
- i need to know, what the xdandroid developers already know about this topic - as far i know, they have the code to switch off - but not to switch on.
- i need a quickstart guide how to setup a "xdandroid development environment".
thank you!
Some thoughts
Baal, good look with your try. I'm sure many people will pray for your success -I'm one of them.
I don't have enough time to try to do that, but I spent many hours thinking about the problem. What I'ld do is:
Try to capture all the operations that WM does diring a sleep-on/sleep-off process, specifically registry modifications, internal calls, etc. Also try to save the status before and after, in case they depend on some kind of previous initialization.
I'm not sure if developers didn't get that information or do have it but didn't know how to implement it. Ask in the XDandroid development list.
If you have to do that, maybe you can use some kind of emulator, but probably you'll need to get a system debugger on your phone.
Modify the android module to do the same operations.
Here, both XDandroid Development List or other android developers should help you a lot.
In this part, you'll have to reboot many times...
Good luck! And keep us informed, please.
Well, this is a kernel issue. Unfortunately there's no "how-to" on the kernel sources...
The Getting the Source page is about the system image unfortunately.
Here's the GIT repo for the kernel code.
As for the rest of it, I don't know how to help you. I don't know how they shut the panel down, and as you know, no one actually figured out how to shut the screen back down. Hopefully someone else chimes in about the other information you requested.
Please keep us updated...
Hi, Baal_zebuz
I know it's been a short time since your intentions were declared, but, do you still keep them and you're working on it, or you already abandoned the idea -no matter the reasons, time, difficulty, etc.? Just to keep the hope's flame lighting or switch it off.
Thanks in advance!
Uhm... I use xdandroid in Raph100 and if the chargher is disconnected, the backlight os turning off after few seconds. I've downloaded the last one from xdandroid.com
Maybe I am OT, in this case I apologize
TheXeno said:
Uhm... I use xdandroid in Raph100 and if the chargher is disconnected, the backlight os turning off after few seconds. I've downloaded the last one from xdandroid.com
Maybe I am OT, in this case I apologize
Click to expand...
Click to collapse
Brightness is set to 0 and the backlight is shut off. Unfortunately the panel itself is still drawing power, and sucking battery life. No one has sorted out the proper kernel code to deinit/reinit the panel.
Howdy,
I have looked at the threads suggested to check out before starting a new one, and they did not help me much. I am a noob, and that may be why.
I have a sidekick 4g and would like the keyboard to stay lit a lot longer than it does. I slide it out and if I pause for the briefest of time, and the light goes out. Id there a way to make it stay lit until I close the keyboard?
Do I have to root the phone in order to make this happen? I have been reading all the root stuff I can find but not quite ready to take the plunge yet. I most likely can do it b sometimes I lack confidence when starting new things.
Thanks for the help ahead of time.
XcntrK
xcntrk said:
Howdy,
I have looked at the threads suggested to check out before starting a new one, and they did not help me much. I am a noob, and that may be why.
I have a sidekick 4g and would like the keyboard to stay lit a lot longer than it does. I slide it out and if I pause for the briefest of time, and the light goes out. Id there a way to make it stay lit until I close the keyboard?
Do I have to root the phone in order to make this happen? I have been reading all the root stuff I can find but not quite ready to take the plunge yet. I most likely can do it b sometimes I lack confidence when starting new things.
Thanks for the help ahead of time.
XcntrK
Click to expand...
Click to collapse
rooting is real simple
first download one click hedmial root (in either a stick in development or my ref)
go to settings on phone then applications then development turn debugging on
open one click
now hit root
finished
and yes to do anything good you need to root
Changing your screen timeout seems to affect how long the keyboard stays lit also. For example, I changed my screen timeout to 1 minute, and the keyboard stayed lit the whole time. Just go into Android Settings, find "Display" --> "Screen timeout" and set it to your choosing. Also, just tapping the Shift or Alt button turns the keyboard backlight on again.
I concur with immorality, rooting is no big deal. It's when you start messing with the system and flashing ROMs that things can go wonky if you don't know what you're doing and aren't careful, but most failures are recoverable using the aforementioned Heimdall.
Thanks for the info. I am going to go ahead and do the root. I would love to get rid of all this tmobile junk on the phone. And there are some other cool things that I have been reading about that you can do after you have rooted your phone. I will keep the forum up and running though just in case LOL
Thanks again y'all
tell you what, ill look into the keyboard light in the next day or so and when i find how to control them ill create you a flashable zip so you can easily change the time they stay on. or maybe even add it to my aroma package
but for now root your phone as you wont be able to do anything without it, follow the above method if youd like, i personally dont like one click root methods for various reasons so heres a quick guide i made
http://forum.xda-developers.com/showpost.php?p=40198560&postcount=27
again follow any method you would like, and i suggest to at least read up on the various ways. hopefully by the time your done and ready to flash your first rom ill have had time to look into the keyboard lights issue
good luck and happy flashing!
@demkantor thank you so very much. I am downloading the aroma, and have copied the notes on your link.
My Kaspersky is not letting me downliad the rage against the machine. I will see if I can get around it and let you know the outcome
I really do appreciate your help with the lights on the keyboard. I have tried resetting the screen timeout and every other thing suggested or that I can think of and it still goes out a second or so after the last letter entered.
hey no problem! try another browser maybe or turn virus protection off, any script that works to exploit a loophole will through the virus protection. hell some wont let you download superuser
but i assure you its legit
as for the keyboard lights, my sk4g is incapacitated right now so i ran a few tests in another android:
When i run this in a shell:
busybox find / -name 'timeout' 2> /dev/null | busybox grep -i timeout
I get this:
2> /dev/null | busybox grep -i timeout <
/system/xbin/timeout
/sys/class/firmware/timeout
/sys/module/uvcvideo/parameters/timeout
/sys/module/nf_conntrack_netbios_ns/parameters/timeout
and if i run:
busybox find / -name 'brightness' 2> /dev/null | busybox grep -i backlight
gives me:
ss' 2> /dev/null | busybox grep -i backlight <
/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
so i know where to start digging in my other androids, and hopefully if i find a fix in one it will be similar in the sidekick. ill keep you posted!
Got it, had to shut of part of Kaspersky and then make a exclusion for it when I unzipped LOL BUT I GOT IT YEAH!!! LOL
Thanks for all the effort with this.
good morning all,
i am hoping someone can help my stupid self.
i finally got a root to work on my phone, for the main purpose of removing mcafee. i start getting rid of the programs i don't need and can't find mcafee anywhere. turns out is in the "cannot remove" list.
so, i find a couple of tasks without any info and turned one off hoping that might be it:angel:.
turns out i turned off my input for the lockscreen. to make it even more fun, it is encrypted. i cannot get it to be recognized on my pc. i can get it to start in safe mode, and i can get it to start in the download mode.
it won't install the mtp drivers, but the rest are there.
so, i was hoping one or more of you wonderful, intelligent and, dare i say, beautiful people would know of a way to get around either the encryption or some way to turn the task back on so that i can enter my code.
thank you for not laughingtoo hard at my pain