I am using a One Plus 9R and somehow I cannot see the call history for callers.
In all my past Android phones I used to be able to get a list of past call times and durations etc by clicking on a particular caller name.
Any idea what could be wrong? I seem to be having the "Phone by Google" app installed and presumably that's my dialer.
I tried clearing the cache for that app. Anything else I should be trying?
You can use Servers Ultimate (com.icecoldapps.serversultimate) from Ice Cold Apps to ran VPN Server on your Android device. But it has limitations:
download and extract ROM from https://www.xda-developers.com/samloader-download-updates-samsung-galaxy
cd /media/xubuntu/1234567890ABCDEF
sudo apt update
sudo apt install android-sdk-ext4-utils android-sdk-libsparse-utils android-sdk-platform-tools-common android-tools-adb android-tools-fastboot f2fs-tools git python3.8 python3-pip
git clone https://github.com/nlscc/samloader
cd samloader
pip3 install .
cd ..
sudo cp -av ~/.local/bin/samloader /usr/local/bin
mkdir Android
cd Android
samloader -m SM-G531F -r SLK checkupdate
samloader -m SM-G531F -r SLK download -v G531FDDU1APJ2/G531FODD1APJ2/G531FDDU1APJ2/G531FDDU1APJ2 -O .
samloader -m SM-G531F -r SLK decrypt -v G531FDDU1APJ2/G531FODD1APJ2/G531FDDU1APJ2/G531FDDU1APJ2 -V 4 -i SM-G531F_1_20161116150254_w0xdzpk60j_fac.zip.enc4 -o SM-G531F_1_20161116150254_w0xdzpk60j_fac.zip
unzip SM-G531F*.zip
tar -vxf AP_G531F*.tar*
convert https://github.com/anestisb/android-simg2img into mountable disk image
mv -v system.img system.sparse.img
file system.sparse.img
simg2img system.sparse.img system.img
file system.img
(optional) check if mountable
mkdir system
sudo mount -vo loop,ro,noexec,noload,noatime -t ext4 system.img system
ls -a system
sudo umount -v system
copy file to MicroSD Card
adb push system.img /external_sd
(optional) compare digest
md5sum system.img
adb shell md5sum /external_sd/system.img
write disk image from terminal dd
adb shell
find /dev/block -name by-name
ls -l /dev/block/bootdevice/by-name/system
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system
reboot recovery
disable dm-verity and recovery-from-boot.p (necessary for TWRP)
adb disable-verity
adb shell
mount -w /system
mv -v /system/recovery-from-boot.p /system/recovery-from-boot.bak
The issue got fixed, the issue was with the ROM. I had flashed a stock ROM from ASUS' website a month or so ago and due to that even factory resetting didn't help. I flashed a new Pixel Experience ROM on it by unlocking the bootloader and it fixed the issue. I'm now getting full speeds, 50 Mbps+
There is no revenue-generating stream for Linux on smartphones in comparison to Android.
Just porting Linux to SoC is not enough. Linux is only a kernel.
You will need to develop a distro suitable for a smartphone.
Android = 1. AOSP + 2. patches and blobs from SoC vendor + 3. user apps`
#2 in the equation has restricted access. SoC vendors don't share internal details even with OEMs, only providing a minimum description for available APIs. Typical Android-capable SoC has a lot of proprietary peripheral modules (such as mentioned GPU or Audio, Image processing, radio modules). Some of them require OS drivers, others even specific complex FW with a separate OS. Even for some desktop peripherals, this factor blocks Linux support.
There were attempts to develop an open-source smartphone. As we can see, they didn't get widespread till the moment, and some of the projects were discontinued. The main reason is the same: the model didn't prove its sustainability.
I have https://play.google.com/store/apps/details?id=com.appstar.callrecorderpro&hl=en&gl=US installed and it is recording phone calls, which I can see in the application. I would like to see these files in filesystem too. Where are they?
I see location Internal storage/CallRecordings, but it contains only few very old recordings, no any new ones.
I installed:
USB debugging & OEM unlock are on.
With the phone turned on everything runs fine. I can copy files onto the device and it shows up in adb and the device manager just fine.
But when I go into the bootloader, fastboot does not list or recognize the device and I noticed in the Device-Manager the phone shows up like https://i.imgur.com/Y4s4EEv.png . Idk if this is normal or not, but I'm out of ideas.
Any help would be much appreciated.
My answer to https://android.stackexchange.com/q/213045/218526 explains the role of Android's mDNS Daemon which is an init service, started on demand. It provides https://en.wikipedia.org/wiki/Multicast_DNS (host/domain name resolution) and https://en.wikipedia.org/wiki/Zero-configuration_networking#DNS-SD (DNS-Based Service Discovery); both part of Zero Configuration Networking.
Technically it's possible for DNS-SD to use the old unicast DNS to resolve the domain name found in the SRV record (of a broadcasted service) to an IP address. But mostly mDNS and DNS-SD are bound to each other. And this is the case with Android.
Android doesn't expose any setting or API to do only the name resolution (as mDNS Responder or Querier) and not the service discovery. Neither the https://android.stackexchange.com/a/218209/218526 uses mDNS. Android's mdnsd serves as mDNS broadcaster / responder only to DNS-SD service. You cannot use either of the both independently (as to my knowledge).
But there are a few options:
Run an app on your Android device with a discoverable service (even a dummy), which uses Android's official API (which in turn interacts with mdnsd underneath) to https://developer.android.com/training/connect-devices-wirelessly/nsd.html#register and https://developer.android.com/training/connect-devices-wirelessly/nsd.html#discover services. So any other host on the local network with mDNS/DNS-SD capability can discover the service. For instance use https://www.systutorials.com/docs/linux/man/1-avahi-browse command on a Linux system. Resolving the service provides the IP address of the Android device.
When mdnsd is running, Android device is already broadcasting itself with a https://android.googlesource.com/platform/external/mdnsresponder/+/refs/tags/android-11.0.0_r1/mDNSPosix/mDNSPosix.c#489 : Android.local. If you don't want to broadcast a service, there's another option.
ADB relies on mDNS to discover devices on local network by registering a service of type _adb._tcp (see references https://android.googlesource.com/platform/system/core/+/refs/tags/android-11.0.0_r1/adb/daemon/mdns.cpp#45 , https://developer.android.com/things/hardware/raspberrypi.html#step_2_connect_the_hardware and https://source.android.com/devices/automotive/virtualization/tools ). So enable "USB Debugging" in Developer Options and you'll see mdnsd running on your device.
Or on a rooted device start mdnsd alone, without starting ADB, by executing setprop ctl.start mdnsd or simply start mdnsd.
In both above cases, when mdnsd is running, executing https://www.systutorials.com/docs/linux/man/1-avahi-resolve-host-name Android.local on a Linux PC should return IP address of your Android device.
In case of name conflict, as the name Android.local is hard-coded, the Android device which joins later automatically renames itself to Android-2.lcoal, Android-3.local and so on (see reference https://android.googlesource.com/platform/external/mdnsresponder/+/refs/tags/android-11.0.0_r1/mDNSCore/DNSCommon.c#940 ). So you can resolve the names accordingly.
Coming to the next problem, what if your OEM/ROM developer removed or modified the mdnsd service, or if you want to run with a name of your choice, not the hard-coded one?
Build and run your own more configurable mDNS responder like https://github.com/lathiat/avahi on Android device.
Even simpler, patch and rebuild Android's mdnsd to receive a commandline argument for name, or read from a config file if exists.
No, it doesn't need a rooted device. The patched mdnsd binary should run fine from adb shell, or even on a terminal emulator app like Termux. As of this writing, there's only one syscall in https://android.googlesource.com/platform/external/mdnsresponder which the seccomp blocks for apps. But it can be removed easily. Neither the DAC or MAC block the execution.
If your pet is not in range to pick it up then yes, the loot is lost. There is no "loot recovery" features in Lost Ark. you pick it up or you lose it.
I saw this in a an old movie (the movie has been made about 20 years ago). Here is a screenshot:
And https://youtu.be/y7SUNPGggdo?t=33 is a YouTube video from the moment the game has been played in the movie.
Research level is based on the checkmarks on the screen, not just based on the number caught (although that number is usually one of the things that gives you checkmarks).
Further, the https://pokejungle.net/pokemon-legends-arceus/pokedex-research-level-guide/ - so you got:
Resulting in 10 points.
According to https://manuals.playstation.net/document/pdf/CFI-1015A-1.0_1.pdf :
Charge your controller
With your PS5 console turned on or in rest mode, use a USB cable to connect your controller to the console. When your console is in rest mode, the light bar on your controller slowly blinks orange. After charging is complete, the light bar turns off.
Emphasis mine.
In other words, since the orange light blinks once and turns off, that means your controller is already fully charged.
As for the different behavior on Mac, unfortunately the official manual doesn't really provide a list of colors and blinking patterns, but according to https://appuals.com/ps5-dualsense-controller-lights-guide/#:%7E:text=DualSense%20is%20Connected%20to%20a%20PC :
Orange with White Light
This is the default color scheme that your DualSense controller will stay in while connected to a Mac, iPad, iPhone, or Android device.
Which means everything is working as intended.
Since you never mentioned actually using the DualSense, we can only assume that it is working properly, and that there is no problem with it at all.
I have searched internet archives.... it's easy to get the entire game, but almost never the soundtrack. Soundtracks from old games are vanishing quickly - Bounce Tales, Guitar Rock Tour 2, etc...
Here are several simple things that may help:
I don't know about increasing the total spawn rate of zombies but you could increase the concentration of hostile mobs by lighting up nearby areas as this forces the hostile mobs to only be able to spawn in the dark areas that you want them to spawn in.
Alternatively, you could build the area in which you want zombies to spawn in the air to make sure that you only load in the platform so that hostile mobs can only spawn on the platform. If you you this method you will need to be at least 128 above the highest point on the ground to increase efficiency.
You could also increase the tick speed thus increasing the amount of mobs spawning
Here is a slightly more complex way that works on Java but I am not sure about Bedrock:
Here is a link for more details:
https://gaming.stackexchange.com/q/354068/277689
If possible, as commented by several people, could you be more specific and give us more information about why you need this for, whether you have access to command (which I assume you do as it is a tag) and several other factors that could help us help you.
I recently collected and assembled the three pieces of the Rainbow Sword. I equipped the item and started a level, but the Rainbow Sword icon was blacked out when I tried to use it.
The Rainbow Sword description says it fires a rainbow blast when powered, but doesn't explain how to power it. How do I use the Rainbow Sword?
Is it really all just luck? I have heard that there is a guaranteed heirloom after 500 packs, but I've opened a bunch- I don't know how many. Still, I was wondering what I can do to raise my chances without wasting all my money.
The possible inconsistencies introduced by "The Crane Returns on the Wind" were indeed noticed by the developers and so completing the quest earlier produces some changes in the game.
Specifically,
the quest "Fishing for Jade" gets altered to mention that "while the Jade Chamber has been rebuilt, pieces of the old one are still floating in the water. "Return of the Jade Chamber?" has the dialogue changed so that the items you are sent to retrieve will be used for internal decoration instead that for the reconstruction.
The altered versions of the two quests can be seen on Youtube here:
https://www.youtube.com/watch?v=_iQzlTjij5g
https://www.youtube.com/watch?v=tjraTgSgn_Y
To evolve Feebas you are required to set it as your buddy and walk a minimum of 20km with it. Once you have completed this task, you can then freely evolve it.
The notification you are receiving about choosing to evolve it, is only in regards to the https://en.m.wikipedia.org/wiki/Pok%C3%A9mon_GO_Battle_League . There are "caps" of 1500 CP, and 2500 CP. Evolving your pokemon may automatically boost their CP beyond one of these caps, which is unavoidable.
There is nothing in regards to this choice being "too late", as this is standard practice for Feebas/Milotic evolution
I think you're reading the "learn engravings" screen (your first screenshot) in Hephaistos's Workshop wrong. This seems to display the list of engravings (and levels thereof) that you're eligible to learn, not those that you already know. Looking at the other engravings available in the displayed screenshots, it looks like every single one is one level lower than what you see in the "learn engravings" screen, not just the two you circled. The Inventory screen (your third screenshot) shows the ones you know, and this seems to match the Engraving screen.
According to the https://cookieclicker.fandom.com/wiki/Garden#Bakeberry :
Additionally, it's important to note that bakeberry harvesting rewards are capped at just 3% of your current cookies, so they should ideally only be harvested when you have loads of cookies saved up to get a bigger reward. (In order to get the full reward from all your bakeberries, you'd need to have at least 16 hours 40 minutes worth of CpS sitting there in your bank.)