As in the thread I have a problem with multitouch after I decided to flash cyanogenmod 10.1.1 the same thing happens when I install RC5 release of CM10. I must eliminate it as I cannot play games and even zoom anything in browser
What happens is : sometimes but rarely multitouch works flawlessly so I can do anything but even after locking screen problems occur again. I checked it with multitouch testing applications and when one figer is on the screen everything is fine. When I add second finger multitouch lags a lot , often cannot see second finger or it cannot see my fingers moving at all. Tried to callibrate multitouch, do wipe/factory reset but still it's no better.
I would like to repair it somehow but I lack knowldge, that's why I'm posting here. I also posted in cyanogenmod forum but they told me get to here and check if there are bootloader updates or radio/baseband updates. I don't know if there are because I thought that with ROM i get everything whats new and if I have newest cyanogenmod stable then i don't need any more updates.
Please help me. I would be very grateful. I wrote what's wrong as well as I can but still I will answear any question if I can. Thanks in advance.
Related
Okay So I followed a video tutorial that said right now the Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[CubeV2]
was the best rom out there. So i installed it. I like the rom alot except it has some bugs that I cannot overlook, was wondering if there was a fix or a recommended upgrade from this Rom.
The bug I hate the most is the keyboard. First it was mapped wrong, but I installed the Tilt fix cab, which fixed that. But now the keyboard spacebar lags. So if i type at a decent speed the spacebar doesnt register being pressed at the right time. For example if i typed : "Hello, how are you doing today? " it would come out as " Hello,h owa rey oud oingt oday"
At first i thought it was maybe my error, that I developed some sort of bad habit of pressing the spacebar at the wrong time. But i sat there and was careful and indeed its the phones fault.
The next bug which I just noticed recently since I havnt had a reason to use it since now, is the video on the camera. When I press record it only records for 9 seconds even though I have it set to no limit. If i keep trying some times it goes past 9 seconds but the video freezes at that point, the counter still goes up and I'm forced to soft reset the phone to get out of it. I tried installing the HTC camera cab , with no effect.
Should i change roms or Is there a fix for this?
thanks
I don't believe dutty has touched these ROMs in almost a year now, and he has moved onto the HD, I believe.
Better to look at some of the more recent ROMS, like Garmin, PDA Corner, etc. and forget working with the Dutty ones.
drtolson said:
I don't believe dutty has touched these ROMs in almost a year now, and he has moved onto the HD, I believe.
Better to look at some of the more recent ROMS, like Garmin, PDA Corner, etc. and forget working with the Dutty ones.
Click to expand...
Click to collapse
How do you personally like your G's SE TF3D rom?
bilago said:
Okay So I followed a video tutorial that said right now the Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[CubeV2]
was the best rom out there. So i installed it. I like the rom alot except it has some bugs that I cannot overlook, was wondering if there was a fix or a recommended upgrade from this Rom.
The bug I hate the most is the keyboard. First it was mapped wrong, but I installed the Tilt fix cab, which fixed that. But now the keyboard spacebar lags. So if i type at a decent speed the spacebar doesnt register being pressed at the right time. For example if i typed : "Hello, how are you doing today? " it would come out as " Hello,h owa rey oud oingt oday"
At first i thought it was maybe my error, that I developed some sort of bad habit of pressing the spacebar at the wrong time. But i sat there and was careful and indeed its the phones fault.
The next bug which I just noticed recently since I havnt had a reason to use it since now, is the video on the camera. When I press record it only records for 9 seconds even though I have it set to no limit. If i keep trying some times it goes past 9 seconds but the video freezes at that point, the counter still goes up and I'm forced to soft reset the phone to get out of it. I tried installing the HTC camera cab , with no effect.
Should i change roms or Is there a fix for this?
thanks
Click to expand...
Click to collapse
Welcome to 2009 from 2008 , Dutty did so great work in this forum last year, but you need an updated YouTube video. Where did you get a video saying that was the best ?
As stated above, start exploring 2009 , you will love it here
I doubt you will find anyone with new information. Have a search/read through the Threads from dutty or try flashing one of the newer ROMs, a few have been suggested above.
Thanks
Dave
I have problem with rom cm 7.2. This rom is the best, but i have a problem with display usage battery, i have a 70% usage. Brightness i have a low level and still is this problem, and my battery drain a very fast with using. Help me please
bump
I have the same issue. I found that on stock Rom the main reason of battery drain so fast was dialer, now on cm7 display take about 50%
Try CM9... battery works for up to 2 days at normal use... Instead of the lopusy 12 hours on stock and cm7...
on cm9 i have this same
Since I am not allowed to post in development section (new user, 10 posts rule) this thread title is the closest one to my questions. I am currently on latest CM7 rom (thanks adlx.xda) and I am facing some issues.
First of all, the rom itself is great. It would be nice to update it with the latest sources. I tried all versions and in the last one there is a huge scrolling lag that was not present in the previous versions (one can see this in browser, opera mini etc. when scrolling down or up with physical keys). I think it has something to do with framework, but not sure. I ported another CM7 rom from various different phones, using adlx's as a base, and those didn't have that lag, but I couldn't remove the default on-screen keyboard because when I remove it the sym key when pressed keeps popping up to select input method.
Speaking of keyboard, when I use browser or any other browser (except opera) the key "enter" will not open the selected link. It will do nothing. This is only on CM7 and SuperOSR. It is working properly on stock, CM9 and CM10. This is very much needed since sometimes I am having trouble opening a link with my big fingers so I use the arrows to select a link and enter to open a link. I have tried to play with the keypad files but without much success.
The last issue I was having has something to do with the camera. I don't care about the front cam, I believe 90% of us doesn't care about it as well. But I was having issues with flash. It is out of sync most of the times. It works, but it is not in sync with the actual moment of taking the pictures so most of the times my pictures are dark and sometimes not visible at all. But I can live with that, just wanted to point it out.
Adlx, I hope you read the general section, and I would really appreciate if you could give me some pointers about keypad files and why enter button when I try to open a link with it is not working only in those two roms.
Best regards.
S
Little bump. Still need 2 more posts
Hello,
When the JB-update came last year, i was disappointed and rooted my phone and wanted to try out some custom roms.
But, when i switched from ViperOneS to Trickdroid, my touch input was suddenly mirrored (touching on the bottom-left side is recognized as touching on the bottom right side, in portrait mode). From then on, it was always this way,changing roms did not change anything on that behaviour.
BUT:
Int TWRP the touch input is perfectly fine, not mirrored, its just like before.
When it happened, i asked in a german android forum, but i got no good answer there, so i searched around and came up with a workaround: i modified the touch driver source (from htc-dev) in the kernel and recompiled it ( changed "input_report_abs(idev, ABS_MT_POSITION_X, fdata->x);" to "input_report_abs(idev, ABS_MT_POSITION_X, 540-(fdata->x));".
That worked, but i could feel that all input was slowed down.
Now, after i read that we can make the phone S-Off, i thought "hey, the ruu changes more than just system data and boot, maybe that will fix it".
But it didn't. And the slowed down reaction is annoying me more and more.
Please, anyone got a clue on what went wrong, or how to solve it? I am pretty sure its not a Hardware problem, because its working in TWRP. As i understand, TWRP is build from android sources too, why is it working as before, while full Android isn`t?
Please help!
Phone: One S with S4 Processor, hboot 2.15, rooted, s-off
Silfa said:
Hello,
When the JB-update came last year, i was disappointed and rooted my phone and wanted to try out some custom roms.
But, when i switched from ViperOneS to Trickdroid, my touch input was suddenly mirrored (touching on the bottom-left side is recognized as touching on the bottom right side, in portrait mode). From then on, it was always this way,changing roms did not change anything on that behaviour.
BUT:
Int TWRP the touch input is perfectly fine, not mirrored, its just like before.
When it happened, i asked in a german android forum, but i got no good answer there, so i searched around and came up with a workaround: i modified the touch driver source (from htc-dev) in the kernel and recompiled it ( changed "input_report_abs(idev, ABS_MT_POSITION_X, fdata->x);" to "input_report_abs(idev, ABS_MT_POSITION_X, 540-(fdata->x));".
That worked, but i could feel that all input was slowed down.
Now, after i read that we can make the phone S-Off, i thought "hey, the ruu changes more than just system data and boot, maybe that will fix it".
But it didn't. And the slowed down reaction is annoying me more and more.
Please, anyone got a clue on what went wrong, or how to solve it? I am pretty sure its not a Hardware problem, because its working in TWRP. As i understand, TWRP is build from android sources too, why is it working as before, while full Android isn`t?
Please help!
Phone: One S with S4 Processor, hboot 2.15, rooted, s-off
Click to expand...
Click to collapse
have you found a fix for this by chance? or can you explain how you changed the kernel in your workaround?
Every few hours the touch barely responding, it takes me like 4 minutes just to reboot the phone, and rebooting is the only way to make the touch work again.
I tried to replace the the rom to cm12 nightly, change the kernel and modem. I even flash to stock cm11s and wipe every thing! And it still not fixed. Please help me!
edit:
https://www.youtube.com/watch?v=S6drgJb6OFg
this is no me but it is exactly what happened to me
Same problem here! Don't know if its related, but I just went on a ski vacation, so maybe the cold has something to do with it? Cause that's when the problem started.
The touch problem is very irritating when I try to unlock my phone, cause I can't draw the unlock pattern. Also scrolling trough photos or apps doesn't work cause it doesn't recognise scrolling, but does pressing instead.
I hope this is a software problem!
I use stock ROM cm 11. Did nothing else with it, I have my oneplus only 3 weeks now.
So I am using blisspop rom for few months now and they have this annoying bug that when u turn the screen into horizontal mode and you try to lock it in that mode (landscape) it automatically goes back to portrait mode and locks it in that mode
Does anyone know where I can report that annoying bug?!
I am pretty sure its super easy to fix it's just that they are not aware of it
Thank you in advance
I would suggest the Blisspop topic?
I've already posted about it in the Blisspop thread, along with many others. Doesn't seem to be a high priority bug I'm guessing. If it's that annoying flash the TeamEOS ROM instead--they are both AOSP (if I'm not mistaken...)
It's not a big surprise either. Even stock nvidia firmware has bugs.
One I found out is after the latest update I can't no longer remove my USB pen drive like before, removing it does nothing (tested on my 2 nvidia shields with latest update).