text:
Samsung devices: dual networking
I have the following setup: a Wi-Fi device which is NOT connected to the internet, like a drone or IoT device. The data of the device shall be uploaded to the internet.
While it is possible to connect to both networks within an app using the ConnectivityManager, it is not possible to use the mobile internet outside of the app. The devices have Android 6.0 or higher, so it should be actually supported by the Android system. But it seems to me, that Samsung did not implemented that support.
How do I use the mobile internet for instance to receive mails or push notifications while I am connected to a Wi-Fi which has no internet itself.
Thanks.

Similar questions have been asked here:

Can an android phone connect to both Wi-Fi and mobile data network at the same time?
How to enable dual networking in Android shell?
and
How do I connect to a wifi ap and 3g network simultaneously?

However due to the bounty description I will try to aggregate these facts and expand a bit since the answers were not marked as accepted.
Short answer it is possible to have dual networking but workarounds differ slightly.

From this source : Switch seamlessly between WiFi and Cellular with Multipath-TCP You can make use of Multi-TCP.

Multipath TCP (MPTCP) is Multipath-TCP is an extension to TCP that allows the parallel usage of multiple Internet connections.
Multipath-TCP is already implemented for the Linux Kernel, but not yet integrated into the official upstream kernel.
The source code (and some precompiled kernels, including Android builds) can be found here: http://multipath-tcp.org
Extra source with reference to Samsung device: MPTCP on Android Devices , and MultiPath TCP - Linux Kernel implementation.

In another source,  enable wireless and 4g at the same time  Users claim they were able to enable dual networking with the following workaround (quoted):

