yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Yes they do, but hopefully, as these aren't nightlys and haven't had all the other devices nonsense updated to break stuff, it should be pretty smooth,and good on battery..that is my goal.. Ya like that boot ani?..(of my design)
[Samsung Galaxy S Blaze 4G] xWolf13:
I like the broken glass part xD. This ROM does save battery. Especially when using the Broken dark theme. Decent and stable ROM. My brother is using CM10 at the moment as he needs speakerphone and camera working as it should. I'm using this on my spare blaze that I play music with. Good Good!
[Samsung Galaxy S Blaze 4G] johnb380:
Where is the download links at for the blaze? I Dont see them on the g+ page anywhere thanks in advance
[Samsung Galaxy S Blaze 4G] krazzdav:
It's there... Click official builds and the last one
[Samsung Galaxy S Blaze 4G] johnb380:
I see it now thanx.... My wife's got my blaze and I just flashed the newest cm11 nightly I think the 28th on her blaze and man is the battery great she worked 10 he's today and had 61 perc left after work so its way better than the July builds were but next time I go to flash something on her phone I'll give broken a try... Let me know how it is on features and battery life and stability...! Tia
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Stop by the community..you can find everything you want to know...I work to make it a good experience, so stop by, say hi, flash it, see what ya think..
[Samsung Galaxy S Blaze 4G] minkmendor:
i feel like this thread keeps going off track... this is supposed to be for cm11... just sayin
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Simmer..its my thread...
[Samsung Galaxy S Blaze 4G] minkmendor:
maybe if you ate a slice of bologna i could simmer!
[Samsung Galaxy S Blaze 4G] johnb380:
Hey ink on my wife's blaze running Broken os 9-28 build when she takes a pic the phone reboots any chance of a fix? Also max CPU freq won't change on kernel trickstermod I change it but when I accept it goes but to 1637000 or whatever it is! It runs so smooth tho but she takes a lot of pics and she doesn't appreciate ROMs like us she just wants her stuff to work lol but it def is way better than cm11... Thanx for you and the teams hard work
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Talk to Thomas ...he's your maintainer..its just my ROM..
[Samsung Galaxy S Blaze 4G] johnb380:
Hey Thomas anyway to get a fix for the camera reboot on latest build of broken os and the kernel max CPU not changing from 1.6ghz thanks for maintaining for our blaze... Might have to try this for my N4 soon !
[Samsung Galaxy S Blaze 4G] johnb380:
Had to put Cm11 back on my wife's Blaze... On Broken OS A bunch of apps were throwing code pages up it was weird... Along with the other few problems she needed something more stable on her blaze... On the other hand the 10-02 build of Cm11 is blazing fast and pretty smooth and stable if anyone was wondering...! Also she's getting pretty great battery life on these newer builds just wish we could get a current custom kernel version for the blazes Cm11 builds that would be great... Hint hint... [MENTION=4145127]thomas.raines[/MENTION] !
[Samsung Galaxy S Blaze 4G] thomas.raines:
I believe it's the kernel that is causing your issues. I'm having a similar issue with the weird code thing on web pages and gmail... I'm working on updating all my kernels and will post them as they come available... check the lz kernel thread later... Thanks for your support...
[Samsung Galaxy S Blaze 4G] xWolf13:
You made the whole Blaze community wait anxiously. Unless we have no more users for this phone /.\
[Samsung Galaxy S Blaze 4G] chweez:
i've been anxiously waiting too. There's been no new toys...? unless i have been checking the wrong thread... Can't wait for it to drop...:p
[Samsung Galaxy S Blaze 4G] thomas.raines:
it's fixed...

it's been fixed... and it has lz kernel built in...

I dropped it like last week... gotta follow our g+ thing guys... wait till the next release...
[Samsung Galaxy S Blaze 4G] osbaldov:
Can you post link please. Thank you
[Samsung Galaxy S Blaze 4G] InkSlinger420:
https://www.androidfilehost.com/?w=files&flid=18718
[Samsung Galaxy S Blaze 4G] johnb380:
Anyway we can get a flashable kernel for cm of lz?
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yeah, you can pull my sources and build it all you want... sorry guys but I'm way too busy to focus on a device that I don't use, don't get donations or kick backs for anymore, and/or just really don't have time...
[Samsung Galaxy S Blaze 4G] osbaldov:
Is there a guide? I'm a noob at building.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
All over the place..there is a search function in google :p
[Samsung Galaxy S Blaze 4G] minkmendor:
stability

