What do you do with our feedback? Can we see what we sent in so far to Google?

[BugMeNot]

Tesco shopping:"""
Köszönöm!

Egy apró észrevétel: Legközelebb nem SMS-ben kérem a futár-követő hivatkozás elérhetőségéről az értesítést, ugyanis csak régi telefonom van, ami nem "okos". Számítógépen tudom csak követni, ami e-mail-t jelent, hogy rá tudjak kattintani. Pl:

_DODO | Order tracking_

Kézzel kellett beírnom, hogy "t.idodo.group/CANMU13U" az sms alapján.
"""

[3ICE]

in Google play games, "Soid app" is the wrong name for farm heroes saga. it gets displayed erroneously.

[3ICE]

Samsung Gaming Hub

Subject: Several game shortcuts lost forever after gaming hub mishap. Disabling it, enabling it, changing shortcut settings from show in game hub only to both have no effect. My games are searchable still, but locate app fails to work on them
Details:
1) OS version: I have auto update enabled...
2) Access type: what access?
3) Description of error: see subject line

[BugMeNot]

3ICE » Reviews » Rush Bros
This review has been automatically flagged for containing potentially harmful content and the review text has been hidden as a result.

5 people found this review helpful
1 person found this review funny

Not Recommended
0.0 hrs last two weeks / 1.2 hrs on record
Posted: 25 Apr, 2022 @ 7:28pm
Updated: 8 Aug @ 1:15am

wtf is this: "This review has been banned by a Steam moderator for violating the Steam Terms of Service. It cannot be modified by the reviewer."
7 Comments

3ICE Just now
I wonder what my original review said... Probably links to my website, 3ice.hu (I only use it for hosting images so idk whats their problem)

3ICE 4 minutes ago
There was an error trying to process your request: 15

3ICE 5 minutes ago
I absolutely CAN edit it by the way. just has to go through "This review is awaiting analysis by our automated content check system. It will be temporarily hidden until we verify that it does not contain harmful content (e.g. links to websites that attempt to steal information)."

3ICE 6 minutes ago
wtf they replaced my review with this text: "This review has been banned by a Steam moderator for violating the Steam Terms of Service. It cannot be modified by the reviewer."

olaf 29 Jul @ 1:25am
now I am not sure if it is bait or not :csd2huh:

3ICE 25 Apr, 2022 @ 7:52pm
Your review is currently marked as publicly visible. You can edit this review, change your rating, and change the visibility setting if you wish. View your review

[3ICE]

Samsung finally replied. But they just canned text spammed the "not my department" button at my general direction. They at least quoted my inquiry back at me.
2025-07-28T10:37:51Z[Etc/UTC]
---
And it's a noreply address? Insulting. I wrote back anyway:
Cannot read this tiny as font. Optimize your email for phones!

Also forcing me to scroll left and right instead of letting text flow naturally and break at the end of lines automatically...

Is just awful UX.

Screenshot_20250811_153426_Gmail.png (131.09 KiB) Viewed 304223 times

Sincerely,
Daniel 3ICE Berezvai

Looks like tiny ants from up here...

[3ICE]

GeForce now:
Any network lag causes me to continue to walk forward helplessly info enemy fire. No way to stop movement. I see it happen in good detail, but no response to my inputs. Probably upload speed drops to 0 but download is still good. So I can watch myself die in high quality.

[3ICE]

Screenshot_20250811_153426_Gmail.png
Looks like tiny ants from up here...

Holy duck there's 126 thousand views on this image already. I'm probably getting ddos attacked like crazy. But my web host don't care about puny numbers in the hundred thousand range. Try a billion!

Although I did get an error:
429 Too Many Requests
The user has sent too many requests in a given amount of time.

[BugMeNot]

Google play store

Why start an update you can't finish
Why make me uninstall apps that aren't even taking up storage space
Why archive apps I used recently
Why move apps to the SD card again after each update

[BugMeNot]

Google play store
Don't attempt the update if there's no room for it. Better yet, stop this stupid shuffle: if an app is moved to my SD card, you pointlessly move it back to internal storage, update it, and then move it again to the SD card. Needlessly slowing my phone right down in the process.

[3ICE]

