yashsingh1/xdaforums huggingface dataset:
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
I have it working. Just install the apk.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Therazorsedge:
I've made it work!!!!!

For install gcam google photos must be installed

Thank you!!!!!
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] CyrilBritto:
Is substratum theme engine supported?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] NaYmaD123:
No it's not that, I changed it to 90hz coz my game runs at 90fps maximum and its runs better than it does on stock but the touch response time feels slower than it does on the same refresh rate on stock rom.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Not any better than stock
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Sure it is. Substratum can theme apps black, as opposed to the stock grey. So it does work, and it works BETTER than stock theme
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] NaYmaD123:
Ok so I tested the touchscreen problem a bit more and it feels like the minimum motion required to register the slide is too high. What i mean is that you need to swipe your finger way more for it to finally show it on the screen.

This setting was originally meant to help avoid accidental slides but here it feels too extreme.

I noticed that turning on "High touch sensitivity" option in display settings helps with "minimum motion" problem but at the same time it turns up the touch sensitivity itself wayyy high as its made to use while wearing gloves.

It would be great if there was an option to customize both touch sensitivity and minimum motion required to slide.

Its hard to explain but i tried my best :)
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] ralovesoc:
Hi , can you please provide a device tree? Thanks
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
LineageOS github,

android_device_asus_obiwan / android_device_asus_sm8250-common
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] ralovesoc:
LineageOS github, android_device_asus_obiwan / android_device_asus_sm8250-common

Thank you! Do you also know where i can find a kernel source and a vendor tree? I didn't see them on your github
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Kernel is still at LineageOS/android_kernel_asus_sm8250.

You can generate vendor.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] ralovesoc:
how can i "generate" the vendor?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Flash lineage

Boot and enable adb (and root debugging?)

cd device/asus/obiwan
./extract-files.sh

Or here's how you can do it locally instead of over adb https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] ralovesoc:
I don't have my ROG 3 yet , so i will try it locally. In the tutorial you sent me i see 3 variants : Block-based OTA, File-based OTA , and Payload-based OTA. Which one should i follow?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
My link points straight to Extracting proprietary blobs from payload-based OTAs

But it's also explained in the first paragraph
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
New build out

2020/12/18

Changelog:

Fixed tethering (wifi, usb and bluetooth)

Fixed LiveDisplay and Night Light

Removed Snap camera app in favour of Camera2:

Some Snap features were broken, and Camera2 is overall cleaner.

For advanced features I'm sure most people will prefer to just install GCam anyways!
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
IS volte fixed properly?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
No :/
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
You may also want to checkout LineageOS 18.1 here
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
I'll just use omnirom. That works properly. Thanks for your concern.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Thanks a lot aleasto for the wonderful ROM.

Just tried the ROM, Everything is working great. Never thought we will get live display working as some developers were telling it was not possible because of proprietary display software.

Some minor issues to report - Was not able to get adb working over usb.

Speakers was loud but had noticeable distortion at high volumes( On 18.1 didn't feel the distortion)

Haptic feedback on navigation gestures was too low/absent.

Thanks a ton again, Keep up the great work.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
You shouldn't have issues with adb...

Yeah the vibration hal is just quickly hacked in place, because in 18.1 we can use qualcomm's default new vibration hal.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] ralovesoc:
Hi , can you please link me the proprietary vendor? I can't find it anywhere on github. I tried extracting it but i failed
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
New build out

2020/12/23

Updated kernel and proprietary files to UL-ASUS_I003_1-ASUS-17.0823.2012.122-1.1.86-user

Fix log spam when using bluetooth audio

Make sure you update firmware to the same version, since it fixes VoLTE being lazy on automatic network selection.

You can grab it from here, and flash it in recovery to both slots:

flash recovery -> flash zip -> reboot fastboot -> reflash recovery -> flash zip

or flash it once, reboot, and use copy-partitions.zip like suggested for other a/b devices
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
New build out

Fixed video recording
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
New build out

Fingerprint implementation by OrdenKrieger
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Nice! is it working close to stock? Or still wonky?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
UI is meh, but functionality is on par
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Thanks. BTW, volte not working Tmo us.

EDIT, sorry it is, LTE only on radio setting. Bummer. Back to omni i go.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Idk, firmware .122 fixed it on my carrier
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Thanks anyway, went back to omnirom. BTW FOD worked very well.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] moslondon:
Are you a T-Mobile user? How did this rom work for you?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
I am. I only had VOLTE when LTE only was selected. If I selected anything else, no VOLTE. Other than that seemed ok. I was only on it for a few hours. FOD did work very good though!
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] moslondon:
What rom are you using now?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Omnirom10
[Android Apps and Games] smaug117:
‘ve been working on an android project that is supposed to help students writing learning and training from their device. If you are one, i need some feedback on what i have been working on so far.

