WTF is going on with android apps?

MrPumaKoala · 2022-06-15T23:22:47+00:00

With Chrome OS currently transitioning into a newer, more resource intensive way of running Android apps, Android apps on Chrome OS is in a rough spot rn. Android app performance is all over the place and it's gonna take developers a bit of time to address the various issues that have popped up with this transition. In the long run, this usage of a new method of running Android apps is a good thing (a lot of security related benefits to it) BUT, in the short term, it's gonna be a bit unstable (unfortunately).

How unstable and rough the experience is does depend a bit on your Chromebook specs/model, so it's always helpful to send in a bug report/feedback about your experience. Also, I don't know if you've tried this already BUT turning off and then turning back on Android apps has been reported to clear up some issues relating to the recent updates. Turning off Android apps will clear the installed Android apps (along with any Android app related data) from your Chromebook, so make sure to backup important info prior to doing this.

MrPumaKoala · 2022-06-12T00:42:26+00:00

Couldn't you have just used a USB C to 3.5 mm headphone jack adapter for this?

MrPumaKoala · 2022-06-08T02:09:58+00:00

As long as your willing to sell somewhat at a loss (so act with that expectation), you might be able to sell it on eBay.

MrPumaKoala · 2022-06-08T00:40:04+00:00

You're not wrong. CrossOver is a tool that lets you run Windows programs on Chrome OS. It's sort of a last resort tool though. How well it works does really depends on the specs of your Chromebook as well as the kind of Windows software you'd be trying to run with it. Not to mention that, even when it does work, the overall performance and experience you'll get in a Windows program (with CrossOver) can be all over the place. It's one of those tools that you turn to out of need and not one that you should be relying upon.

The main question I think you should be asking youself is what kind fo Windows software you think you may need in the future. Depending on what you come up with, you might be fine with the non-Windows alternatives that are available fo Chromebooks OR you might find that you are better off with a Windows device.

Aso, Chromebook's support for wireless printers are pretty good nowadays. In fact, depending on the age/model of printer, my Chromebooks support for printers can be better than what you get with Windows devices nowadays.

MrPumaKoala · 2022-06-07T23:57:50+00:00

Well, commonly reported issues are not necessarily easy to fix. I mean the issue seems to be mainly affecting OG Duet/Duet 5 users BUT it's not affecting ALL Duet/Duet 5 users. For example, I own and use an OG Lenovo Duet BUT am yet to run into this issue. In fact, I've actively tried attaching/detaching my keyboard repeatedly to try to replicate this issue and I just haven't seen it happen. This suggests that this reset/crash issue might be limited to Duets that are running certain apps or Duets that are running with a certain setting/configuration. Fixing an issue that pop ups only when certain conditions are being met might be more complicated than fixing an issue that is just universally affecting a certain device.

Not to mention that the issue isn't major enough for the Chrome OS team to send out a random update over. The only time when they break away from their update schedule is when there is some major security vulnerability that has to be patched OR some major software flaw that is universally impacting Chromebooks. Sometimes they deviate from schedule due to some issue or delay with a prior Chrome OS update, but that's about it. They're pretty rigid about this stuff, so I wouldn't expect the issue to get fixed until at least the next scheduled Chrome OS update.

MrPumaKoala · 2022-06-07T21:37:38+00:00

Reports of something like this happening to others Lenovo duets have been getting posted on this subreddit for the last few days. It seems to be a bug so there's nothing we can do until the developers decide to fix it with a future update.

The next time you see this happen on your Duet 5, make sure to submit a bug report. That's one of the ways in which we can get developers to pay attention to this issue.

MrPumaKoala · 2022-06-07T18:52:57+00:00

Honestly, this sounds like a fundamental hardware issue (specifically your internal storage seems to be done/is damaged in some way). There's really no way (or at least easy or reasonable way) for you to fix this issue.

I'm sorry to say this, but I think you should give up on the Chromebook & trying to find an alternative computer/device. You mentioned research paper, so I'm guessing that you might still be in school? If that's the case, maybe the school can rent out a laptop to you OR maybe let you use their on-site computer (if they have any)? I don't know what options you have, but I wish you luck on your research paper.

MrPumaKoala · 2022-06-07T18:44:24+00:00

You can look up the specs sheet for it using Google. I already did it for you and the Acer Chromebook R13 is using eMMC storage.

MrPumaKoala · 2022-06-07T18:41:29+00:00

Sounds like a bug. The next time it happens, you might wanna send in a bug report to the Chrome OS team.

MrPumaKoala · 2022-06-06T19:58:44+00:00

Take the trial and error approach with the version of the Proton Compatibility. I mean using the older version of Proton have fixed these types of issues for me in the past.

Honestly, this isn't the right place to ask about Steam Proton issues. I think you're better off asking a more Steam/Steam Proton oriented subreddit for help.

MrPumaKoala · 2022-06-04T04:46:50+00:00

