Advanced Calling FIX (HD Calling, Video Calling, and Wi-Fi Calling) - Verizon Galaxy S 5 Android Development

***This is originally a fix for the N910V but may work on other devices***
This is intended for those of you having issues enabling your Advanced Calling features. Whether it is not turning on, or its saying that it is enabled but you still can't use the features I am going to give you the steps I took to get mine up and running successfully. Head over to the original thread for more details.
http://forum.xda-developers.com/note-4-verizon/general/advanced-calling-fix-hd-calling-video-t3524339

Is this going to work for people on ROMs like rooted PJ2 as opposed to having to revert back to stock to enable HD calling and switch back? I am already on rooted PJ2 and only slightly would like these features to work -- enough to follow the procedure reference above by the OP but not enough to follow the more time-intensive / stock route.
EDIT: Tried the OP's procedure on my rooted PJ2 and it seems to work for enabling Wi-Fi calling (no clue if HD voice is really working). Jury is still out if there are issues that relate to this or the features I enabled (like excess battery usage or calling issues). PJ2 has been great on the battery but after doing this procedure, my phone was running hot and draining the battery, but has calmed down now so we'll see. Also for some reason that might not be related to this, I called someone from my Truecaller app and instead of dialing them, it briefly showed the dialing screen and kicked me back to the app. Since then it has worked as expected and dialed the person immediately. May be related to HD calling as opposed to the new APN or maybe just related to the Truecaller app or something else. We shall see. Still cool to have the features enabled without needing to revert back to stock. Thanks!

drewcu said:
Is this going to work for people on ROMs like rooted PJ2 as opposed to having to revert back to stock to enable HD calling and switch back? I am already on rooted PJ2 and only slightly would like these features to work -- enough to follow the procedure reference above by the OP but not enough to follow the more time-intensive / stock route.
EDIT: Tried the OP's procedure on my rooted PJ2 and it seems to work for enabling Wi-Fi calling (no clue if HD voice is really working). Jury is still out if there are issues that relate to this or the features I enabled (like excess battery usage or calling issues). PJ2 has been great on the battery but after doing this procedure, my phone was running hot and draining the battery, but has calmed down now so we'll see. Also for some reason that might not be related to this, I called someone from my Truecaller app and instead of dialing them, it briefly showed the dialing screen and kicked me back to the app. Since then it has worked as expected and dialed the person immediately. May be related to HD calling as opposed to the new APN or maybe just related to the Truecaller app or something else. We shall see. Still cool to have the features enabled without needing to revert back to stock. Thanks!
Click to expand...
Click to collapse
Well overall I'm glad it worked out for you. Period. However I don't see changing APN's being the reason to some of the issues you're having... But I'm not saying throw it out completely.
I would say to just monitor it over the next few days and make sure everything smooths out and you have the advanced calling features still working. Maybe after a while peak back in and check in with us to give an update on how it's treating you. Thanks for sharing!

Related

YouMail Sleep issues

