yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Goatz123:
Yep all the other can is working.

TorstenH - are you saying that notification of the car being in reverse can go via can in addition to the reverse trigger?

thank would make sense why the pin isnt used on the main connector.

im going to order another Chinese harness just to rule out it being defective.

many thanks for all the guidance!
[Android Head-Units] TorstenH:
That's possible. In this case the can signal must be translated to a reverse trigger by the can box.

Some cars have both, the signal on can bus and a reverse trigger wire.

Other cars have only the reverse trigger wire and not the corresponding signal on can bus.

Best would be to use a multimeter to check the potential reverse trigger wire coming from the oem harness. Please ensure you used the correct pin and you've not tried with another by accident.

View attachment 6089305
[Android Head-Units] Goatz123:
Hi all.

I received this back from Eonon regarding the issue.

”1. It's recommended to try connecting the trigger wire of the reversing camear directly to the reversing control wire of the head unit (the one indicated in the attached pic.). Of course, you can also try to connect the reverse control wire of the head unit directly to 12V to see if you can enter reverse mode.

2. It's recommended to strip the insulation of the reversing control wire, and then connect the red trigger wire of the reversing mirror to the reversing control wire of the head unit, thanks.”

From the photo im not clear on what the red wire going to the rca is.

the photo appears to show an aftermarket camera so probably 12v instead of 6v. The red wire coming out of the unit (above the rca) is a 12v line for 12v cameras (not used on my setup)
[Android Head-Units] Goatz123:
thanks Torsten,

so should the red wire also go direct to the camera? There is no other Need for it on the canbus decoder? I assume I need a 12v to 6v step down though.
[Android Head-Units] TorstenH:
Which red wire? I thought the picture is from your head unit support and you want to use an already installed oem camera.
[Android Head-Units] Goatz123:
Ok, after a few more hours I finally solved this issue.

so I had wired it correctly, there was a setting I was missing.

So, for my vehicle the canbus decoder does not appear to trigger the reverse camera trigger wire.

the way around it was to bypass the canbus decoder and wire it up directly, so cut the wire from the canbus to the HU, add a pin to the harness and solder that wire to the wire you have cut (going into HU).

the setting on the HU was called ’prohibit reverse’. confusingly, this needs to be set to ‘enable’.

My car is a 2013 Mazda 6 high trim (Bose) manual transmission european. from what I hear, the canbus decoder can trigger the reverse cam only wher transmission is Automatic.

hope this helps someone.
[Android Head-Units] TorstenH:
I think you connected the REV wire of the OEM harness with G5:

View attachment 6096746

Additionally you set that the reverse signal will not be provided via can (prohibit reverse).
[Android Head-Units] Goatz123:
Yep, rev wire to G5.

interesting, so prohibit reverse means instruction will not come from the can. Makes more sense now.

thanks for the help!
[Galaxy Grand Prime Android Development] wojtaszz:
Nusantra for gprime )
[Galaxy Grand Prime Android Development] zer0_Clover:
Screenshots. And for the people with other models, https://xdaforums.com/t/how-to-use-roms-for-other-models-on-your-model.4512087/

it might work
[Galaxy Grand Prime Android Development] LongestyCandy:
Tem interesse em trazer a versão para o G530H XCU (fortunave3g)?
[Galaxy Grand Prime Android Development] SyedKhizarShahKazmi:
i have fortuna3g if i follow the given method will this rom work with any issues?
[Galaxy Grand Prime Android Development] SyedKhizarShahKazmi:
how is rom stability and battery health?
[Galaxy Grand Prime Android Development] SyedKhizarShahKazmi:
Link to gapps build please
[Galaxy Grand Prime Android Development] SyedKhizarShahKazmi:
I extracted rom files but it doesnt have this code line:

assert(getprop("ro.product.device") == "fortuna3g" || getprop("ro.build.product") == "fortuna3g" ||

getprop("ro.product.device") == "fortuna3gxx" || getprop("ro.build.product") == "fortuna3gxx" || abort("E3004: This package is for device: fortuna3g,fortuna3gxx; this device is " + getprop("ro.product.device") + "."););

