Database Develop

[ROM][AOSP][KK][cfX-Toolchain LLVM Clang 3.5] HTC One (M7SPR) codefireX Nightlies

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CFX website: http://codefirex.com​
This well established Android distribution treats development differently than any other to further our Android platform as a whole. Also, this ROM utilizes our unique build system and a custom LLVM 3.5 suite based toolchain globally.
CFX Issue Tracker.
BUGS:
At this time, there is no embedded SU app in the ROM. A link to download SuperSU flashable zip is located in the downloads section below.
Utilizing the LLVM CLANG CI globally, working heavily with upstreams with a goal of furthering our entire Android platform.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization and Polly optimizations (another custom ROM first). Feel free to google these a bit.
Much of our source have code fixes, cleanups, and many minor optimizations to set us even further ahead of the community. These are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can achieve for your device without sacrificing stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Utilizing all O4 optimizations (Optimization Level 4) including LTO (with binutils plugins), and additionally LLVM Polly.
Of course we also have several neat UI features, including but not limited to:
T-Mobile Theme Engine.
DPI Wizard (no junk like build.prop tweaks).
Quick Settings panel customizations.
Live network stats in your statusbar.
Button backlight customizations.
Hardware button customizations.
Volume button customizations.
Expandable volume menu.
CFX Weather "Found under settings -> CFX -> Weather"
Many more being added during the nightly builds.
CFX 4.4 -Nightlies
You can check the status of the nighlies using this link: M7spr Status
Latest CodeFireX builds
SuperSU
4.4 Gapps
Installation Instructions:
DO NOT FLASH IF INTENDED DEVICE IS NOT A SPRINT HTC ONE [M7SPR]- THIS ROM IS ONLY FOR THE SPRINT HTC ONE
1) Download ROM
2) Save to internal memory
3) Boot to recovery
4) If this is the first time flashing please perform a full wipe - NOT INTERNAL MEMORY
4.5) If you already run this you can wipe cache and dalvik.
5) Flash ROM
6) Flash Gapps
7) Flash Superuser zip
8) Reboot
9) Restore
10) Enjoy!
Team CodeFires GIT
Our thanks go out to all the open source developers who made our work possible.
Below is an ever-incomplete list of some of the 'indirect' contributors to our ROMs:
The Android Open Source Project
LLVM CI
Linux Foundation
Code Aurora Forum
CyanogenMod Inc.
Chainfire
Many more!
​​​
XDA:DevDB Information
CodeFireX 4.4 - M7SPR, a ROM for the Sprint HTC One
Contributors
BMP7777, EmptyGODFATHER
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: Unlocked, rooted, Sprint variant, 5.x PhilzTouch, 6.x CWM, or equivalent TWRP
Based On: AOSP, CM
Version Information
Status: Testing
Created 2014-01-10
Last Updated 2014-03-19​

Changelog
You can find CodeFire's live changelog here: Changelog

I guess I will use this as an update on my status! I work at a hospital in the IT department and am in charge of all things computers / upgrades / network / anything else my boss wants me to do lol. With the XP end date nearing I am in the process of imaging over 400 pc's to windows 7 and also in the middle of migrating our IBM systems to newer hardware so that we can then upgrade our H.I.S. system "not fun". If you are in doubt of the status of the ROM just check the download link in the OP above and see if there is a new nightly posted! Also, any issues found either post in this thread or send me a PM and I will send it off to the devs to fix!

BMP7777, you are seriously awesome for porting all these ROMs to the m7spr. I remember Team Codefire talking about their rom coming out, but haven't been following their work. It's kind of weird to not have CFX and Themes in the Settings menu. Any idea if this should make things more stable, or they just haven't implemented this yet?

SlimWadey said:
BMP7777, you are seriously awesome for porting all these ROMs to the m7spr. I remember Team Codefire talking about their rom coming out, but haven't been following their work. It's kind of weird to not have CFX and Themes in the Settings menu. Any idea if this should make things more stable, or they just haven't implemented this yet?
Click to expand...
Click to collapse
As of now, they are both .apks rather than embedded in settings. Check your app drawer. Don't know the why's behind it, but I'm sure it's by design. Any feedback you have about how this badboy runs will be appreciated. :angel:

