yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] nguyenlucky:
I just checked Samfirm and for A13, EUX and EGY belong to different multiCSC (OXM and OJM)

So it makes sense that u need to flash EGY firmware first to change from OXM to OJM

In his case, all Korean CSCs, including unlocked KOO, belong to OKR multiCSC, and I heard that Samsung specifically blocked CSC changes with Samfw and Samkey in newer phones (S21/S22 etc) for Korea (N model).

:/
[Google Pixel 5a] CustomOShacks:
I was wondering if anyone can help me I recently bought a pixel 5a that came pre installed with a custom version of android 11 now this rom that they put is very annoying as it blocks many thing for example installing apk’s now that wouldn’t be so bad if I was able to use adb to get the apps that I want on the phone but their software restricts developer options

View attachment 5699603

so I have no way of enabling usb debugging so I can’t use adb all of this has caused me to want to flash stock android back onto my phone the only problem with that is that the bootloader is locked so does anyone know any way how to unlock the bootloader without enabling usb debugging and oem unlocking or at least how to unlock developer mode
[Google Pixel 5a] zpunout:
Which custom OS is installed?

I remember reading a similar thread about a Pixel4a someone bought which had ArcaneOS installed. I think the solution was to remotely unlock the bootloader using the Google Pixel website's restore function. Be careful if you choose to restore your phone to the latest Android 13 though because you won't be able to roll back to Android 12 anymore.

This link might lead you to the solution you are looking for https://www.xda-developers.com/fbi-backdoor-pixel-arcaneos-anom/
[Google Pixel 5a] CustomOShacks:
It’s called kosherOS
[Google Pixel 5a] CustomOShacks:
Do you have a solution?
[Google Pixel 5a] CustomOShacks:
It doesn’t give a solution
[Google Pixel 5a] zpunout:
Sorry, the link to the forum thread was on the news article, but I forgot to mention that. I'll put it here: https://xdaforums.com/t/is-it-bricked-cannot-flash-stock-android-to-remove-arcaneos.4285827/
[General Questions and Answers] blaze73:
Hi there,

I need some help or advice. I have upgrade to A13 some days ago and apart from the crazy battery drain with "Phone Idle" and "Mobile Networks" I am facing a weird Viber drain which never occured before :

Shows and 20-30% battery consumation with 15-25 hours "alive" and only 2-3 minutes in background.

