yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] djkeller3:
I found it. But no thanks to anyone.

A small thanks maybe to bhilgeman for letting us know it dropped.

Now let's see how many others we can tease.
[Thunderbolt Android Development] Mustang302LX:
It's all thanks to him! The hint he gave was exactly where this pot of gold was located! :)
[Thunderbolt Android Development] djkeller3:
On second thought, I'll be the love-giver and share the link for RC1.3

http://goo-inside.me/cm/mecha/rc
[Thunderbolt Android Development] DroidMod94:
you are the best
[Thunderbolt Android Development] wtfmate913:
+1 to that!!!
[Thunderbolt Android Development] DroidMod94:
No No +Winning
[Thunderbolt Android Development] trueagle:
Ty
[Thunderbolt Android Development] DroidMod94:
Do i need to wipe before i flash 1.3?
[Thunderbolt Android Development] mitchell4500:
I didn't, it worked fine
[Thunderbolt Android Development] tu3218:
Not looking for a full changelog but is there anything noticeably different in 1.3 vs 1.2? Features, fixes, what have you? 1.2 is perfect in my opinion lol
[Thunderbolt Android Development] bhilgeman:
I haven't got deep into it, but signal bars reflect "correct" signal, seems cellular location services are fixed, 3G 4G toggle icons fixed.
[Thunderbolt Android Development] tu3218:
thank you sir..Will be flashing away. love this!
[Thunderbolt Android Development] mitchell4500:
Signal seems better as said and I also noticed the new 4g toggle icons. I would consider this perfect.
[Thunderbolt Android Development] joshnichols189:
* Changes/Fixes to 7/24 ** -Fixed Certain Music players not tracking play time. -Changes to how signal is computed. (rbox) -Minor changes for data stability -Sync'd Up to the mainline.
[Thunderbolt Android Development] tommy m:
The amber light now is flashing for notifications.
[Thunderbolt Android Development] lilsalmon:
Installed and running good. I'm curious to see the changelog.

-Lil
[Thunderbolt Android Development] jimmydene84:
How's the In call volume??
[Thunderbolt Android Development] DroidMod94:
Just Saying Tiamat 1.0.3 Kernel works with CM7 1.3
[Thunderbolt Android Development] TheLoonyRebel:
As soon as the main post is updated I'll update the ROM listings.
[Thunderbolt Android Development] converge12:
currently running omfgb. any upside to cm7?
[Thunderbolt Android Development] Ath315t:
Everything.
[Thunderbolt Android Development] uultramann:
OMFGB lets you choose 7 screens if you want. Additionally it looks completely like vanilla Android versus using ADW or any other custom launcher.

I've personally gotten a smoother experience with CM7 overall, but that is subjective. Either one is a great choice for the Android purist.

EDIT: No sooner than I type this, looks like CM7 has a new build. Yay!

EDIT 2: OMFGB tended to give me better GPS locks, no matter which KERNEL I was using.
[Thunderbolt Android Development] converge12:
i ask because on my old Inc, cm7 was nothing but headache and omfgb was perfect.
[Thunderbolt Android Development] uultramann:
Yeah, my gf has an INC, and for a while there, she HATED CM7, but it seems that the nightlys over the last month or 2 have been decent. The updates for the TBolt are a lot less frequent, but good when they hit. The one that just came out tonight seems to have corrected the screen calibration issue I was having, and when the GPS lock gets better, it will be pretty flawless. Tonight's CM7 also shows the proper signal strength, as previous AOSP ROMs did not.
[Thunderbolt Android Development] masri1987:
where is the new build ?
[Thunderbolt Android Development] masri1987:
nevermind -- http://goo-inside.me/cm/mecha/rc/update-cm-7.1.0-RC1.3-Thunderbolt-MR-2-signed.zip --- not sure if im gonna switch from OMFGB though ,
[Thunderbolt Android Development] gfro9191:
Never flashed a CM7 ROM on top of another... Is it necessary to wipe?
[Thunderbolt Android Development] ampinc:
I don't what is going on with this Rom. I had it for about a month with no problem. I did not mess with configurations and the phone went nuts. reboots all the time losing half of my apps. every time I get a call no ring just vibrates a lot of FC. I tried factory reset same thing I tried wipe delvik cache, factory reset in recovery mode and same any other Rom works fine has anyone experience this
[Thunderbolt Android Development] ddarvish:
i did not wipe and i flashed from RC1.2 to 1.3. as always it is a good practice to make a backup of your current rom and try it without a wipe. if it doesnt work out worst case is you go back and do a /data and /cache wipe.
[Thunderbolt Android Development] gfro9191:
By factory reset, you mean you wiped data, cache, and dalvik, right?

Also try fixing permissions.
[Thunderbolt Android Development] ANDR0lD:
How big is the download (megabyte wise?)

sent from a 1.5ghz-Cyanogen 'Bolt
[Thunderbolt Android Development] ANDR0lD:
Can we use the RC 1.2 kang kernel with RC1.3? ALSO can we use new gingerbread build?

sent from a 1.5ghz-Cyanogen 'Bolt
[Thunderbolt Android Development] dubious1:
Just got done flashing to 1.3 coming from BAMF 4.9 RC, and before that I was on 1.2 for about 3 hours. GPS is strong with this build (accurate within 5 meters). The one thing that deterred me from 1.2 was the lack of working 4G. I'm happy to report that 4G is BLAZING with the 2.5 radio! But... there's a catch (or a glitch).

Anytime I try to do anything Google related, whether its Google+, Market downloads, or even going to google.com in the browser, I can't seem to connect, or if I do, it's painfully slow on 4G. One example is downloading from the Market. I'm able to search for an app (and I get the search preview as I'm typing), I can get to the app description, but when I click on download, it just sits on the status bar without moving for a couple of minutes. Then I get a notification that my app has downloaded. Also noticed the same data hang-up I've experienced with the Google stuff while running Quadrant Standard. I can run the test, but it takes at least 3 minutes before the results finally finish sending.

Every other site I go to works great, and my Twitter/FB apps update with no problems.

Sorry to be long-winded, but hopefully someone can shed some light on this issue. I'd prefer to stay on 4G, but if I have to go to 3G only to get things to work, then I guess I have no choice.
[Thunderbolt Android Development] yohanseki:
I believe the 4g in the south TX/OK is flakey a network issue. Hopefully it will be back to normal in a couple days. It started happening to me since yesterday.
[Thunderbolt Android Development] dubious1:
Thanks for the reply. I didn't have any issues with 4G while on stock or BAMF 4.9. I've only had these 4G issues with CM7. Hopefully you're right about the 4G issues and it'll work itself out, otherwise it's back to BAMF.
[Thunderbolt Android Development] jr4000watts:
Your not the only one bro, im in Houston TX and i got the EXACT problem as you. i have been flashing and flashing and yes flashing since 3pm and trying crap out to see what the hell is going on (its frustrating me) but i think now its a Network issue or something because ive never had this problem on both 1.2 and BAMF 4.9.

Verizon needs to quit messing with **** and lower its prices lol

Edit: just read on Rootzwiki that some people on the 2.75 leak dont have that issue. ive been flashing mr2 and 2.5 all day on alot of roms and had the issue regardless. going to try 2.75 now see how it goes.
[Thunderbolt Android Development] dubious1:
Let me know how that works out. I'm off tomorrow, so if I have to stay up all night to get it to work, so be it :-)
[Thunderbolt Android Development] Trident77:
Haha. No love from slayher for XDA.
[Thunderbolt Android Development] rafaelvelasquez2:
It's not just you. I been having these same problems for days now and I'm in southeast Houston close to Pasadena. I actually asked about the market thing a few pages back. My downloads were taking 2 or 3 trys to download and sometimes not at all. AND YES goggle is trippin'. My homepage on dolphin browser is Google.com and I ain't seen it in 2 days. I changed my homepage to Yahoo! in the meantime. But I understand it's some sort of location problem strictly effecting southern states. Hopefully it works itself out.

BTW... This Rom is awesome. Quick,Stable, to the point, and alot easier on my battery than all those sense widgets and sense malarkey. I got this thing undervolted AND UNDERCLOCKED and it's still fast as hell. not to mention its the only ROM I've used where my Netflix, Hulu, and HBO GO all work flawlessly. (some roms tell u that u have a network issue when trying to play older show in the Hulu app)

Everything works awesome here and I'm loving the fact that my signal bars work properly with this 1.3 release(for those of you who don't know, u can pick up 1.3 in the thunderbolt dev section of the rootzwiki forums)
[Thunderbolt Android Development] jr4000watts:
Dude your so close to me lol what are your speedtest results there? ive been getting crappy 9 to 14mbs here
[Thunderbolt Android Development] rafaelvelasquez2:
I'm on that 2.xxxxx radio that chingy leaked and I'm getting like 30 to 40 down at times and 3 to 4 up.
[Thunderbolt Android Development] dubious1:
I know you were asking Rafa about his speed, but check my sig. That's inside the loop, near Greenway Plaza. I couldn't believe it when it happened. That whole day I was hitting 30-40mbps easily. I can still hit those occasionally, but now it's between 12-20 regularly.
[Thunderbolt Android Development] jr4000watts:
well i get my crappy speeds because i live out by beltway 8 and the new 90/almost channel view area. and out here well my speeds are no were near as good as when im closer to Houston downtown area.
[Thunderbolt Android Development] daddylonglegs:
Thanks, I tried this, but no dice.

You know what's funny/odd? I don't have this problem with Pandora and Navigation. Maybe Pandora is considered a different "volume" thing than a regular media player?
[Thunderbolt Android Development] ampinc:
Yes
[Thunderbolt Android Development] ampinc:
I have done fix permissions whent back to stock for now um going to try my bro phone maybe is just my phone that's tripping
[Thunderbolt Android Development] 00negative:
1.2 kernel? The old kang 0.8 should work with cm7 1.3 but Drod just released a new version 0.9 on 7/24
[Thunderbolt Android Development] Ryanmo5:
Keep this thread on topic, all anti xda comments, thanks replies and off topic posts will be deleted.
[Thunderbolt Android Development] BigMace23:
Don't think it's just a network problem in southern states, because I am getting this same behavior in Pittsburgh PA
[Thunderbolt Android Development] jamesavery22:
Thanks wraithdu,

I changed the symlinks. ifconfig and route in /system/bin/ are now pointing to busy box.

I have the same results as before though. ip ru only shows local, main, and default. Trying to run those del commands just gives "invalid table ID" errors since it looks like I don't have them.

CM7 built in OpenVPN still gives broken pipe in logcat.

android-openvpn-settings still shows connected but cannot ping anything through the tunnel. Even after resolving the route errors shown in the openvpn log.

Any other ideas?

Should I have to add:

busybox route add -net 192.168.1.0 netmask 255.255.255.0 rmnet_sdio0

?

That resolves the openvpn route add error but is it correct?

Shouldnt some of those routes be associated with tap0?

I notice tap0 gets created when android-openvpn-settings is connect but is not up.

ifconfig tap0 up

brings it up but not really sure which route to associate it with?
[Thunderbolt Android Development] dubious1:
Thought I'd post an update:

Flashed the new Chingy radio (2-xxx-xxx-whatever it is) last night, and I'm still having issues with anything Google related on 4G. I also noted that my Simi Clock weather widget said I was in Riga, Latvia when I woke up this morning! Thinking I lost my GPS overnight, I checked GPS status and was still hitting 9/9 sats, and Maps put me at 6 meters accuracy. I switched my radio to 3G and tried to refresh weather. It worked, but now I'm in Virginia Beach!
[Thunderbolt Android Development] 00negative:
GPS isn't the biggest issue I have found with AOSP roms but I have more issues with network location, which I assume is issues with the RIL or a file missing or something in the system for getting the network to recognize your location
[Thunderbolt Android Development] jr4000watts:
I wonder if Verizon is even aware of this issue.
[Thunderbolt Android Development] dubious1:
Would they even be able to help out? If we're running CM7 (or any other ROM), then that means we're not using the stock phone that Verizon sold us. Same goes with using leaked radios. There are many people, myself included, that don't have these issues with other roms. It seems like to AOSP-based roms are having issues right now. And I hope no one takes that as me knocking the devs for their work. Believe me, I have nothing but the utmost respect for what they're working on and I know no one can just snap their fingers and make things work. If that were the case, I don't think boards like this one would be around.
[Thunderbolt Android Development] 00negative:
Not a Verizon issue it works on Sense and Sense based roms fine. Its an AOSP rom issue, so I am guessing it is tied to RIL since they all basically use the same and have the issue.
[Thunderbolt Android Development] Mustang302LX:
That's what I was about to say as well. The location (NOT GPS) issue only resides in AOSP ROMs. Slayher has mentioned HTC used some strange stuff for location and he hasn't been able to wrap his head around it all just yet. I'm sure it will be fixed eventually though.

The only thing this affects is my ability to check-in to places on FB which I hate FB anyways so not a huge deal lol. Other than that I don't typically use location based apps on my phone. GPS stuff works fine so I have maps and navigation so I'm fine for now.
[Thunderbolt Android Development] 00negative:
Ha you should ditch FB anyway, I got rid of mine a long time ago. Haven't really missed it was actually a relief when I did
[Thunderbolt Android Development] jr4000watts:
I flashed bamf, gingeritus, and still had the same problem. Flashed Mr 2,2.5 and 2.75 and all had the same issues so idk what's going on.
[Thunderbolt Android Development] wraithdu:
So after replying to you, I finally tried out OVPN on CM7. For me, it works perfectly. I didn't have to do any of the things I suggested to you actually. I just had to update the path to openvpn in the OpenVPN Settings app (I use that too) to /system/xbin/openvpn .

