Development [ROM][UNOFFICIAL][pdx215][13] RisingOS 1.4

Search This thread

Sakuu

Senior Member
Mar 29, 2020
325
123
Sony Xperia 10 III
Sony Xperia 1 III
Well, that's the problem. Calling and getting called was fine, but SMS was broken. Bit of an issue with 2FA and setting up whatsapp. It randomly "fixed" itself some time later but it still says unknown number.

Experience so far is a bit all over the place.
The great things:
  1. The amount of customizability is amazing, so many things I can change to what I want without having to resort to lsposed and magisk modules. Especially button control was an absolute pain in the ass to setup on the stock rom.
  2. Having magisk boot images makes life a lot easier.
  3. Finally a toggle between "sane" and native res.
  4. Extensive power menu is nice
  5. Did I mention it looks great?
  6. Very clean ROM! But I think leaving out a browser is maybe a bit too clean :>
But some things are not great...
  1. Lots of slowdowns in the ui. It is very clear that the phone is not outputting 120fps at times.
  2. Very poor battery life compared to A12 stock (with root and some mods, but nothing power related)
  3. Missing fingerprint rejection. Trust me, if I lock the phone with the button I do not want to unlock the phone with 1 microsecond.
  4. Device is a bit too trigger-happy waking up. I have the device laying next to my on my desk on the wireless charger and it seems to trigger for no reason.
I'll be using it a bit more and share some of my experiences, but so far it looks very serviceable, a lot better than some GSI roms definitely.

Regarding power, not the first time on new boot battery life was poor. I'll be doing some testing and tweaking the settings to see if it improves with some settings (or by itself).
Oh yes I forgot to mention you could disable blur for a bit of added perfomance since I noticed it lags QS while its being pulled down by alot
 

UsernameNotRecognized

Senior Member
May 17, 2012
297
46
Regarding the browser, Play Store and GMS are installed by default so the user can install whichever browser he/she wants without forcibly installing Chrome as a system app and then having to disable it if they don't want it. Also about the fingerprint vibration and the device waking up, in case of the fingerprint I think there's a option in either AOSP mods or somewhere in the settings to disable it while the screen is off and for the screen waking up randomly, you can just disable waking the display when it's plugged in under the "Display" option.
Performance and battery life is a bit hit or miss right now, yes the kernel needs some work but I'd need pretty active testers to test new kernel images for me, kinda like how Freak07 does it. And after that battery life should be massively improved and the heat reduced too. And ofc that kernel will all the changes will ship with this/future ROMs going forward.
Consider adding FFUpdater by default, it's a neat app which I use to install Iceraven. Because there's no browser installed I have to sideload neo-store and start from there. I see your point, but it effectively forces the user to use play store or sideload.

I'll be trying your suggestions and let you know if they helped.
 

UsernameNotRecognized

Senior Member
May 17, 2012
297
46
QS blur was disabled, unless I can't find it.

Disabling wake on plug is not something I want. I actually want it to pulse the battery level when I put it on the wireless charger, the problem is that it's randomly waking up while being charged (and it says something about fingerprint, but maybe it always says that).
Neither do I think the fingerprint suggestion will resolve the issue. I don't want to have to wake the device to make the fingerprint scanner work.
That said, I've tried it some more and I think I just had one weird experience and I can't reproduce it.
What does seem quite different than stock is that there's no backoff. On stock if the fingerprint was rejected it would stop trying until you removed the finger. With this ROM it will keep trying over and over until it tosses in the towel and forces me to unlock with pattern.

On stock it would also randomly ask me to unlock with pattern out of nowhere (and no, not because of security), so that behaviour seems identical. Stock just seems to be a lot better at hiding the behaviour I'm seeing.
 

Sakuu

Senior Member
Mar 29, 2020
325
123
Sony Xperia 10 III
Sony Xperia 1 III
Consider adding FFUpdater by default, it's a neat app which I use to install Iceraven. Because there's no browser installed I have to sideload neo-store and start from there. I see your point, but it effectively forces the user to use play store or sideload.

I'll be trying your suggestions and let you know if they helped.
I use FFUpdater too, but I don't want to add it by default, I think I'll add Bromite by default since it's a better Chrome alternative.
 

Sakuu

