yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] death2verizon:
lol, my firmware hasn't been stock since 10 minutes after the ups guy delivered my SGS blaze to replace that f***ed up htc amaze i got conned into buying at the tmobile store....

htc amaze has its friggin antenna mounted to the "METAL" battery cover...wut kinda stupid bullsh*t is THAT? :silly:

edit: u may be right tho, it's quite possible some or all of those dialer codes only work with samsung/touchwiz based roms. i honestly can't remember which rom i was running when i used it. i've flashed both cm9 and 10 since doing it tho and havent had the problem again, so another possibility is to do a nandroid, flash a stock one, then flash back to cm10
[Samsung Galaxy S Blaze 4G] djcody:
I have problem with screen rotation on build 2012.11.07 all option checked for screen rotation what else I miss??

i mean don't want rotate or rotate ones and don't want back to previous position
[Samsung Galaxy S Blaze 4G] strungoutfan78:
Maybe being a little more specific rather than just stating you are having a "problem with screen rotation" would help us to help you.

Sent from a magical unicorn using CM10
[Samsung Galaxy S Blaze 4G] djcody:
Hi everybody, here is my problem

i run for some weeks ics custom rom because cm10 isn't stable for me and giving me sod and reboots. so 2 days ago I find on forum that cm10 is good now and I give another try. I did full wipe just like always never have any problems, installation went good included gapps.

After reboot and some minutes i discovered that my screen don't want rotate or rotate one way and don't want back to previous positions.

I decide to make one more installation with hope to fix problem, when i try do again full wipe i get that msg

Formatting / data......

Formatting / Cache....

Formatting / sd-ext....

E:format_Volume: make_extf4fs failed on on dev/block/mmcblk1p2

Formatting/sdcard/.android_secure....

Data wipe Complete

have no idea what to do now, any advice ??
[Samsung Galaxy S Blaze 4G] strungoutfan78:
Sounds to me like you have a corrupt sd card. Do you have another one available to test?

Sent from a magical unicorn using CM10
[Samsung Galaxy S Blaze 4G] dr4stic:
Is it not rotating in apps? I.e.. the native web browser or maybe chrome? How about the elements in the stock camera?

By default the launcher home app doesn't rotate, so if that's what you're seeing, then that's normal. You can change that in the Launcher settings.

Also, go into Settings -> Display -> Rotation and make sure everything there is set properly. Something may have happened where it was all turned off, got backed up to google that way, and is being restored every time to wipe the phone and set it back up.

I wipe and re-install my device all the time to test builds, as recently as last night. My rotation works as expected. Which version nightly did you install?
[Samsung Galaxy S Blaze 4G] Bradlees:
cwm updater

I thought I saw this discussed before, but I couldn't find it again after reading through this post, so I apologize if this is a noobish repeat question. I can't update/download the nightlies through cwm, is this a known issue?

I've been downloading the nightlies onto my computer and then copying them to an sd card to update. When I do this can I just flash over the current rom(an earlier release) without re-formatting or wiping everything?
[Samsung Galaxy S Blaze 4G] djcody:
My version is from 10-2012.11.08

don't rotate on web stock browser, gallery, camera only landscape mode, es file manager, calendar that what I have check.

also if rotate ones its only 90 degree and dont want back I need back to home screen to put it to horizontal

whats about that error when doing factory reset in cwm??

I check settings for rotation all are check too
[Samsung Galaxy S Blaze 4G] dr4stic:
The error from CWM is fine. The partition it failed on is for sd-ext. It's an extra partition you could set up on your SD card if you wanted to extend the system cache or create swap, etc. I don't know anyone that actually does that anymore, it's rare and unnecessary. Therefore when CWM goes to format it, it doesn't find it and throws an error. You're fine.

