ONEPLUS ONE FIX COMPASS/GPS ISSUES
I don't have an OPO anymore, so I may no longer mantain this thread.
Hi all.
After many months having this issue, I finally have a solution.
This is only a temporary fix in order to have your GPS functioning. It is not guaranteed it will work with future software/ROM updates.
I highly recommend you to open a warranty ticket here.
Now that I'm seeing many people having the same problem, I will share the solution with you.
What's the issue?
Impossible to calibrate or use the compass. GPS accuracy/tracking failures.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's the cause?
Firmware.
Now I know that this problem showed up when the new firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 (commonly known as 241) was released, many months ago.
Since the day it was installed on my OnePlus One I unconsciously started to have this issues.
I changed ROMs, wiped caches, did full clean installs (but maintaining the last firmware) and the problem persisted…
Some weeks ago CyanogenMod released a nightly with the baseband version .4.0.1.c7-00011-M8974AAAAANAZM-1 (commonly known as 011) and the problem was gone. At least until they had it reverted back to 241, when the issue automatically reappeared.
After reflashing the 011 version I came to the final conclusion that 241 was the cause.
I already let them know about this: you can see me "whining" about this when they reverted to 241, but they stated that they were not having such issue, ignoring the problem.
How to fix?
If you have such issue, regardless of the ROM you're using, you probably are with the 241 firmware version.
To solve it, simply flash the 011 013* firmware version.
Note: make sure you have TWRP 2.8.6.0 or 3.x.x in order to properly flash this firmware.
Please read the NOTES and UPDATES sections before you proceed.
You can find the firmware on the attachments or here.
You will have to re-flash it every time you update your Nightly or ROM.
NOTES:
None of the following situations happened to me. I just want you to be aware of them:
I am not responsible for any damage you may cause to your phone when trying to follow this guide.
When flashing things, you may end up with no IMEI. Be safe and backup your EFS partition following this guide.
If you can't access your network after flashing this modem, reboot your phone.
Hope this guide will help you!
Feel free to click "Thanks!" if it helped you!
UPDATE:
This fix is still working on all the COS13 updates!
EDIT 11/08/2016:
* Replaced 011 with 013 as the later won't break the proximity sensor.
Has anybody else tried it?
Could someone confirm this?
I'm very interested to solve this issue, but I can't take risks...
I had problems with Sky map, when my phone is flat down, compass works ok, but standing up it's shaky and rotates... So this didn't really fix my problem.
walent said:
I had problems with Sky map, when my phone is flat down, compass works ok, but standing up it's shaky and rotates... So this didn't really fix my problem.
Click to expand...
Click to collapse
https://github.com/sultanxda/propri...mmit/2d48d254d3d330d3d2304e64fef68978611a4d1f
Changing /etc/sensor_def_qcomdev.conf fixed it for me
waterdaan said:
https://github.com/sultanxda/propri...mmit/2d48d254d3d330d3d2304e64fef68978611a4d1f
Changing /etc/sensor_def_qcomdev.conf fixed it for me
Click to expand...
Click to collapse
Unfortunately i already have it like that
waterdaan said:
https://github.com/sultanxda/propri...mmit/2d48d254d3d330d3d2304e64fef68978611a4d1f
Changing /etc/sensor_def_qcomdev.conf fixed it for me
Click to expand...
Click to collapse
Hi people, unfortunately, in my file both version and numbers end in 5 ?
walent said:
Unfortunately i already have it like that
Click to expand...
Click to collapse
UPDATE:
This fix is still working on the COS13 updates:
GPS Issue with OnePlus One
Hey everyone, I'm suffering from a GPS performance of my OnePlus One. It's been TERRIBLE since I bought the phone in December of 2014!
I tried other software (Waze or Here maps), something is wrong with the hardware I believe.
I've updated my OPO to the latest official OS available.
I'd love to avoid rooting just for fixing my GPS.
Please see screenshots:
I'd appreciate your advice and help!
Thanks you!
Tried this fix and unfortunately it didn't work (currently on 20160708 cm13 nightlies)
I have tried it now, but unfortunately it didn't work. i'm with cm13.1-xxxxS1KN
nurunuru said:
Tried this fix and unfortunately it didn't work (currently on 20160708 cm13 nightlies)
Click to expand...
Click to collapse
It was working until the 20160706 CM13 nightly, until I sent my OnePlus One for RMA. I'm tired of this malfunction.
Hey does it work with Lineage OS? I'm having firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 on build 20170306 of Lienage OS or is there a way developers of Lineage OS can implement the new firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 in Lineage OS weaklies build? I would love to fix this problem once and for all
nipun03 said:
Hey does it work with Lineage OS? I'm having firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 on build 20170306 of Lienage OS or is there a way developers of Lineage OS can implement the new firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 in Lineage OS weaklies build? I would love to fix this problem once and for all
Click to expand...
Click to collapse
Good question!
nipun03 said:
Hey does it work with Lineage OS? I'm having firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 on build 20170306 of Lienage OS or is there a way developers of Lineage OS can implement the new firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 in Lineage OS weaklies build? I would love to fix this problem once and for all
Click to expand...
Click to collapse
I don't have an OnePlus One anymore.
But since you're having the same old firmware (DI.3.0.c6-00241-M8974AAAAANAZM-1) in Lineage I assume the firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 would still work and fix the compass issue.
Do a nandroid backup and test it yourself
PS: you'll have to find the firmwares on another thread since my links were taken down and I no longer mantain this thread.
EDIT: Updated the firmware link with one working.
tfae said:
I don't have an OnePlus One anymore.
But since you're having the same old firmware (DI.3.0.c6-00241-M8974AAAAANAZM-1) in Lineage I assume the firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 would still work and fix the compass issue.
Do a nandroid backup and test it yourself
PS: you'll have to find the firmwares on another thread since my links were taken down and I no longer mantain this thread.
EDIT: Updated the firmware link with one working.
Click to expand...
Click to collapse
Thank you for updating the firmware link.. Will definitely try it
Related
Q&A for [ROM][5.0.2][Official]Dirty Unicorns Bacon
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.2][Official]Dirty Unicorns Bacon. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Du official 5.0.2 question..
I flash this ROM bat in setting info devices is write unofficial ??
A few things I've noticed
So, great rom, I've always been a fan of DU, and I'm glad my OnePlus finally gets it officially.
A few things I've noticed so far:
There is no timeout selector for the buttons backlight, I usually set it to 1 sec, but there's no way to change it from the 5 sec default.
If you turn on the on screen nav bar, the backlight for the buttons still lights up.
If you turn the device off while the buttons backlight is on, it will be stuck on until you turn the device on again. Only fix is to let it time out before locking the screen. (I believe this is a known issue).
In the settings, it reads DU version: UNOFFICIAL-v9.2
On initial setup, it defaulted to using MetroPCS for my carrier (I have T-Mobile) It worked fine when I changed it to the proper carrier. (This seems to be a problem in several roms)
Personal preference: I'd like, when charging, the battery percentage stay inside the circle instead of moving to the side of it.
Most of this is nitpicky (except for the button backlight stuck on when device is locked), I really think it's quite stable and awesome, I can't wait to see 9.3 come out.
Can anyone tell if boeffla kernel 3.1 is compatible with 5.0.2 du rom build 100415..
TIA..
Wifi fix after flash.
My Wifi was having issues, since I still had the old radio firmware. The lollipop modems can be found at http://forum.xda-developers.com/oneplus-one/development/radio-updated-modem-radio-files-oxygen-t3072516
Once I flashed the new modem with TWRP, WiFi works great.
kunal1540 said:
Can anyone tell if boeffla kernel 3.1 is compatible with 5.0.2 du rom build 100415..
TIA..
Click to expand...
Click to collapse
I am on latest weekly build. Not sure if Boeffla will work.
Oxygen radio/modem
Hi all,
First post
Loving DU!
Just wondering if its possible to flash: Full-oxygen-04-04-15-Bacon-modem-flashable.zip onto OFFICIAL-v9.3 build 3.4.67... Or maybe a better question is,.. would this improve reception at all?
Thanks
just wanted to say great job. Loving the latest weekly on bacon!
is it possible to remove the hardware keys?
sewb said:
is it possible to remove the hardware keys?
Click to expand...
Click to collapse
Yes, from Dirty Tweaks, System, Buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM deserves a 1000 thanks from me. I just love it. Looking forward to the next update!!
Hmmz I'm getting "Process system not responding" - not constantly - no idea what triggers it - running catlog for today...
Here's what I did yesterday - coming from Slimsaber -
Flash latest TWRP
Wipe cache - dalvik - system - data
Flash latest CM Nightly
Flash latest DU
Flash Slim-gapps beta fix
Everything seemed to be working fine... 2 crashes that I know of right now... phone just soft-reboots and then the "process system not responding" error... weird...
Probably gonna reflash stuff tonight - something wrong in my flash order?
I do not find in the settings - security - change the order of the numbers in the pin pad
language italy , where I can find them ! thanks
Version 9.4 Dirty Unicorns Bacon
Hey quick question. Does screen pinning work on this rom?
I am about to install this. Does xposed work with this rom? if so what version? Also, any known bugs? cant seem to find these answers anywhere. cheers
http://forum.xda-developers.com/showpost.php?p=61933341&postcount=356
Click to expand...
Click to collapse
I was under the impression this was fixed already. Check out: https://jira.cyanogenmod.org/browse/BACON-3275
I'm not having anymore issues with Bluetooth since this fix went in.
Boot loops - Need Flash help
I'm having an issue flashing this ROM. I just got an RMA replacement on my OnePlus so I am coming from CM11. I flashed CM12.1 Nightly (7/20 build) to get updated firmware, then clean wipe, and flashed DU. After rebooting, I get a boot loop at the OnePlus logo and DU never loads. Interestingly, if I fastboot flash back to CM11, clean wipe, then flash DU, it will load, but is missing the CM12 firmware/modem.
I'm using twrp-2.8.6.0.6-bacon-materialised as my recovery since twrp-2.8.6.0 doesn't load for me when flashing on top of CM12.1 nightly.
Anyone know how to avoid the boot loops while maintaining CM12.1 firmware? Any help would be greatly appreciated.
System UI has stopped
Hi
I have clean flashed (wiped system and caches), and installed the latest update, however my phone keeps giving me "Unfortunately, System UI has stopped". Any ideas please on how to solve?
Thanks
Hey der...m using Official DU..there is some problem in SuperSU (root) rooted apps are not working..please help me...I really liked this ROM very much.. Thanks in advanced..
Incall UI
I'm unable to access the Incall UI in the latest 9.6 . I clean flashed 9.5 then updated to 9.6 anybody has the same issue? any solutions?
First off to give credits to - @robalm for the Base/rom here http://forum.xda-developers.com/lg-g3/development/stock-t2961073
And Credit to - @autoprime for posting, boot,modem,images and so on!
Rom Status - STABLERom Details:
Stock based on D855 v20i
LG apps/LG Update Center (Works?)
Stable?
Stock international on D850 what else is there to say?!
Current Bugs:
Error Message random times at boot: Check HERE ( I have not tried this, flashing may fix?)
Root Can it be rooted by flashing supersu 2.40? (I haven't tested yet)
ONE WARNING: This does change your model number to D855 in Build.prop. You can prob always change it to D850 but I have not tested that. You can however always flash back to a D850 rom. Which I recommend before flashing back to 100% stock if you ever do.
Screenshots:
2nd Post
Download Links:
Main Server - HuntersPad_20D855_20Rom_20V1.zip - 980.8 Mb
Mirror Server (Might be faster at the moment) - http://hunterspad.com/rom/
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another Reserved
So can we just flash this on d850 just like any other rom?
Lol ???
2SHAYNEZ
shayneflashindaily said:
Lol
2SHAYNEZ
Click to expand...
Click to collapse
whats so funny?
So you can't make calls?
omnomnommm said:
So you can't make calls?
Click to expand...
Click to collapse
You can make calls, you just can't hear anything or be heard...... Perfect for calls with your singificant other.... blame it on the phone..... :angel:
I think I know how to fix the no-call-audio bug. I'll give it a look this evening, since I've spent one day on AOSP and I'm actually not liking it too much.
TemporaryTester said:
I think I know how to fix the no-call-audio bug. I'll give it a look this evening, since I've spent one day on AOSP and I'm actually not liking it too much.
Click to expand...
Click to collapse
Thanks!
Sent from my iPhone using Tapatalk
This should resolve call audio. Flash in recovery.
I also tried to bake in the cust fix earlier, but it doesn't do anything. Still throws that error.
Credits to @Cloudyfa, as I reverse-engineered his work to figure this out.
TemporaryTester said:
This should resolve call audio. Flash in recovery.
I also tried to bake in the cust fix earlier, but it doesn't do anything. Still throws that error.
Credits to @Cloudyfa, as I reverse-engineered his work to figure this out.
Click to expand...
Click to collapse
So, does it fix the no-sound problem? Somebody else tested it?
Does this ROM have the tethering working ok?
dev,
is it possible to get a tot file for your base rom? which is d855 20i
waiting your reply
jacktackle said:
dev,
is it possible to get a tot file for your base rom? which is d855 20i
waiting your reply
Click to expand...
Click to collapse
Sorry No don't have it.
Sent from my iPhone using Tapatalk
jdfloresd said:
So, does it fix the no-sound problem? Somebody else tested it?
Does this ROM have the tethering working ok?
Click to expand...
Click to collapse
Though it may carry no weight, I've been running this ROM since I posted that fix. I've had no issue with standard, speakerphone, Bluetooth, headphones, rear speaker sound, etc. Mute works as expected too. This hack was reverse-engineered from CloudyG3 (which, I think, is just the sound drivers and profiles pulled straight from the D85020f ROM); it causes the ROM to handle sound in the way that is identical to his.
Native wifi tethering works flawlessly for me.
jacktackle said:
dev,
is it possible to get a tot file for your base rom? which is d855 20i
waiting your reply
Click to expand...
Click to collapse
You can probably find a TOT somewhere on the international G3 forums, but it won't flash onto a D850 due to the model mismatch.
Rom Status has been changed to STABLE
Can you patch this to 20p?
Images are here.
I hope someone dumps D85021l soon, so that we can get VoLTE working here too. I'll update my fixer zip after, unless you want to integrate it into the base zip (which, by all means, do).
Well, looks like this thread and general interest in stock international ROMs has died, but I still use it. Figure someone else does too.
Patched to D85520w. This uses the original D85020f kernel, as D85021-series kernels are incompatible. Modem has been patched up to D85021r, as that does work for some reason.
Google Drive download.
Thanks to @hyelton for the original zip, and all credit for its components allocated as such.
Thanks to @robalm for the D85020w dump.
Thanks to @Cloudyfa for the hack to make D850 sound work.
Thanks to @Yoshi_Guy for the D85021r modem.
Would this still change the model to D855? You know if the Music app bug is solved?
Thanks
plguzman said:
Would this still change the model to D855? You know if the Music app bug is solved?
Thanks
Click to expand...
Click to collapse
No, it should rename it to LG-D850. In-call and normal audio should be functional.
What's the Music app bug? I use the Music app and have no issues.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM12.1 is here for the D801, aka the T-Mobile LG G2.
This is a source build rom, which includes all the latest changes from cm. The nightlies are starting August 3rd.
Instructions
Official support is now limited to Kitkat and Lollipop basebands. CM-12.1 is based on a completely new kernel. This has enabled support for the latest basebands newer than jellybean.
While many people and devices are in various states we officially recommend flashing back to stock then fully updating your device before using cm-12.1.
If you are coming straight from cm-12.0 the rom will not boot.
Download cm-12.1, and gapps. Put them on your sdcard, reboot to recovery. Flash, and enjoy!
The latest will be available at:
http://get.cm/?device=d801
Gapps:
Official CM ones (soon):
http://wiki.cyanogenmod.org/w/Google_Apps
Click to expand...
Click to collapse
Known Issue
None!
Click to expand...
Click to collapse
Change Log
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the following people:
rashed
acree
Click to expand...
Click to collapse
Source
http://github.com/CyanogenMod
Click to expand...
Click to collapse
Works great, no problems encountered yet!
Edit:
Camera not working, also tried Motorola and Google cameras without success.
My D801 is running stock Lollipop 30B rooted with TWRP. Can I just flash the ROM+GApps normally? Or would I have to install a bootstack changer?
briand.mooreg said:
Works great, no problems encountered yet!
Edit:
Camera not working, also tried Motorola and Google cameras without success.
Click to expand...
Click to collapse
Update:
Camera is working in newest nightly.
I just flashed the latest nightly from the stock lollipop lg rom. I flashed the 20g bootstack, cm, and gapps. Once the rom booted, my phone would constantly freeze and reboot every few minutes. Is anyone here having this issue. Let me know if I missed flashing a file or something. Please and thank you
Sent from my LG-F350K using Tapatalk
Mobile Data Issues
I really want to use this ROM but it's got an issue that I can't seem to fix and it makes the phone almost unusable. I switched back to KK bootstack and installed the ROM and this part went off without a hitch. ROM booted fine but I couldn't get cell data. Tried a bunch of different things until I found out that the APN setting was wrong (I'm on Tmobile). I fixed that and data worked for a bit, was even able to run a speed test. However shortly after that the phone rebooted. Then it kept rebooting, finally figured out that whenever the phone connects to LTE it automatically reboots. No warning, no nothing, just one second the phone is up the next second it's at the LG logo. If I immediately turn on airplane mode at boot it works fine. I can then turn on WiFi and then mobile connection and it works without rebooting. Also of note, when it has one of the LTE reboots, it causes it to lose the saved password of the WiFi connection. If anyone has any tips please let me know! I'm at a loss here, I can provide logcats if it would be helpful!
---------- Post added at 07:21 PM ---------- Previous post was at 07:17 PM ----------
alexnaoumi said:
I just flashed the latest nightly from the stock lollipop lg rom. I flashed the 20g bootstack, cm, and gapps. Once the rom booted, my phone would constantly freeze and reboot every few minutes. Is anyone here having this issue. Let me know if I missed flashing a file or something. Please and thank you
Sent from my LG-F350K using Tapatalk
Click to expand...
Click to collapse
Try switching on airplane mode as soon as it boots up and see if that lets it run without issues for a bit. See my previous post for more info.
Hey guys I figured it out. I had flashed the 20G bootstack and had the same issue - reboot every time connected to LTE. Not only on this ROM but every AOSP 12.1 ROM. Switching to the 30b bootstack solved the issue for me.
thanasisc4 said:
Hey guys I figured it out. I had flashed the 20G bootstack and had the same issue - reboot every time connected to LTE. Not only on this ROM but every AOSP 12.1 ROM. Switching to the 30b bootstack solved the issue for me.
Click to expand...
Click to collapse
Can confirm this is correct thanasisc! Thanks for sharing so others know. I'm honestly pretty miffed right now because some kid posted in the other development forum that you needed the kk boostack which is a bull faced lie and actually causes issues. We need to see if we can get mods to delete that post so more people aren't led astray.
Can I get some help fixing the Mobile Data issue with cm12.1? I flashed a nightly build from Aug. 27th and everything worked perfect until I lost my T-Mobile LTE-4G-3G-Edge-whatever.
Also is it recommended to run a nightly build for a daily driver? Because I ordered a G2 strictly for stock android 5.1
does slimport work on this rom
What is the recovery.img that cm is providing? Should I install that first? I have never seen cm provide recoveries before.
Unofficial CM-12.1 update w/ Snap
Anyone interested in downloading a "newer than November" build of CM-12.1 for the G2, please visit the following page:
http://forum.xda-developers.com/showpost.php?p=66071230&postcount=1458
Build has the official CM-13.0 version of Snap integrated into the ROM w/ working HDR.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Latest update: June 29th 2017
Disclaimer:
Altough we are working hard to deliver a bug-free rom, things may break and we are not responsible if something goes wrong and your hardware becomes damaged or if you have any problem, you are taking a risk flashing roms.
Hi, so you might wonder why the other thread got closed and what's all of this about. Well, the answer is that now I'll be maintaining this rom while Surdu will take care of Resurrection Remix, the rom is the same and you can flash this builds without wiping if you had the 'older' rom.
Instructions:
If you come from stock EMUI 5.0:
Install TWRP (Available in this subforum)
Format data
Flash vendor.zip
Flash LineageOS's zip
If you already have LineageOS:
Flash LineageOS's zip
Downloads:
Find them in this DevDB project section called 'Downloads' (you might need to use a computer)
Bugs:
Encryption
Changelog:
Code:
01/06/2017 - Fixed random reboot issue
01/06/2017 - Added loop support
29/06/2017 - Fixed tethering
29/06/2017 - Fixed shaky camera
29/06/2017 - Updated Lineage source
Asking for help...
There are still some little bugs to fix and things will break from time to time, so in order to properly help you and keep the thread organized every help petition should include:
Brief description of the issue
A way to replicate it
Screenshots/Logs
Without that information, your post will be futile so please meet those easy conditions and try to keep the thread clean!
Last but not least, thanks to the whole OpenKirin team (@surdu_petru @OldDroid) for their amazing job at keeping updated roms for kirin devices as well as helping with this one.
XDA:DevDB Information
LineageOS 14.1 for Honor 8, ROM for the Honor 8
Contributors
XePeleato, surdu_petru, OldDroid
Source Code: https://github.com/OpenKirin
ROM OS Version: 7.x Nougat
ROM Firmware Required: EMUI 5.0
Based On: LineageOs
Version Information
Status: Stable
Created 2017-06-01
Last Updated 2017-06-30
Going to try it these days. Thanks
I see vendor.zip only in Downloads section
Yeah only vender.zip is in the download section, there's no Lineage zip
morpheus302 said:
I see vendor.zip only in Downloads section
Click to expand...
Click to collapse
Gus194 said:
Yeah only vender.zip is in the download section, there's no Lineage zip
Click to expand...
Click to collapse
Please be patient, it's coming very soon
Thank you for understanding !
I'm bit confused. So where is the download section?
Found it
Sorry about that, there must be a problem with XDA servers, it's taking more than an hour to upload! And unfortunately I couldn't upload it without posting the DevDB thread, if it keeps working like that I'll find a more reliable storage solution.
I am really sorry! Check back in 5 minutes or so
Very nice job, and happy you fixed the issue. I'll set it as my daily driver once everything's OK
So what exactly caused the issues ? I'm curious as to whether it could have been solved on our own (i do say without Huawei's kind but forced operations).
And what do we do with that vendor.zip ? Flash it on top of Lineage's original Vendor package ?
(EDIT : Check post on top, the joys of cross-posting )
Still, thank you immensely on behalf of all the community
DJ Daemonix said:
So what exactly caused the issues ? I'm curious as to whether it could have been solved on our own (i do say without Huawei's kind but forced operations).
Click to expand...
Click to collapse
Hi, the problem was that a driver introduced by Huawei checked the time that it takes to boot (running in a kthread), if it takes more than three minutes it reboots to eRecovery, but it looks like it waits for a signal from userspace to check if it booted (like, write 1 to /sys/.... Whenever it boots).
We were actually aware of this being the issue, and tried to avoid it by editing the function's code (ARM64 instructions because we had no source (By filling the function with NOP or returning 0)) but we didn't succeed at first and thought that the kernel release was near so it made no sense to keep wasting time on it, if you want to see more details just go to github and check what we did, I hope that you understood the explanation.
Thanks for your kind words!
EDIT: The rom is up, you can download it now.
The Lineage zip file has uploaded! Thanks again for all your guys work.
Thx for your job. I'll now have to unlock the bootloader and start flashing. Two questions: can I lock the bootloader again once I installed LOS? Do i need to install twrp or is it enough to just boot it for installation?
faeArai said:
can I lock the bootloader again once I installed LOS?
Click to expand...
Click to collapse
Not at all, you need to be on EMUI in order to relock it. (You can if you go back to EMUI but I think that you asked if you could do that while you are on LineageOS).
faeArai said:
Do i need to install twrp or is it enough to just boot it for installation?
Click to expand...
Click to collapse
TWRP is just needed to format data and install the ROM, there's no need to keep it after installing the ROM.
What issues, if any, are present? Does the dual camera work? FPS fully functional along with gestures? Thanks
NeophyteGS2 said:
What issues, if any, are present?
Click to expand...
Click to collapse
Encryption
NeophyteGS2 said:
Does the dual camera work?
Click to expand...
Click to collapse
I am not sure about that, I think it does because that's coded into the HAL and we are using the one from Huawei.
NeophyteGS2 said:
FPS fully functional along with gestures? Thanks
Click to expand...
Click to collapse
It works well but the gestures are not included by now, maybe in the next release.
XePeleato said:
Encryption
I am not sure about that, I think it does because that's coded into the HAL and we are using the one from Huawei.
It works well but the gestures are not included by now, maybe in the next release.
Click to expand...
Click to collapse
Fantastic, thanks for the quick response. I'll test it out later and reply with feedback after a week or so
NeophyteGS2 said:
What issues, if any, are present? Does the dual camera work? FPS fully functional along with gestures? Thanks
Click to expand...
Click to collapse
I do not want to be rude, but if you want a personalized rom, based LOS or AOSP with fully dual camera support and FPS gesture, you better stay on stock EMUI
does the rom supports volte?if no please add that feature..this is the one con to make it as my daily driver
---------- Post added at 07:20 PM ---------- Previous post was at 07:20 PM ----------
thanks for your hardwork :good:
Where can I download this?
XePeleato said:
TWRP is just needed to format data and install the ROM, there's no need to keep it after installing the ROM.
Click to expand...
Click to collapse
What about updates? Do I need TWRP for (OTA-LOS) updates?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Razer Phone
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Razer Phone.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
cheryl - Official builds
cheryl - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Known bugs (won't fix):
- Can't switch FPS to 60 (can only switch between 90 and 120)
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps. - GApps are included in my unofficial builds
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_razer_msm8998
Flashing your unofficial build now.
I take it coming from 18.1 official requires a clean flash?
Thanks so much for keeping these devices alive it really means a lot to me.
Rox598 said:
Flashing your unofficial build now.
I take it coming from 18.1 official requires a clean flash?
Thanks so much for keeping these devices alive it really means a lot to me.
Click to expand...
Click to collapse
if going to unofficial yeah, but officials coming probably this week.
npjohnson said:
if going to unofficial yeah, but officials coming probably this week.
Click to expand...
Click to collapse
Think I'll stick with unofficial for a while since it passes safetynet without root.
Fwiw the at a glance widget doesn't show the weather for me and I had to disable the Android system intelligence as it kept telling me it had stopped not sure if the intelligence controls that widget.
Rox598 said:
Think I'll stick with unofficial for a while since it passes safetynet without root.
Fwiw the at a glance widget doesn't show the weather for me and I had to disable the Android system intelligence as it kept telling me it had stopped not sure if the intelligence controls that widget.
Click to expand...
Click to collapse
android system intelligence is fixed - next build just went live which fixes it.
At a glance is expected - we don't have the tie ins for it.
npjohnson said:
android system intelligence is fixed - next build just went live which fixes it.
At a glance is expected - we don't have the tie ins for it.
Click to expand...
Click to collapse
Ah brill I just saw it and downloading now. Shame about at a glance I'll just use the old one.
Oh and theres a message on boot about an internal error?
Rox598 said:
Ah brill I just saw it and downloading now. Shame about at a glance I'll just use the old one.
Oh and theres a message on boot about an internal error?
Click to expand...
Click to collapse
fixed too.
npjohnson said:
fixed too.
Click to expand...
Click to collapse
You're a wizard thanks!
Official builds running on Saturday night.
I'm currently on 18.1 official and just got an OTA notice about this build (19). Currently using OpenGapps micro for Android 11, should I wait for that to update before i download the new 19 ROM or is it okay to switch to MindTheGapps? The test builds for OpenGapps don't work for SDK32 according to the OpenGapps thread, so I would need to switch to get Gapps.
Just an FYI I moved over to official builds since they released today seems you can't manually pick the Material You colour from the wallpaper and style menu.
I *think* it was there on the unofficial build.
Front Camera Not Working
Yep this weeke update didn't fix the front camera either
The screen size of the app don't macht my phone screen, please check attached pics.
Only the nova settings screens is ok, the rest are positoned on the upper left side of the screen. But only at graphic level. The interface level (touchs) is recognized at full screen. It makes the phone almost unusable.
It works fine with lineageos 18.1.
I don't know if it is a configuration issue or another problem.
Any idea?
Thanks in advance
Are the above issues (front camera and screen size) are still problematic in the most recent builds?
-SKYLINE- said:
Are the above issues (front camera and screen size) are still problematic in the most recent builds?
Click to expand...
Click to collapse
From my side, yes. The screen problem is yet present with the last version installed. See attached pic.
Regards
saenanme said:
From my side, yes. The screen problem is yet present with the last version installed. See attached pic.
Regards
Click to expand...
Click to collapse
pls try unofficial - we may have fixed it.
npjohnson said:
pls try unofficial - we may have fixed it.
Click to expand...
Click to collapse
Where can I download it?
Thanks
npjohnson said:
pls try unofficial - we may have fixed it.
Click to expand...
Click to collapse
If I were to go from LOS17.1 official to your unofficial, do I need to do a complete wipe?
Also, when you say it passes safetynet by default, does that mean banking apps work fine? Thanks!
-SKYLINE- said:
If I were to go from LOS17.1 official to your unofficial, do I need to do a complete wipe?
Also, when you say it passes safetynet by default, does that mean banking apps work fine? Thanks!
Click to expand...
Click to collapse
Yes and probably.