Turn off wifi in the normal way (from the phone's user interface) if it's not already off.

All the following steps done in a root shell:

load the drivers
busybox insmod /system/lib/modules/cfg80211.ko
busybox insmod /system/lib/modules/wlan.ko
start wpa_supplicant to connect to the first available wireless network. The wpa_supplicant.conf file I list below is the one maintained automatically by the phone as you join new networks. If you want more control (e.g. connect to only a specific network), copy the wpa_supplicant.conf file somewhere, modify it as needed, and specify it on the command line.

wpa_supplicant -B -Dnl80211 -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf

dhcpcd

busybox pkill dhcpcd
 rm /data/misc/dhcp/*
 dhcpcd wlan0

verify route

busybox route
For me this is showing the original default first on the list (goes through rmnet_usb0) followed by the new one configured for the wireless lan wlan0. Traceroute shows the traffic going out the first one.
Now, at this point if you try to enable wifi normally from the phone it will not work. To make it work:
ifconfig wlan0 down
 ifconfig wlan0 unplumb
 rmmod wlan
 rmmod cfg80211
And you can turn on wireless again

Alternatively with script:
# enable dual-networking:
pkill dhcpcd
svc wifi disable
svc data enable
netcfg wlan0 up
cd /data/misc/wifi/.
wpa_supplicant -B -Dnl80211 -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf
dhcpcd wlan0
ip route add x.x.x.x via x.x.x.y # add any desired local route

# disable dual-networking:
ip route del x.x.x.x/x via x.x.x.y
pkill dhcpcd
pkill wpa_supplicant
rm -rf /data/misc/wifi/wlan0
netcfg wlan0 down
svc wifi disable
svc data disable

(A script runner is needed to run these scripts and root; you can get one here: SH Script Runner
And they noted:
It works perfectly but note that you don't actually see the wifi icon turning on, but if you run netcfg | grep UP you will see that the wlan0 interface is up and running (as well as the rmnet_usb0 mobile data interface, both of them will be up and will have the expected IP addresses) and you can access your local LAN while your mobile data 3g/4g whatever provides your default route to the outside world.

Other workarounds:

Using Super Download Lite
The developers of the app claim that it has the ability to perfom dual networking on android devices by combing 3G/4G and Wi-Fi networks.

Modifying the routing table

Another source: http://ironings4.rssing.com/chan-3701516/all_p2.html.
Provided details on creating a bash script in order to modify roting table to allow both 3G/4G work with Wi-Fi. Here is the script:
pkill com.android.phone sleep 30 route add -net 10.0.0.0 netmask 255.0.0.0 dev ppp0 route add -net 15.0.0.0 netmask 255.0.0.0 dev ppp0

The above is an example for a couple of address ranges to redirect to 3G connection  to the routing table via linux shell for using INTRANET via ppp0 for a few address ranges, while all the other destination addresses normally go via Wi-Fi.
The trick here is to force an application on the phone (or maybe it is a service, called com.android.phone) probably related to 3G radio interface to crash while you are connected to wifi, the 3G signal indicator will go down for a few seconds and soon after it will return to normal but this time with both H(SDPA) and Wifi icons showing on the notification area on the upper right of the screen.

In another article: Let WiFi and 3G connection work together by hacking ConnectivityService.java   (migrated to XDA forums)
The offered how to accomplish the task by hacking connectivity service:

Fully quoted:
“The goal of COIN project is to use WiFi and 3G connections simultaneously. So it conflicts with the policy of Connectivity Service, but there is no configuration to edit the policy, and it is hard coded. You can find the clue in ConnectivityService.java:handleConnect function.
Our current solution is quite brutal, which is to mask the eyes of Connectivity Service by modifying its message handler entry like the following:
// must be stateless – things change under us.
 private class MyHandler extends Handler {
 @Override
 public void handleMessage(Message msg) {
 NetworkInfo info;
 //added by COIN to disable Connectivity Service
 int networkState = 8; //not any following state
 /*use static google dns server for wifi and 3g*/
 if (msg.what == NetworkStateTracker.EVENT_STATE_CHANGED) {
 SystemProperties.set(“net.dns1″, “8.8.8.8″);
 SystemProperties.set(“net.dns2″, “8.8.4.4″);
 bumpDns();
 }
 //////////////////////////////////////////////
 //switch (msg.what) {
 switch (networkState) {
 case NetworkStateTracker.EVENT_STATE_CHANGED:
 info = (NetworkInfo) msg.obj;
 int type = info.getType();

…..

And then compile the modified ConnectivityService.java in the android source code tree, you can get an new services.jar file in framework directory. Replace the existing services.jar on the cell phone with the following adb commands, then reboot the phone

 adb shell “mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system”
adb shell “chmod 0777 /system/framework”
adb push services.jar /system/framework
 adb shell “chmod 0644 /system/framework/services.jar”
adb shell “chmod 0755 /system/framework”
.”

Conclusion
While I couldn’t test some of the workarounds myself, I have learnt most of these might have worked in earlier android builds (based on the evidence) so I am not   sure if the same is applicable in android 6. This feature seems likely to be implemented with emerging technologies evidenced by Multipath TCP technology described. For all the workarounds require root.
Hope this brings some light.
References
(Included in body text)

It is 2017 now.
Long before mobile devices, people were writing desktop applications connecting to several network interfaces simultaneously. It was necessary to handle that on the application, not system, level.
iOS supports that perfectly, as long as Linux, Windows, OS X.
The developers in Android team broke Linux they used to build Android and introduced a flip-flop switch in the Kernel to switch between Wi-Fi and 3G. Very sad.
Some developers were trying to remove that for several years, but it was so strongly hardwired in the Kernel, that they gave up.


text:
OnePlus One: Multiple issues involving MTP and Google Play on updating to CM13 via OTA
Device: Oneplus One
Android version: 6.0
Cyanogenmod 13.0
Today, I saw there was an update for 20151203 OTA and decided to download it and flash it via TWRP like I usually do. Before that, I was running on 5.1.1 (I think) and I didn't realize that it was updating me to Android 6.0 until my phone rebooted. Upon flash and reboot, I have the following errors

Google Play Services has stopped working: The popup is constant and annoying, sometimes stacking up and by the time I close one stack, another one appears! Makes the phone impossible to use. I read up on a few solutions, where one said - set your location services to "Device Only" and the other was go to settings → apps → reset app preferences. Tried both, didn't help much, still have the annoying popup.

Also, in my notification tray, there is a message saying "Google Play Services won't run unless you update Google Play Services". Everytime I click the notification, it opens a few activity which is just blank, I can't do anything. Google Play is present in my app drawer but on clicking it, I get the same blank screen.

Ever since I flashed, I'm unable to browse my files via my computer. I connect it via the USB cable and while my system is able to identify my device and even asks me if I'd like to browse it's files, when I click "Okay", I get a blank page as if my device has nothing (not even an internal storage option like before). However, my files are intact on my device for I'm able to use file manager and browse it on the device itself.

The problem I kind of solved partially by toggling the USB Configuration type (which was on MTP by default) to something else, then toggling it back. Not quite sure why it happened, but that's how I fixed it for the time being. Although, the second bug isn't completely gone. On rebooting the phone and the connecting it to my system, I'm presented with the same problem. However, on toggling that config type again, it appears, but one can't be expected to do this everytime he wants to connect the phone to his system right?
Any help will be greatly appreciated!
EDIT: Shout out to Tamoghna Chowdhury for the quick help. Finally resorted to wiping, and clean flashing CM13 along with GAPPs for MM. Everything works fine now. Thanks for all your help!

Well, there isn't Android 5.1.2, I changed it to 5.1.1 (it could be 5.0.2 BTW). Did you have CM 12.1 or 12.0 earlier? Also, the 2nd problem is general to all 6.0 devices

No, you're right, it would've been 5.1.1, thank you very much for that. Also, to answer your question, I had CM 12.1 before that. Also, I just tried downloading the Google Play Services apk for 6.0 from online and tried to install it manually. It just says "App was not installed" at the end of it. Uninstall / Force stop for my currently installed Google Play Services is greyed out too. Thanks for your help!

Could you try getting a signed GAPPs pack for MM and flash that? Also, is a clean flash out of consideration?

And regarding the second problem, I can live with it until a fix is rolled out. But any ideas on the first problem? That's a real pain! All google related apps that I have aren't working either since they use the services too.
Edit: I have downloaded GAPPs for MM. Just about to flash it. And clean flash is possible, but I'm trying to keep that as a last resort.

I'm about 60% sure the GApps problem is due to the OTA update (a dirty flash in our terms). If you can do so, completely clean reflash a CM 13 zip (full, not an OTA update from 12.1), and flash a compatible ARMv7 CM13 GApps pack over it.

Haha I kept seeing this term dirty flash all over and wondered if that's what I have. Anyway, I have the files required for flashing. Just wanted to see if there was any less messy option. Anyway, I guess I'll just do that. Also, I don't quite know if this might be why but when I was downloading the update OTA, my net connection was a bit unstable. So maybe the download didn't happen correct! Anyway, will clean flash and post back here. Thank you!

I'll address your 2nd problem 1st, as that is a simpler thing to describe.
I suffer from the same issue on a stock HTC Nexus 9 (6.0, MRA58K). Whenever I connect it to my PC, it defaults the USB connection mode to "Charge Only", and I have to toggle it back to "MTP" from the persistent notification in the statusbar.
AFAIK this is a general problem with Marshmallow, and one of my friends with a OnePlus One with CM13 also experiences this issue. I'm sorry, but we can only hope some enterprising developer corrects this oversight/bug/feature soon in AOSP.
Edit:
From @Firelord's comment, it appears that the Marshmallow default of "USB Charging" is a deliberate feature in Android 6.0. This is highly inconvenient for some users. See the Android 6.0 official change log here. This link is courtesy of @Firelord's answer here.
Now, the 1st problem.
This error of "Google Play Services has stopped" is common after "dirty-flashed" updates. Since the /data partition remains untouched by an OTA update or a dirty flash, the updated versions of the system apps it stores for Lollipop will interfere with the inbuilt, higher versions for Marshmallow which are in the newly-flashed '/system` partition.
Since you use TWRP recovery, I'll recommend wiping /data and clean flashing a full CM13 zip for the Oneplus One with a compatible (ARMv7 Android 6.0 CM13) GApps package zip. Use TWRP's default wipe of /data without /data/media to keep the data on your (emulated) internal SD.
In the future, consider only OTA updating between minor version upgrades, e.g. from 5.0 to 5.1 or 5.1 to 5.1.1, not 5.1.1 to 6.0

It appears that the second problem is a technical and deliberately added feature in Android M, which is now a big inconvenience for some users. See Android 6: connect as camera per default

@Firelord, I have edited in the information you provided

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/

authors: Олег Андриенко

sort: votes


text:
How to backup a full stock firmware image
I'm rocking a OnePlus Nord 2 5G here that just recently came back from assistance because I had wiped the partitions with the IMEI stored in it...
I had made a Nandroid backup, but it didn't backed up all the needed partitions to be able to restore it.
So, I went searching for an alternative way to backup ALL the partitions of the phone. Mainly by the use of adb shell while booted in TWRP to gain root access without being rooted + dd for the backup. And I've made some good progress so far, but now I'm stuck.
For comparison, I've donwloaded a full stock firmware from a third party, and these are all the files it contains:
audio_dsp.img
boot.img
boot_para.img
cache.img
cam_vpu1.img
cam_vpu2.img
cam_vpu3.img
cdt_engineering.img
dpm_1.img
dpm_2.img
dtbo.img
expdb.img
flashinfo.img
frp.img
gz1.img
gz2.img
lk.img
lk2.img
logo.img
mcupm_1.img
mcupm_2.img
md1img.img
metadata.img
misc.img
my_carrier.img
my_engineering.img
my_heytap.img
my_manifest.img
my_product.img
my_region.img
my_stock.img
ocdt.img
odm.img
oplus_custom.img
oplusreserve1.img
oplusreserve2.img
oplusreserve3.img
oplusreserve5.img
oplusreserve6.img
otp.img
para.img
param.img
pi_img.img
product.img
recovery.img
scp1.img
scp2.img
sec1.img
seccfg.img
spmfw.img
sspm_1.img
sspm_2.img
super.img
system.img
tee1.img
tee2.img
vbmeta.img
vbmeta2.img
vbmeta_system.img
vbmeta_vendor.img
vendor.img
vendor_boot.img

Now, these are all the partitions I was able to find in /dev/block/platform/by-name and backup:
audio_dsp.img
boot.img
boot_para.img
cache.img
cam_vpu1.img
cam_vpu2.img
cam_vpu3.img
cdt_engineering.img
dpm_1.img
dpm_2.img
dtbo.img
expdb.img
flashinfo.img
frp.img
gz1.img
gz2.img
lk.img
lk2.img
logo.img
mcupm_1.img
mcupm_2.img
md1img.img
metadata.img
misc.img
nvcfg.img
nvdata.img
nvram.img
ocdt.img
oplus_custom.img
oplusreserve1.img
oplusreserve2.img
oplusreserve3.img
oplusreserve5.img
oplusreserve6.img
otp.img
para.img
param.img
persist.img
pi_img.img
proinfo.img
protect1.img
protect2.img
recovery.img
scp1.img
scp2.img
sec1.img
seccfg.img
spmfw.img
sspm_1.img
sspm_2.img
super.img
tee1.img
tee2.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor_boot.img

As you can see, I'm missing a couple of partitions:
my_carrier.img
my_engineering.img
my_heytap.img
my_manifest.img
my_product.img
my_region.img
my_stock.img
odm.img
product.img
system.img
vbmeta2.img
vendor.img

Including system, which is pretty strange since it's one of the main partitions.
I've no idea how to find the directory of these partitions, with their labels, and how to back them up.

These are all the solutions, tools, and similar questions I've already tried, without success:
How to list all major partitions with their labels?
Command to list partitions?
How can I view the Android internal partition table?
https://github.com/for2ando/dump-android-partitions
https://github.com/IzzySoft/Adebar
https://github.com/dlenski/tetherback
https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en_US&gl=US
I just obtain the same list of partitions I'm finding, or straight not working / the directories do not exists. Maybe because it's a MTK device?
The only app that made a difference is FX file explorer. By going in the "file systems" section I can see the my_* partitions and their directory, but no system, vendor, or others. And I'm searching for a command line solution ofc.
I've contacted the user that posted the unofficial full stock firmware on XDA. I'm still waiting for the full response on what specific method he use to extract it, but for now I know he used some root solution, if that could help.
Root solutions are completely fine by the way, just, no "Nandroid" as an answer please.

All block devices are enumerated as /dev/block/mmcblk* or /dev/block/sd*. You can check from /sys/block/.

Do something like grep PARTNAME /sys/block/*/*/uevent. Or simply use blkid command. Partitioning tools like parted and gdisk also show partition/filesystem labels. Any Linux tool will work on Android.

@IrfanLatif Yeah, the partitions found in /dev/block/by-name are all sd*. Inside /sys/block/ though I find many partitions called dm-* loop* ram*, sdca, sdb, sdc, zram0, that all point to /device/virtual/block/. All without their labels though, so it's not really useful to know which of these partitions is what. I've searched around /sys/block/ and /device/virtual/block/ for a while but without success.

@IrfanLatif Alright, both grep PARTNAME /sys/block/*/*/uevent, parted print all and gdisk /dev/block/sdc listed the same partitions I've already found. But buth df and blkid commands listed all those partitions + all the missing ones minus system. That all points to the /dev/block/dm-* partitions. Now system is the only one left to find!

Just realized that I've never searched in /dev/block manually aaand found them. Exactly all the missing ones that aren't listed in dev/block/by-name, are listed with their labels in /dev/block/mapper, system included (it's /dev/block/dm-1). Thanks for the help!

Found them!
All the missing partitions are listed with their labels in /dev/block/mapper

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Why my SD card name is not the same as I format it?
I formatted my SD card into 2 partition. The first one is exfat and the second partition is f2fs.
I renamed the first partition as "Limbo" and the second as "Saint".
On Linux it shows both name but on the android is different, the first partition is "Limbo" and The second partition is "SanDisk SD Card".
Is there's any reason why it is not the same?
Using Gnome disk:

Is it partition label or filesystem label? Partition table MBR or GPT? What tools you used on Linux and Android to show the label?

@Irfan I think it's partition label, updated post. Sorry for late reply

Getting the partition label seems to be not that easy on Android, therefore a lot of apps show the volume serial name or a name generated using the card manufacturer instead. Check if the partition labels are shown correctly in DiskInfo. This app usually shows the real partition names (as "partition nickname").

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
How can I get rid of the "Restart now to finish the update" popup?
I have a Pixel 2 XL that I MUST keep on Android 10 for various reasons. (Yes, I am aware of the implications of doing this. This is a device that I use for development tasks, I don't go to random websites on it, I don't install unknown apps, I never use it away from my trusted home WiFi network, etc.) However Google seems hellbent on making me upgrade. Every few days I get a popup message (shown below) asking me to "restart now to finish the update." I get this popup even though I have "automatic system updates" turned OFF in Developer Settings, and even though I have Google Play Services notifications turned OFF. Is there any way to stop this message from appearing?

On an un-rooted device as far as I know: No. If your development does not make use of GoogleSafetyNet I would recommend to unlock the bootloader. Then you can install any Android version you want between 8.0 and 11.0: https://developers.google.com/android/images#taimen upgrading and downgrading, both is possible. Usually this option is why people buy Google devices for development.

Any updates on this? On rooted devices maybe somehow?


text:
"Could not launch inspector studio.network.inspection" when using App Inspector on Android Studio Bumblebee 2021.1.1.1 with WiFi pairing
When we use a "pair device using WiFi" in Android Studio Bumblebee version 2021.1.1, in the "App Inspection" section, it gives us an error in reading the "Database".

Could not launch inspector studio.network.inspection: Inspector with given id studio.network.inspection already exists. It was launched by project: sap.
This could happen if you launched the same inspector from two different projects at the same time, or if a previous run of the current project crashed unexpectedly and didn't shut down properly.
[Restart]

Nothing happened after pressing the "Restart" button.
How to fix it?

There is a similar question on Stack Overflow, but it hasn't been answered yet: How to successfully Restart App Inspection in Android Studio Bumblebee.

Kill app and restart work for me again.

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.


text:
Save Gmail attachment to different Gdrive
I have a personal Gmail (Google) account created some years back for my Android phone. Recently I have been given access to a new Gmail account by my employer.
When I open the Gmail or Gdrive apps they both show the two accounts and allow me to easily switch between them (Gmail has a useful combined All inboxes option too). So far, so good.
However if I open a mail sent by my employer to my work Gmail account and click on the Save to Drive icon on the attached PDF, the pop-up dialog box allows me to save the attachment only to my personal Gdrive account; it doesn't list my work Gdrive account at all.
So how do I directly save an attachment from my work Gmail to my work Gdrive?

Directly you can't. What you need to do is:

Tap on the file, and open the pdf file with the Drive.
When it opens, click on the Drive icon (the icon with a plus).
Select the account to saved it to, press Ok.

Not sure if this process is acceptable to you as it is equivalent of downloading and then uploading the file to the preferred account.


text:
Recover Nexus 6P that won't boot past Google logo
So I had a random reboot while debugging apps with android studio and after that device doesnt boot past Google logo. Factory reset and cache wipe do not help.
Eventually I found this guide https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view. But The problem is that I can't complete step 16 because device is enrolled in Adnroid beta program so there is no public image available that I need (NPG05F). I've found https://developer.android.com/preview/download-712.html but there is no Nexus 6P image listed for some reason. Will it be added soon?
Device OS is 7.1.2 (angler/NPG05F)
So is there anything I can do to get my device back?

Why do you have to follow that guide (taking OTAs versus just flashing a factory image)? Do you have any data to keep?

@AndyYan No, all data can go, it's fine. Problem is that flashing is locked so I can't flash anything except "Apply update from ADB"

To OP: bootloop with locked and non-unlockable bootloader is pretty much dead-end. I've looked around on XDA and it doesn't seem that sideloading a zip could solve it either, but doesn't hurt to try when the NPG05F OTA drops in the future. Shame that N6P doesn't have access to Qualcomm 9008 mode as a last resort as some phones do.

Gray area. Call google and complain about a hardware issue on the power button. It sticks and the phone is constantly boot-looping.  They did have issues with 5x and 6P so if you get someone who knows about those past issues, they may just send you a replacement.  Worth a try...

ROMS for your device and instructions to flash them can be found here: https://developers.google.com/android/images
Hope this helps!

Device is locked, executing "fastboot flashing unlock" returns error. So I think I can only flash NPG05F images

What is the error it returns?

@ejj28 Newer devices require OEM Unlocking to be turned on in the OS before the device can be unlockable by that command in fastboot - I assume OP is bumping into this error. Since the OS is unbootable now you can't just go flip that switch either.

@AndyYan exactly. from all my unlocking attempts/successes on many new devices, recently, you need to boot into OS, make sure play services connects and your phone connects to your cell network before you unlock through terminal.  i root, unlock project fi phones, verizon phones for my job

What I did when my Nexus 6P didn´t boot past Google logo and entered in a loop that never passed that state, was:
First, I entered in the Bootload section pressing at the same time the Power button + the volume-down button.
Then, pressing twice the volumen-down button I chose the Recovery-Mode option. (You confirm it by pressing the Power button)
After that, an Android icon with an exclamation sign logo will appear and below this a statement that says "no commands" or something like that.
Now, to enter the Recovery-Mode you have to press, not at the same time, but first the Power button and without releasing it press the VOLUME-UP button, and a screen with many options will appear.
I selected the "Wipe Data/Factory reset" option and when it finished, I turned the phone off.
Then I turned it on but it kept booting and rebooting never passing the Google logo, so I left it on my desk rebooting and went to my job. When I came back, after a few hours, the phone was perfect and had the screen they have when you for the first time turn it on and says something like "Welcome, choose language".
Summary, reset it to Factory and turn it off. After that turn it on and go for a walk or whatever but leave it rebooting a couple of hours. It worked for me and I hope it can work for other people too.
Greetings!

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/


text:
Charging my device from power bank with two-way USB-C cable?
So I have Nexus 6p with USB-C port and a Xiaomi Pro 10000 power bank.
Charging my device with bundled USB A -> microUSB -> USB-C Cable works. But when I connect them with my two-way USB-C cable that was bundled with my phone my phone is charging the power bank. Is it possible to charge my phone instead?

It certainly is unusual- can you charge the power bank fully first and then see if the behaviour persists

I actually already got my answer from reddit. I guess I'll post it here

Xiaomi Mi Pro does not support discharge through the USB-C port. It's not possible. I've tried everything.
If any store promises this feature this might just be a translation error (source)
Quickcharge through the usb-c port on nexus 6p is not possible too.


text:
Disabling "Ok Google" detection on Google Pixel 3a
I wanted to start using Pixel 3a (my old Nexus 5X is outdated) but I wasn't able to disable "Ok Google". I disabled all that was possible and recommended by a few how-tos but not successful.
Did I miss something when I bought this new phone? Where can I disable this?
This question is possibly strictly connected to googles pixel 3(a)
(dont remove that from the question)

Disabled and yet, phone is allways listening and after saying "ok google" it opens a dialog.

Your Google Assistant may allow you to designate the language. Try a really obscure language, if you don't find means to disable it completely.


text:
How to enter in TWRP/recover on Huawei P9 lite with keys?
I have a p9 lite Huawei.
I can boot into twrp with this command
adb reboot recovery

But without adb, I cannot enter in recovery mode.
If I push Volume Down+Power, it goes into bootloader (I can see a green droid logo).
If I push Volume Up+Power, it opens the EMUI recovery.
How to get recovery mode with twrp?Is possible with fastboot?
I have installed the twrp with
fastboot flash recovery twrp.img

Are you sure that TWRP was/is installed properly? Because it seems that you have 2 recoveries.

I have installed with fastboot flash recovery twrp.img

Does it make a difference when usb cable is connected? you can try 'fastboot oem reboot-recovery' or 'fastboot oem reboot recovery' or 'fastboot boot twrp.img' or you can try to flash twrp on erecovery (may brick your device) ask in the forum where you downloaded TWRP does really nobody know it?

I have found a workaround to enter in recovery.
a)Turn off device
b)Push power+VolumeDown
c)We enter in bootloader mode, with volumeup key we select the "recovery" and press power
d)Device reboot to twrp