BMP7777 said:
As of now, they are both .apks rather than embedded in settings. Don't know the why's behind it, but I'm sure it's by design. Any feedback you have about how this badboy runs will be appreciated. :angel:
Click to expand...
Click to collapse
Well, I've only been using it for a half hour or so with no drama. I'm at work so I can't really fiddle with it too much. The one thing I've been getting on KitKat roms is the SIM card lock, and a few of them have been giving me random reboots. I'll let you know if I get either one of these today.
I like the file explorer, it's the perfect amount of simple and functional.
BTW, I had to root with SuperSU. I assumed that this would be included, as it's a Chainfire ROM.

SlimWadey said:
Well, I've only been using it for a half hour or so with no drama. I'm at work so I can't really fiddle with it too much. The one thing I've been getting on KitKat roms is the SIM card lock, and a few of them have been giving me random reboots. I'll let you know if I get either one of these today.
I like the file explorer, it's the perfect amount of simple and functional.
BTW, I had to root with SuperSU. I assumed that this would be included, as it's a Chainfire ROM.
Click to expand...
Click to collapse
This is not a completed ROM, so any extras or even standard items may not have been integrated yet. Have others experienced this?
BTW I don't think that Chainfire has any affiliation with CFX. At least, I see no threads by him here for CFX, and I didn't find him listed as a member on their site.

BMP7777 said:
This is not a completed ROM, so any extras or even standard items may not have been integrated yet. Have others experienced this?
BTW I don't think the Chainfire has any affiliation with CFX. At least, I see no threads by him here for CFX, and I didn't find him listed as a member on their site.
Click to expand...
Click to collapse
Oh, I feel silly. I didn't even think about it. I just ASSumed that they were affiliated. Either way, I had to root it with SuperSU. Not a big deal, just an observation.
Also, I went to lunch today, and lost data until I toggled Airplane Mode. I think it was because the restaurant was a brick building, but I'm not sure because it didn't seem to connect until I toggled Airplane Mode, even though I waited ~5 minutes before trying. Otherwise, nothing to report. No SIM card locks or random reboots yet.

SlimWadey said:
Oh, I feel silly. I didn't even think about it. I just ASSumed that they were affiliated. Either way, I had to root it with SuperSU. Not a big deal, just an observation.
Also, I went to lunch today, and lost data until I toggled Airplane Mode. I think it was because the restaurant was a brick building, but I'm not sure because it didn't seem to connect until I toggled Airplane Mode, even though I waited ~5 minutes before trying. Otherwise, nothing to report. No SIM card locks or random reboots yet.
Click to expand...
Click to collapse
Thanks for your input. I'm going to add a few things to the ROM zip this evening: CFX bootani, SU apk, maybe a couple of other thing to make it interesting. But, it'll have to wait until I'm done building the latest BS update...... did I say that outloud?

ROM layout is great... I like a lot of the KitKat features.
I am getting some random freezing of the screen... Does not seem to be specific to any app or feature.
Also... Can anyone tell me how to get to the browser settings in this new browser version? I can't seem to find them.
Thanks.

I only have one phone you know

I unplugged it from the wall this morning, and when I slid the lock ring, I got a random reboot. Still, to go about 20hr without issue isn't too bad for an experimental build, eh?
Sent from my One using Tapatalk

FrostyF7 said:
I only have one phone you know
Click to expand...
Click to collapse
Life is full of hard choices brother...
Sent from my One using XDA Premium 4 mobile app

Drybonz said:
ROM layout is great... I like a lot of the KitKat features.
I am getting some random freezing of the screen... Does not seem to be specific to any app or feature.
Also... Can anyone tell me how to get to the browser settings in this new browser version? I can't seem to find them.
Thanks.
Click to expand...
Click to collapse
Maybe this will help some....
http://www.howtogeek.com/176009/how...le-experience-launcher-on-any-android-device/

BMP7777 said:
Maybe this will help some....
http://www.howtogeek.com/176009/how...le-experience-launcher-on-any-android-device/
Click to expand...
Click to collapse
Thanks for the link, and I do like the new launcher.
However, I'm probably dense, but after reading that article I'm still not sure how to find the browser settings that I was asking about.

