Develop Bugs

[ROM]3.25.2011 Continuum Clean (In Progress)

Ok, so normally I hate placeholders, but I'd like to give you guys an update of where I am at. Once I am finished tweaking, I will release. The base rom is done, now the modding and tweaking needs to happen.
So far:
--------------
Deodexed, Debloated, Debinged, and mostly, detouchwizzed. Debinged...even in the framework. I think* all Bing traces are gone now.
Visual voice mail gone, voice mail button in dialer opens Google Voice.
Verizon Wireless carrier banner replaced with something....better.
MMS app will not longer do multi-part messages, but instead convert to MMS automatically once the 160 character mark is hit.
GPS tweaked.

Wow in one day of having the phone you have a rom halfway competed
Sent from my Rooted Space Time Continuum w/h a 2600mAh battery

:3
Wow, I can't wait for this even though we have had bad experiences with place holders, I know this isn't the case lol..
I don't know how many times I'm going to say thank you, but here is another thanks!
Sent from my SCH-I400 using XDA Premium App

along the lines of changes to the voicemail button.....it would be awesome if the ticker's voicemail icon could correspond to Google Voice...but I am sure that is a lot more involved than changing the button's link in the Dialer.
a similar desire exists for the sms icon to correspond to Handcent
I used titanium backup to remove the stock messaging app and that killed the ticker's SMS icon functionality....I saved the stock app to reinstall but that introduces a different problem....the ticker icon doesn't go away reliably after having read the text in Handcent.
maybe this thread wasn't intended for our wish list items.....if that is the case, I apologize.
thanks for your help to our little Continuum family!

thanks for the help here adryn! my wife has the continuum, and i got hers to load red recovery, and the other modded rom.
question on this rom you are building..will it have the bstats and fxpms scripts? are the ones for fascinate compatable with contunuum?
thanks...
Samsung Fascinate
SuperClean 2.91 & EC10 Voodoo
Nitro Ultimate HoneyComb 3.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.

U rock thanks for ur work
Sent from my SCH-I400 using XDA Premium App

Gr8 to hear this tha sum1 is eveloping on this lovely handset

Awesome man, you do some quick work man. Thanks for everything.
Sent from my SCH-I400 using Tapatalk

Glad to see this hasn't been abandoned completely yet. I just got this phone in February! Can't wait to see the results. Thanks!
Sent from my SCH-I400 using XDA Premium App

well i have a tbolt (great work over there btw), but my fiance has a continuum and i want to get her some real android action so thanks for the hard work.

eric2112 said:
Glad to see this hasn't been abandoned completely yet. I just got this phone in February! Can't wait to see the results. Thanks!
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
It was all but abandoned. Glad to see some progression!
Also, I saw some news on 2.3 leaks for SGS phones, do you have any info on this adrynalyne? Like a I400 leak perhaps... /lookleft /lookright

Sweet! Looking forward to seeing where this may go!

ExNukeSquid said:
It was all but abandoned. Glad to see some progression!
Also, I saw some news on 2.3 leaks for SGS phones, do you have any info on this adrynalyne? Like a I400 leak perhaps... /lookleft /lookright
Click to expand...
Click to collapse
the gingerbread leaks are only for gsm galaxy s phones...no help for the epic or fascinate/continuum
even our (fascinate) 2.2 cant be directly flashed without issues...but whether or not adryn can put together some kinda hybrid rom...idk we ll see

adrynalyne said:
Visual voice mail gone, voice mail button in dialer opens Google Voice.
GPS tweaked.
Click to expand...
Click to collapse
curious (warning - n00b question) - would it be possible to make the GV VM connection optional for those of us who don't use GV?
Also, what do you mean by GPS tweaked? The only thing i've noticed about mine is when i'm out geocaching with c:geo or using google maps to navigate while walking, sometimes the compass seems to be off by 180 degrees. when driving, google nav seems fine - likely since it can figure out direction based on previous locations in the same way it figures speed, but i don't walk fast enough for it to figure out direction - especially when geocaching since i'm always stopping to look for the cache.
all told - that's pretty impressive that you knocked out so much stuff in the short time you have had the phone! Thanks for your help with this device!
Any chance you have cracked open the ticker, or at least made it more useful to people who don't use the stock apps (that is... EVERYONE)?
One suggestion i saw somewhere (probably here) really interested me - put the notification area in the ticker screen and make it big enough to fill it, so you dont' have to try and hook into their custom ticker app - just use the existing system one, only relocated/resized. that way all system notifications (no matter what app they're from) will be visible in the ticker, all the time, as well as the time of day, and apps won't have to be custom-written to take advantage of the ticker; they'd just WORK.

I just can't wait till it is out I am looking forward to it
Sent from my SCH-I400 using XDA App

http://forum.androidcentral.com/samsung-continuum/73450-rom-3-30-11-clean-continuum-dl17.html
;DDD

I have downloaded the ron and installed it. It is very nice. I do have one problem though when the phone boots it is a black screen no Verizon logo or a new one it is all black till the phone loads is that supposed to happen
Sent from my SCH-I400 using XDA App

tazzstrike said:
I have downloaded the ron and installed it. It is very nice. I do have one problem though when the phone boots it is a black screen no Verizon logo or a new one it is all black till the phone loads is that supposed to happen
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
yes this is normal for now

tazzstrike said:
I have downloaded the ron and installed it. It is very nice. I do have one problem though when the phone boots it is a black screen no Verizon logo or a new one it is all black till the phone loads is that supposed to happen
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
shoot - as long as it doesn't affect anything else, i'd take that over the annoying, noisy crap vzw put on there. is the shutdown screen also black/silent?

I don't have the phone right here handy atm but, I've already downloaded the Rom and alt browser. looking forward to flashing it to my boy's phone! I know he'll be happy too. One thing I love about these Android phones is how they give us the ability to have that "new phone" feeling any time we like, thanks to their rich development community. This is one thing the Continuum crowd has missed out on until now.

[R&D]Wifi calling and Sending MMS

Disclaimer--- this is simply a thread to discuss and rant about issues with wifi calling related to MMS sending and retrieval as well as blurry mms. This is also to keep it in one place rather than on other posts where it becomes unrelated to the original topic. I have tested sending MMS through stock, hand cent, and go SMS and am unable to send pictures. This said I am using kl1 deodexed rom by whitehawx. This is just the beginning of my research and observation. Another user (docmjldds) mentioned that it was working on zombie rom but only using hand cent. Please post what roms you have tested and whether or not sending over wifi calling works for you. Also post what SMS app you are using and what file size it was also. Screenshots help but keep them G rated. Also post whether the pics where blurry. If it helps post what types of mms mods you have flashed. I will clean this up more when I get to a computer and update the list... please feel free to rant and rave. Just don't take it personal.
You can help research by posting the following:
1.) Rom you are using and version
2.) Kernel you are using
3.) Any mods, scripts, etc.
4.) Using wificalling only, NOT 4g, attempt to send MMS to yourself or other person using either
1.) Stock Rom
2.) Other sms app (please state which one works)
3.) State whether or not it DID or DID NOT compress the image when sending and if it failed, or when receiving if it ends up blurry.
My rom:
Deodexed KL1 by Whitehawx. Using Fauxkernel 07b5 default with no scripts or mods added.
[stock mms app] = unable to send large pictures but can send decent size. Takes more than 10 minutes for me to send. Compresses the images right away.
[Go Sms and Handcent] able to send regular sized pictures but not large ones >1mb. Still took 10 minutes to send. Compression occurred.
Did not notice any blurriness from the pictures that I did receive.
Updated List for ROMS able to send MMS/Large sized MMS, etc
--ZombieRom 3.0 Thank you Docmjldds for the heads up on this info.
Updated List for tweaks, mods, tricks to get MMS to send.
--Will update as people post.
Thanks for your contribution. I will post better screenshots of pictures sent and received.

I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...

yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
tcboo said:
I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App

chib1panda said:
yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Not going to repeat the same old same old. I will simply watch and learn what others state. Until I see otherwise, I only ask users to try every ROM 2.3.6 based and tell me if they can specifically send and receive with the following parameters
1. Use WiFi calling enabled. I am NOT interested in 4G. That's NOT the issue here.
2. Be able to enable 1.0Mb file sizes to send with MMS and NOT have files shrink to 16-26Kb file sizes.
3. Not have to R+R any mms.apk files from one source to get around blurry mms issues.
Now, based on these parameters, I am simply going to make the following statement regarding what works for me and specifics. For those that have already heard me say this, hold your ears please since many users here may not have had the misery of reading my prior posts.
I have found that consistently only one ROM here for our model works. I have no idea on why. I am only stating to try the following.
The Zombie based ROM, currently 3.0 version here. Install per OP directions. Then install Handcent SMS third party app. It's the only app that works consistently for me where I can send large sized MMS files (350-950Kb sized) using WiFi calling enabled. It should only take a few seconds to send. And yes, these are the sizes received. I am using 2-3Mb pictures I take with our phone, using the 1.0Mb MMS settings for sending in the Handcent preference setup for MMS. You can use the stock message app to read the same file, AFTER it is first received with Handcent, BTW. Oh, like GoSMS Pro, you don't have that arrow showing in the mms file as if it's a video file you are seeing, BTW. I have seen this asked by others. But Handcent does not give that message "Unable to send. Wait till Network is available message". GoSMS Pro does give that message for me.
I have posted enough screen shots on various development threads so I won't clutter up the post here. If users ask, I will post to prove that with the ROM mentioned and Handcent, it works, but I cannot get this to work with any other ROM. Again, NOT 4G and not 16-26KB file sizes that I am interested specifically in.

1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks

chib1panda said:
1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks
Click to expand...
Click to collapse
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.

Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Docmjldds said:
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.
Click to expand...
Click to collapse

chib1panda said:
Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Click to expand...
Click to collapse
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
EDIT:
PS... I have all the older files for the legacy method here along with the necessary build.prop edits that are required to make that older HTC method work. Not sure it will even be worth it, but I am going to try adding that stuff, lib files and APK and edits to see if it's even possible to use the older wifi calling.
It may also mean also going back to Android 2.3.5 base. I'm pretty ADD about this subject. I just need to find the time

Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Docmjldds said:
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App

chib1panda said:
Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Just to show how lame TMobile support is, out on their tech Forums they are basically telling users NOT to even have wifi calling enabled. Below is a stock answer I see this mod. posting to everyone with issues complaining about this subject.
Being a retired bum, I do have some time on my hands. I can think of better ways to spend it, but this is one nut I really would like to crack. But at least there's a method on a particular ROM that does work. So deoending on importance of this feature will dictate what any user wants in a given ROM. BTW, don't know why the Zombie developer is placing his beta stuff outside of XDA, but there are references to links. Latest 3.1.1 includes update for the multiple toggles above notification area. Just an FYI...NOT...again NOT trying to be a Troll, but I can see how I can be accused, by now
IF...other ROMs would work, I would have no reason to state what to use...really...
http://www.androidzombie.com/az/Andr...x0.9KERNv2.zip
***********************************************************************************
TMobile Reply
8. Jan 11, 2012 8:42 AM (in response to sjmrshll)
Correct AnswerRe: MMS will not download while WiFi is enabled...
Hi!
Let me first thank you for being part of our community! We are happy to have you here and love to see you as an active participant. Unfortunately we cannot guarantee any of your services will work over the wi-fi network. Not being able to both send and receive MMS over wi-fi is an issue that can be slightly common.
If you have any further questions, please feel free to reply to this message or contact any member of the staff. Thank you and have a great day!
- Alicia B.
Community Moderator

1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!

