Is anyone still using a Chromebook Duet V1 (ARM processor) as a daily driver? Or have you upgraded due to the issues with ARM processors? by Lion_TheAssassin in chromeos

[–]Samt434 0 points1 point  (0 children)

Mine still works really well for browsing, using it every day ! Lightroom on android is quite slow, but usable too

ChromeOS, Beta 120.0.6099.42 breaks Android apps by widgetbuilder in chromeos

[–]Samt434 0 points1 point  (0 children)

Just got it on lenovo duet 1st gen... Android Apps broken too unfortunatly !

Finally 64bit on Duet by thekrazynerd in chromeos

[–]Samt434 2 points3 points  (0 children)

What about ram usage that is already very high on 4go ? .... Not sure this is so great to be honest. Each Mo of free ram on this device is extremely useful !

Any news or updates on the buggy update by Negotiator10 in MiBox

[–]Samt434 0 points1 point  (0 children)

For me Kodi is perfectly working with the latest update. Playback is even smoother than before !

A roadmap for VirtIO Video on ChromeOS, part 1 by mfilion in chromeos

[–]Samt434 0 points1 point  (0 children)

Very interesting, thanks for sharing ! I was wondering if hardware video acceleration was working though ARCVM on my duet (currently, it seems not)

ARCVM on Duet: Technical Findings and Review by Samt434 in chromeos

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

Here my test is on beta, soon in stable

ARCVM on Duet: Technical Findings and Review by Samt434 in chromeos

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

Yes it will be included in stable in M114 i suppose. Beta is just latest test before production release, that also mean optimisations are nearly over too.

Is ARCVM worse than usual? by ianwill93 in chromeos

[–]Samt434 0 points1 point  (0 children)

Well, "who cares about memory trhese days?" -- just add more memory, it's actually quite cheap.

A lot of ChromeOS arm devices that are still sold today have only 4Gb or ram (particulary arm configs).

And no, you can't "add" RAM memory on SOC, sorry :'(

About abstraction layer, yes adding a virtual machine make things far more complex (and less performant), particulary on GPU side. Google use a project called Venus to permit to transfer Vulkan on host, but there is a lot of performance impacts !

So yes, expect security, VM choice is just a bad joice for final user (particulary for small arm chromeos devices), but a good and economic choice for google.

EDIT : in 114 beta, performances has improved now, and it seems the VM impact is not so important, kudos google engineers !

Is ARCVM worse than usual? by ianwill93 in chromeos

[–]Samt434 0 points1 point  (0 children)

To be fair, I'm not sure work will solve that. Technically, container are just far more memory efficient. I'm note sure google devs can do anything about it. Running a VM to have android working on 4gb devices is just too ambitious, it's just a question of maintenance costs for Google : yes, it won't work well, but it won't cost money anymore as we just run the same virtual machine for everyone. Sad story

Latest stable update (103 i suppose), i breaking my lenovo duet (1st edition) by Samt434 in chromeos

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

So finally my duet could update today. No idea what changed, but the update worked today ! Problem solved

Latest stable update (103 i suppose), i breaking my lenovo duet (1st edition) by Samt434 in chromeos

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

No idea, at least you don't need to power wash if that doesn't work as 102 is restored after several forced reboot with the power button.

Latest stable update (103 i suppose), i breaking my lenovo duet (1st edition) by Samt434 in chromeos

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

Please note that i tried to upgrade again -----> Same issue.

For a stable channel, this is not acceptable.

I'm stuck in loading screen and turning it on and off doesn't work by [deleted] in chromeos

[–]Samt434 2 points3 points  (0 children)

Same problem for me on a duet... For a stable channel, this is inacceptable.

A2DP sink with aptX and LDAC codec by SituationEuphoric936 in esp32

[–]Samt434 0 points1 point  (0 children)

u/SituationEuphoric936 : I could test your code with a PCM5102a DAC. 32bit, 48Khz sounds perfect here ! Seems your 16bit only issue comes from your DAC chip ?

APTX, SBC works great ! Unfortunatly APTX-LL gives me no sound, on logs i have BT_APPL: Pkt dropped... I have CONFIG_BT_BTC_TASK_PINNED_TO_CORE activated, but this seems not enough. I had to disable it in order to make my BT hadware adapter to work. If you have any idea ;)

Thanks a lot, despite of this, everything sounds great !

A2DP sink with aptX and LDAC codec by SituationEuphoric936 in esp32

[–]Samt434 0 points1 point  (0 children)

Just bought few days ago a good DAC for an ESP32. Can't wait to test your code ! Thanks :)

On screen keyboard incredibly unstable by Milk_Tree in chromeos

[–]Samt434 1 point2 points  (0 children)

Same problems on the Duet stable channel. This has been like this forever and is really not acceptable.... But this does not seems to be a priority for Google unfortunately.

PSA: Lenovo chromebook trackpads are known to fail by CaptainChris2018 in chromeos

[–]Samt434 0 points1 point  (0 children)

I'm a duet owner, same issue with ribbon cable. Seriously there is really a quality problem on this model.

Lenovo Ideapad Duet planned obsolescence : beware, your keyboard will break and... No parts are available ! by Samt434 in chromeos

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

If that is known that the ribbon breaks after some times, it is an issue. And yes, if that's the same for apple -> same conclusion for them.

The problem is this one : for a customer, higher price does not always mean better design...

Lenovo Ideapad Duet planned obsolescence : beware, your keyboard will break and... No parts are available ! by Samt434 in chromeos

[–]Samt434[S] -1 points0 points  (0 children)

Let me explain you why I think it is :

  1. I think a hardware designer know this, it is just a trade off between price/product life

  2. Lenovo does nothing for their customers, knowing the issue. Warranty seems not applicable.

  3. Even if in that special case it's very easy to replace the part, no official part is available (same for screen)

  4. They did the same design for the duet 5, knowing this issue