yashsingh1/xdaforums huggingface dataset:
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
[MENTION=4258433]mdmower[/MENTION]

As I said, I'm going to try the "non-developer" approach you sorta-recommended someone to try. I just ran the RUU and got my phone all setup. But I notice you said "run the ruu AND a factory reset." Wouldn't that be redundant, or does factory reset do something different? I highly doubt this will work, but if I'm going to attempt it, I'd like to try and get it right. Should I factory reset as well? Either way, i'll run it like this for a couple days and report back with results.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Actually, the factory reset is not redundant to the RUU. As a specific example, the borked radio condition is remedied by a factory reset, but not by an RUU.

You're not alone in this endeavor. I RUU'd my phone last night and have been running stock (without even root *gasp*) since then. This morning, for whatever reason, I decided to do a 1hr battery pull as well, 'cause I'm all about superstition at this point. I will run stock until Friday evening most likely, and then will go directly to cm-10.2. My observations so far:

1) In the mdm-builds there was still some flicker (as you've pointed out before) on darker grays. The flicker is absolutely gone as of today and I can't get it show up in any application on stock. This helps reassure me that permanent damage has not been caused to the display.

2) Things "just work"... this both irritated and motivated me.
[Verizon HTC Droid Incredible 4G LTE] cyberkeeper1:
SMS/MMS NOT working in CyanogenMod 10.2; Data Icon not used; Signal Strength wrong...

this explains why when i ran an RUU to fix a radio, it didn't fix it. i didn't know to run the factory reset. haha. installing cm10.2 fixed the radio issue though. i went from not working in stock to working without trying in CM 10.2.

Ok, so the reason i am posting is because i am having a few noticeable issues. First and most important, SMS/MMS is NOT working. Oddly enough, phone calls and even Edge works fine, but again, no SMS/MMS. i can't seem to find the APN settings in the ROM... where would i find them?? i had them in stock but i cannot find these settings anywhere at all. Here is my current network and config:

Network Mode:

GSM/WCDMA/LTE

Network Provider is T-Mobile Prepaid with a SIM card.

I dialed the 4636 secret code to manually set the frequency band as well as radio type. this got me connected to internet and calling, but no texting... I should add that the internet is EXTREMELY SLOW... it was acceptable somewhat on stock but things often time out on EDGE while running this. i rely on texting 90% more than anything else on the phone, and I just got the service yesterday.

Phone Boot Info:

S-OFF, Unlocked, Recovery= PhilZ Touch5 (CWM 6.0.3.7)

Current OS:

CM10.2 NIGHTLY 09/12/2013. Currently i have zero issues with sound OR screen flicker or distortion.

Last Issues:

Signal Strength meter is highly inaccurate. it is measuring -120dBm even though i know i have close to full signal (higher than -60dBm; -59dBm is a higher value on the number scale) OH and according to the phone, it isn't showing that any data is in use (i.e. no E or 3G/4G icon visible.)

Any insight on this? if this is a widespread bug, we should figure out what the problem is. i have no idea myself yet, but i just need my texting working. :/

---------- Post added at 12:41 AM ---------- Previous post was at 12:01 AM ----------

UPDATE: It looks like i am receiving texts but not able to send. I JUST tested this with a couple of friends. nothing goes outbound but all of theirs work for incoming. I thought that might be important to mention.
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
I still have issues with the lock screen. It has been since the cm-10.2-20130904 release. After reboot, lock screen works fine(i am using a pattern lock), but after some use the lock screen fails to show up on screen wake. By some use, I mean somewhere before 4 hours, and it is probably a function of screen wake's rather than time. I have wiped and reflashed with cm-10.2-20130911 and it is still happening. I just flashed cm-10.2-20130913, but no results yet. Wife has the same phone, same setup, same issue.
[Verizon HTC Droid Incredible 4G LTE] MJL99:
That's strange. Ever since you mentioned this issue I tried running the pattern unlock and decided to keep it running. I haven't had one issue yet with it not working. I'm using a 4x4 pattern if that makes a difference. I'm currently on official nightly 9/11 also.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Have you been updating the kernel with each release (if S-ON or using the stock HBOOT instead of the engineered version)?
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
S-Off. Using the updated kernel.

