[akasection]

Hmm.. interesting experience…

or maybe it because I disabled C-power state on BIOS?

 

[akasection]

yeah, I rephrased it wrong, actually I’m not implying that touchscreen driver failed because of windows, but the ‘hack’ one.

Now I think I’ve explained the real problem, is there any way to fix that behaviour? It’s kinda hassle that I need to “suspend” first everytime I want to use the touchscreen.

[akasection]

One of popular case that Windows system affecting dualboot is the fast startup will break other OS if the windows is the host.

Well, I think I need to clarify the timeline.

1. When I posted the thread, I was on windows 1709 and trying to live-cd Android via USB.
2. After that, I tried to find solutions, and someone in stackoverflow suggested that I need to force “suspend” the android.
3. I initially tried to press power button, but it behaves strangely, instead of sleep, it does power options (reboot, turn off)
4. via linux terminal (Pressing Ctrl + Alt+ 1), I tried to exec echo mem > /sys/power/state ; surprisingly, after suspended and wakeup, touchscreen now works.
5. And then I install android and continue to boot windows, update to 1803.
6. When I switched back to Android and tried to do the ‘hack’, turns out now the Android is cannot even suspend. Even I leave it for 20-30 mins. It won’t sleep. it just screen off.
7. At this point, I assumed that Windows 1803 did something to PC wake/sleep system that makes android86/phoenixOS fail to do the hack, hence the second post of mine.

So, basically the touchscreen driver on Android is actually never work to begin with. It’s the hack who enabled it. That’s all.

[akasection]

Hugh wrote:

akasection wrote:

no no no.. I just use the “Install” when boot the android, and follow the wizard. that’s all. And it would be dual-boot (just like ubuntu alongside windows)

In that case, I don’t see how a Windows update would have any effect.

Not directly, it’s just after update, my Android OS can’t suspend/sleep at all, which is I can’t do ‘touchscreen enable’ hack. ( ctrl+alt+1 and then echo mem > /sys/power/state)

FUCKTECHTABLET wrote:

Well, not all game will run on Android x86, as you already know. Even Qualcomm cpu is preferred to other name like Exynos or MediaTek in case of gaming. I already have 2 laptop, and I will have 2 tablet, it is OK. If I can merger them all to only 1 machine.

Yes, I am well aware of that, good thing my selection of games works on Intel CPU (no issue so far). And I play steam games too on Windows, so it’s two-birds in a stone. Man, this cube is almost all-rounder good thing, almost.

[akasection]

Hugh wrote:

I’ve never tried any of this so my advice isn’t worth much. In what way are you running Android under Windows? Are you using Hyper V or some other virtualization? How touch events get to the guest OS is unknown to me but ought to involve some device virtualization, something with a lot of ways of going wrong (I would imagine). The appropriate Android driver for touch under Windows might well be different from the Android driver when Android is running on the bare metal. If you run Android stand-alone, not under Windows, then any driver problems cannot be Windows problems. Then you just have pure Android problems. Sounds simpler to me. Some folks are complaining that Windows updates break the pen driver (I think) and that the fix is to find the old driver and re-install it. I assume that you are not talking about pen input so this is irrelevant. I haven’t tried a pen yet.

no no no.. I just use the “Install” when boot the android, and follow the wizard. that’s all. And it would be dual-boot (just like ubuntu alongside windows)

It’s just you need to enable USB boot. The android runs natively, not virtual. Driver is the one problem though. And I realized Cube Mix Plus sucks in multitouch interaction. Single touch is absolutely fine.

In addition, the windows runs fine, even after update (except the pen driver, yeah, but I don’t use it. It’s not comfy drawing on non-OGS laminated screen)

FUCKTECHTABLET wrote:

akasection wrote:

@virgosun Because I need both Android and Windows OS? I think that’s obvious. And Galaxy Tab A6 only scores ~40.000 in antutu, while Cube Mix Plus scores almost 200.000 @hugh ya, under windows, using existing NTFS. I initially tried to separate it into new partition, but it almost has no difference.

You can buy both. And they both will do there good job I am going to sell my Cube I will by a refurbish Galaxy Book and a refurbish Galaxy Tab

Well… carrying two extra tablets while having one laptop is TRULY not a wise option. You realizd when I mention antutu, it means I used it for gaming, right? and most android tablets are laggy.

I just wish I can tinker this Cube Mix touchscreen so it would be more responsive on multitouch (2-10 fingers).

[akasection]

@virgosun

Because I need both Android and Windows OS? I think that’s obvious.

And Galaxy Tab A6 only scores ~40.000 in antutu, while Cube Mix Plus scores almost 200.000

@Hugh

ya, under windows, using existing NTFS. I initially tried to separate it into new partition, but it almost has no difference.

[akasection]

well, so far I blame Spring update…

After I revert to 1709, touchscreen on android starts working again (still, it needs to be sleep/suspend first after boot, and power button does not work as sleep button)

[Author]

Posts