yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] njstein:
Have you tried a clean flash with older nightly?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
And that's the risk with downloading and using nightlys every day..hence the disclaimer...if ya wanna blame anyone, blame Steve kondik over at cm for merging so many commits so damn fast...lol...I have no responsibility of what gets added to source..I just try to help make what they add not break the hell outta this device..I have spoke with uber, the true cm maintainer, and he is also looking into it..and the fact that we are RIGHT around the corner from losing support as cm is doing another legacy device cleanup...just a matter of time...
[Samsung Galaxy S Blaze 4G] minkmendor:
ruh roh- i hope this doesn't lose support - The phones not that old, i could see them ditching stuff like the kindle fire.... oh and BTW i fresh installed 3/1 release. got the stupid call forwarding message but swiped it away and it hasn't come back. and [MENTION=5190980]InkSlinger420[/MENTION] ..... i agree that its a bad move to put so many commits in one release!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
The problem isn't the amount of commits, I have been in code review and have watched commits be merged that have -2 (for those who know what that means) and say they break stuff for other users in the comments, with utter disregard for other devices still gets pushed...Its a busy place over there, and more now than ever, 1 step forward, and 2 steps back...
[Samsung Galaxy S Blaze 4G] Jserrano56:
I hope we don't lose support any time soon...yet again the blaze is 2 years old...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I'm not saying that's gonna happen, but merely that things like the camera blobs being nothing more recent than ICS and such issues we have with hardware, the fact that no stable release will probably ever be issued for our devices may make the difference..
[Samsung Galaxy S Blaze 4G] minkmendor:
heh the only "stable" release for this phone doesn't even work. It reboots every 5 minutes. I think it was cm 10.0.... anyways does your guys;s vid camera work at all? mine cant record, it lets u press button then does nothing.
[Samsung Galaxy S Blaze 4G] car vs driver:
We are looking into the problem. In short there was a f-ckton of changes merged on 4/3 related to the InCall UI, telephony and frameworks packages.

It's going to take time to sort through all of it to understand why this device specifically was negatively impacted. I would recommend sticking with the 4/2 build until we can sort it out.
[Samsung Galaxy S Blaze 4G] dsulliii:
Okay, ink... I'm no chicken. I see there's a 20140306 nightly this morning. I will give 'er the ol' college try and let you all know in about an hour.

---------- Post added at 06:45 AM ---------- Previous post was at 06:25 AM ----------

Sorry about posting that last comment on your post, car vs driver... I clicked the wrong button.

BUT THERE'S GOOD NEWS!

When I installed 04/06/2014, I still got the interminable forwarding pop-ups as well as the notification icon for forwarding. EVEN though my phone wasn't forwarded.

THIS time, I struggled through all the pop-ups until I could get to phone settings whereupon I "enabled" forwarding. The pop-ups stopped IMMEDIATELY and did not return.

So I powered the phone off and restarted it.

BAD NEWS... is that after the restart, the pop-ups returned (along with the notification icon -- which SHOULD have since it's forwarded now).

FUNNY THING IS.... after clicking through several dozen pop-ups, they stopped. INDEFINITELY!

So.. now that it wasn't so difficult (due to the absence of pop-ups), I went back to phone settings and UNFORWARDED the phone. ONCE I got to the phone settings screen, I was barraged with the pop-ups again. I finally got "disable" clicked.. and was still barraged.

Returning to the home screen, the notification icon was still there for "forwarded". I called the cell phone from my home phone, and it was NOT forwarded, just as it shouldn't have been. BUT... the pop-ups kept bombing me left-and-right.

SO----in conclusion.

Today's 3/6 nightly still has the 3/4 issue and (to me, at least) is not usable. Fair warning to you other venturers out there.

I will have to drop back to 3/1 again.. anxiously awaiting the next nightly to try out.

---------- Post added at 07:11 AM ---------- Previous post was at 06:45 AM ----------

I SHOULD ADD... to any unfortunates who might do today's update without checking here first:

After you drop back to 3/1, your notification icon will STILL be there (even though the pop-up problem goes away). To get your phone back to normal:

1) Go into phone settings and forward your phone.

2) Exit out of phone settings all the way back to your home screen. Your notification icon will now agree with your settings -- forwarded.

3) Go back into phone settings and disable forwarding.

