In this thread, you can let me and the Remix Team know what issues you are having with your Nvidia-based systems!
Before you report any bugs, check this thread by my friend @Vioner : http://forum.xda-developers.com/remix/remix-os/solution-problems-booting-remix-os-dual-t3466027
Also, don't forget to send full bug reports here too, here! Made by Jide!
Notebook Dell XPS 15 Touch (9530)
Notebook Dell XPS 15 Touch (9530)
INTEL HD + NVIDIA GPUs (Nvidia GeForce GT 750M graphics card)
Remix OS for PC 3.0.205
Do not boot with option
nouveau.modeset=0
nomodeset
boot only with
androidboot.swrast=1 --> drawbacks - low performance.
I was able to boot with no additional option on release Remix OS for PC 3.0.202.
Hope you can fix soon.
I have a Dell m3800 and am seeing a similar issue. My computer has the Intel HD + Nvidia (Quadro 1100m). The performance is horrible. I cant even play a youtube video because both the audio and video are studdering so badly...
maxiclo said:
Notebook Dell XPS 15 Touch (9530)
INTEL HD + NVIDIA GPUs (Nvidia GeForce GT 750M graphics card)
Remix OS for PC 3.0.205
Do not boot with option
nouveau.modeset=0
nomodeset
boot only with
androidboot.swrast=1 --> drawbacks - low performance.
I was able to boot with no additional option on release Remix OS for PC 3.0.202.
Hope you can fix soon.
Click to expand...
Click to collapse
Try with:
nouveau.modeset=0 i915.modeset=1
HypoTurtle said:
Try with:
nouveau.modeset=0 i915.modeset=1
Click to expand...
Click to collapse
I
I did try this and the results were pretty strange. During boot, it wound up stuck on the command line. I did an lsmod and noticed that both i915 and nouveau were loaded. I then issued an "rmmod nouveau" from the command line and remix os then continued to boot into the OS. So why would the nouveau module still be loaded even with nouveau.modeset=0 explicitly set?
When inside Remix OS I swithed to the congsole ( using ATL + F1 ) and verified using lsmod that i915 was loaded and nouveau was not. However, I still could not play a video off of youtbe without both the video and the audio being choppy [and unusable at all].
Gtx 980. Works in guest mode. Stay stuck at logo in resident mode .
tailslol said:
Gtx 980. Works in guest mode. Stay stuck at logo in resident mode .
Click to expand...
Click to collapse
How long does it get stuck for? Report back with results from adding "DEBUG=1" to the kernel line.
moman2000 said:
How long does it get stuck for? Report back with results from adding "DEBUG=1" to the kernel line.
Click to expand...
Click to collapse
Stay stuck forever.
Kernel line?
tailslol said:
Stay stuck forever.
Kernel line?
Click to expand...
Click to collapse
Open menu.lst with your favourite text editor (I used Notepad++)
Add this: "DEBUG=1" after "CREATE_DATA_IMG=1"
Make sure the red code is added like this:
Example:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1[B][COLOR="Red"] DEBUG=1[/COLOR][/B]
initrd /RemixOS/initrd.img
boot
Save and reboot to Remix OS, and report back with any errors you see, you could send an image taken with a phone!
I've tried pretty much all of the combinations that I can think of. I can boot fine either with the software rendering flag set or with the nvidia card disabled (usually via a "rmmod mouveau" before remix completes boot.) However, nothing that I do enables youtube or any other video app to play smothly. This is driving me nuts as otherwise Remix seems really aweomse and I want to use it
As a related question, is there a way to gain root access in the command line so that we can do things like edit /system/etc/modules.blacklist ?
For reference, this system runs linux normally so I know that the hardware does work fine when blacklisting the nouveau (and nvidia) drivers. [Although I use Bumblebee for normal operation, which again is typically only using the Intel HD video card]
@HypoTurtle @Adaptive13 I've talked to @masaykh about these nomodeset and .modeset=0 problems - it appears that in Marshmallow they moved driver modules from initrd to system and because of that parameters like nomodeset or nouveau.modeset are not working. I'm not a 100% sure of that, but it seems a quite legit theory since trying all kinds of modeset combinations doesn't disable the driver modules. I've already talked about this with Remix product manager and they're working on it.
Vioner said:
@HypoTurtle @Adaptive13 I've talked to @masaykh about these nomodeset and .modeset=0 problems - it appears that in Marshmallow they moved driver modules from initrd to system and because of that parameters like nomodeset or nouveau.modeset are not working. I'm not a 100% sure of that, but it seems a quite legit theory since trying all kinds of modeset combinations doesn't disable the driver modules. I've already talked about this with Remix product manager and they're working on it.
Click to expand...
Click to collapse
@Vioner Thanks for following up on this. Please keep us posted on when a workaround will be available.
My Nvidia works well but has wrong thermal configurations making the display flash. I fix it by "echo 125000 > /sys/class/hwmon/hwmon1/temp1_max, temp1_crit, temp1_emergency" but this has to been done from the root terminal after every boot manually. I can automate it by adding the command to init.sh but this breaks OTA updating.
Card: Nvidia GeForce 8200 mg.
Vioner said:
@HypoTurtle @Adaptive13 I've talked to @masaykh about these nomodeset and .modeset=0 problems - it appears that in Marshmallow they moved driver modules from initrd to system and because of that parameters like nomodeset or nouveau.modeset are not working. I'm not a 100% sure of that, but it seems a quite legit theory since trying all kinds of modeset combinations doesn't disable the driver modules. I've already talked about this with Remix product manager and they're working on it.
Click to expand...
Click to collapse
Don't think drivers have ever been in initrd/ramdisk with Ax86 - there's too many drivers [100-150MB] for them to be added; AndroidIA (and some arm ROMS) have drivers in ramdisk as the Android build is device specific. There was a change though with MM-r1 (or whatever it was called) that 203 was rebased on; with modprobe being run differently, loading modules in a different order than before - I guess this could be ignoring grub $cmdline and module blacklisting.
modaifallah said:
My Nvidia works well but has wrong thermal configurations making the display flash. I fix it by "echo 125000 > /sys/class/hwmon/hwmon1/temp1_max, temp1_crit, temp1_emergency" but this has to been done from the root terminal after every boot manually. I can automate it by adding the command to init.sh but this breaks OTA updating.
Card: Nvidia GeForce 8200 mg.
Click to expand...
Click to collapse
You could try systemless to write to a loop-mounted init.sh or use a su.d script. That's what I have to do for my touchscreen & I can OTA by replacing 1 file (ramdisk.img).
Also back on topic you could I suppose loop-mount an empty file over the unwanted module (.ko) so that it doesn't load. I've tried blacklisting modules in newer Ax86 builds and that doesn't seem to work either (via grub and etc/blacklist) - not sure if the loop would be made before the module is loaded so likely be better to physically delete the .ko with a rw system.
Asus N76V: Intel i7-3630QM 2.4Ghz, Intel HD Graphics 4000 + Nvidia Geforce GT 650M.
can only make it works with "nomodeset", otherwise, it's stuck at terminal screen.
@HypoTurtle correct, they weren't in initrd, but the driver modules handling changed. @Adaptive13 we already have a workaround ready. I've updated my dual gpu booting guide, check HERE
Netbook ASUS 1215N
Intel ATOMD525 (Intel HD) + NVIDIA ION2 (Nvidia GT218)
Remix OS for PC 3.0.205
O.S Boot fine without change anything.
O.S it's super smooth but there something wrong with 2D and 3D applications.
1) Youtube HD is working, a bit choppy but it's working.
2) 99% of the games run with VERY slow framerate everything from very simple 2D games to complex 3D games like GTA. (some 2D games runs worse than GTA)
Just to make some examples... Angry Birds run @ 3-4 FPS while GTA SA runs 7-8FPS...
clash of clans is super smooth
tomb raider 1 (i tested lara's house level only) working good at the initial locations, but as soon as you reach the hall it drop from 30 stable FPS to 3-4FPS.
@Vioner As your other guide mentions adding EXTMOD=i915 works! And man does it work great! HD Youtube + audio upscaled to my 4k touchscreen display beautifully! I'm running off of a USB drive but the performance is incredible now. I am very impressed! Thanks!!!!!!!!!!!!!!!!!!! (For others reading this, I have DPI=300 also added to the boot parameters to make things look nice on the high res monitor.
@AuRoN89 that might indicate that you are running the system with software graphics renderer (graphics handled by the CPU). You can try my guide with "nomodeset" or "EXTMOD=i915". It should help.
Related
Hi!
Put up a new version of Ubuntu for Raphael based on the current state of Rhobuntu project. This release has the calibration fixed, but the other stuff (like wifi, 3g, etc.) still doesn't work. It also has a very huge boot time (around 5-6 minutes!). The latter is I think because of the non working modules, that are working in the Rhodium ports.
Newerthless because calibration started to work, it might be useful for someone. I try to fix the other things too.
Installation:
Extract and copy the contents of the file to the root of your sdcard. Then start ubuntu/haret.exe You might also want to change the startup.txt to meet your requirements.
Download:
http://winmo.sztupy.hu/raphubuntu.html
Great! Just downloaded and will try it out. Mind if I link to this on the first post of my thread? Also, if I can incorporate this into my build since mine boots faster could I use that? I'd give you credit for calibration of course.
Hi!
Here is the fix: http://forum.xda-developers.com/showpost.php?p=5872418&postcount=385 You can add it to your version. The slowness of the boot time is mostly because the non working modules. I'm working on enabling them, to add Wifi and 3G support. I'm hoping these configurations can be made in a way that it won't break operation on the Rhodium, so the two projects could share the same codebase (and both benefit from the same additions)
Hey,
at my Diam300 it's boot fast ... only 2 Min ... so i don't think it's on loading the modules
dacoon said:
Hey,
at my Diam300 it's boot fast ... only 2 Min ... so i don't think it's on loading the modules
Click to expand...
Click to collapse
Hm. For me it just hangs on gpio fired 1 0 for like forever. It does eventually boot.
Hi thank you for your work. Are you able to make version with ubuntu for netbooks (Ubuntu Netbook Edition)? It should be better than this.
my startup.txt
Code:
set ramsize 0x08000000
set ramaddr 0x10000000
set mtype 1805
set FBDURINGBOOT 1
set KERNEL zImage
set initrd initrd.gz
set cmdline "msmts_calib=0x7a.0x5e.0x35a.0x37f lcd.density=210 msmvkeyb_toggle=hide board-htcraphael-navi.wake=0 msm_fb.fix_x=1 board-htcdiamond.adb=0"
boot
I remove this from "set cmdline" ... because wifi is not working ... and debugging it's nothing for me ^^
Code:
wifi.mac=00:18:41:C8:BF:3A board-htcraphael-navi.wake=0 pm.debug_mask=53 irq.debug_mask=15 gpio.debug_mask=31 pm.idle_sleep_min_time=1000000 pm.idle_spin_time=80000
wow goin to try it right now
any updates?
binary110 said:
any updates?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=640785
http://wiki.xda-developers.com/index.php?pagename=RhodiumUbuntu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Additional resources:
[Guide+Video] How to Play Fallout 1 with Dosbox Turbo
[Guide+Video] How to run Fallout 1 & 2 on Android with QEMU
[Guide+Video] How to Play PC Games on Android with DosBox Turbo
[Guide+Video]How to Play Classic PC Games on Android with Exagear RPG/Strategies
[Guide+Video] How to the Play Baldur's Gate Series and Planescape: Torment on Android with GemRB
Fallout 1&2 QEMU Android installation guide:
Fallout 1&2 are fully playable on Android with the Android X86 emulator QEMU. Today you will learn how to install and play your own copy of Fallout 1&2 on Android with QEMU.
Games are Not included! (Some Assembly Required)
QEMU Fallout Video:
System Requirements
Recommended System Requirements:
CPU: Quad-Core/Octa-Core device 1.6Ghz+
RAM: 2GB-3GB+
HDD: 16GB
Minimum Requirements:
CPU: Dual-core 1.5Ghz+
RAM: 1GB (My default setup uses 256MB)
HDD: 8GB
Note:If you only meet the minimum requirements, then see Step 7 and use the optional Fallout2 Config without Video & Ambient sounds.
Emulated PC Gaming System
CPU: Pentium Processor
GPU: Cirrus Logic+ 2MB (2D)
RAM: 256MB(Default)
Audio: Sound Blaster 16
HDD: HDD image files mounted from your devices internal(default) or external storage. Full install around 2.5GB
Tested Devices: Note2, HP TouchPad, Galaxy s3, Galaxy s1 i9000
How to install Fallout on your Android device:
1)You will need Fallout 1or2 the game fully installed on a PC (Not provided here)
Download QEMU Emulator for Android:
2)a]Version 1.0 for Playing Fallout 2 Regular QEMU here
Or
2)b)Version 2.0 for Playing the Fallout 2 Restoration Project QEMU here
Note: Version 1.0 is more stable but will not work properly with the Restoration Project.
3)Getting Fallout 1 & 2 setup to Play on Android:
Fallout 2
-If you wish to play Fallout 2 I recommend installing Killap’s unofficial fallout 2 patch.
1) Download and Extract the Unofficial patch here, open the folder.
2) Open the extracted patch folder, copy the "data" folder and paste it into your Fallout 2 install directory. (yes to overwrite the files)
3) Open the "Windows 95-98-ME" folder and copy and paste these files into your Fallout 2 install directory. (yes to overwrite the files)
4) Open the “Batch_work’ folder and copy and paste these files into your Fallout 2 install directory. Run the "master_dat_fix_up.exe" file (A window will popup, wait for it..)
5) Next this is EXTREMELY important, in your Fallout 2 install directory delete a file called "patch000.dat"
6) Download and install one of my custom Fallout cfg files here by copying and pasting it into your Fallout directory. These config files correct the game path for the sound data files.
a)Config With Video & Ambient sounds: This is the standard required config file the fixes the sound directory path.
b)Config without Video & Ambient sounds: This increases performance by removing ambient and video sounds. If you experience crashing when the videos play then, you will need this file. Note*NPC conversations will still have spoken dialogue.
7) (Optional) You can also install Mash’s resolution patch here, to increase your screen size.
Note This may impact game performance but allows you to see much more of the map at once.
Download Fallout2 Hi-Res Patch v3.06 here
Fallout 2 Restoration Project
Note(Important) The Fallout 2 Restoration Project requires a faster device to run than a regular install of Fallout2. A fast Dual or Quad core device with 2GB+ is Recommended
-If you wish to play Killaps Fallout 2 Restoration Project on Android then you must do the following.
1) Download and Extract the manual Restoration patch here, open the folder.
2) Open the "main" folder and copy and paste these files into your Fallout 2 install directory. (yes to overwrite the files)
3) Open the "Windows 95-98-ME" folder and copy and paste these files into your Fallout 2 install directory. (yes to overwrite the files)
4) Open the “Batch_work’ folder and copy and paste these files into your Fallout 2 install directory. Run the "f2.bat" file (A window will popup, wait for it..)
5) Next this is EXTREMELY important, in your Fallout 2 install directory delete a file called "patch000.dat"
6) Download and install one of my custom Fallout cfg files here by copying and pasting it into your Fallout directory. These config files correct the game path for the sound data files.
a)Config With Video & Ambient sounds: This is the standard required config file the fixes the sound directory path.
b)Config without Video & Ambient sounds: This increases performance by removing ambient and video sounds. If you experience crashing when the videos play then, you will need this file. Note*NPC conversations will still have spoken dialogue.
7) Download the citylimit49_mapper here and place it into your Fallout 2 folder. Run the exe to extract the files. (yes to overwrite the files)
-Look in the Fallout 2 folder for the F49+.exe file that was extracted and run it(Do it!). It will fail to patch the mapper but will patch the Fallout.exe and allow us to play the restoration project.
Fallout 1
-If you wish to play Fallout 1 I recommend installing the Dos Patch and launching the game from the Dos exe file.
1)Download and install Fallout 1 the game on your PC. Get the DRM free GOG version of Fallout 1 here
2)DOS is no longer included with newer versions of Fallout 1(GOG). You will need to add support for it by doing the following:
-Download the Fallout 1 Official v1.1 DOS Patch here
-Extract the DOS patch files directly into your Fallout 1 game folder
-Download and extract the following DOS files into your Fallout 1 game folder, dos4gw.exe here, hmidet.386 and hmidrv.386 here
3) Download and install one of my custom Fallout 1 cfg files here by copying and pasting it into your Fallout 1 directory. These config files correct the game path for the sound data files.
-There are two different config files. The one without video & ambient noise is for slower devices that just meet the Min system requirements or have performance issues.
4)Optional) I also installed this NPC patch from the no mutants allowed website. This allows you to edit your follows weapons and inventory, like Fallout 2. Download and extract these files here into the Data folder in your fallout 1 directory.
4) Download and Extract either the 2GB or 1GB empty HDD.img files to an easy to find location on your PC. Bigger is Better, for improved stability! Default is 2GB.
5) Install the free 30 day trial of WinImage and run the application. Be sure to use it before 30 days passes.
Download WinImage 10.0 here
6) Open the empty HDD.img by dragging it into the open Winimage program. Or navigating to it from file/open
7) Locate your fully installed Fallout 1 or 2 game folder. Transfer the Fallout game folder into the HDD.img and save it. This should include Killaps Patches and Mash’s resolution patch. I would recommend playing at 640x480 if you have a dual core device. You can attempt 800x600 or 1024x768 if you have a quad core device. Single core devices should use my No Video or Ambient noise Fallout cfg.
(Optional) You can install one of my custom Fallout cfg files by copying and pasting it into the Fallout directory.
a)Config With Video & Ambient sounds: This is recommend to improve screen scroll performance and sound compatibility.
b)Config without Video & Ambient sounds: This has the same sound tweaks but further increases performance by removing ambient and video noises. Note*NPC conversations will still have spoken dialogue.
8) Save your new HDD.img and close the program.
9)Copy and paste your new Fallout2 HDD.img into the SDL folder in your downloads.
10)Transfer the sdl folder to your devices internal memory. This will be the location that opens when you plug in the USB cable.
11)Transfer the libSDL.apk to your device and install it. Note* you may need to Enable 'Unknown Sources' from Settings/Security/Enable.
12)Run the libSDL.apk and start windows. Skip scan disk if it comes up.
13)Play Fallout2 on Android and wander the wasteland.
Important Notes
How to improve the controls:
-Setting up custom onscreen controls or using Bluetooth/OTG devices can help make games playable on your device.
-I recommend adding custom onscreen controls with the paid GameKeyboard + app here
-Follow the apps setup instructions
-Customize the onscreen controls
-Reduce the transparency to better see the game with the onscreen overlay.
-Enable Non-Blocking mode so that the onscreen controls won't block QEMU touchscreen input.
-GameKeyboard + Screenshot with Fallout 2 Setup.
Get the free Hackers Keyboard here. It has a better layout for playing games and includes directional keys.
Image file app for Android:
To access your image files from Android install the free Zarchiver app from the Play Store here. This will allow you to modify and create images files from your Android device.
SDL cfg File:
-Located in the sdl folder you will find the sdl.cfg file. This allows you to edit the instructions given to the emulator.
-You can edit and save changes to this file using notepad.
-Here is the default line for the sdl.cfg file.
/sdl -L . -m 256 -boot c -hda c.img -hdb HDD_2Gb.img -usb -usbdevice tablet -soundhw sb16
-You can increase or decrease the memory amount allocated to the the app by modifying the value of –m 128(reduced) or -m 256(default) or -m 512(+recommended)
-The Default is 256MB for compatibility.
-Set the emulated memory size to half of your total system Memory size. So if your device has 1GB of DDR use the 512 setting.
-You can change the name of the HDD –hdb HDD_2Gb.img Note*It Must match the exact name in your sdl.cfg file.
-Add additional HDD’s by adding sequentially lettered –hd(x) Like so
- /sdl -L . -m 256 -boot c –hda c.img –hdb hdd_2Gb.img –hdc hdd_2Gb.img –hde hdd_2Gb.img… ect
-The default is HDD_2Gb.img but you can edit the file with notepad. Just change the 2 to a 1, to use the HDD_1Gb.img, save and exit.
Extra HDD for Virtual Memory:
-I would highly recommend attaching a 1/2GB HDD used only for virtual memory. You can use the Virtual Memory sdl cfg line below.
-Once you are running the emulator right click on the vault 13 desktop icon and choose properties, select the performance tab.
-Next select “virtual memory” at the bottom, click “Let me specify my own virtual memory settings” and select the HDD you attached.
-It will prompt you to reboot once you exit. Don’t reboot, choose no, and then shutdown and re-launch the emulator.
-This will help to keep System Resources between 98-99% free. This helps to optimize the performance and improve stability.
-You can check the performance by right clicking on the desktop vault computer and selecting properties. Navigate to the performance tab at the top and look for “System Resources:98%free”.
Virtual Memory sdl cfg:
/sdl -L . -m 512 -boot c -hda c.img -hdb HDD_2Gb.img -hdc HDD_1Gb.img -usb -usbdevice tablet -soundhw sb16
Troubleshooting:
-You must click the volume bottom before you can move the mouse.
-To help maintain stability try and minimize back ground app activity while running Fallout.
Note*Fallout1&2 runs reasonably stable. Reasonably stable = testers report gaming session of 1-3hrs.
Links:
ExaGear(Paid App):
[Guide+Video]How to Play Classic PC Games on Android with Exagear RPG/Strategies
Note Currently the fastet PC gaming solution on Android.
DosBox Turbo Version(Paid/Free App):
[Guide+video] How to Play PC Games on Android with DosBox Turbo (Thread)
-Note The Dosbox Turbo version Plays Dozens of Games and has full touchscreen/controller support. Plus 3Dfx Voodo1 support that adds an additional 8MB video memory.
How to Play Baldur’s gate on Android [XDA] Thread]
How to Play Baldur’s gate on Android [Video]
[Guide+video] How to Play PC Games on Android with DosBox Turbo - xda-developers
Fallout 1 Patches @ No Mutants Allowed:
Fallout 2 Patches @ No Mutants Allowed:
Fallout 2 Restoration Project Thread by Killap
First of all: Iam sorry to bump such an old thread.
However Id like to thank you for all info you shared so far.
Now here for the question why I bumped this thread: Is it possible to remap the hardware buttons for the bochs emulator?
I would be very thankfull if anyone could tell me how to do this.
Kind regards, Stefan.
While this will likely be a necropost I just had to say thank you. This is a great discovery, and not something I could have found out myself. Thank you so much for sharing and I hope many others are able to find a use of this.
I am hoping I might be able to use this method for Lords of Magic
you are sweet
Emulator Gaming
orcus2190 said:
While this will likely be a necropost I just had to say thank you. This is a great discovery, and not something I could have found out myself. Thank you so much for sharing and I hope many others are able to find a use of this.
I am hoping I might be able to use this method for Lords of Magic
Click to expand...
Click to collapse
I haven't tested this game myself but its rather hit or miss on what will run. Fallout 1/2, Diablo1 will run for sure but I haven't tested many games. My goal was to make Fallout playable for all Android users.
If this method doesn't work you could also try using the DosBox Turbo Method. You can open the hl.img and just put other games in place of hl. It might require you to tweak the DosBox config file.
Watch the How to play Half Life 1 video on Android Here! You can find links to info and downloads in the description.
I've actually got HL1 running at double the fps on my Note 2 but I haven't made a video yet.:highfive:
eek:n Xperia Neo V any fallout can be playable???
Anybody test F1 or F2???
If F2 will be playable restoration project 2.1.2b will be playable too?????
Read the OP
BillyKidMK2 said:
eek:n Xperia Neo V any fallout can be playable???
Anybody test F1 or F2???
If F2 will be playable restoration project 2.1.2b will be playable too?????
Click to expand...
Click to collapse
I would recommend reading the OP
Recommended System Requirements:
CPU Quad- Core, Dual-core 1.5+GHz, equivalent or better.
GPU Adreno 220, Nvidia Tegra2/3, equivalent or better.
1GB, 512. My Config asks for a min or 256MB & shouldn't be run on a device with less than this.
8GB disk space
Minimum System Requirements:
1Ghz CPU with 256MB of Ram
4GB Disk Space
Note*2)Fallout2 Config without Video & Ambient sounds should be used, see step # 4
Sorry to revive, but I for the life of me cannot get this to work. I'm on a Galaxy SIII and followed the instructions. Have restoration patch, removed the files that needed to be to removed. Only thing really is I renamed the hdd to Fallout2, which I also fixed in the sdl. I get the first loading screen and that is it. Freezes every single time.
Fallout Troubleshooting
Hishuro said:
Sorry to revive, but I for the life of me cannot get this to work. I'm on a Galaxy SIII and followed the instructions. Have restoration patch, removed the files that needed to be to removed. Only thing really is I renamed the hdd to Fallout2, which I also fixed in the sdl. I get the first loading screen and that is it. Freezes every single time.
Click to expand...
Click to collapse
Hi, which loading screen are you stuck at? When you launch the game or when you launch the emulator? Make sure to read the troubleshooting sections. To run the restoration patch you must be using the Fallout Launcher 2.0 version for DX 9C support. One single letter or number wrong in the sdl will cause the game to fail at launch. Logic would dictate that if you're having problems when changing the names, then don't change them. Its all set up and ready to go, test it like that before modifying the setup.
Tweaking the CPU Settings:
Increasing the minimum CPU frequency may help to improve stability. You can use the free CPU Master App. Also set the CPU governor to Performance or on demand. Don’t forget to set it back to normal after your finished exploring the wasteland.
-You can change the name of the HDD –hdb HDD_2Gb.img Note*It Must match the exact name in your sdl.cfg file.
-Add additional HDD’s by adding sequentially lettered –hd(x) Like so
- /sdl -L . -m 256 -boot c –hda c.img –hdb hdd_2Gb.img –hdc hdd_2Gb.img –hde hdd_2Gb.img… ect
-The default is HDD_2Gb.img but you can edit the file with notepad. Just change the 2 to a 1, to use the HDD_1Gb.img, save and exit.
I'll try again after work. It was freezing on emulator load. Tried 7 times and it finally went then shot back to main screen after a min. Got rid of everything so I can redo from scratch. P.S. just r realized I was using the GOG version, I still have the original CD so I'll try that when I get back
Fallout fixing
Hishuro said:
I'll try again after work. It was freezing on emulator load. Tried 7 times and it finally went then shot back to main screen after a min. Got rid of everything so I can redo from scratch.
Click to expand...
Click to collapse
Redoing it from scratch is the best idea. Freezing at launch generally indicates a problem with the sdl config or sdl file. I'll be online since i'm updating some Touchpad stuff, let me know if you get it working.
Still occasionally freezes on first load up or gets to desktop the kicks me out after a bit. Just 3 times so far, but I'm sitting on the desktop right now. I removed the ddraw files like you said but it says error can't find rez ini
More info
Hishuro said:
Still occasionally freezes on first load up or gets to desktop the kicks me out after a bit. Just 3 times so far, but I'm sitting on the desktop right now. I removed the ddraw files like you said but it says error can't find rez ini
Click to expand...
Click to collapse
You're not giving my any new information. Are you using the 2.0 version? Have you set the governor to performance like in the notes?
Tweaking the CPU Settings:
Increasing the minimum CPU frequency may help to improve stability. You can use the free CPU Master App. Also set the CPU governor to Performance or on demand. Don’t forget to set it back to normal after your finished exploring the wasteland.
Did you redownload everything? Have you tried running it without the restoration patch? What version of Fallout 2 are running, CD,GOG, Steam? Have you minimized background app activity? Are you using the default sdl line? if not Let me see the sdl line you are using. Its been confirmed to work on your device so it must have something to do with your setup or config.
Sorry, yes I'm using 2.0 and I've upped the cpu as well. First attempt was GOG but then I just reinstalled the original cd and tried that as well with same results. Played vanilla hundreds of times, never really played the restoration so I would like to get that to work. Background apps are not running, phone is rooted.
sdl
/sdl -L . -m 512 -boot c -hda c.img -hdb HDD_2Gb.img -usb -usbdevice tablet -soundhw sb16
just tried 512
Hishuro said:
Sorry, yes I'm using 2.0 and I've upped the cpu as well. First attempt was GOG but then I just reinstalled the original cd and tried that as well with same results. Played vanilla hundreds of times, never really played the restoration so I would like to get that to work. Background apps are not running, phone is rooted.
sdl
/sdl -L . -m 512 -boot c -hda c.img -hdb HDD_2Gb.img -usb -usbdevice tablet -soundhw sb16
just tried 512
Click to expand...
Click to collapse
Try installing killaps regular fallout 2 patch with the GOG version and the version 1.0 img. The 1.0 is more stable but won't run the restoration project.
Also set the CPU governor to Performance or on demand. This will keep the CPU frequency more stable, the emulator doesn't like the constant fluctuations that Android normally does.
Also keep the memory low till we know if you have too much back ground activity. Since you're rooted you can use the Cool tools system stats app to monitor what is going on. Do you have the S3 model with 2GB or 1GB?, 2 would be better for gaming.
Says 1.2 gbs for ram. In 1.0 it says can not find directx when i launch the game
---------- Post added at 05:18 AM ---------- Previous post was at 05:12 AM ----------
Can not load directx, this program requires windows 95 with direct x 3.0a
manually install Killap's Unofficial Fallout 2 Patch
Hishuro said:
Says 1.2 gbs for ram. In 1.0 it says can not find directx when i launch the game
---------- Post added at 05:18 AM ---------- Previous post was at 05:12 AM ----------
Can not load directx, this program requires windows 95 with direct x 3.0a
Click to expand...
Click to collapse
#1 solution for that problem is installing this patch
-Fallout2: If you have problems launching Fallout 2, manually install Killap's Unofficial Fallout 2 Patch (US/UK - manual install)
Killap's Unofficial Fallout 2 Patch (US/UK - manual install) Download:
#2 solution reinstall direct X. If you've crashed the emulator enough times that might mess it up too and you will need to recopy it to the device again.
http://www.falconfly.de/directx.htm
RolandDeschain79 said:
#1 solution for that problem is installing this patch
-Fallout2: If you have problems launching Fallout 2, manually install Killap's Unofficial Fallout 2 Patch (US/UK - manual install)
Killap's Unofficial Fallout 2 Patch (US/UK - manual install) Download:
#2 solution reinstall direct X. If you've crashed the emulator enough times that might mess it up too and you will need to recopy it to the device again.
http://www.falconfly.de/directx.htm
Click to expand...
Click to collapse
Just did both before your post. Same thing still happens. Thanks for you help though, going to bed pretty soon and will be leaving for a week in the morning, I'll have to try again when I get back
---------- Post added at 05:56 AM ---------- Previous post was at 05:51 AM ----------
Hishuro said:
Just did both before your post. Same thing still happens. Thanks for you help though, going to bed pretty soon and will be leaving for a week in the morning, I'll have to try again when I get back
Click to expand...
Click to collapse
checked out directx in the emu and everything shows fine and the tests ran fine as well.
Hishuro said:
Says 1.2 gbs for ram. In 1.0 it says can not find directx when i launch the game
---------- Post added at 05:18 AM ---------- Previous post was at 05:12 AM ----------
Can not load directx, this program requires windows 95 with direct x 3.0a
Click to expand...
Click to collapse
FYI a memory size of 1.2Gbs is not possible so you are doing or reading something wrong. The S3 has two models one with 1Gb the other with 2Gb.
Hishuro said:
Just did both before your post. Same thing still happens. Thanks for you help though, going to bed pretty soon and will be leaving for a week in the morning, I'll have to try again when I get back
---------- Post added at 05:56 AM ---------- Previous post was at 05:51 AM ----------
checked out directx in the emu and everything shows fine and the tests ran fine as well.
Click to expand...
Click to collapse
Please answer my questions fully. I'm aware direct x is installed, I created the img.... If You installed direct x what version did You use? Did you try using the 2.0 version to launch the regular game? Did you install sfall too? You didn't tell me what version you installed this time either, I recommended the GOG version. Are you using my custom configs?
Edit: It just occurred to me that you might be reinstalling fallout into the same folder that already contains the patches. This would explain when you keep getting the same message. You will need to uninstall the game and delete the left over data to be sure. If you uninstall and reinstall without deleting them they just remain there.
Fallout Tactics update
Hello Fallout fans. Today I got a new Fallout launcher working with DosBox turbo. The Result is that you can play Fallout 1 and 2 on Android very stably with a fully touchscreen interface, on screen keyboard, Joystick and Bluetooth devices. I still have to finish tweaking and testing it but very soon I will make a new video about it. In addition many other X86 PC games will soon be playable on Android. So stay tuned to see the future of PC gaming on Android. Please Stand By!!
Here is the first screenshot ever taken of Fallout Tactics running on Android. Currently the cut scene videos crash the game but I was able to load and play the game.
Fallout 2 runs betters than I have ever seen on a mobile device and is much more stable than using QEMU. Killaps Restoration project is also working with DosBox turbo.
Dosbox Turbo X86 compatibility list for the Fallout Launcher Beta:
Age of Empires
Age of Empires 2
Arcanum (Works but takes 10min+ to load)
Diablo 1
Fallout 1
Fallout2
Fallout2: Restoration project
Fallout Tactics (Turn off 3D sound 800x600 16 bit)
Half life
Simcity 3000
Starcraft
The Sims
Works with daemon tools:
Homeworld 1
Jedi Knight dark forces 2
Now that I've ported the Kexecboot bootloader, I'm moving on to my ultimate goal of getting a GNU/Linux desktop distribution running on the Note. My distro of choice for ARM these days is Debian, because it works well both in a chroot on Android as well as natively booted on its own. With kexecboot, you can boot kernels off of the external SD card or even off of USB drives, so you can have Debian and Android installed simultaneously. I'm booting Debian off of my external SD, a 16GB Sandisk class 10.
TO-DO LIST:
* Creating rootfs [DONE] - Use debootstrap to create a minimal armhf rootfs of Debian testing
* Compile kernel [DONE] - Using the CM11 kernel as a base, compile a kernel with features necessary for Debian
* Booting [DONE] - Boot a kernel that loads the Debian root filesystem natively
* USB OTG [DONE] - Once booted, use USB keyboard and mouse to interact with the device
* WiFi Networking [DONE] - Automatically load the WiFi driver and connect to a wireless network at boot, enabling remote access
* Basic Video [DONE] - Load an X server to display graphical applications on the display
* 3D Acceleration [WIP] - Use the Freedreno driver to accelerate GLES and GL 3D applications
* Screen rotation [TODO] - Figure out if Freedreno can rotate the screen to landscape mode
* Video Acceleration [TODO] - Use the MSM video decoder to accelerate video playback
* Audio [WIP] - Write an ALSA UCM configuration file to map the correct mixer channels to get sound out of internal speaker and/or headphones
* Touch and Pen [WIP] - Pen input seems to work, but touchscreen isn't being detected by X
* Bluetooth [WIP] - I can initialize and scan, but was unable to pair and hold a connection. Useful for keyboard and mouse while charging/externally powering device.
* Mobile Radio [TODO] - Make use of the mobile connection for data, possibly calls if anyone wants to take a shot. I'm not going to work on this.
* Package for release [TODO] - Build a fresh rootfs free of my development changes, copy any necessary stuff, package, and upload.
I plan on developing this simultaneously for the Note i717, Note 3 (N900T), and HP TouchPad as I have all three of these and I should be able to get supported kernels working for all three as well. I'll post pictures as I go, right now I'm still mostly working from an SSH shell over WiFi.
https://www.youtube.com/watch?v=qtb-TSGumNo
EDIT: Got the same patch applied to the TouchPad and it too is running these programs as shown in the video. Unfortunately the backlight doesn't come on on the TouchPad so it's hard to see anything.
EDIT 2: Colors sorta fixed: http://i.imgur.com/1kmKDOw.jpg I fixed the main picture but the 3D rendered video is now messed up with red and blue swapped.
CalcProgrammer1[/QUOTE said:
That sounds way to kool.
If I could get over my "terminal" fear I'd give you a hand, but as reading code I have no clue.
I couldn't even get linuxonandroid nor deploylinux to work and they both had a GUI.
That idea to use a REAL OS on the plablet is as great as using a REAL OS on a computer.
I do hope you succeed especially if the phone works also. LOL!
Thanks. :good:
Click to expand...
Click to collapse
What keyboard/trackpad combo are you using?
SailfishOS (SFOS) is a GNU+Linux system using libhybris to leverage Android drivers from LineageOS.
About everything should work (except NFC, no userspace support for now).
You're root and you've SSH, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build or newer,
and have booted it at least once (otherwise WLAN problems).
See latest release post for OTA update instructions, or flash ZIP download link.
Warning : flashing zip over previous SFOS install erases it ! So use OTA to avoid that, or use integrated backup app...
Note : SFOS only flashes boot partition and install itself in /data/.stowaways/sailfishos/ so :
you can go back to LineageOS only by flashing the LOS boot image
you can reclaim diskspace used SFOS by removing /data/.stowaways/sailfishos/
Reference Wiki page on merproject.org
Kernel | Device | Vendor source trees
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.).
This is not mandatory (though prefered for the full experience) : should you choose not to register (and even if you do),
you still can install an alternative store using OpenRepos client Storeman
Reserved
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
andrejchern said:
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
Click to expand...
Click to collapse
I have installated seilfish os some time ago in my moto g2 and the battery life and boot speed its superior then any version of android ... ?
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
tess1 said:
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
Click to expand...
Click to collapse
It's all politics, also it's the system I use daily
some sort of hommage to a french industry of old (1898), rough-rided by financialization (see, can't build idol3 themselves)
fighting planned obsolescence
taking the power back on a device
powering it with an OS independent from GAFAM
having closer to classical GNU+Linux distro, though not totally open in the case of SFOS
Since 2010 I've been a Nokia N900 then N9 user (which ran with Maemo, resp. Meego, predecessors to SailfishOS) until summer 2017 when I got a Xperia X for the SailfishX release. Only ever used Android for a month, until the build-SFOS-for-X documentation was released and dived in the OS-building fun...
At the beginning of 2018 I looked for a cheap and decent french-branded-androphone (2Gb RAM, HD display) with a working LineageOS port and found the idol3 to begin a new SFOS port. It's been a long 8 months journey, where rebuilding LineageOS if only for the patch-level was not much, then also wanted to "upstream" some fixes or upgrades (eg. kernel) I wanted in SFOS...
I started using my idol3 again and I love Sailfish OS as soon as I figure out android apps im gonna use it alot more
Everything work fine, but the double tap to wake up the telephone.
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Best regard.
Antonio from Italy.
vknecht said:
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it* and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
It's a systemd-based GNU/Linux with 32bits-userspace system, and about every basis function should work.
You're root, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build, and have booted it at least once (otherwise WLAN problems).
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.). This is not mandatory (though prefered for the full experience, for now) : should you choose not to register (and even if you do), you still can install an alternative store using OpenRepos client Storeman
*basic Anbox support was added, but don't count on it for now (plz contribute if you can), it may be broken.
If you really want to try it : (don't just copy/paste, fix the URLs !)
Code:
### As root (devel-su), on the phone via SSH :
# Add mal's Anbox for SFOS repository
ssu ar home_mal_anbox [url]http://repo.merproject.org/obs/home:/mal:/anbox/sailfish_latest_armv7hl/[/url]
pkcon refresh
pkcon install anbox-sailfishos anbox-sailfishos-image-mixed-32-64-bit
rm -f /var/lib/anbox/overlay/system/lib64/libGLESv*
cp /vendor/lib/egl/libEGL_adreno.so /var/lib/anbox/overlay/vendor/lib/egl/
# Install a keyboard APK, eg [url]https://f-droid.org/fr/packages/rkr.simplekeyboard.inputmethod/[/url]
mkdir -p /var/lib/anbox/data/app
cp *apk /var/lib/anbox/data/app
### Networking is broken at the moment... ###
### Comment anbox-bridge.sh lines (ExecStartPre and ExecStopPost) ###
### in /lib/systemd/system/anbox-container-manager.service ###
# Restart Anbox
systemctl restart anbox-container-manager
# There's no "back" button for now
# Run Anbox from app screen again to go back to Anbox app launcher
This is a simultaneous release of SFOS 2.2.1.18 and 3.0.0.8, if you have problem with one version, try the other
SFOS 2.2.1.18
SFOS 3.0.0.8
Sorry no screenshot or video for now, you can find for other devices, looks should be the same.
SailfishOS fir idol3 Wiki page
Kernel | Device | Vendor source trees
Click to expand...
Click to collapse
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
zorro_tj said:
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Click to expand...
Click to collapse
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
For donations, maybe it will be possible later.
h3cat3 said:
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
Click to expand...
Click to collapse
One thing I could do is try building LOS 14.1 with idol347 defconfig, but afaik it's not really working.
Otherwise one could follow the SailfishOS HADK using a working CyanogenMod base and I'd be glad to help, but don't have time to start it myself at the moment.
Thanks!
vknecht said:
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you. Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it? if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
zorro_tj said:
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you.
Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it?
if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
You're welcome For now I don't see any drain, let's hope it stays like this.
I found out that the ini file is not necessary if one sets tp_gesture_id to 2, but still have to set this value on boot
and/or find why it's not the same as in LineageOS by default.
3.0.1.11 release for idol3 is still in devel phase, once it's ready (~ one week or so) it will be published in testing phase and then you'll be able to do
OTA through commandline.
One can flash a devel-image, but then can't rely on OTA : will have to re-flash a testing-image or do risky/unsupported repository-switch.
Those are generally built using SailfishOS porters' Gitlab-CI group, latest being the 20190227 devel image
SailfishOS 3.0.1.11 beta3
Backup...
Update using OTA : the integrated graphical updater doesn't work for community ports
Easiest is to install sfos-upgrade either through Storeman or direct RPM dowload.
Flash image : (erases previously installed SailfishOS)
sailfishos-idol3-release-3.0.1.11-20190321-beta3.zip
Changes :
SailfishOS 3.0.1.11 release notes (points specific to officially supported devices don't apply)
Kernel : enabled Yama security module
Enabled doubletap to wake
Sorry, Anbox confirmed to NOT work, have to check required overlayfs support, maybe broken with the kernel updates.
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
andrejchern said:
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
Click to expand...
Click to collapse
Sorry to hear that... does it happen regularly/systematically and quite early after boot, or after (somehow) extensive usage, especially browser ?
I supposed you tried with flashing as well as OTA ?
A known cause for reboot is fixed in this build (and beta2 iirc) by an updated connman package ("rpm -qi connman" shows ip6tfix in version).
Maybe it's related to Yama security, will make a build without it...
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
andrejchern said:
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
Click to expand...
Click to collapse
Could you try flashing the ZIP inside the artifact from this devel build ?
It uses the same kernel as 3.0.0.8, ie. without yama, pstore and iirc RTC write support...
This build works fine, no reboots. Thanks.
SailfishOS 3.0.1.11 beta4
Update from any previous betas using OTA :
has to be done from commandline (on device or through SSH, USB prefered) since the graphical client in settings doesn't support community ports.
Code:
# Install sfos-upgrade package like this, or through Storeman
curl -O https://openrepos.net/sites/default/files/packages/5928/sfos-upgrade-2.4-1.noarch.rpm
devel-su
pkcon install-local sfos-upgrade-2.4-1.noarch.rpm
sfos-upgrade 3.0.1.11
reboot
# Patience, it takes an additional reboot to flash boot partition
# Go to commandline again and run :
devel-su post_sfos-upgrade
or install by flashing sailfishos-idol3-release-3.0.1.11-20190329-beta4.zip
(this replaces previously installed SailfishOS and SailfishOS-data, backup if needed)
Changes
Fall back to previous kernel
Hey mate, great job! Everything worked fine with sfos-upgrade from command line! Thanks a lot!!!
Just a question... I haven't prediction text, it's normal? Thanks again.
Antonio from Italy.
Hi, there!
Now that we can use Project Croissant to get ChromeOS running or non-Chromebook devices, what is missing is a better kernel for improved compatibility.
Thanks to the threads by @nabil2000 I was able to successfully build a chromeos-4.14 kernel that boots on my test device (Lenovo MIIX320-10ICR - Z8350 processor) using a CONFIG from FydeOS 5.31 with most hardware enabled (WiFi, Bluetooth, sound), but it has the same issue as latest ATB builds: it freezes after a while. This doesn't happen with latest FydeOS or CloudReady builds (CloudReady bought FlintOS so I guess they are using some of their code now), so my guess if that their kernels have some patches that aren't included in the Chromium git. FydeOS is open-sourced only for RaspberryPi and TinkerBoard, there are no sources available for the PC or VMWare versions (PC version is not open source as many say, so be aware).
I already have some ideas to make the trackpad as well as the battery meter and brightness work, but it is not useful if the kernel isn't as stable as FydeOS (virtually no freezes or crashes once booted). I have already checked, and the issue is not the intel_idle.max_cstate issue that plagued most BayTrail/CherryTrail devices in the past (using value 1 doesn't change anything).
So any ideas how to get FydeOS kernel source? Patches to make the current chromeos-4.14 kernel stable?
UPDATE: As @nabil2000 reported, it seems that FydeOS is not willing to release their kernel source. But it is possible to get kernel config from v5.31 using configs.ko module, which is missing in the next version (v6.0). Using FydeOS v5.31 as base it is possible to build a very stable kernel for CherryTrail devices.
Thanks
Installation v71/v72 - kernel 4.14
FydeOS has the best support for the MIIX320-10ICR, with some caveats:
It will boot to a black screen, but you just need to wait until it finishes loading the hit Ctrl+Alt+Fn+F2, the screen will blink and then hit Ctrl+Alt+Fn+F1 to go back to ChromeOS (for some reason, the developer shell is blank in 5.31 but it seems to work fine on 6.0). Use Ctrl+Shift+Fn+F3 to rotate the screen manually;
WiFi works out of the box, Bluetooth is detected but audio does not work (Chromium misses a library for audio over Bluetooth);
Sound works too, but you need to install some UCM files (more about this later);
Camera does not work, and the trackpad works very well, with gestures, but does NOT click (tap to click work with a custom conf file, see below - the trackpad actually sends two events when clicking the physical button, as some Windows devices do, and this doesn't work with cmt driver).
First I tried to build the ChromeOS file using the chromium.img from FydeOS v5.31. It booted fine and I was amazed to see the ChromeOS logo and Google enrollment, but PlayStore setup didn't finish (low space?) and there was no way to install it to another driver: many GPT errors and the installer failed...
Then I tried to do everything on place:
Booted to FydeOS on USB drive;
As I could not get to the dev shell in v5.31, I had to login then use crosh and shell, then installed it on a second external disk (120GB SATA on USB, /dev/sdb):
PS: your device may be a different one, check the correct device name using "lsblk" or "fdisk -l" and be aware that this installation erases the whole disk!
Code:
sudo chromeos-install --dst /dev/sdb
After installing, I have used option 2A from GitHub page (very detailed, thanks!) with the script, soraka (or pyro) and caroline recoveries (both versions 11151.113 = v71) on another disk:
PS: FydOS v5.31 kernel does not have support to VTPM_PROXY, while v6.0 does, it means you cannot use swtpm.jar with FydeOS v5.31 and chromefy. For nocturne or Android Pie ARC, you must use FydeOS v6.0, otherwise ARC won't work.
Code:
sudo bash ./chromefy.sh /dev/sdb recovery.bin caroline.bin
Answered YES to use the local installation, YES to resize partitions and NO in the end to keep SELinux as enforced (it may work fine if you keep it to enforced with nocturne recovery tho when using FydeOS v6.0);
Rebooted using the final installation, logged in and everything seemed fine, but then Play Store would not show installed apps even after a reboot, so I tried a powerwash and it seems it fixed the issue, now it seems to be working fine.
Original post: https://forum.xda-developers.com/showpost.php?p=78891386&postcount=729
Post installation fixes v71/v72 - kernel 4.14
1. Sound
You need to install UCM files using linuxium-install-UCM-files.sh script after remounting rootfs as RW.
Code:
sudo remount -o rw,remount /
sudo bash ./linuxium-install-UCM-files.sh
2. Headphone jack
You must send this quirk to the rt5645 module when loading it, so while rootfs is still RW, as root add a file named "miix320.conf" to /etc/modprobe.d with this line:
Code:
options snd_soc_rt5645 quirk=0x1030
PS: if you have used the correct UCM files then the audio should change between speakers and headphones, but not mic. To enable internal mic:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev DMic
and to enable mic from headset:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev HSMic
3. Tap to click with trackpad
While rootfs is still RW, as root add a file named "50-mixx320.conf" to /etc/gestures:
Code:
Section "InputClass"
Identifier "MIIX320 conf"
MatchUSBID "048d:*"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "Tap Minimum Pressure" "1"
EndSection
PS: for this to work, make sure "tap-to-click" is enabled in trackpad section of system Settings. If you have another device, use "dmesg | grep input:" with "lsusb" to find your device USB id instead of "048d:*".
Still needing fixes:
- chrome://flags is blank for some reason, so any special flags should be added manually to "chrome_dev.conf" instead;
- Trackpad physical button click;
- Brightness control;
- Battery meter;
- Rotation;
- Automatic change between tablet/desktop modes;
- Cameras (hardly they will work as they rely on ATOMISP, which was abandoned and does not work even on newest kernels).
Original post: https://forum.xda-developers.com/showpost.php?p=78978577&postcount=757
reserved
Good news! With chromeos-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
lfom said:
Good news! With chrome-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
Click to expand...
Click to collapse
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
nabil2000 said:
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
Click to expand...
Click to collapse
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-dev in order to successfully build it.
lfom said:
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-devel in order to successfully build it.
Click to expand...
Click to collapse
I am a lazy billy - thanks - I like copy & paste, & think as little as I can afford
Could you help me patching it on my GPD pocket?
it uses cherry tail
https://forum.xda-developers.com/ha...gpd-pocket-t3928828/post79496417#post79496417
thank you