uncommon 2.2 issues

[Guest gilrad]

After realizing how the original thread just moves too fast to get any decent answers on problems that maybe not everybody is experiencing, I decided to create a thread so we can figure out some of the minor issues that maybe not everybody has or notices.

For me,

-touch screen accuracy. Is it jumpy for other people too? An easy way to test is to very slowly drag the notification bar down. It should move one pixel at a time, but for me, it moves at 3-4 pixels at a time. This jumpiness can cause issues with sliding to unlock, occasionally making swipe-scrolling go crazy, and makes dragging look choppy.

Edit--On touch accuracy

Other people report having the same experience, from 1.6 on to 2.2. So this is likely a non-issue and I for some reason remember it moving smoothly... maybe it was a dream? haha. Of course it could be a hardware difference since there have been people reporting pixel-by-pixel movement. But either way I don't think its something to worry about.

On a side note, if you're having touch screen sensitivity issues (like slide to unlock), try running the calibration utility: start the phone up with the volume buttons held, and select option one (I think it was). From what I have read about, that fixes touch screen issues 99% of the time.

Anyway,

-Memory issues with the home screen. It seems as though the system is rather eager to drop home screen info from the memoy. How about everybody else? When you leave an application, does it take a moment for your widgets to load up, even if the application did barely anything? I also am noticing issues with memory-hungry live wallpapers freezing up when entering the home screen, likely related to memory issues.

edit--On the memory issues

Okay, so I did some fooling around with ads settings, and I found a way to improve performance with widget-heavy homescreens. Under ads settings -> system settings -> check 'make system persistent'. You lose orientation sensing on the home screen, and probably take a slight performance hit, but jumping home is super smooth and probably saves some battery as the cpu isn't reloading widgets all the time.

Feel free to ask about any issues you might be having as well!

Edited October 18, 2010 by gilrad

[Guest fards]

this is an open rom, using available code...

if you're so obsessed over something so minor then fix it yourself!

[Guest popetodd]

Yeah, I've noticed some of my widgets need to be removed and replaced after a reboot.

Also had the phone just shutdown on it's own for the first time ever this eve. Might be the back cover so I gave it a good shove to make sure.

[Guest nickp82]

Err, this isn't an official ROM you know? You're not paying anything for it? Have you even donated? :)

Steve is working on smoothing out all the problems as soon as possible. I think the current performance with this Froyo ROM is excellent and matching other releases for other phones running Froyo. If you can hack Android, try to fix them yourself and contribute back.

Otherwise, feel free to reflash Dell's official 1.6 or 2.1 ROMs...

Your touchscreen problems and memory issues seem to be related to your own phone rather than anything else. No-one I know is experiencing such things.

After realizing how the original thread just moves too fast to get any decent answers on problems that maybe not everybody is experiencing, I decided to create a thread so we can figure out some of the minor issues that maybe not everybody has or notices.

For me,

-touch screen accuracy. Is it jumpy for other people too? An easy way to test is to very slowly drag the notification bar down. It should move one pixel at a time, but for me, it moves at 3-4 pixels at a time. This jumpiness can cause issues with sliding to unlock, occasionally making swipe-scrolling go crazy, and makes dragging look choppy.

-Memory issues with the home screen. It seems as though the system is rather eager to drop home screen info from the memoy. How about everybody else? When you leave an application, does it take a moment for your widgets to load up, even if the application did barely anything? I also am noticing issues with memory-hungry live wallpapers freezing up when entering the home screen, likely related to memory issues.

Feel free to ask about any issues you might be having as well!

Edited October 17, 2010 by nickp82

[Guest popetodd]

Wow fards, I've noticed you are a very touchy person, ready to pounce on any perceived slight.

Relax, you've attacked a few people here already and you were wrong every time.

What makes you think you have picked the right target this time?

[Guest fards]

Wow fards, I've noticed you are a very touchy person, ready to pounce on any perceived slight.

Relax, you've attacked a few people here already and you were wrong every time.

What makes you think you have picked the right target this time?

because SOME OF US are working our guts out to make this work

but hey carry on! :)

[Guest popetodd]

Err, this isn't an official ROM you know? You're not paying anything for it? Have you even donated? :)

Steve is working on smoothing out all the problems as soon as possible. If you can hack Android, try to fix them yourself and contribute back.

Otherwise, feel free to reflash Dell's official 1.6 or 2.1 ROMs.

Sooo, we are to keep our bug reports to ourselves from now on?

I see, yes sir commander sir! The private is sorry that the private pissed on the commanders shoes sir! :)