New build on deck
New build with CFX bootanimation and latest commits. All feedback welcomed. I had trouble downloading it, but apparently no one else has because I have 13 DLs in the last hour and no one knew about it. Any problems, let me know. Also post any features you come across so I can add them to the OP. Hard to tell whats what with a beta......
http://goo.im/devs/BMP7777/ONE-CodeFireX//full_m7spr-cfxe-OPENMASTER-20140111.113455.zip
I'll update the OP soon.....

So the three dot menus are disabled, but the back button menu also doesn't bring up the menus. Is this the intended behavior? I can't find anything in the CFX options or system settings to changes any of this. I tried to add the three dot menus back with an xposed module but it also gave me the soft navigation bar. If you can point me to the settings for this I appreciate it.

I've just gotten started, but so far I have 3-dot menus in every app I have opened. Some of them are at the bottom, though.

BMP7777 said:
I've just gotten started, but so far I have 3-dot menus in every app I have opened. Some of them are at the bottom, though.
Click to expand...
Click to collapse
Weird... I didn't have the ones at the top or bottom. I tried your beanstalk rom last night and it does have them if I select the option.
I like the option that the beanstalk has to keep the home and back buttons always lit too.

I do not own this device, but really happy to see developers using codefireXperiment for building custom ROMs as well.
Way to Go !
sorry for off-topic message.

[DISCONTINUED] [8.1.x][OFFICIAL][DISCONTINUED] CarbonROM | cr-6.1 [kagura]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Notice:
For this ROM to work you need to use the latest ODM Images. If you need additional guidance on how to do that, please refer to Sonys Guide on how to flash an ODM Image.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia XZ
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2018-03-31
Last Updated 2018-07-19

No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?

LuthfiKun said:
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
Click to expand...
Click to collapse
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.

Dual sim support?

Myself5 said:
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Click to expand...
Click to collapse
Alright format it is.
agentsandy007 said:
Dual sim support?
Click to expand...
Click to collapse
No it isn't. At least out of the box. You can find a patch on Sony AOSP Build thread.

Volte Supported??

First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:

Klaus N. said:
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Click to expand...
Click to collapse
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?

Can you upload screen recording of rom from home to settings and other functions.

I plan on flashing this soon, but I figured I'd tell you, your link to the Carbon FAQ is broken.

ilininja said:
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Click to expand...
Click to collapse
The battery consumption while in use is ok. But my device doesn't go into deepsleep while the screen is off. So I had lost about 23 % in 10 hrs - leaving the device untouched!
Video recording works; I haven't noticed that bug.
Saroj11488 said:
Can you upload screen recording of rom from home to settings and other functions.
Click to expand...
Click to collapse
Sorry, I went back to stock for now, as there's a new stock fw (41.3.A.2.107).

I have a few bugs to report. First, the fingerprint sensor is extremely slow, about half or even one third of the speed compared to stock. Second, could you guys please fix the deepsleep? That one is not working for now. And third, Night Light does not work at all...
Thank you for updating the XZ to Android 8.1 I am glad to see carbon rom on this device although it is not that stable for now.

Really nice ROM and I'm looking forward to make this my daily driver, I tried it for two days and these are the bugs I found:
1: GPU performance is really bad with 2d games and google maps lagging all the time when they never do on stock
2: CPU performance is inferior compared to stock, especially single threaded
3: enabling 120 hz display won't do anything and the settings or UI will crash when leaving the page
4: fingerprint seems to be sometimes less responsive, usable but can be improved
Camera is not so bad and the modded google camera works well, hopefully this will become the first proper AOSP based platform for this device that has only seen failures until now, keep up the good work.

Can I dirty flash this rom for just update?
I use Carbon Rom 3/31 version, but I can't use delta update because my device cannot receive the stock script.
I must change the rom script with Notepad+.
So...can I use dirty flash or....could you manage it?

Thanks for continously updating this rom and thank you for fixing the bug with the fingerprint sensor.
I'm not sure if deepsleep has been fixed but there is a big problem with playing music. I can't even play any music track at all...

