Recommended Posts

So I'm looking to get a new phone.

My current phone is a HTC Trophy 7 (a.k.a. HTC Sparc). The phone is no longer compatible with the network I am on.

I'm looking at 3 options:

Nokia Lumia 920: http://www.nokia.com/au-en/products/phone/lumia920/

Samsung Galaxy S3 (NOT the 4G version): http://www.samsung.com/global/galaxys3/

Motorola Razr HD: http://www.motorola.com/us/consumers/DROID-RAZR-HD-BY-MOTOROLA/m-DROID-RAZR-HD,en_US,pd.html

To preface this, I WILL NOT BUY AN IPHONE. I would however like some advice as to which way you all think I should go. Price isn't important as all of these phones are free on my contract.

So here's where I am at the moment.

Lumia 920:

Pros:

Ecosystem, I'm already on WP7, LTE, Battery Life, Nice Design, Good (basic) voice control (for calls and messaging in my car), wireless charging (kinda meh).

Cons:

App ecosystem blows, sub-par multi-tasking, No replaceable battery, dual core.

Samsung GS3:

Pros:

App ecosystem, compatible with my email etc, Battery life, Good community support (CM10 etc), strong processor, tons of ram, good storage.

Cons:

Sub-par shipping ROM, Most of the big features are specific to the rom, Screen is a bit meh, Voice control appears hit and miss at best.

Motorola Razr:

Pros:

App ecosystem, compatible with my email etc, BIG Battery life (25% more than both phones in battery size), really nice screen.

Cons:

Sub-par shipping ROM, Voice control appears hit and miss at best, It's a Motorola, dual core,

Regarding usage:

I use my phone to make phone calls a lot. I text a lot, but I'm pretty easy on my data usage (I'm mainly using wireless). I need to be able to use voice control via bluetooth in my car. I don't really stream media, I don't listen to music off of it unless I am running. I don't need LTE and I'll rarely be in locations that support it. I won't touch the GS3 4G because it has enormous battery drain issues.

I'm a bit shy of going WP8 due to what happened with WP7. I really like the voice control (it works well, reads me my messages and lets me reply etc). The app ecosystem doesn't worry me beyond that the apps I use are generally of lower quality on WP than on Android (Endomondo, FitBit) and it has terrible multi-tasking.

Moving to android isn't so much of a worry so long as voice control is still really good. Everything else I can work around, just not that.

So yeah. Any advice, first hand experience etc would be very much appreciated :)

Link to comment
https://www.neowin.net/forum/topic/1121864-some-phone-advice-please/
Share on other sites

From these, I would suggest the 920.

Jelly Beans has brought much needed improvements, but, at least for me, I won't get an Android, unless its a Nexus device.

Razr just has a phenomenal battery, nothing else on its list is impressive.

Moving to Windows Phone 8, you will have the familiar and improved experience.

  • Like 1

If you are already on Windows Phone, pick the Lumia 920. If you have purchased apps/games, you can install them on WP8. I've had the HTC Windows Phone 8X for more than a week now and I've been very pleased. I already love it :D

WP8 is a welcomed upgrade. The hardware (CPU, screen resolution and tech, etc.) is awesome. The performance is very noticeable coming from WP7. the voice control is still one of the best and the multitasking will improve a lot when more apps are updated to support fast resume and other WP8 features.

Like Muhammad said, Android has come a long way, but I wouldn't buy any phone that isn't a Nexus. The stock Android experience is really good. Between the SG3 and the Razr I would choose the SG3 because I think Samsung support for it's flagship devices is one the best of the Android OEMs. Also, the development scene is very active when it comes to Samsung phones.

You didn't mentioned it, but why not consider the Nexus 4? It is cheap and has Android in its stock form. I would choose this one after the 8X or the Lumia 920.

  • Like 2

Still can't get your hands on them in Aus. They're sold out.

Also, contracts in Aus let me buy pretty much whatever I want and not pay any more than the contract price.

I only bought one WP7 app, and it's a navigation app :p I tend to write me own stuff for WP7.

I'm really torn. I'm using Viber at the moment to harass a friend, and it's next to useless on WP7, but it's brilliant on Android. If I close the app after hitting send, it doesn't allow it to send and the message fails. I have to leave my phones screen on while I wait.

I wouldn't have that trouble with Android. It's that kind of stuff that's really getting to me :(

Thank you both for the advice, any other advice is welcome :)

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!