Related
Well I have searched and searched and can not seem to figure out how to disable the service led without disabling all the functions of ALLledmgr. Of course that works but that means vibration and a number of other things. Someone had mentioned the nled reg entry hack tried that no luck. I have looked through countless dlls and files for any reference that might come close to disabling the service led but I just cant seem to find it. So many other phones(cheap phones) let you disable it why cant this one?
I remember back to a simple hex edit on my motorola that could do many things we even had script files that could change the leds colors etc and do crazy things on boot etc(that was linux of course).
So any of you pros out there came across anything that might be related to the service led?
i love the service LED's if it werent for them i wouldnt like my TyTN as much .. they really mean that much to me
sadly we're not in the good ole' motorola days (that was bliss) but i have the perfect soloution! :
Get a black permanent marker, and colour in the Service LED
et voila!! it no longer flashes and you still have vibrate, sounds etc ...
LOL
That´s was a really tip problem solution !!
Service LED does not bother me at all.
Or gently mash it with a sharp knife or screwdriver. (same solution for that silly light/speaker on cars that warn you to put a seatbelt on)
Maybe I wasnt clear about what I wanted. When I meant service led I meant that it just constantly flashes green to tell you that you have a signal. I want my leds to work, but the way I want them to. I want them to flash when I have a missed call or unread message etc. I just do not want it to constantly flash green in a service area Im always in a service area.
Many of you laugh of course and say it doesnt bother you etc. But I bet that when it is figured out where and how it is access and then being able to customize it change its colors etc, those who laugh will also be among the people using those nifty custom leds(blue for bluetooth,green for message,orange for missed call etc. So try and support the idea instead of laughing at it.
For me seeing that green flash over and over is just a constant reminder of something I can not customize on my super customized phone.
Psiodon
Psiodon said:
Well I have searched and searched and can not seem to figure out how to disable the service led without disabling all the functions of ALLledmgr. Of course that works but that means vibration and a number of other things. Someone had mentioned the nled reg entry hack tried that no luck. I have looked through countless dlls and files for any reference that might come close to disabling the service led but I just cant seem to find it. So many other phones(cheap phones) let you disable it why cant this one?
I remember back to a simple hex edit on my motorola that could do many things we even had script files that could change the leds colors etc and do crazy things on boot etc(that was linux of course).
So any of you pros out there came across anything that might be related to the service led?
Click to expand...
Click to collapse
try this out
Wow the attatched file actually worked! Still maintain all other functions with only the service led disabled. Im going to start ripping it apart and see if I can come up with anything new.
Thanks much for finding it, making it, or whatever, hats off to you.
Psiodon
Psiodon said:
Wow the attatched file actually worked! Still maintain all other functions with only the service led disabled. Im going to start ripping it apart and see if I can come up with anything new.
Thanks much for finding it, making it, or whatever, hats off to you.
Psiodon
Click to expand...
Click to collapse
that one was too early. it has a bug when charging. i have a 3.1 version that reads if the charger is on and works better. if you want it let me know.
this 2.1 version is the one i use.
codyppc said:
that one was too early. it has a bug when charging. i have a 3.1 version that reads if the charger is on and works better. if you want it let me know.
this 2.1 version is the one i use.
Click to expand...
Click to collapse
Please do post the 3.1 verison and thanks
The first one you posted seems to e 3.0 the second 2.1, ill try it to see whats the difference but 3.0 works fine even when charging except it gives you a flashing orange led instead of constant on led, letting it charge to full and see what happens. Yes please post any versions you have so I can try to see the different modifications they are doing between them.
I can see that it is simply using a mort script to scan the notification que for changes and using the treo exe to make modifications. Im in the process of decompiling the treo exe to see what mods can be made.
My concern here(which may be a retarded one so small) that you have a fight going on with the phone constantly telling it to do one thing and the mortscript and treo exe telling it to do something else. I can see that mortscript is using about 3%cpu cycle every 5 seconds or so. Not sure if that is going to impact battery usage or not, but my end goal would be do away with the fighting and just having the os do what its supposed to do.
Psiodon
I would like to request that anyone who likes or uses this app please stop by thier forums and send a thank you. After reading through all the threads they put alot of time and effort to make it work. And although it was not designed for our phones by chance it works. I have already sent my thank yous and hope more will do the same.
http://discussion.treocentral.com/showthread.php?p=1313922#post1313922
http://pdaphonehome.com/forums/ppc-6800-xv6800/89656-led-killer-3-1-a.html
BobbyK said:
Please do post the 3.1 verison and thanks
Click to expand...
Click to collapse
i put 3.1 in place of 3.0
i still think 2.1 is better. still work in progess.
fixed it myself
latest version installed working good no problems
Psiodon
@psiodon: Did you do any "re-work" on it? If yes, could u please attach here so everybody can benefit?
Thanks
Chris
No I have not done anything at all since it is already functional, what I am currently looking into is the other three leds that we have and what can done with them. Im also trying to figure out more info on our leds, if they are only tri color, etc and if its possible to get our two green and red phone leds blinking as a notification as well, but I am pretty sure those two leds are controlled together as on or off and probably cannot be controlled individually, time will tell.
Psiodon
Did this work on HTC Artemis (o2 Orbit) too?
Thank you!
Just a quick note of thanks to CodyPPC for the link!
That damned service light has been annoying me for months - I've taken to putting the phone in a draw / turning it upside down to stop the flashing annoying me when trying to get to sleep in an otherwise totally dark room!
This was the 1st site to come up on a google search - and am really impressed - cheers!
I'll send thanks to the devs on the other forum as well.
It looks like you're looking to enhance/fiddle with this further - controlling the LED's in various ways - - have you made any progress? are you in a position to share any code (compiled/source) or tips? I just want to dabble - have no real goal in mind - -- - the main thing is no more flashing green!!! woo!
With past experience with Android on the HD2 I noticed the white letters on boot dissapear when I switched the latest kernels, is there another way of doing this? An image or zip file? I can replace bootanimation.zip from /system/media and I get the new one, but how do I hide the white letters of linux booting? Or is that a new HARET they were replacing?
Thanks.
I know, for a fact, when this port is more complete we'll get rid of the flying text. Not at this stage, sorry.
arrrghhh said:
I know, for a fact, when this port is more complete we'll get rid of the flying text. Not at this stage, sorry.
Click to expand...
Click to collapse
Will there be an option in the port to keep view that text if you like? An escape sequence, so to speak? I personally like watching it and seeing what's going on. Sometimes it's the quickest, easiest way to find a problem.
jchutch2 said:
Will there be an option in the port to keep view that text if you like? An escape sequence, so to speak? I personally like watching it and seeing what's going on. Sometimes it's the quickest, easiest way to find a problem.
Click to expand...
Click to collapse
Hence the reason it's left in at the moment... we need it for debugging. Same reason the LED is used to indicate sleep/wake status.
Anyhoo, I can't really speak to whether or not we'll be able to enable and disable the flying text. Assuming the project is 'stable' and people are just pumping out builds instead of kernels... I would imagine there would be no need for the text to be shown whatsoever - if there's nothing wrong, there's nothing to troubleshoot
Perhaps there's a startup.txt option, or there will be kernels with debugging enabled. Not sure, these are just guesses of what could happen. No clue what will actually be implemented when that day comes.
arrrghhh said:
Hence the reason it's left in at the moment... we need it for debugging. Same reason the LED is used to indicate sleep/wake status.
Anyhoo, I can't really speak to whether or not we'll be able to enable and disable the flying text. Assuming the project is 'stable' and people are just pumping out builds instead of kernels... I would imagine there would be no need for the text to be shown whatsoever - if there's nothing wrong, there's nothing to troubleshoot
Perhaps there's a startup.txt option, or there will be kernels with debugging enabled. Not sure, these are just guesses of what could happen. No clue what will actually be implemented when that day comes.
Click to expand...
Click to collapse
Thanks for the input, sir.
Yes, I agree with you that it's needed, BUT I am just asking if there is a way to get rid of it and not by kernel way... Like a Haret option maybe?
Just wondering, but is there any way to increase the pulsing speed of the trackpad LED?
A lot of people have suggested LedMe Know but it doesn't have support for Google Voice (which I use for sms) and it flashes the trackpad, rather than pulses.
I've also tried Light Flow and although it pulses the trackpad and supports Voice, it doesn't change the speed of the pulse
Any suggestions?
Have you tried playing with the custom timing settings in Led me know?
If gvoice isn't supported, then perhaps it wont work....sry if it doesn't.
Well, like I said up top, it only flashes the led, instead of the pulses, regardless of any speed settings.
Plus no Google Voice in LedMe Know. Light Flow does support it (so its definately possible ), but it does not alter the pulse frequency so it doesn't add anything that stock didn't already do.
Sent from my T-Mobile G2 via telegram
Maybe you could contact the app developers and get them to add the feature(s)?
Some can be surprisingly responsive.
Good suggestion...but not quite the solution I'm looking for since LedMe flashes rather than pulses and I'd prefer if I didn't have to keep an app in memory just to change the frequency of a stock feature :/
Maybe there's a way to modify the lights.vision.so or something?
EDIT: I doubt the developer would try his hand at pulsing rather than flashing since it seems I'm just a minority who prefers the trackpad led rather than the speaker led. Also this seems like a device specific feature and the dev says in the app description: "only available at the moment for htc desire 2.2" so I doubt he has a DZ to test on... I found
EDIT2: I found exactly what I was looking for (http://forum.xda-developers.com/showpost.php?p=5609688&postcount=25) but sadly its only for Nexus One. I'm messaging the developer to see if maybe he'd port it over...
Sent from my T-Mobile G2 via telegram
Yeah I dont know much about editing those files, but some app devs are helpful. It might actually just be a quick edit for them to gain compatibility with GVoice.
I only use LED me know to flash my trackpad light really fast, upon arrival of sms' through tmobile carrier/handcent tho.
I hope you figure something out. I would like like it to pulse fast rather then just blink.
daaango said:
Good suggestion...but not quite the solution I'm looking for since LedMe flashes rather than pulses and I'd prefer if I didn't have to keep an app in memory just to change the frequency of a stock feature :/
Maybe there's a way to modify the lights.vision.so or something?
EDIT: I doubt the developer would try his hand at pulsing rather than flashing since it seems I'm just a minority who prefers the trackpad led rather than the speaker led. Also this seems like a device specific feature and the dev says in the app description: "only available at the moment for htc desire 2.2" so I doubt he has a DZ to test on... I found
EDIT2: I found exactly what I was looking for (http://forum.xda-developers.com/showpost.php?p=5609688&postcount=25) but sadly its only for Nexus One. I'm messaging the developer to see if maybe he'd port it over...
Sent from my T-Mobile G2 via telegram
Click to expand...
Click to collapse
Switch to an MIUI rom. It has the feature built in.
I appreciate pulsing the trackpad LED as well. However it's too slow a pulse at default speed, to be able to quickly peek at your phone and be able to tell if you have a message or not.
xREVOx: What exactly is this feature called? I want to look around and see if it will be included in the net CyanogenMod version.
Proxin said:
I appreciate pulsing the trackpad LED as well. However it's too slow a pulse at default speed, to be able to quickly peek at your phone and be able to tell if you have a message or not.
xREVOx: What exactly is this feature called? I want to look around and see if it will be included in the net CyanogenMod version.
Click to expand...
Click to collapse
I'm not using the MIUI rom right now, but it was called either Pulse Frequency or Pulse Delay. Default is 9 seconds. You can change it to as little as a 1 second delay.
I might have to flash it just to check it out and see how it works.
Currently I have LED me know flash my trackpad at 100 milisec. on and 100 milisec. off. Flashes fast and I notice it right away when checking for messages.
I just rather have the pulsing close to that speed.
Well I guess its nice to know that there's an actual solution... I wonder how hard it is to extract from miui rom?
I was looking around for the source of miui, but apparently its not released by their dev team...?
Sent from my T-Mobile G2 via Words With Friends for 42 points
daaango said:
Well I guess its nice to know that there's an actual solution... I wonder how hard it is to extract from miui rom?
I was looking around for the source of miui, but apparently its not released by their dev team...?
Sent from my T-Mobile G2 via Words With Friends for 42 points
Click to expand...
Click to collapse
You could try just flashing the exact file that controls it to your phone, from the MIUI rom... not sure exactly what it is though.
Proxin said:
You could try just flashing the exact file that controls it to your phone, from the MIUI rom... not sure exactly what it is though.
Click to expand...
Click to collapse
I believe its in Settings? I saw a video of MIUI running on a G2 and Trackpad Settings was in the Settings menu...not sure if it contains the pulse frequency but meh. If it is, I don't think it'll be too smart to flash it but idk.
Sent from my T-Mobile G2 via Words With Friends for 42 points
Someone asked what the point of the new .39 kernel is, well here's a new feature I've coded up that was made possible due to the more modern kernel.
I have modified the touchscreen driver in the kernel so that the zoom bar is now working, and it sends signals to Android that make it think you're sending a multitouch pinch-to-zoom.
I've got it set so that it sends an input from the center of the screen. As you slide right, the driver tells Android two fingers are moving apart from the center. As you slide left, the driver tells Android two fingers are sliding from the sides towards the center. The net result is that the zoom bar works in any app that supports pinch to zoom.
I've uploaded a video showing it in action:
http://www.youtube.com/watch?v=GRWUzPveU14
I'm going to submit this patch soon, and I'd like it if some people would try it out and give any feedback before I do so. I suppose things to pay attention to would be any increased wonkiness in the touch response, as well as boundaries for the zoom bar. Also, if you have a better idea on how this should work, it's now or never.
Unfortunately, this is a modification of the new .39 kernel, which means that a lot of things are not working on it, and this test kernel will most likely not be suitable for daily use if you like wifi and the other things that don't work on .39 yet.
In order to install you must do the following:
1. Replace your zImage with the one attached.
2. Use the .39 haret (included in the zip for your convenience) with the .39 startup.txt line (set initrd_offset 0x00a00000)
3. Place the included android.hardware.touchscreen.multitouch.xml under /system/etc/permissions. I tried bind-mounting it from conf, but for some reason that did not work for me. If you don't do add this permission file, the multitouch points will still be sent to Android (and will show up in the app Multitouch Test), but Google's own apps like Browser will ignore them.
Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.
Tippfehler said:
Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.
Click to expand...
Click to collapse
I totally agree with that!
Rhod100_nl
Nice work!
I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Impressive. Thanks for the vid.
I'm planning to give the .39 kernel a quick test run, hopefully this weekend. There's some software that crashes on me on open now and I'd like to see if its any different with .39. I'll try to give this a whirl then.
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
fortunz said:
I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
well that bar has been designed to be a zoom bar. you can do whatever you want with it but always a zoom bar remains using it as a "virtual button" is possible but on the phone you will always have the magnifying glasses printed
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)
LinoX said:
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)
Click to expand...
Click to collapse
All I suggest is flexibility. I'm not trying to steal your zoom
fortunz said:
All I suggest is flexibility. I'm not trying to steal your zoom
Click to expand...
Click to collapse
All you are actually suggesting is complexity, indeed. A "soft" array button must be handled properly by the kernel / os / applications and it is a lot more than "one hack" for a function that will be probably not used because the zoom is a bit more important than a button
I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.
It's "controversial" because you are asking for a strip of capacitive touch to turn into buttons. As the OP indicated, implementing this requires not only a new kernel+touch, but files in system.ext2, so the system _thinks_ you have p2z when you still have a resistive screen. So what you are asking for is to make that "flexible" when the base feature has barely been coded+tested.
If you truly want capacitive soft buttons, look at the DIAM or RAPH. Back way then (2.0ish), the LED on the bottom button-panel/scroll would light up on finger contact (not pressed) when running xdandroid. It was more of a "wow it's cool" thing because it was a strip of capacitive touch with 5+ LEDs. I don't remember if the p2z worked with the center scrolly or not...
-- Starfox
fortunz said:
I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.
Click to expand...
Click to collapse
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!
arrrghhh said:
Alright, settle down children.
Click to expand...
Click to collapse
Bu... but... even with the bold starfox still couldn't get it Nevertheless, I am reaching out for my zen.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
Fair enough. I was just trying to avoid any potential "now or never" deadline issues.
arrrghhh said:
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!
Click to expand...
Click to collapse
Yeah, after I got the .39 kernel, it took me like 30 minutes to get it working for the first time, and then a bit more time to clean up the code to look nicer.
Whereas I'd spent hours banging my head on the wall with .27, never quite sure where the problem was, since I thought I was sending all the right events in the driver. Now I know I was sending the right events (because it works in .39) which means that the problem must have been something in the kernel not passing along the multitouch sync events (I know it's that event missing from debugging the userland). That narrows things down quite a lot, but I don't think I really want to go back and spend the time fixing things up in the obsolete .27 kernel though.
Awesome work Manekineko!
I think the zoom bar code will be a fun addition to future cooks. It will be fun to see what uses people come up with. Be it soft buttons or just a zoom bar. Either way, cool stuff.
There never is and will never be a "now or never" with Android. If you want a feature and it can be coded, take the source and run with it. You may run into walls, and there will be many, but at least you can try - that's the beauty of open source.
-- Starfox
fortunz said:
I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Click to expand...
Click to collapse
Yes it does
fortunz said:
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
Thanks for the suggestion. I'm not going to be implementing it at this time, but the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
When I was fighting with getting .27 working, I considered at one point simply turning the zoom bar into soft buttons. However, I was never able to come up with a practical use for soft buttons on the zoom bar. The thing that makes it hard is that the list of keyevents Android understand are extremely limited.
You can see for yourself here:
http://developer.android.com/reference/android/view/KeyEvent.html
Set the filter level to API level 8 to see what's available on Froyo. Unfortunately, really useful keyevents like button zoom in/out only became available in Honeycomb (API level 11).
I'm not sure that soft buttons for things like home or power or search would be very convenient when they're not visible on the physical device, are right next to the screen, and could instantly rip you out of what you're doing.
Just in case anyone happens across this that is interested in doing so, here is how you'd probably want to do it:
Android's KeyInputQueue.java, which handles inputs from the touchscreen (and everything else). Do a search for readVirtualKeys and see that it reads from /sys/board_properties/virtualkeys.tssc_manager. Edit the driver so that it generates the virtualkeys file in the format specified in KeyInputQueue, and disable all of the topaz/rhodium zoom bar code.
manekineko said:
the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
Click to expand...
Click to collapse
Flexible structure is really the only thing I was after. Glad it was already in the plan. And thanks for laying out some possible paths to additional features as well.
Thanks button activated! Great work!
whoops thanked fortunz accidentally -1 buddy
If anybody could find an app that supports touch pressure on a regular kernel on XDAndroid, that would be really helpful. I need to check how much we support pressure to start with and make sure that still is the case with this patch.
I tried Crayon Doodle Lite from the Market, which claims to support pressure, but I'm not seeing any pressure on a regular no-zoom-bar build, so that's not working as a test. Or it may simply be the case that pressure touch has always been broken.
arrrghhh said:
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
+1
Developing in a way that MAYBE, ONE DAY, SOMEONE, WILL (or just will not) adds unuseful complexity to every software.
BTW: Great work manekineko
Good job, but....
Broke my internet (is zoom tested with gprs or is it CDMA only ?)
Kernel.39+RIL2+F22 is running fine on my R100. After drop in of the Zoom-zImage, connection died.
Without zoom with working connection (SMS error is my operator NOT android):
k39_no_sms_log(537).txt
Zoom added - go to line 552
k39-zoom_no_data(552).txt
http://hemorrdroids.net/htc-one-x-review/
Hope it helps people make a decision on whether to get the device or not.
Maybe a stupid question... but why not just add to the existing reviews thread rather than create a new one?
DamoElDiablo said:
Maybe a stupid question... but why not just add to the existing reviews thread rather than create a new one?
Click to expand...
Click to collapse
Not a stupid question at all, I'll bare that in mind next time.
Great review. Of all the things discussed in your review and on the forum the only one that concerns me is battery life. It seems to be getting better but using the same apps the same way I did with my SGS2 I'm getting about 30% less battery life and that's with a larger battery.
I know skins like Sense are a hot button on XDA but as SoC power rises the the performance drain is becoming less of an issue. My personal view is that I use my phone to get things done. Having a phone that's faster than everyone elses in benchmarks is secondary. I've been using Sense 4.0 for a week and I've really come to admire the work HTC's done with it. Here's some examples of subtle things they've done to improve productivity.
- The productivity lock screen is brilliant. The ability to see incoming notifications (and scroll through them) without having to unlock the phone is a great idea. As is being able to go directly to them via the ring.
- When sending a rejection text to an ignored incoming caller, Sense creates a task to remind you to call them back.
- Integrating third party music players in to the Music Hub and displaying them full sceen on the lock screen so you can control them is also a nice feature.
There are some faults too.
- No voice dialer to enable BT calling. Seriously?
- No LinkedIn connector for the FriendStream. Come on, it's 2012 and they just IPO'd.
xdaman85 said:
http://hemorrdroids.net/htc-one-x-review/
Hope it helps people make a decision on whether to get the device or not.
Click to expand...
Click to collapse
xdaman,
Great review for the HOX. The night photos are not great and the last one wasn't in-focus. I think HTC needs to fine tune the night settings for better performance. What firmware are you running on the tested HOX? Did you have any screen flickering? Any of the common bugs?
Thanks.