Do the same thing with dtbo.img from lineage zip (just that you don't need to rename it in this case)Hello,
thanks again for your help. I did it, flashed with odin ap. Now, the message changed to Check Fail. Device: 11, Binary:8 (DTBO)
Do the same thing with dtbo.img from lineage zip (just that you don't need to rename it in this case)Hello,
thanks again for your help. I did it, flashed with odin ap. Now, the message changed to Check Fail. Device: 11, Binary:8 (DTBO)
flashed you DTBO too, now i can access the lineageos recovery . In recovery, i formated data like descripted, at the moment, i am flashing. Is there a possibility to sponsor you a coffee? GreetingsDo the same thing with dtbo.img from lineage zip (just that you don't need to rename it in this case)
Niceflashed you DTBO too, now i can access the lineageos recovery . In recovery, i formated data like descripted, at the moment, i am flashing. Is there a possibility to sponsor you a coffee? Greetings
Hello, On no, it stopped with 47% serving on cmd, (for 10 minutes no change), on mobile there is writen "Restoring Google Services Framework". Any idea? Thank you very much.Nice
Thanks for considering a donation, there's a paypal link in my profile
That 47% thing is a common "bug" when using sideload (also on other devices) but it's not really a problem, the output on device's display is what really mattersHello, On no, it stopped with 47% serving on cmd, (for 10 minutes no change), on mobile there is writen "Restoring Google Services Framework". Any idea? Thank you very much.
I don't know what i did wrong, i repeated whiping and installing, now LinageOS bootscreen apppears correctly and system bootsThat 47% thing is a common "bug" when using sideload (also on other devices) but it's not really a problem, the output on device's display is what really matters
Where do you get that message? For sure that's not from recovery
AA is working for me out oft the boy, but only the Version 6x, Version 5x just wants to update and refuses to workLoving this rom, instructions were great.
The only thing I cant get working is android auto, anybody know what I need to do there?
App installed but Car just wont detect it
You would break at least camera by doing so@Linux4 I took your 18.1 branch and built the rom myself. Its security patch level is still May. I can see that you updated your 18.1-experimental branch which includes security patch level June and also a newer kernel. Is it safe to pull and build your experimental branch or would I run into problems doing so?
Thanks for letting me know. The app works for me too, but it wont connect to the android auto headunit in the car. - Are you able to test that and see if it works?AA is working for me out oft the boy, but only the Version 6x, Version 5x just wants to update and refuses to work
Hello,Thanks for letting me know. The app works for me too, but it wont connect to the android auto headunit in the car. - Are you able to test that and see if it works?
It's planned in the future
Thanks a lot for considering that!
If you grab /proc/last_kmsg after it happened I can maybe even figure out a proper fixHi folks. It's me again, the one guy who kept complaining about random resets. I finally figured out how to prevent this from happening.
I primarily use wireless charging for charging the device and let the device "be" for hours on it. Most things I can access through my PC (e-mail, calls, whatsapp, etc). When it is on this charger the device used to randomly reset every now and then.
After installing ACC:
And setting a config using ACCA:GitHub - Magisk-Modules-Repo/acc: Upstream repo:
Upstream repo: . Contribute to Magisk-Modules-Repo/acc development by creating an account on GitHub.github.com
To 5-85-90 (shutdown, start, stop) I no longer got resets.Advanced Charging Controller (ACCA) | F-Droid - Free and Open Source Android App Repository
AccA empowers users to have full control over the device charge cycle.f-droid.org
It seems that the random resets have to do with the battery being near full and being on a wireless charger.
Is there anyone else who can test this?
For me this is an acceptable solution as I wanted to have ACC anyways to improve battery life.
When I tried getting the kmsg it didn't really say anything at all. I've attached it here. But maybe you can use it?If you grab /proc/last_kmsg after it happened I can maybe even figure out a proper fix
I just don't have a wireless charger myself so can't test
If you have any problems with getting that log feel free to pm me
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: