Database Info

[APP] Flip4Silence - Mute incoming calls via a flip/shake | [HELP NEEDED]

Flip4Silence enabled you to flip or shake an incoming call silent! It can also reduce the ringtone volume if you pick up your phone!
Unlike all the other ones I know Flip4Silence do not stress your battery. It's only active when you need it. This got some drawbacks... but hey, it works quiet well!
About "mute via flip/shake":
A friend of mine changed his good old WM6.5 phone into a Android powered device and was annoyed that you can't flip a call silent with a AOSP - now here it is, without the battery stress
About "reduce on pickup":
Someone with an HD2 told me that his phone got this "reduces volume on pick up" feature and I searched the market to find an app for android... Didn't find anything, wrote it myself! Hope you like it too!
Supported android versions: 1.6 and above
Link to Market: Link
Version 1.6.1
- The collection phase is over, thanks everyone for sharing!
Version 1.6.0
- Added "Improve F4S". It would be great if you could help me!
- UI rework
- Maybe fixed "volume not restored" problem
- The fakevibrator used by the "pickup" feature is now stopped when F4S snaps in
Version 1.5.1
- Gingerbread is now supported!
- Fixed 2 rare force closes
Version 1.5.0
- Fixed that "Vibrate only in silent mode" is not a valid mode to enable the pick up volume reducer
- Fixed a bug where the ringer volume is set to early to its normal value
- Fixed the pick up volume reducer behavior
- Fixed shortcut to the audio settings on 1.6
- Added sensitivity settings for the pick up volume reducer
- Added vibration as an option if the pick up volume reducer can't operate
- Minor UI rework
Features:
* flip or shake your phone to mute it (3 modes)
* Pick your phone up from the table and it reduces its volume!
* notifications after hang up (vibration/sound)
* extra battery friendly
Suppoerted modes:
* Mute a call when your phone is laying on its display
* Mute a call when you flip your phone from one side to the oder
* Or mute via a shake
Any feedback/wish/bugreport is welcome!

Will give a try. I've been using Shake2Mute, which is quite similar.
Sent from my HTC Desire using Tapatalk

Version 1.4 is on the market!

Thanks. I wanted this after i saw it on htc.
Sent from my GT-I9000 using XDA App

This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?

hayer said:
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
Click to expand...
Click to collapse
Hm, it seems that something is wrong with the sensorcheck. You are sadly not the only with this issue but the only one who got in contact with me (thanks for this, looking at the comments and see "does not work" is not very nice :/).
I got some questions to investigate this problem:
1) Am I right that the magic is currently on froyo? You got which version?
2) Am I right that a dialog is shown which says "Sorry, no accelerometer and/or magnetic field sensor found"?
3) As you sad other apps are working, which for example (something that uses the phone orientation)?
Currently I have no idea why the code is working on my device (N1) and the milestones I got for testing here...
For the technical people who might have an idea: I'm currently using SensorManager.getDefaultSensor() with the SENSOR_ACCELEROMETER and SENSOR_MAGNETIC_FIELD constants, any idea why this might not work?

Tested on i7500 with 2.2.1 GAOSP.
It lowers the volume when I take it in my hand.
It doesn't mute when flipped.
It does mute when shaked.
Excelent work ! Thanks !

I attached Version 1.4.1 which hopefully fix the issue many people reported. It would be nice if anyone with the message "Sorry your device is unsupported" can try this one and report back how it performs.

hayer said:
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
Click to expand...
Click to collapse
I finally fixed the issue you reported in version 1.4.3. Thanks for your report!

Luminger said:
I finally fixed the issue you reported in version 1.4.3. Thanks for your report!
Click to expand...
Click to collapse
Thankyou Luminger I appreciate the response and the quick fix and this is now working astoundingly on my magic saved my ass in physics class the other day

Thanks,Luminger, Works great on Moto Qunech XT3...thanks alot...

I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !

so it's like one of the feature from HTC Sense, right?
gotta try it when I use clean build with no sense..

Yea, sounds like a bug as F4S should move the volume back to the previous level. I will take a look this evening, thank you for the report!

I really hope that you can fix it.
Thank you !

badeaioan said:
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
Click to expand...
Click to collapse
badeaioan said:
I really hope that you can fix it.
Thank you !
Click to expand...
Click to collapse
Just wanted to inform you and everyone interested that I'm currently reworking F4S to work around those bugs. Currently I have no clue where this behaviour came from but I think it will be fixed with the rework.
alphadeeto said:
so it's like one of the feature from HTC Sense, right?
gotta try it when I use clean build with no sense..
Click to expand...
Click to collapse
It is suposed to be like the HTC Sense yea, don't know if its working in exact the same way (as I never have seen the Sense config dialog ).