Ofcourse this is nonsense the real usage is the 2-3 minutes and not the 15-25 hours :(

I have wiped cache , and done a uninstall re-install but nothing happens.

Viber is the no.1 battery consumer in the app list.

Any advice,guys?

I am already very disappointed with the A13 drain with "Phone Idle" and now this Viber issue comes up :( Heeeeelp !
[General Questions and Answers] ibanezman192:
Why are you reporting a viber bug here?
[General Questions and Answers] vasilisG13:
He's reporting it here because its a13 problem on our device not vibers.i have p6p and i have the same bug. does anybody have a solution?
[General Questions and Answers] vandyman:
This does not have anything to do with the P6.

It is an app issue and needs to be reported to the developer of the app.
[General Questions and Answers] ibanezman192:
Exactly. It's a well known problem with the latest version of Viber across many devices. So stop spamming irrelevant stuff to Pixel 6, or else.
[General Questions and Answers] blaze73:
How come it only showed up after A13 uprade? On A12 Viber was normal, with A13 its a mess with massive drain :(

You cant be serious this is not A13 related..... :(
[General Questions and Answers] tom1807:
Because Viber app is maybe not updated to support A13.

Several apps need an update to work under A13.

In my case, DJI Mimo needed an update to v1.7.26, after that it started correctly.

Cheers

Tom
[General Questions and Answers] blaze73:
I see this is a bummer. However I feel that this is more like a Google issue not Viber's fault but we will see. My battery life

is tragic, worst ever in my 10+ years smart phone usage... :(
[General Questions and Answers] tom1807:
Looks like your feeling is not shared with the moderators, it was moved to general.

Beside that, maybe check Google whether others reported the same problem and maybe offer workarounds.

Cheers
[General Questions and Answers] blaze73:
I tried to check but could not find any workaround so far and this is very annoying that it is the main consumer. (APP)

Top drainer it is, next to "Phone Idle" I have been trying to find a workaround but none so far or I have been bad with searching... :(
[General Questions and Answers] tom1807:
Look into this topic, the section "RECOMMENDED AFTER UPDATE". The first 3 items could help, but you should be familiar with "platform-sdk-tools" and ADB commands (also how to open a command prompt in Windows).

Cheers

Tom
[General Questions and Answers] blaze73:
I did some of the settings and no, I am not familar with "platform-sdk-tools" and ADB commands.

I am a regular user not a tweaker. Unfortunately nothing has changed. Phone ide is 35% in 8 hours in flight mode

and Viber is still top consumer APP :( Insane ! I am really fed up with this A13. Battery cant even last 24 hours

using flight mode for the night. :( : (
[General Questions and Answers] tom1807:
Maybe you should explain what you did?

Cheers
[General Questions and Answers] blaze73:
The recommended "DISABLE" bits and parts. Did not really help. Still heavy battery drain and Viber is no.1 consumer APP-wise otherwise its "Phone Idle" 30-35% :(
[General Questions and Answers] tom1807:
No, I specifically said the 3 commands written in "RECOMMENDED AFTER UPDATE". The others may help, but not for ur problem.

One command specifically deals wit re-compiling all the apps which could help with overheating and battery drain.

The other one deals with battery drain.

"Disable" bit and parts could cripple your phone if you don't know what they exactly do.

And don't focus on how much 30-35% for Phone idle writes.

If your phone used for example 10% battery, the 30% of these 10% were drained, but not 30% of the battery.

Cheers
[General Questions and Answers] blaze73:
Alright. Can you tell me what to do and how to do with these 3 commands? I will perform but I would need some step-by-step help if possible :)
[General Questions and Answers] tom1807:
Enable USB debugging on your mobile. Download the platform-sdk-tools and unzip to a directory.

Connect your mobile to a PC, and open a command prompt.

Type adb devices, authorize the connection on the mobile and then type the commands.

All this can be easily found, here on XDA and internet.

Cheers
[General Questions and Answers] blaze73:
Great. Many thanks, man. I will wait for the september patch if nothing happens I will do these steps.

Viber is still no.1. consumer staying on top with 25% consumation with bogus data :(

Phone Idle is 35% with 18-20hours standby which is insane. This A13 update was a catastrophe in terms of battery life :(
[General Questions and Answers] tom1807:
Google won't fix Viber. That's a Viber problem.

So far Viber is developed up to API 30, Android 13 is API 33.

Cheers
[General Questions and Answers] blaze73:
Good to know that. (API 33) I have sent a report , trouble ticket to Viber support.

Hope it will be dealt with.
[General Questions and Answers] blaze73:
I have completely deleted Viber from Pixel 6 and the battery drain is gone.

In the meantime I reported to Viber suppor that this might be caused that

Viber is developed up to API 30 only, Android 13 is API 33.

After uninstalling Viber the phone in flight mode lost only 4% of charge instead of the previous nights' 30-36%
[General Questions and Answers] blaze73:
Guys, the battery drain is not completely gone. I still have some grey system file (?) in the logs

Cant find it when looking for this fine not even if system files are selected ?

Any idea how to remove this for good?

Thanks !
[Sony Xperia 1 Questions & Answers] Shrihari1428:
Hi All,

Currently I render the video frames using extensions(OpenGL to render the frames) with exoplayer. I have noticed that when playing videos natively the max brightness achieved is around 1000 nits. But when I render the frames using extensions I get only around 600 nits. Is there any method or setting required to achieve the max brightness?

Thanking you in prior!
[Shield Android TV Q&A, Help & Troubleshooting] k3npachi:
Hello, since a few days I have a message on the home page that tells me that my storage is full

I only have 12 applications installed for a total of 2.5gb, I emptied the cache of applications, but I have only 350mb of space left

So I have slowdowns and I can't install new apps

Any solution apart from resetting everything?

EDIT : since a while I lost 150mo I have only 200mo free even by emptying the cache, there is a problem

EDIT 2 : I lost another 50mo and nothing in the cache
[Shield Android TV Q&A, Help & Troubleshooting] ajokay:
Hi,

Had the same problem here. Deleting apps didnt help either.

Storage kept telling me i had several gigs of apps installed although i deleted everything.

I just now did a factory reset and space was recovered. fingers crossed.

I did all updates again abd instalkled all poreviously installed apps.

Also im on the beta firmware from Nvidia.

My thoughts are somewhere a program update messed things up ealier.

greets,

AJ
[Shield Android TV Q&A, Help & Troubleshooting] k3npachi:
ok thanks, I think I'll have no choice but to do a reset
[Shield Android TV Q&A, Help & Troubleshooting] ajokay:
Still working here after the reset.

I think somewhere a program upodate messed something up earlier.
[Shield Android TV Q&A, Help & Troubleshooting] Alekos:
I made a post about this on reddit. 2017 shield, no Plex/Kodi etc. Started happening after the 9.0.1 update in May. Internal storage just slowly disappears (from 10 GB available/free to 150 mb). Factory reset is the only workaround - and yes I have checked every app including system apps, gallery, media, system upgrade apps etc etc. And this happens even If I use adoptable storage (which I don't need since my apps only consume about 0.93 GB and I don't need much free space - but this bug is horrible.

There are a few posts on reddit and a developer from nVidia that is interested in logs. Here is the most recent post.
[Asus Zenfone 9] tbalden:
Readme's and howtos
[Asus Zenfone 9] tbalden:
Changelogs come here later
[Asus Zenfone 9] tbalden:
Be aware that in Battery Saver feature, there's CURRENTLY NO CAMERA APP FOREGROUND DETECTION! Please disable this feature when you use Camera apps (otherwise slow camera, video recording)!

Hopefully camera detection can come later, as still working on more features.
[Asus Zenfone 9] Freak07:
nice work! :)

great to see you here :)
[Asus Zenfone 9] SpursM:
Great develop (y)
[Asus Zenfone 9] Veiranx:
Thanks for sharing! If I have the patience to get the C version when it eventually releases, I'll give this kernel a try!
[Asus Zenfone 9] tbalden:
- Update Android 12 Stable - 1.4.0 -

Major CleanSlate feature update

​

- Build and repack to QGKI2 kernel format (boot, vendor_boot, vendor_dlkm, dtbo images) with new scripts

--- Thanks go to @Freak07 for the teamwork of many hours in getting to the bottom of this crooked path to build Qualcomm's new modular kernel format and make it work on the ZenFone 9

--- Thanks go to ASUS for providing the most complete sources zip for Qualcomm based QGKI kernels up to date by ANY vendor/OEM.

--- Thanks go to @osm0sis for his AK3 installer and @capntrips for his excellent tooling in AK3 and the tips help he lended in the process of getting things rolling

- Now all features possible to implement added to drivers

-- New:

---- Flashlight notifications

---- Vibrating Notifications reminder

---- Gestures Features: Sweep/Tap in corner gestures added

---- Fingerpint customization added:

----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper

----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)

---- Double Vibration feature on Phone Calls in DND or Silent mode

-- Updates

-- Hosts file for KAdaway

-- Safetynet + Play integrity still passes without Magisk

-- All features work with or without Magisk (tho flashing magisk will break safetynet until you use SafetyNet fix magisk modules)

Two types of installation methods provided.

- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)

- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.

CleanSlate S 1.4.0 Downloads:

Rooted installer zip:

CleanSlate S 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820728

Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2030.2030.26)

fastboot image zip CS 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820729

Cleanslate config app version 3.2.11 needed for new features:

Free version download: https://www.androidfilehost.com/?fid=14871746926876820727

Premium version: https://play.google.com/store/apps/details?id=org.cleanslate.csconfig&hl=hu&gl=US

- rolled out to playstore Beta program

Read first post in thread for installation details.
[Asus Zenfone 9] NisseGurra:
Will it run with the latest fw update?
[Asus Zenfone 9] tbalden:
It actually runs, but new sources are up, and I'm updating the installers soon.
[Asus Zenfone 9] tbalden:
- Update Android 12 Stable - 1.4.1 -​

CleanSlate asus sources update

-- sources updated to 2040.23

-- Hosts file for KAdaway

Two types of installation methods provided.

- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)

- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.

CleanSlate S 1.4.1 Downloads:

Rooted installer zip:

CleanSlate S 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834460

Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2040.2040.23)

fastboot image zip CS 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834462

Read first post in thread for installation details.
[Asus Zenfone 9] NisseGurra:
Installed, seems flawless :)
[Asus Zenfone 9] tbalden:
2040.28 update is up, with sources. The new sources has no changes, tested, I'm using the .23 based cs kernel without issues.
[Asus Zenfone 9] tbalden:
- Update Android 12 Stable - 1.4.2 -​

CleanSlate asus sources update

-- sources updated to 2050.29

-- Hosts file for KAdaway

Two types of installation methods provided.

- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)

- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.

CleanSlate S 1.4.2 Downloads:

Rooted installer zip:

CleanSlate S 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957

Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2050.2050.29)

fastboot image zip CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958

Read first post in thread for installation details.
[Asus Zenfone 9] Kylewolf:
Is there any way to add vowifi or volte without rooting with a kernel like this?
[Asus Zenfone 9] Ben-cuisse:
Hello,

I recently buy this phone and wanted to increase the battery life of this phone.

This seem to be an good option, but have you information about battery life with this kernel ?

Thanks you.
[Asus Zenfone 9] dragonii:
Hi,

I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.

Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :

Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')

Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.

Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.

After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).

The kernel version is 5.10.81-cleanstate-100-android12-9.

So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?

Thanks in advance,
[Asus Zenfone 9] tbalden:
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.

Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.

The commands to do are:

adb reboot-bootloader
fastboot flash boot full_img/boot.img

fastboot flash vendor_boot full_img/vendor_boot.img

fastboot flash dtbo full_img/dtbo.img

fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img

fastboot reboot
[Asus Zenfone 9] dragonii:
So, according to you, I should just take the latest zip file and run the commands in fastboot mode even if I flashed already the cleanstate img file in the first post?

EDIT: did it already and no more error messages with version 1.4.2. Thanks !
[Asus Zenfone 9] dragonii:
Hi again,

How can I access these features? There are not showing up in the CleanSlate Configuration tool.

-- New:

---- Flashlight notifications

---- Vibrating Notifications reminder

---- Gestures Features: Sweep/Tap in corner gestures added

---- Fingerpint customization added:

----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper

----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)

