Remix OS for PC Update, Version#3.0.203

Sentario

Senior Member
Sep 1, 2012
124
14
0
Edmonton
SHOWBOX

This OS still does not play HIT or SHOWBOX??? Also isn't there a way to incorperate UBUNTU or MINT into this like seems legit to me since it is LINUX only biggie is the KERNEL setup.
 

masaykh

Member
Oct 29, 2012
26
4
0
Hello, Remix OS for PC version: 3.0.203 not working

i have dual gpu solution (intel\nvidia), nouveau module print errors and logcat keep showing that surfaceflinger crashed due to (i suppose no available video driver), if i do rmmod nouveau, i got remix os animated logo and that all.

tried adding androidboot.swrast=1
tried nomodest=1
tried nouveau.modeset=0 i915.modeset=1
tried nouveau.modeset=0 i915.modeset=0 nomodest=1 androidboot.swrast=1
no changes

how i can get it working?
 

Vioner

Senior Member
May 30, 2012
614
262
0
@masaykh Check if your BIOS gives you the option to select GPU to output video. Some devices let you disable the dedicated GPU and force integrated to be used.
 

thaer.me

Member
Dec 3, 2015
16
2
0
issue with screen brightness and volume control...

After updating to the latest version 3.0.203 via OTA, my screen brightness is at its full all the time, sliding the brightness control slider has no effect at all, it's really annoying as I can't use it at night 'cause it's too bright obviously :eek:
also, if I put it on standby, the screen would go black but the backlight is still on and at full setting!
volume rocker is no longer functioning too, it has no effect whatsoever..
I'm runing remix on my Asus T100T tablet, everything worked pretty well on 3.0.201...
I really appreciate the update done to the key mapping game toolkit, it works like a charm now, and my wirless connection is as good as it should be...
any help with the screen brightness issue will be really appreciated, and thanks in advance :)
 

masaykh

Member
Oct 29, 2012
26
4
0
@Vioner i dont have option to disable video devices in bios.
i tried Android-x86 6.0-rc2 - it dont work with intel \ nouveau modules,
BUT it work with nomodeset vga=355

with same parameters for remix os - no success, i got pass console and to animated remix logo
but not further

very important notice is that no /dev/fb0
if started with nomodeset vga=355 , maybe exist fb0 device.. i dont know but i suppose it is created

without parameters above, command "logcat | grep Surface" give:
SurfaceFlinger is starting
SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
hwcomposer module not found
ERROR: failed to open framebuffer (Invalid argument), aborting

what it say then i can get to logo - i dont know how to get it to write log to my usb drive (fat32 formated)
 

Vioner

Senior Member
May 30, 2012
614
262
0
@masaykh I don't know if that's just a misspelled part in your post or if you misspelled when you were modifying the boot entry, but it's "nomodeset=1", not "nomodest=1".

Seeing your errors it seems like the drivers don't work very well for you. On my device just the "androidboot.swrast=1" was enough.

Try nomodeset=1 and androidboot.swrast=1 boty at once.

If the above doesn't work, you should fill the feedback form https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform

Add the logcat lines there.

Sent from mobile
 
Last edited:

ranaxda200

Senior Member
Jun 3, 2013
650
229
0
Kolkata
After updating to the latest version 3.0.203 via OTA, my screen brightness is at its full all the time, sliding the brightness control slider has no effect at all, it's really annoying as I can't use it at night 'cause it's too bright obviously :eek:
also, if I put it on standby, the screen would go black but the backlight is still on and at full setting!
volume rocker is no longer functioning too, it has no effect whatsoever..
I'm runing remix on my Asus T100T tablet, everything worked pretty well on 3.0.201...
I really appreciate the update done to the key mapping game toolkit, it works like a charm now, and my wirless connection is as good as it should be...
any help with the screen brightness issue will be really appreciated, and thanks in advance :)
For Screen brightness issue, you can use Twilight app. It automatically adjusts your device's brightness (color temperature) over the course of the day, reducing the harsh whites and blues as the day progresses. It's extremely useful and scientifically authentic app. Even I prefer it to f.lux in my windows pc.
 

Vioner

Senior Member
May 30, 2012
614
262
0
@masaykh I've just tested Android-x86-6.0-RC2 and Remix 3.0.203 on Lenovo 700-15ISK (dual gpu) and I fully booted only after applying androidboot.swrast=1. That resulted in virtual graphics adapter being used - lags and crashes... So I entered BIOS, found GPU settings and selected UAM - (integrated intel gpu) instaed of Discrete (dual gpu boot). This allowed me to boot Remix with the Intel HD Graphics 530 - no more lags, much better stability.
Problem for me was that I couldn't even get past the "remix_x86_x64 #/_" command-line which appears before the Remix logo. This also happens when you plug external display before Remix logo appears. You @masaykh could get past that cmdline, so your problem seems a bit different - probably driver issue and not the GPU detection and selection problem.

Since you've found a nightly with a fix, we can anticipate that the fixes will be emedded in future Remix/Android-x86 releases.
 
Last edited:

maxiclo

Senior Member
Mar 30, 2008
177
11
0
@maxiclo can you try to use "nomodeset" instead of "androidboot.swrast=1" ?
I tried to use nomodeset but no way to boot.

However early versions of RemixOS were able to boot only with nomodeset.
Now it is not needed anymore at least on my machine.

Do you know the scope/role of androidboot.swrast=1?
 
Last edited:

masaykh

Member
Oct 29, 2012
26
4
0
androidboot.swrast=1 forcing use of software renderer (graphic will be proccessed only using CPU).
Tested right now 3.201 version, and i can confirm that it work only with androidboot.swrast=1
as nightly builds of android-x86 work without such parameter , i can think only about screwed renderer as only software renderer working.