yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
Don't think stock Android Q firmware is available for this device. If available then you've to use SP Flash Tool in order to install it.
[Google Pixel 3a XL Questions & Answers] hga89:
Is the battery replaceable on the Pixel 3a and/or Pixel 3a XL?
[Google Pixel 3a XL Questions & Answers] ritchea:
Not like the old phones, but take a look. The XL is said to be a bit easier than the smaller. We've replaced batteries on Nexus 5 (quite easy) and on Nexus 6P (not so easy due to camera glass).
[Google Pixel 3a XL Questions & Answers] hga89:
Thank you, that was helpful!
[Galaxy Tab S Q&A, Help & Troubleshooting] jackald2:
I ma trying to install Firmware SM-T700 — Samsung GALAXY TabS OS Version 6.0.1.

I am using Odin and XEF-T700XXU1CRF1-20180911092613 stock firmware.

Odin Pass successfully. But when it starts it stuck on "Installing applications"

Any ideas?
[Galaxy Tab S Q&A, Help & Troubleshooting] rsfinsrq:
Have you tried factory reset from recovery?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
[IMG="rrlogo"]https://resurrectionremix.com/assets/rrlogo.png[/IMG]

Resurrection Remix P

[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]

[IMG="rrabout"]https://resurrectionremix.com/assets/rrabout.png[/IMG]

Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome

combination of performance, customization, power and the most new features, brought directly to your Device.

Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!

Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.

​

[IMG="rrinstall"]https://resurrectionremix.com/assets/rrinstall.png[/IMG]

Make sure you have a custom recovery installed (TWRP is the preferred recovery) and you use Pixel factory images of April or March

Download the latest Resurrection Remix Rom & the latest GApps package

Boot into recovery

FORMAT data and wipe/system and dalvik's/ART cache as a precaution

Flash ResurrectionRemix Rom

Flash TWRP.zip

In TWRP main menu, select reboot, then recovery (this will reboot you into the other slot)

Flash Google Apps package(Optional)

Flash Magisk Root(Optional)

First boot may take up to 10 minutes.

[IMG="rrdownload"]https://resurrectionremix.com/assets/rrdownload.png[/IMG]

ROM Download

GApps

[IMG="rrsource"]https://resurrectionremix.com/assets/rrsource.png[/IMG]

Resurrection Remix Source

Device Source

Kernel Source

Vendor Source

[IMG="rrthanks"]https://resurrectionremix.com/assets/rrthanks.png[/IMG]

XDA Developers

LineageOs Team

Omni Team

And Of Course To All The Supporters, Donators And Users

[IMG="rrbugs"]https://resurrectionremix.com/assets/rrbugs.png[/IMG]

If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.

Download the

MatLog

app from the Play Store.

After downloading the MatLog app, go to the app settings, and change the log level to Debug.

Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.

Copy and paste the entire log either to

Hastebin

or

Pastebin

Save the log, and copy and paste the link into the thread with a brief description of the error.​

[IMG="rrsocial"]https://resurrectionremix.com/assets/rrsocial.png[/IMG]

​
[Google Pixel ROMs, Kernels, Recoveries, & Other De] natsousa:
I cannot get this boot. Coming from newly installed Pixel Factory images of May.

- Boot into 3.2.0.0

- Format Data, wipe system, cache

- Flash ROM

-Flash TWRP 3.2.0.0 zip

- Reboot

Boots back into TWRP

I want to use Microg so did not install gapps or magisk
[Google Pixel ROMs, Kernels, Recoveries, & Other De] lhn7339:
every time reboot to TWRP

only flash rom and twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
RR PIE ON SAILFISH

N U T

Downloading and flashing right away!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
Try with Pixel Factory images of April or March (I updated the step for flash) and I don't think MicroG is supported in Resurrection Remix OS and I said to wipe dalvik's/ART cache not cache (A/B partition don't use cache partition)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] lhn7339:
I try use april image but still reboot into twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
Try with march image
[Google Pixel ROMs, Kernels, Recoveries, & Other De] lhn7339:
still not
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
Hmm, I try to flash magisk and did you reboot to recovery after flash ROM and TWRP.zip ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] lhn7339:
the step is

