Hi!
I've found a new registry tweak for "FaceDownMuteCall"
HKLM\Software\HTC\HTCSensor\GSensor\PhonecallMute = 1
(HKLM\Software\HTC\PHONE\FaceDownMuteRing = 1 is not needed!)
Tested and works.
Cina
I thought that placing the phone face down to cancel the call was enabled as standard? Or are you trying to disable it?
It not worked for me. Never. So I tried to solve the prob.
Ah well... works on mine without any tweaks as standard. Perhaps its only set in certain ROMS? Mine is UK 1.37
Thanks for that. I couldn't get "Facedown..." to work for love nor money, and saw that key and wondered if that was the one.
Ta
Mine is Elite 2.0 But it wasn't working with the default 1.24 nor with Elite 1, nor with 1.35. And I couldn't get it worked with the regtweak FaceDownMuteRing either. With this it works independent of FaceDownMuteRing. So I can be more elegant on meetings just to turn over my little cute Diamond.
cina said:
Hi!
I've found a new registry tweak for "FaceDownMuteCall"
HKLM\HTC\HTCSensor\GSensor\PhonecallMute = 1
(HKLM\Software\HTC\PHONE\FaceDownMuteRing = 1 is not needed!)
Tested and works.
Cina
Click to expand...
Click to collapse
found:HKLM\HTCSensor\GSensor\PhonecallMute = 1
your typo or i should find/add HKLM\HTC\HTCSensor ???
i was wondering what's up with this app 'cose HKLM\Software\HTC\PHONE\FaceDownMuteRing = 1 was working only once, till the first softreset. afterwards....nothing, nada, zilch, 0
KukurikU said:
found:HKLM\HTCSensor\GSensor\PhonecallMute = 1
your typo or i should find/add HKLM\HTC\HTCSensor ???
i was wondering what's up with this app 'cose HKLM\Software\HTC\PHONE\FaceDownMuteRing = 1 was working only once, till the first softreset. afterwards....nothing, nada, zilch, 0
Click to expand...
Click to collapse
Sorry for the typo:
HKLM\Software\HTC\HTCSensor\gsensor\PhoneCallMute
(Correcting first post)
But after a soft reset it reverts back to 0.
But meanwhile it definitely works.
cina said:
Sorry for the typo:
HKLM\Software\HTC\HTCSensor\gsensor\PhoneCallMute
(Correcting first post)
But after a soft reset it reverts back to 0.
But meanwhile it definitely works.
Click to expand...
Click to collapse
now i am really confused
is ANY of this tweaks working even after a soft reset??
i think that no trick is needed, i let my diamond with default settings, (gsensor\phonecallmute = 0, the PHONE\FaceDownMuteRing =1), my problem is that the flipping effect only works with a special angle the phone has top lie and has to be flipped, read here: http://forum.xda-developers.com/showthread.php?p=2360514#post2360514
perhaps some of you have the same problem, try it out with the teeter game if the ball stands still laying on the table or not. if not, try the two porition the ball does not roll (face up and face down), and use excactely these position when flipping to mute.
i'm interested in the results.
maybe the facts that the flipping feature just worked one time is just a fortuity and has nothing to do with the settings?
Related
Hi: I've super-upgraded to TuMa 1.3 with very good happy time till now!
Many thanks guys, especially Tuma!!
i just have one problem, when typing on my keyboard, sometimes, not all the time, keys stick and after pressing a key i get something likeeeeeee thissssssssssssssssssssssssssssssssssssssssssssssssssssssss
or, even worse, the backspace key gets stucked the same way and it erases all EAAARRRHHHGGGG!!!
is this fixable??, is anyone else having this problem???
I use the keyboard big deal...
Have the exact same problem with helmi 1.3
tehCORE said:
Have the exact same problem with helmi 1.3
Click to expand...
Click to collapse
So, I see now that upgrading (something I had planned) to helmi 1.3 doesn't repair this problem. I would like to know where this problem originates to find a solution. I'm using now Pocket Hack MAster with the device running at 597 Mhz and the problem is still there! :evil:
Some advice??
EDIT: I've removed the CPU Meter on the upper bar. It seems to work faster and better. Still waiting to see if the problem arises again..
i'm on helmi_c 1.1b and have this problem too. May be that is hardware problem or driver time bomb?
change the keyboard repeat settings, and delay settings, I have had this problem with every wm5 rom, and by changing the settings it appears to fix this prob.
tesing.. thanks for reply...
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
I've had success with changing the keyboard repeat settings but it comes back eventially. I've had the problem on every WM5 ROM, but less-so on the most recent Helmi ROMs with the AKU update.
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
I'm now using Pocket Hack Master with the feature of using different speeds for different apps. It happens less, so, could be the driver priority on CPU intensive apps. Because the SMS app now seems to need more CPU power than before :? :? (bar & text space redraw or something), it is one of the apps I've selected to run at 590 Mhz:shock:.
Black6spdZ said:
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Click to expand...
Click to collapse
I'm having this problem with other programs also (i.e.: Softmaker TextMaker, Pocket MindMap). Also, someone said that when using the e-mail (nor the SMS) part of the program the problem doesn't happens.. I've not tried myself as I don't currently use e-mail on my device.
xykosomatik said:
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
Click to expand...
Click to collapse
Please, xykosomatik, confirm so. I would be eager to upgrade if this problem is solved on this ROM, as I use the keyboard typing 80% of the time on my device.
Thanks all.
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
It seemed to make an improvement for me, but time will tell. This issue seems to come and go on my phone.
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Tuatara said:
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
Click to expand...
Click to collapse
maybe we could do a compromise, i little higher than the OS priority
the keyboard problem is really annoying
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
*sigh* ... why do people still keep punching in random numbers into the registry without checking what the values could or should be? *sigh*
Black6spdZ said:
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Click to expand...
Click to collapse
gh0st said:
maybe we could do a compromise, i little higher than the OS priority
Click to expand...
Click to collapse
Ok ... before this gets out of hand, and other people start doing "silly" and "stupid" things with Priority256 ... especially without understanding what you're changing, READ THIS! Otherwise you WILL cause untold problems for your device.
http://msdn.microsoft.com/library/d...html/wce50conRealTimePrioritySystemLevels.asp
To give you the comparison for Windows XP ... just open Task Manager, select an application which is using 100% CPU, running at Normal Priority, and switch it to Real-Time. Then enjoy how "responsive" the one application is (unless it's accessing the video display and/or disk - i.e. try doing it to an explorer window file copy! ;-)). You'll enjoy a "locked" machine, and admire how you're unable to do anything else - even open the start menu! You may have to hard-reset your machine depending on the application you choose to make Real-Time.
THANKFULLY ... the Keyboard Driver (QwertyKey) has a FORCED time-delay in it (debounce delay) which ensures it can not take 100% CPU time, and through this ... and ONLY through this fact, it hasn't killed your device. Had you done this to ANY other device driver, I'm sure your device would need a hard-reset, and you could start re-installing everything again.
By raising the priority above everything ... ALL you are doing is making the QwertyKey device driver get serviced AHEAD of any other pending interrupt. While this MAY make a slight difference, it will only do so at the expense of EVERYTHING else in the OS. (Like WiFi, Network, USB, ActiveSync, Memory Management, Compaction, etc ...)
gh0st said:
the keyboard problem is really annoying
Click to expand...
Click to collapse
Yes, I have had the same issue, but there is a LIMIT to which you can go with the driver Priority in order to "fix" what is fundamentally a hardware and driver problem.
gh0st said:
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
Click to expand...
Click to collapse
In my testing, and throughout the TuMa ROMs I've used 0x81 - or a priority of 129. This was carefully chosen to be below the Wave device (which was or should be set at 0x80 or 128 for best performance on the BA - again due to driver issues), so that sounds/rings happen at a higher priority than the keyboard. Yes, this is eventhough BOTH Priority256 values for these drivers were tweaked above the default recommendations from MSDN.
If you're finding that the keyboard is causing you grief, you could try inverting these two devices, and setting the keyboard HIGHER than the sound driver - i.e. to 0x7F or 127, and see if the system sound servicing is the cause of the keyboard stuttering delay. However, you may introduce stuttering into the sound output at this point ... i.e. even when you're NOT using the keyboard (which is most of the time).
At the ABSOLUTE HIGHEST level I would even consider, would be just below that of the touch-screen (0x6D). At this level (or above) would cause handwriting recognition issues, as the touch-screen would not be serviced at the correct rate to track the line drawings.
Never even consider going above the Power Manager Resume Priority Level ... if the driver supports power management, and is taking too much CPU, then the power management thread will never be able to "shut it down", and/or wake it up ... ever. Result = lockup.
So ... in summary:
QwertyKey: 0x81 ... or 0x7F to invert priorities
Wave Device: 0x80
I'd still like to test all this with the latest AKU3.x ROMs and see if the Priority settings are still valid, but for the moment, I'll assume that they are.
Good luck to anyone using priorities outside "sane" values ... you will create "priority inversion" conditions, where a driver is waiting on another driver to run, but it never will, since the priorities are reversed. You have been warned ... but enjoy playing with it anyways. Device recovery is only a hard-reset away.
Thanks for clearing this up Tuatara, good post!
oops! i'm reverting the priority values....
Thanks for the post, @Tuatara. it was very enlightening.
Hello everyone ,
Does someone experiences the same problems as seen in this thread for the Touch HD?
http://forum.xda-developers.com/showthread.php?t=446440
Click to expand...
Click to collapse
To sum up, there's little 'freezes' lasting 4-5 seconds where the screen doesn't respond to any inputs.
It occurs randomly and without reason.
HTC released an hotfix regarding this problem, that can be found here:
http://www.htc.com/www/SupportDownload.aspx?p_id=179&cat=0&dl_id=448
Click to expand...
Click to collapse
However, this is for the Blackstone. When executed on the X1, there is a message box saying
"Please use the correct device to install this hotfix program"
The fix can be extracted and there's a _setup.xml that seems to tell what the .exe does;
I was wondering if it were possible to port it for the X1 as the Blackstone and the X1 are somewhat similar?
NB:
Hard resets didn't helped neither, freezes are also present.
I'm using this:
ROM Version: 1.02.933.3
ROM Date: 08/29/08
Radio Version: 1.06.25.29
Software Version: R1AA017
I also have these freezes occasionally.
I managed to install the files from the hotfix the other night, (because, well because I like to experiment) I spent 5 times as long removing them.
The display inverted, but not the calibration!
ill change the cab info install at your own risk.
however i do not have this issue. I have an issue of after long idels of not using my x1 at work the screen will apear to be cracked but the images are really cracked. a soft reset fixes this issue. (this is ment for a seperate thread) just giving you info on other display bugs on the x1
also can you upload the cab as the htc site will not allow me to download it.
My issue is actually with the camera... if you leave the Camera application on a long time, like 20-30 minutes idle, it will eventually crash, and it will say Camera.exe has stopped responding (or something like that, asking if you want to send a report to MIcrosoft)
just get freezes when i use the HTC album. other then that, nope.
Here's the .exe (renamed to .cab since xda seems to block .exe),
for those who can't manage to download it.
@Shadowmike
Thanks for your help
Sorry to go off topic a little :
Regarding your idle screen problems, I don't have any of it (maybe because I'm experimenting tweaks with it a lot so don't have time to idle really long )
May it be related to GWES:
http://msdn.microsoft.com/en-us/library/aa925858.aspx
Click to expand...
Click to collapse
To sum up, there's an interesting registry value named PORepaint that can take values from 0 to 3.
The key I would change may be:
HKLM\System\GWE\PORepaint
The factory default on my X1 is 0 but for your problem, I would set it's value to 2.
Personal Feedback:
When you press the ON button in order to wake the screen, the screen goes blanks for few milliseconds (blank flash), but it's repainting the entire area.
No major speed issues noticed between 0 and 2 values.
Hope this helps
I have the same problem with my X1, using the latest R2 rom (generic UK). It annoys the most when playing games like Bejeweled 2 and the screen suddenly freeze for a few seconds although the game and time keep running in the background and when it stop freezing I already lose time/points. It also happens with every other game I tried playing, even after hard reset. Any fix available yet?
doclucas said:
I have the same problem with my X1, using the latest R2 rom (generic UK). It annoys the most when playing games like Bejeweled 2 and the screen suddenly freeze for a few seconds although the game and time keep running in the background and when it stop freezing I already lose time/points. It also happens with every other game I tried playing, even after hard reset. Any fix available yet?
Click to expand...
Click to collapse
Exactly what I get. It is most encountered in games where you touch the screen rapidly. Suddenly the whole OS freezes for 5-6 seconds then continues for some time until you get it again. It is very annoying.
Exactly. It happens ONLY with rapid screen presses. I observed this when typing.
Yes. This happens to my X1 also. It is possible to reliably replicate this bug.
The shadowmike's Cab didn't do anything usefull. So the HTC's Hotfix for the HD doesn't apply
Anyway, I made a Video describing this bug:
http://www.youtube.com/watch?v=2cOhX8yY5Yk
Hm.. Yesterday right after I did that video, I flashed my X1 with the newest official ROM (version 1.03.931.8 (dated 12/21/08)) from this site. Then, I installed the shadowmike's cab. After the soft reset, the problem hasn't (yet) surfaced (plus the system seems more responsive). Fingers crossed .
Edit: Nope.. False alarm. It still happens. Though rarely..
yup...
it happens...
doesn't really concerns me though...this is windows mobile anyway
pikipirs said:
Yes. This happens to my X1 also. It is possible to reliably replicate this bug.
The shadowmike's Cab didn't do anything usefull. So the HTC's Hotfix for the HD doesn't apply
Anyway, I made a Video describing this bug:
http://www.youtube.com/watch?v=2cOhX8yY5Yk
Click to expand...
Click to collapse
Youtube a$$hole$ seem to have removed your video for some reason, was a good one though, wonder if they get commission from SE. Maybe you can post it on a different video site...
shadowmike said:
ill change the cab info install at your own risk.
however i do not have this issue. I have an issue of after long idels of not using my x1 at work the screen will apear to be cracked but the images are really cracked. a soft reset fixes this issue. (this is ment for a seperate thread) just giving you info on other display bugs on the x1
also can you upload the cab as the htc site will not allow me to download it.
Click to expand...
Click to collapse
Thx a lot for having uploaded cabs as I have sometmes the freezing issue also from my side on my X1
doclucas said:
Youtube a$$hole$ seem to have removed your video for some reason, was a good one though, wonder if they get commission from SE. Maybe you can post it on a different video site...
Click to expand...
Click to collapse
Strange.. I can still access and see the video (no cookies works too). Does the video still appear deleted? Or was it just a glitch
Aye, same here... Mostly when playing insaniquarium. I just tried the .cab fix, didn't fix anything for me
SquidgyB said:
Aye, same here... Mostly when playing insaniquarium. I just tried the .cab fix, didn't fix anything for me
Click to expand...
Click to collapse
it happens to me as well...i think this generic bug in x1.
So how do I reliably test the bug ? It happens to me sometimes, but I did not find the pattern yet.
Watch my video (top of this page) to see how I did it (I've shot myself (with a camera ) couple of times doing it).
If that doesn't work, try to load some app. Like any game that somehow reacts to your touch (even Bejeweled works). Then try touching really fast and repeatedly. It shoud happen.
Here's a sound recording of me tapping a jewl in Bejeweled (i'm really hitting the display, do it more gently). It should give you an idea how fast you need to tap. Right before 0:06 the screen stopped responding, i did 4 taps to verify, and then another, and then it started responding again (3 more taps). Sometimes all it takes is 5 seconds (like it did here), but other times, your hand will start to hurt before it happens. Just rest a little bit and then try it again.
Hello all, after some extensive messing with the registry settings for the camera, my phone now seems to take photos in the correct orientation here's what i changed i think!!
HKLM\software\HTC\Camera\common\rotate set value to 0 (may already be 0)
HKLM\software\HTC\Camera\image\enableencodeportrait set value to 0
i know this is relevant to the main thread however its got too long and i fear many soloutionm may have been lost. it may also require a soft reset. i have extensively messed with the values for this and it kinda suddenly worked however i think this is what is required. i have not installed any rotation applications, nor have they been installed since a hard reset so that has no influence in my case.
i hope this helps, if not i will attempt to do a more thorough comparison with an unchanged regristry to get the definitive answer
regards
(all mods made at your own RISK!!)
Mat
this working at all?
Not for me . These were the default settings that I already had and I have the bug. I'm playing with other settings now and will report back if I find anything.
Hi,
I've had my X1 for about 4 months now and love the phone. Overall its been great but there have been a few annoying problems with it.
I was wondering if any of you guys out there have heard of the following problems on the X1 and know of any solutions:
1 - I installed HTC's Phone Keypad (Version 1.5 Build 32687) and it's great except that sometimes when press a key, it defaults to a letter - eg, if i press button 2, it defaults to the letter c instead of giving me a choice of a, b or c!
2. - Also when texting, the phone keeps randomly freezing for around 5-10 seconds which is really annoying.
Is there a newer version of the Keyboard i could try installing?
S
I look at it, I am Chinese, I do not know that you use the English-speaking countries use what is ROM. To be able to help you, then I will try my best to help you
Hi,
I've got the latest R3 Rom installed from the Sony Website.
Thanks.
n9805928 said:
Hi,
I've had my X1 for about 4 months now and love the phone. Overall its been great but there have been a few annoying problems with it.
I was wondering if any of you guys out there have heard of the following problems on the X1 and know of any solutions:
1 - I installed HTC's Phone Keypad (Version 1.5 Build 32687) and it's great except that sometimes when press a key, it defaults to a letter - eg, if i press button 2, it defaults to the letter c instead of giving me a choice of a, b or c!
2. - Also when texting, the phone keeps randomly freezing for around 5-10 seconds which is really annoying.
Is there a newer version of the Keyboard i could try installing?
S
Click to expand...
Click to collapse
1 - to me it's no surprise that HTC keyboard is NOT working properly on SE device.
Install something made generically for WindowsMobile. There's plenty of keyboards
2 - texting: on screen? basically X1 has this problem, especially when typed too fast on screen, but may be also caused by this keyboard or
word prediction (if you use any).
Thanks for that Doministry... have you any suggestions on the best keypad to use?
Tried the XT9? Check out the thumbs in the 1st post. http://forum.xda-developers.com/showthread.php?t=494026
Thanks for that, I'll have a look at the Thumbs app you suggested.
I have used the XT9 keyboard and it seemed to have similar issues to those described above.
n9805928 said:
Thanks for that, I'll have a look at the Thumbs app you suggested.
I have used the XT9 keyboard and it seemed to have similar issues to those described above.
Click to expand...
Click to collapse
I used Teksoft FingerTouch
http://forum.xda-developers.com/showthread.php?t=321074
Great one. But I don't use any of these.
WM one is the best feature-wise.
Could someone help me! My Sony X1 has a problem with calling! When I talking on the fone which automatically stop at 12- 14 seconds! Eventhough, I reset hardware, restore or change sim card.
i agree wiz u
Hi.
I got a big problem with my X1. There is a very small gap or pause (some ms) in audio playback every 5 minutes. It's almost in every song or every second. I'm on WM 6.5 H.V4 Extendir Bulid 21869. I've tried many other Roms ,only German -> or ist a problem that only our cook's have, but the gaps are still there. And it does not depend on player I use. Tried S2P, WMMP, Nitrogen, Pocket Player and so on. Already tried to hardreset and so on...
Any1 got a solution 4 me?!
many greets from Germany -> btw. very very nize forum!
Edit: @bootx1: for me it depends also on what rom I use and thx for the faaast answer!
just checked the cpu usage with a taskmanager which has a live graphic display and when there is a gap there is no change in cpu usage
UPDATE: tried this driver -> forum.xda-developers.com/showthread.php?p=5837209#post5837209 and it starts up, but the speakers are silent ... deinstalling ... speaker works but still the issue!
It's a long time since I've searched for a solution for this, so there may be one by now, but I doubt it, as it's in most roms I use, from rom to rom, it varies in it's severity.
hi
had similar issue in Nitrogen on lock screen, every 7 sec for about 1 sec the song froze
could solve it in options - settings - general settings, where I increased prebuffer length to 2.500ms (default 1.500ms), after that my probs where gone
might be worth a try 4 you too
DrakenKorin said:
hi
had similar issue in Nitrogen on lock screen, every 7 sec for about 1 sec the song froze
could solve it in options - settings - general settings, where I increased prebuffer length to 2.500ms (default 1.500ms), after that my probs where gone
might be worth a try 4 you too
Click to expand...
Click to collapse
Dude you are a savior here!!!
YEAH! YEAH!
Late in the last night I've tried another rom. The S4 v1.4(german rom from this forum) with 6.5.5 and the gaps, skips or pauses everything is gone! Just clear sound.
Nice!
But I would prefer a 6.5 bulid... Is it possible to copy drivers from 6.5.5 to 6.5?
fixed
Did you try this?
forum.xda-developers.com/showthread.php?t=545358
@sylvios: THANKS! Works perfect. Been searching for this all the time! U're GREAT!
Now I can use any rom without stutter!
Thread can be closed.