---- Double Vibration feature on Phone Calls in DND or Silent mode

Thanks in advance,
[Asus Zenfone 9] tbalden:
First question, which version does it show on the Info page in the app? It should be 3.2.x in the Config app, and 3.3.x in the companion app for this device.

If you're using the apps from the play store and it's not these versions then you should join the Beta program for both apps to get the right version.

If the version is ok, can you please share a screenshot from the config app, what can you see?

EDIT: In the meantime I noticed that the proper version was only posted once at 1.4.0:

Cleanslate config app version 3.2.11 needed for new features:

Free version download: https://www.androidfilehost.com/?fid=14871746926876820727

This app version should do the trick :)
[Asus Zenfone 9] dragonii:
Here's what I see
[Asus Zenfone 9] tbalden:
Cleanslate config app version 3.2.11 needed for new features:

Free version download: https://www.androidfilehost.com/?fid=14871746926876820727

This app version should do the trick :)
[Asus Zenfone 9] dragonii:
Yes, thanks a lot!
[Asus Zenfone 9] tbalden:
Latest update 2050.2050.34 is up for zf9.

Kernel sources didn't change, so latest cleanslate should work fine with it.
[Asus Zenfone 9] tbalden:
- Update Android 13 Stable - 2.4.0 -

View attachment 5784181
​