thats so simple i used this often that i didn't consider you haven't tried that before and completely forgot about it

The basic process of installing TWRP on every phone is to boot into TWRP itself first so TWRP could overwite the recovery partition and replace the stock Android recovery with TWRP itself.
Step 1:
Boot into bootloader / fastboot mode
Step 2:
Make sure that your device's boot loader is unlocked. If not, please follow this tutorial on forum.xda-developers.com by user Mandrigan. https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Step 3:
Boot into fastboot mode again. Type in the command
fastboot flash xxxxx.img
Where xxxxx.img is your TWRP image file name.
Step 4:
Immediately boot into recovery (make sure you don't boot into Android!!!)
Step 5:
While in TWRP, Press "Mount" and tick on "System" box. Then go to "Advanced" --> "File Manager" find a folder with the name "system". Go into that folder and scroll down until you find a file with something like "recovery-from-boot.xxx". Press on the file name and press on "Rename" and add ".bak" at the end of the file name and it should look like this "recovery-from-boot.xxx.bak"
Step 6:
It is recommended to flash either SuperSU or Magisk so TWRP stays and it doesn't get overwritten by stock Android recovery.
Installation is done and you should have TWRP as your permanent recovery!!

the question is about key combo not how to flash recovery. besides this the fastboot command you stated is incorrect, and bootloader can't be unlocked (not from huawei, at least. they won't provide unlock codes)


text:
Typing hebrew in a text editor
I can't seem to find a text editor which behaves correctly in regards to bi-directional text. I type a lot in hebrew, with some english mixed in. In most of the apps I've tried (google docs, and mobisoft office suite), it doesn't render the spacing correctly and therefore you can't read the text as you're typing.
I started using VerbTeX, which has a simple text editor that works surprisingly well in this regard, but it gets slow and can't save to my external SD card.
If anyone knows a way that I can get my text files to display properly while I type them, it would be very helpful.


text:
Is Backing up my Android Device to the Cloud using Skydrive or Dropbox Equally as Effective As using dedicated Back Up Apps?
Is it equally effective to backup my apps, photos, contacts, SMS texts etc on my Android Smartphone (which is non rooted) using MS Skydrive or Dropbox compared with using a dedicated Backup App from the Google Play Store eg My Back Up Pro ? Is it the case that, it is as effective but the process is far simpler and less time consuming to carry out if a dedicated application is used.
This applies to general backing up and backing up in order to migrate/transition as seemlessly as possible when upgrading to a new smartphone

You would have to look at the pros and cons.
Pros of Cloud Backup

Off site backup (you will keep your data if your house burns down)

Cons of Cloud Backup

Make take a while to upload all of your data to the server
Make take a while to download the data again

Pros of Dedicated Backup App

Quick (no upload)
Quick and easy access (on your SD Card, so you can easily access it without an internet connection)

Cons of Dedicated Backup App

If your SD Card breaks, you lose all the backups
If there is a fire, you lose your backups
If you lose your phone with the SD card in it, you lose both the phone and your backup

You also have to bear in mind that My Backup Pro (which you mentioned), has the ability to back up to the cloud as well as file backups. You can also set scheduled backups.
With this in mind, I would say that a Dedicated Backup App would actually be better and easier than using a standard cloud service.

Excellent, thanks very much for your advice. Does the same apply for Rooted devices and Titanium Backup Pro ?

The same does apply for rooted devices, although I am not sure if Titanium Backup has cloud backup ability, I have only ever used MyBackup :)

Ok fine. My Backup Pro has the advantage that it can be used on both non rooted and rooted devices if my memory serves me correct

That is correct.

Thanks for confirmation and your guidance relating to the above :)

Titanium Backup AFAIK has Dropbox support. Also keep in mind that non-root backup apps cannot backup everything (e.g. not all app data -- just what's available via "provider" services on the device). So Titanium Backup would be a good choice for both, local and Cloud backup.

@Izzy - Titanium Backup though is only a viable option for rooted devices, and cannot be used for non rooted devices (as far as I am aware). My phone is non rooted so Titanium Backup would be option as it currently stands.

would not be*** rather in reference to Titanium Backup

Yeah, I thought I implied that by first stating that only apps with root permissions can really backup everything -- and then saying "so..." (i.e. "for this reason"). Obviously my phrasing wasn't clear enough -- sorry for that!

@Izzy - Yes that right you did, thanks for clarifying :)

One more thing to keep in mind is privacy: While you mostly have control over your locally stored data, you cannot say the same for Cloud services. For storing personal/sensitive information to the Cloud, you should always consider encryption.
A third option is to have your app creating backups on your sd card, and use another app (e.g. FolderSync) automatically sync the backup directory to your local computer (or NAS device). This way you are a bit safer if your card breaks, and have more privacy. And you have both, a local and a remote backup -- plus even if you need the latter one, download is a bit faster as from the Cloud. If you trust some Cloud service, chances are also good that service is supported by FolderSync as well.

I think you have provided some very sound advice in your answer above Izzy. Another point to consider, is what actually happens if the cloud in which your data is stored suddenly disappears - I guess then its lost for ever. Like the old saying goes "never have all your eggs in one basket"

Exactly. Which in a way is also why I'd take separate apps for "accessing all my data, making backups, encrypt them" and the other half "make a copy to the cloud". Best from two different devs. Though in case of TB, I have no concerns regarding Joel :) PS: But right: Good thing to have a local copy (SD), another one on your PC, and an encrypted one in the cloud :)


text:
Is there any way to use Viber on a tablet without a gsm module?
The tablet has a wifi, a microphone and a speaker. It would be ideal to make calls with, but Viber states it is incompatible. Is there any way around this?

Does the playstore state this -- or the app when/after being installed?