Haven't tried zombie but the only rom I have tried that lets me send and receive mms while using wifi is when I'm on complete stock with root of course but its not really too much of a hassle to just switch wifi off if needed while using jugs 4.1 if it ever does get too annoying I always keep a backup of my stock just in case... So I know it has to be something that's been removed from the custom roms that keeps the phone from auto switching to data from wifi when using mms
Sent from my SGH-T989 using Tapatalk

rickm8384 said:
1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!
Click to expand...
Click to collapse
IT basically verifies what my claims have been. Something about the Zombie Rom is different to allow MMS to work correctly as long as Handcent is being used. I used Tmoble_SGH-T989UVKL1_Stock_Rooted.zip as a base 2.3.6 to compare with the latest Zombie ROM although versions of this ROM have always worked. Using a program that actually does a great job of side by side taking files withing a given folder to compare with another source of given files. All of the folders basically used the same exact files. The few times lets say that one ROM used a slightly different version lets say of wificalling.apk as an example could not break either the working Zombie functionality, nor could using the Zombie based file in the stock ROM would NOT make that ROM work either. IOW I tried to switch files between these two ROMs, to either create a working stock ROM, or break the function of the ZOMBIE Rom. Could not succeed in making or breaking opposing ROMs.

If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium

Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk

Killbynature said:
If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I am pretty much confident that you are correct it's a framework issue. I have used file comparison programs and rulled out every other source file, such as all of the lib files etc. And it has nothing to do with kernels. I have tested every kernel on all these ROMs and the same results occur, irregardless of kernel.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
drzplaya1121 said:
Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Nexus one was my first Android too. Bought it the first day of availability to the public, direct from Google back in Jan. 2010. The current Wifi calling is totally a different animal WRT our SGS2 phones. It's more or less based on the Network, itself, the proper Sim Card etc. Unlike the older WiFi calling that uses the Gans lib files and Build.prop edits, this doesn't rely on any of that stuff. And it's also a required Android 2.3.6 min. source. So yes...a totally different implementation.

I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom

This issue is fixed in the ics leaks. Rom reconnects.to 4g momentarily to send or receive mms
Sent from my SGH-T989 using XDA

xUnreachablex said:
I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom
Click to expand...
Click to collapse
I have the beastMOD 5.1 testbuild13 ROM also, but i could receive MMS and send MMS thru wifi in stock sms app. The only difference is that i have the darkside kernel.
Sent from my SGH-T989 using XDA

I'm using darkside rom with the included kernel, no mods or tweaks. WIFI calling and mms works fine, never experienced blurry mms.
Sent from my SGH-T989 using XDA

Samsung Galaxy S III remote data-wipe hack reportedly discovered (updated)

http://www.slashgear.com/samsung-galaxy-s-iii-remote-data-wipe-hack-discovered-25249061/
Little scary; of course if you only use reputable apps you probably have no concerns.
EDIT: yeah its a browser exploit; I hadn't had enough coffee this morning apparently.
Mr. QBKing77 has a video concerning this very thing ....
check it out here
Looks like they've put out an update anyway:
http://www.techradar.com/news/phone...galaxy-s3-and-co-to-block-killer-code-1099859

jdelano said:
http://www.slashgear.com/samsung-galaxy-s-iii-remote-data-wipe-hack-discovered-25249061/
Little scary; of course if you only use reputable apps you probably have no concerns.
Click to expand...
Click to collapse
Thanks for the heads up! :highfive:
I for one do not use NFC and rarely scan QR... But hopefully Samsung will take action on this security hole and patch it up ASAP, probably forcing them to send out JB sooner to the US variants together with the patch :fingers-crossed:

This can apparently be triggered by clicking a link on a malicious page too, not just NFC or QR codes. Not good.
However, from what I can see reading about this in a number of places, you're only susceptible if you're running TouchWiz... someone can correct me if I'm wrong but I believe this is a TouchWiz vulnerability really.
The thing I'm NOT 100% sure about is if you have to be RUNNING TouchWiz or if it can still be exploited if you're using a different launcher but still have TouchWiz installed.
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
Hmm, reading further, I guess I'm not sure what they mean when they say "TouchWiz"... do they mean just the launcher or are the changes Samsung made to Android, aside from the launcher, considered TouchWiz too? In which case what launcher you're using may not matter, you are at risk of this exploit either way. Not sure, although now I'm thinking launcher DOESN'T matter. Anyone?