Does this mean i can install this rom on fortuna3g without errors?
[Galaxy Grand Prime Android Development] zer0_Clover:
i don't know, i only have fortunafz but most fortuna3g roms work for me. you can just flash it. someone said that it didnt work but you are free to try. i used pitchblack recovery and raijin kernel. its for android 10 but you can edit it to support 11, not too many differences between the versions so it works with no problems. i don't recommend gapps especially on android 11, it will lag like crazy. can't you just flash gapps too

exactly the same as los 18.1. built it using the device trees from that rom
[Galaxy Grand Prime Android Development] SyedKhizarShahKazmi:
@zer0_Clover i know this question is out of place but please answer me

I flashed los 18.1 from twrp, rom flashed perfectly but right after that i tried flashing gapps but twrp shows error1, i tried all the different gapps none of them flashed they all showd error1, what should i do? Rom is working perfectly but i can not live without playstore help me please 🥺
[Galaxy Grand Prime Android Development] zer0_Clover:
you probably have wrong gapps zip. it should be arm. again, gapps makes this thing VERY slow, especially on newer android versions. if you want gapps you should probably use nougat or pie
[Galaxy Grand Prime Android Development] katruisya:
I bought a new grand prime for cheap so I'll test this when it arrives
[Galaxy Grand Prime Android Development] zer0_Clover:
nice, which model?
[Galaxy Grand Prime Android Development] katruisya:
G530fz
[Galaxy Grand Prime Android Development] mhkanon:
I successfully installed it, but it did not boot. It goes to download mode auto.

MY device is G530H XCU (fortunave3g).
[Galaxy Grand Prime Android Development] SyedKhizarShahKazmi:
Same happened to me while i was installing rom

SOLUTION: un check f restart, auto reboot option in odin then install recovery. On first boot in some devices ,it deletes recovery there is an solution available on this thread somewhere in start
[Galaxy Grand Prime Android Development] SyedKhizarShahKazmi:
This device is not supported by rom, sorry i thought it was los 18 thread. This rom isn't compatible with fortuna3g i tried it . The problem u asked was also present in los 18 so i answered it. I haven't noticed that it was this thread
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] VDavid003:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Most custom ROMs try changing the Android version by pushing it upwards.

Ever wondered "why not just go in the opposite direction?"

Well this ROM does just that.

Welcome to Android 7.0, on a phone released with 7.1.1!

This is a ported ROM from the Samsung Galaxy A5 (2017).

Features:

Based on A520FXXU3BQLA

Debloated

Support for A530F and A730F

Made with (soon-to-be-released) Android Scriptable Kitchen

What does not work:

First boot requires a manual reboot, otherwise the phone doesn't boot

The initial setup has some bugs that you have to work around (details below!).

Software navigation bar likes to be black even on black backgrounds.

What works:

Everything else

Installation:

If you haven't yet, install a custom recovery and decrypt data

Flash zip in custom recovery

Wipe data

Reboot

Wait 30 seconds, then reboot again using Volume Down + Power button

While on the initial setup, remove your SIM card(s) and skip connecting to WiFi, otherwise you may get a SystemUI crash, or infinite loading.

Downloads/Changelog:

1.1 (DOWNLOAD)

Fixed boot, previous version was broken due to last minute changes

1.0 (DOWNLOAD REMOVED)

First release

Was fully broken, removed

Source Code:

Kernel: https://github.com/VDavid003/universal7885_treeui_kernel/tree/nougat_rom

ROM: Coming soon!

That's right! Android Scriptable Kitchen means that we can actually automate building ported ROMs using code!

Screenshots:

Spoiler content hidden.

Credits:

-Me

Donate:

BTC: 19748ZuTu5f7CShVQMTnDNNe5Q4WryxaDZ

PayPal: http://paypal.me/VDavid003

Will use it to buy stuff that needs fixing :)

If you link to my ROM, please link to the XDA thread, not directly to the file!

P.S.:

Happy (maybe late in some countries/regions) April Fools, everyone!

