yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Themes and Apps] DaveShaw:
Install this special Opera Mini CAB from Here: http://xdaforums.com/showthread.php?t=398567

Use Schaps Advanced config and Map a Softkey to Launch Opera Mini.

Thanks

Dave
[OnePlus 9 Pro] ih8snow.lc:
I am using the non root vanced app and memc does not work. Is there any way to get it to work or do I need to use the root version, and if so can someone confirm that the vanced root app works with memc.
[OnePlus 9 Pro] fifasax:
Yes. It need the root to replace the original youtube. MEMC is triggered by the name of software in the app system file. unless you know how to replace buildin youtube app with adb. I think you have root and use the root method. I already leave a message to the oneplus community to ask them to add a custom button so we can control which app to have MEMC. You should too. So as many people want that feature. It might but it into following update whoever know when
[OnePlus 9 Pro] Klbgr:
Is memc working for someone on root variant of vanced ? Not working for me on 1.2.7.7BA

EDIT : it's now working lol
[Samsung Galaxy S21 Ultra] WisdomWarlord:
My friend has an S21 Ultra 5G with the Exynos SoC. There's an app that constantly crashes, Samsung Audio Remote, that he NEEDS to control the volume on his sound bar because he's handicapped and can not use a physical remote. After a total of 3 HOURS on the phone with Samsung support, the next step and alleged solution is to wipe the cache partition. But I can not get I to recovery. The procedure support told me to use, that I tried 3 times while they were on the phone, did not work. Now, I'm no tech god, but I have successfully flashed dozens of roms on several devices over the years, including 4 Samsung Galaxy devices, so I know a thing or two about pressing buttons in the right sequence. But, this S21 is kicking my tail. It's sooooo much is a trainwreck that I have decided that Samsung does NOT want my money, so I'll be happy to never give them a penny more. But. My friend has this $1000 turd so he's got to get it figured out. So. Please. How do I get into recovery so I can wipe the cache partition on this pile of junk?

Build number is G998BXXU2AUBB.

As a side, this problem exists on his S21, my Moto G Stylus, and his Galaxy Tab tablet, but it does NOT exist on his LG Stylo 3, so I'm pretty confident that even wiping the recovery partition will not solve the problem, but if you've ever dealt with tech support, you know that until you do the next useless troubleshooting step, they won't move on to try to actually solve the issue. So, I gotta do it.
[Samsung Galaxy S21 Ultra] Skander1998:
Turn off the device.

Then boot with both the power button and the volume up button pressed (and hold them) until the phone boots to recovery.
[Samsung Galaxy S21 Ultra] fdomi:
In my experience this only works if the phone is turned off and connected by a USB-cable to a computer. If it doesn't sense the cable connected it will just boot to normal Android OS.
[Samsung Galaxy S21 Ultra] Sukrith:
Ya... You need to connect a cable for it to work!😖😖😖
[Samsung Galaxy S21 Ultra] fdomi:
It's funny that several websites forget to mention this, they just write about the key combination and rebooting, but without the cable being connected to the PC it won't boot to recovery.
[Samsung Galaxy S21 Ultra] sesnut:
on most devices you dont actually need the cable connected first and some devices do weird stuff like turn on when you plug them in. They probably dont have the actual device.
[Samsung Galaxy S21 Ultra] fdomi:
Yes, yet they inform and post the key combination as if they have tried it themselves.
[Samsung Galaxy S21 Ultra] dr.ketan:
You needs to connect to PC to reboot to recovery along with combo key started from Android R on Samsung devices. On older os it doesn't requires
[Samsung Galaxy S21 Ultra] amirage:
Actually you don't need to connect the cable to a PC...the cable has to be connected to a power source. I booted to recovery with the cable connected to my power bank..
[Samsung Galaxy S21 Ultra] dr.ketan:
Power isn't important, storage is

