Like the title says, my touchscreen start behaving erratically, registering random touches, when I use any other ROM except Froyo CEE. It happens when the phone is charging as well as when it's on battery (on battery less often). On froyo it happen's only when charging (so i can live with it).
My question, does any one have some advice as to what i can try, because i like CM7, but i'm unnable to use it like that.
My deduction is that somehow the froyo kernel+gingerbread framework are triggering these events. I can't use gingerbread kernel as i have SOC camera module, and i kinda need camera functionality.
Thanks.
Related
Hi guys, i have a weird issue with this rom, i've been using it for like 4 days now, but lately i've been getting random reboots, this happens when the phone freezes up out random, it shows the battery icons with a ? mark and the phone responds to volumen up and down commands but thats it, also the screen and the capacitive softkeys stop working when this happens to, and when i press the power button it restarts its self, i've alrdy wipe data+dalvik+cache and nothing the device keeps on behaving the same, im about to just re-flash the rom, from my acer s200 experience, acer phones tend to have random isolated issues to specific devices/hardware, and mostly these issues are hard to reproduce, anyways i might re-flash the oem rom today, il see if this fixes it or if its just another issue that the rom it self has, as its a beta release, any suggestions will be great appreciated.
edit: i have reflashed 10000 times it still does it, my last option would be to flash 1.6 but meh i like 2.1 better =]
hic, can u help me up rom acer liquid from 1.6 to 2.1 thanks .
It's most likely the ROM, but, still could be the kernel. I have been using the rooted kernel only, nothing else. Actually some lowmemkiller settings. I was not able to test if removing the threshold settings (I forget what the other thing was too) before I sold Liquid.
I can report bad use of the digital compass, when in navigation with google maps or (f.e.) copilot 8.
Gps receiver says that i'm going forward, but digital compass says that i'm going backward.
Stupid compass
Yes, I have the same issue in Navigation. The compass is fine in Google maps app though
I'm still getting touch screen freezes with any of the Cyanogen Mod Froyo builds, Bangsters/HyperDroid, assumed to be associated with the g-sensor.
I re-formatted my SD-Card and re-installed and I'm still getting freezes.
This is the 1 thing that is stopping both from becoming a perfect build, as everything else is amazing.
Any suggestions? Does it have something to do with AXI/NOAXI/EVO kernels? Under-overvolting? Is it the kernel?
Ive had problems with screen freezes with almost every rom, but i got barely any on this one. http://forum.xda-developers.com/showthread.php?t=790374
It also is a very good looking rom.
scbrother said:
Ive had problems with screen freezes with almost every rom, but i got barely any on this one. http://forum.xda-developers.com/showthread.php?t=790374
It also is a very good looking rom.
Click to expand...
Click to collapse
Yeah, I've experienced similar results, though I dislike SENSE based builds and prefer a Cyanogen Mod. I know Sense builds are more stable in the sense that they don't have as many touch-screen freezes, but would like to find a solution for the other builds.
:-/
FriedSushi87 said:
I'm still getting touch screen freezes with any of the Cyanogen Mod Froyo builds, Bangsters/HyperDroid, assumed to be associated with the g-sensor.
I re-formatted my SD-Card and re-installed and I'm still getting freezes.
This is the 1 thing that is stopping both from becoming a perfect build, as everything else is amazing.
Any suggestions? Does it have something to do with AXI/NOAXI/EVO kernels? Under-overvolting? Is it the kernel?
Click to expand...
Click to collapse
I didnt get any touch freezes with this setup: http://leoandroid.com/viewtopic.php?f=212&t=168
Are the devs trying to fix this problem/Are they aware of it? I'm asking because I have not heard anything about this issue since months and the release notes list g-sensor as "working" (freezes are definitely related to or caused by g-sensor). The freezing problem still exists. I can even reproduce it perfectly when g-sensor is activated. Compass is shaky too.
I've tried a LOT of builds since September, mostly Mdeejays (love them ) the last few weeks. Could reproduce it with any build. Also tried many radio ROMs, many WinMo ROMs -> no change.
It's the kernel. Try one of the builds that use a current kernel (such as Hastarin's, rather than the old desire-based kernal on most of the stock builds). They still get the occasional, very short, freeze, but it is almost un-noticable. I'm using Darkstone's stock build (from here) with hastarin's 7.8 and it's fine with screen rotation left on.
The freezes are caused by saturating the i2c bus on the device. G-sensor is one of the things on that bus, but not the only one. The current kernels have increased the speed of the bus to help keep it clear, but it is now set to its maximum speed. I'm not sure if there where other fixes done as well.
I was using different versions of hastarins kernels. I don't get the freezes (only sometimes) when I hold the device in a normal way. But I get them EVERY time when the camera is facing down (for example when I look on the ground in streetview in Google maps with activated compass function, or when I play teeter). It's the same position you have to lay down the device for calibrating the g-sensor. The air bubbles will freeze almost every time in this position. All other orientations work very well.
I've made some videos where you can see the problem (sorry for the quality):
http://www.youtube.com/watch?v=-RlCuITimvM
http://www.youtube.com/watch?v=A8PWNIhwTqM
There is workaround which works: http://forum.xda-developers.com/showthread.php?t=803242... new hastarin and mdeejay kernels include this patch... and no, freezes aren't caused by saturating i2c bus but by occasionally not releasing i2c bus by g-sensor chip after reading its state...
I'm pretty new to the Android platform and I just bought a HTC Hero on 2.1 which I really like BUT, I have one gripe which I was wondering if anyone could help with!
Whenever I get an email / text, the trackball flashes but the rate of flash is so slow that it's really easy to miss it unless you're staring at the phone for 6 to 8 seconds!
Is there any way to make the thing flash at maybe 1 sec or something similar?
Not a major problem as problems go but I was just wondering if it was possible....
Not that i know of, although i would like to know as well. Some custom roms utilize the led light at the top instead or along with the trackball. The led light notification is a lot more frequent and noticeable than the trackball. I think floyo blinks the trackball way faster than the usual 6-8 second rate
Can anyone confirm that 2.2 speeds up the trackball?
Is there a ROM that is currently 100% working (all features) on the Hero?
Im using a custom rom, Floyo 1.2 and when I get a message the green LED and the trackball LED flash at similar rates, maybe even at the same time. And it is not the pulsating light effect, more like a flash .. a very quick pulsating effect
EDIT: as far as all features go. I think the custom rom even exceeds the features of what the hero could do (a2sd =lifesaver)
There are 2.2 ROMs working flawlessly on HTC Hero. I'm using Froydvillain 1.7.2 right now and everything I've tested seems to work all right.
Nevertheless, I don't know if there is something to change trackball notifications behaviour.
Sent from my HTC Hero
Does that include:
GPS, Maps, Bluetooth?
I'm a bit scared of bricking the phone as my technical knowledge is non-existent!
Also, what happens to the HTC apps - I love the way that the phone interacts with the contacts and keeps records of convos, messages , emails etc in one place. Would all those features go too?
Sorry for all the q's - just a bit worried about causing expensive & irreperable damage!!
All of the GPS, Maps, Bluetooth work, but the HTC apps aren't present.
If that is the only issue that bothers you about your phone then I suggest you look for an app that could do that. you could start with an app called blink, but I dont know if it would work. Try the android apps part of the forum (its outside the G2 forum).
If you do decide to root it, then you could try the sense 2.1 roms and see if someone mentions trackball flash. I think the sense rom called RCMix 2.2 has the trackball flashing fast.
actually dont try blink.. it broke my flashing trackball find another app
Does that include:
GPS, Maps, Bluetooth?
I'm a bit scared of bricking the phone as my technical knowledge is non-existent!
I've tested Maps and Bluetooth successfully, but I haven't tested GPS (I installed my first custom ROM a week ago, so I haven't tested everything). I read it is difficult to brick your phone if you follow a good tutorial step by step, but nobody will guarantee it's absolutely safe.
Also, what happens to the HTC apps - I love the way that the phone interacts with the contacts and keeps records of convos, messages , emails etc in one place. Would all those features go too?
It depends on the ROM. If you want an Android 2.2 system, you will lost all HTC apps. If you'd rather Android 2.1, some ROMs include HTC Sense (for instance, VillainROM).
I think like nijnvy about the way to solve your issue. If you only want to change the way blinking works, I would try to configure it with some application instead of installing a custom ROM.
Hy folks.
I got a small problem with modded rom and Screen Calibration. Please forgive me if there is already a thread about it....
The Roms i tested on my gt540:
Quarx Black
Vanilla Eclair
Greenex One
Rom alek1988r
Elegance Swift 4.5
Green Rom 2.0
Every Single of these Roms failed to calibrate the Screen Properly (always 5-7 mm dead on the roght side of the Phone)
The only rom with working Screen Calibraiton is the Softmod by mmxtreme, but it isnt available with my Language.
My Question is:
Is there anybody out there with the same problem?
Is there a fix?
Thanks in Advance
Same problem. But I've tried several other GT540 and it seems that all of them have the same problem. I think it's hardware based, and the touchscreen is just faulty. Other than that it's a great phone. Waaaay better than HTC Wildfire.
If it helps you i can asure you that it is not the Hardware. with the stock rom everything ist fine.
I also build a little "mod" for myself and the touchscreen works fine.......
There is a problem with most of the custom roms here (at least for me and you)
Whats your mod doing exactly?
My "mod" (i use the "" because its not really a mod) gives me the abilitiy to calibrate my touchscreen. I just fiddeling around to get what i want of my phone working (LG Homescreen, overclocking, thethering, quick gps fix, touchscreen calibration).
It was just very diapointing to see that most of the 2.1 mod-firmwares wont calibrate my touchscreen. So i will build my own
I have vast experience in calibrating different devices and gadgets.
So if someone can point me to a source code of CM7 2.3.3 Mu4ik, and place where the kernel processes X,Y touch events. I can build my own calibration application, and mechanism.
Any help will be appreciated.
Anyone can tell me which is the stock app for the screen calibration so we can pull it out of the stock rom?
I have Miui installed in my HD2, currently running from SD. Since the beggining i noticed that sometimes the rom freezes when doing stuff. (I´ve seen the chinese guy and the turtle a lot) but nothing really bad.
Since a few weeks, the telephone freezes sometimes when receiving a call and i cannot answer. i have to lose the call, wait a few minutes and then be able to see who called. When bad comes to worse, it keeps ringing and vibrating and i have to remove the battery. It is not my wokr phone so i could live with it.
The last 2 days, it started doing the same, but with the screen black. I was able to pick up the call with the button, and terminate the call, but after that the screen remained dead. Buttons light up if touched, but screen no. Again, only fix was to remove the battery.
I went back to the 2.2 rom w/sense that i have in magldr.
Questions are:
Can this be because i was running from SD? I assumed that because running from SD might be slower.
It is possible for a Rom to degrade and start presenting errors like that? in the 2.2 rom i have none of this problems, do i do not think its hardware related.
Probably will use this chance to try another ROM.
Interested in a Cyanogen port of trying ICS if there is something stable yet.
What are my options for stable roms?
Im no dev, no cook, only an average user...