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

Development ROM ❯ ALIOTH/ALIOTHIN ❯ UNOFFICIAL ❯ ProtonAOSP 11

Search This thread

r3sp

Senior Member
Dec 6, 2010
94
41
Update very smooth, if someone has a problem at the first install, extract the super_empty.img then in fastbbot: fastboot wipe-super super_empty.img, after that fastboot update protonaosp-file.zip
Then before its booting up force in recovery (if you boot to recovery and has a error sign just press power and vol up and you get in the recovery) and format Data and then boot system :)

At the first times so smooth like HentaiOs Geekbenck Single 812 / Multi 3110
 
Last edited:

ngukz

Member
Jan 20, 2012
11
1
Surabaya
I've got very high temp even when idle

on the latest build, is there any fix to this?

edit----->
The problem persists when I turn on mobile data,
but the sims have no internet.
after turn on mobile data, temps back to normal.
 
Last edited:

MugetsuX93

Senior Member
Jul 15, 2017
50
41
Update very smooth, if someone has a problem at the first install, extract the super_empty.img then in fastbbot: fastboot wipe-super super_empty.img, after that fastboot update protonaosp-file.zip
Then before its booting up force in recovery (if you boot to recovery and has a error sign just press power and vol up and you get in the recovery) and format Data and then boot system :)

At the first times so smooth like HentaiOs Geekbenck Single 812 / Multi 3110
Can you check if normal phone calls are working fine for you? When I dial someone, I am able to hear their voice but they are not able to hear mine. VOIP calls like whatsapp/duo/telegram work well but normal calls, without using any bluetooth earphones are not working properly.

To reproduce this bug -

1. Connect a bluetooth earphone.
2. Make a call
3. The other party will be able to hear
4. disconnect the bluetooth earphones and continue talking, they will be able to hear.
5. Turn off bluetooth, make a call again, they will still be able to hear you.
6. Restart the phone
7. Now dont connect the bluetooth earphones, just make a call.
8. The other party will not be able to hear your voice.

Connect a bluetooth earphone once, and voila, it starts working normally. Some audio routing issue is present.

Edit: This issue gets resolved if I turn off google assistant voice recognition stuff. :D
 
Last edited:

Animesh Singh

Senior Member
Mar 17, 2014
237
71
29
kathmandu
www.facebook.com
Xiaomi Poco F3
Can you check if normal phone calls are working fine for you? When I dial someone, I am able to hear their voice but they are not able to hear mine. VOIP calls like whatsapp/duo/telegram work well but normal calls, without using any bluetooth earphones are not working properly.

To reproduce this bug -

1. Connect a bluetooth earphone.
2. Make a call
3. The other party will be able to hear
4. disconnect the bluetooth earphones and continue talking, they will be able to hear.
5. Turn off bluetooth, make a call again, they will still be able to hear you.
6. Restart the phone
7. Now dont connect the bluetooth earphones, just make a call.
8. The other party will not be able to hear your voice.

Connect a bluetooth earphone once, and voila, it starts working normally. Some audio routing issue is present.

Edit: This issue gets resolved if I turn off google assistant voice recognition stuff. :D
Bro is there ECHO problem on VOIP calls on speaker? because every ROM i tried has ECHO on Speaker.
 

UtsavTheGreat

Senior Member
Aug 10, 2016
424
3,865
19
Surat
Redmi K20 Pro
Xiaomi Poco F3
I knew the prob now. My bro "illuminated" my brain: I had to use Minimal ADB & Fastboot 1.4.3 to apply "fastboot --set-active=a" cmd, but actually what I was using was the normal/Windows cmd on the folder where I had the Boot and Vendor files (shift + right click opens Windows, not the Minimal 1.4.3 fastboot).

So what I did was:

(with the normal cmd: shift + right click)
  • fastboot flash boot_a boot.img
  • fastboot flash vendor_boot_a vendor_boot.img
(closing the normal. Going to the Minimal 1.4.3 and executing fastboot.exe)
  • fastboot --setactive=a
It worked.

I was writting well the --setactive=a, but it was returning me a "-- setactive" idk why.
Now what I will try, as you said, to insert "cmd" on the platform-tools folder and done.

EDIT:
Possible bugs:
- Weird stuff adding in the setup the Google Account (like had to repeat it twice)
- Telegram, Instagram, Whatsapp, etc. audios-vocals, are sent/recorded in quite low voice
- Periodically, Wifi stops working: it doesn't find any wifi. It happened once in 2 days, so it's not so, so bad (I'm in a place with around 20 wifi sources). Always solved by a system reboot, so nothing important.
View attachment 5356595

Tryied to factory reset and, for now, these are the bugs on both factory reset. I will add more when I know.
Yeah there is a problem with wifi which has been addressed and fixed in beta stay tuned for next release
 
  • Like
Reactions: ADEL_

uriii13

Senior Member
Nov 25, 2012
292
35
Yeah there is a problem with wifi which has been addressed and fixed in beta stay tuned for next release
I did not care a lot about that bug as long as it was periodically. I was more worried about the (quite) low voice recording. Now trying SyberiaOS and it's perfectly working. Can it be related to the noise cancellation micro's?

Rooted with some essential tweaks, love this rom quite a lot. I will change once this voice is fixed :) I will stay tunned!
 