fzammetti said:
This can apparently be triggered by clicking a link on a malicious page too, not just NFC or QR codes. Not good.
However, from what I can see reading about this in a number of places, you're only susceptible if you're running TouchWiz... someone can correct me if I'm wrong but I believe this is a TouchWiz vulnerability really.
The thing I'm NOT 100% sure about is if you have to be RUNNING TouchWiz or if it can still be exploited if you're using a different launcher but still have TouchWiz installed.
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
Hmm, reading further, I guess I'm not sure what they mean when they say "TouchWiz"... do they mean just the launcher or are the changes Samsung made to Android, aside from the launcher, considered TouchWiz too? In which case what launcher you're using may not matter, you are at risk of this exploit either way. Not sure, although now I'm thinking launcher DOESN'T matter. Anyone?
Click to expand...
Click to collapse
I believe they are referring in some point to the TW dialer, since they mention a dial code that is present in AOSP dialer and the user can simply cancel before it goes out, in the case of TW dialer it automatically goes through without the ability to cancel at all. Scary stuff!
"Only Samsung devices running TouchWiz appear to be affected, with basic Android only showing the code in the dialer screen but not running it automatically, Pau Oliva reports. Samsung’s default, though, is to dial the code automatically."
I think the article needs a bit more detail...

fzammetti said:
This can apparently be triggered by clicking a link on a malicious page too, not just NFC or QR codes. Not good.
However, from what I can see reading about this in a number of places, you're only susceptible if you're running TouchWiz... someone can correct me if I'm wrong but I believe this is a TouchWiz vulnerability really.
The thing I'm NOT 100% sure about is if you have to be RUNNING TouchWiz or if it can still be exploited if you're using a different launcher but still have TouchWiz installed.
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
Hmm, reading further, I guess I'm not sure what they mean when they say "TouchWiz"... do they mean just the launcher or are the changes Samsung made to Android, aside from the launcher, considered TouchWiz too? In which case what launcher you're using may not matter, you are at risk of this exploit either way. Not sure, although now I'm thinking launcher DOESN'T matter. Anyone?
Click to expand...
Click to collapse
Not launcher. TW rom. As long as you are on a TW rom your susceptible. Aokp, aosp, etc won't work. You pretty much have to be able to use dialer codes because that's how it wipes your data, it automatically puts in the wipe data code
Sent from my SPH-L710 using Tapatalk 2

xCovErtWolFx757 said:
Not launcher. TW rom. As long as you are on a TW rom your susceptible. Aokp, aosp, etc won't work. You pretty much have to be able to use dialer codes because that's how it wipes your data, it automatically puts in the wipe data code
Click to expand...
Click to collapse
Yeah, I thought it might have just been TW launcher at first but after reading things a bit more I got what you said too... that's not cool

Problem was reported by a dev on Twitter to SamsungCarla and she escalated it to security unit.

So, according to AndroidPolice:
The bug is based in the stock Android browser, is in fact quite old, and has been patched in more recent builds of Android - this is probably why Nexus devices running the most recent OTAs are unaffected. The fact is, this is not a Samsung problem, it's an old Android problem that has been known about for some time. More recent versions of Android avoid the wipe issue, but unpatched devices (like some Samsung phones) may still be vulnerable.
Click to expand...
Click to collapse
http://www.androidpolice.com/2012/0...eset-on-many-samsung-phones-running-touchwiz/
Guess it will take a while to get the true story.

