Develop Bugs

WP7 Annoying Call Menu

Hi guys
Who else thinks that planning of making calls in WP7,
is very annoying to click a button (marked in red picture) to open a menu specially Speaker
What do you think?
{
"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"
}

For over 3 months this never annoyed me honestly.

Hasn't annoyed me yet either but i just got my phone this week. I was thinking of a better way they could have done it but all of my ideas have pluses and minus just the same so guess we got what we got.

No issues here... has worked fine for those time when I need to speaker phone it or use the keypad.

not annoying. it's a minimal design, so why have those options always display if you don't always need them?

Not happening here

I don't use speaker as much so it's no biggie, nor do I often use the keypad during a call, though I do sometimes. But overall it isn't THAT annoying, just a little.

I use the speaker about 50% if the time and I whole heartedly 100% agree with the OP. Its a pain to have to hit that little button every time
it doesn't ruin the whole experience for me, but it is pretty annoying.

<3 hTc
If I want something from the menu, it's not too much hassle to have to click, and what's even better is that thanks to hTc's Attentive Phone app if i want the speakerphone, i just put the phone face down on a surface and the speaker automatically activates. Simples.

what the hell do the poll options mean lol

DatDereX1 said:
what the hell do the poll options mean lol
Click to expand...
Click to collapse
i haven't a clue either

doministry said:
For over 3 months this never annoyed me honestly.
Click to expand...
Click to collapse
Agree. I think that's actually a pretty good design, however I find it clunky. The buttons should be at the bottom, and I do think some obvious functionality like speaker phone should not require you to click twice. That's just my opinion.
TBQH, I much prefer the Galaxy S (Vibrant) dialer interface. It makes more sense.
But there isn't much wrong with this...
There is a point where you can take minimalist so far that it actually starts to impede on usability. This is one of those cases, IMO.

No problems for me either. I actually dig it because it allows you to tap the screen and perform tasks in the background. Alternatively, it allows you to look at whatever screen you were looking at before the call was made or received. e.g. you went into a specific profile under People, you're still able to see their contact info such as email if you were to email something to that person.
Even if those soft keys were available immediately when the call became active you'd still have to do some kind of multi-step process to accomplish some other task you wanted to do on your phone.
Frankly, I'd rather have the information I was looking at prior to when the call came or when I initiated the call, still immediately available to me. All in all seems pretty efficient to me for viewing information.

ScottSUmmers said:
No problems for me either. I actually dig it because it allows you to tap the screen and perform tasks in the background. Alternatively, it allows you to look at whatever screen you were looking at before the call was made or received. e.g. you went into a specific profile under People, you're still able to see their contact info such as email if you were to email something to that person.
Even if those soft keys were available immediately when the call became active you'd still have to do some kind of multi-step process to accomplish some other task you wanted to do on your phone.
Frankly, I'd rather have the information I was looking at prior to when the call came or when I initiated the call, still immediately available to me. All in all seems pretty efficient to me for viewing information.
Click to expand...
Click to collapse
The dialer app multi tasks. There no excuse for hiding 4 options under a button - none whatsoever. You can simply home out of it and look at the entire page, or even use your data connection unless you're unfortunate and have a CDMA phone...

aquadextrous said:
If I want something from the menu, it's not too much hassle to have to click, and what's even better is that thanks to hTc's Attentive Phone app if i want the speakerphone, i just put the phone face down on a surface and the speaker automatically activates. Simples.
Click to expand...
Click to collapse
Yes but what happens IF the phone is "face down" in pocket?

N8ter said:
The dialer app multi tasks. There no excuse for hiding 4 options under a button - none whatsoever. You can simply home out of it and look at the entire page, or even use your data connection unless you're unfortunate and have a CDMA phone...
Click to expand...
Click to collapse
So you'd rather have the dial pad hidden instead? Or is everything going to be placed out in the forefront? There's only so much screen space, though I guess it could work. I'm looking at the Galaxy S and it looks ugly as ****. Screw that mess, I'd rather have the stuff I was looking at available for viewing in the background then a damn num pad.