As for rotation. That's very odd. Which ICS custom rom? Did your phone ever run the stock ICS from samsung? Are you on the latest radio? Could you try going back to full stock and then re-root from there and then install CM10? The only thing I can think of is that maybe your phone doesn't have some driver or firmware. Otherwise, I'm at a loss. I hope you can get your problem worked out.
[Samsung Galaxy S Blaze 4G] djcody:
to go back stock I need use odin right??
[Samsung Galaxy S Blaze 4G] dr4stic:
That's called dirty flashing, and it should be fine for the most part. Just wipe your dalvik (in the CWM advanced menu). However if you run into weird issues that only you seem to have, you'll be expected to wipe your phone and retest to confirm it's a real issue. Therefore I recommend you take backups of your system (I like Titanium Backup Pro myself...)
[Samsung Galaxy S Blaze 4G] dr4stic:
Yes, there are threads in the forum. If you want to be doubly sure, you could go to stock GingerBread from samsung, and then update your phone through the computer using Kies. Good luck.
[Samsung Galaxy S Blaze 4G] DylanTheVillian:
So, a little off topic... But seeing that if I get this phone as a replacement I will be running CM10... TMobile offered to swap this phone in place of my HTC Sensation. I've compared the specs and they are even enough... The Blaze has a few over the Sensation and vice versa.... How do you guys like the blaze? How great is it having Official CM10? If you were in my position would you switch to the blaze or stay with the sensation?
[Samsung Galaxy S Blaze 4G] anactoraaron:
I have both phones and prefer the blaze (my wife uses the sensation). It's just faster and more responsive all around- it may be because the Blaze has more ram. Having an 'official' CM doesn't make it any better than an 'unofficial' CM, but it does mean you will get consistent nightly updates (which may or may not be stable).
[Samsung Galaxy S Blaze 4G] djcody:
looks like i brick phone I fallow instruction and went ok ( in odin pass complete ) but stuck in boot lop, cant go back to download mode anymore
[Samsung Galaxy S Blaze 4G] anactoraaron:
Search the forums please, this exact thing has been covered more times than I can count.
[Samsung Galaxy S Blaze 4G] asinglenoob:
I really love my Blaze, it's fast, never really lags on anything. It's not massive, yet the screen real estate is definitely better than that of the iPhone (I am a recent Android convert). The Blaze also feels great in the hand, the plastic body doesn't look or feel cheap, and in fact the back is almost rubberized so it feels very solid in your hands, no real chance of it slipping out as is the case with some plastic or glass backed phones. Battery life could be a little better, I get about 12-13 hours a day, but that's with only about 3-4 hours of real use and the rest of the time it's sitting in standby. Maybe I'm just not managing my battery settings well though I keep screen brightness at lowest possible setting. The awesome thing about this screen is that the colors are great, and even at my lowest brightness setting I can see the screen really well even in sunlight, definitely easier to use OLED screens in direct sunlight than it is to use LCD panels. There are some issues with the screen though, if you look closely quality is nowhere close to retina displays on Apple products. There is a lot of pixelation, especially with text but if you hold the phone the usual distance from your face you're not going to notice it too much. Another thing that worries me is that being an AMOLED screen, the screen is subject to faster wear than an LCD screen, and there is also the chance of burn in. I'm not sure how bad the burn in and wear on AMOLED's is but from everything I've read it's definitely something to be aware of. There's also the fact that the blue sub pixels wear faster than any of the other pixels in an AMOLED and seeing as how CM10 has tons of blue, I can't see that being great of the screen (even though it looks really nice). The photo quality seems pretty meh to me, but acceptable.

CM10 is great, there are a few little bugs here and there, but nothing massive, I get 1-2 screens of death a day, but all I have to do is hold down the power button for 10 seconds, and the tap it again and the phone restarts in a fairly short amount of time, it's annoying but workable. Also I've never once had a screen of death while using the phone, only while starting it up from sleep mode, so it's not like it will die on you when you're in the middle of something. Another thing to take into consideration is that at the moment camera flash can't be turned off in CM10, that's a little annoying to me. There's also the issue of storage, at this point there's no way to save photos or apps (in my understanding) to your SD card without some (cumbersome) (again in my opinion) workarounds. Otherwise I would rate CM10 as being one of the best mobile OS's that I've ever used, it surpasses iOS (in my opinion) in almost every way imaginable.
[Samsung Galaxy S Blaze 4G] anactoraaron:
Am I the only one to discover that the CM themes on the play store are AWESOME on our CM10? They all seem to work just fine. I'm using cobalt inferno - I love orange.
[Samsung Galaxy S Blaze 4G] DylanTheVillian:
I've done some reading... are the screen of deaths something everyone deals with? Is it just CM related ROMs or all custom ROMs... Some of the issues sound annoying and the unofficial CM for the sensation doesn't suffer from those issues but has a few of their own... How many chefs cooking for the Blaze?
[Samsung Galaxy S Blaze 4G] djcody:
well, I back to ics rom stock one, but my rotation don't work any way, maybe hardware problems
[Samsung Galaxy S Blaze 4G] asinglenoob:
Screen of death's are a problem for many CM10 devices from my understanding. As far as I know this isn't an issue with other ROMs. As I've said they rarely happen to me, perhaps 1-2 a day, and we're talking about 20-30 seconds of downtime while the phone is restarted. Some of the issues are a little inconvenient, but overall the pros far outweigh the cons for me at any rate. I would say, try CM10, and see what you think of it. I'm almost willing to bet that you would be sold on it even with the issues. As far as I know camera storage is on the road to being fixed. The screen of death issue is being looked at by many devs, however there doesn't seem to be any consistent thing that causes it so it may be a long time before it gets fixed, or it may never get fixed, we'll see. When you say chefs I'm assuming you mean how many devs are working on the Blaze? To my knowledge only dr4stic is working on our phone specifically (at least in the realm of CM10). There are several other ROMs for the Blaze, (none of which were very impressive to me) that are being worked on by other devs.
[Samsung Galaxy S Blaze 4G] DylanTheVillian:
We had a similar issue, screen off min CPU frequency was the culprit....
[Samsung Galaxy S Blaze 4G] mdneilson:
Fyi changing the brightness will fix the button backlights, even from the lock screen widget and status bar brightness mod.

