Database Users

[Q] Navigation Bar not working in Portrait working in Landscape in Nexus 4

My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.

The softkeys are enabled within the framework.
Sent from my Nexus 4 using Tapatalk 4

Help
manojsap said:
My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
Click to expand...
Click to collapse
same issue here even i try a factory reset
I flash the stock rom again and no clue of what to do

The exact same issue here, started behaving quirky since 4.3 and went bat**** crazy after the update second 4.3 ota (1.8mb patch google released recently). i used developer options to show the on screen touch blobs as well and it registers touches in the nav bar area, it just will not work in portriat (or rather that section of the screen) It is extremely frustrating.
I even went as far as to use adb and fastboot to restore my phone to stock 4.3 which would remove all files and place a stock 4.3 directly from dev.google but still It doesn't work.

The same issue
Im having this exact issue just a few days after i install a new update i hope that its a software issue :crying: and if is not warranty will cover it?

Navigation Bar issue
Same problem here , wont respond on portrait mode.
I did try to downgrade my android version to 4.2.2 (from 4.3) after the factory reset did not work, that did not work either.
Any ideas? could use some help

I have the same problem, I tried to restore the 4.3, the 4.2, but the problem remains, I also tried the cyanogenmod and 4.4, but it still does not work the navbar in portrait mode ..
No one knows a solution to the problem? You may have a hardware problem? Who takes care of the navbar?

Having the same issue here. Works in Landscape but not portrait. It went spastic this morning randomnly opening the clock and pullin the bar down itself. Show touches showed it registering touches all around the nav bar then suddenly it stopped. I cant use the bar now at all in portrait but the random touches are gone. I downloaded a touch detector and it shows all the way up to where the nav bar would be then deadzone, but fine in landscape again

anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...

sorschumi said:
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
Click to expand...
Click to collapse
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.

Same issue here
Tried lot of things still not working .........
pls someone find the solution.......

skycoresaunish said:
Tried lot of things still not working .........
pls someone find the solution.......
Click to expand...
Click to collapse
I think it's a hardware problem. Mine just went bad as well.

I have this problem now, too. Google now NAVRING still works to open Google Now from the middle nav button, which is why I do not understand why they nav bars do not work at seemingly the bottom of the screen. It just seems like that part of the screen has died, though some times it randomly works....... what the hell is this?

Huawei ascend mate navbar problem
I have same problem. And not only that my landscape control also got messed up After factory reset.
Also when I try to scroll down the web page in landscape mode it dosent work on the same area. So does this mean screen is screen is not registering my touch.
Some times the middle button start acting funny. It operates by itself even the internet is off. Like virus or some thing I did checked with antivirus nothing found. After activating show touch option it is shows Google shortcut is always pressed.
Dont know how to fix. Dont know the reason pls. Help. Xda.

Do you use dt2w? For me, after enabling that feature this would happen after a while. The borders of the screen would become unresponsive. I disabled dt2w, rebooted and it was fine again.
Sent from my Nexus 4 using XDA Free mobile app

Hi to everyone!
I have the same problem since some days with the nav bar on stock 4.4.2. Factory reset + rom flash via fastboot + CM 11 innstallation did not help at all. I'll bring my Nexus 4 today back to the retailer for reparation / replacing.
I'll inform you guys about the report of service center but it can take up to 45 days.

Thanks. This works for me
haris0032 said:
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Click to expand...
Click to collapse
Hi, I was facing the same issue on my mako. It just started without any notice. Being a flashaholic I thought it could be due to something I installed. Tried a lot of differnt ROMS including stock but no luck. Read somewhere about the "Show touch" function in the developer options and found that almost 7.5mm of the bottom of screen was not responding to touch. I then installed the stock 4.4.3 ROM, rooted it and installed gravity box. In Gravity I changed the navigation bar height to 120% and selected "keep at bottom" for landscape. I am now able to use the phone. I wish some custom ROMS start implementing 52dp height option so we could use these directly. I tried using gravity with Mahdi ROM but there is some conflict and I cant see the recents button. Also, the NB reverts to original and it needs to be enabled again manually
But thanks anyways. I dont want to buy a new phone for the next 6 months and this will work well for me.
Cheers

PIE Inhibiting Bottom of Screen

I flashed PAC onto my Galaxy Note 10.1 just a few days ago when I ran across the PIE section in the settings, as I started toying with it I fell in love with how the nav bar was no longer hanging around the bottom all of the time, and I certainly liked PIE's interface better. However, ever since I started using the bottom 1/2 inch (interestingly about the size of the nav bar) hasn't been responsive to any touch input other than PIE. For example, if I was typing something, only the top of the spacebar would recognize a touch as a space, but the other, bottommost part would still operate if I swiped up to reveal PIE.
Is anyone aware of a fix to this problem, or is it just a tradeoff of having PIE, and this is just the way it is?
--John Galt from my GT-N8013

