yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] goranak2000:
Same here, Maps 6.10.0 crash few seconds after been loaded w/CM9 aug 15
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Braaank:
You should do a wipe cache, erase data from settings >> app >> maps or probably you should change you kernel flashing a new one
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] boobiestar:
I have also the same problem. Wiping cache changes nothing. I use cm9-p4-20120814.zip ROM.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] teddybaerd:
Same issue here on Ganbarou CM9.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] isthisagoose:
I updated to the latest CM9 nightly last night, cm-9-20120819-NIGHTLY-p4wifi, and Maps is still crashing.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] GazaIan:
6.10 is buggy. I only updated it on my Sensation and it causes reboots when I use it, and causes reboots for Rezound users as well. Guess we all have to roll back or wait for an update.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] isthisagoose:
Can anyone post the previous .apk? I haven't been good about keeping Titanium Backups, I admit.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] GazaIan:
Here's version 6.9.2 - http://goo.gl/4p2O9
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] goranak2000:
thank you, 6.9.2 is OK, no crash.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] goranak2000:
new google maps 6.11 = same crashes.

back to 6.9.2.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] fix.kowalski:
p4wifi, update Maps to 6.11.1. Same problem. The crash occurs each time I enter an area that is cached for offline use, or when I try to modify the offline settings.... or after just a few seconds. Not only the app crashes (that would report the issue to Google, which could be useful), but it directly crashes the tablet (possibly a kernel panic, I have no console so no clue).
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] oopewan:
I'm having this issue with maps crashing my Samsung tab 10.1 AOKP milestone 6 and my Sensation running cyanogen 9 and when I flashed revolutionary rom with sense. I noticed on the sensation in location settings the GPS source was not checked off (cyanogen). After I chose internal source the problem stopped. There is not this option on the tablet AOKP so it still crashes. Not sure if anyone else is seeing this issue.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] MrFaxus:
Same problem here, with Galaxy Tab 10.1 P7500 on latest Ganbarou ROM. Current GMaps reboots the tablet after few seconds. I looked for GPS Source setting and it's present on Ganbarou ROM. However, it is correctly checked and problem still persists. Looks more like a kernel/driver bug invoked by GMaps, putting tablet into kernel panic.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] antz69:
galaxy tab cm9 maps crashes

I have this issue as well. Its a version conflict. You need to install v6? Or something like that. Anyone have the link? Its somewhere on droid basement i just havent found it
[Sprint Samsung Galaxy S III] Ls1ssz28:
I have searched and tried everything I could think of or find. The commercial makes this feature look great and want to give it a shot, but I can't get it working, any ideas?

I'm rooted and running blazer Rom
[Sprint Samsung Galaxy S III] gpgorbosjr:
Settings > Language and input > Voice cmd for apps needs to be ON. Also click on it and make sure the Incoming calls box is checked.
[Sprint Samsung Galaxy S III] Ls1ssz28:
Just double checked that is turned on and unless I have to yell or something to make it work... It still continues to ring when ever I say answer or reject
[Sprint Samsung Galaxy S III] gpgorbosjr:
I've never actually used it so I don't know how well it works...I'm going to try it now. Maybe it isn't recognizing your voice.

EDIT: Didn't work for me. Maybe it is broken in Blazer (I'm running Blazer 1.7) or it didn't work that good to begin with.
[Sprint Samsung Galaxy S III] jhuff83:
On blazer as well. Reject seems to work and answer works too.
[Sprint Samsung Galaxy S III] gpgorbosjr:
Do you have to put your phone to your head like your talking on it for this feature to work?
[Sprint Samsung Galaxy S III] jhuff83:
Seems hit or miss. I do have to kind of raise my voice. Probably because the ringtone is loud.
[Sprint Samsung Galaxy S III] Ls1ssz28:
I'm not sure if this matters but my phone is on vibrate does that matter?
[Sprint Samsung Galaxy S III] Citizen Snips:
This is a cool feature, but I had trouble getting it to work with the FreeGS3 rom as well.
[Sprint Samsung Galaxy S III] Special_opps:
Vibrate has to be off in stock Rom. Not sure about blazer prolly off.

GS3
[Samsung Galaxy S Blaze 4G] dr4stic:
Folks,

