• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL] PixysOS v3.1.0 [Android 10]

Search This thread

Pintoslp

Senior Member
May 21, 2019
120
101
Presidente Prudente
Ban-Q.png


Code:
#include <std_disclaimer.h>
/*
 * Your warranty is... still valid?
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */


about.PNG

Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.
Get ready to taste the unique features it brings with itself.
We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.

Team.PNG

@Subinsmani
@rahul9999
@@ki
@Shreejoy Dash
@kvijaya
@AxelBlaz3
@Psycho-Mods
@amarbajpai
@gero
@melvingarcia

donations.PNG
]

Support Us if you like our work

[SIZE=+1]Got an issue or suggestion? Reach us at[/SIZE]
Telegram: https://telegram.me/pixysos_chat

features.PNG


Coming soon :)

source.PNG

Pixys: PixysOS
Pixys Device Sources: PixysOSDevices

install.PNG

- Backup your personal data (Important)
- Download the ROM and GApps and transfer them to your device.
- Boot to recovery (TWRP recommended).
- Wipe the System, Cache, Data and ART/Dalvik cache.
- Flash the ROM + Gapps Zipfile.
- Flash the root solution of your choice (optional).
- Reboot your device.


The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every update (= ROM Update)


Currently Supported Root Solutions:

Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine

download.PNG

ROMs: DONWLOAD

known%20issues.PNG


You tell... :p

credits.PNG


- Google for AOSP
- AOSCP
- Dirty Unicorns
- Pixel experience
- AOSP extended
- LineageOS
- Nitrogen Os
- Bootleggers Rom
- Superior OS
- AICP & POSP Team for thread template idea
- Also many pro devs who all help us to bring this rom to you..
- Please let us know if we forgot to mention your name in credits..​

XDA:DevDB Information
PixysOS, ROM for the Moto G (5S) Plus

Contributors: @Pintoslp

Kernel source:
https://github.com/lit-kernel/android_kernel_motorola_msm8953

ROM OS Version: 10.x.x Ten
ROM Kernel: Linux 3.x.x
Based On: AOSP

Version Information
Status: Stable
Current Version: v3.03
Release Date: 02-13-2020
 
Last edited:

unl0ck

Member
Feb 10, 2020
40
9
I never faced this issue before. Can you try install again? Clean flash required.
Hugs!

I have reinstalled it before and it didn't help. I guess I should mention that I installed the Mayhem Unravel 4 OC Treble kernel (https://forum.xda-developers.com/moto-g5s-plus/development/kernel-mayhem-kernel-t3942444). Could that be the problem or is there a fix from an xposed or magisk module? I need a kernel that can boost my phones performance and battery, and I would really appreciate some recommendations.

I also use Magisk 20.3 with Magisk Manager 7.5.1 and Riru EdXposed (Sandhook) 0.4.6.0.
 

Damage1972

Senior Member
I have reinstalled it before and it didn't help. I guess I should mention that I installed the Mayhem Unravel 4 OC Treble kernel (https://forum.xda-developers.com/moto-g5s-plus/development/kernel-mayhem-kernel-t3942444). Could that be the problem or is there a fix from an xposed or magisk module? I need a kernel that can boost my phones performance and battery, and I would really appreciate some recommendations.

I also use Magisk 20.3 with Magisk Manager 7.5.1 and Riru EdXposed (Sandhook) 0.4.6.0.

Mayhem kernel 4.0 is for Pie Roms !
All your problems must come from that.
Wipe everything and install the ROM again (Gapps already included !) .
Then you should be fine !
This ROM doesn't have many features, but is the only one with FM Radio and DTV working for this device so far.
I think we don't have any custom kernel for Android 10 yet.
Hope this could help you.
Good luck !
 
  • Like
Reactions: unl0ck

unl0ck

Member
Feb 10, 2020
40
9
Mayhem kernel 4.0 is for Pie Roms !
All your problems must come from that.
Wipe everything and install the ROM again (Gapps already included !) .
Then you should be fine !
This ROM doesn't have many features, but is the only one with FM Radio and DTV working for this device so far.
I think we don't have any custom kernel for Android 10 yet.
Hope this could help you.
Good luck !

I didn't even notice that. I will remove it and I hope this was the problem and that it will fix the alarm app. I have been late to school for a couple of days because of this.
 

unl0ck

Member
Feb 10, 2020
40
9
I thimk it'll be ok, man.
I'm using Pixys OS as my daily driver, since it has DTV working.
Good luck !

A quick update: I removed the kernel and killed the battery (used it until it shut down) to calibrate it, but when I turned it back on my battery was still limited to 70%. The alarm app is fixed though, so that's a relief.

I have already tried the following which people said is solutions:

Calibrating battery (draining it & charging while it's powered off).
Reinstalling PixysOS.
Removing the kernel (Mayhem Unravel 4).
Performing a factory reset.
Uninstalling all magisk modules (one by one (including Xposed)).
Uninstalling all Xposed modules (one by one).
Uninstalling magisk root completely.
Installing the "Battery Charge Limit" application & limiting it to 99%.
Wiping cache partitions (wiped cache & dalvik in recovery mode).

None of these worked and I have tried all of the at least 2 percent (except for the "uninstalling the kernel" since I didn't notice that it is for Pie). Is there a flashable zip or a magisk/xposed module (or application) that could be a potential fix, or can I fix it by modifying some system files?


Also, speaking of modifying system files, I went through the system files and navigated to "/sys/class/power_supply/battery" which redirected me to "/sys/devices/soc/qpnp-smbcharger-17/power_supply/battery". I went through and viewed the content of some files, and some of them could be a solution to my problem.

(I am just using logic here, and I don't know anything about this stuff. I was hoping you could help me, since you seem to know what you're talking about.)

I went into the following files:

capacity (file name)
58 (inside of the file)

(the value of the file changes every time my battery percentage changes)


charge_counter
1928327

charge_full
3013000

(this is what I meant with logic. The file is named "charge_full" as in the maximum charge the phone can have. Maybe if I change the numbers to something else it could reach 100%.)


charge_full_design
3013000

charge_rate
None/Normal/Fast

(depending if I am charging or not and if I am using the turbo charger which came with the phone)


constant_charge_current_max
2000000

current_now
452420



Then there's a lot of other files in the folder, for example:

flash_active
flash_current_max
input_current_max
input_current_settled
voltage_max
voltage_max_design
voltage_now

and then there's a file named "uevent" which contains the following:

POWER_SUPPLY_NAME=battery
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CAPACITY=54
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_CURRENT_NOW=374448
POWER_SUPPLY_CHARGE_COUNTER=1859488
POWER_SUPPLY_TEMP=357
POWER_SUPPLY_VOLTAGE_NOW=3800331
POWER_SUPPLY_CHARGE_RATE=None


There's one last thing which I think is strange.

The files "battery_charging_enabled" and "charge_enabled", and that doesn't sound strange, but when I looked inside of them while charging my phone I found that the "battery_charging_enabled" was set to '1' while "charge_enabled" was set to '0'. When I tried to change the 0 to a 1 (after backup of course) it saved, but when I plugged out my charger the "battery_charging_enabled" became a '0' but the "charge_enabled" was unchanged as if that file isn't needed.


I hope that's all information you (or anybody reading this and is willing to help me) need to be able to find a fix. Thank you for reading this extremely long comment/post. I will not waste any more of your time, but I really appreciate that you've spent your time helping me.

Thank you so much.
 

Pintoslp

Senior Member
May 21, 2019
120
101
Presidente Prudente
A quick update: I removed the kernel and killed the battery (used it until it shut down) to calibrate it, but when I turned it back on my battery was still limited to 70%. The alarm app is fixed though, so that's a relief.

I have already tried the following which people said is solutions:

Calibrating battery (draining it & charging while it's powered off).
Reinstalling PixysOS.
Removing the kernel (Mayhem Unravel 4).
Performing a factory reset.
Uninstalling all magisk modules (one by one (including Xposed)).
Uninstalling all Xposed modules (one by one).
Uninstalling magisk root completely.
Installing the "Battery Charge Limit" application & limiting it to 99%.
Wiping cache partitions (wiped cache & dalvik in recovery mode).

None of these worked and I have tried all of the at least 2 percent (except for the "uninstalling the kernel" since I didn't notice that it is for Pie). Is there a flashable zip or a magisk/xposed module (or application) that could be a potential fix, or can I fix it by modifying some system files?


Also, speaking of modifying system files, I went through the system files and navigated to "/sys/class/power_supply/battery" which redirected me to "/sys/devices/soc/qpnp-smbcharger-17/power_supply/battery". I went through and viewed the content of some files, and some of them could be a solution to my problem.

(I am just using logic here, and I don't know anything about this stuff. I was hoping you could help me, since you seem to know what you're talking about.)

I went into the following files:

capacity (file name)
58 (inside of the file)

(the value of the file changes every time my battery percentage changes)


charge_counter
1928327

charge_full
3013000

(this is what I meant with logic. The file is named "charge_full" as in the maximum charge the phone can have. Maybe if I change the numbers to something else it could reach 100%.)


charge_full_design
3013000

charge_rate
None/Normal/Fast

(depending if I am charging or not and if I am using the turbo charger which came with the phone)


constant_charge_current_max
2000000

current_now
452420



Then there's a lot of other files in the folder, for example:

flash_active
flash_current_max
input_current_max
input_current_settled
voltage_max
voltage_max_design
voltage_now

and then there's a file named "uevent" which contains the following:

POWER_SUPPLY_NAME=battery
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CAPACITY=54
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_CURRENT_NOW=374448
POWER_SUPPLY_CHARGE_COUNTER=1859488
POWER_SUPPLY_TEMP=357
POWER_SUPPLY_VOLTAGE_NOW=3800331
POWER_SUPPLY_CHARGE_RATE=None


There's one last thing which I think is strange.

The files "battery_charging_enabled" and "charge_enabled", and that doesn't sound strange, but when I looked inside of them while charging my phone I found that the "battery_charging_enabled" was set to '1' while "charge_enabled" was set to '0'. When I tried to change the 0 to a 1 (after backup of course) it saved, but when I plugged out my charger the "battery_charging_enabled" became a '0' but the "charge_enabled" was unchanged as if that file isn't needed.


I hope that's all information you (or anybody reading this and is willing to help me) need to be able to find a fix. Thank you for reading this extremely long comment/post. I will not waste any more of your time, but I really appreciate that you've spent your time helping me.

Thank you so much.

I have the solution: don't change the kernel.
 

ainstushar

Member
Sep 28, 2013
34
10
Hi there, I am using the latest build and for some reason the fingerprint sensor doesn't work. If I try to setup a new fingerprint, it read my fingerprint, but I can't use it to unlock my device.

Anyone having this issue?
 
  • Like
Reactions: Pintoslp

CarlosXDA2014

Member
Dec 30, 2013
27
1
first congratulations on your work, your rom is great and apparently without bugs, I managed to root it, but after rooting the twrp I use version 3.2.1r20 does not flash zip files showing the error "updater process ended with error 1" you know how to solve this? ah, i already tried the solution here on xda which is extracting the "boot" image from your rom and flash boot via twrp but it didn't solve it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Ban-Q.png


    Code:
    #include <std_disclaimer.h>
    /*
     * Your warranty is... still valid?
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */


    about.PNG

    Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.
    Get ready to taste the unique features it brings with itself.
    We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.

    Team.PNG

    @Subinsmani
    @rahul9999
    @@ki
    @Shreejoy Dash
    @kvijaya
    @AxelBlaz3
    @Psycho-Mods
    @amarbajpai
    @gero
    @melvingarcia

    donations.PNG
    ]

    Support Us if you like our work

    [SIZE=+1]Got an issue or suggestion? Reach us at[/SIZE]
    Telegram: https://telegram.me/pixysos_chat

    features.PNG


    Coming soon :)

    source.PNG

    Pixys: PixysOS
    Pixys Device Sources: PixysOSDevices

    install.PNG

    - Backup your personal data (Important)
    - Download the ROM and GApps and transfer them to your device.
    - Boot to recovery (TWRP recommended).
    - Wipe the System, Cache, Data and ART/Dalvik cache.
    - Flash the ROM + Gapps Zipfile.
    - Flash the root solution of your choice (optional).
    - Reboot your device.


    The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
    The root solution should be flashed together with every update (= ROM Update)


    Currently Supported Root Solutions:

    Magisk stable
    Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine

    download.PNG

    ROMs: DONWLOAD

    known%20issues.PNG


    You tell... :p

    credits.PNG


    - Google for AOSP
    - AOSCP
    - Dirty Unicorns
    - Pixel experience
    - AOSP extended
    - LineageOS
    - Nitrogen Os
    - Bootleggers Rom
    - Superior OS
    - AICP & POSP Team for thread template idea
    - Also many pro devs who all help us to bring this rom to you..
    - Please let us know if we forgot to mention your name in credits..​

    XDA:DevDB Information
    PixysOS, ROM for the Moto G (5S) Plus

    Contributors: @Pintoslp

    Kernel source:
    https://github.com/lit-kernel/android_kernel_motorola_msm8953

    ROM OS Version: 10.x.x Ten
    ROM Kernel: Linux 3.x.x
    Based On: AOSP

    Version Information
    Status: Stable
    Current Version: v3.03
    Release Date: 02-13-2020
    1
    Update

    ​​PixysOS Update

    New build available for Motorola G (5S) Plus (sanders)
    by @pintos

    Version: 3.1.0 (ten)
    Build date: (2020/06/23)
    Edition: NON-GAPPS

    Download Now

    #sanders #pixysos
    1
    I have reinstalled it before and it didn't help. I guess I should mention that I installed the Mayhem Unravel 4 OC Treble kernel (https://forum.xda-developers.com/moto-g5s-plus/development/kernel-mayhem-kernel-t3942444). Could that be the problem or is there a fix from an xposed or magisk module? I need a kernel that can boost my phones performance and battery, and I would really appreciate some recommendations.

    I also use Magisk 20.3 with Magisk Manager 7.5.1 and Riru EdXposed (Sandhook) 0.4.6.0.

    Mayhem kernel 4.0 is for Pie Roms !
    All your problems must come from that.
    Wipe everything and install the ROM again (Gapps already included !) .
    Then you should be fine !
    This ROM doesn't have many features, but is the only one with FM Radio and DTV working for this device so far.
    I think we don't have any custom kernel for Android 10 yet.
    Hope this could help you.
    Good luck !
    1
    Hi there, I am using the latest build and for some reason the fingerprint sensor doesn't work. If I try to setup a new fingerprint, it read my fingerprint, but I can't use it to unlock my device.

    Anyone having this issue?