yashsingh1/xdaforums huggingface dataset:
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I'd like to start investigating the phone calling issue so I tried to build using the Pro1 instructions but the "breakfast pro1x" step doesn't work:

$ breakfast pro1x

16:47:13 Build sandboxing disabled due to nsjail error.

In file included from build/make/core/config.mk:353:

In file included from build/make/core/envsetup.mk:352:

build/make/core/product_config.mk:228: error: Can not locate config makefile for product "lineage_pro1x".

16:47:14 dumpvars failed with: exit status 1

Device pro1x not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).

Found repository: android_device_fxtec_pro1x

Default revision: lineage-20.0

Checking branch info

Using fallback branch: lineage-20

Checking if device/fxtec/pro1x is fetched from android_device_fxtec_pro1x

Adding dependency: LineageOS/android_device_fxtec_pro1x -> device/fxtec/pro1x

Syncing repository to retrieve project.

Fetching: 100% (1/1), done in 1.282s

repo sync has finished successfully.

Repository synced!

Looking for dependencies in device/fxtec/pro1x

Default revision: lineage-20.0

Checking branch info

Traceback (most recent call last):

File "/run/media/kevin/SEAGATE4TB/lineageos/android/lineage/vendor/lineage/build/tools/roomservice.py", line 308, in <module>

fetch_dependencies(repo_path)

File "/run/media/kevin/SEAGATE4TB/lineageos/android/lineage/vendor/lineage/build/tools/roomservice.py", line 228, in fetch_dependencies

dependency['branch'] = get_default_or_fallback_revision(dependency['repository'])

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/run/media/kevin/SEAGATE4TB/lineageos/android/lineage/vendor/lineage/build/tools/roomservice.py", line 262, in get_default_or_fallback_revision

result = json.loads(urllib.request.urlopen(githubreq).read().decode())

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib64/python3.11/urllib/request.py", line 216, in urlopen

return opener.open(url, data, timeout)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib64/python3.11/urllib/request.py", line 525, in open

response = meth(req, response)

^^^^^^^^^^^^^^^^^^^

File "/usr/lib64/python3.11/urllib/request.py", line 634, in http_response

