(Pretty much a crosspost from /r/Xiaomi cause I got no answer there):
Per the title: Once I had finally gotten past that Error 86006 stuff with bootloader unlocking and such, I immediately went to flash some custom ROMs on my Vince (since that was honestly what I had bought it for). One of the things I enjoy about those custom ROMs is that they often have the "Hold volume key to change tracks" function while the screen is off. Unfortunately, with any ROM I've tried so far (AOSPEX Official [7.1.1], LOS 15.1Unofficial [8.1.0, Non-Treble], RR 6.0.0 Unofficial [8.1.0 Non-Treble]), I've had an issue of my headset's buttons not functioning properly.
(Using CTIA/Android-compatible headsets [that also worked fine on my Kenzo]), whenever I press the top button, it acts identical to a middle button press, something I confirmed through the use of a KeyTest app I found on GitHub, showing a scancode 226 [HEADSETHOOK] for both top and middle buttons, while the bottom button was reporting as scancode 257 [BUTTON_2]. Not gonna lie; I don't really know the implications of that besides the fact that my top/middle buttons are essentially clones.
What this results in is: my top (and middle) button does the standard pause/play/skip track thing while my bottom button does weird stuff - sometimes acting like a "Tab" key would on Windows, selecting various boxes and then clicking on them. (Still not sure what it's doing.) This has been the same across 4 different headsets and it's becoming a bit irritating. I found some people with the same(?) issue with the Mi 2 and Mi Max 2, but the Mi 2's solution included some kernel tweaking for headset button electrical resistance (and I compared the values between the vince kernel dump and the ROM kernels and they seemed to be the same, so I dunno) while the Mi Max 2's solution involved some editing of the Generic.kl file in /system/usr/keylayout but that didn't work for me either. Has anyone else come across this issue/found a fix?
tl;dr: headset buttons aren't doing what they're supposed to in every single non-MIUI ROM I've flashed - some 7.1.x/8.1.0. Does anyone have a fix/the same issue?
I has same problem with 3 different headset. Non of them were working and no solution.
Same here. Any workarounds?
Related
Both the on-screen keyboard and the menu keep annoyingly popping up on my Viewpad7. It is driving me crazy.
At some point I thought it had to do with how I moved the device around, but I still think it's a random thing. It was/is a problem before and after loading it with a custom rom.
Is this a known hardware (or software?) bug ? If so, is there a cure for this? I have looked for settings, but was unable to find them. Thank.
SWVer=3.16K
MODEL=FM6-0001
HWVer:103
Android 2.2.2
Hi
Have the same problem and some other users here too.
Seems the Touchscreen/Softkeys are faulty and have to be replaced.
I bought mine 1 week ago and day by day it went worser. I didn't upload a custom rom so far, so it's a stock problem.
Now every 2nd time I take the device it vibrates and menu/keyboard keeps popping up/down. Looks like, the "menu" softkey does his own business, right?
Also the G-Sensor/Compass seems to be defective for me - after a few hours I have to calibrate always.
I made some videos, look at this thread:
http://forum.xda-developers.com/showthread.php?t=1258052
Where have you bought yours?
Regards
With my device it was when I held it in landscape mode and touched the bottom part of the right side or the rightmost part of the bottom of the device itself. It was also HWVer 103. You will most likely have to get the screen and soft keys replaced like I did.
Sent from my ViewPad7 using XDA App
Or, it could be just be a "normal" thing with Froyo OS itself, I've noticed it on 2 newer build - both ITE enabled - in U.S. market.
SWVer=3.41
MODEL=FM6-0001
HWVer:107
Android 2.2.2
This happened only on certain Apps - even when Auto Rotation under Settings are turned off, it will switch to the "opposing" mode and won't go back once it make that orientation change, i.e. YouTube whereas Angry Birds will stay landscape all the time. Device has been calibrated & sensors working, as I had no issues with GPS status & Maps, etc.
Should be a simple fix or patch on the OS or custom ROM .... BTW, I'm running the stock, rooted 2.2.2 ROM while waiting for an OC one with the ITE kernel working to boost the Quadrant scores, LOL.
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
astuermer said:
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
Click to expand...
Click to collapse
Hmmm, interesting after I checked out a few YouTube videos & it sounded like it's all HWVer 103 yet running Froyo 2.2.2. Is the device ITE enabled as I noticed that the pop-up keyboard is "standard" whereas mine has Swype style keybaord with ITE.
It's a pain to get it returned, exchanged & repaired at the authorized factory service center and be without the use for 2+ weeks, unless one's within a 30 days period & can send it back to the place of purchase for a new one (could take just as long)
Another post mentioned a new stock ROM just being released, it might be worth an effort or try to flash it (FM6-3350-0-1008-A01.nb0) upon downloading & using the SUTL3 app to do it - would need to root it again - if one is brave enough (since it's going back for repair/exchange anyway?)
BUT, I'm guessing whether this newly released stock ROM is for ITE devices vs. non-ITE ones with HWVer 103, 106 and 107's ???
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Brought it back to the store for repair. I think they put a new screen and cover (back) on it. Works like a charm.
flez1966 said:
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Click to expand...
Click to collapse
Can you describe more precisely how and what did you do or can you (better) do some photos?
Did you pulled off a back cover and inserted a piece of paper somewhere?
Need to experiment
Software solution
This is a solution from a user 'retrochip' from 4pda.ru forum
(Link to original post in Russian and i'm not able to post is here)
1. Root your device (can be done with Gingerbreak)
2. Find out codes for Menu button and Search button (229 and 217)
3. Edit configuration file /system/usr/keylayout/qwerty.kl (you can use RootExplorer)
In qwerty.kl:
Find text:
key 217 SEARCH WAKE_DROPPED
and change to:
key 217 MENU WAKE_DROPPED
Find text:
key 229 MENU WAKE_DROPPED
and change to (just comment it with #):
#key 229 MENU WAKE_DROPPED
Save and reboot.
Now Menu button isn't active and Search button works as a Menu button.
No annoying random popping keyboard anymore.
This has killed my all soft buttons, now the only option is to fix it in adb, because screen keyboard doesn't appear in terminal, I need to touch menu then screen keyboard.
I have searched everywhere for a solution to this problem and trust me, the search button has never had this many presses before
I have a HTC HD2 and 'almost' everything works, but there are a few issues I have.
I'm not a noob in ANY sense and I always try and find a solution to my problems before posting about them, that is IF I can't solve the problems myself
First off, this is my current setup for the HD2:
HD2: International 512mb HTC HD2
Radio: 2.15.50.14
HSPL2.08
MAGLDR V1.13
Recovery: MAGLDR CWM Recovery v3.0.2.4
Current ROM: NexusHD2 JellyBean CM10.1.3 V2.7 by Tytung
Previous ROM: PACman HD2 v1.2a by Xylograph
Kernel: tytung_jellybean_r2
Ok, the problems. What are they?
First off, the phone will NEVER, and I really mean NEVER, enter Deep Sleep. Deep Sleep is always amongst the unused CPU states. I have tried everything to get it to go to Deep Sleep to no avail. I tried another ROM to see if the ROM/kernel was at fault, but it isn't. They all have that problem. There are no apps that are causing wake-locks and even using an app that forces Deep Sleep will not work. The lowest the CPU will go is 96Mhz and never below it. I have the Max CPU speed set to 1190Mhz and the lowest set at 96Mhz. I also can never confirm a time when Deep Sleep did work, because it never did
Second problem, the physical buttons on the device act very erratically. I don't have the well-known power button issue, but I have something similar. The power button doesn't work on a long-press. If you long-press the power button it should give you the power menu, right? In my case, that never happens. What will happen is the display will turn off, as if I simply pressed and released it, like when you lock the phone. No matter how long you hold it in, the power menu will never appear.
Other buttons also act odd. The volume down button does work, but it also triggers the multitasking window to appear, every time I press it. This behaviour is not restricted to being in Android. Scrolling in CWM with the volume rocker, because that is the only way you can navigate this version of CWM, also does this. The log window will disappear and re-appear constantly, but sometimes it doesn't do this. This problem is only with the volume down button. The volume up button works just like it should. Other buttons do give problems, but they are not ever-persistent like the ones I mentioned above. The others just have constantly changing behaviour. They will perform different tasks at random when pressed, like open the dialer, or go home, or open the multitasking window as well, or even go back sometimes.
Now, I don't know what happened to Tytung on XDA, nor do I want to find out because it isn't important to me, but I'm not trying to advertise his work. I'm just trying every ROM I can find.
The phone does have water damage, but that was many years ago. No repairs were done to it, but it still works just like it should. The only problems are the ones I mentioned above. I do think that the water damage did do something to the buttons of the phone, but is it even possible that Deep Sleep can be affected by this? Isn't Deep Sleep something that is software-based?
I really would like to know what the is going on here
Any help would be greatly appreciated
I hope I provided enough information about this problem
D395267 said:
I have searched everywhere for a solution to this problem and trust me, the search button has never had this many presses before
I have a HTC HD2 and 'almost' everything works, but there are a few issues I have.
I'm not a noob in ANY sense and I always try and find a solution to my problems before posting about them, that is IF I can't solve the problems myself
First off, this is my current setup for the HD2:
HD2: International 512mb HTC HD2
Radio: 2.15.50.14
HSPL2.08
MAGLDR V1.13
Recovery: MAGLDR CWM Recovery v3.0.2.4
Current ROM: NexusHD2 JellyBean CM10.1.3 V2.7 by Tytung
Previous ROM: PACman HD2 v1.2a by Xylograph
Kernel: tytung_jellybean_r2
Ok, the problems. What are they?
First off, the phone will NEVER, and I really mean NEVER, enter Deep Sleep. Deep Sleep is always amongst the unused CPU states. I have tried everything to get it to go to Deep Sleep to no avail. I tried another ROM to see if the ROM/kernel was at fault, but it isn't. They all have that problem. There are no apps that are causing wake-locks and even using an app that forces Deep Sleep will not work. The lowest the CPU will go is 96Mhz and never below it. I have the Max CPU speed set to 1190Mhz and the lowest set at 96Mhz. I also can never confirm a time when Deep Sleep did work, because it never did
Second problem, the physical buttons on the device act very erratically. I don't have the well-known power button issue, but I have something similar. The power button doesn't work on a long-press. If you long-press the power button it should give you the power menu, right? In my case, that never happens. What will happen is the display will turn off, as if I simply pressed and released it, like when you lock the phone. No matter how long you hold it in, the power menu will never appear.
Other buttons also act odd. The volume down button does work, but it also triggers the multitasking window to appear, every time I press it. This behaviour is not restricted to being in Android. Scrolling in CWM with the volume rocker, because that is the only way you can navigate this version of CWM, also does this. The log window will disappear and re-appear constantly, but sometimes it doesn't do this. This problem is only with the volume down button. The volume up button works just like it should. Other buttons do give problems, but they are not ever-persistent like the ones I mentioned above. The others just have constantly changing behaviour. They will perform different tasks at random when pressed, like open the dialer, or go home, or open the multitasking window as well, or even go back sometimes.
Now, I don't know what happened to Tytung on XDA, nor do I want to find out because it isn't important to me, but I'm not trying to advertise his work. I'm just trying every ROM I can find.
The phone does have water damage, but that was many years ago. No repairs were done to it, but it still works just like it should. The only problems are the ones I mentioned above. I do think that the water damage did do something to the buttons of the phone, but is it even possible that Deep Sleep can be affected by this? Isn't Deep Sleep something that is software-based?
I really would like to know what the is going on here
Any help would be greatly appreciated
I hope I provided enough information about this problem
Click to expand...
Click to collapse
I have a similar set up with the opposite problem: won't come out of deep sleep! Hate to hijack your topic but if anyone knows what could be causing this...?
OK so I got my Z4 tablet three days ago. Fantastic construction, fantastic specs on paper.
I had a Z tablet up until last weekend that I sold for a good price and got this as a much needed replacement.
Both are LTE versions.
Anyway, here are some things I've noticed and I would like to have your comments on.
1) The "antitheft" system for the first two days seemed to be a PITA. As my device is set for three users (me, my wife, my son), it kept popping for the others that it locked and needed MY credentials to unlock. I did unlock it at least five times for each, which means I can't really be... far from the device and let them use it. That I use two step authentication, makes things even harder. Once my "authenticator" phone was out of power and I had to wait several minutes to unlock the tablet. Yesterday I updated to latest firmware and I haven't noticed the issue since. But it's just one day, it may come back. Once (before updating firmware) I tried to disable My Xperia (although I love the find my device feature) so they could work, but it kept me "waiting". In the end I pressed back and it didn't get disabled. Any similar experiences with the theft protection?
2) Backlight (set in auto) seems to be too dark some times. I clicked on the intensity bar, set it brighter while STILL in auto (like it is now set to have a brighter "base value"?). Does this sound normal?
3) This is not a Z4 issue, I also had this in Z. It's probably a lollipop thing or I don't understand something properly. Clicking the volume buttons I can set it to "no" sound from home screen. Or so I think. Because even if I set it to "off", apps STILL have sound and I have to RE-adjust the volume to off from within the app (without the "priority buttons" under the volume bar)... Am I the only one to find this stupid?
4) Anybody notices some lag or ESPECIALLY stuck web browser, when other profiles (users) have run apps? If I reset the device and not visit the other profiles, the device is more snappy. If some other user goes in, even quiting every app they run, the device seems to get slower when back in "owner" user. Still fast but not as "snappy". Anybody noticed the same?
5) Any idea when we get Android M? Will we get 5.1 before that? I mean official firmware. Anybody?
6) Is there a way to go to test menu? The tablet Z method doesn't seem to work.
7) Serious. No restricted profiles. Why? Sony support replied that lollipop has this disabled only on 3G/LTE devices (that makes no sense), yet my Z was also LTE and both are on lollipop 5.0.2 and it DID have restricted profiles. What's up with that?
Thank you for your time people, have fun.
...wow
2) Yes.. brightness is usually set a little low at first for battery purposes.
3) There are different volumes for different things. Using the volume rocker on the home screen and putting it all the way down will only adjust ringer/notification volume. In-app sounds will use the media volume which you will need to adjust while media sounds are playing or you can adjust it in your sound settings. Not stupid imo, just gives more flexibility.
5) It'll come when it comes.. nobody knows except google and sony. I'd like to hope we'd get 5.1 before 6.
(pending something on the other questions above)
2) So the set value, when brightness is in "auto" is like a base value?
3) Well I find it stupid. Why: Because when I am in home screen I used to be able to manage the universal audio settings of the device. Turning device to mute, would turn it to mute. As simple as that. Also clicking a simple icon next to volume bar, you could separately adjust notification and ringer and stuff like that. Now? You THINK you set your device to mute, but you have only set the notifications. You sleep in a silent house (next to the wife or something), start a game, it YELLS with the last volume settings, ignoring that you set the device to mute in home screen and you have to "run" and re-adjust the volume to zero, usually with some delay (in the meantime waking everybody) since the device won't let you adjust anything while loading the game. No, I call this stupid.
5) Well if it won't delay 6, I don't mind for 5.1. But I want 6 the soonest possible.
Hey everyone
Recently, android 6.0 was built for the oneplus one and one of the bugs is that the hardware keys work but you cannot use them for long presses (for example long press menu for recents) and I am wondering if any other devices have this issue... and if some dev has found a solution, why am I posting in here? Well because it's kinda hard to find a device that has hardware keys and runs 6.0 (not a single samsung device has it, not a single htc device has it) some sony devices have it but then again they have no hardware navigation keys :/
Is anyone experiencing this issue as well with a built android 6.0 rom? leave your comment down below
Hi guys,
I just flashed android 10 on my oneplus 3 via Havoc v3.4.
I was wondering, whether somebody were able to help me with a kind of special problem.
So I'm using my home button to put the phone to sleep by long pressing it. This can be set in the phone settings. so far so good.
But now on android 10 the duration of said long press seems to be unnecessarily long, like over a second. Thats really annoying, when you just want to put your phone away and have to keep your finger on that capacity button for that extra amount of time.
So I was wondering, whether there might be a relatively simple way of tweaking the build.prop or something, to change the duration of said time_out ?
I already tried the hold/delay in the google settings, but that's just for touch inputs on the screen.
Also the forum search didn't pop up any usefull results.
Thanks so far!