Related
I am about to get a p3600i in a few days.. any warnings or anything i need to know about this phone. i flashed my himalaya into non existance many years ago and my tornado is running wm6 now and i love xda-dev but from what im reading in the forums, no one knows jack about this device yet.... can i network unlock it? supercid??? etc etc. tried following posts but too much confusion with having p3600 and 3600i in the same froum so i cant always make sense of whats being posted.
Any help appreciated!
EDIT REASON: GOT THE DEVICE!!
Well thanks for the heaps of input guys
only irritating thing i found with this device (p3600i) so far is the stylus being right next to the camera button so every time i go for the stylus i start camera. definate annoyance!
Turn：mikeyangly（Come from：pdafans.com）
Touch screen, and drive signals are not supported, I hope the faithful machine can solve this problem
System Download:rayfile.com/zh-cn/files/4e80a502-973c-11df-abb4-0015c55db73d/
GREat news !! hope its just a question of time for the others drivers!
On my neotouch android doesn't boot. It stays on this:
EDIT (22:05): now it boot. I haven't got in the root of Storage Card .
s200 froyo 2.2
O ye,this is a very great news,incredible ,we jump directly to Froyo 2.2,as you say it is a matter of time and developers now.The waiting has began!
Otherwise phone boots very quck:
-no touch
-no sound
-no keys
-no gsm ...
we hope all will be on soon
good start. hope problems are possible to be solved....
Oh very goog!!
Does tsamolotoff's TS driver works?
its drivers work with ubuntu!
Wow great news!I am waiting for a full working version(rom)
Android just has more free apps than windows..
that would be the only reason i would want android
free apps... oh well
The only reason i would want android is a bunch of games ported for this system. Android for games and WinMob for everything else. and all this stuff in one device. that would be nice
very good.
Why do I have blue screen after 10 seconds working of it?
Because there are many problems to resolve to use android on our s200...The os is not alredy usable like in htc hd2,and our device is not supported like the htc one.So maybe the project for s200 is end.I wish i could use android in my phone,but maybe i will never see a usable interface
This is an exciting good news. Soon we can use the Android system has. Thank you for your efforts.
Sadly theres no kernel/android dev that has an s200, so android partly working on it might never happen, unless a dev picks it up and starts making patches/fixes for the kernel.
Not so good if you think that s200 and hd2 project started togheter,but hd2 after 1 month has a usable android or ubuntu release and our s200 has only a not usable android "desktop".Our device is not supported by comunity as hd2,so correct me if i m wrong,but i think no one still working on android s200 release
Ok guys it has been a month since first post, anyone reckon this is going somewhere? who was developing this in the first place? I am willing and ready to help in any way I can (I have stated this before) if necessary. I have a working s200, but no experience in linux programming, although I could learn some basics if needed.
Maybe we could send some android devs a pm? I mean how hard can it be if our hardware is so similar to the Liquid, AND we already have it running on our processor...?
I have seriously considered leaving the s200 and getting an HD2 by now...
Greets
no news of any progress for a while now...
anyway i never expected a fully working android on our neotouch. theres just not enough guys working on it like on the HD2...
can someone mirror this file please?
i dont want to download & install rayfile's client...
Thanks.
It s a really hard porting job...Hd2 owner has a good partialy stable android port,but as you all know there's 20 times hd2 then s200.The problem on our phone is the restricted comunity support
Well, it seems that when I got my s200 broken nobody raised the banner from my cold hands
Now my device is up and running again, and maybe i'll try to do something more... don't expect ts to work in android, as it's completely functional via tslib, and i don't know droid's architecture to determine why this PoS of an OS can't use it... if you really want it guys, why don't you experiment with sequence of input_abs_* functions within ts worker thread in driver ? There're so many *experts* who make ROMs via kitchens or do fancy icons/pictures - take up your time and learn C / linux kernel... I started with barely basic knowledge of the first (and I was lucky with the fact that there're many pre-coded drivers that simply needed some testing, or with semi- or fully-compatible initialization (many thanks to dcordes, Cotulla and the team))
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
No pb for me with each Nand i tested. (prj Clean Desire, typhoon, Hyperdroid)
i had this to on my sd build i used to have but when i went to NAND everything was fixed
maybe you can try to recalibrate it in android?
Auralol said:
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
Click to expand...
Click to collapse
Usually d G-Sensor/Accelerometer has been pre-calibrated while cooking d android build...I've never had such a problem on SD, NAND or RAM builds....Perform a Task 29 on ur device and try flashing the build contained in my signature....CMY's work has always been great...
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Auralol said:
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Click to expand...
Click to collapse
Hmmm...Since it works on WinMo, try recalibrating it there and then run an android sd build (i just tried "Desire_DL" series and all was ok....on d other hand, have u tried d NAND build in my sig?
I have tryed everything, including your builds in the signature.... Nothing helps
Help!
Try the post that is in my sig, there is alot of info in there that might be of use to you. What definitely controls the G-Sensor is the bma150_usr file. If nothing in my post helps you at all, then I am unable to help you further since I dont have a Eu HD2. But I still believe that there might have been a revision which might explain your troubles as well as some other people.
Tryed that also, no help at all.
Auralol said:
Tryed that also, no help at all.
Click to expand...
Click to collapse
Hmm, dats quite a dilemma....I tk it u can't return n request for another device seeing as u got it 4rom Estonia...or can u?
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Auralol said:
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Click to expand...
Click to collapse
True it wasn't but IT IS...I and several others are proof it works beautifully on the HD2, even better than some native android devices...I offered a suggestion n its ur call 2 tk it or leave it...I on d other hand, love my current android build on my HD2.
Have u tried this workaround?
P.S. Oh yeah, and my accelerometer/g-sensor works perfectly in apps n games.
I mean, yeah it is working, but... not working for my device. And the point was that i can't take it to my local shop for a return, as the g-sensor works for the WinMo, and they will say that its your fault that it isn't working in android. Yeah i know that accelerometer works on androids on the Tmobile HD2-s
And yeah, i have tryed
Different type of g-sensor
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
[email protected] said:
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
Click to expand...
Click to collapse
Hi Jay, I've got a similar problem.
Actually, I've got (or had) an EU model, and my screen cracked, so it has been out for repair. So both descriptions in this post (yours and Auralol's) fit my problem. I have been looking for a fix for a while now, did you find anything?
I would love it to work, it really is the only thing that doesn't. If this is fixed, my HD2 would be perfect and irreplaceable.
If you find anything that helps, keep me posted?
Kind regards,
Bas
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
[email protected] said:
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
Click to expand...
Click to collapse
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Bas2ct said:
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Click to expand...
Click to collapse
Hi,
I'm having the same issue as you and was wondering if you had made any progress or if there is anything I could help you with although my programming knowledge is probably more limited than yours. Anyway this issue seriously needs to be looked at! :'(
Still no fix?
Hello, I know it is old thread, but I see there are more people than only me having this issue. Same thing happens to me. Accelerometer isnt working on Android, but it works great on WinMo. I tried a lot of ROMs, "fixes", but nothing helped at all. I used apps like Sensor debug, and sensor list, seems that they dont see my g sensor at all, like someone said before. As I know, g sensor is connected with bma150_usr file, but I used my Root Explorer to search for that file and there is no such a file at all. Shouldnt it come to my device with other ROM files? Yes, I tried to put it where it should be, but the same s**t again... Is there anyone who solved this thing? Because I dont see any solutions mentioned in the whole xda forum.
Looking forward for answers which REALLY helps.
Hi,
I have this same problem, My g-sensor didin't work on AMeriCan Android.
I was reading a topic http://forum.xda-developers.com/showthread.php?t=902129, and my question for this: How I can delete files
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
Click to expand...
Click to collapse
hello all, first let me just say yeah im a noob and yeah i tried searching.
so like the rest of the world i hated win 6.5 more than anything. seriously. probably something like 1. hitler 2. win 6.5 3. snakes
finally i managed to install win 7, but however the battery is just way to short, some numbers wont be recognized, marketplace isnt open in my country, etc. frankly im ****ing tired of all of this. now i want to remove it and again try to install android on NAND. if not maybe just settle for win 6.5 i dont know.
EDIT
to clarify:
-basically ive searhed everywhere
-i have the offical rom and i want to install that
-i cant connect my phone to zune,
-so when i run the offical htc rom, it just says connect your phone
You need to either flash a stock ROM via sd card method or via bootloader (hold vol down key during power-on, then flash with normal exe from windows).
so, just to be clear,
you got a device with Win mobile on it which you seem to have a massive dislike for and wrongly make an assumption that everyone else doesnt like it, then in a hugely disrespectful manor you compare it to hitler, quite what you are thinking is anyones guess but it might be worth considering a change of manor is perhaps in need
Then attempted to install WP7 without fully reading everything.
Then try and install an original ROM without Fully reading everything
I think That about sums it up
So, in the intrest of sanity, go here
http://forum.xda-developers.com/showthread.php?t=1074233
read it all, and if you have an issue reply in that thread
Couple of pointers to help your days on XDA dev out, if there is a thead open on an issue use it, dont make a new one because it makes it harder for people who actually search for things to find what they are loooking for and its a pain for people who try an help because we are forever repeating ourselves
Secondly, when you make a tread it gave you a list of threads already out here with a similar name, if you didnt see anything relivent its because your use of title is pretty poor, Its windows phone 7 or WP7, Noob isnt a word most of us use
Thirdly, if you can not use the XDA search then use google, (i find it much more accurate) i just searched google using this string
XDA DEV LEO WP7 FLASH ORIGINAL
and the third one down took me straight to that thread above
XDA DEV is pretty obvious, LEO is the listed device name thats on this site WP7 is the OS then FLASH ORIGINAL is the subject matter im searching for
Keep it short, like bullet points, not a long story
So, head over there an folk will be happy to help you out, including myself
I hope i didnt sound rude and off hand, im simply nudging you in the right direction
Neo84 You need to either flash a stock ROM via sd card method or via bootloader (hold vol down key during power-on, then flash with normal exe from windows).
ok, thanks for you reply. sorry to ask but what is a stock ROM? is that like an official ROM from HTC?
also tried to hold down the volume key, get the coloured screen, but then cant do anything. where would one find the "normal exe"? thanks for your willingness to help out someone not as experienced as yourself
and dazza, my good man i do appreciate the nugde, but do find it a bit harsh.
you got a device with Win mobile on it which you seem to have a massive dislike for and wrongly make an assumption that everyone else doesnt like it,
-everyone i spoke to agrees, including the guy who sold it to me for almost nothing (bought for 1100 US 6 months before) because he hated it like no other
then in a hugely disrespectful manor you compare it to hitler, quite what you are thinking is anyones guess but it might be worth considering a change of manor is perhaps in need
-well irony doenst work online my bad, haha seriously noone in ther right mind would compare the 2 and/or accuse someone of doing so
Then attempted to install WP7 without fully reading everything.
-i did, it works almost perfectly, reading on these forums ive seen plenty of ppl having issues, so yeah its close to perfect, except the battery drain (which still works for a full day so i can charge at night)
ive searched google, xda and god knows what. and after trying all, my good old hd2 still wont connect maybe in the end its not worth the time and effort, just leave WP7 on there (it is in fact pretty sweet) and buy an offical android next time! however i do feel i have the right to be a bit angry. winmo 6.5 isnt worthy of selling for a high price in 2010.
anyways, thanks for your help, i will check out those links and see where it takes me just remember that not everyone is as experienced as yourself, a friendly heads up works wonders sometimes
I appologise, it was not supposed to come across rude, harsh is perhaps an accurate way of putting it, remember that some of us take a lot of time out of our lives to go over these things, infact some have even added entries in to the Wiki for just such issues (check leo wiki section) and im sure you can imagin that repeating yourself over and over can be quite frustrating!
I completely agree that a "heads up" is always needed, which is why ive nudged (perhaps with a prod or two ) you in the right direction, those few tips can save you a lot of hassle in the future, the google one especially as i know only too well that the XDA search is crap
I have just installed WP7 and when it started the touch screen doesnt want to work at all. On everything it said it was installed successfully and i did every step in the guide -> http://forum.xda-developers.com/showthread.php?t=1356833.
Buttons works.. i can volume+ and - and i can also lock the phone but due to not working touch i cant work with it..
Anyone? Its not broken .. it was working great on the Android before the flash. Please i really need to know what to do.
Edit: I even tried installing v4 but still doesnt works.... :x
Im really sorry for triple posting but this is getting annoying. All day im trying other and other ways, flash back to WM6.5 .. TOUCH SCREEN WORKS ITS NOT GOD DAMN BROKEN ... I've send a PM to the developer of the ROM, guess what no answer.. i dont want to get back to WM6.5 .. I've used to flash 4 NAND androids (the best ones) each one of them in the main functions shows at least 2 bugs which are annoying like freezing display or my favorite - i cant hang up... i posted a thread in the Q&A Android forum about this, again no answer... I ONLY NEED TO KNOW WHAT TO DO to get my touch screen responding and working on my god damn WP7 so i can stop getting freezing stupid display and to be able to god damn hang up.. IS IT that hard!?!?!? Oh the best one is - i cant post to the main topic of the rom because according to the forum rules the newbies are idiots and they cant recognize any bugs in the rom so they can report it!... Jesus Christ give me a f***ing answer how to fix my touch screen driver or something or whatever i want my god damn phone working........
Hello I have the same problem, I went back to Windows Mobile 6.5 but the problem remains !!!!!! The touch does not work anymore!! How do you solve this problem??http://media.xda-developers.com/images/smilies/mad.gif
Hello you some news? I hope you do not have to buy the new touch screen!
For the original poster, I have no idea, sorry. For the second poster, it definitely sounds like your digitizer is broken. Have the same problem with my HD2. You can get them for cheap on Amazon, but replacing it takes some skill. Don't know where you live, but most repair shops will do it for around $50 here in the states.
Same here. i tried the YukiXda/Xboxmod Rom and after a reboot the touchscreen stops working. Will report to the devs. do not worry my friend
Hey darky, did you try installing the old HTC drivers on your WP7? Not sure if you did, or if that particular rom uses the newer drivers, but that could potentially help out. I found the old drivers in the Xboxmod cab update thread. Don't know if the rom you're using supports cabs or not, I've only used xboxmod & yukis rom. Search that thread, would post a link but using my phone at work.
---------- Post added at 08:38 AM ---------- Previous post was at 08:35 AM ----------
Nitro_123 said:
Same here. i tried the YukiXda/Xboxmod Rom and after a reboot the touchscreen stops working. Will report to the devs. do not worry my friend
Click to expand...
Click to collapse
Same as you, over here. As soon as I updated to SP1 & rebooted, no more touchscreen! But mine wouldn't work in any OS, including WM6.5. So I think my digitizer just had bad timing for me, but who knows could be rom related.
Thank you all for taking time to answer!
@lorispari No i couldn't get it fixed at all, your problem sounds different than mine because my touchscreen works with other OS without problem.
@JonnieLasVegas I haven't tried, i only tried different radio version and reinstall of the HSPL... though i dont know how much that could help me because im still new with the smartphones... as far as i see this HTC HD2 is really great but has a lot of factory bugs in hardware and software side (if i could say it that way). Even with stock WM 6.5 it had a lot problems. Anyway when i saw the thread with all the known bugs that WP7 has... i just clicked the HTC Leo: HD2 category and switched back to Android ICS which was another mistake because i forgot its still buggy as hell so im flashing atm to Gingerbread however in few months im selling this phone and getting HD7, hope till then there will be a category for him (or it may have.. i havent checked)
Thanks again for the answers! Appreciate it!
My screen was unresponsive twice. Turns out digitiser was broken. So had to flash to stock rom and send to htc for repair
If you need a fix, pm me, found one