Edited October 17, 2010 by popetodd

[Guest popetodd]

because SOME OF US are working our guts out to make this work

but hey carry on! :)

And thank you.

But you don't need to be an overbearing jerk about your contribution.

Or is it that you don't want to know about any bugs?

Edited October 17, 2010 by popetodd

[Guest fards]

And thank you.

But you don't need to be an overbearing jerk about your contribution.

Or is it that you don't want to know about any bugs?

I will be exactly how I want to be...

I don't think namecalling is putting *YOU* in a very good light is it ?

Edited October 17, 2010 by fards

[Guest popetodd]

I will be exactly how I want to be...

Of course you will.

And I will be laughing at you for being so.

BTW, my name calling? What, by calling you out for being a jerk?

That's an observation, not name calling.

I can call you names if it will turn you on though.

Edited October 17, 2010 by popetodd

[Guest nickp82]

I will be exactly how I want to be...

I don't think namecalling is putting *YOU* in a very good light is it ?

Just a troll, dude... ignore. :)

[Guest XsCode]

there are people who contribute bugs and there are people who look through previous posts for the answer... unfortunately the latter are becoming VERY rare at the moment. get off your high horse popetodd until you earn the right to sit on it.

And thank you.

But you don't need to be an overbearing jerk about your contribution.

Or is it that you don't want to know about any bugs?

[Guest popetodd]

there are people who contribute bugs and there are people who look through previous posts for the answer... unfortunately the latter are becoming VERY rare at the moment. get off your high horse popetodd until you earn the right to sit on it.

Says who?

You?

Didn't know you were in charge here.

Get a life, the trolls here are the ones having a nut up about nothing (hint: that would be you guys).

Edited October 17, 2010 by popetodd

[Guest XsCode]

I'm sorry??? no I'm not in charge, I'm one of the people who spend several hours of their day on #dellstreak working out how to fix these bugs so that you can have a better phone... If you don't like something about the current rom, and the customer service (customer??) isn't to your liking, go back to O2's 2.1 and see how ofter you get random reboots.

Says who?

You?

Didn't know you were in charge here.

Get a life, the trolls here are the pones having a nut up about nothing (hint: that would be you guys).

[Guest popetodd]

You're not too bright for a smart guy eh?

Didn't say I wasn't grateful, never said I didn't like the rom.

I said that you were being jerks and jumping down this guys (and now my) throat for nothing at all except that you feel like being jerks and are demanding worship and compliance.

But please, do feel free to keep being a self righteous jerk just because you can program. I suppose that somewhere that would warrant worship. :)

Edited October 17, 2010 by popetodd

[Guest XsCode]

You're not too bright for a smart guy eh?

I'm not the one abusing some of the few people who can help you with your problem...

I said that you were being jerks and jumping down this guys (and now my) throat for nothing at all except that you feel like being jerks and are demanding worship and compliance.

Although it might not have been very eloquent, the point being put across was that there are far more pressing problems and starting a new thread when the problem had already been stated (and we do log these problems even if they are not immediately acknowledged) was unnecessary.

But please, do feel free to keep being a self righteous jerk just because you can program. I suppose that somewhere that would warrant worship.

[Guest popetodd]

Well, now, let's answer this one point by point:

1) The people who could be helping are being abusive so they are getting a little of what they (and you) are giving.

2) If it has already been covered then perhaps you Gods of the keyboards should just back off and ignore the thread and leave it to someone else to help these 'lazy' people out instead of popping up and being complete jerks. Unless of course it is just in your nature to be complete jerks, in which case carry on.

I know fards seems to have this problem.

3) Troll, funny. It seems that anyone who challenges you while you are being a jerk is a troll. Go figure.

It appears that the 'uncommon 2.2 issues' are not the actual bugs being reported but that some of the people contributing have no social skills and anger management issues (that would be you guys in case you geniuses hadn't figured that out).

Edited October 17, 2010 by popetodd

[Guest gilrad]

Jesus guys, chill. I just wanted to make things easier for the devs by isolating out the across-the-board issues from the issues that not everybody experiences, so we don't end up reporting bugs that aren't related to the build.

For example, I will now try to fix the sensitivity issue by doing a thorough wipe instead of looking at the wrong places for a fix.

[Guest popetodd]

Not to worry gilrad, fards is just an angry angry person. :)

Best of luck, hope the wipe fixes the problems.

Also be sure to recalibrate the touchscreen, that might fix the accuracy issue you are having.

Edited October 17, 2010 by popetodd