Hey guys i see noone has posted lately on they're luck with the newer nightlies. Ive been running 10/13 rls for a few days now and the cpu issue seems to have vanished. Will keep updated if anything changes
[Samsung Galaxy S Blaze 4G] mk1277:
Thanks Mink. I've been sitting on a build from early September wondering myself about the new nightlies. I'll give a newer one a try too.
[Samsung Galaxy S Blaze 4G] jafferkhan:
i wanted to ask, which files do we need in order to theme the battery icons from UOT Kitchen for ICS? I've tried using the framework.res, the touchwiz and the systemui, but it gave me a bootloop.... any suggestions?

Sorry for asking here since it is the only active thread
[Samsung Galaxy S Blaze 4G] minkmendor:
no problem dude, i was sick the damn thing freezing and rebooting all the time.
[Samsung Galaxy S Blaze 4G] minkmendor:
edit - 1 reboot needed since then :) screen wasnt coming on, just the lights so had to reboot. not bad for a few days tho!
[Samsung Galaxy S Blaze 4G] dsulliii:
10-22 Nightly has Forwarding error.

Installed the cm-11-20141022-NIGHTLY-t769.zip and the ever-repeating interminable "Call forwarding Service was enabled" error has returned.

I tried everything that I'd done last time to get it to go away with absolutely no success. Up-to-and-including... format system/data/cache, factory reset, clear cache, clear Dalvik. Clean install, clean install with clean GAPPS installs. Nope, nothing made it go away.

I even waded through the messages to enable call forwarding, reboot, disable call forwarding, reboot, you name it.

It won't go away.

Unless anybody has better luck, my advice is to avoid this nightly and wait for one where the bad-boy forwarding problem gets resolved again.

Reverting back to 10-19.

-- David
[Samsung Galaxy S Blaze 4G] jafferkhan:
you're saying the 10-19 is the most stable? kinda tired of trying different roms here and there... if your experience is good, should i go for the one you've mentioned?
[Samsung Galaxy S Blaze 4G] dsulliii:
Hey jafferkhan, sorry that I can't really say. I follow the "NIGHTLY" scenarios because I enjoy seeing how things are coming along, and I like to try out new stuff and experiment with changes. It's just part of my tinkering nature. If I was looking for a stable build, I'd definitely not be trying every nightly that comes out the way that I do.

That being said, I can't really say that 10-19 is stable. It's stable enough for me as I await the next build so that I can poke around in it some more, though. The last few-or-several nightlies frequently begin some kind of background all-consuming process that brings its ability to run apps to a near standstill. So that's not necessarily stable. It's okay for me, though, because when it misbehaves, I try to figure out what's going on. And if I can ever figure it out, I'll post my hypothesis and maybe thus contribute to the developers. Until then... it's going to be the not-the-most-stable road that I'll follow.

You know, the first CM build listed (the cm-10.0.0-t769.zip one), works just fine and isn't significantly different than these nightlies. It's not KitKat, but it sure is extremely stable.

So if you're looking for a recommendation, that's mine if you're wanting to stop trying the different ROMs. If you just want to slow down a bit, and if you're willing to re-boot when the OS decides to crawl to a stop, then yeah, stay with the 10-19 until you see that somebody says there's a better nightly available.

But following the nightly trail has its inherent risks... which I'm always happy to take.

Good luck.

-- David
[Samsung Galaxy S Blaze 4G] minkmendor:
hehe it's funny u mention the 10.0 rom. That was the least stable for me, rebooted every 5 minutes :D. But yeah everything seemed to work as intended other than that hiccup!
[Samsung Galaxy S Blaze 4G] jafferkhan:
understood, thank you for the detailed analysis david, your review will help me out big time. I have tried the Cm10, well one of the ones posted, the stable one i recall. Everything was good except the touch response, it felt i had to push the selection, that isn't the case with 4.2 and up, the touch response is excellent on those. I might be missing out something, because i tried to incorporate build props to make the touch response smoother and more fluid, but i couldn't... any suggestions i could use? if i can make the touch response sensitivity better, ill flash Cm10 now :)

---------- Post added at 05:24 PM ---------- Previous post was at 05:23 PM ----------