flash rom

flash twrp.zip

reboot to rec

reboot system

then always into twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] natsousa:
I tried

- wipe

- flash rom and twrp zip

-reboot TWRP

-Flash open gapps

and still end up in a bootloop to TWRP. I have not tried with Magisk but I can't imaging that should be required.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ziauddin_Sameer:
don't install magisk after installing gapps package, flash magisk after first boot :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] lhn7339:
I install only rom and twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sohip:
It didn't work for my either.

I flashed RR + TWRP 3.3.0.0

Reboot to recovery

Flash Magisk 19.2

Reboot Device

Device show RR Logo but after a few minutes sends me back to Recovery.

I tried again and made sure to wipe System/Art/Data but still end up with the same result.

I went back to Lineage for now, but I'm still following...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
Anyone can give me a logcat when device boot please ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] natsousa:
I'm not experienced with this stuff but are I got these from sys/fs/pstore after bootloop

dl=0http://www.dropbox.com/s/i4xsd2a9nvy80br/pmsg-ramoops-0?dl=0

https://www.dropbox.com/s/qlv42mm3h1t2mqf/console-ramoops?dl=0
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
Anyone can try this:

(Use latest pixel factory image like official lineageOS 16.0)

Reboot to TWRP, flash ROM and TWRP installer, reboot to recovery, mount vendor and delete vendor/overlay folder in TWRP file manager, flash Gapps or Magisk and reboot system
[Google Pixel ROMs, Kernels, Recoveries, & Other De] natsousa:
I tried

- flash factory May Images

- wipe system, data, dalvik cache

- flash lineage 16 and twrp

- Reboot

- Boot to TWRP

- Flash RR and TWRP

- Reboot TWRP

- Mount vendor and delete vendor/overlay

- Flash pico gapps

- Reboot

and now stuck in bootloop
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
Why you flash lineage 16 ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GuestK00355:
Try this [MENTION=7669286]natsousa[/MENTION]

- flash factory May Images

- wipe system, data, dalvik cache

- Flash RR and TWRP

- Reboot TWRP

- Mount vendor and delete vendor/overlay

- Flash pico gapps

- Reboot
[Google Pixel ROMs, Kernels, Recoveries, & Other De] natsousa:
[MENTION=9666565]Neverhopless[/MENTION]

I did what you suggested but after many minutes of the RR boot animation, I get sent back to TWRP

Do you want logs?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Yes
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
How does one fetch logs for these boot-loopy situations?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] honeybear81:
Has anyone been able to get this to boot? I triedand got the same results as the other posters. Boot animation shows for awhile and then reboots into twrp. Tried multiple times and followed all suggestions.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
Same. I wanna help with logs but idk how to fetch logs of bootloops
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Arju:
Did you include vendor in your build? If you do any it's still not booting then it might be a permission thing. What someone could test is to flash your ROM and then flash debug.zip to see if it boots. https://drive.google.com/file/d/1nM_Jbz9RtcJ1ITcXEWdFnmYB8XxE9Cj-/view it should boot after that. Credit is not mine, saw user shagbag913 posted it sometime in a chat.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] honeybear81:
That works.

Wiped

Flashed ROM

Flashed TWRP

Rebooted Recovery

Flashed GApps

Flashed Debug

So far so good. Just installed but everything seems to be working.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
EDIT: ROM installs and boots into setup fine. I can't get past "Set up a WiFi network" screen. It connects, says "installing updates" then returns to wifi screen. Force connecting to a network a few times results in a black screen. Only option at that point is to restart phone.

Skipping Wifi setup doesn't work either, and also results in the black screen.

Flashed in latest GApps, Pico package from OpenGapps.

Post with location of debug.zip file
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Arju:
Got it from a chat and I'm not going to post that channel here, respecting the founders. I'll tag the devs who might know though.