WM-Sef

Senior Member
Jan 30, 2009
159
11
I can't flash this ROM. I followed the instruction, but in usermode fastboot it errors out:

"Old partitions are not compatible with the new super layout; wipe needed"

The wiki suggests reflashing MIUI stock which I did, but that didn't fix the problem. Any hints?

Edit: After flashing LOS, it worked all of a sudden...
 
Last edited:

uriii13

Senior Member
Nov 25, 2012
292
35
I can't flash this ROM. I followed the instruction, but in usermode fastboot it errors out:

"Old partitions are not compatible with the new super layout; wipe needed"

The wiki suggests reflashing MIUI stock which I did, but that didn't fix the problem. Any hints?

Edit: After flashing LOS, it worked all of a sudden...
I'm nooby here, but maybe it's because you have TWRP installed. It's not compatible with it. So yeah, flashing MIUI will help as long as you will flash authomatically stock recovery.

That's my theory. If it's other prob, idk hahah
 

WM-Sef

Senior Member
Jan 30, 2009
159
11
I can't use some apps. They are hanging while being started.

The logcat logs show this:

08-08 02:48:26.258 594 594 E spcomlib: [spcom_wait_for_event] event [0] [pil_called] EVENT_STATUS_TIMEOUT
08-08 02:48:26.258 594 594 E spcomlib: [spcom_wait_for_sp_link_up] PIL not called !
08-08 02:48:26.258 594 594 E KeymasterUtils: SPU is not available
08-08 02:48:26.258 594 594 E KeymasterUtils: IsSbKmAvailable failed
08-08 02:48:26.259 594 594 E KeyMasterHalDevice: legacy_generate_key
08-08 02:48:26.259 594 594 E KeyMasterHalDevice: ret: -45
08-08 02:48:26.259 594 594 E KeyMasterHalDevice: resp->status: 0
08-08 02:48:26.263 9088 9088 E KeyStore: generateKeyInternal failed on response -45

This seems like a ROM issue. Any ideas? Might this be the culprit?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    ProtonAOSP
    Android 11 ROM​

    ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.

    Screenshots
    Screenshots of the latest version

    Installation
    This ROM is currently distributed as OTAs.
    Complete procedure can be followed from this detailed guide

    Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.

    Features
    List of current features, with accompanying screenshots and explanations

    Downloads
    Downloads and Changelogs for all the versions.

    Builds with and without minimal Google services (GApps) included are provided for convenience.

    Support
    If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.

    Join the Telegram group for support and extras

    Donate
    If you found my work useful and want to continue supporting development contribute by becoming a
    • Patron for early releases and better support.
    • You can also provide a small donation through PayPal
    • Indian users can support through UPI: [email protected]

    Kernel source code
    ROM source code
    6
    ProtonAOSP 11.5.2 has been released.

    Changes:
    ROM side
    • July security patch
    • Added search to website
    Added red, green, and blue color balance settings
    Added alarm, ringtone, and notification sounds from Plasma Mobile
    • Added HarmonyOS Sans font style
    Extended font styles to affect third-party apps (reboot to apply changes)
    Improved Night Light quality using chromatic adaptation (reduced color distortion)
    • Improved Ambient EQ quality (with modern color science: CAT16)
    • More gradual transition when turning Night Light on/off
    Device Side
    • Added setting for increased touch sensitivity
    • Added support for HDR10+
    • Added support for MifareClassic and NDEF on NFC
    • Updated NFC SN1XX configuration and binaries for MW 11.2.0
    • Updated FW and vendor from MIUI 21.7.21
    • Fixed issues related to modem resulting in subsystem panic in some cases
    • Implemented retry mechanism on modem helper
    • Enabled PCIe bandwidth scaling to modem
    • Fixed inaccurate reading of some GPU temperature
    • Speed up the touchscreen SPI clock max frequency
    • Upgraded alioth touchscreen firmware to latest
    • Fixed video playback freezing in some usescases
    • Optimized display panel configuration
    • Kernel updated to latest CAF tag and synced with ACK android-4.19-stable
    • Kernel compiled using latest proton-clang 13.0

    Download

    If you found my work useful and want to continue supporting development contribute by becoming a
    Patron for early releases and better support.
    • You can also provide a small donation through PayPal
    • Indian users can support through UPI: [email protected]
    3
    Install without problems, nice stock rom like HentaiOs.

    For everybody no Faceunlock or did I miss something, didn't find it.

    How to install Magisk? If I flash Twrp nothing happens just a black screen if I boot to Recovery.
    Twrp is not supported
    And for magisk you can just patch the provided boot image and flash from bootloader mode.

    About faceunlock there is no open-source implementation made for aosp ROMs.
    3
    Still nothing:
    View attachment 5355235

    And these are the files I have:
    View attachment 5355233

    Edit: still blocked there :( I guess it has to be something related to the "adb" folder and the fastboot.exe. I have the "adb" folder from my last ROG Phone 2. Anyway, in the tutorial it doesn't say anything about that folder, but as long as I'm reading in the cmd, it's trying to find something there, innit?
    There shouldn't be a space between "--" and "set-active=a"

    Wrong -- set-actice=a
    Right --set-active=a

    Also download the latest platform tools and unpack them and type cmd in the address bar of that folder (which would launch cmd window) and use fastboot commands from there