i've tried it myself seemed pretty stable for me. could be a bad download in your case. The only thing wrong is the touch sensitivity... it isn't as sensetive as it is on other roms apart from 4.1.2... ive tried them all they're the same. plus i can't incorporate a build prop, it makes no difference...
[Samsung Galaxy S Blaze 4G] dsulliii:
Sorry. I think I'm getting too old. It's been too long ago that I don't recollect if I did or not.
[Samsung Galaxy S Blaze 4G] ProlificSwan:
I can confirm that this issue appears with the 10-23 install as well. Wish I had checked here before updating. Restoring a backup was no good for me either. Guess I'll live with it for a while.
[Samsung Galaxy S Blaze 4G] minkmendor:
i hear ya man, i can barely remember last week :p
[Samsung Galaxy S Blaze 4G] brut7:
"Call forwarding Service was enabled" bug still present in the 10/23 nightly so it's back to 10/19.
[Samsung Galaxy S Blaze 4G] dsulliii:
10-23 Nightly still has call forwarding bug from 10-22

Agreed. I didn't do my normal full-wipe testing with the 10-23 since it was futile with the 10-22. I reverted back to 10-19 as well.

-- David

---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
[Samsung Galaxy S Blaze 4G] johnb380:
It wont let me quote ur post [MENTION=2658307]jafferkhan[/MENTION] anyways Broken OS the new build has [MENTION=4145127]thomas.raines[/MENTION] new lightning zap kernel included and many fixes from the earlier builds I believe everything is working that should be... All I can say is my wife hasn't complained so download it 10-22 build is the one I recommend and flash it and put it thru its paces and report back here... Also the G+ link works fine for me on Chrome idk why it won't work for you but if you go on G+ and search Broken OS you'll find it in a few clicks!

Good luck and if I help Thank me its only a click away!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
BrokenOs is my creation as lead dev and I find it quite nice :p . It is SLIM based aosp and the latest release was dropped before **** got busted with the call forwarding...The normal scanner apps and such are still borked (of course) but as for battery, performance, options, and such, I pride myself on making quite a beast...Not here trying to sell the thing, just letting those who have followed my work for awhile, who's at the helm...Thomas is yalls maintainer for the blaze, helped out in ROM source (with a few things ;) )and as my i577 is toasted, I create the rom and maintain for my flo (n7-2k13)...You guys are welcome to try it out..till if and when cm gets the **** back together..just putting it out there..

sent from my Broken Nexus 7 via this damn XDA app...
[Samsung Galaxy S Blaze 4G] jafferkhan:
[MENTION=3556013]johnb380[/MENTION] wow that's amazing... great reviews and such, and i've just managed to see the rom itself, looks very cool... scanner apps i don't care about, as long as the needed things work smoothly... thanks everyone for the review and helping me get the best of this old beast... it really helps...

:)

---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------

you've always been very helpful ink, this wasn't an exception, we all expect nothing less than staggering work from you and your team... that's awesome :good:

---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
[Samsung Galaxy S Blaze 4G] johnb380:
Did u use the link I gave you https://www.androidfilehost.com/?w=files&flid=19489 go here scroll down look for 10-22 build for t769

Here the direct link sorry OP

https://www.androidfilehost.com/?fid=95747613655048962

Sorry its 10-21 my bad lol
[Samsung Galaxy S Blaze 4G] jafferkhan:
is bluetooth working on broken? i need it for music
[Samsung Galaxy S Blaze 4G] daboross:
I was having this issue as well with the 10/23 nightly. It *did* work though just to flash back to 10/19 then enable and disable call forwarding. Have you tried that?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
It is on other devices..not the best guy to ask about the blaze

sent from my Broken Nexus 7 via this damn XDA app...
[Samsung Galaxy S Blaze 4G] ProlificSwan:
I did exactly as you say and it's gone now. Thanks for the help!

All this talk of BrokenOS makes me want to give it a shot now. I'm not as much a fan of the risk as others might be.
[Samsung Galaxy S Blaze 4G] johnb380:
Just make a backup flash and try it out man.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Risks?....the ROM is solid...feature packed and would only have the same hw issues cm does (without the call forwarding bug)

There is NO additional risk to flashing the thing except if you are a crackflasher and need to break your device every day with nightlys cause we dont do those..try to release every 2 weeks after I'm done in source, and devices are built for and tested prior to dropping to the public..I care about the end user experience..

sent from my Broken Nexus 7 via this damn XDA app...
[Samsung Galaxy S Blaze 4G] ProlificSwan:
Apologies, my wording left room for misunderstanding. My intention was to state that I plan on trying Broken OS as it appears less risky than the CM nightlys (unlike dsulliii who enjoys tinkering with the nightlys). Everything I've been hearing about it is good, and I like your release plan.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
All good bro..just clarifying our team / ROM experience and how we roll..

