yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] electrikjesus:
I noticed that too. There was a change in the kernel for this that I have yet to be able to track down. It's likely a kernel config flag that was changed or missing in the android_x86_64 defconfig

As for the firmware, If wifi works better without it, I recommend just doing the touchscreen firmware then. Like I stated a page or two back, I haven't been able to test any changes to my IPTS kernels, so I'm kinda hitting a wall there...
[BLISS ROMS Development] protectivedad:
There is no sdcardfs.ko module in the image. If you are able to generate one I can drop it in the system and see if it works.

I haven't even needed to update the touchscreen firmware. But I am focusing on the 4.20 kernel so it is hard without a working internal storage to really test.
[BLISS ROMS Development] beacool:
My tablet touchscreen is silead mssl1680 can someone edit the rom for it?
[BLISS ROMS Development] electrikjesus:
If you can point to the sources of where I can find Linux firmware or drivers for it, then maybe
[BLISS ROMS Development] KornyeiDavid:
Hi, i have seen you use the bliss os on a Surface Go, and i would like to know could you use the camera and messenger app on your device ?

I couldnt use on my surface go and if you can i would like to kniw how should i solve the problem.

If you could say how could i do log files or anything else what could help your or bliss team work i will try.

Thanks in advance
[BLISS ROMS Development] protectivedad:
To the best of my knowledge there are no kernel drivers for the cameras on the Surface Go. So no linux or android camera usage. After the BlissOS loads up if you have an external keryboard or keyboard cover attached pressing alt-f1 will go to a command prompt for entering logcat/etc, alt-f7 will get you back.
[BLISS ROMS Development] beacool:
Thank you,

I found this

https://github.com/onitake/gsl-firmware/tree/master/firmware/teclast/x5_pro
[BLISS ROMS Development] electrikjesus:
OK, you're the second person that's let me know about updates I should pull from onitake/gsi-firmware, so I guess that's my sign ;)
[BLISS ROMS Development] beacool:
Thank you so much!! Please inform me when you done :)
[BLISS ROMS Development] ramirezit:
5/26 build 1304 - no sdcard directories created

feedback on 5/26 build 1304 on a Dell 64 Touchscreen Inspiron. So close. It will be fantastic after two issues:

1. installation does not create the standard SDCARD directories (Documents, Downloads, Music...)

2. after changing the theme in Blissify settings, crashes the UI when rotating screen. even after reverting to default theme, the issue persists. Easy enough. Don't switch themes.

Issue #1 is critical, and after that's fixed I will sing your praises high and wide, cause this is freaking fantastic work! thanks.

---------- Post added at 10:13 AM ---------- Previous post was at 10:00 AM ----------

update:

same directories/symlink issue with all 5/26 builds 1104, 1304 & 1326 (installed on its own ext4 partition) going down line of older builds until one creates directories properly, hopefully
[BLISS ROMS Development] Mohamed Anwar:
Is this the Official Bliss Team?

Hello World,Hello Bliss Team.

Is this the Official Bliss Team on Facebook?

It's link on facebook:https://www.facebook.com/BlissFamilyOfROMs/

Thanks :)
[BLISS ROMS Development] electrikjesus:
What kernel build we're you using? This may be the sdcardfs issue we're having on kernel-4.20
[BLISS ROMS Development] electrikjesus:
So you're trying to donate some CPU cycles for our Jenkins server?
[BLISS ROMS Development] laharl_22:
Which version are compatible 32 bit please?
[BLISS ROMS Development] ramirezit:
thanks for replying.

Update: no go on all kernels from 20 down to whatever Jan 19 release was. Install USB also EFI. EFI hard drive, no security, NOT created user directories ...Documents, Music,...etc.

