yashsingh1/xdaforums huggingface dataset:
[Nexus One General] flarbear:
I had a similar problem with my G1. It was better some days and worse on others, but it always worked great when I held it in my hand. I haven't seen the problem so far with my N1, though. I just tried it on my wooden desk and also on a plastic surface and it responded to my finger just fine.

Never tried a spoon, though... ;-)
[Nexus One General] cekle:
My MyTouch 3G operated the same way, my first Nexus One did this, and my replacement Nexus One also does this.

I live in southern california where it's dry and hot.
[Nexus One General] lolobabes:
the spoon thing didnt work on me either... ahihihihi
[Nexus One General] windmill_81:
Do the phones you have tried act exactly the same as mine in the video?

As I said before, mine works perfectly, then, once in a while starts getting unresponsive and I cannot understand what triggers this behavior..

I really would prefer it to just always not work so I would just stop using it that way instead of hoping it wont do it.. :o

If I turn the screen off and then on again everything goes back working ok, so I have wondered if this could have been a software generated issue.

At the end I have come to the conclusion that it could only be caused by a slightly imperfect hardware that does not manage to dissipate the phones electrical current which then somehow interferes with the touchscreen.
[HD2 General] Smartmob:
First of all, Hello everyone!

I was reading this forum and about HD2 for 2 months now, and finally i bought it! My first WM mobile but not first smartphone.

All in all I'm very happy with my device, it works perfectly and with any bug or problem, just flawless :)

But, yesterday, early in morning, I dont know why but I shake my phone and i heard veeery quite sound from the inside, very tiny sound like something is shaking. I dont know is that normal or not, is it part of G-sensor or not. Everything works perfect, just wanna know what that sound is. It can be heard only in quite enviroment, its not a problem, just wanna know :)

Thanks all! ;)
[HD2 General] kilrah:
Not G sensor, but vibrating motor most likely. The volume keys can move a tiny bit too making a little sound.
[HD2 General] samsamuel:
there is another thread about this and their conclusion seems to be that it is the camera which is held inside a magnetic cage.
[HD2 General] ardsar:
its the camera - the focusing lens inside the sensor.
[HD2 Windows Mobile 6.5 Themes and Apps] Giles Turner:
Hi

I've just loaded the above application onto my HTC HD2. The main explorer component works as well as ever, but I can't seem to be able to utilize the Resco Today plug in and although the Resco Task Manager appears in the program menu, I can't get it to close applications down in the usual way.

Does anyone know if the above issues are a function of the HTC sence platform, or are they resolvable.

May thanks
[HD2 Windows Mobile 6.5 Themes and Apps] degake:
Mine is fully working (that is: Resco Explorer 2010, FTP add-in, Registry add-in and today plugin)

Grtz,

Degake
[HD2 Windows Mobile 6.5 Themes and Apps] mikkie:
same problem here.... "found no add-in" when i want to open the registry editor
[HD2 Windows Mobile 6.5 Themes and Apps] kinnyfaifai:
I have no problems here using 2010 (v8.0)
[HD2 Windows Mobile 6.5 Themes and Apps] fur0n:
don't install resco explorer 2010 via CAB (i have the same problem with it) but install with your phone connected to your pc with active-sync and use the *.exe file setup you can download from the resco website

p.s. excuse my english.
[HD2 Windows Mobile 6.5 Themes and Apps] degake:
What did you do to install resco explorer? (Did you use a .cab? or the .exe file found at their website?)

When you're in Resco Explorer, press "Menu" > Options > Add-ins.

Don't you get a message there like "download resco today now"? (if so, you didn't install it :))

Grtz,

Degake
[HD2 General] mannyshere:
Hi there

in the wireless controls the data connection (set up datta connection) seetings always stays on. When i manually turn this off i have no problems recieving and sending MMS but this only lasts for a minute and then i cant send mms or receive, i then check the wireless controls again and notice the data connection set up tab has been switched back on!!!!!!....... i have to keep going back and forth to turn this off each time i rec or send mms??

I am on T-mobile UK with an unlimited data plan
[HD2 General] kilrah:
The data connection is whst is used to go on the net... MMS uses a separate connection, and AFAIK both can't be active at the same time.

