I tried these 2 modes:
settings put secure display_cutout_hide_notch 1
settings put system op_camera_notch_ignore 1
Nothing worked.
Reason: OS cuts out more pixels than actual cutout killing my useful space. (verically and horizontally).
I want OS to set cutoit to NONE as if there is no cutout.
ALTERNATIVE: How to set custom size cutout without root?
Seems it's a complete hit or miss depending on the phone manufacturer and even model.
I have 2 Note 10+'s, one running on 9, the newer on 10. The both look and behave almost identically though. Under the hood though it becomes apparent Samsung went to great lengths to accomplish this on the Q variant. The Q variant has dozens of new small system apks to achieve this. They don't appear to reduce battery life or performance at all.
Then I saw this. It's nuts. Be glad you don't have that phone!
I'm pretty sure there is an option in developer options.
To enable just go to about phone find build version and spam tap it around 10 times then go to dev options and it "should" be there
If it's a samsung, it might be hidden. But My old ANDR11/OneUI3.1 device shows it.
JaydenDev said:
I'm pretty sure there is an option in developer options.
Click to expand...
Click to collapse
The Problem is, in Dev.options I see "Default, Corner, Double (Top&Bottom), Narrow (narrower but taller)".
I don't see None option. Usually if you don't, you stillmight find that in hidden Engineer Menu but that is too much of a hassle for a possibility.
AjvarXX said:
The Problem is, in Dev.options I see "Default, Corner, Double (Top&Bottom), Narrow (narrower but taller)".
I don't see None option. Usually if you don't, you stillmight find that in hidden Engineer Menu but that is too much of a hassle for a possibility.
Click to expand...
Click to collapse
Setting it to none would cause lots of issues I believe.
Related
Hoping someone may be able to help me figure this out. Daughter got ahold of my phone the other day. Along with trying to charge about $50 worth of Talking Animal apps, she also enabled some sort of a process that appears in the upper right hand corner of the screen. It updates real-time, with what looks to be currently running processes [See attachment]. There is a graph bar behind the text that looks like it could either be a graph of memory or disk space usage. I've gone through every setting in the phone and can't seem to find anything that would be linked to it. It appears as though its a hard process that runs outside of a software controlled environment, if that makes sense. No matter what applications are opened up, this process overlay still persists. Checked in MAGLDR just to be sure there wasn't some funky option that had been changed.
Also, not the biggest deal in the world but somehow she changed my default sound effect for keypress on the keyboard. Sounds like a typewriter now. Maybe I'm not as near as familiar with the CyanogenMod environment as I thought; I can't seem to find that option either.
I'm currently using CyanogenMod-7 NIGHTLY Desire with MAGLDR v3.6.5.
Any help you guys can provide would be greatly appreciated. This is starting to drive me a little crazy.
No one has any idea?
It's under developer options uncheck "Show CPU usage". And for the keyboard sound go under sound and uncheck keytone (Which when enabled plays a sound when a keyboard key is pressed). Hope this helps .
Sent from my SCH-I535 using xda premium
Thank you Shrimp! It wasn't exactly the spot but it did definitely give me an idea of where to look. Completely forgot about the actual "Dev Tools APPLICATION on the phone. Found the setting under Dev Tools > Development Settings > Unchecked the 'Show Running Processes' option.
As far as the sound goes, I want the sound but somehow the original sound effect of the keyboard itself got swapped out with the this Typewriter sound. May need to make a separate post about it, just one of those minor inconveniences I'd hoped to knock out along the way.
Thanks again!
warpedcell said:
Thank you Shrimp! It wasn't exactly the spot but it did definitely give me an idea of where to look. Completely forgot about the actual "Dev Tools APPLICATION on the phone. Found the setting under Dev Tools > Development Settings > Unchecked the 'Show Running Processes' option.
As far as the sound goes, I want the sound but somehow the original sound effect of the keyboard itself got swapped out with the this Typewriter sound. May need to make a separate post about it, just one of those minor inconveniences I'd hoped to knock out along the way.
Thanks again!
Click to expand...
Click to collapse
Backup your apps and other data then reinstall Cyanogenmod that should fix your keyboard sound issue.
Sent from my SCH-I535 using xda premium
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
srdempster said:
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
Click to expand...
Click to collapse
My test device - that I picked up very cheep as it had been dropped and the SIM reader no longer works - displays the same issue, I had always assumed it was because of the fall it had.
Sorry if that doesn't help you
like this?
http://youtu.be/oyv5QmD5uQA
Exactly the same issue thanks
Same here but my phone is allways in case and i never dropped it. Oh and factory reset or flashing another ROM is not solution.
Any ideas?
I can only guess that either the RAM fills up with the screen off and once it starts to clear when the power button is pressed it suddenly can draw faster, or it's because the CPU and GPU clock down and slowly ramp up on wake. I'll change my performance settings see if that changes things?!
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
srdempster said:
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
Click to expand...
Click to collapse
So it's actually software problem right? Not damaged screen or something inside the phone.
Jecmenn said:
So it's actually software problem right? Not damaged screen or something inside the phone.
Click to expand...
Click to collapse
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
srdempster said:
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
Click to expand...
Click to collapse
mine is a hardware issue. you will see that it is currently on cm12 but it has done that on Stock, 4.4.x custom and 5.0 CM/AOSP as well. It will only do this if it hasn't be used for a few hours.
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Awesome, T2W works better now.... Thanks
P. S. Adding your thread to my all in one place guides.
xgerryx said:
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Click to expand...
Click to collapse
With the shortcut master i had several loading problems, i used QuickshortcutMaker and this is more easy, Thanks !
xgerryx said:
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Click to expand...
Click to collapse
This definitely helped! Kinda odd that there is a slight delay from when you double tap and when it actually wakes. I remember the LG G2 responding more quickly with this feature. Also miss the double tap to lock screen too that almost no other phone had (though with nova launcher and an app, you can do this). Regardless, I'm glad the functionality is there.
What's interesting about this little hack is that it clearly is using the force touch settings that will be found in the 6GB RAM model that has a force touch display. Funny how it remains in the ROM anyway, just tucked away since this model doesn't use force touch.
Can I remove the vibration when I use the double tap to wake?
This has made 0 difference for me. I've got a 64gb US variant. I've also noticed double tap to wake stops working when the phone is in Doze. Anyone else have this issue?
Same same with doze, but when my phone isn't deeply asleep this tip indeed increased touch sensitivity.
Sent from my ZTE A2017U
DrakenFX said:
Awesome, T2W works better now.... Thanks
P. S. Adding your thread to my all in one place guides.
Click to expand...
Click to collapse
Did you know this app is also present on the a2017u usa version?
But it is not doing anything...
manu7irl said:
Did you know this app is also present on the a2017u usa version?
But it is not doing anything...
Click to expand...
Click to collapse
I'm using the a2017u LoL always has been.
tolymatev said:
Can I remove the vibration when I use the double tap to wake?
Click to expand...
Click to collapse
Is there a setting to disable the vibration with double tap to wake?
I've tried the mod but don't see any differences for better response for the double tap to wake.
Sent from my iPad Air 2
I don't have anything like force touch in quick shortmaster app or shortcut master lite. I'm on european B03 update... Can anyone confirm this?
kodrnusa said:
I don't have anything like force touch in quick shortmaster app or shortcut master lite. I'm on european B03 update... Can anyone confirm this?
Click to expand...
Click to collapse
It's actually there as been always and with B02 software version.
Do hard reset if not see it
Something get wrong with upgrade in your case.
pklee said:
Is there a setting to disable the vibration with double tap to wake?
Click to expand...
Click to collapse
Don't have vibration with double tap.
How did you get it
paatha13 said:
Don't have vibration with double tap.
How did you get it
Click to expand...
Click to collapse
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
rczrider said:
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
Click to expand...
Click to collapse
Totally agree with this. It's still very inconsistent, but mine does work if I slam it twice as well as tap it lightly twice. It doesnt always work and it's still delayed. This was sort of a bandaid for a bigger problem though. I hope CM, and ....probably nothing else? at this point...can address it further.
rczrider said:
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
Click to expand...
Click to collapse
At EU version I don't see any option for vibration so far.
But totally agree I would like to be more response to a range of touch.
I remember when had LG flex 2 was better implementation than ZTE.
Hope future update improve that.
Sent from my iPad Air 2
paatha13 said:
At EU version I don't see any option for vibration so far.
But totally agree I would like to be more response to a range of touch.
I remember when had LG flex 2 was better implementation than ZTE.
Hope future update improve that.
Click to expand...
Click to collapse
Quite honestly, the Axon 7's story is perpetually: "[insert company here] did a better job of implementing [insert feature here]". There is very little (if anything) that the Axon 7 does better than the big manufacturers, IMO. It does a passable (sometimes even decent) job of most things, though - and at an appreciable discount - which is why I still have mine. It's a budget flagship. It's high-trim Toyota versus a Lexus. Add to that the potential for improvements via software (which is the source of many of my complaints, really), and I think it's a solid buy with quirks I'm willing to live with for a little while as ZTE steps up and makes improvements.
Yep exactly from hardware point is very very capable device but from software although it's pretty good level but there's still staff for many improvements.
Axon 7 is my first Chinese smartphone from Chinese company until now and I'm quite pleased with the all package offering having it 5-6 days,but I would like to see from ZTE much more effort and listening the user base and bring as much improvement and tweaks to the software.
Sent from my iPad Air 2
paatha13 said:
It's actually there as been always and with B02 software version.
Do hard reset if not see it
Something get wrong with upgrade in your case.
I already did factory reset. And then again . No such setting in quickshortmaker. I can post pics.. Weird...
Edit..
Did change language to English and found it ?
Click to expand...
Click to collapse
I notice no difference in the week that I used this tweak. So I just put this settings back. Yup, still no difference to me.
Sent from my ZTE A2017U using Tapatalk
I use my phone very often throughout the day, flash ROMs. The usual with such device as many of you know. To cut to the chase the navbar is almost always lit. So there is a likely hood of the navbar burning in, or the status bar.
More important things will be bolded, and the most important bolded and underlined
1. Go to Settings => Display => Set sleep to the lowest time that will work for you, the lowest - 15 seconds - is the best for your screen.
2. You can turn on inverted colors, this will turn the largely white UI to black. Although this will not look very aesthetically pleasing. It will reduce the burn in probability. - Not desirable I know
3. Change your wallpaper to a solid black color, I don't do this personally. But it does reduce the risk. You can also go for Black and gray wallpapers - you can find very good looking ones - but it won't be as great as just the black wallpaper.
4. Keep your brightness low, this keeps the diodes - pixels - from being at full brightness the entire time. Which lengthens their life span.
5. Change your theme to a black theme, or dark. As this will also help. You can change your keyboard to black from the Google Keyboard app. If you want a absolute black background on a keyboard, use the wallpaper from #3 after hitting "my image" under theme.
6. After extensive use, run a Burn in fixer even if you don't see the affects of burn in. As it changes the pixels that stayed the same for a long period of time. These work by flashing a variety of colors on your screen in semi-rapid succession. Which can also undo some minor burn in. The one I use is here (playstore link) . Run this for around 5-10 minutes before you go to sleep for example, or while you're doing something on your computer.
Hope this helps! This is what I use and I haven't yet gotten burn in on my Nexus 6P after extensive use day to day.
I've never had a problem with burn in on any OLED phone I've had and I've had many.
The most important thing for power savings is a dark theme.
Also, no burn in on my devices, but use a dark wallpaper, theme, etc....
This thread is pure dumbness...it's almost imposible to burn an amoled screen unless it remains lit and static one whole day...normal use will never burn the screen.
Enviado desde mi Nexus 6P mediante Tapatalk
Only poor quality OLED panels exhibit burn in. Except if you display a static image at full brightness for days non stop, something that doesn't happen in normal usage. If you are so paranoid then never buy an amoled phone. It's the same with the silly "battery friendly" battery tips for charging and quick charging. Use your phone like normal. This is why you bought it. It's a device that's built to last only few years and you will change it before major problems arise. That unless you have a very crappy made device.
My Nexus 6p has burn in, I can see the navigation and status bars burnt into the top and bottom. I attribute it to using navigation on long trips and Pokemon Go always needing the screen on. Just started noting it in the last month (got it in the initial preorders).
The app says its for LCD..?
My device has burn on the top and bottom of the screen pretty badly actually and I have the navigation bars hide them selves. I think the screen degrading.
Mines has burn on top and bottom
Sent from my Pixel XL using Tapatalk
This has always been a minor concern with any smart phone I've had, but can't say it's ever happened to me. I did however find a much better way to prevent this that works flawlessly on my [rooted] Nexus 6P. In one of the last few major android versions we got immersive mode (L methinks?), but it's not always accessible depending on phone/manufacturer (haven't seen an option on a stock ROM yet). I use Tasker to run root shell commands from notifications and found the following command a while back (source stack overflow or similar answer site via Google):
settings put global policy_control immersive.full=*
This will toggle full immersive mode. It persists across reboots and fits me perfectly as I enjoy the extra screen estate and I can just swipe from top/bottom to get those bars. Basically makes it like you are always in video mode. This only has to be run once, but I have a companion command to disable just in case:
settings put global policy_control null*
I figure if my normal apps are putting different designs and colors in those areas, I shouldn't have to ever worry about pixel burn in. Plus it's way better than crippling a devices usability with color inversion.
sevro said:
This has always been a minor concern with any smart phone I've had, but can't say it's ever happened to me. I did however find a much better way to prevent this that works flawlessly on my [rooted] Nexus 6P. In one of the last few major android versions we got immersive mode (L methinks?), but it's not always accessible depending on phone/manufacturer (haven't seen an option on a stock ROM yet). I use Tasker to run root shell commands from notifications and found the following command a while back (source stack overflow or similar answer site via Google):
settings put global policy_control immersive.full=*
This will toggle full immersive mode. It persists across reboots and fits me perfectly as I enjoy the extra screen estate and I can just swipe from top/bottom to get those bars. Basically makes it like you are always in video mode. This only has to be run once, but I have a companion command to disable just in case:
settings put global policy_control null*
I figure if my normal apps are putting different designs and colors in those areas, I shouldn't have to ever worry about pixel burn in. Plus it's way better than crippling a devices usability with color inversion.
Click to expand...
Click to collapse
MAN, THANK YOU!!!
THANKS!! :good::highfive:
sevro said:
This has always been a minor concern with any smart phone I've had, but can't say it's ever happened to me. I did however find a much better way to prevent this that works flawlessly on my [rooted] Nexus 6P. In one of the last few major android versions we got immersive mode (L methinks?), but it's not always accessible depending on phone/manufacturer (haven't seen an option on a stock ROM yet). I use Tasker to run root shell commands from notifications and found the following command a while back (source stack overflow or similar answer site via Google):
settings put global policy_control immersive.full=*
This will toggle full immersive mode. It persists across reboots and fits me perfectly as I enjoy the extra screen estate and I can just swipe from top/bottom to get those bars. Basically makes it like you are always in video mode. This only has to be run once, but I have a companion command to disable just in case:
settings put global policy_control null*
I figure if my normal apps are putting different designs and colors in those areas, I shouldn't have to ever worry about pixel burn in. Plus it's way better than crippling a devices usability with color inversion.
Click to expand...
Click to collapse
I had that for a while its baked into my rom but I found it annoying.
Riardon said:
Only poor quality OLED panels exhibit burn in.
Click to expand...
Click to collapse
That is not true. All OLED panels exhibit "burn in", it's the nature of the technology. It's not really burning in though but rather "burning out".
That being said, burn in during normal usage is very unlikely and pretty much impossible unless you use apps that keep the screen on with static picture or UI elements. The only thing that WILL "burn in " on any device, and is just a matter of time, is the status bar and nav bar. But they are both there almost always anyway so you won't even see it unless you decide to switch to pie controls down the road and turn the nav bar off.
As for OP, using a full black wallpaper would actually INCREASE chances of burn in but you don't spend that much time on homescreen for it to matter. Running any burn in "fixers" is absolutely unnecessary and is very unlikely to help once the pixels on your display do degrade unevenly. Basically the only thing you need to do to prevent it is to use common sense. Don't use higher brightness than necessary and don't (over)use apps that leave the screen on with static picture.
---------- Post added at 06:46 PM ---------- Previous post was at 06:38 PM ----------
sevro said:
This has always been a minor concern with any smart phone I've had, but can't say it's ever happened to me. I did however find a much better way to prevent this that works flawlessly on my [rooted] Nexus 6P. In one of the last few major android versions we got immersive mode (L methinks?), but it's not always accessible depending on phone/manufacturer (haven't seen an option on a stock ROM yet). I use Tasker to run root shell commands from notifications and found the following command a while back (source stack overflow or similar answer site via Google):
settings put global policy_control immersive.full=*
This will toggle full immersive mode. It persists across reboots and fits me perfectly as I enjoy the extra screen estate and I can just swipe from top/bottom to get those bars. Basically makes it like you are always in video mode. This only has to be run once, but I have a companion command to disable just in case:
settings put global policy_control null*
I figure if my normal apps are putting different designs and colors in those areas, I shouldn't have to ever worry about pixel burn in. Plus it's way better than crippling a devices usability with color inversion.
Click to expand...
Click to collapse
LMT launcher is your friend. Swiping up just to reveal the nav bar is too much of a hassle. With pie controls you can navigate with just one continuos swipe and you can configure it in any way you want. At first I did this to get back the screen space wasted by navbar but I've realized navigation is actually better than with the nav bar itself. It's also easier to do one handed because it can not only be activated from the bottom but from the sides as well. I urge anyone who dislikes the nav bar to try it. Works flawlessly and for those concerned, it prevents burn in as well.
Jockson said:
LMT launcher is your friend. Swiping up just to reveal the nav bar is too much of a hassle. With pie controls you can navigate with just one continuos swipe and you can configure it in any way you want. At first I did this to get back the screen space wasted by navbar but I've realized navigation is actually better than with the nav bar itself. It's also easier to do one handed because it can not only be activated from the bottom but from the sides as well. I urge anyone who dislikes the nav bar to try it. Works flawlessly and for those concerned, it prevents burn in as well.
Click to expand...
Click to collapse
I actually ran across LMT and used it before I found immersive mode. Extremely robust and customizable. However I use the swipe kinda like a "confirmation" that I want to navigate away. The swipe up and tap is almost second nature now
App switching screen on Android 12 is pretty bad. So easy to make mistakes, always unintentionally swiping down or up. I haven't used Android 11, not sure if they are same . Came from iOS.
I came from an lg v20 with android 8 on it and i prefer how it was done on there but with the new app switcher screen I have to say I love the easy screenshot, url sharing, and text selection on screens that are otherwise not text selectable so I guess that makes up for it.
What i dont like is the screen isnt very responsive to touch with my tempered glass screen protector unless I force 90hz in developer options. Speakers sound like crap compared to my v20 , and of course no easily removable battery, no microsd slot, no headphone jack and no ir remote sucks too but as far as I know there isnt a single good flagship phone out there that still has all those.
I only bought a new phone because the v20 became unbearably slow and good new batteries are hard to come by anymore, I also need it for developing AR apps.
nraudigy2 said:
App switching screen on Android 12 is pretty bad. So easy to make mistakes, always unintentionally swiping down or up. I haven't used Android 11, not sure if they are same . Came from iOS.
Click to expand...
Click to collapse
By default, they use a bunch of hideous gestures.
Go into System Settings --> Accessibility --> System controls, and change "System navigation" to "3-button navigation". That will give you three nice buttons on the bottom edge of the screen... back, home, and task switcher.
96carboard said:
By default, they use a bunch of hideous gestures.
Go into System Settings --> Accessibility --> System controls, and change "System navigation" to "3-button navigation". That will give you three nice buttons on the bottom edge of the screen... back, home, and task switcher.
Click to expand...
Click to collapse
Checked this out too, but you get the ancient Android 7-or-8 like buttons. Much rather see the Pixel 3's buttons placed on the bottom.
Although the gestures are a bit finicky, it took me a while to get used to, but now I've got it under control.
Its not about "ancient", its about EFFECTIVE. The 3-button menu bar is the only option that has ever existed that doesn't involve indecypherable/inconvenient gestures.
Helpmepleasekidnqpped said:
My wife was kidnapped and I have no idea how to get her GPS turned on. her phone find my device is off but she tried to share location with me
Click to expand...
Click to collapse
Call the police! They may require SIM card tracking from the operator! Or by IMEI of the device!
trabadura said:
Call the police! They may require SIM card tracking from the operator! Or by IMEI of the device!
Click to expand...
Click to collapse
I'm 99.99% positive that you replied to some kind of scammer. They created a profile to report this on a random forum? I reported the user, if there is any legitimacy, forum admin can sort that out and deal with it.
bebop707 said:
I came from an lg v20 with android 8 on it and i prefer how it was done on there but with the new app switcher screen I have to say I love the easy screenshot, url sharing, and text selection on screens that are otherwise not text selectable so I guess that makes up for it.
What i dont like is the screen isnt very responsive to touch with my tempered glass screen protector unless I force 90hz in developer options. Speakers sound like crap compared to my v20 , and of course no easily removable battery, no microsd slot, no headphone jack and no ir remote sucks too but as far as I know there isnt a single good flagship phone out there that still has all those.
I only bought a new phone because the v20 became unbearably slow and good new batteries are hard to come by anymore, I also need it for developing AR apps.
Click to expand...
Click to collapse
Welcome to 2021! Phones haven't had removable batteries for a while now...
dunno how your triggering app switching when swiping up and down considering you need to swipe from bottom of screen and hold it for a good second
basic gestures hard