N8ter said:
The dialer app multi tasks. There no excuse for hiding 4 options under a button - none whatsoever. You can simply home out of it and look at the entire page, or even use your data connection unless you're unfortunate and have a CDMA phone...
Click to expand...
Click to collapse
It's not shown by default for the same reason battery and signal aren't shown on the start screen. Much cleaner look without the buttons showing. No need to always have them showing.

Samsung Lock Screen Bypass Exploit

Posted in the General S III forum but it's so severe, everyone should be informed:
http://forum.xda-developers.com/showthread.php?p=38848847#post38848847

BluechipJ said:
Posted in the General S III forum but it's so severe, everyone should be informed:
http://forum.xda-developers.com/showthread.php?p=38848847#post38848847
Click to expand...
Click to collapse
I'll test this out tomorrow. Pretty bad if it does indeed work (which it seems it will).

Just tested it took a couple times this dose work they need to fix this,I'm also running 4.1.2 MB1
Sent from my Thrive using Tapatalk 2

Guess I'll stay on LJ7 until its fixed.
Sent from my GS3

The bad thing about reporting these exploits, is that it allows for the people that are liable to steal someone's info/device to know exactly how to do it. It's great to precaution owners, just wish there was another way to alert users.

HashTagHell said:
The bad thing about reporting these exploits, is that it allows for the people that are liable to steal someone's info/device to know exactly how to do it. It's great to precaution owners, just wish there was another way to alert users.
Click to expand...
Click to collapse
True. But then it becomes more difficult because how can you determine if those users wont try to steal someone info? Its hard

yes everyone needs to be educated on this exploit because in no way will anyone ever use this to learn how to unlock a stolen phone.
makes sense.

cnstarz said:
yes everyone needs to be educated on this exploit because in no way will anyone ever use this to learn how to unlock a stolen phone.
makes sense.
Click to expand...
Click to collapse
Well now that they know they can take preventative measures to keep it from happening, like using another lockscreen thats not stock, or flashing an AOSP rom.

CNexus said:
Well now that they know they can take preventative measures to keep it from happening, like using another lockscreen thats not stock, or flashing an AOSP rom.
Click to expand...
Click to collapse
because there's no possible way of getting that information across to people without showing everyone with bad intentions the exact, step-by-step method used to exploit it.
{
"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"
}

cnstarz said:
because there's no possible way of getting that information across to people without showing everyone with bad intentions the exact, step-by-step method used to exploit it.
Click to expand...
Click to collapse
Well obviously he has to state it like that or no one would be able to replicate the issue and believe him. Seems like you have better ideas as to how to do it, mind sharing?

I dont see the big deal, if someone steals your phone and cant access it, they will just do a factory reset and you will lose any chance of tracing and recovering your phone or remote wiping it.

ricocollege said:
I dont see the big deal, if someone steals your phone and cant access it, they will just do a factory reset and you will lose any chance of tracing and recovering your phone or remote wiping it.
Click to expand...
Click to collapse
Yup, that too. Unless you move your lockscreen app to the system partition which cant be wiped like that

CNexus said:
Well obviously he has to state it like that or no one would be able to replicate the issue and believe him. Seems like you have better ideas as to how to do it, mind sharing?
Click to expand...
Click to collapse
If it was me, I'd send Samsung a message about it. If that was the video poster's intent, he could've went about informing Samsung another way. People that find lost GS3s will definitely find this now. I know somebody who's found an ipod that had a PIN on it and the first thing they did was google how to crack it.
Still, this video also serves a purpose to inform those who can fall victim to this. It's a hit or miss. Samsung definitely is aware of the issue now, though.

Of course any exploit is a problem, but put it in perspective.
First, the criminal has to have physical access to your phone. This in itself makes it much less worrisome than most software hacks that you can download.
Second, according to Engadget:
"Despite literally hundreds of attempts in front of the lens and several more behind it, we've only managed it once -- we found it impossible to nail down the correct timing between the home and power button pushes."
and also from Engadget:
" Samsung has responded, confirming a fix is indeed on its way:
"Samsung considers user privacy and the security of user data its top priority. We are aware of this issue and will release a fix at the earliest possibility."
http://www.engadget.com/2013/03/06/galaxy-s-iii-bug-disables-lock-screen/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+weblogsinc%2Fengadget+%28Engadget%29
So, the blogs stir up a frenzy, make some money on click-thrus, and it gets fixed.
Nothing to see here,