It just can't be done. Similarly WhatsApp too doesn't work on non GSM devices.

Yes.
Install Viber on tablet.
Once it asks for phone number give any cell phone number where you can receive the confirmation code from Viber service.
Try to activate the account.
Once you receive the activation code on the cell.. put the same activation code on the tablet and you are good to receive calls on the same device. Make sure you don't activate this Viber cellphone number on any other device.

I tried that, but google play said it was incompatible


text:
Why is Google Maps telling me that Offline Maps aren't available?
So, I've been travelling around the world a lot over the last couple of months, and one thing that I've been doing to avoid big roaming data charges on my personal phone, has been using the cached offline maps feature in Google Maps. This has worked without any problems in China, Australia, the UK and the US.
So I'm now in Brazil, and I suddenly find that I can't download any offline maps of the local areas.
When I go to the menu in Google Maps and select Make Available Offline, I get the usual square overlay to select the area, and then it turns red and says "Offline maps is not available in selected area".

I've tried zooming in and out, and moving the selection area around, but no luck.

It turns out that just because you can see and use a map online, that doesn't mean that Google will allow you to make the area available offline.
Offline maps are only currently available for certain countries, and Brazil isn't currently one of them, in fact it seems to be a fairly odd selection.
Google have published the full list of countries that it's available in here: Maps for Mobile - Offline Availability

EDIT: note that in a July 2013 Google Maps update, Google made offline maps into a hidden feature with no menu option any more. More about how to make maps available offline here: Get offline maps in new Google Maps

I found that I was able to remove the version of google maps I had installed (which was 6.11.1) and downloaded and installed an older version (6.6.0) from here which allowed me to pre-cache the area I was previously not allowed to. But in the older version I had to go to settings,labs and turn on the pre-cache option and then long press on the map, click on the balloon, and then scroll to the bottom for the pre-cache option.
I don't understand why downloading maps of certain areas is not allowed in newer versions. Obviously its not a technical reason. Is there some sort of political or legal reason? Other map apps can download maps for the entire world. It really doesn't make any sense to me...

Sure that "other map apps" don't use different map sources (like e.g. OSM) instead?

Early versions of google maps you can save offline large maps anywhere. Newer versions only allowed a smaller area to be saved and the latest verion makes the save function hard to find and you cant save some countries.
Everything seems to get worse with the newer version, its all to do with money I guess. Advertising can only be seen when online. Terrible.

How long ago did this change? What age of Google Maps app would you need to find to be able to save any area offline? (Bearing in mind that this question was asked 2 years ago, and it wasn't possible in some areas with the current app version then)


text:
Milestone outperforming Galaxy Nexus on mobile data connection speed
I recently switched from a Motorola Milestone to a Samsung Galaxy Nexus, and it seems the quality of my mobile data connections drops considerably between the devices without any apparent reason. The Motorola device can get up to 2mbps, while the Nexus struggles at ~150kbps.

The  *#*#4636#*#* menu on both devices shows no noticeable differences.

The tests were made 20 minutes apart using the same SIM card.
In summary:
Is there any configuration that can interfere so heavily on the way the data connection operates? If not, can it be a Radio/Baseband problem?
I'm using the 'stock' Google Rom (yakju) on the Galaxy Nexus, while the Milestone is using a custom Rom (ShadowMod 2.3), although it's behavior was the same on stock Froyo 2.2.

That ping is massive.  I would suspect network issues, even though they were just 20 minutes apart.  You should test multiple times to confirm and perhaps run some ping or trace tests.

Just did more tests on both devices. The ping went down on the Galaxy Nexus, varying between 100~300, although the speed kept the same. No changes on the Milestone, also.

Have you unlocked the Nexus? If so I would recommend trying a new radio image. You can find a nice list here . It's a fairly safe procedure, you can flash US radios to EU devices and vice versa without any issues

Yes, if you would share the information on your Bootloader, it would likely confirm what benwh is saying.

While this might not be the complete answer to your issue, it appears that the Galaxy Nexus is connected to an HSDPA:9 radio (10.1mb/s theoretical speed) while the Milestone is connected to an HSPA radio (14mb/s theoretical speed, not HSPA+ which can have a theoretical speed of between 21 and 42 depending on the network). While the theoretical capacities of the networks are similar, it does seem that they are using different radio tower connections, which could explain the difference in bandwidth that is being experienced.

HSPA most commonly refers to HSDPA+HSUPA.  Are you meaning HSPA+ by it?

No, I was referring to early HSPA networks which were 3.6-7.2-9mb/s theoretical. HSDPA+HSUPA I think of as a newer revision.

But you said HSPA was 14 mb/s.

Sorry I meant HSDPA early networks. HSPA commonly is held as having a 14mb/s speed. After doing some further looking HSDPA:9's theoretical speed is 10.1mb/s.

The screenshot one is using a different radio band - one that is more popular than the camera one.
This means that is is more congested, and therefore has slower speeds.
This is the most likely explanation.


text:
My Kindle Fire is stuck at the yellow triangle screen after installing TWRP. How can I fix this?
I followed the instructions on the official TWRP site on how to install TWRP on the Kindle Fire. So I did
wget <twrp.img>
adb shell idme bootmode 4002
fastboot -i 0x1949 flash recovery <twrp.img>

But now, my Kindle Fire wont boot. It just shows a yellow triangle. How can I fix it?

You need to reset the bootmode. This can be easily done with fastboot. Execute the following commands:
fastboot -i 0×1949 oem idme bootmode 4000
fastboot -i 0×1949 reboot


text:
How to insert Unicode characters by their hex codes using USB keyboard on ICS?
Is typing hex codes to insert Unicode characters possible when using USB external keyboard on vanilla ICS or Jelly Bean? Any root modifications available to achieve this?
Or, if not possible system-wide, are there any text editing apps that will allow such behavior?
Inserting Unicode characters such as various bullets, subscript and superscript numbers, Greek letters and so on has been very useful while studying. I normally use gedit on a netbook running peppermint distro, because it's very simple and nondistracting while typing my summaries. I've ended up knowing by heart the most used hex codes. I'm planning to replace the netbook by a cheap vanilla ICS tablet (already factory-rooted) and a comfortable, decent USB keyboard, and the described feature would be mostly appreciated.
Thanks in advance!

I know I can keep some special characters in a note and copy-paste them on demand, but I'm looking for a less distractive method that won't require exiting the text editor.

superset http://android.stackexchange.com/questions/17994/how-can-i-type-special-symbols-on-my-android-device-like-or-as-a-regular-cha

There is a way, actually! By editing system files in a rooted device through ADB. These two pages have the answer:
First, http://source.android.com/devices/input/key-layout-files.html explains how to edit the files that map any key scan codes of your USB keyboard (or even joystick buttons and the device's physical and touch buttons) to standard Android key codes. That's an optional step, useful if there are keys in your keyboard that do nothing in Android, or to remap the ones you don't use (multimedia keys, etc.). There's an app, Key Test by Chris Boyle, that will assist identifying key scan codes from your keyboard.
Then, http://source.android.com/devices/input/key-character-map-files.html shows how to map those Android key codes to Unicode characters when typing, so you can assign, for a given keystroke and modifiers combination, any Unicode character by its hex code, or one of the "magic" hex codes below:

The system reserves two Unicode characters to perform special functions:
'\uef00': When this behavior is performed, the text view consumes and removes the four characters preceding the cursor, interprets them as hex digits, and inserts the corresponding Unicode code point.
'\uef01': When this behavior is performed, the text view displays a character picker dialog that contains miscellaneous symbols.

So to have the behavior I wanted, all that's needed is to assign \uef00 to a key combination. Sweet!

Try this app: https://play.google.com/store/apps/details?id=org.tiwu.unicodekeyboard&hl=en_US
It does EXACTLY what you asked in your question. The app is free and does not contain any ads nor in-app purchases. You simply need to enter the Unicode character point, without the "U+", and then click on the character to enter it in the textbox. I hope this helps!


text:
Swype keyboard not swyping
Yesterday I installed Swype Keyboard to replace SlideIT. At first Swype was working but today it only lets me press the keys and not drag my finger. I think I briefly saw a message saying "dragging is not allowed in this mode" but it went away fast. I've tried disabling and enabling and selecting Swype again but not good. How can I fix this?

This happens when you use Link2SD or Apps2SD and move either the Swype App or the Swype installer App to your SD card. To fix it, move the installer and Swype back to the phone and reboot.
I found some of this information on http://forum.xda-developers.com/showthread.php?t=1042241 the rest I figured out by trying things.

This is most likely due to a licensing issue.
You should uninstall Swype and then use the Swype installer to install it again.

You don't say anything about what phone or Android version you currently have. But Android 4.2 includes now a Swype-like gestual typing keyboard.
There is a downloadable version for you to install, if your phone supports it.
Try out the new Android 4.2 keyboard now!


text:
Where does the Play Store store the apps I am currently downloading?
I was downloading Facebook from the Play Store awhile ago when the phone suddenly hanged up so I forcefully shut it down by removing the battery. Now when I re-boot Facebook is no longer in the queue and I need to download it again. Now my question is, where did the Play Store temporarily store it while it was being downloaded? I fear that there's now a rogue incomplete Facebook apk file somewhere that's using up wasted space.

chances are, it is stored in a corrupt format that the phone cannot read. Plug your phone to the PC and do a scan and repair to clear out broken files, that should take care of it.

@forums PCs do not generally have tools to clear incomplete downloads from partitions on Android devices.  /data isn't even accessible without ADB.

ok, I just assumed android automatically scans partitions on reboot and clear out broken files in partitions so its only the sdcard that need scanning. Big files (50mb-up) cannot be stored in phone memory, so when it is interrupted, only scan and repair may be able to reclaim the memory.

The Playstore app usually uses /data/local to temporarily store .apk files while downloading, then installs them from there, and finally removes the temporary download-file (which then went to /data/app). The /data/local directory should be readable by all processes (so no root needed to list its contents), as it is used as a kind of "temporary directory" for a lot of things (you might think of it as a "misnamed" /tmp directory).
This directory should be "cleaned up" on reboot1, so your issue might rather be a broken .apk in /data/app. A new install should solve this anyway. I further recommend using AppMonster Pro -- yes, the Pro version: on each install/update it grabs the .apk file of the installed/updated app and stores away a copy. So in cases like this, you could simply grab a previous version and install it over.
Just for completeness: There seem to be more such "temporary directories" on Android devices. Investigating a dump from a stock 2.2 Motorola Milestone 2, I e.g. also found /data/download. Different devices might use other directories additionally. But that should not affect your Playstore question.

1 I can only base this on one of my devices (Motorola Milestone 2, stock Android 2.2), where I extracted a Nandroid backup stored on my PC. There the init.rc file (which is called during the boot process) a.o. contains the following:
mkdir /data/local 0771 mot_tcmd shell
mkdir /data/local/tmp 0771 mot_tcmd shell
mkdir /data/local/12m 0771 mot_tcmd shell
mkdir /data/local/12m/batch 0771 mot_tcmd shell

Easy to see: the /data/local directory is created during the boot, which suggests it being empty at this point. Same is valid btw. for /data/download

In your opinion it's cleared out?  Do you mean in your experience? :P

I never felt the need to thoroughly check. Whenever I looked, it was empty. But as I never experienced trouble with an aborted install, I cannot say for sure. Not being at my computer when I wrote this, I had no chance to verify what I thought might be behind -- so thanks for the reminder, I'll update my answer...

On my Xperia Ray (ST18i) running ICS, I do not have access to the /data directory. Could the settings be different on Xperia phones or it's an ICS thing?

You don't have full access to the /data directory and its contents unless your device is rooted. Without root, you can access parts of it if you know where they are; you should e.g. be able to directly access the /data/local folder, but might not be able to "browse" the /data folder contents. So with clicky-clicky graphical interfaces, you might have a hard way getting there unless you can input the full path manually :)


text:
Could not enable mobile hotspot function on HTC One X
I am using HTC One X and I was trying to enable mobile hotspot function, so I could enjoy internet from my PC adhoc wireless network but it says :
 There is a temporary network problem that prevents the
 enablement of the Mobile Hotspot function.
 Please retry later.

Looks like you've messed up some terms:

I was trying to enable mobile hotspot function, so I could enjoy internet from my PC adhoc wireless network

First: the mobile hotspot function is to share your Android device's mobile Internet connection to other devices not having Internet on their own, e.g. a tablet or laptop, via WiFi.
Second: only few Android devices support ad-hoc networks. There are solutions, but all of them require your device to be rooted.
Third: if you wanted to use your PC's Internet connection on your Android device, that would be reverse-tether, and again require root to be established.

Thank you @Izzy, can you provide me links for your second and third solution. I have rooted my phone.

Simply click on the relevant tags: ad-hoc-networks and reverse-tether. As those questions are already answered, we don't need to repeat the same solutions again :)

Make sure Mobile network in Settings is ON.
To change timeout time on the HTC One X, do the following:

Settings
More
Portable Hot Spot Tethering
Portable WiFi Hotspot Settings
Menu at top right
Advanced
Power Mode
Always On

Problem solved! Install open garden. It's fabulous. Don't have to root or get a mod Rom. It uses best available option between Bluetooth..WiFi and infra red to keep android phone continuously tethered to your devices. Im loving it

What's your relationship with this app? If you want to recommend or promote it, it might help to include a link.

I faced this problem three days. and Today I'm happy. Because I found the answer. Some Carriers such AT&T (my Case) use to block mobile hotspot feature. You may want to solve it as I did. I flashed/install the ODEX for my HTC ONE (M7, Not ONE X) Stock rom. But solution should be very similar.
Before flashing it, you need to consider prerequisites. (1) Root your device (2) install a Recovery Manager  (I recommend the "TeamWin Projects - TWRP 2.5")
(3) Download the ODEX or DE-ODEX, depending on your current rom.
Please visit the next reference, I did it and it Works :) x 1000
http://forum.xda-developers.com/showthread.php?t=2285047
Good Luck!!!