it all came to me while I was taking an online course where I was struggling to take notes that makes sense to me all in one place. It was always a struggle, the best thing to do was to use a classic big old notebook but I couldn't always take it with me everywhere, So I decided to build an app that will help me take complex class notes. So far i manage to do all of those

- A n architecture for organizing notes.

- Markdowns styling

- LaTex ( for maths formulas )

- drag and reorder

- Images/gifs

- Quiz (to train before an View attachment 5147981View attachment 5147983exam)

- Text to Speech (to listen to note on repeat mode while i am standing on a bus doing nothing)

- Cards ( don’t really remember why i add this someone told me it will be cool )

- Light, dark mode

View attachment 5147985

- backup/restore

- Share your class notes with other people having the app (the one i like the most because i can share my class note and import what somebody else have written )

the last one i have added is the ability to import .md file

If you have idea or suggestions to help improve my app hit me, don’t feel shy

https://play.google.com/store/apps/details?id=com.neptunestudio.nott
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
I have an ASUS ZenFone Max Pro (X00T/X00TD)

It is/was discharged and powered off. When i plug it in for charging, it is cycling in start of chaging:

1. vibration

2. the icon of empty battery

3. The bootloader is unlocked... text

4. the icon of empty battery

5. empty screen

1. and then starts again from vibration

I tried to clean the phone's connector, even wiped and stracthed the connector a littlebit, and changed cable, charging source. (One cable is in the 1A charger, another cable is connected to PC.) It doesn't get better.

I tried to leave it in the cycling, i hoped it gets some power.

