yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Questions & Answers] jaybg:
Maybe this will help you figure out the required setup for your needs.

Calls, texts and contacts in your work profile - Android Enterprise Help

You can use dialer and SMS apps in your work profile. Your administrator might also allow you to search for work contacts from your personal contacts and dialer apps on your device with Android 7.0 No

support.google.com
[Samsung Galaxy S20 FE Questions & Answers] triosis:
Hello,

I found a s20fe 5g on this website

https://uk.shopping.rakuten.com/offer?action=desc&aid=10653633481&productId=5504650604

it is an international version SM-G781B/DS, does this cause network problems in France?

Otherwise is there update problems?
[Samsung Galaxy S20 FE Questions & Answers] creditabricole:
Hi triosis

The galaxy S20 FE 5G (Qualcomm) SM-G781B/DS is the version distributed in France !

Of couse there is no problem to flash/update with french stock Roms (XOM_XEF/BOG/SFR....)
[Samsung Galaxy S20 FE Questions & Answers] Mirdar:
I have the same version, and I had absolutely no problems with anything when I was in France on holiday.
[General Questions and Answers] hrm5023:
Hey guys,

I know I am going to sound really newby, but that is true in this PDA world for me. I recently got my HTC love, and I really love the phone.

I have surfed XDA for quite a while, and I am truly amazed at the number of PDA users. It truly is a great collection, but I have not been able to find answers to these questions. The search option has not helped much but give me several different ROM types and versions, but I dont know what exactly they are so can someone help me out on these questions please:

What exactly is ROM?

What is Flashing ROM?

Different languages of ROM?

Manila 2D ROM? Kaiser ROM? Diamond ROM?

It would be really kind if someone could answer these questions.

I appreciate your time.

Thank You
[General Questions and Answers] Restorer:
ROM stands for Read Only Memory and is the part of your phone's memory where the Operating System is stored - equivalent if you like to XP or Vista on the PC.

Flashing the ROM refers to replacing the ROM that came with your phone with another - usually written or "cooked" by enthusiasts who build in there own programs and preferences. Flashing is best done after much study as there is a chance you can wreck your phone. If you want to modify your phone it is best to start off using CAB files.

Yes there are different languages of ROMs available. A Manila2D ROM would have the Manila2D interface built into it. Kaiser and Diamond are other phones in the HTC range.
[General Questions and Answers] hrm5023:
My phone slows down with the cab files, and I can see how memory plays a part there.

Also installing manila 2d was way too laggy, I kind of want more memory and space available.

So if I do the flash ROM, and have this huge ROM space, all I have to do later is to install cab files on ROM right?

Thanks for your reply Restorer.
[General Questions and Answers] orb3000:
Welcome to the forum

Please READ the Wiki, and you´ll find answers to almost all your questions
[General Questions and Answers] + Que PPC:
yes but this is the quick answer thread ok lets see.

The Phone has memory to run programs like virtual memory and storage memory partitioned (as fake) on some provided to Operative system's phone... I mean Wizard has a little and other phone has so much more... why? cause it needs more program memory or the app are more heavy ok?

well diamond ROM... Wizard ROM... hermes ROM.... here we said it as the develops on cooks some Operative systems for each other device specially for that device ok?

See you soon.
[General Questions and Answers] joel2009:
this is the questions an answers section, in otherwords if someone has a question give them an answer. if you are going to say "read the wiki" you need to atleast give them a link on where to start, otherwise you are just spamming.

now to ANSWER the question....

yes you can install cabs, its still windows mobile its just like when you a get a computer from dell, dell will give you windows but they will also give you a bunch of "Dell-ware" (usually a bunch of useless shareware someone is paying them to load on their computers)

When you get a new rom you still get windows you just get a choice at what you want on your phone, instead of what your service provider thinks they might be able to sell you or what they think you will use.

You can get roms in all different flavors, anything from something striped down to the very core of the operating system, or something loaded with multimedia features, or something based around a program such as a manilla rom.

