Hi all,
Just got my new SGS...
One small problem: can't send sms messages. Did correct the SMSC number in Messaging application (+27829129).
But, when I use "*#*#4636#*#*" to check the SMSC, I get a completely wrong number.
The same sim card work fine on previous HTC Touch pro.....
Any ideas on how to fix this problem?
(Using Froyo I9000XXJPM via ODIN [http://forum.xda-developers.com/showthread.php?t=807886])
Thanks,
D.
did this happen after you updated your phone?
i had the same prob, i had to wipe the phone to get it to work again.
Can you receive text?
Talk to your wireless service provider before you jump the gun and wipe everything.
When I had an issue with sending text (not receiving), my provider sent me a special text (with some settings). It fixed my sending issue.
Did a factory reset and everything worked.
THEN, used SMS Backup and restore to restore all my old SMSes - and it stopped working again.
Seems as if there is a bad "SMS" somewhere in the sms store....
Deleted all messages and everything is working 100%.
D.
i have the same problem
i only on rogers with the i9000m
i sent a text this morning....but now that everytime i try to send something it said failed....
so i have to do a factory reset?
I'm having the same issue with rogers/i9000m
930929930 said:
i have the same problem
i only on rogers with the i9000m
i sent a text this morning....but now that everytime i try to send something it said failed....
so i have to do a factory reset?
Click to expand...
Click to collapse
Guys I have an issue too, I still can't send any messages, I am on 4.1.2 REMICS, I even flashed old 2.3.6 JVU and it didn't work on it too. Do I have to call my provider and ask him for the instructions?
Hi everybody, I've recently bought a new I8190N, about two weeks ago, coming from a rooted but messed up Galaxy Ace, I decided to don't root it at all just for now, but a few days ago, when I was texting my gf (with the stock sms app), all new messages I was sending were not sending at all, the sending spinner just stayed there forever.
Then, I pressed back and after a millisecond conversations thread became empty, saying "no messages, to write a new message... etc", so I tried backup sms's with Sms Backup & Restore and it did, they were all still there, but neither stock sms app nor go sms pro displayed them. After a reboot, they magically reappeared. From then, it happened once a day independently from how many messages I am sending.
Also, I read of similar problems on lots of other Samsung phones, but no solution was found all over the internet, so, is this a Samsung's Jelly Bean bug or could it be just an app that interferes with mmssms.db? Or a carrier related issue? :banghead: Thanks to everyone who will help me
Sent from my GT-I8190N using a rocket powered banana
Why don't you try a newer firmware with ODIN? As far as I know, first release of 4.1.2 had some bugs.
flash a newer firmware, or software update your phone.
for SIII Mini, I think you need a CM. stock is too buggy and slow to use
I'd try when I will be ready to start with flashing like I did on my previous phone, till then will try to bear the bug... the only thing is that on my NFC model I'll need to flash a different country firmware (if I want to stay stock) for N, or also the non-N firmwares will work? (Obviously losing NFC capability) for what concerns CyanogenMod, I like it but I'm more like a stock-lover thank you guys
I flashed another firmware (mine is from december while newest is from july), done a factory reset and when I restored SMS with SMS Backup & Restore, when it was approximately reaching the restored messages number of a particular message (a message I sent with GO SMS Pro containing emoji coming from the go sms emoji plugin) message app has crashed and bug happened again, so I revert to my origina FW but this time I'm not restoring that SMS. Hope that will fix my bug, because I'm thinking it was a corrupted mmssms.db database file... I'll see and post what happens so everyone having my problem will probably find a solution!
Ok, just appened again, don't know what to do :crying:
Flash CM 10.1 :thumbup:
Sent from my GT-I8190 using xda app-developers app
I found that the culprit was Viber, it goes in conflict with sms databases and causes the bug (maybe because it has the permission to read and edit sms) so after uninstalling it I've never experienced the bug again... it's a little bit strange I think
[Q&A] [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13
Q&A for [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13 [EOL]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13 [EOL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I too had some problem with last R13 update:
- Contacts in SIM are no longer seen, so they can't be transferred to phone,
- Found WI-FI and mobile network turned off, may airplane mode have been set on by itself?
Now went back to R11
Brightness issue
Hello, loving the ROM so far!
Only thing I dont know how to solve is max brightness after I reboot the phone (I have set mine to minimum).
It gets back to minimum after the screen turns off or after I manually set it off.
I tried factory reset, didnt help.
Thanks for the help!
upgrade new rom
Hi,
last week i installed this version
20140910 Release 12 on my samsung galaxy s plus
followed all steps from the openings post of this thread:
http://forum.xda-developers.com/showthread.php?t=2579431
I used CWM.
My question is with steps should i take if i want to upgrade to
20141011 Release 13 [EOL]?
Thanks a lot
First you have to update TWRP to 2.8.0.0. from there you can flash R13 and reboot.
Gesendet von meinem Nexus 5 mit Tapatalk 2
Installing CM11 rel11, serial disappeared - best way to restore?
Hi folks!
I've upgraded the stock firmware to CM11 rel11 from this thread on a i9001. Now it is on EOL rel13.
By the initial upgrade I assume the serial number turned unknown, so now I am only able to make emergency calls. Until now it didn't make me upset at all, however recently my priorities have changed. (In a nutshell: VOIP telephony was kicking in, thus it would be handy to turn my GPS device a 3G and callback capable... well... phone.)
Before the upgrade operation I followed the recommendation and created a backup of /efs and /persist. Not surprisingly the backed up and current images of these partitions do differ on some bits. However at this point I became a bit confused, and teh internetz didn't answer (yet?) my questions:
- Shall I simply dd the original images back, reboot, and problem is solved? Or doing so I will brick my precious device (being even unable to restore the current state of these partitions) thus lose even navigation?
- Is there any better restore tool around that supports i9001?
- Am I totally off track, and should make some other magic? (Like using some 2013 patch that kicks out S/N check, etc.)
Thank you in advance!
Project dead?
I have tried to download R13 files. All downloads hosted by devhost failed because the files seem to be unavailable. Tested with Chrome and Dolphin on i9300 and i9001.
Can you or someone who has already downloaded the files please provide an additional mirror?
And why is R13 EOL if there is no clue of a newer Version? Have you stopped the development completely or are you preparing for Lollipop?
I have the same problem as PsychoGame
"Hello ADC-Team,
First of all thank you for all your hard work on this device, it's much appreciated.
Second I want to report a small bug which I've encountered and am unable to get past. I followed the next steps in flashing:
I flashed TWRP 2.8.0.0 on my Samsung Galaxy S Plus.
Rebooted into TWRP 2.8.0.0
Completely wiped the device (Cache, Dalvik Cache, Android Secure, SD-card, System & Data)
After full wipe installed the cm-11.0-20141011-ION-dev_connection_team-release13-ariesve.zip
After flashing CM11 installed GAPPS package
Cleared Cache and Dalvik Cache once more
Rebooted and set-up device
After the device has been set-up I'm unable to use the contacts app for some reason.
I've tried clearing Cache/Dalvik Cache and Fix Permission but this error still persists
Reflashed the CM11 package again but still no luck, the error still persists.
Does anyone have a suggestion, or is anyone also facing this same problem?
Greetings PsychoGame "
I'm unable to open my contacts, i din't have the problem with release 12. Is there a know solution?
Yes I share the same problem, as said in post 21 oct 2014 at 07:30 PM.
I can't use the contacts because they can't be read in the SIM and can't be exported to the thelepone memory.
Tried with wiping, cleaning, etc., but I had to step back to a previous release (R11) very well working.
Looking at the lenght of the files I could see that R11 is 210.888 KB, R12 is 211.708, and R13 is decreased to 189.921.
Something lost
deduud1 said:
I have the same problem as PsychoGame
"Hello ADC-Team,
First of all thank you for all your hard work on this device, it's much appreciated.
Second I want to report a small bug which I've encountered and am unable to get past. I followed the next steps in flashing:
I flashed TWRP 2.8.0.0 on my Samsung Galaxy S Plus.
Rebooted into TWRP 2.8.0.0
Completely wiped the device (Cache, Dalvik Cache, Android Secure, SD-card, System & Data)
After full wipe installed the cm-11.0-20141011-ION-dev_connection_team-release13-ariesve.zip
After flashing CM11 installed GAPPS package
Cleared Cache and Dalvik Cache once more
Rebooted and set-up device
After the device has been set-up I'm unable to use the contacts app for some reason.
I've tried clearing Cache/Dalvik Cache and Fix Permission but this error still persists
Reflashed the CM11 package again but still no luck, the error still persists.
Does anyone have a suggestion, or is anyone also facing this same problem?
Greetings PsychoGame "
I'm unable to open my contacts, i din't have the problem with release 12. Is there a know solution?
Click to expand...
Click to collapse
I don't share this. The contacts are properly downloaded from Google and I can access them normally. I can also add contacts and save them!
Edit: were did you save your contacts? If you've saved them on your sim card, I'd suggest an app called 'sim contacts'. I found out I had some very old contacts stored on the sim card! I almost forgot this possibility...
smitharro said:
I don't share this. The contacts are properly downloaded from Google and I can access them normally. I can also add contacts and save them!
Edit: were did you save your contacts? If you've saved them on your sim card, I'd suggest an app called 'sim contacts'. I found out I had some very old contacts stored on the sim card! I almost forgot this possibility...
Click to expand...
Click to collapse
I reinstalled the rom and gabs again in my pc at home and the problem is gone. I have another question I like the english language on my phone because if there is a problem and a solution it is mostly written in english. I live in the Netherlands, i tried language english us but that gave problems with reception. My provider signal (t mobile) disconected sometimes ramdomly. My solution was select english united kingdom instead of Dutch and Nederland. My question about that solution is: Is it possible that i have slighter worse reception than if i select country Netherlands and language dutch of shouldn't that change make any difrent i means of reception signal strenght?
Thanks for the fast response smitharro
deduud1 said:
I reinstalled the rom and gabs again in my pc at home and the problem is gone. I have another question I like the english language on my phone because if there is a problem and a solution it is mostly written in english. I live in the Netherlands, i tried language english us but that gave problems with reception. My provider signal (t mobile) disconected sometimes ramdomly. My solution was select english united kingdom instead of Dutch and Nederland. My question about that solution is: Is it possible that i have slighter worse reception than if i select country Netherlands and language dutch of shouldn't that change make any difrent i means of reception signal strenght?
Thanks for the fast response smitharro
Click to expand...
Click to collapse
I don't think the language settings of your interferes with the signal of your provider. I always use English with Kpn..
Hello folks,
I still am having problems with contacts from SIM.
To make short a long story:
-1-I have my contacts (216) in SIM.
-2-I must have them in SIM because sometimes I have to put SIM in other phones neither Android nor Google.
-3-That means I do not save my contacts in Google Cloud.
-4-CM11 doesn't use SIM directly (R/W), so I used to select all contacts in SIM and transfer to Phone Memory (not in Google Cloud).
-5-I could do that until R11 and R12.
-6-(Note_1 : before an update I perform a total wipe and a factory reset)
-7-Now I installed R13 with the same procedure: factory reset and instal ZIP
-8-The transfer of contacts is not possible because contacts in SIM are no longer visible,
-9-If I install R12, copy contacts to phone, then install R13 on it without erasing nothing (cache, dalvik, reset) then i can see contacts previously transferred under R12.
Note (tried as suggested by smitharro) "sim contacts" from market. It Reads and Writes contacts on SIM, but cannot transfer to Phone, I get this message "operation failure. try again".
My question is: how can I transfer contacts from SIM to phone under R13 as per step -7- and not pass via step -9-?
I may make something wrong, but do not understand what.
Help please
Many Thanks
callegan said:
Hello folks,
I still am having problems with contacts from SIM.
To make short a long story:
-1-I have my contacts (216) in SIM.
-2-I must have them in SIM because sometimes I have to put SIM in other phones neither Android nor Google.
-3-That means I do not save my contacts in Google Cloud.
-4-CM11 doesn't use SIM directly (R/W), so I used to select all contacts in SIM and transfer to Phone Memory (not in Google Cloud).
-5-I could do that until R11 and R12.
-6-(Note_1 : before an update I perform a total wipe and a factory reset)
-7-Now I installed R13 with the same procedure: factory reset and instal ZIP
-8-The transfer of contacts is not possible because contacts in SIM are no longer visible,
-9-If I install R12, copy contacts to phone, then install R13 on it without erasing nothing (cache, dalvik, reset) then i can see contacts previously transferred under R12.
Note (tried as suggested by smitharro) "sim contacts" from market. It Reads and Writes contacts on SIM, but cannot transfer to Phone, I get this message "operation failure. try again".
My question is: how can I transfer contacts from SIM to phone under R13 as per step -7- and not pass via step -9-?
I may make something wrong, but do not understand what.
Help please
Many Thanks
Click to expand...
Click to collapse
I tried to copy one of my old contacts from the Sim to the phone with 'Sim contacts'. It works perfect! The contact is visible in in 'contacts' after this operation! It isn't visible when it's only on the Sim card however... Sorry but I'm afraid I can't give you a solution for this, other than just use Android phones...
Hello people,
Thanks smitharro for the test you did with "sim contacts" with R13.
It doesn't work with me; if I try to copy with "sim contacts" (by Needom Studio), it gives me the message "Operation Failure" and stops.
BUT
Then I tried with "sim manager" (by Robotobia) and all was perfect: I could copy from Sim to Phone and from Phone to Sim.
(Info: my sim operator is WIND, memory capacity 64 KB)
I hope this could be useful for other people that might have same problems.
Hello
callegan said:
Hello people,
Thanks smitharro for the test you did with "sim contacts" with R13.
It doesn't work with me; if I try to copy with "sim contacts" (by Needom Studio), it gives me the message "Operation Failure" and stops.
BUT
Then I tried with "sim manager" (by Robotobia) and all was perfect: I could copy from Sim to Phone and from Phone to Sim.
(Info: my sim operator is WIND, memory capacity 64 KB)
I hope this could be useful for other people that might have same problems.
Hello
Click to expand...
Click to collapse
Glad it finally worked out for you! I used the Needom Studio app. That one worked fine for me. Don't know why it didn't work for you. Most important: your problem is (somewhat) solved, although it's just a workaround. The Rom still doesn't read the sim-contacts 'by itself'. For me, personally, that's not an issue. Hope the rom will be made 'perfect' before it reaches it's real EOL... On the other hand, nothing in life is absolutely perfect! remember: this rom is brought to us absolutely with no charge by people who volunteer to do this development, just because they like doing this.
Still confused
Hi again
I'm still confused, whether it is safe to dd my saved partitions back to restore my serial number. (Still not 100% sure if these partitions are bound to a particular firmware revision, e.g. only usable as a source to harverst my serial from, not to restore anything; and neither 100% sure if dd is the best tool to rewrite them.)
Having no - even a short - answer means I am asking something pretty obvious? By my opinion if it were obvious, google had answered it already - but it didn't.
Any answers appreciated.
chronosynclastic said:
Hi folks!
I've upgraded the stock firmware to CM11 rel11 from this thread on a i9001. Now it is on EOL rel13.
By the initial upgrade I assume the serial number turned unknown, so now I am only able to make emergency calls. Until now it didn't make me upset at all, however recently my priorities have changed. (In a nutshell: VOIP telephony was kicking in, thus it would be handy to turn my GPS device a 3G and callback capable... well... phone.)
Before the upgrade operation I followed the recommendation and created a backup of /efs and /persist. Not surprisingly the backed up and current images of these partitions do differ on some bits. However at this point I became a bit confused, and teh internetz didn't answer (yet?) my questions:
- Shall I simply dd the original images back, reboot, and problem is solved? Or doing so I will brick my precious device (being even unable to restore the current state of these partitions) thus lose even navigation?
- Is there any better restore tool around that supports i9001?
- Am I totally off track, and should make some other magic? (Like using some 2013 patch that kicks out S/N check, etc.)
Thank you in advance!
Click to expand...
Click to collapse
chronosynclastic said:
Hi again
I'm still confused, whether it is safe to dd my saved partitions back to restore my serial number. (Still not 100% sure if these partitions are bound to a particular firmware revision, e.g. only usable as a source to harverst my serial from, not to restore anything; and neither 100% sure if dd is the best tool to rewrite them.)
Having no - even a short - answer means I am asking something pretty obvious? By my opinion if it were obvious, google had answered it already - but it didn't.
Any answers appreciated.
Click to expand...
Click to collapse
First of all, your question is not fully clear to me. What doe you mean by serial number? You're IMEI number? If you've lost that, your phone is nothing more than a small tablet. This is a unique number to identify your phone on the provider's network. So you'll have to restore the backup!
The serial number in my phone however is 'unknown' in the rom. But the rom works fine! There's no need to have that for the use of this phone. I don't know where it was stored in the original rom, but be very careful with messing with the 'EFS' partition!
Thank you for your reply!
My IMEI number remained well, however I learned that both IMEI and serial (S/N) is needed to have a phone (e.g. to connect to carrier) instead of having a tablet.
For example here is said: "IMEI is showing now but still no calls and sms. I also noticed that the serial number is not the same as the one written at the back of the phone. I have read that restoring EFS solves this problem".
There is also some magic ("azira patch") to S3 that states the same. It operates by bypassing serial check, but since it is old (2013) and originally for S3, I'd rather stuck restoring my /efs partition.
Backing up /efs is written down everywhere. Restoring it... well. Mostly external tools are mentioned, that don't support i9001.
Even further, suppose restoring /efs and /persist is the solution for my problem, I think I know how to do that. At least by dd. What I don't know is that the structure of these partitions is fix or may change between Android versions. And of course: if I rewrite them to original, will my device boot again?
Considering these, any idea if I'm off track, or not?
smitharro said:
First of all, your question is not fully clear to me. What doe you mean by serial number? You're IMEI number? If you've lost that, your phone is nothing more than a small tablet. This is a unique number to identify your phone on the provider's network. So you'll have to restore the backup!
The serial number in my phone however is 'unknown' in the rom. But the rom works fine! There's no need to have that for the use of this phone. I don't know where it was stored in the original rom, but be very careful with messing with the 'EFS' partition!
Click to expand...
Click to collapse
I never touched my /efs partition nor will I ever! My phone is running fine without the serial number displaying in the rom! I can make phone calls, send text messages and I have mobile data! So you really don't have to restore the serial number. Possibly it's still there and still used by the provider, but is the settings app simply not reading it... Sorry I can't help you more. I'm not a developer, just a user...
Hello Everyone...
Posting here first rather than in the "Update Failure" thread because I'm not so sure I have a "failure" with the update....just an issue after the udpate.
I have 2 cloned HTC M9 phones. I say "cloned" as they are exactly the same make, model, ROM, etc (one business, one personal phone). They have the following information if needed:
Sprint HTC M9
SuperSU Free v2.65
Custom ROM ViperOneM9 3.5.0 with no custom kernal
Android 5.1
HTC Sense 7.0
Kernal (standard) 3.10.49-perf-g26c593c
[email protected] #1
SMP PREEMPT
I updated some apps this as I normally do through Google Play. A little while afterward I was prompted to update the SU Binary. I did so on one of my phones. I hit the TWRP option (on the right side of the prompt screen), nothing happened, phone did not reset so I rebooted into recovery. The update ran automatically and the phone rebooted.
I noticed two issues (perhaps there are more). The huge problem is that I cannot make OUTGOING calls. I use a custom dialer PixelPhone Pro. I click on a contact to dial and nothing happens. I type in number to dial, hit the green "send" button to make the call, nothing happens.
I also tried the stock Phone app....same thing, cannot dial out.
I attempted to update the Profile and PRL for the phone, however, as that appears to need to make a "special call" that function is not working either
The other problem I noticed is with an app I have called Quick Settings. The app is always accessible through the pull-down notifications on the phone. Although the app is still installed and functional, it no longer appears in the pull-down notifications. I tried to reset the option to show it there (turning the option off and back on) and it will not show up despite the proper setting chosen.
I still have full root access as I tried a couple root apps (such as Titanium Pro) and have full root access.
I have been prompted on my other phone to update the SU Binary and I am concerned with doing so. Any idea why this is happening and how I can troubleshoot and fit my outgoing call issue??
THANK YOU all very much!!
Scott
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Scudderb said:
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Click to expand...
Click to collapse
**UPDATE**
Still problems....
Right after I first updated the binary the "only" problem was that I could not make calls which I could use the other functions of the phone. I rebooted the phone and I cannot reach any function of the phone because I constantly get the message "...the process com.android.phone has stopped" obviously related to the previous problems.
I dirty-flashed the ROM...that did no help. I even tried to flash an older SuperSU version (I don't know what that would have done....I'm running on HOPE now ) and that didn't help. Re-dirty-flashed the ROM a second time. Again that didn't help.
I flashed an old backup and THAT WORKED fine. Problem is that the backup is 6 months old. I could quit and totally clean/wipe/install the ROM and start again from scratch but I reeeeeeallly don't have time for that at the moment.
Is there ANY way I can simply get my com.android.phone process back?? Why did all this happen in the first place??
ANY help is greatly appreciated!! THANK YOU!!!