Development Paranoid Android Topaz Beta 1 - Nothing phone (1)

Search This thread

MarcoReckless

Senior Member
Other than some lag in the beginning (probably due to me charging while transferring data, probably causing even more heat and making it throttle), now it's smooth as expected, the only real problem I'm facing is not being able to record videos in chat apps (ex. WhatsApp).
 

Taylorsay

Member
Nov 16, 2022
18
1
Other than some lag in the beginning (probably due to me charging while transferring data, probably causing even more heat and making it throttle), now it's smooth as expected, the only real problem I'm facing is not being able to record videos in chat apps (ex. WhatsApp).
What about Snapchat? Also are you a tiktok user? My refresh rate is capped at 60 in nothing os with no way to stop it. Is it 120 on PA?
 

gamal001

Senior Member
Jul 15, 2011
806
204
Google Pixel 5
Nothing Phone 1
I'm not 100% sure, but that should be the new Play Integrity API, if that's the case you can't really bypass it (at least for now) because it checks the bootloader status.

I'm not 100% sure, but that should be the new Play Integrity API, if that's the case you can't really bypass it (at least for now) because it checks the bootloader status.
actual one app (government app) when installing and starting run coming message "This application can not run on rooted devices".
the other applications are running okay.
 

MarcoReckless

Senior Member
actual one app (government app) when installing and starting run coming message "This application can not run on rooted devices".
the other applications are running okay.
I'm aware of that, not all apps have implemented it (I can use my banking apps just fine, they all still use SafetyNet) and not all the apps that have implemented it have the same requirement (you can have MEETS_BASIC_INTEGRITY as a requirement for example and still be able to use the app on a rooted device, as long as the developer doesn't implement the MEETS_STRONG_INTEGRITY requirement you should be good).
I assume you already have the SafetyNex fix and you hid the apps through Magisk? Because I'm able to use all the apps that require SafetyNex just fine, I didn't even need the MagiskHide Props module.
 
Last edited:

Taylorsay

Member
Nov 16, 2022
18
1
Can you provide a little more detailed information?
Honestly no. I spent hours that night trying to just flash whatever I could to get it working again. I must've flashed about 15 times.

I can't remember the video I used but it's possible it could have been the unbrick/downgrade/revert video from 4utech. It has about 500 views. I skimmed through it and it looked like the process I did. I'd start there. Make sure you have the eea version. I think I started on 1.1.3 and did ota after it was all done
 

MarcoReckless

Senior Member
I found these issues so far:
- Unable to record videos in chat apps (can send them properly if I record them using the system camera)
- The screen doesn't wake up sometimes (I can't wake up the screen unless I tap power twice, this doesn't happen if I use double tap to wake and AOD is already disabled, the power button works properly only shortly after turning it off so it's probably some idle/powersaving thing)
- Special permissions are randomly resetting (from what I've seen this bug is related to Android 13 and not PA itself, many posts report this in the Android 13 beta and it applies only to the special ones such as managing files, I ticked the option to avoid resetting them but it gets ignored, it's not related to reboots but it happens every once in a while)

Other than these ones, the ROM is running properly, I'm looking forward to the beta.

This one and this one are the posts that I've seen where the permission issues was reported.
 
Last edited:
  • Like
Reactions: flozge
Nov 26, 2022
7
1
Is there no NFC button on the control panel? I use NFC usefully, but I can't set the NFC button in the control panel while using that rom. I always use NFC with Bluetooth - NFC -ON &OFF Please improve!
 

RivalTin

Member
Jan 16, 2022
30
5
Congrat' for developers, Topaz 3 for Phone (1) is even better than stock OS in my opinion. UDFPS is much faster than stock rom and there are fewer bugs in this custom OS. My special fav' is glyph flashlight wich is a brilliant feature. The only 2 things I wanna see in the future: the stock camera integration (difficult to perform) and the fully working glyph functions. Thank you for your work, guys.
 
Nov 26, 2022
7
1
My phone (1) had wifi issues from the stock rom.