Hello, looking forward to make this my daily driver, is it possible ?
What I would want is decent battery life and camera.

Hello. I tried to listen to music after installing the ROM, but the earphones are disconnected as soon as they are connected to the smartphone.
The earbuds pfe 132 and are made up of earphones with an iphone microphone.

L'ily said:
Clean flashed the 10th build along with Rytekk's dual-SIM patch, Pico Open GApps and Magisk 16.3 to my F8332 and other than that annoying SD notification (which can be banished to the notification drawer by making System UI notifications low priority) and Night Light not working, the only other major issue raised ITT of the CPUs not entering Deep Sleep is fixed according to Adiutor.
Great stuff. I haven't been able to standardise on one ROM since the CM days (interesting side note, it looks like you built the kernel for the NOCT build on my Z2 tablet).
I recommend this to anyone for daily use. Also, lower your expectations to realistic levels guise. I remember when XDA threads were for flagging major broken functionality, not complaining that a few amateur enthusiasts weren't putting out work that competed on every indicator against the finished product of a multibillion-dollar for-profit international conglomerate.
Sent from my Sony Xperia XZ using XDA Labs
Click to expand...
Click to collapse
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works

Hello, with the 10th build I have a problem with the installation, it keeps telling me that Google services framework stopped.
Any help ?
(V11 vendor image odm, formated data)

BigMixman said:
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Click to expand...
Click to collapse
Add these lines in build.prop, and reboot.
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,0

[11][OFFICIAL] CarbonROM | cr-9.0 [fajita]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​

FINALLY! YES! WOOHOO!

I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever

void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.

Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.

Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look

Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.

Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?

Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.

When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work

Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.

My facebook and insta videos r not playing.. can't able to see them .. how to fix it

Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.

So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever

Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.

Google Camera, just google up gcam ports

only reason fr nt using Carbon is there is no
face unlock

Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks

Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website

I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?

[ROM] ubuntu touch 16.04/20.04 community port

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits​
https://github.com/8890q/ for LineageOS 18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/NotKit for giving me very helpful hints about ubports/halium specifics
https://github.com/ExpressLuke for testing the edge on my behalf
these awesome people gave me useful pointers for https://github.com/Kethen/herolte_treble to come to fruition, and is used in this port:
https://github.com/ivanmeler
https://github.com/ExpressLuke
https://github.com/00p513-dev
​Status​
Samsung Galaxy S7 (Exynos) • Ubuntu Touch • Linux Phone
Flash your Samsung Galaxy S7 (Exynos) with the latest version of the Ubuntu Touch operating system, a privacy focused OS developed by hundreds of people.
devices.ubuntu-touch.io
There might be other instabilities that I do not know of, use at your own risk
while 20.04 development builds are available through ubport installer, note that 20.04 is still in heavy development
Installation​ubport installer now supports Galaxy S7 exynos
alternatively zips for the latest twrp can be found below, herolte for flat, hero2lte for edge
Downloads​note that these releases are extremely outdated, for updated builds, use ubports installer
Releases · Kethen/samsung-exynos8890
halium 11 ubports for herolte, hero2lte and gracerlte - Kethen/samsung-exynos8890
github.com
Building and more information​
GitHub - Kethen/samsung-exynos8890: halium 11 ubports for herolte, hero2lte and gracerlte
halium 11 ubports for herolte, hero2lte and gracerlte - GitHub - Kethen/samsung-exynos8890: halium 11 ubports for herolte, hero2lte and gracerlte
github.com
Reporting Issues​
Issues · UBports / Porting / Community Ports / android11 / Samsung Galaxy S7 / samsung-exynos8890 · GitLab
Samsung Galaxy S7/S7 Edge
gitlab.com
Unofficial Waydroid Images​This is no longer required, waydroid has official h11 support and should be able to download official images during init. The waydroid helper app from openstore should be able to setup waydroid without using custom images.
Releases · Kethen/waydroid_build
personal waydroid build script. Contribute to Kethen/waydroid_build development by creating an account on GitHub.
github.com
Telegram discussion group​
S7/Edge/NoteFE Exynos Ubuntu Touch
S7/Edge/NoteFE Exynos Ubuntu Touch discussions Use the bug tracker at https://gitlab.com/ubports/porting/community-ports/android11/samsung-galaxy-s7/samsung-exynos8890/-/issues if you have an issue Try to be nice to eachother and stay on-topic /notes
t.me
If you have an issue please use the bug tracker above instead

