Development Paranoid Android Topaz 1 - Nothing phone (1)

[Exodusnick]

Ever seen something so crazy
I deleted Google Play services data and it comes an update to pa from Nothing os

 

[JKurtz87]

Ever seen something so crazy
I deleted Google Play services data and it comes an update to pa from Nothing os
View attachment 5749305

You should download it and dump that full 1.1.6 update lol

 

[P6P]

You should download it and dump that full 1.1.6 update lol

It's already available

 

[Exodusnick]

Is a bug

Problem solved Google Play Services data deleted thereby's reset and then Google Play Services updated via Play Store now comes the message from the system update no longer.

 

[sumit61900729]

Wieless charging working in this rom

 

[Exodusnick]

Wieless charging working in this rom

Yes work .

 

[Exodusnick]

What is this and why does it happen every time?

Looks like a nothing OS update again.

 

[kimocoder]

So, i merged latest android-common and added full Kali NetHunter support to the kernel

 

[aikattx]

I just got my Nothing Phone today, and to my surprise, PA is already started development ! Definitely gonna test this out

 

[Exodusnick]

https://twitter.com/i/web/status/1590289674899443715

 

[dexlemaffo]

I just got my Nothing Phone today, and to my surprise, PA is already started development ! Definitely gonna test this out

I honestly think that you should hold this thought a bit until it's stable enough.

 

[demiii]

1st Feedback
2nd Feedback
3rd Feedback

7h15 SOT - Excellent Battery Life (with AOD disabled)




What is your Operating System ? Windows 7 ?
You must redo these commands with ADB & Drivers updated.




Il you have installed Root module like "Safetynet Fix" it's the reason you have L3 Wide

PA is stock "Certified", not need to use Module for Certified Device/Safetynet

My OS is windows 11, I am using the latest version of ADB and Fastbootd drivers, also using updated android drivers. Tried everything on a Intel and on a AMD device, nothing changd

 

[Exodusnick]

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

Details:
• Version: #AOSPA #T
• Type: #ROM
• Build: #Official #beta
• Device: #Spacewar
• Updated: 18th Nov 2022

Links:
Download (http://paranoidandroid.co/phone1)| Mirror (https://t.me/paranoidaospa/110)
(https://t.me/paranoidaospa/78) Instructions (https://graph.org/AOSPA-Topaz-Spacewar-Flashing-instructions-10-15)
🖼 Screenshots (https://t.me/NothingPhone1/118880?single)
XDA Thread (https://forum.xda-developers.com/t/paranoid-android-sapphire-alpha-1-nothing-phone-1.4505797/)
Support (https://t.me/stayparanoid)

Changelog:
• Implemented Face Unlock
• Fixed display corruption
• Improved vibration
• Fixed Bluetooth codecs
• Fixed charging speed
• Improved auto brightness
• Improved boot time,
• Fixed DRM (Widevine L3 for now)
• November SPL
• Known issues (https://forum.xda-developers.com/t/paranoid-android-sapphire-alpha-1-nothing-phone-1.4505797/)

Maintainer: herna, xboxfanj, 33bca, TheCrazyLex
Updates : @NothingPhone1Updates
Chat : @NothingPhone1

 

[marcii-ec]

Thanks for the Update, seems a lot smoother now.

 

[QaulityPro]

Can anyone advise on the attempt to update to alpha 3

Im sure drivers are up to date. I didn't have this when updating from alpha 1 to 2.

Any help appreciated, thanks.

C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable

 

[Pho3nX]

Can anyone advise on the attempt to update to alpha 3

Im sure drivers are up to date. I didn't have this when updating from alpha 1 to 2.

Any help appreciated, thanks.

C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
usage: fastboot [ <option> ] <command>

---

Try to copy/past a proper folder contain adb / fastboot files on the c:\ root, don't use adb from a OneDrive synced folder with extracted files from your desktop.
And your line was wrong ;

C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip

instead

C:\>fastboot update C:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip

 

[QaulityPro]

Try to copy/past a proper folder contain adb / fastboot files on the c:\ root, don't use adb from a OneDrive synced folder with extracted files from your desktop.
And your line was wrong ;

C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip

instead

C:\>fastboot update C:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip

Thank you, I shall give that a go

 

[Black_Sandy]

why do I get this error message?
>fastboot update C:\Users\....\Downloads\aospa-topaz-alpha-3-phone1-20221118-image.zip

target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
Invalid sparse file format at header magi
archive does not contain 'system.sig'
Invalid sparse file format at header magi
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: d3960
--------------------------------------------
checking product...
OKAY [ 0.004s]
sending 'boot' (98304 KB)...
OKAY [ 2.231s]
writing 'boot'...
OKAY [ 0.202s]
sending sparse 'system' (775407 KB)...
OKAY [ 20.227s]
writing 'system'...
FAILED (remote: Partition not found)
finished. total time: 22.697s

 

[marcii-ec]

If someone is interested: I also tried the connection with my car today, it works perfect. I tried it with Android Auto cable and Android Auto wireless, no problems so far.

 

[AdiGurjar]

Bugs I found on PA Alpha 3 for NP1:

1-General Screen flickering
2-Auto brightness is poor
3-Battery life can be improved


Critical bugs:

1-Screen won't wake up at all with power button sometimes when AOD is on, a forced restart is the only workaround. Keeping the AOD off prevents this bug.

2-Excessive screen flickering when typing on low brightness.

3-Call UI is choppy.

Rest the rom is smooth and very responsive, kudos to the devs!