Temporary Fix (Makes it much harder to exploit)
Temporary fix:
1) Download another launcher like "Go Launcher". Set it as default.
2) Download and install another lock screen like the "Go Locker" and set it up.
:good:
The problem is Samsung's Touchwiz launcher, getting another launcher is the only thing we can do until we get a fix from Samsung. This exploit takes about 5 minutes every time if you sit and get good at doing it. Dont kid yourself, this is very easy to reproduce.
In theory installing another launcher will make doing this much harder to do but will not completely eliminate the chances of getting exploited. This is because the touchwiz launcher still rears its ugly head when you reboot your phone. But if the attacker cant exploit your phone by the time the new launcher is loaded in the background then they have to restart your phone and try all over again.

I'll test it tomorow.hii

I found it simple to repeat. It took me 5 tries to get it. I am not that concerned about it but my work probably would be...
Sent from my Nexus 7 using xda app-developers app

Tried this with multiple scenarios and activating "with swipe lock" in addition to password or pin will prevent it from working because the swipe lock will always come up even if you're seeing the home screen.
pr0fess0rx29 said:
Temporary fix:
1) Download another launcher like "Go Launcher". Set it as default.
2) Download and install another lock screen like the "Go Locker" and set it up.
:good:
The problem is Samsung's Touchwiz launcher, getting another launcher is the only thing we can do until we get a fix from Samsung. This exploit takes about 5 minutes every time if you sit and get good at doing it. Dont kid yourself, this is very easy to reproduce.
In theory installing another launcher will make doing this much harder to do but will not completely eliminate the chances of getting exploited. This is because the touchwiz launcher still rears its ugly head when you reboot your phone. But if the attacker cant exploit your phone by the time the new launcher is loaded in the background then they have to restart your phone and try all over again.
Click to expand...
Click to collapse

nacron said:
Tried this with multiple scenarios and activating "with swipe lock" in addition to password or pin will prevent it from working because the swipe lock will always come up even if you're seeing the home screen.
Click to expand...
Click to collapse
Nah, "with swipe lock" in addition to password or pin doesnt change anything. My friend can still break in within 5 minutes. Then he laughs at me. the only thing that shut him up was changing the launcher and lock screen to something other than touchwiz. :highfive:

I tried on my Sprint S3 and I couldn't re produce the exploit can somebody be more speciffic on how to do it exactly with the button combo. So I can try again.
Sent from my SPH-L710 using xda premium

Knock code do not work

Hello, guys.
Knock code is not working on my G4...
I need to turn on the screen to use the code...
I have to make some configuration?
Thx.

This happens to me sometimes to, it works with the screen off sometimes, but most of the time I have to turn the screen on. Usually use double-tap to wake when that happens. Probably going to get better functionality with an update hopefully.

Happen to me too... Never had this problem on G3
Sent from my LG-H818 using Tapatalk 4

i tought im the only one experiencing this. good thing others are encountering this as well.. i missedthe touch sensitivity feature now which is not avail in this phone anymore..
Sent from my LG-H815 using Tapatalk 2

Same thing was happening to me. I had a screen protector on that covered everything but the speaker. I took that off, and put one on with cutouts and I haven't had an issue since.

{
"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"
}
How do you even enable knock code? Mine is greyed out.

Mine works just fine here on Verizon. Knock twice to turn on/off the screen LOVE IT! Much better than clicking the home or power button on my past Sammys

Dennisg34 said:
Mine works just fine here on Verizon. Knock twice to turn on/off the screen LOVE IT! Much better than clicking the home or power button on my past Sammys
Click to expand...
Click to collapse
Not the double tap to wake. The option where you tap a code into the screen instead of using a standard lock screen code or pattern unlock.

Same here, too many misses of the Knock code (compare to the G3). I really hope that it's just software issue and not hardware (digitizer).

