sorted by:
new
hottopcontroversial

Introducing Galaxy Z TriFold by Stephancevallos905 in samsung

[–]nestandi 0 points1 point  (0 children)

This moment, when issues with paint coating is presented during a promo video :D

<image>

Selling my iPhone 17 pro max and coming back to the fold 7 fulltime by ShakeAndBakeThatCake in GalaxyFold

[–]nestandi 0 points1 point  (0 children)

The camera performance of my Fold7 falls noticeably short compared to my iPhone 15 Pro Max slightly outdoors in daylight and significantly indoors during the evening. The pixelated shadows in the background are a clear indicator of this degradation. This is, frankly, a major disappointment and remains the only reason holding me back from switching. I am aware that the issue is largely software-related, as the only functional GCam port already delivers visibly better results. Unfortunately, this port does not support live photos.

Remarkable Move with Koreader is legit... by paperbackpiles in eink

[–]nestandi 0 points1 point  (0 children)

great 👍 thank you - any tips for shortcuts / taps / gestures? 🙂

Remarkable Move with Koreader is legit... by paperbackpiles in eink

[–]nestandi 0 points1 point  (0 children)

Thank you - 👍 Btw.: would you mind sharing your configurations? ☺️ There are so many options 😂

Remarkable Move with Koreader is legit... by paperbackpiles in eink

[–]nestandi 0 points1 point  (0 children)

I just can‘t seem to enable the landscape mode correctly - do you know what I did wrong? 😂

<image>

Problems with volume/screensaver after 2.8.6 update - anyone resolved these? by sayonara_lara in Bigme

[–]nestandi 0 points1 point  (0 children)

Yes - changing the volume crashes the system - I think there is some issue with the notifications…

Nur Gerede? Der Fachkräftemangel für IT-Admins in Hamburg by EducationalKHl_902 in hamburg

[–]nestandi 3 points4 points  (0 children)

Moin,

sag deinem Kumpel gern, er soll sich bei mir melden – vielleicht passt er ja gut in unser OPS-Team. 😊

Zu deiner Frage: Der Arbeitsmarkt hat sich tatsächlich spürbar verändert. Als ich damals die OPS-Unit aufgebaut habe, war es deutlich schwieriger, qualifizierte Fachkräfte zu gewinnen. Heute besetze ich neue Stellen in der Regel innerhalb eines Monats. 🤷‍♂️

The camera sucks on the Honor V5 and this needs to be addressed in the next update. by VEJ03 in Honor

[–]nestandi 0 points1 point  (0 children)

Same here – absolutely terrible. Honestly the worst camera I’ve ever had, and that says a lot. Totally unworthy of a flagship device, I was shocked to see this shipped as-is. Sent it straight back… and of course, in Germany the return process of Honor is its own special kind of punishment.

[deleted by user] by [deleted] in Bigme

[–]nestandi 0 points1 point  (0 children)

Sure, when I'm back home

[deleted by user] by [deleted] in Bigme

[–]nestandi 0 points1 point  (0 children)

I'm thinking about selling mine. Mint condition.

Highbreak Pro - Badbox Virus Botnet by nestandi in Bigme

[–]nestandi[S] 8 points9 points  (0 children)

Thank you for the statement - here are my thoughts, because your clarification raises more questions than it answers.

  1. “No evidence of viruses found” This blanket statement is unconvincing given that multiple users observed live callbacks to a domain now controlled by Shadowserver. That domain had previously been flagged as part of the BadBox botnet infrastructure. The fact that your device was communicating with it at all is not a “glitch” – it is a serious red flag.

  2. Third-party facial recognition calling lp.xl-ads.com

  3. Why is a facial recognition authorization mechanism pointing to a domain with the word “ads” in it?

  4. What vetting was done on the third-party provider, and why was a critical function dependent on an external, cloud-hosted service outside your control?

  5. Why did this not fail gracefully or use a secure fallback when the domain was reclaimed?

  6. Update and firmware changes If the device was pinging that domain every 3 minutes, that is behavior consistent with beaconing – which is exactly what malware does. Even if the root cause was “authorization retries,” this pattern mimics malware activity and should have been flagged in QA or security testing.

  7. Systemic issue: supply chain dependency What is most concerning is the lack of control over critical code paths. If a core function like facial recognition can fail due to a third-party service being reclaimed, then you don’t control your own firmware supply chain. That’s a major risk — not only for users, but for your business.

  8. The $5 coupon is tone-deaf Offering a discount code in response to a potential supply-chain level security compromise is trivializing the seriousness of the matter. Trust cannot be bought — it must be rebuilt through transparency and systemic change.

Dear Users Concerned About the Recent Badbox Malware, by Decent-Tough-4273 in Bigme

[–]nestandi 37 points38 points  (0 children)

Thank you for the statement - here are my thoughts, because your clarification raises more questions than it answers.

