Interesting, it looks like I am on c6 as well, I will try this. In the logcat I saw some messages related to the WiFi - Radio handoff, so it could be that's the part of the equation that is causing the reboot (and hence why updating your radio firmware would fix the problem).
[OFFICIAL][7.1] LineageOS 14.1 - OnePlus One [bacon]
- Thread starter linuxxxx
- Start date
Interesting, it looks like I am on c6 as well, I will try this. In the logcat I saw some messages related to the WiFi - Radio handoff, so it could be that's the part of the equation that is causing the reboot (and hence why updating your radio firmware would fix the problem).
G
GuestK0061
Guest
Im still using the same firmware from the last cyanogen os build 13.1.2. Should i be on a newer firmware?
First restore TWRP backup to see if the Sim is ok (I hope you have a backup)
Gesendet von meinem A0001 mit Tapatalk
Why so complicated? Just try the SIM on another phone to see if it's broken.
If you have another phone [emoji4]. If not you can reflash the nightly you used before.
By the way, I never heard of this SIM issue before...
Gesendet von meinem A0001 mit Tapatalk
For users having problems with Wifi<->Mobile data auto switch. Go to developer options and enable "Mobile connection always active". Mobile data connection will be always ready, without any need to reconnect after wifi connection lost. I guess it's not battery friendly, but it solves all problems for me.
I have had that activated since the setting exists. It does not use much energy—check it in Settings, Battery. Recommended.
G
GuestK0061
Guest
Ok so how can there be a new firmware if that was the last official update? And what should i be on now? Because ive had no problems with it
That new firmware isn't really new. It's a hydrogen os firmware it seems. You do not need to flash a newer firmware. Just use what you are using now.
You should realize that: there will be no any firmware update. The one you have is last for ever. Lineage nightlies don't include any firmware.
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
Hydrogen firmware is not oficially supported to use with Lineage, there is no need to flash it unless you have really good reason to do that
G
GuestK0061
Guest
Thanks, this is what i thought anyway. Dont know why people were saying otherwise.
Radio causes random reboots?
Who has said otherwise? I only mentioned that I am testing c7-00011 for a particular reason, but I have never recommended it.
Let me repeat this once more: The standard radio firmware for the OnePlus One is c6-00241, I think, of 2015-05-15, probably made by OnePlus and distributed through CyanogenMod. If a user has no problems with this radio, keep it.
Who has said otherwise? I only mentioned that I am testing c7-00011 for a particular reason, but I have never recommended it.
Let me repeat this once more: The standard radio firmware for the OnePlus One is c6-00241, I think, of 2015-05-15, probably made by OnePlus and distributed through CyanogenMod. If a user has no problems with this radio, keep it.
G
GuestK0061
Guest
Anyway.. where I can find your radio ..have u a link for me??
Inviato dal mio A0001 utilizzando Tapatalk
I'm getting random reboots on 20170710 and the c6-00241 modem.
I haven't been using Lineage very long.. I think I started around 20170620 or so. (was previously on stock COS)
Reboot when leaving Wi-Fi
They are all here:
https://xdaforums.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
I am still testing only bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip and cannot vouch for the others. I would hope that bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip is the stable one that everybody has initially had on the OnePlus One from CyanogenMod.
My test seems to work fine, but I am not testing thoroughly enough to recommend the version to everybody. I will stick to my statement that everybody should keep the c6-00241 CyanogenMod version as long as it works well.
---------- Post added at 10:43 PM ---------- Previous post was at 10:26 PM ----------
Any idea what triggers these reboots? Or are they truly random?
I got reboots when I left my home Wi-Fi. I am currently testing the bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip radio firmware for this reason, and it seems that I no longer get these reboots. But if you do not observe spontaneous reboots when leaving some Wi-Fi area, then it does not make much sense to repeat my test.
Some people get spontaneous reboots in all kinds of circumstances, on various Android versions, and on all kinds of phones. The trigger is apparently not always the same, but a strong contributing factor is that Android does not and cannot be made to log the cause. Insofar I think Google is to blame. They have too little competition and too little interest in fixing Android's defects. I don't think that this is the fault of LineageOS alone.
They are all here:
https://xdaforums.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
I am still testing only bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip and cannot vouch for the others. I would hope that bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip is the stable one that everybody has initially had on the OnePlus One from CyanogenMod.
My test seems to work fine, but I am not testing thoroughly enough to recommend the version to everybody. I will stick to my statement that everybody should keep the c6-00241 CyanogenMod version as long as it works well.
---------- Post added at 10:43 PM ---------- Previous post was at 10:26 PM ----------
Any idea what triggers these reboots? Or are they truly random?
I got reboots when I left my home Wi-Fi. I am currently testing the bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip radio firmware for this reason, and it seems that I no longer get these reboots. But if you do not observe spontaneous reboots when leaving some Wi-Fi area, then it does not make much sense to repeat my test.
Some people get spontaneous reboots in all kinds of circumstances, on various Android versions, and on all kinds of phones. The trigger is apparently not always the same, but a strong contributing factor is that Android does not and cannot be made to log the cause. Insofar I think Google is to blame. They have too little competition and too little interest in fixing Android's defects. I don't think that this is the fault of LineageOS alone.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
93
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:All information and files — both in source and compiled form — are provided on an as is basis. No guarantees or warranties are given or implied. The user assumes all risks of any damages that may occur, including but not limited to loss of data, damages to hardware, or loss of business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty covering your device, it should be assumed that any warranty accompanying your device will be voided if you tamper with either the system software or the hardware.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our website.
Wiki
Official LineageOS Wiki: https://wiki.lineageos.org/devices/bacon
Installation
First time LineageOS 14.1 installation on your OnePlus One:
- Read the official Wiki page
- Unlock your bootloader if you haven't done so already
- Flash a custom recovery via Fastboot
- Push GApps (arm) and the CM 14.1 zip to your device
- Boot into Recovery
- Perform factory reset
- Flash the LineageOS 14.1 zip from SD card
- Flash GApps from SD card
- Reboot
Downloads
- Downloads : https://download.lineageos.org/bacon
- Changelog : https://download.lineageos.org/bacon/changes
- Google Apps (arm) (nano is recommend): http://opengapps.org/?api=7.1&variant=nano
- Su addon (arm): https://mirrorbits.lineageos.org/su/addonsu-arm-signed.zip
- Su remover (arm): https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip
Reporting bugs
You can report bugs on our Jira bug tracker as explained in our wiki.
F.A.Q.
- ROOT! ROOT! Give me root or i'll die!!! Where root is???
- Root has been removed from LineageOS builds, to allow people who are not interested in root access to enjoy apps such as PokemonGo or banking apps. A zip to re-enable root will be provided here. Other packages such as SuperSu, magisk or others are not supported and may cause problems
- Why no nightly this week?
- Build failed. Check again in 7 days
- When do I have to wipe data?
- You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
- Will you add <insert awesome feature here>?
- I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[OFFICIAL][7.1] LineageOS 14.1 - OnePlus One [bacon], ROM for the OnePlus One
Contributors
linuxxxx, forkbomb444, cyanogen
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2017-01-23
Last Updated 2017-04-1220
Yes. It also turns your phone into an aeroplane when you turn on Airplane mode!18"I think what a lot of people forget is that this is not a "make my phone neat & kewl" place.
As implied by the name this is technically a Developers forum/community.
Now what does that mean? Well first off it means that there is an expectation that if you are here then you want to customize your device but rather than just installing something that someone packaged you want to understand how it works and maybe even enhance it yourself.
These days, we have a flood of new users who are asking not "How can I do this myself" but more like "Give me the quick fix" without caring to understand the process. See if you read the threads then you get to experience the learning process, you see how the issues were investigated and confirmed. Then you get to watch the different attempts at resolution and learn why some failed while others worked. That is called Development.
The NooB backlash is coming from users who have walked in the development shoes and is directed mainly at those who don't care for the journey but just want the end result or destination.
As a Development Forum we are just as much (if not more) about the journey. I've read so many comments like "I don't have time to read all of the threads" or "I don't care how it works, just that it does". These very statements are contrary to the heart & soul of XDA-Devs and that is why the backlash is so strong.
Let me be very clear on this: IF YOU DON'T CARE ABOUT UNDERSTANDING THE JOURNEY THEN YOU PROBABLY SHOULDN'T BE HERE IN THE FIRST PLACE.
XDA-Devs is about developers & hackers helping each other and working together to get the most out of our devices by understanding them better than most.
XDA-Devs is not about helping everyone who wants a "Kewl bit of kit" make their phone better than the guy next to him.
Now do we go kicking users off who never contribute anything, NO. We tolerate it to an extent. Where the toleration ends is when these users start diluting the usefulness of the forum by repeating the same questions over and over again.
You ask the developers/ fellow members to understand your position. Well if you want to benefit from our experience and time then I think it is only fair that you understand our position."
- @kyphur16Pixel Experience updated.. (Phew!)
Changelog:
*Pixel Theme and Pixel Navbar made compatible with the latest weekly as of 24.04.17
--
Get Pixel Launcher and Pixel icons from the previous post here
>For Pixel-like blue accent, flash pixel_theme.zip
>For Pixel Navbar with animation, flash pixel_navbar.zip
NOTE: pixel_theme and pixel_navbar are build specific. Do NOT flash it on any build other than the aforementioned one, or else your device will bootloop. Consider yourselves warned!
**
Link to the Debloater I created a while ago : here
//thanks for the support guys, it really means a lot15Pixel Experience updated..
Changelog:
*Pixel Theme and Pixel Navbar made compatible with the latest weekly as of 11.04.2017
--
Steps to get Pixel icons
>To just get the Pixel Launcher, flash pixel_launcher.zip only
>For Pixel-like blue accent, flash pixel_theme.zip
>For Pixel Navbar with animation, flash pixel_navbar.zip
NOTE: pixel_theme and pixel_navbar are build specific. Do NOT flash it on any build other than the aforementioned one, or else your device will bootloop. Consider yourselves warned!
**
Link to the Debloater I created a while ago : here
New posts
-
General Android 15 Beta 1.1 AP31.240322.023 - "Vanilla Ice Cream" - Pixel 8 Pro [Husky]- Latest: roirraW "edor" ehT