to read up on this go here, MAKE SURE YOU READ, if you follow direction you will be fine but if you just jump in without reading everything you will brick your phone.
[General Questions and Answers] Corpsegrinder:
Here is some good readin that will answer some of your questions....
[LineageOS Questions & Answers] Agairty3:
Im not sure how to go about adding this official component, Is there an APK somewhere I can download?

The Flip Flap LineageOS GitHub Repo is > https://github.com/LineageOS/android_packages_apps_FlipFlap
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Sjll:
Lineage 19.1 for Xperia X Performance​

#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.
*/

About LineageOS

LineageOS is a free, community built, aftermarket firmware distribution of Android 12.x (S),

which is designed to increase performance and reliability over stock Android for your device.

All the source code for LineageOS is available in the LineageOS GitHub repo.

And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

Official LineageOS website : http://lineageos.org

About LineageOS Legal : http://lineageos.org/legal/

Important Information

1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.

2. You need to flash Stock 41.3.A.2.149 and boot into it before flashing this ROM.

3. This ROM is suitable for dual and single model

4. You will meet a delay when recognize sim at the first boot.

5. We support Gcam, but you need to install Gapps at first.

Downloads Links

LineageOS 19.1:

Unofficial:

https://sourceforge.net/projects/release-sjll/files/dora/19.1/

Google Applications (optional):

NikGapps: https://nikgapps.com/ (ARM64->Android S->core,)

Information: Flash the GApps before the first boot. If not, a clean flash is recommended.

Flashing and updating

LineageOS clean install:

Download the latest build of LineageOS ROM

Full wipe and factory reset (recommended / backup to make sure not to loose data)

Flash the LineageOS ROM zip from the Recovery

Flash the GApps to have the Google Applications (optional)

Every additional zip you want to flash (optional)

Reboot

LineageOS update/upgrade:

Download the latest build of LineageOS ROM

Wipe cache and dalvik cache

Flash the latest LineageOS ROM zip from the Recovery

Every additional zip you want to flash (optional)

Reboot

About the builds:

Source: https://github.com/linelessos

Issues and reports

Report issues only if you are using the ROM kernel

If an additional mod is installed, make sure it's unrelated, and mention it

Make sure the issue wasn't discussed earlier in the threads

Share a log of the error with CatLog for example

Also thanks to:

The LineageOS Team

The CyanogenMod Team

The SODP Team.

Olivier

Chippa_a

Everyone involved in working and testing

Contributors

@erikcas @Sjll

ROM OS Version: 12.0

ROM Kernel: Linux 4.4.x

Version Information

Status: Beta
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Sjll:
FEATURES AND ISSUES

- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: 2.4 Ghz Only
- RIL - Phone - Data: Ok
- VoLTE: No
- GPS: No test
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: No test
- Offline Charging: No
- USB: Ok
- USB Tethering: No test
- USB OTG: No test
- Encryption: No
- SEPolicies: Permissive
[Sony Xperia X Performance ROMs, Kernels, Recoverie] jlabo:
Fingerprint Sensor stopped working,

First of all, thanks for the ROM, Sjll.

After installing the Rom could enable Fingerprint Sensor successfully. But after a while Fingerprint Sensor stopped working. Couldn't workaround this problem. Any idea how to fix the problem?

Also it is not possible to delete already scanned Fingerprints and it is not possible to overwrite.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Sjll:
Thanks for your feedback. It is a known issue that FPC and CAM might cause randomly reboot on tone platform after we upgraded to kernel 4.4. We do not have method to solve it currently.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Glazami:
Thanks for the update. I checked and when I turn on the camera, I also reboot, the fingerprint scanner also does not work. We will wait for updates and hope that a solution will be found.

And I wanted to install flamegapps but they don't install.

Immediately after installation, a window pops up with the inscription An internal error has occurred, contact the device manufacturer for details.