poit said:
So, according to AndroidPolice:
http://www.androidpolice.com/2012/0...eset-on-many-samsung-phones-running-touchwiz/
Guess it will take a while to get the true story.
Click to expand...
Click to collapse
That's interesting because it says to me that just disabling the default browser, as I've done since I use others, should avoid the issue... that'd be my conjecture anyway... but I'm NOT willing to test
Plus, that link also has an update saying the latest OTA for the GSIII don't suffer this problem... but that's a pretty nebulous statement, vis a vis, does it mean the latest Sprint OTA for example, or does it mean the GB for international models that started rolling out in Poland?
You're definitely right, the true story seems to be something we're still waiting on

On android police they also say that the AT&T doesn't have it, it got patched last week. Maybe LI3 fixed this.
Sent from my SPH-L710 using xda app-developers app

Nothing to see here people. This is not an exploit, but a feature called S-Reset.
Sent from my Nexus 7 using Tapatalk 2

hayabusa1300cc said:
Nothing to see here people. This is not an exploit, but a feature called S-Reset.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
ROFL!!! :highfive:

add QBKing's video link to op
check it out; QB King does a really nice video showing you just how this happens.

This has apple written over it
Apple just give up the IPHONE sucks deal with it.

Tried the test site on QBKings video and nothing happened except the dialer opening. (Stock rooted LG8)

jamcar said:
On android police they also say that the AT&T doesn't have it, it got patched last week. Maybe LI3 fixed this.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Tried that link that shows imei from qbking on my gs3 with li3 and my wife's that's still running lg8 and it doesn't do anything. Think the latest softwares fixed that issue
Sent from my SPH-L710 using Tapatalk 2

I have a S3 running CM9, I tested this link http://dylanreeve.com/phone.php and my phone shows immediately my emei without any confirmation box !!

Well ppl make sure you all have a handy dandy nandroid just in case
Sent from my Sprint GS3

Samsung fixed it
I added a link to a story that says Samsung has fixed this (even though the S3 seems to be ok)

Yup, according to Engadget:
If you were worried about stumbling onto a malicious website and accidentally wiping your Samsung Galaxy S III or other TouchWiz smartphone or slate, you can probably breathe easy. It's likely you already have firmware on your device which isn't vulnerable to the so-called dirty USSD code, and if not, you can download it now, according to Samsung. The company issued the following statement on the matter: "We would like to assure our customers that the recent security issue concerning the Galaxy S III has already been resolved through a software update. We recommend all Galaxy S III customers download the latest software update, which can be done quickly and easily via the Over-The-Air (OTA) service." It turns out we couldn't reproduce the bug earlier as we already had the latest update, and you should probably check to see that you do, as well. Meanwhile, we're also checking to see if other Touchwiz devices have been patched, so don't forget to watch what you click.
Click to expand...
Click to collapse
http://www.engadget.com/2012/09/26/samsung-patched-dirty-USSD-vulnerability/
So it appears this is an old exploit that was patched long ago

(Warning) of touchwiz browser vulnerability (factory reset)

Found this today so heads up ppl we are at risk website can factory reset our device with one script http://m.androidcentral.com/major-s...hones-could-trigger-factory-reset-web-browser

WOW!

idbl_fanatic said:
WOW!
Click to expand...
Click to collapse
Time for a non-TW rom, lol.

desultory677 said:
Time for a non-TW rom, lol.
Click to expand...
Click to collapse
I just read it, It can broke your sim as well. So its not just a factory reset

Video and original post here
http://www.androidpolice.com/2012/0...eset-on-many-samsung-phones-running-touchwiz/
Please read this
Sent from my SGH-T989 using xda premium

