yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] John Paden:
Same here - ssems this was a 'thendontdothat' idea.

My S10e did boot into TWRP with Power + Bixby + VolUP.

I followed the flow like a dirty flash:

Reboot to TWRP from the reboot menu

wait - 2 min - press vol up to see screen

wipe cache and davlik -> fehler

adb push lineage-17.1-2020xxxx-UNOFFICIAL-beyond0lte.zip /sdcard

Install (flash) LOS17 (lineage-17.1-2020xxxx-UNOFFICIAL-beyond0lte.zip)

wipe cache and davlik ->

adb push beyond0lte-boot-magisk-2020xxxx.img /sdcard

Install (flash) Magisk_Boot (beyond0lte-boot-magisk-xxxxxxxx.img) as boot

(same fstab you have changed before)

adb push fstab.exynos9820.FDE /sdcard

mount menu mount vendor

adb shell

mv /vendor/etc/fstab.exynos9820 /vendor/etc/fstab.exynos9820.bak

mv /sdcard/fstab.exynos9820.FDE /vendor/etc/fstab.exynos9820

Optional: Delete OK Google und X Google from system/priv-app

ls /system/priv-app/HotwordEnrollmentOKGoogleExCORTEXM4/

rm /system/priv-app/HotwordEnrollmentOKGoogleExCORTEXM4/HotwordEnrollmentOKGoogleExCORTEXM4.apk

rmdir /system/priv-app/HotwordEnrollmentOKGoogleExCORTEXM4/

ls /system/priv-app/HotwordEnrollmentXGoogleExCORTEXM4/

rm /system/priv-app/HotwordEnrollmentXGoogleExCORTEXM4/HotwordEnrollmentXGoogleExCORTEXM4.apk

rmdir /system/priv-app/HotwordEnrollmentXGoogleExCORTEXM4/

ls /system/priv-app/

Reboot

-> worked here (puh!)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ichmyselfandi:
Thank you for the reply. But I am unable to boot into TWRP. I just want to pull my user data. But this isn't working with samsung recovery, because of missing root.

How can I be able to download my data? I was thinking about flashing twrp via fastboot. Good idea? Could you help me with that and which twrp I should choose?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
I'm still not sure which files to use in Odin the first time, during Magisk installation. And which files should be patched during the later steps (according to this plan).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Pogromonolith:
I can't answer in confidence, as I'm trying to figure it out myself and still haven't run this yet.

Following [MENTION=3918085]seburton[/MENTION] advice, "the custom droid" tutorial is pretty detailed and should clarify what to patch and when.

He also has a guide to install TWRP after.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] PeePeeKittyPuss:
I know magisk 20.4 just came out but I am looking to update my 20.3 version. Can anyone help me out with this? Ive tried different methods but I keep on getting bootloop
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fusseldieb:
Came here to look for an AOSP ROM for my new S10, and I must say... Wow!

In such a short time we already have a fully working ROM with almost everything working. Come again?

[MENTION=4610599]Ivan_Meler[/MENTION] , congratulations for the hard work continuing the "tradition" of AOSP on our beloved Samsung devices. A true hero.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] PeePeeKittyPuss:
just saw you posted new 20.4 in orignial 17.1 google drive folder. Thank you so much!! I have 20.4 on my s10e lineage rom now!!:good:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] brokenworm:
[MENTION=4610599]Ivan_Meler[/MENTION]

unautorized payments

it was a damn mess with that 2 unautorized payments thru paypal

thx for bieng so damn nice to pay me back long before paypal reacted.

respect.

ill never use paypal again :o

best regards

Marsdroid
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
I have just followed the steps on the*********** to the letter, but still can't get TWRP installed. The first part (installing Magisk) worked fine and my phone is rooted now.

But after I install the patched TWRP using Odin, I reboot to the recovery and end up in the stock recovery.