There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..

It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...

I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.

Hell, it'd be nice if we could even just get a date.
[Samsung Galaxy S Blaze 4G] Chitown021:
I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.

If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.

If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?

Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.

Sent from my Samsung Galaxy S Blaze.
[Samsung Galaxy S Blaze 4G] chjema:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
[Samsung Galaxy S Blaze 4G] crazydrummer95:
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us
[Samsung Galaxy S Blaze 4G] dr4stic:
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.

I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.

Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.

I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.

I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.

You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone :)
[Samsung Galaxy S Blaze 4G] Chitown021:
Yeah, a 720p screen would have been nice... thanks for the detailed explanation.

I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB. :)

Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).

Sent from my Samsung Galaxy S Blaze.
[Samsung Galaxy S Blaze 4G] danTM:
Yes lets please do this.

T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182

I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755

Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.
[Samsung Galaxy S Blaze 4G] heavenlydemonic:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.

And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...

If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
[Samsung Galaxy S Blaze 4G] chjema:
Dr4stic

If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
[Samsung Galaxy S Blaze 4G] AwesomeTurtle:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
[Samsung Galaxy S Blaze 4G] megatherian:
I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.

I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.

If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.

I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.

Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.

I know this all sounds cynical but I've seen this show before.

Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.
[Samsung Galaxy S Blaze 4G] L7ChrisL7:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
[Samsung Galaxy S Blaze 4G] dr4stic:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back :)
[Samsung Galaxy S Blaze 4G] dr4stic:
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?

And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.

And don't get me started on the underutilisation of the video hardware.

No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.

This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.

If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.
[Samsung Galaxy S Blaze 4G] L7ChrisL7:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
[Samsung Galaxy S Blaze 4G] dr4stic:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone ;)
[Samsung Galaxy S Blaze 4G] L7ChrisL7:
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.
[Samsung Galaxy S Blaze 4G] spartanerik:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions

^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
[Samsung Galaxy S Blaze 4G] anactoraaron:
here's a thread we can vent at!

I already did - rather I saw a post and have decided to bump it daily so it remains at the top.

http://support.t-mobile.com/thread/31124?tstart=0

Create a support account and let's let them know they need to get this done!!!

Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
[Samsung Galaxy S Blaze 4G] spartanerik:
http://support.t-mobile.com/people/tmo_erica

Try sending an email to TForce@t-mobile.com and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction
[Kindle Fire Q&A, Help & Troubleshooting] techboydino:
Helped a buddy setup his drivers so he could use the Kindle Fire Utility. ADB recognized and he wanted to do the rest on his own. He told me when he was flashing the bootloader there was an error on his machine and the program quit. Now the device is stuck on the KF logo and nothing shows up under device manager except a generic USB device that cannot be recognized. I tried it on my machine which has the KF drivers and still nothing. Anyone have any ideas? The UnBrick utility does not work since nothing can be seen in ADB. Thanks.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
It's actually pretty rare to have a messed up bootloader and still have the device show anything on the screen at all. My guess is that it would most likely be a Windows problem.

On the off chance that it is a broken bootloader, the only to fix it is via USBboot + "shorting trick". In either case, it's likely you'll have to get very familiar with Linux.
[Samsung Galaxy Fit GT 5670] Suranjan16049:
google play update v3.8.15

http://phandroid.com/2012/08/15/goo...play-store-gift-cards-and-wishlists-download/
[Samsung Galaxy Fit GT 5670] Avilove.Cullen:
Posting review soon
[Optimus One, P500, V Q&A, Help & Troubleshooting] krazzyvishal:
This is a modified Phone.apk for CM7. It looks like the ICS call screen when you receive a call or dial a call.

The problem is, the app isn't fully perfect with the call screen's UI on our O1. This was made for Galaxy I5500 or something by Abhishek.

The original thread for it is here : http://madteam.co/forum/customizations/modified-phone-apk/

The screenshots in the original thread are not what it looks like on our O1, the app works but UI is misplaced.

