Database Info

Can not connect to the camera. Still no solution? CM10.0.

Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).

Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix

bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.

Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?

CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol

Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.

CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever

dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?

If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch

dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium

bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time

Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.

CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?

Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.

CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.

Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/

dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium

TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.

[Q] Did updating to the latest CleanROM handle everything with regard to my baseband?

This is a little confusing so bear with me.
I installed CM for my S3 and ended up reflashing the modem to fix SMS. Eventually I noticed there were a lot more issues(GPS, signal, etc) with the phone and have went back to CleanRom (Stock-Root-I535VRUCML1-De-Odex-V2.zip) though the bars still seem a little low. I'm guessing I need to update my modem and I saw a few threads in the archives over at Scott's about the ML1 modem (d2vzw_ML1_modem.zip) can I just flash that file and everything will be fine?
Right now the baseband is I535VRBMB1. If I need to update it what should I update too? Also are there any good 4.4 alternatives? Could I go back to CM mod and flash this ML1 modem and have a good experience? Or are the modem issues I experience with CM mod just unavoidable?

Bump. Anyone have an answer?

MF1 is the commonly recommended latest unlocked radio/firmware. (You MB1 is clearly much older.) You can add the ML1 radio on top of this, but don't add the entire ML1 firmware (which includes the locked bootloader).
mastamoon has the MF1 firmware (which includes radio) on his ROM thread here: http://forum.xda-developers.com/showthread.php?t=2569769 I would suggest starting there, and then you can consider applying the ML1 radio-only which can be found here: http://forum.xda-developers.com/showpost.php?p=54520377&postcount=1343 (since invisiblek.org is down)...
At least this is how I understand it to be. I'm running the ML1 radio on the MF1 firmware on stock, rooted, BL-unlocked...
EDIT: Mind you, this assumes you're staying unlocked. Putting in an older FW/baseband on a locked BL phone can cause a brick. I expect you don't have this situation, as you were running CM (natively? or on safeboot?)... so you need to be clear on what you have, and where you want to go...

schwinn8 said:
MF1 is the commonly recommended latest unlocked radio/firmware. (You MB1 is clearly much older.) You can add the ML1 radio on top of this, but don't add the entire ML1 firmware (which includes the locked bootloader).
mastamoon has the MF1 firmware (which includes radio) on his ROM thread here: http://forum.xda-developers.com/showthread.php?t=2569769 I would suggest starting there, and then you can consider applying the ML1 radio-only which can be found here: http://forum.xda-developers.com/showpost.php?p=54520377&postcount=1343 (since invisiblek.org is down)...
At least this is how I understand it to be. I'm running the ML1 radio on the MF1 firmware on stock, rooted, BL-unlocked...
EDIT: Mind you, this assumes you're staying unlocked. Putting in an older FW/baseband on a locked BL phone can cause a brick. I expect you don't have this situation, as you were running CM (natively? or on safeboot?)... so you need to be clear on what you have, and where you want to go...
Click to expand...
Click to collapse
Thanks a ton. Yes I'm staying unlocked and I was running CM natively. Downgrading the radio was a fix to a problem a lot of people in my area had with CMs radio. I'll look into it more I guess. Going back to CleanRom was just an attempt to solve the problems CM seemed to be causing me.
Presently I have Cleanrom 8.2 http://forum.xda-developers.com/showthread.php?t=1832070 I'd like to go back to 4.4 since it felt like I got better battery life. So I'll take a look at some of the various things on the forum. I don't know if putting 4.4 on the S3 at this point is just going to cause issues or what exactly.

[MODEM][d800] KK Modem Patched with 10D Radio (SMS Send Bug Fix)

20C Baseband with 10D Radio
SMS Send Bug Fix
!!d800 Only!!​
Edit (2015.05.12) - I have dumped and posted d80020y modem to my website. It seems that 20y might have fixed this issue. I have been using it for a day or so now and have not noticed this bug. You may wish to try that modem before this one.
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: ROMs that require the KK Modem (for rotation to work) cause SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
https://www.gregtwallace.com/lg-g2/d800-modems/
(It is the Modded One - Baseband: D80020C; Radio: D80010D)
Install:
1) Copy .zip and .md5 to the root of your sdcard.
2) Reboot into TWRP.
3) Install -> Select .zip File.
4) Check "Zip file signature verification." (File is properly signed.)
5) Swipe to install the zip. (MD5 and Signature should verify and modem should install.)
6) Wipe cache/dalvik (for good measure.)
7) Reboot System and Enjoy!
Note: In "System Settings" under "About Phone" -> "Software Information" the Baseband version will be listed as ending in ".190034". This is the 10D baseband.
10D & 10O Baseband Rev: M8974A-AAAANAZM-1.0.190034
Default KK Baseband (20c) Rev: M8974A-AAAANAZM-1.0.190082
This Patched KK Baseband Rev: M8974A-AAAANAZM-1.0.190034
Please respond with any issues, etc.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal

Reserved

So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?

c_brown93 said:
So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?
Click to expand...
Click to collapse
No, this will not work for ROMs based on the old source (e.g. CM11).
This only works for KK based ROMs. It allows KK based ROMs to be fully functional, while still using the old baseband (radio).

This looks promising, I'll provide feedback once I return from work tonight!
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
I'm running Lam Hoang G3 ROM on D800 but it should still be fine

Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.

