Database Develop

Did froyo fix the crazy screen bug?

Is it me, or did froyo fix the "crazy screen" bug? I also noticed that my phone doesn't get as hot when it's been charging on my car dock.

I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.

lorin.bute said:
I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.
Click to expand...
Click to collapse
This, and I'm on FRF85B

Gotta be the best part of froyo for me, crazy screen bug fix, flash player, Jit compiler.

Which crazy thing happening are you guys screaming about? Are you talking about when the touchscreen would begin to register touches in the wrong place until the screen is turned off and on again?

Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.

RogerPodacter said:
Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.
Click to expand...
Click to collapse
Funny thing is that I had those issues on an AT&T-banded phone and they have gone way downhill since Froyo.

I find the granularity/preciseness of the screen better, and more responsive when, for example, you are dragging left-to-right and you start dragging up-down. However, I only do this in the browser so it could be down to better browser performance and/or JIT?
Still have screen uncalibration issues but seem to be better in 85 than 72

Does indeed seem to be a thing of the past, and on a similar note, it's improved the capacitive button accuracy as well.
Good that they've done it, but now I keep hitting them in the wrong place.

I'm using FRF91. Crazy screen bug happens with me twice a day. I don't know what I do to go away, but after a few minutes it stops by itself.

Ok I have been noticed a new problem for the past few days where the screen did not response at all when I turned on the phone. I cannot slide the unlock bar to unlock it. I had to turn it off and on again for one or two times to make the screen response again. Anyone else having this same problem?

Crazy screen occurrence definitely reduced.. however, it still happens when phone heats up significantly.. say, on a dash board while navigating. It's most definitely heat-related... so it must be hardware =(

I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.

vzontini said:
I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.
Click to expand...
Click to collapse
I've had the N1 since day one and never had this bug. But I don't use Skype...

Problem with Notification Bar.

I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)

Where do you live? I live in florida, and this happens to me when I'm outside for an extended period on a really humid day. Once I take it in to the ac for a few, it's all ok.
Sent from my HTC Hero CDMA using XDA App

Louisiana. Doesn't seem like that would be it though. My wife has the same phone and has never experienced this problem (she has OEM 1.6 version). I am leaning towards software issue.

mar122999 said:
I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)
Click to expand...
Click to collapse
You posted this in the wrong forum
Anyway, it could be a hardware problem, but it sounds more like a software issue. Sometimes this happens to me when the phone slows down. Are you low on RAM when this happens?

Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?

mar122999 said:
Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?
Click to expand...
Click to collapse
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.

derekwilkinson said:
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.
Click to expand...
Click to collapse
+1
when i had one on my phone it would do this. i think its static tricking the touchscreen.

NeoFroyo!! Well testing

hey guys!
Well i was trawling the android forums and found this!
http://www.neopeek.com/viewtopic.php?t=7524
All thanks yo neopeek for the rom.
I decided to test it out on my kovsky. This coupled with I believe duckkly's kernels worked like a charm!! ill post the kernels up here too as I experimented with quite a few to see what worked best!
Battery life: 8 hours on full blast so i rekon around 11 on normal usage
Wifi: never ever ever dropped on me so far! thou it does seem to be weak in some places around my house where i usually should be getting more signals and strong at places where i get little signal :S.confusing
phone: well calls come in and stuff but sometimes ull see a black screen and cant see who's calling! :S
Bluetooth: paired with my mw600s just fine dont know about file transfer
market:works just fine a bit slow though..could be my internet speeds out here in pakistan.
Apart from that using whatsapp like a charm. facebook apps. gaaps everything works!! not a single sod to date been using it for around about 5 days or so.
Sorry for the spelling errors! big thanks goes out to neopeek and duckkly or whoever compiled those kernels !
PS: oh and the keys will freeze up as you hit around 20% battery. I simply reboot. Also terminal doesnt seem to be working. keeps crashing on me but i dont really ever use it in daily use so it seems to be pretty stable apart from these flaws. Also you'll need to reinstall quickpic from market
Also im on radio 1.16 i believe. 1.14 seemed to drop calls randomly.
please read all of neopeek's instructions before flashing ! happy flashing

can't confirm 20% battery being the point where keys stop working. for me 4 hours of uptime seems the be magic point...
i stopped restarting modules via script (how to has been explained many times in here) and simply restart. most of the time it happens when an app is running - now what good is it if you have a shortcut somewhere, but can't get there because back- and home-key isn't working?!
but yeah, neofroyo is a big step forwards. first time using android on x1 is fun!
for terminal to work you have to reinstall it just like quickpic.
i just hope we'll see some kernel-update soon. without it the whole thing is pointless.

lol truee..thanks for the terminal update. oh if u press the camera button it will take you back to your home screen. than i guess u could load the keyboard modules..annoying i never bother with it. try my combination of kernel it gives me decent battery lifee but yea its the kernel with all the problems. tried the new kernels but they dont seem to work properly

hm, which kernel-version is that?
might try if i know which it is. just had to step down from ygge-monster to ygge-turbo. monster made my touchscreen getting unprecise in left half.
thx for the update with cam-button - never bothered to press that, since camera doesn't work anyway.
yeah, new kernels suck for our device, especially since they're missing the specific battery-driver for x1. the only guy still working on x1-kernel has been silent for months, but i can see he's still at it (porting 2.6.35.7).

Just tried pressing cam-button.
Falls back to lockscreen, after unlock shows homescreen. But system is frozen and after some time reboots directly to android. But lots of stuff doesn't work, especially phone-stuff. So i have to reboot winmo anyway.
Sent from my X1i using Tapatalk

i think its the ducckly's keyboard not loaded as modules turbo verison. I believe it should be that because i remember the msm drivers werent really working properly on it
Sent from my Transformer TF101 using Tapatalk

[Q] Multitouch lag/issues? what could be the cause?

So I started noticing lag on games with a virtual pad. As in, jump works fine if im standing in game for example, but im running and I try to jump, either it doesnt do it at all, or it does it with some lag.
So I downloaded a multitouch tester and pretty much confirmed that there's an issue there.
If I just touch with one finger at a time, it works fine. If I press with two fingers and keep them there moving them around and whatnot, it also works fine.
BUT, if I keep pressing with one finger and use the other one to do a fast light tap, half of the time it doesnt register it.
Im using the ROM posted here: http://forum.xda-developers.com/showthread.php?t=1583871
wich im finding to be great, but I thought of originally posting my issue there since I gather it is more likely to be caused by software and not hardware.. right? considering simple touch works completely fine.
Any ideas?

Ace supports only 2 fingers at a time. But i did not find any types of lags while using 2 fingers. But it wont work if u use 3 or more fingers at once.

REPLY
Hey I got 100% same issue too. On original cm7 nightly.
But I found out sometimes it works and sometime it doesn't seems to work. I think it's similar to the rounding bug.
Maybe it's the kernel problem. Just don't overclock and it will work well. Or, reboot your phone and wait for a night without touching it, and the problem is gone. However, the bug will occur again after you install an app or launch an app. This multi-touch bug always occur on cm7. If you don't want this problem you can use stock roms. But if you say touch making it lags, it doesn't make our phone lags or the game you play using this phone is a bit slow. Just the second finger is responding slowly if the first finger is pressed/touched on the screen.
And I've tested this bug using the dev tools in the cm7 rom. dev tools/pointer location. All of the stock rom doesn't have this bug except cm7. CM7 will not have this problem on the first few weeks since the first boot. hope it helps

It's a Ace Hardware issue. Nothing to do about it.
King of the mashed potatoes©

Getting a faster device is the only solution
I got transformed into a potato while writing this post..

Why is my phone SO #%@!* SLOW??

I bought a used Droid Bionic off eBay cheap as a temporary replacement for my broken Samsung S3 to last until contract renewal time. But, this thing is just a turd. It's a PITA to use.
I'm running SlimKat in Slot 1. That's the only custom ROM I have installed. But it's just as slow if I boot the stock rom (and was before I rooted or did any customizing).
When I get a call, it rings several times before the screen wakes up so I can answer it. A couple times, the call has gone to voicemail before the screen woke up so I could answer the call. The capacitive buttons light up, it vibrates, the ringtone plays, but the screen stays dark until the 3rd ring.
Sometimes it takes 10 or 15 seconds just to get the keyboard to come up when I touch a text entry box. Doesn't matter what app or what keyboard I use.
Sometimes it takes so long for it to respond to a touch that I don't know if it registered my touch so I touch the screen again then a few seconds later it registers both touches which totally screws up whatever I was trying to do and I have to start over.
Sometimes I just want to throw this thing against a brick wall. It would be very satisfying to watch it shatter into pieces. It's frustrating me so much, I'm seriously thinking of borrowing a friend's old iPhone... Just typing that made me feel dirty, but that's how bad it is.
I don't see anybody else complaining. What's wrong with my phone?

HeathicusF said:
I bought a used Droid Bionic off eBay....
....I don't see anybody else complaining. What's wrong with my phone?
Click to expand...
Click to collapse
Have you tried running LagFix (from the Play Store; I am unable to post a link)? My phone slowed significantly over time while running CM11 nightlies; I occasionally boot into stock and run LagFix and it does clear up a fair number of slowdowns. This seems the most likely cause which would impact both stock and slot performance.

It's not ROM but the battery that makes phone slow over the time... Old battery creates static charge and unable to generate enough discharge to run the phone.
Replace the battery with the new one.. And you are good to go...
Sent from my DROID BIONIC HD using Tapatalk

I tried LagFix, but got an error saying it was incompatible.
My battery does die awfully fast, so I've ordered a replacement. I have doubts about that fixing the slowness, but I needed a new battery anyway so it won't be a total loss if it doesn't work.

HeathicusF said:
I bought a used Droid Bionic off eBay cheap as a temporary replacement for my broken Samsung S3 to last until contract renewal time. But, this thing is just a turd. It's a PITA to use.
I'm running SlimKat in Slot 1. That's the only custom ROM I have installed. But it's just as slow if I boot the stock rom (and was before I rooted or did any customizing).
When I get a call, it rings several times before the screen wakes up so I can answer it. A couple times, the call has gone to voicemail before the screen woke up so I could answer the call. The capacitive buttons light up, it vibrates, the ringtone plays, but the screen stays dark until the 3rd ring.
Sometimes it takes 10 or 15 seconds just to get the keyboard to come up when I touch a text entry box. Doesn't matter what app or what keyboard I use.
Sometimes it takes so long for it to respond to a touch that I don't know if it registered my touch so I touch the screen again then a few seconds later it registers both touches which totally screws up whatever I was trying to do and I have to start over.
Sometimes I just want to throw this thing against a brick wall. It would be very satisfying to watch it shatter into pieces. It's frustrating me so much, I'm seriously thinking of borrowing a friend's old iPhone... Just typing that made me feel dirty, but that's how bad it is.
I don't see anybody else complaining. What's wrong with my phone?
Click to expand...
Click to collapse
Not sure what you are doing to your Bionic to make it so slow. Mine is by far no speed demon but definitely not slow. Do you have a lot of unnecessary crap such as widgets, themes, etc.. running?
matriX1218 said:
It's not ROM but the battery that makes phone slow over the time... Old battery creates static charge and unable to generate enough discharge to run the phone.
Replace the battery with the new one.. And you are good to go...
Sent from my DROID BIONIC HD using Tapatalk
Click to expand...
Click to collapse
That is debatable.

mikemikemikexxx said:
Not sure what you are doing to your Bionic to make it so slow. Mine is by far no speed demon but definitely not slow. Do you have a lot of unnecessary crap such as widgets, themes, etc.. running?
Click to expand...
Click to collapse
Not at all. The only widget I use is the calendar widget. I use Nova launcher, trimmed down to one home screen. No themes. No games. Only a handful of apps and most of those are utilities (ES File Explorer, Swifkey, Dropbox, XBMC remote, an alarm clock, etc.). Facebook is the only social media app.

HeathicusF said:
Not at all. The only widget I use is the calendar widget. I use Nova launcher, trimmed down to one home screen. No themes. No games. Only a handful of apps and most of those are utilities (ES File Explorer, Swifkey, Dropbox, XBMC remote, an alarm clock, etc.). Facebook is the only social media app.
Click to expand...
Click to collapse
That is bizarre, must be Slim Kat. I am on CM M8 and while it does have some minor slow downs sometimes but nothing what you describe.
(A good time to update SafeStrap if you are not on the newest version)

HeathicusF said:
I tried LagFix, but got an error saying it was incompatible.
...
Click to expand...
Click to collapse
LagFix has to be run from the stock install, rather than from a custom rom slot; it will then work only on the /data partition, which is normal.
Concerning the delay in pulling up the screen for an incoming call, I also have that same issue inconsistently on CM11 nightlies - it's often the third pulse of the motor before the screen wakes up. I haven't found a good solution to this, as it seems to be related to the phone being in deep sleep with the second core hot-unplugged. You may be able to increase the responsiveness at the cost of battery life by increasing the minimum processor speed or using a different governor, but I haven't experimented with this systematically enough to make a recommendation.

I found a solution!!
A new Samsung Galaxy S5 will be here tomorrow.

[emoji23][emoji23][emoji23][emoji23][emoji23]
Sent from my M2 using Tapatalk

Battery effecting speed seems quite farfetched. If you say it's "static charge" that really means nothing. Maybe you mean it won't source enough current. Therefore effecting processor speed? If so then plugging in would fix you up.