yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] TKMankindv2:
Hello,

Thanks for this information, it does seem the right way to do it. But... how to compile a specific part of the android code, here android_frameworks_base ?

I mean, despite my lack of knowledge in development, there are multiple wikis who explain how to set up a build environment for LineageOS compilation, git interaction etc. and so I have a Xubuntu LTS on Virtualbox to do so. But there is nothing about compiling only android_frameworks_base or others. Each time I try something (make, mmm, etc.), there are always errors. Well, make services works, but give no files.

I can launch a full compilation of my actual fork of LineageOS with your correction as the environment is created for that, but I bet it will be SLIGHTLY longer :D than compile only android_frameworks_base, or a module from it.

Can you explain how you compile it ?

EDIT : Ok... I think that I need to build the full OS BEFORE trying to get one module only, for dependencies sake. Am I right ?
[Nexus 4 Q&A, Help & Troubleshooting] labs20:
dialer.diff

Hi, what is the purpose of dialer.diff ??? :confused:

Thanks
[Nexus 4 Q&A, Help & Troubleshooting] bilatche:
UP
[Nexus 4 Q&A, Help & Troubleshooting] digital0:
You don't need it.
[Nexus 4 Q&A, Help & Troubleshooting] RomeoRoot:
Fix for Samsung S7? (SM_G930F)

Hi all,

Tried this on a Pixel and worked perfectly.

However this doesn't work for my S7!