badeaioan said:
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
Click to expand...
Click to collapse
1.4.4 is out now which should fix your issue. I managed to reproduce the error by accident and reworked the code at this place - seems to be fixed with 1.4.4.

Luminger said:
1.4.4 is out now which should fix your issue. I managed to reproduce the error by accident and reworked the code at this place - seems to be fixed with 1.4.4.
Click to expand...
Click to collapse
1.4.4 appears to keep the "Reduce volume" option always grayed out. That's really the only feature I want from the app, and before this version I had enable flip4silence unchecked and only reduce volume checked.

c00ller said:
1.4.4 appears to keep the "Reduce volume" option always grayed out. That's really the only feature I want from the app, and before this version I had enable flip4silence unchecked and only reduce volume checked.
Click to expand...
Click to collapse
Hm, doesn't sound good...
Are you sure the ringer vibration is off? Off should be the only option F4S accepts.
Did you managed it to get it working when you change the F4S settings ore the vibration settings?
Which device on which version, ROM?
Sorry that I broke it for you, but it's working perfectly on my Nexus One here :-/

Oh, never mind! Somehow my ringer vibration became enabled again before I updated the app. Great app

CM13 Z5P E6853 Beta -- Updated NegaSpork

This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m

Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:

Updates and Notes
Reserved

Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.

Thanks for the input. I get error: 7 to install the .zip file
any solution?

Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs

KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.

@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)

Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.

moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash

Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?

moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.

Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app

Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m

moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.

Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently

zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.

Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here

Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:

@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel:

[ROM][XC][MM][6.0.1_r74]OmniROM

XC/KUGO/F5321 OmniROM BUILDS
MARSHMALLOW 6.0.1_r74
DOWNLOAD OFFICIAL
DOWNLOAD HOMEMADE
OFFICIAL and HOMEMADE builds are not intercompatible! You will need to do a full wipe if you are switching from one to the other.
CURRENT ISSUES ON OFFICIAL:
1. Incall speaker volume is too low (earpiece volume is fine)
2. Camera sometimes doesn't start (rare)
3. Blutooth and FM radio can't be used concurrently. If you use either you need to reboot to use the other.
4. Double tap to wake doesn't work
5. Adding fingerprints only works on initial device setup. Adding fingerprints from Settings is buggy.
CURRENT ISSUES ON HOMEMADE:
1. Incall speaker volume is too low (earpiece volume is fine)
4. Double tap to wake doesn't work
5. Adding fingerprints only works on initial device setup. Adding fingerprints from Settings is buggy.
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-6.0
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
CHANGELOG:
https://changelog.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
[/CENTER]
XDA:DevDB Information
[ROM][XC][MM][6.0.1_r74]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-12-19
Last Updated 2017-02-11

reserved

Been trying this out since yesterday. Nice ROM, very smooth. Its great to see an AOSP rom with 90% of functionality. Battery usage is on par with stock.
One bug that I noticed is that if bluetooth is on (regardless of whether it is connected or not), it'll keep a 'bluesleep' wakelock which preents the device from going into Deep sleep.
Edit: Another note on the deep sleep problem. Even after turning bluetooth off, the phone doesn't deep sleep. Other wakelocks (event3, event4, event6) show as keeping the phone awake. Reboot fixes it and the phone can finally deep sleep.

Are you guys still enjoying this ROM?

Thanks to oshmoun to this amazing ROM i use it every days and i prefer Android 6 for the xposed module

Fantastic rom! Finally got rid of all the crap Sony bloatware.
However two questions. The camera on the back can now only shoot 8MP photo's. I've disbled the 8MP option in the setting, but it still won't let me shoot 23MP photo's. Is there a way to fix this?
Also the fingerprint scanner doesn't seem to function. When trying to add a fingerprint, it immediately fails (registration cannot be completed). Any fix?

LeZiGue00 said:
Thanks to oshmoun to this amazing ROM i use it every days and i prefer Android 6 for the xposed module
Click to expand...
Click to collapse
speedtoucher said:
Fantastic rom! Finally got rid of all the crap Sony bloatware.
However two questions. The camera on the back can now only shoot 8MP photo's. I've disbled the 8MP option in the setting, but it still won't let me shoot 23MP photo's. Is there a way to fix this?
Also the fingerprint scanner doesn't seem to function. When trying to add a fingerprint, it immediately fails (registration cannot be completed). Any fix?
Click to expand...
Click to collapse
about the camera,you need to wipe camera data after toggling 23MP mode. You'll then see the 23MP resolution in settings.
about the fingerprints, thanks for the hint. This is a bug. Sometimes it works though, so you might get lucky if you try a lot.
also, it's cool to know people are using this rom lol
if you're interested, I can post custom HOMEMADE builds that contain some bugfixes.
Notice though that HOMEMADE builds are signed differently, and won't be compatible with OFFICIAL builds. That means you'll need a full wipe before flashing and booting.