response = self.parent.error(

^^^^^^^^^^^^^^^^^^

File "/usr/lib64/python3.11/urllib/request.py", line 563, in error

return self._call_chain(*args)

^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib64/python3.11/urllib/request.py", line 496, in _call_chain

result = func(*args)

^^^^^^^^^^^

File "/usr/lib64/python3.11/urllib/request.py", line 643, in http_error_default

raise HTTPError(req.full_url, code, msg, hdrs, fp)

urllib.error.HTTPError: HTTP Error 404: Not Found
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
i would assume you have some error in your roomservice.xml, but please, this thread exists to gather feedback from users, we cannot and will not provide help with how to build lineage yourself. there are plenty of places for that, and it just distracts from our goal here. providing good logs and error descriptions is more valuable to us either way. thanks for understanding, we will take a look at the logs.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I just wanted to add that my issue with callers not hearing me is intermittent. I previously had issues calling my Mom but I just had a long call with her without a problem. Afterwards, I did adb logcat and I searched for "Mic0 event failed" and did not find it (and logcat covered the time period of the entire call), so that error may be a symptom of the problem.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
what network are you on? Some use specific routing for IMS calls.

Are you using VoLTE (hd iconic dialer) or standard calls?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I'm on T-Mobile. I'm not sure how to answer your questions but if it helps, I see "LTE" in the top right before I call. Looking at SIM status shows LTE. If I click app info on the dialer, it shows com.android.dialer. I'm willing to try others.

Another note is that when I first got the phone, with stock OS, I updated APN settings as per https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings

They were slightly different than what TMobile suggests. I'm not sure if these were persisted and still apply after I flashed LineageOS, but looking now, they do look similar to what I changed to. For example, TMobile suggests APN type of default,supl,mms and that's what I have now, but when I first got it, it showed more items in the list.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
When you call, does "LTE" stay in the corner or does it go away?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
LTE stays in the corner after the call connects.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I'm currently able to reliably reproduce the issue of the caller not able to hear me. Can someone please provide what diagnostics I should gather? The issue is strange as just yesterday calling was working fine, and I didn't change anything.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
so it would help if you ran 2 commands before reproducing the call issue (yes, in parallel, so ideally in 2 terminal windows):

adb logcat -b all > all.txt

adb logcat -b radio > radio.txt

i've checked the log you posted above, it seems to me that is more camera related than calls? also, if you gather the logs, do not post them publicly, just to be safe (there may be imei numbers, ip addresses, wifi network names, etc in it).
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
Hi, thanks, I'll get that soon! What's the risk of making the logs public? What's the preferred alternative? Maybe an encrypted zip pushed to GitHub and then sending the password privately through this forum?

Yes, I posted a log of the camera issue but I also posted an earlier message for the phone call issue and the timestamps as well. The log is above but I'm going to delete it now and anyway I'll re-create the issue with the additional logs...
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
thanks, you can direct-message me with the pastebin (or github gist) logs, or zip them up and send me the zip.

as i said above, logs may contain at least parts of the number you called, mac and ip addresses, imei numbers, wifi network names, etc.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
Unfortunately, just yesterday, the problem was happening consistently, but today it went away! I'm sure it will come back and I'll gather the additional logs. Here is a re-upload of the previous failure in an encrypted zip: https://github.com/kevgrig/Pro1X/raw/main/callerdoesnothear/originalfailure.zip

I will send you the password privately, and if any other verified developer wants to help, please reach out to me privately and I'll also send the password.

For reference, I also gathered both adb logcats (at the same time) of a successful call: https://github.com/kevgrig/Pro1X/raw/main/callerdoesnothear/callworks.zip
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Regarding phone calls I noticed that I hear no ringing tone when I call someone. Complete silence. This happens on calls with an "hd" sign. Once the other end picks up we can understand each other without problems.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
I use a headphone with cable. When I do a phone call I hear myself loudly echoed back from the headphone's microphone into the earplugs.

Edit: No problem with these headphones on other devices.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
I have a keyboard with German layout. Since using the 20230209 version I can use shift + number keys to type special chars like $%& etc., but I am still not able to type any special chars on the letter keys. For example, @ is on Q and would be typed with the yellow arrow key, but it only prints q.

Do I need to do anything regarding the setup of the German keyboard for the yellow layer to fully work?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Andross Guile:
I'm on Google Fi (which is also t-mo I think) and am also experiencing the issue where the caller cannot hear me. I'm also getting lower speeds on wifi and LTE than I'd expect. Happy to provide logs if needed!

I've also noticed that AptX appears to be broken. This was also an issue on the stock firmware, in fact Lineage appears to gracefully fall back to AAC if supported. On stock I don't get any audio at all unless I disable HD audio and use SBC. Am I the only one with this problem? I was under the impression the SD662 supported Bluetooth LE audio.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
Good to know I'm not the only one! I believe they'd like the following data. In one terminal window, run

adb logcat -b all > all.txt

In another terminal window, run:

adb logcat -b radio > radio.txt

Then reproduce.

Unfortunately for me, it was reproducing for a solid couple of days, but has been working fine since (no clue what changed).

I also feel like my LTE is much slower than my older phone.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] justme8800:
For what it's worth, the microphone-disabled-during-phone-call bug isn't limited to LineageOS. I've suffered the same bug on F(x)tec's ungoogled vanilla android release since I started using the phone a month ago.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Is anyone using a cable headset and has audio trouble? I noticed the following issues:

* Audio playback does not stop after pulling out the headset's cable from the audio jack.

* Phone calls often only work on speakers, but not in "normal" mode or with a headset plugged in. This seems to be a bit erratic and a reboot helps for a while.

* Sometimes when the headset is working with phone calls, the phone is echoing the headset's microphone back into the headphone and I hear myself very loudly.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
The caller-not-hearing issue has started happening again! Problem reproduced twice with all and radio traces, both over WiFi and not over WiFi: https://github.com/kevgrig/Pro1X/raw/main/callerdoesnothear/20230224.zip
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I compared success and failure logs of the caller-not-hearing issue and the failure logs alone have the message "voice volume failed" which sounds like it lines up with the problem symptom. I found a post with the same error that was fixed by seemingly enabling Fluence . I searched all of ~/android/lineage for "setprop persist.audio.fluence.speaker" but couldn't find anything. In the commit, there was a comment referencing another commit that changes some variable types. I applied similar changes to hardware/qcom/audio/hal/msm8974/platform.c and ardware/qcom/audio/hal/Android.mk, re-built with brunch pro1x, and installed the new build, but the caller-not-hearing issue is reproduced and adb logcat still shows "voice volume failed". Any ideas appreciated, particularly on how to enable Fluence, if that's possible.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
to modify most audio settings, you are not going to have to modify the source code and build yourself. it is rather easy to remount the partition r/w and then take a look at /vendor/build.prop

restart the audio service or reboot the device and you are set.

in other news, there is a new build up now :)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
Just tried the 20230301 build and still facing the caller-not-hearing issue.