The signal strength comes out normally, but when I actually use Wi-Fi, the speed becomes very, very slow after a while, and each time I had to turn Wi-Fi off and then turn it on again.

(Even after going through this process, the actual Wi-Fi operating time at normal speed did not exceed 1 minute.)

I tried to send A/S, but the distance was too far, and I gave up because there was no answer even when I inquired on the official page.

I've tried all custom roms, and all of them had problems with WiFi, and the only custom rom that my WiFi worked normally was Topaz Alpha 3.

I don't know how the developer solved this problem, or where there is a difference from Topaz Alpha 3 in the case of other custom roms, but I really wanted to tell the developer this.

Thanks to the developers of Topaz Alpha 3.

Without the Topaz Alpha 3, I wouldn't have been able to afford my data bill.
 
  • Like
Reactions: drashlex

drashlex

New member
Oct 12, 2020
4
0
My phone (1) had wifi issues from the stock rom.

The signal strength comes out normally, but when I actually use Wi-Fi, the speed becomes very, very slow after a while, and each time I had to turn Wi-Fi off and then turn it on again.

(Even after going through this process, the actual Wi-Fi operating time at normal speed did not exceed 1 minute.)

I tried to send A/S, but the distance was too far, and I gave up because there was no answer even when I inquired on the official page.

I've tried all custom roms, and all of them had problems with WiFi, and the only custom rom that my WiFi worked normally was Topaz Alpha 3.

I don't know how the developer solved this problem, or where there is a difference from Topaz Alpha 3 in the case of other custom roms, but I really wanted to tell the developer this.

Thanks to the developers of Topaz Alpha 3.

Without the Topaz Alpha 3, I wouldn't have been able to afford my data bill.
For me too, this is the only ROM that solved my WiFi problem
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    New update beta 1 available

    Changelog
    January 2023 SPL, Improved Glyph, Enforcing SELinux
    1
    No problem, I got a perfect custom kernel to use with Topaz beta 3.
    1
    New update beta 1 available

    Changelog
    January 2023 SPL, Improved Glyph, Enforcing SELinux

    You miss the most important mate :)
    NOS 1.5 base (the first custom rom using 1.5^^)


    Paranoid Android Topaz Beta 1 - Official | Android 13 | Nothing Phone (1)

    January 09, 2023


    PA Beta 1 Changelog (spacewar)

    • Upgraded to January 2023 Security Patch Level and Android 13 Quarterly Platform Release 1
    • Upgraded Nothing binaries to Nothing OS 1.5 Beta
    • Enforcing SELinux
    • Added additional Glyph settings
    • User builds
    • Single Tap to Wake
    • Performance improvements and bug fixes
    1
    @herna At last after falcon moto g, came here to meet you ,
  • 34
    Frame 7.png


    We are very excited to announce the alpha of Paranoid Android Topaz, based on Android 13.

    On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.

    Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.

    Notice

    We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.

    You can donate on the link below:

    Donate

    Device-specific issues

    * Some HDR videos might lag after a few seconds of playing.


    Requirements

    Make sure you've latest platform tools for Android.

    Download

    You can always get our Alpha builds from our website Paranoid Android website

    Note: Custom kernels are NOT supported the kernel says it supports PA and GMS is included!

    Changelogs

    Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.

    Paranoid Android Topaz released

    Instructions


    • Unlock your bootloader, and in bootloader mode follow the next command

      fastboot update aospa-topaz-alpha-*-image.zip

      After the reboot, factory reset the device (only required for the first time you flash Paranoid Android)

    Kernel source.

    Important / Useful links
    Paranoid Android Twitter
    Paranoid Android Channel (Telegram)
    Paranoid Android Download Channel (Telegram)
    Paranoid Android Community (Telegram)

    Cheers and #StayParanoid!
    5
    Paranoid Android Topaz Alpha 2 is out!

    This update includes the following device specific changes:


    Fixed 5G indicator on statusbar and improved data connectivity
    Fixed UDFPS on lockscreen
    Improved vibration haptics

    For download links you can find the links in the next tweet (not available on website for infrastructure problems):

    Tweet


    #StayParanoid
    3
    Updated PA A1 to A2 :

    1/ Step 1 > Bootloader (Fastboot)
    Code:
    c:\Android>fastboot update aospa-topaz-alpha-2-phone1-20221019-image.zip
    --------------------------------------------
    Bootloader Version...:
    Baseband Version.....:
    Serial Number........: 8xxxxxxx
    --------------------------------------------
    extracting android-info.txt (0 MB) to RAM...
    Checking 'product'                                 OKAY [  0.002s]
    Setting current slot to 'a'                        OKAY [  0.007s]
    extracting boot.img (96 MB) to disk... took 0.531s
    archive does not contain 'boot.sig'
    Sending 'boot_a' (98304 KB)                        OKAY [  2.748s]
    Writing 'boot_a'                                   OKAY [  0.167s]
    extracting dtbo.img (24 MB) to disk... took 0.073s
    archive does not contain 'dtbo.sig'
    Sending 'dtbo' (24576 KB)                          OKAY [  0.664s]
    Writing 'dtbo'                                     OKAY [  0.038s]
    archive does not contain 'dt.img'
    archive does not contain 'pvmfw.img'
    archive does not contain 'recovery.img'
    extracting vbmeta.img (0 MB) to disk... took 0.001s
    archive does not contain 'vbmeta.sig'
    Sending 'vbmeta' (8 KB)                            OKAY [  0.001s]
    Writing 'vbmeta'                                   OKAY [  0.001s]
    extracting vbmeta_system.img (0 MB) to disk... took 0.001s
    archive does not contain 'vbmeta_system.sig'
    Sending 'vbmeta_system' (4 KB)                     OKAY [  0.001s]
    Writing 'vbmeta_system'                            OKAY [  0.001s]
    archive does not contain 'vbmeta_vendor.img'
    extracting vendor_boot.img (96 MB) to disk... took 0.237s
    archive does not contain 'vendor_boot.sig'
    Sending 'vendor_boot' (98304 KB)                   OKAY [  2.657s]
    Writing 'vendor_boot'                              OKAY [  0.283s]
    extracting super_empty.img (0 MB) to disk... took 0.001s
    Rebooting into fastboot                            OKAY [  0.001s]
    < waiting for any device >
    Sending 'super' (4 KB)                             OKAY [  0.001s]
    Updating super partition                           OKAY [  0.019s]
    Resizing 'odm_a'                                   OKAY [  0.004s]
    Resizing 'product_a'                               OKAY [  0.004s]
    Resizing 'system_a'                                OKAY [  0.005s]
    Resizing 'system_ext_a'                            OKAY [  0.004s]
    Resizing 'system_b'                                OKAY [  0.004s]
    Resizing 'vendor_a'                                OKAY [  0.004s]
    Resizing 'vendor_b'                                OKAY [  0.004s]
    archive does not contain 'boot_other.img'
    extracting odm.img (1 MB) to disk... took 0.015s
    archive does not contain 'odm.sig'
    Resizing 'odm_a'                                   OKAY [  0.005s]
    Sending 'odm_a' (1568 KB)                          OKAY [  0.046s]
    Writing 'odm_a'                                    OKAY [  0.096s]
    archive does not contain 'odm_dlkm.img'
    extracting product.img (1786 MB) to disk... took 14.842s
    Invalid sparse file format at header magic
    archive does not contain 'product.sig'
    Resizing 'product_a'                               OKAY [  0.005s]
    Sending sparse 'product_a' 1/7 (262116 KB)         OKAY [  7.673s]
    Writing 'product_a'                                OKAY [  0.454s]
    Sending sparse 'product_a' 2/7 (262124 KB)         OKAY [  7.725s]
    Writing 'product_a'                                OKAY [  0.442s]
    Sending sparse 'product_a' 3/7 (262124 KB)         OKAY [  7.709s]
    Writing 'product_a'                                OKAY [  0.444s]
    Sending sparse 'product_a' 4/7 (262128 KB)         OKAY [  7.706s]
    Writing 'product_a'                                OKAY [  0.430s]
    Sending sparse 'product_a' 5/7 (262116 KB)         OKAY [  7.723s]
    Writing 'product_a'                                OKAY [  0.449s]
    Sending sparse 'product_a' 6/7 (262140 KB)         OKAY [  7.725s]
    Writing 'product_a'                                OKAY [  0.445s]
    Sending sparse 'product_a' 7/7 (250948 KB)         OKAY [  7.405s]
    Writing 'product_a'                                OKAY [  0.448s]
    extracting system.img (923 MB) to disk... took 8.025s
    Invalid sparse file format at header magic
    archive does not contain 'system.sig'
    Resizing 'system_a'                                OKAY [  0.005s]
    Sending sparse 'system_a' 1/4 (262108 KB)          OKAY [  7.662s]
    Writing 'system_a'                                 OKAY [  0.454s]
    Sending sparse 'system_a' 2/4 (262120 KB)          OKAY [  7.721s]
    Writing 'system_a'                                 OKAY [  0.459s]
    Sending sparse 'system_a' 3/4 (262116 KB)          OKAY [  7.700s]
    Writing 'system_a'                                 OKAY [  0.448s]
    Sending sparse 'system_a' 4/4 (156524 KB)          OKAY [  4.622s]
    Writing 'system_a'                                 OKAY [  0.359s]
    extracting system_ext.img (565 MB) to disk... took 4.721s
    Invalid sparse file format at header magic
    archive does not contain 'system_ext.sig'
    Resizing 'system_ext_a'                            OKAY [  0.004s]
    Sending sparse 'system_ext_a' 1/3 (262116 KB)      OKAY [  7.697s]
    Writing 'system_ext_a'                             OKAY [  0.446s]
    Sending sparse 'system_ext_a' 2/3 (262140 KB)      OKAY [  7.559s]
    Writing 'system_ext_a'                             OKAY [  0.429s]
    Sending sparse 'system_ext_a' 3/3 (53244 KB)       OKAY [  1.570s]
    Writing 'system_ext_a'                             OKAY [  0.223s]
    archive does not contain 'system_other.img'
    extracting vendor.img (857 MB) to disk... took 7.361s
    Invalid sparse file format at header magic
    archive does not contain 'vendor.sig'
    Resizing 'vendor_a'                                OKAY [  0.004s]
    Sending sparse 'vendor_a' 1/4 (262100 KB)          OKAY [  7.707s]
    Writing 'vendor_a'                                 OKAY [  0.461s]
    Sending sparse 'vendor_a' 2/4 (262124 KB)          OKAY [  7.700s]
    Writing 'vendor_a'                                 OKAY [  0.452s]
    Sending sparse 'vendor_a' 3/4 (262140 KB)          OKAY [  7.702s]
    Writing 'vendor_a'                                 OKAY [  0.449s]
    Sending sparse 'vendor_a' 4/4 (88768 KB)           OKAY [  2.635s]
    Writing 'vendor_a'                                 OKAY [  0.285s]
    archive does not contain 'vendor_dlkm.img'
    archive does not contain 'vendor_other.img'
    Rebooting                                          OKAY [  0.000s]
    Finished. Total time: 197.003s

    2/ Step 2 > Update Magisk Boot Patched
    Code:
    c:\Android>fastboot boot magisk_patched-25205_96FMZ.img
    Sending 'boot.img' (98304 KB)                      OKAY [  2.721s]
    Booting

    3/ Step 3 > Boot Success
    Apply Root after Boot Successfuly
    Code:
    Open Magisk :
    Magisk > Install > Direct install (Recommanded) > "Let's Go"
    "All done!" > Reboot


    BUG : I use 2 SIM and now on Alpha 2 there only one Signal for the "prefered Data" SIM and not the other SIM