yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] irvine32:
Yah man I'm no pro you may wanna hit one of the devs up on a chat to see if there is something else that can be done. good luck
[Thunderbolt Android Development] qman66:
Video chat sound

noone hears me during a video chat in any of the video chat apps. is there a fix for this?
[Thunderbolt Android Development] irvine32:
A far as skype goes I have to pause.the vid for a second then un pause

and they can hear me. Haven't tried other apps yet.
[Thunderbolt Android Development] qman66:
interesting. ill try that. thanks
[Thunderbolt Android Development] Jodiuh:
Just wanted to chime in and say how awesome it was to see a string of posts with people helping people instead of smartass jerks negatively responding with "Google it!"

My hats off to all of u! Truly wonderful to read! (Sorry I'm of no help! ;-))
[Thunderbolt Android Development] irvine32:
Jodiuh, don't get all sentimental on us ;)....sorry its been off topic tonight guys.
[Thunderbolt Android Development] bill3508:
On the 1700mah batts that you buy two and get the charger with. Here is a pic continued as it slept overnight.

Thunderbolt CM7 1.3

Tiamat 1.0.3
[Thunderbolt Android Development] mkitchen:
So quick question, I have rc1.2 on my phone and thinking about upgrading to this. I only have the MR1 radio, is rc1.3 only for MR2? I only see the download for the MR2 radio version.
[Thunderbolt Android Development] daddylonglegs:
No, not output volume on my speakers, I'm guessing the best way to explain it is input microphone on my phone when I have something plugged into the headphone jack.

For example, when I am in my car, I plug in the headphone jack of my phone into my auxiliary jack in my car to listen to music. If I make a phone call/receive a phone call, it plays through my car speakers which is awesome. Except NO ONE can hear me on this ROM. Everyone says it sounds like I'm talking from really far away and they can't hear me unless I yell. If I put the phone right up to my mouth, they hear me fine.

I believe there's two mics on the Thunderbolt, one for when you talk normally, and one for when you are using speakerphone. When you plug something into the headphone jack, the Thunderbolt is SUPPOSED to switch over to the speakerphone mic. It's not doing that on CM7. It's staying on the "normal phone up to your face" mic.

I hope I got that right, but in short, every other ROM (and stock) did not have this problem. I extensively tested it yesterday and everyone can hear me fine on every ROM except CM7.
[Thunderbolt Android Development] black05x5:
Is there a black gmail app that works on CM7? I was using one when running bamf 1.8 but it doesn't seem to work on this rom.
[Thunderbolt Android Development] 00negative:
1.3 working great just wish they could figure out how to fix network location in the RIL.

Other than that, fast and smooth.
[Thunderbolt Android Development] nick2585:
I was on Cyanogenmod7 1.2 MR1

I updated the radio to the OTA MR2

Opened ROM Manager and flashed 1.3 MR2 with only wiping davlik cache, and everything worked great. I hope this helps someone who is having cold feet about flashing a radio!
[Thunderbolt Android Development] mmtoman:
I just downgraded to 1.2 because I couldn't get audio working out of both headphones. Only one channel would work even after doing voice search. I booted 1.2 and audio worked from both headphones instantly.
[Thunderbolt Android Development] arasky:
running the newest GB radio (1.46.00.0704w_2, 0.01.76.0703_2r), tiamat 1.0.4 kernel and cm7 rc1.3 and i have both headphones working

did you try

completely

wiping 1.2 before upgrading to 1.3?
[Thunderbolt Android Development] LittleLebowski23:
I had wiped battery stats and wiped the whole phone three times. I went back to BAMF 3.0 RC4.9 and conducted the same experiment. Result was 22% battery life this morning.
[Thunderbolt Android Development] superskaterxes:
anyone having problems connecting to google services? everything seems to be working fine for me but once in a while ill loose the green bars and it wont come back for quite sometime or w/o a reboot. is this a google problem?
[Thunderbolt Android Development] rulevoid:
I upgraded to 1.3 from 1.2 with only clearing Dalvik Cache and now my GPS doesnt work at all. I toggle it on and it shows as enabled even in the settings. But it never locks and the GPS location icon in the navigation bar never appears. Even with unobstructed clear view of the sky from all sides and waiting 5 minutes straight. Anyone having GPS issues like this?

I am running leankernel by the way.
[Thunderbolt Android Development] bobby janow:
Same here without a wipe. (drod 0.9 kernel)
[Thunderbolt Android Development] raziel36:
1.1 to 1.2 upgrade did the same thing to me. I didn't need it, so didn't worry. However, before going to 1.3, I reloaded a Sense rom and got a GPS lock. Now on 1.3, my GPS is working wonderfully again. Just backup your current setup, load up Sense and get a lock, then restore your current setup. Should be fine.
[Thunderbolt Android Development] rulevoid:
Interesting I will give that a try and report back.
[Thunderbolt Android Development] altimax98:
Anyone having an issue with a language dialer? I it even affects go dialer. It connects but no sound or anything for seconds And other person could have already picked up lol

* FIXED clock speed at 245 conservative caused it ;-)
[Thunderbolt Android Development] [SP]JESTER:
I know right! Im glad i switched man. Im gnna dump my home inet lol
[Thunderbolt Android Development] mkitchen:
So long story short, yes I need MR2... Guess I have to man up and take the radio flashing plunge sigh