Sent from Tapatalk on Android.
[Samsung Galaxy S Blaze 4G] blazetim:
On the latest build and running good.only had one sod yesterday.can you add the option to move the clock to the left side of the screen?
[Samsung Galaxy S Blaze 4G] marchingknight11:
I'm on 11-10 and still having sod fairly commonly. It happens at least twice every day, and sometimes more. There are some apps that seem to cause it (bad piggies, for example) but it also does happen a lot just sitting there. Instill haven't had any luck getting a logcat.
[Samsung Galaxy S Blaze 4G] dr4stic:
you're saying you can generate it relatively reliably?

Standard debugging techniques haven't helped, but lemme ask around and see if I can generate a debugging kernel for some specific drivers. Maybe that'll reveal something.
[Samsung Galaxy S Blaze 4G] strungoutfan78:
I'm getting something similar. There are 2 apps in particular that, while not officially a "SOD", completely freeze my device, requiring a battery pull. (One of them being Flow Free) If you get the debugging kernel in there I can get you a logcat as well. Dunno if it will help but worth a shot I suppose. I just assumed it was on the app developer's end.

Sent from a magical unicorn using CM10
[Samsung Galaxy S Blaze 4G] dr4stic:
Potential SoD Fix, need testers

Guys,

Based on the recommendations of some of the other devs, I've run a kernel build that should hopefully (cross your fingers) solve MOST (but not all) of the SoD problems. If this works, it likely won't remove them alltogether, but they'll be DECIDEDLY infrequent.

If you apply this, keep in mind I need a LONG TERM TEST. That means no upgrading or rebooting your phone unless you absolutely need to.

Go to my funhouse for more details.
[Samsung Galaxy S Blaze 4G] johnb380:
I'll bet it has something to do with running apps not compatible with jelly bean
[Samsung Galaxy S Blaze 4G] strungoutfan78:
That's what I was leaning towards. I sent the developers an email with a logcat as well. I figured this couldn't hurt to do as well though.:)

Sent from a magical unicorn using CM10
[Samsung Galaxy S Blaze 4G] chinabear13:
Thank you sir, just flashed and will let you know. Thanks again for all you do!
[Samsung Galaxy S Blaze 4G] chjema:
I cannot get thw GPS to work correctly on any CM based ROM. Full wipe does not help. GPS wroks perfectly in tweaked and Stock ICS. I cannot figure it out.

Lol I guess its the nasty weather here. Guess it helps to look out your damn window Hermit here today haha