I just tried installing the recovery using the TWRP app, but that failed. Not sure why.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] seburton:
I don't really understand. If you read carefullfy the custom droid, you will notice you have to replace both stock recovery and AP file with magisk patched at the same time. By doing this, your system and recovery are rooted together so i can't figure why you say "i install the patched TWRP using odin", how are you doing this considering the TWRP must be renames as "recovery.img" and must be in the AP file?

---------- Post added at 01:07 PM ---------- Previous post was at 01:00 PM ----------

You can find some informations by topjohnwu himself for installing magisk samsung devices:

https://topjohnwu.github.io/Magisk/install.html

What he describe here is with the stock samsung recovery.

If you want TWRP, you will need to patch both AP file and TWRP image directly with magisk.

After patching done, you will have a full AP patched (with system patched and stock recovery patches) and your TWRP patched img.

If you want to boot to TWRP instead of stock recovery you just have to replace the stock recovery in then AP file by the TWRP patched.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
The first guide (the root guide) says I have to use the patched AP from stock firmware. I added everything from stock to Odin. At the end of that tutorial I had a rooted phone, so that tutorial was a success.

The second one (installing TWRP) says to put the patched TWRP into the AP-slot of Odin and just upload that one. After uploading, I should boot into recovery. That's when I end up in stock recovery.

Do you mean I have to add the patched TWRP into a different slot during the first guide? Where should I put it then?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] seburton:
Ok i think i understand.

When S10 was launched, TWRP was not available for this device. So it was impossible to install TWRP permanently.

I didn't know the custom droid made two guides. You choose the wrong one...

Can't find the original URL so here is the pdf version of the "good" guide: https://1drv.ms/b/s!AnBD94SVrlpXjB8yMQTl0FVs8JH5?e=4opo4E

I You can find exactly the same process describe here: https://xdaforums.com/galaxy-s10/development/recovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
Ok, seems like it should work. Unfortunately, now I can't get into recovery at all! It just boots into download mode with some errors:

ODIN MODE (AVB FAIL)
recovery: Error validating footer. (0)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM RECOVERY
VBMETA G975FXXU4CTC9 29996307R

I managed to 'fix' it by uploading all stock files using Odin and started the process again.

Unfortunately, when uploading the patched AP-file, I get an error in Odin:

<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 58 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> dqmdbg.img
<ID:0/005> dt.img
<ID:0/005> dtbo.img
<ID:0/005> recovery.img
<ID:0/005> ANDROID!**
<ID:0/005> Unassigned file
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

After a restart I got into download mode automatically: the same error as above. Now I was able to upload the patched file, but rebooting into recovery ended up into stock recovery again.

When I upload all files (BL, patched AP with patched TWRP, CP and CSC) I can't boot into recovery afterwards. I do see a quick blue screen with the message 'Erasing' though. That's a message telling me that TWRP is getting erased again?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lambik333:
TWRP not working for latest CTC9....
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
Which means I have to download an older stock firmware and just follow the steps agan?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ichmyselfandi:
This is not true. The newest TWRP is fully functioning with the newest Samsung Firmware from a couple days ago.

I did it today and everything worked.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
With 'the newest' being 3.3.1.9? That's the one I have been using the whole time. Without success. :mad:

I just noticed that the files are alphabetically ordered: 3.3.1.is the top one, while 3.3.1.10 is far down, but is newer. :silly:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Pogromonolith:
Is it possible to install Lineage 17.1 on a Galaxy S10+ with a Android 9.0 stock firmware?

Or must the phone be flashed with an Android 10.0 firmware before installing Lineage 17.1?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ichmyselfandi:
https://xdaforums.com/galaxy-s10/development/recovery-twrp-3-3-0-galaxy-s10-exynos-t3924856

Choose from there:

G970F (S10e): twrp-beyond0lte-3.3.1-102_ianmacd.img

G973F (S10): twrp-beyond1lte-3.3.1-102_ianmacd.img

G975F (S10+): twrp-beyond2lte-3.3.1-102_ianmacd.img

G977B (S10 5G): twrp-beyondx-3.3.1-100_ianmacd.img
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
Yes, that's the one I'm using now (patched using Magisk), but now I'm back at