I'll check out /vendor/build.prop, thanks. I noticed a few other differences that are only in the failing logs preceding the "voice volume failed" messages so I'll be investigating them next:

voice_get_cal: No cal data for cal 8!

voice_send_cvp_register_dev_cfg_cmd: DSP returned error[ADSP_EBADPARAM]
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Andross Guile:
OK I made a phone call where the other party can't hear me and then did a speed test on wifi and LTE. sent logs to qsnc... hope it helps!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I tried to apply the aforementioned commit to enable fluencepro but problem is still reproduced so I guess it's something else

$ adb shell grep -e ro.qc.sdk.audio.fluencetype -e persist.audio.fluence.voicecall -e persist.audio.fluence.speaker /vendor/build.prop

ro.qc.sdk.audio.fluencetype=fluencepro

persist.audio.fluence.voicecall=true

persist.audio.fluence.speaker=true

BTW, I tried to re-mount /vendor rw but edits would result in "no space" errors:

QX1050:/ # mount -o remount,rw /vendor

QX1050:/vendor # sed -i 's/persist.vendor.audio.fluence.speaker=false/persist.vendor.audio.fluence.speaker=true/g' /vendor/build.prop

sed: short write: No space left on device

Then I tried to unmount and remount but couldn't:

QX1050:/ # umount /vendor

umount: /vendor: Device or resource busy

QX1050:/ # mount -t ext4 -o rw,seclabel,relatime,discar /dev/block/dm-3 /vendor

mount: '/dev/block/dm-3'->'/vendor': Device or resource busy

In any case, I re-built the whole build with the changes to device/fxtec/pro1x/vendor.prop

Anyway, it seems the proximate first issue is the following (not seen when issue is gone) which I'll investigate next:

03-01 22:43:23.508 0 0 E voice_get_cal: No cal data for cal 8!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I know XDA aren't F(x)tec, but I think you all should be aware of how F(x)tec are behaving as the Pro¹X's brand is directly tied to XDA: https://community.fxtec.com/topic/3...errible-is-it-incompetence-or-something-else/
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
guys, i will not have this kind of bashing in this thread. it is meant for LineageOS matters on this device only, not for complaints about fxtec, xda, or anything else. please follow the rules.

as you are well aware, LineageOS can't change anything about the hardware or practices of the involved partys you are not happy with.

@kevgrig: you followed the wrong procedure. most new android devices implement dynamic partitions, so you will need to do this: https://android.googlesource.com/platform/system/core/+/master/fs_mgr/README.overlayfs.md

@Andross Guile: thanks, i will check it out!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] zstas:
can confirm that arrows work correctly in the last release. thank you!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Schuhabtret0r:
Someone installed MindGapps 13 arm64 ?

Sideloaded lineage and MindGapps, but Only Lineage Working after reboot.

Fix:

Reboot after lineage sideloading to recovery and apply gapps after that reboot
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
new release up!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Andross Guile:
With the latest update, my bluetooth is now failing the way it used to on stock: if I leave HD audio checked, it will show that I am streaming qualcom aptx however I get no actual audio playback on two different headsets. Unchecking HD audio causes the phone to fall back to SBC, which works and gives me sound. Are others experiencing this or is it just me?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Schuhabtret0r:
unoffical cant be updated thru options update or ?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Andross Guile:
Correct, you need to flash/sideload zips to update. FWIW, something always seems to go wrong with installing GAPPS that causes me to need to FDR every time I do an update, which is less than ideal obviously. Is likely due to rank incompetence on my part.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Just to make sure: You do only sideload the GApps once on initial installation, not after an update. Otherwise it'll break und you'll need the factory reset.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
For anyone who's late to the party or needs the *.img for other reasons again, where can one find the following files now?

dtbo.img

vbmeta.img

recovery.img

The link https://mega.nz/file/hb9FWJgA#SRF1XqdWGpNAQGD4ozob8eoFrNN3Y2Q0hzESHJ_0sZE only points to the file lineage-20.0-20230322-UNOFFICIAL-pro1x.zip
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] rasva1:
One thing I noted with this release - notification LED does not lit during battery charging if brightness is set to lower level than 100%.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
my bad, the link is now corrected :)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
I noticed a few things with this release:

Camera in Signal works again, yay! But it's not perfect. In some apps it's not focusing correctly and everything is blurry, so it cannot read QR codes.

Background setting is empty and I cannot change the background. I also noticed that when the first setup assistant asks you to pick a background, the background app crashes.