Thanks for the info though
[Thunderbolt Android Development] contractcooker:
No you are not the only one. I can't get the built in tethering OR the android wifi tether to work. Anyone have a fix?
[Thunderbolt Android Development] hotelmrrsn:
No issue getting the built in tethering or the android wifi tether to work
[Thunderbolt Android Development] hotelmrrsn:
I moved to CM7 from Das BAMF 3.0 RC4.9 and could not be more happy that I did. The ONLY glitch that I have is with weather(regardless of app) identifying my location correctly. Any other program that uses GPS locks in on my correct location within 5 seconds even when i'm inside. But if i set any weather app to geolocation it shows me somewhere in florida no matter how many times i reset. Very odd, but not a huge deal.
[Thunderbolt Android Development] daddylonglegs:
Me too, unfortunately I have to switch back to BAMF until CM7 fixes using the headphone jack not switching to speakerphone mic. :(
[Thunderbolt Android Development] DaRkL3AD3R:
Ok I figured something out here. Now I haven't done detailed testing as to what triggers it completely, but I have found a way to get 100% working Network Location based GPS on CM7 that works 100% with any Weather/Clock program.

Basically its the same as the real GPS trick where you load up a Sense rom, get a lock on with GPS, while holding the lock reboot into recovery and reflash CM7. If you do that and don't use actual GPS, just Network location services, you SHOULD get proper Cell Tower location.

As for what BREAKS this? Wifi. Yep. Wifi.

I first discovered it yesterday after I did a full wipe and flashed CM7 RC 1.3. I wanted a clean slate, so I got it all setup, backed up CM7, did my Sense GPS trick, and booted back up into CM7. I did NOT enable Wifi at any point after rebooting and sure enough, waddya know. Accurate Network Location. So I said wow I wonder if 1.3 fixed it? Nope. As soon as I started tinkering with Wifi it completely broke my Mobile Network location capabilities. It would not go back to the way it was pre-enabling Wifi. So I said to myself well maybe it is the same as the Sense GPS thing? Since obviously it wasn't RC1.3 that fixed it.

So I backed up my fresh installation of CM7, wiped everything went on BAMF Sense 3.0 RC4.9, got cell tower location lock, enabled hard GPS, got a hard GPS lock, rebooted, WIPED EVERYTHING (data/cache/dalvik/system) then Restored my CM7.1 installation. Sure enough, without enabling Wifi or hard GPS again, there was my location. Accurate to 2000m and I was pretty damn close to the center.

So what I've gotten out of this was that Network Location DOES work on CM7.1, however its tied into the same glitch that affects GPS. The difference is that hard GPS is STANDALONE. Once you fix it on a Sense rom and restore a CM7 rom, it holds. With NETWORK location, it can choose between 2 types of radio based location, CDMA and Wifi. Unfortunately I do not know why, I am no programmer, but somewhere a long the lines once you switch to Wifi for finding location, it breaks CDMA tower location. I hope this post helps a Dev somewhere to figure out this issue, because honestly this is THE ONLY, and I mean THE ONLY noticeable issue I have with CM7.1, which is imho THE BEST ROM OF ALL TIME!!!! =D
[Thunderbolt Android Development] rulevoid:
It sounds like you are having the same issue as me. If i am listening to Pandora with headphones plugged in (no mic) and a phone comes in, I can hear them over my headphones but they can not hear me, im assuming because like you said that it is looking for input from headphone jack?
[Thunderbolt Android Development] dB Zac:
Man, I switch to wifi at work and at home, with no location or GPS issues
[Thunderbolt Android Development] daddylonglegs:
Yep exact same issue. Does not happen with other roms.

You put it a good way. It's probably that CM7 is expecting all things plugged into the headphone jack to also have a mic. Obviously this isn't always the case. CM 7 should be switching to the external mic, but it's not.

Hopefully it's resolved soon so I can go back to CM7.
[Thunderbolt Android Development] leoingle:
So how is 1.3? I am still on RC1 and have been for 3 weeks without a flaw. Switch from BAMF 3.0 and couldnt be happier that I did. BAMF is a great ROM, but CM7 is so responsive, quick and smooth on window transistions. The changelog looks pretty minor on 1.3, is it worth updating?
[Thunderbolt Android Development] dB Zac:
I never had RC1. I did go from RC1.2 to RC1.3, I don't notice any real difference but RC1.2 seemed flawless for me anyways
[Thunderbolt Android Development] dB Zac:
So your plugging in a set of ear phones that have an external mic? There is only one input mic on the phone it self, the other is used for noise cancellation
[Thunderbolt Android Development] altimax98:
Agreed. I came from BAMF 4.9 and only miss the sense dialer, but go dialer with the dark theme is a fantastic replacement
[Thunderbolt Android Development] theredspecial:
I upgraded to 1.3 yesterday and flashed the Tiamat kernel. I have been having a lot of problems losing my 4G today, which could just be Verizon. The biggest problem for me is the call quality. The earphone is still too low and the speakerphone quality is almost laughable. I would say it's actually worse on 1.3/Tiamat than on 1.2.

I really wish some dev could figure out this issue that seems to be on all GB ROMs. Hopefully an official GB build will come out soon and fix this so it can be implemented into our ROMs.
[Thunderbolt Android Development] mmtoman:
On my phone so can't search.

Quicker to respond than to *****...

Hotspots is not working for me. I'm 1.3 stock kernel mr2.5 radio and I'm connected to 4g. Can't figure out the problem. I've toggled airplane mode. I've rebooted. And nada
[Thunderbolt Android Development] nkgangew:
Well, there's a big difference in a rom that's 80 MB compared to 300 MB. Can't really compare an ASOP to a Sense based rom (BAMF stripped isn't ASOP). If cm7 or liquid tbunderbread or any other ASOP could get the GPS working, it would be my everyday rom.
[Thunderbolt Android Development] mmtoman:
Its AOSP (Android Open Source Project)
[Thunderbolt Android Development] bigd5783:
Im having the oddest problem. I cant get to google. I open the browser and type in www.google.com, gmail, google+ and it will not go. I can get all other web pages fine though. Any ideas. This is after a full wipe and install. I even went as far as not retreaving my settings from google but still www.google.com.....nothing.
[Thunderbolt Android Development] dB Zac:
both the free and the paid version freezes up my phone (black screen) on the 2nd lock
[Thunderbolt Android Development] irvine32:
Do a search in here for DNS I believe. Some people have been reporting it in fact I had that issue for awhile but there is a DNS app that helped some people. Good luck
[Thunderbolt Android Development] bucklyv:
Where did you find the newer radio? Link?

