Recommended Posts

RAM: 1 GB

Processor: ARM Cortex-A8 OMAP3630 1 GHz

GPU: PowerVR SGX 530

It was right there in the first post...

Dayum, I must be going blind or something... thanks :laugh:

Yeap, I apparently missed it... thanks :pinch:

It looks very good. Too bad it didn't come out earlier, horrible timing.

Agreed, I love the design and the UI, both.

Hardware looks amazingly good. Software looks boring. nothing different from what other phone manufactures are doing (samsung et al) and could be a skin for android if i didnt know any better. The swipe feature is the softwares only saving grace. If this ran WP7 mango it would be almost perfect.

As opposed to boring rectangular tiles on the side of a screen?

Except for the fact that they're not boring plain tiles and most update with a good chunk of usefull information, even more so with Mango in a few months. Nothing is more boring than a grid of icons that just take up screen space with no other job than to start an app.

I'll take a grid of icons over some giant, flat squares with a boring white icon in the middle any day.

Which just tells me you have no clue about Live tiles and how they work or what they can do, even more so with mango.

Looks stylish and simple to use...but do we need Meego :)

[RANT] And did we really need to post all the videos and screenhots of every page on the webpage in the first post? Simple links would have sufficed! [/RANT]

smugcat.jpg

It's never late for open sauce.

It's still pointless to release a phone running MeeGo knowing that Nokia is switching to WP7. It's nice and all, but likely to remain the only Nokia MeeGo phone. What earthly reason do customers have to buy this instead of one of the many Android phones or WP7 devices or iOS devices? 'It's open source!' is not a valid reason for 99.9% of all potential customers.

The problem is that these Meego phones are going to be priced at the higher end. Look at the N8 as an example, I can buy it for 500euros right now but it's been out how long? The E7, 600euros. I mean these aren't even new last I checked. I'm sure this N9 will sell for 800euros brand new without some expensive contract which, in the end, you'll still have to pay 300-400euros for the phone.

Android got to where it is off of lower end cheap phones that are given away for free or basically for free with a contract.

It's still pointless to release a phone running MeeGo knowing that Nokia is switching to WP7. It's nice and all, but likely to remain the only Nokia MeeGo phone. What earthly reason do customers have to buy this instead of one of the many Android phones or WP7 devices or iOS devices? 'It's open source!' is not a valid reason for 99.9% of all potential customers.

But 'brand' is of value to a lot of customers, especially the hardcore Nokia ones, and on the other end of the spectrum, the un-knowledgeable ones that just replace the phone when they release the 'next' version of it. That's why I'm so confused by this move, a lot of people will buy this one and then expect something similar from N10 and I can bet any amount of money it'll happen and it'll be running MeeGo. As I said, horrible timing, they should have had this ready last year, then test it and definitely decide to go either full on Windows Phone, or invest in MeeGo (which has potential, especially with backing from someone like Nokia). I just don't see how they plan on supporting both, seems actually worse than ditching both Symbian and MeeGo and going WP only.

As it stands now, even if there are no new Symbian phones announced, they need to take care of the userbase (maintain the Ovi Store and services etc), but by introducing this one, they are actually obliged to take care of MeeGo, all the while working on introducing WP. So, right now they're basically having three OS's. Next year they'll maybe have just two. No wonder their CTO left the company, there's still no clear roadmap imo. Either they're flip flopping to see which one does better, or they're just doing the people who expected MeeGo a favor and releasing this one as 'hello and goodbye.'

But 'brand' is of value to a lot of customers, especially the hardcore Nokia ones, and on the other end of the spectrum, the un-knowledgeable ones that just replace the phone when they release the 'next' version of it. That's why I'm so confused by this move, a lot of people will buy this one and then expect something similar from N10 and I can bet any amount of money it'll happen and it'll be running MeeGo. As I said, horrible timing, they should have had this ready last year, then test it and definitely decide to go either full on Windows Phone, or invest in MeeGo (which has potential, especially with backing from someone like Nokia). I just don't see how they plan on supporting both, seems actually worse than ditching both Symbian and MeeGo and going WP only.