oshmoun said:
about the camera,you need to wipe camera data after toggling 23MP mode. You'll then see the 23MP resolution in settings.
about the fingerprints, thanks for the hint. This is a bug. Sometimes it works though, so you might get lucky if you try a lot.
also, it's cool to know people are using this rom lol
if you're interested, I can post custom HOMEMADE builds that contain some bugfixes.
Notice though that HOMEMADE builds are signed differently, and won't be compatible with OFFICIAL builds. That means you'll need a full wipe before flashing and booting.
Click to expand...
Click to collapse
Definitely interested in updates. Do you know if the Bluetooth issue got fixed?

ammarr said:
Definitely interested in updates. Do you know if the Bluetooth issue got fixed?
Click to expand...
Click to collapse
ok cool. I'll post an updated HOMEMADE build.
Main bugfixes are:
1. camera doesn't randomly crash at start anymore.
2. bluetooth doesn't cause device to stay awake
3. bluetooth and fm can be used without rebooting the device inbetween (not concurrently though, using bluetooth when fm is on will disable fm for example)
EDIT: build is done, tested and all seems ok
download link in OP

Thanks for the new rom. I'm going to flash it asap and let you know how it works. Keep up the work!

Tried this out today and it works really well. I'll probably try it out as a daily this week, because the bugs seem quite minor at this stage. I'm surprised that this isn't getting more attention. Since the BT bug is fixed, I'm wondering if the same fix will work for CM13 as well?
@oshmoun Nice work! I'm not sure how OmniROM works, but what is stopping you from updating official with the same changes?

ammarr said:
Tried this out today and it works really well. I'll probably try it out as a daily this week, because the bugs seem quite minor at this stage. I'm surprised that this isn't getting more attention. Since the BT bug is fixed, I'm wondering if the same fix will work for CM13 as well?
@oshmoun Nice work! I'm not sure how OmniROM works, but what is stopping you from updating official with the same changes?
Click to expand...
Click to collapse
Hehe well I'm just doing the building. Awesome people from the Sony open devices project helped fix the bugs
Official updates for omni 6.0 only come in form of security updates, i.e when Google uploads a new revision. That's why i can't update official that simply. Although to be honest I haven't asked if there are exceptions

I've flashed the rom today and it is working very well. The fingerprint scanner now works fine, even from the settings.
Thanks!

speedtoucher said:
I've flashed the rom today and it is working very well. The fingerprint scanner now works fine, even from the settings.
Thanks!
Click to expand...
Click to collapse
Really? It still doesn't work here.
Maybe it's because you did a full wipe.
Can you try adding/removing fingerprints from settings multiple times please? If it works reliably, that'd be great

oshmoun said:
Really? It still doesn't work here.
Maybe it's because you did a full wipe.
Can you try adding/removing fingerprints from settings multiple times please? If it works reliably, that'd be great
Click to expand...
Click to collapse
I flashed the Homemade version yesterday. I too am able to add fingers after initial setup in the settings. I tried to delete a finger in order to retry but the OS shuts down and reboots.

I believe I found a bug. Homemade version.
While listening to Audio, the whole phone locks up after what seems to be random times. I've listened to audio for a few minutes then it locks. I've listened up to around 45 minutes then locks up. Never more than an hour. If it helps, I've had this occur with Google Play Music, Poweramp, and Pocket Casts apps.
To resolve this, I have to hold power and volume up (Force shut down?)

Turnilemikus said:
I flashed the Homemade version yesterday. I too am able to add fingers after initial setup in the settings. I tried to delete a finger in order to retry but the OS shuts down and reboots.
Click to expand...
Click to collapse
yeah so it's still buggy I guess. I don't think i'll be able to fix that though, sadly. However, I can confirm that the issue doesn't appear on android nougat.
Turnilemikus said:
I believe I found a bug. Homemade version.
While listening to Audio, the whole phone locks up after what seems to be random times. I've listened to audio for a few minutes then it locks. I've listened up to around 45 minutes then locks up. Never more than an hour. If it helps, I've had this occur with Google Play Music, Poweramp, and Pocket Casts apps.
To resolve this, I have to hold power and volume up (Force shut down?)
Click to expand...
Click to collapse
hmmmm, yes you are right. I was able to reproduce that. I think I know why that happens. I used another fix for mp3 playback. The solution that's used in OFFICIAL is different from HOMEMADE.
well, the good news is that android nougat requires neither lol.

