Related
I'd be interested to see how many of us upgraded rom on new Pure.
Which rom you used, performance improvements, battery life, problems etc.
Did you back up stock rom?
Andy
I'll usually run the stock rom for a few weeks then start playing. I'll be watching this thread!
What I have noticed is that on a lot of the popular roms, you'll see things like "landscape/rotate will not work", or you will see nary an ATT person in there, but lots of euro TD2 owners, etc.
I have the WWE AT&T Pure and had it stock for about 4 days and decided to flash to !Amen!'s R5 Ultimate ROM which had the new TouchFlo 3d 2.5 Leo interface. As much as I liked the new interface it was sluggish and I had a few bugs that kept me from liking it a lot. I then looked into "TESS's 3.6 WinMo 6.5 TouchFlo 2.1" ROM and switched to it and haven't looked back. It's coupled with the new radio and all it's signal goodness. I have had no issues with this rom and have thoroughly tested everything from data, tethering, bluetooth file transfer and stereo profiling, wi-fi strength and connection, gps, overall interface response time, multitasking, and video playback to the kicker -the battery life (which I am reporting is excellent, a full day of heavy use and it's at a little over half battery). All worked and I am proud to bring you the good news that if you are looking for a solid ROM to flash to then head to TESS's release thread for info. on his ROM and it's glory.
flashed my pure to energy ROM within 30 minutes of getting it, so while i cant comment on battery life, speed and stability is much better.
did the new rom affect your ability to use 3g?
gmarcoux said:
did the new rom affect your ability to use 3g?
Click to expand...
Click to collapse
ROMs do not affect the radio so AT&T 3G will still work. Flashing a Radio would probably not change it either since the bands are in the chip and changeable by software. But don't take that last part for fact.
I have a Pure...running the latest stock htc Euro WWE 6.1 ROM until the official htc 6.5 ROM is out. Good Lord, when will it be here? I tried the official 6.5 ROM on my Touch Pro 2 and WOW!
FWIW, I noticed that I know have an H instead of 3G in the signal indicator. The AT&T ROM is so full of crap I just couldn't stand it. I am not big on cooked ROMs because there always seems to be something that bothers me...
Had my Pure for over a week now, played with stock ROM for only about half a day before replacing it with a cooked one. Tried multiple ones during my past week and here's my findings:
- Dutty's R4 (and R5) [WM6.5/Manila2.5]: The first one flashed to replace AT&T stock ROM, I really liked it for almost all the aspects. However, push mail sometimes does not push (which happened to Dutty's ROMs on my Diamond as well before) so I have to give it up.
- EnergyROM Leo [WM6.5/Manila2.5]: Pretty fast and stable, but the interface is not my cup of tea, and battery drains pretty fast on mine, so this one didn't stay too long.
- Tom Topaz Leo R2 [WM6.5/Manila2.5]: Very nice ROM, stable and fast, close to stock ROM in terms of interface (not too many customizations). Quite similar to Duttys but without the push mail issue. Battery life seems to be fair. This is the one I'm staying with.
- TESS 3.6 [WM6.5/Manila2.1]: A lot of people says it's good but didn't appeal to me. Forgot what was the exact issues but there were a few, so it didn't stay too long on my Pure.
- Nataly 3.0 [WM6.1/Manila2.1]: A very nice ROM, super fast and clean, just that it's a 6.1, I do prefer 6.5, so I switched back to Tom's ROM. But after a days use of this ROM, I liked its simplicity and performance. I'll probably try it again once the 6.5 version is released. Battery life is said to be super on this one but I didn't have enough time to test out. From my one day's experience it seems to be pretty good.
jimanywhere said:
Had my Pure for over a week now, played with stock ROM for only about half a day before replacing it with a cooked one. Tried multiple ones during my past week and here's my findings:
- Dutty's R4 (and R5) [WM6.5/Manila2.5]: The first one flashed to replace AT&T stock ROM, I really liked it for almost all the aspects. However, push mail sometimes does not push (which happened to Dutty's ROMs on my Diamond as well before) so I have to give it up.
- EnergyROM Leo [WM6.5/Manila2.5]: Pretty fast and stable, but the interface is not my cup of tea, and battery drains pretty fast on mine, so this one didn't stay too long.
- Tom Topaz Leo R2 [WM6.5/Manila2.5]: Very nice ROM, stable and fast, close to stock ROM in terms of interface (not too many customizations). Quite similar to Duttys but without the push mail issue. Battery life seems to be fair. This is the one I'm staying with.
- TESS 3.6 [WM6.5/Manila2.1]: A lot of people says it's good but didn't appeal to me. Forgot what was the exact issues but there were a few, so it didn't stay too long on my Pure.
- Nataly 3.0 [WM6.1/Manila2.1]: A very nice ROM, super fast and clean, just that it's a 6.1, I do prefer 6.5, so I switched back to Tom's ROM. But after a days use of this ROM, I liked its simplicity and performance. I'll probably try it again once the 6.5 version is released. Battery life is said to be super on this one but I didn't have enough time to test out. From my one day's experience it seems to be pretty good.
Click to expand...
Click to collapse
Which HardSPL did you use to flash the ROMS?
on this one Topaz-HardSPL_V5_00R5_183HSPL my AV shows a virus and deletes it
I used the stock ROM for about a day, but like most everyone else, I don't like all the extra junk that AT&T puts in there, so I flashed right away. I first used the EnergyROM Leo, liked it well and may go back to it. However, after reading the benchmark spreadsheet, I decided to give Dutty's R5 a try, and have been happy with it. I like the eye candy look of the EnergyROM better, and generally, I can't tell much difference in speed between the two, though Dutty's benchmarks much faster.
Strangely, I found that the stock AT&T ROM was the most error-prone. I got a lot of Windows error messages (shell32.exe, I think) with it. I've managed to lock up both EnergyROM and Dutty's here and there.
I can't say much about battery time at all.
eltoro said:
Which HardSPL did you use to flash the ROMS?
on this one Topaz-HardSPL_V5_00R5_183HSPL my AV shows a virus and deletes it
Click to expand...
Click to collapse
There are no viruses at all. Just turn off you AV and DL it. Do you have Norton? For some reason Norton sees it as a virus a lot. AVG did not for me. But there is no virus. Or I'm sure there would be hundreds of angry TD2 owners and you woulda heard about it.
HTC Touch Freak said:
There are no viruses at all. Just turn off you AV and DL it. Do you have Norton? For some reason Norton sees it as a virus a lot. AVG did not for me. But there is no virus. Or I'm sure there would be hundreds of angry TD2 owners and you woulda heard about it.
Click to expand...
Click to collapse
Thanks for replying, and you are right I've Norton.......I'm going to try later... Cheers
Tried just about every rom available: energyrom, Showdowline's, Dutty's, and TESS rom. Out of all of them the TESS rom drains my battery the least and is still the most quick in response and rarely locks up or lags. The others have manila 2.5 and I just don't think the pure can handle it unless htc or att comes out with their own version for the pure/td2.
Ahh I can't wait until I get my Pure and start crankin out builds.
HTC Touch Freak said:
Flashing a Radio would probably not change it either since the bands are in the chip and changeable by software. But don't take that last part for fact.
Click to expand...
Click to collapse
What do you mean "bands changeable by software"? If I'll install radio from Europe, will HTC Pure start support European 3G?
AT&T Pure results
I've had pretty good success with several of the most popular ROMs on the AT&T Pure, including TESS, Dutty, X-Treme2.V5, and some of the less popular ROMs too.
What I've found, though, is that in many of these ROMs there is a dialer glitch and a close-button glitch that probably is unique to the Pure.
The dialer glitch: When a voice call comes in, it seems that a third of the time, you cannot use the slider to actually answer the call. And when the call does answer, there is major lag between sliding and answering. I have no idea what causes this, but I've been looking for a ROM that doesn't have this glitch and haven't found one yet.
The close window glitch: This might or might not be unique to the Pure, but in a lot of ROMs, the close-window X in the upper right corner has a graphical glitch. When pressed, the highlight graphic actually appears to the left of the button, rather than beneath it. This is not a functional issue; it's an aesthetic one. But it crops up a lot in the ROMs that I've tested.
I also installed a reduced AT&T Pure ROM listed in another thread, but that was a work in progress and had broken aliases scattered around. I actually like the blue AT&T Pure interface, and I'm hoping that somebody will take that stock ROM and do a nice speed customization with it to cut out the bloatware and make it more responsive.
coldcarbon said:
When a voice call comes in, it seems that a third of the time, you cannot use the slider to actually answer the call. And when the call does answer, there is major lag between sliding and answering. I have no idea what causes this, but I've been looking for a ROM that doesn't have this glitch and haven't found one yet.
Click to expand...
Click to collapse
If it's anything like the prior gen diamond for ATT, you will want to find a rom WITHOUT a slide to answer add on.
They were 100% not compatible with the phone, and did exactly what you described.... well if it even connected the call after waiting a while.
Most of those rom cookers are aware of the problem with the prior gen, maybe if you are having a problem, mention it AND mention you are on ATT. Looks like history is repeating itself.
syntrix said:
If it's anything like the prior gen diamond for ATT, you will want to find a rom WITHOUT a slide to answer add on.
They were 100% not compatible with the phone, and did exactly what you described.... well if it even connected the call after waiting a while.
Most of those rom cookers are aware of the problem with the prior gen, maybe if you are having a problem, mention it AND mention you are on ATT. Looks like history is repeating itself.
Click to expand...
Click to collapse
Intersting. But isn't the slider the default for all dialers in Manila/Sense? This means I would have to go to Titanium to avoid this bug I guess -- unless there's some dialer mod that can patch a Manila/Sense slider. All the Manila/Sense ROMs I've tried have had this slide dialer.
Oh, and by the way, it's not just the slide itself that seems to be causing the problem. Actually pressing the physical send/talk button has the same effect when answering a call. That is, about a third of the time, it won't actually answer a call at all, or does connect but only after lagging for four or five seconds. Really annoying stuff.
Ths send/talk button issue might be related to the dialer glitch you're talking about, but I haven't done any testing with a dialer that doesn't use the slide-to-answer. Haven't seen a ROM that doesn't have the slider in the dialer.
Yup in my prior gen case, it was also the physical buttons. Sounds exactly the same!
The ONLY one that would work was a stock ATT diamond rom that someone took the bloatware out of, and left the stock answer buttons.
Is the slider modified in any way in each of these roms?
Do they use another slider in place of the manila slider?
Usually they give a list of the oem rom and the added or modified applications.
Sometimes, and actually a lot of times, they base their work on a euro rom version and call it WWE, that may not have the right drivers or whatnot for the ATT specific hardware.
It really does sound like the same issue all over again. But I'd ask in each of the rom threads and hopefully you'll get a quick answer!
Just finished some testing on Dutty's new Holy Grail ROM, and the results are good. Called my phone 20 times, and answered with the slider 10 times and send/talk physical button 10 times. All slides/presses connected the call immediately with no lag whatsoever. So unless my sampling is too low to be conclusive (perhaps the glitch will kick in less than 10 percent of the time) I think this is the ROM I will use for now.
Unfortunately, the graphics glitch with the close button (the highlight occurs to the left of the X rather than beneath it) is in this build. Plus, the built-in version of Bing doesn't work/launch. But these are small sacrifices to pay for a great all-around ROM that actually answers calls when you press the button or move the slider. Woot!
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..
Hey guys.. I love Android. I've ran so many different rom's and CM6 Nightly's n such on my Nexus One and I really love the phone. I love this HD2 also tho.
I've been using the HD2 with DarkStone FroYo for the last 10 Days or so. I must say I LOVE the HD2. It's a great phone, I love the screen and it's size, but hard buttons all being one piece of plastic was a bad move but thats about it.
Basically here's my issue. I have screen freezes that are a few seconds, or up to 10 allll day long. sometimes it will freeze and wont go into sleep mode for up to a minute (at least a few times a day) I lose my Data signal at least 10 times a day also. Sometimes it comes back, other times I need to Toggle Airplane on/off and my signal will come back.. Basically it's very smooth and awesome, then just craps. and this is extremely often and very random and it's starting to get very irritating. I wanna go back to my Nexus. I've also tried SkinnyEVO and had similar problems.. Are there any ROM's that are smoother and more stable, screen freezes and data drop-outs are really starting to irritate me knowing I wouldn't have these issues on my N1.
Should I wait for Nand to get going, should I try a few more ROM's. Is there fixes for these issues? Any info or suggestions would be great. I'd love to use this for a Daily phone, but in the current state it's a hard call.
Man Try MCCM 1.6 with updating kernel hastarin 8.5
it doesn't freeze at all.
everything work no bugs at all.
camera with zoom , face detection.
it is an awesome build
which radio u have and wim mobile u got ?
Darkstone has not updated his build for quite some time. Definitely try an updated build with latest kernels before giving up on the ole HD2. The touchscreen freeze has been eliminated with the newer kernels. I've been using the Motodroid build which has very good performance with the best working camera; no green tint, full 5 mp with working wide screen mode and shutter sound is selectable (which I have not found in any other build).
I don't know what MinMo build. I'll check, but I have the latest Kernel for the HD2. Kernel 2.15.50
I'll check what WinMo after work. Thanks for posts. I'll report back later
Do try a newer build, like the others said. I upgraded mine to hdone and replaced the kernels and i have yet to have my phone screen freeze. When i was using every other build with the old kernals, it froze all the time. Don't give up on your hd2 yet!
I think you have hit on 2 major issues the first screen freezes has been pretty much solved with the latest kernels with the g sensor fix. So try Hastarins 8.5 or mdeejays latest.
Second the data problems still exist but has been much improved with Letamas Ril Wrapper and other ppp tweaks ,see Letamas thread. if you try one of the newer roms they might have all above already in, so worth a try before going back to nexus.
I've been following Android on HD2 since August, and I've gone from all your problems and more to almost none (touch wood: my phone has begun to freeze today after three weeks of no problems - I'm hoping it's an installed app issue).
They are getting better and better and it's only battery life which remains an issue (for me).
Everyone's going to have different results depending on Radio/Location/Operator, but personally the MDeeJay Sense Revolutions (both types - Froyo and his other one), have worked very well for me, on Energy ROMS (currently the barebones one).
I can't promise Android on HD2 will always be flawless, but your two biggest gripes are certainly solvable on the right combination. (I hope!)
Change your SD card to a Class 6 and let us know.
Give up on the HD2, go back to the Nexus, send me your HD2
Scan my signature for my setup - I find it the best after changing at least 15 builds, 7 WinMo ROMs and 4 different radio combinations.
PS I am really stubborn guy, so that tells you that I've tried all possible combinations with above count of builds, roms, radios - and so far this one gives me what I want: HD2 with the Build that is smoothest and more stable than any Android phone I played around with so far... including nexus one
Thanks for all the information posted here guys. I appreciate it. I'll try mdeejay's latest and see how things go. (all of mdeejay's are Sense UI) I want stock Froyo
Another question. Can I copy everything from my Android Folder, to a New Android Folder for the new ROM I'm about to try, and have everything be exactly how it is now on DarkStone, or will that not work?
xguntherc said:
Thanks for all the information posted here guys. I appreciate it. I'll try mdeejay's latest and see how things go. (all of mdeejay's are Sense UI) I want stock Froyo
Another question. Can I copy everything from my Android Folder, to a New Android Folder for the new ROM I'm about to try, and have everything be exactly how it is now on DarkStone, or will that not work?
Click to expand...
Click to collapse
Titanium backup is your friend there. google for the wiki and read up on how to backup and restore.
Oh and if you don't like Sense, that's fine, just install whatever launcher you want, press the home button and it will ask you what launcher to use, tick the box for "use this by default" and sense won't come back to bug you. You can also remove the lockscreen slide by deleting the "HTCLockScreen.apk" via adb.
Just also to backup what others are saying, later builds like the one in my sig are far more reliable and useable, I get no data drops or any of the other problems you experience currently.
I know how titanium and all that works, thanks for trying to help though.
I just figured since everything is in the Android Folder, couldn't I copy it to another Android1 folder and boot to that build, and everything be there. but if not. It's ok. I'll just titanium backup everything instead.
I'm thinking about trying out BiffMod 1.2
xguntherc said:
Hey guys.. I love Android. I've ran so many different rom's and CM6 Nightly's n such on my Nexus One and I really love the phone. I love this HD2 also tho.
I've been using the HD2 with DarkStone FroYo for the last 10 Days or so. I must say I LOVE the HD2. It's a great phone, I love the screen and it's size, but hard buttons all being one piece of plastic was a bad move but thats about it.
Basically here's my issue. I have screen freezes that are a few seconds, or up to 10 allll day long. sometimes it will freeze and wont go into sleep mode for up to a minute (at least a few times a day) I lose my Data signal at least 10 times a day also. Sometimes it comes back, other times I need to Toggle Airplane on/off and my signal will come back.. Basically it's very smooth and awesome, then just craps. and this is extremely often and very random and it's starting to get very irritating. I wanna go back to my Nexus. I've also tried SkinnyEVO and had similar problems.. Are there any ROM's that are smoother and more stable, screen freezes and data drop-outs are really starting to irritate me knowing I wouldn't have these issues on my N1.
Should I wait for Nand to get going, should I try a few more ROM's. Is there fixes for these issues? Any info or suggestions would be great. I'd love to use this for a Daily phone, but in the current state it's a hard call.
Click to expand...
Click to collapse
You need to change you're SD card. I had gone through the same problem with A-Data class 4 sd card...but large waking times randomly spoiled the whole android experience....so much so that I gave up android...
But ever since I went back to replacement 16GB samsung SD card (which is ironically class 2) things have improved...and the phone wakes up instantly..
Also upgrade the kernel to hastarin v8.5.1 of ur build..it just solved all Data issues for me..maybe it will work for you too
I'm using the stock 16GB Class 2 Samsung that it came with. I have a 16GB Class 10 in my Nexus if we want to compare. but I'm not sure how large the SD class will really change things. Maybe a little.
I came to the HD2 from a Nexus.
I love my nexus... but wanted a larger screen.
Originally I had all the issues you commented... Id already sold my N1 so I really had to work on the HD2 working how I wanted it.
After flashing different roms, radio's, androids and kernels Ive finally landed where I am happy and in just the recent weeks with the tweaks the devs have done to their kernels my phone is rocketing and would never go back...
Only thing I do miss is the trackball and its colored notifications.
OP, you asked about overwriting your files, here's what I did...
I backed up my whole SD Card to my PC, so that I had my full working phone backed up just in case.
I then overwrite the contents of my old Android build with my new Android build, ignoring the data.img file.
Then re-booted, and Voila! EVERYTHING (apps, settings, wallpapers etc) came back, but my ROM was faster and smoother and upgraded.
This was switching from one ROM-maker to an entireley different one (both were Android 2.2 though).
If this had failed, I could have wiped my SD card, and made a choice between trying a fresh new Android, or using my SD Card back-up. If I'd had to go fresh, I'd know my Google Account would hold my contacts and purchased app settings. The AppBrain app is also useful in this regard.
Have fun!
im in a similar situation. i got me a secondhand nexus one, to try how android runs on a native device. i walked around with it for some days now, and i think im soon going back to my hd2, cause I CANT GET USED TO THE SMALL SCREEN ON THE NEXUS XD
really. not.
android on the hd2 runs almost as smooth as on the nexus one, i dont even cared in choosing the right build for my hd2, i just picked froyostone, and thats it xD
so yea, in the end, the only thing i really love on the nexus one is the awsome trackball, with its different colours :3 omg i want that on my hd2... ;(
i was having the freezing problem when i was using energy rom with the stock sd card when i flashed to the newest tmobile rom all of my freezing went away so if you have that problem try the newest tmobile rom it worked for me
Hello everyone, I'm having a few problems with eb13 I havnt seen in any of the bug threads, forgive me if I overlooked. But anyway, compared to di18 the dropdown notification bar is very stuttery and laggy whenever the menu is slid down. I'm also seeing a touchscreen responsiveness delay in any scrolling menu. The fps of the scroll is fine but it seems to take the epic a half a second longer to relize that your finger has moved on eb13. I have flashed the new rom every possible way, odin, samsungs exe, update.zip from di18. It also applies to every eb13 custom rom I've tried so far as well as the stock rom, but not the miui rom or cyanogen beta1. I'm just curious to see if anyone else is seeing the same problem as me or if its just my phone. Thanks for any input, this is driving me crazy.
Sent from my Samsung-SPH-D700 using XDA App
I'm not having this problem. Currently using supernova with ext4. Wasn't on stock long enough to test it.
Zoen22 said:
Hello everyone, I'm having a few problems with eb13 I havnt seen in any of the bug threads, forgive me if I overlooked. But anyway, compared to di18 the dropdown notification bar is very stuttery and laggy whenever the menu is slid down. I'm also seeing a touchscreen responsiveness delay in any scrolling menu. The fps of the scroll is fine but it seems to take the epic a half a second longer to relize that your finger has moved on eb13. I have flashed the new rom every possible way, odin, samsungs exe, update.zip from di18. It also applies to every eb13 custom rom I've tried so far as well as the stock rom, but not the miui rom or cyanogen beta1. I'm just curious to see if anyone else is seeing the same problem as me or if its just my phone. Thanks for any input, this is driving me crazy.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
im not getting alot of panning lag. Seems the same as eclair. But the stop down drawer is jerky and stutters alot. Eclair was very smooth, don't know why froyo does that. I mentioned it several times when the initial leaks were available. Pretty much ppl said that its beta so most likely it will be better on the official release. Well... Here we are.. Still jerky.
ever since eb13 I have noticed way too many fingerprints on my screen
Nope. My phone flies. Running SuperNova w/ Gingerbread theme on EXT4.
both of those issues seem to me to be the difference between a set rate or maybe a couple that the dropdown and the app list move at... on DI18. It seems froyo is more responsive to what your finger actually does, than just go 'ok, drop down at X rate'... could be just me... most roms I have tried are awesome that way... I like that its really responsive.... like the dropdown for example, if you slide your finger up 1/3 of the way, if follows the speed of your finger, pull away at that point and it continues at a set speed... I kind of like it... it seems like the stutter is where your finger leaves the screen, if I go all the way to the top, as fast at I can with my thumb in a normal grip on the phone, it does seem like it could use some framerate, or maybe its hitting little increments along the way... idunno... I like it better to be able to throw it up there fast than watch it nice and smoothly take a second.
for the record, on midNIGHT ROM, Genocide Kernel, 200-1200 on SetCPU, conservative scaling- dont remember stock EB13 being too much different in this particular case...
While I don't seem to get lag when scrolling, when it's not plugged in, it does take a second or so for the power button to register a press and wake the phone up.
Oddly enough, when plugged in, it turns on instantly.
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?