[Guest navrac]

I think the actual OP was not implying any criticism of the work Steve and others are doing. (No offence intended by not mentioning everyone who is working on it - but if I miss one person out who I don't know about , I don't want to offend them)

He actually pointed out that it was getting hard to find answers in the original thread and was posting here 'MINOR' issues that maybe 'NOT EVERYBODY IS EXPERIENCING' maybe 'WE can figure out...'

Which rather implies that he was looking at a community type support arrangement so we could share experiences and how people solved them as they don't apply to everyone and therefore aren't necessarily related to the build. His point was that these are not common problems that the answers are in the main thread as they've been answered over and over again in the main thread. These are the weird little ones that aren't worth clogging the thread up with.

He has a point - there are lots of issues raised in the main thread which aren't related to the ROM at all, the trouble is that if its the first time you see the problem it's easy to assume its the ROM.

Equally when you give up your time doing something which you are proud of, its f'ing irritating to have people going on about minor details, especially when some seem to think they have a god given right to have it perfect for free or a small donation. It becomes easy to assume that all reports of errors are of that type - when some are earnestly trying to help by reporting bugs and others like the OP are also trying to help in their way.

So can we all please calm down, No one is forced to use this rom but equally no one is forced to work on it either - there are enough trolls and genuine whiners out there that if we all took a second to read what people were saying and tried to see their point of view before laying into each other it would be nicer for all of us.

Mind you , it would't be the internet then would it.....

<edit> just seen gilrads second post - apologies for speaking on you behalf - It took so long to write this you posted whilst I was doing it,</edit>.

Edited October 17, 2010 by navrac

[Guest gilrad]

Okay, so I did some fooling around with adw settings, and I found a way to improve performance with widget-heavy homescreens. Under ads settings -> system settings -> check 'make system persistent'. You lose orientation sensing on the home screen, and probably take a slight performance hit, but jumping home is super smooth and probably saves some battery as the cpu isn't reloading widgets all the time.

First post edited with my findings.

Edited October 18, 2010 by gilrad

[Guest cowballz]

One thing i would really.like is for the.colors to be a bit more vibrant, compared to sgs,iphone,ipad and other devices the dell streak has the most washed out screen out of all my devices.

[Guest Dogmann55]

Hi cowballz,

Well i am finding the Streak to have the best screen by far of any device i have used or seen and its much brighter and produces much better colours then my Galaxy S does and by a long way to this is especially true when outside in bright sunny conditions, what setting do you have your screen brightness on? as mine is on the brightest setting as are all of my devices always and the results are nothing short of stunning definitely not washed out at all.

Marc

[Guest gilrad]

UPDATE on the touch screen issue:

Well this is strange. I did a complete wipe, even went back to 2.1 but the low resolution of the touchscreen sensor still showed. If it weren't for the fact that I distinctly remember being able to slowly drag something one pixel at a time (not to mention numerous people assuring me they can do the same), I would think that I am chasing a non-issue here. But just to be certain, if you slowly, barely move your finger at all when dragging, it does move the object one pixel at a time, not two three, or four. Right?

Where could I look for other possible causes? What doesn't get wiped completely when you install a .pkg/update.zip? I really hope its not a hardware defect.

Oh, and after using ADW in persistent mode for a day, I can say battery life and homescreen performance WAS improved. Sure, losing orientation switching is a tough pill to swallow, but its just sooooo smooth now, jumping between the homescreen and apps is incredibly quick and easy.

[Guest Newcron]

UPDATE on the touch screen issue:

Well this is strange. I did a complete wipe, even went back to 2.1 but the low resolution of the touchscreen sensor still showed. If it weren't for the fact that I distinctly remember being able to slowly drag something one pixel at a time (not to mention numerous people assuring me they can do the same), I would think that I am chasing a non-issue here. But just to be certain, if you slowly, barely move your finger at all when dragging, it does move the object one pixel at a time, not two three, or four. Right?

Where could I look for other possible causes? What doesn't get wiped completely when you install a .pkg/update.zip? I really hope its not a hardware defect.

Oh, and after using ADW in persistent mode for a day, I can say battery life and homescreen performance WAS improved. Sure, losing orientation switching is a tough pill to swallow, but its just sooooo smooth now, jumping between the homescreen and apps is incredibly quick and easy.

I'm on stock AT&T 1.6 Streak here. I never paid this close attention to it but after trying what you said to do, the object definitely doesn't move one pixel at a time. The movement is not smooth, it jumps ahead maybe 3-4 pixels at a time.