It started happening again in 9/13 release.
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
I decided to flash the nightly early. I couldn't stand stock and I figured what difference is there going to be between 1 day or 2 days. So after the RUU and factory reset, I ran stock, unrooted for about a full day. After flashing the nightly, I turned up brightness and noticed some very slight flicker after about 30 mins. This was mild, like I would see on the mdm builds. Over time the flicker got worse. Seemed to be just as bad as usual. You can mask it for a time by lowering brightness, but it's no use in the long run. There has to be a way to beat this, if some phones don't experience it, then it can't be entirely kernel related can it?
[Verizon HTC Droid Incredible 4G LTE] Pete02:
I use the pattern lock screen all the time. I keep it on mostly for work and turn it off when I'm not but I've never had any problems with it not working properly. I use the 5x5 pattern.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
I did not fare any better today. To say I was disappointed would be a severe understatement... in that it would fail to recognize the holes in my drywall, flipped tables, and shattered glass everywhere. My motivation to keep dealing with this phone just plummeted.
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
I think we might be stuck until an official jelly bean update comes out. I'll probably have a new phone by the time that happens. I was even considering jumping over to the moto x. $140 isn't bad at all.

---------- Post added at 07:26 PM ---------- Previous post was at 07:15 PM ----------

Oh, by the way. It's not possible to build an unofficial 4.3 build with the old kernel?
[Verizon HTC Droid Incredible 4G LTE] Pete02:
Don't be too hard on yourself man. You've done more for this phone than anyone else and as far as you've gotten us it's still greatly appreciated. Would it help you if you had another phone that doesn't experience the flicker to make comparisons against?
[Verizon HTC Droid Incredible 4G LTE] brianr134:
I remember a few of the items you compared when you were looking at phones that flicker vs those that don't. Can you post the comparisons that you have done if you wrote them down?
[Verizon HTC Droid Incredible 4G LTE] zhaotiantian:
You can help our fix sense5 and sense4 do ?
[Verizon HTC Droid Incredible 4G LTE] sx10:
I just flashed the 9/12 nightly, which is the first non stock ROM I've put on my fireball. I do have the camcorder audio noise, and I do have the flicker. Kind of a bummer, but I'll give your mdm build a try next.
[Verizon HTC Droid Incredible 4G LTE] times_infinity:
[MENTION=4258433]mdmower[/MENTION]

Apparently flickering is fixed for us on dlx? Don't know of it'll help though.

EDIT: Apparently this is the commit?

Like I said, not sure if it would help. Worth a shot taking a look though?

http://review.cyanogenmod.org/#/c/50278/
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
This peaked my interest. Does anyone know if this is something that is automatically merged into newer builds, or is this something mower has to look into specifically and push to our device's builds?

If it is automatically merged into the newer builds, then it fails to stop the flickering.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
AFAIK this was not merged into our source. i cant find it in the change log at all.

edit: this was for the M7 kernel source we use the MSM 8960 common for ours. for this to be included we would need to submit it as a patch for us.
[Verizon HTC Droid Incredible 4G LTE] scottyb96:
Flashed the 8/24 release, dirty, and lock screen works fine. Strange.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
They don't need to be "added" because they weren't missing in the first place: L33 and L120. Thanks for the suggestion though [MENTION=3103747]times_infinity[/MENTION].
[Verizon HTC Droid Incredible 4G LTE] vazersecurity:
WiFi is having issues. Wiped data and reinstalled and still doing it. anyone else?

--

Edit: fixed somehow in latest update.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
Does placement matter? On theirs lvs7 has it on ours it doesn't.
[Verizon HTC Droid Incredible 4G LTE] times_infinity:
[MENTION=4258433]mdmower[/MENTION]

Have you ever tried merging the Inc LTE into the M7 source? I know intervigil wanted to combine the two sources since they're not much different.

I wonder if that would make any difference.
[Verizon HTC Droid Incredible 4G LTE] jrior001:
In that commit its set to match all the other 8064 devices, in our kernel those lines are in a differnet location but match up with all the other 8960 devices.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
Cm10.2 9/15 and 9/16 won't let me send text messages. Anyone else have this problem?
[Verizon HTC Droid Incredible 4G LTE] Pete02:
So far I've gone from mdmower's 0901 build to the 0911 nightly and now on to the 0915 nightly. I haven't tried the 0916 build yet but everything still seems to be working fine for me. Just dirty flashed em all too. I sent some pic msgs last night and regular texts today but had no trouble at all.

