This is exactly why you don't make a password super complicated to where you need a very unsecure method to remember it (such as a post-it note taped to the monitor like with our work PC)

There's secure passwords and then there's crazy passwords.

I would make sure to get a security suite that checks for any of your identity being on the dark web. I was getting tons of these scammer calls and after checking with one of those suites I had TONS of my data where it wasn't supposed to be, such as my phone number being on tons of lists, sold to tons of businesses many of whom probably deal with scammers.

Today, I never give my real phone number to a business. I'll give a fake one, or one that I no longer use, or even a made-up one like 555-2659 because if a company really wants to contact you, it will be via email, text, or their app. they NEVER call. Many sell the numbers to data collectors who sell it to the lowest common denominator. After removing my data from those lists, changing passwords, and changing the phone number that I had on sites such as Google Play, Microsoft and Amazon to a fake number, those calls are few and far between.

Back in the 1990s, there used to be a little gadget you could put on your landline called TeleZAP that would listen for specific codes that scammer call centers used (sounds, clicks, delays, etc) and if it detected a scammer, they'd hear a very high pitched ear rape sound. I don't know how successful it was, but I loved to imagine the image of them whipping their headset off in sheer discomfort over it. I often wanted to use an air horn against a few back in the day as well.

There are exceptions though, many times your phone number is a reused number that someone else had. I had a home phone once that apparently must have belonged to a grandparent, since it got tons of automated calls from medical groups, insurance companies, and one from a school system that basically is recorded propaganda known as OneCall. Sadly, any attempts to stop those failed since calling them back (these were local comanies as well) was met with a recording of "this number does not accept incoming calls' so I was forced to change the phone number. In these cases, the calls were specifically coming in at a specific hour, day of week. There was no way to get rid of them, since answering them only had recordings, not real people, nor a method to tell the automated system to go frell itself.

Fair enough - I don't mind being the exception. The Z Fold 5 is expected to be a small improvement over the 4, but rumors are already trickling that the Z Fold 6 will be a major change.

I would definitely miss this main display when writing on the go, as I can use Word and see the entire page. Still undecided and I'm sure I'd have some regret right after selling this one. I hope, for all of you, that the foldable phone doesn't end up like VR or even 3D TVs. We were in deep with both technologies and the plug got pulled on us.

%25 Discount Now Available !!

olbriar said:

I know nothing about an Android box. Does it have any aspect ration settings that you might adjust to force full screen?

Click to expand...

I haven't found any specific setting.
Researching about this issue, I found some apps supposed to force the execution of all apps in full screen/landscape, but it hasn't worked for me.

Today, I wanted to download some songs to re-create the 'nature rock' playlist that I use for my Saturday hikes in the woods. I had just gotten a Samsung A03s to replace a dying Samsung Galaxy S5, and so far love the new phone (first for me) but it had one major issue that caught me off guard.

First, Amazon Music downloaded the songs I wanted, but Samsung Music (preferred music player) couldn't see anything but the Over The Horizon song it comes with. I tried rebooting the phone, rescanning, and attempting to browse via My files to no avail. I also tried many other file manager apps (even my old standby, a spare APK of ES File Explorer 3.x from Android 2.3) but no dice. Apparently, Amazon changed the location of downloaded files, even including purchased MP3s. It took me a long time (try two hours) of messing around and then viewing random Reddit posts but they did something to Android 13 to really screw with my sanity.

Apparently, Amazon Music no longer saves under the 'com.amazonmp3' folder like it did since, like, 2011? It has changed to the 'Android/Data/com.amazon.mp3/purchased' folder, but as of Android 13, that folder is no longer viewable (Why Google?!). So the only 'official method' is to use Amazon Music to play the downloaded songs. Their app would work for that I figured, so since that 'Nature Rock' playlist is indeed backed up to Amazon cloud, it shows up in the app. I had downloaded it ahead of time planning on playing it today. Unfortunately, while when I downloaded it, it had 50 songs, today, when I chose to play it, it only had 7. Literally more than 3/4 my songs are gone. Trying to look at all the purchased songs, a good 50% now show up only accessible via 'Amazon Music Unlimited'.

Oh, hell no! No way. I cleared data from the app (we're on hour 3 now, I planned my hike at 10, now it's 1) and re-logged in. Now all my songs show up, even all the 50 in that playlist, only now I no longer trust the app to work when I expect it to, like say, next week, will it go back to 7 again? I need to find out how to get them to show up under Samsung Music. I own the damned songs, they're MP3s, they obviously downloaded since they take up space, but only Amazon can see them (until it 'forgets again')

