[ROM][10.0][OneUI 2.5] Rise-Q v2.1 for A5 and A7 2017

Search This thread

tangoviking

Senior Member
Aug 15, 2016
62
8
Is it recommended to always install RiseKernel on this ROM or only if we want a little more speed? (for this old phone I just want stability, good battery life, good call quality) Thank you for a reply
 

murt4z4

New member
Nov 13, 2022
2
0
Thank you for this system, it works very good.
And it could be faster, I hope you will be able to improve this system.
 
Last edited:

Jmackley

Senior Member
Aug 12, 2017
502
228
Is it recommended to always install RiseKernel on this ROM or only if we want a little more speed? (for this old phone I just want stability, good battery life, good call quality) Thank you for a reply
It's entirely up to you, can easily try both with and without if you want and see what works best for your phond
Thank you for this system, it works very good.
And it could be faster, I hope you will be able to improve this system.
It's probably not going to get any faster than it is now, oneui 2 is 2 more versions than this phone got natively, if you want the best performance try risekernel
 

brød

Member
Dec 4, 2022
37
4
Finl.
Samsung Galaxy Tab 3 10.1
I wonder if this is a good rom, i take a lot of photos and i want to use my phone daily. Alarm clock and camera and banking apps are the apps that really want to use, so is this good for me? And can you uptade the ROM from the settings, OTA? And of course i want to make calls and send text's with it.


 
Last edited:
I wonder if this is a good rom, i take a lot of photos and i want to use my phone daily. Alarm clock and camera and banking apps are the apps that really want to use, so is this good for me?
And of course i want to make calls and send text's with it.
Yes, they all work fine. Some banking apps may fail due to having an unlocked bootloader though. Also there will most likely be an echo in phone calls when set to speaker mode.

And can you uptade the ROM from the settings, OTA?
No, this ROM is ported from another device and will therefore not be able to receive any OTA's.
 
Do you mean that there is no developer working on this ROM?
I said "A5 and A7 are too old for that to be fixed" which means that Samsung doesn't give us new android versions anymore (=we are running stuff that was made for Android 9 on Android 10, which was never intended by Samsung).
And since there is no sourcecode available for 99% of things it's more than unlikely to be ever fixed.
 

Aman gee

Senior Member
Apr 28, 2016
231
45
37
Lahore
Simon can you complete Fix *#0*# Test menu?
90% i fixed only front and back camera not working rest of all option *#0*# is working ....
 