I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
crunchybutternut said:
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
Click to expand...
Click to collapse
I stopped using the app because of this. I tried contacting support and was brushed off. I love the app but not the lack letting my phone sleep.
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
crunchybutternut said:
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
Click to expand...
Click to collapse
That would be great. Thanks for helping him out with this as I would love to use the app.
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Kcarpenter said:
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Click to expand...
Click to collapse
YouMail http://www.youmail.com/home/index.do is a service that replaces Sprint's (or any other provider) voice mail service with their own. It allows you to set custom "smart" greetings for each caller in your contacts, among other things. Check out the site for more info.
Here is the latest response from the developer I have been working with.
Hi [Name],
I did some more research and can confirm that I see the same behavior as you when I run the YouMail app ('active' @ 100%)
I'm not exactly sure what the cause is, as the application is indeed going to sleep when it has nothing to do. The problem also seems to be quite widespread, affecting what seems to be "most" applications that loiter around in the background doing nothing for most of the time.
Since you use 'Spare Parts' you should notice that in there is a way of viewing the 'Partial Wake Lock' usage of a given application. According to the Android developer documentation this is the ONLY way an application can keep the phone "awake" other than 'prodding' it every 30 seconds or so (and you'd notice that 'coz the screen would never go off).
As long as that "Partial Wake Lock" value is low (and it should be unless you're constantly hitting "Menu -> Poll") it means the application is indeed behaving correctly.
All I can offer is that we develop a new feature into the app so that you can tell it to automatically exit when all of the automatic polling settings are disabled - that way the phone would literally shut down the app "sometime" after you back out of the message list. Do you think that's worth it? Or should we wait for HTC/T-Mobile to fix the root cause of the problem?
Doug
Click to expand...
Click to collapse
And my response:
Do you mind if I share some of our conversation with a community forum? It might help get others involved and more feedback for you to use in further development.
As far as other apps loitering in the background, my understanding is that Android (using the same process as other Linux distros) keeps recently used applications in RAM to make them more quickly accessible to the user, and will clear them as the RAM is needed by other apps.
I have seen this issue in the past with other apps (i.e. the HTC messaging app locking the dialer and maintaining 100% awake time) but has all been resolved by updates to the apps themselves.
Click to expand...
Click to collapse
Lastly, his response:
Feel free, I don't think I said anything bad
I we get enough requests from "the community" I'll be given time to add the 'exit when done' option (basically it'll become a "dumb" app that only checks for messages when you start it up instead of waking up every so often to check [like after you miss a call])
And yes, Android is a little stranger than normal in that it tends to leave applications running for an unspecified time after you "close" them. (basically until it needs to run something else, or it runs out of memory, or .....)
The YouMail app is a little different in that it runs as a background service and schedules the phone to wake it up whenever "events of interest" occur (you get a TXT, your phone rings, it needs to poll, etc) - so even if the OS does close the app because you logged onto "hugebitmaps.com" and the phone ran out of memory, it'll start it up again as soon as it can.
I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something
Doug
Click to expand...
Click to collapse
I can post more of the conversation history if it would help. Anyone have any ideas what might be causing this beyond coding issues?
If anyone wants to send their YouMail log for inspection just enter this code in the dialer *#*#963867#*#* (*#*#YMDUMP#*#*) and it will let you send an email with the log's text.
Tried in 2.1 beta
"I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something "
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Hi, Doug from YouMail here.
Just noticed my words and thought I'd give an update - although not much good news.
I basically spent the last 2 days completely reworking the YouMail app's back end code so that anything and everything that could possibly be shut down when it isn't actually doing anything is indeed shut down.
When it came time to test it out -- 100% awake time again (although I stand by my earlier comments that "its not just us").
If I run the same app on a HTC G1 the phone will last a good 2 days (maybe more) without battery issues. If I uninstall the app the difference is minor.
This information, added to all the discussion on the Sprint forums about how the HTC "extras" that this phone comes bundled with have caused the same problem leads me to think that there is something in the Hero that's not behaving properly.
I see other comments like "It does the same on my <insert phone model here>" - well, we don't have unlimited resources, so if you can put the small amount of effort in to dial the 'dump' code mentioned above (*#*#963867#*#*) then maybe we can start to find a pattern here (maybe it's all the Android 1.5 based devices for example).
I'd also like to thank crunchybutternut for all of his assistance and time in trying to sort this issue out.
Doug
superman.namrepus said:
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Click to expand...
Click to collapse
If I can get in touch with someone who has access to the "guts" of the device and that can help me determine whats going wrong then that would be great. Neither the Android developer list nor the HTC forums are particularly helpful when it comes to tricky problems.
Bump
Anyone have some insight on this?
Ok - If someone working on one of these custom builds is prepared to lend a little assistance I'm willing to put a custom build on my phone and try to debug this a little deeper. However, with the number of hours that I get to work on this app.... and all the "fun" blocks that Google have been putting in our way w.r.t Android 2.x, I may not get much more time to work this problem.
That being said, I'm going to try experimenting with a new test app that just adds (one at a time) the raw features of the YouMail app in the hope that a single change triggers this wonderful problem you guys have. If that's the case then I'll put on my Sherlock Holmes hat and try to work around whatever is causing it.
Doug
Any news ?
soundmind said:
Any news ?
Click to expand...
Click to collapse
Got this from ymDoug:
No progress as yet - not seen anything from xda folks either.
I've made *massive* changes to ensure the app is shutting down absolutely everything it can when it has nothing to do - still no joy.
I've even gone through a lot of the Android source code and can't find anything that would indicate I'm doing anything wrong. There is one debugging method I'd dearly love to call inside the Google Android code (it dumps out a list of who is keeping the phone awake at any point in time) but the method is only accessible to (a) Google, and (b) People who cook their own ROMs. The official Android people are doing their usual stand-up job of ignoring the difficult questions
I am still making the odd change here and there, and my test app doesn't seem to be having the same problems (of course)
Regardless, there will be an updated version on the web site in the next day or so - I'll need to ensure my changes haven't completely screwed things up
Click to expand...
Click to collapse
Doug has made some changes, does not seem to completely resolve the sleep issue though.
Here's the link to the change log:
http://forums.youmail.com/forums/viewtopic.php?f=12&t=18
Click to expand...
Click to collapse
FYI: The version in the market is several revisions behind.

[BIG FAQ] Nexus S General [Start Here before Clicking New Thread!] ** OUTDATED **

EDIT: EXTREMELY OUTDATED. I have not had this device for some time and will not be updating this post.​
Please report all bugs encounter or search for and star the ones mentioned on these forums here: http://code.google.com/p/android/issues/list ; This is the official bug report forum of Google and the best way to let them know of the problems you are having. Don't post "Me too"s on known issues, simply star and cross your fingers!
Because people seem to be incapable of using the wonderful "Search" function built into these forums, I'm putting together a list of questions that keep popping up in new threads every other day.
Q: How's the Battery Life?
Officially, the Nexus S is rated for 6hrs of talk time and 427 of standby time. How much battery life you get will entirely depend on what you use the device for and how much. On my first real non-vacation day, my Nexus S lasted a little over 16hrs on one charge through what I would consider heavy usage (flashing roms/backups, emails, texting, web browsing, long phone calls, etc). Your mileage may vary. Fellow poster @Luxferro managed to get 2days, 14hrs, and 13minutes out of his phone on a single battery charge. Discussed here: http://forum.xda-developers.com/showthread.php?t=875809
Q: Does your GPS work?
Most people have reported their GPS to be functioning just fine, though there have been quite a bit of variation on lock times.
Q: Will this work on AT&T?
Yes, but you will not get 3G service. This is due to the different frequencies that T-Mobile and AT&T's 3G runs on.
Q: But it says it supports GSM band 850mhz!
GSM is 2G. UMTS is 3G.
Q: But Joe Bob/Dude down the street/My cousin's brother's nephew's wife said...
Stop it. It is likely that Google will release a version of the Nexus S with support for AT&T's 3G some months down the road, just like they did with the Nexus One but for right now, if you want 3G service, T-Mobile is the only way to go.
Q: Is tethering free?
So after having the phone for a bit of time now and tethering unimpended, I'm going to have to agree with @nxt that T-Mobile is not charging for or redirecting for tethering on this device. At least, for now. However, like in the original version of this answer, T-Mobile did announce that they were going to be charging for tethering but I've tethered every day for various amounts of time (including torrenting nearly a gig to my netbook) without so much as a hiccup. Source: http://bit.ly/d1NS9o
Q: Will TZones/Web2go/grandfathered web program work on this phone?
No, or at least, it doesn't appear to anymore due to T-Mobile locking down the IMEIs. When the phone was first released, people were reporting that it worked fine, then after a few days it became sporadic, before finally not functioning at all. See the discussion here for more information: http://forum.xda-developers.com/showthread.php?t=864843
Q: I unplugged my phone, and my battery dropped from 100% to 95% immediately, or it won't/takes along time to charge past 99%, what gives?
This is by design. Your phone will slow down and eventually stop pulling charge at or slightly greater than ~95% regardless of what your battery indicator says. This is to extend the overall life of the battery, as constant 100% to 0% charge/discharge cycles will cause it to fail prematurely. If you're interested in really pushing it to 100%, you can use a technique that is called "bump charging" and is better detailed here: http://bit.ly/f6xiZ0
Q: When I reboot my phone while it's charging, the battery jumps from X% to Y%, what gives?
I'm honestly not sure what causes this, but sometimes Android/Gingerbread gets confused on how much exact charge is in your battery if you reboot it while it's charging. However, from personal observation, it's just a display issue. Android/GB will eventually start showing the correct percentages once the battery has "caught up" with what it thinks it is at. Also wiping the battery stats(root only) seems to help alleviate this issue. Either way, it's not a large concern.
Q: Can we port SenseUI/Galaxy S apps to the Nexus S?
Most likely, no. Those apps typically require the Rosie/Touchwiz framework in order to function. You can have those apps when and if a developer decides to port those ROMs in their entirety.
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Follow the root guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Q: Linpack/Quadrant Scores?
Linpack doesn't play very nicely with the Galaxy S lineup generating very low numbers in comparison to HTC devices. This is because the processors that are powering these devices operate in different ways. Does this mean the Nexus S processors are slower? Not really, just different. As for Quadrant, it doesn't currently work very well with Gingerbread and needs to be updated. The scores folks have been seeing though put it in the 1600 range without a modified kernel.
Q: There's no LED Indicator? What are those two circles next to the speaker?
Correct, like all Samsung devices(minus the Epic 4G on Sprint) thus far, there is no LED indicator light. There are apps, such as NoLED, on the marketplace which work great on the Nexus S and provide more or less the same functionality. There's another app called BLN which will blink the capacitive touch keys to let you know you have a notification, but it requires a custom kernel to support it. Those two circles are the Proximity Sensor and Ambient Light sensor.
Q: I can't zoom in and out on the camera app!
Correct, the digital zoom feature seems to be missing.
Q: Can the Nexus S do 720p?
No, at least, not right now and not on the stock ROM. It is possible that eventually our wonderful developer community will come up with a software hack for custom ROMs to allow 720p video recording, but at a reduced framerate than if it had a true 720p chip similiar to what they did with the Nexus One. Until then, the answer is no.
Q: But that one guy in Italy says the Italian version can do 720p recording!
No, he says that it can do 720x480 which isn't the same thing. The 720p "name" comes from the last numbers in the resolution, so in this case, it would be 1280x720(which the other Galaxy S phones are rated to shoot at).
Q: How do I video chat?
Google, unfortunately, did not develop a native app to support video chat and so we must rely on some from the marketplace. Right now, as far as I'm aware, Tango is the only one that has been updated to support video chatting on the Nexus S.
Q: My toys are better than your toys! Hahahaha!
Stop it and grow up. Different strokes for different folks. People spend their money on what they want to spend it on regardless of your agreement on their choice. Not to mention that this kind of behavior goes against the spirit of this community.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Q: Clockworkmod says I'm not set up for OTAs! What gives?
That's not for official OTA updates from Google. Some custom ROM developers set up their roms to receive custom OTA updates or at least notifications of said update specifically for that ROM.
Q: Why have my Wifi/3G/Signal bars switched from green to white?
A green set of bars typically means that you are connected to and syncing with the Google Account servers. White means that this is not happening for whatever reason, usually something like a bad signal or low coverage area. Also the WiFi connection is set by default to turn itself off(aka sleep mode) when the screen is off, this can be adjusted under Settings > Wireless & Networks > Wi-Fi Settings > Menu Key > Advanced > Wi-Fi Sleep Policy. Don't panic, though, it's nothing too major.
(Suggested by mmas0n, thanks!)
Q: How do I restore the stock recovery?
Right now, it is NOT possible to flash the stock recovery over Clockwork Recovery at all. The only way to restore it is by NAND restoring the Stock 2.3.1 backup in the development section.
Q: Does the Nexus S have Gorilla Glass?
No, it does not. Take care of your device.
Q: The Nexus S only gets 3G? Omg, I only see a 3G icon!
The Nexus S gets UMTS and HSDPA, which are both technically 3G. Your phone idles on UMTS 3G, and when it starts downloading/uploading, it'll flip to HSDPA after a few moments. You can see this by typing *#*#4636#*#* into your Dialer, going to Phone Info, and looking at Network Type while downloading something. The ability to switch the icons on the notification bar is something that was added in custom ROMS, and is not supported by the stock ROM. Furthermore, the icon is not always an indicator of what kind of data connection you have. If I were so inclined(and I'm not) and/or had the technical skills(which I don't) to modify the framework, I could make it say OVER9000g when connected to anything. Rest assured, if you are on a network that uses the 3G bands the Nexus S supports, then you are recieving HSDPA regardless of what icon you see.
As suggested by Gogol(thanks!), now adding a...
Possible Known Issues(Reported by some users but not all):
Lag in the Web Browser
Back button is not responsive or doesn't light up
Pink / white / yellow tint on the screen
Weak WiFi signal
Weak cell signal (not necessarily specific to the Nexus S; T-Mobile's frequencies typically have bad building penetration)
Some apps running wild consuming battery
Missing apps in market (until Google updates to recognize 2.3.1 buildprint)
Accelerometer becomes "locked" after using Google Sky Maps requiring a reboot to free
Ringtones changing on their own following reboot/USB plugin (Push the .mp3 to /system/media/audio/ringtones to stop this *requires rooting*)
Stock launcher has home screen/scrolling lag issues (not present on market launchers like ADW/LauncherPro)
Home screen icons on stock launcher randomly disappear, disappear after move, or show up in folders they weren't moved to. (not present on market launchers like ADW/LauncherPro)
Please report all bugs encounter or search for and star the ones mentioned on these forums here: http://code.google.com/p/android/issues/list ; This is the official bug report forum of Google and the best way to let them know of the problems you are having. Don't post "Me too"s on known issues, simply star and cross your fingers!
EDIT: EXTREMELY OUTDATED. I have not had this device for some time and will not be updating this post.​
Sti-cky! Sti-cky! Sti-cky!
Thanks for taking the time to make this list. Should be the first thing newbies read when they join the forum
Stuck due to the usefulness of this thread
Great FAQ thread man. Thanks a lot.
And lol @
But Joe Bob/Dude down the street/My cousin's brother's nephew's wife said...
Great FAQ, but it would be much better to add the list below, because there are many threads opened and will be more and more ...
Possible known issues:
1. Web browsing lag
2. Back button is not responsive
3. Cannot zoom when taking photo or video
4. Pink / white / yellow tint on the screen
....
Q: There's no LED Indicator? What are those two circles next to the speaker?
Correct, like all Samsung devices thus far, there is no LED indicator light.
Click to expand...
Click to collapse
Actually not true, the Galaxy S Epic 4G does have a LED notification light.
Q: Is tethering free?
No, tethering is not free. T-Mobile charges for this service. That being said, people have and still do tether without paying for the service with little to no consequence. T-Mobile seems to track the User Agent of the browser you're using on their network, and it is possible to mimic the Android browser's user agent on a desktop PC and tether undetected. In the event that T-Mobile discovers you tethering, you will receive a text message and all internet traffic on their network that doesn't contain the Android UA string will be redirected to an official T-Mobile site encouraging you to sign up for their tethering service.
Click to expand...
Click to collapse
This is wrong.
Tethering is free and included with the Nexus S as long as you have a normal data plan with T-Mobile (not any $5.99 or $10.00 T-Zone hacks/etc.). There is NOT an extra special $10 add-on tethering free.
jblparisi said:
Actually not true, the Galaxy S Epic 4G does have a LED notification light.
Click to expand...
Click to collapse
Thanks! This has been corrected.
nxt said:
This is wrong.
Tethering is free and included with the Nexus S as long as you have a normal data plan with T-Mobile (not any $5.99 or $10.00 T-Zone hacks/etc.). There is NOT an extra special $10 add-on tethering free.
Click to expand...
Click to collapse
Negative. As of 11/03, T-Mobile has begun charging for this service.
Source: http://www.tmonews.com/2010/10/t-mobile-launching-14-99-tethering-plan-november-3rd/
Android 2.2 introduced the ability to hotspot tether regardless of a paid service on nearly any device(and before that, this was available through some market apps). I believe some have had this ability "disabled," in the sense that it doesn't show up in the Wireless & Networks menu(such as the G2, though this was corrected in an update) but through apps such as AnyCut you can still activate the service and tether.
So, once more, you CAN tether without paying for it, however, T-Mobile may start redirecting your web traffic that doesn't contain the Android UA string to their website. They've been super inconsistent in their enforcement (a good thing, if you ask me!).
EDIT: After looking through the "services" options on my T-Mobile account, I don't see anything about a tethering plan. If other folks could take a peek and let me know, I'll revise that section and make the correction.
gogol said:
Great FAQ, but it would be much better to add the list below, because there are many threads opened and will be more and more ...
Possible known issues:
1. Web browsing lag
2. Back button is not responsive
3. Cannot zoom when taking photo or video
4. Pink / white / yellow tint on the screen
....
Click to expand...
Click to collapse
Thats a great idea, I'll definitely start try to start collecting known issues.
Understand that the development section for more detail on rooting / unrooting, but would greatly appreciate if you could post specific links in your FAQ to threads that you would use to root / unroot.
Am a newbie and since I see more than a couple of threads on the subject in the development section, I would greatly appreciate it if you can give links here based on your order of preference (after all its your thread) if there are more than one ways.
Point is a link in the FAQs would give more greater confidence
Paparasee said:
Understand that the development section for more detail on rooting / unrooting, but would greatly appreciate if you could post specific links in your FAQ to threads that you would use to root / unroot.
Am a newbie and since I see more than a couple of threads on the subject in the development section, I would greatly appreciate it if you can give links here based on your order of preference (after all its your thread) if there are more than one ways.
Point is a link in the FAQs would give more greater confidence
Click to expand...
Click to collapse
Updated to include links to two threads in the development section which should get you on your way.
The first one will help you setup ADB and the relevant drivers needed to input commands to the phone from your PC. The second is the actual rooting method and custom recovery installation.
unremarked said:
EDIT: After looking through the "services" options on my T-Mobile account, I don't see anything about a tethering plan. If other folks could take a peek and let me know, I'll revise that section and make the correction.
Click to expand...
Click to collapse
Again, since this is the Nexus S forum, the Nexus S, has NO tethering pay plans for T-Mobile. It's included and free. Yes that option was removed on the G2, etc., but again, this is the Nexus S.
nxt said:
Again, since this is the Nexus S forum, the Nexus S, has NO tethering pay plans for T-Mobile. It's included and free. Yes that option was removed on the G2, etc., but again, this is the Nexus S.
Click to expand...
Click to collapse
I'm well aware of which forum I am in and which phone I have.
The option was removed in the G2 and added back in via OTA update, it was also there on the MT4G at launch. I'll admit even setting my device to to show as one of those still does not pull up that option under services. I'm willing to believe that perhaps T-Mobile announced their intention to charge for the service then decided not to.
However, just to point out, the Nexus S/Nexus One are not special phones(as far as T-Mobile are concerned) on T-Mobile's network and thus entitled to special privileges. They are subject to the same rules and regulations as any other phone. In any which case, I'm going to make an adjustment to that section to note the ambiguity.
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
PhaedraCorruption said:
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
Click to expand...
Click to collapse
Not really. Every device has it's bugs and issues at release, the Nexus One included. Touch screen wigging out randomly, capacitive buttons misaligned, the relatively easy "death grip," and just generally (at least for me) weak 3G connection. My favorite was when the Nexus One wouldn't send or receive any text messages or phone calls.
We should also keep in mind that Gingerbread itself is brand new as well.
unremarked said:
Q: Can we port SenseUI/Galaxy S apps to the Nexus S?
Most likely, no. Those apps typically require the Rosie/Touchwiz framework in order to function. You can have those apps when and if a developer decides to port those ROMs in their entirety.
Click to expand...
Click to collapse
regarding this...
we might see some ports over in due time.
they guys over at SGS are already in the process of porting the SenseUI
once they are done with that feast, it'll be a lot more doable to bring it to Nexus S
http://forum.xda-developers.com/showthread.php?t=788866
and
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=827745 Alpha ready for testing!
Please add "Q: Why do the Cell and WiFi signal icons switch to white?" or something to that effect.
We have 3 thread on this issue and I foresee many more.
mmas0n said:
Please add "Q: Why do the Cell and WiFi signal icons switch to white?" or something to that effect.
We have 3 thread on this issue and I foresee many more.
Click to expand...
Click to collapse
Done so! Thanks for the suggestion.
PhaedraCorruption said:
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
Click to expand...
Click to collapse
its just the high expectations, the NS wasnt a game changer like the N1 was
After the update I can't download anything from the marketplace. Anybody else have this problem?
katana24 said:
After the update I can't download anything from the marketplace. Anybody else have this problem?
Click to expand...
Click to collapse
Can't say that I have. Are you talking about missing apps, or are you getting some kind of error message?

Successful Wifi Calling setups - please describe?

I'm curious for all you TmoUS people who have the ability to use wifi calling, if you are using it for ICS and it works could you describe your setup - rom, router, internet service, etc.
I've tried wifi calling on 3 different ICS roms and it didn't work for any of them. For my personal setup things work for about 2 or 3 minutes and then the call fails and my phone freezes for a few seconds. To call back I need to disable wifi calling, I've given up on it for now. I'm just curious to know if it might be just the app or if it could be the router or wifi signal or some combination or factors.
kingston73 said:
I'm curious for all you TmoUS people who have the ability to use wifi calling, if you are using it for ICS and it works could you describe your setup - rom, router, internet service, etc.
I've tried wifi calling on 3 different ICS roms and it didn't work for any of them. For my personal setup things work for about 2 or 3 minutes and then the call fails and my phone freezes for a few seconds. To call back I need to disable wifi calling, I've given up on it for now. I'm just curious to know if it might be just the app or if it could be the router or wifi signal or some combination or factors.
Click to expand...
Click to collapse
It is none of the above. Wifi calling on Tmo US with an ICS ROM is a known issue and will not be resolved until a developer gets an actual Tmobile US RUU to play with.
Between that and the inability to use the MyAccount app on an ICS is the whole reason I'm still on AHRD 3.6.
It is well known and documented that WiFi calling will work for a short time then cut out...and the fix by a dev is waiting on the above mentioned RUU.
I know that I've read posts that people claim to have been using wifi calling on ICS without any issues. I know its a known issue and I know the root of the problem is ICS itself, but why do some people say they use it without a problem?
My guess is people try to talk on the phone like me...as little as possible.
if someone is able to carry on a lengthy conversation without issues, I'm in the same boat as you...I'd like to know too.
Sorry...I didn't know you were aware of the apparent issues...
I have Wifi Calling partially working on my T-Mobile/HTC G2 running Andromadus Alpha13 (CyanogenMod 9 based).
I haven't figured out all the specific build.props entries that it needs to work, except I know that some update.zips with a minimal set don't work. I have one that pretty much replaces the build.props with one that spoofs TMO build data as well as other stuff and that this build.prop file works.
In addition to needing the .so files that are provided in all the update.zips I've found, and the Wifi Calling APK, I've read that GanOptimizer.apk is needed too and added that to mine.
I've found I can unreliably make outgoing calls. The first boot it did not work, the second boot I was able to make a call every other attempt or so. The audio quality seemed good too.
I can receive every single incoming call but they won't route audio wise and will drop. Then the app gets into a bad state and can't make outgoing calls either. Rebooting fixes that.
I haven't finished figuring out the bugs. The bottom line is it seems that CM9 *does* support Wifi Calling and it can work with some libraries and APKs added, however there are bugs that need to be figured out and fixed.
So from what it sounds like if I switch to Revolutinoary HD, then I won't get wi-fi calling, but since I'm running CM7, I get wi-fi calling but in exchange my HD camera doesn't work. We really just have to wait for updates now don't we?
Hey I actually just got HD Revolution installed, made a call on wi-fi for 15 minutes or so and it worked just fine.
Im running ARHD ICS and wifi calling works perfectly for me.
Sent from my HTC Sensation 4G using XDA App
That's kind of the point of my post, if it works for you I wanted to know what your exact setup is. I started with ICS on ARHD and wifi calling still only worked a couple minutes before cutting out.
kingston73 said:
That's kind of the point of my post, if it works for you I wanted to know what your exact setup is. I started with ICS on ARHD and wifi calling still only worked a couple minutes before cutting out.
Click to expand...
Click to collapse
+1. Same boat.
Well there's not much to tell really. I just updated my firmware as I was running CM7 to ICS and installed AR HD ICS 6.5.1. Other than that I guess I run NOVA launcher and that's really it

Add Wi-Fi calling?

How can I add wifi calling to a ROM? I remember back in my G2 days it was an APK I could simply install... but now this is more baked into the ROM.
I REALLY need it and have been dealing with their tech support to reset the "iHLR" settings. I've switched out my SIM but the TM number doesn't match what I've researched works best with Wifi calling. I've done a good bit of forum searching for anything and every single result didn't have one instance of even the word "calling".
And now my favorite ROM doesn't have wifi calling :crying: lol
theratdude64 said:
How can I add wifi calling to a ROM? I remember back in my G2 days it was an APK I could simply install... but now this is more baked into the ROM.
I REALLY need it and have been dealing with their tech support to reset the "iHLR" settings. I've switched out my SIM but the TM number doesn't match what I've researched works best with Wifi calling. I've done a good bit of forum searching for anything and every single result didn't have one instance of even the word "calling".
And now my favorite ROM doesn't have wifi calling :crying: lol
Click to expand...
Click to collapse
WiFi calling on TMobile is terrible. I'm not sure if that was fixed in the latest update. As for porting the WiFi calling feature to other ROMs, it has not been done yet since TMobile has integrated it into the framework (and it works horrible so there is no incentive).
I've never had a good experience with it either, but I need it so bad Stupid feature
It's more than an apk now, it's a couple of lib files.
Wifi in the latest release seems a lot better than the older.
Does Venom's Rom support it? It comes up when I do a "Wifi Calling" forum Search. I don't see it where it usually is, but I did de-sense it so I'm not sure if that effected it or not.

Couple of questions about troubleshooting a problem/RMA

Hey ladies and gents, I have a strange issue with my N5. I am losing data connection despite having a 4-bar LTE signal. Most of the time, I will catch it at work while streaming music from Spotify/Pandora. Once in awhile i'd catch it while browsing Facebook as well. It will show a 4-bar LTE connection, but the apps will report "no data connection available." I've tried surfing Chrome when this problem arises and it says "You are Offline." I found a temporary fix - turning Airplane mode on/off or restarting the phone.
Has anyone ever heard of this, and does anyone have any suggestions. I was running SlimKat before, but now i'm on stock 4.4.4 with ElementalX kernel, with the issue crossing multiple ROMs/wipes.
I also just got off of chat with Google support. The lady is emailing me some troubleshooting steps, and wants me to contact T-Mobile as well. If the problem is still there, she wants me to RMA. What are the steps needed in order to do so. Some quick searches brought up factory images but I haven't found anything recent, and want to make sure I have all my bases covered.
Thanks guys!
Google doesn't care whether the bootloader is unlocked or whether the phone is rooted. If it's a hardware issue, you are covered!
If you want to return to stock before sending it in for peace of mind then follow this thread: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Sorry for the late reply, been pretty busy the last couple of days. Glad to hear that Google doesn't care about the unlocked bootloader! I'll probably just return completely to stock and return it like that IF I have to.
However, I think I may have fixed the problem. I altered my APN settings and changed IPv6 to IPv4 and it seems to have fixed my problem, at least for now (the problem is random so i'll have to use it for awhile to make sure it really is fixed). Anyone else ever heard of this problem, or this fix, especially on T-Mobile?

Categories

Resources