Does the phone charge always when connected to power, or it just start the charging process after it shows the charging animation (which i don't reach)?

I tried to step in Fastboot mode. It stays in this mode, no cycling.

Does the phone charge in fastboot mode?

I tried to step in Recovery mode.

1. vibration

2. powered by android

3. The bootloader is unlocked... text

4. powered by android

5. empty screen and turns off

In fastboot mode i tried to flash stock recovery, and also TWRP recovery. The flashing process works, but i still cannot get in recovery mode, to see something more, maybe about battery or i dont know.

Of course the phone does not turn on. The same as when i try to get in recovery mode.

1. vibration

2. powered by android

3. The bootloader is unlocked... text

4. powered by android

5. empty screen and turns off

I did not do anything special nowadays with the phone. Bootloader unlock and rooting was years ago, nor i did upgrade, so nothing special. I just used the phone, it discharged, and i'm in this state.

What can i do? Is it something with charging, or it has enough power after connected in fastboot mode, but the problem is something with the software?

Please help.
[Asus ZenFone Max Pro M1  Questions & Answers] blackhawk:
Was it discharged until it turned off or left more then a few weeks in a very low charge state?

Auto shutoff is about 5-6% of battery capacity.

If allowed to sit until it self discharges below 1% the battery's microprocessor will permanently disable the output to prevent a possible runaway thermal event from charging a depolarized LI cell(s).
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
It discharged today morning, turned off (or maybe i turned it off, i don't remember), and about one hour later i tried to charge.

Does it mean really permanently, without any possibility of get it back?

One more thing: maybe i "pressed" the buttons randomly in my pocket. Is it possible that in an unlucky situation i got into the recovery mode and pressed something away in recovery menu?
[Asus ZenFone Max Pro M1  Questions & Answers] blackhawk:
Even if discharge to the 6% cutoff you have at least a few weeks in cool temps until permanent auto shutdown.

It is permanent. If disassembled you could bypass the controller and attempt to charge.

Once the cell voltage reaches the controller threshold (if it takes a charge) it would function as before. Generally this is impractical to do.

If the cell has completely dipolarize it may not charge and will simply overheat with a potential thermal runaway if not manually disconnected.

Inspect port for debris, clean if needed.

Try a -known- good charger/wall socket and cable.

Normally phones will take a charge regardless of their power on/off state.

Otherwise the port, battery or the internal phone power control circuit may have failed.

A cable, charger, port failure are the most common causes though.

Best to use a 3 foot long cable; longer ones can cause charging issues.
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
It was definitely not a few weeks. :)

Sure, this was the first thing i checked. I also tried to carefully scratch off the possible oxid/dirt layer with a paper clip's end.

So should i try to leave it in the cycle? Or better leave it in the fastboot state?

Hm. But i tried to charge in fastboot state for a few hours.

I don't understand. :(

Yesterday with a third charger everything was fine. And this charger was fine, last time i used it two weeks ago. I tried to charge in my car now - the same cycling of starting to charge.

Okay, so i keep trying to charge, if you don't have better ideas.

But why does not it go into recovery mode? Maybe i could inspect the things more in recovery mode.

Thank you very much for your detailed answers.
[Asus ZenFone Max Pro M1  Questions & Answers] blackhawk:
If the battery is nearly fully discharged ie >5-6% and not recieving enough current or voltage from the cable, it will not power up even to its boot menu.
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
But it should start to charge without cycling, and show the charging animation, right? :unsure:

Edit #1: Ah, you mean, IF enough current. And if three different charger and cable was not enough for it, then probably the connector damaged. But i don't know how and why.

Edit #2: No, you mean this for booting up. But charging should start normally without the cycling. :rolleyes:
[Asus ZenFone Max Pro M1  Questions & Answers] blackhawk:
Your first concern is getting the battery to at least 60%

That's why you use a known good wall socket, cable and charger; a process of elimination.

I've had 2 bad power cables in a row before; more bad cables, etc. doesn't help.

For the boot issues someone here will hopefully recognize your problem if it persists.
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
Yes, i threw out a bad cable last week. But these 3 cables were good, there is not a big chance that all of them get wrong suddenly and at the same time, i think. I would be happy, because this would be the most easy solution for my problem.

In fastboot the red/green LED is dark, even if the cable is plugged in. Is this LED controlled directly also by the charging controller? Or does not the dark LED show anything, because it controlled by software, what does not run now, while the charging still work?

Or maybe both of charging start cycling and fastboot are use power of battery, while they don't charging it, so power is only getting lower? (Although you said the opposite, as phone is charging, not matter of the power state.)
[Asus ZenFone Max Pro M1  Questions & Answers] blackhawk:
Could be a bad batch if all are the same brand.

That's why you use a >known< good cable etc.

Don't have that phone so can't say how it behaves.

If it's below 5% power it won't do anything except maybe try to boot maybe not even that. Plus each attempt drains the battery more towards that critical 1% auto disable in the Li pack.

Killing the battery won't help your cause...
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
Okay, i try.

Thank you very much for your help.
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
Is it possible to turn off the charging screen, charging vibration, screen turning on from fastboot mode? Maybe flash something on or similar?

Because then it won't use the slowly chagring power.
[Asus ZenFone Max Pro M1  Questions & Answers] blackhawk:
So the screen is active abnormally when it's charging?

Is it stuck in a boot loop?

I know zero about rooting and firmware flashing.

Eventually someone here with that knowledge will step up... be patient.
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
1. I plug the cable in.

2. It recognize there is power, so vibrates a littlebit, then starts to charge OR starts to start to charge - it would be in important thing to know which.

3. It shows the big battery icon at the center of the screen.

4. It notices its boot loader is unlocked, so it warns me - i can pause the phone for one minute in this step.

5. It shows the big battery icon at the center of the screen for a second.

6. But i think it feels its battery is too low, so it turns itself off, even from the charging process.

2. Then it feels the power again, so the cycle starts again and again...

In step 2., if i would know it is already charging itself, then i played with it, i pause every time for a minute, and everytime the battery gets a little more power. Because every vibrate and starting charging take a littlebit power from the battery i think.

So, for example, in every unpaused charge cycle (about 10 seconds) it gets 5 mAh, but uses 7mAh from the battery, then it get worse and worse. But if i pause it for a minute, it gets 30mAh, uses 7mAh, then every minute it gets 23mAh more, so this game eventually worths.

But, if in step 2. it does not start to charge itself, just later, after the "unlocked" text, then playing with this does not help, worse, take the battery lower and lower.

But: if i could disable the charging screen and the vibration, then it won't use the power just for showing to me it charges. And maybe the screen is the one who use the power and makes the controller feel low power from battery/cable.

Or, maybe, charging is already disabled, so no matter what i do, it does not help, and the only solution is to take apart and charge the battery directly.

I just put

Okay i try to be patient. :)
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
Good news!