So yes, that's what you need to do. When you turn data connection off it will turn on by itself again as soon as any program wants to access the net, be it auto weather/facebook/twitter/mail updates or something you check yourself.

Interesting, I've rarely seen people using MMS regularly... you seem to be a rare species :D
[HD2 General] mannyshere:
:) ok mmmmmm so how is this going to make things simple for me to be able to send mms as i though the hd2 was all about communication....lol:p......so what u are saying is that i need to go back and turn the data connection setting thing off everytime i wanna send or rec mms!!!!

:confused:
[myTouch 3G, Magic Android Development] Binary100100:
Alright so it's been a couple of weeks and anyone can see that the Nexus is casting a shadow over the new MyTouch so it's probably not going to get much attention from Cyanogen. We can still use his roms however we lose touchscreen support. Actually, we can use pretty much any rom as the old MT3G and G1 can use but we can't use the touchscreen.

What I've tried was pulling the /system/usr directory, flashing a CM rom and pushing the directory back but it still didn't make any difference.

I've tried flashing the Cyanogen ROM then flash the boot.img from the Fender ROM but I forgot that the current SPL (1.33.0013) is locked. Another obstacle. So I replaced the boot.img in the CM rom with the Fender and of course it didn't work. I'm out of ideas... but I'm far from being a dev. But there are a lot of you smart guys out there. Has anyone broken any ground on these devices? Now that the original MyTouch is obsolete it's only a matter of time that the popularity of this device will grow since the MyTouch (original) is more popular that the G1 to date.

In conclusion I see two options from here:

We cook a custom MT3G 1.2 ROM from source (whereever that could be found).

We work together to discover a workaround for this touchscreen issue to allow us to use CM ROMs (perferred).

So far the only ROM for the new MT3G 1.2/Fender is an odexed stock rom from http://xdaforums.com/showthread.php?t=623141 (thanks CursorDroid) and the only method of rooting is by goldcard methoddiscovered by Crypysmoker.

If there are any others can you please post them.

I would really like to see the development for this device take off and I'm sure that it will eventually. Themes, kernal mods, custom roms, tethering, overclocking, a2sd, etc and I'm sure that I'm not alone.

Thanks.
[myTouch 3G, Magic Android Development] robkoehler:
I would love to see this phone get some attention. I call it my poor mans nexus
[myTouch 3G, Magic Android Development] tepic:
Has anyone tried adb pulling the touchscreen kernel module from stock and inserting it into a modded ROM to see if it even loads?

/system/lib/modules only has wlan.ko

