Hi! I hope to write in the right area, but if not I ask someone to move my post in the right one.
Now I have a HTC Diamond device, but I've to change it for a GalaxyS or an iPhone4.
I would like to buy a GalaxyS device, but I read many posts about bugs, lags, gps problems, so I wonder if it is a great choice this GalaxyS.
I like android and all the development opportunities around it (thanks to XDA), but it seems to be not so stable yet...
I flashed many ROMS on my Diamond in the past, so it's not a problem to do the same for my GalaxyS, but problems are fixed? The GPS works fine? Maybe not...
Maybe with Froyo 2.2?
iPhone4 is not so open as an Android device, but it's a very stable device!
What do you think about?
coming from a winmo background you're gonna love the galaxy s! its miles ahead in terms of refinements, polish and brilliant integration. The GPS problems are nothing so critical...its more of a sw fix im guessing. I live in India, and i have ZERO problems on my GPS....i feel the bug is something country/carrier specific.
there are many things to love and obsess with the galaxy s....go get yourself one, you sure wont regret it
While I'd love to echo what dreamtheater39 has said, I can't. It's a brilliant phone, but after having mine for just under a month, it's starting to lag like crazy, and in the last two days I've had a ton of dropped calls and the phone has switched itself off/crashed three times in the last few hours resulting in data loss because the power button doesn't respond (forcing me to hard-reset the phone).
All I can say is that, if you do get one, have an open mind. And make sure you don't get locked into a lengthy contract in case things do go awry.
same here GPS working great since day 1
http://forum.xda-developers.com/showthread.php?t=775450
Maybe I got a lemon
Maybe I got a lemon but I can not stand the i9000. I have 4 bugs that drive me crazy.
1. Market Place hangs at starting download. I have to do a factory reset to download an update an app.
2. GPS just stops working or it puts you on a different street when you are using navigation. The worst part is then it has to recalculate the directions twice, once for the wrong location and then again for the correct location, which is a real pain in the pocketbook when you are rooming.
3. Receives invalided cert from a hotspot connects the 1st time then never again. So I cannot use my hotspot at work, my old iphone connects no problem.
4. Does not always switch between wifi and mobile network. Have to go to airplane mode and back to get 3G network. (I tried changing the wifi sleep settings)
Mmmm...so maybe it's a good device, but I understand that who had an iPhone before it seems to be a step backward...is it?
Hello every one.
I'm the proud user of a HTC Touch Diamond. It has served me well since day one, and now i want to make it even better.
I need the phone to work. And i need Android (read: want). So i'm asking everyone which version do you find more stable. What i need:
Phone. Must work. Must work well. Cannot wait 20 seconds for the device to wake up (while ringing) to show me who's calling me. When i decide to pick up, the other guy gives up, or the call os forwarded to voice mail.
Wifi is a must, that sim has no data plan.
Battery, though superficial due to a 2400mAh bat, it takes alot of calls and sms's.
Market. Must work.
Camera is a bonus, helps here and there.
The rest is rest. i don't need bluetooth, GPS, or anything like that. Anything from 2.1 forward is enough. So... i'm open to suggestions.
I did this same question of the kaiser section, and was greeted with 2 very stable versions. One Eclair and one Froyo.
froyo b ver 6
it is very stable
and the 3d performance is better than the old version
url http://forum.xda-developers.com/showthread.php?t=970476
I'm getting 21FPS (diam100) and 20.2FPS (raph100) with NeoCore with no overclock and camera+camcoder works great
I'm currently using that one.
Though "snappy", its quite slow. Market is a pain. (Wifi)
Takes too much time to wakeup and show the screen (i actually have to unlock to see the screen).
Looking for something else maybe. 3D isn't a must.
I've got three different Android ROMs form different developers and the fastets and most stable ROM would be http://forum.xda-developers.com/showthread.php?t=907509
additions like camera or WiFi works fine for me.
Hi everyone!
Does the Optimus 2X support native 3G video calling?
I mean, like Samsung Galaxy S does?
I am not refering to IP videocall, such as fring, oovoo, clearsea and such.
All i want is plain old native 3G video calling to be enabled in the dialer, so that i can videochat using my free air time (no waste of data plan megabytes) with people who do not even have a smartphone, but their phone does support 3G video calls.
Please let me know if it does, because it is a major thing for me to know, before i decide whether to buy.
Thank you very much in advance!
As far as I have been able to ascertain the LG 2x does in fact support proper video calling via the 3g network.
Can some one(those who are using it and did video call over native 3g) confirm it...
samchristopher said:
Can some one(those who are using it and did video call over native 3g) confirm it...
Click to expand...
Click to collapse
I'am in Indonesia and I can confirm that native video call via 3g is working. I can video call my family several time (they use Nokia though).
Works for me
yupe! it works for me too. I even vid call to different provider and everything is good. Of course you need to have at least 3g connection. Better if yours is 3.5g..
3G videocall supported... Well!
But... only with stock rom?
Are there cooked roms that supports 3g videocall?
Thank you!
Cyanogen ROM does not support videocall.
So I'll never download it: I dont want a silly iPhone (people pay for a device that can't even do a video call..)
Any other ROM works ok!
4s8kalz said:
3G videocall supported... Well!
But... only with stock rom?
Are there cooked roms that supports 3g videocall?
Thank you!
Click to expand...
Click to collapse
All cooked roms except AOSP roms (like Cyanogen or MIUI)...the other stock-based roms support videocall
DJ Palmis said:
Cyanogen ROM does not support videocall.
So I'll never download it: I dont want a silly iPhone (people pay for a device that can't even do a video call..)
Any other ROM works ok!
Click to expand...
Click to collapse
Never used videocalls (they're expensive )...I tried cyanogen...a next-gen mod! Ram management is fantastic, never had a lag....only videocamera doesn't work as expected so I had to return to stock based roms
I have videocall free of charge for one hour a day.
And i don't like to pay a device and then loose functionality.
But I know that you can't agree with me.
Personal background: Associate degree in Laser Electro Optics. 12 years research and development semiconductor manufacturing, 15 years as an EMT, last 10 years as a 911 telecommunicator for Austin-Travis County Emergency Medical Services. 6 of those years as a Training Officer.
The reason for my (cough) resume is so everyone understands I have the technical background and experience to explain the differences between e911 and 911.
Public Safety Answering Point: the local organization tasked with answering emergency request phone calls and dispatching appropriate emergency resources. PSAP's are broken into two types, primary and secondary. The primary PSAP is typically the local police department for city's and the local sheriff's department for unincorporated areas. Some colleges have their own police department and may have their own PSAP. So realistically a person can connect to a different 911 call center depending upon their location within a small geographic area.
Large urban areas typically have secondary PSAP's. The secondary PSAP usually consists of public safety departments not related to law enforcement such as fire and/or emergency medical services (ambulance services) specially trained to send request specific resources dependent upon the emergency. In Austin and Travis County we run 120 thousand EMS 911 calls per year. The police department takes about 2000 911 calls per day.
911: a simple to remember phone number nation wide allowing everyone access to emergency services. No location information is transmitted or received. The PSAP is responsible for determining location by interrogation of the caller. This can a problem if the caller is altered or otherwise unable to give accurate information.
e911: Enhanced 911 was created to ensure location information was transmitted to the 911 call center regardless of the callers ability to give this information. The phone companies are responsible for ensuring this information is available and transmitted to the PSAP. Conventional e911 is effective for landline phones. Cell phones present a completely different problem.
Cell phones are required to meet two different location technology standards.
Phase 1 wireless data: as cell phone use skyrocketed in the nineties, legislation was passed requiring provider's to transmit location data based on the cell phone tower that the cell phone was connected to. While this is helpful, it is problematic due to the sheer size of the area that had to be searched if the caller was unable to give their location.
Phase 2 wireless data: legislation now requires GPS location data be provided by the cell phone company. This location information can be transmitted via the gps chip from the cell phone or via radio location triangulation using the cell towers in the immediate area of the caller.
So in a nut shell, my test of neobuddy's ICS indicated that 911 worked for a sim loaded phone. I did not test the phone with the sim pulled. I also did NOT verify that GPS data was being received by the PSAP.
If 911 works with your phone it should work in any area. I was connecting with two different PSAP's as I live right between two different area's and sometimes connect to one or the other.
Hope this clears some of the confusion. A good explanation is located at en.wikipedia.org/wiki/Enhanced_9-1-1.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Later tators
Sent from my Touchpad using xda premium
thanks a lot. i can confirm cm7.1 has 911 issue.
Sent from my SGH-T959 using XDA Premium App
Developers should also note that as technology continues to advance, video conferencing and text message 911 activation requirements will also be legislated in.
I firmly believe that Google should begin requiring manufacturers make their modem software and audio software open source. Manufacturers should also be required to provide detailed explanations of how the relevant library's interface with the operating system, modems and audio system when activating an emergency call. This is Androids achilles heel. All it will take is one national media event to slam the door on open source operating systems for cell phones. I love the freedom Android provides and the exceptional programing skilss of our developers.
Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Sent from a cell tower to the XDA server to you.
Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Click to expand...
Click to collapse
correct as none had the source code....but for 2.3 onwards rom.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Click to expand...
Click to collapse
made my day.....thanks a lot....will be keeping a close eye on this thread...
My understanding is the issue is only without a sim right?
The 911 issue is with SIM, i don't know about without and im not planning on finding out.
HaloMediaz said:
My understanding is the issue is only without a sim right?
Click to expand...
Click to collapse
It has to do with emergency mode (no dim) and when no compatible roaming network is around (no service) .
Sent from my HTC Sensation 4G
hmmm I havent called 911 in YEARS but it still feels nice to have the ability and this was a nice explantion thank you
MIUI 360 in Asheville NC works fine but not in other areas?
Hopefully they can test the cm9 test ports that are out now.
Sent from my SGH-T959 using xda premium
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Can we get independent confirmation of this? (not that I don't believe you)
Sent from my SGH-T959 using xda premium
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
You typed all that from your touch pad? props
Sent from my SGH-T959 using XDA App
Genesis3 said:
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
Click to expand...
Click to collapse
No, I get that. Just wanted to make sure he verified was all..
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Don't know who you are or where you came from but, you sir may have saved CM development for the vibrant community. Here's hoping and you're the man!!!
Sent from my SGH-T959
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
I just downloaded your kang and running great so far, Thanks for you work !!
Question, is this 911 fix kernel dependent ? ie will it break if I flash another cm7 kernel ?
Thanks again for your hard work !!!
will replacing the kernel break both 911 and gps fixes?
I didn't save anything.
Here's the bottom line, if you're interested in it.
In the original Vibrant device directory there was a set of sources for libaudio -- one of the shared libraries that Android depends on to talk to the audio hardware in the phone. There was no documentation as to where this source came from, but I know where it didn't come from -- it didn't come from a public Gingerbread source for the Vibrant, because there isn't one.
It turns out the library this source builds does not work correctly but exactly why I'm not certain of. One of the problems with debugging this is that I have to have someone else test for me, which means I can't do the sort of testing I like to when I'm tracing things like this (a highly-iterative process that requires that I actually be staring at the debugging screen while doing the deeds that cause the bad behavior) since I can't call 911 myself.. Had the provenance of this code been documented originally (or lack thereof) I would have investigated this possible connection, as I knew the problem lay in the audio connectivity due to myriad kernel and application traces a couple of months ago. I didn't chase that library down and attempt to graft in other related versions because I assumed that the CM people knew what they were doing building that library from source rather than using a cribbed copy from, for example, Froyo or a different gingerbread build off a similar device.
Picking up a different shared library does work. Exactly what the provenance of that library is (e.g. was it grabbed from a binary, was it built from DIFFERENT source, where did it come from?) is also unknown.
Now that I have a working shared library on this device and a non-working one I'm going to compare traces. Maybe I'll get lucky and find the changes necessary in the source that's in the build tree and be able to fix that, at which point I'll know what I've got rather than having a "magic" library from God-knows-where.
Now here's the part that annoys me -- I was all over some of the CM guys about audio problems with other Samsung devices and tried to get access to the "not yet finished" repos because I expected that if I could run down the same sort of problem with ordinary calls in one of the OTHER Samsungs it was rather more likely than not that the same fix would be pertinent in some way on the Vibrant -- simply because manufacturers tend to use the same chipsets and bits, along with APIs, between different devices (it makes it easier for their coders and maintainers to do their jobs.) In addition when I started working one this one of the other protagonists didn't give me jack and crap about the provenance of anything in the device tree and, again, there's no docs embedded in the tree either. You can find the flamewar and slander aimed at me here if you'd like. It turns out I was on the right path; the problem this library allegedly fixed was having to hit <MUTE> twice to turn off and on the audio path. Sound familiar? Well, the pointer to the file that I found and integrated was from a bug logged against the I-9000, a similar phone to the Vibrant, and that library version works. What's changed in it? There's no set of commits logged against the ZIP file provided in that patch; is it a binary lift from a different build (e.g. some factory build) or did someone fix the source?
Who the hell knows because again, it's not documented in the bugtracker. Until I know where it came from and, if there's source, I have access to it, I won't support it. I don't play the "hide the sausage" game when it comes to alleged community coding projects.
I ran into something similar with the Triumph in that there was a different set of parameters coming up from the hardware when a wired headset was plugged in. That was easy to run down because I could do it and see what was going on; it was a literal couple of line change in the code once I found it. There are a couple of places in the libaudio source that might be the cause of this now that I have a reason to look in there, but without being able to easily reproduce the condition that creates the failure (e.g. call 911) it's a guess.
The ICS builds out at present have a different copy of the same compiled library and it also works. I bet that one works too on CM7 as it's fairly close to the metal and thus the API's probably the same (or close) on the Android side but I haven't tried it yet. I've got little reason to since I now have a libaudio.so that's functional on CM7 in any event.
While I've been working on the 911 issue (for a couple months on and off) I also traced down some actual working (properly) GPS libraries that handle the AGPS assist data in the correct way, something that other sets of them do not, and added those too. I also made a few other changes. The battery life is reported to be rather impressive, and the near-instant GPS locks most-definitely are. I can't speak much to the battery life view of the world as of yet but I will be looking at that; that's an area I know quite a bit about (getting these devices to properly go into deep sleep as they should) and the source tree I'm working with does have kernel source.
Any sideloaded kernel that leaves libaudio.so alone (check the zip file to make sure that /system/lib/libaudio.so is NOT present) should be ok, but no promises. Before you go screwing with kernels make sure you want to --you might break GPS performance as a number of the kernels have various attempts to get the GPS to work right and load various libraries along with the kernel itself with varying degrees of success.
I'd be willing to maintain this port but there are two conditions -- first, I expect apologies from the CM people who attacked me, in public, and second, I expect a formal commitment that there will be no more hiding of information. "I don't know" is an acceptable answer provided you run down the person who does -- someone does know because someone DID either import or code the material in question; silence and lack of documenting where things came from and how they came to be is not acceptable. When things go into the codebase through review they damn well ought to be documented. I played "talking to the brick wall" with the Triumph and now the Vibrant and I won't do it if I'm taking on responsibility for maintaining something.
If CM wants me involved in this that's the deal. If not I'll consider setting up a parallel build and set of repos for the bits that have to be changed from the base CM7 Gingerbread branch as I did for the Triumph if there are people interested in it, but my time is not unlimited and in all honesty my taste for working with the CM people and the CM code in general has been seriously damaged, never mind that what I have here seems to work just fine. As such the benefits of continued efforts are likely to be relatively small. If I decide against a continuing effort I will take the build environment that produced that I have now and attempt to set up a manifest so it can be cloned by anyone else who cares to do so, which should take care of others being able to build and run the KANGs from source if they wish. The latter may take a while as I need to find a day when I'm not busy and can put that together (again, lack of documentation doesn't help) and then pull a clean test from a zero base and make sure it builds and runs.
The Vibrant is no longer my daily device but I do still own one, and given its relatively modest resale value I'll probably keep it as a spare device -- it's a very credible phone and with working GPS code it actually locks faster and better than my Hercules does. It's biggest shortcoming is that it's relatively RAM-starved compared to more-modern devices.
Fancy that.
Forgive the noob question, but I have several older android cell phones, I think it'd be neat to turn them into wifi enabled dedicated music players. I.e. no apps, less services to run. Are there such roms? How complicated would it be to build a rom with no cell radio, but bluetooth and wifi only? Would it be as easy as stripping a rom that exists for the phone to its bare essentials? What are the primary challenges in building a stripped-out rom for a individual legacy phones? Is there such a thing as a universal Android rom? Or, short of a full rom, a full launcher replacement that acts solely in this fashion?
I mean, if I have an old Verizon cell, and I'm on t-mobile or at&t, it seems a fate less worthy for a device that could still perform such a basic function as a music or media player.
I'm just thinking, that's all.
And if no such thing exists but is certainly possible, i'll probably become a new developer.
Lol
My old SII sits around the house as a dedicated music / radio streaming device. There's not really any need for a special ROM, just flash something light like CM or AOSP and remove anything not needed. Put it in airplane mode to disable the radio and leave wifi on, job done.