Did you do that? Are you using the openvpn binary that came with CM7 or a different one? There was another individual I helped out with OpenVPN who was also having trouble on CM7 until he switched to the built-in binary.
[Thunderbolt Android Development] SolZer:
Definitely! CM7 has more options (Settings > CM Settings), and 3G/4G Toggles. I've run OMFGB, and I prefer CM7 hands down.
[Thunderbolt Android Development] jamesavery22:
Found it. Didn't have to run the route add

Just

netcfg tap0 dhcp

found here:

http://code.google.com/p/android-openvpn-settings/issues/detail?id=79&can=1&q=route tap0
[Thunderbolt Android Development] boristhebladexx:
GPS locks for me, and foursquare works fine, but on CM7 google places won't let me check it. it worked on OMFGB and OMGB but no CM7. i noticed this on 1.2 as well.
[Thunderbolt Android Development] 00negative:
You wiping data, cache and formatting system? If you aren't wiping it could carry over just like people use the GPS fix by getting a lock on sense rom then restore a cm7 backup to get GPS fix on AOSP that tells me something is being stored in the memory that helps it to work.
[Thunderbolt Android Development] jr4000watts:
Wiped 3 times on everything still acts up
[Thunderbolt Android Development] 00negative:
Wiping multiple times isn't necessary. Format system? Reboot Recovery after wiping/before installing new Rom or backup?

You going to backups of those Roms or setting up new. I would try new.
[Thunderbolt Android Development] SUB-dawg:
1.3 is out on RootzWiki
[Thunderbolt Android Development] brownat:
Is anyone else have wakescreen issues with rc1.3. Cant seem to wakeup the screen unless i plug it in or get a text. Im running the latest radio by chingy and tiamat kernel. Ive tried two data wipes and three different kernels. Any help would be appreciated.
[Thunderbolt Android Development] jburnette87:
omfgb has 3g/4g toggles as well. and is pure aosp
[Thunderbolt Android Development] tu3218:
For those who overclock, what do you have your governor set to or do you use setcpu? I've been running this stock kernel, at 1ghz and I would like to try overclocking and see how it performs and if I still can get decent battery life. But I don't want to overwork my cpu at 1.8ghz when I'm not using my phone. Any suggestions for this?
[Thunderbolt Android Development] ANDR0lD:
Screen On: 1.5Ghz/1.5Ghz; Lagfree

Screen Off: 410mhz/356mhz; conservative

sent from a 1.5ghz-Cyanogen 'Bolt

[ROM]Cyanogenmod 7 RC1.3

[Kernel] Drod BFS AOSP. 9
[Thunderbolt Android Development] nick2585:
Is there a GPS issue fix in 1.3? I know the trick in 1.2 but just wondering...

THANKS!
[Thunderbolt Android Development] Auronis1:
SMS notification disabling?

I've done a lot of searching, without switching back to Handcent is it possible to disable the status bar notification that shows a preview of the text message. I want to still get a warning chime or it to vibrate but I don't want any of the text to be visible until I actually open the messages and look at them.
[Thunderbolt Android Development] bobby janow:
Did you try disabling popups in settings menu?
[Thunderbolt Android Development] arasky:
just jumped on 1.3 here, but as a previous cm5 and cm6 moto droid user, whats up with the numbering system of the release candidates, "rc1.3"? why isn't it rc1, rc2, etc.? Also, at what point does cm for the thunderbolt become an official port?
[Thunderbolt Android Development] joshnichols189:
No it's not. OMGB is pure aosp and doesnt have toggles.

Also, i experienced sleep of death (phone not waking) on kangbang using lagfree govenor with 184 as my lowest slot.
[Thunderbolt Android Development] joshnichols189:
Sorry to double post, but because it's not ready to be labeled RC2, and when merging our RIL stuff doesn't break other devices
[Thunderbolt Android Development] Absolute_Zero:
RC2 hasn't rolled out for any device on CM yet. I'd imagine slayher's just trying to keep in line with those numbers. For instance, I'm guessing we won't see an "RC2" for Tbolt until RC2 actually rolls out for officially supported devices.

Not sure what an "official port" is exactly since once it joins the mainline it will not technically be considered a "port". Anyway, it'll get merged when it gets merged.
[Thunderbolt Android Development] arasky:
one of my friends just got the bolt, and when he went to cyanogenmod.com and didn't see the thunderbolt listed on the devices he assumed there wasn't development on it, just wondering at what point a phone gets taken off the unofficial port forum http://forum.cyanogenmod.com/forum/23-unofficial-ports/ when clearly the bolt has more posts than all other phones there combined. just a curious noob question.