This gets the voltage of the battery:

fastboot getvar battery-voltage

It says it's 4,32 V. If i remember right, this is around a fully charged battery. So probably it charged up when i left in Fastboot state for some hours. And the cycle/loop meant not that it cannot charge, but rather it does not need to charge.

Bad news!

Then what the heck is with my phone? :oops:

Summary:

1. My phone is fully charged.

2. It does not boot into normal.

3. It does not boot into recovery, nor by hardware keys, nor by command from fastboot. I tried to flash TWRP, RedWolf and the original recovery too.

4. Fastboot mode works normally.
[Asus ZenFone Max Pro M1  Questions & Answers] trob83:
Believe it or not...

The solution was very stupid.

I cleaned the phone inside, especially the bottom part. Around the connectors, lot of dirt and drying moisture got in. Just enough for - probably - some short circuit.

I don't know why was it okay for fastboot mode, and not okay for recovery and normal boot.

Blackhawk, Thank you soooooo much for your help and your time. I learned a lot from you now.
[Asus ZenFone Max Pro M1  Questions & Answers] blackhawk:
Excellent.

Guess it was getting mixed signals...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] liamwhite:
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. This is a straightforward port of the device tree for flame (Pixel 4) to sunfish (Pixel 4a).

Downloads:

sunfish (Pixel 4a) rom (v2): https://mega.nz/file/zG4UVTQB#ZXLw_qULzC8-an-MEdxdAvUMhmIa5qLI6YG54Feh2z0

410b3f523795d9d1481d183309adb170 lineage_sunfish-qd3a.200805.001-rel-v2.zip

sunfish (Pixel 4a) rom (v1, broken, do not install): https://mega.nz/file/jXRB2a4B#a5Dcf9T6emWAwvAj3oFvofkI0la0zf7vj5KIMn-yQaM

MD5: 86743134c3032a030d35195d44f02e1b lineage_sunfish-qq3a.200805.001.zip

This is not a recovery-installable zip! Please read below for how to install this image

Prerequisites:

Like the TWRP build for this device, this ROM build is only known to be compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.

Instructions:

1. Flash the vbmeta.img file in the included zip (fastboot flash vbmeta vbmeta.img)

2. Reboot into fastbootd (fastboot reboot fastboot)

3. Run fastboot update -w lineage_sunfish-qd3a.200805.001-v2.zip

(If you do not have a working fastbootd, extract boot.img from the update zip and flash it from the bootloader first)

Working:

- Camera

- Fingerprint

- Wi-Fi

- Bluetooth

- Sound

- Mobile data (tested with T-Mobile only)

Not tested:

- Google apps (should work fine, but you never know)

Changelog/Source Code:

sunfish device tree: https://github.com/liamwhite/android_device_google_sunfish

sunfish kernel tree: https://github.com/liamwhite/android_kernel_google_sunfish

Credits:

Many thanks to all LineageOS team members and all the contributors out there in the community.

Android version: 10

Kernel version: 4.14.117
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?

just asking because that's how I flashed a lineage test build.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] posıtıve:
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] liamwhite:
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.

The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] liamwhite:
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.

I added a MD5 of the zip image I flashed to the OP.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
I'm sure it's not broken. Probably a issue with my phone. I'm getting a error in the bootloader about debug policy enabled, not in list. I know that's not normal because my wife has the same phone and hers doesn't say that. And I have no idea what or how to change verity. My bootloader is unlocked.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nixromancer:
Same error here, getting corrupt error then it sticks to google logo
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] liamwhite:
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.

Board: sunfish MP1.0(NA)

Bootloader: s5-0.2-6539975

Baseband: g7150-00018-200701-B-6643937

Secure boot: PRODUCTION

NOS production: yes
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
any idea how to check if verity is enforcing and how to change it. Did a search, can't find anything.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] liamwhite:
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.