sent from my Broken Nexus 7 via this damn XDA app...
[Samsung Galaxy S Blaze 4G] jafferkhan:
I should've done broken sooner, it's fantastic and I love the tweaks that come with it. The battery is solid and the rom is as stable as anything I've tried.

I need some help regarding keeping the capacitive keys lit, I don't use the touch ones and they just keep turning off... Perhaps a build prop would help? I only know of the virtual soft keys on and off...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
The hw keys???...keeping em lit??..that's a battery killer by itself..just saying

sent from my Broken Nexus 7 via this damn XDA app...
[Samsung Galaxy S Blaze 4G] dsulliii:
10-24 Nightly still has call forwarding bug from 10-22&23

It didn't take much to determine it, but the current nightly still does not work due to the ever-repeating interminable call-forwarding notification and toast bug. Build is unusable, so reverted back to the 10-19 version again.
[Samsung Galaxy S Blaze 4G] minkmendor:
appreciate the testing sir!
[Samsung Galaxy S Blaze 4G] mpop235423542567:
the bluetooth bug

Question what is the status on the crashing of bluetooth. I have an android ware device, and I have noted that the CM-11 bluetooth crashes 3 to 5 times a day, and the only solution is to reboot. I have (the very few times it been offered, when trying to turn bluetooth on from the android wear app.) submitted the crash log.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
This device HW is no longer actively being worked on in CM eyes...as far as I know all devs have moved on voluntarily or forced by no longer owning the device...Thomas still has his, and will be building Broken, but I'm not sure what his plan is for active development..

sent from my Broken Nexus 7 via this damn XDA app...
[Samsung Galaxy S Blaze 4G] dsulliii:
10-25 Nightly still has call forwarding bug from 10-22,23&24

The new 10-25 nightly still does not work due to the ever-repeating interminable call-forwarding notification and toast bug. This build is also unusable, so I do NOT recommend anybody trying it. Reverted back to the 10-19 version again.

The last version that works (no forwarding bug):

cm-11-20141019-NIGHTLY-t769.zip

The most recent versions that are unusable due to the forwarding bug:

cm-11-20141022-NIGHTLY-t769.zip

cm-11-20141023-NIGHTLY-t769.zip

cm-11-20141024-NIGHTLY-t769.zip

cm-11-20141025-NIGHTLY-t769.zip​
[Samsung Galaxy S Blaze 4G] dsulliii:
The following was posted on the cyanogenmod forum this morning regarding this problem. I haven't tested the 10-26 just yet (will soon, though), but I am sure that it will not work either. Don't anybody else bother trying to test it because it's surely going to fail. (I hope I won't end up eating my words <grin>.) ANYWAY, when this happened previously, it was an RIL problem. And as you can see from the proposed fix, that's exactly what they're going to fix. So we should be in business soon again, folks. Yay.

---------- Post added at 07:54 AM ---------- Previous post was at 07:47 AM ----------

Note: Refer to previous post... this bug is slated to be corrected again.

The new 10-26 nightly still does not work due to the ever-repeating interminable call-forwarding notification and toast bug. This build is also unusable, so I do NOT recommend anybody trying it. Reverted back to the 10-19 version again.

The last version that works (no forwarding bug):

cm-11-20141019-NIGHTLY-t769.zip

The most recent versions that are unusable due to the forwarding bug:

cm-11-20141022-NIGHTLY-t769.zip

cm-11-20141023-NIGHTLY-t769.zip

cm-11-20141024-NIGHTLY-t769.zip

cm-11-20141025-NIGHTLY-t769.zip

cm-11-20141026-NIGHTLY-t769.zip​
[Samsung Galaxy S Blaze 4G] jafferkhan:
they are battery guzzlers, since i've got two batteries i've no issues... i still would like the hw keys turned on till the screen's turned on...

still, any workarounds or a build prop to get those working till the screen's turned off? :)
[Samsung Galaxy S Blaze 4G] mpop235423542567:
Thanks for the information. I do appreciate your honesty there.
[Samsung Galaxy S Blaze 4G] dsulliii:
10-27 Nightly still has call forwarding bug from 10/22-10/26

The new 10-27 nightly still does not work due to the ever-repeating interminable call-forwarding notification and toast bug. This build is also unusable, so I do NOT recommend anybody trying it. Reverted back to the 10-19 version again.

The last version that works (no forwarding bug):

cm-11-20141019-NIGHTLY-t769.zip

