I apologize in advance for my english.
Hi guys, I think I have a big problem with my GSIII.
My phone is rooted, WanamLite 5.2 ELL5, Phenomenal 4.0 Extreme; my carrier is Vodafone and my plan provides 1 GB per month of navigation.
I started to notice a massive (relative to me) money consumption.
Yesterday, when I had 28 cents left, my credit decreased to 8 cents after receiving a SMS (18 cents is the standard cost of a SMS for my plan) but I wasn't doing anything! Further checks let me discover that using the secret sms plug-in of the "Hide it pro" app costs 18 cents for every SMS received or sent, even if my plan provides them.
I obviously disinstalled the app, but I wanted to wait a bit, to check if all it's ok.
Some time later (a couple of hours), with still 8 cents left and doing nothing, I received a SMS from Vodafone, informing me that my credit wasn't sufficient for doing what I wanted to! I wiped data (factory reset) from CWM and also a factory data restoration (from the settings).
Today, still 8 cents left, at 13 o'clock I received another SMS from Vodafone like the previous one (yesterday).
Do you think that the problem is related to the phone (dunno, a virus?), or not?
Thanks a lot.
Use the free app "Permission Explorer" and check which apps are allowed to receive or send SMS or do phone calls.
Obvisously something is not quite as it is supposed to be.
Stock and some stockish Samsung roms have the Exynos Camera bug which allows any app to gain root access and thus install itself in the system itself and by consequence prevent being removed by a full-wipe. Any app you used which uses root could also have done the same. Not saying this actually did happen but it's a very real possibility. Only completely secure solution is to flash a full firmware (including recovery!) from Odin since theoretically CWM cannot be trusted either anymore, should the phone be compromised.
Easy steps would be:
- flash back to stock (any stock)
- flash Siyah through Odin
- boot to CWM (should be included in Siyah)
- factory-reset the phone
- install a freshly downloaded copy of Wanamlite
- reinstall Siyah kernel
- restore your apps and data (obviously making sure you trust all and any that require access to the camera, sending SMS or such)
On a side-note: I know that some crazy phone providers actually cost to RECEIVE sms and not only send. Could it be you are receiving SMS' from someone?
d4fseeker said:
Use the free app "Permission Explorer" and check which apps are allowed to receive or send SMS or do phone calls.
Obvisously something is not quite as it is supposed to be.
Stock and some stockish Samsung roms have the Exynos Camera bug which allows any app to gain root access and thus install itself in the system itself and by consequence prevent being removed by a full-wipe. Any app you used which uses root could also have done the same. Not saying this actually did happen but it's a very real possibility. Only completely secure solution is to flash a full firmware (including recovery!) from Odin since theoretically CWM cannot be trusted either anymore, should the phone be compromised.
Easy steps would be:
- flash back to stock (any stock)
- flash Siyah through Odin
- boot to CWM (should be included in Siyah)
- factory-reset the phone
- install a freshly downloaded copy of Wanamlite
- reinstall Siyah kernel
- restore your apps and data (obviously making sure you trust all and any that require access to the camera, sending SMS or such)
On a side-note: I know that some crazy phone providers actually cost to RECEIVE sms and not only send. Could it be you are receiving SMS' from someone?
Click to expand...
Click to collapse
Thanks a lot (I already know, however, about Camera Bug reported from Faryaab ).
I'll proceed as you wrote, only one question: why Siyah?
However, Vodafone doesn't apply costs for received SMSs from standard numbers (even of other carriers), as the one I received the message from.
In attach files there is the list of apps with "write sms permission".
Now I'm going to flash through Odin stock Ita firmware, I already have it...
WTF is joyn?!?!
UPDATE!!!
I restored again from settings. When it completed, I received the usual sms from Vodafone about insufficient credit! WTF?
Now I'll flash stock Ita...
UPDATE #2
After flashing Stock Ita, I received THREE SMS from Vodafone about attempting to do something...
joyn app in permission explorer disappeared, but ChatON, SVoice, Keyboard, Favourite Contacts and Samsung Apps appeared.
Related
Having upgraded to XXKI3, I noticed samsungdive (tracking / Find the phone feature..) is no longer working. I had a closer look seemingly IMEITracker.apk (system app) is not there either - this might be the cause ?
I wonder if this just happened to me or someone else ?
Samsung Dive works with me and I am on KI3 villainrom
Doesn't work for me either.
Sent from my GT-I9100 using XDA App
@achillies400 : i guessed it could be the feature of VillainRom - have IMEITracker.apk hang over from old rom
@rdbhalla: wonder if you can check via RootExplorer or something similar that you didn't have IMEITracker.apk in "/system/app" either ?
Same problem here on non-wipe (frankenstein), non-rooted stock xxki3 on Bell Canada.
qbnb said:
Same problem here on non-wipe (frankenstein), non-rooted stock xxki3 on Bell Canada.
Click to expand...
Click to collapse
I receive no errors but when I try accessing any of the functions on the Samsung Dive website (ex: "Find my mobile") on both Firefox and Chrome I have no success, it never successfully connects just thinks about it for hours.
I also noticed that imeitracker.apk was not present but mobiletracker.apk was, not sure if that makes a difference.
I re-flashed the release firmware - and apparently imeitracker.apk is no longer there definitely. Re-used the old version made no different as well.
If mobile tracking is important for you, I reckon it's time to move on . The free version of AVG Mobilation is good enough for me. (Sorry as new member I cannot post link) - Google will do
same for me ... dive stop working after flashing leomar revolution 2.7.1 ( ki3 )...
btw imeitracker.apk is present on /sustem/app ( root explorer )
also tried to restore my 2.6 backup ( kh3 ) and still not working ... pretty confused because it was working fine on 2.6 before updating to 2.7.1 ...
Yip. I had flashed back to XXKH3 (which originally worked), it didn't help too. I started wondering if that's a backend problem from Samsung ? Notice the webapp got updated recently .
for myself i think the issue come from ki3 cause on my second galaxy s II ( revolution 2.6 never updated to ki3 ) it's still working fine ...
I have just tried it on my Touch KI3 rom and it is not working as well. Have anyone found a workaround yet?
Looks like there's a number of missing files in KI3 - maybe integrated into something else, maybe removed entirely?
File link in post here: http://forum.xda-developers.com/showpost.php?p=18101252&postcount=4
Hi,
I have been using KI3 for past 1-2 weeks and i have no issues with Samsung Dive....i can call my ccell, track my location, get logs, wipe data..everything......not sure why u cant...
i used KI3 uploaded my intratech and samfirmware....
have you used samsung account in ur cell..in accnt and sync section???
may be a complete reset will work.....
just throwing my 2 cents......
@smilingcruel ... m8 you're lucky
here even after full wipe, kh3 restore, etc etc etc nothing to do ... dive won't connect to my phone ...
of course all setting are ok ( samsung account linked, mobile tracking is active )
tried on wifi, 3g ... just nothing
and it was working perfectly before ki3 update ...
btw i noticed something strange on titanium backup ... no I have com.android.imeitracker strikethrough and grayed ( like not installed backup )
but i can't do nothing w/ it ... it's not a backup, i can't uninstall/install it ... nothing to do ...
and of course this is not present on my second SII w/ kh3 ( revolution 2.6 ) that have never been updated to ki3 ...
This purely a piece of guess from. But this XXKI3 release is for Poland which outside the current service zone of SamsungDive (i read somewhere UK/German and some other regions) .. hence the removal of IMEITracker.apk which explained why it's not working.
After all, i just don't bother now ...move on to some other service and freeze the rest apps to save memory
For @OniKim, the titanium have grey, strike-out package because IMEITracker.apk create a data folder and Titanium backup picks it up yet can not find (for some reason) the matched APK.
If you want to remove it, look into "/data/" there is a folder called "com.android.IMEITracker" then removing this will be okay else just leave it there
humm ... ok about the ki3 release issue cause it's for poland ...
but what is making me going crazy it's why after restoring kh3 dive is still not working ... and why dive still working for lots of people w/ ki3
btx thx for the info about imeitraker data folder ...
also can you point me to the alternate solution you're using ???
i really want a remote acces to my phone ...
As I've said earlier... I gave up on this.
I assume you mean remote tracking / lock instead of access.
But anyway here is the one that I used AVG Mobilation from AVG http://www.avgmobilation.com/
It's free for tracking, remote lock, shout ... all just work - I haven't tried the remote wipe for an obvious reason . Btw, it comes free with antivirus
oups sorry i missed your first post about avg
and yes by remote access i mean remote tracking etc ...
anyway will give it a try ... thx for the info !!!
I had the same problem (rooted SGS2 with 2.3.5 and KI3) - I have createted a new Samsumg-Account and it works now. The Problem is, it is normaly not possible to delete the Samsung-Account without a hard reset.
I have do this with Titanium Backup:
-> backup your phone with TB
-> deaktivate with TB the Samsung-Account
-> reboot the phone
-> restore the Samsung-Account without data
-> activate the Samsung account again
-> now you can create a new account
I hope this workaround works on your side too...
JHimmelbauer said:
I have do this with Titanium Backup:
-> backup your phone with TB
-> deaktivate with TB the Samsung-Account
-> reboot the phone
-> restore the Samsung-Account without data
-> activate the Samsung account again
-> now you can create a new account
I hope this workaround works on your side too...
Click to expand...
Click to collapse
Thanks! That totally worked. I've added a couple of notes for those that follow this process to make it clearer for noobs like me.
-> backup your phone with Titanium Backup - the specific file/app you need to backup is called "Samsung Account" (v1.0 in my case)
-> Freeze Samsung Account with TB
-> reboot the phone
-> go back into TB and restore the Samsung-Account *without* data
-> activate the Samsung account again (Settings -> Accounts and sync -> add account)
-> now you can add a samsung account. You can still use the Samsung account you had previously (e.g. use the same email and password) and just recreating it will make samsungdrive start to work again.
I've spent the whole night trying to figure this out so hopefully the information is useful for some of of you
The usual scenario is that the phone is encrypted due to using Exchange email (eg. Corporate email) and now you can't upgrade or root it. The first thing to do is to delete that email account and hopefully the phone will decrypt itself or the option appears when you go to phone security settings. You can also try to access the corporate email via a browser and delete the mobile connection.
This worked for me previously but it doesn't now - I don't know if its because I'm using a non-stock rom. Either way a lot of people seems to be stuck with a Samsung rom as well. So you now have a phone with the exchange account gone and its restriction so you should in theory be able to removing the decryption but no it doesn't work. I don't know why as this is a basic OS stuff.
At this stage you can try to full wipe it - but this doesn't work, both through settings or CWM. The only way to sort this out is to copy / backup all your information then flash it to factory state and this means using odin and a stock rom. I've done this several times and there is no lasting issues.
I''m by no mean an expert and would be happy for anyone to correct me
I have a problem on my Galaxy S3, running android 4.1.1 on Vodafone network in the UK. It is not rooted.
I want to make sure the phone is unlocked before buying a sim card for use in France
Using the stock dialer, "*#7465625#" gives me "ussd code running" followed by "Unknown command".
Looking around elsewhere, others have blamed it on Mobile Tracker, which as far as I can see, I don't have. The only solution I have seen is a factory reset, which is a scary prospect for me, not having any idea what that entails. And then reinstalling apps one by one until the culprit is found. I have also seen comments about ussd security issues. I am slowly heading out of my depth here (I know my way round windows quite well, but phones are unknown territory for me,).
I am hoping some clever souls on this forum might be able to help. Is this a known, and solved, problem? Or is a factory reset my best bet?
If I have to reset, I know where the reset is in the menu system - on the same page as a checked box saying backup. So...does does the back up happen automatically or when I press reset or have I got it completely wrong? If not, which files do I need to save away from the phone? What happens to things like contacts I can remove the external SD card, so that won't be an issue. How do I reinstall the apps, particularly the ones I have already paid for?
I have spent most of the afternoon tried to get a handle on this and my head is spinning now.
Any help at all, would be very warmly received.
Polly
1st solution : root your phone, very easy procedure then you can flash the same stock ROM from sammobile.com to become unrooted again without wiping/resetting your phone.
2nd solution: download APPSAVER from market for free, then you can save all the applications you have downloaded but not the DATA (for example you can save the game itself but not the progress you have achieved)
as for the contacts, go to the contacts folder - menu import/export - export to usb storage and voila all your contacts will be written in a single file that you can import after you reset your phone
as for SMS, you can download "SMS Backup & Restore" from market for free to backup then restore your SMSs
after you perform the above, go to Settings - Back up and reset - Factory data reset and your phone will be back as you received it.
On the other hand if the phone is locked you can always unlock it using Voodoo S3 on the Play Store, it can sim-unlock your device if you're rooted of course.
Great reply, thank you!
Rooting...a bit loth to do that while still under guarantee and at my level of experience. One day I will get hold of an old phone and try it with that first.
Appsaver - what a brilliant app, thank you again. If it is one particular app that is the problem (and that is the sense that I get from elsewhere), then I can use this to back up my apps, uninstall them all, check for the ussd error. If it has disappeared, then reinstall apps one at a time until the error reappears. If it hasn't disappeared, then I can go the reset route, after backing up contacts and SMS.
Thank you so much for your help.
Polly
the code *#7465625# doesn't work on Jelly Bean anymore..
v2leech said:
the code *#7465625# doesn't work on Jelly Bean anymore..
Click to expand...
Click to collapse
Ah. The more I try to read up on this, it feels the more lost I get.
How do I check whether the phone is unlocked...borrow someone's micro sim card?
Hi,
I am running standard Samsung ROM on my S3. Last night installed a new Firmware Update pushed OTA. Since then I have completely lost all SMS functionality and even any trace of the SMS function. The 'Messaging' icon does not exist anywhere and when I 'swipe left' on a contact to send a message the only option that comes up is to use Skype or WhatsApp. In the call log there are the numbers of which I have received an SMS from, but touching that I get to a log with a little blue envelope and I cannot see the message. The only way I have managed to find the actual SMS are using the app 'SMS Backup & Restore', that one finds them in the backup, but no other way available.
Anyone else came across this problem? Is there a way I can downgrade my firmware to previous version? (I do not have a full backup available, and to be honest, not quite sure how to backup 'everything' when I am not rooted)
Model: GT-9300
Android: 4.1.2
Baseband: I9300XXELLA
Kernel: 3.0.31-1276773
Build: JZO54K.I9300ZSEMF1
Thanks for any comments!
/Dan
flash the offcial 4.2.2 via odin and you wiil be fine you dont lose anything
If you were rooted, you could extract the required SMS .apk from a stock ROM zip and install that.
As a temporary workaround, you can try to use an app like GO SMS.
Thanks for your feedback and suggestions! I have worked the problem this weekend and eventually got functionalities back through 'Firmware Installation' in Kies. I will look further at Odin though as well. Sounds an interesting option. Thanks for that tip too!
/Dan
Sent from my GT-I9300 using xda premium
Checked your SMS settings are correct ?? in message centre .
jje
Hi, I have some issues with S-Voice on my Galaxy S3.
When I use S-Voice to send a text message or make a call by using contact name (for example if I say "Call François Dupont"), it records my sentence, starts the voice recognition phase, and perfectly writes back my sentence on the screen, but nothing happens. It does not call Mister Dupont as I asked him.
But if I tell him the phone number instead of contact name, it's working perfectly, so if I say "Call 01 99 88 77 66", S-Voice use an audio feedback to tell me he is calling the given number, and it starts the call.
Someone else with the same issue ? is there a solution somewhere ?
I'm using ArchiDroid 1.7.9 (based on stock 4.3 UGNA7) with bloatware package installed, I face the same issue with an older stock ROM (it was the stock Samsung MK1), and it worked again with a previous AD version (1.7.6, based on ML4 if I remember well).
What is causing this ? it looks like S-Voice is unable to access the contact list...
I made some trials to understand why this phenomenon happens.
First I started with a backup of my actual ROM (ArchiDroid 1.7.9 based on Samsung NA7) and the content of my internal memory and SDcard.
Then, I tried to install the latest official 4.3 ROM for my version of the Galaxy S3 (code FTM, branded by Orange) : the firwmare is ML2.
I downloaded it and flashed it with Odin 3.09. I had the surprise after reboot to find my apps and parameters... I thought Odin would erase everything, but no, it has left everything.
So I made the test :
** Stock official Samsung ML2 : S-Voice fails. If I tell "her" to send a message, she asks who to send the message to, I say "François Dupont" (name has been changed), she writes "François Dupont" after the speech recognition, and stops.
So I made a factory reset, wiping data, internal memory and sd-card, entered my account, wait for the syncs to end, and started again :
** Stock official Samsung ML2 after full wipe : S-Voice fails. If I tell "her" to send a message, she asks who to send the message to, I say "François Dupont" (name has been changed), she writes "François Dupont" after the speech recognition, and stops.
So I decided to return to ArchiDroid 1.7.6 (based on ML4).
I flashed recovery through Odin and installed ArchiDroid 1.7.6, making a full wipe again, and test again after end of syncs :
** ArchiDroid 1.7.6 : S-Voice works perfectly. If I tell "her" to send a message, she asks who to send the message to, I say "François Dupont" (name has been changed), and after the speech recognition, she asks to select the phone number I want to send the message to, then requests the message to be sent, and proposes to send it.
I continued the test by installing ArchiDroid 1.7.7 (still based on ML4) over 1.7.6 (no wipe, using previous preset, only used the forced update mode of ArchiDroid installer).
** ArchiDroid 1.7.7 : S-Voice works perfectly. If I tell "her" to send a message, she asks who to send the message to, I say "François Dupont" (name has been changed), and after the speech recognition, she asks to select the phone number I want to send the message to, then requests the message to be sent, and proposes to send it.
So I continued the test by doing a backup and installing the ArchiDroid 1.7.9 (based on NA7) over 1.7.7. Strange thing is that it could not use my previous preset, I had to recreate it.
** ArchiDroid 1.7.9 : S-Voice fails. If I tell "her" to send a message, she asks who to send the message to, I say "François Dupont" (name has been changed), she writes "François Dupont" after the speech recognition, and stops.
I wiped everything, and restored the backup of 1.7.7, reboot and again :
** ArchiDroid 1.7.7 : S-Voice works perfectly. If I tell "her" to send a message, she asks who to send the message to, I say "François Dupont" (name has been changed), and after the speech recognition, she asks to select the phone number I want to send the message to, then requests the message to be sent, and proposes to send it.
I then tried to make a TB-backup of the ML4 apps (contacts, phone, s-voice and messages) and install the ArchiDroid 1.7.8 :
** ArchiDroid 1.7.8 : S-Voice fails. If I tell "her" to send a message, she asks who to send the message to, I say "François Dupont" (name has been changed), she writes "François Dupont" after the speech recognition, and stops.
I then tried to restore the different apps backup I had from ML4 and rebooted, but no way, S-Voice is still broken.
So I'm going to use ArchiDroid 1.7.7 for the moment.
If you've installed the whole bloatware before first boot, then there's no way that something could not work properly (I'm talking about .zip package).
Eventually you can compare my deodexed bases with stock bases, but I highly doubt that deodexing could cause such strange issues, especially because it works in some much more customized releases (ArchiDroid).
I'm going to read this all through, I've never been able to use the S voice.
JustArchi said:
If you've installed the whole bloatware before first boot, then there's no way that something could not work properly (I'm talking about .zip package).
Eventually you can compare my deodexed bases with stock bases, but I highly doubt that deodexing could cause such strange issues, especially because it works in some much more customized releases (ArchiDroid).
Click to expand...
Click to collapse
I tried both, it does not change the behavior whether I flash the bloatware package before or after first boot. The only thing that seems to have an effect is the version of the base ROM.
ScratMan38 said:
I tried both, it does not change the behavior whether I flash the bloatware package before or after first boot. The only thing that seems to have an effect is the version of the base ROM.
Click to expand...
Click to collapse
I'm out of ideas then. You'd need to compare my deodexed base with stock base, it's the only thing which comes to my mind.
JustArchi said:
I'm out of ideas then. You'd need to compare my deodexed base with stock base, it's the only thing which comes to my mind.
Click to expand...
Click to collapse
I agree with you, it seems the issue is not from your mods but from stock samsung firmwares. With the stock Samsung ML2 (official firmware) it doesn't work, but with your modded ML4 it is working.
I made this post mainly to inform you it was not your fault if S-Voice was failing, but only Samsung's fault.
The only thing I don't understand is why I'm the only one to report this issue.
Update : with the UGNB1 firmware, using the corresponding ArchiDroid ROM (v1.7.13), S-Voice is working correctly, it correctly resolves the contact's name and asks for the text of the message.:victory:
Hope Samsung will keep it the good way for future updates.