hi
i installed lastest cyanogen mod for my G2 but unfortunatly i found out that most of my sensors are disabled like the gyroscope.
any idea why ? anything i need to install ?
thanks
You need the proper baseband for CM11.
CM11 uses jelly bean sources so you need the 4.2.2 baseband. cloudyfa has them, search around in these forums or on Google. That will fix the sensors. Keep in mind when returning to a 4.4.2 Rom that you need to flash the 4.4.2 baseband..
(note: if you have the verizon lg g2 and you're using unofficial cm11 that's based on 4.4.2 sources, you need to flash that. Again, cloudyfa has a repo)
Last week there was a problem im CM which f...ed up sensors. Same problem in some CM based AOSP Roms. In this case has nothing to do with baseband.
Should be fixed now. Just flash newest version.
tropenfrucht said:
Last week there was a problem im CM which f...ed up sensors. Same problem in some CM based AOSP Roms. In this case has nothing to do with baseband.
Should be fixed now. Just flash newest version.
Click to expand...
Click to collapse
We hope that ?
So I follow the instruction, flashed the bumped bootstack, the resurrection remix rom and recommended gapps, but no matter how many times I tried, the phone simply hangs at LG logo. Does anyone knows what the issue might be? Oh, my model is d800.
On d800 you need the loki LP bootstack, but be sure to flash back to bumped before you flash a stock based rom like cloudy
kansasboy001 said:
On d800 you need the loki LP bootstack, but be sure to flash back to bumped before you flash a stock based rom like cloudy
Click to expand...
Click to collapse
I have tried using loki lp bootstack but when I do I just get an error message when flashing the rr rom zip.
Make sure you have the 5.5.5 version. It is NOT at the bottom of the list on afh. 5.5.5 will not error
I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I
So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?
From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.
ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.
i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]
S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.
I think you need hybrid bootstack for android 7.
WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.
Hello devs i need some help sorry for my bad english
I'm facing random reboots and freezing on some apps on my lg g2 F320 rom aosp extended 4.6 and lambda kernel n13
The phone restarts randomly whole day no specific reason or pattern and when ever i open facebook then phone got freeze that i need to pull battery out
faced same issue on my g2 d800 different roms and lambda kernel random reboots and facebook app freeze and restart
I had the same problem with my LG G2 f320, but it had been improving. Try for the latest Nougat Rom like LOS 14.1
I can't find any issues so far with the latest Rom.
kegang said:
I had the same problem with my LG G2 f320, but it had been improving. Try for the latest Nougat Rom like LOS 14.1
I can't find any issues so far with the latest Rom.
Click to expand...
Click to collapse
Tried many roms same problem i also tried lamba on my d800 my d800 also face same issue.. Can you tell me complete things like which bootstack you are using lamba version and rom link.. Thanks in advance
robroid said:
Tried many roms same problem i also tried lamba on my d800 my d800 also face same issue.. Can you tell me complete things like which bootstack you are using lamba version and rom link.. Thanks in advance
Click to expand...
Click to collapse
Well, I'm using the latest Lamda Kernel N13. For other aspects, I followed the guide about installing any d802 Rom to f320l. You can find the thread in this forum.
However, I installed Lineage OS 14.1 d802 Rom to my f320l.
Is there some magic combination of custom ROM + Kernel where this works?
Have tried latest Alpha and Super ROMs, as well as many different versions of mk2000 kernel and the Alpha kernel included with Alpha ROM.
It worked on bone stock 10L, but hasn't worked since. I can activate it and change my 911 address but the icon never shows up and it can't actually make calls over Wi-Fi.
Currently on SuperV20 4.1 10v with mk2000 1.5.6 beta 10.
Not sure if it's a ROM issue or kernel or modem or what.