During the throttling test, the smartphone does not turn off, as it was with version 18.1 But the battery temperature is 45.5 degrees Celsius, and the processor temperature is 63.5 degrees Celsius, after which, due to overheating, the application was stopped and an inscription appeared in another language. Is it possible to reduce CPU overheating? The latest version of ubuntu touch does not have a solution to the kernel problem about the camera and fingerprint?
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Glazami:
Dear Sjll, I think I figured out how to overcome the problem with a non-working fingerprint scanner, while setting up the smartphone, I did not set up protection, but missed this item, after setting up the system, I went to the security settings, fingerprints and added a fingerprint, and it all worked, The fingerprint works every time I put my finger on it. Is it possible to put the camera application from the stock firmware android 8 and where can I get it separately? Google camera works much worse than stock and picture quality is worse. And yet, during the installation of the firmware in twrp, I get a message that it was not possible to mount / oem, does this need to be fixed somehow? does it affect anything? Error installing flamegapps, But nikgapps is getting installed, don't know why. Immediately after installing the firmware and the first start, I get a message about some kind of critical error, and I have to contact the manufacturer. And after starting, sometimes this message appears.

And resetting all smartphone data does not work.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] jlabo:
Hi Glazami,

Regarding NikGapps problem:

I had the same problem but I could solve it with installing in Twrp following NikGapps version after 19.1 image installation but before first boot:

https://sourceforge.net/projects/nikgapps/files/

(--> this is NikGapps version ...12.1-20220822...)

Without using this NikGapps version I got the same error (like you got).

Regarding Fingerprint sensor problem:

I already had scanned my fingerprints while first setup (of LOS19.1) and it worked at the beginning. But after some time fingerprint sensor stopped working and I could not unlock the system (with my fingerprint) anymore. Sometimes after a reboot it worked again bit not for long time. Most of my reboot tries didn't bring back fingerprint scan functionality. I'm hoping for a future release that solves this problem.

Regarding OEM-mount message in TWRP:

I got the same message in TWRP and I ignored it.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Oliwier1990:
Nice android 12 for xperia x perf. i will try it
[Sony Xperia X Performance ROMs, Kernels, Recoverie] The Dumb Dino:
Ive been using this on my old Sony for a while now but sometimes the phone "crashes" the screen turn black for about 2-5 seconds and then gives a picture of the last displayed frame with hard distortion and a grain out of red green and blue pixels. The stock rom never had this issue and I am not sure how to solve or how to deal with it so I came here to tell you.

Another problem I came across was that the wifi turns off sometimes and when I try to turn it back on the System-UI crashes.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] The Dumb Dino:
I managed to capture one of these crashes, maybe this helps.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Saciu2:
After the phone is put to sleep and turned on, the phone resets. Over and over again.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Saciu2:
This is caused by the fingerprint reader. When there is no added, everything works, but this we add. The system crashed.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Saciu2:
I also noticed that every few flashlight turns on, the phone freezes and restarts. In addition to the fingerprint reader and this flashlight, I did not notice any errors in the system.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] waywadi168:
the oem error maybe caused by

cause mine is update from 18.1 directly and got this error too !
[Sony Xperia X Performance ROMs, Kernels, Recoverie] RazeChan:
Been using this ROM for 2 months now. Regret installing GAPPS additionally because of it's constant background power consumption . A clean lineage os keeps charge 1.5 longer in case of my X Performance (Dora).

Camera module issues: toggling (turning on and off) a camera or a flashlight causes a phone to reboot on every second time in my case. Basically I'm unable to use a camera in this ROM.

By my research v.19.1 of LineageOS has an issue of an unfixed proxy. I am not an expert in network but what is evident is that some websites are hardly blocked for a phone to connect, and it required to use external proxy if you want to visit those pages

Downgrading to an older version of LineageOS. This build is highly unstable, although it was nice to see that such an old of a phone performs good on Android 13+
[Sony Xperia X Performance ROMs, Kernels, Recoverie] dhan774:
usb tethering not working, is there any way to fix it?
[Introductions] triosis:
Marc 31 from France using a S9 exynos dying i'm looking for a new Samgung, S20 FE 5g seems to be nice.

