Android and wp8


Recommended Posts

Now that I'm pretty much an android convert, I wondered how the community felt about windows phone 8, more specifically the lumia 920. When I went to AT&T for my Android device they pretty much shoved the 920 down my throat. While I'm sure it's a great device, I'm just curious what android loyalists think about it.

Link to comment
https://www.neowin.net/forum/topic/1122032-android-and-wp8/
Share on other sites

Personally i'm not keen on the Metro style interface used on Windows Phone devices, i have tried to like it however it just annoys me and feels dull / lifeless in my opinion.

There is nothing wrong with Windows Phone, i'm sure some pretty good devices exist, however its just not for me.

I like the freedom you get with Android devices to customise all aspects of the os, flash custom roms and generally tinker / customise the phone as much as you want.

I might be sorry I asked, but but what is switching rom's?

You can flash a different rom to your phone, this could be a newer version of Android, add new features that were not present in the manufacturers rom for your phone or totally change the look and feel of your phone.

A great custom rom for various Android devices is MIUI.

You can flash a different rom to your phone, this could be a newer version of Android, add new features that were not present in the manufacturers rom for your phone or totally change the look and feel of your phone.

A great custom rom for various Android devices is MIUI.

Very interesting. I have a Nexus 4 and a Nexus 7. What would the benfit of using that ROM on my phone or tablet be? Aesthetics? speed?

Very interesting. I have a Nexus 4 and a Nexus 7. What would the benfit of using that ROM on my phone or tablet be? Aesthetics? speed?

Both, generally those are the main things the devs aim for, along with removing bloatware and improving stability etc

XDA Forums is a great place for custom ROMs

Very interesting. I have a Nexus 4 and a Nexus 7. What would the benfit of using that ROM on my phone or tablet be? Aesthetics? speed?

Both, generally those are the main things the devs aim for, along with removing bloatware and improving stability etc

XDA Forums is a great place for custom ROMs

I think +pat already has the newest and best functionality from his devices, as they're recently released by Google with the newest available software.

Of course there are some bugs, but the dev community has nothing better for him at the moment, unless he wants to root his device.

Anyway, as he does not even know that rom is, I don't think he can benefit from that at this moment.

Also, I have a Galaxy Note 2 and Samsung has done a great job with software now, very sophisticated and closed, and it is getting harder for the dev community to improve that, competing with a huge company with billions to invest and resources to offer, compared to a group of independent devs.

I'm not really dismissing the indie dev community, but it is just that I feel they are losing appeal ATM. :)

I think +pat already has the newest and best functionality from his devices, as they're recently released by Google with the newest available software.

Of course there are some bugs, but the dev community has nothing better for him at the moment, unless he wants to root his device.

Anyway, as he does not even know that rom is, I don't think he can benefit from that at this moment.

Also, I have a Galaxy Note 2 and Samsung has done a great job with software now, very sophisticated and closed, and it is getting harder for the dev community to improve that, competing with a huge company with billions to invest and resources to offer, compared to a group of independent devs.

I'm not really dismissing the indie dev community, but it is just that I feel their losing appeal ATM. :)

I have an ASUS Transformer and their own stock ROM was buggy and almost unusable, XDA ported JellyBean and is easily the best experience I have had since getting my tablet, 100% bugs that ASUS failed to fix, XDA fixed

I have an ASUS Transformer and their own stock ROM was buggy and almost unusable, XDA ported JellyBean and is easily the best experience I have had since getting my tablet, 100% bugs that ASUS failed to fix, XDA fixed

Yes, but the Transformer is not so new compared to his Google branded cutting-edge devices.

Maybe I'm actually arguing towards Samsung's and Google's newer devices.

Yes, but the Transformer is not so new compared to his Google branded cutting-edge devices.

Maybe I'm actually arguing towards Samsung's and Google's newer devices.

:) I wasn't trying to argue or disprove anything you said, just commenting my experience with XDA, stock is probably great for most people, just nice to have devs when you need them like in my case

I flashed a custom ROM to my Lumia and fairly quickly returned to stock, stock was a much nicer experience

Very interesting. I have a Nexus 4 and a Nexus 7. What would the benfit of using that ROM on my phone or tablet be? Aesthetics? speed?

I wouldn't recommend using custom ROMs on your Nexus devices, at least not at this time. Custom rom makers have yet to sync their roms with the latest Android versions, the Cyanogenmod team has barely even started working on CM10.1 and so does MIUI, you may use a 'tweaked' version of your stock rom or any rom based on the stock images but shall you use an other roms you'll be facing some nasty bugs especially considering that the Nexus 4 is a rather new device. There is hardly even any performance difference between stock Android 4.2 and other aftermarket roms.

