blissroms-x86 / bug_reports Goto Github PK

I attached a ProLite T1731SAW to a ONDA MiniPC with Win 10 installed and touch input works just fine. When booting BlissOS live system from USB the touch doesn't work at all (mouse and keyboard all ok). The monitor uses the eGalax Inc. USB TouchController, is there any kernel supporting this input device?

Steps To Reproduce

Expected behavior

Screenshots

BlissRoms source:

• Link to last merged Gerrit commit:

Device:

• Codename (ex. bullhead):
• Build date (ex. 20200204):

Additional information

The computer that Im using has a broken internal ssd so I tried to revive the computer by trying out android 86 distro's with an external ssd. I already installed primeos on it and I decided that I did not like it so I reformatted the external ssd and tried with blissos 86. When I booted from the external ssd I found all of my primeos apps on a different ui even though I erased the drive. There were left over system apps frome Primeos like termux and gamecenter. I think it's possible because II was a quick erase so the data was not technically gone and somehow the installer for bliss restored that data. I had to install again but with a fuller erase and that time it worked.

Steps To Reproduce

1. Install primeos (maybe other android distros would produce the same bug I am not sure)
2. Quick reformat your drive (A slow but fuller erase might not work)
3. Install Bliss 86

Expected behavior
Bliss os overwriting the data and not installing on top of that or prompting me that it was gonna restore data.

Additional information
I think this bug could be turned into a feature if a prompt was added. This was a Bliss os 14 Install.

Basically I tried Bliss OS Because Android x86 would corrupt when I restart my touch computer without a keyboard but when I did it would boot loop or not boot at all I tried every version of Bliss OS but it would still not boot I will give specs to any willing developers.

Name: ASUS PRO A4110
Model number: A4110-BD198M
Processor Type: Intel® Celeron® J3160 64 bit
Graphics: Intel® HD Graphics
Memory: 4GB
Storage: 128GB SSD

On a kodlis gn41 and minis forum GN31 mini pc bliss os 12 will not boot past the logo, just hangs.

Steps To Reproduce

run live form usb and installed to a partion

Expected behavior

Screenshots

BlissRoms source:

• Link to last merged Gerrit commit:

Device:

• Codename (ex. bullhead):
• Build date (ex. 20200204):

Additional information

Steps To Reproduce

Expected behavior

Screenshots

BlissRoms source:

• Link to last merged Gerrit commit:

Device:

• Codename (ex. bullhead):
• Build date (ex. 20200204):

Additional information

is there any version ready for laas/cloud?

When I first boot the latest Bliss OS 12 build on my Microsoft SP3, SystemUI crashes and returns to a lock screen. It repeats when I swipe up, with the same stacktrace.

Steps To Reproduce

1. Install the OS
2. Unlock the lock screen

Expected behavior

It shouldn't crash

BlissRoms source:

Probably the file mentioned on this line

at com.android.systemui.statusbar.policy.KeyButtonDrawable.draw(KeyButtonDrawable.java:271)

Device:

• Microsoft Surface Pro 3
• Build date (ex. 20200204): 20200327

Additional information

Here's a stack trace: https://pastebin.com/raw/X4gzns6c

I suspect Rescue Party comes into play and causes #2.

The Linux Surface project offers currently the best experience for Surface devices. Would be cool if not only "regular" desktop Linux distributions could benefit from it but also BlissOS. Just an hour ago they've announced an IPTS daemon as a replacement for the older in-kernel driver.

Links:

The Linux Surface project: https://github.com/linux-surface/linux-surface/

Their announcements: linux-surface/linux-surface#96

Steps To Reproduce

1. The instaĺlation completes successfully
2. And they you try to boot bliss os 12...it starts displaying the bliss logo and then the pc shuts down.

Expected behavior

Screenshots

Device:
Hp Elitebook 820 g1
Core i5
Intel hd graphics
8gb Ram

Additional information

Steps To Reproduce

1. Download Bliss-OS-Merkaba-v12.6-android_x86_64-OFFICIAL-202005041401_k-k5.6.2-si-yling-rmi_m-10.0.8-ax86_ld-2.4.100-ax86-ma_dg-_dh-_mg-_gms_cros-hd_cros-wv and install it
2. Reboot the computer and set to boot on the android that already installed
3. Enter Android x86 and wait the boot animation
4. Congrats, the laptop shuted down

Expected behavior

I think it normal on the first time booting and the laptop will turn on again automaticly, but it didn't.

Screenshots

BlissRoms source:

• Link to last merged Gerrit commit: https://sourceforge.net/projects/blissos-dev/files/merkaba/Bliss-OS-Merkaba-v12.6-android_x86_64-OFFICIAL-202005041401_k-k5.6.2-si-yling-rmi_m-10.0.8-ax86_ld-2.4.100-ax86-ma_dg-_dh-_mg-_gms_cros-hd_cros-wv.iso/download

Device:

• Codename (ex. bullhead): ASUS Vivobook Flip 14 TP410UA
• Spec : Intel core i3-7100 U, 2.4 GHz, 4 GB DDR4 RAM, and
  

Additional information

Steps To Reproduce

1. Enable Developer Mode
2. Enable "ADB over network" in Developer Mode
3. Try to connect to the device through by using ``adb connect `
4. The RSA authentication window is not shown and the connection will fail due to a lack of ADB_VENDOR_KEYS

Expected behavior

• System generates the appropriate keys
• System displays the authentication screen
• Connection is established

Screenshots

martin@tabarchat:~$ adb connect 192.168.1.101
* daemon not running; starting now at tcp:5037
* daemon started successfully
failed to authenticate to 192.168.1.101:5555
martin@tabarchat:~$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

BlissRoms source:

• Bliss version: 11.13 (official build)
• Build: android_x86_64_userdebug 9 PQ2A.190405.003 eng.electr.20201113.152513 test-keys

Device:

• Codename (ex. bullhead): Virtualbox
• Build date (ex. 20200204): 20201113

Additional information

• Possible workarounds include manually pushing a keyfile to data/misc/adb/adb_keys/

I'm not too tech savy, but Androidx86-Installv26.0003.exe created an error log and told me to report it, so I guess the log should go here?
AndroidInstall_797.log

Steps To Reproduce

Hello , lot of intel laptops suffers from BD PROCHOT flag that throttles cpu when charging , its easily fixable in windows using throttlestop and linux using msr tools

me and my friend tried to port msr tools to android x86 and compiled it using ndk in Android 7.x source

copied binary files and chmoded them then modprobe msr

rdmsr 0x1FC

it returns this error "rdmsr: open : no such file or directory"

Expected behavior

cpu gets throttled to 25 % while plugged in
Screenshots

nonee

Device:

• intel cpus on laptops

Additional information

here is the source code of what my friend compiled

https://github.com/hmtheboy154/msr-tools-android

reference :

https://github.com/DivyanshuVerma/throttlestop-linux

(i wouldnt consider this as a bug in bliss os itself but it makes system buggy by limiting its resources . i shared this because some of users suffer from it without knowing the issue or thinking that android x86 is slow and laggy)

Trying to enable wifi after waking pc from sleep does not enable it, it's just stuck on trying to enable wifi, rebooting doesn't solve the issue either

Steps To Reproduce

1. Make pc go to sleep
2. leave sleep and power up the pc, Wifi won't work

Expected behavior
Wifi gets enabled . . .

Device:

• Device : Lenovo Thinkpad Yoga X1 3rd Gen

• Build date (ex. 20200204): Bliss 11.10 - 20200411

Additional Info:
Wireless card is : Intel Dual-Band Wireless AC 8265