[MENTION=8680413]shagbag913[/MENTION] [MENTION=4517290]stebomurkn420[/MENTION] Does any of you know where the debug.zip comes from?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
Followup from my previous post. Tried this:

- Wipe

- Flash RR

- Flash TWRP

- Reboot into Recovery

- Mount vendor

- Delete /vendor/overlay

- Flash Pico GApps

- Flash debug.zip

- Reboot

Device boots into setup but the same issue of being unable to get past "Connect to Wi-Fi" is present.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Arju:
Not sure what it could be but try different gapps provider. Try mind the gapps: https://androidfilehost.com/?fid=1395089523397894328
[Google Pixel ROMs, Kernels, Recoveries, & Other De] stebomurkn420:
Shagbag made it... Lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=9666565]Neverhopless[/MENTION] all that debug zip does is put priv-app permissions on logging mode, so you're missing some critical permission that is breaking boot. To find the permission(s) you're missing, run this script that's included in aosp to find the missing permissions after building the rom:

./development/tools/privapp_permissions/privapp_permissions.py

Give it a second and it will output what's missing. You can add the permissions to your device tree in permissions/privapp-permissions-marlin.xml.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] honeybear81:
I had the issue your having at the wifi step as well. I've encountered similar on other roms. I used mindthegapps instead of open gapps and it fixed it. I would try that. Same steps just swap the opengapps for mindthegapps

http://downloads.codefi.re/jdcteam/javelinanddart/gapps
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
- Wipe

- Flash RR

- Flash TWRP

- Reboot TWRP

- Flash MindTheGapps

- Flash debug.zip

- Reboot system

(optional but I did it before I forgot)

- Reboot TWRP after successful boot

- Flash Magisk 19.2

- Reboot system

First system boot was lightning fast - vs the time it took when flashing OpenGapps - AND I GOT PAST THE WIFI SCREEN!! I'm continuing setup; will report as I proceed.

Edit: Setup completed without issues! I had an initial "Android setup has stopped working" after the very first screen to which I force closed it but setup resumed as normal.

EDIT 2: Whenever there is a reboot, phone is stuck on "Phone is starting." Clearing Dalvik/cache through TWRP fixes the issue, but it means having to remove any sort of screen lock because otherwise recovery cannot be accessed, meaning it is a tedious process to remove lock, reboot, wipe cache, reboot, reapply pin and fingerprints on every boot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Sorry if I'm missing something obvious, but why are you unable to decrypt with phone PIN in TWRP?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
If you have a pin set up, then it asks for a password to decrypt on TWRP. It isn't the PIN tho. I tried. lol

Only way I know to get around it is to disable screen lock entirely prior to rebooting to recovery
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Weird. I'm on a different Pie rom and have TWRP 3.2.3-1 and it decrypts with my PIN just fine. I feel like I may have run into this in the past once and for some reason think back then it had something to do with scrambling the numpad on the lock screen? But that doesn't really make sense because I use the scramble now and am obviously not having the issue.

Quick searches bring up things about remnants of old lock settings maybe getting in the way. Long shot, but is there any way you disabled require PIN on boot (is that even a thing?) and that that could be confusing TWRP?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
I remember having tried the PIN on TWRP and it didn't work. I'll give it a shot again when the phone reboots.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] gbfdtx:
all i did was flash the debug.zip after if rebooted into twrp and its seems to work fine. no hangup at the wifi menu or anything...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
Post your steps, please.

___

Edit to avoid double posting: Clearing Dalvik before rebooting does not solve "phone is starting" lock. I tried doing if before the first reboot and it didn't help. I restarted it then without clearing Dalvik and the phone boots without issues.

Also, huge kudos. I tried putting in PIN into TWRP and it worked. I swear that I did this while on a different rom and it failed. Huh. TIL. thank you!!

___

Edit 2: Phone was bricked and would not get past Phone is starting no matter what I did. I wanna attribute it to MindTheGapps as I had that exact same issue with a different ROM later that day also with MTG. This is probably why sailfish ROMs come with built in gapps?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SilverSix:
Have to repost, sry.