So, what's the answer? All I see is a link.


text:
how can I change my Facebook account on a app game or how to fix that error?
I am trying to change an account on a app I've downloaded (heart of Vegas slot game) I use to be able to change it before but now everytime I try to log into my Facebook account it won't let me.. It always pops up a warning sign saying ERROR  " you have already logged into one Facebook account on this device . please use same account to continue" I've already tried to uninstall the app and reinstall it, I also tried to clear cache, and also tried to clear data but none is working..
HELP!?


text:
Change orientation in androidx86
How can I fully rotate my screen and not only resize it like in the picture?
In already tried several rotation apps in the play store. I tried via root shell the commands: wm size, settings put system accelerometer_rotation 0 and settings put system user_rotation 0 both are working fine on my phone, but not on my tablet.

You should try some rotation control app from play store, like Rotation Control which can rotate the screen in any direction you want (like reverse portrait)
     But you should also note that it's not possible with every app, because maybe the layout is not provided or the layout is forced to be in portrait mode, in that case no app can help you.
    There ain't much apps available specifically for xxhdpi & xxxhdpi screens and so you're not left with much choice but to work with the way it is....

@Abochur As OP puts, "How can I fully rotate my screen and not only resize it like in the picture?" - what I understand from this is, the situation shown in the picture is what OP has right now, and is not what he wanted. I'd say this answer got it right.

@Abochur On Android-x86 it works differently, since 1) most PCs have a built-in keyboard which is recognized, and Android by default will disable rotation with a keyboard connected (even if auto-rotation is enabled), and 2) many PCs don't have a sensor to detect auto-rotation with in the first place.

That is exactly what I get when I use such a rotation app you mention. I also tried via shell WM size, and settings put system user_rotation.

@AndyYan my tablet, has a rotation  sensor. It works on windows but it seems that android does not recognize it. I also detached the keyboard several times to see if that helps but it does not unfortunately.

Android x86 is not a perfect os for PCs, it has a lot of glitches and this is one of many...

@DhrubaJyotiSaikia so there is no way that this works? Should o try something like RemixOS (but i think it has been discontinued) or PheonixOS (its not very good).

If you ask for my suggestion, then I'd say you should go with Linux, that's pretty amazing, and it'll definitely allow you to use your device to its full potential...

Rotation Control works only properly if in init.sh has_sensors is set to true

I face same problem on chuwi Hi10 x.
Reason was if your tablet orientation sensor is not recognized
Or defined in Android it forces screen in one orientation
To solve this
Open init.sh file which in device root /etc/init.sh
Find the following line
"has_sensors = false" and make it = true
this tell android that you have orientation sensor even if it actually not recognized it
Then reboot
Now you can change orientation using any orientation app.

I did not found any solution. I installed the new PhoenixOS. It works good, and the orientation sensor works too. Maybe we will find a solution for android x86 soon.

In latest version of Android x86_64 8.1 Screen is rotating normally if you select in Grub ... > Advanced Options ... > Vulkan Support


text:
Titanium Backup cannot Backup Accounts
I want to move to a new phone. But Titanium Backup does not work in backing up my accounts. It always says success even though the backup is only 1KB big and has nothing in it. Is there any other app or a manual way to backup the accounts? Or has anyone a fix for Titanium?
To clearify this I'm talking about the accounts in the settings like this:

What accounts are you talking about? Google? Or...?

@beeshyams im talking about the accounts section in the settings. Yeah one example is the google account.

Thanks to the https://github.com/machiav3lli/oandbackupx/ project I found out that the accounts are saved at /data/system_ce/0/accounts_ce.db, at least for me. I then tried, editing this file very careful, but I think there are some dependencies to other things I don't understand yet. Even with the smallest editions my phone got stuck in a bootloop. Also recovering an backup of the file, didn't fix the bootloop. I had to restore a whole nandroid data partition backup.


text:
Storage space running out and I have tried EVERYTHING
I have a cheapo Wayteq xTab-700qci tablet. It just gave me the dreaded

Storage space running out. Some system functions may not work.

message. I tried every solution that I could find but none of them works. These are the parameters:
Internal storage: 1 GB

Available: 68 MB
Apps: 863 MB

Google Play Services: 478 MB
Google App: 46 MB after deleting data but it automatically grows back to 69 MB
Adobe Acrobat, Google Drive, Firefox, FolderSync and iRealPro are the only other apps I have installed besides system apps. All of them take up under 40MB on internal storage because I've moved each to the internal 5.6 GB SD card where it was possible.

I've cleared data and cache for all apps.
The 'System functions may not work' part is true. App updates usually fail because of insufficient space and I'm now getting used to getting 'Google Play Services has stopped' and 'android.process.acore has stopped working' messages right after startup.
What should I do? Is rooting the only solution? Is Android such crap that only by hacking its bowels can I make it usable?

Disable system apps you don't use. If there were updates for the app the space is freed by disabling the app.

A temporary solution is to uninstall Google Play Services. It will be reinstalled (at least it was, for me) when you open the Play Store, but in my case it was only 170 MB after reinstallation, so I reclaimed a lot of space.


text:
What is the size of the Android System app?
On my phone the Android System app is zero in size.
Is this normal or have I been hacked?
Thanks, J

Which system app? System apps are those apps which are installed out of the box and removing/uninstalling may cause errors on future operations. ex: phone, google etc.

Android System is not an app, it's the whole system itself. But if you are talking about an installed Android System.apk it could be a problem (potential threat).

Android System App is only there to represent the Android Framework. If your device is working, you don't have a reason to worry about that.
If that "App" was really of zero size your phone would not even work up until the point that you could actually see its size (= Android would not boot)
Whether you have been hacked is quite a different story, we can't determine that just out of knowing that it shows zero size for you on Android System.


text:
How to resolve boot loop problem on android PumpKinx 10.1" tablet
I've android PumpKinx 10.1 tablet with 5.1 Lollipop android os.
I did take backup of its stock recovery image.
Since there is no custom recovery image for this device I tried to flash it with twrp recovery image. But after running below command, device goes into bootloop.
I've tried many methods but no success.
fastboot flash:raw boot twrp.img

Any help would be highly appreciated. Thanks in advance.
Update :

Every time this screen comes

Then if we go for normal boot or recover mode goes to this screen

Recover mode has these options but none of this is working

You should know that we cannot use a recovery that was not created for that particular device. No one has compiled a custom recovery for your device it seems.. So, the only way is to build a recovery yourself. If you device has Mediatek (MTK) chipset, you can easily create CWM recovery using this method here: http://www.theandroidhow.com/2014/05/how-to-make-flash-cwm-recovery-without.html (You can find out what chipset your device has using apps like 'CPU-Z')

So, is your phone working now? If yes, if your aim is to root your device, try apps like Kingroot or Vroot or Towelroot or whatever......

Thansk @Gokul for spending some time on this questions. No, my tablet is not working please see updates in question.
I've tried with kingoroot, Towelroot non of these were worked for me.

As far as I can understand from your question, it seems you flashed some other device's twrp into your tablet's boot partition. The only solution is finding your device's boot.img somewhere from internet and flash it (it might be inside the firmware file if you found any). BTW, I'm wondering how did you backup stock recovery (without rooting or custom recovery)

