Related
"RC33JF" vs. cupcake - does cupcake have multitouch built in?
I expect some are going to jump on me for asking a dumb question, but a search on this site, which I consider the finest knowledge base around on this topic, yielded mostly conversations around the fact that cupcake will support multitouch, but they don't mention if it is turned on out of the box. In other words, would we need Luke/JF's patch work as we did with RC30 for multitouch to work, or would it just work as it should.
With RC33 out and my confidence in JF that there will be a "RC33JF out within a week" and what appears to be a MUCH more usable cupcake image (as of 2/2, anyway), I am thinking hard about if I'd give up RC33 and Maps, Gmail, etc. and just use AndNav, K9, etc. and APK repositories to survive to get my A2DP bluetooth and full time virtual keyboard, and cupcake is looking more and more promising...
first off, multitouch only works in the browser. Im not sure if the current browser would work with the cupcake firmware. If it does then you could just push it to the phone using adb.
JF or LucidREM can one of you please please please make this image without the multi-touch hack in it. You don't know how much i would appreciate it and probably others. Its too weird to have it throughout the OS and there aren't any apps that can utilize it.
I have no use for the multi and don't like the quirky issues that come with it.
Again please please please and thank you! Your work IS appreciated greatly!
you are incorrect multi-touch effects apps other than the browser in 1.41
It may cause problems but it doesnt work properly. The app would have to be coded to work with the hack. I dont know of any apps that have been coded to work with this hack.
It's off by default. Just go into your browser settings and uncheck what you checked in the first place.
I don't know much about it (multi-touch) but if it's built into the OS and (allegedly?) leads to some quirks here and there (does it?) I don't understand how you can turn it off from the browser...
I'm sure there are a lot of us who don't care about multi-touch at this point, so I would agree with the OP that it would be nice to have the option of a modified RC33 *without* multi-touch.
I would like to add my request as well.
Its off by default in the browser but the kernel is still hacked to sense multi-touch which causes issues with certain apps. This is because the hack uses an existing field to sense the 2nd finger. So apps that actually use that field for legitimate purposes don't work correctly.
Pls add me to the requests for a no-multi-touch version.
It is my understanding that you can turn auto rotate on and off in the browser, but not multi-touch.
there are the highest chances that multi-touch wont be included in cupcake..that is in the original unmodified update..
kernel is still hacked to sense multi-touch which causes issues with certain apps
Click to expand...
Click to collapse
Which apps are having issues? Somebody mentioned Steamy Windows in another thread... what other apps are having issues. I like the auto-rotate/multi-touch functionality in that order.
aukicadeso said:
Which apps are having issues? Somebody mentioned Steamy Windows in another thread... what other apps are having issues. I like the auto-rotate/multi-touch functionality in that order.
Click to expand...
Click to collapse
I was having issues where my home screen would skip back and forth. I also had issues clicking the proper menu options/icons.
So yeah count my vote in too.
justanothercrowd said:
JF or LucidREM can one of you please please please make this image without the multi-touch hack in it. You don't know how much i would appreciate it and probably others. Its too weird to have it throughout the OS and there aren't any apps that can utilize it.
I have no use for the multi and don't like the quirky issues that come with it.
Again please please please and thank you! Your work IS appreciated greatly!
Click to expand...
Click to collapse
OMG, how many threads are you going to post this in? I've counted about 4. If your steamy windows app doesn't work on JF v1.41, go back to non-rooted. I took a look at your past 15 posts, and it all relates to the multi-touch. Version 1.31 didn't have it, you could use that...
/rant
Honestly, beggars can't be choosers.
If JF chooses to not implement this, I think it'd be a step back. You are all welcome to go back to 1.31 or even use the nonrooted version... or better yet, come out with your own version of root.
But, ultimately it's up to JF, and I really hope he doesn't waste his time making two separate versions of 1.33. Ofc, if you really want him to listen to you, don't be a beggar, and be a supporter.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=1014600
If JF doesn't do it, someone else probably will... which is perfectly fine. Nobody is knocking JF if he won't do this.
I think people are just asking (kindly, I don't see anyone being a jerk about it honestly) for a "vanilla" RC33... As in, exactly as it came from Google except WITH root access added back in. No extra stuff, no recompiled kernel, no extra modules, nothing but root access added back in.
All of my posts are about it because it is the biggest issue with people in the 1.41 build.
The stock RAW image viewer does not work properly either...or cracked screen app....just becasue the apps that take advantage of the second field arent great right now doesnt mean that this isn't an issue. It could end up being a big issue since most dev's don't develop for hacked ROMS.
And for your info I have been running 1.31 for the past few days. I just don't want to see this hack pigeon hole users into not being able to use certain apps. I would like to be able to take advantage of future releases without having multi-touch.
Currently it is only a benefit in the browser and the stock zoom works much smoother, and in the rest of the OS it is a bother.
I will continue to voice my concern and it appears that quite a few others have the same concern.
justanothercrowd said:
All of my posts are about it because it is the biggest issue with people in the 1.41 build.
The stock RAW image viewer does not work properly either...or cracked screen app....just becasue the apps that take advantage of the second field arent great right now doesnt mean that this isn't an issue. It could end up being a big issue since most dev's don't develop for hacked ROMS.
And for your info I have been running 1.31 for the past few days. I just don't want to see this hack pigeon hole users into not being able to use certain apps. I would like to be able to take advantage of future releases without having multi-touch.
Currently it is only a benefit in the browser and the stock zoom works much smoother, and in the rest of the OS it is a bother.
I will continue to voice my concern and it appears that quite a few others have the same concern.
Click to expand...
Click to collapse
Feel free to ask all you want. I think it might fall on deaf ears. The point I was trying to make, is that it's not necessary to post in 4-5 different threads. I think one thread would be sufficient enough...
I agree with justanothercrowd. I'm all for the multi-touch hack, but the fact that its using an existing documented field is an issue.
I believe if you search the threads JF has already answered this question or it has been at least brought up. The only problem that was really brought to light was the steamy app. Really I think this would be a huge hassle for JF who works for free to have to update two versions every time an update is to come out maybe a simple setting to turn it off would be easier and more likely.
a setting would be great. and im more than willing to contribute $$$ for the extra time spent. i would recompile my own but im not that savvy with the android platform yet.
any feedback jf?
Updates (twitter.com/TwistedUmbrella):
Remix Re-established Concept:
http://code.google.com/p/cupcake-frosting/
You can find previous updates and info there
Update 2: http://www.megaupload.com/?d=CTGCPR4
Excellent idea! I was hoping someone would do this.
I'll load it up this morning and let you know if I see any issues!
Ahhh perfect, I was poking around to see what I would need to do to bring the multitouch browser to H (I already have the Voice Search and Dialer) and I find this. Thank's dude.
Hmmmm sounds tempting, but how does the speed compare to adp hr3?
diaztradeinc said:
Hmmmm sounds tempting, but how does the speed compare to adp hr3?
Click to expand...
Click to collapse
Not 100% sure, but this loads faster on mine. I "overclock" to slow to save battery haha but I didn't notice a difference running hr3. I've been going back and forth trying to get what I need. The blue lock screen overlay is actually the MAIN reason I am doing this. Stupid, huh?
Key factor may be that I DID update the radio.
I did leave out superuser, spare parts, and anything else that can be installed normally for those who don't want them. I change my mind about apps hourly so I try to keep default installs as clean as possible to avoid troublesome adb commands.
This sounds very intersting. Does it include the Exchange integration from the 5.0H build?
This is EXACTLY what I've been waiting for... soon as you get locked down which apps ur keeping, I'm on it.
Sounds great twisted. I'm in love with 5.0.2H because of the mail app and pdfviewer. Yesterday I stepped up to ADP1.5 and although it was fast, it's missing these key components that I use daily. I look forward to you app log.
This is really interesting. I can't wait to hear(read) thee results. Lol
vettejock99 said:
This sounds very intersting. Does it include the Exchange integration from the 5.0H build?
Click to expand...
Click to collapse
It currently has the 5.0.2 exchange. I saw no point in taking it out. I don't use it but I know it's far easier to remove system components like that than it is to implement them once an update is installed.
So far I see no real difference in Gmail. Mail seems to crash for me in 1.5 with something about a Plus account - looks like 5.0.2 mail stays. Maps and Market will be updated because I see no reason not to.
Any thoughts on Gmail? Anyone see any updates worth having?
Can you put the H build camera in the build instead of the 1.5.3 camera? The HTC camera was far superior than the google implementation. That's all I can think of so far
ala380 said:
Can you put the H build camera in the build instead of the 1.5.3 camera? The HTC camera was far superior than the google implementation. That's all I can think of so far
Click to expand...
Click to collapse
H camera crashed when using the camera button. The one I'm using is the one from the "add features to 5.0.xH" thread. Seems to be the most stable and all you really lose is zoom. Forgot to take out additional HTCAlbum, though. Planning to fix this and some other updates when I get back to my hideout. If I can remap the H camera button I will get that in there, but that takes a little longer than just swapping apks.
a2sd
is this version an as2d version?
jamesbui12 said:
is this version an as2d version?
Click to expand...
Click to collapse
Please allow me time to obtain all the information I need (and the conmplimentary copy of Paragon) before I begin posting parallel versions for those of you that require a2sd. Until then I am taking the advice of a pm and adding in the black vk. It is "slick"
Please feel free to follow me on twitter at the same name. Much as I have followed the trend of making one for such an endeavor.
Please excuse the fact that I edit my posts almost immediately. I view them from my G1 and while the logic may be flawed, I find them cleaner when words do not hang loosely into additional lines.
twistedumbrella said:
5.0.2hr5a-twisted:
Items From 5.0.2:
Messaging
Calendar
Contacts
Youtube (Temporarily)
Mail, Music, and Gmail
Widget Interface
Chinese Keyboard
Items From 1.5.3:
Multitouch Browser
VoiceSearch
VoiceDialer
Google Sync
Android Keyboard
Updated Camera
Updated Settings
Updated System
Updated Market
Updated Maps
This was for those, like me, that liked the original look and feel of the Haykuro 5 series builds and didn't want to miss out on the new features of the 1.5 series builds. My own firmware is very custom so no screenshots currently.
http://sharebee.com/1965e7ad
http://sharebee.com/c4919794
Please let me know if you test this and find any bugs. I know altering updates MAY cause items to crash when installed. I will fix them ASAP.
Currently in the process of checking out Dude's Cupcake to see if anything in there might improve the build.
Click to expand...
Click to collapse
any chance you could add the launcher in from here? http://forum.xda-developers.com/showthread.php?t=507244 Or does this now not have the problem when you slide out the keybord? Because im currently running an old version of this rom i think? I had to install G keybord my self so.. Almost deff :L lol, Oh dont meen to be fussy but ayway you you edit the title of the thread whenever you update? only this seems a very intrsting build as i tooo love the HTC look and dont wanna loose the feel exactly cheers for your work dude
everything seems to work. not seeing the multi-touch...suppose to be there right. not a big deal, just testing out the version.
How is this going?
Still developing the build?
Looks great, and appears to fit me perfectly!
However, what is the difference between the two builds that you link to in your first post?
Is the 5.0.2hr5-twisted.zip the normal version, while the 5.0.2hr5a-twisted.zip is the Apps2SD version?
Zappza said:
How is this going?
Still developing the build?
Looks great, and appears to fit me perfectly!
However, what is the difference between the two builds that you link to in your first post?
Is the 5.0.2hr5-twisted.zip the normal version, while the 5.0.2hr5a-twisted.zip is the Apps2SD version?
Click to expand...
Click to collapse
Sorry apps2sd is still coming. Having technical difficulties with getting both my G1 and computer to recognize the same partitions. The new version has the Andreoid keyboard included along with updates to youtube, maps, and market. The slider problem still exists for a day or two. Wanted to get the new market in place because I isolated the market download issue to have been cooperation between market and launcher. Now that the new market accepts downloads I can fix launcher. Expect updates tomorrow. I have a 4-hour block of boredom. Hehe.
jleake said:
everything seems to work. not seeing the multi-touch...suppose to be there right. not a big deal, just testing out the version.
Click to expand...
Click to collapse
Still isolating libs and such. JesusFreke redid the kernel so the program alone was not enough. Didn't think that far ahead when I was throwing parts together. I'm learning as I tear apart the 7 builds on my desktop. I just have to teach myself as I go.
Open source never meant well-documented.
Plans are in the works to go backwards from the HTC build, but like most others I need something to default back to when I'm not testing. Building this version was first priority with that being my next step. That is when the speed increases will occur with some new features. Can't say I'm not a dreamer, right?
twistedumbrella said:
Sorry apps2sd is still coming. Having technical difficulties with getting both my G1 and computer to recognize the same partitions. The new version has the Andreoid keyboard included along with updates to youtube, maps, and market. The slider problem still exists for a day or two. Wanted to get the new market in place because I isolated the market download issue to have been cooperation between market and launcher. Now that the new market accepts downloads I can fix launcher. Expect updates tomorrow. I have a 4-hour block of boredom. Hehe.
Click to expand...
Click to collapse
Beautiful!
I love your work!
Before you flash:
understand the risks, ideally have flashed roms before, have hspl and spl 3.7, maybe not ideal for people who use it daily as a first or only device due to possibilities of things not working straight out of the box.
New Download:
http://www.sendspace.com/file/tqivt9[/url]
A lot of changes addressed, I believe there may still be issues with the camera though
***Please note this is a test build(not Tested) do not complain if you brick your device, I welcome feedback good or bad but please respect the amount of time it takes me to cook these ROMS, if something doesnt work be patient as I have a full time job and a family that come first***
hey guys come on you don't want a wm6.5 rom with latest build??
hurryyyy
saied 1 said:
hey guys come on you don't want a wm6.5 rom with latest build??
hurryyyy
Click to expand...
Click to collapse
If there is no interest I will still build one for you 2 to test, and we can see where we go from there. Hopefully have something for you for tonight or tomorrow depending if I can sort out the problems with my kitchen
Hello I would be a tester but the problem is I don't have a original WM6.1 Dutch rom so I can't reverse to original if i want to.
I heard HTC wil come with an update when this happens it is possible for me to test roms till then i will stick to the original rom.
got experience of rom flashing with wizzard, Iphone and a MIO A701.
greetings
Oebele63
Maybe I Can be a backup tester
I plan to flash in the next few days, but I'm not experienced with this. But I have read up on the subject for some time now so I've read about the things which go wrong from time to time and I'm aware of the risks. Be glad to help out though, i'm sick of my beloved x7510 being so sluggish
I will be your tester. Hope your rom work well
Just flash your lastest build rom. Your Roms is not for X7510. The flash errors occurs
thanhlonely said:
Just flash your lastest build rom. Your Roms is not for X7510. The flash errors occurs
Click to expand...
Click to collapse
thats because you have flashed the clearly marked for x7500 not x7510, i will be cooking an x7510 build tnight or tomorrow and releasing to the people who expressed interest in beta testing, either you have misread my post here or not understood and i would advise you to wait for a release or your device
avengerpenguin said:
thats because you have flashed the clearly marked for x7500 not x7510, i will be cooking an x7510 build tnight or tomorrow and releasing to the people who expressed interest in beta testing, either you have misread my post here or not understood and i would advise you to wait for a release or your device
Click to expand...
Click to collapse
Heck yes I still want the ROM!! I'm always interested and once we work out the bugs, I'm sure everyone will be on board. I'm willing to help out wherever I can with this and if it means walking me through the kitchen and creating the .nbh then I'm game still.
Just my two cents...lol
will try and put a beta together when i get home from work probably be around 1am gmt, will pm download link to beta testers and update here and twitter when its up
Its done Beta1.01, links to download sent to selected beta testers, please do not publicly post download link until tested fully and I release a version for general release, feel free to post feedback here.
BETA testers, make sure you are on SPL3.5!!!!!
Try out as much as you can and then report back any issues etc, please try not to request things that are available via cab install as its not worth me installing specific software etc at the cost of module space in the native kernel. This rom should be very quick due to modifications to the space used in slot 0 of the native 6.1 memory kernel(0 modules). Also please be aware that some issues may be down to me using a leaked beta from MS and I may not be able to change some things.
avengerpenguin said:
Its done Beta1.01, links to download sent to selected beta testers, please do not publicly post download link until tested fully and I release a version for general release, feel free to post feedback here.
Click to expand...
Click to collapse
I didn't receive any links to download Beta1.01. So you didn't choose me, did you?
avengerpenguin said:
Its done Beta1.01, links to download sent to selected beta testers, please do not publicly post download link until tested fully and I release a version for general release, feel free to post feedback here.
Click to expand...
Click to collapse
6.5 Beta Issues:
1. The memory allocation sucks badly. Only 30mb left for program memory. This is a problem for running other programs or simutanious ones. There also appears to be a memory leak because the memory is going down slowly. A soft reset takes care of this for a little time.
2. Audible manager does not work. My personal feeling is take it out, never use it anyway.
3. Some of the icons do not render well. I would be more than happy to create a couple for you to insert in there place: Comm Manager, Clear Storage, Backlight and others. Not smooth on the edges.
4. G sensor works well, but again, not really a use for it. I would add it as an extra .cab to install for an additional cab package.
5. Real VGA - Another personal preference. Although I don't mind it being there.
6. VueFlo - Really? Wow, haven't seen that in a while and haven't tried it yet.
7. The Calculator wants to be in portrait mode at all times. Not a big issue, but I usually never use my device in portrait mode.
8. The ROM is fast, actually blazin fast for 6.5. I'm still trying to get use to the bottom bar but I do believe I'm stuck on 6.5 now. Very stable rom and runs without any hiccups.
9. SMS text received. When you click on notification and it opens the sms, it doesn't mark it as read. You have to click on it or scroll up onto it with the arrow keys for it to appear read and then no new messages waiting to be read.
10. The dialer....strange. I don't know if you have added a new one or if it is a component of the new 6.5. It does not render properly in portrait mode and the names/numbers on the left of the dial pad is very annoying. You cannot read the full name of the contact that comes up. The dial pad is not all the way on the screen. You can see the right numbers are a little off the screen.
11. Quickmenu - Don't understand why that was incorporated. The x doesn't close even though quickmenu is set up to close it.
12. While in the sms/text screen to read or create a text, when the phone rings, the caller id does not pop up. That is a bad one for me. I like to see who is calling before I answer...lol.
13. The Comm Manager isn't the normal one. I understand the quickness of it, but I prefer the original style. No issues with bluetooth or connection to the internet via media net.
I do believe that is it right now. I would literally call it a RC version. You did a great job, but like I said, the memory consumption is to much/great to be used heavily. I'll look forward to your next release.
New Release post 1, changes
Just about right said:
6.5 Beta Issues:
1. The memory allocation sucks badly. Only 30mb left for program memory. This is a problem for running other programs or simutanious ones. There also appears to be a memory leak because the memory is going down slowly. A soft reset takes care of this for a little time.
Hopefully this release will be better have removed a lot of unused packages
2. Audible manager does not work. My personal feeling is take it out, never use it anyway.
Removed
3. Some of the icons do not render well. I would be more than happy to create a couple for you to insert in there place: Comm Manager, Clear Storage, Backlight and others. Not smooth on the edges.
I dont do graphics so any help would be appriciated
4. G sensor works well, but again, not really a use for it. I would add it as an extra .cab to install for an additional cab package.
This has been left in unless I get more requests for removal as I do not have a cab
5. Real VGA - Another personal preference. Although I don't mind it being there.
This has been left in unless I get more requests for removal as I do not have a cab
6. VueFlo - Really? Wow, haven't seen that in a while and haven't tried it yet.
This in the dump from the original rom, I will remove at some point but involves digging into OEM files, will do this when closer to full release
7. The Calculator wants to be in portrait mode at all times. Not a big issue, but I usually never use my device in portrait mode.
Think I removed this calc but not sure now
8. The ROM is fast, actually blazin fast for 6.5. I'm still trying to get use to the bottom bar but I do believe I'm stuck on 6.5 now. Very stable rom and runs without any hiccups.
I recmod a lot of modules meaning that memory slot0 has zero modules in leaving it free for just the device kernel
9. SMS text received. When you click on notification and it opens the sms, it doesn't mark it as read. You have to click on it or scroll up onto it with the arrow keys for it to appear read and then no new messages waiting to be read.
Maybe a feature of 6.5 **not addressed in this build**
10. The dialer....strange. I don't know if you have added a new one or if it is a component of the new 6.5. It does not render properly in portrait mode and the names/numbers on the left of the dial pad is very annoying. You cannot read the full name of the contact that comes up. The dial pad is not all the way on the screen. You can see the right numbers are a little off the screen.
**possibly due to the build having the bigger bottom taskbar, cant remember if I included advanced config, if I did disable the phone skin, if not search for advanced config and disable**
11. Quickmenu - Don't understand why that was incorporated. The x doesn't close even though quickmenu is set up to close it.
**Removed I think**
12. While in the sms/text screen to read or create a text, when the phone rings, the caller id does not pop up. That is a bad one for me. I like to see who is calling before I answer...lol.
**Not address yet, but may be fixed through other changes, please report back**
13. The Comm Manager isn't the normal one. I understand the quickness of it, but I prefer the original style. No issues with bluetooth or connection to the internet via media net.
**Removed, back to original**
I do believe that is it right now. I would literally call it a RC version. You did a great job, but like I said, the memory consumption is to much/great to be used heavily. I'll look forward to your next release.
Click to expand...
Click to collapse
Please note changes to feedback received
I appreciate the fixes and await the release for download and install. I did do some research and the 0409 and other res are an integral part of the new 6.5. I found this weird because of the consumption it takes up in windows, but what do you do. Let me know what size icons you need and I'll fix the ones up and shoot them over to you. If it comes down to it, I'll strip the original and replace it with a doctored up one.
Just about right said:
I appreciate the fixes and await the release for download and install. I did do some research and the 0409 and other res are an integral part of the new 6.5. I found this weird because of the consumption it takes up in windows, but what do you do. Let me know what size icons you need and I'll fix the ones up and shoot them over to you. If it comes down to it, I'll strip the original and replace it with a doctored up one.
Click to expand...
Click to collapse
Download was added to first post last night
No-one tried it?
Hi Mate,
I'm downloading now and wil let you know in a few days how I got on. Thanks for the ROM (beta or not, this is progress!)
NanoRuler said:
Hi Mate,
I'm downloading now and wil let you know in a few days how I got on. Thanks for the ROM (beta or not, this is progress!)
Click to expand...
Click to collapse
If you could let me know if it boots etc as I dont have an x7510 to test with, many thanks
***Over the last 2 months, I have been through more issues with T-Mobile then just the issues from the software side. I have spent the majority of that time working with them to try and fix a data connectivity issue I was having. After hard resets, ROM update, and then a site survey, T-Mobile found that the area where I live does NOT have adequate enough coverage to competently supply data coverage to my phone. Notes from the tech said that towers were noted as needed but NO BUDGET was available to deploy a new tower in the area. Because of this, the account rep I spoke to immediately offered a full refund on my unsubsidized HD2 and a refund for all services rendered to-date, including accessories for the phone. As of last night, I left T-Mobile and joined AT&T with a 32gb iPhone in preperation for the upcoming 4G. I'll either trade it in if within 30 days, or give 3GS to wife and get a 4HD on a second line. I have been a Windows Mobile user for YEARS. I still love the HD2 and would never have gotten rid of it, except for the fact I know that AT&T's Edge bands are going away to make room for 3G, and I don't want issues of trying to run HD2 on AT&T's network. I want to stress how much I LOVED the HD2. To me, the phone had a lot of improvement needed, but for what MS and HTC had to work with, it was the best Windows Mobile phone to-date, IMHO. That being said, I have lots of friends with the iPhone, our company exclusively carries it, so I also got a nice discount. I've used one from a distance several times, but never really had one that was mine to really dig into. So far, I am REALLY happy with the phone. I'll jailbreak it and start tweaking it, just like I have my Windows Mobile phones for years, but it's something new for me to play with. =) So, with that being said, I am going to retire from this thread and anybody is more then welcome to take it over. Nibbley15 might be able to do this. I'm still need to get him setup with some software issues he was having, but baby and family haven't left me with a lot of time. Nibbley15, I haven't forgot about you, I just haven't been home to get things configured yet. I'll be in touch soon.
Thanks! ZIMMAY!***
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
I have finished making a CAB. Use at your own risk. I played guine pig and did this myself with no ill effects.
Here are the reg keys that are changed:
Settings from HD2Tweak:
[HKEY_LOCAL_MACHINE\Drivers\TouchPanel]
"PressureThreshold"=dword:000162f2
This is the setting that seems to help the most with being able to click/touch items on screen, especially the corners:[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
Settings from HD2Tweak:
[HKEY_LOCAL_MACHINE\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
"SpeedHigh"=dword:00000000
"SpeedLow"=dword:0000000e
I am still curious what the other settings that Nibbley15 found and how they relate.
***Update 5/21: Added cab to enable Screen options in System Settings to do a screen calibration.
***UPdate 5/22: Reg entry for new CAB is as follows:
[HKEY_LOCAL_MACHINE\\ControlPanel\Pen]
"Hide"=dword:00000000
zim2323 said:
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
Below is what I found to work for me, better then anything I've tried so far. I will be the first to warn you that I have NO IDEA what I'm really doing in relation to TouchResponse, but I do have a good understanding of the registry. The values I've applied may really be nothing more then a happy thought in my head. Though I seem to be able to actually use the close/ok buttons in the upper right part of the screen.
I can make a CAB later, but these are the settings I adjusted my settings to.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
I'd like to see if others could test and post what your experience is. Even better, we may get some help from the chef's to confirm, deny, correct, extrapolate, etc, etc, to find a better fix.
***Edit: Forgot to mention. While the bottom 2 did help, the first FingerThreshold settings seemed to be what made the real difference for being able to competently hit buttons without feeling like I was jackhammering the phone. =)
Thanks!
Click to expand...
Click to collapse
I would have to say that there would be a way to adjust the touchscreen on 2.13 as 2.10 does not have those registries...Well I'll give it a try when I upgrade to 2.13.
Thanks
secano said:
I would have to say that there would be a way to adjust the touchscreen on 2.13 as 2.10 does not have those registries...Well I'll give it a try when I upgrade to 2.13.
Thanks
Click to expand...
Click to collapse
Thanks. Personally I'm running these exact reg and it's working a million times better. But like I said, could be in my head. The only other things I changed sensitivity wise is the scrolling affects that HD2Tweak has. I'll be adding those to whatever I CAB up for a complete fix. I used SKTracker to find out which reg entries changed.
Yes,
Thanks! Please keep the ideas flowing here. Thanks to all that are working this!
I'm posting this reply for folks that are using the 2.13 STOCK ROM and you may want to know the original settings to revert back too or other places to look for you REG peeps to look at.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031 STOCK SETTING
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
STOCK 2.13 version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
STOCK 2.13 version doesn't have this key
Did find these keys:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 20
"FingerThreshold"=dword:31 (0X00001F) <- NOTE:
"NoiseThreshold" = dword: 20
NOTE: if you change the key[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel] to "FingerThreshold"=dword:0
then this value will change to 20, hmmmm.
Other notes: I think that BaseThreshold is where it starts?
I think that the Fingerthreshold here is where it all starts from after learning?
I think that the NoiseThreshold is the amount of "noise" from your fingertouch is allowed before it recognizes before it knows your finger is really touching the screen?
2nd half of post: I'm posting this for folks that may want to know what was in the 2.10.1 STOCK ROM:
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
STOCK 2.10.1 version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
STOCK 2.10.1 version doesn't have this key
Did find these keys:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 0
"FingerThreshold"=dword: 20 (0X000014) <- NOTE: now this is interresting
"NoiseThreshold" = dword: 20
This is what I recommend folks to change their 2.13 Builds to match the 2.10.1 Build for Touch Response.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 0
"FingerThreshold"=dword: 20 (0X000014) <- NOTE: this may change automatically on you from the above change (Setting\TouchPanel)
"NoiseThreshold" = dword: 20
i'm a newbie!!!!
can anyone tell me how cani get to those registry or what kind of program that i need to see the registry? do i need to connect with the computer to see it and change it?
ipsaa said:
i'm a newbie!!!!
can anyone tell me how cani get to those registry or what kind of program that i need to see the registry? do i need to connect with the computer to see it and change it?
Click to expand...
Click to collapse
Hello,
I will try to put this simply, please do not mess with your registry unless you know what you are doing it can crash your phone. When we finally find the fix for this, a cab file will follow shortly. The cab file will do the work for you and you don't have to worry about killing your phone.
If you really really really want to try then please search the threads and there you will find your answers.
Please refer to post #5
zim2323 said:
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
Below is what I found to work for me, better then anything I've tried so far. I will be the first to warn you that I have NO IDEA what I'm really doing in relation to TouchResponse, but I do have a good understanding of the registry. The values I've applied may really be nothing more then a happy thought in my head. Though I seem to be able to actually use the close/ok buttons in the upper right part of the screen.
I can make a CAB later, but these are the settings I adjusted my settings to.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
I'd like to see if others could test and post what your experience is. Even better, we may get some help from the chef's to confirm, deny, correct, extrapolate, etc, etc, to find a better fix.
***Edit: Forgot to mention. While the bottom 2 did help, the first FingerThreshold settings seemed to be what made the real difference for being able to competently hit buttons without feeling like I was jackhammering the phone. =)
Thanks!
Click to expand...
Click to collapse
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
mmeyer4663 said:
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
Click to expand...
Click to collapse
I just tweaked the ones that I posted (to a 21903 2.13 BASE build);
I did not add those other 2 registry keys and it is a great improvement;
still testing myself.
Nibbley15 said:
I just tweaked the ones that I posted (to a 21903 2.13 BASE build);
I did not add those other 2 registry keys and it is a great improvement;
still testing myself.
Click to expand...
Click to collapse
Interesting. I do not see the last two entries in my reg.
I guess the difference is, the HTC version for TMO HD2 leaked last week is 21892.
Nibbley15 said:
I'm posting this reply for folks that may be using 6.5.X and not know the original settings to revert back too or other places to look for you REG peeps to look at.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
6.5.X version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
6.5.X version doesn't have this key
Did find this key:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\]
"FingerThreshold"=dword:31 (0X00001F)
[HKEY_LOCAL_MACHINE\\HARDWARE\SETTING\TOUCHPANEL]
"FingerThreshold"=dword:31 (0X00001F)
some others worth looking at possibly:
[HKEY_LOCAL_MACHINE\\SOFTWARE\HTC\TouchGL]
"DBCLKFingerDistance"=dword:45
"DBCLKFingerInterval"=dword:350
Click to expand...
Click to collapse
THANK YOU for posting this info. I hadn't got back to do that yet.
mmeyer4663 said:
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
Click to expand...
Click to collapse
Both of those keys/values were there. Although the one thing I had already installed and run was BSBTweaks and HD2Tweaks. Either of those 2 could have created the values. They seem to actually work, but that's kinda why I was posting, to see what others experience was with it.
mmeyer4663 said:
Interesting. I do not see the last two entries in my reg.
I guess the difference is, the HTC version for TMO HD2 leaked last week is 21892.
Click to expand...
Click to collapse
Just to clarify,
I am using a completely stock build of the new TMobile ROM. Based on the information I've read and that has been posted here, it looks like older ROMs may, or may not have those reg keys/settings implemented depending on the ROM timeline.
For those that have had a chance to try these settings, does it seem to improve things?
The numbers I used were just numbers I kept increasing. I have no idea what the max value is or could be.
I'm hoping tomorrow I'll have a chance to post the reset of the reg tweaks I used from HD2Tweaks that would be apart of the entire TouchResponse "package" that I've been working with.
Also, just in case someone wonders, don't ask for permission, TAKE PERMISSION to use this information however you want. You can say you figured it out and incorporate it into "My Awesome ROM". I really don't care. It's about getting things fixed we don't like, and making them better. I could care less who gets credit. I know for a fact that there are chef's and others out there that know a bazillion times more about this stuff then me. I just like know that I helped, if in fact it really does help.
Peace out!
I only had the first value in my registry:
"[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031"
But I did make the change and it absolutely made a huge difference, for the better.
Thank you for this. I just made the first tweak and things are 100% better. That eliminated my one big gripe about the new stock ROM.
xanderdad said:
I only had the first value in my registry:
"[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031"
But I did make the change and it absolutely made a huge difference, for the better.
Click to expand...
Click to collapse
So maybe that alone is the fix. I included the other keys because they were apart of the HTC Sense settings in HD2Tweak. Those keys may be more for scrolling issues.
Please put out a cab file for this mod. The lack of responsiveness is killing many here. Thanks.
NickPP said:
Please put out a cab file for this mod. The lack of responsiveness is killing many here. Thanks.
Click to expand...
Click to collapse
Well, before I did that I wanted to know exactly what was "fixing" the problem and what exactly those settings were doing or how it may interact or affect other functions of the phone. So far I have had nothin but positive response to this.
I have a little more testing to do and then I will putting out a CAB with all the fixes I apply that are related to making TouchResponse behave like I would expect it to. Expect something in the next 24 hours. In the mean time, you can always use a registry editor and apply the reg values yourself.
I'm dealing with job and a new baby so my time is short. =)
Hello,
Since switching to Android from WinMo I was so badly missing a decent dialer, that I made my own. It enables dialing and fast search through contacts by number or name, and enables search in two different alphabets:
Latin (supports all european latin-based languages) and
One of the following: Greek, Hebrew, Arabic or Cyrillic (Russian, Ukrainian, Bulgarian, Belarusian, Serbian and Macedonian) currently implemented.
For Android 1.5 and above
I'd appreciate to hear your feedback.
Latest version: 3.5.1 (3.1.2 for Android 1.5)
Android Market address: https://market.android.com/details?id=eir.dialer3
If you want to contribute to the translations, you are welcome: http://www.getlocalization.com/eir_fast_dialer/
Full change log, user manual etc. available here: [URL="http://eir3.com]http://eir3.com[/URL]
Looks nice. Does this have any advantages over Dailer One (info here http://www.appbrain.com/app/kz.mek.DialerOne)? They seem pretty similar.
c00ller said:
I was so badly missing a decent dialer, that I made my own. .
Click to expand...
Click to collapse
Just curious: how does it compare (i.e. why is it better) than the other dialers on the market?
Very nice. It looks like the Sense dialer. Thanks
Just installed it, crashed when I hit the number 4.
diastro said:
Just curious: how does it compare (i.e. why is it better) than the other dialers on the market?
Click to expand...
Click to collapse
You can search for contacts by name using two different alphabets at the same time. So if you have contacts written in, for example, both Latin and Cyrillic letters, as I do, this comes quite handy, not to say essential. I wasn't able to find another dialer that does this, please let me know if you know of one.
c00ller said:
Does this have any advantages over Dailer One?
Click to expand...
Click to collapse
Above is the first advantage over Dialer One. The second, which is for me also crucial, is that it runs on 1.6 devices, while Dialer One requires Android 2.1.
Third would be, that Dialer One doesn't seem to handle properly some Latin letters, for example German umlauts - as far as I tested, it wasn't able to find, for example Andreas Köpke by pressing 56. Maybe it's a language setting, but still, if it cannot search using umlauts unless your language is set to German, that is a disadvantage. Fast Dialer searches using an extended set of Latin characters, covering all Latin-based European languages, regardless of what language settings you have.
dEris said:
Just installed it, crashed when I hit the number 4.
Click to expand...
Click to collapse
I would like to examine this. Could you please tell me at least the device you ran it on, what Android version etc. From your signature I assume HTC Droid Eris, which runs Android 2.1?
Don't like the "trial" in the name of attachement. Why it's there? You didn't explained in OP.
1. FC on i5700 spica
2. trial version, and nothing about it...
Force close after touch first digit.
If it's trial, then it is obvious, that you are making paid app. LOL, make working app first, then try to squeeze money out of it xD.
raven_raven said:
LOL, make working app first, then try to squeeze money out of it xD.
Click to expand...
Click to collapse
True.
It's a backwards-compatibility issue. I thought the AVDs did emulate behaviour of an actual device... I'll fix that.
The app does work on 1.6 for anyone willing to try.
Thanks.
Actually I did try it on official 1.6 for my country (my signature is a little bit out of date).
Oh, a new version - 1.1. I'll try it, however now my phone is on CM6, so I can't try it on Donut .
raven_raven said:
Actually I did try it on official 1.6 for my country (my signature is a little bit out of date).
Oh, a new version - 1.1. I'll try it, however now my phone is on CM6, so I can't try it on Donut .
Click to expand...
Click to collapse
Thanks a lot!
I uploaded two new files: 1.6 and 2.1 for the Donut and Eclair/Froyo.
Until I figure out if (and how) it would be possible to build once for both targets.
Let me know how you find the app. That is my main dialer, and for myself, it does the job.
Is it possible to make it so it works on Android 1.5? Old, I know, but my friend uses a Motorola Cliq XT and is stuck on 1.5 for a while until Moto gets their act together
It's not a bad start with this app. But this isn't really a trial but rather a demo with limited functionality. You can't dial a # containing "7" as the app advises you to purchase full version. Posted version is basically unusable. So why posting it in this forum where people are normaly helping each other or sharing things with no commercial intentions? Wrong place for advertising.
On a different note: check out Dialer One and AContacts. These are wonderful apps with a lot of thought and effort put into them.They are free as well. Fair enough, your app has got a unique function (one) but other than that its functionality can't be even compared to that of AContacts or Dialer One. Whole 3 options in settings menu?
c00ller said:
Is it possible to make it so it works on Android 1.5? Old, I know, but my friend uses a Motorola Cliq XT and is stuck on 1.5 for a while until Moto gets their act together
Click to expand...
Click to collapse
I won't be able to do that. It compiles and installs on an 1.5 AVD, but there are some problems with the view generation which I won't have the time to look into.
rubbish said:
It's not a bad start with this app. But this isn't really a trial but rather a demo with limited functionality. You can't dial a # containing "7" as the app advises you to purchase full version. Posted version is basically unusable. So why posting it in this forum where people are normaly helping each other or sharing things with no commercial intentions? Wrong place for advertising.
On a different note: check out Dialer One and AContacts. These are wonderful apps with a lot of thought and effort put into them.They are free as well. Fair enough, your app has got a unique function (one) but other than that its functionality can't be even compared to that of AContacts or Dialer One. Whole 3 options in settings menu?
Click to expand...
Click to collapse
Yes, Dialer One and AContacts are much richer apps. Unfortunately, they lack this small functionality, which I need very much.
And I have a 1.6 phone.
In my opinion, having only 3 options in the menu is an advantage. Best would be zero options.
I was hoping to receive feedback, rather than advertise. And I did, for which I'm grateful. I made this app because I needed it, not because I intended to make a fortune out of it. That's why I find it valuable, and perhaps other people will find it too, and would spare a coin on it, as I would have, had there been such an app available several days ago.
BTW, the files are updated.
does it support Arabic
OK, now app do not FC while pressing a digit (CM6). I really like it, basic, light T9 dialer for Android. It's good, that it has only 3 options. I mean - what to set up in app like that? It has do to a specified task and it's doing it right.
However, two issues was bugging me:
1. I don't like the way contacts number is aligned, it simply do not look good when name is aligned to right, and a number is aligned to right. I think both aligned to right would look better.
2. App isn't so... quick. I mean, try SuperDial (also runs on 1.6, but it is an ugly app). It is instantious, you press a key and there is response, the contacts are showing up. In you application you have to wait a bit of second.
I see potential. There is no that good looking T9 dial app on Android 1.6. DialerOne is fantastic, but it won't run on G1, X10, X10 Mini, LG GT540 etc. Please, do not set the price too high ($0.99 is max IMO).
denteno said:
does it support Arabic
Click to expand...
Click to collapse
It could, if I find out how the Arabic letters should be put on T9. Perhaps you could give me a hint
raven_raven thanks for the advices!
i hope this is what you mean
1= '.,
2= ب ت ة ث
3= ا ء
4= س ش ص ض
5= د ذ ر ز
6= ج ح خ
7= ن ه و ي
8= ف ق ك ل م
9= ط ظ ع غ
denteno said:
i hope this is what you mean
1= '.,
2= ب ت ة ث
3= ا ء
4= س ش ص ض
5= د ذ ر ز
6= ج ح خ
7= ن ه و ي
8= ف ق ك ل م
9= ط ظ ع غ
Click to expand...
Click to collapse
Yes, that's what I meant. I added support for Arabic, perhaps you can try it out and let me know if it works ok.
raven_raven said:
However, two issues was bugging me:
1. I don't like the way contacts number is aligned, it simply do not look good when name is aligned to right, and a number is aligned to right. I think both aligned to right would look better.
2. App isn't so... quick. I mean, try SuperDial (also runs on 1.6, but it is an ugly app). It is instantious, you press a key and there is response, the contacts are showing up. In you application you have to wait a bit of second.
Click to expand...
Click to collapse
I took your advice and changed the alignment of the name.
I also did some optimizations, and the app runs even faster. I didn't figure out how I can measure the startup time of SuperDial, but according to the ActivityManager log, if that is a valid parameter to reference, Fast Dialer is faster than SuperDial. Cold start of SuperDial takes ~500ms, while of Fast Dialer ~430ms. Once in memory, SuperDial takes ~300ms to show up, and Fast Dialer ~180ms.
BTW, good that you mentioned it SuperDial is a nice app, I think it has some very clever decisions, like initially showing the log of calls instead of the contacts, but also some less clever decisions - like no possibility to directly (with one click) call a contact once you found it. The developers say, on their site, that the app is not polished, which is obviously true, since it also has some not-so-minor flaws (like failing to load a newly entered contact), which Fast Dialer handles just fine.
The updated Fast Dialer apk is in the initial message of this thread.
c00ller said:
Is it possible to make it so it works on Android 1.5? Old, I know, but my friend uses a Motorola Cliq XT and is stuck on 1.5 for a while until Moto gets their act together
Click to expand...
Click to collapse
eirh said:
I won't be able to do that. It compiles and installs on an 1.5 AVD, but there are some problems with the view generation which I won't have the time to look into.
Click to expand...
Click to collapse
I take that back. There's a version for 1.5 phones attached to the initial message.