yashsingh1/xdaforums huggingface dataset:
[Honor 4x Questions & Answers] Elguevara:
1. ¿Qué versión de Android tienes?

2. Tener el cargador de arranque desbloqueado no debería causarle ningún problema.

3. ¿Ha probado el método forzado con el teléfono apagado, instalando la rom presionando los 3 botones al mismo tiempo, teniendo la rom en la carpeta de descarga dentro de la tarjeta SD?

4. En este video tutorial se encuentra la rom kitkat que te permite actualizar con el método de instalación de 3 botones lollipop y marshmallow, también tiene los enlaces de las 3 roms para descargar.

5. He instalado la rom de p8 lite Ale-l23 en mi Gplay G735 / honor 4X Che2-L11 de un sim, instalando la rom kitkat del tutorial y luego la marshmallow de p8 lite ale-l23, y la actualizo a la versión B601 instalando twrp de p8 lite, tengo las funciones del p8 lite como aplicación gemela, descanso visual y activar otras funciones como; botón de bloqueo en la barra de navegación, ventanas múltiples y otros.
[Honor 4x Questions & Answers] Moka-retaj:
Thanks.but i do everything.. But every thing was failed.. Are you have a box soft to do any thing

Thank you again
[Introductions] Kingkillr88:
Hi guys I'm kinda new to this but I'm here to learn give away any knowledge I have so I can better understand rooting and customizing phone
[Introductions] orb3000:
Welcome aboard!

What device do you have?
[HTC Vox] smccaldin:
Does anyone know how to change the keyboard layout on the Vox/S710 to match the S730.

E.g. Shift the top row of letters (QWERTYUIOP.) to (.QWERTYUIOP) so that typing is more natural?

Hope that makes sense! Any help greatly appreciated.
[HTC Vox] Pikranus:
Hmm... My Vox comes with .QWERTY layout. Anyway, I think you should change the locale in system registry. Try this key (make sure you've created a registry backup first):

HKLM\HARDWARE\DEVICEMAP\KEYBD

Set the value "CurLang" to 0x409 (1049) and reboot the phone. That will probably shift your layout.
[HTC Vox] ant1012:
wont this just complicate things as ur keys will be messed up. so the letters will be:

.qwertyuiop

but the buttons on the actual keyboard will say:

qwertyuiop.

way more trouble than its worth
[HTC Vox] smccaldin:
Maybe... but I keep making mistakes when typing, as I'm assuming that the keyboard layout is as per a normal keyboard (or Hermes, which is what I used before).

The fix works nicely - for the top row.

But...

Now the number keys are not 'aligned', as per the layout on the keyboard. Is there a way to move these - bearing in mind that the numbers are used using the 'fn' lock?
[HTC Vox] Pikranus:
You might want to try creating your custom layout. With AEKMap you can do most anything with hardware keys. Here it is.

It would take a lot of time to create a layout from scratch, so I suggest using my (Roan) or other people's layouts as templates.

Hope this helps.
[HTC Vox] Phrak:
Sounds like it's more trouble than it's worth. Depends on how much your personal (or work?) time is valued at I guess..

Just deal with it and get used to the keys. I'd expect it to be different to your Hermes, it's a different phone!
[Android Auto General] RKCRLR:
I use Screen2Auto on an unrooted phone which only seems to work on AA 6.4 or earlier.

Some people have commented that they are being forced to update AA to 6.5.

I had a notification that said something about a required update to AA. I tried to read it but it just took me to the AA update page in the PlayStore.

Are some people being forced to update AA?
[Android Auto General] syphen6:
I was forced to update now I'm trying to find a workaround.
[Android Auto General] itamarbh:
Yes.

Do not proceed, un-install the latest update of Google Play Services.

If already installed the AA update, so remove the update of play services and re-install the old version of AA from April.

All good.
[Android Auto General] RoyRomeo:
I uninstalled the latest update of Google Play Services and rolled back Android Auto to version 6.3, but Android Auto will not work unless you hit the update button.
[Android Auto General] blzj8:
it's not that I'm sitting here wearing a tin foil hat or anything.. but I think we should discuss workaround methods in private messages. Google obviously has some form of eyes watching these forums because everytime a workaround is discussed it magically gets patched not soon after. 🥸🤫🤐
[Android Auto General] mangio85:
Dear friend, you have news? ... I will have to take a long drive with my son. Can you help me?

forced to update..6.5.612134
[Android Auto General] sosimple:
Any work around?
[Android Auto General] RKCRLR:
So far, my Galaxy S7 (G930V) on Android 8 is still working with Android Auto 6.4.

I've gotten notifications that I will need to update soon but they haven't cut me off yet.
[Android Auto General] JLPDA:
I also have a non-root Galaxy S7 (G930V) on Android 8. Uninstalled AA last year as I've been screen mirroring using USB to my BMW MMI (no touch screen). If I now install AA (6.5 from Play Store), then I won't be able to install S2A with AAAD at this point? Should I try to find and load AA 6.4 and attempt the S2A install or wait to see if they'll be an update to S2A and AAAD that works with AA 6.5?
[Android Auto General] RKCRLR:
I was incorrect about the Android Auto version on my non-rooted G930V. I'm actually on version 6.3.611324.

I couldn't get my phone to work with AAAD. I installed S2A using ADB per the Automatic method instructions on the inceptive.ru website:

Установка программ Android Auto на телефоны без рут

Установка программ Android Auto на телефоны без рут

inceptive.ru
[Android Auto General] lokeshguniganti:
I've workaround for this issue. ping me directly for solution
[Android Auto General] ludovico1973:
Hi,

can you let me know the solution? I've got the same issue with my AndroidAuto&Screen2Auto

Thx
[Android Auto General] Thanos19801980:
Can you let me know the workaround please
[Android Auto General] songmiao88:
Mod Translation

Hi, can you tell me the solution? Thanks

You

Original

嗨，你能告诉我解决方案吗？谢谢

你
[Android Auto General] Thanos19801980:
Your reply is the same as my question. Is it possible for you to help me with my original question. Thank you
[Android Auto General] lokeshguniganti:
Hello all,

My workaround for force update is

You need to Clear Data of Google play services app just before connecting to the car.

Remember, Every time you connect to the car 😊
[Android Auto General] SOFO888:
One question about this: does it download app data afterwards during your drive?

Additional question: can you also clear data and cache after being connected to Android Auto? I would prefer a Tasker task to do this for me. The idea is to clear data and cache as soon as I get connected to Android Auto.
[Android Auto General] mike.s:
Is your tinfoil hat borken? If so, just use the AM/FM radio or cassette player. If you want "free" from Google, you have to pay. Seriously, they make money by trying to target advertising at you.
[Android Auto General] SOFO888:
What do you want to say me?

Tasker is an app which can automize things. For example it can automize the clearing of cache and data.

I wanted to clear data and cache automated so that I don't have to do all the clicks by myself.

I just want to know if I have to program the task to clear data and cache every day or everytime I connect to Android Auto...
[Android Auto General] Macusercom:
I think there is no need for tinfoil accusations. Everyone uses their devices differently and has different tasks. Some have Android Auto, others prefer having a classic AM/FM radio (and if you've seen the series Superstore you'd know how Dina does not have any music capable device in her car but sings the songs herself) 😉

Also nobody was asking for free stuff. If you have an issue that can be fixed by automation, why not get Tasker, support a great developer and deal with it yourself instead of having to wait for Google to fix it 🙂
[Android Auto General] lokeshguniganti:
Yes it'll download app data after driving 🚘.

No, we should clear data before connect to the car 🚙
[Android Auto General] SOFO888:
Thanks a lot.

I have an idea now how to automize the data and cache clearing.

Step 1: as soon as the car gets connected to the AAWireless Bluetooth, clear cache and data and set car mode to off.

Step 2: wait until clearing is done.

Step 3: turn car mode on and continue with the connection procedure.

I guess I will have to play around a little with the wait time and the timeout time of AAWireless.
[Android Auto General] SOFO888:
I tried to make a tasker script.

Right now the timing is a little bit problematic. Everything gets cleared and after 30 seconds or so Google Play Services is updated again. If I do not get connected to Android Auto in this time, it's too late.

Perhaps I find a way to turn off data until I am connected to Android Auto.

Moreover, I think I really have to play around with the wait times in each step.
[Android Auto General] SOFO888:
Another question: did someone try to use Netguard to block internet access for:

- Google Play Services

- Google Play Store

?

Of course it is necessary to test out which apps are affected by this.
[Google Pixel 4a Questions & Answers] TechX1991:
So, at first, I thought it was my computer because I was running the leaked Windows 11, but now its doing it with windows 10 as well. I was trying to install GrapheneOS (bootloader unlocked, done this countless times, tried different cables) but for some reason whenever it gets to

Writing sparse 'system_b' 4/10 FAILED (remote: 'Operation not permitted')

I get this with google's Flash-All for flashing to stock, I get this on GrapheneOS, I get it with GSI images. Seems like its always step 4 on the ROM. Not sure what's going on here. Stuck at bootloader currently. Recovery states android 11.

I'm about to attempt to flash with Chrome via google's online flash tool

Update: Flashed GrapheneOS "successfully" with chrome through their online flasher... but then start up error is "error setup km". Fresh install of win10

Update2: Fixed. Flashed the OTA image from google via stock recovery with adb sideload
[Android Q&A, Help & Troubleshooting] Beytullahcan61:
Hi guys. I am new about kernel developing..

I need really good guide for using wsl ( set up etc)

And need which proton clang i have to use , how to use and

Compile it..

I really need help please
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
>> crDroid Features <<​

-Installation instructions-

1. Download the ROM and GApps and transfer them to your device.

2. Boot to recovery (TWRP recommended).

3. Do a full backup of your device

4. Wipe the System, Cache, Data and ART/Dalvik cache. (Recommended)

5. Flash the ROM Zipfile.

6. Flash the GApps (optional, needed for e.g. Google Playstore to work).

7. Flash the root solution of your choice (optional).

8. Reboot your device.

TWRP 3.7.0 SM-T350 IMG DOWNLOAD​

TWRP 3.7.0 SM-T350 ODIN DOWNLOAD​

TWRP 3.3.1 SM-T350 DOWNLOAD​

If you are having problems flashing this ROM you are most likely running into issues other members were having with the device most of which were already solved, please spend some time reading through this post of other posts related to this device.

-Backlight issues-

Read this post https://xdaforums.com/showpost.php?p=83488241&postcount=41

Thanks

CrDroid Team

Evervolv Team

XDA:DevDB Information

crDroid Android, ROM for the Samsung Galaxy Tab A series

Contributors

nubianprince

ROM OS Version: Android 11

ROM Kernel: Linux 3.10.x

Based On: crDroidAndroid

Version Information

Status: Stable
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Reporting Bugs

DO NOT Report bugs if you're running a custom kernel

Grab a logcat right after the problem has occurred. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)