Why the Android Search Engine Selector Wouldn't Appear (And How a Missing Permission Was the Key)
I noticed it was missing key permissions... I chose to give it notification permissions and try another reboot.
Problem solved. On this reboot the app was finally able to fulfill its purpose; ask me for browser and search engine preferences and show me the legally required bunch of Google competition (that uses Google crawler data anyway) and chrome alternatives (that are chrome based themselves)

AI response:
Your discovery about the Notification permission is actually a very important insight for troubleshooting this specific system feature, especially since Android 13 (which the A14 runs) and later versions introduced stricter rules for notifications:
​Android 13+ Notification Model: System apps (like the Search Engine Selector) and all other apps now must explicitly ask the user for the POST_NOTIFICATION permission before they can display notifications (like the "Choose your search engine" prompt).
​The Vicious Cycle: Without that permission, the system component (the "Search engine selector") couldn't actually notify you or initiate the selection screen process, so it just kept running, waiting for the necessary condition (the permission) to be met to start the selection process.
​You were absolutely right about the nature of the selection screen as well. This feature is part of the compliance measures (like those required under the EU's Digital Markets Act - DMA) imposed on "gatekeepers" like Google to ensure competition. It mandates that users be given a choice of different search engines and browsers.
​Thanks for sharing that fix—it will be very helpful for other Samsung A14 (and similar modern Android device) users who encounter the same persistent background process issue!
​Would you like me to search for any information about the different search engines or browsers that were presented in the choice screen?

Blog post:
​For many Android users in Europe, the launch of a new phone or a major system update brings an unavoidable screen: the Search Engine Selector (often implemented to comply with regulations like the EU's Digital Markets Act). This screen is supposed to give you a choice of default browser and search engine.
​However, after a new setup on my Samsung A14, that screen simply refused to show up. The system component responsible seemed to be running, but the prompt itself was missing, preventing the official process from completing.
​After a lot of frustrating reboots and false starts, the solution was surprisingly simple—and reveals an important, subtle change in modern Android security

Problem: A Phantom Selector
​My new phone was ready to go, but the mandatory choice screen never materialized. The system app responsible for the selector was clearly waiting for something, but it just wouldn't trigger.
​I tried common fixes like clearing cache and restarting, but the selection screen remained locked away. The entire process was essentially stuck in a holding pattern.

Breakthrough: The Missing Notification Permission
​The key to the solution lay in a deep dive into the permissions for the specific system app responsible for the selector. I found that this core system application was missing a crucial permission: Notification Access.
​On a modern Android version (Android 13 and later, which the A14 runs), all apps, even system components, must now explicitly have the POST_NOTIFICATION permission before they can send a notification to the user.
​The Vicious Cycle: The Search Engine Selector is meant to notify the user and display the selection prompt (which is technically a type of notification or system overlay). Without the permission to notify me, the app couldn't do its job, so it just sat there, waiting for a condition that was never met.
​Granting this single, missing permission was the fix. After a final reboot, the selector screen immediately appeared, allowing me to make my choices and finally complete the setup.

Solution: A Quick Fix
​If you are experiencing a similar issue where the search engine or browser selector screen is missing or stuck, here is the quick troubleshooting fix that worked:
​Go to Settings: Open your phone's main Settings application.
​Navigate to Apps: Find and tap on Apps (or Applications).
​Show System Apps: You need to find the core system component. On most devices, you may need to tap the three-dot menu (or a filter icon) and select Show system apps or Show system services.
​Find the Selector App: Search the list for a component with a name related to search or browser selection. (The name can vary by manufacturer and update, but look for anything related to "Choice," "Selector," or "Browser.")
​Check Permissions: Tap on the identified system app and go to its App info page.
​Grant Notification Permission: Look for a section like Permissions or Notifications. If you see a toggle or setting that indicates notifications are disallowed, turn this permission ON.
​Reboot: Restart your device. The system app should now be able to run and display the necessary prompt upon startup.

Conclusion
​It’s a great example of how modern OS security—specifically the move to a stricter, explicit notification model in Android 13+—can unintentionally break critical system functions if the necessary permissions aren't properly configured during the initial setup.
​For me, granting that single Notification permission was the key to unlocking the functionality and finally moving past that annoying, invisible bug. If this solution worked for you, let me know in the comments!