- Installed onto another USB, read only sys, squeezed onto a 16Giger ALL works perfectly, (except for aforementioned minor bug of UI crash after Theme change.

Would love to throw your amazing product onto an internal SSD. that's all my technical depth. Hope you have some useful thoughts. THANKS

---------- Post added at 06:25 PM ---------- Previous post was at 06:12 PM ----------

...so I can't fix, but I got a possible workaround until its fixed.

dd USB onto SSD. Replace all USB with symliniks to SSD. USB is only for initial boot. How hard is that for me to do? any way to automate it? Dont know command line enough to create a pretty script to do that. Any ideas?
[BLISS ROMS Development] noobernz:
Hey, Do you have the touchscreen working on a Surface Pro? If so did you have to create your own build and then add the jake firmware? I have it working on 11.6 IPTS version with that firmware but not on anything after.

Thanks!
[BLISS ROMS Development] Pact:
I confirm this issue too. I downloaded the 4.20 kernel version, upgraded from a previous version installed on an SSD from the live USB menu upgrade option, and after restarting the sdcard/user data space simply disappeared - non existent everywhere I checked, on Solid Explorer etc

Oh, and I also affirm that following statement - honestly except for well-known issues (hardware video playback etc.) everything just works! :good: Testing on a Thinkpad X220T, and a VAIO Pro 11 (coincidentally, Torvalds himself once uses that series)

Will try a fresh install from the newest builds using 19.3.2 kernels soon
[BLISS ROMS Development] electrikjesus:
I'm working on a fix for sdcardfs on Kernel-4.20. Let me make sure things are working right and if so, I might push the update out soon.
[BLISS ROMS Development] Pact:
Good news! I installed the latest, 3-days-ago release that has 4.19 kernel over my previous 4.20 install (dirty flashing?) and I confirm that sdcard/user data space appeared as normal back alongside all data stored, which I thought was lost forever.

Laptops spec, for additional info:

X220 Tablet

i5 2520M

6GB RAM

256GB SSD

1366x768 resolution

Wacom ISDv4 panel, pressure sensitivity works as well as apps that uses it

Automatic screen rotation and screen rotate physical button doesn't work

VAIO Pro 11

i5 4200U

4GB RAM

128GB SSD

fullHD touchscreen IPS, touch works splendidly

Both:

Detects fat32-formatted USB stick

Detects NTFS-formatted 1TB ext hard disk

Doesn't recognise exfat-formatted SD card
[BLISS ROMS Development] electrikjesus:
exfat-formatted sdcard... Hmm... I will have to look into that one.
[BLISS ROMS Development] protectivedad:
I'm using the Surface Go not the Pro. There is no IPTS required on the Go.
[BLISS ROMS Development] noobernz:
Are there instructions out there that could point someone with no experience in building code to create an IPTS build off the latest version?

Thanks!
[BLISS ROMS Development] KornyeiDavid:
Thanks a lot :D
[BLISS ROMS Development] electrikjesus:
Follow the instructions to build from the OP, and ignore the first build. Make clean, then CD to kernel/ and git checkout the target ipts kernel, then make clean && make mrproper.

Then CD back to the project folder, and run the build again, this time it will build with the target kernel
[BLISS ROMS Development] jeraldsatya2000:
Hello Bliss OS team

Can you please bring emulator detection and keymapper for games like Call of Duty, PUBG Mobile and etc???

Really loved the working of BlissOS in my PC
[BLISS ROMS Development] electrikjesus:
Emulator detection? I can only see that being used for dishonesty, please correct me if I'm wrong.
[BLISS ROMS Development] jeraldsatya2000:
Sorry for that if I'm wrong

At least can you please add keymapper for playing FPS, RPG games?
[BLISS ROMS Development] Darrian:
I have a Surface Go, too. I would also like to know if you have to build a custom version or if you are just downloading it. And, if you are downloading it, which file are you using? I haven't tried it for a while, but the last time I did, touch didn't work (and probably other stuff, too, but I couldn't even get past setup without an input method).
[BLISS ROMS Development] ElfinJNoty:
You may search for, install, and use any of the many keymapping .apk's found around the web. I do believe there are several in the Play Store

We will not be including in our public releases at this time.

Please understand this is our decision to make, and that decision has been made.
[BLISS ROMS Development] protectivedad:
I tried all four of the latest builds. They all worked to varying degrees. The 4.9 kernel had a problem with the power button. The 4.19 kernel had the most working only the cameras failed, but that was expected because there are no drivers. The 4.20 kernel worked but Google's sdcardfs module has not been included in the image so there are file system issues.

The 4.19 kernel version has too flavours the Mesa 18 and Mesa 19 version I am using the 19 version. They both seemed to work the same.

If you haven't already read the first page of this post where the poster describes the image file names and how they are put together.

There are "hiccups" I have noticed at times after booting:

1) The touch screen is "sticky" or unresponsive;

2) The wifi sometimes won't turn on properly after booting;

3) The touchpad on the surface cover doesn't work (but the keyboard still does).

These occur after boot if I don't unlock the screen immediately and I let the tablet "sit".

For example the following is what I observed while writing this:

1) Turn on my Surface;