Senior Member
Mar 29, 2020
325
123
Sony Xperia 10 III
Sony Xperia 1 III
2 more things.
Holding search button config doesn't seem to work.
Holding camera button launches camera app while in the camera app?
1st is a ROM but (long press doesn't work) but short press works and Assistant needs to be changed from Google to None and then back for it to work after every reboot and about the holding camera button thing... I don't know tbh might be bugged too just don't hold it for too long and it should work fine
 

UsernameNotRecognized

Senior Member
May 17, 2012
297
46
1st is a ROM but (long press doesn't work) but short press works and Assistant needs to be changed from Google to None and then back for it to work after every reboot and about the holding camera button thing... I don't know tbh might be bugged too just don't hold it for too long and it should work fine
Yeah I noticed pressing it works. I used it for toggling torch, but I disabled single press because it's too easy to press it by accident.
Camera button is not usable sadly. It snaps a picture fine but also immediately opens a new instance of the camera app. That's not very useful lol.
The best way to do this would be to blacklist opening the camera app if already open.
Tasker already allows you to do so, but it can't capture the button sadly.
I did consider installing something like button remapper, but I really like the soft-press to peek which is surely going to break if I go that route.

I think I messed up regarding battery life btw. I toggled Personalizations > User Interface > Ambient Display > Sensor based | Wake up which obliterated battery life while using Sleep as Android (and general randomly waking up!). Disabling this solves most of the problems.
 

Sakuu

Senior Member
Mar 29, 2020
325
123
Sony Xperia 10 III
Sony Xperia 1 III
Yeah I noticed pressing it works. I used it for toggling torch, but I disabled single press because it's too easy to press it by accident.
Camera button is not usable sadly. It snaps a picture fine but also immediately opens a new instance of the camera app. That's not very useful lol.
The best way to do this would be to blacklist opening the camera app if already open.
Tasker already allows you to do so, but it can't capture the button sadly.
I did consider installing something like button remapper, but I really like the soft-press to peek which is surely going to break if I go that route.

I think I messed up regarding battery life btw. I toggled Personalizations > User Interface > Ambient Display > Sensor based | Wake up which obliterated battery life while using Sleep as Android (and general randomly waking up!). Disabling this solves most of the problems.
Ah I think you didn't set it from the settings? Could you double check the camera section has the same settings as mine (should fix the short press issues you're having)
 

Attachments

  • IMG_20230313_121630_554.jpg
    IMG_20230313_121630_554.jpg
    53.9 KB · Views: 65

UsernameNotRecognized

Senior Member
May 17, 2012
297
46
Just chiming in to share some more experiences.

The issue with the camera button is annoying but doable. I may try to find an alternative solution (maybe I should revisit some of the apps I've used with the stock rom).
The issue with the assistant button is a big fat whatever and I may tackle it with the previous one.
Accelerometer is too sensitive when enabling "pulse on pickup".

Battery life is a serious issue. I'm quite confident my battery life has halved. I used to be able to charge the phone to 80% and comfortable make it till the end of the day, but now I'm very often getting dangerously close to 0% and having to scrounge a charger from somewhere.

Aside from that I can't complain, there are some definite improvement from stock, especially ricing, but the battery life is making me reconsider.
 

Sakuu

Senior Member
Mar 29, 2020
325
123
Sony Xperia 10 III
Sony Xperia 1 III
Just chiming in to share some more experiences.

The issue with the camera button is annoying but doable. I may try to find an alternative solution (maybe I should revisit some of the apps I've used with the stock rom).
The issue with the assistant button is a big fat whatever and I may tackle it with the previous one.
Accelerometer is too sensitive when enabling "pulse on pickup".

Battery life is a serious issue. I'm quite confident my battery life has halved. I used to be able to charge the phone to 80% and comfortable make it till the end of the day, but now I'm very often getting dangerously close to 0% and having to scrounge a charger from somewhere.

Aside from that I can't complain, there are some definite improvement from stock, especially ricing, but the battery life is making me reconsider.
Yeah I'm working on other ROMs atm and trying to improve battery life as well, but I'm not very good with kernels and stuff and that of course would need me to have active testers (which I really don't have) and I can't test myself since my 1 III is my only "good" working device and I need it for daily usage so for now, it is what it is I suppose...
 

UsernameNotRecognized

Senior Member
May 17, 2012
297
46
Yeah I'm working on other ROMs atm and trying to improve battery life as well, but I'm not very good with kernels and stuff and that of course would need me to have active testers (which I really don't have) and I can't test myself since my 1 III is my only "good" working device and I need it for daily usage so for now, it is what it is I suppose...
Understandable. And obviously I can't complain because, well, you're doing it for free. Maybe I can take a gander at the kernel and make some sense of it, perhaps my embedded development skills is something I can use for this but I doubt it honestly.
 

The_Maze

Member
Mar 26, 2023
16
3
Understandable. And obviously I can't complain because, well, you're doing it for free. Maybe I can take a gander at the kernel and make some sense of it, perhaps my embedded development skills is something I can use for this but I doubt it honestly.
What is a good battery life for you?
Because I also flashed rice, had a problem with my battery consumption and thought why not
pair it with the Kirisakura Kernel and since then, had a massive improvement.
Maybe worth a try for you?
 

UsernameNotRecognized

Senior Member
May 17, 2012
297
46
What is a good battery life for you?
Because I also flashed rice, had a problem with my battery consumption and thought why not
pair it with the Kirisakura Kernel and since then, had a massive improvement.
Maybe worth a try for you?
It's something I'm definitely willing to try yes.
Capping battery at 80% would be more than enough to comfortably survive a working day (leaving me with 20-45%), but since this ROM I have consistently been having trouble surviving the day at all. Still at the end, but it's a problem.
 

The_Maze

Member
Mar 26, 2023
16
3
It's something I'm definitely willing to try yes.
Capping battery at 80% would be more than enough to comfortably survive a working day (leaving me with 20-45%), but since this ROM I have consistently been having trouble surviving the day at all. Still at the end, but it's a problem.
What settings are you using? 5G network? How much screen time? Now I'm curious.
 

UsernameNotRecognized

Senior Member
May 17, 2012
297
46
What settings are you using? 5G network? How much screen time? Now I'm curious.
Nah just 4G.
SOT is about 2 hours, with 1 hour reserved for navigation while plugged in (charging speed is like 5W which is less than the device consumes while actively navigation). The other hour is primarily checking notifications and very occasionally checking whatsapp/mail. Sometimes I listen to music as well, but not for more than 2 hours and I do next song while holding volume buttons (so device doesn't turn on).
Nothing unreasonable I'd say.

I also use Sleep as Android and I used to be left with 50~55%, now I wake up with about 35% left.
 

The_Maze

Member
Mar 26, 2023
16
3
Nah just 4G.
SOT is about 2 hours, with 1 hour reserved for navigation while plugged in (charging speed is like 5W which is less than the device consumes while actively navigation). The other hour is primarily checking notifications and very occasionally checking whatsapp/mail. Sometimes I listen to music as well, but not for more than 2 hours and I do next song while holding volume buttons (so device doesn't turn on).
Nothing unreasonable I'd say.

I also use Sleep as Android and I used to be left with 50~55%, now I wake up with about 35% left.
Yeah, then definitely give the Kirisakura Kernel a try. I have been using it just for 5 days, but the battery life is superb. Got more than 7 hours of SOT with a total of 30+ hours before my battery died, have not optimized it further, so there is still room for more. :cool:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I don't know how to turn this into Chinese。I can't find the settings
    Those aren't translated into Chinese so... nothing I can do about it
  • 5
    photo_2023-08-22_23-04-03.jpg


    RisingOS is An OpenSource Aftermarket Android Operating System that aims to deliver unique and refreshing android experience.

    Community RisingOS

    Code:
    /* 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.
    */

    Notes

    1. You need to flash Stock Android 13 before flashing this ROM (61.2.X.X.XXX)

    2. If you came from a SODP based ROM, you need to go back to official Android 13 firmware, and boot until you get to the Xperia Launcher

    3. If you can't change the Refresh Rate from the Display settings, swipe down the quick settings, and press on the pen icon, then scroll down till you find the "Refresh Rate" option and toggle it off & on, after that you should be able to switch the Refresh Rate from the Display settings

    4. To enable charging or the battery charge limit go to Settings > System > Xperia Parts > Battery Care > Turn on Use Battery Care > Turn on Enable Charging > And set your custom percentage limit

    5. If your device isn't charging make SURE you have Pause Charging (Aka H.S. Power Control)

    6. If you can't change the Refresh Rate from the Display settings, swipe down the quick settings, and press on the pen icon, then scroll down till you find the "Refresh Rate" option and toggle it off & on, after that you should be able to switch the Refresh Rate from the Display settings

    7. The 360 Reality Audio preview music is broken (Even with the required blobs it does not work yet but I am keeping it there for now)

    8. If the 360 Reality Audio app shows a globe with a strikethrough icon go to Settings > Apps > See all apps > Three-dot menu in the top right of the screen > Show system > Click on 360 Reality Audio Settings > Mobile data & Wi-Fi > Allow network access


    9. 360 Upmix Lite is on by default, to turn it off head to Settings > System > Xperia Parts > Audio Settings > 360 Upmix > And disable 360 Upmix by tapping on the the toggle in the top right of the of the app (NOTE: 360 Upmix Lite does not seem to work at the moment, this may be due to a ROM bug, or maybe a QPR bug like what happened with the DS4/5 Controllers not working on A13 QPR3)

    Support group available on Telegram!


    What works?​

    • Wi-Fi
    • Wi-Fi 6e
    • Mobile Data
    • Bluetooth
    • SDCard
    • Cameras
    • GPS
    • LED
    • Flashlight
    • Fingerprint Sensor
    • Battery Health Statistics
    • Pause Charging
    • Battery Care
    • Sound
    • Vibration
    • Dolby Sound
    • 360 Reality Audio Lite
    • Creator Mode
    • HDR10+
    • 120Hz
    • 240Hz Touch Sampling

    What's broken?​

    • DualShock 4 Controller (Over BT)
    • You tell me

    Flashing Instructions
    (Download both the ROM, boot & vendor_boot images from the links below)​

    Clean Flash:​

    Code:
    adb reboot bootloader
    fastboot --set-active=a
    fastboot flash boot_a [boot image]
    fastboot flash vendor_boot [vendor_boot image]
    fastboot reboot recovery
    Factory Reset > Format data/factory reset
    Apply update > Apply update from ADB
    Code:
    adb sideload <rom.zip>
    Back Arrow > Reboot system now
    BUT If you want to flash Magisk go to
    Advanced > Reboot to bootloader
    Code:
    fastboot flash boot_a [magisk boot image]
    fastboot flash boot_b [magisk boot image]
    fastboot reboot
    NOTE: For v1.3 and above you'll have to patch the boot.img for Magisk yourself
    Code:
    adb sideload <rom.zip>
    Back Arrow > Reboot system now
    OR If you want to flash KernelSU go to this link, download the latest KernelSU kernel image and then do the following
    Advanced > Reboot to bootloader
    Code:
    adb sideload <kernelsuimage.zip>
    Back Arrow > Reboot system now

    Updating from a older build (Dirty Flash):​

    Code:
    adb reboot bootloader
    fastboot reboot recovery
    Apply update > Apply update from ADB
    Code:
    adb sideload <rom.zip>
    Back Arrow > Reboot system now
    If you've had Magisk flashed before you need to reflash it again, go to the steps below the Clean Flash and do the same again, then reboot and you should still have Magisk

    Post-Install: (DO NOT SKIP THIS STEP OTHERWISE YOU WILL BE MISSING ESSENTIAL APPS FOR THE CAMERA & XPERIAPARTS)


    Due to some weird ROM bug not all apps are installed by default, head over to the Download folder and go to the Post-Install folder and download all the APKs then install them manually, this step is HIGHLY recommended.

    FIXED IN THE 1.3> BUILDS

    For the Camera button I suggest Installing Key Mapper and then configuring it as in this and this picture. (Screen off button detection is only available for rooted users)

    Downloads:
    Folder Download

    Sources:
    RisingOS Source
    Device Tree
    Kernel Source

    Build Author | Maintainer
    Saku

    Build Information
    Device: Xperia 1 III (pdx215)
    Build Type: Unofficial
    Android Version: 13
    Kernel Version: 5.4.242

    Version Information
    Status: Stable
    RisingOS Version: 1.4
    SELinux Status: Enforcing
    Release Date: 24/02/2023
    Last Updated: 04/09/2023
    2
    Update for v1.3 Dvaraka is now up!
    Vanilla build coming in a few.
    1
    The program is pretty self-explanatory, but reach out anytime if you need help.
    Also, load the right Kirisakura kernel, there are different ones for different Android versions (11,12,13).
    Oh, yeah, when I posted that I had already succeeded.
    It refuses to install 12, don't ask me how I know.
    I'll chime in half a day to let you know how it performed with sleep at least.
    1
    If anyone is still interested in battery life with riceDroid + Kirsakura Kernel,
    got this during my one-week off.
    I admit I did not use my phone much, just to check messages, take some pictures while outside, answer calls,
    but I am very satisfied, compared to Stock.
    1
    I don't know how to turn this into Chinese。I can't find the settings
    Those aren't translated into Chinese so... nothing I can do about it