:(

I installed all Odin-slots together with the recovery.img replaced in the AP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ichmyselfandi:
https://www.youtube.com/watch?v=7QvGRlyA8NY&list=PLWyAfSK34BC4I210-fLKcLVurHJvx-mBr&index=7&t=0s

All you need to know and already know :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
But he skips the Magisk-part, while the TWRP-guide strongly advises to use Magisk before.. :confused:

And when trying to upload the twrp-tar (renamed the image to 'recovery.img' before), it fails:

<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 0 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> ANDROID! Ç
<ID:0/005> Unassigned file
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fernix_:
That's where you went wrong. The twrp hide strongly advises you use Magisk because of the way OneUI works. In this case, you actually need a stock TWRP and not a Magisk patched one, because you're doing away with Samsung's software for the most part. Magisk is installed using the boot img after installing the rom. byteXpression has a really detailed guide. It's post 505 on this thread I believe.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
That's the post I started with in the first place. :silly:

But then all the guides started to confuse me.

I just installed all stock files, rebooted and rebooted into download. When I try to upload the twrp-file in the AP-slot (other slots empty, right?) I get an error. When I reboot into download, it succeeds. The same for vbmeta_disabler: first time it fails, but after a reboot is succeeds.

Unfortunately, after booting to recovery, I end up in stock recovery again. :mad:

I finally made it to TWRP: I took the stock AP-file, extracted it, removed recovery.img.lz4 and vbmeta.img.lz4 and copied the other versions of those images in. Then I made a .tar file and uploaded it together with all the other stock-files.

[update]

And I'm running LineageOS now! :)

The key for me was to just follow post #505, not installing Magisk (yet) and placing the twrp recovery file and vbmeta in the AP-file from stock.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] medoko:
I do have a fully working "Ivan-LOS" 17.1 (from his update he provided on 02-11-2020) with working TWRP and functional MAGISK app at the moment...

But i am a bit confused right now about the latest 20.4 Magisk update.

Can i just flash the 20.4 (MAGISK) file which Ivan provided (see post i quoted) with TWRP?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] TheMrM00n:
Yeah just flash magisk imahe in boot partition and reboot device
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Pogromonolith:
[MENTION=1129480]amelsfort[/MENTION] Glad you made it! :highfive:

Did you do all of this after rooting with Magisk using the method I've mentioned before (post #871 )?

Also, after you extract the stock AP firmware file, replacing recovery.img.lz4 and vbmeta.img.lz4, when you tar the AP file again using 7-zip, does it not ending up as .tar.tar file?

Did you just delete the extra .tar?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
Hi everyone.

I bought s10e on 10 march and I wanted to know if there was a gain of battery life for those who installed this rom?

Thanks for your answer.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] willy_666:
I was able to flash boot image (original bundled with LOS17.1) with Odin and reboot the device.

[MENTION=4610599]Ivan_Meler[/MENTION]: does the twrp has crypto support? --> OK, reading is key --> no crypto support
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] chong xda:
I'm using s10 plus and the battery life is much much much better than stock
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
I did root with Magisk before, but re-applied all the stock images afterwards. So when I started the whole process, I only had my phone unlocked.

I extracted the AP....tar to a folder, deleted recovery.img.lz4 and vbmeta.img.lz4. Then I copied recovery.img (the one from twrp) and vbmeta.img into that folder, selected all files and archived them to a .tar without an extra .tar. But that's only when you extract the .tar in the first place. It's also possible to remove and add the files direct in the archive. Then there's no need to archive the file again.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] willy_666:
With which Magisk version was the boot image (provided with the latest LOS17.1 build ) patched?

Thank you!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Saumya Mishra:
Could someone post their SOT on the the regular s10 after switching?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Pogromonolith:
Thanks [MENTION=1129480]amelsfort[/MENTION]!

My issue is that when I try to remove and add the files directly in the archive, I get a "not implemented" error in 7-zip.