It looks like the driver might be tied to the kernel :( so a new kernel is needed
[myTouch 3G, Magic Android Development] epeets:
LMAO!! Even though I don't have one and don't intend to get one cause I'm satisfied with my original MyTouch, ROM development is always encouraged. the more ROMs, the better!
[myTouch 3G, Magic Android Development] Binary100100:
Unfortunately, the more ROMs the more confusion.

Now that we have two different MyTouch verions (not including the 32a/32b for the original) this is going to get VERY confusing. It already is. Even if you use "1.2" people are going to wonder if that's the ROM version or the phone version. Maybe MT3G2 or something.
[myTouch 3G, Magic Android Development] Binary100100:
And thus we need a dev. LOL. Unless someone can tell us what controls the touchscreen input. That might give us a step in the right direction.
[myTouch 3G, Magic Android Development] C0dy:
I'm still hoping for Cyanogen ROMs on the Mytouch 1.2.
[myTouch 3G, Magic Android Development] crypysmoker:
Lol since im the one who even discovered the pain staking rooting process ... omg such a pain... I felt the need to comment.

I just today started using my fender over my G1 because Criffmon (however the hell you spell it) came out with the themed stock rom. It looks perfect.

But the reason for no rom yet is the kernel tied into the new touchscreen drivers and 3.5mm jack. There is a whole new touchscreen which is why it doesnt work when u load other roms.
[myTouch 3G, Magic Android Development] kbeezie:
What bout this post though?

http://xdaforums.com/showthread.php?t=623141

That's what I rooted my Fender with. (downgrading of course done with the link you provided)
[myTouch 3G, Magic Android Development] Binary100100:
Of course. How rude of me. Sorry Crypysmoker. I'll update the op.
[myTouch 3G, Magic Android Development] Binary100100:
Yeah that's the rom that I used too... maybe i got my links confused.

That rom is odexed. I managed to de-odex the apps but I can't figure out the framework. I would like to add things like the modified browsers, dialer, contacts, mms app, etc. But I am unsure if it can be done because of the odex.
[myTouch 3G, Magic Android Development] kbeezie:
Ahh I see. (runs off to google 'odexed' :D )
[myTouch 3G, Magic Android Development] Binary100100:
Link please?

EDIT: ahh... did you mean this? http://xdaforums.com/showpost.php?p=5665902
[myTouch 3G, Magic Android Development] ceas909:
wow that looks sweet!!!...
[myTouch 3G, Magic Android Development] Binary100100:
So according to tmonews the MyTouch 1.2 is sold out and anyone interested will have to wait until this Spring to pick theirs up.

Then I noticed an interesting tweet from Haykuro:

"just realized something. The Nexus One and the N900 are amazing phones and a whole bunch of people have it but you NEVER see anyone with it."

So let's get this straight... the newest MyTouch is sold out and all of the devs (like Cyanogen) are rushing to develop firmware for a device that isn't anywhere near as popular. Meanwhile... what has been accomplished with the new MyTouch?

What's wrong with this picture??? :confused:

Has anyone made any progress at all lately?
[myTouch 3G, Magic Android Development] Aeikozz:
there's loads of things wrong with that. but sadly when your a gifted developer you have the right to develop for whatever device you want, even if loads of people won't be using it.
[myTouch 3G, Magic Android Development] Binary100100:
I understand all that but my point is out of the hundred of thousands of devices sold there isn't ONE person out there that tried to develop a rom for it and share it? There are over two dozen people (at LEAST) in this forum that has the phone and not one of them possess the skills to at least figure out how to use a CM rom on the device? Really? Why is that so hard for me to believe?

I'm not saying that I can do better because I know that I can't... but I also don't have any coding experience either. It would appear that all the T-Mobile customers with coding experiences decided NOT to buy this device for some reason. Or they decided to buy it... but not try to improve on it in any way.

You know that if Haykuro or Cyanogen had the phone we'd be on the twelfth rom version by now. :rolleyes: C'mon devs! I'm still using my G1 if I want to show off the power of Android. I want to retire this device already. :p
[myTouch 3G, Magic Android Development] crypysmoker:
No no.. You have it a bit wrong. Wes and Ctso were/have been working on it trying to get the kernel into Open eclair.

The main problem is those 3 drivers we need for the touch screen and 3.5 jack seem to be a super pain in the ass to extract from the current kernel to push into another or build a new one all together. Basically, the drivers can be seen, but not used.

ALL 32a roms will boot on the fender/mytouch 1.2, I have tried literally 10 pages of them.... Bu the moment it looks for a touch screen, all it sees is the track ball and defaults to it. YOu can fully run other roms, but you cant touch. They are trying lol, But were basicly gona have to deal with criffmon's themes for now since 2.1 will be on us in the next few weeks. Supposedly, we are getting the full 2.1 since these are 32a boards.

People are trying, But think of this as a first, NEW release in a long while.

I mean hell, it took me 3 days just to figure out how to root it, when the nexus 1 took maybe a few hours with ways already known.

It will come, be patient. The moment I get a working kernel I will let everyone know.
[myTouch 3G, Magic Android Development] zombierockstar:
Hey Crypysmoker!!! Thanks for all the hard work on this!
[myTouch 3G, Magic Android Development] C0dy:
It's good to know there are people working on this device.
[myTouch 3G, Magic Android Development] kbeezie:
I kinda figured it was a driver issue, since the fender/1.2 seem to have a minor difference from anything HTC was pushing out directly.

Far as the comment that any 32A rom would boot, not that I've noticed, the only thing that booted other than the one provided by cursordroid was normally with a 32A patch from the G1 forum oddly enough. But as said no touch screen and most likely no 3.5 headphone jack support.
[myTouch 3G, Magic Android Development] tubaking182:
just want to throw my name in here, i just upgraded to the fender phone today(but gave it to my fiancee) and my tmo rep actually told me that they are no longer allowing people to do the yearly upgrade to this phone because it is so high demand, but they will no longer carry the original mt3g. once my girl falls asleep i can hopefully get on the damn thing and have a look around, not saying i will have any great news for all of you but i would love to see some custom roms for this phone
[myTouch 3G, Magic Android Development] kbeezie:
Yearly upgrade? You mean existing customers looking to upgrade to a higher model?
[myTouch 3G, Magic Android Development] tubaking182:
i went to the store the other day and asked when i could upgrade my phone and i was informed that since i have a smartphone, they are now doing upgrades every 12 months. not sure when this happened but it's good because i love to upgrade my phone
[myTouch 3G, Magic Android Development] kbeezie:
Odd, I never heard that from any of the t-mobile stores I was at. I just figured if you wanted to upgrade, say for example you were on a subsidized phone you'd have to pay something like 200-300 to upgrade. Least according to their website.
[myTouch 3G, Magic Android Development] tubaking182:
yeah, their site says nothing about it, but the t-mo guy here in stl let me upgrade today and there is still another line on my account available for an upgrade(waiting for the my touch slide cause i can't stand the onscreen keyboard BS). like i said i went in and asked when i could upgrade and he looked it up and said i could upgrade today
[myTouch 3G, Magic Android Development] ceas909:
any info for us?? :D
[myTouch 3G, Magic Android Development] tubaking182:
unfortunately not, she won't let me near the dang thing, she thinks if i get to plug it into my computer then i will try to do something and possibly brick it. but after thursday i will probably not be any more help as i think i am trading with someone to get the original with the 32b board
[myTouch 3G, Magic Android Development] AngioNicholai:
is there any root method for this yet?
[myTouch 3G, Magic Android Development] kbeezie:
For what yet? The Fender/1.2? If so check out the link in my sig, its only a stock rom but least its rooted.
[myTouch 3G, Magic Android Development] Vatofat:
Early upgrade

Im a tmo rep. Early upgrade plus is the same as a full upgrade except you are not eligible got mail in rebates.

That upgrade starts at one year. Fortunately all of the android phones have no mail in rebate. Btw, there is a beta for swype available. Im faster with my left thumb with swype than with both thumbs on a physical kb. I have a black mt3g 1.2.
[myTouch 3G, Magic Android Development] Binary100100:
I posted this three weeks ago hoping that someone will step forward with the knowledge of how to do this. Still nothing. I find that amazing and unacceptable. Come on guys! The G1 didn't take this damn long! :mad:
[myTouch 3G, Magic Android Development] Aeikozz:
G1 is always going to have stupid support cause it was the first the android phone. i wouldn't keep my hopes up for the myTouch LE Specifically
[myTouch 3G, Magic Android Development] Binary100100:
Well here's the thing.

There are more people with the new MyTouch than the Nexus.

The MyTouch Fender has been how for how long? Since January.

The Nexus? About the same time.

How many roms has been cooked for the Nexus? How many developers does it have?

How many roms has been cooked for the Fender/1.2? How many developers does it have?

So about two and a half months and still nothing! NOTHING BUT A ROOTED ROM! Come on! We have stuff for Blur, Nexus, G1, Regular MyTouch, Hero, Droid, etc, etc, etc and all though these are not as common as the G1 or regular MyTouch you MUST look at the fact that eventually the new MyTouch is going to outnumber the old version. And there are more people with the regular MyTouch than the G1. So this tells me that if this keeps up then the majority of the Android devices out there will be stock. Really? Is that what we've been endorsing all along? Is that what this community is here for? Come on now! Three months is two months too long!
[myTouch 3G, Magic Android Development] Aeikozz:
Well by that theory that means that the orignal myTouches will become like higher in ebay value because they can tether.
[myTouch 3G, Magic Android Development] Binary100100:
Unless we can get tether on this device.
[myTouch 3G, Magic Android Development] Aeikozz:
what if we threw a bunch of cash towards cyanogen mod's way?
[myTouch 3G, Magic Android Development] Binary100100:
I would personally donate $50 for the cause.

But I need the rom to be released because so far he hasn't responded to ANY pm that I have sent.
[myTouch 3G, Magic Android Development] Aeikozz:
i'll match your 50$ throw that his way see if he responds.
[myTouch 3G, Magic Android Development] Binary100100:
so assuming it doesn't take him any longer than two hours to patch it up to work it'll be a $50/hour job. That's a decent deal. Anyone else? I'm not paying until I can get a working rom though. Otherwise if I just donate $50 and nothing comes from it I'll be really pissed.
[myTouch 3G, Magic Android Development] Aeikozz:
same here. see what he says
[myTouch 3G, Magic Android Development] Binary100100:
he's not going to say anything because he's living in the Nexus forum.
[myTouch 3G, Magic Android Development] RaindropBebop:
Do you think calling him out will make him want to help you? You do realize that, with the release of eclair and nexus, the MyTouch is old news, right? Even if it got a facelift, the nexus is capable of twice what the MyTouch can do without so much as a loading bar.

It's the nature of the industry. New technology comes out, developers migrate to support the new and improved stuff, and spend less time on the old.

I'm not saying that a rom for the 1.2 MT3G will never happen, but you might have to wait until a developer gets his/her hands on one (since they all undoubtedly dished out all their phone-cash for a shiny Nexus One 2 months ago).

Also, from what I hear, the 1.2 will be getting the android 2.1 update since it can support eclair. Maybe the devs believe that it would be more prudent to just wait for that before making a rom based on an old version and having to back-port what they can from eclair.

Trust me, If I had the cash lying around right now, I'd grab a Nexus One in an instant. Unfortunately I'm a piss poor college kid, so $500 for a phone is out of the option.
[myTouch 3G, Magic Android Development] Binary100100:
I'm not calling him out. I'm not a gunslinger. More like spurring on the community. By looking at the stats on this thread there are at LEAST 56 people at this point that want this. If all $56 people donated $10 it'll be enough for the creator of a working CM (to include all future updates) to buy his/her damn Nexus. That sounds like a pretty damn good deal to me. I've already spent several hours packing boot.img files to try to get it to work. It can work because it's been done... barely. A member (not sure if I can call him a dev) named Angio(something) has ported over a few roms to use. None of them are stable though. Why would it be not of his interest? A member that posted earlier is willing to match my $50 donation to make this happen. There is no way that all 57 people will donate $50 but if it did happen (which is more likely than Cyanogen patching the original boot.img file for his roms) is $2,850. But we all know that isn't going to happen. But you should know how quickly it all adds up as long as we have enough interested people. But sadly there doesn't seem to be any. There are several developers that constantly unpack and change boot.img files and manipulate kernel files and not one of them want to make this easy money. What's wrong with this picture? If I knew how to do it (I've tried, remember) then it would have been done two months ago!

"Maybe the devs believe that it would be more prudent to just wait for that before making a rom based on an old version and having to back-port what they can from eclair."

Which is exactly why we gave up in trying to make bluetooth work on Hero roms. We've been waiting for the source. We don't even know for a fact that the phone is even going to get 2.1. Even if I see an official notice from T-Mobile or Google that it will get the 2.1 Eclair update on any certain date range... I'm still adding about two months to that period in my expectations. Because they've done that for over a year now. They kept pushing back Cupcake, then Donut and now they will definitly push back Eclair because there are more devices that it needs to be compatible with. I'll give it another six months I think. Perhaps I'm just being a pessimist though. But if I'm right and we are waiting for 2.1 to roll out, you guys go ahead and wait until September for your rooted firmware.
[myTouch 3G, Magic Android Development] Binary100100:
There is an open issue here: http://code.google.com/p/cyanogenmod/issues/detail?id=1174
[myTouch 3G, Magic Android Development] Aeikozz:
make sure you check the star on that page. as the more stars there are on a topic the more it shows how many people are intrested in it.
[myTouch 3G, Magic Android Development] Binary100100:
Did you do that?
[myTouch 3G, Magic Android Development] Aeikozz:
yes sir .
[myTouch 3G, Magic Android Development] Binary100100:
Great! Just about 100 more to get their attention.
[myTouch 3G, Magic Android Development] Aeikozz:
with any luck it should happen naturally now that it's on the main page, cause like you said this is the only version of the myTouch being sold right now
[myTouch 3G, Magic Android Development] dstauth:
I added a star. Hoping we can see some custom ROMs for the mt3g 1.2 at some point. Right now there isn't much.

Is that port of Stokes Eclair working well? I see the 2 of you using it. What doesn't function? Thanks.