Edit nope. Gps is still really bad with PA/CM hmm
[Samsung Galaxy S Blaze 4G] shaikmonster:
Anyone have trouble with the movie studio app?
[Samsung Galaxy S Blaze 4G] jdruc:
Same here, GPS is completely busted except in smart compass. Even google maps are hosed. Official update included. :(
[Samsung Galaxy S Blaze 4G] chinabear13:
Working for me, no issues
[Samsung Galaxy S Blaze 4G] djcody:
GPS working perfect for me on 2012.11.11 ver actually this most stable version I get so far, no problem at all, not single one
[Samsung Galaxy S Blaze 4G] marchingknight11:
I'm still having crashing issues that are unpredictable, so to be able to get a logcat of it, I'd like to pull the logcat through the terminal emulator and store it on the sdcard, rather than having to keep the phone plugged in all the time. however, the local adb server can't find the device itself. is this a bug or a feature (or am i just doing something wrong)?

---------- Post added at 11:47 AM ---------- Previous post was at 11:25 AM ----------

Answered my own question. adb isn't needed for gathering a logcat locally. just use the logcat command.

I've got a logcat writing to my sdcard perpetually, so if the device crashes again (or I notice any other problems) I'll make a note of the time and will have a log of what happened that I can send to dr4stic.
[Samsung Galaxy S Blaze 4G] miki755:
Root Galaxy Blaze after 4.0.4. update using Mac

Hello,

I apologize if my question does not belong to this forum but I would like to know the steps to root my Samsung Galaxy Blaze 4g after I updated its OS version to 4.0.4 via Kies.

I only have a macbook air (not PC) so I would like to know what software I need to use to accomplish that task.

Any tip is greatly appreciated,

Thank you
[Samsung Galaxy S Blaze 4G] BrownLarry:
I've heard heimdal works.
[Samsung Galaxy S Blaze 4G] anactoraaron:
CM 10.0.0!

I just started to download the latest 'stable' cm10 - 10.0.0 through cm updater.

I don't know what exactly is changed as I found that the latest nightly 11-12 is perfectly stable. No SOD, gps issue etc. Only issue I have is turning on network data from the notification drawer doesn't seem to work properly. Turning it on (so it lights up) actually turns it off and vice versa.

EDIT: I did discover with 10.0.0 that there's something causing a major battery drain. I unplugged my blaze to charge my wife's sensation before going to bed and when I woke up my blaze (with wifi off, screen off, basically nothing running) was at 82% battery. Phone idle was 56% and cell standby was 34%. Something doesn't seem right here. I'm updating to 11-14 nightly to see if it's fixed, otherwise I'm nandroiding back to 11-12. That's a big drain for 8 hours of standby/sleeping.

Edit 2: There's definitely something going on with CM10. I just updated my KF to a recent unofficial CM10 build and over about 24 hrs my KF completely discharged sitting untouched from 88% battery. On the prior build I was running it had been 3 days since I last used it or charged it (it was fully charged prior to me letting it sit) and I still had 90% battery.

This issue does seem to be resolved for the blaze in the 11-14 nightly build. 2 hrs of standby and 97% battery. I don't know what happened (whether there was something eating cpu cycles or an inability to properly deep sleep) but I would recommend staying away from the stable build 10.0.0.

I'm at 5 hrs now on the latest nightly and am at 94%. Don't know what happened but it's fixed.
[Samsung Galaxy S Blaze 4G] rush_ad:
Thanks for heads up, I was about to update my sister's Blade to CM10.

By the way, does CM10 have WiFi Calling feature?
[Samsung Galaxy S Blaze 4G] namaui:
Currently running 10.0.0 since it was released, been running since it was installed and I havent had any SoDs, and battery life was a bit weak the first day but it is back to normal now. 21+ hours on battery @ 40% left with moderate usage. :good:
[Samsung Galaxy S Blaze 4G] Ltitus8900:
Hi. Will the guys a CM continue to update this when you stop?
[Samsung Galaxy S Blaze 4G] Chitown021:
I hope they keep our device in the mix when 10.1 is released.

Sent from my Samsung Galaxy S Blaze.

---------- Post added at 07:41 PM ---------- Previous post was at 07:20 PM ----------

The 10.0 version seems really stable. The only issue I've been running into is random gallery FCs. The last one happened a couple minutes ago when I updated my Facebook app.

Sent from my Samsung Galaxy S Blaze.
[Samsung Galaxy S Blaze 4G] johnb380:
Ya Facebook messes my phone up a lot to the point that I just use friendcaster now it's way better 10 times faster and more features too and fully compatible with JB unlike FB
[Samsung Galaxy S Blaze 4G] jbats:
I was curious about what other users are setting their governor to and if changed which setting offered the best performance? I am fully aware this is mainly opinion based but nonetheless still curious.
[Samsung Galaxy S Blaze 4G] abser703:
So I'm getting a notification for a stable version of CM10. Is it legit or not?

Sent from my magical unicorn
[Samsung Galaxy S Blaze 4G] shaikmonster:
At this point CM is stable, but the kernel is still wonky.
[Samsung Galaxy S Blaze 4G] marchingknight11:
BTW, where did we land on customizing the camera save location? I remember a while back there was a patch for it, but it doesn't look like it ever got committed.
[Samsung Galaxy S Blaze 4G] squlnt:
I've found that when I have the phone on vibrate, and I receive a notification but press the power button before the vibration stops, the screen won't wake and I have to restart the phone by holding the power button. I've had this problem for a while with the nightlies.
[Samsung Galaxy S Blaze 4G] dr4stic:
Need testers

Anyone that used to experience the SoD regularly, please go here: I need your help. Thanks.
[Samsung Galaxy S Blaze 4G] marchingknight11:
I updated to 11-19 yesterday, and have since been having issues with my connection to google. after a couple hours, it will give me an alert notification saying "sign-in failed" or something like that, then doesn't give me a chance to sign back in. I'll take a couple screenshots and post them next time it happens.
[Samsung Galaxy S Blaze 4G] jbats:
Probably some maintenance on Googles part. I had a similar problem with yahoo the other day wait a day to see if time (meaning google) fixes the problem. If that dont work try unistalling your google apps and reinstalling a fresh gapps pack. Hope this helps

Edit: another thing to try is hitting the notification in the noti. bar. My google plus needed permission to access blah blah, hence give it the permission it requests

SGH-T769 CM10

1121 Build
[Samsung Galaxy S Blaze 4G] LiveFaster:
Under developer options, the setting to disable hw overflows does not stick when phone is rebooted. I am not sure if that's a bug or not, but I have to select it again after every reboot ( that makes my instagram work)

Sent from my SAMSUNG-SGH-T769
[Samsung Galaxy S Blaze 4G] Animosity:
Where have you been? O_o
[Samsung Galaxy S Blaze 4G] 2vivid:
I must say amazing job on all of this. Only had one sod and it was within the first 30 mins I stuck with unofficial forever because I was lucky enough to hardly ever get an sod. Going on a week or so now sod free. Thanks for your hard work :)
[Samsung Galaxy S Blaze 4G] shaikmonster:
On 11/21 and have had 3 SODs in the last hour. I'm not convinced this is all kernel... I still love it. No way I could go back to ICS.
[Samsung Galaxy S Blaze 4G] johnb380:
I've Givin up Cm10... Aokp is so much more stable with lightning zap kernel its has dr4stic SOD fix in it and haven't had an SOD for days
[Samsung Galaxy S Blaze 4G] jbats:
You should go look at The next change log , looks pretty serious. Plus cm 10.1 is right around the corner can't wait.