I am not able to use FIDO2. My Yubikey is neither working via NFC or USB. I tried Chrome and Firefox as browser for the FIDO2 login. NFC is working though, I was able to use it with my government ID.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
The camera still does not work in Threema. The image gets stuck after showing one or two frames.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
uploaded a new release (march 31, usual download spot).

a bit of punching in the dark here, so... please do test audio, especially over bluetooth (and try if aptx works, i cant, dont have any aptx capable endpoints)

let me know how it goes please

beware: this might actually make things worse, so dont try if you are risk averse :)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Andross Guile:
If I don't sideload gapps along with the update package, I get continuous force closes from google fi and play services upon first reboot. After restarting, the phone bootloops and won't make it past the spinning blue logo. Copying gaps along with lineage restored the phone, however fi continued to crash until I reinstalled it. Play services continues to complain about a blocked SMS permission however when I clicked allow, the permission setting did not change. SMS I'm also not able to use the Google assistent because it seems to think there is no internet connection. (which there is, wifi and data work fine and so do SMS's. Though airplane mode was turned on at first for some reason) This happened last time as well and I ended up doing a FDR which resolved things.

Edit: youtube also force closes on launch so I just went ahead and did another reset. Also worth noting that my aptx and in-call mic audio are in the same state as before. (AKA broken)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Correction: The camera still does not work for taking pictures in Signal with the app version from March 22. It just worked for reading the QR code for linking with the signal desktop app. I'll try the current version after Easter.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
ok people, another test build. try and see if it improves any of the audio related issues (call problems? better? worse?)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] PIKA!:
After trying, various sensors do not seem to work. Is this a ROM-specific problem?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
such as what sensors?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] zstas:
If you have installed custom non-android roms (like droidian or UBPorts or sailfish), you have to "restore" sensors. Please take a loot at [0] at the chapter "Repair sensors/ folder in persist.img"

[0] https://community.fxtec.com/topic/3...ecific-partitions/?tab=comments#comment-62622
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Not on the one in this thread.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] PIKA!:
This is exactly what happened.

That solved the problem, thanks!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Official lineageos builds roll on Thursday!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] zstas:
hooray!

LineageOS Downloads

download.lineageos.org

thank you guys, you're amazing!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
you're welcome -- first post updated to reflect the changes.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Benni:):
I installed lineage on the Pro1x today and I have a very strange charging problem - and I'm wondering if somebody can reproduce.

(message translated from German, sorry)

When plugging it into a "dumb" USB port, it's showing "is charging slowly" and predicting 1h20min for ~90% charge to full.

My Pro1 on the same charger and cable says 16min and just "is charging" - after a very short "ping of "is charging slowly".

/sys/class/power_supply/battery/charge_type reports "Fast" - while Android reports: slow charge

---

When plugging in a fast-charger it alt least says: "charging rapidly" but still predicting 1h20min for ~90% to full.

I observed ~6h from 60%.

It's also not getting warm when charging.

I flashed dtbo and I installed Magisk.

Update: I found: https://community.fxtec.com/topic/3588-android-1112-charging-issue-reproducible-trigger-method/

But I can't get it to charge at a reasonable speed (tried pressing power for 10s and attaching an OTG device)

UPDATE: My other dumb charger leads to a prediction from ~70% to full of a 1h10, so I don't think Lineage has anything to do with the very slow charging.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] dicer42:
backb I have an orientation problem when taking videos with the standard camera app. I usually take landscape videos, but sometimes the videos are displayed in the wrong orientation when playing them back after recording.

Took me a while to figure this out but I can reproduce like this:

1. Close keyboard

2. Hold phone in landscape and launch camera app (from desktop)

3. Switch to photo mode

4. Switch to video mode

5. Record

This produces wrong orientation in resulting videos for me, even though the UI is displaying the orientation correctly. I also have the "horizon level" enabled and it shows correctly.

The workaround to make it record properly: Rotate the phone to portrait and back to landscape while staying in video mode. Subsequent videos are correct. Switching to photo mode and back to video mode break videos again.

Things get really bad when the keyboard is out in landscape mode. Then the UI is weird and the level already displays wrong (the level always displays correct in the cases described above). The resulting videos are always in wrong orientation.

Can others reproduce this?

Also: I can't seem to scan any qrcodes with the default camera app in scan mode. Is this a known issue?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] dicer42:
For me call quality seems to have worsened. Now sometimes the call only connects really distorted and people

hear me like a really bad robot/speech synthesizer.

I never noticed this before switching to the april builds. Doesn't happen all the time though and might be related to wifi calls only. Couldn't find a pattern yet. Most calls are good