Related
Can anyone provide a link for the new T-Mobile US rom that was just released?
did you mean http://forum.xda-developers.com/showthread.php?t=636387
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50 .07U_2.08.50.08_2_Ship
please use search button
if you mean newer release please give more version information
Gurgulio said:
did you mean http://forum.xda-developers.com/showthread.php?t=636387
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50 .07U_2.08.50.08_2_Ship
please use search button
if you mean newer release please give more version information
Click to expand...
Click to collapse
The new stock ROM has a slightly different version, but I'm sure is very similar:
2.10.531.1 (82076) WWE
Radio ROM version appears to be the same
2.08.50.08_2
biscuits1978 said:
The new stock ROM has a slightly different version, but I'm sure is very similar:
2.10.531.1 (82076) WWE
Radio ROM version appears to be the same
2.08.50.08_2
Click to expand...
Click to collapse
I'd be interested to see a dump of the actual final ROM, even if there are only minor changes, they could squeeze out a bit of performance somehow.
Is there already one posted somewhere?
I'll dump mine if I knew how . I'll read up.
its so buggy and laggy with only 3 apps running...
and also wondering wth it is when I press the back button fast it corrupts the bottom bar
aswell as loading tons of images it crashes the gallery app....
Yeah, I think this is the one I was after. Is this the final shipped ROM from the US version on the 24th?
death1246 said:
its so buggy and laggy with only 3 apps running...
and also wondering wth it is when I press the back button fast it corrupts the bottom bar
aswell as loading tons of images it crashes the gallery app....
Click to expand...
Click to collapse
Yeah this is pretty bad-- I've had the phone for just two days now, but it's lagging all throughout, I can't run more than a couple of apps without major slowdowns, and even with no apps running and a fresh boot, it has issues.
It can't even play the Transformers movies that came with the phone without stuttering.
Earlier today, the volume rocker stopped working and somehow turned into a scroll wheel (it'd slowly move up and down in whatever was selected instead of adjusting volume).
The phone also has lots of issues where it won't come back after the screen is turned off (or will take 30 sec or more), and it seems sometimes the bottom buttons just don't work, or something freezes up. Then for a while I wasn't able to call anyone-- I could get into people's profiles in contacts, but tapping on the phone number would do nothing. It's also locked up on a few occasions while showing that services.exe or other processes crashed.
Also, not sure how related this is to the ROM, but I have voice quality issues-- people on the other end report hearing lots of background noise even in relatively quite environments, and to me they sound a bit muffled / put through a cheap speaker.
In any case, this is not a ROM anyone would voluntarily want to put on their phone.
Hi Does anybody know where the HTC HD2, TMO-US 1024 GB version "2.10.531.1" ROM is???
Will this ROM work on my T-Mobile HD2 from Germany with HSPL2 installed?
HD2 Freezing issues...
amb9800 said:
Yeah this is pretty bad-- I've had the phone for just two days now, but it's lagging all throughout, I can't run more than a couple of apps without major slowdowns, and even with no apps running and a fresh boot, it has issues.
It can't even play the Transformers movies that came with the phone without stuttering.
Earlier today, the volume rocker stopped working and somehow turned into a scroll wheel (it'd slowly move up and down in whatever was selected instead of adjusting volume).
The phone also has lots of issues where it won't come back after the screen is turned off (or will take 30 sec or more), and it seems sometimes the bottom buttons just don't work, or something freezes up. Then for a while I wasn't able to call anyone-- I could get into people's profiles in contacts, but tapping on the phone number would do nothing. It's also locked up on a few occasions while showing that services.exe or other processes crashed.
Also, not sure how related this is to the ROM, but I have voice quality issues-- people on the other end report hearing lots of background noise even in relatively quite environments, and to me they sound a bit muffled / put through a cheap speaker.
In any case, this is not a ROM anyone would voluntarily want to put on their phone.
Click to expand...
Click to collapse
I am having the exact same issues as you with the phone freezing when locked down as well as unable to make calls from contact lists or even ending calls from the "end call" on screen button. By any chance did you find a fix to this? The new ROM did nothing for me.
actually t mobile usa should had sent you a new message a few days ago for the update. its confusing because its all the same version package, just fixed these issues. i hated the first update, and i started myself because my graphic's driver was laggy and the touch controls were not usable. I installed this new one, and its fine!! not a problem yet!!!
Hi guys, i have a weird issue with this rom, i've been using it for like 4 days now, but lately i've been getting random reboots, this happens when the phone freezes up out random, it shows the battery icons with a ? mark and the phone responds to volumen up and down commands but thats it, also the screen and the capacitive softkeys stop working when this happens to, and when i press the power button it restarts its self, i've alrdy wipe data+dalvik+cache and nothing the device keeps on behaving the same, im about to just re-flash the rom, from my acer s200 experience, acer phones tend to have random isolated issues to specific devices/hardware, and mostly these issues are hard to reproduce, anyways i might re-flash the oem rom today, il see if this fixes it or if its just another issue that the rom it self has, as its a beta release, any suggestions will be great appreciated.
edit: i have reflashed 10000 times it still does it, my last option would be to flash 1.6 but meh i like 2.1 better =]
hic, can u help me up rom acer liquid from 1.6 to 2.1 thanks .
It's most likely the ROM, but, still could be the kernel. I have been using the rooted kernel only, nothing else. Actually some lowmemkiller settings. I was not able to test if removing the threshold settings (I forget what the other thing was too) before I sold Liquid.
I can report bad use of the digital compass, when in navigation with google maps or (f.e.) copilot 8.
Gps receiver says that i'm going forward, but digital compass says that i'm going backward.
Stupid compass
Yes, I have the same issue in Navigation. The compass is fine in Google maps app though
Hi all,
I've been trying not to let this bother me too much but it just does. Why, when we've come so far with mobile technology, are basic things like this still not done properly?! specifically:
1. my hero doesn't actually start ringing for at least 3 rings on the callers side? this it might not seem much but is almost 10 seconds that the caller is waiting before I know about it. By the time I do and get to the phone I will almost miss the call.
2. this may be a handcent problem but I don't get the trackball flashing 2-3 seconds and the actual audio notification for 5-10 seconds.
-
l just want these things to feel instant and zippy. Is that too much to ask? I don't think so considering this handset can show me which constellation I'm looking at and that there is a 'titty/tapas bar 500 yds that way'.
Is there anything I can do to improve these fustrations?
Don't get me wrong, I think the handset is generally great but don't want a 'Jack of all trades, master of nothing'.
R,ant over.
Orangepeel.
Sent from my T-Mobile_G2_Touch using the XDA mobile application
powered by Tapatalk
Hi,
I get the same problem with my phone not registering a call for atleast 10 seconds and usually missing calls, it's very annoying!
Something I've found that helped me was to prolong the time it takes before the caller is sent to your voicemail i.e. your phone SHOULD ring for longer before the caller gives up...
Search the forums for the code you need to enter to prolong the time period (I think it's 30 seconds).
Hope this helps...
It depends on the rom your running.
For example the latest VillainRom rings instantly now but always used to be quite delayed.
the handset is very well aware of the incoming call, it just takes a few seconds to ring and display the call. when you are listening to music you will notice that it stops, then after a few seconds it will start to ring. try to use .ogg ringtones, apperantly that makes it better.
Lennyuk said:
It depends on the rom your running.
For example the latest VillainRom rings instantly now but always used to be quite delayed.
Click to expand...
Click to collapse
I'm using Modaco 3.2 and have always had this issue since upgrading from the Stock rom months ago!
Are you saying that the latest Villain ROM (based on 2.1) fixes this issue?
So in theory this problem should be rectified once 2.1 is officially released??!
bunt83 said:
I'm using Modaco 3.2 and have always had this issue since upgrading from the Stock rom months ago!
Are you saying that the latest Villain ROM (based on 2.1) fixes this issue?
So in theory this problem should be rectified once 2.1 is officially released??!
Click to expand...
Click to collapse
yes it seems to be fixed in VillainRom 5.2 or its certainly a lot better than it was.
This fix was something the Dev (Nathan) did I think so official 2.1 may still have the problem
Lennyuk said:
yes it seems to be fixed in VillainRom 5.2 or its certainly a lot better than it was.
This fix was something the Dev (Nathan) did I think so official 2.1 may still have the problem
Click to expand...
Click to collapse
Interesting!
I guess I'll wait until 2.1 is released and see if that fixes the problem otherwise I'll be switching to the Villain ROM based on the official 2.1!
Cheers for the info Lenny...
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
CodeMonk said:
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
Click to expand...
Click to collapse
Just go back to 2.0d. I ran 2.1.2 for a very short time and I couldn't take it anymore plus you know that the sprint 2.1 has confirmed issues one of which is the sdcard
Where can I get the original 2.0d now? Can someone post a download link to it please? I'm also experiencing a lot of lag these days as well..
Here's a quote from Fresh Toast v2.1:
A note on slowness: It is coming to our attention that there are several bugs in the latest Sprint 2.27.651.5 RUU which is the official Sprint release. It doesn't surprise me that there are bugs considering our original 1.5 had plenty. The main one that we have come across is a service called com.htc.bg that sucks up your processor. This causes that phone to become extremely laggy and overall run like crap. Go read my new FAQ: Why is my Android phone running so slow? to see what you can do about it, and to report the issue. Keep in mind that this would be a Sprint bug and not Fresh Rom / Fresh Toast.
Click to expand...
Click to collapse
I think this is why we're experiencing lag, hopefully someone can find a fix for it..
EDIT: Nvm, found the link, here it is:
http://geekfor.me/new-release/fresh-20d
I think you guys are right. I've been toying with the idea of using Fresh Toast to get overclocking, but 2.0d just worked for me and I had no real issues other than keyboard lag.
Are you guys running w/ Auto Killer (or alternative TK) or no? I've been running FT w/ AutoKiller set to Extreme, with max time between boots having been about 48 hours, and haven't seen any significant slowdown the longer the phone's been on..
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.