Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android app and Play Store not working (work but needed to wait for 2-3 mins). #864

Closed
b4iterdev opened this issue Feb 10, 2021 · 7 comments

Comments

@b4iterdev
Copy link

I'm using Brunch r88 unstable 20210207 v2 with ChromeOS 88 rammus. Initial setup work, but after a reboot it's not loading.
It's only load if I wait for 2-3 mins on login screen, then everythings works. I wondering why I need to wait, is there any fix ? Or just because i'm using hdd and "rammus" don't ?

My device:

Dell Insprion 14-3467 (N3467)
Core i5 - 7200U
4GB DDR4
1TB HDD

/var/log/messages output:

2021-02-10T16:19:29.196502+07:00 INFO session_manager[1188]: [INFO:session_manager_impl.cc(1280)] Android container is running with PID 2030
2021-02-10T16:39:06.503234+07:00 INFO session_manager[1188]: [INFO:session_manager_impl.cc(1872)] Android container with PID 2030 stopped
2021-02-10T16:39:09.171188+07:00 ERR session_manager[1188]: [ERROR:session_manager_impl.cc(1354)] Error getting Android container pid.
2021-02-10T16:39:09.171280+07:00 ERR session_manager[1188]: [ERROR:dbus_util.cc(13)] CreateError(...): Domain=dbus, Code=org.chromium.SessionManagerInterface.ContainerShutdownFail, Message=Error getting Android container pid.
2021-02-10T09:44:27.550523Z INFO session_manager[1621]: [INFO:session_manager_impl.cc(1809)] Started Android container with PID 3473
2021-02-10T09:44:29.045985Z INFO session_manager[1621]: [INFO:session_manager_impl.cc(1300)] Android container is running with PID 3473
2021-02-10T09:45:18.099773Z INFO session_manager[1621]: [INFO:session_manager_impl.cc(1896)] Android container with PID 3473 stopped

dmesg log: https://pastebin.com/5zgJurpP

@b4iterdev
Copy link
Author

And, I tried to delete google sync, add_efi_memmap to kernel command line after cros_debug from issue #74 , do a powerwash then add android_init_fix. But none of them works.

@b4iterdev b4iterdev reopened this Feb 10, 2021
@b4iterdev
Copy link
Author

dmesg log when apps work: https://pastebin.com/FCb7vXXW
as I notices these last 3 lines:

[  204.775338] ESDFS-fs (esdfs): mounted on top of /opt/google/containers/android/rootfs/android-data/data/media type ext4
[  204.776490] ESDFS-fs (esdfs): mounted on top of /opt/google/containers/android/rootfs/android-data/data/media type ext4
[  204.779575] ESDFS-fs (esdfs): mounted on top of /opt/google/containers/android/rootfs/android-data/data/media type ext4

@b4iterdev
Copy link
Author

Confirmed that it's because of my HDD, if you are facing this problem, take a look at #813 and #790

@khanhtranngoccva
Copy link

khanhtranngoccva commented Feb 10, 2021

Can you just add a warning on the README homepage that ChromeOS must be run on an SSD, otherwise functions will break down? If you don't others will just keep asking this over and over again.

@WitaloA
Copy link

WitaloA commented Jul 29, 2021

friend help me

@bybenjamin
Copy link

same problem and same outputs. brunch 107 rammus 107
intel 4500
UHD video card
4gb ddr4 ram
256gb ssd
can anyone help ?

@b4iterdev
Copy link
Author

try to reinstall chromeOS

same problem and same outputs. brunch 107 rammus 107 intel 4500 UHD video card 4gb ddr4 ram 256gb ssd can anyone help ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants