Related
my touch screen was crazy when I get my phone out of my pants. I did not touch the screen but it still automatically run the app and drag the taskbar up and down .........
nobody is like me???
care to share more details and/or what ROm you're running? 2.2?
it happened randomly to me too, with any rom 2.1 2.2, but I still didn't figure the reason out yet..
Same for me.I have cronos 1.6.1 on phone with adw launcher.But happens only ones or twice.
Sent from my Milestone using Tapatalk
You guys probably overclocked it too much damaging the touchscreen.
Crypto_ahash said:
You guys probably overclocked it too much damaging the touchscreen.
Click to expand...
Click to collapse
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy
lapy said:
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy
Click to expand...
Click to collapse
I used to have that issue with stock 2.1 roms.
CM6, Sense mod, fastest Eclare and now MIUI does not bring that night mare back to me.
Also, if you charge using a 2-pin socket [the one without the earthed pin, popular in Asia], it'll show up.
OP needs to be a little more clear, but let me say my results.
Ever since flashing 2.2.1 SBF and then applying a few Froyo Mods and even goign back to ECLAIR,
I noticed that multitouch screws up. Sometimes it things I have a finger on the screen already, so by putting a finger on, it does a pinch zoom on me even though I only have 1 finger on it. Then sometimes it doesn't let me press an icon on my screen insisting my finger is elsewhere. Other times the notification bar starts getting pulled down randomly.
Perhaps Kadalban can explain his Multitouch fix, but for me it seemed to solve a lot of issues. Granted it was only pushed out in CM6 12/4/2010, which gives me 1 day to test so far, but some of those freak-incidents have been disappearing. You'd have to give me 3-5 days to conclude anything, but for now it seems to have done the trick.
i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate
duytrum444 said:
i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate
Click to expand...
Click to collapse
Update to the new CM6. 12.04.2010 solves it for me.
i'm using it....and now,i don't have issue again. i testing it.
Sent from my Milestone using XDA App
how did you fix your screen.my homebutton does not respond
I just changed to some mod roms and the problem disappeared for me.
Some of my friends got really big issue with the touch panel and when they came to Motorola service point, the technicians said there is a known issue with the panel they used but not all customers are affected (hence some people are OK after trying different roms).
So if one experiences it then just needs to go to Moto and they'll change to a healthy-guaranteed panel obviously, if you're still under warranty, it's free!
Well, to tell the truth, I like this phone. Dual-core CPU, perfect screen, HDMI output etc.
But as soon as I get this phone, I found it cannot be wake up from sleep.
I heard that LG has released a update software to fix this problem, but after I had connected my phone to the computer and opened the LGMobile Update, it told me there was no newer update available.
So I'm trying to figure out the reason of this problem.
This problem does not happened every time when I push the ON/OFF button to put the phone to the sleep mode. If I just reboot the phone, and then turn off the screen, there will never be any trouble, even I put it on the desk for the whole night.
But if some programs has been run, like the games, map, internet browser, or even a call or SMS, then lock the screen, it will never wake up. Or if I plug in the charger or connect the phone to the computer, it works great with no trouble.
What's more, after the phone has 'dead', the temperature of the phone became high, and even became higher and higher, very strange.
So I try these way to solve the problem with no success:
-replace the battery with another one.
-wipe the battery information by using ClockworkMod and then re-calibrate the battery.
-flash a different version ROM, including MCR ROM and LG Stock ROM.
-flash a different version baseband.
-force the CPU frequency to stay in 800Mhz by using 'pimp my CPU'.
-lower the voltage of the CPU.
-forced the frequency to stay about 400Mhz when the screen is locked.
-remove any applications installed by myself.
-disallow any background applications.
-put the phone in the rom with air conditioner turning on which the air temperature is about 25°c.
Then I guess this problem is caused by power management bug.
There will never be any problem when the phone is awake, or the charger is plugged in, so I don't think it's a hardware bug.
Must be a bad unit. :-(
Sent from my LG-P990 using Tapatalk
As I said before.
When you press power button to wake-up the screen, and the screen is black (bsod), press power button again (so it would power off the screen, even tho the screen is black), count till 20/30sec and press power button again....
There yoy go, phone working again!
Ive overwon my bsod since I know this trick!
Sent from my LG-P990 using XDA App
Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk
Sckank said:
Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
No, no work.
Now, after playing games or using Google Map, I must turn off the phone, and then turn it on again to avoid this issue.
OK, now I can almost confirm that this issue is caused by overheat.
I boot the phone, then put it on the desk without any operation, it will remain OK.
Then I put it into my jeans pocket for about 1~2 minutes, it will be dead.
Again, after playing games, I put the phone just near the air conditioner, it will be cooled down very soon, and the issue will not happen.
So, is there any way to make the ‘temperature protection’ or something like that higher? Or just remove it from the Android OS.
I don't think removing any sort of temp failsafe would be a good idea.
I just had a bsod and the phone was really hot. If anything, it needs a proper failsafe put in, so it at least reboots in stead of hanging on the black screen
Sent from my LG-P990 using XDA App
I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym
TrymHansen said:
I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym
Click to expand...
Click to collapse
Thanks for reply dude.
But I've tried almost every version of baseband and rom already.
I'm from China, newest version of baseband I got is V10S, which is a Korean version, and the newest Chinese version is V10K. I have tried to flash the phone back to V10A - a European version ROM, and then update the phone using LG Mobile Update software to V10D, and this did no help to the issue.
As I said, this problem always happen when the temperature of the phone is high. I'm not sure whether the CPU/GPU temperature or the battery temperature will cause this issue (I prefer to believe it's because of the battery temperature, cuz the Google Map won't use too much CPU and GPU resource)
Another interesting thing I found, is that if I leave the music playing in background, then lock the screen, the phone will never meet any issue.
So now, my solution is to avoid the high temperature, or playing the music in background, muted, and then lock the screen. This may drain the battery faster, but at least I will never miss any call.
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
Hey, first I want to let you know the wonderful news that XBMC is available for android (at it is sweet). But I've noticed that when I hook up my USB to HDMI cable to my phone, the display screen gets lag. Plays fine on the phone, but the display on the screen is pretty bad. I'm running the latest holics and tried playing with CPU speeds, still no fix. If anyone knows what to do to get the lag to go away on the big screen, it would be helpful.
Glitch04 said:
Hey, first I want to let you know the wonderful news that XBMC is available for android (at it is sweet). But I've noticed that when I hook up my USB to HDMI cable to my phone, the display screen gets lag. Plays fine on the phone, but the display on the screen is pretty bad. I'm running the latest holics and tried playing with CPU speeds, still no fix. If anyone knows what to do to get the lag to go away on the big screen, it would be helpful.
Click to expand...
Click to collapse
This is the first I am hearing of XMBC. Did a few quick Google searches to get some basic info and it sounds awesome, but I'm still left a little confused. If you have the time to walk me through how to set up some of this stuff, I would really appreciate it!
Find apk in forum...
Download apk...
Make sure unknown sources is checked...
Side load xmbc...
Sent from my HTC Holiday using Tapatalk 2
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.