CleanSlate asus sources update

-- sources updated to 2060.65

-- Hosts file updated for KAdaway

Two types of installation methods provided.

- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)

- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.

CleanSlate S 2.4.0 Downloads:

Rooted installer zip:

CleanSlate S 2.4.0: https://xdaforums.com/attachments/cleanslate_s_zf9_240-zip.5784179/

Non rooted, Android S images for fastboot based flashing (firmware wwe 33.2060.2060.65)

fastboot image zip CS 2.4.0 https://xdaforums.com/attachments/fastboot_cleanslate_s_zf9_240_imgs-zip.5784177/

Read first post in thread for installation details.
[Asus Zenfone 9] Ax1qwer:
Hi, is somehow possible to use the LED, which is in the top right corner as notification LED? It seems it is only working as camera indicator. Thanks.
[Asus Zenfone 9] Hermann2306:
I would say there is no LED. Just a painted dot on the screen.
[Asus Zenfone 9] tbalden:
- Update Android 13 Stable - 2.4.1 -
​

CleanSlate asus sources update

-- Common kernel image updated to 5.10.136 from Google's sources

-- sources updated to 2060.100

-- February sec level

-- Hosts file updated for KAdaway

Two types of installation methods provided.

- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)

- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.

- This kernel (modular) is not working with TWRP, and shouldn't be flashed when you use TWRP. If a modular custom kernel is flashed with TWRP being used, it will render your phone non bootable until you restore to stock partitions.

CleanSlate T 2.4.1 Downloads:

Rooted installer zip:

CleanSlate T 2.4.1: https://xdaforums.com/attachments/cleanslate_s_zf9_241-zip.5850313/

Non rooted, Android T images for fastboot based flashing (firmware wwe 33.2060.2060.65)

fastboot image zip CS 2.4.1 https://xdaforums.com/attachments/fastboot_cleanslate_s_zf9_241_imgs-zip.5850319/

Read first post in thread for installation details.