But not shure that the network would be ok in my country

It's an international version sm-G781B/DS

​

​
[Introductions] orb3000:
Hello, welcome to the forums
[Nothing Phone 1] fladnag:
The letter font on my weather widget change to normal font and i cannot get back de Dot matrix font back.

I already try to remove the widget and add on again but the letter font remain the same, even after restarting the phone.

Does anybody know why that is?
[Nothing Phone 1] fladnag:
Already figured out the problem.

It's because of the system language.

If I switch the language to English it shows up the original Dot Matrix font.

Must be a bug from the last update...
[FYT Android Head Units] ludditefornow:
I have a Navifly 7862 head unit and up until now have not bothered to add a rear cam to integrate into the head unit. My car has a separate factory rear cam that has the monitor integrated into the rear vision mirror.

So due to a rainy weekend, I decided to add a new AHD cam. Cam is wired to the reverse light. My 6m RCA plus power lead at the head unit gets 11 volts when reverse gear is triggered. The RCA gets about 0.5 volts.

The options to connect to the 11 (12) volt red power to the head unit are wires called "Camera B+" (red), "IR" (grey), "Brake In" (pink) and two different unnamed yellow wires that are all running from the same connector from the head unit.

The 11 volt red power is connected to Camera B + yet when in reverse the head unit screen does not change. I have tried the live 11 volt line on IR, Brake In and the 2 yellow wires to try and get the head unit to switch to rear cam mode but I cannot get that to happen.

eve if the camera was faulty, I would expect to see the head unit change from home screen to a blank screen that states "no signal" or similar.

Can anyone suggest what the issue might be. I have looked through the settings but am yet to find anything to force the head unit to change to rear cam mode.
[FYT Android Head Units] rigattoni:
Go to factory settings and find a setting called "Prohibit Reverse", switch this setting and try again.
[FYT Android Head Units] rigattoni:
By the way...

You are forcing 12V into the Videosignal line... What are you doing there?

I just had a look at your attached picture. You should not wonder if the radio is now in the eternal hunting-grounds.

If you don´t know how to install a radio, please search for one who can do that without burning down your car. On top the 12V line just twisted together... Whow...Never seen someone doing such bad things in one single posting.
[FYT Android Head Units] ludditefornow:
I have temporarily twisted the wire for testing purposes. I solder and heat seal connections when confirmed. Are you always this critical of people?

So what voltage should be fed to the Camera B + line?

The directions was to tap into the reverse light (which is 12 volt) and send that to the power line that runs parallel with the RCA. Are you suggesting that I shouldn't?

Well how about helping here instead of criticising, please, if you know better.
[FYT Android Head Units] marchnz:
Not critical- post is accurate and suggests finding a skilled installer to assist you. Poking power on to the head unit wires without understanding is a sure way to break the unit or vehicle.
[FYT Android Head Units] ludditefornow:
There are 5 in lines to tap.

The literature that came with the cam as well as all videos online from the likes of Joying that I found show a 12v tap from the rear reverse light for the trigger.

You posted recently about 4PDA not being wanted at XDA because the silo knowledge.

Are you not willing to take a few minutes to actually share knowledge when there is a direct lack of knowledge from suppliers?
[FYT Android Head Units] ludditefornow:
Well I found the issue and somehow 'managed' not to destroy my head unit, my car, my house or the local power station.

All connections are nicely soldered and heat shrink wrapped now that I have a permanent fix.

The initial attempt at connecting the 12v line to Camera B + as noted on other how tos did not work.

To stay in the spirit of XDA (unlike the postings of some) I would like to advise that the wiring diagram from Navifly was incorrect.They have the pin 2 on the main connector as the reverse that feeds the CAN module. Pin 2 carries a constant 12v. Pin 3 (pink on my HU connector) carries zero voltage. I tapped pin 3 pink wire on the way to the CAN and added the red daughter wire on my 6m long RCA cable.

