Database Develop

[Q&A] [ROM] [4.4.4] [VS980] ParanoidAndroid [10/10]

Q&A for [ROM] [4.4.4] [VS980] ParanoidAndroid [10/10]
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

To whom it may concern;
I'm new to the world of programming but have been in the android game since the original g1 with T-Mobile. I've been flashing custom roms and recoveries since then and I have also been doing some very basic coding. C++ and C# primarily. If you would like a beta tester to prevent more tedious and time consuming problems from arising prior to your updates I'm willing to test for you and if you'd think I could be of any programming assistance or would like to show me around the programming world I'd love to take you up on that. Pm me for my personal email if you'd like and I'll get back to you ASAP.
Sincerely,
Mike J.​

New to G2...flashed beta-3 and lost VZW LTE/3G data
I recently upgraded from VZW gnex to the LG G2 (bought off swappa). It was rooted already but running stock, and I'm used to AOSP, so I decided to go with Paranoid Android Beta-3. Long story short, I was having issues with LTE so I flashed the latest build (beta 5) and it got stuck in a boot loop. I was able to get back into recovery (TWRP 2.8.0.1) and restore nandroid backup, but when I booted I could no longer get verizon LTE or 3G data. Wifi connected fine, and calls/SMS go fine...just no mobile data. It does connect to "eHRPD" though, which doesn't have any data access.
Things I've tried:
1. Flashing a new bootstack. Tried 12A, 12B, 24A, 25A, 25B, 26A. No data with any of them
2. Flashing a new ROM (Tried Spirit ROM, which flashed fine but no data, and CM11, which went into a bootloop)
3. Calling *228 for a reset
4. Wiping the whole ROM and reflashing the same ROM and Gapps
5. Also tried setting APN as shown on a few websites. But as soon as I hit "Save" the modified APNs disappeared off the list.
Does anyone have any experience with losing LTE/3G like this? Luckily I have my old phone still so I just pop my SIM card back into it and it connects to data fine.

Updates
I am currently running the 10/25 build. When it comes to updates, do I want to flash over my current with the newer? Or is there a different process?

rpc:s-7:aec-0 after flash last night.
I'm getting the [rpc:s-7:aec-0] info from server error on my vs980 since i flashed last night. I flashed 26A, then PA, and then PA micro gapps.
this morning I did a full wipe and clean reinstall of PA, and I tried using the pico Gapps instead of the micro build. same result.
tried clearing google related app data, no fix. any ideas?

to the user with the apn problem, I had to set the apn 3 times before it saved
Love the ROM, great work. Was wondering how I would get Tmobile wifi calling option on this? I'm using the verizon vs980 version. Thanks

What about JDI pannel? PA kernel support JDI panel type?

ZBBfan3092 said:
I recently upgraded from VZW gnex to the LG G2 (bought off swappa). It was rooted already but running stock, and I'm used to AOSP, so I decided to go with Paranoid Android Beta-3. Long story short, I was having issues with LTE so I flashed the latest build (beta 5) and it got stuck in a boot loop. I was able to get back into recovery (TWRP 2.8.0.1) and restore nandroid backup, but when I booted I could no longer get verizon LTE or 3G data. Wifi connected fine, and calls/SMS go fine...just no mobile data. It does connect to "eHRPD" though, which doesn't have any data access.
Things I've tried:
1. Flashing a new bootstack. Tried 12A, 12B, 24A, 25A, 25B, 26A. No data with any of them
2. Flashing a new ROM (Tried Spirit ROM, which flashed fine but no data, and CM11, which went into a bootloop)
3. Calling *228 for a reset
4. Wiping the whole ROM and reflashing the same ROM and Gapps
5. Also tried setting APN as shown on a few websites. But as soon as I hit "Save" the modified APNs disappeared off the list.
Does anyone have any experience with losing LTE/3G like this? Luckily I have my old phone still so I just pop my SIM card back into it and it connects to data fine.
Click to expand...
Click to collapse
I'm having the EXACT same problem.

fndfd
广东省给多少个大概代购复古风格

any idea why my vs980 loses signal when i connect it to wifi, or reboot? running paranoid android custom rom, and even when i'm on stock, this happens???
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
Sent from my LG-VS980 using XDA Free mobile app

Help - No data on Verizon network using stock image

Ver 5.0.1
Baseband MDM9625_104335.118.02.55.04R
Kernel 3.10.40
Build LRX22C
All stock
Received phone today, popped in SIM no issues at all.
Performed the following steps.
1-Decrypted phone (unlock bootloader)
2-Root
3-Flash TWRP
4-Flash lean kernel
After these steps no issue with data. Everything working.
5-Started installing apps/configuring phone. Restarted phone several times during this process. Noticed after restarts that LTE wouldn't come up. Toggled airplane mode to fix. Eventually no service after restarts.
Re-flashed stock image, no root, no custom recovery, stock kernel. No service at all. Confirmed that SIM still works in different device.
I am aware that some N6 custom ROMs have data issues with Verizon. I had not seen anything reported with the stock image.
Has anyone experienced this?
Any help is greatly appreciated.
Thanks.

touch-screen freezes at lock screen

hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,

It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.

i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.

Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.

schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.

they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.

About phone > Software Info > software version will will say h81110n if on 10n.

Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...

Android 7.0 Call Problem

Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie

I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it

Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie

aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.

Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie

I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.

none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me

I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.

stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well

Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!

Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie

Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie

aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?

SM-T817W info for root and custom roms - INPUT needed please

I currently use the SM-817W version and using the following get root:
Flashed stock Android 6 image
Flash twrp_3.0.2-1_sm-t810.tar using latest Odin
Flash latest SuperSU sytemless
Boom everything works (lte, wifi, sound, camera)
Here are my questions:
Using the same recovery it lets me flash any 810 roms and they work fine (even Nougat versions) except the LTE since the 810 is a wifi only tablet. I see no problem here.
Now I flashed TWRP_3.0.0-1_sm-t815.tar so it would let me flash 815 roms that have LTE. Every rom I flash does not detect the SIM card. Just says it is not inserted. I can obviously get back to my initial setup and have everything work, but would love to use Android 7 on this thing.
Does anyone have any ideas on what I can possibly do to get SIM working?