It's actually based on my personal experience with the products themselves. And notice that my comments about RAM and OS performance were specified to Chrome OS detachables/tablets and NOT all Chromebooks. You're right that the Acer Spin 513 (mostly used in laptop mode) can do just fine with 4GB of RAM. The same can be said about most convertible/clamshell Chromebooks (also often used in laptop mode). With Chrome OS detachables/tablet devices though, it's different because detachables/tablets are often used in Chrome OS's tablet mode. I agree, btw, that Chrome OS's tablet mode looks horrible and is annoyingly resource intensive, BUT I also know that memory does make a difference when using tablet mode.

It's funny that you mentioned the Spin 513 and its CPU (the Snapdragon 7c). I once did a comparison between two different RAM configs (4GB RAM & 8GB RAM) of the HP x2 11 (detachable Chromebook that happens to come with the same exact Snapdragon 7c CPU). During that comparison, I found that tablet mode on the 4GB RAM model of the HP X2 11 would stutter and lag a LOT more than tablet mode did with the 8GB RAM model of the HP X2 11. A lot of freezes on the screen with the 4GB RAM model that didn't show up on the 8GB RAM model. A similar comparison with tablet mode on different configs of the Duet 5 (which come with a slightly different Snapdragon 7c Gen 2) showed similar results.

Now this is based on just my personal experiments that I've done out of curiousity, so it's nothing super scientific or definitive. Based on what I've seen through these comparisons though, I feel confident in saying that RAM config does makes a difference with Chrome OS detachables and tablets (once again, notice how I didn't say this applied with all Chrome OS devices).

MrPumaKoala · 2022-06-04T03:51:43+00:00

You know... The recent update delays seem to be a result of Chrome OS trying to address your Android version frustation.

As you may be aware, Chrome OS is currently transitioning from running Android apps in a container set up to running Android apps in a virtual machine set up. As a part of this transition in how android apps are being run, the Android part of Chrome OS is also transitioning from Android 9 to Android 11 (you may have noticed recent talks about this on this subreddit). Now there are several advantages & disadvantages to this new way of running Android apps. One advantage is that it will become easier to update from one version of Android to the next. This means that a transition from Android 11 to Android 12 (or some other future Android version) will be quicker & easier to do than past Android updates have been for Chrome OS. Along with that, there are also security related advantages to running Android apps within a virtual machine set up.

A significant disadvantage of running Android apps with this virtual machine set up is that there is more overhead/usage of resources with it. To be blunt, Android app performance with this new method hasn't been as good as it has been with the older container method. This can be somewhat addressed by developers through optimization & fixes, but that's not something that can be done quickly. This is one of the main reasons why this transition (signified by the transition from Android 9 to 11) is taking so long. The developers are being cautious with how they roll this out to try to ensure that the transition doesn't lead to completely unusable Android apps in Chrome OS. Based on how things have gone so far and based on which devices are yet to go through said transition, it seems like the Chrome OS developers/team are being especially careful with how they do this transition with lower end/not powerful devices, like Kuikui... And personally I'm kind of glad that they are.

Now I get the frustration with recent update delays (which, based on timing, seems like it could be related to this Android transition) and having to deal with Android 9 for a while longer, but you're gonna have to be a tad bit patient as the Chrome OS folks work things out. Unless you want a broken Android app experience on your Chromebook (which I suspect you don't), that's just how it's gotta be. After this transition has been completed though, I suspect they'll be able to do an update from Android 11 to Android 12 (maybe 12L) in a much more timely manner. I also do think that there's a good chance that your devices will get the Android 12 (if not 12L) update prior to the AUE.

MrPumaKoala · 2022-06-03T23:46:41+00:00

If they both have the same amount of RAM, go with the Duet 3. If the Duet 3 comes with 4GB of RAM and the x2 comes with 8GB of RAM, I'd either go with the HP x2 11 or hold off and wait for the Duet 3 w/ 8GB of RAM to become available.

With Chrome OS tablets & detachables, you get the best experience with 8GB of RAM. That's not to say that the 4GB of RAM are unusable. It just that there are really noticable stutters and lag with the 4GB of RAM configuration that you just don't see with the 8GB of RAM config.

MrPumaKoala · 2022-06-02T21:46:18+00:00

Putting aside whether it can fold back that way, I've always felt that folding back the detachable keyboard will end up negatively affecting the longevity of it. The keyboard's alright for a detachable keyboard cover and works well enough for something that came included with the device, but it's not made to be super strong or durable. It's not difficult to imagine it breaking after repeatedly being folded backwards. Worse of all, if the detachable keyboard does break, it's not super easy finding a replacement for it.

My advice is to just detach the keyboard whenever you don't need it. It's not as convenient as flipping the keyboard back, but it's the safer option for the keyboard.

MrPumaKoala · 2022-06-02T21:38:19+00:00