2) Select Bliss OS;

3) Text screen shows up, finds android;

4) Bliss boot logo shows, bliss boot image shows;

5) Lock screen shows, wifi shows empty, battery shows a non-zero percentage;

6) Lock screen messages show, wifi connnects;

At this point if I don't touch the tablet and I let it sit a number of things can happen:

1) Screen blinks, wifi symbol disappears (not empty, but gone), battery shows 0%;

At this point the screen seems unresponsive but the power button works and I can use the touch screen to select restart. The keyboard cover works and I can ALT-F1 to the boot terminal to see what's going on.

2) Nothing changes and the screen just "freezes".

At this point the screen seems unresponsive. The power button does not work. The keyboard cover works and I can ALT-F1 to the boot terminal to see what's going on.

Typing reboot at the boot terminal reboots the surface (or hold the power button for long enough to force shutdown).

So from your post I get the idea you don't have a cover, so the most successful strategy is that immediately after boot make sure to touch the touchscreen. If I touch the screen and unlock it seems to work quite well. For my installed system the "sweet spot" is when the "SuperSU needs updating" message shows on my lock screen. But NEVER try to update the SuperSU just ignore the message, it is just my trigger to touch the screen. You may need to find a similar trigger on the install screens. Even if the system is not accepting input it might be helpful to touch the screen.

Good luck. As I get time I am capturing logs and looking at them to hopefully track some of the problems.
[BLISS ROMS Development] Darrian:
Thank you for all the info. I wasn't expecting that much detail!
[BLISS ROMS Development] electrikjesus:
This tells me that you are running into the sleep issue we have on Pie. Try to disable lockscreen in Settings or Blissify, and set the sleep to timeout at like 30 min (Or use the Caffeine QS toggle). If you do get stuck in this again, hit alt-f1, and type in "svc wifi disable && stop && start" in order to restart the session the right way and not have wifi lock up on you ;)

Good news is that screen blanking is now working right too, so if you do have a typecover on a model where the sensors work, it should put the screen to sleep at least. Still working on a proper Doze solution for PC's
[BLISS ROMS Development] protectivedad:
Thanks, I came to the same conclusion. I'll use your suggestions for stopping the issue from happening, but of course those can't be implemented before the system is installed for people having problems installing because they waited a little too long before interacting with the device during installation.

I was trying to duplicate the jakeday arguments for module loading by adding them to the kernel command line. The problem is that a commit in 2017 changed the modprobe to symlink to init instead of toybox. So the modprobe being used doesn't check the kernel command line like the toybox one does. Plus when I looked at the init source I can't find any mention of modprobe at all. Any tips on being able to add parameters to the atk10k_core modprobe? Plus when the DEBUG=1/2 is added to the boot the system uses the toybox modprobe (during the shell escape which then uses the command line options) which might cause problems with trying to figure out what is going on.

Anyway I'm trying to build it but I got errors on the "bash build-x86.sh -s" command. Is the "https://github.com/BlissRoms-x86/manifest" readme still valid?
[BLISS ROMS Development] electrikjesus:
If you look in root/init.android_x86_64.rc or something like it should be in there. Those are where we normally add our modprobe options. You Can't really edit it from the ROM though, it'll have to be through a Linux install, or in the source before compile.

If I go the route Android-x86 uses to disable the lockscreen, it can't be enabled again, so I am working to try and get the overlay values to take as a default. But until that's fixed, people are just going to have to read before trying.

When I started down this rabbit hole of fixing issues for Pie on PC's, I didn't realize how messed up this version of Wonderland was...
[BLISS ROMS Development] Lagg4free:
Hey there,

first time i got my Cube mix plus booted in BlissOs!!!

Amazing!!!

But:

only with --- Bliss-v11.9--OFFICIAL-20190525-2025_x86_64_k-k4.9.153_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org.iso

All other Builds freezes while booting in live!!!

The Booting build is really great, beside two little things,

1. Touchscreen isn't very reactive, its hard to use the tablet with fingers, funny with wacom pen everything is

working like it should (so could i improve the touchscreen by myself or do i have to wait for improvements from the builder?)

2. Pressing the Power key do not send to sleep (always the andvanced shutdown dialog pops up) - I tried Sleep earlysuspend=1

in build.prop but changes unfortunately nothing. Is there an further tip to get it work?

So keep up going and hopefully someone helps me out off this little troubles.
[BLISS ROMS Development] jeraldsatya2000:
Okay