On a side note I noticed last night that the flash now works while your in a call too. Very cool! :good:
[Verizon HTC Droid Incredible 4G LTE] mdmower:
This is another one of those "definitely not the problem, but let's try it anyways" ideas. I use the unlimited.io engineered HBOOT and get screen flicker. Has anyone checked whether screen flicker occurs when using the stock HBOOT?

Eventually, I will have a thread that summarizes both technical and non-technical attempts at resolving this issue, and put to test XDA's claim of being a "developer forum" by inviting real outside help. It'll take a while to write-up everything though, so be patient.
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
I've mentioned this before, but it was shot down as a dumb idea so I never attempted.

I also have another strange idea. Follow me here, cause I'm a little tipsy right now. So, when CM first came to this phone, some people had GPS problems, and some did not. The solution was to flash back to stock, enable location services and flash back to CM. Enabling GPS on stock first allowed it to function properly.

Now, if you google ''screen flicker CM'' or ''screen flicker AOSP'' among other things, you will see TONS of people recommend enabling ''force GPU rendering'' as a solution.

Now my strange idea is this: If GPS didn't stick unless it was enabled in stock first, maybe that ''force GPU rendering'' setting isn't functioning properly unless it's ticked on stock first before flashing CM. Thoughts? lol
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Of course just about any idea is worth testing (aside from maybe dunking your phone in the toilet), but I have significant doubts about the force GPU rendering setting carrying across ROM installs. As far as I know, it's not a setting which ever gets written to non-volatile memory. Don't take this as the end of the line answer though, test it and prove me wrong.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
to keep the thread less cluttered i when ahead and started a thread for a brain storming sestion to see if we can help fix the flicker problem some of you have been dealing with.

http://xdaforums.com/showthread.php?p=45765248#post45765248
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
That's good to gather some info but I just want to mention I tested the stock HBOOT last night and it did not make a difference.
[Verizon HTC Droid Incredible 4G LTE] brianr134:
Thanks mdmower.

Anyone willing to share the CM build info & a logcat starting at boot from a device with the flickering panel?
[Verizon HTC Droid Incredible 4G LTE] somerandomname1:
[MENTION=4258433]mdmower[/MENTION] how about this for another "let's try it anyway" idea:

Flashing the original RUU, the one before the update, then flashing CM.

Would that break anything? Would there really be any difference between doing this and what we already attempted with the most recent update RUU?

Obviously its a silly idea, but I'm willing to try anything. Would like to hear your thoughts first though.
[Verizon HTC Droid Incredible 4G LTE] mdmower:
I wouldn't suggest this, though with S-OFF, I don't foresee too much trouble attempting it. Just don't go S-ON or you're gonna have a bad time. I really think this will come down to a timing issue with the backlight -- so, a kernel side fix.
[Verizon HTC Droid Incredible 4G LTE] jrior001:
I don't know exactly what RUU's are available here but I know on Evita there were so many issues with the new kernel for people on the older 1.xx, and even on the 2.4x RUU's that h8rift basically mandated everybody to upgrade to newest 3.18 RUU. From looking around though I don't see where you guys ever got a 3.xx RUU. Is that correct?
[Verizon HTC Droid Incredible 4G LTE] MJL99:
Well wtf. I just noticed I have the screen flicker. It's only noticeable with brightness all the way up and with a certain grey showing on the screen. If I open YouTube app and slide out the left panel, it dims the background on the right side and I can see it flicker there.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
this is correct.

---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------

can not be unseen
[Verizon HTC Droid Incredible 4G LTE] lwinstead:
Well what the hell. I thought I'd try cm 10.2 Nightly from 9/11/2013, today. I'm currently on 10.1.2-mdm05. So I downloaded the ROM along with the GAPPS zip from 8/13/2013, and installed them via TWRP 2.6 after a full wipe. What do I get for my - admittedly insignificant - trouble? A boot loop that JUST. WILL. NOT. GO. AWAY. I reflashed. I wiped and THEN reflashed. I wiped, reflashed, and even separately applied the boot.img. After every restart it just boot loops. And yes, I DID make a backup before I started all this and just now restored it to a 100% working 10.1.2-mdm05 ROM, so I'm not SOL. But can anyone tell me why I was stuck in that boot loop? Ughhhhhh!
[Verizon HTC Droid Incredible 4G LTE] MJL99:
Not sure about your boot loop issues but I'd suggest not using 9/11 nightly. I had camera issues with that version. Not sure if a report was made for it but when I installed 9/14 the issues went away.

