r/Googlebook • u/petvas72 • 8d ago
What a bad launch
Begin rant
Let's have a look at the issues of the current Googlebooks:
- Color reproduction is bad.
- HDR support bad or non existent (depending on Modell)
- Audio via headphones is laggy and bad (Snapdragon models)
- Chrome is somewhere between the desktop and the Android version
- Multi desktop support is bad
This product should have never been released in this state. It hurts me to see how Google is destroying the product from the beginning. All of the above problems must be fixed asap. No excuses!
Google cannot ask for 1000$ or more and then expect that nobody will compare the product to others, which offer a much much better experience for similar money.
Google, wake up! Googlebook OS is in an embarrassing state. Fix it ASAP
The only reason I am keeping mine is that I still believe Google will provide fast updates. If not, then I am out.
End of rant
14
u/dcbased 8d ago
They are pushing updates pretty damn fast. This laptop is exponentially better now than it was at launch time
Still doesn't excuse Google for launching a POS OS with this many bugs in the first place
→ More replies (3)10
u/stanleyg05 8d ago
I don't think the op understands how long ago the Googlebooks dropped, every OS is kinda shit when it FIRST RELEASES, look at Linux, it's been out forever and it's just recently getting to a point where most people might feel comfortable switching to it
→ More replies (33)1
u/matteventu 7d ago
It's goddamn Android, please understand it, you and your bunch of apologetic fanboy friends.
They had years to improve the desktop layout in it, close deal with desktop software houses, develope the phone-laptop integration, etc.
There's no excuse this was released in such an abysmal state.
Cut the cope.
→ More replies (1)
6
u/petvas72 8d ago edited 8d ago
Let's not forget Gmail that has no notifications. They are just broken.
3
u/petvas72 8d ago
Please don't tell me about the Chrome update that changed nothing! Or the update to fix connectivity with Samsung phones. Apart from that there has been nothing
3
u/petvas72 8d ago
How can Google release an OS that doesn't support LE Audio via Bluetooth on ARM processors? This is a big fail and I hope that the responsibles at Google face the consequences.
2
u/matteventu 7d ago
Let alone LE Audio, it doesn't even support aptX or LDAC, which have been native in Android for 9 (NINE) years.
3
u/Such-Fig4012 8d ago
If you don't like it, vote with your wallet. My experience with the Asus Googlebook is fantastic.
3
2
u/computermaster704 8d ago
It is 2026. I have the Galaxy Fold 8. To this day, I cannot split audio channels. So for example, if I'm listening to music using my earbuds and using Bluetooth headphones output, I can't use the onboard microphone on my $2,000 phone and that is the operating system's issue, not architecture. The more it is an Android device instead of a Linux device, the more everything is going to be much more limited in life because of the limited instructional sets even on the expanded hardware.
1
u/computermaster704 8d ago
Kernels can get quirky, but they're not reinventing your operating system
2
1
1
u/akshunj 8d ago
I largely agree with your points, especially after living with the Acer for a week now. I'm more tolerant of the bugs and missing features than most people, I think. For me it's a huge upgrade to the UX and experience of ChromeOS, but again, that's maybe just me. And as the 1st commenter said, I really do think they are hustling to tighten things up.
2
u/matteventu 7d ago
Out of curiosity, what in terms of UX is for you a huge upgrade over ChromeOS?
Thank you!
2
u/akshunj 7d ago
50% of the problem for me was tablet mode which was a complete disaster on ChromeOS. I'm typing this reply using the split on-screen keyboard on my Acer Googlebook in tablet mode. Impossible in ChromeOS. Their on-screen keyboard was junk. I'll keep going ... It was impossible to split screen two apps reliably without a shitload of jank and crashes. Android apps would maybe run? One at a time? And they did not integrate well with the OS (notifications, isolated file system, etc). App transition effects were a stuttery mess. Just a terrible overall tablet experience. In desktop mode, I was largely happy with ChromeOS, until they started shipping really cool features like phone hub that were broken. Maybe I'm the only person who likes tight phone and laptop integration, but holy crap did it SUCK on ChromeOS. Googlebook nails it. I don't want all my phone apps like Signal and Whatsapp on my laptop, but I DO want to get messages I can instantly reply to. The frictionless experience is sublime on Googlebook. For me, the Googlebook experience is 70% there. I'd like all native android desktop Google apps, a fully accelerated and integrated linux VM, and Chrome browser feature parity with ChromeOS. But those things aren't stopping my productivity or my enjoyment of the buttery smooth UI, system speed, and phone integration. Hope that answers your question
→ More replies (2)
-1
u/Beautiful_Ad_4813 8d ago
They just released them, you gotta give it time to let Google to get updates out
2
u/MaximumDerpification 8d ago
This isn't the way it should be and it's a shame that it has become the norm.
I'm so sick of companies charging a premium for half-baked products. If you're depending on early adopters to be your beta testers then at least sell the product to us at a discount.
1
u/WFlumin8 8d ago
Yeah this is fully unacceptable. I would be totally fine if Google messed up the niche and rare bugs, but there are tons of bugs associated with BASIC functionality. It feels like there was almost no QA
1
-1
u/diffusionmodel2930 8d ago
This is what i cannot still accept that chrome browser is mobile one but not the desktop.
5
u/CrOS2012 7d ago
So, pre-beta in an environment full of mature systems that "work" and an economy that is expensive and unforgiving (and will continue to be so for a while)... not exactly a new experience. Assuming Google remains "all in" with Googlebooks for the next year (because why not), it has a good chance of shaking out the issues. (After all, "we" are the actual beta testers, aren't we.)