[Q] XDANDROID: panel/LCD switch off/on (raph) ? - Touch Pro, Fuze General

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.

Related

Backlight reverting to 10 seconds

I am posting this because 1) I don't think this issue is specific to one cooked ROM, and 2) despite searching, I can't find a solution.
The issue is that with all of the ROMs I tried that are based on recent AT&T or HTC 6.1 ROMs, the backlight reverts back to 10 seconds. I can change it through Backlight settings to something else, and go back to the control panel a minute later and see it's back to 10 seconds. Very annoying.
I've seen this with a couple of L26 ROMs, the stock AT&T 6.1 ROM, and the HyperDragon III Pro ROM which I am currently using. I see this whether I have S2U2 or not (I am on 1.22b now). My current set-up: HardSPL 3.56, HyperDragon III Pro Sept-17, S2U2 1.22b... but like I said, I don't think it's ROM-specific.
Calling all experts: is there a fix for this? (If you are planning on posting something like "I don't have this problem" or "Change your backlight setting through the control panel", please don't clutter the thread with your post).
Thanks!
I spent a fair bit of time searching this and testing various suggestions that seemed to work for other people, however I was constantly getting the 10-second reversion, plus the even more annoying dimming backlight when locked.
Anyway I posted this:
http://forum.xda-developers.com/showthread.php?t=425361
And now after removing the registry 'BatteryTimeout' my backlight is working exactly as I want it - i.e. backlight dims afer 30-seconds regardless of whether it is locked or not, plus when locked the backlight comes on when the screen is tapped.
Now wait for the various replies saying 'use the search'.....
Andy
FWIW, I too had this annoying issue, but found that using ROMeOS roms (last version is 4.6) I don't get this issue. Not sure why or what the chef did to fix it.
The chef has now moved onto the Raphael...so he is not working on his Kaiser roms anymore
ADB100 said:
I spent a fair bit of time searching this and testing various suggestions that seemed to work for other people, however I was constantly getting the 10-second reversion, plus the even more annoying dimming backlight when locked.
Anyway I posted this:
http://forum.xda-developers.com/showthread.php?t=425361
And now after removing the registry 'BatteryTimeout' my backlight is working exactly as I want it - i.e. backlight dims afer 30-seconds regardless of whether it is locked or not, plus when locked the backlight comes on when the screen is tapped.
Now wait for the various replies saying 'use the search'.....
Andy
Click to expand...
Click to collapse
Thanks, let's see if it sticks. I've tried quite a few methods I found during my search and those didn't work....
It happened to me also with akadonny's 3.29.DK.10 / SPL 3.56.Hard
I changed SPL in the meantime for a different reason, and I had no backlight issues afterwards, but still I would not link that strictly to SPL cause I changed many other things.
Anyway, I found a power setup that works for me very well:
- for "on battery power" I only use turn off device (uncheck turn off backlight)
- for "on external power" I only use turn off backlight (uncheck turn off device)
P.S. This never happened to me with earlier builds, only with 20748.1.4.0.
Well, the first approach didn't work. I have a setup similar to the previous post, but that hasn't helped. I am on SPL 3.56 Hard. Which SPL did you go back to?
Second approach didn't work either. I see a lot of posts with people reporting the same problem... Has there been a definitive solution?
Im using HyperDragon_III_Omnia_20080818. With this ROM I dont have the issue of the 10 sec backlight. I use Hard SPL 3.29.
Chau Juan
I also have this problem and it is making me sick, at night while in bed I am trying to read an ebook but I have to tap on screen every 10 seconds!!
I am HyperDragon_III_Omnia ROM and I have tried many tweaks no luck.
Edit...
Ok I think the problem is now sorted.
Here's what I did... changed the following registry - HKCU\ControlPanel\BackLight\ACTimeout set the DWORD to 0 and reset the device.
So far it seems to be fine.
Invisible Sense said:
I also have this problem and it is making me sick, at night while in bed I am trying to read an ebook but I have to tap on screen every 10 seconds!!
I am HyperDragon_III_Omnia ROM and I have tried many tweaks no luck.
Edit...
Ok I think the problem is now sorted.
Here's what I did... changed the following registry - HKCU\ControlPanel\BackLight\ACTimeout set the DWORD to 0 and reset the device.
So far it seems to be fine.
Click to expand...
Click to collapse
Hmmm, I'll try this, thanks. This should be for backlight while connected... but worth a shot. I wonder if HardSPL version makes a difference... I'm on 3.56.

Where to Start

Hello everyone,
My AT&T sales guy sent me to this forum. I have been looking around and searching and realized that I am in over my head to be honest. I just got a Fuze and like it for the most part. There are a few things that I do not care for that maybe you guys can tell me if I need a new ROM and if so, which one. The things I would like to change are:
1. I would like quicker/easier access to my Tasks. I use Outlook tasks A LOT and it is not easy to get to them (not as easy as contacts and messaging anyway)
2. The notifications are not obvious. I was running an 8525 with WM6 and the notification would pop up at the bottom of the screen. I have to click the tiny notification bell symbol on the Fuse, which is annoying.
3. Scrolling is an issue. I am very used to my scroll wheel on the 8525. Is it possible re-map the volume control buttons to scrolling arrows?
Also, dragging my finger on the screen is a pain. I almost always call someone inadvertently when I try to scroll.
4. Battery life is MUCH better than my 8525 (probably due to the 8525s age + the better technology), but battery life could always be better.
5. The ring and speaker phone volume is pretty low, even with my volume control maxed out.
6. I don't like that the screen turns off when someone answers. It is great for everything except voicemail.
So, all in all, I am happy with it and hopefully the short list above is comprised of things that are easy to fix. What do you think, can I fix these issues with registry changes, or do I need to change the ROM? If I need to change the ROM, which one (I have found dozens)??
Thanks!
Can't answer most of those.
#6. Get Touch In Call Screen Tweak
http://forum.xda-developers.com/showthread.php?t=488991
This is a good page to start looking for answers:
http://wiki.xda-developers.com/
Yes - a custom rom will (probably) make it easier to access the parts you want quickly, however some 3rd party apps may give you the same control without the hassle of flashing (however, if you do decide to flash - its not difficult, just make sure you read the guides carefully before you start!
As for the audio volume - (sorry if this sounds dumb) make sure that the screen protector has a cut-out over the speaker. Crazy i know - but from reading some old threads on here - not all of them did, so you end up blocking the speaker & not being able to hear properly.
Battery life - depends on usage of course, also a different radio may make a difference for you. Unfortuantly there isnt a magic one here, different radios seem to give different performance & battery life in different areas (and of course usage patterns)
Re-mapping buttons? google for AE Button - can remap buttons in anyway you like.
Notifications - i believe you can get the balloon preview at the bottom of the screen using advanced config (search for it on here) [dont have my phone with me right now so i cant check what the setting is]
Hope it helps a little and welcome to the forums
Thanks for the info guys. I like the looks of the in-call tweak, but think I'll wait until I get the rest of the stuff and do it all at once.
Beeble,
I admit that I am a little worried about flashing it for a new ROM, especially since there are so many out there. If I do it, I want to make my choice, do it and be done with it. I do not want to be flashing it every 2 or three days until I find a ROM that I like.
As with the phone tweak, I think I'll try the the AE Button one when I do the in-call tweak.
Couldn't find a setting on the notification bubbles. Maybe I am not looking in the right place.
How do I get a new radio? I assume this is a software thing. Does this require flashing? Is it an ordeal to do this?
Thanks!
Unfortuantly you will almost certainly flash more than 1 rom once you start!
You'll (probably) spend hours and hours reading about them and trying to decide which is right for you. Then 3 days later you'll start grabbing random ones and just trying them out!
Before you flash anything you'll need to hard spl your phone. This is very important, but really pretty simple (if you dont hard spl, you can only flash official roms from your phone supplier - once you have hard spl you can flash any rom from any carrier, aswell as custom roms)
This is the guide to flashing and its very simple to follow - just take your time & dont skip steps.
If you do get the flashing bug - check out this UC thread it'll tell you how to automate about 95% of the setup of the phone after a flash (or hard reset).
Flashing a radio is the same process as flashing a rom, although it wont perform a hard reset (so you dont have to set everything up again) - But as always backup first just in case!
Radio thread here - remember, once you have hard spl'd your phone you can flash any Raphael radio. If you want to use a radio from another device, you'll need to Security unlock it first
Backup - you can use backup software like sprite, but if you are changing rom dont restore the old backup - you'll get all kinds of problems! Instead use PIM backup (free) which you can use to restore numbers/meetings/calls etc regardless of rom
If you get problems - or want some help - just let us know whats stumping you, make sure you've had a good read first - and please dont ask what rom you should get without listing exactly what you want the rom to do for you! most roms come down to preference.
Finally - good luck! and remember you have a GSM phone - so stay away from CDMA threads & downloads, otherwise you could brick your phone (follow the links in the guides and you cant go wrong)

Htc Touch Pro (Raphael 500) Running Android , How to overclock?

Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.

[Q] Tasker Q

Hey got a weird problem with my Tasker. I had followed the guide posted in the Android forums about creating a text and missed call widget using minimal text as well.
It was all going swell. until seemingly randomly it stopped counting when the phone was locked. I am completely stumped, which is not surprising, as I'm relatively new to this whole thing. As far as I'm aware I haven't changed anything except updating the apps.
Anyway, if anyone has a nice answer I'm happy to let you say it as patronisingly as you want.
Cheers
John
Bump for frustration!
The phones cpu usually gets turned into a low state when it is in standby. Only major events like calls or texts will wake it.
You need a PARTIAL_WAKE_LOCK for your phone to still register widget events or sensors during that time.
It is possible that some one app/widget of yours aquired such a wake lock before, which in return made it possible for your widget to work during that time.
I have made you a small tool that will aquire a wakelock when it is turned on.
Tell me if it helps.
Thanks for your reply. I have tested it with your app and unfortunately it has not worked.
Sent from my Nexus S using Tapatalk
Back up to the top for other suggestions or workarounds.
Use adb logcat from the android sdk to read the log, there might be some hints on whats going on when you lock your phone.
Cheers for your suggestion. I've looked into it, but tbh am struggling a bit. I think I'll leave it, thanks for your ideas though.

[Q] Make soft button lights stay on

Hi,
Is there anyway to make the soft keys stay on all the time when the screen is on? I searched all over for this answer and I found a bunch of apps and tweaks that work on other phones but none for ours.
My Light/Proximity sensor don't work , as I confirmed with androsensor. So my button lights never turn on. When I flash a new rom sometimes they work for a few hours or till I restart then never turn on again. They also work when im in recovery. I also just now tried a CM9 rom and found out if I adjust the brightness they lights turn on until I turn off the screen then they go off.
Only tweak I could find for our build.prop is
"ro.mot.buttonlight.timeout=0"
Which didnt help me.
Thanks in advanced
as i know you can control it with kernel file.but i dont know to edit it.ask it from a kernel developer (flaux, or sebestian)
Sent from my HTC Sensation Z710e using XDA
Thanks I'll shoot them a message
Guess I'll bump this thread with a little update.
Sent a PM to every kernel dev for the sensation.
1 is busy working on his first android app
1 is willing to research it and if he figures it out will compile something
1 is confident he could do it but is busy and its something he wouldn't want in his kernel.
Will update it if anyone succeeds and I know there are a few people looking for this feature.
I'm glad the community is responsive
HeXDeMoN said:
Hi,
Is there anyway to make the soft keys stay on all the time when the screen is on? I searched all over for this answer and I found a bunch of apps and tweaks that work on other phones but none for ours.
My Light/Proximity sensor don't work , as I confirmed with androsensor. So my button lights never turn on. When I flash a new rom sometimes they work for a few hours or till I restart then never turn on again. They also work when im in recovery. I also just now tried a CM9 rom and found out if I adjust the brightness they lights turn on until I turn off the screen then they go off.
Only tweak I could find for our build.prop is
"ro.mot.buttonlight.timeout=0"
Which didnt help me.
Thanks in advanced
Click to expand...
Click to collapse
@HexDemon:
Did you try this app? I've been running it and it fixes it perfectly (link below). My lights don't work at all otherwise. LeeDroid Tweaks will either turn them ON or OFF, not let them be controlled automatically. The newest versions of LD Tweaks (4.2/4.3) don't let them turn on AT ALL and the Devs are not interested in answering my questions there either. Other users have gotten involved though thank God, but no answers really.
https://play.google.com/store/apps/...1bGwsMSwyLDEsImNvbS5kZXNrYW5nZWwua2JsaWdodCJd
My Proximity and Light Sensors are also ****ed......and no fixes that work to date.
I'm willing to pay $$$ to whoever can find a fix that will STICK! (I am dead serious!)

Categories

Resources