The most recent versions that are unusable due to the forwarding bug:

cm-11-20141022-NIGHTLY-t769.zip

cm-11-20141023-NIGHTLY-t769.zip

cm-11-20141024-NIGHTLY-t769.zip

cm-11-20141025-NIGHTLY-t769.zip

cm-11-20141026-NIGHTLY-t769.zip

cm-11-20141027-NIGHTLY-t769.zip​
[Samsung Galaxy S Blaze 4G] InkSlinger420:
As reported to Uber (the OG CM guy for the blaze) he is aware of the issue, and seems to be affecting most if not all msm8660 devices..there is a patch in the works, but it isn't done yet...

http://review.cyanogenmod.org/#/c/75569

Recent RIL changes got merged and now the maintainers over there for several devices need to unbreak what those changes did...All in time, but be aware the devices are no longer high priority to the big wigs...

sent from my Broken Nexus 7 via this damn XDA app...
[Samsung Galaxy S Blaze 4G] Sydius08:
Getting that annoying call forwarding notification bug. The last stable nightly you guys say is 1019, does anyone have the link to it?? The one on CM isnt working
[Samsung Galaxy S Blaze 4G] minkmendor:
i have the 10/13 if it helps
[Samsung Galaxy S Blaze 4G] Sydius08:
Do you have a link to the 1013 .zip nightly? Or the 19th??
[Samsung Galaxy S Blaze 4G] brut7:
http://download.cyanogenmod.org/?device=t769

I tried Ink's broken and it works great too.
[Samsung Galaxy S Blaze 4G] dsulliii:
Forwarding problem APPEARS to be gone!

I am ecstatic to share that I have been running the latest (10-28) nightly this morning and find it to be just-as stable as the 10-19 one was.

I did notice in the change log that they mentioned a RIL fix. SPECIFICALLY for Samsung:

So for any of you having trouble locating the 10-19, I'm guessing that you have a great chance of today's cm-11-20141028-NIGHTLY-t769.zip nightly probably being just as good.

THANKS CM11 developers!
[Samsung Galaxy S Blaze 4G] minkmendor:
nice dude thanks for the testing! my 10/13 cpu issue has come back up :/ do me a favor and keep posted to see if it happens on the 10/28? thx ;)
[Samsung Galaxy S Blaze 4G] dsulliii:
The cpu still tends to arbitrarily take off and cycle all on its own. I added the "Cooler Master" app that tends to get it under control most of the time. Other times, I just reboot it.
[Samsung Galaxy S Blaze 4G] minkmendor:
figures... this never used to be an issue a few months back. i wonder if theres someone we can report it to
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I already said that this device no longer has a full time maintainer for CM...I can relay messages to the guy who used to be, and still helps out a little as i believe he still owns one..but again, i started this thread as he didnt want to keep up with it...I think the cpu race condition is actually written into **** on purpose as multiple devices have it..It just affects you guys more with the age and specs of the phone..
[Samsung Galaxy S Blaze 4G] minkmendor:
yea i hear ya ink... it would be cool if you could relay the message as maybe some magic will come from it :p Im still looking for a better phone similar in size btw if anyone has suggestions.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
will do
[Samsung Galaxy S Blaze 4G] mikeck:
My wife and two kids have bought 2 LG Optimus F6s, and one Optimus F3 (not F3Q with hardware keyboard)

You can find the new on ebay for $110 and $100 respectively. F6 , F3

The F3 has the same size screen as the Blaze but the phone is slightly smaller. The F6 is slightly bigger. The F3 has great battery life, the F6 has good battery life. They both have JellyBean.

My kids bought MetroPCS branded phones because they were cheaper at the time and unlocked them to use on T-mobile. They also got the unlock code via ebay for about $2. I hope that's not unethical as T-mobile now owns MetroPCS. Wifi calling works on T-M with the MetroPCS phones.

These phones suffer from limited memory like the Blaze. They have very little development but are fairly easy to root. I was worried that because the CPU specs are less than the Blaze, dual core 1.2GHz vs the Blaze 1.5 GHz that they would be really slow but they are snappier than the Blaze. I think the CPU is similar to the 1st Gen Moto G.

XDA doesn't have a forum for these phones but Android Forums does. Here's the F6

Here's the F3 page. See the bottom of the page for root sub-forums

Maybe these phones are cheap enough to hold you over till the next phone.

I selfishly bought the 1st Gen Moto X now available for $250 with 16 GB or $300 with 32 GB.