Wall mount power won't work, power bank, usb storage will do.
[Samsung Galaxy S21 Ultra] fdomi:
I tried that and it didn't work for me, I actually needed to boot into a PC, or maybe it doesn't work with simple slow charge USB? I will play with this to see if it works with another power source.
[Samsung Galaxy S21 Ultra] dr.ketan:
Try any usb storage if you have, it will work. It doesn't need power.
[Samsung Galaxy S21 Ultra] mankvl:
Even usb c headphones will work :)
[P3300, MDA Compact III General] marcello.mezzanotti:
whats the internal diff between arte100 and arte200 ?
[Galaxy S II General] FarmerDaveo:
Hi, my Galaxy S2 was working great with KitKat that I flashed and then thought why not try a new LiniageOS. That Rom failed to install and I figured I would try an updated TWRP recovery. I tried the newest version and it failed to install. It warned me I had no rom installed on reboot but I rebooted anyway and went back to recovery. No issues until I tried an earlier version of TWRP that failed during install as well and now is in boot loop with no Rom. Can not enter recovery mode either. Can enter download mode but Odin and my computer do not seem to detect my phone when plugged in via usb. Tried 3 usb cables but only one computer available. Samsung usb drivers installed.

Any ideas what to do next.

Thanks!

P.S. I tried to post this in the S2 Q&A section but it will not let me post there as it wont stay logged in to do it once that section is clicked.
[Galaxy S II General] It_ler:
I recommend to check this thread:

https://xdaforums.com/t/guide-fix-a...d-gsii-i9100g-m-p-t-version-included.1457458/

If you have questions or need further help, ask in this thread directly.

Good luck!
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
Dear all,

I am trying to build a LineageOS 17.1 ROM for the Galaxy Tab A 9.7 (gt510lte) SM-T555.

Using the repos of @retiredtab and aala27's repos I managed to build a config that resulted in a buildable LineageOS that I could install and that shows the Lineage boot animation but crashes/reboots after a while.

Fyi, my forks for the GT510LTE (SM-T555) I currently maintain here: https://github.com/blizzard4591?tab=repositories

Questions to @retiredtab:

- What is your current local_manifest/roomservice? I could not locate this in your Github and used one posted by aala27 in a different thread, but it might be "off".

- Did you extract the required proprietary files by hand from stock ROMs or is there an automated way? I have "SM-T555_1_20190103084053_we4a668guy_fac" with T555XXU1CQHA/T555XXU1CRG1 that I know works on my T555.

- The repo "vendor-samsung-gt5note10wifi" in your Github only contains a branch for Lineage 18.1, is that intentional?

Sadly, I am a total noob in the area of building Lineage, so I might miss some obvious things!

I am willing to put in some time and effort to make this work, but I just do not know enough to do it efficiently.

If you can spare the time for a few hints, I believe I can make some progress!

Cheers

Update 1:

My image is working, i.e. it boots and gives a stable system.

Problem: Bluetooth does not work and crashes a lot, I have no clue what the problem is.

Problem: Audio is not working, I see a lot of "audio_route: unable to find path 'low-latency-playback speaker'

The system settings dialog is missing the "Android Patchlevel" information - is this expected? I am building using "repo sync, breakfast gt510lte, brunch gt510lte" - is this correct? I am just an idiot.

Update 2:

Bluetooth and Audio are working, SELinux is not, so permissive it is for now.

Builds available on request.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
It was there before, but I think after the switch to Xenforo on Dec 1, 2020, it might have gotten lost. It's there now and what I use to generate 17.1 for T550.

No, I just used what's in at https://github.com/Galaxy-MSM8916. Having said that, I found that for the SM-T350, it was missing some very important files so I grabbed those from stock.

gt5note10wifi is for the P550, not T550. You shouldn't be using that as the *.mk files won't copy the correct blobs for your device.

Congrats on getting a bootable stable system. For bluetooth, you are probably missing a bluetooth blob. Look in your adb logcat (see below) for red messages that are bluetooth related. It might say something like "missing libbt-nv.so".

Missing Android Patchlevel means you don't have a property declared in your *.mk file. Right now, I can' t remember what it is, but I will look for it.

Instead of brunch, I do

TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j2 bacon

This makes an engineering build that starts adb logcat immediately. That way, you can see all the messages as soon as the device boots. It helps a lot in troubleshooting stuck at boot animation problems.

The -j2 indicates how many CPU cores I have. If you have more, say 4, then -j4.

Once you solved all your problems and if you want to share your ROM, then do a brunch which is userdebug by default (for me, I just do a make -j2 bacon).

For adb logcat, I find

adb logcat -C | nl

helpful. It color codes the log so anything in red (error) needs attention. Nl numbers the log so it's easier to remember where you error messages are vs a timestamp.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
For the Android patch level, show me a screenshot so I exactly what you mean.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
Try not to edit your initial post because I didnt' see the audio problem. Just make a new one so that I see new responses.

The audio problem is likely you don't have the correct definition in mixer_paths.xml. aala27 had the exact same problem. It's likely this

https://xdaforums.com/t/unofficial-...ab-a-9-7-sm-p550.4160909/page-2#post-83703037

For SM-T550, the line inside mixer_paths.xml looks like

<path name="low-latency-playback speaker">
<ctl name="QUAT_MI2S_RX Audio Mixer MultiMedia5" value="1" />
</path>

You can see above, I have a path name that matches 'low-latency-playback speaker' exactly. Your mixer_paths.xml probably doesn't have this defined so you get no audio.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
BTW, all the info I'm giving wasn't available via search engine when I first started. It's extremely frustrating to troubleshoot when I first started. Even now, I have problems with audio over bluetooth and stuttering audio over bluetooth for two platforms that both worked perfectly on the previous last major revision on Android.
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
Thank you so much; I know how hard this kind of initial research is!

Regarding the audio issues:

I tried that already, as you can see in https://github.com/blizzard4591/android_device_samsung_gt510lte/tree/lineage-17.1/configs/audio I used the config files from my stock image (I had assumed they would work, but they do not - why?) and then added said speaker there, but no luck, it still has the same error message. What am I misunderstanding?

Regarding Bluetooth:

Thanks to you tip, I added the libbt-nv.so module, but this did not change the situation.

I am now building a debug/eng build, but in the log I still see no messages of missing drivers/firmware/SOs. You can find my Logcat attached - could you take a look and tell me whether I am missing something? Should there be messages?

How did you find out that you were missing BLOBs?
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
You need to check the actual rom image to see if the mixer_paths.xml is correct. Do

adb pull /system/vendor/etc/mixer_paths.xml

and compare if the two are the same.

I only guessed at what might be missing. The logs will tell who what's missing.

I see no log attached. Zip the log and then attach it.
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
Yes, the file was incorrect, I guess the path

$(LOCAL_PATH)/configs/audio/mixer_paths.xml:$(TARGET_COPY_OUT_VENDOR)/etc/mixer_paths.xml

did not resolve to where it should, I changed that, once the build is done I will check.

Interesting, I can see it, but I attached it as ZIP!
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
The log you attached is missing all the bootup sequence. You need to start adb logcat as soon as the device boots.

Audio

=====

Your mixer_paths.xml should be in /vendor/etc. /system/vendor is usually a link to /vendor. From my P550.

$ adb shell
gt5note10wifi:/ # ls -al vendor
lrw-r--r-- 1 root root 14 2008-12-31 17:00 vendor -> /system/vendor

If you are using the 17.1 msm8916-common repo, see lines 80 to 83

android_device_samsung_msm8916-common/msm8916.mk at lineage-17.1 · Galaxy-MSM8916/android_device_samsung_msm8916-common

Common MSM8916 tree for Samsung devices. Contribute to Galaxy-MSM8916/android_device_samsung_msm8916-common development by creating an account on GitHub.

github.com

may be overwriting your stock mixer_paths. I would comment out lines 80 to 83 as a test.

Bluetooth

=========

You have tons of errors with your bluetooth. If you view your logcat in color, these are all in red.

04-01 13:19:22.910 1212 1212 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-01 13:19:22.911 1212 1212 F DEBUG : LineageOS Version: '17.1-20210401-UNOFFICIAL-gt510lte'
04-01 13:19:22.911 1212 1212 F DEBUG : Build fingerprint: 'samsung/gt510ltexx/gt510lte:7.1.1/NMF26X/T555XXU1CQI8:user/release-keys'
04-01 13:19:22.911 1212 1212 F DEBUG : Revision: '8'
04-01 13:19:22.911 1212 1212 F DEBUG : ABI: 'arm'
04-01 13:19:22.912 1212 1212 F DEBUG : Timestamp: 2021-04-01 13:19:22+0200
04-01 13:19:22.912 1212 1212 F DEBUG : pid: 866, tid: 1203, name: bt_hci_thread >>> com.android.bluetooth <<<
04-01 13:19:22.912 1212 1212 F DEBUG : uid: 1002
04-01 13:19:22.912 1212 1212 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
04-01 13:19:22.912 1212 1212 F DEBUG : Abort message: '[0401/131922.772914:FATAL:hci_layer_android.cc(119)] Check failed: btHci != nullptr.