It might have to do with how the Duet 10 comes with an ARM processor while the Pixlebook Go comes with an x86 processor. I don't know if this still the case, but the same thing used to happened with the Call Of Duty Mobile game. It would work on the Duet 10, but crash on the Pixelbook Go.

MrPumaKoala · 2022-06-02T03:09:48+00:00

Not really. It's still early days for the device and it seems to currently be available mainly through the official Lenovo website.

I'm personally waiting until we start seeing the Duet 3 pop up at Best Buy, Amazon. and other retailers. This is partially out of convenience and partially cause I have better return experiences with those retailers. It also partially has to do with how pricing can be a differ bit with those retailers. Depending on the configuration (RAM, storage, etc.) of the Duet 3 that those retailers will be offering AND the pricing of these differently configured Duet 3s, the pricing currently found with Duet 3 11" 4gb might actually not be very good. We just don't really have a good frame of reference in regards to how the various configs of Duet 3 will/should be priced and, without that frame of reference, it's difficult to assess whether its actually "very well priced". This combined with, as you mentioned, the lack of reviews is making me hold off on a purchase.

As it becomes more available and as we see it pop up at other retail website, I suspect we'll start seeing more in-depth reviews about the Duet 3. You can hold off on a purchase until then OR you could try picking up the 4gb version now and try it out (hopefully the return policy is okay?). Maybe you can play the role an early adopter of and help the rest of us out by posting your own review of the Duet 3 on this subreddit?

MrPumaKoala · 2022-06-01T14:08:03+00:00

Oof. Out of curiousity, what Chromebook are you using?

MrPumaKoala · 2022-06-01T14:05:31+00:00

Well, the pricing aspect of it is somewhat of a fair point.... Your statement though implies that the ARM processors used in Chromebooks are the same kind that can be found in smartphones and that's not quite right. It's true that some of the ARM processors found in Chromebook have also been used in tablets/smartphones, but some of the newer ARM Chromebooks are actually using ARM processors that have been specifically designed for laptops.

Like with other processors, there are different tiers/types for these "made for laptops" ARM processors (entry level, mid-tier, etc.). ARM Chromebooks tend to stick with the entry level processor EVEN when their pricing is a bit much for entry level performance. I mean the HP X2 11 came with an older, entry level, "made for laptops" Snapdragon 7c processor and it was MSRP-ing at $599 (has since flopped and dropped). I just think it'd be nice if the $400-$600 ARM Chromebooks could come with a little bit more performance than what we get with entry level processors.

MrPumaKoala · 2022-06-01T13:51:24+00:00

Yea... Linux apps are in a weird place right now. They're available in Chrome OS BUT the way their treated within Chrome OS is a bit all over the place.

It probably won't do much in the short term, but you could try submitting bug/feedback report about this to the Chrome OS team. It may be a minor issue, but I'm sure you're not the only one dealing with this rn.

MrPumaKoala · 2022-06-01T03:17:36+00:00

Okay. Gotcha. Appreciate the clarification.

Currently, Chrome OS does not seem to have the feature that will turn off power saving mode for a specific app.

Having said that, do you really need to have power saving mode enabled? Can't you have the "Keep display on" setting enabled and just close the lid of the Chromebook whenever you need/want to put it into power saving mode?

MrPumaKoala · 2022-06-01T02:28:27+00:00

Have you tried disabling android apps on Chrome OS and then enabling them again?

Be warned that disabling all Android apps will wipe the Android apps that you currently have installed, so make sure to backup some stuff that you don't want to lose BEFORE trying this.

MrPumaKoala · 2022-06-01T02:24:40+00:00

"power saving mode or the display turns off"

Just to clarify, are "power saving mode" and "display turning off" supposed to be referring to the same thing here? Or is there some "power saving mode" on Chrome OS that is different from the display turning off?

MrPumaKoala · 2022-06-01T00:06:43+00:00

Well, ARM Chromebooks do technically support Android apps better due to the fact that Android apps are mostly built with ARM infrastructure in mind. There are actually certain Android games that won't run on x86 Chromebooks but will run fine on ARM Chromebooks.

The frustration with Android apps on ARM Chromebooks has more to do with the specific ARM processors used for Chromebooks. Even when strictly compared with just other existing ARM processors, the ARM processors found in recent Chromebooks tend to be of the not so powerful variety and, with a major portion of them, can be a little old. I'm sure there is a rational behind why newer ARM processors haven't been used with newer Chromebooks, but this reality limits performance with apps in general. This is something that may change in the future. With where we are now though, I think there are certain x86 Chromebooks that can do a better job at handling certain Android apps than ARM Chromebooks currently can. As I mentioned previously though, a lot of this assessment/comparison does come down to use case.

MrPumaKoala · 2022-05-31T19:55:24+00:00

Huh. I don't tend to have problems with the interface when using the Duet with the detachable keyboard. Interface stutters & glitchiness mainly occur for me when I'm in tablet mode. Do you have linux apps enabled? Google Assistant?

MrPumaKoala

TROPHY CASE

Welcome to Reddit,