4) Exit out of phone settings all the way back to your home screen. Your notification icon will still agree with your settings -- unforwarded.
[Samsung Galaxy S Blaze 4G] mk1277:
Adding my 0.02 USD. I was one of the unfortunate ones to apply the 20140304 update before hitting the forum. I have the popup issue like others but have not been able to get them to go away by "enabling" then disabling the call forwarding. I also cannot roll back to 20140301. Granted, I did not do a full data wipe, just cache/dalvik and then flashed. I get phone and acore errors way worse than the call forwarding popup when back on 20140301. I also cannot even get into the phone settings to try to adjust anything at that point. I ended up flashing 20140306 simply because at worst it has the same call forwarding popup error. Again, I cannot get this to go away by "enabling" then disabling the call forwarding setting. I'll fight through this annoyance for now and hope the next nightly fixes it. I just wanted to add my experience to the thread.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Why can't you roll back? And why don't you have a backup? Just curious..
[Samsung Galaxy S Blaze 4G] mk1277:
I've got a second Blaze phone running another ROM that I can use as my backup. I've not had a problem with CM this severe that I couldn't just go back. I suppose that I could wipe the phone and reinstall but that's more work than just dealing with the popup until the next nightly drops.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Yep,this is the most fun bug/fail I've seen so far..?lol
[Samsung Galaxy S Blaze 4G] dledwith2:
Anybody try the March 6th nightly yet? I skipped the March 4th one after seeing your posts, thanks for the heads up.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Bug still exists...many heads looking it over..trying to figure out how, even though noones touched our device files in a hot minute, this still ends up being a device specific issue..?
[Samsung Galaxy S Blaze 4G] JamTastic:
I actually ended up making a thread about this bug in the general area because I hadn't seen this string of posts yet (oops). I did a factory reset,used black hole super wipe, and then flashed 02/26 nightly + gapps....and the icon persists in notification bar. Popup is thankfully absent though.
[Samsung Galaxy S Blaze 4G] vetalik:
I reverted back to 3/1/14 the icon persisted as well.

What I did is pull down the status bar click on it then entered my own number after it failed to do any kind of forwarding and the icon vanished.
[Samsung Galaxy S Blaze 4G] krazzdav:
I'm on 2/26 still and it doesn't have the cfwd bug or pop ups. I did not install any nightlies after this and revert back either though.

minkmender check your settings for the vid quality and change it to a lower resolution. After I did this it would record but I can't find the video being saved anywhere. Maybe yours will save and we can have our logs compared. :D
[Samsung Galaxy S Blaze 4G] minkmendor:
haha yeah - i got it to claim it was recording, but no trace of a video on the device or sd card
[Samsung Galaxy S Blaze 4G] krazzdav:
CWM

I just recently came across PhilZ Recovery and mentions in threads to back up the EFI partition.... Is there a reason this isn't listed in the original post as a recovery option or any mention that it's recommended to back up the EFI partition?

For those that see this and want to know where it is the blaze link is here http://xdaforums.com/showthread.php?t=2461823
[Samsung Galaxy S Blaze 4G] njstein:
It's one of those things a person should come across when researching the whole root thing. Not saying everyone will, because I didn't until after I had rooted and flashed a few ROM's. But now that you know, kudos for getting the word out there...
[Samsung Galaxy S Blaze 4G] Tgarius:
Call forward icon/popup

I had done the update before I read anything and had the popup problem, I wiped everything out and went back to my previous from the middle of last month.. had to redo everything but at least it's working but I have the call forward icon. I'm an IT guy but rather new to the Android fun deal, I do have CWM 6.0.4.5 installed.. a couple of questions, will an upcoming nightly build fix the icon/popup deal directly or would I have to clear everything off again and what is the best way to backup the firmware to take everything directly back to where it was before the update.

Thanks
[Samsung Galaxy S Blaze 4G] njstein:
Hopefully, yes, a new cm in the future will take care of this and everything continues on no problems. I would imagine, though, that you'll want to do a fresh install (format cache/dalvik/data/system/sdcard0) because then you'll know for sure all the bugs are gone.

This is the most important thing when modding Android: having a complete and functional nandroid just sitting on your external SD card in case you need it. Since you have the bug if you do a nandroid, then of course, the bug will be present if you restore. Go to backup/restore in Philz, you'll see quite a few options, I always choose "backup to sdcard1" (or something similar). There's your firmware backup.

I don't know if it'll get rid of the notification, but car vs driver posted a few pages back the build one should flash to not have this bug. Have you clean installed this build to get rid of the notification?

Clean installs sucks, but so do persistent notifications that don't need to be there...
[Samsung Galaxy S Blaze 4G] JamTastic:
Biting the Bullet

so I made sure to make a nandroid of my no-popup persistent notification install (I believe the 02/26 build) and just took the plunge with the 03/08 nightly. it's booting as I type this, so I will edit post with what it does in a bit.:eek:

*edit*

I'll put it this way...did a full wipe and restored my backup, as I can live with the icon in the notification bar, but constant popups are too much of a hassle to deal with. 03/08 nightly still has popup bug.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I will announce it when its guaranteed all clear...promise..
[Samsung Galaxy S Blaze 4G] dsulliii:
JamTastic, It seems that you and some others have not been able to get rid of the notification after doing a full-wipe on a downgrade. I'm quite confused because that was not a problem with me. After downgrading with a full-wipe, did you go into phone settings and forward your phone on purpose, power down and back up again, then go into phone settings and unforward it? When I did the unforward after the forward after a clean-wipe downgrade, my notification icon disappeared permanently. My phone is exactly as it was before this bug showed up?

I wanted to chime in just in case you hadn't pursued this (even though you did say that you can live with it, I hope that you don't have to.)

-- David
[Samsung Galaxy S Blaze 4G] cravingrom:
call forwarding icon stuck in status bar

I also couldnt get rid of the icon even when i downgraded

to my backup! I even used an older backup on a different rom

and icon was still there. Used a backup that at least was stable

enough that i could use the dialer app, then entered # 21 # and hit

send. This deactivated the call forwarding, and the icon was cleared

as well. Hope it helps
[Samsung Galaxy S Blaze 4G] minkmendor:
lol i dont get it either - i did the usual full wipe and install - no icon for me 3/1 and below - u guys gotta be doing suttin different
[Samsung Galaxy S Blaze 4G] cravingrom:
ca

Yeah youre probably right minkmendor, but cant think of what we did wrong.

i did the full wipe, cache ,dalvik etc. Even tried clean install of previous nightlies

and Still had the icon!! Have had my blaze now for over a year and have bricked

my phone a few times, had to go back to odin to fix!! Love that all the info i ever

need is here and how i can keep it going and even be on kit kat.Thanks to all who

post here. Without all your comments i would have a nice paper weight as my

everyday phone!!
[Samsung Galaxy S Blaze 4G] mk1277:
You guys probably already know this, but I had to share. . . .

I took out my SIM from my CM11 phone running the 20140308 nightly with the forwarding notification and popup bug and put it in my backup phone running a completely different ROM. The notification persisted across phones. I had to enable then disable the setting to get the notification to go away. I'm sure that you are aware then that this setting seems to be written to the SIM but wanted to share that this appears to be at least part of the problem. Maybe something is being written and then read wrong? I know the smart minds are looking at this and they all know WAY more than me but I figure every little bit of information helps. :)
[Samsung Galaxy S Blaze 4G] dsulliii:
AWESOME observation! I don't have a phone to try crossing the SIM onto, but what an outstanding thing to try. (I also hope that it helps.)
[Samsung Galaxy S Blaze 4G] dledwith2:
Any news on the Mar 10th nightly? I'm still running the Mar 1st one before the pop up problems. I realized that my speakerphone still doesn't work, I thought that it was fixed previously but I may be mistaken. I don't use it often.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Again, same bug exists...there are ATLEAST 3 people ( if not more) working on it..and speakerphone was never fixed..

...sent from a gummed up Nexus 7 using Tapatalk pro mofos...
[Samsung Galaxy S Blaze 4G] dledwith2:
Thanks for the speedy service :)
[Samsung Galaxy S Blaze 4G] minkmendor:
hey ink.... u had any success in getting the video camera to save?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I don't have the device guys...I'm running this thread as a favor..please don't forget that...I DO however communicate with your cm maintainer any issues you guys have..I have too much on my plate, and a lack of the device to take over maintainership(?) ..hence why I always need testers for my blaze builds..I will never be able to fix the hw bugs myself..just pass on the message to those who may..

...sent from a gummed up Nexus 7 using Tapatalk pro mofos...
[Samsung Galaxy S Blaze 4G] Veliion:
Didn't you use to have a Blaze? Just wondering.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Nope..i used to have a i577 for daily use..Variant..Just saw there was nearly no devving for the blaze and picked up pac for you guys...and it snowballed from there..
[Samsung Galaxy S Blaze 4G] njstein:
And everyone on here is dam glad you did, bro.
[Samsung Galaxy S Blaze 4G] Skywalker.00:
I may be able to help you out with that. Maybe make troubleshooting a bit easier?

-Paranoid Nexus 5-
[Samsung Galaxy S Blaze 4G] InkSlinger420:
That would go leaps and bounds...having a test/dev device..But thats up to you bro..
[Samsung Galaxy S Blaze 4G] minkmendor:
[MENTION=5438592]Skywalker.00[/MENTION] -- that's awesome man! by all means i can test too. and as for my video camera question.. has anyone that actually owns the device been able to save video recordings?
[Samsung Galaxy S Blaze 4G] mk1277:
I can record video with the stock camera. I also use a better camera app and that video camera doesn't work.

Also, put me down for testing. I have two of these devices and can mess with my cm11 one and still use my other as a daily driver.
[Samsung Galaxy S Blaze 4G] minkmendor:
you can record but can you save? mine doesn't have an option to save nor do i see it on the device or sdcard
[Samsung Galaxy S Blaze 4G] mk1277:
I don't see an option to save but it's on my sdcard and I can play it back.
[Samsung Galaxy S Blaze 4G] minkmendor:
very strange yeah mine just looks like its recording.. then when I stop it, swipe to left, its only pics. does it save to your internal or external card, and which nightly are you on? im on 3/1.
[Samsung Galaxy S Blaze 4G] krazzdav:
What's the exact folder path that ur video is saved on your sdcard? I don't have any video on it either.
[Samsung Galaxy S Blaze 4G] mk1277:
My vids show up in /sdcard/DCIM/Camera/

I can play back from the Gallery app or find it in ES File Explorer and open from there.

I forgot to add that I posted last night on 20140310 regarding video. I flashed before I knew about the forwarding bug so I've kept up to date. I'm on 20140311 today and video still works.
[Samsung Galaxy S Blaze 4G] krazzdav:
hmmm thx. Can you post a logcat of you starting and stopping a recording and then I will do the same? Hopefully this will help the devs to find out what's going on ;)

One other question... How did u format/partition ur sdcard? I don't think this would make a dif but never know lol

Are u still having issues on 3/11 with the forwarding/popup bug?
[Samsung Galaxy S Blaze 4G] ZekeAdebayo:
Phone Calls Cutting off

Good morning

This is an issue related to the beanstalk 4.4 build, I didn't ask the question there because I knew it wouldn't be answered, and the last time I checked beanstalk was based off of Cyanogenmod. Cutting to the point, I'm using the UVLH5 radio, (running the beanstalk 4.4 rom build from the 2nd page on Android Developement) but for some reason phone calls seem to cut off really easily on the rom, (sometimes as soon as you make the call it cuts off, or during the call) which is not an issue the phone had on the stock Samsung rom from T-Mobile, Cm 10 had a period where it wouldn't make calls, but overall the issues got fixed, and it wasn't a problem for me. So I was wondering what the issue could be, could it be that I need to use another radio? What are other alternatives, or is it more of an issue with the rom? I know it's not just my phone because I used the same rom for my Dad's phone, and he gets the same issues. Anyways any help would be appreciated, this is the only real issue I'm concerned about with this rom, otherwise it's a great rom, much more stable than the rom for my bro's exhibit 2.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
This is a device related question and should be asked in device q&a thread

But, yes, you can try another radio as it will most likely will help, but you can also try another ROM such as gummy to see if the issue persists as well..just don't use a build newer than 3/3 for right now there is a fun call forwarding bug..
[Samsung Galaxy S Blaze 4G] minkmendor:
thats a good question with the formatting . seeing as my device still for some wierd reason makes sdcard0 (which is split internal storage) and sdcard1 which is external card
[Samsung Galaxy S Blaze 4G] krazzdav:
That's how it is supposed to be so don't worry. And your vids are being saved on ur internal storage sdcard0 ;) sdcard = storage/sdcard0 whatever browser you are using if you select properties it should show u that.

I just wasnt sure if u formatted ur external some special way and that's where they were being saved. CWM format does the whole external as FAT32

