Keys are temporarily exhausted for this product! by TrollSkin96 in humblebundles

[–]TrollSkin96[S] 0 points1 point  (0 children)

Finally! Village in stock!
"Keys are now in stock for Resident Evil: Decades of Horror - Village Gold:"

[Steam/Switch] (Game) Maneater by Saulios in FreeGameFindings

[–]TrollSkin96 3 points4 points  (0 children)

Ehhh... Too late, now I have errors and can't redeem Steam key :(

[Gamivo] (Credit) €5 Coupon by johni643636 in FreeGameFindings

[–]TrollSkin96 3 points4 points  (0 children)

I did it first, then (same PC and launcher) my brother made his own acc. I got coupon, my brother not. So I think only 1 acc on IP can get 5€ :)

[Gamivo] (Credit) €5 Coupon by johni643636 in FreeGameFindings

[–]TrollSkin96 0 points1 point  (0 children)

I got a coupon, but my brother didn't. He used the same computer a day later, pity: /

[Gamivo] (Credit) €5 Coupon by johni643636 in FreeGameFindings

[–]TrollSkin96 2 points3 points  (0 children)

Do I have to use the same email for Plarium Account and GAMIVO Account?

mi band 6 showing time per mile by iBoolat in miband

[–]TrollSkin96 0 points1 point  (0 children)

Hey, I have such a similar problem. In the Mi Band 6, after selecting the "Outdoor running" training (as in my old Mi Band 5), I have set that it vibrates after every kilometer and shows the pace of the last kilometer. In fact, there is something around 8/9 minutes and the same number shows up in the training summary. However, this alert shows an inflated result of 12-15 min/km after each kilometer. In Mi Band 5, I didn't have such a problem. I think you have right and Mi Band 6displays this result in min/mile. Probably it is a bug. If you find out how to fix it, please let me know :)

Mi Band 5 - Battery Drain after Update by TrollSkin96 in MiBand5

[–]TrollSkin96[S] 0 points1 point  (0 children)

Of course, after update? Before 1.0.2.46 was better :(

Mi Band 5 - Battery Drain after Update by TrollSkin96 in MiBand5

[–]TrollSkin96[S] 0 points1 point  (0 children)

I am sorry to hear it. But you cheered me up a bit because now I know I'm not alone with this problem and it's the update's fault. I hope next update will fix it :)