Hi, does Anbox work on this ROM?

Ex novo said:
Hi, does Anbox work on this ROM?
Click to expand...
Click to collapse
waydroid has no halium 11.0 support at the moment, but it should work once that is out

does sms out work

King081 said:
does sms out work
Click to expand...
Click to collapse
yes

Cool

I love this port and I've been able to pull off daily driver activities with it so far on my S7 edge. Still testing.

I've been working with the daily builds and at version 140, I can't tell much significant difference with each one though my phone freezes less randomly and heats up less (I think this is specific to my particular phone or maybe because I tried tinkering with waydroid for so long before giving up for the time being?) the random freezes persist after a good number of hours of constant use, still great. As with the calling, it works quite well on my device, both recieving and sending calls. Only major issue seems to be with the USSD codes as they would go through but the further responses after the first dial do not work (maybe something with the mms situation?). This is something I am quite new to, so I don't know how useful this feedback is but this OS is definitely something I'm keeping on this device.

childoftext said:
I've been working with the daily builds and at version 140, I can't tell much significant difference with each one though my phone freezes less randomly and heats up less (I think this is specific to my particular phone or maybe because I tried tinkering with waydroid for so long before giving up for the time being?) the random freezes persist after a good number of hours of constant use, still great. As with the calling, it works quite well on my device, both recieving and sending calls. Only major issue seems to be with the USSD codes as they would go through but the further responses after the first dial do not work (maybe something with the mms situation?). This is something I am quite new to, so I don't know how useful this feedback is but this OS is definitely something I'm keeping on this device.
Click to expand...
Click to collapse
some mitigations against random freezes were added last Friday, the issue is being tracked here https://gitlab.com/ubports/porting/...msung-galaxy-s7/samsung-exynos8890/-/issues/4
While I can do ussd codes consecutively without issues, a cellular issue fix was also added recently https://gitlab.com/ubports/porting/...msung-galaxy-s7/samsung-exynos8890/-/issues/2, and no one ever sends mms here so idk if that could get in the way

katharinechui First of all, congratulations for the excellent work, I tested this rom and it is excellent!.
I really love Ubuntu Touch, but I need to have dualboot because I have a lot of apps I need to work that don't work on waydroid...
Do you happen to have a ready-made Halium-boot image to use with the Ubports GSI? or any way to use your Halium11 image in dual boot?
I've been trying to do a dualboot on the S7 for a while, I know that with a GSI image you can just change the boot.img to halium-boot, I've already done that on Redmi, but on the S7 I really didn't find anything working for a dualboot with ubports.
I've already compiled the Redmi Note 4X image (mido) once following the ubports tutorial, but I don't have time to research this on the S7 Edge anymore, I also don't have the patience anymore..

mcgragor said:
katharinechui First of all, congratulations for the excellent work, I tested this rom and it is excellent!.
I really love Ubuntu Touch, but I need to have dualboot because I have a lot of apps I need to work that don't work on waydroid...
Do you happen to have a ready-made Halium-boot image to use with the Ubports GSI? or any way to use your Halium11 image in dual boot?
I've been trying to do a dualboot on the S7 for a while, I know that with a GSI image you can just change the boot.img to halium-boot, I've already done that on Redmi, but on the S7 I really didn't find anything working for a dualboot with ubports.
I've already compiled the Redmi Note 4X image (mido) once following the ubports tutorial, but I don't have time to research this on the S7 Edge anymore, I also don't have the patience anymore..
Click to expand...
Click to collapse
starting from https://gitlab.com/ubports/porting/...mmit/0342d2858fd431a8f0c5e4118141cad615a8c835, the halium bootscript will prefer booting from /data/ubuntu.img or /data/halium-rootfs/ if available
you can find the new boot.img on CI once that's ready, ubuntu.img is also available on CI
that should enable your use case of dual booting by swapping between halium boot.img and android boot.img, while having android system.img installed to partition and ubuntu.img installed to /data
note that this is not and will not be the default installation method so OTA will not work