It's hit or miss with mine (no pun intended). When the screen is on, there is a square, blue outline of a box in the lower half of the screen. I assume at that point you're supposed to tap within the box, rather than using the entire screen?
Signature edited to appease the OCD's

frigidazzi said:
How do you even enable knock code? Mine is greyed out.
Click to expand...
Click to collapse
Do you have exchange mail set up? A lot of companies require a more secure lock to the phone and disable knock code and face unlock, etc.

Semantics said:
Do you have exchange mail set up? A lot of companies require a more secure lock to the phone and disable knock code and face unlock, etc.
Click to expand...
Click to collapse
Nope. This is a personal device. h815.

frigidazzi said:
Nope. This is a personal device. h815.
Click to expand...
Click to collapse
Check what has admin privs on your phone. Something has credentials that are blocking Knock code and swipe unlock.

Semantics said:
Check what has admin privs on your phone. Something has credentials that are blocking Knock code and swipe unlock.
Click to expand...
Click to collapse
Where can I check this? Because I have no idea what you are talking about...
My device model is H818P.

Semantics said:
Check what has admin privs on your phone. Something has credentials that are blocking Knock code and swipe unlock.
Click to expand...
Click to collapse
I tried this. I un checked everything. Still no change. I thought maybe because I wasn't using the stock home screen, but even switching to that didn't change anything.

frigidazzi said:
I tried this. I un checked everything. Still no change. I thought maybe because I wasn't using the stock home screen, but even switching to that didn't change anything.
Click to expand...
Click to collapse
I too am having the same problem... H815 uk version... I even factory defaulted it and it was still greyed out without any settings on it

frigidazzi said:
How do you even enable knock code? Mine is greyed out.
Click to expand...
Click to collapse
I was having this same problem and even factory defaulting the device did not help.
I later found out that I was accessing it the wrong way and all is well now.
Go to Settings > Display > Lock Screen > Select Screen Lock and you should be able to choose them properly.
However, I was accessing it through:
Settings > General > Security > Screen pin and over here the options for knock code is grayed out.
I hope this helped~!

I've been having the same issue with the knock code only working 70% of the time when the screen is off. I didn't own the G3 so I have no idea if this is worse performance than it. It's very frustrating. This and the slow charging issues the G4 has are really disappointing.

pandap said:
I was having this same problem and even factory defaulting the device did not help.
I later found out that I was accessing it the wrong way and all is well now.
Go to Settings > Display > Lock Screen > Select Screen Lock and you should be able to choose them properly.
However, I was accessing it through:
Settings > General > Security > Screen pin and over here the options for knock code is grayed out.
I hope this helped~!
Click to expand...
Click to collapse
Yeah this is exactly how in accessing it