I found out that my internal storage has a bad sector which has been ****ing up many things, so idk if that was causing issues during flashing. It's currently quarantined (was copying a bunch of files and a folder got corrupted mid copy meaning that it's on the bad sector but now it's in use so nothing else will try to use it)

It is important to see if someone else can replicate my errors or if they were just isolated issues.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GHOST1010:
Did anyone get this running properly?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] honeybear81:
Yeah I had it running for a bit.

Did wipe

Flashed rom

Flashed twrp

Reboot recovery

Flash gapps

Flash debug.zip

I used the most current mindthegapps.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GHOST1010:
For a bit? ,then what happened?

---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------

Not daily driver really?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] honeybear81:
I have a rom flashing problem :) It was fine. Reminded me of Lineage OS but with more features.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] koolsavas22:
how works it? any bug's?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GHOST1010:
Is this active?

Going official?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Device broken actually and I don't have money actually for bought one again so need to wait for a long time maybe
[Google Pixel ROMs, Kernels, Recoveries, & Other De] hinnis:
Would anybody please reupload the Debug.zip? Thanks a lot~
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jvyden:
completely lost

I know this thread is pretty old but I'm bloody desperate. I'm trying to build my own version and I cannot for the life of me find a method to create a device tree for RR. Your github 404's so I can't get any clues as to how I would do this., or just steal yours.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
;___; what
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ilko:
[MENTION=9666565]UnparallelSKY[/MENTION] hey, the file is not available to download and you don't seem to maintain this anymore. And since, you probably bought or got another phone. So, please do something or close this topic.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
File is available for download so don't spread wrong information ;___________;
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ilko:
Seriously... It was an invalid mega link before you edit your post
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Idk where you clicked for get to a mega link but the link was changed to gdrive since 2 month ;_____;
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ilko:
okay.... here is your Drive

this is your post

and the previous link

https://mega.nz/#!l0UxwICL!7taXjifjW9Q2HgKBCZjFirAq-v9GO5Vxryy_Zwlaaf0

You don't remember, but I do.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Can you stop annoying me ;___; I said I already changed link to gdrive some month ago to gdrive and I edited my post recently for replace my gdrive link because I disabled the share option of my link by mistake
[Google Pixel ROMs, Kernels, Recoveries, & Other De] strongst:
deleted
[Xiaomi Mi A2 / 6X Questions & Answers] TheGuyBelow:
Hi guys, according to my old thread; https://xdaforums.com/mi-a2/help/lots-issues-updated-to-android-9-pie-mi-t3881173

Since I updated my A2 to Android 9.0 Pie, I found that its portrait mode seems close to be useless.

It only focuses on the subject which is located on the middle of the frame, I cannot tap anywhere else in the frame to focus. In addition, locking focus doesn't help at all.

This issue has been appearing since the first Pie update, and is not fixed til now. I send my feedback to Mi every single update patch, but seems all my feedbacks are completely useless.

Any other modes work fine, both camera performs perfectly. There's only the mentioned issue in portrait mode.

Please note that I already tried factory reset, but it doesn't help fix the issue. Moreover, I found that many users also face this issue, so I am extremely sure that there's not only me.

Since the issue has never been fixed, so I wonder if you guys have any good suggestions to fix the issue, or any ideas how to force Mi to fix this big bug for us?
[Samsung Galaxy S10 Questions & Answers] SoNic67:
I had various Bluetooth headphones and I have found out that the sound quality varies a lot with the codec that is actually used by those headphones.

On Android 8 and above the list of system codecs can be seen by enabling Developer Options in the system, and scrolling trough those new options.

SBC is the basic codec (lowest quality), AAC is slightly better (used by Apple), apt X is a definite step-up in quality.

But to have a truly quality sound, either the aptX HD is needed or Sony's LDAC (only on Sony headphones/soundbars). I saw also, on my Galaxy S7 Edge, a Samsung HD codec (can be used only with some Samsung headphones/soundbars, like my Level U headphones).