katharinechui​Thank you for your help. This will help me a lot in my personal project...
I'm doing everything to banish systems like android from my life, I managed to completely abandon windows last year, but unfortunately android is still necessary until I can run the apps I need on wayroid or anbox, but using dual boot with Ubuntu I can minimize the amount of data that can be exposed, because I'm going to use E-foundation's GSI firmware that already drastically reduces the exposed data and I'll only use it when strictly necessary.I'm doing everything to banish systems like android from my life, I got it completely windows in the last year, but unfortunately android is still needed to work until I can run the apps I need on wayroid or anbox, however using dual boot with Ubuntu I can very much avoid my data being exposed, because I will only use android when necessary.
I took the ubports_GSI_installer_v10.zip file that I had here and changed the rootfs.img to your ubuntu.img and flashed the boot.img, it worked perfectly, even though I used a Lineage Pie.
About OTA, I can do the update manually when a new update is released.
I forked your gitlab repository to keep up with the changes and try out some ideas.
Thank you so much!
You saved my life and my data privacy! XD

mcgragor said:
katharinechui​Thank you for your help. This will help me a lot in my personal project...
I'm doing everything to banish systems like android from my life, I managed to completely abandon windows last year, but unfortunately android is still necessary until I can run the apps I need on wayroid or anbox, but using dual boot with Ubuntu I can minimize the amount of data that can be exposed, because I'm going to use E-foundation's GSI firmware that already drastically reduces the exposed data and I'll only use it when strictly necessary.I'm doing everything to banish systems like android from my life, I got it completely windows in the last year, but unfortunately android is still needed to work until I can run the apps I need on wayroid or anbox, however using dual boot with Ubuntu I can very much avoid my data being exposed, because I will only use android when necessary.
I took the ubports_GSI_installer_v10.zip file that I had here and changed the rootfs.img to your ubuntu.img and flashed the boot.img, it worked perfectly, even though I used a Lineage Pie.
About OTA, I can do the update manually when a new update is released.
I forked your gitlab repository to keep up with the changes and try out some ideas.
Thank you so much!
You saved my life and my data privacy! XD
Click to expand...
Click to collapse
If you know how to use adb, all you need to do after installing boot.img is adb shell mount /data; adb push ubuntu.img /data/ubuntu.img in recovery instead of splitting android-rootfs.img and rootfs.img from ubuntu.img then adding them to the zip. Unlike other halium 9+ ubuntu touch ports, the port for s7 provides it's own vendor image and does not use a vendor partition at all, ubports_GSI_installer_v10.zip is very very incompatible here and would likely cause you to pair a halium 9 system.img with the android 11 vendor inside ubuntu.img if you did not update system.img with a halium 11 one
Also note that since ubuntu.img contains it's own vendor image, you can use any device native roms without a vendor partition in this dual boot use case, without treble converting the device
On the other hand, E is rather questionable in my opinion
While I really respect their phone refurbish business and they do bring relatively hassel free installation and beyond official LineageOS device support to the table, their OS is often a month to three months behind LineageOS security updates, the built-in app store ships playstore apps from a shady french apk mirror, ships closed source magic earth that they've been saying "it will be opened source" for years and it's still closed source now, forked multiple open source applications to serve as their core apps but does not have the man power to keep them updated timely after the initial rebrand (you can see them getting mutiple releases behind on their gitlab), and all they really did towards privacy was to use another time server for ntp and another web server for checking whether internet is up, rebrand bromite and change the default search engine to not be google
They did all that rebranding to make a less secure LineageOS release that had very insignificant "degoogle" changes just to market and bundle their nextcloud fork ecosystem
I suppose they are capable of improvement, I'm very happy to see that their k9 fork has been pretty close to upstream as of late; but then overall they still put more effort into rebranding opensource projects rather than contributing to upstream, and are not keeping up with core things like keeping up with LineageOS security updates, stopping their iOS minic launcher from breaking deep sleep keeping your phone warm in your pocket and overnight draining battery, keeping their rebranded bromite fork up-to-date (current official release) (e bundled version)
If you don't use ecloud and don't need microg in your android dual boot, I'd really recommend Ivan_Meler's LineageOS builds; if you need microg and find it too cumbersome to manually install microg as system app on top, I'd recommend checking out Exodusnick's LineageOS for microG builds

