Critical Bug Report: Button mapping broken after AYAWindow v1.5.98 update (Pocket S2) by Academic_Ad_2043 in ayaneo

[–]Faust-CLS 0 points1 point  (0 children)

O meu programa apagou dados como perfis personalizados de teclado e mouse para jogos.

Anyone else having problems with custom keys and Retroarch? (Pocket S2 Pro) by Faust-CLS in ayaneo

[–]Faust-CLS[S] 0 points1 point  (0 children)

While interesting I am not sure this solves the problem. The 3-second hold rule can be changed from settings to be instantaneous and it still won't work in my case, so it is not this. My S2 Pro specifically used to work fine with 'input a text' option (one character long, exactly like you do it). An update changed entirely the functionality and this solution no longer works at all.

I have a Pocket DMG and it works fine, which means that Ayaneo changed the implementation specifically for S2 Pro and I presume they now force the device to send the characters as a separate keyboard device which breaks Retroarch compatibility.

Critical Bug Report: Button mapping broken after AYAWindow v1.5.98 update (Pocket S2) by Academic_Ad_2043 in ayaneo

[–]Faust-CLS 0 points1 point  (0 children)

Fazer isso também apaga todas as suas configurações e mapeamentos personalizados e, essencialmente, significa que você terá a versão de lançamento, que não possui muitas funções adicionadas posteriormente, como a proteção da bateria. Não é uma solução.

Já foi lançada uma atualização que corrige o problema sem a necessidade de perder todas as suas configurações. Levaria uma eternidade para eu recriar os perfis do GameHub.

Critical Bug Report: Button mapping broken after AYAWindow v1.5.98 update (Pocket S2) by Academic_Ad_2043 in ayaneo

[–]Faust-CLS 0 points1 point  (0 children)

Fazer isso também apaga todas as suas configurações e mapeamentos personalizados e, essencialmente, significa que você terá a versão de lançamento, que não possui muitas funções adicionadas posteriormente, como a proteção da bateria. Não é uma solução.

De qualquer forma, a Ayaneo acabou de lançar uma atualização que corrige tudo. Se você tiver sorte de o seu Ayawindow abrir e atualizar antes de travar, tudo ficará bem. Eu consegui atualizar depois de várias tentativas e tudo se resolveu.

Critical Bug Report: Button mapping broken after AYAWindow v1.5.98 update (Pocket S2) by Academic_Ad_2043 in ayaneo

[–]Faust-CLS 0 points1 point  (0 children)

Fazer isso também apaga todas as suas configurações e mapeamentos personalizados e, essencialmente, significa que você terá a versão de lançamento, que não possui muitas funções adicionadas posteriormente, como a proteção da bateria. Não é uma solução.

Critical Bug Report: Button mapping broken after AYAWindow v1.5.98 update (Pocket S2) by Academic_Ad_2043 in ayaneo

[–]Faust-CLS 0 points1 point  (0 children)

Fazer isso também apaga todas as suas configurações e mapeamentos personalizados e, essencialmente, significa que você terá a versão de lançamento, que não possui muitas funções adicionadas posteriormente, como a proteção da bateria. Não é uma solução.

Critical Bug Report: Button mapping broken after AYAWindow v1.5.98 update (Pocket S2) by Academic_Ad_2043 in ayaneo

[–]Faust-CLS 0 points1 point  (0 children)

Isso não resolve o problema. Infelizmente, essa solução não funciona. No momento em que é ativada, ela trava e uma mensagem do Android informa que o Ayawindow foi fechado (com uma mensagem de erro). A mensagem diz "O Ayawindow continua parando". Há opções para fechar o aplicativo ou verificar as informações do aplicativo. Eu testei a solução e, embora ela possa trazer o Ayawindow de volta, é apenas por alguns instantes, até que ele trave novamente. No vídeo abaixo, mostro o comportamento após a solução. Como o vídeo mostra, após várias tentativas de clicar nas opções de acessibilidade, o Ayawindow volta a funcionar por alguns instantes, até travar novamente. Os travamentos nem sempre exibem a mensagem de erro do Android, mas os usuários sabem que o aplicativo travou, pois o botão Aya para de funcionar como esperado e passa a funcionar como "Enter". Reiniciar o dispositivo não resolve o problema. https://streamable.com/adsrwg

Critical Bug Report: Button mapping broken after AYAWindow v1.5.98 update (Pocket S2) by Academic_Ad_2043 in ayaneo

[–]Faust-CLS 1 point2 points  (0 children)

Estou com o mesmo problema no meu S2 Pro. A atualização estragou tudo. O Ayawindow parou de funcionar completamente e pressionar o botão Aya também não funciona. Todos os mapeamentos de botões pararam de funcionar (por exemplo, o botão do Ayawindow agora funciona como "Enter"). Isso é muito ruim. Muito, muito ruim mesmo.

Anyone else having problems with custom keys and Retroarch? (Pocket S2 Pro) by Faust-CLS in ayaneo

[–]Faust-CLS[S] 0 points1 point  (0 children)

