yashsingh1/xdaforums huggingface dataset:
[Verizon HTC Droid Incredible 4G LTE] bvirg:
I ended up with a borked modem after accidentally accepting the CM automatic update. Flashing back to a recovery did not work unfortunately. I am trying to flash back to the stock firmware to accept the OTA update to hopefully fix the radio, however I can not locate the stock recovery image (recovery_signed.img). All old links in the forums no longer seem to be valid. Anyone have a link where I can download it?

---------- Post added at 05:12 PM ---------- Previous post was at 04:32 PM ----------

Ok, looks like I was able to find it from the RUU. After extracting the stock recovery, flashing it, performing factor reset, and rebooting it looks like I am making progress.
[Verizon HTC Droid Incredible 4G LTE] kg_jettaIV:
Updated to 10.2.1 last night and all was well until I rebooted tonight and couldn't get connected to LTE or WiFi. After a battery and Sim pull and turning airplane mode on and off multiple times I am now connected to Verizon but my WiFi won't turn on. It toggles to the on position shortly then goes back to off. Any ideas?

SOLUTION: http://forum.cyanogenmod.com/topic/87474-1021-wifi-wont-turn-on-since-ota-update/

Per the above link for the same issue on the One XL I downloaded the 10.2.1 zip from CM directly, extracted and flashed the boot.img and it fixed the issue. This may be something that needs to be addressed in the OTA update method.
[Verizon HTC Droid Incredible 4G LTE] nconroy1:
Running 10.1 and I'm having problems with SD card being unavailable. I followed instructions to set path directory to /storage/ but still won't work. Used es file explorer.

The strange thing is I got this to work before and after reinstall of ROM can't get it to work. Any suggestions please?
[Verizon HTC Droid Incredible 4G LTE] therreid:
Been on 10.2.1 for a few days now. It seems like a decent ROM except for a couple issues. GPS does not function well at all. Trying to use Google Maps for navigation was terrible. It also seems like the radio does not give me as strong signal as stock. Any thoughts on these issues?

Thought about going up to a KitKat rom, but that would likely be more unstable.
[Verizon HTC Droid Incredible 4G LTE] wmuflyer:
For the GPS the early posts on the dev thread discuss GPS issues. You need to backup your current system, restore a sense based rom and turn on all location services, confirm those are working (test out maps or another app), then restore your 10.2.1 rom. Radio signal is most likely just as good just displayed accurately stock tends to show more bars for the same signal.

As for KitKat I've been using CM 11 since early January and have had few issues, nothing that makes me consider trying anything else it's just smooth.
[Verizon HTC Droid Incredible 4G LTE] therreid:
I may have to give KK a try. Thanks.....
[Verizon HTC Droid Incredible 4G LTE] JokoInteractive:
Trouble upgrading to 10.2.1

I'm S-ON, HtcDev unlocked, been running a CM 10.1 build since 3/31/2013.

I tried upgrading to 10.2.1, but hit a reboot cycle at the white HTC screen, haven't seen the CM logo.

My install steps:

- TWRP backup

- factory wipe and system wipe

- installed CM 10.2.1 and GAPPS at the same time using the queue

- from fastboot did the manual boot.img flash.

Please let me know if there's anything else I can try, before I go back to my backup (which will hopefully still work). While I'm here, is there any reason why my background apps would always get killed on my March 2013 build? Seems like a RAM issue, but I didn't want to mention it without trying the newest builds.

Thanks!

FIREBALL PVT SHIP S-ON RL

RADIO 0.98.09.0602_2

HBOOT 1.02.0000
[Verizon HTC Droid Incredible 4G LTE] JokoInteractive:
Well, I tried going back to 10.1, and now my internal storage is unrecognizable, either through Windows or the ROM. Android says it's unmountable, and would like to reformat it. I guess this is outlined as a rare problem in the dev thread, but I hit the issue, and now it seems like I'll have to format.
[Verizon HTC Droid Incredible 4G LTE] MJL99:
I was in the middle of replying but you said you already tried to flash the boot image? Are you sure it flashed? Normally boot loops with s on are because boot image didn't get flashed. So currently I'm not sure what the issue could be.

Is there a reason why you want to stay with 10.2? Cm has a kit Kat version released that runs well on the latest nightly.
[Verizon HTC Droid Incredible 4G LTE] JokoInteractive:
I guess I can try KitKat. It just seemed all the build instructions were for 10.2, and I didn't want to risk running into problems with something which wasn't well tested. Plus I couldn't find a link to gapps for 4.4.