Well, on my previous Galaxy S9 and and now on my Galaxy S10 (both unlocked devices) I could not find aptX HD or even the Samsung HD codec that is present in my old Galaxy S7 Edge.

Anyone has an idea why are those codecs missing in S10 and if/when will they be enabled?

This is what I have now:

[IMG="Samsung S10 aptX"]https://dl.xda-developers.com/4/7/6/9/0/0/6/Screenshot_20190531-074518_Settings.jpg?key=JCfrliN9wVedZI9Fy3vesA&ts=1559303318[/IMG]

Sadly, my old moto G4 Plus, on Android 8.1 has AptX HD available (since 2018):

[IMG="AptX HD"]https://dl.xda-developers.com/4/7/6/8/9/9/1/Screenshot_20190531-072250.png?key=nAAUlEwjq0gFNIOnTtOWZA&ts=1559302176[/IMG]

And this what can be seen on Galaxy S7 Edge:

[IMG="Samsung HD"]https://img.gadgethacks.com/img/original/32/08/63656409124633/0/636564091246333208.jpg[/IMG]
[Samsung Galaxy S10 Questions & Answers] Pierre118:
AptX HD and Samsung is a no-go, i'm afraid.

'Our developer has got back to us on this one today. It would appear aptX HD isn't quite as "robust" as they'd like, as it needs to send a lot of packets to the Bluetooth device - which could cause audio chopping whilst streaming stuff.

Their plan is use aptX Adaptive instead, a Qualcomm codec which combines support for high quality along with the required "robustness" - although they'll consider supporting aptX HD too if it proves to be able to cope with the required demands.'
[Samsung Galaxy S10 Questions & Answers] SoNic67:
aptX-HD (also known as aptX Lossless) has a maximum bit-rate of 576 kbit/s (48kHz/24bit). A standard PCM 1.4-Mbit stream (44.kHz/16bit) is converted into only 352 Kbit/sec aptX HD stream.

In my tests with the LDAC, it works fine with the 660/606kbps, and it starts to be choppy at 990/909kbps. So I would assume that aptX HD would be fine to play.

Of course the LDAC is superior codec in this case, but that limits me only to Sony headphones/soundbars.
[Samsung Galaxy S10 Questions & Answers] charlescc2:
Was the implication that aptX Adaptive is a codec they plan to implement in future device releases, or is this something that can be patched into current handsets such as the Galaxy S10?
[Samsung Galaxy S10 Questions & Answers] techhahn:
With my aptX headphones connected, my Galaxy s10e(Exynos) uses SBC codec. If I manually select aptX than again it switches back to SBC.
[Samsung Galaxy S10 Questions & Answers] sebixy:
on my s10+ it sais the maximum bt data transfer rate is 990kbps but the maximal bt audio quality is 96khz and 32bit which should be like 3.somthing mBps which is the maximal value of the teoretical bt tranfer the phone is capable of, don't know why this huge difference originates
[Samsung Galaxy S10 Questions & Answers] mac_angel:
just wanted to add a bit of info. You mentioned LDAC being the best, and I agree. It is a Sony codec, but there are other devices that use the profile. I have the EarStudio ES100. It lets you use any set of headphones you like, supports High Res audio, has a great upsampler and software, and supports LDAC. I have the Samsung s9 myself, and looking at getting the S10 as well. I've been trying to find info to see what Bluetooth codecs it supports. I have been chatting with Samsung for an hour and they can't tell me and don't even know how to find it. I'm literally shaking my head at their stupidity at not just grabbing an S10 and opening up the developer options like you did.

This all started because I'm trying to find a new set of in ear bluetooth headphones for my fiance. She's not an audiophile like myself, so not looking for anything expensive, she just uses them to work out. But I don't want to buy anything crappy either. But no one lists bluetooth profiles any more. Not the phone manufacturers, nor the headphone manufacturers.