Related
This is the official thread for the Condi app. Please post your feedback here and I'll do my best to reply.
Condi (was previously listed as Mini Tasker but pent asked us to change the name) is an automation tool for Android 4.0 or higher. It's completely free. It's our first attempt at android programming for a university project we just submitted.
There are many other automation tools, many of them had time to mature, most of them have better support for older devices and some are just irreplaceable, but, having said that, most of them are really hard to operate. If you tried it you know what i'm talking about.
With Condi you can setup most action+condition pair in 6 clicks or less. You don't have to pick names, write down descriptions, you don't need to approximate the radius of your house, set up variables, put up web sites, join a social network and all these other weird requirements other apps force you to do. You get a simplistic experience, the kind you can share with the less technical friends.
Talk about sharing, did you know you can share any set of tasks just by selecting them on the main screen, and clicking share from the menu? Your friend can open the generated link with his Condi app and import the tasks instantly.
We got some amazing reviews from people, and we're gonna work real hard to live up to the expectations. We had to take a short break after 0.2.13 but we're back in business. If you don't mind a lot of consecutive upgrades, and care to send us vital feedback before we push out to the thousands of users we have - please join our beta channel: (subscribe to this group) https://groups.google.com/d/forum/minitasker
You can download the app from the Play Store here.
There's a cool video demo here (thanks Dan Graziano): http://cnet.co/1eXYCqx
Thanks,
Anton Wolkov and Michal Romano
FAQ
Location Based Condition misconceptions
* It does not drain battery - google probes your location regardless of our app so it adds almost no extra drain or overhead.
* It doesn't turn on GPS - but will use it if it's on by another app.
* It doesn't have good accuracy, if you turn off wifi and mobile data it will suck.
* We use Google Play Services' fused location provider with low power sensors preference.
* The condition doesn't start unless the phone is sure you are completely inside the blue circle.
* Choose a bigger radius by pinch-to-zoom-out on the map and click again.
Mixing Conditions
* A task with multiple conditions starts when all are true
* A task ends when a single condition is no longer true
* If you want "OR" relationship between conditions, you need to have 2 tasks. Just use the duplicate button.
* To avoid confusion, starting 0.3.0 you can see and remove the "end" task.
* If multiple actions of the same kind overlap, the automatic end-action is only executed for the last one. If you set your phone to silence at 16:00-18:00 and to max volume when you plug in headphones (2 separate tasks), if you plug in at 16:30 - you're volume will be set to max, but if you unplug at 17:30 the volume will be restored only at 18:00. You can set time to be a "start-only" event, i.e. to add 2 tasks with 2 "start-only" times, this way you won't get an overlap. I am open to suggestions on how to improve this.
Feature Requests
* 3g-4g-2g toggle action (scheduled for 0.3.5)
* Screen lock toggle (scheduled for 0.4.0)
* Hotspot toggle (done)
* WiFi near (scheduled for 0.3.5)
* Bluetooth connected (scheduled for 0.3.5)
Price / Privacy / Tracking
* Is it free? Yes.
* Do you have ads? No.
* Do you track users? No.
* Why is it free? It's a university project, we got an academic grade for this. If you want to say thanks you can put a 5 star review.
* What's the statistics thing on the settings window? We store our own process wake ups but this is only sent if you turn the settings option on.
* Can I have the source code? It will be uploaded to a git repo soon.
* Will there be a premium version? We're gonna keep the client free. We might allow purchasing a server side always-on notification back-end but we will allow you to set up your own server (for free) if you wish.
Misc
* Michal is a girl
Changes Log
v0.3.4.1
* activity log
* call silence white list
* wifi condition, location condition reliability
* start-only conditions reliability
v0.3.3.1
* quick fix for a background crash
v0.3.3
* WiFi tethering toggle
* launching multiple apps bugs fixed
* SMS sending - will attempt to resend on failure
* root actions silently failed - attempt to fix
* calendar reliability improvements
* periodical active location detection setting
v0.3.2.1
* fixed regression in restore values
v0.3.2
* restore actions - yet another fix
* direct links to running tasks dubbed "nfc links"
* German translation
v0.3.1
* airplane mode fix
* restore last state more accurate
v0.3.0.1
* hotfix for users upgrading from older versions
v0.3.0 public
* share + bug report no longer crash when there's no internet connection
* selection bug in the main screen fixed
v0.3.0 rc3
* sharing and market reworked slightly
* directly report bugs and upload local database
v0.3.0 rc2
* mobile data proper detect of current state
v0.3.0 beta 5 (release candidate 1)
* hdmi slimport now actually works
* terminate apps can use root to force close other apps
* timers no longer cancel each other (major reliability bug)
v0.3.0 beta 4 (only in the beta channel)
* hdmi slimport condition
* fixed upgrade bug (crash on start) for people who skipped beta 1
v0.3.0 beta 3 (only in the beta channel)
* sms forwarding and sending should work on kitkat and with hangouts or other non default sms clients
v0.3.0 beta 2 (only in the beta channel)
* new execution engine
v0.3.0 beta 1 (only in the beta channel)
* new main screen with inline editing, labels, duplicate tasks etc
* actions are now split to 2 explicit "start" and "end" parts
* restore last value should work a little better, still a work in progress
* wireless charger support
* street names in the location condition (only for newly added conditions)
* calendar supports repeat events
* send sms can now reply to the last caller using target phone number *69
v0.2.15
* wifi connected condition
* shortcut clicked / app-launched condition
v0.2.14
* Orientation lock added
* Music "Play" button now uses a hybrid of new and old code (both keyboard and broadcast)
* Location auto-description fix
* New name! (and new domain name cond.im)
* 2 new permissions: install shortcuts, edit sms.
How to join the beta
Beta users get much more frequent updates.
You can see your feedback being directly transformed into running code.
A lot of times new code comes to life only when there are enough testers for it.
If you want to contribute, this is a great way.
To get started please subscribe to this mailing list (you don't actually have to get the emails, just be a member)
https://groups.google.com/d/forum/minitasker
Once done that, use the same email to join the beta channel here:
https://play.google.com/apps/testing/il.co.kix.minitasker
Translation Volunteers
If anyone cares to help translating Condi to other languages, or to verify translations please contact us.
No Market Access?
You can download v0.3.4.1 here, but do note that we use Google Play Services so you must at least have that in order for the app to work.
This looks cool for more noob-friendly users
v0.2.14 released
new release requires 2 new permissions
* create shortcuts for a new "app-launched" condition (still not visible in this release though)
* edit sms messages - this will insert the sms messages sent to your messaging app (in a future release)
Hi,
I'm using Condi (Mini Tasker) for about one month. I don't know if this is the correct communication channel to report this but here I go...
One of the things that is annoying me is the fact that the actions are repeating themselves over and over again.
Let me explain with an example that I have.
I have one task to turn on bluetooth every time I'm driving my car. The problem is that when I stop in traffic, at a stop sign or at a red light semaphore, the bluetooth radio turns off, I believe because the conditions (driving) is not fulfilled. I have already been disconnected while in a call...
The thing is that I don't want the bluetooth turned off, I think If I wanted to turn bluetooth off I should have created one other task to turn bluetooth off when standing still.
I think that wold be a good improvement if you can configure the task as "fire and forget", i.e., monitor the condition only when the action is not set.
Another improvement wold be to make a bluetooth device connection/disconnection based action.
I hope to see good news in the next updates
thank you and thanks for this great app
Nero
Good stuff. Appreciate your work. Request: ability to toggle screen lock. When I'm sitting at home, no need to lock screen. When I go to work, no way am I gonna trust those jokers with an unlocked phone!
--
Problems? Search before you read. Read before you ask.
This seems a great project, I'll follow this closely aswell, seems very beneficial in itself. Keep up the great work. When I have some spare time I'll give it a try.
nero said:
Hi,
I have one task to turn on bluetooth every time I'm driving my car. The problem is that when I stop in traffic, at a stop sign or at a red light semaphore, the bluetooth radio turns off, I believe because the conditions (driving) is not fulfilled. I have already been disconnected while in a call...
The thing is that I don't want the bluetooth turned off, I think If I wanted to turn bluetooth off I should have created one other task to turn bluetooth off when standing still.
I think that wold be a good improvement if you can configure the task as "fire and forget", i.e., monitor the condition only when the action is not set.
Click to expand...
Click to collapse
It would be great to let any condition that is currently start/end be start-only. It would also be nice to be able to set a different end action for start/end conditions, e.g. "when driving begins, enable bluetooth; when driving ends, notification pop-up "done driving -- disable bluetooth" so that if you happen to be on a call when your driving ends you aren't disconnected, but you still get the reminder.
Nero, for the time being there is a global condition-end-delay which you could increase to help with this. I think the default is 30s, but if you bumped it to 4 minutes that should outlast any red lights.
---------- Post added at 09:58 AM ---------- Previous post was at 09:09 AM ----------
If a task has multiple conditions, does the task end when ANY condition ends or when they ALL end?
For example, if task is "set ringer and notification to vibrate when time is 22:00-09:00 and AC charger connected", what happens:
(*) If the charger is disconnected at 08:30?
(*) If the time is 09:01 but the phone is still connected?
Another example: if Nero made his condition "turn bluetooth on when driving and AC charger connected", and he happens to be talking on the phone at a long stop light, will his call be disconnected if he's not driving but the charger is still connected?
In the first example, the desired end-task is that the end of ANY condition ends the task. If I get up and take my phone off the bedside charger at 08:30 it should go off vibrate mode. If I sleep late and my boss calls at 09:02 asking why I'm not at work, the phone should ring even though it's still plugged in.
In the second example, the desired end-task is that the end of ALL conditions end the task. If Nero is on the phone at a stop light, he should not be disconnected.
Final thought: if you're on a call and bluetooth is disconnected, the call is still connected and goes to handset, right? So if you're on the phone with a client and you pull into the driveway, unplug your phone and walk away from the car, you continue talking to your client on your handset?
NormMonkey said:
Nero, for the time being there is a global condition-end-delay which you could increase to help with this. I think the default is 30s, but if you bumped it to 4 minutes that should outlast any red lights.
Click to expand...
Click to collapse
I tried that already (with 300ms/5mins) but I think is not a good approach because the phone eventually gets disconnected (stop in 2 or more signs in the time it is checking the condition again) and it is also needed more time to connect
NormMonkey said:
If a task has multiple conditions, does the task end when ANY condition ends or when they ALL end?
Click to expand...
Click to collapse
I think it ends only when all conditions meet (Anton - the developer - can confirm).
NormMonkey said:
Another example: if Nero made his condition "turn bluetooth on when driving and AC charger connected", and he happens to be talking on the phone at a long stop light, will his call be disconnected if he's not driving but the charger is still connected?
(...)
In the second example, the desired end-task is that the end of ALL conditions end the task. If Nero is on the phone at a stop light, he should not be disconnected.
Click to expand...
Click to collapse
That could work but I rarely connect the phone to the charger while driving...
Instead I would preferred to have conditions based on bluetooth connected devices, i.e., car BT system. Then when I turn car off, car's BT system also off -> phone disconnect => phone's bluetooth off
NormMonkey said:
Final thought: if you're on a call and bluetooth is disconnected, the call is still connected and goes to handset, right? So if you're on the phone with a client and you pull into the driveway, unplug your phone and walk away from the car, you continue talking to your client on your handset?
Click to expand...
Click to collapse
yes, the call continues at the handset but I have to pick it up and place it in my hear... and talk on the phone while driving is not a good idea and could cost me a lot of money if caught by the police!
Thank for your comments.
Task ends when a single condition is no longer true (i.e. one false and the rest are true is enough to trigger an end).
for example, if you have 2 conditions (time and headset plugged) task ends when you either unplug or time runs out, one is enough to end it.
Activity recognition is a special case, it starts like all other tasks (when google play services reaches confidence level of 66% for the first time), but it ends after a delay. We start counting from the first time the condition no longer holds with confidence of 66% (default is 30 seconds, you can change that in the settings). If during this time google play services detect another activity - the timer resets, so theoretically, this condition ends if your phone is safely on your desk.
Now I understand people still have issues with the activity recognition, and it's likely due to different phone sensors, and maybe even different versions of google play services. Not much I can do about it, it's pretty much a black box.
Now, if you see for some reason, the delay is not holding (i.e. you set it to 600 seconds and condition ends while your car sits idle for less then 5 minutes) please let me know.
If this doesn't work for you, try the conventional conditions (dock, headset, charger, inverse location combination).
about the lock screen, this will require root, i'll play around with this soon.
i'm planning to release a new beta version shortly, i've finally managed to make the wifi condition work like intended, and there's a new "when-app-launched" condition thingy (uses the new shortcut permission).
thanks for the feedback, I do try to keep up with all the suggestions, I have quite the backlog already.
Anton.
Data Bug
Hi,
Just wanted to report a minor bug I have been experiencing since the update prior to the most recent. I had set Condi to turn off WiFi at 8:09 am and turn data on at 8:10 am. Before that update, things have been working fine. Since that update; however, WiFi turns off but data does not turn on.
I have a Motorola XT-1030 DROID Mini if that helps.
rabidhunter said:
Hi,
Just wanted to report a minor bug I have been experiencing since the update prior to the most recent. I had set Condi to turn off WiFi at 8:09 am and turn data on at 8:10 am. Before that update, things have been working fine. Since that update; however, WiFi turns off but data does not turn on.
I have a Motorola XT-1030 DROID Mini if that helps.
Click to expand...
Click to collapse
try this one: https://kix.co.il/minitasker/importer.php?id=487
Seriously good app. Thanks
v0.2.15 beta
just released a new version to the beta channel (you need to subscribe to this group https://groups.google.com/d/forum/minitasker then go to this link https://play.google.com/apps/testing/il.co.kix.minitasker)
you can try out the new wifi connected condition and the app-launched condition.
wifi connected is long overdue, please tell me if it works as intended.
app-launched is a bit more interesting, it doesn't really monitor for running apps, it creates a "fake" shortcut for an app, that actually runs condi which in turns runs a task. tell me if you like the idea and if it works adequately. it's new so there may be issues i overlooked.
thanks.
sorry for the bump, but would really appreciate some feedback on the new beta.
is it good enough to release? any suggestions?
thanks.
I didn't spot anything broken. Is there a chance of reducing/choosing range for location from 75m?
raul6 said:
I didn't spot anything broken. Is there a chance of reducing/choosing range for location from 75m?
Click to expand...
Click to collapse
I obviously can, but it will probably not work.
The condition only triggers when google play services is 100% sure the device is inside. Since we only use low power sensors it probably will never trigger.
The limit was mainly to avoid comments like "it never works".
I can add a setting if you want, but, this just won't trigger unless you have a navigation app in the background that has gps running.
Thank you for explaining and offering but better use your time for implementing features that work.
Camera RemoteI can confirm this works with s5 there are a number of camera apps that work
Just type this in ebay Wireless RF Camera Remote Shutter*
Wireless Shutter Controller Camera Remote Control for
Samsung Galaxy S4, S3, Note 2, Note 1
Features:
RF wireless remote control make it possible for you to take pictures yourself from long distance.
Operation distance up to 10 meters.
Small size, easy to carry.
Compatible with Samsung Galaxy S3/S4, Samsung Galaxy Note 1/2.
Note:*
1. Please download and install the APP of "camera 360" in your device before using this product.
2. The receiver will automatically shutdown without any operation in 10 minutes.
Specifications:
Color: White
Material: ABS
Compatible with: For Samsung Galaxy S3/S4, Samsung Galaxy*Note 1/2
Operating frequency range: 2400 MHz ~ 2482MHz
Control distance: up to 10m
Operating voltage: 2.5V ~ 3.3V
Operating current: 16mA, max 20mA
Working time: Continuously work up to 3 hours
Power supply: 2 * CR2032
Remote size: Approx. 5.3 * 3.5cm / 2.1 * 1.4in(L * W)
Receiver size: Approx. 7 * 3.5cm / 2.7 * 1.4in(L * W)
Item weight: Approx. 22g / 0.8oz
Package size: Approx. 13 * 8.5 * 3.2cm / 5.1 * 3.3 * 1.3in
Package weight: Approx. 58g / 2.04oz
Package included:
PA1499
1 * Remote
1 * Receiver
1 * User's Manual
http://www.google.co.uk/imgres?imgu...=3&page=10&start=196&ndsp=25&ved=0CBYQrQM4yAE
Grizzly123 said:
Camera RemoteI can confirm this works with s4 zoom there are a number of camera apps that work
Just type this in ebay Wireless RF Camera Remote Shutter*
Wireless Shutter Controller Camera Remote Control for
Samsung Galaxy S4, S3, Note 2, Note 1
Features:
RF wireless remote control make it possible for you to take pictures yourself from long distance.
Operation distance up to 10 meters.
Small size, easy to carry.
Compatible with Samsung Galaxy S3/S4, Samsung Galaxy Note 1/2.
Note:*
1. Please download and install the APP of "camera 360" in your device before using this product.
2. The receiver will automatically shutdown without any operation in 10 minutes.
Specifications:
Color: White
Material: ABS
Compatible with: For Samsung Galaxy S3/S4, Samsung Galaxy*Note 1/2
Operating frequency range: 2400 MHz ~ 2482MHz
Control distance: up to 10m
Operating voltage: 2.5V ~ 3.3V
Operating current: 16mA, max 20mA
Working time: Continuously work up to 3 hours
Power supply: 2 * CR2032
Remote size: Approx. 5.3 * 3.5cm / 2.1 * 1.4in(L * W)
Receiver size: Approx. 7 * 3.5cm / 2.7 * 1.4in(L * W)
Item weight: Approx. 22g / 0.8oz
Package size: Approx. 13 * 8.5 * 3.2cm / 5.1 * 3.3 * 1.3in
Package weight: Approx. 58g / 2.04oz
Package included:
PA1499
1 * Remote
1 * Receiver
1 * User's Manual
Click to expand...
Click to collapse
very cool!
you do know there is a bluetooth product? its called shuttr. i use ut and works amazingly
doesnt voice shutter do the same thing
on a S5? idk i haven't tried it yet im assuming you would say cheese or some kind of phrase, the thing is however is that noise from background would disrupt it im assuming.
Playing With Notification LED
Original source (for MotoG) <<< make sure you read the blog article before commenting ....
dedicated Blog article for MotoE
It's always cool to know at a glance that your device is charging without the need of lighting the screen, here is how:
Requirements :
Moto E (tested on XT1022)
Rooted
SU rights granted
adb if you want to monitor all this from a computer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, BURNT LEDs,
* thermonuclear war, or you getting fired because the alarm app failed.
* 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.
*/
in /sys/class/leds/charging/trigger we have these triggers available :
Code:
[none] bkl-trigger usb-online mmc0 mmc1 battery-charging-or-full battery-charging battery-full battery-charging-blink-full-solid bms-online
easy to change them using :
Code:
echo battery-charging >/sys/class/leds/charging/trigger
needs to set any value !=0 for brightness (LED is either ON or OFF on MotoE):
Code:
echo 1 >/sys/class/leds/charging/trigger
Moto E (is quite different than Moto G MotoG has two LEDs too, they are simply impossible to see):
If you pay attention, you can se that Moto E has Two little white LEDs soldered under the LED hole, the first one (left) is ruled by /sys/class/leds/charging and the second one (less bright, ont the right) is ruled by the /sys/class/leds/white.
/sys/class/leds/white/trigger, and /sys/class/leds/white/brightness configure the right LED and these settings are overridden has soon as a notification comes.
/sys/class/leds/charging/trigger and /sys/class/charging/brightness configure the left LED (the brighter one) and these settings are not overridden by notifications AND both can work toghether:
You can see the left one kept ON while charging (using battery-charging trigger) and the right one Blinking with an incoming notification.
It is time for the community to help, and we will find out a way to correctly dim the LEDs if possible.
For now, the best way is to set left LED (/sys/class/leds/charging/) for charging using dedicated trigger and keeping the right one to none and get both working together this way.
______________________________
Set at boot:
WARNING : if you fail this, you may screw up your device ... (keep a backup somewhere)
Create a blank file and name it like 99charging_LED-blink
paste the following in that file :
Code:
#!/system/bin/sh
# enabling charging LED blinking while charging
echo "battery-charging-blink-full-solid" >/sys/class/leds/charging/trigger
echo "1" >/sys/class/leds/charging/brightness
mount /etc/init.d as RW
Paste 99charging_LED-blink there
set permissions as -RWXR-XR-X
Open terminal emulator, and type :
Code:
su
sh /etc/init.d/99charging_LED-blink
Plug it to charger, it should start blinking ... if not, make sure everything is correctly set
Reboot
Enjoy!
______________________________
For whose who asked, here is the proof of the 2 LEDs and their White-color :
http://forum.xda-developers.com/showpost.php?p=57039807&postcount=7
Feel free to test further and report your discoveries!
The above has been tested on stock rooted ROM, and reported to work on CM11-m12, both on XT1022.
Here is the LED related Thread for MotoG
XDA:DevDB Information
[LED][DEV] Moto E LED Custom Controls, Tool/Utility for the Moto E
Contributors
matmutant
Version Information
Status: Testing
Created 2014-11-24
Last Updated 2014-12-15
reserved
reserved
@matmutant Epic discovery sir.. :good:
tried this in trickster mod led control... but since the left one is so bright it overrides the indication of the right..i.e the change in the blinking intensity is not visible until observed closely...
AshuGite said:
tried this in trickster mod led control... but since the left one is so bright it overrides the indication of the right..i.e the change in the blinking intensity is not visible until observed closely...
Click to expand...
Click to collapse
In fact, you should use the following :
Code:
echo battery-charging-blink-full-solid >/sys/class/leds/charging/trigger
This way the brighter will blink during charge, so the notification LED will be visible too (that's not the same blink pattern so it gives an irregular blink feeling)
Of course, i have no idea why there are 2 LEDs, and if lighting the brighter one will burn it or not : i'm going to add a disclaimer to OP since this mod has potential consequences on Hardware.
Thank you for your report, may i ask you your device and ROM?
matmutant said:
In fact, you should use the following :
Code:
echo battery-charging-blink-full-solid >/sys/class/leds/charging/trigger
This way the brighter will blink during charge, so the notification LED will be visible too (that's not the same blink pattern so it gives an irregular blink feeling)
Of course, i have no idea why there are 2 LEDs, and if lighting the brighter one will burn it or not : i'm going to add a disclaimer to OP since this mod has potential consequences on Hardware.
Thank you for your report, may i ask you your device and ROM?
Click to expand...
Click to collapse
same results on cm11 m12 and stock 4.4.4 in XT1022
For whose who asked :
I was able to show that our MotoE has 2 LEDs (until now it was only a high suspicion) and that they are really White and not mis-configured RGB.
Here is the in-depth proof.
If only we could change their color.
Sent from my GT-I9070
Is this working?
Because i have planned to make app for this.
svprm said:
Is this working?
Because i have planned to make app for this.
Click to expand...
Click to collapse
Sure it works
Two steps are needed to set up each LEDs :
The Brighter One:
Code:
echo battery-charging-blink-full-solid >/sys/class/leds/charging/trigger
Code:
echo 1 >/sys/class/leds/charging/brightness
The 'notification' One (better keep it to trigger=none, so it will keep its role of notification LED), but if you wanna play with it:
Code:
echo battery-charging-blink-full-solid >/sys/class/leds/white/trigger
Code:
echo 1 >/sys/class/leds/white/brightness
Contrary to MotoG, i couldn't dim this LED by setting 0~255 for brightness
There might be a way to trigger flash LED when getting notification, but this is not for Moto E either
if you make an app for this we could share this thread as co-contributors and in-depth study these new possibilities
If we can change colour, it will be too good
Sent from my XT1022 using xda premium
nisu4717 said:
If we can change colour, it will be too good
Sent from my XT1022 using xda premium
Click to expand...
Click to collapse
didn't you read this? : http://forum.xda-developers.com/showpost.php?p=57039807&postcount=7
btw here is the latest discovery :
Using "bkl-trigger" as */charging/trigger allows you to get the LED on as long as the screen ("bkl" stands for backlight)
Code:
echo bkl-trigger >/sys/class/leds/charging/trigger
Just because having this feature working at boot is soooo cool xD
Set at boot:
WARNING : if you fail this, you may screw up your device ... (keep a backup somewhere)
Create a blank file and name it like 99charging_LED-blink
paste the following in that file :
Code:
#!/system/bin/sh
# enabling charging LED blinking while charging
echo battery-charging-blink-full-solid >/sys/class/leds/charging/trigger
echo 1 >/sys/class/leds/charging/brightness
mount /etc/init.d as RW
Paste 99charging_LED-blink there
set permissions as -RWXR-XR-X
Open terminal emulator, and type :
Code:
su
sh /etc/init.d/99charging_LED-blink
Plug it to charger, it should start blinking ... if not, make sure everything is correctly set
Reboot
Enjoy!
matmutant said:
Set at boot:
WARNING : if you fail this, you may screw up your device ... (keep a backup somewhere)
Create a blank file and name it like 99charging_LED-blink
paste the following in that file :
Code:
#!/system/bin/sh
# enabling charging LED blinking while charging
echo battery-charging-blink-full-solid >/sys/class/leds/charging/trigger
echo 1 >/sys/class/leds/charging/brightness
mount /etc/init.d as RW
Paste 99charging_LED-blink there
set permissions as -RWXR-XR-X
Open terminal emulator, and type :
Code:
su
sh /etc/init.d/99charging_LED-blink
Plug it to charger, it should start blinking ... if not, make sure everything is correctly set
Reboot
Enjoy!
Click to expand...
Click to collapse
i already created a script for myself but unable to figure out how to control blinking pulse...
AshuGite said:
i already created a script for myself but unable to figure out how to control blinking pulse...
Click to expand...
Click to collapse
The blinking pulse is Hardcoded, that means end-user cannot modify it, though some work in the light Hal should both give hability to dim the LED and control its pulse frequency (no idea if it will really be userspace configurable or not then)
@dhacker29 had done something related for MotoX a while ago :
http://review.cyanogenmod.org/#/c/57550/
However, that's not part of my skill range :cyclops:
matmutant said:
The blinking pulse is Hardcoded, that means end-user cannot modify it, though some work in the light Hal should both give hability to dim the LED and control its pulse frequency (no idea if it will really be userspace configurable or not then)
@dhacker29 had done something related for MotoX a while ago :
http://review.cyanogenmod.org/#/c/57550/
However, that's not part of my skill range :cyclops:
Click to expand...
Click to collapse
in cm11 we have the option to control the pulse frequency..
AshuGite said:
in cm11 we have the option to control the pulse frequency..
Click to expand...
Click to collapse
Exactly, buy only for the notification LED (the one we can dim, under the rule of /sys/class/leds/white), not for the charging LED (/sys/class/leds/charging)
Any video tutorial?
bsaikartheek said:
Any video tutorial?
Click to expand...
Click to collapse
As i told you on G+, feel free to make one and i'll share it here
Can someone tell me how to do it please m not able to do it
Sent from my XT1022 using XDA Free mobile app
Hi All,
Do you know when Sony will issue a SW update to solve the high battery consumption of (phone idle, google play services, and android OS) processes.
I am on Nougat, 39.2.A.0.442
Thanks,
well they are kind of slow in getting updates on time...only issue i wish they fix is battery drainage...phone idle consumed 1050 mah of battery in 2 days, why Sony?is system doing something from behind that we dont know or what LOL.im also on latest Nougat .442
I debloated my phone on fw 442, build.prop and init.qcom.post_boot.sh tweaks and get 8-10 hrs SOT [without any cpu profile or underclock or vm tweaks!]
Without all of that, can get 5-6 hrs SOT too. (1-2 hrs play Clash Royal on LTE or 3G)
My Galaxy S6 get 4-5 hr on marshmallow and 5-6 on Lollipop.
I think for a LCD panel, not any problems at Sony battery consuming!
Can you share details about power usage for google play services? This is google fault not sony software!
---------- Post added at 07:03 PM ---------- Previous post was at 06:42 PM ----------
If you on stock fw without root check:
1- In Settings>Location click on 3dots menu an select "scan" then check wifi and blutooth scan is off?
2- don't use vibration at all (notifications and calls. touching display, keyboards, dialling, etc)
3- turn off auto-sync
4- turn off trust agent if do not use smart locks
5- turn off auto update for play store and firmware
6- check which app use data in background (and manage restriction for each of them)
7- at Settings>google>nearby, click on gear icon and turn of "nearby links" and "device ready to setup"
8- turn off "double touch to wake up" (optional)
i have the same issue on my Dual Sim Sony Xperia XZ. 8hrs idle and lost 15%. its same every day. Shame Sony!!! Its your flagship device.....
mzeshanhakeem said:
i have the same issue on my Dual Sim Sony Xperia XZ. 8hrs idle and lost 15%. its same every day. Shame Sony!!! Its your flagship device.....
Click to expand...
Click to collapse
It's easy to blame Sony when a simple change in your settings can make a huge difference in power consumption while the phone is idle.
Maybe you should check this rom if sony's stock software doesn't satisfy you https://forum.xda-developers.com/xperia-xz/development/duality-rom-legendary-battery-beta-t3574300
I'm on my way to 11h of SoT with moderate use, play services together to idle struggle to get to 20% after two days.
GenomeX said:
I debloated my phone on fw 442, build.prop and init.qcom.post_boot.sh tweaks and get 8-10 hrs SOT [without any cpu profile or underclock or vm tweaks!]
Without all of that, can get 5-6 hrs SOT too. (1-2 hrs play Clash Royal on LTE or 3G)
My Galaxy S6 get 4-5 hr on marshmallow and 5-6 on Lollipop.
I think for a LCD panel, not any problems at Sony battery consuming!
Can you share details about power usage for google play services? This is google fault not sony software!
---------- Post added at 07:03 PM ---------- Previous post was at 06:42 PM ----------
If you on stock fw without root check:
1- In Settings>Location click on 3dots menu an select "scan" then check wifi and blutooth scan is off?
2- don't use vibration at all (notifications and calls. touching display, keyboards, dialling, etc)
3- turn off auto-sync
4- turn off trust agent if do not use smart locks
5- turn off auto update for play store and firmware
6- check which app use data in background (and manage restriction for each of them)
7- at Settings>google>nearby, click on gear icon and turn of "nearby links" and "device ready to setup"
8- turn off "double touch to wake up" (optional)
Click to expand...
Click to collapse
Thanks alot... I did most of that, will monitor and let you know
Dears... and did you ever notice some cut in the notification sounds? especially whatsapp? ... random behaviour
Thanks,
for rooted user follow this tutrial for fix battery drain at android 7.0 fw...
open /system/etc/init.qcom.post_boot.sh and find this (method for msm8996)
Code:
case "$target" in
"msm8996")
# disable thermal bcl hotplug to switch governor
add red line:
Code:
echo 0 > /sys/module/msm_thermal/core_control/enabled
[COLOR="Red"]echo N > /sys/module/msm_thermal/parameters/enabled[/COLOR]
and
Code:
# Enable Adaptive LMK
echo 1 > /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk
echo 81250 > /sys/module/lowmemorykiller/parameters/vmpressure_file_min
[COLOR="red"] # Configure virtual memory for battery drain
echo 500 > /proc/sys/vm/dirty_expire_centisecs
echo 3000 > /proc/sys/vm/dirty_writeback_centisecs
echo 100 > /proc/sys/vm/vfs_cache_pressure[/COLOR]
now find
Code:
echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
and change like this:
Code:
echo [COLOR="red"]100[/COLOR] > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
above # online cpu2
add this:
Code:
[COLOR="red"]echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down[/COLOR]
# online CPU2
above # Override with SOMC tuning parameters for governor
add this:
Code:
[COLOR="red"] echo 1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down
# Disable touch-boost
echo 0 > /sys/module/msm_performance/parameters/touchboost[/COLOR]
# Override with SOMC tuning parameters for governor
now re-enable hotplug
Code:
# re-enable thermal and BCL hotplug
echo 1 > /sys/module/msm_thermal/core_control/enabled
[COLOR="red"] echo Y > /sys/module/msm_thermal/parameters/enabled[/COLOR]
==============================================================
now let's go to edit build.prop
end of the file add this:
Code:
#
# CUSTOM_BUILD_PROPERTIES
#
ro.ril.power_collapse=1
ro.ril.disable.power.collapse=0
ro.ril.fast.dormancy.rule=0
pm.sleep_mode=1
power.saving.mode=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=90
persist.sys.scrollingcache=3
ro.media.enc.jpeg.quality=100
persist.sys.purgeable_assets=1
reboot and enjoy
GenomeX said:
for rooted user follow this tutrial for fix battery drain at android 7.0 fw...
open /system/etc/init.qcom.post_boot.sh and find this (method for msm8996)
Code:
case "$target" in
"msm8996")
# disable thermal bcl hotplug to switch governor
add red line:
Code:
echo 0 > /sys/module/msm_thermal/core_control/enabled
[COLOR="Red"]echo N > /sys/module/msm_thermal/parameters/enabled[/COLOR]
and
Code:
# Enable Adaptive LMK
echo 1 > /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk
echo 81250 > /sys/module/lowmemorykiller/parameters/vmpressure_file_min
[COLOR="red"] # Configure virtual memory for battery drain
echo 500 > /proc/sys/vm/dirty_expire_centisecs
echo 3000 > /proc/sys/vm/dirty_writeback_centisecs
echo 100 > /proc/sys/vm/vfs_cache_pressure[/COLOR]
now find
Code:
echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
and change like this:
Code:
echo [COLOR="red"]100[/COLOR] > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
above # online cpu2
add this:
Code:
[COLOR="red"]echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down[/COLOR]
# online CPU2
above # Override with SOMC tuning parameters for governor
add this:
Code:
[COLOR="red"] echo 1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down
# Disable touch-boost
echo 0 > /sys/module/msm_performance/parameters/touchboost[/COLOR]
# Override with SOMC tuning parameters for governor
now re-enable hotplug
Code:
# re-enable thermal and BCL hotplug
echo 1 > /sys/module/msm_thermal/core_control/enabled
[COLOR="red"] echo Y > /sys/module/msm_thermal/parameters/enabled[/COLOR]
==============================================================
now let's go to edit build.prop
end of the file add this:
Code:
#
# CUSTOM_BUILD_PROPERTIES
#
ro.ril.power_collapse=1
ro.ril.disable.power.collapse=0
ro.ril.fast.dormancy.rule=0
pm.sleep_mode=1
power.saving.mode=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=90
persist.sys.scrollingcache=3
ro.media.enc.jpeg.quality=100
persist.sys.purgeable_assets=1
reboot and enjoy
Click to expand...
Click to collapse
nice to see that...looks like im going for root soon Thanks
GenomeX said:
for rooted user follow this tutrial for fix battery drain at android 7.0 fw...
open /system/etc/init.qcom.post_boot.sh and find this (method for msm8996)
Code:
case "$target" in
"msm8996")
# disable thermal bcl hotplug to switch governor
add red line:
Code:
echo 0 > /sys/module/msm_thermal/core_control/enabled
[COLOR="Red"]echo N > /sys/module/msm_thermal/parameters/enabled[/COLOR]
and
Code:
# Enable Adaptive LMK
echo 1 > /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk
echo 81250 > /sys/module/lowmemorykiller/parameters/vmpressure_file_min
[COLOR="red"] # Configure virtual memory for battery drain
echo 500 > /proc/sys/vm/dirty_expire_centisecs
echo 3000 > /proc/sys/vm/dirty_writeback_centisecs
echo 100 > /proc/sys/vm/vfs_cache_pressure[/COLOR]
now find
Code:
echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
and change like this:
Code:
echo [COLOR="red"]100[/COLOR] > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
above # online cpu2
add this:
Code:
[COLOR="red"]echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down[/COLOR]
# online CPU2
above # Override with SOMC tuning parameters for governor
add this:
Code:
[COLOR="red"] echo 1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down
# Disable touch-boost
echo 0 > /sys/module/msm_performance/parameters/touchboost[/COLOR]
# Override with SOMC tuning parameters for governor
now re-enable hotplug
Code:
# re-enable thermal and BCL hotplug
echo 1 > /sys/module/msm_thermal/core_control/enabled
[COLOR="red"] echo Y > /sys/module/msm_thermal/parameters/enabled[/COLOR]
==============================================================
now let's go to edit build.prop
end of the file add this:
Code:
#
# CUSTOM_BUILD_PROPERTIES
#
ro.ril.power_collapse=1
ro.ril.disable.power.collapse=0
ro.ril.fast.dormancy.rule=0
pm.sleep_mode=1
power.saving.mode=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=90
persist.sys.scrollingcache=3
ro.media.enc.jpeg.quality=100
persist.sys.purgeable_assets=1
reboot and enjoy
Click to expand...
Click to collapse
I do this thing but the result is the same at before. I must wait some cycle of charge? I copy the files on pc and i do this things there and then i replace those files in their directory
djgigi94 said:
I do this thing but the result is the same at before. I must wait some cycle of charge? I copy the files on pc and i do this things there and then i replace those files in their directory
Click to expand...
Click to collapse
Maybe one of your third-party app call google play services.
Reboot to safe mode and see is the problem still alive.
When writing this comment, I am on 67% battery and Play Services only drain 3%, android system only 7%!
I get 2hr sot (%36 drain)
play Asphalt8 for 45min (set on hi-graphic)
surface web with chrome for 30min
telegram for 10min
Instagram for 10min
7min call with SIM1 (gsm) and my SIM2 is on LTE when use social networking and web browsing.
I think this is where good battery life for a flagship smartphone with same useage.
I never problem with Standby; (becuse i use my phone always LOL)
Try (okey try if i can LOL) to change my useage and live the phone alone for few hours (really hard job for a internet lover you know) and share with you: is phone idle really a problem or not?
You can see i have not any battery drain problem with 7.0 firmware
http://uupload.ir/files/m6hi__20170406_065247.jpg
I use my phone from 100-95 (4G network) before sleep, after wakeup drain only 1%, 8hrs idle. (the 4G network was on)
** consider i debloated my phone too. Maybe some Sony or third-party apps may the real problem, not fault of play services or android 7.0 or kernel codes! (Pixel, HTC10, Moto Z, are normal with 7.x. Deep customized android firmware like Xperia X, XZ and Galaxy S6,S7 have issue)
*** use cpu monitoring apps to find cpu deep sleeping work correct and whiche services wakeup processor in background.
the strange thing here... after some days of phone usage, the phone seems to learn my usage. now battery takes hell of time before it drains! which is good
I don't see the point of having to turn off some settings in order to get by 5-6 hours of SOT...you shouldn't have to do that with phones in 2017.
I wish I could root my Japanese XZ, but I'd lost my mobile payments and that is too valuable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* 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.
*/
Supported devices
All variations of A52 4G and A72 (A525F, A525F/DS, A525M, A525M/DS, A725F, A725F/DS, A725M and A725F/DS) are supported, but only A525F (6/128 variant) is well tested as I have this device.
Working
Audio
Wifi
Hotspot
Calls
WifiDisplay
Bluetooth
OMX
Camera
NFC
Fingerprint
Screen-Off-FOD
Mobile data
GPS
DT2W
...
Bugs
VoLTE/VoWIFI (Samsung's implementation doesn't work on AOSP)
Audio output in VoIP calls is swapped (WhatsApp, Discord, etc)
On some bluetooth Watches/Earphones In-Call sound is played from the phone's speaker/earpiece
Installation instructions
Recommended
Follow the guide on the LineageOS website: A52 4G | A72
Alternative way (TWRP/OrangeFox)
Make sure your device's bootloader is unlocked.
If not done before, flash blank VBMeta with Odin in AP slot.
Make sure to have the latest available version of TWRP/OrangeFox installed.
If wanted, backup all your necessary partitions (super, boot, data, EFS) before flashing this in case something goes wrong.
Download the lineage build for your device from the link below and optionally download your preferred GApps package too.
Flash the LineageOS zip using the "Install" button.
Optionally, flash Gapps right after.
Format data in TWRP/OrangeFox as the very last thing, otherwise you may end up in a bootloop if coming from stock ROM.
Wipe metadata and cache partitions. This only has to be done once when you install LineageOS.
Reboot
Downloads
You can find them here on a mirror hosted by me.
Gapps (choose arm64 and 12.1/12L): MindTheGapps | OpenGapps canary | FlameGapps Canary | NikGapps Canary
Old builds: LineageOS 18.1
Support
Telegram
Donations
They aren't necessary, but if you like my work feel free to send me or LineageOS a donation.
Credits
To...
Me, for spending my time on this project
Whoever made the VBMeta disabler
@Grarak for his fingerprint fix for A70 and DT2W fix
@TheLeo2307 for testing on his A72
@miamighost for testing on his A52
Maybe more, feel free to tell me if I forgot someone
Source Code: https://github.com/LineageOS/android_kernel_samsung_sm7125
FAQ
Can I root my phone with this ROM?
Yes, just install the latest version of Magisk.
How can I pass safetynet?
Follow this guide.
Automatic camera flash doesnt work!
That's an issue with Lineage's camera app. Use GCam or any other camera app instead.
Unofficial changelogs
06-08-2022
Code:
-Updated blobs to A525FXXU4BVG1 respectively A725FXXU4BVE3
-Implemented proper screen-off-fod support (Settings->Display->Lockscreen->Long press fingerprint sensor....)
-Improved FOD dimming values
-Imported HotwordEnrollment blobs to fix "OK Google"
-Switched to OSS camera provider
-Slightly decreased vibrator intensity
-Enable correct reading mode in LiveDisplay
-Add Dolby audio effect (Actually works this time)
-Excluded AudioFX to improve Dolby effect
-Built FlipFlap to fix flip covers (Thanks for reporting @Peter_Petersen
-Corrected brightness for SunlightEnhancement mode in LiveDisplay
-Built AdvancedDisplay for advanced display modes
-Set ZRAM size to 5GB to improve performance
-Switched to CAF USB audio configuration to fix audio in phone calls with USB headphones/headsets
-Enabled pickup gesture support
04-07-2022
Code:
-June security patch
-Switched to using Samsung's HBM implementation instead of lighting up the whole screen when touching the fingerprint sensor
-Dim the screen if touching the fingerprint sensor
-Wake the screen if touching the fingerprint sensor during screen off or AOD instead of killing doze
-Fixed fingerprint sensor on A72 by dimming the screen (You may need to hold your finger a bit tight on the sensor)
-Correctly reset brightness on fingerprint errors
-Fixed the screen not turning on again if removing the phone from your ear during a phone call
-Added custom audio impl to fix audio in calls with Sim 2
-Disabled Dolby again (doesn't seem to work correctly for us)
-Re-enabled doze/deepsleep support
-Show correct fast-charging values
30-05-2022
Code:
-Updated to Lineage 19.1
-May security patch
-Enabled freeform windows
-Build SamsungDAP for dolby audio
-Fixed color calibration in livedisplay settings (Please note that not all display modes support color calibration)
-Show download mode instead of bootloader in advanced restart menu
-Re-enabled FM-Radio
-Enabled night display/bluelight filter
-Fixed audio with USB headphones/speakers/etc
-Correctly detect phone variant and set props accordingly
-Enabled encryption (FBE)
-Removed unused partitions from fstab
-Fixed USB mode not being select-able
-Enabled MAC randomization for WiFi
-SeLinux enforcing
-Use correct default network mode (4G)
-Enabled adoptable storage to work with FBE
-Set props from stock ROM to make Netflix select DRM L1
-Fixed proximity sensor not working at all
-Updated kernel to A525FXXS4BVA2
-Enabled burn-in protection
02-03-2022
Code:
-Updated to Lineage 19.0
-February security patch
-Updated all blobs and configs to A525FXXS4BVA2 (Android 12)
-Updated kernel to A525FXXU4BUL8 (Android 12)
-Unified more blobs
-Fixed screen rotation on A72
-Switched to AOSP WifiDisplay implementation
-Corrected status bar padding
-Built more blobs from source
-Switched to Clang r383902
-Disabled APEX compression
-Switched to UDFPS
-Fixed FOD on AOD
-Make FOD stay always on for working FOD on AOD
-Increased the amount of time the screen lights up when touching the fingerprint sensor
-Switched to stock health blobs
-Overall cleanup
-Enabled F2FS support for system partition
-Switched to newer AIDL libperfmgr power HAL
-Updated vibrator to AIDL to switch to manifest level 5 and match stock
-Fixed audio in bluetooth phone calls on A52 (for somehow still broken on A72)
-Imported APTX BT encoder from Pixel 5
-Enabled unofficial monet implementation
13-01-2022
Code:
-Latest lineage sources with december security patch (january one wasn't released yet)
-Updated blobs to A525FXXU4AUJ2
-Added initial A72 support
-Switched to OSS fingerprint HAL by [USER=4443334]@Grarak[/USER]
-Cleaned up unused config files
-Built lineage recovery for both devices
-Added missing overlay for the system to know that we have a notch
-Built more blobs from source
-Fixed A2DP offload and switched to AOSP bluetooth audio implementation
-Correctly boost brightness when the fingerprint sensor is touched
-Fixed fingerprint sensor not working when screen brightness is low
-Corrected size and position of the fingerprint sensor (And yes, the sensor is REALLY that big)
-Disabled screen off FOD for now since it doesn't work anyway
-Limit fingerprints to max 4 per user
-Temporary disabled FMRadio since it somehow broke with latest sources
-Built QCOM audio effects from source
20-11-2021
Code:
-Initial release
Nice to see someone's already got custom roms working on this phone!
good job, i hope we see more roms coming for this device
nice one, but the fingerprint often doesn't work
8/128, twrp-3.5.2_10-0-a52q, have done all the installation instructions
iam23 said:
nice one, but the fingerprint often doesn't work
8/128, twrp-3.5.2_10-0-a52q, have done all the installation instructions
Click to expand...
Click to collapse
What do you mean it doesnt work "often"?
If its for unlocking the phone when the screen is off then that is already a know bug and is currently not fixable.
Apart from that the fingerprint sensor always worked fine for me.
Awesome work!
Amazing work! Thank you for creating ROM for A52
I really appreciate the value you're providing!
Simon1511 said:
What do you mean it doesnt work "often"?
If its for unlocking the phone when the screen is off then that is already a know bug and is currently not fixable.
Apart from that the fingerprint sensor always worked fine for me.
Click to expand...
Click to collapse
I'm sorry, I use google translate,
I know about the off screen bug.
I mean, sometimes it says "finger moved too fast", and after that happens the fingerprint can never work.
i know it's still early, thank you for the first a52 custom rom
nfc does not work properly.
2.Wi-Fi calls do not appear, therefore they do not work.
3. and unfortunately when installing this version you cannot go back to the original version, enter the boot loop
does volte work?
and does battery life somehow improve over stock oneui?
axljohn said:
does volte work?
and does battery life somehow improve over stock oneui?
Click to expand...
Click to collapse
Currently no (i dont know if its even possible to get to work on Samsung devices).
Probably yes.
diegobenti said:
nfc does not work properly.
Click to expand...
Click to collapse
Whats the problem with NFC?
diegobenti said:
2.Wi-Fi calls do not appear, therefore they do not work.
3. and unfortunately when installing this version you cannot go back to the original version, enter the boot loop
Click to expand...
Click to collapse
2. Not yet supported (if even possible to get to work).
3. Flash full stock and you should be fine.
Simon1511 said:
Whats the problem with NFC?
2. Not yet supported (if even possible to get to work).
3. Flash full stock and you should be fine.
Click to expand...
Click to collapse
NFC, for example, does not work for me on "SUBE" cards from Argentina (bus cards), I have not tried on credit cards, but the bus card reads it but gives a reading error
diegobenti said:
NFC, for example, does not work for me on "SUBE" cards from Argentina (bus cards), I have not tried on credit cards, but the bus card reads it but gives a reading error
Click to expand...
Click to collapse
Thanks for reporting.
Great job mate! Didn't expect someone already trying to bring LinageOS to this phone. Thank you very much!
Great news that someone is working on LOS for a52! Keep it up and thank you so much.