Is there any plan to include external GPU for working in PCs ?

At least it can be made as per the request of myself and other fellow users

I think Tencent Gaming Buddy is using External GPU for its working....
[BLISS ROMS Development] Ahmed elrased:
The Bliss-v11.9 k4.20 was tested on a lenovo yoga 710-15isk touchscreen machine that does not work

The Bliss-v11.9 k4.9 The sound is very low. Mike's definition does not work. How to raise audio to 150 like Ubuntu

The most important problem come after the installation of Android on Partition ext4. Boot takes a long time 5 minutes

Why the individual system is not in the folder instead of what hue compressed on the system.Img to be faster in boot

I still do not know how Mount Internal Windows Partition (NTFS) does not make it automatic

Not all people are programmers like you

Thank you
[BLISS ROMS Development] charackthe:
HP x360 Pavillion (14-ba101nt), issues for the people who are planning to install it:

1) Sound output breaks after a reboot or two sometimes doesn't work at all from the start (it forces towards to the 3.5mm jack, bluetooth was not able to find my headphones so I couldn't test it maybe BT doesn't work)

2) Pen input works but really bad it doesn't track good (pointer stays 20 cm above from where it supposed to be, this did not happen in the PrimeOS, I had the bootable USB laying around so I compared with that)

3) Locking the screen is only possible with a gesture clicking the power button brings up the power menu, normal behavior, when the screen is locked it doesn't open back up and gets stuck at a lockscreen that shows 0% charge

These problems are persistent on every build of the latest version.
[BLISS ROMS Development] electrikjesus:
I am done replying to all these posts where users refuse to read the instructions, ignore the update posts or ignore the simple requirements we need to properly diagnose these issues. You will all be ignored until you can fulfill those simple requests.

Thank You
[BLISS ROMS Development] ElfinJNoty:
TO ALL READERS:

feel free to read any of the helpful info found in the first 3 posts, where there is also links to each release post with build specific instructions if needed. 'The Instructions' in post 2 contain info that, if read, would eliminate %90 of the redundant questions being asked, and allow for more development if the team is not spending unnecessary time re-answering the same info requests.

If you have a bug to report... Stop. Think:

Should I provide a log with this feedback? Or chose not to, making my feedback pretty useless to the development team.

Should I state what device I am installing to? And THE EXACT NAME OF THE BUILD IM USING, or should I challenge the development team to a guessing game, then still expect them to tell me how to fix so everything works to my liking.

Weather you are a seasoned Android tinkerer or you've never used Android before.... We expect all current and future users to read the material provided and be understanding that this project is huge, we are a small team, we try to help everybody in need but that does not mean we will help those who aren't willing to, or are too lazy to, help themselves.
[BLISS ROMS Development] protectivedad:
Surface Go Sleep Issues

I know the sleep states are a "known issue" does that mean you'd like logcats and information about them or that you haven't gotten to them yet and don't pester about them? I assumed the former, but just realized it might be the latter :).

Machine: Surface Go

Lockscreen turned off

Timeout set to 1 minute for testing

Scenario:

Fresh boot.

ALT-F1, logcat -b all -c, ALT-F7.

Wait for timeout.

Continue waiting after timeout for it to "timein".

ALT-F1, logcat -d, ALT-F7.

Go into Settings.

ALT-F1, logcat -d, ALT-F7.

Press power button and select restart.

ALT-F1, logcat -d, reboot.

Results:

Bliss logo, then home screen on boot.

After timeout screen brightens, kind of blanks but with status and navigation bars still visible.

Battery percentage goes to 0%.

Screen recovers and home screen comes back battery percentages goes back to real value.

Wifi is "broken", Settings "hang", Power Button Restart "hang".

Reboot from ALT-F1 terminal.

Logcat after it went to sleep and came back:

https://pastebin.com/E9kHix9w

Logcat after trying to go into the Settings:

https://pastebin.com/YDMzPgti

Logcat after trying to use the restart:

https://pastebin.com/8ZxDRYTp

I'm still working on my build environment not enough disk space. Do you think it would be a problem if while I followed the instructions I used depth=1 to create shallow clones?

I'm not really wanting help so much as willing to provide information to make finding problems easier. Let me know if I'm not being helpful.
[BLISS ROMS Development] electrikjesus:
Please don't think that providing relevant info is not helping, or being redundant. I welcome the feedback when it comes in this form.

