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.

JeffreyCaiden said:

Open the Spotify and Tunein Radio apps, and look for any settings related to Bluetooth auto-play or auto-start. Disable these settings if they are turned on.
Thanks

Click to expand...

Tune-IN has a selection "Autoplay" with description "Turn ON to resume your last stream when tune In launches" and this is deselected. Few other chocies are enable and nothing seems to apply.

Nothing on Spotify setting seems to be appropriate.


Thanks!

..Tom

ocnbrze said:

No worries. Come back and tell us which one you ended up with and why you like it.

Click to expand...

I've decided to go with Mobicip "Lite" version. It seems there are a couple of good free ones out there, such as Kaspersky Safe Kids and Google Family Link, but they are not compatible with Amazon Fire. I'm primarily concerned with web/app filtering and blocking, and Mobicip "Lite" for $2.99 per month seems to fit the bill.

Hi, thank you and appreciate your timely reply. But i didn't updated any app or software etc

could well be right.

annoying in the mean time..

slunsford911 said:

okay I have a tough book as well have you tried the offline maps downloaded and using the windows 10 maps app that's what I use for offline navigation in tablet mode and you can your chrome with a maps extension to bring up google maps just make sure your Toughbook has the GPS device installed

Click to expand...

That's what I do now, but I want access to OnX and TrailsOffroad because they have way superior maps for boondocking.

How is pregnancy similar to success?

Everyone congratulates you, but no one knows how many times you were screwed in the process.

SMAUG117 said:

Pc game

Click to expand...

so not your game? why did you post this? is it a good game? never heard of it? what are the system requirements?

AugieTN said:

I hope you don't plan on beta testing with your primary phone.

Click to expand...

I have two phones, nothing is a problem to me. I can swap out numbers.

Hi Mike,
Oh no!! I'm washing my hands right now, and reaching for the isopropanol💩.
..... john

The only thing I can think of is trying a USB headset or a Bluetooth headset.

Could help me out to delete parental advisory explicit content the curse want to delete. Please could assistance with your help , please the youtube advance . Please do better update system to show picture. Rest assured you handle this . First am I haven't problem with this one. Please delete avatar icon user, could took search how delete the icon user. Fix youtube advance please

mikedt said:

Is the A52 an Android Go device? From what I've read about it on AF, Android Go is a cut-down lite version of Android for lower-performance phones. And so apparently doesn't have all the features and functiions of full Android. This is what I've read, and have never seen or used an Android Go device myself.

Click to expand...

None of Samsung's A-series phones are Go devices. Not even the most crappy budget model they make. They're all OneUI running on top of full Android, even on devices with only 2GB of RAM. At best they cut some specific Samsung gimmicks out to make up for the lesser hardware/price, but hey, it's one way to get rid of Bixby--she don't exist on A-series. At this point in time, I don't think Samsung makes an Android Go device.

The only Go stuff are very garbage-tier phones like the AT&T "Calypso" or the Alcatel "Onetouch POP"

For the record, the A52/A53 are upper-mid-tier, aka, AMOLED displays, decent cameras, 90/120Hz refresh rates, and expandable storage and a headphone jack. They're one step or two below a flagship.

A-series designation is confusing to most, and is a mess of various redundant models but the basis for the model number is:

AXY where X is the tier (beginning at 0 for lowest, higher # for better) and Y is the generation. Aka, the Samsung A52 is the middle tier, second generation. The highest end A-series is in the A7x range.