I read on another forum that this is because on the S7 the app only replaces the front end not the back end so the proximity sensor remains unchanged :(

Does anyone know of any dialers for the S7 that disable the proximity sensor/keep the screen on permanently while on calls?

Thank you!
[Nexus 4 Q&A, Help & Troubleshooting] TKMankindv2:
Hello,

Ok, so I tried the method from Shimakaze in the post #61 and it didn't work. I think that it is my fault, as I use a LineageOS+microG system but there is no source code available to download and modify/compile, only a Docker app who don't seem to work on my virtual machine (I don't understand how Docker work, to be honest... it is so confusing...). So I tried with a pure LineageOS version as the base, coming from the same day of the microG release, but the result bricked my phone. TRWP, reinstall, fine again.

Only way remaining, modify Dialer.apk directly. Chances that a LineageOS+microG has a different Dialer.apk than a pure version is rather low, so I modified it from my pure LineageOS version and applied it on my phone (I first renamed the original Dialer.apk, restarted the phone, then install my Dialer.apk like any other apps because I didn't use Minimal ADB (check post #71)) = it works. Well, the FIRST launch did crash -maybe because of the lack of authorizations that I granted after that- but it works fine since then. Now, I know how create my own Dialer.apk at will.

Still, I don't use the same modifications than the post #17 or the linked #253.

Well, it is VERY close of #17. In the ProximitySensor.java file, he added a variable and modify an IF condition in the class constructor, to make sure that the new variable disable the "wake lock" (the IF condition define a variable called mProximityWaveLock. If mProximityWaveLock remains null at all times, the screen will remain on). It does sound more professional, at it is possible to restore at will.

For my case, as it is necessary to modify the file anyway at each update of all the source code, I removed the condition itself and only keep the declaration of mProximityWaveLock at null, like in this image :

https://i.imgur.com/MluwOKP.png

It is less professional, but easier. I just had to remove 5 lines :) Of course, the Power button will shutdown or wake up the screen at will without any effects on the call (don't forget to remove the "Stop call with Power button" function in system parameters).

I share here the Dialer.apk I have, but it is for LineageOS 14.1 (7.1.2_r36, NJH47F), not for any 8.x version. And obviously, I have only tested on my old Samsung Galaxy S4 (i9505 / jfltexx) who don't have any LineageOS 15.x so I can't do more. And no clue on other devices :

http://dl.free.fr/qXLmhzAtW

EDIT : Oups, so there is a latency to each post created. I didn't know :D

EDIT 2 : I don't abandon the idea of using post #61. Disable it at a system level would be so much more convenient. I just have to find a way...
[Nexus 4 Q&A, Help & Troubleshooting] bilatche:
Thanks I will try this apk.

I'm on nougat on my 9505.

Just have to install the apk without anything else?
[Nexus 4 Q&A, Help & Troubleshooting] TKMankindv2:
In all cases, you have to rename the old Dialer to make it powerless and so avoid any problems (and be able to restore if needed). It is located in /system/priv-apps/Dialer. Rename as Dialer.bak or anything else, as long that you don't delete it.

For the rest :

*** If you are NOT using Minimal ADB (available in XDA) or the official ADB (too heavy, I don't recommend it), you will have to install it as any other application/dialer. Because if you try to just place the new file in the same location than the old one, it won't work, period. So first, rename the old one, then reboot (the old dialer should disappear from shortcut bar and apps list), then install the new one and configure.

*** If you are willing to install Minimal ADB, then you can do better : rename the old file (DON'T reboot for the moment), activate the USB debugging in the device (System parameters > Developper Options), make sure that root access are given to "Applications and ADB", and then you can use the method described in post #15, and now you can reboot (using "ADB reboot" command). The new file will take the place of the old one (that you have to rename anyway) and it will work this time. Lastly, disable USB debugging :)

In both cases, the first start will crash the app, because of the authorizations. Once granted, it will be good.
[Nexus 4 Q&A, Help & Troubleshooting] Shimakaze:
Sorry, I haven't checked the forums in a long while.

I've never heard of LineageOS+microG before, but taking a quick look, it seems like the Docker image will do a full build when run. Think of Docker images like recipes for a VM crafted to do very specific things. In this case, the image is created from an Ubuntu base image, and contains bash scripts that will essentially do all the steps required to perform a full LineageOS build with microG.

One of the first steps to perform a LOS build is to pull remote sources, as you can see here at this line in the script: https://github.com/lineageos4microg...1af491962552b9cd236cb271128c/src/build.sh#L34. You can modify that line to point to your fork of the remote resource manifest. In your fork of the manifest, you would want to modify the "frameworks/base" project to be sourced from your own fork that has the proximity sensor fix. By doing this, when you run the Docker image, it'll build LineageOS+microG from all the default sources, plus your modified "frameworks/base" code.

All of this of course hinges on you getting Docker to work, which is beyond the scope of my post. There are plenty of resources that you can google to help you with that. Good luck!
[Nexus 4 Q&A, Help & Troubleshooting] bilatche:
Hi everyone

Does an Oreo update if this moded apk dialer exist?

When will if be released?

Thanks.
[Nexus 4 Q&A, Help & Troubleshooting] Rhaegar85:
Big help, thank you and yes this one doesn't hide the answer button for an incoming call. Thanks again!
[Nexus 4 Q&A, Help & Troubleshooting] msainani:
This doesn't work with Lineage 15.1 (Oreo 8.1)
[Nexus 4 Q&A, Help & Troubleshooting] digital0:
I recompiled Dialer.apk for Lineage 8.1. I also post instructions how to do that in the future:

According to https://xdaforums.com/chef-central/android/how-to-build-lineageos-14-1-t3551484 I used these commands on Linux PC :

repo init -u https://github.com/LineageOS/android.git -b lineage-15.1

repo sync

patch the source file packages/apps/Dialer/java/com/android/incallui/ProximitySensor.java with the attached diff file or make the corrections manually

make Dialer DISABLE_DEXPREOPT=true WITH_DEXPREOPT=false

you will find Dialer.apk in ./out/target/product/generic/system/priv-app/Dialer/Dialer.apk
[Nexus 4 Q&A, Help & Troubleshooting] bilatche:
Wow nice thank you! I will try this new dialer apk for 8.1 with the simple method which worked on nougat (juste replace in system/app....)
[Nexus 4 Q&A, Help & Troubleshooting] bk0012000:
OMG!! I have been having problems since I upgraded to Lineage 15.1 (Android 8.1) with the dialer and the proximity sensor. Nothing I tried worked. I used to replace the dialer in Lineage 14.1 and that worked, but didn't know anyone did an update for 15.1. I downloaded your dialer for 15.1 and NO more blank screen on calls. I can't say thank you enough!!

---------- Post added at 04:55 PM ---------- Previous post was at 04:49 PM ----------

Thank you!! It works great on my Samsung Note 4, N910P, using Lineage 15.1.......spent many days trying to research any proximity sensor apps, nothing worked.....Thank you again!!
[Nexus 4 Q&A, Help & Troubleshooting] furi0n786:
I likewise have the proximity issue with my SM-N910F Galaxy Note 4, under Nougat I replaced the dialer.apk file as described here in an earlier post.

However, I've since 'upgraded' to Resurrection Remix 6.0 (Oreo/Lineage 15.1) and attempted to replace the dialer.apk as before -

1. Rename existing app in /System/priv-app/Dialer

2. Copy new Dialer apk to this location, renaming as necessary.

3. Set permissions

4. Reboot phone

Unfortunately, when I launch the app it force closes immediately. Where am I going wrong? Or could you please provide the steps you followed to succeed?

Thanks

***Please ignore request for help, I somehow mixed up several dialer.apk's and initially used the wrong one. All working now. Great, thanks Digital :good::laugh::victory:
[Nexus 4 Q&A, Help & Troubleshooting] bk0012000:
I don't know what to tell you. It works for me with rippee's uploads. Rippee's is at https://xdaforums.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969

You've done what I've would have checked, but it works great for me....I'm on 0410 and it still works...
[Nexus 4 Q&A, Help & Troubleshooting] bk0012000:
Just confirming you tried the dialer apk from Digital0 posted just above? Thats the one I used....
[Nexus 4 Q&A, Help & Troubleshooting] furi0n786:
Thanks for responding, embarrassingly, I was using an old Dialer apk thinking it was the latest version from this forum. All working. My phones only shortcoming is the fingerprint scanner, it fails to register a single scan at all, frustrating but not a deal breaker despite most reporting it now works :(

Thanks
[Nexus 4 Q&A, Help & Troubleshooting] bk0012000:
Glad I could help. I know the people in XDA are the best! Ripee's uploads have done alot with the fingerprint scanner. I don't use it so I don't know, but alot of people who use Ripee's ROMs are successful with it. I am having problems with the hotspot not providing internet access. I think that is Lineage wide tho.
[Nexus 4 Q&A, Help & Troubleshooting] droid.developer.ashish:
So now i am in Resrruction remix 6.0 , replaced the dialer apk with digital0's apk.. outgoing calls work fine but face reboot on incoming calls.. any help please?

Can u update that apk from present source please?
[Nexus 4 Q&A, Help & Troubleshooting] ze7zez:
I just checked that Proximity Service version 1.1 works on Nitrogen-OS-O.

Access to version 1.2 and higher is on the author's website ssaqua - ProximityService.

Let someone check if the app does what you want.
[Nexus 4 Q&A, Help & Troubleshooting] digital0:
You quoted the info i gave about how to recompile dialer.apk. Please get the Resurrection remix 6.0 source and compile dialer.apk.
[Nexus 4 Q&A, Help & Troubleshooting] H0ss1:
hey Digital you work its amazing!

Its possible to recompile the Google Dialer from PixelExperience Oreo 8.1 without proximity sensor?
[Nexus 4 Q&A, Help & Troubleshooting] digital0:
If the source code of the Google Dialer from PixelExperience Oreo 8.1 is available - yes.
[Nexus 4 Q&A, Help & Troubleshooting] H0ss1:
Hey Digital0 i think the code is here but really idk anything about coding https://github.com/PixelExperience

Tell what ever you can do
[Nexus 4 Q&A, Help & Troubleshooting] digital0:
I will not do anything. i posted instructions how to recompile dialer.apk yourself, so do it or find someone who does it for you.
[Nexus 4 Q&A, Help & Troubleshooting] LeChat84:
Oh thanks ! You solve my broken proximity sensor problem !

<3
[Nexus 4 Q&A, Help & Troubleshooting] Fif_:
If you have Xposed and XPrivacyLua, there are custom hooks that I wrote that can block the proximity sensor in any app...

XPrivacyLua: https://xdaforums.com/xposed/modules/xprivacylua6-0-android-privacy-manager-t3730663

XPrivacyLua Pro: https://xdaforums.com/general/paid-software/xprivacylua-pro-companion-app-t3743040 / https://lua.xprivacy.eu/pro/

The hooks you need (these can be installed directly from inside XPrivacyLua Pro):

https://lua.xprivacy.eu/repo/view?id=89

https://lua.xprivacy.eu/repo/view?id=88
[Nexus 4 Q&A, Help & Troubleshooting] Rhhs:
how should i install this, i readed all the replies of this thread and others in the site searching for a solution, i dont know how to install this, please help :(
[Nexus 4 Q&A, Help & Troubleshooting] digital0:
Replace Dialer.apk in a location which is written in https://xdaforums.com/showpost.php?p=69744456&postcount=12
[Nexus 4 Q&A, Help & Troubleshooting] Rhhs:
Thank you, it is working great now ?
[Nexus 4 Q&A, Help & Troubleshooting] revalero:
Very simple, Magisk + Xposed + Sensor Disabler.

The sensor value "mock sensor value" must be set to the maximum. :D
[Nexus 4 Q&A, Help & Troubleshooting] jacobyo7:
I love you ! You just saved my ass with your thing, nothing would work but xposed module "sensor disabler" but it don't support oreo so I was stuck on 7.1 , then I decided to try your thing and it work ! It is even better because it start by itself after a reboot, where I had to "mock the sensor value" after every boot with the other module ! You are a real hero of XDA my friend you just made my day i'm really really happy !!! Thank you 1000000x !
[Nexus 4 Q&A, Help & Troubleshooting] scoopspoof:
Why don't people realize how godly this fix is? Thankyou so much for making my oreo usable again!
[Nexus 4 Q&A, Help & Troubleshooting] Oyvindo:
Hi Folks, I tried to install the dialer.apk build version 11 on my Galaxy S6 running Lineage OS 16 (Android 9 Pie), but unsuccessfully.

I first renamed the original /system/priv-app/Dialer/Dialer.apk.org and then saved the above dialer in the same folder and rebooted. The result was a 'broken' file that would not install.

Then I saved it in the 'download' folder and installed it from there. Now the program ran, and everything seemed just fine until I tried to actually place a call - and the dialer crashed - over and over again.

However - calling into the phone, worked just fine (and the proximity didn't interfere with the call) !!!

So I feel I'm close - but not quite there yet.

What did I miss here?

Please help?
[Nexus 4 Q&A, Help & Troubleshooting] Silie86:
Oh may god, thanks ! You solve my broken proximity sensor problem ! XDA are the greatest!
[Nexus 4 Q&A, Help & Troubleshooting] pay4php:
Recompile dialer.apk for lineage 16/android 9 pie

Can any one Recompile dialer.apk for lineage 16/android 9 pie so that proximity problem in dialer can be fixed for this version also? Help would be appreciated because I can't call with my latest lineage 16 due to blank screen.
[Nexus 4 Q&A, Help & Troubleshooting] jonipin:
Finally did it!!!! God dammit took me over two days to git clone the repo from lineage OS! thx to digital0! but he could have warned us about needing to sync the full repo to recompile just one apk.

The repo is 100GB im size!!!

It's finally Here Lineage OS 16 Dialer.apk

Used the same code that digital0 used.

Cant upload here file is too large so Here is GDrive Link: https://drive.google.com/open?id=1AjT4cXc3ULQMniU9EeLb759qpzFw7Kcg
[Nexus 4 Q&A, Help & Troubleshooting] gezgin78:
I tried this, the person closes when clicking search can you fix it thanks
[Nexus 4 Q&A, Help & Troubleshooting] xLoyd:
It works on LG Fino Lingage OS 14.1

many thanks
[Xposed Framework Modules] MrGodMan:
Can we have atk/def/sta available in hex as well as dec?
[Xposed Framework Modules] mirosz:
show me an example please :)
[Xposed Framework Modules] MrGodMan:
Instead of the atk using numbers 1 to 15 (decimal) it uses 1 to F (hexadecimal). This keeps the individual IVs as single characters for easier formatting.

eg a 15/12/5 Pokemon would show as F/C/5. This also has the advantage that you can remove the spacer character between each part.

PS, just installed app and it works good for me :D Thanks for keeping the app updated since elfinlazz seems to have stopped development.
[Xposed Framework Modules] crafty35a:
Hey, glad to see you are picking this project up. Unfortunately, the custom format still doesn't seem to do anything for me. Also, the preview text below "Set custom format" never changes to reflect the format I entered (it does change in the previous version of this module).
[Xposed Framework Modules] nnrs1:
What's differences can you see between "ignore nicknamed pokemon" option when it's actived or not ?

Envoyé de mon SM-G935F en utilisant Tapatalk
[Xposed Framework Modules] mirosz:
The displayed text doesn't reflect what you have entered. Your changes are only visible in the edit field (after clicking "Set custom format")

What language and device are u using? please post the exact custom format u used.

if this option is enabled, the monsters you rename by hand on your own will not get overwritten by pogo ivy

thx, good to hear its working for u.

want upper or lower case? :)
[Xposed Framework Modules] crafty35a:
English, Nexus 5x, Pure Nexus rom. I even tried just setting the custom format to "%NICK%" but I still just get the default format in game.
[Xposed Framework Modules] MrGodMan:
uppercase please :)
[Xposed Framework Modules] mirosz:
which xposed version u using?

try to change devices language to french just to test if its language problem

edit:

ahh i think ive found the problem: https://github.com/rovo89/XposedBridge/issues/102

edit2:

try changing permissions like this using root browser:

/data/data/info.xposed.mirosz.pogoivy/shared_prefs/info.xposed.mirosz.pogoivy_preferences.xml -> 664

and

/data/data/info.xposed.mirosz.pogoivy/shared_prefs/ -> 755
[Xposed Framework Modules] crafty35a:
v86 -- French doesn't seem to help.
[Xposed Framework Modules] mirosz:
http://xdaforums.com/showpost.php?p=68483222&postcount=10

^^ edit2 ;)
[Xposed Framework Modules] crafty35a:
Doesn't seem to work. The file was already set to 664. I changed the folder to 755 and rebooted but still no luck.
[Xposed Framework Modules] mirosz:
damn got a bootloop while testing a workaround :D

ok the last solution is to manually change the format in the preferences file :/

maybe there's a fix comming soon for xposed
[Xposed Framework Modules] The invisible Lord:
Great Module so far. Thanks for your work!
[Xposed Framework Modules] crafty35a:
The prefs file actually does contain my custom format, so I don't think that is the issue.
[Xposed Framework Modules] TheJakee:
Thanks for updating this module I was wondering if the original was ever going to get updated again. I have one problem though when I disable the module within the POGO Ivy app it doesn't actually disable it for me. I can still see my IVs when I disable it.
[Xposed Framework Modules] mirosz:
u need to restart pgo app, its not chnaged on-the-fly
[Xposed Framework Modules] TheJakee:
I did restart it and nothing happened. Heck, I even restarted my whole phone and nothing happened. The Pokémon still had their IVs next to them. :(

I'm using the OnePlus 3 and everything worked fine in the old version.
[Xposed Framework Modules] crafty35a:
Maybe you still have the old module active?
[Xposed Framework Modules] fiveighteen:
What do you mean the base attack and defense "is not up to scratch"? You're right, for now, about only caring about getting the highest attack for beating gyms and the highest defense/stamina for guarding them, but what about when trainer battles become a thing? At that point, you will want some balance like in the main games, which is where my suggestion will become more relevant. We're talking apples and oranges. I'd implement it myself if it were open source..
[Xposed Framework Modules] Dan_Jacques:
Well, the 0.37 update its worse than ever.

Magisk works, I can use root without issues after start pokémon go (and while it keeps in memory). Other Xposed modules (not related with Pokémon GO) works normally. But I cant play without it.

Lets go back to .35 and see my IVs again.
[Xposed Framework Modules] spamir:
HP Settings

Can we have HP and remaining HP? It'll help when reviving with the optimal potions.

Loving the module so far!
[Xposed Framework Modules] M-A-X:
Hey. Any idea of a workaround for 0.37? I cant find a good working IV Modul :(
[Xposed Framework Modules] ianmacd:
Downgrade to 0.35.0.
[Xposed Framework Modules] GeneYuss:
That release only works with 0.35, missing out on the buddy system kind of sucks and Niantic is going to force update sometime. I'm using the new update 0.37 and I'm appraising each Pokemon I catch and only keep 82%+.
[Xposed Framework Modules] steal25:
Not a "real" work-around, but if you have a second device that you dont play pokemon on just keep 0.35 on it and use this module. Then I rename the pokemon to IE: Vaporeon92 then you know the IV on the device you play on. Not as good as using the module but good enough till a new module drops.
[Xposed Framework Modules] Gaffadin:
Awesome module. Still using 0.35, so it works great.

Only issue I've noticed: the evolved name function doesn't seem to work for me. I have a Growlithe, for example, and renamed him "Arcanine" to see what his evolution would look like. Instead, all that is displayed is "Arcanine Evolve!!" This is the same for any lower pokemon I rename to check their evolution. The "preview evolve pokemon" option is checked, so I'm not sure what I'm doing wrong.
[Xposed Framework Modules] MrGodMan:
I've also noticed this in the latest version. It did seem to work in previous versions though.
[Xposed Framework Modules] Ramzh:
Not working anymore in my case after the update.... Any solution?
[Xposed Framework Modules] Gaffadin:
Yes, roll back to 0.35.
[Xposed Framework Modules] Ramzh:
Sorry forgot to specify I am on 0.35
[Xposed Framework Modules] Gaffadin:
This module works fine with 0.35, other than the aforementioned issue with previewing evolved Pokemon not working correctly.
[Xposed Framework Modules] Ramzh:
I got it working after 2 re installation dont know what happened the when I updated
[Xposed Framework Modules] El ZiK:
OP is a great fixer :) I'm sure he will fix such issue soon ;)
[Xposed Framework Modules] Campi1995:
I don't know why but it doesn't work for me.. Everytime I rename a Pokémon it just shows, for example, "Glurak Evolve" but nothing more.. No stats..
[Xposed Framework Modules] The invisible Lord:
Not "Glurak evolve", try "EVO NEXT" or "EVO LAST". After that, look at the CP, this works for me.
[Xposed Framework Modules] Campi1995:
Sorry, my mistake.. I meant that I rename a Pokémon with EVO NEXT, for example my Glutexo and then it just displayed "Glurak Evolve".. Nothing else..
[Xposed Framework Modules] MrGodMan:
Read other posts, that feature is currently broken.
[Xposed Framework Modules] Dalamar666:
Niantic forces update to new vers...

bye module =( =(