When I just extract the archive, 7-zip gives me a "There are some data after the end of the payload data" warning.

Was just able to extract the AP file using UniExtractRC2 instead of 7-zip, then replacing the files and archiving again using 7-zip into .tar.

Hope that'll do it.

Just one question - the initial firmware AP file is .tar.md5

After taring it back it ends up just as a .tar.

Is that normal?

Thanks!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
That's perfectly normal. Odin eats both *.tar and *.tar.md5, but checks the content of the latter (and so chewing longer).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] amelsfort:
I got the exact same warning when extracting the .tar. I decided to just ignore it and take my chances. :cool:

I did find some issues though: scanning my fingerprint was troublesome. It looked like the fingerprint target was a bit off and I had to put my finger a bit above it. Anyone else having that issue?

And somehow my phone get locked every time even though I added my home address as a trusted location.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Jab_:
I had the same problem. All you have to do is press power button and power and connect to the computer with you USB c cable, and the screen will go black for a few seconds, in that moment you have to boot to twrp with the key combination. Once you're on twrp you can reboot normally. If you want to update magisk, you just have to download the magisk boot patched, which you can find in the same folder that the Rom, and flash it via twrp (dirty flash is okay). And you're done.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
New builds are up with support for XXU4CTC9 amongst other changes

- April vendor security update (System is still march as april tags havent been released on aosp yet)

- Rebased kernel on top of G97*FXXU4CTC9

- Added dt and dtbo images to rom

- merged G97*FXXU4CTC9 vendor binaries

- Removed simstat service as samsung fixed dual sim device detection

- Updated boot images to Magisk 20.4

- Misc performance and stability improvements

Make sure you also download a new magisk boot image if you used magisk on previous rom version

Big thanks for everyone who supported this project in past as it wouldnt be possible without them also april system security update will be released as soon as google drops source for it
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] vomad:
Ivan you're the best developer! :) Thanks for a new build. Is there any changes on Live Display (I mean color profiles) or still the same?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Saumer:
S10(beyond1lte), I flashed BTA4 firmware before install 0303 LOS, and LOS worked.

after update(without wipe) to 0331, unlock make systemui crash.

(I had using fingerprint+pattern 5x5) so I couldnt use phone.

I success to unlock my phone with fingerprint once luckily. (I dont know how)

after once unlock, fingerprint unlock worked but pattern unlock still make systemui crash.

So I try install(without wipe) 0303 and that problem not appear. (All seems work fine)

in 200303ver, set swipe to unlock to avoid crash in 0331, and update to 0331, softreboot occur.

I tried to boot without install magisk img, but softreboot occur. so It might be not occur by any magisk module.

should I full wipe my phone when upgrade this rom? or I should re-download rom?

+I wipe /data and can boot without problem above.. I'm going to backup all app data now.

is it common that need wipe /data when update custom rom?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ms2204:
Encryption and updating

Thank you very much for this guide. After trying this installation guide, my S10 is now running LineageOS and seems to be stable and working well. I have one question about the encryption parts.

If I perform the encryption steps, and end up with a fully encrypted device, how do I go about updating LineageOS?

How do I go about dirtyflashing LOS?

How do I do a complete flash? (Do I have to start completely over again?)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] zero5liters:
flash boot image

Hey there,

so far so good. Thx to this thread and everyone involved.

I'm running LOS on my 970F with actual Stock, TWRP up and running. But i'm unable to flash the magisk boot Image.

I tried like the other images (Post 505). But odin was unable to flash. One time it went ok right after fresh boot, but Magisk Manager says not installed.

Since that happend i tried it many times but Odin get stuck at deploying the img file.

Do i have to rename the img File before tar'it?

Perhaps someone can give the dummie a hint.

And i tried it oldschool via fastboot. But fastboot didnt work for me. Is it diasabled nowadays?

thx in advance

Matt
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] zero5liters:
Ahhhhh .... ok.

Renaming did the trick. Or at least after renaming and flashing afterwards it worked.

thx