I Believe you are using some non branded (fake or Chinese) device and unfortunately the device don't get updated officially. But you can do a couple of things with it first restore and enjoy the previous version, or contact the manufacturers of the device they will send you, your desired ROM, it will take a couple of working days. I had this issue back in the day, all I did to restore it and hard reset. After two days I got an email, but they wanted me to pay for sending me the new ROM.
visit this link you will understand more. http://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool


text:
How do I force Google Photos app to refresh?
I deleted some images on photos.google.com but the Photos app on my phone doesn't reflect these changes and still show the images. How do I force the app to refresh? I already tried clearing cache but that didn't do anything.

Turn the sync on for your Google account. If it still does not update, re-install the app, that should solve the problem.

Sometimes just dragging down just below the notification bar and releasing will give the circling "I'm refreshing" arrows and start the sync.

This doesn't work for me.

You can try one or more of the following:

restart the app.
sign out and sign in your google account again; or, switch to other account and switch back.
restart you phone.
cut off network connection and reconnect it.
clear drive database.


text:
Android 10 Swipe Forward
I am using the new gesture navigation with Android 10 and was wondering if there is a way to have the swipe from the right side to the left trigger a "go forward" action. When I swipe from either the right to left or left to right, it always does a "go back" action. Is this a bug or does Android only support going back with these swipe gestures?

It is not a bug. Swiping to move forward as not yet been implemented natively only swiping to move back

with the new system navigation mode - users can navigate back (left/right edge swipe), to the home screen (swipe up from the bottom), and trigger the device assistant (swipe in from the bottom corners) with gestures rather than buttons.

To use the swipe forward gesture, the app should implement it (ie Chrome).
Gesture Navigation: A Backstory


text:
Any chance to unbrick relocked HTC One M7 with S-on and a old copy of the RUU.zip
Background
After 1 year of use,  the most recent OTA to my HTC One rendered several key features,  including the notification bar and the home and back buttons, unusable , effectively soft-bricking my phone. Although it was still under warranty, I decided to fix the matter myself,  and also try a custom ROM. Unfortunately, I was unable to make a backup with ADB,  because that was one of the functions the OTA update rendered unusable.
First,  I tried a few factory resets,  to no avail. I decided more drastic measures were needed and unlocked my bootloader using the instructions at HTC Dev and installed a custom recovery, ClockworkMod Touch.
I then tried to flash a new ROM, the newest snapshot release of CyanogenMod, via ADB sideload. Unfortunately, I was not aware of the need to change the CID,  and thus rendered main ROM completely non-functional. Around this time,  ADB also ceased to function in recovery, and my device was no longer detected.
A week or so later,  I flashed a different recovery, TWRP and again flashed it with fastboot. This restored ADB functionality, however,  ADB still failed to detect my device in sideload mode, which caused me to be unable to use the Guru Reset tool I managed to download. I then searched for and found a RUU.zip for my CID, VODAP021, at XDA forums. I then tried to flash it. I re-locked the bootloader and tried to flash it with
fastboot flash zip RUU.zip

after putting the phone in RUU mode, which returned
load_file: could not allocate (filesize) bytes

presumably because 1.5 GiB was too much to handle.
My question
Is there and hope of unbricking my phone (HTC M7_ul) now that I can't access recovery or normal ROM, and have a relocked bootloader with S-On? If so how,  and if not,  what do you suggest I do with it?

Comments are not for extended discussion; this conversation has been moved to chat.


text:
Why don't Google services work on Android 4 versions?
For some reason, in recent days I can’t go into either maps or mail from my old tablet, I write there is no connection. Although other applications work fine, the Internet does not complain. Google disabled 4ver. support? I would be grateful if you check for yourself.
ADB LOG
E/CheckinTask(  582): SSL error, attempting time correction: javax.net.ssl.SSLException: SSL handshake aborted: ssl=0x1158a28: I/O error during system call, Connection reset by peer

E/CheckinTask(  582): Checkin failed: https://android.clients.google.com/checkin (request #0): javax.net.ssl.SSLException: SSL handshake aborted: ssl=0x1158a28: I/O error during system call, Connection reset by peer

With the release of Android version 10, Google has stopped support for Android 7 or earlier https://endoflife.date/android

@alecxs That is support of Android OS itself (no changes to AOSP) but not for Google services. E.g. login to Google on devices with less than Android 3 was ended July 2021. And Play services updates for Android 4.1-4.3 were ended in August 2021.

Would updating the certificate help? In Google services, certificates are not built into the apk?

I don't think it is related but as you asked about... https://android.stackexchange.com/q/231025


text:
Could anyone identify this crDroid ROM?
Found some third-party crDROID 7.11 build  that works flawlessly on my phone, g530FZ. However, I couldn't find it listed on any credible sources (such as XDA). Anyone else used this rom or saw any info on it? Details below:

I've been looking for a LineageOS 17.1 build for my phone, G530FZ
Galaxy Grand Prime (or "gprimeltexx") to switch to from LineageOS 18
due to slowdowns and short battery life on newer version.

Decided to search androidfilehost.com to look for "gprimeltexx".

Unexpectedly, the crDroid 7.11 (Android 11) 2021 build for g530FZ (highlighted) showed up in the search. crDroid does not officially support g530FZ

Previously I've searched high and low for crDroid build for g530FZ that is newer than 2018 (xda thread) to no avail.
Scouring the google and duckduckgo for variations of "crDroid 7.11 grand prime" yielded no results EXCEPT this androidfilehost file. Searching for the highlighted rom filename shows ONLY this androidfilehost link in the results.
Since my phone was long wiped anyway, I've decided to download and flash this crDroid rom via TWRP.
Surprisingly, it did flash, and after about 5 min of initialization I was prompted to go through regular Android initial setup (language, etc)
Even more surprises: despite running Android 11 (which has always been slow on the prehistoric Grand Prime), this crDroid rom runs very fast even with all the fancy animations (which mercilessly lagged the device on lineageos 18)

I am tempted to use this rom as my main phone os. HOWEVER, given that it came from a totally random source and has no info on it on XDA, I am naturally hesitant. Could anyone could clarify the following please:
Does this ROM come from XDA or some other credible sources? I've searched on it myself couldnt find anything, but maybe I've missed something that you know. Developer of the ROM is listed as "AaronPhilips101". Does that ring a bell?

install telegram and contact dev

Please note that ROM development is off-topic since Android Enthusiasts focuses on end-users or power-users (but not necessarily developers) solving their issues, so we can't really provide any tutorials about building a ROM.

@AndrewT. Ok, thanks for the tip. Removed the dev part of the question

You can find other files for the same phone from the same developper posted on SourceForge. The developer as posted his telegram link. I think you should follow @alecxs advice and contact him directly.


text:
Any way to format external sd card as FAT?
I've been searching on Google to find a way to format an external sd card in FAT file format, but I didn't find anything. Every links were asking for FAT32 or EXT4.
I use AndroidM. Recovery is TWRP 3.0.2-0 (if my memory's good).
I don't have any computer, so that's why I'm trying to do it on my phone.
Thanks in advance.
Update: my device is rooted.

Have you tried aParted in the Play Store? I don't have a card small enough to test if it does straight fat or only fat32 though, fat12 max out at 32MB and fat16 at 2GB.

@acejavelin yes I did , but unfortunately it doesn't do FAT.

Use mkdosfs or mkfs.vfat commands from Terminal.. See its documentation for usage..

@GokulNC isn't this for FAT32?

No, it also supports FAT16.. Check the docs


text:
Lineage OS 14.1 ROM can't connect to camera
I have recently flashed Lineage OS 14.1 (fortuna3g unofficial build, Android Nougat 7.1.2) onto my Samsung Galaxy Grand Prime Duos (G530H/DS). Everything in working order, except the rear camera. Each time when I try to access camera from other apps(Whatsapp, Banking etc.) OR opening the stock camera app, it gives me "Can't connect to camera" message.
I have tried with 3rd party apps (open camera), some online tutorial fixes (cmfix camera fix for cyanogenmod), restarting camera app, restarting phone, reflashing LOS 14.1 etc.
I went back to stock to verify that camera works fine. There is no hardware issue.
Anybody had similar problem? Were you able to fix it?

This sounds like a bug that you should report to Lineage. There's likely nothing we can do to fix it for you.

wasn't actually hoping anyone would do something to fix it for me... just really hoping someone had the same issue happening to them and would point to something I have not yet tried

Answering my own question.
My particular problem had to do with baseband and device codename, no bugs or problems with the build. For those, like me who were unaware of how this is related.
My baseband version matched the fortunave3g codename. So I should have installed that build of the of the ROM instead of fortuna3g, like I initially had. More information can be found in the device model master thread at xda-dev forums
I was unaware of the relation between the two things. But anticipating issues I had previously downloaded the three available builds (fortuna3g, fortunafz & fortunave3g). So all I needed to to was flash the appropriate build.
Everything is working fine now.
Thanks to all for the attention. Ultimately my problem was lack of awareness.

As this is an unofficial build so most likely this will be a bug in the rom.
Update it to latest build if problem still persists then stick to the xda thread for the rom and wait for the developer to fix it or try fixing it yourself if you have experience in android builing.
Edit: By browsing through xda thread I found this comment. So it seems like there is no camera bug in new builds so you have to just update it to the latest build.
Try clean flash if the problem still persists.

Already have latest build, released on 11th. That comment you point out is in response to my very own post on their forums, in the same thread you linked above.. I am however, still with a camera problem.. Guess i'm out of luck... I was just hoping someone else had the same issue, and maybe a fix... thanks anyway.

Try clean flashing the latest build

This is a common bug in during early stages of android nougat development in custom ROM Lineage 14(cyanogenmod14), which was solved after few updates.
This problem doesn't occur in latest builds.
Possible Solutions:

Try to clear cache of stock camera.
Try to find any Official Nightly Builds(which updates regularly, otherwise contact developer and report the bug).
Try to clean flash(Backup user data, and wipe /system, /data, cache etc. install as new)
Please check whether you can turn on flash light from notification shade.
If you have used adoptable storage(SD card as internal), then check whether camera storage is internal or not.

already found problem.. turns out it has to do with baseband. I just had the wrong build. adding answer right now


text:
Black background on Trebuchet
On my current phone (HTC Wildfire S), with a AOSPA (Paranoid Android) 4.45 ROM, I installed Trebuchet, because Launcher3 lacks features, and other customs lauchers takes a lot of battery, while my current battery is already going down fast.
Here you can see a screenshot of what it looks like:

The background is black.
But it isn't supposed to be black:

How can I show correctly my background?
Edit: Sometimes it show correctly on the bottom:

...
The APK I used was for the OnePlus One and had a MD5 of 2fd1a3e8f5a6ef44d1f14752b4caa5c9.
I installed another APK, coming from this ROM, and everything fixed itself (the MD5 was different: 3f465ccbfe8566479f863582671575c2)

The two APK had the same version number (1.0) and OnePlus One's was 1.97 MB while the working one was 1.9 MB o_0
Akward


text:
How to run Starlink Android app on PC via emulator/VM?
Has anyone successfully run the Starlink Android app on a PC via an emulator or VM?
I know of accessing the web GUI of Starlink by URL with http://dishy.starlink.com/ or 192.168.100.1. However, a lot of features are not available unless configured via the app. In some windows, parts are greyed out with a message stating Edit these settings using the Starlink mobile application for iOS or Android

I have attempted so far with Windows 10 to run Starlink on emulators suggested from here such as BlueStacks, MeMU Play, NoxPlayer, and Android Emulator with Android Studio. I have also attempted to run Android x86 with the steps provided here, but still no success. Each try, the app attempts to load, but then crashes and never fully loads.
I should add that the Starlink app does not appear in my search when I try to find it on an Android Studio emulator with the Google Play Store enabled.

This post that I found leads me to believe there is some kind of check to determine whether it is being loaded on an emulator.
My current specs for my Win10 PC are the following:
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045
OS Build Type:             Multiprocessor Free
System Manufacturer:       Dell Inc.
System Model:              Precision 5560
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz   2.50 GHz
                           [01]: Intel64 Family 6 Model 141 Stepping 1 GenuineIntel ~2496 Mhz
BIOS Version:              Dell Inc. 1.19.0, 3/10/2023
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
Total Physical Memory:     32,492 MB
Available Physical Memory: 12,525 MB
Virtual Memory: Max Size:  65,260 MB
Virtual Memory: Available: 29,946 MB

Is it possible that the Starlink app simply cannot be run via an emulator or VM due to technical limitations?

EDIT:
As suggested in the comments, I side loaded the Starlink app on the android emulator, and I also had crashes. In an attempt that took less than 5 seconds, I only extracted error messages that seem to relate to the Starlink app crash from Logcat from android studio to avoid bloat (here is a pastebin link for full log):
2023-06-13 10:43:18.323  9504-9504  SoLoader                pid-9504                               E  couldn't find DSO to load: libjscexecutor.so
                                                                                SoSource 0: com.facebook.soloader.DirectorySoSource[root = /data/app/~~qoOC8gBYQvkgf0PRhrZKRQ==/com.starlink.mobile-LPC2LUqn-Tbl-QKGoc-Jtw==/lib/x86 flags = 0]
                                                                                SoSource 1: com.facebook.soloader.DirectApkSoSource[root = (/data/app/~~qoOC8gBYQvkgf0PRhrZKRQ==/com.starlink.mobile-LPC2LUqn-Tbl-QKGoc-Jtw==/base.apk!/lib/x86, )]
                                                                                SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib flags = 2]
                                                                                SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
                                                                                Native lib dir: /data/app/~~qoOC8gBYQvkgf0PRhrZKRQ==/com.starlink.mobile-LPC2LUqn-Tbl-QKGoc-Jtw==/lib/x86
                                                                                result: 0