Nowadays my main focus is being on the privacy of my data...
It's been a very difficult and complicated search, initially I thought of using /E/ for the data filter they claim to have, but your considerations about application repositories sparked an alert, even though I don't use the custom to install applications from stores, I always prefer to manually download apks, but this practice of them really opens up the security holes
about /e/ wake lock issue on 0.17-q, I tested version 1.4-q in the official repository and didn't report this problem, on the contrary, I noticed excellent battery life with no battery drop for long periods.
I will take your considerations and recommendations into consideration and I will check those lineage builds you mentioned, I intend to use android only when necessary but with microg, and ubuntu on a daily basis, but even in the short period of use of android I want to maintain a certain level of privacy.
Thank you very much for your advice

cant install 20.04

lentas said:
cant install 20.04
Click to expand...
Click to collapse
I'm not sure what issue you are having, just tested the AppImage version of the installer on fedora linux and it works; it might be an issue with the ubports installer for windows
meanwhile, make sure you have drivers installed for adb and heimdall

katharinechui said:
I'm not sure what issue you are having, just tested the AppImage version of the installer on fedora linux and it works; it might be an issue with the ubports installer for windows
meanwhile, make sure you have drivers installed for adb and heimdall
Click to expand...
Click to collapse
it worked with using linux app, windows app is buggy

Development Paranoid Android Topaz Beta 1 - Redmi 9T

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We are very excited to announce the alpha/beta 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
-
Requirements
° Make sure you've latest Stable firmware flashed before flashing the ROM.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels are NOT supported unless 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
Fastboot Method
° Make sure your data is backed up
° Unlock your bootloader, and in bootloader mode follow the next command
° Fastboot -w (Wipes the entire device as well as userdata)
° Fastboot update aospa-topaz-beta-*-image.zip
° Reboot to system
Recovery Method
For Custom Recovery:
° Reboot to Recovery
° Wipe cache/ data/ *
° Install PA zip package
° Reboot to recovery
° Format data
° Reboot to system
Kernel source.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!

What is Offline Charger?

ShelbyHell said:
We are very excited to announce the alpha/beta 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
° DT2W
° Offline charger
Requirements
° Make sure you've latest Stable firmware flashed before flashing the ROM.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels are NOT supported unless 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
Fastboot Method
° Make sure your data is backed up
° Unlock your bootloader, and in bootloader mode follow the next command
° Fastboot -w (Wipes the entire device as well as userdata)
° Fastboot update aospa-topaz-beta-*-image.zip
° Reboot to system
Recovery Method
For Custom Recovery:
° Reboot to Recovery
° Wipe cache/ data/ *
° Install PA zip package
° Reboot to recovery
° Format data
° Reboot to system
Kernel source.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!
Click to expand...
Click to collapse
What is Offline Charger?

can i flash miui 12.5.8??? Or which one do you recommend globally?

Read comment below.