I will b able to do a catlog tonight if u can sometime today as well.
[Samsung Galaxy S Blaze 4G] minkmendor:
lol well that doesn't help my disappearing vids hehe - and id love to help with catlog if someone would explain now :)
[Samsung Galaxy S Blaze 4G] krazzdav:
oops my bad :eek: thought I was replying to mk1277 that said his were saving :laugh: My phone screen isn't that big you know lol

I think we need a logcat from mk1277 since his vids do save but for you to learn how it's in the general q&a here http://xdaforums.com/showthread.php?t=2399907
[Samsung Galaxy S Blaze 4G] mk1277:
Hey guys. I will get you a logcat. What specifically do you want me to check for? I haven't looked at one in a while but know that there are all kinds of filters that can be applied.

As for the storage formatting/location, my device saves to the internal sdcard location (sdcard0) and I haven't done anything special for the formatting.

Edit: catlog attached.
[Samsung Galaxy S Blaze 4G] krazzdav:
Cool thx!

Is this catlog of you starting a video recording and then stopping it? I will post one tonight of mine too which doesn't save the vid hoping it can help the devs out on this.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I will reiterate again guys..we are using ICS camera blobs....If we had been dropped official Samsung JB things would be different...EVERYTHING else that's wrong will be easier to get going than the camera..but I appreciate the effort,and maybe if [MENTION=5438592]Skywalker.00[/MENTION] decides to, I may be able to actually have a device to Dev on as its insane to try to fix anything without it being in front of you,(hence why ROM teams prefer the maintainer to own the device, can't fix it if ya don't have it kinda thing)...time will tell..until then I can only help keeping what's already working,working...
[Samsung Galaxy S Blaze 4G] minkmendor:
pretty sure we are all just sharing thoughts and ideas here about the vid cam. It def cant hurt to throw them out there with the logs. Who knows, maybe the right person wills tumble across this forum and have a fix :D (wishful thinking)
[Samsung Galaxy S Blaze 4G] InkSlinger420:
No harm at all..just wanted all to know for anyone new to this thread that has yet to post..
[Samsung Galaxy S Blaze 4G] krazzdav:
Sorry...thought since we actually had the video recorder working and one that was saving properly comparing the logs might show something "easy" to fix for the saving of the file portion.

Thx again for helping with this phone blindly....until you get yours from Skywalker :D
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I concur...The thing with these 2 devices (the blaze and i577) is in particular, somehow, some things work for some and not for other identical device..its similar to my i577 has never booted on the 1.8 oc kernel from [MENTION=4145127]thomas.raines[/MENTION] but most other users devices did...i could only ever get the 1.5 to actually boot...I keep saying hit or miss because there are so many variables, and for whatever reason, even 2 exact devices give 2 separate situations..
[Samsung Galaxy S Blaze 4G] ultimahwhat:
FYI PAC 3/12 nightly for i577 dirty flashed from PAC 3/3 does not have call forwarding pop up, which likely means cm11 3/12 nightly for blaze has call forwarding fixed...
[Samsung Galaxy S Blaze 4G] mk1277:
NOOOO!!!!!! I dirty flashed the 20140312 CM 11 yesterday and the popup is still there!!! NEVER assume.
[Samsung Galaxy S Blaze 4G] njstein:
Thanks for the input. I know I really appreciate all information given. It's a good sign that i577 bug is fixed, means the Blaze is around the corner!

Really, dude? Can't just say thanks and report that it's not fixed yet? You have to use caps, and an unnecessary amount of exclamation points? Then flame him for giving information? No wonder our phone is losing devs and people willing to help. Jesus.
[Samsung Galaxy S Blaze 4G] mk1277:
Please relax. No offense was intended other than to strongly point out that assuming another ROM has something fixed it will immediately apply to this one doesn't make sense. Also, I flashed 20140313 and couldn't get the device to boot. It was stuck at the CM animation.
[Samsung Galaxy S Blaze 4G] dledwith2:
I'm still on the March 1st rom due to the recent bugs. I tried to use tethering today and it's not working. When I turn it on I lose all wifi capability and icons unless i reboot or turn airplane mode on then back off. Any ideas? I don't use it often so I don't know if this is a new bug or an old known one.
[Samsung Galaxy S Blaze 4G] minkmendor:
march 1st build is whack man. it drains my battery in a day without using anything. also gets stuck on lock screen.