.
.
.
2023-06-13 10:43:20.773  9504-9557  Manish                  pid-9504                               E  createNativeModules
.
.
.
2023-06-13 10:43:20.817  9504-9557  AndroidRuntime          pid-9504                               E  FATAL EXCEPTION: create_react_context
                                                                                Process: com.starlink.mobile, PID: 9504
                                                                                java.lang.UnsatisfiedLinkError: dlopen failed: library "libviro_renderer.so" not found
                                                                                at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
                                                                                at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
                                                                                at java.lang.System.loadLibrary(System.java:1664)
                                                                                at com.viromedia.bridge.module.MaterialManager.<clinit>(MaterialManager.java:58)
                                                                                at com.viromedia.bridge.ReactViroPackage.createNativeModules(ReactViroPackage.java:111)
                                                                                at com.facebook.react.ReactPackageHelper.getNativeModuleIterator(ReactPackageHelper.java:42)
                                                                                at com.facebook.react.NativeModuleRegistryBuilder.processPackage(NativeModuleRegistryBuilder.java:42)
                                                                                at com.facebook.react.ReactInstanceManager.processPackage(ReactInstanceManager.java:1456)
                                                                                at com.facebook.react.ReactInstanceManager.processPackages(ReactInstanceManager.java:1427)
                                                                                at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1338)
                                                                                at com.facebook.react.ReactInstanceManager.access$1200(ReactInstanceManager.java:135)
                                                                                at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1109)
                                                                                at java.lang.Thread.run(Thread.java:923)

It looks like there was a fatal crash when attempting to find libviro_renderer.so.
For those who would like to attempt to recreate this error, drag the apk to the emulator and wait for it to install. Once installed click on the starlink and you should see it display its splash screen and promptly crash/disappear.
Current emulator specs:
Emulator Version: 31.3.13-9189900
Android Version: 11.0 (R) - API 30
AVD Configuration: Nexus_5X_API_30
Host Machine: Windows 10 Pro

EDIT2:
Regarding a different suggested comment from Ramhound, the Android subsystem for Windows 11 also had trouble launching the app.

I will try and follow Andrew's comment with a specific ARM-based image within Android Studio soon.

Have you tried running it within WSA on Windows 11? Viewing the web GUI should worked on any operating system provided the device can reach the Starlink terminal on your network

@Ramhound  unfortunately I do not have access to a system with Windows 11, since I am either running on Windows 10 or Linux.

The app contains libraries for all platform (x86 and ARM both 32 and 64 bit) therefore it is not limited. But it requires Open GL ES 3.0. According to this answer the Android Studio emulator can support that if your graphics driver is supported. What I don't know is if the app simply checks if it is running on an Emulator and then behaves differently.

@kyrlon - You should be able to download a free trial Windows 11 VM directly from Microsoft, enable WSA within the VM, to see if the application will even run within WSA.

@Ramhound That is a suggestion that I might have to try later. Ideally I was hoping for an OS agnostic approach w/ a VM rather than dependent on a specific feature the OS provides.

@kyrlon - You have attempted the only two other methods to run Android applications within Linux or Windows, through a hypervisor like BlueStacks or through Android X86 within a Virtual Machine and you have indicated both those methods DO NOT work. Which leaves you WSA, or accepting the fact, the application cannot run in those environments.

@Robert you can see my update adds a link to a post that mentions some apps are not present in the emulator store. I might have to come to terms that the app is not capable to run on emulators.

What is visible in Play Store or not does not tell you anything about if it will work. Just grab the APK from somewhere else and install it. Then you will see if it work or not.

Welcome to Android Enthusiasts. "Each try, the app attempts to load, but then crashes and never fully loads." you may consider checking the log to possibly see the exact reason why it crashed.

After checking the content of the APK by opening it as a ZIP file, looks like libjscexecutor.so is missing on all architectures (related report on GitHub Issue)? However, libviro_renderer.so is also missing on x86, which is the default installation image, so maybe try with an ARM-based image instead.


text:
How can I remove a device that is displayed when installing an application from Google Play's "Choose a device" list?
I am trying to install an application from Google Play on my Android device, but I see several devices listed in the "Choose a device" screen that I no longer use or own. This range from actual devices to emulators like Virtual android machines and android emulators. In the image below, devices I would like to remove everything except S21_Plus such as Asus ASUS_Z01QD, Verizon SM-G925V, Google SDK_gphone64_x86_64, OnePlus NE2211, etc...

Is there any way to remove the devices from the list so that only my active and currently owned devices are displayed?
EDIT:
I have come across what seems to be a now outdated article that states you can remove the devices within Google Play. However, when I attempted the same I was only given the option to hide and not remove. This was also shown in these steps from Google.

EDIT2:
It seems that even attempting to "hide" any devices besides S21_Plus, they are automatically re-enabled as shown from the gif below. Is this a glitch with Google Play??

You can see and manage all devices registered in your account on your Google device management page.
If you select a device there you can log-off it.

You’re signed in on these devices or have been in the last 28 days. There might be multiple activity sessions from the same device. None of the devices in my screenshot (one is in June) I see in the link that you shared.

@kyrlon had you used always the one Google account you are currently logged-in on the shown devices?

yes. Also I have updated my question from some articles I have come across.