Although this ROM is meant more as a joke rather than anything serious, it is, in fact a fully functional 7.0 ROM. Good for some nostalgia.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] VDavid003:
reserved
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] Note 9 Hype:
I tested the rom on my A8 (a530f) and it's very very good, but only nav bar is bugged. I have an neon flip cover case and it's working on this rom. I LOVE THIS ROM!!!
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] iliyaz234523:
Можно ли установить ядро Mesa?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] VDavid003:
I'm not sure if the Nougat version of Mesa's Custom Kernel would work with this ROM.

You can try it, but it may not work. The main issue I see is that the ramdisk may be incompatible with the A5 system. If that kernel doesn't boot, you could replace the ramdisk in it with the one from the ROM and probably boot that way.

Anyways, if it does boot and you find issues, please try the included kernel before reporting anything. I won't (can't) fix issues caused by this.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] duskynights:
It wont install for me it just gives error 7
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] VDavid003:
Which recovery are you using?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] duskynights:
TWRP 3.6.2
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] DaviVole:
you need an older one, install the 3.4.0 and try again
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] iliyazk:
why this project if there is project dynamick?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] DaviVole:
idk
[Xiaomi Mi 10 ROMs, Kernels, Recoveries, & Other De] TechPanelGM:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/

Introduction

Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.

Based on TWRP version: 3.7.0_12

PitchBlack version: 4.0

For device: CMI

Maintainer/Authors build: TechPanelGM

PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject

Device tree: https://github.com/TechPanelGM/pbrp_device_xiaomi_cmi

PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar

Features

Installation Instructions

From previous version or other recovery

Download the PitchBlack zip to your device

Reboot to your current custom recovery

Flash the PitchBlack zip

The device will automatically reboot into PitchBlack Recovery after installation

Enjoy

From PC

Download PitchBlack Recovery flashable zip from bellow

Extract the PBRP zip

Goto fastboot mode in your device

Flash the recovery.img by fastboot flash recovery.img

Boot into PBRP

Copy the zip to internal storage

Flash it

Enjoy

Changelog

PBRP Side Changelog

PBRP Version - 4.0
- Bump to 4.0
- Based on TWRP 3.7.0_12
- Redesigned homescreen
- Fixed minor glitches
- Added more languages support

Device Side Changelog

Bugs

- You tell me!

Downloads

Flashable zip

https://drive.google.com/file/d/1dhu5DD-0lHxmtqAbhK4MNZ1bPz3w9PIi/view?usp=drive_link
[General Questions and Answers] peido:
Hi!

I have a Xiaomi Redmi Note 6 Pro that decided to die a couple of days ago.

I usually make backups regularly, so I haven't lost everything, but I would like to recover the most recent photos I took.

The phone doesn't give any signs of life. I tried Fastboot, Recovery Menu and Removing/Reinserting battery.

I've measured the battery with a multimeter, and it's with 4.2V.

The screen is always off and the LED never blinks.

When I connect the phone to a computer, the phone is detected as "05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".

I decided to use https://github.com/bkerler/edl on Linux, followed all the instructions, but I was getting a 'version = conninfo["data"].version' "AttributeError: type object 'req' has no attribute 'version'" error on line 295.

I then tried on Windows 10, but was still getting the same error, until I installed Zadig's libusb-win32 drivers and everything started to work better.

Now I'm getting errors when I try to do:

python edl --loader=prog_emmc_firehose_Sdm660_ddr.elf printgpt

And:

python edl --loader=prog_emmc_firehose_Sdm660_ddr.elf r userdata userdata.bin

I'm attatching 2 TXT files, one for log of the command:

python edl --loader=prog_emmc_firehose_Sdm660_ddr.elf printgpt --debug

And another for the command:

python edl --loader=prog_emmc_firehose_Sdm660_ddr.elf r userdata userdata.bin --debug

I tried with the loaders 'prog_emmc_firehose_Sdm660_ddr.elf', 'prog_emmc_firehose_Sdm660_lite.elf' and 'prog_emmc_firehose_8953_ddr_xiaomi5_rb1.mbn' (I'm also attaching the loaders I used).

I also tried not indicating a loader, but that fails.

Some other things I tried, but the EDL results were the same:

- Connecting the phone to PC with battery disconnected;

- Connecting the phone to PC with the EDL pins connected;

- Connecting the phone to PC with the EDL pins connected and with the battery disconnected.

Anyone has any ideas of what I should try next?

Thanks a lot :)
[General Questions and Answers] Zxalilh:
How about trying other versions of the tool?
[General Questions and Answers] peido:
Hi.

