Hello everyone,
I flashed to Pheonix 4.1 last night from 3.0, previously 2.5. I had 4.03 on only for a few days and then Adam released 4.1 so I made the jump to it [image attached]. The trouble I am having with the lastest build is that email no longer functions properly. I have 2 pop accounts and one Exchange account configured and none will allow me to compose a new email message. I can touch the "compose" button but a new message window never appears. I also cannot reply or forward any email I have received, and yes all account do receive mail properly [image attached].
When attempting to reply or forward, I feel the haptic feedback buzz, a pause for about 2-3 seconds, then a force close [image attached].
Anyone have a thought what may have gone wrong for this to happen?
I'm having a very similar issue with email on Paragon v 3.0....All the email meesages in my inbox appear blank, and the program is very buggy overall....so obviously not useable. I would love to know if there is a fix of some sort, because I love the ROM
you could always pull the email.apk from a different ROM that worked, and place it in the system/app folder on the phone. see if that helps...
I'll give that a try.
Flashed Pheonix 4.1, it's fast but email isn't working - SOLVED!
I checked the file details and the Email.apk was the same back to the 3.0 ROM, maybe even futher but I didn't check beyond that. In stead of replacing it with the exact same data, I decided to remove one of my POP accounts and add it back manually because they had been restored via Titanium Backup. This step corrected the issue so there must have been some form of corruption in a config file from the restore. Good news is, this problem is resolved for me. Now I am looking into an unstable bluetooth connection to my car radio....
CaptiMod said:
I checked the file details and the Email.apk was the same back to the 3.0 ROM, maybe even futher but I didn't check beyond that. In stead of replacing it with the exact same data, I decided to remove one of my POP accounts and add it back manually because they had been restored via Titanium Backup. This step corrected the issue so there must have been some form of corruption in a config file from the restore. Good news is, this problem is resolved for me. Now I am looking into an unstable bluetooth connection to my car radio....
Click to expand...
Click to collapse
hmmmm any ideas if you don't have a titanium backup from the pre-ROM period? I just have a nandroid backup
Sorry, but I didn't work with nandriod backup. I rooted and went straight to a TiBu solution.
anyone experiencing this problem? I'm getting A LOT of crashes.
I'm not using any task killers what so ever.
Rooted or not rooted? Stock ROM? Custom ROM? Under what conditions does it crash?
Stock ROM and I have no idea what the circumstances are, it seems sporadic.
Hmm. Are you rooted? You could try fixing the permissions using the ROM Manager app if so. If not, perhaps a re-flashing of the RUU might be in order to fix it.
Hi!
I am having the same problem. My Acer Liquid E keeps crashing. It is reproduceable: when I log on the network the first call I receive is without problem, when I receive the second call com.android.phone crashes and the network is dropped (input SIM key). Then I can again receive one call without problem.
My phone is rooted (z4root) and I use Titanium Backup. I can solve the problem by resetting to factory settings. But it keeps coming again after a couple of days. Of course I would like to know what causes this but at first I would be very happy to know how to get rid of the problem when it is there ... Titanium is not so helpful:
When I restore the Titanium backups:
-I first restored my user applications plus settings without problems, after this everything still works
-Then I restored some of the green marked backups in Titanium Backup. After this the phone starts to have this problem again.
Does anybody know which backup this might be? I mean: solving the problem itsself would be great but at first it would be nice to be able to get the phone working quicker than factory reset. Maybe this could be achieved by resetting to an old backup with Titanium Backup (just need to know which one ...)
Help would be appreciated! Been browsing the net a long time and could find lots of ideas how to solve this but none worked so far.
My system settings:
-Acer Liquid E
-FroYo from the start (updated from .8 to .14 when I first had the problem)
-removed some apps from the rom - but nothing essential and I know that non-essential sounding things like maps or talk are actually essential. I removed things like twitter, roadsync, etc.
Daniel
daniu, unfortunately it's unlikely anyone here will be able to help you as you have a completely different phone. This forum is only for the HTC Incredible S.
Hi!
I know ... but I am not really sure this is a problem of my specific phone. I read a lot about this kind of problems for many different phones. Mine is not really that common - but I think I will crosspost - thanks for the hint
Daniel
Actually this is also happened to my IS, running ARHD 1.1.5 with latest radio.
I notice this bug after i flashed my radio to non-stock radio.
I haven't try to revert back to the original radio, and the bug remains mystery.
com.android.phone FCs can be caused by incompatible older version sim cards. Try consulting a retail store of your carrier to check if there's a need to upgrade your sim card.
Sent from my HTC Incredible S using XDA Premium App
Hi!
I read about the old SIM-Card idea but I doubt it in my case cause the problem can be reinstalled with Titanium ...
EDIT: this link may be interesting for this problem.
Regards Daniel
I have had the same prob on virgin AU stock rom. Did factory reset and kept getting the same problem. Sent the phone back and they replaced it. Getting the same FC after about a month on the new phone :/
Hi!
I don't think that this is a hardware problem. That's why I think you can send your phone as often as you want. They cannot give you other software than the one you can get yourself ...
regards
Daniel
I flashed my phone HTC one to page using DFS and I pretty much just copied everything from the donor but everything works but I just cant make outgoing calls. I get a message telling me that there was an Error and i should turn my phone off then back on. Do you have any idea of what went wrong ? I tried changing prls and radios and restarting the whole flashing back to zero and even resting the phone back to zero with the RTN menu. i flashed this phone the same way to Verizon and worked fine but outgoing calls not working. Anyone have an idea what could be the problem ?
Wipe everything and flash again – dont forget to backup user apps
android_smiley said:
Wipe everything and flash again – dont forget to backup user apps
Click to expand...
Click to collapse
Did that Already, I even used ##RTN# just so it can really wipe it all back to stock
pimix2009 said:
Did that Already, I even used ##RTN# just so it can really wipe it all back to stock
Click to expand...
Click to collapse
Well... thats weird ...
Hello
Make sure you have the correct ESN in the phone. Also make sure your phone number is attached to that ESN.
[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...