When it crashes hard like above, there's no way bluetooth will work.

Again, if you are using the 17.1 msm8916-common repo, it's missing the bluetooth entries for manifest.xml and msm8916.mk.

For the manifest.xml you need something like

<hal format="hidl">
<name>android.hardware.bluetooth</name>
<transport arch="32+64">passthrough</transport>
<version>1.0</version>
<interface>
<name>IBluetoothHci</name>
<instance>default</instance>
</interface>
</hal>

For msm8916.mk, you need

# Bluetooth
PRODUCT_PACKAGES += \
android.hardware.bluetooth@1.0-impl
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
[Sorry for the delay]

Okay, I think I ironed out most of the issues.

What is confirmed working:

- WLAN

- Bluetooth

- Audio

- GPS (though the initial fix took 30min+...)

What does not work

- SELinux

WLAN:

I see a messages like

Is that an issue? I don't know...

I see a lot of messages from the PowerHAL:

I already tried https://review.statixos.com/c/android_device_essential_mata/+/1626/1 but that apparently was not enough.

SELInux:

I added the policies by https://github.com/VirsysElectron/android_device_samsung_gt510wifi and made them work, but it seems they are not really working.

Example:

I declare

in device/samsung/gt510lte/sepolicy/file_contexts, but it is not applied:

And I really do not know enough about SELinux to effectively engage this.

@retiredtab: How did you solve SELinux in your builds for the T550?
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
That seems like a really long time. Did you go outside to do the GPS reading? Sometimes it makes a difference if you are in or outside. You should do an adb logcat while testing out GPS. It might show some clues as to why it takes so long.

With the P550 and using GPStest from

GPSTest | F-Droid - Free and Open Source Android App Repository

An app for testing GPS and GNSS capabilities of a device

f-droid.org

I get a lock in 48 seconds by the window.

You need to read posts 202 and beyond at

https://xdaforums.com/t/rom-sm-t350...5-android-10-galaxy-tab-a-8-0.4158163/page-11

I list the tools that you can use to help build selinux policies. As I wrote in the other thread, do you blindly trust the policies generated by the tools? I'm not an expert so I don't know and it's highly dependent on each hardware device.

I built an image with selinux enforcing as a test sometime in March and while it works, I'm not confident and ready to release that. In addition, each device will require it's own set of selinux policies. What might work for the P550 may not work on the T555 due to differences in hardware (LTE, S-pen).

Building the correct selinux policies is an iterative exercise. Wipe everything on your device, format data. Install the ROM only. You grant the initial batch of policies, reboot, look at logs, grant some more and repeat until they are gone. You should do this with the ROM only. Don't load gapps, games, apps, etc and then run selinux.

I see them in my own builds and so far there's been no problem.

Same as above.

You will find through experience and more building that what works for one platform may not work for another. It's highly dependent on the device and code specific to that device.

In order to boot selinux enforcing, you need to remove line 140 from

android_device_samsung_msm8916-common/BoardConfigCommon.mk at lineage-17.1 · blizzard4591/android_device_samsung_msm8916-common

Common MSM8916 tree for Samsung devices. Contribute to blizzard4591/android_device_samsung_msm8916-common development by creating an account on GitHub.

github.com

Also, I'm not an expert in selinux, but I don't know why you would permit untrusted_app.te, untrusted_app_25.te and untrusted_app_27.te?
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
I think it was just the initial, first fix, and yes, I was not in the best position. Now that it knows where and when it is, a new fix even inside takes a couple of seconds. I used the same tool, also from F-Droid :)

I had to load Magisk and LiveBoot to even get the early-boot log. Using ADB logcat I was unable to get a log from "system start" - the adb process would hang and wait for the device to be fully booted. Even afterwards, no messages from boot. I had USB debugging enabled, default USB conf "file transfer", etc.

Any ideas what I am doing wrong?