Thanks for the help.

Before I was using the latest commit (29March2024). Today I tried version 3.0, but it also didn't work:
[General Questions and Answers] peido:
I also tried Zadig's libusbK, this driver seems to work as well as libusb-win32.

Also tried the loader in "Loaders\qualcomm\factory\sdm636\000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek.bin", but this one is worse.
[General Questions and Answers] Zxalilh:
Maybe a dead emmc. 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode), the 05c6:9008 probably means it's in memory dump mode.
[Moto G Power (2021)] yagmire:
Wanting to sell this phone to a friend. Phone was bootloader unlocked by me and without research (stupidly) I ran fastboot oem lock. Now the phone is only getting to the bootloader and not fastbootd or recovery. The phone is also locked so cannot reverse and re-flash. Tried the rescue tool and getting this error: View attachment 6086823

Trying to turn the phone on normally, will result in an error saying, "No valid operating system could be found. The device will not boot." Running 'fastboot devices' works and is recognized.

Running fastboot getvar securestate, results in:

securestate: flashing_locked

Trying to unlock with my unlock code results in:

Here is my fastboot getvar all:
[Moto G Power (2021)] McChadwicke:
You bricked it real good. It's a paperweight. Unless you have a hardware solution such as taking the phone apart and replace chips, there's a good bet you'll never get this into a bootable state ever again.

Taken from:

Fastboot oem unlock/ fastboot oem lock please read!

I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do. 1. Fastboot oem unlock will unlock your...

xdaforums.com

"Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first."
[Moto G Power (2021)] Lioplurodn:
Use qboot on windows computer while in EDL mode should fix it.

1.) I'm not sure if I'm supposed share attachments or links here so I apologize if I shouldn't be and warn people to always know what they're clicking on and/or downloading and advise caution.

2.) This is the qboot command prompt tool and one of the flash files I used (can't remember which one) I used back in 2021. Worked on windows computer but didn't work on linux(Ubuntu) for me btw.

3.) It looks like your build might be slightly off as mine was 32GB and 3GB ram version so I'd recommend making sure you're using your specific device/model flash file but these will give you an idea of what you're looking for.

I tried booting my phone on slot _b while slot_b had literally nothing on it and it completely bricked my phone into EDL mode where it wouldn't even boot up. That's how I got into my situation of trying to fix it from literally a paperweight. Qboot and your exact phone model/build flash file is your golden ticket if the stars aline right. Good luck to you
[General Topics] Muhammad Menhajul Islam:
I was wondering if its possible to port Windows 10 Mobile to modern Android devices with powerful hardware and flash like a custom rom. It would be great if Google Play services and Android emulation can be implemented.
[General Topics] Oswald Boelcke:
Thread closed not only due to

***NOTICE*** Do NOT post questions here

This section is for discussing anything relating to technology that doesn't fit into the other forums such as general tutorials, news, guides and how-tos. Please post all your questions, requests here: Questions and Answers Thank you, Your...

xdaforums.com

but also as you've already created a subject matter related thread:

Porting Windows mobile to modern Android devices

Most of the people love how the Windows mobile os looks. The major complain is the app support which is also the major reason of its extinction. So I was wondering if its possible to port Windows 10/8.1 Mobile to modern Android devices and flash...

xdaforums.com

Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[XPERIA X1 General] rotsu:
How to change the sensitivity of the screen ?

I want it to be more sensitive to finger touches so i dont have to apply any pressure on the screen to register a "click."

Is there any way to change this ?
[XPERIA X1 General] bharat4ever:
I heard somewhere that when you calibrate the screen, it not only calibrates where you touch the screen, but also how much pressure you apply? Is that true anyone?
[XPERIA X1 General] Nippero:
Seems true to me, barely takes any pressure for me to use the touch screen.
[XPERIA X1 General] ehajj:
I had the same problem wen I formatted my phone again, I had to calibrate the phone again and it worked perfectly.
[XPERIA X1 General] dogans:
That is AFAIK true.