I also thought it was the boot image not flashing, but I tried that several times. Is there a way to tell whether it flashes successfully? I extracted the boot.img from cm-10.2.1-fireball.zip, and did the fastboot thing after the successful rom and gapp install.

Another problem related to my missing internal storage. I can't seem to get access to it, even from TWRP mount, and windows won't give me the option of formatting it.

Thanks for your help, really appreciate it.
[Verizon HTC Droid Incredible 4G LTE] MJL99:
Sounds like your boot image is flashing ok. What twrp version are you on? It might be an issue that requires updating to the newest twrp or cwm. Either can be found at their respective sites. You can also use their apps to flash but not sure if you have a running phone sure to your storage issue
[Verizon HTC Droid Incredible 4G LTE] JokoInteractive:
Yeah, I can get the phone up and running on my old TWRP backup, but internal storage is still missing, and I can't seem to fix it.

I was using the March 2013 build of TWRP, so maybe when I have time again I'll update TWRP to 2.7 and try again. Thanks!
[Verizon HTC Droid Incredible 4G LTE] JokoInteractive:
I can't seem to get any recovery working except for my original TWRP from March 2013. I've tried TWRP 2.7, TWRP 2.7c, most recent CWM. For each I would flash the recovery.IMG within fastboot, and do a fastboot erase cache for good measure. I can only ever get to the white HTC screen, then boot loops from there.

I tried the stock recovery, since I read somewhere that you can't update TWRP unless you're on stock recovery (?!), and it behaves a little differently. It will go to a black screen with a green HTC-ish icon, and will eventually boot to the Welcome screen. But I still have no luck getting a different recovery on after that.

In fact, I get the boot loops with my original TWRP build as well. However, if I try to boot to the OS as normal after flashing the original recovery, I can get to the CM logo, which never goes away. Then if I do a battery pull, I can then boot into that original recovery. This method doesn't work with any of the other builds, though.
[Verizon HTC Droid Incredible 4G LTE] phoenix220693:
Shows less RAM than is available

I am using an lg optimus p935 unrooted using the p930 firmware. my device originally said 1gb ram but after installing cyanogen mod it says 742 mb. Its not very noticable during normal activity but i can see a difference in performance when gaming. Does anyone have any ideas?

oh btw when i run some full screen apps like subway surfers i can only see a tiny line at the top and the rest of the screen is black. sometimes if i flip the phone upside down and run it it might work.

Running cyanogenmod 10.1.3
[Verizon HTC Droid Incredible 4G LTE] megaghostgamer:
both the LG P935 and Inc 4 come stock with 1gb of Ram. Not all of it is going to be available to the user. Basically on your p935 it's telling you that your phone has 1GB of Ram inside the phone. On your Inc, it's telling you that you have 742mb of the 1GB usable for your needs. This is as far as my knowledge, I could possibly be wrong.
[Verizon HTC Droid Incredible 4G LTE] phoenix220693:
i dont believe that was always the case

When i was using the stock rom it would show 300 and something mb in use and 700 and something free but now it shows around 300 in use and 300 free.i only realised the decrease after i installed cyanogenmod. Maybe it could be a hardware issue.
[Verizon HTC Droid Incredible 4G LTE] SnoStorm:
Hi all,

I've been running cm 10.2.1 on my fireball and I love it. I am having one particular issue.

Now judge me all you want but I am a snapchatter. There is an issue with CM and snapchat which doesn't allow front camera usability. Back camera works fine but the front is a no go. When I switch to the front camera it freezes the screen or is completely black.

Would something like installing a different camera.apk work? (and how would I do so correctly) Snapchat was working when I was using Viper so I figure its something within CM.