Thank you for your time and the build. I've never seen OmniROM before today.

Today I've tried to add some more fingerprints. But now it fails.
I skipped the fingerprint registration during the initial installation and added 3 fingers later, but now it just fails every time.
I also encountered the audio playback issue while using Spotify today.

Hey oshmoun
I'm enjoying your Homemade!
Herzlichen Dank!
Keep on coding! :good:

Official Android Pie - discussion and experience

We should use this thread to discuss about the official Android 9 update for the Mi A2 Lite!

Cool, but many didn't get the update yet...

It has dark mode?
I am on Havoc OS 2.0, but it hasnt update... Maybe I will return to stock...

iniro said:
It has dark mode?
I am on Havoc OS 2.0, but it hasnt update... Maybe I will return to stock...
Click to expand...
Click to collapse
I thought it has the dark mode, but it hasn't. You can find it in the settings but if you activate it nothing happen..

I noticed that the performance is slightly better than Oreo. The phone runs faster and there are much fewer lags!
First I thought the battery drain got heavier, but after the second day it reached the normal drain, which we know from Oreo
Also I love the new stock launcher. It's like the Pixel-Launcher with the "at a glance" feature, just as the new navigation-gestures which we also know from the Pixel-devices.

00norman00 said:
I thought it has the dark mode, but it hasn't. You can find it in the settings but if you activate it nothing happen..
Click to expand...
Click to collapse
It has a dark mode but it's very limited. When you activate it the quick settings in the notification area and some colour accents on the home screen and app list will become dark. It will not, however, change any other colours in the OS.

I'm experiencing some serious lag at moments.
On oreo I barely experienced lag at all.
Any advice?

I'm having lag/stutter in recent tasks... It was way faster in Oreo and I preferred the vertical layout.
Sent from my Mi A2 Lite using Tapatalk

agamotto said:
I'm having lag/stutter in recent tasks... It was way faster in Oreo and I preferred the vertical layout.
Click to expand...
Click to collapse
If you have root, you can disable the StockLauncher and download another launcher from the PlayStore. Then you will have the vertical layout.

Updated mine in Austria by following the VPN method.
On first boot I face WiFi connection issues and also Bluetooth is not working fine. - resolved by the first reboot
I face a poor call audio distortion.
Videos, Music, etc. that uses the other loudspeaker is working fine but in phone calls using the other speaker I face massive saturation effects even with small volume.
I also tried to manufacturing reset my phone, without success.
best regards,
Mario

Correct. I updated mine yesterday and can confirm, poor call audio distortion. That thing drives me nuts.
The arrows on the network and wifi icons on notification is also a thing to remove, or at least give us the chance to remove it.
Besides that, i didn't see to much cases.

sandman01 said:
Updated mine in Austria by following the VPN method.
On first boot I face WiFi connection issues and also Bluetooth is not working fine. - resolved by the first reboot
I face a poor call audio distortion.
Videos, Music, etc. that uses the other loudspeaker is working fine but in phone calls using the other speaker I face massive saturation effects even with small volume.
I also tried to manufacturing reset my phone, without success.
best regards,
Mario
Click to expand...
Click to collapse
This is a widely seen bug for Pie which I personally find not acceptable in 'stable' release. Couldn't do a calls due to sound quality and reverted back to Oreo.

I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?

itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you clear the Data of the Google Apps?

itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you clear the Data of the Google Apps?

streetspy said:
This is a widely seen bug for Pie which I personally find not acceptable in 'stable' release. Couldn't do a calls due to sound quality and reverted back to Oreo.
Click to expand...
Click to collapse
Can you detail how to revert to Oreo?
Sent from my Mi A2 Lite using Tapatalk

itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you remove sim card and wipe all the things?

00norman00 said:
Did you clear the Data of the Google Apps?
Click to expand...
Click to collapse
I did.

itwasmistake said:
I did.
Click to expand...
Click to collapse
Mhmm, it only work for me when I used the CyberGhost-VPN-App (free trial). ExpressVPN or something else didn't work for me

Okay. So doing factory reset fixed the lag in recent apps.
But I did an antutu benchmark and the performance has dropped significantly from 78232 to 67477.
Anyone else can confirm this?

Question Ghost touch issue