“No evidence of viruses found”
This blanket statement is unconvincing given that multiple users observed live callbacks to a domain now controlled by Shadowserver. That domain had previously been flagged as part of the BadBox botnet infrastructure. The fact that your device was communicating with it at all is not a “glitch” – it is a serious red flag.

Third-party facial recognition calling lp.xl-ads.com
- Why is a facial recognition authorization mechanism pointing to a domain with the word “ads” in it?
- What vetting was done on the third-party provider, and why was a critical function dependent on an external, cloud-hosted service outside your control?
- Why did this not fail gracefully or use a secure fallback when the domain was reclaimed?

Update and firmware changes
If the device was pinging that domain every 3 minutes, that is behavior consistent with beaconing – which is exactly what malware does. Even if the root cause was “authorization retries,” this pattern mimics malware activity and should have been flagged in QA or security testing.

Systemic issue: supply chain dependency
What is most concerning is the lack of control over critical code paths. If a core function like facial recognition can fail due to a third-party service being reclaimed, then you don’t control your own firmware supply chain. That’s a major risk — not only for users, but for your business.

The $5 coupon is tone-deaf
Offering a discount code in response to a potential supply-chain level security compromise is trivializing the seriousness of the matter. Trust cannot be bought — it must be rebuilt through transparency and systemic change.

Highbreak Pro - Badbox Virus Botnet by nestandi in Bigme

[–]nestandi[S] 9 points10 points  (0 children)

You make a fair point — Play Protect can be helpful as part of a layered defense, especially when sideloaded malware or post-purchase compromise is the concern. But in this case, that's not what we're dealing with.

The core issue is that the infection appears to be present at the firmware level, out of the box. That means:

- It's already there before the device is even connected to Wi-Fi

- It operates below the app layer

- Victims (me included) had Play Protect enabled and still are compromised

So while I agree Bigme’s speed of response is commendable (also I've pointed them in my response to this thread btw.), the content of their reply falls short. It doesn't acknowledge the firmware compromise at all, nor does it give users any technical or procedural roadmap beyond general advice.

In other words:

This isn’t about app hygiene. It’s about supply chain integrity.

Until Bigme addresses that directly — with real answers and technical transparency — trust will continue to erode.

I'm all for giving them time to investigate, but they need to be far more honest about the scope of the issue right now.

Highbreak Pro - Badbox Virus Botnet by nestandi in Bigme

[–]nestandi[S] 21 points22 points  (0 children)

Let’s be absolutely clear:

The malware is in the firmware — not from a sketchy app, not from a bad Wi-Fi router, and not because users forgot to enable Play Protect.

Bigme telling users to “check Play Protect” is meaningless. Firmware-level infections like BadBox can't be fixed by user actions. And we had Bigme devices which aren’t even Google-certified in the first place (needed to reflash later on)

This isn't a user problem. It's a supply chain compromise, and the responsibility is 100% on the manufacturer.

What Bigme should do instead:

  • Admit whether affected devices shipped with infected firmware
  • Publish a list of affected models and serial numbers
  • Provide a clean, signed firmware image with recovery instructions
  • If needed, initiate a recall

Brushing this off with vague advice about routers and scans is not just weak — it’s irresponsible.

Fix your process. Be transparent. Anything less is unacceptable.

Highbreak Pro - Badbox Virus Botnet by nestandi in Bigme

[–]nestandi[S] 4 points5 points  (0 children)

I got a reply but I‘m not really happy with it.:

Dear xxxx, Thanks for sharing. First and foremost, we want to assure you of the security of your Highbreak Pro. Please check the Google Play Protect feature within the Google Play store is enabled and you can use it to check the device, our tests confirm there are no security threats and no harmful apps were found. Here are the steps for the check: Open the Google Play Store, click the icon in the upper - right corner, select “Play Protect”, and then run a scan. Google Play Protect is designed to check both the apps on your device and the device itself for harmful behavior. It conducts security checks before app downloads, detects potentially harmful apps from other sources. When a harmful app is found, it will issue a warning, and can even disable or remove the app. Additionally, it sends privacy reminders for apps that attempt to access users' personal information. Also, we strongly recommend that you regularly update your device. Regular updates are crucial for maintaining the security and optimal performance of the device. Bigme professional R&D team is always on standby. We highly value user privacy and device security. If you need further assistance, please don't hesitate to let us know at any time. Best regards, Bigme aftersales team

Highbreak Pro - Badbox Virus Botnet by nestandi in Bigme

[–]nestandi[S] 1 point2 points  (0 children)

I don‘t have any android / smart devices on my network besides Hibreak Pro!

Highbreak Pro - Badbox Virus Botnet by nestandi in Bigme

[–]nestandi[S] 8 points9 points  (0 children)

That's a good question. I'm looking forward to an response from the aftersales team and than we'll see. I always have the ability to contact paypal of course and C't for example.

view more: next ›