[UPDATE] Remix OS for PC update 3.0.207

[RemixOS_Jason]

We haven't given touchscreens support yet. However, our product managers know about this request and have it somewhere on their priority list. The more asks, the more I report to them, the more it'll get bumped up. Thanks.

any Surface Pro4 touch screen Support ?

 

[oofnik]

We haven't given touchscreens support yet. However, our product managers know about this request and have it somewhere on their priority list. The more asks, the more I report to them, the more it'll get bumped up. Thanks.

Hm? I have it running on my Lenovo Yoga 700, the touch screen is working just fine.

 

[RemixOS_Jason]

@oofnik - What I meant to say was, we haven't done specific things to optimize for specific software, including fix touchscreen bugs on specific touchscreen x86 devices. If it does work for you, then you're good!

Hm? I have it running on my Lenovo Yoga 700, the touch screen is working just fine.

 

[chals91]

Mmm.. sorry for the question, but why 4.4.3 Linux Kernel? Linux Kernel goes by 4.8 right now... Anyone can explain me? Because i´m waiting for 4.8 kernel for the Surface 3.

 

[Silver Moon Sam]

Hi Jason, i really appreciate the Remix Os. It is the best OS i have used so far on my Dell laptop. I am currently running Remix OS v3.0.206 as dual boot with Ubuntu v16 on the same partition on my HDD and a 2nd partition is formated to FAT as bridge to share files between my Ubuntu and the Remix OS. I have created the "remix" folder inside the root folder of Ubuntu using sudo su and created its data folder inside then tweak the boot script Grub customizer to create a boot menu.

I had recently upgraded to 207 by extracting the kenel, initrd.img , ramdisk.img , system.sfs from the v3.0.207 iso file, everything was working fine for 2 days until a game crashed (i not so sure). That unknown bug occurred while i was playing a game then everything freeze and when i restarted my Dell Laptop model Inspiron 3542, it stuck on the boot Remix OS screen only. I deleted the Dalvik-cache folder then rebooted my device where it displayed the boot Remix OS screen again but after 2 minutes it was upgrading then optimizing my 52 apps until it boot loop on Android Starting.

Yesterday i downgraded the Remix OS to version 3.0.206 by extracting and replacing iso files : kenel, initrd.img , ramdisk.img , system.sfs from the iso version 3.0.206 file and then deleted the dalvik-cache.

I am currently running the Remix Os v 3.0.206 without any bug so far.

I have 2 questions :

1st one is what will happen if i used the OTA update, will it overwrite my grub customizer configuration? because if i lose my grub configuration i will lose access to my Ubuntu.

2nd question: How can i upgrade to newer or future version?

 

[mediawiz]

Made progress on this...

This build doesn't seem to work if I have a "data.img" (data partition file) in the RemixOS directory. If I delete the "data.img" file, it will boot. But then, after I create another empty data.img file, it hangs during boot.

The issue was that RemixOS (at least this build) seems to have an issue that... If the data.img file is not formatted, or if there is something that Remix doesn't like about how it's formatted, it just freezes up during boot. I created a new data.img file, formatted it at ext4, and Remix booted OK.

Note: Other Android-x86 derrived ROMS (ie: Android-x86 v6.0, PheonixOS build 226) will detect during the boot process if the data.img file is not formatted, and format it before proceeding with the boot.

RemixOS seems very "finiky" about what parameters the kernel is given during the boot process (yet I have not been able to get any documentation for these), and what is contained in the data.img file. I have not run into this problem with Android-x86 v6.0.

---------- Post added at 08:51 AM ---------- Previous post was at 08:37 AM ----------

This update coincides with the release of our shiny new GitHub Feedback System & Troubleshooting Center!
Thanks @Vioner for building the system and @moman2000 for testing it out over the past couple of weeks!

If you experience an issue or bug, you can reproduce the bug in "Verbose mode" and Remix OS for PC will send us a system log for our developers to troubleshoot much more efficiently and effectively. Verbose mode will be an option during your reboot.
_______________________________________________________________
Remix OS version: 3.0.207
Release date: November 25, 2016
Remix OS Build Number - 64-bit: B2016112101
Remix OS Build Number - 32-bit: B2016112201
Release notes:

1. Added Verbose mode to save log files for easier debugging.
Guidelines: https://github.com/JideTechnology/Remix-OS-For-PC/wiki
2. Updated Linux kernel to 4.4.30
CORRECTION: We pulled this part of the update when we realized that there were still issues. Thus, this kernel update will come with the next OTA update. Apologies if this caused any inconvenience!
3. Added "Never sleep option" to be seen in languages other than English
4. Fixed a bug there was an issue remembering the last selected system in your boot menu
_______________________________________________________________
If you experience any bugs or issues, report it through our Verbose mode!

I had (after a great deal of experimentation) gotten Remix OS to boot, and it seemed to be working ok. I loaded a bunch of my apps, browsed a few web pages, and went on Facebook, and all seemed good. Within a day, I got a notice from Google Play Market that there was an update for the RemixOS WIFI. The WIFI had always been a little flaky (problems getting it to work with WIFI outers that do not broadcast SSID), so I updated it. After this, everythng seemed ok.