bps119 said:
Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.
Click to expand...
Click to collapse
You're welcome.
XERO_Racer said:
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
Click to expand...
Click to collapse
This isn't anything fancy. It is exactly what it professes to be. All of the KK modem files, except the 10D radio files were swapped in. So if you had any other 'better' things on 10D vs. the KK modem, you might get them in this, but probably not.

Used this modem all day today. No issues. Didn't have the SMS issue at all.

blastagator said:
Used this modem all day today. No issues. Didn't have the SMS issue at all.
Click to expand...
Click to collapse
You think this will help with reboots caused by low LTE signal?

RenderBroken said:
You think this will help with reboots caused by low LTE signal?
Click to expand...
Click to collapse
I've never had that problem, so I have no idea.

blastagator said:
I've never had that problem, so I have no idea.
Click to expand...
Click to collapse
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!

The sending delay bug was very annoying, I just flashed it and will report back if there are any issues!

RenderBroken said:
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!
Click to expand...
Click to collapse
To be honest, I'm not 100% sure. It's easy enough to figure out though. Usually the ROM post says which to use. If not, you can just flash one of the modems, if your sensors work, you're using a modern that is compatible with your ROM. Easiest sensor to check is rotation. Open Maps and your gps blip will have an arrow showing your rotation orientation (compatible) or there won't be an arrow (wrong modem).

OMG Thank you SO much!
blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
I have been waiting for a solution for this problem for so long. Downloading now. If this works I would be more than happy to donate. I love the CloudyG3 roms, but the issue with SMS getting stuck in "sending" has been a complete headache for me.

blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori kernel?

I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.

joeynox said:
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori?
Click to expand...
Click to collapse
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
phatmanxxl said:
I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.
Click to expand...
Click to collapse
This modem is not intended for CM11. CM11 is not stock KK based.

blastagator said:
I believe the bug is a part of the KK radio and ROM independent..
Click to expand...
Click to collapse
thanky you for responding. will i have any issue if i use this with dori kernel?

blastagator said:
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
This modem is not intended for CM11. CM11 is not KK based.
Click to expand...
Click to collapse
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.

joeynox said:
thanky you for responding. will i have any issue if i use this with dori kernel?
Click to expand...
Click to collapse
Kernel and Modem should be independent and thus not cause a problem, but I don't know for sure since I haven't done it.
phatmanxxl said:
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.
Click to expand...
Click to collapse
Oh, okay

[Q] Why am I not consistently connecting to LTE

Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!

iFrostyy said:
Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!
Click to expand...
Click to collapse
Are you stock? S-off? Which firmware are you on?

brholt6 said:
Are you stock? S-off? Which firmware are you on?
Click to expand...
Click to collapse
I am s-off and I am on a GPE 5.0.1 ROM.

iFrostyy said:
I am s-off and I am on a GPE 5.0.1 ROM.
Click to expand...
Click to collapse
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk

dottat said:
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.

LibertyMonger said:
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.
Click to expand...
Click to collapse
If you flashed the vzw ruu you are no longer on custom firmware.

dottat said:
If you flashed the vzw ruu you are no longer on custom firmware.
Click to expand...
Click to collapse
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.

LibertyMonger said:
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.
Click to expand...
Click to collapse
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.

OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!

Croak said:
OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!
Click to expand...
Click to collapse
Think that horse was beat dead already lol
Sent from my SM-T320 using Tapatalk

dottat said:
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.
Click to expand...
Click to collapse
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.

LibertyMonger said:
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.
Click to expand...
Click to collapse
It was made for the gpe version phones. They weren't sold for vzw.

dottat said:
It was made for the gpe version phones. They weren't sold for vzw.
Click to expand...
Click to collapse
Yeah I think most who are using it are either lucky or do not care or notice the dropped, weak signals. I've tried everything more than once to get it working right and the results are always the same, it acts like it's the wrong firmware, cause it is lol. Some claim to have the same issues but ignore them. I need my phone to work no matter what ROM it is. Thanks for all your help bro I see you are willing to help us when in need, that is greatly appreciated. I hope users send donations your way, I sure will once i get ahead again.

Have you set your APP correctly.

So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.

kj13569 said:
So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.
Click to expand...
Click to collapse
When you get the red triangle, you press volume up and power to enter stock recovery. Keep practicing.

LTE drops on and off
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?

Flylowguy said:
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?
Click to expand...
Click to collapse
That signal drop off issue happens to me on gpe ROMs. So far all the cm12 ROMs out there have had a perfect signal with good speeds for me. I think the signal drop off issue is something to do with the gpe ROMs.
Currently running blisspop newest nightly with 4.4.4 straight from RUU.

Suddenly extremely poor reception

I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!

toohsieh said:
I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!
Click to expand...
Click to collapse
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.

silentcovenant said:
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.
Click to expand...
Click to collapse
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!

toohsieh said:
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!
Click to expand...
Click to collapse
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.

silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
Well, stock is 4.4, but when you use the stock CM updater you'll be brought to CM12, 5.0.2. You don't have to stay on 4.4

silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)

toohsieh said:
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)
Click to expand...
Click to collapse
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4

silentcovenant said:
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4
Click to expand...
Click to collapse
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.

toohsieh said:
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.
Click to expand...
Click to collapse
The stock version they gave me was: XNF9XBS28K

silentcovenant said:
The stock version they gave me was: XNF9XBS28K
Click to expand...
Click to collapse
I can't say I've ever seen that version before but it looks like someone else had the same issue: https://forums.oneplus.net/threads/xnf9xbs28k-ota-updates.315441/