My red daughter wire is fed 12v from my rear reverse lamp. Reverse lamp also feeds the reverse cam.

I hope this assists someone in future.
[FYT Android Head Units] marchnz:
You did it. Thanks for posting your findings, I believe this has been posted about before.

I wouldn't recommend projecting at those that have actually spent hours to days developing methods, tools and helping others here.
[FYT Android Head Units] leo06:
All that because of the canbus. i believe they send you a canbus box that only works for steering wheel buttons and nothing else. i had the same problem and solved it like you did.
[FYT Android Head Units] rigattoni:
Sorry to say, but the wiring diagram is not really incorrect. It always depends on the aftermarket cam you use. But it is never a good idea to feed 12V into a CPU which just expects a video signal.

...and if you have a look at the wiring diagram of the camera, it shows 2 different ways to get the cam feeded with 12V.

The first one is the yellow connector which has a red wire coming out.

If you would have used this one, plug it into the "CAM IN" connector of your unit and the red one to the Back wire of your unit you would have been okay.

Using the back light to feed the camera is in most cases not necessary.

By the way... As I have seen that you feed the Video-In chinch-connector with 12V, I really was the meaning that you even don´t know anything about that what you did. I just gave the tip to search someone who knows what he does. I didn´t see any chance to start from scratch to teach you how to do.

I am on top really pissed if I see someone just wiggling cables together.

I just counted 1+1 and decided that I have to stop you doing strange things, which could lead to shorts and such things.

So... if it is working now as expected: Fine! ...and thanks for posting.
[FYT Android Head Units] leo06:
First, the diagram is incorrect and has nothing to do with the aftermarket cam. He didn't feed any 12v to video signal, the red wire is the trigger for the head unit to switch to reverse cam input, the 12v from the head unit is to feed the camera and doesn't need to be connected when you feed the camera from the reverse light. When you put the reverse the head unit must switch to reverse cam input if the canbus box is correct for your car, in this case and mines as well it isn't. The wire he shows came from the canbus box must have 12v when you put in reverse but no 12v
[FYT Android Head Units] rigattoni:
Sorry, but you are wrong.

The head unit reacts on a voltage difference to switch to the back view camera. It´s not needed to have 12V feeded to the head unit.

CAM-IN from the head unit expects the video signal nothing else.
[FYT Android Head Units] leo06:
Sorry, you are wrong. The cam in expects video and that what gets. The 12v from the head unit is to feed the camera but if you already feed the camera with reverse light not needed to be connected. If the canbus box worked properly, all will work too. Do you have the head unit and everything is working? The diagram is incorrect because the brake ctl is not the brake ctl but the reverse camera trigger
[FYT Android Head Units] ludditefornow:
I searched thoroughly and did not find the answer. Why didn't you link me to the answer?

Based on your condescending and unhelpful posts to me, I don't see why projecting at you in this instance is not unwarranted. You had the answers and you chose to not assist. You siloed.

"Prohibit Reverse", was a total red herring and forced me to add more variables into my testing. I now had to test multiple software options and wiring config as well as the incorrect Navifly info very time consuming.

If you feel I need to be banned for calling out this condescending, repugent and unhelpful responses. Go ahead. I have helped more people in this site than I have received and frankly I don't want to be a part of something where your attitude is acceptable.
[FYT Android Head Units] PPCholic:
If you haven't fixed it. I had the same problem with different HU.

I tought my camera or my wiring at the back of the car was wrong.

The reverse camera (12+) signal cable from the back reverse light goes to the REVERSE or BACK cable mostly at the main harness of the HU. In my case it was orange green from XTRONS.

The other red cable at the Rerverse Camera Video In harness is the so called "CAMERA POWER CABLE 12v" it's very irritating that both cable are red and have something to do with camera.

After restarting the HU it worked.