Nice rom. Flashed it on my friend's redmi 9t and me and my friend haven't noticed any issues. I used fastboot since most custom recoveries were broken.
Here are some issues and solutions I had(not the rom's fault, just inexperience):
Had to use the --force flag on fastboot since the codename was set to bengal and my friend's was lemon.
Had to install Google's adb and fastboot drivers(https://developer.android.com/studio/run/win-usb) due to windows not detecting fastbootd.
Very good rom and the only one I was able to flash.

can you tell me anything which was include on this rom?
any screenshot?
GApps is included or vanilla?

Prof.HB-69 said:
can you tell me anything which was include on this rom?
any screenshot?
GApps is included or vanilla?
Click to expand...
Click to collapse
GApps included.

howdy..
I'm currently running PixelOS based on Android 13, but it has some stupendously annoying issues, including:
screen randomly stops turning on - it vibrates on unlock with my fingerprint, but the screen never lights up. tapping the power button to "turn off the screen" and then unlocking with my fingerprint makes it vibrate again as expected, but the screen still doesn't light up. when this occurs, the "double tap to wake" feature also stops working... only workaround is to hold the power button for 10 seconds to force a reboot.
camera randomly opens when I tap the power button - it has a "short hold" shortcut (half a second? I think?) that launches the camera, but this seems to trigger sporadically when I don't expect it to.
custom launcher randomly thinks it's no longer configured - using Apex Launcher 4.9 pops up a message every day or two to say that it's not the default launcher, while it actually still is.. setting it as my launcher again or simply dismissinng the popup makes no difference at all, the same message will inevitably pop up again in a few days.
I see the "beta 2" changelog mentions "Fixed double tap to wake", which I suspect might be related to my first issue with PixelOS.
so before I go through the fun process of changing Android and setting up all my apps.. again.. has anybody experienced any sort of daily-driver deal breaker issues with Topaz?

ZaLiTHkA said:
howdy..
I'm currently running PixelOS based on Android 13, but it has some stupendously annoying issues, including:
screen randomly stops turning on - it vibrates on unlock with my fingerprint, but the screen never lights up. tapping the power button to "turn off the screen" and then unlocking with my fingerprint makes it vibrate again as expected, but the screen still doesn't light up. when this occurs, the "double tap to wake" feature also stops working... only workaround is to hold the power button for 10 seconds to force a reboot.
camera randomly opens when I tap the power button - it has a "short hold" shortcut (half a second? I think?) that launches the camera, but this seems to trigger sporadically when I don't expect it to.
custom launcher randomly thinks it's no longer configured - using Apex Launcher 4.9 pops up a message every day or two to say that it's not the default launcher, while it actually still is.. setting it as my launcher again or simply dismissinng the popup makes no difference at all, the same message will inevitably pop up again in a few days.
I see the "beta 2" changelog mentions "Fixed double tap to wake", which I suspect might be related to my first issue with PixelOS.
so before I go through the fun process of changing Android and setting up all my apps.. again.. has anybody experienced any sort of daily-driver deal breaker issues with Topaz?
Click to expand...
Click to collapse
No, there doesn't appear to be any daily-driver deal breaker issues with this. The only problem my friend had was no aod, which he solved with an app.

RicardosCameraman said:
No, there doesn't appear to be any daily-driver deal breaker issues with this. The only problem my friend had was no aod, which he solved with an app.
Click to expand...
Click to collapse
awesomeness.. thanks for the feedback. I don't really care much for AOD, so that's no issue for me.
guess it's time to refresh backups then.

Hi,
Where can i find advanced restart meniu (ex. boot te recovery) and dual SIM ringtone settings?
Thank you.

Is the included kernel good, I`m curious about kernel and average battery drain since support for custom kernels is limited. also , is offline charging fixed? thanks in advance

After a week of use I can say that I am very satisfied with this rom. Leaving aside the small shortcomings (it's beta though), offline charging is working, I recommend this build.
Thank you for this great rom.

diaconu.silviu said:
After a week of use I can say that I am very satisfied with this rom. Leaving aside the small shortcomings (it's beta though), offline charging is working, I recommend this build.
Thank you for this great rom.
Click to expand...
Click to collapse
any major or minor bugs?,And how is battery life?

Major bugs didn't find, minor advanced restart meniu (ex. boot te recovery) and dual SIM ringtone settings. Battery life, i can't say because i connect a lot my phone to pc (usb cable) also to my car (android auto). I can say with confidence that it lasts almost two days. No reboots, the phone does not freeze as I experienced with other roms.

Can I sideload it using pixelos recovery or pixel experience recovery?
Or what recovery do you prefer for this build

Abdulrahmantaha said:
any major or minor bugs?,And how is battery life?
Click to expand...
Click to collapse
I was not able to call and receive call in sim 2.

tedcm said:
I was not able to call and receive call in sim 2.
Click to expand...
Click to collapse
What recovery are you using sir?

I use twrp 3.6.2_12
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/lime/