:) I wasn't trying to argue or disprove anything you said, just commenting my experience with XDA, stock is probably great for most people, just nice to have devs when you need them like in my case

I flashed a custom ROM to my Lumia and fairly quickly returned to stock, stock was a much nicer experience

Yeah :) I was on CM9 on my note 1 and then Samsung catched up with real nice features and I came back. But indie devs are much faster on fixing small bugs. I'm also glad they exist and manage to spare their time even if they don't get any money for that. ;)

I love WP8 as a mobile OS. I think it's a great alternative for people who are looking to buying an iPhone. Personally, neither WP8 or iOS cater to my needs, and Android has introduced me to certain features that I now can't live without.

I wouldn't recommend using custom ROMs on your Nexus devices, at least not at this time. Custom rom makers have yet to sync their roms with the latest Android versions, the Cyanogenmod team has barely even started working on CM10.1 and so does MIUI, you may use a 'tweaked' version of your stock rom or any rom based on the stock images but shall you use an other roms you'll be facing some nasty bugs especially considering that the Nexus 4 is a rather new device. There is hardly even any performance difference between stock Android 4.2 and other aftermarket roms.

I might agree with you if you're talking big custom rom makers like CM and roms based on CM, but in most cases rom devs start making from AOSP source as soon as it's dropped. Most of these devs are also able to fix bugs before Google releases a new update (ie the December bug) and are able to add new little features without detracting too much from being an AOSP rom. Bottom line is there are plenty of reasons to use a custom rom on Nexus devices, though maybe not something like CM right away.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • it would've been better to just have a screenshot with claude running instead of using a generic thumbnail that doesn't fit the narrative.
    • Helium Browser 0.13.2.1 by Razvan Serea Helium is a private, fast, and honest Chromium-based web browser — built for people, with love. It offers the best privacy by default, unbiased ad-blocking, and a clean experience free from bloat and noise. Proudly based on Ungoogled-Chromium, Helium removes Google’s clutter while keeping a fast, efficient development pipeline. With thoughtful touches like native !bangs and split view, Helium is a people-first, fully open-source browser that puts control back in your hands. Privacy, security, and control come first. Ads, trackers, and third-party cookies are blocked automatically, HTTPS is enforced everywhere, and all Chromium extensions work seamlessly — while Google can’t track your activity. Helium’s 13,000+ offline-ready !bangs let you jump straight to sites or AI tools like ChatGPT instantly. Open-source, people-first, and unbiased, Helium delivers a browsing experience that’s fast, secure, and free from noise, ads, and compromises. Helium Browser key features: Performance Fast, efficient, and lightweight — built on Chromium’s optimized engine. Energy-saving and consistent — stays fast over time without slowing down. No bloat — stripped of unnecessary components for maximum speed. Minimalist interface — compact, clean, and distraction-free. Customizable toolbar — hide elements you don’t need. Smooth and stable — no flicker, lag, or animation glitches. Comfort-focused experience — intuitive and unobtrusive. Privacy & Security Best privacy by default — blocks ads, trackers, phishing, and third-party cookies. Unbiased ad-blocking — powered by community filters and uBlock Origin. No telemetry or analytics — zero background web requests on first launch. Strict HTTPS enforcement — warns for insecure sites. Passkeys supported — modern authentication made simple. No built-in password manager or cloud sync — your data stays yours. Extension Compatibility Full Chromium extension support — including MV2 extensions. Anonymized Chrome Web Store requests — Google can’t track extension installs. Extended MV2 support — maintained for as long as possible. Smart Features Native !bangs — browse faster using 13,000+ offline-ready shortcuts. AI integration — use !chatgpt and others directly from the address bar. Offline functionality — bangs work without an Internet connection. Philosophy People-first design — open source, transparent, and community-driven. No ads, no noise, no bias — privacy and honesty over profit. Helium Browser 0.13.2.1 changelog: 6b6fbd0f revision: bump to 2 (#1907) cb3f77bd helium/ui/zen: fix cmd+s shortcut sidebar preference in zen mode (#1849) e3980159 deps: bump onboarding (#1905) c99531d5 helium/core: add an option to copy URLs from tab context menu (#1904) c1aba0ea helium/search: add kagi image search params (#1899) eb6711f4 helium/core/hibernate: add an option to hibernate other tabs (#1901) 425306f5 merge: update to chromium 149.0.7827.102 (#1897) ae94c3c8 helium/core/update-pref: improve auto updates strings (#1896) 06897c1d patches & domain_substitution: refresh for chromium 149.0.7827.102 d09826d0 merge: update ungoogled-chromium to 149.0.7827.102 9aeb58da helium/search-engine: reject default engine urls without %s (#1893) 4d7bb965 Update to Chromium 149.0.7827.102 fa67665c i18n: fix "add shortcut" string collision (#1891) 6894bd30 devutils/i18n: parse meaning into source.gen.json dc3fe739 helium/kb-shortcuts: disambiguate "Add shortcut" string cbf38eb4 i18n/apply: pass meaning to fingerprint generator 53ea9920 extra/disable-jit-flag: build drumbrake only if supported Download: Helium 64-bit | Portable 64-bit |~100.0 MB (Open Source) Download: Helium ARM64 | Portable ARM64 Links: Helium Home Page | macOS | Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • ExplorerPatcher 26100.8457.70.2 by Razvan Serea ExplorerPatcher is a versatile and free tool that allows you to tweak and enhance the Windows Explorer. It comes with a range of useful features, including the ability to add new context menu items, change file name colors, and enable hidden features. Feature summary Choose between Windows 11 or Windows 10 taskbar (with labels support, small icons and lots of customization). Disable Windows 11 context menu and command bar in File Explorer and more. Open Start to All apps by default, choose number of frequent apps to show, display on active monitor and more. Choose between the Windows 11, Windows 10 and Windows NT Alt-Tab window switcher with customization. Lots of quality of life improvements for the shell, like: Skin tray menus to match Windows style, make them behave like flyouts and center them relative to the icon. Choose action when left and/or right clicking the network icon. Revert to the Windows 7 search box in File Explorer, or disable Windows Search altogether. Disable immersive menus and use mitigations that help you run the real classic theme without glitches. Discover the program's full range of features by reading this wiki article. ExplorerPatcher 26100.8457.70.2 changelog: Tested on OS builds 22621.4317, 22631.7079, 26100.6899, 26100.8037, 26200.8246, 26200.8457, 26300.8493, and 28000.2113. TIP: Windows Defender no longer flags ExplorerPatcher. It is no longer needed to configure Defender exclusions. Enjoy! Important Fixed Windows 10 taskbar and Start menu crashes on builds 26220.8474 (Beta) and 26300.8493 (Experimental). Update ExplorerPatcher as soon as possible. Without this update, Explorer and the Windows 10 Start menu may stop working on future builds. Microsoft removed Windows 10 Start menu components from StartTileData.dll on these builds, so the Windows 10 Start menu option has been removed where it is no longer supported. Temporary workaround: replace C:\Windows\System32\StartTileData.dll with the version from build 26xxx.8457 (x64/ARM64). This may stop working in future builds. Work is ongoing to restore Windows 10 Start menu support. Highlights Fixed Windows 10 battery flyout crashes on build 25951+. Network flyout buttons reverted to pre-24H2 behavior as a side effect. Taskbar location changes now apply instantly. Windows 11 taskbar auto-hide is no longer modified when Explorer starts. "Open Start in All apps by default" is now hidden when using the new Windows 11 Start menu. Fixed Windows 10 Start menu crashes on builds 21996–22000.51. Fixed Regedit crashes when switching to thumbnail view in registry import/export dialogs. Improved compatibility with recent Windows builds, including 26H1 ARM64. Improved ARM64 performance. Added Greek translations. ep_taskbar Now supports all 43 Windows 11 languages. Fixed issues in the system tray and other components. Updated DLL naming scheme for mod developers. Improved TrayUI compatibility and vtable stability on builds with multiple ITrayUI revisions. Fixed a taskbar initialization deadlock. Windows 10 Start Menu Added a new tile layout engine to restore support removed in build 26xxx.8474. Restoration is currently partial: Tiles may overlap when pinned using "Pin to Start". Restarting StartMenuExperienceHost.exe or explorer.exe fixes the layout. Further improvements are planned. Other Changes Added an executable blacklist to prevent shell extensions from loading in selected applications. Updated Windows 10 Start menu animation support for ARM64 builds 28xxx.2149+. Please consult the README for more details. Download: ExplorerPatcher 26100.8457.70.2 | ARM64 | ~11.0 MB (Open Source) View: ExplorerPatcher Home Page | Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft: Windows 11 KB5094126, KB5093998 finally stops trusting a critical system threat by Sayan Sen This week Microsoft released the Patch Tuesday updates for June 2026 with KB5094126 on Windows 11 25H2, 24H2, and KB5093998 on Windows 11 23H2. On Windows 10 22H2 it's under KB5094127. Alongside the announced release notes for the new builds, Microsoft has revealed another change that is coming to Windows with these new releases. It has been confirmed that custom folders are getting a significant change with the June 2026 updates as such folders or folder names defined by desktop.ini will no longer appear after this update is successfully installed. While you may inititally think this is a bug with the new release, Microsoft has stated that this is in fact "expected behaviour" in its new support article regarding this which Neowin spotted today while browsing. Essentially it's a security hardening measure such that custom folder presentations are treated as potentially unsafe whenever Windows is not sure about their origin and whether that desktop.ini folder can be trusted or not. Here is list of such untrusted files and folders: Files downloaded from the internet that carry Mark-of-the-Web (MOTW). Files copied from certain remote locations, such as some WebDAV or HTTP-based locations. Files on network paths that are not classified as intranet or trusted by zone policy. For those who may not be familiar, Desktop.ini is a special configuration file used by Windows to customize the appearance and behavior of individual folders. Basically Windows can read specific instructions stored in Desktop.ini instead of displaying every folder with the same default settings. This can be used to apply custom icons, thumbnail images, localized folder names, and such informational tooltips (infotip). The file can also influence certain folder-specific behaviors and properties. It is typically stored as a hidden system file within a folder that has been designated to support Desktop.ini customization. However, because Windows Shell automatically reads and applies these attributes whenever a customized folder is opened, they have historically (since the Windows XP days) presented an attack surface as a result of an unchecked buffer in the Shell component responsible for extracting custom attributes from Desktop.ini files. As such an attacker could create a specially crafted Desktop.ini containing a malicious or corrupted attributes and place it on a network share. So if a user were to browse that folder, Windows would automatically process the file, potentially triggering a buffer overflow. This could allow arbitrary code to run with the same permissions as the logged-in user. Hence a seemingly harmless folder could become a security risk when their contents are not properly validated. For admins and users alike looking to manage this behaviour, Microsoft has shared a few ways. One of them is to assign a trusted mark on the folder in case you are sure of its source. Secondly a policy can be used to revert back to the previous state. Finally, the MOTW can be removed too to indicate to Windows that this is a safe file. The company explains: Option 1: Add the source to Trusted Sites (Recommended) If the affected content is stored on a known internal or managed source, add that source to the Trusted Sites list. Once the source is treated as trusted, Windows processes desktop.ini from that source normally. This keeps the protection in place for other locations and is the lower-risk option. Option 2: Use policy to restore previous behavior Organizations that need broader compatibility can enable the policy Allow the use of remote paths in file shortcut icons.Enabling this policy restores the pre-June 2026 behavior for affected remote or untrusted scenarios. Option 3: Check for and remove the Mark of the Web (MotW) If the desktop.ini file has a Mark of the Web (MotW), Windows may treat it as coming from an untrusted source and block customization. Verify whether MotW is present and, if appropriate, remove it from the desktop.ini file. This can restore expected behavior, but should only be done for trusted content, as it removes the associated security protection. To remove the MotW tag, open PowerShell and run one of the following commands: For a single desktop.ini file: Unblock-File "C:\Your\Folder\Path\desktop.ini" For all desktop.ini files in a folder: Get-ChildItem "C:\Your\Folder\Path" -Recurse -Filter desktop.ini -Force | Unblock-File Microsoft has warned though against using a broad opt-out using the provided policy as it reduces protection against potentially malicious remote folder-customization content. As such the tech giant recommends trusting only controlled internal sources and keeping trust settings as strict as possible. You can check out the official support article here on Microsoft's website.
    • LAV Filters 0.82.0 by Razvan Serea LAVFSplitter is a multi-format media splitter that uses libavformat (the demuxing library from ffmpeg) to demux all sorts of media files. LAV Splitter is a Souce Filter/Splitter required to demux the files into their separate elementary streams. LAV Audio and Video Decoder are powerful decoders with a focus on quality and performance, without any compromises. Supported Formats: MKV/WebM, AVI, MP4/MOV, MPEG-TS/PS (including basic EVO support), FLV, OGG, and many more that are supported by ffmpeg! LAV Filters are based on ffmpeg and libbluray and is aimed to offer a all-around solution to perfect playback of file-based Media as well as Blu-rays. LAV Filters 0.82.0 changelog: LAV Splitter NEW: Support for demuxing Dolby Vision Enhancement Layer streams NEW: Support for Animated WebP images Changed: When demuxing Blu-ray discs, Dolby Vision metadata is available on the primary video stream LAV Video NEW: Support for Animated WebP images Changed: Hardware decoding support for DVDs has been removed Download: LAV Filters 0.82.0 | 15.5 MB (Open Source) View: LAV Filters Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      PsYcHoKiLLa
      207
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      79
  • Tell a friend

    Love Neowin? Tell a friend!