Did you make sure to download the correct gapps package to flash? I've read of people having issues with incorrect gapps being flashed. I had them when I first tried 10.2 cause of the wrong version.
[Verizon HTC Droid Incredible 4G LTE] lwinstead:
Yeah, I had the correct gapps for it, but I think I'll try again with another build, maybe 9/14 as you say. In fact, I really never tried to just flash the 9/11 nightly all by itself; I had always batched it with gapps. I'll try another build tonight and really get granular if I still have trouble.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
ive noticed in the last few builds, about 2 weeks or so, had problems clean flashing with gapps at the same time. i stopped flashing both at the same time and went back to flash cm boot reboot flash gapps.
[Verizon HTC Droid Incredible 4G LTE] lwinstead:
Well that didn't work. Last night I clean flashed 9/18 Nightly - all by itself, and it did the same thing. Boot loop ad nauseam.

Is there some way for me to see what's actually happening when it boot loops? Is there a log I can read?
[Verizon HTC Droid Incredible 4G LTE] eng3:
Just to report, I upgraded from mdm05 and am running with the 9/24 nightly and have not noticed any flickering issues. (camera seems to work fine too).

I plan to go on international travel planning to use GSM. Are there any known issues with 10.2 w/r to this? I have read reports of success with someone using the mdm builds, but haven't seen anything in the 10.2 area.
[Verizon HTC Droid Incredible 4G LTE] cyberkeeper1:
I have an official report to make. I don't know how to show logs or what not, but this is my experience. On the nightlies, my GPS does not work, and there is no icon for being in use. This is after proper reset instructions and making sure to lock on and enable all 3 GPS services in stock.

Also, upon a fresh install or wiping the dalvik cache, the phone enters a boot loop for several minutes. During this time, the boot animation appears to glitch while loading and suddenly freeze, and then crash and reboot. Only a battery pull fixes it. I imagine it clears the memory of errors. I am using the ENG hboot with the latest PhilZ touch recovery and latest nightly, as of today.

On the bright side, my screen doesn't flicker on the custom ROM, but does with stock a tad bit. It's totally backwards but it is what it is.

Things are missing from cm10.x that were present in cm7. Such as lock home in memory and lock messaging app in memory. I am requesting that home and messaging persistence be added as an option, if possible. I am finding that only after a few seconds after I leave an app, it is wiped from memory, thus having to start again with what I was doing. No I don't have the dev option to "kill the activity as soon as I leave it" enabled. Suffice to say, multitasking is not doing so well at the moment. Idle apps shouldn't be cleared from ram unless I go into recent apps and swipe it away myself.
[Verizon HTC Droid Incredible 4G LTE] cyberkeeper1:
Feature request as of nightly_9/28. The ability to choose whether or not notifications are linked to the main ringer volume are missing from the sounds menu in settings.

Things that aren't quite as they should be :

Apollo player makes my audio jump up and down in volume at random, with or without the DSP settings in use. It's literally like someone is rapidly raising and lowering the volume control. Any other player such as Winamp does not have such issue.

Signal strength (text w/dBm) reports this number, 2147483647(should be -125 or the infinity symbol for no connection), when not in range or whenever there is an error. This number also reoccurs in the 4636*#*# menu as information about current cell connection.
[Verizon HTC Droid Incredible 4G LTE] lwinstead:
Okay. I got past the boot loop. Granted, I had to completely RUU my phone, but at least I left myself S-OFF. Anyway, now I'm at it again, and I've got the ROM up and running. The only glitch now is that I'm not making a connection with Verizon. I changed the connection as per post 3 and restarted the phone, but its not making any connection, period. I just reflashed the ROM and will see what's happening.

On a positive side note, I don't see any flicker so far! I'll keep playing and report my findings.