Good catch - I simply copied the policies from VirsysElectron to start, but since they do not really work, I don't think I will continue much on this path. I share your opinion on old drivers and the greater picture. I had hoped the old policies would work for most of the basics, but they do not.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
For an eng build, there's no need for Magisk and LiveBoot to get an adb logcat. Part of the eng parameters is that it enables adb right away.

For developing selinux policies, you leave it in permissive first, develop the policies as I stated and then when you think you are done, then enable selinux enforcing. More at

Validating SELinux | Android Open Source Project

source.android.com

And that's the problem right there. It's so easy to kang or copy someone else's work today (legal or illegal) that some don't bother to check if it's right in the first place. I'm not saying VirsysElectron code is wrong, he may have a good reason why those files are generated.

I also fall into that boat. I use the public open source repos, but there's no way that I have the expertise or time to check everything in the repo for errors, security vulnerabilities, code correctness, etc.
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
No, that is the problem - it did not. I am using eng-builds and, as I described, adb did not work, and I have no clue why.

I read that and some other introductions to SELinux, I get the general idea and concept - but as shown in my example, the labeling rule

is not applied, I did not find anything that would tell me why or how to debug such an issue.

I started writing my own policies from scratch (its somewhere in the repo history), but I first wanted to get my bearings, see how things work - ideally from a known, working starting point - which was a good idea, as otherwise the issue mentioned above regarding the labeling rule that does not get applied would have cost me much more sanity than just questioning someone else's code :D
[Samsung Galaxy Tab A series Questions & Answers] Schaagi:
Hello RandomAndroidTinkerer

I also own a T555, currently with TWRP 3.3.1 and LineageOS 16.0 from Virsys( 20191231). It's very stable, except the SIM didn't work.

Am of course interested in your image and would like to test it out. Which TWRP version do you use ?

Friendly greetings

Schaagi
[Samsung Galaxy Tab A series Questions & Answers] tabletuser555:
Hallo RandomAndroidTinkerer,

thank you very much for your work and of course thanks for retiredtab and the others for their work This is my first post here and I you are the only one I found who builded an actual image. I'm very interested in testing your build. Could you send me an link, please? Thank you and bye bye.
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
Hi, I applied for an uploader account at AndroidFileHost, once this is granted I will upload a current build.
[Samsung Galaxy Tab A series Questions & Answers] RandomAndroidTinkerer:
Current engineering build is up: https://www.androidfilehost.com/?w=files&flid=324776

I am using TWRP 3.1.0 from here.

Be kind on the feedback :)
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
For fun, I tried it on the P550 and not surprisingly, it doesn't boot. It doesn't even out adb logcat.

LineageOS also builds it's own recovery.img as another recovery option to TWRP. It's not as user friendly and lacks some features, but it's functional.
[Samsung Galaxy Tab A series Questions & Answers] Schaagi:
Thank you so much for your image - I am very excited to test it. Feedback follows in the next days.
[General Questions and Answers] thsiw:
Hi,

Does anyone knows how to root Huawei Y5 2019?

I just want to root it because i want to be able to transfer the APPS to SD Card

And i can't find a way to do this from the phone itself, so if anyone knows how to do this.. Please help
[General Questions and Answers] Deleted member 1890170:
How to move apps to external SD-card in detail is described here:

How to Move Your Android Apps to an External Sd Card: 7 Steps

This wikiHow teaches you how to move an Android app to an SD card. This option may not be available for all of your apps. Open your Android's Settings. It has a gear icon that's either gray or white. If you don't see it on the home screen,...

www.wikihow.com
[General Questions and Answers] thsiw:
Unfortunately, this is not possible on Huawei Y5 2019, if i manage to root it then with, for example Link2SD application i can transfer them.. Like this, i cannot do anything, but i said that if maybe anyone knows a way without root too
[General Questions and Answers] thsiw:
Bump
[General Questions and Answers] Austinredstoner:
Maybe because your phone doesn't have a sd card u need a sd card for the phone

Not all phones have a sd card

If you're phone doesn't support for a sd card than it's just not possible
[General Questions and Answers] Deleted member 1890170:
Phone has a microSD slot.:)
[General Questions and Answers] Austinredstoner:
Yep that's true
[General Questions and Answers] thsiw:
Bought a 32gb one few days ago, just cant find a way to transfer the apps to it, unlucky