Hey guys!
I'm currently on ArrowOS 07.09 build with firmware 12.5.1. In the last 2 weeks I got ghost touch issues quite frequent. The phone starts to recognize touches crazy fast without me touching it and doing random things. I have to lock the phone with the power button to make it stop.
Does anyone else have or had the same issue? Is it a hw or sw related issue in your opinion? Any tips, ideas, working methods are welcome to make it stop.
Thank you!

It's mostly a SW issue , but it can also be a hardware issue(extremely rare),change the room to pixel plus UI 3.7 most stable(tested by me).
edit: also less bugs than others and very fluent.

I had the same problem. The solution is to turn off the Game Turbo app. Your problem will be solved.

Mine problem is solved by send it to service center. They replaced screen module.

Reporting.
For anyone facing heavy ghost touch issue, you might want to try indonesian miui 12.5.2 rom (rjuidxm)
Previously I got ghost touch on xiaomi.eu 12.0.4, 12.5.1, 12.5.2 to 12.5.4, few arrow OS version, to the point that I got tired of testing backing up restoring and doing clean flash everytime, because this is my primary phone I use for daily driver
But now I have used miui 12.5.2 ID for 9 days and haven't faced any ghost touch.. I also always turned on show taps on dev options so that I'll know if theres any ghost touch, and theres none so far (I have 6/128 unit with tianma panel)
But there's huge performance drop in this rom, game that I play (PGR) have noticeable frame drops where theres none before, others also reported lower performance on genshin impact

i dont have such issue
at least i dont notice it responding to "something" when i just leave it on table
btw, clothing contacts are also contact

Antonio7489 said:
It's mostly a SW issue , but it can also be a hardware issue(extremely rare),change the room to pixel plus UI 3.7 most stable(tested by me).
edit: also less bugs than others and very fluent.
Click to expand...
Click to collapse
sw?

Skytsengel said:
sw?
Click to expand...
Click to collapse
software?

runfox said:
software?
Click to expand...
Click to collapse
software

Skytsengel said:
sw?
Click to expand...
Click to collapse
software my friend , i write it fast

For me, it has helped now to set the refresh rate and the screen to 60 Hz. We'll see for how long. All other activities did not help, including the game turbo exclusion.

Unfortunately, but with the 60 Hz refresh, the touch has gone crazy once, but it probably happens less often

well it depends on what screen you have, if it's tianma the ghost touch is "normal" and will only get worse because is hardware related, if it's Huaxing it's probably software related or (very bad luck) defective screen...
you can know your screen:
If you are on a Custom ROM or have installed Magisk:
1. Download Device Info HW application
2. Tap on 3 dots in the right corner of the application
4. Restart the app
5. Check LCM (above touchscreen)
dsi_j20s-42-02-0b <- CSOT/Huaxing
dsi_j20s-36-02-0a <- Tianma
If you are on MIUI without root:
1. Open your dialer and enter: *#*#284#*#*;
2. Open a File Manager, go to ~/MIUI/debug_log/ directory, you should see an archive named bugreport-yyyy-mm-dd-HHMMSS; (Date and time when bugreport was created)
3. Extract that archive, then extract another archive which was in bugreport zip, its name should look like this - bugreport-vayu_global-RKQ1.200826.002-2021-05-27-13-32-52.
4. In bugreport-vayu_global folder open dumpstate_board.txt and type in search tianma. If it's found, you have tianma, otherwise huaxing.

Thanks. I checked my tianma. I found such a coincidence "MDPPLATFORM_PANEL_TIANMA_NT36672C_J20S_LCD_VIDEO" How do you think to advertise the phone?

Well there is many reports that it fixed with MIUI 12.5.5.0 global latest update. ( confirm it, please!?)
For me never happened "tianma".
Regards

Jestem na miui 12.5.2.0 EEA i nie ma jeszcze aktualizacji do 12.5.5.0

Update to miui 12.5.5

Antonio7489 said:
software my friend , i write it fast
Click to expand...
Click to collapse
ok thanks for be clear XD

Abdullah.Csit said:
Well there is many reports that it fixed with MIUI 12.5.5.0 global latest update. ( confirm it, please!?)
For me never happened "tianma".
Regards
Click to expand...
Click to collapse
yes my phone update the MIUI to 12.5.5.0 and everything its good and smooth but I'm a little scared, if another update ends up breaking the device. On the other hand, I activated the option, to see the touches on the screen through the developer options, and detect that when I use YouTube and try to put a video in landscape using the button in the video, a single ghost touch appears in the middle of the screen, it does not affect at all apparently, but it seems to me that the ghost touches were not corrected correctly or in its entirety.