Android PoliceMenu
[Update: Not Just Samsung] Exploit Could Force Factory Reset On Many Android Phones
Published on September 25th, 2012Written by: Cameron SummersonNextSkip to ResponsesPrevUpdate 2:*This exploit probably won't work on most*Galaxy S III's as long as they have the most recent OTA update, as*we demonstrate on video here.Update:*This issue is, unsurprisingly, a lot more nuanced than the video here lets on. The bug is based in the stock Android browser, is in fact quite old, and has been patched in more recent builds of Android - this is probably why Nexus devices running the most recent OTAs are unaffected. The fact is, this is not a Samsung problem, it's an old Android problem that has been known about for some time. More recent versions of Android avoid the wipe issue, but unpatched devices (like some Samsung phones) may still be vulnerable.Ouch. This is not the type of PR Samsung needs right now. Apparently a new vulnerability has been found that can force a factory reset with zero user interaction on many Samsung phones running TouchWiz. The bug is found within the stock TW browser, which allows direct execution of dialer codes like the one used for this exploit. This code is easily embedded into HTML, so one tap of a malicious link will reset the phone instantly. Other browsers, like Chrome, Dolphin, etc. aren't affected, so we highly recommend switching if you've been using the stock TouchWiz browser.At this time it's unclear exactly how many Samsung phones are affected, but so far users have been able to reproduce the issue on the*Galaxy S II*(assume all variants), the*Galaxy SAdvance, Galaxy Beam, and Galaxy Ace, among others. From what we're hearing, the international GSIII variant*should*be unaffected, and the AT&T version was updated with a patch for this very exploit last week. It's unknown at this time whether or not the*Sprint, Verizon, and T-Mobile variants are susceptible.We'll keep you updated as more information comes to light.[The Verge,*Engadget]Categories:*News,*SamsungTags:*exploit,*factory reset,*Samsung,*TouchWiz,*vulnerabilitesShare Article** **Save to InstapaperNextBack to TopPrevMobile ThemeONOFF1 queries in 379.8 ms
Sent from my SGH-T989 using xda premium

http://forum.xda-developers.com/showthread.php?t=1904867
Sent from my SAMSUNG-SGH-T989 using xda premium

I found a test page on neowin, that uses the same exploit but shows ur IMEI instead to see whether you're vulnerable
http://haggistech.co.uk/USSDtest/
My CM9 **IS** vulnerable. WTF!

So I did the "test" website and if it is correct me on Eugene's asop build are at risk as well...hope the website is wrong.

Funny how before all the hackers (well the ones that are looking to exploit people, not the hardware for a benefit) were going after your pc, and now it's just as easy to go after your phone. I still don't know why someone would want to do this to a bunch of phones, but people are weird sometimes
It is kind of freaky knowing our phone is vulnerable, but then again, any time something new comes out, someone is going to try and hack it in a negative way. Grr, why people? Just develop ROM's, not exploits
Sent from my SGH-T989D using xda premium

I'm assuming AOKP is no exception to this? Basically anywhere the default browser exists right??
Edit : Tested the website and it popped open a dialer but displayed the digits needed to pop open the IMEI..does that still mean I'm vulnerable? AOKP Build 3.
Sent from my SGH-T989 using xda app-developers app

My dialer opened but no imei or ussd code appeared. Using stock rooted 4.0.4

Rekzer said:
I found a test page on neowin, that uses the same exploit but shows ur IMEI instead to see whether you're vulnerable
http://haggistech.co.uk/USSDtest/
My CM9 **IS** vulnerable. WTF!
Click to expand...
Click to collapse
i tried all the browsers for android, Stock, Chrome, Firefox, Dopehin, etc
They are all vulnerable, except for OPERA!!!
so, if you're the types that are paranoid, I'll suggest you to make Opera as the default browser in your phone
Sent from my SAMSUNG-SGH-T989 using xda premium

kitila said:
Found this today so heads up ppl we are at risk website can factory reset our device with one script http://m.androidcentral.com/major-s...hones-could-trigger-factory-reset-web-browser
Click to expand...
Click to collapse
Wow that's no bueno
Thanks for the heads up.

Tested Jedi mind trik V7... no good
I don't know whetehr the newer version is vulnerable, but if stock 4.04 has no problems I would think even the cooked rom based on it should be fine
---------- Post added at 08:31 PM ---------- Previous post was at 08:02 PM ----------
benti77 said:
Tested Jedi mind trik V7... no good
I don't know whetehr the newer version is vulnerable, but if stock 4.04 has no problems I would think even the cooked rom based on it should be fine
Click to expand...
Click to collapse
Installing DialerOne you block the exploit, infact android will ask you wich dialer use, so you just have to choose the new one.
The original dialer remains there to be used normally.
Waiting for new from my loved developer :good:

Noooo
read above
the hack / exploit / vulnerability only works if your browser is not patched
just avoid using a vulnerable browser then you wont have anything to worry about.
OPERA browser is not affected, tested them all.

AllGamer said:
Noooo
read above
the hack / exploit / vulnerability only works if your browser is not patched
just avoid using a vulnerable browser then you wont have anything to worry about.
OPERA browser is not affected, tested them all.
Click to expand...
Click to collapse
But how come i dont get anything? I have stock rooted 4.0.4

AllGamer said:
Noooo
read above
the hack / exploit / vulnerability only works if your browser is not patched
just avoid using a vulnerable browser then you wont have anything to worry about.
OPERA browser is not affected, tested them all.
Click to expand...
Click to collapse
thanks, but I really like using dolphin
even if has been a long long time since I last tried Opera on android...

AllGamer said:
Noooo
read above
the hack / exploit / vulnerability only works if your browser is not patched
just avoid using a vulnerable browser then you wont have anything to worry about.
OPERA browser is not affected, tested them all.
Click to expand...
Click to collapse
Are you sure it's just the browser? Has anyone tried using a ripped browser from the apparently patched S3 then? I'll give it a shot now.
Sent from my SGH-T989 using Tapatalk 2

From what I read the phone is only vulnerable if your IMEI shows on the phone dialer, correct. If so Dolphin is not vulnerable. Tested with latest version.

Different dialer

Hi all,
Is there an alternative to the stock dialer for the SIII? Couple of things I don't like about the stock one if anyone knows any fixes for it that I'm not aware of.
When using the keypad to enter the name or number of the person you want to call, my old phone's dialer would suggest people or numbers based on recent or frequent calls so I can punch in a few letters or numbers and who I want to call would normally be at the top of the list and i can just click the name and it would call. The SIII doesn't seem to do that.
Also, this dialer seems pretty sluggish sometimes when working with dialer screens (dialing the chosen number, opening pull down menu, going between tabs, etc.).
Thanks,
Ho'okani

Hookani said:
Hi all,
Is there an alternative to the stock dialer for the SIII? Couple of things I don't like about the stock one if anyone knows any fixes for it that I'm not aware of.
When using the keypad to enter the name or number of the person you want to call, my old phone's dialer would suggest people or numbers based on recent or frequent calls so I can punch in a few letters or numbers and who I want to call would normally be at the top of the list and i can just click the name and it would call. The SIII doesn't seem to do that.
Also, this dialer seems pretty sluggish sometimes when working with dialer screens (dialing the chosen number, opening pull down menu, going between tabs, etc.).
Thanks,
Ho'okani
Click to expand...
Click to collapse
Yea man you type the first number(letter) it pulls a name and next to that name it shows an arrow pointing down with the list of names for that letter. Works great
Sent from my SGH-T999 using xda app-developers app

Thanks. Knew about the arrow thing but just looking for something more intuitive. When you open up the list of names there doesn't seem to be any logical order to it and the ones at the top are usually names I rarely call. You would think the most used or recently called names would be at the top. Plus my phone seems sluggish when trying to open that list of names.
Thanks,
Ho'okani

App store search for dialer will answer your questions.
Sent from my SAMSUNG-SGH-I747 using xda premium

My favorite is exDialer paired with exDialer ICS Theme. Both free ON Google Play.

Thanks. Trying out exDialer and seems to be pretty good so far.
Ho'okani

Try out task650 aokp rom its got that and way way more
Sent from my SGH-I747M using xda premium

thatsupnow said:
Try out task650 aokp rom its got that and way way more
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Any AOSP rom for that matter, the dialer on AOSP roms are really good. But if you want to stay on the default rom, I'd +1 exdialer for its customization options and speed. I think there are modified stock roms with the AOSP dialer, but I'm not too sure/can't find them at the moment.