@kyrlon based on my experience with emulators and my older broken devices, AFAIR, you have to log them off (from Google's "Your devices" link in this answer) to remove it from the Play Store.

@AndrewT. I have emulators/VMs that I have destroyed and none of them appear in my "Your devices"


text:
Cannot set my APK MainActivity as the Home Activity via ADB
I am using one these AndroidTV 11.0 S905W2 boxes from Amazon and I could not make my APK the Home Activity via ADB.exe
I am using the following adb command via WiFi as connecting via a USB cable to my PC does not reveal this box.
adb -s 192.168.1.40:5555 shell cmd package set-home-activity "org.mumti.MUMTIG3/org.mumti.MUMTIG3.MainActivity"

Response is "Error: Failed to set default home."
Regarding my APK "MainActivity" aapt.exe output reveals there is a launchable-activity: name='org.mumti.MUMTIG3.MainActivity' so I don't know why adb does not succeed.
The reason adb fails setting my APK MainAcitivity may have to do with a post I read relating to the possibility that my APK is made of Java classes that are spread across more than one DEX file (Dalvik EXecutable) this is a bit of chinese to me and I am not sure if it applies.  I don't have direct control over the building of my APK as it is developed with a hybrid framework (JavaScipt/HTML/ionic/angular/cordova) and an Android/JAVA wrapper is put around it in the build process of an APK.  Perhaps there is a way to tweak the gradle build process and make adb succeed, I don't know.
I tried to increase minSDK to 22 from 21 in my config.xml but I get same error.
        <preference name="android-minSdkVersion" value="22" />
        <preference name="android-targetSdkVersion" value="30" />

Here is the output from aapt.exe
 $AAPT_EXE dump badging "S:/_W/ARP/UPS.ion/SRC/UPS.ion.3/platforms/android/app/build/outputs/apk/release/app-release.apk"
package: name='org.mumti.MUMTIG3' versionCode='29' versionName='0.0.29' platformBuildVersionName='11' platformBuildVersionCode='30' compileSdkVersion='30' compileSdkVersionCodename='11'
sdkVersion:'22'
targetSdkVersion:'30'
uses-permission: name='android.permission.INTERNET'
uses-permission: name='android.permission.ACCESS_NETWORK_STATE'
uses-permission: name='android.permission.ACCESS_WIFI_STATE'
uses-permission: name='android.permission.REQUEST_INSTALL_PACKAGES'
application-label:'MUMTIG3'
application-label-af:'MUMTIG3'
application-label-am:'MUMTIG3'
application-label-ar:'MUMTIG3'
application-label-as:'MUMTIG3'
application-label-az:'MUMTIG3'
application-label-be:'MUMTIG3'
application-label-bg:'MUMTIG3'
application-label-bn:'MUMTIG3'
application-label-bs:'MUMTIG3'
application-label-ca:'MUMTIG3'
application-label-cs:'MUMTIG3'
application-label-da:'MUMTIG3'
application-label-de:'MUMTIG3'
application-label-el:'MUMTIG3'
application-label-en-AU:'MUMTIG3'
application-label-en-CA:'MUMTIG3'
application-label-en-GB:'MUMTIG3'
application-label-en-IN:'MUMTIG3'
application-label-en-XC:'MUMTIG3'
application-label-es:'MUMTIG3'
application-label-es-US:'MUMTIG3'
application-label-et:'MUMTIG3'
application-label-eu:'MUMTIG3'
application-label-fa:'MUMTIG3'
application-label-fi:'MUMTIG3'
application-label-fr:'MUMTIG3'
application-label-fr-CA:'MUMTIG3'
application-label-gl:'MUMTIG3'
application-label-gu:'MUMTIG3'
application-label-hi:'MUMTIG3'
application-label-hr:'MUMTIG3'
application-label-hu:'MUMTIG3'
application-label-hy:'MUMTIG3'
application-label-in:'MUMTIG3'
application-label-is:'MUMTIG3'
application-label-it:'MUMTIG3'
application-label-iw:'MUMTIG3'
application-label-ja:'MUMTIG3'
application-label-ka:'MUMTIG3'
application-label-kk:'MUMTIG3'
application-label-km:'MUMTIG3'
application-label-kn:'MUMTIG3'
application-label-ko:'MUMTIG3'
application-label-ky:'MUMTIG3'
application-label-lo:'MUMTIG3'
application-label-lt:'MUMTIG3'
application-label-lv:'MUMTIG3'
application-label-mk:'MUMTIG3'
application-label-ml:'MUMTIG3'
application-label-mn:'MUMTIG3'
application-label-mr:'MUMTIG3'
application-label-ms:'MUMTIG3'
application-label-my:'MUMTIG3'
application-label-nb:'MUMTIG3'
application-label-ne:'MUMTIG3'
application-label-nl:'MUMTIG3'
application-label-or:'MUMTIG3'
application-label-pa:'MUMTIG3'
application-label-pl:'MUMTIG3'
application-label-pt:'MUMTIG3'
application-label-pt-BR:'MUMTIG3'
application-label-pt-PT:'MUMTIG3'
application-label-ro:'MUMTIG3'
application-label-ru:'MUMTIG3'
application-label-si:'MUMTIG3'
application-label-sk:'MUMTIG3'
application-label-sl:'MUMTIG3'
application-label-sq:'MUMTIG3'
application-label-sr:'MUMTIG3'
application-label-sr-Latn:'MUMTIG3'
application-label-sv:'MUMTIG3'
application-label-sw:'MUMTIG3'
application-label-ta:'MUMTIG3'
application-label-te:'MUMTIG3'
application-label-th:'MUMTIG3'
application-label-tl:'MUMTIG3'
application-label-tr:'MUMTIG3'
application-label-uk:'MUMTIG3'
application-label-ur:'MUMTIG3'
application-label-uz:'MUMTIG3'
application-label-vi:'MUMTIG3'
application-label-zh-CN:'MUMTIG3'
application-label-zh-HK:'MUMTIG3'
application-label-zh-TW:'MUMTIG3'
application-label-zu:'MUMTIG3'
application-icon-120:'res/8X.png'
application-icon-160:'res/u3.png'
application-icon-240:'res/SD.png'
application-icon-320:'res/jy.png'
application-icon-480:'res/D2.png'
application-icon-640:'res/CG.png'
application: label='MUMTIG3' icon='res/u3.png'
launchable-activity: name='org.mumti.MUMTIG3.MainActivity'  label='MUMTIG3' icon=''
feature-group: label=''
  uses-feature: name='android.hardware.faketouch'
  uses-implied-feature: name='android.hardware.faketouch' reason='default feature for all apps'
  uses-feature: name='android.hardware.wifi'
  uses-implied-feature: name='android.hardware.wifi' reason='requested android.permission.ACCESS_WIFI_STATE permission'
provides-component:'device-admin'
main
other-receivers
supports-screens: 'small' 'normal' 'large' 'xlarge'
supports-any-density: 'true'
locales: '--_--' 'af' 'am' 'ar' 'as' 'az' 'be' 'bg' 'bn' 'bs' 'ca' 'cs' 'da' 'de' 'el' 'en-AU' 'en-CA' 'en-GB' 'en-IN' 'en-XC' 'es' 'es-US' 'et' 'eu' 'fa' 'fi' 'fr' 'fr-CA' 'gl' 'gu' 'hi' 'hr' 'hu' 'hy' 'in' 'is' 'it' 'iw' 'ja' 'ka' 'kk' 'km' 'kn' 'ko' 'ky' 'lo' 'lt' 'lv' 'mk' 'ml' 'mn' 'mr' 'ms' 'my' 'nb' 'ne' 'nl' 'or' 'pa' 'pl' 'pt' 'pt-BR' 'pt-PT' 'ro' 'ru' 'si' 'sk' 'sl' 'sq' 'sr' 'sr-Latn' 'sv' 'sw' 'ta' 'te' 'th' 'tl' 'tr' 'uk' 'ur' 'uz' 'vi' 'zh-CN' 'zh-HK' 'zh-TW' 'zu'
densities: '120' '160' '240' '320' '480' '640'
native-code: 'arm64-v8a' 'armeabi-v7a' 'x86' 'x86_64'

Addendum1: I learned about logcat and posting the tail here with
"$ADBW logcat -d -v time > logcat.txt"
I put a pair of ===BEGIN ===END around the lines that I think pertain to failure of set-home-activity.
04-05 12:29:08.014 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}
04-05 12:29:09.116 I/chromium(27522): [INFO:CONSOLE(236)] "12:29    UserActivityTracker.Start. >>D---  this.MinutesOfInnactivity 7", source: https://localhost/build/main.js (236)
04-05 12:29:09.688 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:11.025 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}
04-05 12:29:11.688 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:13.688 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:14.032 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}
04-05 12:29:15.688 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:17.040 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}
04-05 12:29:17.689 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:19.689 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:20.050 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}
04-05 12:29:21.053 I/Finsky  ( 5139): [8519] fyo.run(10): Stats for Executor: BlockingExecutor iar@5bd16ca[Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 25]
04-05 12:29:21.054 I/Finsky  ( 5139): [8519] fyo.run(10): Stats for Executor: LightweightExecutor iar@8b0703b[Running, pool size = 3, active threads = 0, queued tasks = 0, completed tasks = 84]
04-05 12:29:21.689 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:21.823 I/Finsky  ( 5139): [8519] fyo.run(10): Stats for Executor: bgExecutor iar@df3f358[Running, pool size = 4, active threads = 0, queued tasks = 0, completed tasks = 284]
04-05 12:29:23.059 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}
04-05 12:29:23.690 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:24.386 D/CompatibilityChangeReporter(  583): Compat change id reported: 135634846; UID 10055; state: DISABLED
04-05 12:29:24.386 D/CompatibilityChangeReporter(  583): Compat change id reported: 143937733; UID 10055; state: DISABLED
04-05 12:29:24.404 D/Zygote  (  297): Forked child process 6940
04-05 12:29:24.408 I/ActivityManager(  583): Start proc 6940:com.android.permissioncontroller/u0a55 for service {com.android.permissioncontroller/com.android.permissioncontroller.role.service.RoleControllerServiceImpl}
04-05 12:29:24.409 I/Zygote  ( 6940): seccomp disabled by setenforce 0
04-05 12:29:24.428 I/adbd    (28115): jdwp connection from 6940
04-05 12:29:24.470 D/ApplicationLoaders( 6940): Returning zygote-cached class loader: /system/framework/android.test.base.jar
04-05 12:29:24.558 D/NetworkSecurityConfig( 6940): No Network Security Config specified, using platform default
04-05 12:29:24.559 D/NetworkSecurityConfig( 6940): No Network Security Config specified, using platform default
===BEGIN
04-05 12:29:24.589 I/CarUiInstaller( 6940): CarUiInstaller started for com.android.permissioncontroller
04-05 12:29:24.618 W/Role    ( 6940): Cannot get ApplicationInfo for default holder: com.android.messaging
04-05 12:29:24.633 W/Role    ( 6940): org.mumti.MUMTIG3 not qualified for android.app.role.HOME due to missing RequiredComponent{mIntentFilterData=IntentFilterData{mAction='android.intent.action.MAIN', mCategories='[android.intent.category.HOME]', mDataScheme='null', mDataType='null'}, mPermission='null'}
04-05 12:29:24.633 E/RoleControllerServiceImpl( 6940): Package does not qualify for the role, package: org.mumti.MUMTIG3, role: android.app.role.HOME
04-05 12:29:25.690 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
===END
04-05 12:29:26.070 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}
04-05 12:29:27.690 E/ocessService0:(27600): failed to create Unix domain socket: Operation not permitted
04-05 12:29:29.082 E/WifiVendorHal(  583): getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_UNKNOWN, .description = unknown error}

Have you checked adb logcat if it displays more details why the command fails?

I'd assume Android TV expects Leanback support, though I don't have any experience with it either.

@Robert I looked up "logcat" command and updated the post thank you.

Your app is not built to use Roles. To be set as home activity (technically a home launcher) by that cmd package command this app has to have HOME role provisions coded in. It is failing that test (see error at 04-05 12:29:24.633 and later). See HOME role in Android Roles if you are a developer keen on fixing this problem (don't know how). Failure occurs here

@Firelord I browsed the folder platforms\android\app\src\main and found AndroidManifest.xml (probably auto generated by this ionic hybrid framework to target Android) I could post as I don't know how to correctly add to it this ROLE and leanback support requirements.  Alternatively could you point me to a "skeleton sample" Kotlin project that I could tackle to be the main launcher and in turn launches my APK?  Thank you so much.

Just a note that app development is off-topic since Android Enthusiasts focuses on end-users and power users (who are not necessarily developers) solving their issues. Thus, while the community might explain the technicality of Android OS to your queries, coding solutions are out of the scope of this community. For programming questions, you might want to try [so].

Like Andrew said you'd have to ask about this at [so]. I don't know how to fix this problem either.