Distro PhoenixOS DarkMatter - Supercharged for Everyone Exo4.7 (BETA-2)

GhostWarrior said:

Bug Report Please Read Carefully :
-Screen Turn Black and White after the second Boot on kernel 4.14(Windows is normal this is not a issue with my hardware).This is CRITICAL !!!!!!
-Kernel 4.19 does not boot on old hardware like celeron or atom cpu .
-Google services Crash is still there happening but not as before.The bug is still there.
-Some stuttering on games like Free Fire and PUBGM and some graphic glitches on mentioned games.

Click to expand...

Nilavarasan said:

1.--Google playservices keeps stop working after using gearlock /Initialization/Default App Installation
2.--Some AMD processors (like AMD-A4 etc..) & iNTEL DualCore does not boot in Kernal 4.19.x
so.. u need to boot first time through 4.14.x (1st option)
After successful boot .. you can use to boot kernal 4.19.x
3.--Disply looks so smooth(slightly blurred)...

Click to expand...

HMTheBoy154 said:

I need your specs, can you show it for me ?

Post automatically merged: Jan 21, 2020

specs ?

Click to expand...

HMTheBoy154 said:

I need your specs, can you show it for me ?

Post automatically merged: Jan 21, 2020

specs ?

Click to expand...

dendjd said:

Hi axon i tryed 2 times for clear installation but gearlock not working.
It was worked only exo4.2 i need help.
And sdcards not mounting aotumatically.

Click to expand...

Nilavarasan said:

Try to launch gearlock using alt+f1/f2 key
Or allow super user permission to gearlock app

Click to expand...

AXON said:

It's not because of that.....
It's because hez using some SSD with an uncommon prefix...
I've resolved this issue over 4.5, so @dendjd must a wait a bit

Click to expand...

SRunreal said:

hey guys im new here, i realy impressive about this custom os, everything almost working great on my PC.
can i ask somthing, is magisk module isnt supported yet, i tried download module but when reboot my pc, module is gone.
and i tested modules by installing foxy-boot from magisk manager to check modules are working or not. after reboot my pc dosn't start foxy-boot modules.
i also tested placing my simple script to post-fs-data.d for control my amdgpu fan auto start, then i reboot again for test, my script working great.
whats wrong for magisk moduls.
sorry guys my bad english , iam from indonesia

#edit i just tested sound not working on my PC

Click to expand...

Night said:

Magisk 20+ is not currently working on any android x86 due to certain change in their boot scripts you can patch with an old version like 19.1 if you want to use but i suggest to use SuperSU since magisk also increases os boot time & some modules could brick your os if not supported properly.
also to due to loltrex claiming init.sh his own property we have decided to move audio tweaks in gearlock itself goto gearlock >> Game/ System Tweak >> ALSA try all parameter & see which one works for you the best for me parameter 1 (for 3.5mm audio port ) & 3 (for USB audio) works great.

Post automatically merged: Jan 26, 2020

Also we are working on a new program called gearboot which will allow you to install & load magisk modules without magisk

Click to expand...

SRunreal said:

ok thank you mybe latest magisk now isnt support for phoenix right.
can you explain me how to patch magisk 19.3 for DM, on Original PhoenixOS i am copy initrd ramdisk etc loltrex and its work magisk modules etc on packed system.img , for unpacked system.img isnt working, magisk 19.3 version

#for sound
i recently test ALSA option on gearlock apps, all option is not working on my pc my mobo is MSI H77MA-G43, i put on front or back for 3.5mm audio port its not working yet.

Click to expand...

SRunreal said:

hey guys im new here, i realy impressive about this custom os, everything almost working great on my PC.
can i ask somthing, is magisk module isnt supported yet, i tried download module but when reboot my pc, module is gone.
and i tested modules by installing foxy-boot from magisk manager to check modules are working or not. after reboot my pc dosn't start foxy-boot modules.
i also tested placing my simple script to post-fs-data.d for control my amdgpu fan auto start, then i reboot again for test, my script working great.
whats wrong for magisk moduls.
sorry guys my bad english , iam from indonesia

