Anything I can do to help add nfc and/or FM?Again I can look but sprint runs different hardware so it isn't exactly as simple as saying to build a module and it working.
Anything I can do to help add nfc and/or FM?Again I can look but sprint runs different hardware so it isn't exactly as simple as saying to build a module and it working.
I have to use my magic and create more time 1) for testing and 2) repair - for my phone and this ROM.
I broke it doing something. Came across a bad backup. all while not having time. Where is that magic ! ?
I thank you again for the attempt at fixing the PRL update and I will test and forward resuts ASAP.
"Thank you button" for the file alone - let alone the rest.
You can create and push the patch. Other than that I just need some free time which I don't have right now. I'm not ignoring you but nfc isn't playing nice and I haven't even started looking at FM.
Downloaded and installed the November 03, 2017 ROM and still no joy. The only place that I found a responsive Dialer Code was using the *#*#72786#*#* dialer code (SCRTN) which is a HUGE step forward from other builds - KUDO's! An oddness is that the a new Prl file should be downloaded/installed with the code howeer, when instagating the Code, it only (SCRTN) resets MDN, MSID, Slot 1 NAI and Slot 1 NaI Password and nothing to UPDATE PRL as it seems to do with older builds (prior to nougat).
In the Wireless and Networking section under the MORE section there is an option (Provider settings) that I was specifically looking for to Update Prl which is where i believe it should be however, the process reports "com.android.phone has stopped" immediately when attempting to access it. The only option listed is 'Open app again. If attempting after that, the singular option/only option changes to "close app". Any other path to PRL update would be fine as well.
I have NO clue why my Cell/Data (Using FreedomPop Account and SIM) radios works in Lollipop but not Lineage Nougat. Updating the PRL is what causes the radio to work in the prior build. In all honesty, my assumption of the Updated PRL may not be the culprit.
Anything specific/special place I should be lookig to/for testing specifically?
NFC not tested as I don't use it but extremely rarely an I wont be using it if the device can't work as a phone
Per your request: PM Sent
Has anyone ever been able to get the phone to work via Bluetooth in the car ? I have 2 LS990's and both connect fine and do media but the phone icon has a slash through it on the radio and the battery indicator is greyed out and empty . Is this a known issue with no workaround ? I've flashed multiple builds of several roms back to Feburary in the last 2 days and it's the same on all of them , Vanir , Tipsy , Tesla , Lineage etc all . The only common denominator must be the source they are based on is all I can figure . Anyone know of a fix ? Thanks
I have a similar issue to yours. I am on Ting and have not been able to get my PRL/profile to update, even using the methods described earlier in the thread Flash, restore other backup, update prl/profile, restore new backup.
I would be glad to test any prl update code as well. If anyone can point me to where that code is in the repo and what it logs I would be glad to look at that too.
I apologize for the silly question but, did you delete your old Blue Tooth phone pairing from your car and ensure the Car is NOT paired with your phone? The pairing in your phone should not have made it through the wipes and flashing but....
In any case, before you 'start', ensure the BT pairing is deleted on both ends of the connection.
Sorry for the "Is it plugged in" question but, sometimes it the simple thngs eh?
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
----------------------------------------
In all honesty it is a Cyanogen Mod issue that has followed into Lineage.
I'm NOT sure if it works as I finally broke my phone BUT, what at least partially works is using the native dialer in the Unique/Special ROM a few posts up from the OP (Kasual52) and dialing *#*#72786#*#* - Phone will reboot once if not 2-3 times and one of those times is the PRL Update. Fair warning now, my radio is toasted now from my playing, but I don't think it has anything to do with the ROM or *#code.
After I attempted the Nougat ROM and couldn't get my Cell signal to connect, I restored a backup or three and reflashed ZVF and (same) ZVC modems and nada dang thing worked. Going to try a new FP SIM next - holding breath - other ideas welcome.
Good Luck
I apologize for the silly question but, did you delete your old Blue Tooth phone pairing from your car and ensure the Car is NOT paired with your phone? The pairing in your phone should not have made it through the wipes and flashing but....
In any case, before you 'start', ensure the BT pairing is deleted on both ends of the connection.
Sorry for the "Is it plugged in" question but, sometimes it the simple thngs eh?
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
----------------------------------------
In all honesty it is a Cyanogen Mod issue that has followed into Lineage.
I'm NOT sure if it works as I finally broke my phone BUT, what at least partially works is using the native dialer in the Unique/Special ROM a few posts up from the OP (Kasual52) and dialing *#*#72786#*#* - Phone will reboot once if not 2-3 times and one of those times is the PRL Update. Fair warning now, my radio is toasted now from my playing, but I don't think it has anything to do with the ROM or *#code.
After I attempted the Nougat ROM and couldn't get my Cell signal to connect, I restored a backup or three and reflashed ZVF and (same) ZVC modems and nada dang thing worked. Going to try a new FP SIM next - holding breath - other ideas welcome.
Good Luck
Ouch. I'm feeling less adventurous now.
So even reflashing a backup based on the Sprint ROM PRL/Profile update fails? Do you have any system update apps frozen on those ROMs?
When I try to flash this and some other rims I get a error message that says something like "this device was made for . it was made for . I forget the exact message..some rims like crdroid and turbo do work...I am on a ls990 but it is a boost mobile phone not sprint is that a problem? Please I know this device is old but it seems like there's still a decent sized user based seeing as there are quite recent posts in some of the threads for this phone...if anyone could help or respond I would greatly appreciate it..I have tried using Google and searched ls990 threads and turned up nothing..thank you in advance and thanks to all the devs of this phone.
#include <std_disclaimer.h>
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.
Beautiful ROM! S'much appreciated.
Settings, More, Cellular Network, Carrier Settings produces the error:com.android.phone has stopped
Open app again.
There is a reload/refresh circular button to click on the second line before "Open app again".
Having issues locating where/how to update PRL due to horrid DATA reception which is nothing new to this location.
Freedompop is the carrier.
LS990 running (latest) LineageOS version 14.1-20170611-NIGHTLY-ls990
Since Cell/DATA was not beautiful before the ROM Flash and horrid after, I flashed Modem VFC and although possibly imaginary, the connection is more stable but also still poorly and "apparently" not as good as before.
I think it was an issue with one of the CVEs that were merged but I haven't had a chance to figure out the exact issue yet. I'll get the build pulled.Has anyone had any success booting the last two weekly builds? The 8/30 and 9/6 builds both go into a bootloop for me... the Lineage startup logo never appears... tried many things including erasing and clean installing and I get the same. Going back to 8/23, all is good again...
The latest download is available -> https://download.lineageos.org/ls990. Let me know if there are any issues with it.
The only way to get rid of that error it's to install an older factory firmware (I think around zvb) and flash from there or go with stock. It isn't an issue but it lets you know that you aren't running a stock image. You should get it booting into TWRP and Lineage but not if you go to fastboot.I'm having some small issues with my most recent installation of Lineage OS nightly on my G3 (LS990).
I did the following:
I installed TWRP.
I advanced wiped the cache, system, and data partitions.
I flashed the LineageOS zip (lineage-14.1-20170913-nightly-ls990-signed.zip).
I wiped the dalvik cache.
I flashed the LineageOS su add on zip (addonsu-14.1-arm-signed.zip).
I flashed the GApps zip (open_gapps-arm-7.1-pico_20170914.zip).
I rebooted.
Everything seems to be going ok, but everytime I reboot, I see a "secure boot error, error 1003" at the top of my screen. Is there a way to get rid of that message? Also, is there a way to install SuperSU onto the device, or is the su add-on the root for the device? I enabled apps to have root in the developer options screen. The hash sign in the status bar at the top really bothers me for some reason. Is that something built into LineageOS or is that part of the su add-on? Is there a way to hide that?
Thanks for the help.