Develop Bugs

[Q] 3G connection with ProjectAndroid2.2Froyo.112210

Hi,
I am new and just installed Android ProjectAndroid2.2Froyo.112210 on my HTC Touch Pro 2 phone. Once I had the 3G connection with the Dutch KPN working but after a reboot of the phone, I can not manage to get it working again. Wifi and BT are ok except the 3G connection.
Did a 'to default reset' and tried several APN setting but none of them turn the 3G connection back to live.
Does anyone have a solution?
Thanks in advance,
Rick.

Does the cell radio function? In other words, can you make/receive calls/texts?
If yes, then the APN settings are a good thing to look at - also, do you have a 3g icon with up/down arrows next to the signal strength meter?
One other good question to ask - does your provider require a proxy to access the 'net?

Yes, I can call and recieve calls. Also sms messages are working fine.
The only thing which is missing is the G3 data connection icon and actually the datalink.
No, the provider does not need a proxy setting. As I wrote in my start, I had it working good but just after a reboot without any changes on the APN parameters, it didnt come back again.
Thanks for your reply Arrrghhh!

slimmehenkie said:
Yes, I can call and recieve calls. Also sms messages are working fine.
The only thing which is missing is the G3 data connection icon and actually the datalink.
No, the provider does not need a proxy setting. As I wrote in my start, I had it working good but just after a reboot without any changes on the APN parameters, it didnt come back again.
Thanks for your reply Arrrghhh!
Click to expand...
Click to collapse
Hrm. May want to try with a new/fresh data.img. If you rename your existing data.img, a new one will be created during boot. See if it helps... unfortunately deleting that file has fixed so many odd issues, it's not even remotely funny.

Okay, I will give it a go when comming back from my trip next week.
I did remove all files a couple of times and re-installing the Android software but maybe not all data has been removed? At least it did not solve the problem.
By the way, could it be caused by having the system on the SD card rather than in the phone memory? And could it be related to the type of phone selected during boot time? I am using the HTC Touch Pro 2 and not selecting the Tilt-2 but the ?210 (forgot the name and the phone is off) due to the fact that the keyboard is wrong with the tilt-2 option.

slimmehenkie said:
Okay, I will give it a go when comming back from my trip next week.
I did remove all files a couple of times and re-installing the Android software but maybe not all data has been removed? At least it did not solve the problem.
By the way, could it be caused by having the system on the SD card rather than in the phone memory? And could it be related to the type of phone selected during boot time? I am using the HTC Touch Pro 2 and not selecting the Tilt-2 but the ?210 (forgot the name and the phone is off) due to the fact that the keyboard is wrong with the tilt-2 option.
Click to expand...
Click to collapse
Ehm, you can wipe your SD card all the times you want, but this won't solve anything if the APN is wrong or if your carrier requires user/pass, proxy or whatever else.
So first go check you actual APN configuration in WinMo, get a paper, copy it down piece by piece, then get back to Xdandroid and modify/create a new one, checking all the settings are properly set.
Have a nice trip.

@Wind,
your right but again, it has been working with a certain set of parameters but just after a reboot without any change on APN, the phone did not want to reconnect on 3G.
Thanks for your wishes. Will get back when I return.

do not use this version modules-2.6.27.46-01232-gb7033df.tar.gz , zImage-2.6.27.46-01232-gb7033df, change it.

@muziling,
I did update the phone with your advised release and re-started the phone again. No result. Due to low battery the phone went down and had to re-charge. When the battery was full again, turned on the phone and guess what, I had a 3G icon.
Just to be sure that it was not a lucky shot (but I was thinking it) I decided to reboot the phone again and ships.... the 3G icon did not show up again.
No change inwhatever parameter was made during the reboot session. This means that the 3G performance is intermittend and depeding on a certain condition which I do not know how to find. Any suggestions?
Thanks in advance.

I have a similar problem. After a fresh install, the 3G connection works exactly the first time, I boot into android. After a reboot, the 3G connection mostly does not work. I cannot figure out, which conditions have to be met, to get 3G working. Its just pure luck to me.
btw, I have a german rhodium.

try this version, it works perfect on my rhod400
neopeek.com/forum/Android-ROMs/1553-Barebone-CyanogenMod61-Minimum-System-22-11-2010

[Q] Desire z slow at messaging

Hi
I have a problem with a Desire Z. Alot of times when I try to send a message (SMS) it takes forever (5min) before it gets sent. If I hit the home-button while watching/waiting for the message to be sent, it's put in drafts instead of keep trying to send.
It's also slow at recivieving messages. Tested with a couple of other phones and compared.
Does anyone else have a simular issue? The sim-card has been used for years with other phones without troubles.

Try using a different messaging app (i.e. handcent)

kjeksomanen said:
have a problem with a Desire Z. Alot of times when I try to send a message (SMS) it takes forever (5min) before it gets sent. If I hit the home-button while watching/waiting for the message to be sent, it's put in drafts instead of keep trying to send.
Click to expand...
Click to collapse
Same problem for me. Hoping the new OTA solve this problem.
Tap on "send", put the phone away, look at the phone after an hour, somethimes the sms is still "sending" !

I only get this if I have no or very bad signal, i.e. it will wait till it's got a signal to send it.
I wonder if it's worthwhile for you guys to do a factory reset or re-flash the ROM ?

Only thing I can think of is using the "delete old messages" function after deleting all your messages. other than that, I'd try wiping cache and dalvik cache (assuming you are rooted). Re-flashing the ROM should be a last resort (assuming that you even have a custom ROM installed).

omarsalmin said:
Try using a different messaging app (i.e. handcent)
Click to expand...
Click to collapse
Thanks that's a good tip, I'll def try it and report back!
steviewevie said:
I only get this if I have no or very bad signal, i.e. it will wait till it's got a signal to send it.
I wonder if it's worthwhile for you guys to do a factory reset or re-flash the ROM ?
Click to expand...
Click to collapse
This isn't relevant for my problem since it's always good strength + when I tested the slow recivieving the other phones was in the same room, with no problems
lordevol said:
Same problem for me. Hoping the new OTA solve this problem.
Tap on "send", put the phone away, look at the phone after an hour, somethimes the sms is still "sending" !
Click to expand...
Click to collapse
Sorry but what does OTA stand for? If you're talking about the recent update, I sure do to!
Nissan350 said:
Only thing I can think of is using the "delete old messages" function after deleting all your messages. other than that, I'd try wiping cache and dalvik cache (assuming you are rooted). Re-flashing the ROM should be a last resort (assuming that you even have a custom ROM installed).
Click to expand...
Click to collapse
So it's possible it's so slow at sending since it has alot of messages in the inbox? It might be the case, but even so it's lame if that's the reason, it's far more powerfull than just handling some textfiles
--------
Thanks for all your answers, will test'em out as soon as I can!

kjeksomanen said:
So it's possible it's so slow at sending since it has alot of messages in the inbox? It might be the case, but even so it's lame if that's the reason, it's far more powerfull than just handling some textfiles
Click to expand...
Click to collapse
Haha I agree with you on that, mine has messages in it from weeks and weeks ago. the only reason i said that is because when I was with sprint, I had a HERO (i know, they arent even close to the same spec-wise) and it acted the same way your G2 is acting now. I fixed it by doing what I recommended. worth a try

A little nomenclature for you...
OTA - Over The Air update. It's an update that HTC or your service provider pushes to your phone when it does a check-in, if it is more current than the version your phone is running. Basically it's a software patch for the system software located in your phone.
Seeing that you don't know what an OTA is yet, I can deduce that a rooted phone definitely isn't your problem. I think you should check your phone for updates (Settings -> About phone -> System updates -> Check for updates) and see if anything pops up after you hit okay.
If you find an OTA and the problem still persists, you may find a new SIM card would be an ideal option. Let me explain myself here:
When Cingular made the switch to AT&T I was still using a Cingular labeled SIM card. It worked fine until AT&T switched to 3G. When I got a 3G phone, I found that I couldn't get 3G no matter what I tried, because for some reason the SIM spec didn't support 3G. So I had to switch my SIM to get 3G. I've found that with each new spec that comes out, often times the best way to go is just to switch the SIM out each time you get a new phone. Might take a few minutes longer getting your contract up, but new SIMs seem to be sent out to our store (which is a AT&T/T-Mobile vendor) every time a new network spec is introduced by the carriers. I'm not entirely convinced that this is just a strange "coincidence".

deliberate187 said:
A little nomenclature for you...
OTA - Over The Air update. It's an update that HTC or your service provider pushes to your phone when it does a check-in, if it is more current than the version your phone is running. Basically it's a software patch for the system software located in your phone.
Seeing that you don't know what an OTA is yet, I can deduce that a rooted phone definitely isn't your problem. I think you should check your phone for updates (Settings -> About phone -> System updates -> Check for updates) and see if anything pops up after you hit okay.
Click to expand...
Click to collapse
Hehe thank you, but I do indeed know what rooting is etc., but the phone we're talking about isn't rooted so it's not the problem.
Just because I haven't bumped into the word OTA doesn't mean I don't know how the updatesystem from HTC works
And yes, it's the latest version, just got a update ticking in, dunno if it fixed the problem yet.
deliberate187 said:
If you find an OTA and the problem still persists, you may find a new SIM card would be an ideal option. Let me explain myself here:
When Cingular made the switch to AT&T I was still using a Cingular labeled SIM card. It worked fine until AT&T switched to 3G. When I got a 3G phone, I found that I couldn't get 3G no matter what I tried, because for some reason the SIM spec didn't support 3G. So I had to switch my SIM to get 3G. I've found that with each new spec that comes out, often times the best way to go is just to switch the SIM out each time you get a new phone. Might take a few minutes longer getting your contract up, but new SIMs seem to be sent out to our store (which is a AT&T/T-Mobile vendor) every time a new network spec is introduced by the carriers. I'm not entirely convinced that this is just a strange "coincidence".
Click to expand...
Click to collapse
Thank for your tip, I'll check it out although the sim was used on another phone which also supported 3G afaik.

kjeksomanen said:
just got a update ticking in, dunno if it fixed the problem yet.
Click to expand...
Click to collapse
The recent update solved the problem (for my Desire z),
it was an HTC bug

Sorry for the late answer, but one day the mobile just decided to empty it's inbox for whatever unknown reason, and well, that solved the problem.
But thanks for all the answers, once again

the htc sense messaging app is horrible. the dates and times are wrong and it is like a pig. openeing, sending, reading are all slow.
install the vanilla android messaging app as shown here then you dont have to install third party
http://forum.xda-developers.com/showthread.php?t=846231&page=12

[Q] HTC ONE X phone number unreadable after upgrade to 4.2.2

Hi everyone,
I seem to be facing a problem that I haven't found discussed here with my phone.
Following a successful upgrade to Slimbean 4.2.2 build 6 OFFICIAL, everything seems to be working correctly with my Tmobile UK SIM card and I can make or receive calls and texts, I can read the IMEI reference but for some reason my phone number is not displayed anymore in the "about phone" section in Settings or if I use an app like "SIM Card" to read the details of the SIM. I get instead the message "unknown number"
I am not sure if this is a problem or not, so I would like to know if anyone can think of any potential limitation due to this issue.
On top of this, I am about to move abroad and was going to request a code from Tmobile to unlock the phone as I assumed the phone was locked to their network, but when I tried a THREE SIM card, the card was actually accepted and I connected to that network but again the phone number is not displayed in the settings section...
Has anybody seen or heard a similar issue?
I installed a fresh Slimbean ROM from scratch as I was previously running a completely different ROM and I assume it was successful as everything seems to be working.
The only issues I could find in the forum were related to not being able to retrieve the IMEI number after the upgrade, but nothing about the phone number itself.
I would be very grateful if anyone could offer any help or suggestion.
Thank you in advance.
David.

I have noticed the same thing on the official CM 10.1 builds (with both Three UK and giffgaff SIMs), I suspect it is an issue but it's not a real bother to me all it means that any app that auto detects your phone number (eg hangouts) will just ask for it during initial setup instead.
Again the same for the IMEI sometimes this doesn't show up but it does most of the time.

hydo1 said:
I have noticed the same thing on the official CM 10.1 builds (with both Three UK and giffgaff SIMs), I suspect it is an issue but it's not a real bother to me all it means that any app that auto detects your phone number (eg hangouts) will just ask for it during initial setup instead.
Again the same for the IMEI sometimes this doesn't show up but it does most of the time.
Click to expand...
Click to collapse
Thanks Hydo1,
I have found a couple of things yesterday.
First, I have been able to add the number manually through the settings menu in the dial pad and it now shows in the "about" section.
Second, I have found out that although my voicemail is setup and active when I call the Tmobile services, it doesn't actually work anymore and I can only guess it is due to this issue as it was working before...
I'll try again once I have switched to a new network abroad...

[Q] How to change locked APN?

I've have recently upgraded to HTC One M8 and as such transferred my number over to a new micro sim.
The transfer was from a micro Tmobile sim to a Nano Tmobile sim (UK) - this was done in store.
Problem - only some apps recognise the WCDMA (3G) connection as a legitimate connection. Google Play Store, Spotify, Google Now, Google Now Voice and a few others will not connect to internet reporting back a "no connection" error or timing out.
Other streaming apps such as youtube, vimeo, vevo, facebook all work fine.
I have tried:
WCDMA Only - no effect on problem.
GSM Only - all apps work.
WCDMA GSM Auto - no effect.on problem.
:good: I have also bought a 3 UK pay as you go sim - this works perfectly with no errors. :good:
The conclusion im coming to is I may have some issues with the APN settings for Tmobile UK (which in reality is EE-Everywhere) - however on the HTC One M8 the APN settings are locked, they can not be edited. I can add a new APN connection but it can not be selected.
Does anyone know how to unlock the APN options. I have tried Tweakker APN from Google Play but this has no effect.
Any guidance would be appreciated.

Never heard of locked apns,though the first thing I did was flash a custom Rom, maybe that's your answer? Get viper rom on there and never look back!
XDA app on m8 running venom

samsamuel said:
Never heard of locked apns,though the first thing I did was flash a custom Rom, maybe that's your answer? Get viper rom on there and never look back!
XDA app on m8 running venom
Click to expand...
Click to collapse
Custom rom is on the list, as last resort, in-case I have to send phone back. Trying to ascertain if its the sim thats locking the APN, if I put in different networks sim card the APN is not locked.

Have you selected the correct network operator first in network settings ?

ashyx said:
Have you selected the correct network operator first in network settings ?
Click to expand...
Click to collapse
Yep definately.

The apns are stored in an xml file in the rom, the rom identifies the sim and finds the corresponding apn info. There is a reasonably easy way around this: decrypt your framework-res.apk and change the apns.xml file and then reencrypt the file and push it back to the phone. There is a guide somewhere on xda that covers it in detail.

lampel said:
The apns are stored in an xml file in the rom, the rom identifies the sim and finds the corresponding apn info. There is a reasonably easy way around this: decrypt your framework-res.apk and change the apns.xml file and then reencrypt the file and push it back to the phone. There is a guide somewhere on xda that covers it in detail.
Click to expand...
Click to collapse
Update: I've rooted and installed several Roms (Viper, InsertCoin). The Viper rom allowed me to change the APN settings. This had no effect on the issue.
So I've accertained:
1. Its not the phones hardware as other networks sims work perfectly.
2. Its not the APN settings - I have managed to change them they have no effect.
3. It is not Sense 6.0 as I have tried Google Play Edition Rom.
4. It is not my Tmobile account - I have spoke to them several times on the phone.
Leading me to the conclusion it must be the new nano sim and the way its communicating with phone. I have bought a nano sim adapter to that I can try it in my old phone to see if this is the case.
As a side note - i had a bizarre conversation with HTC support, the guy tried to convince me my "Google Account was corrupted" and this was causing the issue. I said to him this is not a real thing and he is talking out of his backside. It also doesn't explain why I can't connect to spotify. But I humored him and signed in with a fresh google account - no difference. Just for my piece of mind - is there any such thing as a corrupted google account?

UPDATE
After much searching around I found an article indicating that Google play and Google play services may have a bug when your data and time is set to automatic.
I switched the date and time to manual and the play store, Google now, search all started working for the first time.
Does anyone know why date and time would be an issue?

M8 can't receive calls, flashed wrong ROM? (4G problem)

Yesterday I flashed my AT&T HTC M8 to a custom ROM (Wolla) because my phone was really laggy after the Lollipop update, and I noticed that although I am still able to make calls, I cannot receive calls anymore. I am wondering if it is possible that I messed up a step somewhere (especially step 3), or if I flashed my phone with the wrong ROM?
I also looked around on XDA more, and realized a few people also had this problem, and it was resolved by turning 4G data off. Apparently this is a problem with AT&T activating Voice over LTE, and the custom ROM not supporting/compatible. Is there a suggested fix to this problem (eg. flash back to the RUU on HTC's site)?
Here are the instructions that I followed to flash the new ROM:
Unlocked my phone via the HTCDev website
Installed TWRP
(Here is where I think the problem occured). I downloaded the Wolla Marshmallow ROM from the XDA thread, and took the boot.img image from the .zip into my fastboot folder.
Then in fastboot, I typed in "fastboot flash boot boot.img", then "fastboot reboot" to reboot my phone.
HOWEVER, my phone would be stuck in white Android booting screen, and wouldn't move for around 10 minutes, so I thought it was stuck.
I redid step 4 a few times, but the same thing always occured.
Finally, I decided to take the boot.img file from an RUU from HTC's website, and use that instead of the boot.img from the Wolla .zip file.
Now my phone boots, and everything seemed to work.
The only issue is that although I can make phone calls, I cannot seem to receive phone calls. It doesn't "ring" on the caller's end, and goes to voicemail in the end.
Does anyone have any experience with this?
My phone is an HTC One M8 bought from AT&T, unlocked about a year ago.

You're on the right track (AT&T's deployment of VoLTE is the problem), and there is one more suggestion I can make: call AT&T and have HD Voice (their branding of VoLTE) turned off for your account. Details here: http://forum.xda-developers.com/showpost.php?p=62001970&postcount=28
Not a true "fix" as obviously, you will not have VoLTE if you do this. But its not a bad compromise, IMO. Not may folks are going to miss VoLTE, and at least the above workaround will allow you to use the custom ROM you want, and have LTE data.
Your other option, is to use an AT&T-based ROM. But who the heck wants that?

I think I'll hit up AT&T chat support today to turn it off, thanks!
I'm sure there are a lot of other AT&T users using custom ROMs on the HTC M8 on this forum. Are all these people getting this problem too, or are they using a special ROM that doesn't run into this issue?
Edit: I'm also a little worried if this problem might occur on other 4G networks internationally? I tend to go abroad once or twice every year, and have a SIM card for the other countries I go to. Is this an AT&T specific issue, or would I run into this problem for every country that also uses HD Voice?

Kwkevinlin said:
I think I'll hit up AT&T chat support today to turn it off, thanks!
Click to expand...
Click to collapse
Note that the base level customer service probably can't turn off HD Voice (won't know what you are talking about, or even wrongly claim it can't be done). Ask to talk to a Tier 2 (or some such term) tech support.
Kwkevinlin said:
I'm sure there are a lot of other AT&T users using custom ROMs on the HTC M8 on this forum. Are all these people getting this problem too, or are they using a special ROM that doesn't run into this issue?
Click to expand...
Click to collapse
If you click on the full thread, for which my previous linked post is from, you'll see that there are a good number of folks that had the same issue. And that is just on that one thread, there have been others (like this one of yours).
Plus, there are other variables that will effect whether AT&T users (on "international" based ROMs) will see this issue or not, such as whether HD Voice has been deployed in their market or not (heck, lots of places don't even have LTE yet, much less HD Voice), or whether the HD Voice feature was ever turned on for their account.
Personally, I have yet to see this problem, despite being on several different non-ATT ROMs and frequently travelling to various US regions. So I'm guessing in my case, HD Voice was never activated on my account.
Kwkevinlin said:
Edit: [/B]I'm also a little worried if this problem might occur on other 4G networks internationally? I tend to go abroad once or twice every year, and have a SIM card for the other countries I go to. Is this an AT&T specific issue, or would I run into this problem for every country that also uses HD Voice?
Click to expand...
Click to collapse
From what I can gather, this is entirely an AT&T issue. Although nothing is a sure bet when travelling international, I'm sure you probably already well know if you travel abroad occasionally. In particular, LTE implementations seems a lot less standardized from one country to another than 3G or 2G. But falling back to 3G is not a bad option, if you end up needed to. Really, unless you are streaming video a lot, or downloading huge files, 3G is really all you'll need most of the time.

So I think I found might have accidentally found a way to deal with this problem without calling AT&T.
On my stock ROM, I turned of the VoLTE (HD calls or whatever) options under data connections.
Made a few calls to myself to made sure that it was dropping to 3G (ect...) when I called it.
Afterwards I flashed a custom ROM (the new sense 8 rom by sundream) and my phone could still receive calls as it dropped it for 3G.
While you don't have VoLTE you could avoid the hassle of calling AT&T.