I have been to the rootzwiki website and through almost every post on this thread and I cannot seem to find a link to the 704_w radio. :-(

I am running RC 1.3 with ZERO problems and it is awesome!
[Thunderbolt Android Development] evolutioncsr:
LOL seriously? http://rootzwiki.com/showthread.php?1669-Radio-Leak-7-17-11-2.xx.xxx.x-Radio-New-Gingerbread-RUU

First page on their TB development section.
[Thunderbolt Android Development] dc iz 2 legit:
Hey guys just reporting on the 704 radio I recommend not using it since I believe it might of bricked my phone radio wise after I flashed the radio a couple days later my 3g and 4g would not work correctly at first my phone was not able to pick up 4g and after doing everything possible I finally got it working but as soon as I did that I was not able to pick up 3g and did everything to get that working I Evan left it alone overnight to see if it would work and it was a big fat negative but I did manage to get little glimpses of 3g but they did not stick now all of this happened while I was das. Bamf 4.9 with 704 radio I also downgraded to mr2 radios and cm7 and went to full stock sense with mr1 and nothing worked I also found one other person in q&a with similar problem good thing I had insurance

Edit again I started having problems as soon I flashed this radio my phone would get hot Evan if I was not doing anything I recommend using ota since their is no real difference
[Thunderbolt Android Development] yohanseki:
Try downloading setDNS from the market and try the Google one or set dns1 to 4.2.2.2 and dns2 to 4.2.2.3.

Sent From My Mecha Sipping On Some Pink Floyd
[Thunderbolt Android Development] sabbotage:
Anyone having issues with location try going to applications/development and uncheck allow mock locations. I have never had location issues as long as that box is unchecked.
[Thunderbolt Android Development] novafoundry:
Location issues...

So after days of using cm7 1.2 & 1.3, I can safely say that (at least for me) there is no permanent location

fix. Sometimes it works, sometimes it thinks I'm in angola. Mostly its weather apps that get confused, but google maps does as well. Sometimes when maps and weather show the wrong location, gps status will have no problem getting a lock. I've tried mock locations on and mock locations off. Right now I'm in the process of ripping the location service out of an app we write to try and figure out which of the systems is giving the bad location. My plan is to try and log the location that each subsystem provides for a couple of days (if the api allows..can't remember if it lets you see each at the moment our just tells you the best source currently available). After that, we should have a better idea of what's going on.

