yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] osbaldov:
Has anyone tried force stopping or disabling telephony(phone dialer app) To see if the call forwarding is still there. I am on Pac-Man ROM and haven't been able to try it out on CM11 yet.

---------- Post added at 10:16 PM ---------- Previous post was at 10:13 PM ----------

3/12 pacman is OK to run
[Samsung Galaxy S Blaze 4G] ultimahwhat:
Before I flashed the bug away as previously mentioned, I used the option in Philz recovery to "Clean to install a new ROM"

This additionally wipes .android_secure on all partitions on which it resides, from what I can tell. Maybe that will help; can't think our devices are that different unless it's a Tmo SIM thing...
[Samsung Galaxy S Blaze 4G] minkmendor:
i recommend anything b4 3/1 guys.... although it doesn't have the call forward issues, ive notice my battery life cut in half and other wierdness happening as well. :)
[Samsung Galaxy S Blaze 4G] daboross:
Force stopping it doesn't do anything, the notifications persist. Also tried freezing the app with titanium backup, made it disappear for 3 seconds, and it's back again.
[Samsung Galaxy S Blaze 4G] iptux:
"Call forwarding Service was Enabled" popup issue

it seems that the "Call forwarding Service was Enabled" popup issue is still there.

i have dive into the problem these days, and found the solution (i'm not using t769 but my phone also have this issue)

the cause: the value of a CONST in RIL changed, the CONST's name is "RIL_UNSOL_ON_SS", whose value changed from 1039 to 1038, the previous const with value 1038 is "RIL_UNSOL_RESPONSE_TETHERED_MODE_STATE_CHANGED", if you're using a vendor provided ril binary, that means lower ril send a RIL_UNSOL_RESPONSE_TETHERED_MODE_STATE_CHANGED event, but the upper framework mistaking it as a RIL_UNSOL_ON_SS event, then "Call forwarding" dialog popup

the solution: instead using the ril binary from vendor, ril related binary have to be built from source, including `/system/bin/rild', `/system/lib/libril.so', `/system/lib/libreference-ril.so'. ril from source don't works on cm-10.2 but works on cm-11 in my case, hope the source built ril also works for t760.

hope this post will help;)
[Samsung Galaxy S Blaze 4G] minkmendor:
nice find!!!! i hope this helps for this phone too!!!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
We are looking it over right now..will report back..

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] UberPinguin:
http://review.cyanogenmod.org/#/c/61289/1
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Yes...Help is on the way...Damn it Uber..I was eating dinner,then I was gonna tell em :p

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Gotta love the people here who don't even have the device, but come in and clean up an issue for us all...big thanks [MENTION=4870421]iptux[/MENTION]...

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] minkmendor:
absolutely agree with you ink! im down to test whenever a promising build shows up :)
[Samsung Galaxy S Blaze 4G] InkSlinger420:
New build dropping in 10 mins..
[Samsung Galaxy S Blaze 4G] minkmendor:
sweeeeet - making backup now :)
[Samsung Galaxy S Blaze 4G] iptux:
the c/c++ version RIL const define `hardware/ril/include/telephony/ril.h' should update at the same time
[Samsung Galaxy S Blaze 4G] car vs driver:
Got it, thanks. Will upload a second patch for this part in a few minutes. Rerunning a build to test.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
http://www.androidfilehost.com/?fid=23329332407580213

Got a new build courtesy of [MENTION=2933674]UberPinguin[/MENTION]

Says its good to go....
[Samsung Galaxy S Blaze 4G] minkmendor:
trying it now!

---------- Post added at 05:55 PM ---------- Previous post was at 05:38 PM ----------

yessss!! thanks so much [MENTION=2933674]UberPinguin[/MENTION] !!!!! booted right up - clean flash no call forwarding crap :)
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Mad props to [MENTION=4870421]iptux[/MENTION] for the find..We've all been so busy, aint had much time or energy to dig that one out..
[Samsung Galaxy S Blaze 4G] UberPinguin:
Thanks, [MENTION=4870421]iptux[/MENTION].

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

EDIT: Oops, I didn't see that [MENTION=4685003]carvsdriver[/MENTION] already had http://review.cyanogenmod.org/#/c/61292/ up!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Y'all need to communicate...lol?

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] minkmendor:
so just as a heads up.. the video camera still doesn't save. no clue what the one guy was talking about that said his saved. :cyclops:
[Samsung Galaxy S Blaze 4G] JamTastic:
is this more recently patched build the one that was pushed to/showed up in CMupdater ?
[Samsung Galaxy S Blaze 4G] minkmendor:
yes it is. its the cm-11-20140319-UNOFFICIAL-t769.zip ..... that one from cm updater is an official and still has the bug.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
The bug free build is the one I upped to androidfilehost on the last page..the commit to fix hasn't even been merged yet and needs tests to make sure it doesn't break other devices..so, in other words, no..not in cmupdater

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] minkmendor:
hey ink, any idea why when i do a factory reset /wipe on phone that all of my pics and videos remain on the sdcard0? i'm using clockwork 6.0.3.8.... it makes me wonder what else isn't being erased
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Because those are personal files and folders, not meant to be removed by a standard factory reset.. Have a looksie here

http://www.talkandroid.com/guides/beginner/how-to-factory-reset-and-wipe-your-android-device/

Specifically states personal folders need to be deleted/removed manually..Its like that on every android device i have touched

unless you format sdcard0...good thing to remember before selling or giving away your device at eol.

Edit: [MENTION=5649653]minkmendor[/MENTION] , Is that a ferret?? I used to own a mongoose..like a manic/bipolar ferret..?

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] JamTastic:
Thanks !:good:
[Samsung Galaxy S Blaze 4G] minkmendor:
ha ha its a mink! ;)
[Samsung Galaxy S Blaze 4G] njstein:
Hey to all you bad mofo developers that figured the bug out, a huge thanks to all of you!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Makes sense..lol

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] mk1277:
I'm that guy and it saves on my device. Don't know why.

Edit: if it makes anyone feel better, my second Blaze doesn't save video. It doesn't even show the preview. However, that's running CarbonROM at the moment.

Edit2: I just installed the unofficial update file and get no popup or notification - excellent work! My video still records too. :)
[Samsung Galaxy S Blaze 4G] freddy2081:
Hello everybody!!

I've been a quiet user for quite a few years now, I managed to have a very good success with a galaxy S3, still have an HP touchpad that runs cm10 with jskullins patch almost flawlessly and now I rooted my blaze 4g with CM11.

I need some help with a couple of things. First, CWM wouldn't install anything, kept getting an error and soft brick the phone, so I tried with TWRP and managed to install 11-20140113 and it seems to work quite other than for a couple of minor issues.

1 issue that I can't seem to resolve is the storage problem. I can't seem to use the external SD card, when I move my apps to the SD card they get moved to the second partition of the phone and not the external SD. The phone is pretty much out of storage space, and I don't know how to solve the SD problem.

Another issue is to update it. When I download it, TWRP tries to install it, but can't find the folder, and I can't find it manually either. I tried reinstalling CWM when CM11 was already on the phone, but it wouldn't install it, kept coming back with an error (section 7 maybe) and would soft brick the phone.

I tried looking around, but at this point after trying quite a few different things, I'm kinda tired of chasing my tail and i figured you probably already know where is the problem and how to solve..

thanks a bunch!!!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Have you formatted the sd since coming up to 4.4? Needs to be done through recovery as well as being on the most recent recovery for the device

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] freddy2081:
What an honor having you answering!!

Actually I did not!! I did some research last week and the latest TWRP for this thing seems to be 2.4.3.0, which is what I have.

Now, when I go to wipe the "external storage" is not going to format the side of the partition that the phone is considering as "external storage", but the SD card, I assume, right?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Correct... And after reboot it should be recognized properly

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] InkSlinger420:
And just a heads up, if your using twrp as you like the touch interface, philz is preferred as its cwm based and still has touch interface..zip can be found here if you choose you wanna try it

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t769

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] freddy2081:
Thank you, I'll try it, although I really don't care about the touch interface, the only reason why I was using TWRP is because with CWM I kept getting some error (I don't remember but it was something 7) and getting a soft brick.

Just formatted the SD card, but I still can't seem to be able to move any apps on the SD, they only move on the SD which is the internal memory of the phone..

What am I doing wrong??
[Samsung Galaxy S Blaze 4G] InkSlinger420:
If your talking about moving apps to external SD, you need to use a vold swap zip or an app like foldermount that will actually mount an internal folder as external folder..I have a vold swap zip that tricks the mount points so external mounts in the device as internal and vice versa somewhere in this thread I believe.

And error status 7 in flashing a zip is an error in updater script designed to stop people from flashing things that aren't for the device being used on..but sometimes its an unneeded error..it can be resolved by extracting the zip, removing the assert prop lines in the updater-script inside the zip and rezipping it up before flash, but be careful, and do NOT flash things for the device that aren't meant for it..The error actually occurs sometimes when the zip is compiled and the device call name isn't properly setup..you'd be surprised how often it happens..hope that helps

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] freddy2081:
I found the information about the status 7 and did the unzip and rezip after correcting the assert line, but I still got a status 7, I found information on what lines to remove, but didn't work.

I'm gonna try to run an update now that the SD card should be ok, and I'll see if it works..

Thank you very much for your help, but I'm sure I'll be back for more...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
What zip are you trying to modify? Link me and ill look it over for you...there are several lines to remove normally
[Samsung Galaxy S Blaze 4G] freddy2081:
It was the one that I ended up installing without modifying, but using TWRP.

The zip was 11-20140113-NIGHTLY-t769, but don't waste your time, is now running fine, only difference I had to use TWRP.

I'll try to download an update later on, since that what I'm still running at this point.
[Samsung Galaxy S Blaze 4G] minkmendor:
bro use latest cwm - it got rid of that error for me.

CWM 6.0.3.8 (No touch) - http://d-h.st/Cc2 ---- this one from page one works flawlessly
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Damn..That recovery has a few downloads..Glad its working..
[Samsung Galaxy S Blaze 4G] freddy2081:
Gotta wait till I go home, work computer won't let me go there.. LOL
[Samsung Galaxy S Blaze 4G] champ784:
CWM needs to be up to is latest version to flash 4.4 ROMs. The first custom ROM I used was based on 4.1.2, and I was able to use the old version of CWM that I installed via Odin until right after 4.3... When I tried flashing 4.4, I got the error 7. Because there are some major changes in 4.4 vs older ROMs, CWM had to be updated to compile it properly... Its pesky cuz you have to do a bit more than you would normally do to simply flash a new ROM... But if you wanna stick with TWRP, that's fine too! XP

Sent from The Doctor's Nexus 7
[Samsung Galaxy S Blaze 4G] car vs driver:
Correct, for KitKat you need to make sure that your recovery supports formatting volumes with SELinux. Otherwise, you'll run into problems.
[Samsung Galaxy S Blaze 4G] minkmendor:
Hey [MENTION=5190980]InkSlinger420[/MENTION] - any idea if the call forward fix has been thrown in the latest nightly? Im fine with the unoffical one, just for other peoples sake ;)
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Doesn't appear to be yet..need more tests to verify on cms side to make sure it doesn't break something else when going in..

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] car vs driver:
We are working through tests to verify that it doesn't break other devices. May be a few more days.

Run the test build for now, you aren't missing anything.
[Samsung Galaxy S Blaze 4G] minkmendor:
kewl dealio! thanks for the quick reply [MENTION=4685003]car vs driver[/MENTION] and [MENTION=5190980]InkSlinger420[/MENTION].... everything other than the normal issues seem to be ok. And ink you think it might be worth adding that the video camera doesn't save to the known issues section on the first page? Also for the camera flash issues .. Say u have the flash set to on and want to turn it off. If you just switch with the camera launched, the change wont stick. You need to close and reopen the camera app for the flash settings to stick. Maybe this will help in someone finding a resolution on it :D

edit - sry really high to be spelling correctly
[Samsung Galaxy S Blaze 4G] njstein:
Ha! Nice...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Shouldn't need to close camera to change flash, just need to enable it or disable it twice for it to stick..

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] InkSlinger420:
FYI.. I am starting a group hangout for blaze devs and users to try and move the communication along a little quicker..Users and/or devs who are interested in joining and talking live as opposed to clogging the thread, feel free to pm me with your gmail account and I will add you to the group..(your pm will be deleted/destroyed immediately after as to not have addresses laying around, and I promise not to sell your info..)..again. Anyone interested, let me know via pm...

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] freddy2081:
Not sure at this point if you guys found a solution, but what happens if you just happened to install a bugged version and now the pop up wouldn't leave for any reason??
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Scroll back a few pages, there is alot of talk about it..
[Samsung Galaxy S Blaze 4G] car vs driver:
Phone fix will be in the next nightly.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Thank you Dave!!!?

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] dsulliii:
Testing the waters

Okie Doke... I've looked carefully over this past page and don't see anything specific to a "phone fix" for the Blaze that may indicatively be separate from the forwarding pop-up bug. So based on the context of these past few messages, I am hypothesizing that the "phone fix" may indeed be the forwarding pop-up bug. I awaited the posting of the 3/23/2014 nightly, and now I see it posted. I am going to presume that this is the one mentioned. I MAY BE WRONG... granted. It's easy for me to misinterpret stuff.

But since I apparently have one of those phones that seems to want to behave well for the most part when other people's don't necessarily, and since I thrive on taking chances (especially considering I seem to be able to recover from disasters quite adeptly), then I shall take the dive.

I may be a fool since i don't have a confirmation on my presumptions/assumptions yet... but being a fool can be fun. And sometimes advantageous.

I will try the 3/23/2014 nightly on the blaze right now and let you all know what's up.

Wish me luck.

-- David

---------- Post added at 09:20 AM ---------- Previous post was at 09:15 AM ----------

Note: Yeah, I did read the change log first, and it doesn't specifically mention the pop-up bug. But like all these past nightlies, it does mention merging issues, which apparently is at the root of this bug. NOT being one of the developers, and comparing texts, it DOES say "RIL_UNSOL_THETHERED_MODE_STATE_CHANGE". So I'm PRETTY comfortable with my assumption. Like I said, "I'll let you know."

---------- Post added at 09:50 AM ---------- Previous post was at 09:20 AM ----------

I don't know if any of you need something more authoritative from an appropriately authoritative source, but the 3/23/2014 nightly is working PERFECTLY for me. NO FORWARDING POP-UP BUG, no erroneous forwarding notification indicator. My spearkerphone works (it always did, though), camera works, video-cam saves, well, for ME anyway, it works perfectly.

THANK YOU to all the CM developers working on this and to Ink and Car-vs-Driver for being so fervent to keep MY phone up to date. I love ya all!

-- David

:good: ;) :D :) :silly: :laugh: :cool:
[Samsung Galaxy S Blaze 4G] shutt1e:
just a question guys, because this seem the only thread in xda talking about this problem. i'm suffering the same on my device, an annoying and continuous popup about call forwarding service. this happened when i last synced my sources with cm11 repo. never happened before.(i'm compiling cm11 myself because my device is unsupported)

glad it has been fixed for your device, my question is, it has been fixed with a change in the device tree or with a change on the cm11 sources?
[Samsung Galaxy S Blaze 4G] car vs driver:
We merged two patches to fix it.
[Samsung Galaxy S Blaze 4G] minkmendor:
[MENTION=4671041]dsulliii[/MENTION] thanks for heads up. Im about to test on a clean flash. Not sure how the hell your device doesn't suffer the bugs ours does. It's a T769 from the US? (dont think there is another model) - Will report back :)
[Samsung Galaxy S Blaze 4G] shutt1e:
thanks

are they publicy available or still not merged?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
They should be merged now as the latest nightlys do not suffer the issue any longer

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] dsulliii:
Yeah, bought it from T-Mobile in-store stock right here in Aurora Colorado. Maybe last year when we had problems with our phone system at work I may have caused different behavior. Calling our system from the outside always resulted in the calls being routed to our voice mail ONLY IF it came from a T-Mobile phone. I volunteered to experiment (as is my nature) and swapped out radio ROMs in my phone. I don't know which one I *should* have, but I've had it set at T769UVMB1 ever since. I don't see how that could make a difference, and it seems that it *is* the newest and correct one. But I don't recall. BTW, our work problem was resolved by changing a setting in our internal system, but the cell phones.
[Samsung Galaxy S Blaze 4G] gilberts555:
Aw man, I just experienced the bug. The Blaze is the phone I lend to people, and when it happened, someone thought that they broke my phone. :laugh::laugh: I thought I was alone with this bug, but then I found this.

Sent from my T999l
[Samsung Galaxy S Blaze 4G] dsulliii:
I hate to clutter the thread with something this huge, but maybe there's something in my device that is newer than what everybody else has? When I bought mine, it was at a very low price due to being right after they came out with a new Galaxy line, and the Blaze being twilighted. Maybe the latest runs had some newer hardware?
[Samsung Galaxy S Blaze 4G] Codeseven:
Confirming that the "call forward billion popups" bug is gone. Thanx peeps!

Small bug to report, though. When I get a text from someone, I pull down the notification bar and click the message and go to the message in the messaging app. However the "new message" notification icon doesn't go away. I have to manually clear it out every time.
[Samsung Galaxy S Blaze 4G] mk1277:
From your earlier post you said that speakerphone works - does that mean that the mic isn't muted when speakerphone is enabled? I think you and I are the only two that can get video to save properly but my mic suffers from the speakerphone mute bug. FYI to all: I'm on the 20140319-UNOFFICIAL build with the popup fix and am going to flash to 20140323 in a bit to get back on the main nightly release. I'll report back if anything changes.
[Samsung Galaxy S Blaze 4G] dsulliii:
MANY apologies... I'd forgotten that THAT was the specific symptom. When I read the way you worded your question, my aging mind said, "oh yeah, THAT's what the problem was." And I remembered having it as well.

So I tried THAT specific experiment. Like I said, many apologies everybody. I also have the muted-mic when on speakerphone issue. So nothing magical about my phone as far as that bug goes. It's something I almost never use. Maybe that's why I don't use it??? <grin>
[Samsung Galaxy S Blaze 4G] Codeseven:
It's great for when you're doing stuff on the computer like I am now. Typing out a message and talking to someone at the same time with no other head piece. I hate this bug because I can't use the speaker anymore :( . Or it's also for people that just don't like to put the phone up to their ear, or people that are needing to multitask talking to someone and browsing the web/using other apps while talking.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Restored download link as issues are now resolved...

.....If I had even a quarter from everyone I've helped....Maybe I could stay stocked in beer.....-sent from a very xposed nexus 7-
[Samsung Galaxy S Blaze 4G] minkmendor:
found a new issue..... The google search bar at the top keeps displaying incorrectly. Shows the bar with no "google" or mic symbol. Also cl0ck disappears from my home screen but stays on lock screen. A reboot brings the google toolbar back to life.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Interesting as thats a google app, and shouldnt be rom issue....clOck may be a launcher issue
[Samsung Galaxy S Blaze 4G] Codeseven:
Any progress on bluetooth?
[Samsung Galaxy S Blaze 4G] minkmendor:
hmmm.. im using the same gapps (standard) from page one on the forum - its spotty ink... the google bar.