Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
Known issues
- [Fixed] New icons are not working when TorchButton is installed to Storage Card
Todo
- Create an app to configure the registry settings
- See if support for Omnia Pro (B7610) is feasible (someone should send me the related dlls...)
- [Done] Add a seperate timeout for bright mode
- [Done] Add blink mode with bright led
- [Done] Use new icons provided by tnyynt
- [Done] Add support for Omnia (the one found here)
- [Impossible] See if it's possible to control leds seperately ('economic mode') Sorry, this is not possible. (Tech-talk: setting a single GPIO enables both LEDs. There doesn't seem to be a GPIO for each LED seperately.)
Wishful thinking
- Camera app to interpret the morse
History
Version 2.3
- Fix icons not showing in HTC Sense or WM 6.5 start menu when installed to Storage Card.
Version 2.2
- New icons for all TorchButton apps (thanks tnyynt!). These only work in WM6.5 and up. Older OS's will still see the old icons.
- Added registry setting to use bright setting in blink mode (see BlinkUsesBrightMode).
- Bright mode now has a seperate timeout, configurable in registry (see BrightModeTimeout).
- Added support for Samsung Omnia i9x0 devices (hopefully they all work). Thanks to raph/zemrwhite2/PaSSoA. Thanks to Chainfire for testing on his Omnia i900L.
- [edit] Shortcut names have changed. I found them nicer this way, no two-line icons. And the text is now also not cut-off when added as shortcut in the home screen.
- [edit] Improved handling of bright mode. It should stop immediately now when pressed again, instead of waiting for a 500ms interval. This makes BlinkUsesBrightMode possible combined with low intervals for blink mode.
- [edit] Soft-reset your phone after upgrading from an older version! Else the new icons will not show.
Version 2.1
- Bright mode is now support on the HTC HD2 (Leo).
- Added a one-time warning message when bright mode is used for the first time.
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Dont think about something. Untill i read your post. This could be handy sometimes. Thnx
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Great ! thanks
Have it on my Omnia and was hoping to have it for my future HD2 !
You're all welcome! Glad to hear you like it.
12aon said:
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Click to expand...
Click to collapse
The mode is there, but it's not as easily called as it was on the Touch Pro. In fact I haven't found the API call at all yet. May need some hacking around the API to get that to work. The normal mode produces _quite_ the amount of light though, it's even more light than the bright mode of the Touch Pro thanks to the dual led.
Zero Masamune said:
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Click to expand...
Click to collapse
hTorch will work again once I update the C# wrapper to support the Leo, as hTorch makes use of my C# library. I'll do that somewhere in the upcoming week.
Great, works perfect ! Txs
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
kinnyfaifai said:
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
Click to expand...
Click to collapse
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
NetRipper said:
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
Click to expand...
Click to collapse
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Heej nice, i come from oud-Beijerland
nice app, but bright mode doesn`t work for me..
NetRipper said:
Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
History
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Click to expand...
Click to collapse
20mihalko said:
nice app, but bright mode doesn`t work for me..
Click to expand...
Click to collapse
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
ET said:
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
Click to expand...
Click to collapse
sorry, my mistake
kinnyfaifai said:
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Click to expand...
Click to collapse
The vibrate function does not work at all on my X1 after installing and using hTorch. User beware..!
This is my next phone when O2 decide to put it on their shelves, and hopefully its built better than the X1.
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
l3v5y said:
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
Click to expand...
Click to collapse
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
NetRipper said:
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
Click to expand...
Click to collapse
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
l3v5y said:
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
Click to expand...
Click to collapse
There doesn't seem to be an un-init function. However, the debug console shows that it detects when the DLL is being attached to or detached from, so there's probably some cleanup code there.
I also haven't found any side-effects yet. TorchButton works fine even when the camera app is running. They don't interfere with eachother (other than toggling the LED to their own behalf). On the Touch Pro it wasn't possible to run TorchButton and the camera app at the same time. Not that I ever wanted to, but still.
In regard to that mode function. It must be for something. I tried using it in various ways already but it didn't matter. Maybe you'll have more luck
might be confused right now, but seems that when in camera mode, and battery is below 50% you cant use the flash - anybody know if this will affect the app?
haven't got my hd2 yet so cant help you out, but there's a thread under the Leo -- > Leo sub-forum
cheerios!
Related
Is there a reg hack to turn off the blue bluetooth light? I hate having 2 flashing lights on all the time (One blue and one green).
Thanks
I have installed Microsoft voice command 6.1 french and then the blue light turned off!
it is expensive to turn a light off but it works
(by the way if any body knows how to turn it one I'll be pleased to know...)
DXL007 said:
Is there a reg hack to turn off the blue bluetooth light? I hate having 2 flashing lights on all the time (One blue and one green).
Thanks
Click to expand...
Click to collapse
I will be please to be able to turn the green flashing light off too. I know that the flashing light indicates that the phone is on, but still annoying specially at night (please do not tell me to turn the TC upsidedown)
LOL, that's funny... Any way there has to be a way to turn them both off
There is a way. You know how to do a soft reset - you put a small thing in the reset hole.
If you want to disable the lights, do the same thing, but instead of putting a small thing in the reset hole, you put it on the light. You need to press really really hard... ;-)
However, there is no way to get them turned on again...
johncj said:
There is a way. You know how to do a soft reset - you put a small thing in the reset hole.
If you want to disable the lights, do the same thing, but instead of putting a small thing in the reset hole, you put it on the light. You need to press really really hard... ;-)
However, there is no way to get them turned on again...
Click to expand...
Click to collapse
Thanks for that awsome fix...lol however, I would like a little less violent solution....
This could be done in some devices with Tweaks2k2 .NET (http://www.tweaks2k2.com/portal/staticpages/index.php?page=20050224182009983). I don't know if this could work for Polaris too.
athanaso77 said:
This could be done in some devices with Tweaks2k2 .NET (http://www.tweaks2k2.com/portal/staticpages/index.php?page=20050224182009983). I don't know if this could work for Polaris too.
Click to expand...
Click to collapse
No I have this program, tried this first. I doesn't work.
Anyone have an answer?
Try this
Try this one
It works great on my TC. It's written for the Kaiser but also works on the TC. I've turned off all my LED's except when I've missed a sms or call. It's in Dutch but the interface is pretty clear so I don't think you'll have any problem controlling it. If so let me know.
The only downside with this program is that you can't control the WLAN LED. If you turn off the Phone LED (green flickering) the WLAN LED also gets turned off. Another thing is that the orange LED doesn't light up anymore when you charge your device. Hopefully someone will write a similar program especially designed for the TC. But apart from that it's a neat little program.
Cheers.
Found a fix! This program is awsome. It is for the Tilt, but works great on my TC!
Thanks for this.
It seems to be written for the Kaiser and says that its freeware as it installs.
Seems to work fine on my Orbit2.
I've now turned off both my lights as default - they should illuminate if I miss a call / get mail etc.
I do some work with User Interfaces for avionics.
Cardinal rule - "flashing lights are an exception, not default mode of operation".
ALL flashing lights
Thanks for this, works a treat on my Touch Cruise / Orbit 2
Maybe this link deserves its own post... took a while to find it
tigerpower said:
I have installed Microsoft voice command 6.1 french and then the blue light turned off!
it is expensive to turn a light off but it works
(by the way if any body knows how to turn it one I'll be pleased to know...)
Click to expand...
Click to collapse
Hmm! That explains why my BlueTooth LED stopped working - I recently installed M$ VC too... Weird.
Anyhow - while you've found a solution to turning off you LEDs, I thought I'd suggest another thing worth looking at for controlling them, for future reference - nueLED... It lets you redirect different LEDs. Still won't turn my BlueTooth LED back on though!
In Hermes I loved one feature: possibility of turning on the LEDs (called boldly a flash) with one of Vijay's apps. Of course I could not resist to test in on our (beloved) Rapahael but... Yes, you guessed right: marche pas/does not work/nie działa (choose the one you prefer). Anybody tried to work on this "problem of a person moving often in the dark areas with keys that must be inserted in always-too-small hole in the door"?
Of course you could just go in to camera settings to turn it on or off, it is only 3 or 4 screen taps away...
I mailed the author of the software, and he says that he will try to adapt to software as soon as he has some time, which would be in a few weeks. He says that there are people that already have modified his software to make it compatible with other devices. Anyone that can do this for the TP? I REALLY need that software too.
count me in on that one
i have been looking for it for 2 years now and it still dont look like there is gonna be an app for turning the flashlight on and off
as far as i know it is controlled by the cameradriver
Two years? It's been long available for wizard (vario) and hermes (vario 2). However, in case of my wizard I needed a rom update which included the correct htccamera1.dll (one that exports camera_flashlight method).
On a seperate note. I've been trying to get the flashlight to work on the touch pro, but no luck so far. Seems there is indeed (read it in diamond forums) at least one new parameter to the camera_init method. After debugging the dll it seems there may even be a lot more new parameters to the camera_init.
Anywayz, if I get anything to work I'll let it be known.
Waiting impatiently to test the results amd/or help in the process.
You could always try this:
http://www.artamata.com/pocketlight/
That doesn't work on the Raphael. It doesn't turn on the camera LED.
If you mean to use the screen blanker of that software, I sure hope you looked further, as there are other developers that made free versions, which are even more advanced (i.e. turning up backlight to full capacity at startup). Search the diamond forums for flashlight to find it.
Yay! I've just got it to work.
I'll build a small app for it to make it usable and post it on the forum.
Update:
http://forum.xda-developers.com/showthread.php?p=2588623#post2588623
NetRipper said:
Two years? It's been long available for wizard (vario) and hermes (vario 2). However, in case of my wizard I needed a rom update which included the correct htccamera1.dll (one that exports camera_flashlight method).
On a seperate note. I've been trying to get the flashlight to work on the touch pro, but no luck so far. Seems there is indeed (read it in diamond forums) at least one new parameter to the camera_init method. After debugging the dll it seems there may even be a lot more new parameters to the camera_init.
Anywayz, if I get anything to work I'll let it be known.
Click to expand...
Click to collapse
cheers mate ur the best
havent seen it for the vario only app i know off is vjay candela and that didnt work neither does all other applications for the flashlight..
and now i have a new phone and the flashlight application you just made ..
i cant be happier right now .. you made my miserable day a very illuminating one
flashlight
now that i've downloaded the code how do i implement the flash light?
jakubd said:
In Hermes I loved one feature: possibility of turning on the LEDs (called boldly a flash) with one of Vijay's apps. Of course I could not resist to test in on our (beloved) Rapahael but... Yes, you guessed right: marche pas/does not work/nie działa (choose the one you prefer). Anybody tried to work on this "problem of a person moving often in the dark areas with keys that must be inserted in always-too-small hole in the door"?
Click to expand...
Click to collapse
you should try hTorch 3.2 as well,
which has a very elegant interface:
http://forum.xda-developers.com/showthread.php?t=440405
As I said in another thread; lately I have been using TourchButton in combination with G-Trigger, I'm really pleased with how well it works.
The G-Trigger program runs in the background all the time, so now I just shake my phone a bit and I get light, shake it again and the TorchButton program runs again (thus turning it off).
And in the event the light should somehow accedentaly turn itself on, it will turn off after 60 sec as per the TorchButton code.
I know that there are many projects going on porting Android to quite a few WinMo HTC phones out there. (I'm currently only following the TyTN2/Kaiser porting, since that's the phone I have).
At least for the Tytn 2, there's still quite a few limitations (camera, bluetooth, wifi not working), so I was wondering if anyone knows if other projects have made more progress?
Are other HTC (newer) devices getting more features to work?
I will start, and keep a running list of what works on what device, and do my best to keep it updated regularly.
If you have some news/info/changes that need to be made, please post it here.
UPDATE:
So far it seems that Kaiser and Raphael has the most usable version of Android.
Kaiser: [SOURCE]
LCD :yes: Some applications have resolution issues
Touch screen :yes:
Keyboard :yes: Some kernels include option for Tilt configuration
Ambient light sensor :not yet: Button backlights always on
Camera :?: Anyone know the status here??
LEDs :yes: Android is able to control them, but they are currently mostly used for diagnostic purposes
WiFi :not yet: Drivers from HTC Dream probably won't help
Bluetooth :not yet: Drivers from HTC Dream may help?
Radio/GSM :yes: Needs work - data works sporadically
SD controller :yes:
Power saving :yes: Power collapse recently added, still a work in progress
Rear speaker ? Pressing the Speaker button from the Dialer menu does nothing!
GPS ?
Click to expand...
Click to collapse
Raphael [SOURCE]
What works...
:dialer
:incoming calls
utgoing calls
:messaging
:wallpapers changing
:affects
:touch screen
ictures
:music
:games
:icons
ower off(hold end key)
What doesn't work...
:camera
:sound
:sleep
:browser
:battery status
:some settings
:and many more!!
Click to expand...
Click to collapse
The Xperia X1 status is currently stopped, but the progress so far is: [SOURCE]
It boots.
It start doing a test.
Touch screen colours are fu up.
On screen keyboard only works.
Screen Align Fu up.
So it basicly only boots and does a test.
Not much more!
Click to expand...
Click to collapse
xmoo did some work for the xperia, but don't know how far he actually has come.
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=456595
Maybe this belongs in the development area but...
The evo3d got a notification led wich i like...what about if we can make the capacitive button led's blink or something when we have a mail and sms...
Maybe more guys have this idea but well....tell me if its possible and a good idea
It is probably possible and I think developers will have a hand on it if they havent yet.
It will be eventually supported.
this idea is awesome. i think it is possible
joker20 said:
this idea is awesome. i think it is possible
Click to expand...
Click to collapse
Glad someone's liking it
This would be a nice to have for sure. If can light up those "buttons" to use for notification, it will be great.
This is already done with O2X, so it is definitely on the way for us
My previous phone was GalaxyS which had no led aswell.
I used a programmed called NoLed on the Galaxy. Installed on Optimus 3d and seems to work fine.
Link to developer - http://www.devasque.com/noled/index.php
HTCtouchuk said:
My previous phone was GalaxyS which had no led aswell.
I used a programmed called NoLed on the Galaxy. Installed on Optimus 3d and seems to work fine.
Link to developer - http://www.devasque.com/noled/index.php
Click to expand...
Click to collapse
It doesnt support the capacitive button led's.
Sorry i was only suggesting this as a temporary alternative until further developments.
I really like this idea!
But is it possible to expand on it further?
Since there's 4 capacitive buttons on the phone, are we able to make them blink individually?
For example... home button blinks when we have a missed call, menu button blinks when we have a message, back button blinks when we have an email, and etc?
Noled seems to be working fine for me...
gismo918 said:
Noled seems to be working fine for me...
Click to expand...
Click to collapse
Yeah works fine for letting the SCREEN blink?
Were talking about the buttons
HTCtouchuk said:
Sorry i was only suggesting this as a temporary alternative until further developments.
Click to expand...
Click to collapse
Unfortunately not. As the app page states, AMOLED uses no power displaying a fully black pixel so displaying alerts on the screen takes very little power.
Now as the O3D has an old fashioned LCD, it consumes potentially a ton of power just to turn the screen on at all, because it has to light the whole screen just to start. Plus, it uses the MOST power displaying black (least displaying all white), so it would need the opposite behaviour.
[UPDATE]
Ah I see you can make the screen blink, I didn't notice that at first. Might actually be useful then.
i've tested it with the developer of the LG notification app. it seems, that the files which have to be used are'nt writeable. so without root it won't work
perhaps we should send tons of mails to LG, that they make it possible.
Alex Atkin UK said:
[UPDATE]
Ah I see you can make the screen blink, I didn't notice that at first. Might actually be useful then.
Click to expand...
Click to collapse
Also the notifications can have a time limit, i have set at 15mins and haven't noticed any battery drain.
Modified 2X/Black touch led notification app
Hi guys,
I've modified Martin Börjesson's app and now it works on ROOTed O3D and I'll upload it soon.
To-do:
1) fading doesn't work
2) change of brightness doesn't work
What will never work
1) separate LEDs - I don't think there's a way to control each of them, only all 4 LEDs
ztracenyDen said:
Hi guys,
I've modified Martin Börjesson's app and now it works on ROOTed O3D and I'll upload it soon.
To-do:
1) fading doesn't work
2) change of brightness doesn't work
What will never work
1) separate LEDs - I don't think there's a way to control each of them, only all 4 LEDs
Click to expand...
Click to collapse
i am checking every 15 minutes for an update to this
Here it is!
I'm new to android, so I hope the "apk" file is enough for installation:
Fileserve: http://www.fileserve.com/file/qqFjsfS/Optimus3Dnotifications.apk
Mirror: http://home.zcu.cz/~chylek/Optimus3Dnotifications.apk
Source code:
http://www.fileserve.com/file/YvbqKbk/optimus3DnotificationsSRC.zip
Hi
I have a problem with downloading app
Cane you upload to other server
Megaupload or rapid
Thankyou
Sent from my LG-P920 using XDA App
This thread is meant for (technical) discussion of OT-995, notably ICS-based (e.g. CM9 and AOKP) OS and kernel development.
Any non-technical questions/discussion belong in the general OT-995 thread.
Status quo
There's an ongoing effort bring CM9 and AOKP to the OT-995. Although neither is anywhere near complete, basic functionality (graphics/audio/gsm (non-data)/wifi/sensors) is present.
Both iuss and fonix232 currently maintain Android repositories related to OT-995. A common kernel is maintained by iuss, based on the 2.6.35.11 release by Alcatel.
Updates will likely be posted in this thread, but this topic start may not be fully up-to-date.
Source repositories
kernel: https://github.com/ius/tct_cocktail_kernel
android/bootable/recovery: https://github.com/ius/android_bootable_recovery
android/device/tct/cocktail: https://github.com/ius/android_device_tct_cocktail
(on top of the CM 'ics' branch)
android/device/alcatel/cocktail: https://github.com/fonix232/android_device_alcatel_cocktail
android/vendor/alcatel/cocktail: https://github.com/fonix232/android_vendor_alcatel_cocktail
Flashable releases
fonix232 has provided flashable builds of CM9 and AOKP: http://goo.im/devs/fonix232/OT995/ICS
(Be aware that these might not always be up to date with the repositories listed above)
Other bits of interest
iuss' slightly outdated README for his repositories.
fonix232 said:
Possibly, couldn't really boot yours though :\
Also, some more info about liblights. The tempfix works (keyboard lights up with screen), but apparently when the keyboard file is set in liblights, it won't call the keyboard function. If I set it to e.g. the notification LED, it is called, but bails out with error 13 (no access to notification LED control).
Click to expand...
Click to collapse
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.
iuss said:
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.
Click to expand...
Click to collapse
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens. I've logged it, every device open, every call of write_int, every device light setting, everything, and keyboard only showed up when:
a, Not the proper keyboard brightness path was given (in my case, it was the notification LED)
b, Moved the keyboard control to the lcd-backlight controller function - as it is currently.
And apparently yes, I've forgot to chown the whole LED folder's content to system
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)
handy tool for making logs...
This app runs the following commands:
dmesg
logcat -v time -d
logcat -v time -b radio -d
getprop
uname -a
ps
Click to expand...
Click to collapse
Download : dl.dropbox.com/u/2889810/apps/getlogs_v1.1.apk
Thread : http://forum.xda-developers.com/showthread.php?t=1123129
I do it by hand, but thanks ;D
maby its a good thing to copy the apk to system/app
there will be a lot of people installing the build and then complain here that some stuff dont work (also bugs u didnt even realize they where there cuz u cannot test alone)
and when u ask them for logs some of them dont even know how to do it..
fonix232 said:
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens.
Click to expand...
Click to collapse
If I interpreted things right, you mean neither was ever called? If you had wired buttons-to-keyboard it should've worked, the reason why set_keyboard_light was never called is because TCT hacked the Java framework (by making the turn-on-screen-backlight-and-buttons event turn on the keyboard light as well).
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
Click to expand...
Click to collapse
The monkey approach - I checked out the code for Nexus; it doesn't provide a battery light at all (which is probably only useful if you have a green/red led); attention and notification are routed to the same led.
The stock liblights seems to work quite well, e.g. notification (sms/mail) causes a blink, attention (USB inserted) a constant light.
Let's just copy stock liblights for now, we can rewrite/reverse it later.
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)
Click to expand...
Click to collapse
Good catch. Fixed in my kernel tree (no-op instead of a null fptr call)
iuss, I understand your concerns, and most probably will stick to it, but I've already began writing liblights Actually, it's like, around the fifth revision, fifth try, and still no worky. Just finished up my test-package (ultimate AOKP-CM9 with GApps installer, will post it separately), will test that and check back.
EDIT:
Tried your new kernel, but somehow, wifi fails to connect. DHCP timeouts, etcetera.
Works fine here (and I didn't touch anything related). For reference, a built zImage.
iuss said:
Works fine here (and I didn't touch anything related). For reference, a built zImage.
Click to expand...
Click to collapse
Egh, turns out it was my fault, something frikked up with my installer. Still working on the small quirks tho
Also an idea about BT - why not use the same module that the Galaxy Tab P4 series used? They are all BCM4330, so theoretically it should work!
question is it possible to make 3 point multitouch? (or more?)
The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.
iuss said:
The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.
Click to expand...
Click to collapse
The 5306 can detect up to 5 distinct touches, but apparently either the chip was locked down to two (or via baseband, and might be unlocked in ICS), or just the communication signal is processed in a wrong way.
But nice addition with the multitouch support!
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.
fonix232 said:
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.
Click to expand...
Click to collapse
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).
iuss said:
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).
Click to expand...
Click to collapse
I don't see either, but when brightness is on manual, I have to modify the value for the keyboard lights to show up.
Performance issue
I know, my question is maybe premature.
But what about the performance. Do you feel it could be faster than the stock rom?
Maybe some quadrant test would give us some idea?
it feels amazing
I think I might know a way to have 5-point touch, but it won't be easy...
Looking at the source code of the ft5306, you can see that in the firmware upgrade part, it points to a header file: FTS0094P430_CockTail_V1d_20111123_app.h
This header is nothing else, but an actual FT5306 firmware file, dissected into bytes. Basically, they took the hexa code of a binary firmware, and pasted it into a text file byte by byte! Sounds stupid, but actually a good way to integrate a firmware into the kernel.
However, the function can be overwritten so instead it reads bytes from an actual binary firmware file, located on the filesystem. Doing that, plus acquiring a 800*480 FT5306 firmware image (so far I've only found an 1024*600 one) would result in unlocking the whole capacity of the panel!
Also gave a try at the camera HAL. I can't make it work sadly :\
What happens if you write bogus firmware to ft5306, though? :x
The panel will most probably won't work, although the firmwares are pretty similar in all the ft5x06 series.
Aaaalthough, if you reflash a proper firmware, it should work again