I don't know what Android 13 borked, but I was able to use an app called 'FV File Explorer' that can see and copy from /Android/Data/* so I was able to use it to copy the music to the Music folder on my SD Card, and rebooting, now Samsung Music sees all of it. I recreated the playlist in Samsung Music, and after 5 literal hours of hair-pulling frustration, it's back to where it was on my S5. But this is exactly why I despise modern tech, modern software. It can make the simple act of playing offline, purchased MP3s a royal, headache inducing pain in the empennage. I don't know why they keep trying to fix what ain't broken. So far this is the only major issue with my new phone, and hopefully the last. It otherwise works fine despite it being low-end. I still have to plug in the Type-C cable in twice before it recognizes the charger, but that's a Type-C bug that will likely never get fixed (much like how loose it feels, not like the far more secure 'click' I got from Micro USB)

I'm on an A03S with the same version, but mine is now an empty speech bubble. I'd post it but USB Type-C won't play with Windows 7 (thinks my phone is a camera instead of a media device). The icon for the app is the same, but the notification is different.

It looks like I need to extend this class:
TrustAgentService.java

There is a comment in the code which says:

Trust agents may only be provided by the platform.

Click to expand...

Does that mean I can't write my own?

tenletters said:

I know what you're saying. I'm on a Samsung Note 20 Ultra. The pop up itself isn't a picture in the options I could even choose. The lockscreen is the "Dynamic Wallpapers" where it changes to a new picture every time I go to unlock the device. The homescreen is a static image (one from my gallery). I could trial and error a static image on the lockscreen moving forward?! Thanks for the response.

Brian706 said:

Is it possibly one of the included wallpapers on the device? Not sure which device you are on but on my phone if I long press the homescreen, I have an option to view pre installed wallpapers. Anyway, when I select a wallpaper, photo, solid color, etc. to set as wallpaper there is an option for homescreen, lock screen or both. Maybe you can do something similar and set your usual wallpaper as both or select something different for your lock screen?

Click to expand...

Click to expand...

This worked, or solved the inquiry at least. I disabled "Dynamic lockscreen wallpapers" and this image is the default image if I don't select ANY other wallpaper. I think it was flashing briefly when all the images selected to show in dynamic mode had been seen and it was starting the set over again...which happens to be about 30 different pictures. Finally, solved. Truly appreciate you taking the time to chime in and locate the issue!

new update dial img fixed

fangirlfants said:

Hi, did you fix it by any chance? i lost my phone and when i reinstalled whatsapp no backup was found in my google drive even though i'm sure i had one

Click to expand...

do you see the file in drive? if it is not there than you can't restore a backup if there is not one there.

which redmi note 9 do you have? the 4G version? what is your model number?

i do not have your phone and i see that there is a Redmi Note 9 and a Redmi Note 9 4G. just the note 9 can be upgraded to android 11 while the note 9 4G can be upgraded to android 12.

and as @Dannydet suggested updates will depend on your carrier and manufacturer. if you know your exact model of the phone, you can do a search and see if there is a firmware update available for your phone. keep in mind that firmware updates are very device specific and installing the wrong firmware can have seriously bad consequences.

AugieTN said:

Buddy of mine with a Verizon Pixel 6 said he got the April 2023 update last night

Click to expand...

I got mine last night too, finally!

Welcome to AF @Shirazi . I moved your thread here for better exposure and assistance.

Do this via Google Chrome for Android. Open a new tab. The search bar will appear. Search for the thing you're interested in. When the search returns click the three dots to the right of the search bar. Click add to home screen. Rename, drag and drop.
Enjoy!

Dannydet said:

Long press on the icon on your home screen and choose delete or move it to the top for removal. Then swipe up to bring up your app drawer, scroll to your messages app icon, long press on it and drag to your home screen.

Click to expand...

Yep, that is exactly what I did to fix it, prompted by the first response.

Data recovery is possible, and there are PC downloads that can do it. Hopefully OP will use the free Google Photos backup going forward (although I also backup to our NAS).

ocnbrze said:

you can use Tasker - Apps on Google Play and set times when the app can run.

Click to expand...

Omg! That sounds easy. Thank you...ch checking it now.

Android System - Charging connected device via USB - Tap for other USB options