liamR said:
Same here, too many misses of the Knock code (compare to the G3). I really hope that it's just software issue and not hardware (digitizer).
Click to expand...
Click to collapse
FYI, T-Mobile pushed out an update this week. Among the changes (actually, the only change I've noticed so far) is the knock to unlock has improved. That seems to suggest a software fix can help.
Signature edited to appease the OCD's

Question Android TV app weirdness or glitch

Hi everyone.
I'm faced with difficulties when I run Android TV remote control app (https://play.google.com/store/apps/details?id=com.google.android.tv.remote) on my P6Pro. It appeared to behave like an obsolete app abandoned by its developer - it never opens fullscreen.
{
"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"
}
I really don't care about that and could live with it as the app works like it should until I leave it foreground and turn off the screen. As soon as I turn my screen back on my phone hangs up and there is no possibility to get to home screen or go back. It happens from time to time, not every time I use it. Power button just turns the screen on/off and my only option is to press power+volume up buttons to reboot the phone.
I remember I was able to adjust full screen behavior for my apps in the previous versions of Android somewhere in settings. Now that option has gone in A12.
Any ideas?

I don't have an Android TV, but I just wanted to let you know your link https://play.google.com/store/apps/details?id=com.google.android.tv.remote doesn't work for me.

checked, the link works for me. Anyway I mean this app

asdor said:
I checked, it works. Anyway I mean this app
Click to expand...
Click to collapse
Weird. Google must have it blocked unless you actually own one. On both the phone (Wi-Fi and Mobile Data) and the computer the link doesn't work and I can't find that app listed when I search for it by name.
Anyway, I know it's not relevant (I guess), just weird.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Another glitch? Unfortunately not the last one.

BTW, I just tried to open that link in chrome incognito mode
What's going on, Google? Is the app account-specific? Is it not available for everybody?

I just realized what the problem is. The app is really abandoned and it's obvious from my 2nd screen.
"Last updated April 4, 2017"
The reason I like it is an ability to enter login/pass details on my Android TV using my phone screen. This is the feature I was envious of iPhone users for its native integration into Apple TV.
Ok, RIP.
My only options are to get used to manual reboots or Force Stop the app after each use.

My understanding is that "Android TV Remote" is actually obsolete, and its functionality has been incorporated into "Google Home": https://play.google.com/store/apps/details?id=com.google.android.apps.chromecast.app

The standalone Android TV Remote app has been decommissioned by Google. The functionality has been moved to the Google Home app and is available as a Quick Settings tile

craigacgomez said:
The standalone Android TV Remote app has been decommissioned by Google. The functionality has been moved to the Google Home app and is available as a Quick Settings tile
Click to expand...
Click to collapse
Ah! That's helpful to know.

asdor said:
Another glitch? Unfortunately not the last one.
Click to expand...
Click to collapse
Not a glitch. Stop spreading misinformation. This is a perfect example of why half the complaints on this forum are bogus.

It is a frustrating change though in the very least, because who needs all the bloat of "home" when all you want is a remote control?
Anyway, I just ordered a couple of ADT-3's, which is the "developer" version of ccgtv. I'm tired of being locked out, and I don't give a flying f*** about netturds. Years ago I wrote a remote service for nexus player, which shouldn't be too hard to adapt to ADT-3.

wulfgarfang said:
Not a glitch. Stop spreading misinformation. This is a perfect example of why half the complaints on this forum are bogus.
Click to expand...
Click to collapse
I think they were joking (smiley face).

96carboard said:
It is a frustrating change though in the very least, because who needs all the bloat of "home" when all you want is a remote control?
Anyway, I just ordered a couple of ADT-3's, which is the "developer" version of ccgtv. I'm tired of being locked out, and I don't give a flying f*** about netturds. Years ago I wrote a remote service for nexus player, which shouldn't be too hard to adapt to ADT-3.
Click to expand...
Click to collapse
Well, from Google's perspective, it is logical to have it as part of the Google Home app. Android TV/Chromecast is part of the Google Home (devices) ecosystem.
That being said, if you don't want to use the Google Home app, there is an alternative
Android TV Remote - Apps on Google Play
Unofficial Android TV / Google TV remote control. Simple, convenient, complete!
play.google.com

craigacgomez said:
That being said, if you don't want to use the Google Home app, there is an alternative
Android TV Remote - Apps on Google Play
Unofficial Android TV / Google TV remote control. Simple, convenient, complete!
play.google.com
Click to expand...
Click to collapse
Thanks, I know there are several alternatives by other developers but I always do my best to go google Just figured out how to enable Open Remote button in Google Home app at 3 different android tv boxes I own - Shield Pro, Onn TV and Dynalink TV. I had to manually update Android TV Remote Service to v.5.
Now I've got almost the same features, at least I can still enter text remotely on my phone.

Question Experience any bugs on the Vivo X80 Pro? Let's share and help each other!

So the few of us that bought this phone so far probably encountered some bugs here and there.
Let's share them and try to help each other, or even make Vivo aware of it.
1) Not Vivo exclusive, but the LTPO 3.0 display never drops to 1hz for me.
I've read it happens on S22 as well, OPPO, ONP phones.
Will update more in the future.

My refresh rate is set at 120hz but why does it still go down to as low as 10? Shouldn't it remain 120 no matter what since that's where I set it?

That's how LTPO works, in order to save battery as well.
You barely notice it though, i also set 120hz and i don't feel when it gets down.

set light mode and brightness more than 70% and screen will go 1hz at still.
problems - a lot of apps crashes/not start. diablo immortal not working at all