You can disable pie from the settings menu. You should also consider upgrading to 4.4 as JB is no longer receiving updates.

Well I know that I can disable PIE, but I want to know if the bottom of the screen not being functional is just something I have to deal with or if there is something that I can do about it.
I'm not aware of a 4.4 update for PAC for my device. I'm willing to try a nightly release, but I'm not sure how to tell what version a ROM is from the name of the .zip.
For example, what version is: pac_n8013-nightly-20140122.zip ? I can't anything except for "pac", "n8013" (my model no.), "nightly", and "2014".
The "0122" I'm not sure of.

Galt42 said:
Well I know that I can disable PIE, but I want to know if the bottom of the screen not being functional is just something I have to deal with or if there is something that I can do about it.
I'm not aware of a 4.4 update for PAC for my device. I'm willing to try a nightly release, but I'm not sure how to tell what version a ROM is from the name of the .zip.
For example, what version is: pac_n8013-nightly-20140122.zip ? I can't anything except for "pac", "n8013" (my model no.), "nightly", and "2014".
The "0122" I'm not sure of.
Click to expand...
Click to collapse
You can move the pie trigger to the side of the screen to see if you get the full touch screen back...
0122 is the date of the nightly build. Up to 0128 is 4.3 and from 0303 will be PAC-4.4
Sent from my ST18i using Tapatalk

Thank you for the clarification. I could be missing something, but there are no ROMs that have any release after 0128 (which I have now) for my device.
Seems like I'll have to wait for an update to roll around, but until then I'll keep playing with the settings and see if perhaps I have something not set properly.
Sent from my GT-N8013

Hybrid Properties
As I was thinking about the correlation between this problem and the nav bar, I realized that the nav bar was likely still active, but not visible because I clicked on the PIE fullscreen button in the quick settings. So I went to Hybrid Properties, clicked on interface, and set the "Nav. bar" slider to 0%, and clicked Apply. When that didn't work, I went back to that screen and found that the Nav. bar slider was all the way back at 100%. I've tried several times to get this to work, including adjusting the "Size" slider, clicking "Tablet UI" in the Launch screen and applying that, but nothing has stopped that slider from returning to it's default setting. Anyone know why this might be?

Cursor and Dialog Box icons glitch faulty incorrect

Hi Everyone,
Recently my phone was updated to Android v7 and since then I noticed that the icons for the cursor in text boxes and system dialog boxes have got messed up.
I read on Android central, one user posted that uninstalling Kaspersky fixed the issue, although in my case I don't have Kaspersky, so I can't go about uninstalling all apps, got a hell lot of them!
1drv.ms/i/s!AigR1NGUKZ2stFWGsf_bkkIg_WEa
1drv.ms/i/s!AigR1NGUKZ2stFa4-NP8jEiQCuMs
1drv.ms/i/s!AigR1NGUKZ2stFRZcp6bHn6VE_JE
It's frustrating everytime i see this... Please help me...

I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted

jivenene said:
I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted
Click to expand...
Click to collapse
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.

jivenene said:
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.
Click to expand...
Click to collapse
I have those glitches as well apart from what i posted.
I read online its because of some app messing things up. I seriously don't want to reset and start testing this out one app at a time. It will take at least a few days to get back up to speed.
Thanks :crying:

Navigation bar not working in EPD

Hello,
I am suffering from a really annoying problem for the last month and I cannot find a solution. I have tried to flash several firmwares but the EPD navigation bar seems to become somehow irresponsibe making the phone quite unusable.
With LP EU (5.0.0-EU1.1.87a and 5.0.0-EU1.1.124b) the navigation bar on the EPD seems to be working on the YotaHub without problems, I can navigate and I can unlock the screen by either double tapping or sliding. However, when I enable the YotaMirror the screen is mirrored but the Navigation bar becomes somehow disabled so I cannot exit the application that is running. The only way is turning on the normal screen so the EPD goes back to the YotaHub (quite annoying).
With LP RU (5.0.0-RU1.1.124 and 134 sideload) the YotaHub works fine but when I enable the YotaMirror a message saying "YotaMirror mode is enabled" with a help message explaining how it works and two buttons "Skip" and "Continue" which do not respond to any action; making it impossible to leave that screen. The only way to get rid of this is going to the normal screen and opening the YotaHub settings. This error seems to be already reported by another user: https://forum.xda-developers.com/yo...phone-201-stuck-androis-5-0-ru-1-124-t3571739
In MM (EU and RU) the area of the Navigation bar, no matter if YotaHub or YottaMirror seems irresponsible to any actions; so I cannot move across the panels in YotaHub nor exit an application opened in YotaMirror.
I thought this could be a hardware issue but I have discarded the option knowing that in LP it works and in both LP and MM the double tap unlocking feature (once enabled) unlocks the screen even being tap on that area.
I will continue flashing firmwares and eventually come back to the version of LP that was working fine (I cannot recall which one was it so I am downloading and trying most of them). But any help would be appreciated.
Thanks!

