thank you it works.Use the jio call app from play store, just be sure to keep data and location on all the time, it works for me...
Got any permanent solution...?? Coz when connected to wifi it goes offline. And I don't want to go back to stock.An important notice for jio users,
If the rom you use doesn't currently support VoLTE, then download this app to make and receive calls
And set it up, then you will be able to make calls without native VoLTE support, but a few things are to be kept in mind to use this app without issues,JioCall – Apps on Google Play
HD Voice, Video calls, RCS and Jio FixedLine number on your smartphone!play.google.com
1. Your mobile data must babe enabled all the time, because the app services only work with jio mobile data for now, so, connecting to a wifi network might prevent you from getting any calls
2. You have to keep location enabled at all times, I don't know why but calls won't work without location being on, and also, if you use android 10 or Android 11 you have to manually change the app location access from 'Only while using the app' to 'Allow all the time' otherwise incoming won't work unless the app itself is open
3. Don't worry if you run out of mobile data, this app can work normally even if your data has been exhausted, as long as your mobile data is on regardless of the remaining data
4. Calling from this app won't use your data, so, don't worry about it, this app needs data only to maintain a connection with the jio servers, that's all, and that's the reason calls will still work, because the 5-10kbps speed after exhaustion of your data is good enough for the app to be connected to the jio servers...
Edit: You must never enable battery saver otherwise calls won't come in...
Nope, no other solution, and I did mention beforehand that calls won't work when connected to a WiFi network, if you really want to use calls while connected to WiFi, then you must be connected to a JioFi network, so, yeah, stick to data for nowGot any permanent solution...?? Coz when connected to wifi it goes offline. And I don't want to go back to stock.
It iis stable as I can tell.i hope @jarpeguin you are doing okay and please take your time to develop a stable version of it trust me it will be worth it patiently waiting for it!!
That is intentional. There is no way to support both locking and unlocking via long pressing on the fingerprint sensor, because while the screen is on long press is already tied to launching the Google Assistant.Hi
I install the rom yesterday and found a bug, or I miss a setting.
I cant lock the phone via fingerprint, only unlock is possible.
That is bad.That is intentional. There is no way to support both locking and unlocking via long pressing on the fingerprint sensor, because while the screen is on long press is already tied to launching the Google Assistant.
Unfortunately it's not possible to implement on customs. If you turn off the navigation bar you can customize the actions for long press.That is bad.
In stock rom it was possible and I dont need Google Assitant.
A long press on the fingerprint do nothing here.
You should be able it to swipe up from the bottom to reveal it.2.Bug:
When I open the camera the buttons for back and close are gone away, so I cant close the app.
Thanks for t.he tipp, I dont know thatYou should be able it to swipe up from the bottom to reveal it.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
2021-04-08:
Initial 18.1 build.
2020-10-13:
Initial release.
It was a problem with the F2FS driver.Thank you! Just curious, what was the core reason of the issue?