Jump to content

dwallersv

Members
  • Content Count

    901
  • Joined

  • Last visited

Community Reputation

1 Neutral

About dwallersv

  • Rank
    Addict

Profile Information

  • Your Current Device(s)
    Omnia
  1. Yeah, yeah, yeah, there are always transition pains. It's like moving to a foreign country and having to learn new customs. Frustrating and uncomfortable at first, but as you figure things out, it gets better and better. I'm two weeks in now with my Epic 4G. I love it. I agree that there are plenty of youthful pimples and blemishes on the young Android system -- chief irritant to me the lack of BT voicedialing support in Eclair (implemented in Froyo, coming soon to the Epic), but I have not found anything yet -- nothing -- that I couldn't find a solution for. And in balance, I'm happier with the platform. BIG pluses: Fast and smooth. Apps are cheap cheap cheap from the Android Market (like generally 10-20% of what winmo apps cost) The graphics engine is phenomenal -- game graphics are mind-blowing, comparable rendering to the PS2 and XBOX And games -- the multitouch screen makes it possible to have usable controls and actually play a FPS or driving game. Nova (FPS) is like having Halo on your phone; Asphalt 5, included, is spectacular. Some things work better than winmo -- bt sensing and connections are more reliable. I get tired of having to constantly re-enable A2DP for BT devices as I switch around to different ones. Finally, and more important, it lives up to the Open Platform promise, just like Winmo, and in some ways even better. I've "rooted" my phone now, am running a custom kernel, and it's really cool that kernels and "ROMs" can be mixed and matched. Got a nice environment you like, but someone's created a kernel that fixes or optimizes something? In most cases, load it up, without losing your setup. Because of its "youth", Android is going to have some kinks compared to Winmo. That's quickly being mitigated.
  2. Been a WM devotee going all the way back to my TREO 700, right after it was released. I've heavily hacked, customized, written apps, and on and on. The flexibility of the open platform, leading to the very active user community, and the wide spectrum of 3rd party apps kept me snickering at iPhone lunkheads for years. I abandoned WM last week for a Sprint Galaxy Epic 4G (a.k.a. the Galaxy S Pro). Should have done it months ago. Android on Linux is the future of the Smartphone market. WP7 is MS's attempt to duke it out with Apple for the iPhone-type user, and will probably fail, iPhone has such a big headstart. Yet, one is reminded of Macintosh, eventually overwhelmed by Windows. So who knows. Regardless, for the folks that frequent these forums, Android is the way to go. WM will not get any more meaningful dev from MS, app developers are switching their efforts to Android, so waiting if you don't have to is just masochistic.
  3. The writing's on the wall. Microsoft iPhone looks to be, well, as much of a steaming pile of **** as the Apple iPhone. So, WM is dead, and so is all the hacking and customization. I've been a loyal, happy Omnia fan for over two years. First the i910, then the i920. My daughter's going to love her hand-me-down Omnia II. I've made the leap -- got a Galaxy Epic 4G last week. After nearly a week of using it (an customizing it, and "rooting" it, and starting up the learning curve to hack, build ROMs, etc.), I can say I should have done it sooner. Andriod is simply "da bomb". Big time. I've found a solution so far either as a hack, or (mostly) in the Android Market to every bit of functionality I need... Microsoft RDP client to manage/control my PC at home, and all sorts of other things I feared I'd have to live without for awhile while the Andriod market grows. I was wrong. It's grown. Even TouchWiz on the Epic is good enough to be more than usable -- it's a suitable substitute for MS3 on my OmniaII. The native browser kicks major buttocks on Opera... scads faster, can open multiple pages at once without killing the OS, renders better, fewer bugs, problems. A lot more RAM, slide-out kbd, Swype, and of course, the capacitive touchscreen -- my God, I had no idea how much better that technology is just in terms of accuracy and smoothness, not to mention the nice feature of multitouch. As for MS3 v. Andriod, well, all I can say for the latter is, "there's a widget for that". And for the former, "no, usually there isn't". Oh, and of course, there's 4G!! 6Mbps down, measured. 1.5Mbps up. WHOAH... Anyone here familiar with me knows I'm a big Omnia fan, and a contributor to these forums. So, don't take any of this as slagging on the Omnia/II. They're great machines. However, a few days with Linux and Android make the indisputable case that WM is a dated OS simply not up to the task of managing the full-PC resources and capabilities of modern HPC hardware, and the S/W implementation is similarly old-school, requiring lots of retrofitting to make it decent. Hence the hundreds of $$ I've spent on third-party apps and tools to get the most out of my Omnia/II. A great deal of what I spent to retrofit my WM phones is, well, just there on Andriod. I made the leap, couldn't be happier, and won't be looking back. Best wishes to you all, and see you around when you come over to the dark side... :)
  4. Well, there's "support", and then there's "support" :-) Orb can stream in a variety of formats, with varying resolution, quality, and UI experience. Streaming WMV produces the best results. Streaming RDP is probably the worst. So, I was hoping there was another Orb user here that could comment with some detail on streaming to a Galaxy as a client.
  5. Anyone here an Orb Media Server user, and have any feedback on the Galaxy S as a client with Orb? I stream from my Orb server to CorePlayer on my Omnia II, and need to know that there is a good solution for this on the Galaxy S before I make the leap. Thanks!
  6. Sorry for the simpleton question, but I couldn't find anything by searching. I'm going to try out a Galaxy Epic from Sprint, leaving behind my VZW Omnia II. How do I transfer all my pim DBs (calendar, tasks, contacts, etc.) from the Omnia to the Galaxy? Thanks!
  7. Me too... at first it was just the taskbar and menu bar at the top and the bottom -- annoying, but the main window area of the screen was still active with SPB shell... I added a new email account (started a new job), and now the entire app pops up constantly in the middle of doing things. It's obviously a notification issue. Anyone know how to shut off new mail notifications completely? I think this would solve the problem, and as I have indicators on my home screen for that anyway, I'd be fine with it off.
  8. I don't like the simple orange boot screen image that comes with the i920, so I did a quick search online and found a more attractive (to me) replacement, cropped and scaled it to size. Here it is... to use this, simply copy this file to \windows on your i920 (you will have to use Resco Explorer, Total Commander, or some other file manager that will copy over ROM files). Enjoy.
  9. While the complaint subject of this thread is absolutely valid, and every frustration people have voiced are shared by many (including myself), there are some workarounds that can be employed in the mean time to improve the situation, while we wait (in vain, IMO) for Samsung and/or Verizon to address the issue. Before I get to the ways to help this situation, a few comments on the technical details here. As some have discussed, the phone does indeed have a 256MB RAM chip in it. Also, as some have suggested, a portion of this is consumed by other operation "parts" of the device, and so are unavailable. Among them are the graphics hardware, the camera, the FM radio, and then a portion set aside by the WM kernel that is not a part of the free RAM pool for satisfying process memory requests. After all this is accounted for, the operating system is left with a residual amount of "free" RAM for running processes, around 148MB. However, there are a set of essential processes that must run after the initial OS boot -- among them various drivers, for example -- and these eat up a chunk of that 148MB of working RAM as the device finishes booting. As a result, when fully booted, there will usually be only around 70-75MB RAM left. Then, from this the non-essential stuff starts up (like TouchWiz, for example), and when all is said and done, you're usually left with around 50MB to run your own optional programs in. From here it only gets worse. Because of WM's primitive memory management system, it's quite possible (and easy) for free memory to become "trapped" in a way that makes it unusable by a new request from a running process. This is not the infamous WM6 memory leak... This is a by-design flaw in the way the memory system works in WM that dates back to when WM-based devices were much, much simpler, had far less processing power, RAM, ROM, and other resources, so this design actually served a real purpose, where code footprint was the design constraint more than anything else. Those old WM devices worked pretty well for what they were asked to do. Now we are asking these devices to, in essence, meet the performance, abilities, and flexibility of a desktop PC of just 5 years ago or so, without a sophisticated operating system underneath that has the capability to meet these demands (this is one reason why, running linux, droid phones can do so much of this so much better). So, this is why 50MB of free RAM, which would seem to be more than enough to run a program only demanding 10MB, cleanly and with all the performance the hardware is capable of -- yet falls flat on its face in this circumstance. It gets worse. Depressingly so. In order to deal with this shortcoming of WM, Samsung added a memory management subsytem that tries to keep free memory above about 40MB. It's a very crude and blunt instrument too -- as everyone has experienced, this memory monitor will, without notice, simply shut down applications, sometimes even the foreground application you are using right in front of your face, to get free memory back above this threshold. Apps will be closed without saving work, any warning or notice. To me, this is the single biggest "crime" Samsung has to answer for in this whole debacle, as the design as is is completely indefensible, harmful to the user, and most of all is the single easiest thing they could invest some effort into vastly improving. But they won't. So, what can we do, given what we have, to maximize the utility, performance, and experience with this phone? Thankfully, there are several things that, some or all, will make things markedly better. Not as good as a true fix -- bump the RAM up to 512MB -- but have made a very significant difference for me: Turn off TouchWiz. Disable and don't use Today if you use a third-party shell, like SPB Mobile Shell (or any of a plethora of others). Most people don't need Today if they are using another shell. Even if you do need Today (as I do, for hosting WeatherPanel), get SecondToday and use that instead of the built-in Today; unlike the latter, SecondToday is a regular process that can be shutdown/closed while the built-in Today can't, so whe you need memory to run something else, you can get it by killing SecondToday, and then restarting it later when you want it. This works well with my scripts for freeing memory, discussed below. To disable Today, set the following value in the registry and reboot: HKLM\Software\Microsoft\Today\Enabled->0 Use Chainfire's AutoClose patch to improve Samsungs awful free-memory monitor. This one is essential -- it will nearly completely solve the annoying problem of things autoclosing all the time, and being virtually unable to run more than one or two applications at a time. Unfortunately, it doesn't fix the fundamental problems with the WM memory management system, so, depending on the app, performance will suffer (for example, apps like Opera which are memory pigs and do a lot of dynamic allocation/deallocation will be poor performers when free memory gets below 25-30MB). With this patch installed, and the "agressive" version of the registry settings, you will even bump up against WM6's native memory manager trying to close an app now and then, which is much more graceful than Samsungs (it gives you notice, and let's you choose what to close). Use my mortscript process manager to free up memory for application memory hogs. I've attached zip with a set of scripts I use to launch the worst memory hogs, so that they can run with as much memory as possible, and therefore get as much performance out of the device as possible. It works well for me, the tradeoff being that app startup and shutdown are slower, but if you're willing to live with that little bit of a wait, you'll benefit. Basically what these scripts do is manage the whole app shutdown/restart aspect of memory management in a controlled way, rather than the crude "bull in a china shop" manner of Samsung's memory manager, and the somewhat better WM memory manager. Here's the concept: I usually have things running all the time that consume memory, that are of no consequence to stop and then restart later when I want to run a memory hog. Examples are SecondToday, hosting WeatherPanel, and SPB MS. Between these two processes, they usually eat up something like 20-25MB. So, when I want to use Opera, a memory pig, killing off these other two processes has a huge benefit. Opera runs fast and smooth with all that free memory. When I'm done with Opera, I can simply restart these other programs, and nothing's been lost in terms of my usage, except for a little wait time. The script "RunSpecial.mscr" automates this process, in tandem with a script for the target application that is used to start the app rather than the direct link. You create a script for each "pig_app" you want to maximize RAM for, then edit the shrtcut for it in \Windows\Start Menu\Programs to point to the customized script instead of the original executable. By way of example, for Opera, the original shortcut pointed to \My Storage\Program Files\Opera Mobile 10\Opera-armv4i.exe the location where I have Opera 10 installed. I modified this to point to \Scripts\Opera10.mscr then created a script of that name in that location with the following code: shell="\Program Files\SPB Mobile Shell\MobileShell.exe" today2="\Program Files\SecondToday\SecondToday.exe" target="\My Storage\Program Files\Opera Mobile 10\Opera10-armv4i.exe" CallScript("\Scripts\RunSpecial.mscr", target, shell, today2) The syntax for calling RunSpecial allows for as many "shutdown" processes as you want, ending with the target app to run. RunSpecial will kill off all the processes that you designate are "unnecessary", run the target app, and then when you exit the target app, the other programs are automatically restarted. Since I didn't develop these scripts with others in mind, they're not flexible in terms of location. You have to create a directory \scripts, and put them there. Feel free to modify them at will to meet your own needs. Also, they require Mortscript to work. You can get that here. This all may be too much of a pain for some -- in which case, don't use it. As I said, it works well for me, makes my use of opera fast as without frustration (as well as some other apps I have employed this with). Finally, retargeting the shortcuts for apps will screw up your icons. There are a variety of ways to fix this, the cheapest (free) being more technically challenging. Easier is to get something like SK Shortcut Manager, which makes it easy to set the icon for a shortcut.
  10. Just to make sure everyone's clear on this: The O2 has no backlight. AMOLED displays generate light directly. So, unlike an LCD display that can be viewed (poorly) without a backlight on, when the AMOLED display is in an equivalent "off" state it is truly off -- there is no visual information available to see at all. The dim "backlight off" state on the O2 is simply a low-brightness state simulating an LCD display with the backlight off. In any meaningful sense, it's still on, drawing power.
  11. URGENT: Bug in the original AutoJack.mscr script -- after window wait times out (1 hr as written), the script will give and error and terminate. Attached is the fixed script, unzip and replace \Scripts\AutoJack.mscr with this one. Reworking the installer as we speak, and will be updating it in post#1 shortly. Also improving the installer to detect Mortscript installation and automatically skip if unnecessary. AutoJack.zip
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.