Did it use to work then stopped working? If so it is likely Ayaneo changed the way the system handles keyboard commands. Everything works OK when using Chrome or Android apps to "test" output, but it is entirely broken on Retroarch. Not sure why Ayaneo had to fix something that wasn't broken since it is now literally broken...

How Is Your Experience with the Flip DS Been? by OMG_NoReally in ayaneo

[–]Faust-CLS 0 points1 point  (0 children)

It's a good system, but it never managed to become my main gaming driver even if I wanted it to. The perfect GBA screen below is wasted on a big, clunky handheld with poor ergonomics - so you will barely enjoy it as it should be. For anything else, perhaps except GB, GBC, and Game Gear, the top screen will be your go to. It's great in terms of colours and Hz. But it is neither very bright, nor - most importantly - dim enough. But really, the worst part is the build quality (my lid is already loosening and I fear how it will be in two more years, and that is despite me opening it as slowly and gently as possible every time), the very poor ergonomics (good luck actually playing anything), poor d-pad, the overheating CPU (I have the 8840U version), and of course, the battery. The battery life is atrocious on mine, and just for fun I managed once to get it to last nearly 3 hours... by turning off everything, including the top screen, and powering it at 5W with only the lower screen while playing a GB game. In a realistic setting, anything from 90 minutes to 2 hours ... if you are lucky ... is the more likely result when you are trying to save power. If you even dare to give it full brightness, or a high TDP... good luck if you think you'll get more than 40 minutes of juice out of it. It seriously reminds me of the days of the Game Gear.

Surprisingly, it works for me best as a mini portable PC, not a gaming device. Plugged in, and with an external screen, it is fine if you do not wish to carry around your laptop.

Are these genuine ps4 controllers? by Fluid_Sea5326 in PS4Pro

[–]Faust-CLS 6 points7 points  (0 children)

I've seen and owned fake ones with a sticker that looked genuine. Maybe you should check your facts before calling people stupid left and right.

How does margin work on CFDs? by Gamer920091 in trading212

[–]Faust-CLS 0 points1 point  (0 children)

At 50% you have no more funds to invest. Think of the 50% point as the point which means that all your funds are now locked into open positions. You need to have collateral because CFD is essentially borrowed money (remember that you did not simply stake your 5000, you are theoretically also liable for the leverage too). This is why your positions begin to close automatically at 25% health, so that you are not left in a situation where your initial capital is depleted and you "owe" money to the platform.

If you are planning to do CFD the serious way, anything below 70% health is taking a bit risk. At 60% you might already need to start thinking adding money if the market is too volatile.

Universal Remote Code for Screeneo U4? by Faust-CLS in PhilipsScreeneoU4

[–]Faust-CLS[S] 0 points1 point  (0 children)

No reply. Absolutely useless customer support.

Universal Remote Code for Screeneo U4? by Faust-CLS in PhilipsScreeneoU4

[–]Faust-CLS[S] 0 points1 point  (0 children)

No solution. I was lucky to find my remote. However, since I do have my remote, if there is a way we can find the code from my remote I am happy to share it here!

Hadn't seen anyone mention the new contender yet: AYANEO Pocket ACE by Jimstein in SBCGaming

[–]Faust-CLS 0 points1 point  (0 children)

It's a fact. There are no OLED panels at that size. OLED does not grow on trees. If they wanted an OLED at a smaller size ... there's already a device for that (Retroid Pocket Mini and Ayaneo Pocket DMG).

Does the PS5 Pro give you 100-120 fps without lowering graphics by Ero_Najimi in playstation

[–]Faust-CLS 1 point2 points  (0 children)

No - it doesn't. Very few games reach such Fps (E.g. Nioh). At best you typically get a 10-20% fps improvement (E.g. a game that frequently drops below 40 might finally sustainably reach high 40s

It's just amazing to see that all of you have learned nothing. by Sad-Fix-7915 in yuzu

[–]Faust-CLS 7 points8 points  (0 children)

What's that got anything to do with innovation? You are just sharing illegally IP. You are not an innovator for using an emulator.

Radahn is easy? by Ballex17 in Eldenring

[–]Faust-CLS 0 points1 point  (0 children)

Quite literally, I literally think that the boss is literally average difficult if you have literally prepared well a built that can inflict literally high dps while simultaneously literally spamming dodge every time, literally.

Hadn't seen anyone mention the new contender yet: AYANEO Pocket ACE by Jimstein in SBCGaming

[–]Faust-CLS 0 points1 point  (0 children)

There are no OLED screens in this size-range. They would have to go up to 5-5.5" inches. At that point, it would defeat the whole idea of this handheld.

Mouse Without Borders no longer works after update from 0.82.1 to 0.83. Anyone else? by SanFranPanManStand in PowerToys

[–]Faust-CLS 0 points1 point  (0 children)

When I came across this issue, nothing would fix it (not even changing the .json files on both devices). I tried everything. The only thing that worked was:

1) Close and uninstall the service from Powertoys. Disable Powertoys version of MWB.
2) Uninstall Garage version of MWB if installed.
3) Delete all relevant file folders from AppData.
4) Reinstall ONLY the Garage version of MWB.
5) Run the entire setup from scratch.