also,

i wasn't able to find anything on the stock kernel, this link has a listing of kernels and i couldn't figure out which one it is. are a lot of people sticking with the stock? i just want to try to undervolt this as much as i can to save battery
[Thunderbolt Android Development] Jodiuh:
Can I just install this over the top of 1.2 or is a full wipe necessary? Is there a bug/fix/feature list?
[Thunderbolt Android Development] booda3000:
I installed over 1.2.

Same radio of course.
[Thunderbolt Android Development] booda3000:
Didnt wipe anything.

lets c what happens.
[Thunderbolt Android Development] Crimton:
curious to see if better battery life is reported. sense based roms make it through the day for me, sadly cm7 doesn't come close :(
[Thunderbolt Android Development] idle0095:
im wondering as well if a full wipe necessary?
[Thunderbolt Android Development] Jodiuh:
Just did the same thing...no backup...just went for it. I'm seeing 4 bars of 4G in areas with 2 previously!

GUI seems snappier too! Is there a list of release notes somewhere?

Edit: I've had multiple disconnects from 4g...
[Thunderbolt Android Development] Absolute_Zero:
In the rootzwiki OP as always.
[Thunderbolt Android Development] joshnichols189:
Like I said above you, the TB will be merged and turned into an official port when adding our source doesn't break other phones which it currently does.
[Thunderbolt Android Development] mackentosh:
"UPDATE" 1.3

http://rootzwiki.com/showthread.php?392-ROM-CM7-for-Thunderbolt.-RC1.3-Updated-7-24-10-30PM-EST
[Thunderbolt Android Development] 00negative:
Have you tried raising the lower threshold of the kernel from maybe 2xx to 3xx
[Thunderbolt Android Development] Jodiuh:
Thanks!!!
[Thunderbolt Android Development] Breezer23:
Is anyone else having severe issues with Cell Standby on this build?
[Thunderbolt Android Development] Odinist:
Badass. Thanks!
[Thunderbolt Android Development] Auronis1:
Messaging settings or Cyanogenmod settings?
[Thunderbolt Android Development] David 617:
i recently wiped my pc and have yet to plug in my cm7-thunderbolt. i read somewhere that i need gb drivers? where can i get them?

also can someone give me the steps needed to flash the latest radio (version #?) and the latest firmware?

thanks
[Thunderbolt Android Development] Sean Hicks:
I am. I have come to accept it. My battery isn't all that bad. Maps keeps running for some reason though
[Thunderbolt Android Development] tu3218:
Not sure about gb drivers? Just plug your phone in and select sd card.

As far as the radio goes, grab the latest radio(mr2), put it on the root of the sd card, hold power and volume down and boot into hboot. The radio file should be recognized and just accept to flash the radio.
[Thunderbolt Android Development] David 617:
after the radio i should put the rom on sd, boot up, use rom manager to install from sd?

-also, is MR2.5 newer?
[Thunderbolt Android Development] tu3218:
Yea you can. You can do it any order you want. I recommend when installing the rom, to boot into recovery and install that way. Installing through rom manager is iffy and have seen a lot of problems related.

yeah, thats the newer radio. Also, not sure if your installing 1.2 or 1.3, but make sure you select the rom version for the mr2 radio and not the older one. Not sure about 1.3, as I remember there only being one option. I would imagine its for the new radio though.
[Thunderbolt Android Development] nucher:
The MR2 from this thread http://xdaforums.com/showthread.php?t=1160346 is the official MR2 from Verizon and the latest from Verizon. MR 2.5 is a leaked radio although different people categorize the radios differently. I always install ROMs from ClockworkMod recovery, wiping first of course. With the EVO some people had problems installing ROMs with ROM manager, not sure if that's true with the Thunderbolt but I've never had any problems using ClockworkMod.
[Thunderbolt Android Development] Archangel:
I remember from the OG droid days and cyan mod that the cell standby issues were just something that was reporting and showing wrong however it does not really have a adverse affect on the phone.
[Thunderbolt Android Development] David 617:
anyone know the deal with the new radio, MR2.75?
[Thunderbolt Android Development] mitchell4500:
Yea, I do. Burns battery
[Thunderbolt Android Development] chimpsnest:
Odd, in Handcent they have that checkbox for "privacy mode" so it won't show the message in the notification bar unless you set it to. I can't see anyplace in the native messaging app for that option.

Do you happen to have Handcent installed?
[Thunderbolt Android Development] stearic:
The new radio is the official MR2. The ones that were leaked were RC versions of MR2.