So I am requesting anyone of you to make it proper. I would have done that, but with my knowledge, I cant do such hardcore modifications. :(:silly:

It will be awesome if someone of you does that for all of us.

Qualcomm disappointed us everyone else I would have never requested for this... :crying::crying::crying:
[Optimus One, P500, V Q&A, Help & Troubleshooting] :
I think, this phone.apk is for HDPI, we can try to resize the pictures in that. Btw, just use an ICS theme, it's better, and if you're calling someone, it has an ICS-like UI.

Anyway, I can have a look over that

EDIT: When I'm calling someone, I can not even see any button... Can you post a screenshot of it, as I need to know how it looks right now, otherwise I don't know what the problem is

Please press THANKS, instead saying thanks.

Protos State:

Build:

protos-gb-one-100-1000

protos-gb-one-100-1001

protos-gb-one-100-1002

protos-gb-one-100-1003

protos-gb-one-100-1004 (17/08/12)

protos-gb-one-100-1005 (18/08/12)

protos-gb-one-100-1006 (18/08/12)

protos-gb-one-100-1007 (18/08/12)

protos-gb-one-100-1007 (18/08/12)
[Optimus One, P500, V Q&A, Help & Troubleshooting] weignewrenzsean:
i use rocket dial and theme is ics, it works great on my O1 using hybridCM9
[Samsung Galaxy Nexus] Gja88:
Looking for a complete stock MMS app that isn't themed with emoji support (like the cm10 one that was recently released). Anyone have this available? I use another ROM atm and emoji support isn't supported right now, and I prefer the stock look.
[Samsung Galaxy Nexus] Gja88:
Mods please close thread. I was able to solve/find my request.
[Samsung Galaxy Nexus] Kryptonian_Knight:
Where
[Samsung Galaxy Nexus] buzzcomp:
Please share it with us ...
[Samsung Galaxy Nexus] Gja88:
Alright what I did was downloaded the cm10 Kang fits made and found the mms.apk in the system files. It works perfectly for bamf paradigm, but I can't confirm for any other Roms. This is cm10 work so I take no credit whatsoever for it. I would like to also mention I did this with a toro/verizon device so I can't verify if it works for GSM (even though it should).

How to install:

Using root explorer, go to system > app and find your current mms.apk and rename it to mms.apk.bak (do this step in case the new mms doesn't work, so you can rename your old apk back just in case.)

Move the downloaded apk in this post to the same folder which is system>app folder.

Restart your phone and it should be installed and working.

Edit: forgot to mention that once the MMS is installed to turn on emoji support under the MMS settings in the bottom. Any questions ask away.
[Samsung Galaxy Nexus] lsv-1:
It doesn't work on stock JRC03C, force closes.
[Samsung Galaxy Nexus] haleybob1228:
Hopefully people don't get upset about me replying to an old thread but I used the above Mms.apk and found that it didn't have CM10's "Quick Reply" so I copied over the emoji pngs used by Gja88 into the newer CM10 MMS app.

Since this was the only thread that I could find with the non-Android-ified emoji I will put up my Mms.apk too. This has no Android creature emojis (instead they all look like the emoji on the iPhone) and it has CM10's QuickMessage feature.

Thank you Gja88 & CM10 for the original leg-work here, please read Gja88's earlier posts. I have only tested it on my LTE GNex running CM10 M2
[Galaxy S III Q&A, Help & Troubleshooting] SephiZ:
Hello !

i have some question to ask to the community since i can't really find answers to satisfy me ( maybe becose i'm doing bad research due to my bad level in english and by the way i apologize for that. )

- i would like to find more informations about the different permissions off application to understand more precisely the consequences.

- i'm maybe a bit paranoid but when i see an application with " your personnal information " , " phone calls " i always think that developers have access to my personal data and can ( even if illegal, i dont believe all the people develop free application for the lulz ) sell it to commercials

- is it possible to block the access of an application to this data, a typical exemple is Facebook application that have access to way more thing that it must do : " your personnal information " and "phone calls " i dont understand why it is usefull for the application to work properly.

any kind of help to improve my vision and understanding of this would be helpfull.

thanks and sorry for my bad english.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Firewall blocking via an Antivirus

http://www.appbrain.com/app/lookout-security-antivirus/com.lookout

Many apps on the market like .

http://www.appbrain.com/app/appbrain-ad-detector/com.appspot.swisscodemonkeys.detector

jje