To recalibrate, go to Start -> Settings -> choosing the system tab -> tap the screen icon.

There, you can recalibrate where you touch the screen and how much pressure you apply to the touches.
[XPERIA X1 General] rotsu:
Thanks guys.

Just tried to re-calibrate the screen with little pressure by my clicks, and it works better now.
[XPERIA X1 General] rarewolf:
My X1a arrived from a previous owner without the stylus working, so I'm hopeful that calibrating the screen will remedy the problem like it has for so many (altho a handset problem is still a possibility).

However, before I do (which will be after work today), I was hoping to hear why, or how anyone could screw it up, so that I could either troubleshoot the current problem, or minimally not screw up the procedure myself.

This is my 1st smartphone so pardon the newbish query ...

TIA :)

and cheerios from the Avalon Peninsula
[XPERIA X1 General] SquidgyB:
*sigh*

A quick (5 seconds?) search and:

http://xdaforums.com/showthread.php?t=485037&highlight=screen+sensitivity
[XPERIA X1 General] rarewolf:
Thanx Squidgy ... my search tumed up this thread only, altho your thread seems to be more about an alternate procedure, and does come up short on why or how anyone could screw up the primary procedure(?) :p

Edit: I also could have been more clear ... ie, finger touch seems to work well, while my stylus does not ... and that's a bit of a mystery to me(?)

cheerios :)
[XPERIA X1 General] flub:
I Have found that if you calibrate with finger, then stylus doesnt work so good but if you calibrate gently with stylus, then finger and stylus works far better

try it
[XPERIA X1 General] rotsu:
This post is old.

almost 2 months before softtouch was released.
[XPERIA X1 General] rarewolf:
Thanx Flub!

My own approach to the procedure (called an alignment) took me around the screen several times. I don't know if it was trying to acquire some minimum threshold of satisfaction, but I might imagine it leading some users to pressing harder and harder. Your suggestion was an impetus for using soft touches only, and the result is a stylus touch that is now very sensitive.

cheerios :)
[XPERIA X1 General] SquidgyB:
I don't understand what you mean "this post is old"...

The methods described in the post work, and I can't see any other newer versions of that softtouch, apart from the softtouch keyboard which is a completely different app.

As for why you would want to use the 2nd procedure (I don't know how you could bugger up a .cab installation), personally I prefer a quick clean reg edit to installing a cab. But each to their own.
[General Questions and Answers] RealNovgorod:
Is there a way to disable the pop-up demanding to turn on Google Play Protect without disabling the entire Play Store app?

View attachment 6086825

The phone in question is a Galaxy S22 Ultra (Android 14), but it's most likely a general Android/Google issue. It used to be a "reminder" a few years ago popping up once in a while, but since the last few Android versions (probably 12 or 13) it pops up every few minutes, essentially not allowing you to use the phone unless you turn on Play Protect (then why ask in the first place?)...

Old posts with this problem suggest blocking security notifications, but this doesn't work anymore. It pops up even if all notifications from the Play Store app are disabled.

The only way to get rid of it is to disable the Play Store app entirely and only enable it when you need to install a new app from the Play Store or to do manual app updates and disable it again. Being forced to disable the Play store is also not great for security because you won't get auto-updates (the irony, eh?)..

Is there any way to suppress the nag screen? Maybe some system setting with SetEdit? Obviously, I'm not turning on Play Protect, so if that's now "mandatory", I'll have to ditch the Play Store altogether and use a different package manager for the "official" Play Store apps (like apkmirror or so) to get auto-updates (but then you have to manually confirm every update if it's not installed by the Play Store app, right?)..
[General Questions and Answers] EllieCat:
Hi, hope this helps!

(Link was not correct)
[General Questions and Answers] RealNovgorod:
Of course not. Read at least the title of this thread, not just some key words.
[General Questions and Answers] EllieCat:
Sorry about that. Try to use adb shell and imprint this command

adb shell pm revoke de.androidpit.app android.permission.SYSTEM_ALERT_WINDOW