#edit i just tested sound not working on my PC
i insert screenshoot and log from magisk

--------- beginning of main
--------- beginning of system
01-26 18:03:08.463 1395 1395 I Magisk : Magisk v20.1(20100) daemon started
01-26 18:03:08.463 1395 1395 I Magisk : * Device API level: 25
01-26 18:03:08.478 1395 1396 I Magisk : ** post-fs-data mode running
01-26 18:03:08.478 1395 1396 I Magisk : * Initializing Magisk environment
01-26 18:03:08.479 1395 1396 I Magisk : * Mounting mirrors
01-26 18:03:08.479 1395 1396 E Magisk : mount /sbin/.magisk/block/system->/sbin/.magisk/mirror/system failed with 16: Device or resource busy
01-26 18:03:08.479 1395 1396 I Magisk : mount: /sbin/.magisk/mirror/system
01-26 18:03:08.479 1395 1396 I Magisk : mount: /sbin/.magisk/mirror/data
01-26 18:03:08.479 1395 1396 I Magisk : link: /sbin/.magisk/mirror/vendor
01-26 18:03:08.479 1395 1396 I Magisk : * Setting up internal busybox
01-26 18:03:08.488 1395 1396 I Magisk : * Running post-fs-data.d scripts
01-26 18:03:08.488 1395 1396 I Magisk : post-fs-data.d: exec [.placeholder.sh]
01-26 18:03:18.523 1395 1453 I Magisk : ** late_start service mode running
01-26 18:03:18.554 1395 1396 I Magisk : post-fs-data.d: exec [start-amdgpu-fan.sh]
01-26 18:03:18.576 1395 1396 E Magisk : mount /sbin/.magisk/mirror/data/adb/modules->/sbin/.magisk/modules failed with 2: No such file or directory
01-26 18:03:18.589 1395 1396 I Magisk : * Running module post-fs-data scripts
01-26 18:03:18.589 1395 1396 I Magisk : * Loading modules
01-26 18:03:18.589 1395 1396 I Magisk : foxy-boot: constructing magic mount structure
01-26 18:03:18.589 1395 1396 E Magisk : opendir: /sbin/.magisk/mirror/system/bin failed with 2: No such file or directory
01-26 18:03:18.677 1395 1470 I Magisk : * Starting MagiskHide
01-26 18:03:18.677 1395 1470 I Magisk : hide_policy: Hiding sensitive props
01-26 18:03:18.677 1395 1470 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
01-26 18:03:18.678 1395 1470 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
01-26 18:03:24.198 1395 2129 I Magisk : ** boot_complete triggered
01-26 18:03:26.364 1395 1470 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[3213] UID=[10008]

Click to expand...

AXON said:

you might wanna check out this location ?
/system/phoenixos_darkmatter/gearboot

Post automatically merged: Jan 26, 2020

and dont worry, all such bugs will be fixed over the next version.

Click to expand...

SRunreal said:

ok AXON i will be wait thank you very much for youre response , can i request,
in setting option for display resolution is gone i cant set to 1080p resolution if i use MESA 18, but if i use MESA 17 i can set 1080p resolution by modifying persist.sys.drm.mode.set on root:/data/property/

Click to expand...

HMTheBoy154 said:

So put this in your build.prop instead
debug.drm.mode.force=1920x1080@60

Click to expand...

HMTheBoy154 its solved now, maybe future gearlock option will be add resolution change, it will be helpfull for newbie like me

#edit for sound problem i use 3rd party apps called SoundAbout its solved my problem now.
i cant undersrand how to configure ALSA..

thanks for you all

AXON said:

you might wanna check out this location ?
/system/phoenixos_darkmatter/gearboot

Post automatically merged: Jan 26, 2020

and dont worry, all such bugs will be fixed over the next version.

Click to expand...

Nilavarasan said:

Waiting for the next version's release by hoping it will be free from the bug google play services stops working.

Click to expand...