undefined | Better HN

0 pointsdavid-given10y ago0 comments

Crouton in a window doesn't really work so well --- on my Asus Flip it frequently forgets to redraw the window after changes, which makes it nigh unusable.

I haven't tried rootless mode, though.

I'll agree with you about Chromebooks for developers, though (well, if you like doing everything from text mode, which I do). My ARM-based Flip is a lovely machine. Cheap, ultraportable, completely silent, ludicrous battery life and the quad-core ARM flies.

I just wish they'd get X running in a VC working. (The Flip uses a special graphics stack which apparently makes this hard.)

0 comments

2 comments · 1 top-level

jshevek10y ago· 1 in thread

That's too bad about the Flip and the screen not redrawing. The Pixel doesn't seem to have this problem, and its runs android studio on X no problem.

It can do AS on X in a window or tab, or as a separate desktop. The last mode seems to require the two systems to handing over low level control of the hardware to each other, whereas the first two modes are more seamless. So yes trying the other approach might solve the redraw problem.

Yes, for text mode only things are even easier. The "crosh window" app (plus tmux, etc) is all I need to perfectly happy with Crouton.

david-givenOP10y ago

Okay, yeah, the Pixel's obviously using the older graphics stack. The new one's called Freon and is apparently loads simpler and faster... but has a few side effects.

(It still has a VC, although the VC2 shell is actually a user-space program called frecon which draws text via Freon. Switching from VC1 to VC2 is super seamless. So it's obviously possible somehow to draw full-screen graphics through Freon.)

Also, I agree; the crosh window is surprisingly good, and interacts nicely with full screen. Bit slow, though. `ls -lR` will wedge the window for a while until it flushes its buffer.

j / k navigate · click thread line to collapse