If it is a random reboot, grab /proc/last_kmsg.

What is the issue?

Attach or link the file.

Working

Audio (Tested)

Bluetooth (Tested)

Wifi (Tested)

Face Unlock (Tested)

Camera (Tested)

Netflix (Tested)

Not Working

You tell me

F.A.Q

1: Can I flash this on my SM-P355 tab

The ROM was built for the SM-T350 device (you can edit the updater script and flash at your own risk, a lot can go wrong)

2: Is this for Samsung Tab A 8.0 (2019)

The 2019 tablet is a SM-T290 device this ROM was built for the SM-T350

3: I get an error 7 when flashing this ROM

Install the TWRP image in the main post

4: Will you build for the SM-P355, SM-T290, SM-P350?

No I am only building for the devices that I own, feel free to use my device tree to build for your device
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Changes

2021-06-18

- May Security Patches

2021-06-21

- June Security Patches

- DRM fixes

2021-06-24

- Overclocked Kernel & GPU

- Added missing vendor blobs to fix drm issues

2021-06-27

- Cleaned up sensor spamming

- Some sepolicy fixes

2021-07.07

- Fix for UI blur issues

- Some sepolicy fixes

2021-07.08

- Fix for live display

2021-09-19

- September Security Patches
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Two bugs.

1) sensors not working

2557 12-16 15:23:13.580 372 372 E Sensors : couldn't find 'accelerometer_sensor' input device
2558 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'accelerometer_sensor' input device
2559 12-16 15:23:13.581 372 372 E Sensors : Couldn't open accelerometer_sensor.
2560 12-16 15:23:13.581 372 372 E Sensors : AccelerometerSensor: undefined chip spec()
2561 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'light_sensor' input device
2562 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'light_sensor' input device
2563 12-16 15:23:13.581 372 372 E Sensors : Couldn't open light_sensor.
2564 12-16 15:23:13.581 372 372 E Sensors : LightSensor: undefined chip spec()
2565 12-16 15:23:13.582 372 372 E Sensors : couldn't find 'grip_sensor_wifi' input device
2566 12-16 15:23:13.582 372 372 E Sensors : couldn't find 'grip_sensor_wifi' input device
2567 12-16 15:23:13.582 372 372 E Sensors : Couldn't open grip_sensor_wifi.

For my build, I found that sensors have to be in passthrough mode and sensors.msm8916 has to be removed. That is, manifest.xml

<hal format="hidl">
<name>android.hardware.sensors</name>
<transport arch="32">passthrough</transport>
<version>1.0</version>
<interface>
<name>ISensors</name>
<instance>default</instance>
</interface>
</hal>

and msm8916.mk

# Sensor HAL
# RT sensor needs to be passthrough and sensors.msm8916 needs to be removed in order to work
PRODUCT_PACKAGES += \
android.hardware.sensors@1.0-impl
# android.hardware.sensors@1.0-service \
# sensors.msm8916

2) drm not working

2527 12-16 15:23:13.530 364 364 E android.hardware.drm@1.0-impl: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...

You are missing a commit like

https://review.lineageos.org/q/_ZN6google8protobuf8internal13empty_string_E

===

Since you are using evervolv's kernel code, I suggested to them that they consider overclocking the CPU/GPU and gave them the commits, but they haven't or decided not to implement them.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
For overclock, see

https://xdaforums.com/t/rom-officia...b-a-8-0-sm-t350.3411150/page-12#post-84773289
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I already started a new build to fix the sensors with June security patches... I will look into drm thought I had that fixed
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I use devcheck by flar2 to check sensors and drm. When I click on the system menu in devcheck, my build with DRM shows Version 14.0.0, security L3 and clearkey 1.2. On your June 18 build, the same app shows nothing for DRM because of the error message that I included.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
TCP/IP errors.

With Android 11, you also need a patch to fix TCP/IP errors. I found these in my build back in March 2021 and you have them too in your build.

03-24 08:08:09.674 1059 1653 E TcpInfo : parsing error.
03-24 08:08:09.674 1059 1653 E TcpInfo : java.lang.IllegalArgumentException: Length 104 is less than required.
03-24 08:08:09.674 1059 1653 E TcpInfo : at com.android.networkstack.netlink.TcpInfo.<init>(TcpInfo.java:118)
03-24 08:08:09.674 1059 1653 E TcpInfo : at com.android.networkstack.netlink.TcpInfo.parse(TcpInfo.java:143)

To fix, see

https://xdaforums.com/t/rom-unoffic...g-galaxy-s5-klte.4209545/page-2#post-84211415

and

https://xdaforums.com/t/rom-unoffic...g-galaxy-s5-klte.4209545/page-2#post-84211093

I opted for the DerpFest fix at

TcpSocketTracker: Opt-out for TCP info parsing on legacy kernels · DerpFest-AOSP/packages_modules_NetworkStack@22fd53a

This feature requires netlink features that are unsupported on kernel versions lower than 4.4, therefore opt-out for it in such cases and avoid constantly crashing TcpSocketTracker. Change-Id: I12...

github.com

since I didn't want to touch the msm8916 kernel code.

Thanks to Henrik Grimler for pointing this out to me back in March 24, 2021.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Henrik Grimler submitted those kernel changes to msm8916 gerrit a while back after discovering it, but gerrit been down for days and I don't know when it will be up.

Again, I opted for the DerpFest fix, but I'm following the msm8916 kernel, not evervolv, so if Henrik's changes get merged into 18.1, I can revert the DerpFest fix.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Running a new build to include the patch for DRM, will do some testing when it is done, as for overclocking the kernel will take a look at that is weekend
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
New build uploaded (2021-06-21) with a few fixes @lividhen that app you couldn't get to work in the android 10 build should work in this build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@nubianprince , the June 21 build still has problems with DRM and sensors.

1. DRM

Your DRM shows clearkey 1.2 now using devcheck by flar2, but is mssing the widevine other info as I wrote in post #7.

2434 12-19 09:31:43.905 0 0 I [1: init: 1] init: starting service 'vendor.drm-hal-1-0'...
2435 12-19 09:31:43.913 0 0 E [1: init: 1] init: File /vendor/bin/hw/android.hardware.drm@1.3-service.clearkey (labeled "u:object_r:vendor_file:s0") has incorrect label or no domain transition from u:r:init:s0 to another SELinux domain defined. Have you configured your service correctly? https://source.android.com/security/selinux/device-policy#label_new_services_and_address_denials
2474 12-19 09:31:44.041 363 363 E android.hardware.drm@1.0-impl: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...

2. Sensors are still broken. As you can see in trace, it's starting and then dying (signal 9).

339 06-21 13:01:47.743 0 0 I [3: init: 1] init: starting service 'vendor.sensors-hal-1-0'...
340 06-21 13:01:47.761 2841 2841 E android.hardware.sensors@1.0-service: Couldn't load sensors module (Unknown error -2147483648)
341 06-21 13:01:47.761 2841 2841 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xa6f00114)
342 06-21 13:01:47.761 2841 2841 W RefBase : CallStack::getCurrentInternal not linked, returning null
343 06-21 13:01:47.761 2841 2841 W RefBase : CallStack::logStackInternal not linked
344 06-21 13:01:47.762 2841 2841 E LegacySupport: Could not get passthrough implementation for android.hardware.sensors@1.0::ISensors/default.
345 06-21 13:01:47.790 0 0 I [0: init: 1] init: Service 'vendor.sensors-hal-1-0' (pid 2841) exited with status 1
346 06-21 13:01:47.790 0 0 I [0: init: 1] init: Sending signal 9 to service 'vendor.sensors-hal-1-0' (pid 2841) process group...
347 06-21 13:01:47.790 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 2841 in 0ms
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Pictures from devcheck to illustrate what I'm describing. The file names tell you which screenshot is what. You can see the difference between my build and yours. I didn't take a picture of crDroid sensors, but yours only has temperature whereas mine as 2 more.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
So your June 21 build is completely missing the widevine information in the screenshot above. And yes, clearkey info is at the bottom of that crdroid screenshot. It cannot scroll any farther down in case you were wondering. The adb logcat error message I included also tells you that something is still wrong.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
New build uploaded with overclocked kernel and some other fixes, still need to cleanup a few things
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@nubianprince , June 24 has overclock for both CPU and GPU. DRM and sensors both are fixed as viewed by devcheck app.

While the sensors work in devcheck, adb logcat still shows something is not quite 100% as it continually spams

9184 06-24 14:27:53.969 0 0 I [1: init: 1] init: starting service 'vendor.sensors-hal-1-0'...
9185 06-24 14:27:54.000 2879 2879 I sensors_hal_wrapper: Initializing wrapper for Samsung Sensor-HAL
9186 06-24 14:27:54.002 2879 2879 E Sensors : couldn't find 'accelerometer_sensor' input device
9187 06-24 14:27:54.002 2879 2879 E Sensors : couldn't find 'accelerometer_sensor' input device
9188 06-24 14:27:54.003 2879 2879 E Sensors : Couldn't open accelerometer_sensor.
9189 06-24 14:27:54.003 2879 2879 E Sensors : AccelerometerSensor: undefined chip spec()
9190 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'light_sensor' input device
9191 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'light_sensor' input device
9192 06-24 14:27:54.003 2879 2879 E Sensors : Couldn't open light_sensor.
9193 06-24 14:27:54.003 2879 2879 E Sensors : LightSensor: undefined chip spec()
9194 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'grip_sensor_wifi' input device
9195 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'grip_sensor_wifi' input device
9196 06-24 14:27:54.003 2879 2879 E Sensors : Couldn't open grip_sensor_wifi.
9197 06-24 14:27:54.003 2879 2879 E Sensors : GripSensor_wifi: undefined chip spec()
9198 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'meta_event' input device
9199 06-24 14:27:54.004 2879 2879 E Sensors : couldn't find 'meta_event' input device
9200 06-24 14:27:54.004 2879 2879 E Sensors : Couldn't open meta_event.
9201 06-24 14:27:54.004 2879 2879 D Sensors : sensors_poll_context_t: sensor list: 0
9202 06-24 14:27:54.006 2879 2879 E HidlServiceManagement: Service android.hardware.sensors@1.0::ISensors/default must be in VINTF manifest in order to register/get.
9203 06-24 14:27:54.006 2879 2879 E LegacySupport: Could not register service android.hardware.sensors@1.0::ISensors/default (-2147483648).
9204 06-24 14:27:54.033 0 0 I [2: init: 1] init: Service 'vendor.sensors-hal-1-0' (pid 2879) exited with status 0
9205 06-24 14:27:54.033 0 0 I [2: init: 1] init: Sending signal 9 to service 'vendor.sensors-hal-1-0' (pid 2879) process group...

Do a grep for "vendor.sensors-hal-1-0" in your device tree and/or vendor tree to what is calling it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I am aware of the sensor spamming, I will see what is going on with that as soon as I can, I have to take a closer look at the vendor blobs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
There's no rush to fix. I'm just pointing out the bugs/errors that you may have missed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] batouttahell24:
Will this work if I have a Tab A with 7.1.1 installed? Also what variant of Gapps should I download?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Make sure you have TWRP recovery installed and follow the steps in the main post, you can google open_gapps-arm-11