MrDiegoSPB said:
set light mode and brightness more than 70% and screen will go 1hz at still.
problems - a lot of apps crashes/not start. diablo immortal not working at all
Click to expand...
Click to collapse
From 10hz to 1hz probably won't make much difference anyway.
As for Diablo immortal, it works great here no crashes at all.
Have you tried clearing the cache out?

Derpling said:
That's how LTPO works, in order to save battery as well.
You barely notice it though, i also set 120hz and i don't feel when it gets down.
Click to expand...
Click to collapse
But isn't that what smart switch is for? Why have the option for smart switch, 60, 120 if it'll always switch anyway? I feel it's what's causing the stutters even when I'm just scrolling

you have global rom (funtouch) or CN Origin?
Diablo works fine when i got device (OriginOS) but after last update of firmware a lot of apps wont work now

enyaj said:
But isn't that what smart switch is for? Why have the option for smart switch, 60, 120 if it'll always switch anyway? I feel it's what's causing the stutters even when I'm just scrolling
Click to expand...
Click to collapse
You are right, the stutters are due to LPTO 3.0 and the way Vivo implanted it.
They might fix it, but we need to ask them.

Derpling said:
You are right, the stutters are due to LPTO 3.0 and the way Vivo implanted it.
They might fix it, but we need to ask them.
Click to expand...
Click to collapse
Yeah I hope they do release a fix. Not that it's a deal breaker but I'm just used to smooth scrolling with my Pixel phone

Well let them know then.
I'll open a ticket.

For me (CN Version) Samsung health is not working. Anyone else has the same Problem ?

Hi! i have and x80 pro cn version and i cant unistall the pdf reader that comes with the phone. I try to use the ones that comes with the google drive, or another and simply doesnt let me and its annoying.Anyone has the same problem? because the ones that come with the phone its in chinesse and i dont understand nothing.
Help! thanks!! i think that the solution is disable via ADB but i dont know how or which app is it.

Anyone knows a solution for google assistant? Everytime I start the phone new, i have to set Google as my Standard App for speech assistance. Its kind of annoying me

monex12 said:
Hi! i have and x80 pro cn version and i cant unistall the pdf reader that comes with the phone. I try to use the ones that comes with the google drive, or another and simply doesnt let me and its annoying.Anyone has the same problem? because the ones that come with the phone its in chinesse and i dont understand nothing.
Help! thanks!! i think that the solution is disable via ADB but i dont know how or which app is it.
Click to expand...
Click to collapse
Have you solved it yet?

kenajanek said:
Anyone knows a solution for google assistant? Everytime I start the phone new, i have to set Google as my Standard App for speech assistance. Its kind of annoying me
Click to expand...
Click to collapse
What version you have?

Derpling said:
What version you have?
Click to expand...
Click to collapse
Chinese snapdragon Version

Just curious, one question to the owners of funtouch os: do you have google lens integrated into your camera app enabling a barcode scan?
I do not find any possibility to do that with the global (origin os, Chinese) version. Apparently one needs an extra barcode scanning app...

ZarW said:
Just curious, one question to the owners of funtouch os: do you have google lens integrated into your camera app enabling a barcode scan?
I do not find any possibility to do that with the global (origin os, Chinese) version. Apparently one needs an extra barcode scanning app...
Click to expand...
Click to collapse
You can scan barcodes in Jovi Vision.
Camera -> More -> Jovi Vision.
But I think only chinese barcodes are supported.
It didn't work for any euro barcode I tried.

{
"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"
}
I've noticed that after using the vivo 50W wireless charger to charge the phone to 100% then checking battery health in devcheck or any other app for that matter it will show "Overvoltage" in battery health. Sometimes it happens randomly during the day. It will return back to "Good" after rebooting the phone but then after a while it will show Overvoltage again. Is this because the phone has dual-cell battery? A software bug? Because I'm not having any battery issues whatsoever like overheating and battery backup has been great.

Whilst using night mode sometimes, the phone takes too long to process. Then ends up turning the picture into a fully green picture. So none of the original image is saved. Only green screen. Any ideas on how to fix this?