Hi,
short question: Does the Cardock detection for P990 work on a CM7-Rom? I'd like to get myself a supported dock, but i wanna know before I spend any money.
Thanks,
Tobi.
Yes it does.
Hey,
it's me again..
first of all thank you for your answer. It really DID work with CM7.
Now I'm back to stock (GB, V20L or whatever it's called) and there it doesn't work anymore. That's a pity, because unlike with every single custom rom i tried i didn't have any crashes yet.
Does anyone else have this problem? Can someone tell me how to fix it? Or can someone recommend a stable custom rom which has this thing working?
Thank you,
Tobi.
Hello Everybody,
I am having an incoming call issue even with JVT modem.
The fact is: intermitently the caller doesn't hear hear me when I pick up a call.
Workaround used: hold/unhold the caller and then I hear perfectly well.
Has anybody found a fix for this? (I am already on JVT modem).
Thanks in advance,
Same Problem ...Waiting for the right solution
Hi ,
I am facing the same problem on my i9000....with CM7 ...MIUI....or ICS build (CM9) ,tried and tested different modem's but no success....I hope there is someone to help us out ...
First thing is when this happens try to hold and unhold the call.
If you use custom kernel download voodoo control app and in recording presets set it to original.
That is the workaround.
Hi Malcho..
Thanks for your suggestion , i have tried setting preset to ORIGINAL in voodoo control app when i was in ICS by Teamhacksung ....but that didnt work out too ...
same problem i am facing in MIUI and cyanogenmod
me too
up up!
same here...fugu mod kernel + voodoo control app recording preset to original = same issue.
Did I miss anything?
Same problem for OneCosmic Rom
I was facing the same problem in Build 9 of teamhacksung.. went back to CM7 and everything was fine again.. then tried Onecosmic's ICS and now MIUI.. no such problems.. so that was in CM9 only I guess and maybe it's been resolved in the later builds don't know..
See comment 31
code.google.com/p/cyanogenmod/issues/detail?id=4681
Edit: Reply if this works for you + what rom and kernel you are using
"hit THANKS if i helped you"
hello,
Thanks a lot for that.
I will test it next week and let u know the result. (Have installed ICS for the moment).
Had this a while back, all i had to do was move the phone away from my ear so the screen will light up and its back to normal
Tried everything..
Flashed hhb_test2.zip , different modems , voodoo control app.... Nothing works till now..
Its fine only on stock rom..
Any comments guys?
Hi
I have tried using several different AOSP roms (Omni, Cyanogenmod, Sentinel) but must always go back to a Samsung Rom (Ripperrom v20 or stock 4.2.1) because I always get the same problem.
You can hear the sound if you search on "Cyanogenmod Weird Unlock Sound" on youtube
It's not me who filmed this video but I have exactly the same problem.
This annoying sound is coming anytime. In both the lockscreen and when I use the I9305 for other things. In airplanemode or when i turn of all the sounds then its not coming.
.
I don´t use Titanium backup to restore any apps.
Anyone have a solution? I always do a factory reset and wipe everything.
No one who can help me?
i dont know if its against some rules or something, but i want to ask you guys if somebody can help me fix that custom-rom i found years ago.
its a custom-rom on 5.1.1 based on aicp. i use this rom for more than 2 years now, cause its the only 5.1.1 rom i know wich works perfectly (camera, bluetooth, batterie, and got slimpie) but the original developer abandoned it and i can't remember his name nor find the page where i got it once
Reason why i ask is, the rom has one big annoying problem: system.ui
it just crashes randomly for non-reproducible reasons and because on lack of knowledge of mine, i'm not able to fix that. When the crash happen, only a full wipe help. Everything else including doing a backup ends everytime in a "system.ui has crashed" window.
is it possible to fix this just by swapping some files or something? would be nice if someone could help me, because i dont want to use another one, because there is none wich fit my needs
The touch delay is present since the release of Marshmallow, Nougat and Oreo ROMs in Titan (not sure about Falcon). There is no escape. It's good to see our 2014 devices with the latest version of the Android, but this error is very annoying and is being ignored. Doesn't matter how good the ROM is. If you using any custom ROM with Android 6.0 and up on titan, i'm sure you have this issue.
So i want to open a discussion about this issue here
If you don't know what i talking about, let's simulate the issue:
Try to write something in stock keyboard of your MM,Nougat or Oreo ROM. Now try pressing a second finger in the screen out of the keyboard and write anything else... You noticed? No?
Try to play a very intensive tap game, like Geometry Dash. Play a bit. Now play with a second finger on screen... You noticed?
Only KitKat and Lollipop Roms are free from this bug.
So, the only workaround for this touch delay is pressing a second finger on screen. Shame.
The questions left: Anyone knows a solution? The cause of this issue? There is no way to fix this?
I tried some custom kernels, no success.
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Metalhead666 said:
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Click to expand...
Click to collapse
Some people say the same on Lenovo Foruns...
Pixx 1001 said:
Some people say the same on Lenovo Foruns...
Click to expand...
Click to collapse
I think it is a kernel related issue rather than the bootloader,like some people said on lenovo foruns.I don't have proper knowledge to fix it,you could try to contact some of our developers,maybe there's still someone interested.
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
HiR3x said:
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
Click to expand...
Click to collapse
Every single ROM above 6.0 that I tested have this problem (Cm,AOKP,AOSP,Lineage,Slim,DU,CypherOS,AEX,CrDroid,RR and many more),with and without custom kernels.
I don't use my Moto G to play games , but some random games from PlayStore (Minigore 2, Bejeweled 2, Samurai II) the touch doesn't work well (or simply doesn't work! You can test all of them if you want). Using a 5.1 ROM, they work normally. It would be nice if the people post more problems about this touch issue happening on apps/games on Moto G Titan. I want to know if the same happens on Moto G Falcon, 4G variants.
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Jimisballjohn said:
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Click to expand...
Click to collapse
Well, I used ViperOs (7.1) as my daily driver at work, school for a good time (6 months I guess)... I liked Nougat Features and I guess I will keep using it, or another Nougat ROM, as they work perfectly for it on Titan.
Looks like titan Pie ROMs have the issue too (Used LineageOS 16 for testing).
It sucks that this still has not been resolved. Happened to me as well on LineageOS 16.
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
LightWard said:
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
Click to expand...
Click to collapse
I would like to test it myself and give a feedback, but sadly, my old Moto G2 had the input of the charger/usb connector broken. If anyone have tested the ROM too, would be good if they give a feedback here.