jaboto said:
Hello,
I am suffering from a really annoying problem for the last month and I cannot find a solution. I have tried to flash several firmwares but the EPD navigation bar seems to become somehow irresponsibe making the phone quite unusable.
With LP EU (5.0.0-EU1.1.87a and 5.0.0-EU1.1.124b) the navigation bar on the EPD seems to be working on the YotaHub without problems, I can navigate and I can unlock the screen by either double tapping or sliding. However, when I enable the YotaMirror the screen is mirrored but the Navigation bar becomes somehow disabled so I cannot exit the application that is running. The only way is turning on the normal screen so the EPD goes back to the YotaHub (quite annoying).
With LP RU (5.0.0-RU1.1.124 and 134 sideload) the YotaHub works fine but when I enable the YotaMirror a message saying "YotaMirror mode is enabled" with a help message explaining how it works and two buttons "Skip" and "Continue" which do not respond to any action; making it impossible to leave that screen. The only way to get rid of this is going to the normal screen and opening the YotaHub settings. This error seems to be already reported by another user: https://forum.xda-developers.com/yo...phone-201-stuck-androis-5-0-ru-1-124-t3571739
In MM (EU and RU) the area of the Navigation bar, no matter if YotaHub or YottaMirror seems irresponsible to any actions; so I cannot move across the panels in YotaHub nor exit an application opened in YotaMirror.
I thought this could be a hardware issue but I have discarded the option knowing that in LP it works and in both LP and MM the double tap unlocking feature (once enabled) unlocks the screen even being tap on that area.
I will continue flashing firmwares and eventually come back to the version of LP that was working fine (I cannot recall which one was it so I am downloading and trying most of them). But any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Can you unlock the back display without doubletap? So by using the power button when the epd display is facing up. IE, does it still correctly sense which display is facing up?

Hi @tomgaga Thanks for your response.
I can unlock the screen with in every mode: double tap, swipe and power.
I can fully confirm that this is not a hardware issue, meaning that the screen gets the touches as I have just captured the events with adb and saw how the screen gets the input event on the area of the screen "YotaMirror is enabled" that allows me to "Continue" or "Skip". So the taps are registered but it seems that this notification doesn't seems to work.
Anyone knows how to avoid this notification? I think this could solve the issue...

jaboto said:
Hi @tomgaga Thanks for your response.
I can unlock the screen with in every mode: double tap, swipe and power.
I can fully confirm that this is not a hardware issue, meaning that the screen gets the touches as I have just captured the events with adb and saw how the screen gets the input event on the area of the screen "YotaMirror is enabled" that allows me to "Continue" or "Skip". So the taps are registered but it seems that this notification doesn't seems to work.
Anyone knows how to avoid this notification? I think this could solve the issue...
Click to expand...
Click to collapse
I had this problem when using gravitybox from xposed and made an adjustment to the navigation bar. You got any mods installed?

@tomgaga , I didn't install xposed until now, I also tried to increase the size of the navbar with a mod but it seems to not doing the trick (I have the impression that the nav bar on the EPD doesn't get affected by this). When you had this issue did it go away by just removing the mod? Or you increased the size? However, I believe that after a full reset this should be gone...
Danke!

jaboto said:
@tomgaga , I didn't install xposed until now, I also tried to increase the size of the navbar with a mod but it seems to not doing the trick (I have the impression that the nav bar on the EPD doesn't get affected by this). When you had this issue did it go away by just removing the mod? Or you increased the size? However, I believe that after a full reset this should be gone...
Danke!
Click to expand...
Click to collapse
Yeah if you reinstalled the system images and reset the data, then any mod should be gone, but not if you just did a factory reset.
And the problem went away after I removed the mod yes.

tomgaga said:
Yeah if you reinstalled the system images and reset the data, then any mod should be gone, but not if you just did a factory reset.
And the problem went away after I removed the mod yes.
Click to expand...
Click to collapse
Hi again @tomgaga. The thing is that I reinstalled the ROM many times and I did full factory reset every time, so for me it seems there is an issue coming from somewhere else... Thanks anyway for your comments.

[ROM][UNOFFICIAL][Oreo 8.1] CypherOS 6.0.0 [h901] 5/6/2018

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.