I am trying to flash TWRP into my Samsung Galaxy A8 (2018) based on official instructions from: https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-roms-kernels-recoveries--other-development/recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201 I have followed the instructions carefully and repeated several times. I initially tried things on linux with adb and heimdall, however heimdall was failing to flash, so I returned back to the exact Windows instructions using Odin3 v3.13.1. When I try to flash twrp-3.4.0-0-jackpotlte.img.tar into my Samsung Galaxy A8 (2018) aka SM-A530F, Odin fails consistently with this log: Added!! Odin engine v(ID:3.1301).. File analysis.. Total Binary size: 35 M SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. NAND Write Start!! SingleDownload. recovery.img RQT_CLOSE !! Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1) Removed!! I believe my phone is not RMM locked because I see Developer Options in my settings. I tried the process with OEM unlocking enabled and disabled in my phone Dev Options. No success yet. I googled the issue for a few hours, however people mostly report seeing RQT_CLOSE when phone is RMM locked, which I believe is not my case. Maybe this is related to the recent Android update I installed yesterday. Phone software: Android 9 Baseband version: A530FXXUECTH1 Kernel version: - 4.4.111-19323942 - #1 Mon Aug 3 15:36:52 KST 2020 Build number: PPR1.180610.011.A530FXXUECTH2 Security patch level: August 1,2020 Security software verion: - ASKS v3.1.1 Rlease 20200120 - ADP v3.0 Releasae 20191001 - SMR Aug-2020 Release 1 What does RQT_CLOSE actually mean? Could you please help investigate?

And I don't mean the Screen Timeout or the actual phone lock. I have a Samsung Galaxy A8 running Android 9, and since I found out it hasn't been updated since 2018, AKA before OneUI, I decided to do it. But since that update, when I don't touch it for a bit, LESS than the ten minutes I set the screen timeout to be, the phone screen get dimmer and lock itself with a 'drag to unlock' message. It is annoying as I am using a third party program to help me grind in a mobile game, and what it feels like every five minutes I need to unlock the phone screen so that it can keep working. The screenlock must be new because it didn't happen before I updated it. I tried to see how to turn that off, but all I find is the Screen Timeout and the phone's actual lock, same for google searches. I can't find ANYTHING on this screen lock. Hell, even the 'Don't go to sleep while plugged it' dev setting doesn't stop it. Edit : Added a picture to show what I am talking about.

I'm currently in the process of transferring my old phone's (Samsung Galaxy A8) settings, data, media etc to the new one (Samsung S22 Ultra). The Samsung **Smart Switch** app *does* transfer things like the apps themselves, the home screen layout, photos etc just fine. However, preferences and bookmarks in (at least some) non default apps do *not* seem to transfer. One example is the national news app, NOS . Smart Switch has transferred the app itself, however none of my settings or news bookmarks (I have a few hundred) can be found on the new phone. Other examples: PostNL , Buienradar and Calls Blacklist . PostNL for example does allow you to log in, but past deliveries and mail history disappear. Other apps only run locally, without an account, and are therefore stuck on the old phone. I've found that this lack of data/settings transfers applies to all of the non-default apps I've opened so far. In some cases *some* data can be transferred by logging in (if possible), but *historic* data does not seem to transfer. I assume all of these end up being files in the internal memory structure however. So, is there a means to (relatively painlessly) **transfer these to the new phone**? Note that the new phone uses Android 12, and a recent comment suggests that adb based solutions may not work. I also get the impression that Titanium Backup (which would additionally require rooting) may not work as smoothly anymore based on recent reviews. PS. The **samsung-galaxy-s22** tag does not exist yet, I'd appreciate it if someone with sufficient reputation could create this. Thanks!

I have problem with KG State prenormal on my Samsung Galaxy A8. So, I installed TWRP, after I installed SaboorROM, and after connect to WiFi, the device set's the KG state to Prenormal and I was unable to boot into TWRP or into SaboorROM. So I installed Stock ROM (AP: A530FXXSBCTC4 | CSC: A530FODXBCTC2). After install I enabled Developer settings and OEM was already unlocked. So I tried to "date|time changing experiments" to reach KG state checking, but nothing worked. Than I was about 500 hours if KG state will change, nothing :/ OEM: unlocked FRP: unlock KG: prenormal Binary: 11 Android: Pie **How to change KG state?**

I need to turn off CPU cores in order to make energy measurements of sets of cpu cores in isolation (meaning that I want to run an application on a set of cpu cores and turn off the cpu cores that are not in the set). I looked at the documentation on the [android linux kernel source](https://android.googlesource.com/kernel/common/+/refs/heads/android-4.4-p/Documentation/cpu-hotplug.txt) and it says the following: > Q: How do i logically offline a CPU?
A: Do the following.
#echo 0 > /sys/devices/system/cpu/cpuX/online
Once the logical offline is successful, check
#cat /proc/interrupts
You should now not see the CPU that you removed. Also online file will report the state as 0 when a cpu if offline and 1 when its online.
#To display the current cpu state.
#cat /sys/devices/system/cpu/cpuX/online
But when I write 0 to the online file, it still reports the CPU as being online even with superuser permissions and marking the file as writable (chmod +w). I imagine that the kernel is enabling the cpu again after I disabled it. Also I did not try to turn off CPU 0 because in the same documentation it says that it's not removable in some architectures, this behavior is happening on other CPUs. Do I need to rebuild the kernel in order to enable the cpu hotplug or is this an architecture specific problem? Maybe my cpu doesn't support hotplugs. **What I've tried by now** - Writing to /sys/devices/system/cpu/cpuN/online with a rooted device. (echo "0" > ./sys/device/...../online) - Changing the kernel to a custom one and trying the step above again. (Kernel installed was Quantum Kernel) - Using [kernel adiutor](https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en) to turn off the CPUs on the CPU tab (this turns off the CPU for a while then it turns back on again) - Using su on adb shell to change file permissions on sysfs (chmod 664 /sys/devices/...../online) and then trying to write to it. **Device Information**
**Model:** Samsung Galaxy A8 (SM-A530F)
**Android Version:** Android Pie (9)
**Kernel:** Quantum Kernel V4
**Kernel version:** 4.4.111-Quantum_pie.V4.0-A530F
**Processor:** Samsung Exynos Octa 7885
**Architecture:** aarch64
EDIT: Forgot to mention that my device is rooted.

I'm trying to setup Samsung Pay on a new Galaxy A8 2018 but I get this error message every time, even after re-installing Samsung Pay and resetting the phone as well as clearing Samsung Pays data. > **Connection Error** > > Unable to connect to Samsung Pay temporarily. Try again later. I've looked through the Samsung Account data and entered all I could. The phone has "Magyar" as default region when I start it, could that be it? I don't have any SIM card in it but when I try putting one in I still get the same error message. " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy">

My phone, Samsung A8 2018, sometimes vibrates without there being any notification. I've noticed this since yesterday. The two new things which yesterday changed about my phone are: I updated my phone and I started playing games through facebook. I've reset my phone's notification settings and at least one of the games does also send notifications when something happens. The other one doesn't, but I haven't noticed any correlation between the virbations and something happening in the game. Smart Alert is turned off. Something which might be irrelevant: permissions for certain apps (Whatsapp and Snapchat) got reset, either after the update or after resetting notification settings. What causes these vibrations without notifications? Is there any way to check what causes a vibration?