Nevermind,plz delete because ctrl,shift,and letters do not work in fullscreen.
retroben said:
Nevermind,plz delete because ctrl,shift,and letters do not work in fullscreen.
Click to expand...
Click to collapse
What do you mean? If you want to type without the keyboard popping up, hold the mouse button down in the text section til the little position arrow pops up then let off the button and you can type without the the onscreen keyboard popping up. It does not work in all apps, but it does in a lot of them. All the keys work for me
No,My FireTV is rooted with the onscreen controls disabled via ADB's "pm disable" command.
I mean the game is less playable because the controls on my K400r don't respond when in fullscreen,which is thuggin stupid.
I hate how crappy and broken Flash is for Android,I wish someone could hurry up and make a hacked mod of Flash Player for Android with control fixes,full update,and performance tweaks.
retroben said:
No,My FireTV is rooted with the onscreen controls disabled via ADB's "pm disable" command.
I mean the game is less playable because the controls on my K400r don't respond when in fullscreen,which is thuggin stupid.
I hate how crappy and broken Flash is for Android,I wish someone could hurry up and make a hacked mod of Flash Player for Android with control fixes,full update,and performance tweaks.
Click to expand...
Click to collapse
Yes, I've noticed in DoxBox that the AFTV keeps control of the function keeps, the ctrl key and some others. Really annoying, and haven't taken time to figure out the best solution to fix that.
Hello all. Just yesterday my XT1575 started acting up, the navigation buttons - all three, Back, Home, Recents - are not working anymore. Initially, I thought it was a minor thing that could be sorted out with a reboot. I rebooted yet no show, still not working. I went to the extreme and did a factory reset, still no show. I fastbooted a fresh install, no show. I installed custom recovery and flashed a ROM, no show. But I made one discovery - in TWRP recovery the navigation buttons work just fine, and they are almost at the same location the main ones are on the phone screen when booted. This made me more skeptic if it was a hardware issue. As it is now I'm thinking of getting another screen to replace this one, but want to be sure this will fix the issue before shelling out more than $50 for a replacement screen.
Please all suggestions and advice is very welcome. I need to fix this. I love this phone. Thanks all.
maybe try to go to settings, enable dev options and then enable show touches
iks8 said:
maybe try to go to settings, enable dev options and then enable show touches
Click to expand...
Click to collapse
I also agree. Doing this will allow you to see if any key presses being registered when pressed in the affected spot.
Fix(?)...
OK. I stumbled on a fix, maybe a permanent fix, maybe not... I rooted with BETA-SuperSU-v2.62-3-20151211162651.zip directly flashed in TWRP recovery, no need messing with extracting anything and all those long steps in a related rooting thread. Flashed Xposed (xposed-v86-sdk23-arm64.zip), installed XposedInstaller_3.1.1.apk and after all this, installed Gravity module for Marshmallow. Go to Navigation bar tweaks in Gravity, activate master switch, enable navigation bar and scroll down and then increase the height and width of horizontal navigation bar to 124 or more (124 is the minimum for things to work again). And, voila... The navigation buttons work again. I hope this helps someone with this issue.
ezeuba said:
OK. I stumbled on a fix, maybe a permanent fix, maybe not... I rooted with BETA-SuperSU-v2.62-3-20151211162651.zip directly flashed in TWRP recovery, no need messing with extracting anything and all those long steps in a related rooting thread. Flashed Xposed (xposed-v86-sdk23-arm64.zip), installed XposedInstaller_3.1.1.apk and after all this, installed Gravity module for Marshmallow. Go to Navigation bar tweaks in Gravity, activate master switch, enable navigation bar and scroll down and then increase the height and width of horizontal navigation bar to 124 or more (124 is the minimum for things to work again). And, voila... The navigation buttons work again. I hope this helps someone with this issue.
Click to expand...
Click to collapse
Hi im having the same issue. How did yours happen? Mine happened after dropping my phone. Also I enabled Show Touches in Dev Options and the pointer would only go to the top of the nav bar and not on it even though my finger is on the nav bar.
I had this exact same issue with my Moto X Style. I was not willing to spend anything on this 3 year old device. Looked around for solutions but none worked. Finally settled for a 3rd party app which floats on screen, but very annoying. Found a commnet on a Youtube video who asked to change the display setting and it worked.
Settings -> Display -> Display Size. Change it from Default to large, larger or largest. It worked for me when I set Large. Just wanted to share it here, so it might help someone desparate.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Every time I press the mic button on the keyboard and try voice typing, the typing works but then the whole system UI stops responding to touch. I can't do anything inside any app or even in the main screen, only the physical buttons and touch within the lock screen works. Afterwards I have to access the shutdown menu from the lock screen (or use the button combination) in order to restart the device and restore touch response.
Is there a known issue with the Google Voice Typing in the device, or is it caused by some Xposed module or something?
The device is I-9300i running stock Androod Kitkat 4.4.4 Rom.
Nawarelsabaa said:
Every time I press the mic button on the keyboard and try voice typing, the typing works but then the whole system UI stops responding to touch. I can't do anything inside any app or even in the main screen, only the physical buttons and touch within the lock screen works. Afterwards I have to access the shutdown menu from the lock screen (or use the button combination) in order to restart the device and restore touch response.
Is there a known issue with the Google Voice Typing in the device, or is it caused by some Xposed module or something?
The device is I-9300i running stock Androod Kitkat 4.4.4 Rom.
Click to expand...
Click to collapse
Hi!
I had similar problems with other stock apps of android KitKat, sometimes I solved the problem deleting the app cache, in your case you can try to delete the cache of the app called Google text-to-speech. If it doesn't work try also to delete the cache of the keyboard that you're using (stock Samsung keyboard or any custom keyboard downloaded from the store).
Let me know if works!
CoDed99 said:
Hi!
I had similar problems with other stock apps of android KitKat, sometimes I solved the problem deleting the app cache, in your case you can try to delete the cache of the app called Google text-to-speech. If it doesn't work try also to delete the cache of the keyboard that you're using (stock Samsung keyboard or any custom keyboard downloaded from the store).
Let me know if works!
Click to expand...
Click to collapse
Sorry for abandoning the post. The issue resolved itself without any interference, so I can't tell whether clearing the cache helps or not. Thanks for responding anyway.
This has reached a point that those who don't depend BT calling may be able to use it as a daily driver. Just be sure to backup first!
The flashing on first boot during setup may cause issues for those with epilepsy. This is due to how to disable the second screen.
Working:
Camera! https://www.celsoazevedo.com/files/android/google-camera/f/GCam5.1.018-Arnova8G2-V1.7Beta2.apk is recommended with Nexus 6 HDR config in advanced settings.
Bluetooth (skips with wifi, and doesn't work in call)
NFC
Wifi -- two users have reported issues on their devices, while it works for others.
GPS
Sensors
Sound
Calls
Fingerprint
Data
WiFi tethering
Second screen disable hack
Not working and issues:
Screen glitches on first boot. Reboot and will be good after (part of hack to disable 2nd screen)
Tap to wake
Flashlight tile: install flashlight tile for kenzo in play store with root to workaround.
Slight animation glitch when switching activities due to second screen hack.
BT issues above, and doesn't work in call.
If you use camera immediately after turning on, it may not work. You must wait about a minute after powering for it to work (it will always work after).
Probably more.
TODO
BT fixes
Tap to wake
flashlight tile
get a proper 2nd screen fix like v20 working without additional issues. v20 dtsi hack doesn't work for us due to dual panel depending on partial update (most likely).
Repos (kernel is lineage-15.1 branch):
Kernel
v10-common
h901
blobs
Changes from AOSCP
Using Ruthless launcher instead of Luna
Two reverts to support substratum themes in addition to CypherOS' color manager.
Use opengapps for gapps, magisk for superuser (may have issues with modules).
Download
Buy me a beer with Bitcoin: 1h9o1Ei9thLd8JKRz3z7PUGhX6dtfnktY
Bugs with workarounds:
Wifi doesn't connect and MAC address is all zeroes (only some users):
This is a misc partition that has MAC address hardcoded to a randomly generated address. This should work permanently on any device with the issue so long as two aren't on the same network. If anyone would like instructions on how to modify with a new MAC address, let me know.
Image https://www.androidfilehost.com/?fid=818222786056033811
Instructions:
Place on /sdcard
Reboot to recovery (for advanced reboot in CypherOS hold reboot button for full menu)
From twrp terminal or adb shell, run: dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc
Reboot and enjoy fixed wifi
No charging indicator (but still charges):
Boot device plugged into power or USB and the indicator will work the entire power cycle. Working on a fix but not as trivial as I'd hoped.
Bootloop bug:
I recently got hit by the infinite bootloop bug, with the only workaround of disabling the big cluster. Here's a modified TWRP that only uses the little cluster (used Eliminator74's image):
https://www.androidfilehost.com/?fid=818222786056035329
And here's a little cluster only boot image from the titan kernel (our CAF kernel has msm_thermal issues with booting with disabled big cores, needs modifications):
https://www.androidfilehost.com/?fid=674106145207491774
Just uploaded a new build with the second screen backlight bleed fixed (from v20 for liblights).
Recently bluetooth was broken, and I need to debug further. In addition, the future builds (not yet posted) will be using the "lineage-15.1" branch of the kernel. I had based the kernel for this rom off the g4 cypheros kernel, but that Titan kernel is very buggy and has far worse performance (jittery mess compared to los 14.1, realized it's kernel not rom). The kernel also had very bad data corruption issues (also documented on g4).
Man thanks for working on our near forgotten devices. I cannot test this much ATM until things get a tad more stable, but you have my attention!
Just uploaded a new build. This is using the lineage-15 kernel branch on my github, which has CAF merged in and is buttery smooth compared to the Titan kernel .
BT is now back to the g4 state at least (fixed for music, still has some issues), and incall mic is now working correctly (updated mixer_paths.xml).
For me this is a daily driver now, but I also don't need fingerprint, nfc, or some other functionality that is no doubt broken (not sure yet due to minimal testing). Enjoy!
PS: due to all lg v10 now being unlockable, I'll be doing some test builds for the other variants in the next few days..
Downloaded the rom on my H901 and flashed it. It seems to work okay, there were some screen issues during the initial setup. The rom seems nice but with some issues (like the ones mentioned above - missing second screen, etc). The screen is shifted down so I can barely see the navigation bar. If ya need some testing of some options, settings, etc - let me know.
JuSkoch said:
Downloaded the rom on my H901 and flashed it. It seems to work okay, there were some screen issues during the initial setup. The rom seems nice but with some issues (like the ones mentioned above - missing second screen, etc). The screen is shifted down so I can barely see the navigation bar. If ya need some testing of some options, settings, etc - let me know.
Click to expand...
Click to collapse
Thank you! It looks like I messed up the init script in that build that's supposed to adjust the screen accordingly. Using adb, run the following (it's only needed once):
adb shell wm size 1440x2560
johngalt1 said:
Thank you! It looks like I messed up the init script in that build that's supposed to adjust the screen accordingly. Using adb, run the following (it's only needed once):
adb shell wm size 1440x2560
Click to expand...
Click to collapse
Thanks!. the screen now fits. However, I did seem to find another issue. Not sure why, but when I try to tap on the navbar buttons, only the upper half of that area works and the bottom half doesn't. Same thing happens with the statusbar. I think changing the screen size (or whatever else it could be) is making it so that the touch area is also reduced. I tried restarting it, but it still does it. Still usable but then that means i have to pay attention when I tap on the home button.
JuSkoch said:
Thanks!. the screen now fits. However, I did seem to find another issue. Not sure why, but when I try to tap on the navbar buttons, only the upper half of that area works and the bottom half doesn't. Same thing happens with the statusbar. I think changing the screen size (or whatever else it could be) is making it so that the touch area is also reduced. I tried restarting it, but it still does it. Still usable but then that means i have to pay attention when I tap on the home button.
Click to expand...
Click to collapse
Thank you for bringing this up. I had forgotten and got used to it early on. I'll fix this today.
Just uploaded a new build. Changes:
Tweaked touch offset
Synced CypherOS to 6.0.0 (fixes navbar on first boot and removes some features)
Fixed init script to set display res (part of the second screen disable hack)
Updated Ruthless Launcher
Will give this a try with my V10 since I don't use it as a daily driver, can play around with it. Shame they couldn't get the 2nd running properly but no biggie. Also what firmware is recommended for this? Here is a pic of the current software/firmware it has
Edit: sorry about the pic, shows up portrait in my gallery but landscape on here
Update: after wiping in TWRP (v 3.0.2-0), install gave me an error 7
"E3004: This package is for device: pplus, v10,h901; this device is. "
Sent from my LG-H918 using XDA Labs
amoot329 said:
Will give this a try with my V10 since I don't use it as a daily driver, can play around with it. Shame they couldn't get the 2nd running properly but no biggie. Also what firmware is recommended for this? Here is a pic of the current software/firmware it has
Edit: sorry about the pic, shows up portrait in my gallery but landscape on here
Update: after wiping in TWRP (v 3.0.2-0), install gave me an error 7
"E3004: This package is for device: pplus, v10,h901; this device is. "
Click to expand...
Click to collapse
Second screen is in the works for lineage on the v20, which we'll be able to use when it's ready ?.
Try twrp 3.2.1 https://forum.xda-developers.com/tmobile-lg-v10/development/twrp-3-2-1-h901-t3765971
Much thanks. Will give it a try and see.
Update: bingo, that did the trick ?
Probably sticking with stock rom on my v20. I rely on the Google certification for Netflix and my banking. Only have it rooted with magisk and no modules downloaded, passes safety net.
Sent from my LG-H918 using XDA Labs
---------- Post added at 09:24 PM ---------- Previous post was at 08:54 PM ----------
As previous poster mentioned, the navbar buttons only register the top half, bottom half has no reaction. During setup, popped up with wrong vendor image. I ignored the message, continued with setup. Lots of flashing graphical glitches and static screen. Using ruthless launcher, will test some more out
Sent from my LG-H918 using XDA Labs
amoot329 said:
Much thanks. Will give it a try and see.
Update: bingo, that did the trick ?
Probably sticking with stock rom on my v20. I rely on the Google certification for Netflix and my banking. Only have it rooted with magisk and no modules downloaded, passes safety net.
Sent from my LG-H918 using XDA Labs
---------- Post added at 09:24 PM ---------- Previous post was at 08:54 PM ----------
As previous poster mentioned, the navbar buttons only register the top half, bottom half has no reaction. During setup, popped up with wrong vendor image. I ignored the message, continued with setup. Lots of flashing graphical glitches and static screen. Using ruthless launcher, will test some more out
Click to expand...
Click to collapse
The navbar button one is weird and not as trivial as I'd hoped (but an issue with the 2nd screen hack). Regarding the glitches they shouldn't appear after the first reboot (in issues in OP).
May be all related to the whole screen aspect, when I try to swipe down the notifications bar, have to start the swipe gesture almost halfway down the status bar. With stock rom, youre usually able to start your swipe down gesture from the 2nd screen area.
Sent from my LG-H918 using XDA Labs
amoot329 said:
May be all related to the whole screen aspect, when I try to swipe down the notifications bar, have to start the swipe gesture almost halfway down the status bar. With stock rom, youre usually able to start your swipe down gesture from the 2nd screen area.
Click to expand...
Click to collapse
It is. The touchscreen is disabled in the second screen portion of the display. The v20 style disable hack doesn't work for our panels, but they also disable the touchscreen in the second screen.
For that functionality, the best hope we have is the work into lineage second screen work being done for v20 which we'll be able to use.
Wow, this is a giant step for us H901 users!
Going to DL and test.
Am I able to revert back to my current ROM after testing this?
Sent from my LG-H901 using Tapatalk
Double0EK said:
Wow, this is a giant step for us H901 users!
Going to DL and test.
Am I able to revert back to my current ROM after testing this?
Click to expand...
Click to collapse
Yes, be sure to fully backup in TWRP prior to flashing, and then you'll be able to restore if the current issues are too great for you. You'll even be able to backup this ROM after flashing and setting up to switch between them as v10 issues are tackled.
On another note, I think I may have finally found the issue with the touchscreen offset (bottom half of navbar not working) I'll be testing today.
New build uploaded. Changes:
- Fixed touchscreen alignment. Bottom of navbar now works.
- Synced with upstream CypherOS
- Testing navbar theme settings from gerrit.