I have a feeling the wifi is getting stuck on the crash, so if you could test adding "svc wifi disable && svc wifi enable" in the console after it first times out, and let me know if that helps it in crash recovery, we could likely add the disable and enable into init, just as a redundancy layer.

Thanks

PS, for clone depth, if your'e syncing all the repos, I suggest using the repo sync commands found in the Bliss manifest to help slim things down. Theres also a good bit of other info there too

The two issues I see so far are memtrack issues, tmpfs issues (sdcardfs related), and missing libs for googe play stuff. I'll keep digging though. spot and fix more issues with every log you guys provide.
[BLISS ROMS Development] electrikjesus:
Of course, if you can use Catlog to slim things down and only show the errors, that's better.

As for manifest, try to use this one for now, until I am able to catch up to r40 that Bliss merged

https://github.com/BlissRoms-x86/manifest

There will be a few conflicts, but not too many
[BLISS ROMS Development] electrikjesus:
It looks like your missing some important patches still.

Try to repo sync --force-sync first, then repo init the x86 manifest, and force sync that

You'll get a Houdini warning if you haven't ran "bash build-x86.sh -r", that will fetch those proprietary files, but it will require a root password to mount the volume in order to extract the files

If you get stuck, it's easiest for us to help using a chat platform. So please find you way over to the Bliss build support chat.

• TΞAM • BLISS • Build Help

Build support for the public

https://t.me/Team_Bliss_Build_Support
[BLISS ROMS Development] charackthe:
On my device, the sound output never is made through the speakers. I downloaded some 3rd party apps and making it redirect to speakers just makes the headphone volume louder and nothing else. On Windows speakers and the headphones are also considered the same output and when a headphone is plugged in it doesn't change or add a source it switches internally and still uses the Speakers/Headphones source.
[BLISS ROMS Development] protectivedad:
Sure, I will figure out how to use the chat in the future. I did locate the problem it was a commit from 20 days ago look at the BlissRoms-x86/external_magisk p9.0 branch on git it has been messed up.
[BLISS ROMS Development] electrikjesus:
Ahh, you could likely just remove that from vendor/magisk if it's giving trouble. I had likely pushed my updates to a test branch instead of the default
[BLISS ROMS Development] charackthe:
All of these I stated the sound (still broken after a reboot though), the pen etc works very well with the "Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180727-2157_k4.15.18_18.1.0-devel_w14_dev-kernel.org" build.

I am certain the sound situation is just my laptop's fault because it uses the same output and driver for the headphone jack and the speakers so it just jumps around between the two. This happens in all Android on pc projects not just Bliss. But if anybody got an idea I'll try and report back.
[BLISS ROMS Development] kugelblitz:
Hi! How to edit GRUB2-Options in EFI-Mode?
[BLISS ROMS Development] electrikjesus:
Tap "e" when the grub menu shows, or to edit permanently, you'll want to mount your efi partition from Linux or windows to edit.
[BLISS ROMS Development] kugelblitz:
E is not permanent - and direct editing of grub.cfg is worthless because auf beeing overwritten ... normally it should be "update-grub" - but it isn't in the image ... thats why I ask ...
[BLISS ROMS Development] electrikjesus:
No, that would have to be run from your Linux install.
[BLISS ROMS Development] appollokillers1:
get in Linux and add the necessary lines for grub in the 40custom (i think that is the name) and do an update-grub
[BLISS ROMS Development] kugelblitz:
Hi! How to do that - there is no update-grub inside ... its only busybox ...
[BLISS ROMS Development] kugelblitz:
The Bliss-ROM runs inside a VBox-VM on MacOS
[BLISS ROMS Development] appollokillers1:
well, assuming that you are using linux, but you are not, talkin about busybox, i guess that you are on a tablet or phone, if you are using a tablet or phone, then choose the right version of bliss, or, you don't explained right what you want to do
[BLISS ROMS Development] kugelblitz:
https://xdaforums.com/showpost.php?p=79699119&postcount=895 ;)
[BLISS ROMS Development] GOOGLE_USER:
Spreading the word

Quote from HERE.
[BLISS ROMS Development] kugelblitz:
Thats why I ask ...
[BLISS ROMS Development] GOOGLE_USER:
Yes, no issue with your asking.

As I read it, the quoted response would indicate that issues regarding implementation of BLISS OS in VM are, in actuality, issues with Android_X86.

Therefore, remedies are best sought via relevant and more direct sources.

Just tempering expectations of the Team.