As it stands now, even if there are no new Symbian phones announced, they need to take care of the userbase (maintain the Ovi Store and services etc), but by introducing this one, they are actually obliged to take care of MeeGo, all the while working on introducing WP. So, right now they're basically having three OS's. Next year they'll maybe have just two. No wonder their CTO left the company, there's still no clear roadmap imo. Either they're flip flopping to see which one does better, or they're just doing the people who expected MeeGo a favor and releasing this one as 'hello and goodbye.'

Not really though since MS handles taking care of WP and the OS compared to Nokia having to take care of it like they do with Symbian and MeeGo. The only problem is the integrated Ovi Store that they're probably going to run, but I don't see it as a big problem in the end. Symbian and Meego development isn't exactly burning hot right now. All they really need to think about is hardware when it comes to WP and any services they add in, like their Maps for example, so that those work. That's really it, no more than any other WP OEM.

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

    • No registered users viewing this page.
  • Posts

    • BATorrent 3.0.2 by Razvan Serea BATorrent is a lightweight, open-source BitTorrent client built with modern C++ and Qt 6, offering a clean, fast, and privacy-focused alternative to traditional torrent apps. It supports magnet links, .torrent files, resume data, sequential downloading, per-file priorities, and even imports from qBittorrent. Power users benefit from integrated RSS auto-download with regex filtering, duplicate detection, and automatic tracker lists from Stremio. Streaming is seamless thanks to auto-detected players like VLC and IINA. BATorrent includes robust VPN tools—interface binding, auto-detection for WireGuard-based services like Mullvad and NordLynx, kill switch, proxy support, and IP filtering. A full WebUI enables remote control, while integrations with Plex, Jellyfin, and Emby automate library updates. With themes, speed scheduling, system-tray alerts, and cross-platform support for Windows, Linux, and macOS, BATorrent delivers a polished, high-performance torrenting experience. BATorrent features: Core .torrent file and magnet link support Resume data — picks up where you left off after restart Import torrents from qBittorrent Create .torrent files from any file or folder Sequential download mode Per-file priority control (skip, low, normal, high) Seed ratio limits with auto-pause DHT, PEX, UPnP, NAT-PMP RSS Auto-Download Subscribe to RSS feeds — automatically download new torrents as they appear Regex filters — match only what you want (e.g. 1080p|720p, S01E\d+) Per-feed settings — custom save path, check interval (5–1440 min), enable/disable Auto-download — matched items are downloaded automatically in the background Supports magnet links, .torrent URLs, and tags Tray notifications when items are auto-downloaded Duplicate detection — never downloads the same item twice Stremio Stremio Addon System pre-installed — works out of the box Auto tracker list from ngosang/trackerslist Streaming Play while downloading — stream video files before the download is complete Supports mp4, mkv, avi, mov, wmv, flv, webm, m4v, ts Auto-detects installed players (VLC, IINA, system default) VPN & Privacy Interface binding — lock torrent traffic to a specific network interface (e.g. tun0) Auto VPN detection — identifies VPN interfaces (tun, tap, WireGuard, Mullvad, NordLynx, ProtonVPN) Kill switch — automatically pauses all torrents if the VPN interface drops Auto-resume — resumes only the torrents paused by the kill switch when VPN reconnects Proxy support — SOCKS5 and HTTP proxy with optional authentication IP filtering — load P2P blocklists to block unwanted IP ranges Protocol encryption (enabled / forced / disabled) WebUI Remote management — control torrents from any browser at http://localhost:8080 REST API with JSON responses Add torrents via magnet link or .torrent upload Pause, resume, remove torrents remotely View peers and files per torrent Dark theme matching the desktop app HTTP Basic Auth with SHA-256 password hashing Configurable port and remote access (localhost vs 0.0.0.0) Interface 3 themes: Dark, Light, Midnight (bat/vampire aesthetic) Real-time speed graph Detailed panel with tabs: General, Peers, Files, Trackers Filter bar: search by name, filter by state (Active, Downloading, Seeding, Paused, Finished) Drag & drop .torrent files and magnet links Drag & drop reorder in torrent list System tray with notifications (download complete, kill switch events, RSS auto-downloads) Splash screen with bat animation Bilingual: English and Portuguese (BR), auto-detected from system locale Bandwidth Scheduler Alternative speed limits — set different download/upload limits on a schedule Time range — configure active hours (e.g. 01:00 to 07:00), supports overnight ranges Per-day control — choose which days of the week the schedule applies Automatically switches between normal and alternative speeds Media Server Integration Plex — automatically trigger library scan when a download completes Jellyfin / Emby — same automatic library refresh via API Configure server URL and authentication token/key in Settings System Cross-platform: Windows, Linux, macOS Auto-shutdown — automatically shut down PC when all downloads complete (60s cancellable countdown) Auto-update system (AppImage on Linux, installer on Windows, DMG on macOS) CLI arguments: pass .torrent files or magnet: URIs directly Keyboard shortcuts: Space to toggle pause, Ctrl+A to select all, Ctrl+O to open BATorrent 3.0.2 changelog: Phone pairing & WebUI The browser WebUI was reskinned to match the desktop app — same dark palette, Inter font, flat surfaces, the real BATorrent logo (it was a random bat before), and a proper magnet icon. It now looks like the same product, not a separate dashboard. Pairing is one tap and zero typing: the generated WebUI password is now copyable, and the QR code carries the credentials — scanning it from your phone logs straight in (no typing the IP or password), then drops the credentials from the address bar. Search Two new providers: RuTor (CIS sources, no login, via a public TorAPI relay) and Torrents-CSV. Results are sorted by seeders (healthiest first), and each search now times out after 15 s so one dead provider can't hang the UI. Files & trackers Per-file priority is back: right-click a file in the detail panel to set Skip / Low / Normal / High. Rename an individual file inside a torrent (double-click or the file menu), separate from renaming the torrent. Remove a tracker from a torrent (the ✕ on a tracker row); adding was already there. Smart Paste on Ctrl+V — paste a magnet, a 40-char info-hash, or a .torrent URL straight from the clipboard and it's added immediately (text fields still paste text normally). Covers & titles Anime fansub naming ([Group] Title - NN) now resolves to the right show. Audio channel layouts in titles (DDP5.1, 7.1, …) are stripped so they don't pollute cover matching. Under the hood The legacy QWidget interface is gone. QML had been the only UI since 3.0.0 (reachable old code lived behind a hidden --legacy flag); with parity confirmed, the entire QWidget layer — main window, every dialog, the theme manager — was removed (~13,400 lines). The four restored actions above were features that backend already supported but the QML port had never wired. macOS: the WebUI password hash moved out of the keychain into app settings, so launching the app no longer pops a login-keychain password prompt on unsigned builds. The actual password still lives in the keychain. Cleanup: ~400 orphaned translation strings and a batch of dead code removed; internal duplication collapsed; an ARCHITECTURE.md added for contributors. Unit / security / memory tests and the ASan/UBSan/TSan sanitizers stay green. Download: BATorrent 3.0.2 | 30.5 MB (Open Source) Download: BATorrent Portable | 42.3 MB Links: BATorrent Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How about a global switch to turn the awful things off instead of a registry hack? Then everyone wins.
    • This doesn't strike me as so shocking when... " IT admins do have some control over this rollout. If they choose to opt out, devices in their tenant won't automatically get the dreaded Copilot app"
  • Recent Achievements

    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      257
    3. 3
      Skyfrog
      79
    4. 4
      ATLien_0
      60
    5. 5
      FloatingFatMan
      60
  • Tell a friend

    Love Neowin? Tell a friend!