I'm posting this so that hopefully some other dev will attempt something similar... Basically to repeat the experiment and confirm results... Or someone can tell me if my approach makes no sense.

thanks,

Marshall
[Thunderbolt Android Development] Jodiuh:
Thanks!

Fyi, GPS, wifi, hotspot, 4g, 3g all working fast on cm7 rc1.3/imoseyon lean 3.5.8/627r radio. Least warm/hot phone combo IMO so far.
[Thunderbolt Android Development] Archangel:
liquid thunderbread 2.3 has working GPS still waiting from the dev on next release cause 2.4's gps didnt work
[Thunderbolt Android Development] Quantify:
Son of a *****. That fixed it. Wow!
[Thunderbolt Android Development] Dlnp22:
Flashed yesterday and have definitely been digging, but just tonight am experiencing a crazy issue ONLY after rebooting.

Every time I make a call, I get a phone force close, and I lose all radio and data connections for a minute.

Tiamat 1.04 kernel and mr2 radio. Is it one of these two or ROM related?
[Thunderbolt Android Development] ktech11:
I have wireless tether for root users 2.07 working just fine on mine. I still have the apk on my SD if you need it. PM me so I get the notification immediately because I usually only check once a day, but PM's get to me faster and I can get the apk to you.
[Thunderbolt Android Development] dustinb17:
Try pressing the volume key after the power button. Oddly enough disabling the Status Bar in the Agile settings fixes any issue I had with this app.
[Thunderbolt Android Development] altimax98:
I had the same issue until I switched to 245 on demand and it stopped for me. I I also use go dialer
[Thunderbolt Android Development] jcortes187:
Random Signal Drops. Is this Normal?