I had to do something in Windows 10, so I rebooted the system. When I was done with what I was doing, I again rebooted the system to bo back into RemixOS. Now Remix freezes during boot. I am guessing that my only choice is to delete the data.img file, create a new one, and start reloading all my apps and configuring everythng from scratch.

I like RemixOS, but it seems overly fragile. Any little configuration issue, or problem with the data.img file and it won't boot. I have not run into these sorts of issues with Android-x86. Being that RemixOS was derived from Android-x86 I don't understand why the core is not as stable.

 

[ImbaWind]

Latest version still stuck after the terminal screen: A N D R O I D [email protected]_x86:/ #_ (Not blinking), any idea? It worked a few version back but always stuck at here on recent version.
Installed on a UEFI CUBE iWork 11 HardDrive.

 

[Dunard]

Pointing out that the Wifi issue is from Androidx86. They ported the bug over onto the Remix OS. They tried to fix the issue. But still having connection issue. Trust me. Try to set Wifi up on Androidx86. It will not connect. Just sit there with a confuse face and hands in the air.

Anyway. Remix OS loaded more games than the Androidx86. Remix OS Dev team added extra stuff.

 

[priatnaadnyana]

hmmm... How about AMD hardwares?? is there any problem about this?

 

[iamsupersam]

working fine via ota update from 206 on a thinkpad yoga 260. keep up the awesome work guys i am thinking of getting a remix pro when it becomes available.

 

[Ni10God]

please add feture to not kill app running when close the app . and add persian pysical keyboard

 

[lyzxyzzy]

thanks for this clue. i expanded the remixos partition in win10 and now the update continued and completed successfully .

Good deal. My problem was the remix os partition size as well. I screwed up and reinstalled remix os a few times. Since parts of the update are in the partition and in the data.img file, and I had done a reinstall, my problems were worse. I had to move data.img, recreate it by booting into remix os, start the update, and put my desired data.img back. A flag file or a boot option to revert the update, or just an disk space error check would've helped a lot.

---------- Post added at 10:18 PM ---------- Previous post was at 10:07 PM ----------

This build doesn't seem to work if I have a "data.img" (data partition file) in the RemixOS directory. If I delete the "data.img" file, it will boot. But then, after I create another empty data.img file, it hangs during boot.

My guess is this had to do with the partition being full. The updates to not correctly take disk space on the partition into account and it locks the update.

 

[mediawiz]

Pointing out that the Wifi issue is from Androidx86. They ported the bug over onto the Remix OS. They tried to fix the issue. But still having connection issue. Trust me. Try to set Wifi up on Androidx86. It will not connect. Just sit there with a confuse face and hands in the air.

Anyway. Remix OS loaded more games than the Androidx86. Remix OS Dev team added extra stuff.

Wifi is working fine for me on Android-x86.

 

[hunggh]

Still no sound on Asus E200HA, all other things work perfectly

 

[Alisnowpy]

twitter

i cant type any tweets on twitter
each time i try
the app is relaunched
and go back to twitter homepage

 

[ralphwiggum1]

@oofnik - What I meant to say was, we haven't done specific things to optimize for specific software, including fix touchscreen bugs on specific touchscreen x86 devices. If it does work for you, then you're good!

My device (Dell Venue 11 Pro 7130, i5-4300Y) had working touchscreen around 204/205 (did multiple updates at the time, so don't remember which one broke it). 206 and 207 still not working, so seems like some touch drivers may have been removed.

 

[lastrider]

Has anyone got Showbox working with 3.0.207 yet?

Just closes after a couple of screens.

 

[modaifallah]

Hey how can I use verbose mode?

 

[gps3dx]

CHANGED COMPRESSION for SYSTEM.SFS ???

After rebooting to apply the update, it is stuck at 20% and will not move. This is on a Latitude 7350.
I had mounted it read-write in the past http://forum.xda-developers.com/showpost.php?p=67971055&postcount=22 . Removing the book option didn't help. Any ideas? Is there a boot option to ignore the update so I can get back to a functioning device on the old version?

same here
surface pro 3 i5 256G

what's the alternative? reinstall??

@RemixOS_Jason - I think this reported issue is because you since v3.0.207 you changed the COMPRESSION of the system.sfs file.
Previously on v3.0.206 I could unsquashfs it without any issue using "unsquashfs -f -d " command using ubuntu.
now, with latest v3.0.207 I just can't run that command successfully, and I get a "filesystem uses unknown compression" error.

What kind of compression did you used this time ?
How can I unsquashfs it ?

EDIT: just found out that it's LZ4 compression and one should recompile squashfs-tool with LZ4 support.... did it... and I manage to extract the .img out of the .sfs. @dev - any reason for the compression change ?

 

[Vioner]

@gps3dx it has changed a long time ago. In first or one of first 3.0.X releases.
@modaifallah
Didn't you read Jason's post? Cmon...

1. Added Verbose mode to save log files for easier debugging.
Guidelines: https://github.com/JideTechnology/Remix-OS-For-PC/wiki