Related
i have recently upgraded my xda II to wm5 and everything was perfect but when i was going to take a photo i realized that both left buttoms, camera and record, don't work, in any way.
Does anyone have the same problem, or maybe is a natural problem and i haven't read enough?
sorry bout my poor english and thanks for ur great work!!
This is a known issue, but one that doesn't seem to affect everyone. This issue is also being discussed in another thread: http://forum.xda-developers.com/viewtopic.php?t=21391&postdays=0&postorder=asc&start=325
xda 2s
can the Xda 2s keypad be use after upgrade to Wm 5
10x diving i going to read and if i get something i would repost here
I've tried a lot of android builds whilst the development has been going on and found that Bangster's 1.4 coupled with Michy's R11 was the best for me with regard to screen sensitivity and keyboard accuracy.
I recently had a dabble with m-deejay's next-gen builds Desire HD/Z etc (which are excellent by the way, credit to him), and found that I was getting a lot of screen bounce, missed button presses and a very frustating keyboard experience (Hastarin R7.1). Pressing and holding the delete key for example would result in keypresses bouncing all over the place, sometimes several keys removed from the delete key. I tried a plain Froyo Sense build and found the same thing, although not quite as bad.
So, I decided to try the bare kernel from Michyprima's R11 (AXI, Desire, OC) on my current Froyo Desire build just to see if it was down to the kernal 100%. Instant bounce removal... keyboard is accurate and now when I press & hold on the home screen, I don't get the screen wobbling from side to side as the software thinks that I'm moving my finger around rapidly.
To recap; it seems like I was getting more bounce with Hastarin's R7.1 than any other, but certainly Michy's R11 (Desire based) is making my phone usable again. It really was bad before.
More messing required methinks... I may re-load the Desire Z build on to my SD card and try R11 to see what it's like. One thing I remember is whilst trying m-deejay's Desire HD 3.1 (which had an Evo kernel IIRC), keyboard bounce was almost non-existant. It wasn't until I changed to D-HD 3.3 that the keyboard became a pain to use (Hastarin R7.1).
Hastarin if you read this, please note this is by no means a dig, I have the greatest respect for all the guys posting builds here, these are just my obvservations.
As with all things Android/HD2 related, YMMV. Your thoughts are welcome.
---------------------------------------------------------------------
---------------------------------------------------------------------
Edit: I've taken a couple of quick videos of m-deejay's brand new 3.4 Desire HD build showing this phenomenon (kernal is huanyu's #21). Replacing the zImage with Michy's R11 virtually eliminates it.
Video 1 - homescreen
Video 2 - keyboard
Could this be Windows ROM related? Might flash another WinMo ROM to see if it's any different.
Edit 2 Sent my HD2 back to HTC today, hopefully for TS replacement... see relevant post here.
Edit 3 Received my HD2 back from HTC's repair department. Problem fixed. No more bouncing Relevant post here.
No-one else with similar experiences?
Me too!
previously was using M-deejay's froyo sense 2.2 and the keyboard was a great improvement from my old stock HD2 Windows keyboard, which was oversensitive and jumps alot, making typing a hassle. I did not have any problems with the froyo sense 2.2 keyboard, it was accurate and sufficiently responsive, and even have my essential chinese input.
However, after the 2.4 version was released, i updated it, and noted that the browser's bookmark crashes. So i though, why not give EVO Sense 1.6 a try?
Btw, i did not realise any problems with the 2.4 keyboard, so it's probably as good as the 2.2 version.
Then i ran EVO sense 1.6, and i feel that the keyboard is different. Firstly it's the additional arrow buttons below, which is useful, and more like the original HD2's keyboard. Then it also has chinese input.
BUT i experience alot of the "bouncing" problems, if not more than my original HD2 windows rom. tried calibrating a few times, and deleting the calibration, but it doesn't help.
i want to emphasize again i am very grateful to all the developers like M-deejay, Hastarin, for developing all these builds that are effectively working. this is likewise, just my observation.
Anyone else? I can't believe it's just us two!
Videos added to 1st post.
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
have the same prob!
yep...and I get phantom touches also.
jaka.erc said:
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
Click to expand...
Click to collapse
What WinMo ROM are you running?
JanssoN said:
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
Click to expand...
Click to collapse
CleanEx DsE GTX 6.5.x
anoschka666 said:
have the same prob!
Click to expand...
Click to collapse
muzicman0 said:
yep...and I get phantom touches also.
Click to expand...
Click to collapse
Try changing your zImage to Michyprima's R11 and post your findings
Major_Sarcasm said:
No-one else with similar experiences?
Click to expand...
Click to collapse
OK ! very common HD2 touchscreen failure! ...ur touchscreen is defective ....there are many threads already on xda regarding this ...but could not be solved because this is a hardware problem ...this even happens in winmo ! here are the youtube videos having same problem
http://www.youtube.com/watch?v=DhhrA3u4rcI
http://www.youtube.com/watch?v=3rJJ1eyM9FM&feature=related
http://www.youtube.com/watch?v=QEHn9CaHFpk&feature=related
http://www.youtube.com/watch?v=hY60I9Z0RU0&feature=related
http://www.youtube.com/watch?v=TSvAlqw6HJw&feature=more_related
http://www.youtube.com/watch?v=6hIE_wV4djs&feature=more_related
and here is my thread about this in detail - http://forum.xda-developers.com/showthread.php?t=745255
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Got it to but not in my homescreen. When I am typing with swype ... When I try to delete a word it will write 10 :X nice feature but its really anoying. But lets wait I thing dev know about it let wait for nand and the bother them with this. I heard It is a long way to nand
coolbeer1990 said:
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Click to expand...
Click to collapse
Thanks for your reply. However, my screen isn't defective as I don't have this problem in Windows and using a different kernel fixes it.
major_sarcasm said:
thanks for your reply. However, my screen isn't defective as i don't have this problem in windows and using a different kernel fixes it.
Click to expand...
Click to collapse
that's great my friend
Well.. i have the same thing in hastarins latest kernel
I dont have this on DesireZ out the box.
I have MDeejay's latest Desire HD build and have this problem, how do I fix it? If I need to replace the Kernel how do I do it? What side effects will it have?
Thanks in advance
keyboard bounce also experienced by me when i am trying to type fast, using hastrin r7.1 as well, maybe is caused by the touchscreen delay?
have you tried keyboard calibration?
in the setting menu ..
it ask you to type that ..lazy brown fox jumps..
it helps me alot.. well some of it i guess
and also try the schrub bartome build. the keyboard is perfect-iphone like. im using this build for day use
I experience the same issue with the new kernel releases. But with hastarin #3 the touchscreen works normally.
Sent from my HTC Vision using XDA App
Hello.
*update*
after install jm6 on my tab there was a "Horizontal calibration"
install jm6 go setting -> display settings -> horizontal calibration.
Works perfect for me. Now i can play alot of doodle jump
-------------------
My G Sensor on my Tab is really bad..
and i can't play games like Doodle jump..
How can i fix this?
- Maybe with Terninal Emulator?
I talk with Samsung, and they just say that i shall send it to service..
Sorry for poor english.
Hi
I have exaclty same problem, sensor are badly calibrated.
Can t play doodle jump... (I know, life is difficult)
Any idea to calibrate it?
Thank and regards
Matt
Hi,
Try Google Sky in landscape position ;-)
Poor or bad calibration !
Have the same issue. 2 Degrees x, 6 in y direction.
No feedback from Samsung service up to now.
BR
Peter
There is a sensor self test - dialpad *#0*#
Thx, but a selfetest does not solve the problem
Calibration would help....
Anyone any idea, someone knows how Samsung would repair this, via Software or do they have to change ´some hardware?!
BR
Peter
My tab also has the g-sensor problem. I tried two tab and both of them has different degree of G-sensor problem, I think the G-sensor problem caused by samsung's inaccurated calibration. I would also want to know the way to calibrate the sensor by myself, anyone can help?
This is the first thing I noticed when I buyed the tab. The gsensor is off, it often changes to landscape or portrait when only a little inclination is given.
Sent from my GT-P1000 using XDA App
Yeah I just download that free 'level bubble' app.
Pitch off by 2 degrees
Tilt off by 4 degrees
Noticed the same on mine. Not a big issue for me. Hopefully it will be addressed
Sent from my SGH-T849
Dicussion today with Samsung Service Hotline,
try full hardware reset, if that does not help send it to repair it.
Tomorrow ill have the chance to talk to a technical guy.
Keep u update.
Peter
Today discussion result.
1.) Wait for software upgrade, known issue, no info for release of new
Software
2.) Exchange Hardware. If lucky new ist ok, if unlucky change again.
Br
Peter
Wasn't there a method to calibrate on the galaxy s? Would it work
Sent from my T-Mobile G2
bug fixed. look at first post
Sent from my GT-P1000 using XDA App
Means if u dont want to do unofficial Firmware update, not to loose ur warranty, there is no solution.
Anyhow good info, means no hardware defect.
Peter
You can calibrate it with 3d compass apply in the market. It has a calibration option that should work fine.
P.d Samsung service has to be amongst the worst in the world. Will they ever solve anything?
Sent from my GT-P1000 using XDA App
Tiamath99 said:
You can calibrate it with 3d compass apply in the market. It has a calibration option that should work fine.
P.d Samsung service has to be amongst the worst in the world. Will they ever solve anything?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Hey which developer is 3d compass by?
Sent from my SGH-T849
Its probably to calibrate the compass (magnetic North)
I use spirit level plus (by Androidika) which has calibration but only within the app itself which means you place the tab on a level surface and hit the calibration button and it 'zeros' everything out. I doubt it calibrates the internal sensors.
Tried both, but calibration only works inside the app.
Try to get any statement from t-mobile our Samsung on monday
If someone has a solution....
Br
Peter
Ok,
finaly T Mobile sent me mail.
Software Update to come, no but no idea when...
In the meantime use "official" Firmware from Samsung and flash it (even if not offered via Kies).
Anyone can tell me what is the latest "official" firmware for European device?
Got already feedback from other user, that with a flashed ??6? version there is a botton to calibrate..
thx
Peter
Okay, I'm creating this thread so that all users can post their experiences/bugs here because its annoying some of the devs when people post questions in the dev threads. So all you guys like me who need to ask questions or talk about this ROM please post here. I hope they will be kind enough here to answer everyones questions.
I flashed this ROM 3 days ago and I have to say im pretty goddamned impressed. A few words and questions.
First off, I love the stock look from 2.1. 6 Bars for signals, stock moto launcher. That has got to be the most important for me because everytime I flashed a froyo build the launcher would include just the app drawer and no dialer or message buttons like in stock 2.1. The haptic feedback is crisp and works in a few places. Like the dialer and 4 buttons below. The thing I love most about this ROM is is the built in moto LED notifications. I always missed that on the froyo builds and tried using apps like LEDme now and others but it just didnt cut it. The media button works. Its really fast and overclocked its a beauty. The only problem I found with the dialer was the number format and I dont know WHY that should be a problem for anyone. A cool thing I noticed with the dialer was you can block calls from inside the dialer. Love the stock appearance. Okay I dont know what issues you guys have with SMS. All I did was install keyboard for gingerbread longpressed the text input space and chose the input method. It replaced the stock keyboard and everything is fine. The SMS has nice solid black background compared to the grey in dexters and CB's which I assume saves battery. Also you have extra SMS options like pop ups. All apps work great and fast. Over clocked at 1000 mhz, 74 vsel it works as a charm. I use autokiller at moderate and never felt any lessening of RAM or slowing of the phone. About the APN settings yes I cant choose them but for some reason it picked up the settings itself and my data connection is active. I have an unlimited plan so its always on, for those who dont theres a power control app called switch pro you can turn off data along with another bunch of functions. Its basically an extended power control menu. It also has a nice UI. Camera works nicely and over all I just love the stock feel. I have had no signal problems its actually really good. WIFI signals are keeping well even though my router is far away and with froyo I used to get only 1 bar. Apps like Google+ work nicely.
Issues/Questions: I fastbooted into fjfalcons boot4.img. For some reason it became really slow and I had to reboot without it and now its fine. In set CPU half of my swap was active without even running any apps. I use 91 mb linux swap on my SD card like in reverends video from the old khal rom days. Besides that I want to ask about the super sleep mode button, what does it do? When do i activate it? How does it work? etc. By the way im using M7's patch with extended menu's. Umm besides that I tried installing root explorer but it already has its own korean RE, and I cant install root explorer on top because it says system app cant remove. Theres also another browser which in in korean but I just ignored that.
Besides that I have had no Issues with this ROM. Seems very solid and suitable for everyday use. I flashed directly from CB's froyo without reformatting my SD. All my apps were preserved and I had no issues booting this ROM up. I did loose the calvin bootloader img in the start which is now replaced by the official moto M and a sexy T logo after works. All in all I feel this is a keeper, after trying literally every ROM on this forum atleast 2 dozen times. Thats my review as a normal moderate user. I don't play many hardcore games and use my phone for calling, sms, browsing and photos.
Please post your opinions and experiences. And any bugs. Thanks!
How is it's speed compared to miui? does it beat miui?
Sent from my Milestone XT720 using XDA App
It feels like an official update from moto
If the dialer and messaging were fixed (americanized), I bet cincy bell would backtrack and call this the official update, especially with a swype keyboard.
Sent from my XT720 using XDA App
Just curious, does swype really feels that great? Cos im using swiftkey and i feel that i type much better there :/
I'm not a huge fan of swype. My favorite keyboard actually is the stock gingerbread keyboard. I really fly with that one.
Swype is perfect for me when it understands my words correctly.
Sent from my XT720 using XDA App
cancrippler said:
Swype is perfect for me when it understands my words correctly.
Sent from my XT720 using XDA App
Click to expand...
Click to collapse
Yeah, well that's kind of the issue. Sometimes works well and types fast, other times it misses my words. Too many misses makes the gingerbread keyboard my default for speed and reliability.
But Swype also lets you type normally as well as swype to type.
Sent from my XT720 using XDA App
spectacle said:
How is it's speed compared to miui? does it beat miui?
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
I think the speed is comparable to miui, but its way more stable with very few reboots or any other problems. Could someone comment on the battery life? I'm getting a day with low use. I flashed from the CB Froyo does that make any difference if I don't flash 2.1 Korean first. Kernel issues?
Sent from my XT720 using XDA Premium App
Nice review! But how did you get LED-notifications to work? They don't work here w/o LEDmeknow.
Battery life here is somewhere between 2.1 stock and 2.2-ROMS on here.
Vistaus said:
Nice review! But how did you get LED-notifications to work? They don't work here w/o LEDmeknow.
Battery life here is somewhere between 2.1 stock and 2.2-ROMS on here.
Click to expand...
Click to collapse
It was in the display options. LED Notifications and periodic notifications just like in 2.1. After I selected them I got the flashing 4 bottom LED's which would stop after a few seconds and restart every 4-5 minutes.
My battery life for me sucked bad even after calibration, so I flashed stock 2.1 signapore sbf to see if that changes anything. I heard there are kernel issues if you dont go back to stock. Also memory leaks.
sohrab.naushad said:
Okay, I'm creating this thread so that all users can post their experiences/bugs here because its annoying some of the devs when people post questions in the dev threads. So all you guys like me who need to ask questions or talk about this ROM please post here. I hope they will be kind enough here to answer everyones questions.!
Click to expand...
Click to collapse
Im being an annoying DEV because of morons that post **** like this in a thread about a Deving from 2.1 stock to WanHu's then applying the Deved patches.
Ps..I installed wanhu straight over dex 1.3 and was working perfect straight from the start...or so I thought ...I think cos I used mybackup and saved and then restored "system settings" in the upgrade process.
Im on stock 2.1 and rooted, i use link2sd too. i also see
And on and on.... no relevance.
hellmonger said:
Im being an annoying DEV because of morons that post **** like this in a thread about a Deving from 2.1 stock to WanHu's then applying the Deved patches.
Ps..I installed wanhu straight over dex 1.3 and was working perfect straight from the start...or so I thought ...I think cos I used mybackup and saved and then restored "system settings" in the upgrade process.
Im on stock 2.1 and rooted, i use link2sd too. i also see
And on and on.... no relevance.
Click to expand...
Click to collapse
Relax. He didn't say you were annoying, he respects you guys and doesn't want to annoy you in that thread.
I for one can't wait till you guys get the phone numbers fixed. This rom will rock!
Sent from my XT720 using XDA App
hellmonger said:
Im being an annoying DEV because of morons that post **** like this in a thread about a Deving from 2.1 stock to WanHu's then applying the Deved patches.
Ps..I installed wanhu straight over dex 1.3 and was working perfect straight from the start...or so I thought ...I think cos I used mybackup and saved and then restored "system settings" in the upgrade process.
Im on stock 2.1 and rooted, i use link2sd too. i also see
And on and on.... no relevance.
Click to expand...
Click to collapse
Lol, im sorry but I didn't understand whether you're happy or pissed off about this thread. Hopefully its the former, and thanks again for all the good work!
Just a small update. I was getting really crappy battery life, so I decided to flash the stock singapore SBF and then reflash WanHu's ROM. I took it right from scratch. Root with Universal android root which is so much easier than superoneclick. I tried superoneclick though and it didnt work, maybe because i was trying to do it under MONO in linux. After that I applied the Mioz Patch!
Okay here's where the weirdness starts. First all you guys must remember that annoying ugly korean keyboard and the weird gestures keyboard in the sms, well after the sbf flash my ROM has kept its old android 2.1 keyboard WITH the original haptic feedback. This wasnt there when I flashed directly from the CB froyo. Also Im getting haptic feedback on long touch in the homescreen along with the 4 LED buttons.
Hope this helps. Im going to do some more exploring!
EDIT: Okay so the keyboard is FC on me. It was fine when I was putting in my google info
sohrab.naushad said:
Just a small update. I was getting really crappy battery life, so I decided to flash the stock singapore SBF and then reflash WanHu's ROM. I took it right from scratch. Root with Universal android root which is so much easier than superoneclick. I tried superoneclick though and it didnt work, maybe because i was trying to do it under MONO in linux. After that I applied the Mioz Patch!
Okay here's where the weirdness starts. First all you guys must remember that annoying ugly korean keyboard and the weird gestures keyboard in the sms, well after the sbf flash my ROM has kept its old android 2.1 keyboard WITH the original haptic feedback. This wasnt there when I flashed directly from the CB froyo. Also Im getting haptic feedback on long touch in the homescreen along with the 4 LED buttons.
Hope this helps. Im going to do some more exploring!
EDIT: Okay so the keyboard is FC on me. It was fine when I was putting in my google info
Click to expand...
Click to collapse
I get haptic feedback with long press now over the cbw sbf. And I have 3 and a half out of the 4 flashing led's. I think he said the only thing that won't work without flashing over korean sbf was the tv out. I don't currently use tv out (no cable) but i plan too so can you test this for us bud?
LibertyMonger said:
I get haptic feedback with long press now over the cbw sbf. And I have 3 and a half out of the 4 flashing led's. I think he said the only thing that won't work without flashing over korean sbf was the tv out. I don't currently use tv out (no cable) but i plan too so can you test this for us bud?
Click to expand...
Click to collapse
Sure ill test it out for you in a day or two
sohrab.naushad said:
Lol, im sorry but I didn't understand whether you're happy or pissed off about this thread. Hopefully its the former, and thanks again for all the good work!
Click to expand...
Click to collapse
Nah im not mad Bro, it's a good idea actually
Can you add some screenshots?
Hi there,
I recently bought an used milestone 2. I discoverd that the camera is taking blurry pictures. It seems like that the auto focus is waaay out of focus. I read blogs and solutions for a while now before posting this tread, but without succes. When I bought the phone there was miui installed on it. I figured out that it could be an bug, so I flashed to the stock rom, however, the camera still takes blurry pictures. I have tried almost every possible settings in the camera, downloaded various camera apps, flashed it to the stock rom, but the camera still takes blurry pictures.
Anyone any idea how to fix this ? I have gone through the forum, without any success.
Has anyone got any idea?
SauceBoss7_ said:
Has anyone got any idea?
Click to expand...
Click to collapse
Could it be a hardware problem?
Sent from my MotoA953 using Tapatalk 2
No, I dont think so. The handset is in good condition and everything works just fine. The camera is just way out of focus!
SauceBoss7_ said:
No, I dont think so. The handset is in good condition and everything works just fine. The camera is just way out of focus!
Click to expand...
Click to collapse
If you got stock firmware and did a full wipe data/cache with factory reset, I'd say it's not a software problem, but I'm no expert, let's hope someone comes up with a solution!
I do have the same problem.. Someone told me MS2 users are used to that kind of Problem and it is a hardware bug that happens a lot. You need to get the device repaired to have the camera working again..
(Sorry for bad english)
Sent from my A953 using Tapatalk 2
Seems pretty much like a hw problem.
Sent from my XT860 using xda app-developers app