Top Liked Posts

  • There are no posts matching your filters.
  • 60
    rise-Q.png


    Disclaimer
    Code:
    I am NOT responsible for bricked devices, dead SD cards or any
    damage to you device.

    Features
    • OneUI 2.5 ported from official Galaxy Note10 Lite Q release (N770FXXS7CTL1)
    • January 2021 security patch
    • Kernel built from A720SKSU3CSH1 sources with Linux 3.18.140
    • Fully deodexed
    • De-knoxed and debloated
    • S9+ CSC
    • Aroma installer
    • Working Secure Folder

    Requirements
    • An A5 2017 or A7 2017 (A520F/-W/-K/-L/-S or A720F/-S)
    • Oreo bootloader and modem
    • TWRP/SHRP/OrangeFox recovery
    • Vendor partition is NOT required, but this ROM will work regardless of an existing vendor partition.
    • A brain

    Bugs
    • Fingerprint scanner doesn't work in most third-party apps such as banking apps due to outdated keystore

    Installation
    • Make a backup of your important data in case something goes wrong!
    • I highly recommend to wipe /system, /data and /cache before installation, especially if coming from stock ROM
    • Download the ROM from the download section below and copy the ROM's zip to your phone's internal storage or SD card
    • In recovery, select install and choose the ROM's zip
    • If not done before, you can make the choice to wipe /system, /data and /cache in the aroma installer
    • Make all your choices in the aroma installer and wait for it to finish the installation
    • Reboot your device and wait until it booted. NOTE: First boot can take up to 10 minutes!

    Downloads
    • See post #2

    Donations
    • If you like my work feel free to send me a donation.

    Support

    Credits
    Thanks to...
    • Me, for all the time I spent on this project
    • @corsicanu and @ananjaser1211 for their magisk fix
    • Again @ananjaser1211 for his button light fix
    • @Option58 for updating and upstreaming our kernel to Linux 3.18.140
    • @Astrako for his countless fixes
    • @SuperR. for his android kitchen
    • @3arthur6 for his bluetooth library patch
    • All Telegram users who tested and helped me
    • Anyone else I missed

    Kernel source
    Github
    22
    Downloads
    Rise-Q v2.1: [03/07/2021]
    See downloads in Release post


    Rise-Q v2.0: [10/04/2021]
    See downloads in Release post
    Rise-Q v1.1: [18/01/2021]
    See downloads in Release post
    Rise-Q v1.0: [14/12/2020]
    Google Drive | OneDrive | Androidfilehost


    Changelogs
    -Fixed Secure Folder and made it an Aroma selection (You may need to enable it in Settings/QuickSettings first)
    -Switched to proper A720S hardware backed keystore and gatekeeper blobs
    -Patched SystemUI to get rid of the huge margin between the pin field and the bottom of the lockscreen when fingerprint + pin were set
    -Removed the fingerprint unlock animation used on N10 Lite firmware because it was freezing the phone sometimes when unlocking
    -Pulled ANT+ APKs from T720 Q and re-added them to aroma
    -Merged A600FN Q kernel wifi changes
    -Fixed a problem with wifi channels 10-13 not being shown in wifi menu by using wifi blobs from T720 Q
    -Added some missing WiFi kernel options
    -Reduced WiFi wakelocks by tweaking its config files
    -Reduced wakelocks in general with multiple kernel patches
    -Switched to newer composer 2.2 service and pulled more HWC blobs from A720S Pie
    -Binderized some graphics services
    -Improved sound quality and noise cancellation
    -Reverted experimental mic changes from v2.0
    -Fixed a wrong UUID for an audio effect
    -Fixed a typo in the CSC script that caused issues on dual-SIM devices
    -Enabled CPU bandwidth control in kernel as it's expected to be enabled
    -Re-added bluetooth patch for lasting device pairings which I forgot to the v2.0 update
    -Added missing bdaddr path for bluetooth
    -Fixed some small under-the-hood errors
    -Removed Face Recognition from settings as it's unsupported
    -Gathered a bit more space by removing unneeded stuff and replacing some apps with smaller apks
    -Added AppLock to aroma
    -Enabled function key menu for Bixby

    -Updated base ROM to N770FXXS7CTL1 (OneUI 2.5 from Galaxy Note10 Lite)
    -January security patch
    -Upstreamed the kernel to Linux 3.18.140 (thanks to @Option58)
    -Fixed changing volume in 3rd party apps (thanks to @ananjaser1211)
    -Fixed LiveFocus for rear camera
    -Fixed poor GPS signal
    -Fixed status bar icons being more centered than they should
    -Fixed button lights not being lit up when touching them
    -Fixed setting USB mode in notifications
    -Set device's fingerprint to G965F to bypass safetynet and show correct updates in Galaxy Store
    -Set 1.5GB SWAP/ZRAM space by default to improve overall performance
    -Switched back to Pie SSWAP blob due to Q one causing performance issues
    -Switched to A720S Pie power HAL for better power management
    -Enabled various vibration/haptic options in settings
    -Enabled high performance power mode in settings
    -Slightly boosted microphone for media
    -Switched to OMX from Galaxy S9 Q
    -Removed GoodLock from aroma due to region lock - Use patched GoodLock from corsicanu instead
    -Removed Honeyboard from aroma (already included in OneUI 2.5)
    -Removed ANT+ apps from aroma
    -Added 4G only network mode selection in aroma
    -Moved Flipboard to aroma
    -Moved Dictionary to aroma
    -Moved Bixby to aroma
    -Moved Edge Lighting to aroma
    -Edited the aroma splash "Rise-Q"-logo to match the logo of the XDA thread (and capitalized "Rise")

    -Updated base ROM to november firmware (A750FNXXU5CTK1)
    -Switched to J600FN audio HAL
    -Fixed moving apps to sdcard in settings
    -Fixed torch brightness crashing SystemUI/Cameraserver
    -Disabled unsupported secure WiFi option in settings
    -Updated rated charging speeds for A5/A7
    -Dropped dummy CSC folder in system (use /system/odm/etc/omc respectively /system_root/odm/etc/omc)
    -Fixed large shutdown animation
    -Fully killed vaultkeeper service
    -Switched to original A750FN RIL
    -Fixed missing Vulkan support
    -WiFi should be improved
    -Fixed neon case support
    -Added back video editor APK
    -Fixed screen on/off animation
    -Corrected some wrong values in power profiles
    -Added missing XID (Indonesian) CSC from S9+ firmware
    -The "SIM card changed" bug should be fixed
    -Fixed a bug where no CSC or a random CSC would be selected
    -Moved to setting default CSC to DBT if users' previous CSC is not supported
    -Added configurable kernel wakelocks (Changeable through e.g. hkTweaks)
    -Added a HACK that should block more apps from detecting magisk root (e.g. banking apps)
    -Added white bootanimation option in aroma
    -Added Samsung Honeyboard keyboard from OneUI 2.1/2.5 in aroma
    -Made Game Tools/Launcher optional by adding it in aroma
    -Updated included bloat to latest firmware
    -Updated disclaimer in aroma
    -Added selectable CSC features in aroma
    -Added GoodLock manager app in aroma

    -Initial release


    Workarounds
    NOTE for those who want/need to restore EFS backups:
    I created a GitHub repository that contains a flashable zip template that will allow you to restore previous EFS backups.
    DON'T FLASH THIS UNLESS YOU HAVE SERIOUS ISSUES LIKE
    • corrupted EFS partition
    • IMEI or any other EFS information being broken
    I am NOT responsible for any damage that may happen to your device!
    GitHub repo: See here and follow the steps provided.

    • ACG
    • ACR
    • AFG
    • AFR
    • ARO
    • ATO
    • ATT
    • AUT
    • BGL
    • BMC
    • BNG
    • BRI
    • BST
    • BWA
    • CAC
    • CAM
    • CAU
    • CCT
    • CHA
    • CHO
    • CHR
    • COO
    • DBT
    • DKR
    • ECT
    • EGY
    • EON
    • ESK
    • EUR
    • FMC
    • GCF
    • GLW
    • ILO
    • INS
    • ITV
    • KDO
    • KSA
    • KTC
    • LAO
    • LRA
    • LUC
    • LUX
    • MID
    • MTB
    • MWD
    • MXO
    • MYM
    • NEE
    • NPL
    • ORX
    • PAK
    • PEO
    • PHE
    • PHN
    • ROM
    • RWC
    • SEB
    • SEE
    • SEK
    • SKC
    • SKZ
    • SLK
    • SOL
    • SPC
    • SPR
    • TFN
    • THL
    • THR
    • TLS
    • TMB
    • TMK
    • TPA
    • TPH
    • TUN
    • TUR
    • USC
    • VMC
    • VMU
    • VTR
    • VZW
    • XAA
    • XAC
    • XAR
    • XAS
    • XEF
    • XEH
    • XEO
    • XEU
    • XEZ
    • XFE
    • XID
    • XME
    • XSG
    • XSP
    • XTC
    • XXV
    • ZTO
    • BTC
    • BTU
    • BVO
    • CEL
    • CPW
    • DOO
    • GLB
    • GTO
    • KOO
    • LYS
    • MAT
    • MM1
    • NZC
    • OPS
    • PCL
    • PTR
    • SER
    • SIN
    • SMA
    • SMP
    • STH
    • TEB
    • TEL
    • TKD
    • TMC
    • TNZ
    • UPO
    • UYO
    • VAU
    • VNZ
    • WTL
    • XFA
    • XNZ
    • XSA

    • Boot into recovery, mount /system and delete /system/priv-app/CIDManager folder through the recovery's file manager. (Note that the path may be /system/system/priv-app/CIDManager depending on the recovery used)

    • This mostly happens if you're rooted with Magisk because the system detects that you're rooted and denies DRM. To fix that, install this Magisk Module. Note that DRM will fall back to L3 which means that you won't be able to watch anything in HD.
    17
    UPDATE
    Rise-Q v2.1 is here!

    This is mainly a bugfix release, mostly small things (like removing the fingerprint unlock animation), but also some bigger ones. One of those fixes is Secure folder. I have finally been able to get it to work. To bypass issues with secure folder, I highly recommend to install Secure Folder only when doing a clean flash. I won't reply to bugreports from people who dirty flashed and have issues with it.
    Apart from that, I have seen multiple users report low media sound since v2.0. I compared the sound volume between v1.0, v1.1 and v2.0 and it sounded 100% identical for me. It may be an issue that comes from dirty flashing v2.0 on top of v1.1, so consider a clean flash first and tell me the exact steps to reproduce.

    Finally, as always for a new update, I recommend wiping your system partition before installation to bypass possible issues.

    Downloads
    Rise-Q v2.1: [07/03/2021]
    Google Drive | MEGA | Androidfilehost

    MD5: 06bf79a0ebea01d23b3166369d75ab3c

    Changelog
    -Fixed Secure Folder and made it an Aroma selection (You may need to enable it in Settings/QuickSettings first)
    -Switched to proper A720S hardware backed keystore and gatekeeper blobs
    -Patched SystemUI to get rid of the huge margin between the pin field and the bottom of the lockscreen when fingerprint + pin were set
    -Removed the fingerprint unlock animation used on N10 Lite firmware because it was freezing the phone sometimes when unlocking
    -Pulled ANT+ APKs from T720 Q and re-added them to aroma
    -Merged A600FN Q kernel wifi changes
    -Fixed a problem with wifi channels 10-13 not being shown in wifi menu by using wifi blobs from T720 Q
    -Added some missing WiFi kernel options
    -Reduced WiFi wakelocks by tweaking its config files
    -Reduced wakelocks in general with multiple kernel patches
    -Switched to newer composer 2.2 service and pulled more HWC blobs from A720S Pie
    -Binderized some graphics services
    -Improved sound quality and noise cancellation
    -Reverted experimental mic changes from v2.0
    -Fixed a wrong UUID for an audio effect
    -Fixed a typo in the CSC script that caused issues on dual-SIM devices
    -Enabled CPU bandwidth control in kernel as it's expected to be enabled
    -Re-added bluetooth patch for lasting device pairings which I forgot to the v2.0 update
    -Added missing bdaddr path for bluetooth
    -Fixed some small under-the-hood errors
    -Removed Face Recognition from settings as it's unsupported
    -Gathered a bit more space by removing unneeded stuff and replacing some apps with smaller apks
    -Added AppLock to aroma
    -Enabled function key menu for Bixby

    NOTE
    Also, before reporting bugs, check workarounds in post #2 first.
    In addition, I will NOT accept bug reports from those who dirty flashed over previous releases.
    14
    UPDATE
    Rise-Q v2.0 is here!

    At first, I want to thank @ananjaser1211 for his fixes and of course for answering all my stupid questions. Also thanks to @Option58 for upstreaming our kernel to Linux 3.18.140. Finally, huge thanks to all testers on Telegram for even finding the tiniest bugs.
    As this release of Rise-Q is now based on OneUI 2.5 from Galaxy Note 10 Lite, dirty flashing it over Rise-Q v1.0 or v1.1 will in most cases not work! It is highly recommended to wipe /data in recovery before installing Rise-Q v2.0.
    You can find downloads and the changelog of this release down below.

    Downloads
    Rise-Q v2.0: [04/10/2021]
    Google Drive | MEGA | Androidfilehost

    MD5: 3a582bbff799bc792fee7e73fc9e0f6c

    Changelog
    -Updated base ROM to N770FXXS7CTL1 (OneUI 2.5 from Galaxy Note10 Lite)
    -January security patch
    -Upstreamed the kernel to Linux 3.18.140 (thanks to @Option58)
    -Fixed changing volume in 3rd party apps (thanks to @ananjaser1211)
    -Fixed LiveFocus for rear camera
    -Fixed poor GPS signal
    -Fixed status bar icons being more centered than they should
    -Fixed button lights not being lit up when touching them
    -Fixed setting USB mode in notifications
    -Set device's fingerprint to G965F to bypass safetynet and show correct updates in Galaxy Store
    -Set 1.5GB SWAP/ZRAM space by default to improve overall performance
    -Switched back to Pie SSWAP blob due to Q one causing performance issues
    -Switched to A720S Pie power HAL for better power management
    -Enabled various vibration/haptic options in settings
    -Enabled high performance power mode in settings
    -Slightly boosted microphone for media
    -Switched to OMX from Galaxy S9 Q
    -Removed GoodLock from aroma due to region lock - Use patched GoodLock from corsicanu instead
    -Removed Honeyboard from aroma (already included in OneUI 2.5)
    -Removed ANT+ apps from aroma
    -Added 4G only network mode selection in aroma
    -Moved Flipboard to aroma
    -Moved Dictionary to aroma
    -Moved Bixby to aroma
    -Moved Edge Lighting to aroma
    -Edited the aroma splash "Rise-Q"-logo to match the logo of the XDA thread (and capitalized "Rise")

    NOTE
    Also, before reporting bugs, check workarounds in post #2 first.
    In addition, I will NOT accept bug reports from those who dirty flashed over previous releases.
    12
    GOD bless you MR.Simon1511;
    I hope to see android 11 ui3 for a520f Can I see?

    TANX Dear Friend
    Im gonna say this for once so everyone knows about it:
    Do NOT expect a OneUI 3 port from me. In my opinion, the added value between OneUI 2.5 and OneUI 3 is too low for the amount of work this would probably need.
    Apart from that, there would be 2 major problems:
    1. HWC
    2. Samsung Camera

    Our old Pie HWC has been working fine on Pie and Q, but on R Google decided to change HWC related stuff again which makes our Pie HWC incompatible to android 11. And yes, I know that HWC has been fixed on LineageOS 18 for our device, but the fix from there is likely not gonna work on OneUI. In short, this means for you: Broken HWC = very poor performance.
    Also samsung camera is gonna be a problem since all(?) newer samsung devices use a newer camera API that is simply incompatible to our "older" camera implementation.

    Note that these are just a few big bugs we know about so far, but there would probably be even more that would make a ROM based on that pretty much unusable in my opinion.

    So in conclusion: No OneUI 3 for our device(s).

    Apart from that, I want to thank everyone once again for all the bugs you found and reported and all your thankfulness!