Thanks for the effort, to all involved. Seriously appreciated!!
[Verizon HTC Droid Incredible 4G LTE] cyberkeeper1:
Even though it's set in build.prop to be default at startup, double check your subscription type in mobile network settings. Make sure it's set to RUIM/SIM and then reboot. You may get a SIM card added message a few times but just ignore it. Make sure the connection is set to GSM/LTE/WCDMA so that your phone can use LTE and make calls.
[Verizon HTC Droid Incredible 4G LTE] lwinstead:
Okay, thanks for the tip. Out of necessity, I had to jump back to my 2.17.605.2 Stock TWRP backup, but tonight I'll try again. I am sure it was set to GSM/LTE/WCDMA at first, but not RUIM/SIM. In fact, I KNOW it's set to NV by default. But no matter - I'll keep trying tonight. :)
[Verizon HTC Droid Incredible 4G LTE] antwonw:
I am having some issues with some of these releases. Let me explain each one.

I flashed cm-10.1.2-mdm05-fireball.zip and successfully am able to connect to the Verizon network and make a test call. However, the home button does not work and will not take me home. I can not get the QuickSettings menu from the notification bar. Also, I keep getting AOSP Keyboard FCing on me every 20 seconds or so. I tried rebooting and it didn't help. Also, I tried to open things like Browser and the music app an they immediately close out like they are FCing as well. The network bars do not turn blue so I am not sure if I am getting data or not. It says I am connected to 3G though.

I also flashed m-10.2-20131001-NIGHTLY-fireball.zip and had no issues with anything FCing. However, I am not able to connect to the Verizon Network. I waited like 30 minutes and it still wouldn't connect. I tried rebooting and also changing the Network Mode and RUIM/SIM (when changing RUIM/SIM, it would always revert to NV). Still none of these attempts connected me to Verizon. I followed the steps in Post 2 and was able to get connectivity back.

Any one know of either 1) Which ROM I should be using that is stable enough to use as a daily driver or 2) How to fix one of these problems on one of the ROMs?

Thank you!
[Verizon HTC Droid Incredible 4G LTE] MJL99:
When you flashed the 10.1 mdm05 build, you installed the wrong gapps package. I had the same issue before and that cleared it up. Pay attention to what you are installing because they look similar but aren't. 10.1=4.2 gapps. 10.2=4.3. This is the reason when you flashed a 10.2 build regarding your second issue you didn't have any problems with FCs.

As for your second issue, it's probably related to the ruim/sim setting. Some nightlies revert to nv. I would suggest trying a different nightly and see if the setting sticks. I'm still on 9/14 and it's working fine for me.
[Verizon HTC Droid Incredible 4G LTE] lwinstead:
I've had those two exact problems, the latter just yesterday. I resolved the former as per the suggestion to install the correct GAPPS version.

I am going to continue to play with the Nightlys until I find one that connects to Verizon. On the one I did try (9/27/2013), I didn't have any screen flicker, but no connection. Good luck, and if you find one that works please post it here so everyone knows! :)
[Verizon HTC Droid Incredible 4G LTE] Pete02:
The mdm builds are very stable. If you do a full wipe and install the proper gapps you should have no problems. If you don't get the screen flicker and would prefer to run cm10.2 I've found mower's 0901 build to be pretty stable. The only issue with that build is the delayed screen on but other than that everything works well for me. To resolve the screen on issue you can dirty flash the nightly 0911 build over that and you should be good. The newer nightlies are becoming too unstable for me to run for some reason.
[Verizon HTC Droid Incredible 4G LTE] antwonw:
Haha. I don't even have to go back and look. I now remember that this indeed was the issue I had. Thanks! Obviously was late when I was flashing.

You aren't having any issues with that build? By the way, where is that build? I can't find it here (http://download.cyanogenmod.org/?device=fireball) or here (http://goo.im/devs/mdmower/fireball/cyanogenmod)

Two questions for ya. 1) Where can I get those builds? Am I missing another location for builds? I can't find it on CMs site or Goo.im. 2) Could you explain to me what you mean by dirty flash 0911 over 0901?

Thanks guys!
[Verizon HTC Droid Incredible 4G LTE] lwinstead:
A while ago I tried a 3.4 Kernel build of 10.2 straight from ViperROM, but I'm drawing a blank on who's it was. Nevertheless, I had the flickering screen, and that's what moved me to try mower's 10.1.2 mdm05 build. That's what I'm running right now and yes, its stable and great. As per your suggestion, I'll give his 0901 build a shot and do the dirty flash. I will report what I find. THANKS!