I get random signal drops after opening apps such as Pandora, the bowser, Rhapsody, Maps... Just about anything that uses data really. Is this normal? happens about every 20 minutes sometimes more often. I am running the MR2 OTA radio. I have also wiped everything including system yet this problem persists. Take a look at the screenshots below. Is this happening to anyone else?
[Thunderbolt Android Development] Mean Bro Greene:
This is happening to me as well, sometimes. 4 or 5 times in an hour. I changed out radios, and it still behaves this way.
[Thunderbolt Android Development] chimpsnest:
That did not work for me :( Right now it's not entirely wrong, it just says either "Massachusetts" (when using Accuweather) or "Massachusetts, Massachusetts" when using Google.

It hasn't put me in Vosu in a while :)
[Thunderbolt Android Development] daddylonglegs:
OK, I basically dedicated my evening to figuring this out, I think I got it "solved", hopefully this will be fixed because it makes CM7 unusable for me unfortunately (and it should do the same to anyone using their phone as an audio player in their car and then receives a phone call).

If I plug *anything* into the headphone jack, CM7 shows an icon on top of a headset with a mic. It can literally be a headphone jack extension cord, and it will show a microphone on top. I flashed a different ROM, it was able to correctly detect a headset and a normal headphone with no mic. CM7 does not distinguish them. On the other ROM I tried, I get a microphone icon with a headset, and a NORMAL non-microphone headphone icon.

I hope this makes sense. Took a lot of work for me to figure this out. Hopefully there's a fix so I can come back to CM7!
[Thunderbolt Android Development] sabbotage:
Mine is also doing this. I don't have 4g in my area yet but I'm seeing the same behavior on 3g.
[Thunderbolt Android Development] LittleLebowski23:
I also experienced that.
[Thunderbolt Android Development] slckofit:
Me 3. My phone signal seems to always bounce around but usually stays within 2-3 bars. My wifi signal does the same. I ended up going back to Bamf and my signals are always full and my gps works again.
[Thunderbolt Android Development] eallan:
Same problem here. Also Google Voice is way finicky.
[Thunderbolt Android Development] hotelmrrsn:
I have to say that I have zero signal issues since flashing this rom (I came from Das BAMF 3.0 RC4.9). For reference I'm using radio: 1.46.00.0704w_2, 0.01.76.0703_2r with imoseyon 3.5.8AOSP lean kernel. When I had signal issues on Das BAMF I would try downloading a new radio and flashing in hboot and found that I had to give the radio some time to "settle in"(hour or so). It's my understanding that all phones are different and will respond differently to the various radios. First thing I would try is flashing a new MR2 radio and see if your issues subside.
[Thunderbolt Android Development] CryForJustice:
No Cell Phone Usage!

I'm having huge issues. I love this ROM a lot, but I am completely unable to send, receive or anything with my calls.

When I try to, my phone force closes the. .phone process and signal dies and the phone rebooted.

Running RC 1.3 and the MR2 Radio...

Help!

Thanks.
[Thunderbolt Android Development] sabbotage:
I am already on the MR2 OTA radio. And 1.2 didn't have this behavior on my phone. As soon as I flashed 1.3 thats when the signal issues started. I even tried a complete wipe with the same results. My problem isn't low signal, I just see the 3g icon flashing white quick almost every time I access an app that uses data.
[Thunderbolt Android Development] skinien:
If I get FCs after installing a ROM, I usually just wipe again and that solves the issues - might as well re-flash the ROM too.
[Thunderbolt Android Development] tgwaste:
your battery will not change that is part of the framework and not systemUI.

you can watch this thread for my full theme coming soon to CM7

http://xdaforums.com/showthread.php?p=13100408#post13100408
[Thunderbolt Android Development] avlfive:
Thanks! I'm definitely gonna give it a shot tonight after work. It's being used in my phone in the meantime. Is that going to cause any issues?
[Thunderbolt Android Development] gdanko:
I am addressing this message to anyone in this thread who is using this ROM but has not donated.

This ROM is almost 100%. It's stable, most of it works, and it can really be used for day to day work. And even if it's missing something you require in a "daily driver", that feature will eventually be included and/or fixed and at that point you will be using it.

Having worked on CyanogenMod for another device I know how much work and tedium is involved. If you are using this ROM and/or have a vested interest in CM for the ThunderBolt, take 5 minutes and donate at least $10 or $20 to Slayher and/or ToastCFH. If you can afford a high end phone like this as well as a data plan, you can afford to donate to the men who are working day and night on this thing. If after reading this you still opt not to donate, you're a cheap SOB and deserve to be restricted to Sense for the rest of your cell phone using life. :P
[Thunderbolt Android Development] Jaxidian:
Thanks for the reminder that I haven't yet done this. Oversight has been corrected. :)
[Thunderbolt Android Development] necosino:
I'm a single father that works full time to support his family and pay his own way through school. Does that make me a cheap sob?
[Thunderbolt Android Development] gdanko:
If you can afford a premium cell phone and data plan you can afford $10.

I have a wife, 3 kids, 2 mortgages, and 2 car payments, plus preschool for my son. I found a way to donate.
[Thunderbolt Android Development] MFK DGAF:
My self, like many others are having problems with data. After a fresh install and 5-10 minutes of waiting for data to connect on CDMA +LtE/EvDo. There's is no connection as well as my signal bar has 0 bars untilled I place a call then I gain bars (2-3). But what I have noticed is that on stock as well as TeslaCoil 1.7. When you go to settings -> mobile network settings -> APNs there is a APN in there called "VZWINTERNET" but on test 2 and 3 there is no APN and when you try to add one I get a FC. I don't know if that has to do with not being able to get LTE/4G or not. But do you guys think? Also when I switch to CDMA/EvDo I do get 3g but today I'm only getting 1x due to the outrage.
[Thunderbolt Android Development] ibuddha:
guys i have a problem i tried flashing the test2 zip and it seemed to flash fine...however it froze on me on first boot so i rebooted and now i'm stuck at the android boot screen!!! does anyone have any idea how i can get out of this? i was able to get the phone to boot up but when i tried to restart into recovery the phone froze again...please help!
[Thunderbolt Android Development] m00nshake:
He's right... I just lost my j0b but slayher is working damn hard getting AOSP on our phones... just d0nated $10 to Tony Layher... =)
[Thunderbolt Android Development] raziel36:
Turn the phone off and hold power+down to get to the bootloader, from there select Recovery. If you have a PG05IMG file on the root of your SD card, this won't work. If that's the case, hook the phone to your PC while it's "stuck" and use ADB to reboot into recovery.

adb reboot recovery

Should do the trick.