Also I haven't had sod since Tuesdays nightly. Idk if has anything to do with it but I also unchecked force 2d rendering in settings, not for that reason but to make androidify work properly
[Samsung Galaxy S Blaze 4G] jbats:
Did the Sod changes ever get committed? I haven't had a SOD since Monday and I've been using the phone like crazy. Ever since the Tuesday nightly, the phone is very stable, almost enough to make it your daily driver. Thx again dr4stic

SGH-T769 CM10 1124
[Samsung Galaxy S Blaze 4G] johnb380:
Yes the commits are in the newest nightly 24th look at the change log for T769 ull see 2 commits for our phone specifically

I'm not a Dev, I just flash alot.
[Samsung Galaxy S Blaze 4G] Ltitus8900:
Hello, is there a way to get photosphere working correctly? It refuses to calibrate and when I do manage to wait long enough, it doesn't save the image.
[Samsung Galaxy S Blaze 4G] johnb380:
I believe it's a kernel compatability issue it needs a 4.2 rom and kernel to run at full fps... Honestly were lucky to get the 4.2 camera working on our phone at all alot of phones won't run it at all it just fc's or reboots they're phones

And that's on Google not any of our Rom Devs email Google and maybe they'll fix it u can go download an app called 4.2 camera plus it works perfect Cuz its ported to our kernel base

I'm not a Dev, I just flash alot.
[Samsung Galaxy S Blaze 4G] Ltitus8900:
Thanks for the response. I figured it was something like that. Just was hoping because its such an awesome feature.
[Samsung Galaxy S Blaze 4G] mdneilson:
Is the OP still working on this ROM? My 11/25 version is freezing like mad, but CMUpdate is reporting no new versions. :?

Is anyone else having issues with the 25 version? If not, I'll try a full wipe since it is a dirty flash.
[Samsung Galaxy S Blaze 4G] johnb380:
Ya wipe system factory wipe and wipe davlik and reflash ROM and gapps this is the most stable cm10s ever been no sods for me anymore or reboots and I think dr4stic has done enough for us... and I think Cm is getting ready for another stable build or a RC build for our phone maybe RC= release candidate

I'm not a Dev, I just flash alot.
[Samsung Galaxy S Blaze 4G] eggytoasty:
Can someone tell me what the different is with the sizes of the nighties. One is 151.68 or .69, or the second is 128.48 or .46. any and all help will be greatly appreciated. Cheers.