matt
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] catormeme:
i tried updating to the latest version i downloaded the new los version and the magiskboot and now my phone doesnt ulock anymore.

just like last time exept i do have the new files now
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] seburton:
As you should know, battery drain heavily depends on your usage...

There is no perfect answer, maybe people will tell you it's better than stock but, because you have not a strength 4G connection, because you are playin games a lot, or just because you are using others apps than the man said it was betrer, your experience will not be the same...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] DreckSoft:
Currently I'm unable to unlock my phone. The whole story:

- I updated Magisk to 20.4

- The phone was stuck at the boot screen

- I installed the new 20.4 boot image and upgraded LOS to 20200331 from 20200303 (using twrp-beyond0lte-3.3.1-102_ianmacd)

- Flashed the latest gApps (after the first unsuccessful try, so that's not the issue)

- Wiped Dalvik / Cache

Now the phone boots and I can unlock my SIM. But when I want to unlock the phone (PIN) it immediately goes back to the locksceen.

Any ideas?

Maybe important: I was using Launcher 3 prior to the upgrade and going back to 20200303 does not help.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Saumer:
to solve no unlock, choose one of these

1. just use 0303ver. flash previous rom.

2. (If you want to use 0331 ver) wipe /data

it might be not cause by any magisk module or edxposed module.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] DreckSoft:
No, going back to 0303 does NOT solve the issue. I don't wanna wipe /data.

---------- Post added at 05:49 PM ---------- Previous post was at 05:05 PM ----------

Maybe going back to the old Magisk Patched Boot Image will help. Anyone has the version for 0303 with Magisk 20.3?

---------- Post added at 06:13 PM ---------- Previous post was at 05:49 PM ----------

Magisk does not seem to be the issue. "Normal" boot image vom 0303 shows the same issue. There Magisk should be disabled.

---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------

Ok, I just reflashed the Magisk 20.4 boot image (I think for the 3rd time) and currently I can unlock my phone. Will do a full Titanium Backup now and won't touch anything till it is clear what happened.

I'm back on 0303 btw.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ichmyselfandi:
Here is an upgrade instruction from the thread:

7th March 2020, 12:01 PM |#780

After restoring my backup I started the process again. I had a suspicion and it was correct. The smali patcher module I use to enable signature spoofing needs to be uninstalled first. Otherwise you end up in the bootloop.

So basically the upgrade process from LOS 17.1 (19.02) for me looks like that:

(If you do not need the mail app or do not use signature spoofing... well skip the steps regarding that)

1. Backup E-Mail app (e.g. oandbackup)

2. Uninstall Smali Patcher module from magisk

3. Boot into recovery

4. Wipe Cache/Dalvik

5. Flash LOS update

6. Flash magisk boot img to boot

7. Reboot System

8. Create a new smali patcher module and install it via magisk

9. Reinstall E-Mail app. Go to app settings menu and manually grant all permissions the mail app needs.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] PeePeeKittyPuss:
Hello, I installed lineage os on my galaxy s10e and I have magisk. Everything is working correctly but I cant find a way to remap Bixby button. I've tried looking for it in the setting not there, downloaded magisk modules bxmapper didn't work, and also tried installing button mapper from the play store. When I try and give button mapper full permissions it says "because an app is obscuring a permission request settings cant verify your response." Please help thank you
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] vomad:
You can open system/usr/keylayout/gpio.keys and remap key 703 (assist by default). For example I remap it as "CALL" so bixby answers the calls and open dialer.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Dn7o/:
Are there any plans to make this ROM an official LOS release at some point?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
Hello Ivan. Charging when phone is off still has the old issue. Tried LOS from 31. March. Is there a fix for this issue coming? Or any setting one has to make?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] mat_pav:
Hallo. Is there any way to disable the mute button during call. I dont hold the phone on the ear but a little more distant from it so the screen does not turn off with proximity sensor and a lot of times happens that i hit the mute call button. Or maybi is there any way to adjust the proximity sensor so it will pick longer distances Thx for any suggestion.