Any replies with help are greatly appreciated! Thanks!
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
Garbled speakerphone appears to be fixed. Good work. No other regressions...will report back if I find any.
[Verizon HTC Droid Incredible 4G LTE] TheGOAT232412:
I would really like to thank mdmower for sending me in the right direction for my ADB setup. Worked like a charm, thanks again! So after restoring my phone back to stock and completing the "borked radio" procedure, I downloaded the CM10/16 nightly and flashed it with GAPPS 08/13 I got a series of boot loops. A battery pull fixed that issue for a bit just so I could get through setup. I immediately notice that I was once again not able to send txt messages and that my calls were hanging at "dialing". I took mdmowers advice on setting the CDMA subscription on RUIM/SIM and then reboot. I also tried that and once it booted up, I checked it and it was right back to NV. Just giving a little feedback, sorry that I am not able to produce a logcat at the moment.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Can you check that your network mode is set to LTE/CDMA/EvDo ?
[Verizon HTC Droid Incredible 4G LTE] TheGOAT232412:
Yup, that is what it was set on both times. It is odd because some reason when I first installed, I was on the phone for about an hour between calls and texting. I have no problem with data at all either, it just seems the phone calls and texting. After the first radio restore and the clean flash of the 10/16 nightly, it let me do any calls or text right off the bat.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Did you verify your radio was working in Stock before flashing CM again?
[Verizon HTC Droid Incredible 4G LTE] TheGOAT232412:
Yeah, I followed your instructions step by step in the op for CM.
[Verizon HTC Droid Incredible 4G LTE] Sum Dumb Guy:
Ditto on the NV

Followed the thread and I'm having I think the same problem. My CMDA subscription will change to RUIM/SIM but when I re-boot it goes right back to NV. PHone number is 000-000-0000.

I thought this issue popped up earlier and was fixed.
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
Instead of rebooting when you change the settings you can turn on airplane mode, wait a minute and turn it back off. I've had this issue at times too, but if you play with the settings for a little while and using airplane mode to see if it sticks, you can eventually fix it. Once you get it to stick you shouldn't have any issues updating to new nightlies unless you're flashing other roms in between. This isn't really the best way to solve the issue, but it works eventually: play with the settings. Try something like this: check off LTE/CDMA/EvDO/GSM/WCDMA and then check off RUIM/SIM...turn on airplane mode, wait a minute, then turn it back off and wait a minute. Then switch the settings back to what they're supposed to be and do the airplane mode again.

It's a really stupid way to deal with it, but I swear you CAN get it to stick if you fool around with it a little bit...
[Verizon HTC Droid Incredible 4G LTE] TheGOAT232412:
Thanks for the response, will give it a try tonight. Up all night last night getting my phone up and running again for today. I'll give it a try when I get off work.
[Verizon HTC Droid Incredible 4G LTE] Sum Dumb Guy:
This worked for me. Not the first time. Maybe I was turning airplane on/off too quickly. I ended up turning airplane on and forgetting about it for 30 min. Turned airplane off and phone worked.

Thanks,

J
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
Other caller can hear me very well now, but volume of my speakerphone is very low, even with my volume at max. It is not close to loud enough to be able to use as a speakerphone.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
I tried to do a sweep of as many volume adjustments as I could so I don't have to come back to this issue again. Here is a test build. A commit has been posted to gerrit, but I'm going to hold off on merging it until I get several confirmations that volumes are reasonable everywhere.
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
Great job. Call clarity is good and volumes are now good.
[Verizon HTC Droid Incredible 4G LTE] biodiesel.ufo:
Thank you. I flashed the 20131016 official nightly, but I still have the problem with the sound. The sound setting "Volume adjustment sound" is checked, and the screen shows the volume changing when I press the volume buttons, but I cannot get sound out of the speaker. Headphones is ok, but it seems like the sound works immediately after a reboot, but not after I have silenced the phone or used headphones. I've been lucky as my alarm has been silent all week, but I've still managed to make it to work on time.

I do have ringtones set for certain callers, they are still set, however when I receive a call from one it's the default ringtone, not the custom one.
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
Weird animation change in the last couple nightlies. You can reproduce it by going into settings and just opening one of the settings such as sound and hitting the back button. Just me or...?
[Verizon HTC Droid Incredible 4G LTE] Pete02:
If your talking about a sort of delayed screen out effect then no, it's not just you. I've noticed that the phone is not as snappy as it used to be too.
[Verizon HTC Droid Incredible 4G LTE] spectre559:
I recently tried 20131019 and 20131020 nightless. On both, I could not get WiFi to connect. Also, out of range networks were reported as "disabled". I'm back to 20131018 for now. Any commits that might have caused this?
[Verizon HTC Droid Incredible 4G LTE] MJL99:
Wi-Fi is connecting on my just fine. I do run into times where Wi-Fi is on and sees the network but won't connect despite a good signal. Is that what you're referring to? An airplane mode switch on and off remedies this problem for me tho.
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
May have spoke too soon. Clarity of speakerphone is good. However, the persons on the other end have complained that they can barely hear me while on speakerphone unless I have my phone right next to my face. I replicated it with my office phone, and it's true. If my phone is on speakerphone, and sitting on my desk about 14 inches below my face, very little volume comes through on the receivers phone.
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
Can confirm. Used speaker phone today and the distance was about the same as you describe and the other person didn't answer me until I moved it closer. They couldn't hear until I picked it up closer to my face.
[Verizon HTC Droid Incredible 4G LTE] Spoojaka:
Bluetooth non-functional