I have had the same on a Galaxy Note 9 ... And think I have figured out why ...
This is an Android OS Issue ... Not Hardware Related !!!
The Phone has been connected to an extrrnal device (game controller, Flash Drive, Android Auto, or similar) and part of that connection was to change the USB Connection Defaults to suit that device. Reconnect the device and see if you get different options.

1. "AndroidAuto" was what changed the settings for me ... after I re-connected to AndroidAuto, and changed the preferences about auto-start and auto-play-music etc, the error message/notification went away.
2. My Phone charged again when cable was connected and I tapped the Notification "Android System - Charging connected device via USB - Tap for other USB options" and chose "This Phone" ... You MUST connect Charging Cable first, to get option for "This Phone"
Hope that helps ...
Beauvaidos

Jesus, can't it tell me which? "There's a problem" is not a valid message to give a user. Android can get lost next time I buy a phone. It's a piece of crap.

Weather Api Updated.

Hi sir, can i get gpt_main.bin from firmware i downloaded for my devices? I downloaded so many firmwares but there is no gpt files when i extract it.

I have to design something like this and add click event for each block, how should I proceed for that. Could anyone guide me regarding this
how to implement in android studio? like circular menu

Oh yes. My apologies. Here is the link...

Logisity - Apps on Google Play

Trying to start up a x86_64 based phone via the Android Studio Emulator, but it freezes at the white screen showing "Google". Here are the particulars:

1. Intel Core i7 chipset on the Mac
2. Android emulator uses API level 33
3. system image is from system-images/android-33/google-apis/x86_64

In Android Studio, when I hit the "run app" icon, as mentioned, it tries to start up the emulated phone, but freezes up.

I have tried --
1) installing intel-haxm driver via Mac "brew"
2) in Android Studio: "wipe data" on the emulator, then "cold boot" of the emulator but same problem.
3) tried at the command line: "emulator -avd Pixel_XL_API_33_x86_64", but again freezes at white screen.

