Dodgy settings/attempted hack?

Lost

Well-known member
Likes
79
Location
Spain
Repeatedly keeps flashing up...

Should I be worried?
Anyone else got/getting this?

Reads as "Sorry, the com.android.settings program has an error. Normal, collecting logs, about to exit"

20251011_142805.jpg
 
I have the same since I've got an replacement Arkenstone two weeks ago. So far I'm just ignoring it since i use the phone as little as possible anyway (now it's usually turned off in a box somewhere) and I use SVAG on my personal phone instead.

Michael
 
So never on the previous device?

It's very strange. Had my bike since beginning of April, never had anything like this until today...
 
Well i imagine it still is a Chinese phone so could be ''normal'' behavior for that type of phone.

Still don't like the whole phone as a dashboard thing.
 
Stark says to me that don’t worry about this error. It did not affect the use of the motorbike.
Agreed that it doesn't affect the bike (so far).

What bothers me, it's that a third party seems to be collecting "logs" without my agreement.

I expect Stark (and encourage them) to collect information themselves, as this helps improve the bikes over time, but this is odd.
 
Agreed that it doesn't affect the bike (so far).

What bothers me, it's that a third party seems to be collecting "logs" without my agreement.

I expect Stark (and encourage them) to collect information themselves, as this helps improve the bikes over time, but this is odd.
All phone providers throughout the entirety of the foodchain from hardware, operating system, and applications collect logs (which vary in their intrusion/privacy level). And the communication systems have been doing this for a long long time. I am not saying I like it but we pretty much agree to this by signing onto any utility/communication system.
 
View attachment 14902

This is the Waze symbol, a popular map application Driving directions, live traffic & road conditions updates - Waze - doesn't look sinister.
Likely is running in the background and crashing, thus collecting debug logs.

You might be able to deactivate 'running in background' for Waze in the Android settings or uninstall it entirely.
Ha ha, it does look like that! I added Waze day one. The "error log" is separate (and comes up regardless on app/page).
 
I seem to have fixed it. Read in another thread here, that resetting the phone to factory settings helped with some Bluetooth issues. So I wiped everything off the phone and started from scratch with doing a full reset to factory defaults. Only thing I did different this time was to log into my Google account right away when prompted at the initial install. Last time I delayed the Google log in until after the install. Once everything was done the Stark app did its update and connected to the Varg without any issues. Haven't had the error msgs in question since!

Michael
 
I seem to have fixed it. Read in another thread here, that resetting the phone to factory settings helped with some Bluetooth issues. So I wiped everything off the phone and started from scratch with doing a full reset to factory defaults. Only thing I did different this time was to log into my Google account right away when prompted at the initial install. Last time I delayed the Google log in until after the install. Once everything was done the Stark app did its update and connected to the Varg without any issues. Haven't had the error msgs in question since!

Michael
Glad that's worked for you.
 
It seems that it could be more serious...

I emailed "support" with a picture of the issue and an explanation of what was happening.
Got a message back saying they tried to remote in but bikes firmware was out of date, and to update.

Checked my bike and it's at 1.2.8. Went through the steps to update anyway, but no update found....

Messaged back explaining this, and was told to try updating again as they tried remoting in again and the was bike was showing update 0.0.0. (Wouldn't that be a bricked bike?)

Took a picture of the update to confirm to them and straight up asked if this is a data breach?

It's been total radio silence from them since. Even after repeated requests for updates. Even offering to bring the bike straight to the factory. Nothing.

As a result I'd suggest anyone who's getting this message to contact Stark.
 
But the bike is running, isn't it? Anything you'd loose doing a factory reset on the phone, it is just 15-20minutes max.

Michael
 
I've seen this a few time recently on my EX. Seems to be when the phone is connecting via bluetooth after i bring it back to the bike after several hours away from it.
 
I've seen this a few time recently on my EX. Seems to be when the phone is connecting via bluetooth after i bring it back to the bike after several hours away from it.
Weird isn't it?

If it was after the last update I'd be less concerned, but that was back in July?

Why is it a thing now?
 
The EX phone is produced by a Chinese company Shenzhen Emdoor Information Co., Ltd. and Stark uses their MDM (Mobile Device Management) service to manage the OS version and I assume other device config. It's not too surprising you'd see notifications in Chinese as most of the internal services on the phone would be managed by Emdoor. It's unlikely Stark would know much more than that.

It seems that it could be more serious...

I emailed "support" with a picture of the issue and an explanation of what was happening.
Got a message back saying they tried to remote in but bikes firmware was out of date, and to update.

Checked my bike and it's at 1.2.8. Went through the steps to update anyway, but no update found....

Messaged back explaining this, and was told to try updating again as they tried remoting in again and the was bike was showing update 0.0.0. (Wouldn't that be a bricked bike?)

Took a picture of the update to confirm to them and straight up asked if this is a data breach?

It's been total radio silence from them since. Even after repeated requests for updates. Even offering to bring the bike straight to the factory. Nothing.

As a result I'd suggest anyone who's getting this message to contact Stark.
1.2.8 is the latest and unless Stark is maybe implying you have a corrupt firmware version there wouldn't be a way to update (and obviously 0.0.0 is nonsense so it seems more likely whoever your talking to at Stark is clueless).
 
Back
Top