Hello all,

BIG SHOUT OUT TO MDMOWER! :good::good::good::highfive::good::good::good:

Your hard work on our device has been TRULY invaluable for me.

Just switched to 10.2 running 10.2-20131018 nightly.

kernal 3.4.66-g05fb86c

having trouble with bluetooth not wanting to activate, i use it daily with my lg hbs730 headphones (Invaluable buy them) and tablet talk with my nexus 7.

i attempted to do the switch by the gps recovery method (install stock rom turn everything on) but no luck.

any suggestions gentlemen?
[Verizon HTC Droid Incredible 4G LTE] MisterNikky:
Hey I'm running 10.2-20131018-UNOFFICIAL and I noticed the Wifi hasn't been connecting well. I live on a college campus where I move around alot, so that may have something to do with it. But ever since I updated it's been extremely difficult getting it to connect to my campuses wifi.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
When you say bluetooth wont activate, do you mean toggling the on/off switch for bluetooth causes the switch to fail to turn on and stay on? I tested this with the equivalent of 10.2-20131023 and it activates here. Can you try this latest nightly (make a backup of your existing ROM fist though because I'm not sure whether a RIL commit was made in time for the build-bot to catch last night). If the problem still exists, please post a logcat and kmsg.
[Verizon HTC Droid Incredible 4G LTE] void4ever:
I have whats possibly a silly question but I've been out of the game for a while.

I was lucky enough to get an HTC unlock of my device before they removed it, so i am unlocked but not s-off. I've been running a senseless rom from Hasoon2000 for over a year now.

I'd like to give CM a go now that the flickering issue has been taken care of. I remember a while back there was an official update from HTC for this device which i believe included a radio update among other things. I never touched it since Hasoon2000's rom was working so great for me.

So the question is, do i need to flash the official HTC update before trying to play with CM to get whatever possibly radio firmware updates were released, or is that all included with the CM rom as well?

Void4ever
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Yes, you should update since CM relies on the most recent radio firmware. Before you do, dig through your email and locate Unlock_code.bin. You will have to re-lock your device before running the update, but the unlock token should still be usable after update. RUU
[Verizon HTC Droid Incredible 4G LTE] void4ever:
I really appreciate the quick response. One more question which you may or may not be able to answer. Since the old ROM i'm running now was made with the old radio in mind, would updating basically take away my option of swapping back to my old ROM should i not find one of these nightly's a good DD?

I've been keeping up on the dev thread and this one, and i think the latest nightly would probably be fine as a DD. I rarely use my speakerphone so those issues don't worry me, and the wifi thing mentioned doesn't really bother me either. But as everyone knows having a backup to goto is never a bad thing.

Void4ever
[Verizon HTC Droid Incredible 4G LTE] mdmower:
You will not be able to revert to a ROM based on 1.43. Really though, between Viper or Stock Rooted 2.17, you have worthwhile alternatives to CM. I should say that a day or two of patience if you're most interested in CM would be advisable while I iron out remaining RIL issues due to the recent overhaul. Ultimately, the radio should work better, or at the very least as well as it ever has in the past in CM.
[Verizon HTC Droid Incredible 4G LTE] void4ever:
I can certainly wait a few days. Been waiting for the flicker to be fixed because i didn't want to risk it, so whats a few more days!!!

Thanks very much for the info.

Void4ever
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Use Root Explorer or ES File Explorer to edit /etc/snd_soc_msm/snd_soc_msm_2x on your device. Find the section labeled

SectionDevice
Name "Speaker DMIC Endfire"
Comment "Dual MIC Endfire Tx device"

In that section, adjust the volume of DEC4 and DEC6 simultaneously in very small increments (like +/- 2 or 3 at a time). If I'm not mistaken, DEC6 corresponds to the top mic and is used for noise suppression while DEC4 is the bottom mic. These are usually adjusted together, but you may find it necessary (unlikely, but possible) to pull them slightly out of equilibrium with each other.

After adjustments, save the file and restart the phone.

Once you find a mic volume that satisfies the person on the other end of the line, you can share it here and I'll confirm.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
I see what you mean, and it looks like disabling hw overlays in dev options brings back expected behavior. logs aren't very telling, but i'll look into it.

Edit: if you know the build number where this first showed up, it would help quite a lot.
[Verizon HTC Droid Incredible 4G LTE] xdadevelopers-user:
Secure Element / Google Wallet / ISIS

One thing that keeps me from using CM as my daily driver is the apparent lack of support for ISIS.

Thinking that maybe ISIS is more proprietary than Google Wallet I decided to have a go at setting up Google Wallet tap-to-pay in the 1023 nightly of CM 10.2.

The first thing I did was confirm which devices on Verizon's network support Google Wallet tap-to-pay. I found that the Galaxy Nexus is supported and has been reported to work. So, I modified the build.prop changing the following lines:

ro.product.name=htc_fireball
to
ro.product.name=takju

and

ro.product.model=Incredible 4G LTE
to
ro.product.model=Galaxy Nexus

I then cleared data on Google Wallet and rebooted. Upon reboot Google Wallet no longer complained that htc_fireball/Incredible 4G LTE wasn't supported. However, when I launch Google Wallet and select my Google account it just hangs with the message "Just finishing up a couple of things".

Logcat reveals that it IS attempting to access the secure element.

10-23 10:39:56.747 I/LockSecureElementIfNecessaryTask( 3105): task started
10-23 10:39:56.787 I/NfcExecutionEnvironment( 3105): NFCEE.open locked: stack=[SecureElement] openTid=194 nfceeOpened=false tryLock=0ms
10-23 10:39:56.827 I/NfcExecutionEnvironment( 3105): NFCEE.open ++: stack=[SecureElement, SecureElement] openTid=194 nfceeOpened=false references=2
10-23 10:39:56.867 I/NfcAdapterExtras( 3105): Wakelock WakeLock{41f1e9f0 held=false, refCount=0} acquired 1382546396881 ms
10-23 10:39:56.867 D/NfceeAccess( 1254): Granted NFCEE access to com.google.android.apps.walletnfcrel (wildcard)
10-23 10:39:56.877 D/NfcService( 1254): NFC-EE OFF
10-23 10:39:56.907 D/NfcService( 1254): NFC-C ON
10-23 10:39:56.937 I/NfcAdapterExtras( 3105): Wakelock WakeLock{41f1e9f0 held=false, refCount=0} released 1382546396950 ms elapsed 69 ms
10-23 10:39:56.937 I/SecureElementManagerImpl( 3105): Card emulation disabled.
10-23 10:39:56.937 I/NfcExecutionEnvironment( 3105): NFCEE.open ++: stack=[SecureElement, SecureElement, SecureElement] openTid=194 nfceeOpened=false references=3
10-23 10:39:56.937 I/NfcExecutionEnvironment( 3105): NFCEE.open ++: stack=[SecureElement, SecureElement, SecureElement, CardManagerApplet] openTid=194 nfceeOpened=false references=4
10-23 10:39:56.967 W/NFC-LLC ( 1254): bad LLC length byte 51

But I don't know what, if anything, I can do to get past this and actually see it work.

Any help would be greatly appreciated.

Thanks,

-xdadevelopers-user
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
80 for both seems to be good.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
We've already had this discussion. This is an unsupported modification to stock CM, so you will need to find another developer to help you (not in this thread).
[Verizon HTC Droid Incredible 4G LTE] mdmower:
I'm leaving it up to you to ensure other audio functions are not compromised with this change. Test as many things as possible that use the microphone. Also, ensure distance between you and phone doesn't result in new issues like distortion when too close.
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
Will do. Will report back later today or tomorrow.
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
I believe it was the 10/19 build.
[Verizon HTC Droid Incredible 4G LTE] ZackehSoul:
In the OP there are known issues for official builds, but not for unofficial...

Meaning unofficial doesn't have these bugs, or just left them out of the OP?
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
safe bet if the official builds have bugs, the unofficial builds will have them too. most of the time the unofficial builds are custom commits that the OP wants us to try before pushing them to the official source.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
If you could test 10/18 just for this it would be appreciated. My local source tree has all kinds of crazy going on right now and I don't want to go back in time.