A small portion of the (adb) logcat (excuse the ctrl-M's) shows:
--------- beginning of crash^M


04-27 12:29:20.046 450 480 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 480 (RenderEngine), pid 450 (surfaceflinger)^M


04-27 12:29:20.301 603 603 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***^M


04-27 12:29:20.301 603 603 F DEBUG : Build fingerprint: 'google/sdk_gphone64_x86_64/emu64x:13/TE1A.220922.012/9302419:userdebug/dev-keys'^M


04-27 12:29:20.301 603 603 F DEBUG : Revision: '0'^M


04-27 12:29:20.301 603 603 F DEBUG : ABI: 'x86_64'^M


04-27 12:29:20.301 603 603 F DEBUG : Timestamp: 2023-04-27 12:29:20.132342416-0600^M


04-27 12:29:20.301 603 603 F DEBUG : Process uptime: 6s^M


04-27 12:29:20.301 603 603 F DEBUG : Cmdline: /system/bin/surfaceflinger^M


04-27 12:29:20.301 603 603 F DEBUG : pid: 450, tid: 480, name: RenderEngine >>> /system/bin/surfaceflinger <<<^M


04-27 12:29:20.301 603 603 F DEBUG : uid: 1000^M


04-27 12:29:20.301 603 603 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------^M


04-27 12:29:20.301 603 603 F DEBUG : Abort message: 'Unable to generate SkImage. isTextureValid:1 dataspace:513'^M


04-27 12:29:20.301 603 603 F DEBUG : rax 0000000000000000 rbx 00000000000001c2 rcx 000075020db346ff rdx 0000000000000006^M


04-27 12:29:20.301 603 603 F DEBUG : r8 000074ff79a18660 r9 000074ff79a18660 r10 000074ff79a184c0 r11 0000000000000207^M


04-27 12:29:20.301 603 603 F DEBUG : r12 000000000000000d r13 0000750059e203b0 r14 000074ff79a184b8 r15 00000000000001e0^M


04-27 12:29:20.301 603 603 F DEBUG : rdi 00000000000001c2 rsi 00000000000001e0^M


04-27 12:29:20.301 603 603 F DEBUG : rbp 0000750029e22c28 rsp 000074ff79a184b0 rip 000075020db346ff^M


04-27 12:29:20.301 603 603 F DEBUG : backtrace:^M


04-27 12:29:20.301 603 603 F DEBUG : #00 pc 000000000005f6ff /apex/com.android.runtime/lib64/bionic/libc.so (abort+191) (BuildId: 007cb2313464df63debf8020e631c990)^M


04-27 12:29:20.301 603 603 F DEBUG : #01 pc 000000000000abba /system/lib64/liblog.so (__android_log_default_aborter+10) (BuildId: 6b5490b5683793c72167e11556e0b7d9)^M


04-27 12:29:20.301 603 603 F DEBUG : #02 pc 0000000000008712 /system/lib64/liblog.so (__android_log_assert+338) (BuildId: 6b5490b5683793c72167e11556e0b7d9)^M


04-27 12:29:20.301 603 603 F DEBUG : #03 pc 00000000001ef207 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::drawLayersInternal(std::__1::shared_ptr<std::__1:romise<android::renderengine::RenderEngineResult> > const&&, android::renderengine:isplaySettings const&, std::__1::vector<android::renderengine::LayerSettings, std::__1::allocator<android::renderengine::LayerSettings> > const&, std::__1::shared_ptr<android::renderengine::ExternalTexture> const&, bool, android::base::unique_fd_impl<android::base:efaultCloser>&&)+23335) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #04 pc 00000000005ead7c /system/bin/surfaceflinger (android::renderengine::RenderEngine::drawLayers(android::renderengine:isplaySettings const&, std::__1::vector<android::renderengine::LayerSettings, std::__1::allocator<android::renderengine::LayerSettings> > const&, std::__1::shared_ptr<android::renderengine::ExternalTexture> const&, bool, android::base::unique_fd_impl<android::base:efaultCloser>&&)+124) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #05 pc 00000000006023d8 /system/bin/surfaceflinger (android::renderengine::skia::drawImageLayers(android::renderengine::skia::SkiaRenderEngine*, android::renderengine:isplaySettings const&, std::__1::shared_ptr<android::renderengine::ExternalTexture> const&, std::__1::shared_ptr<android::renderengine::ExternalTexture> const&) (.__uniq.148735152540075350775156443829291153399)+760) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #06 pc 0000000000600a38 /system/bin/surfaceflinger (android::renderengine::skia::Cache:rimeShaderCache(android::renderengine::skia::SkiaRenderEngine*)+1720) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #07 pc 00000000005fc1db /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine:rimeCache()+11) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #08 pc 00000000005fb2dd /system/bin/surfaceflinger (android::renderengine::threaded::RenderEngineThreaded:rimeCache()::$_3:perator()(android::renderengine::RenderEngine&) const (.__uniq.64102821644698991011622682901256404626)+93) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #09 pc 0000000000251e8c /system/bin/surfaceflinger (android::renderengine::threaded::RenderEngineThreaded::threadMain(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>)+700) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #10 pc 0000000000351be5 /system/bin/surfaceflinger (decltype(*(std::__1::forward<perfetto::base::ThreadTaskRunner*>(fp0)).*fp(std::__1::forward<std::__1::function<void (perfetto::base::UnixTaskRunner*)> >(fp1))) std::__1::__invoke<void (perfetto::base::ThreadTaskRunner::*)(std::__1::function<void (perfetto::base::UnixTaskRunner*)>), perfetto::base::ThreadTaskRunner*, std::__1::function<void (perfetto::base::UnixTaskRunner*)>, void>(void (perfetto::base::ThreadTaskRunner::*&&)(std::__1::function<void (perfetto::base::UnixTaskRunner*)>), perfetto::base::ThreadTaskRunner*&&, std::__1::function<void (perfetto::base::UnixTaskRunner*)>&&)+85) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #11 pc 00000000005fb059 /system/bin/surfaceflinger (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (android::renderengine::threaded::RenderEngineThreaded::*)(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>), android::renderengine::threaded::RenderEngineThreaded*, std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()> > >(void*)+73) (BuildId: caf11998e449c0913886496d851f3e37)^M


04-27 12:29:20.302 603 603 F DEBUG : #12 pc 00000000000ccd2a /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+58) (BuildId: 007cb2313464df63debf8020e631c990)^M


04-27 12:29:20.302 603 603 F DEBUG : #13 pc 0000000000060d37 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+55) (BuildId: 007cb2313464df63debf8020e631c990)^M


04-27 12:29:23.096 637 656 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 656 (RenderEngine), pid 637 (surfaceflinger)

Of note to me in this log portion--

(1) I do not see /system/bin/surfaceflinger on my Mac
(2) Abort message: 'Unable to generate SkImage. isTextureValid:1 dataspace:513' - this sounds important. Is it?

Pls let me know how one can get around this issue of the emulated phone freezing up.

And definitely, if I am asking on the wrong forum, pls let me know and I will direct this question elsewhere. Thx.