Overlooked Mobile Application Testing Condition - Testing

Testing iOS and Android software presents unique challenges that require unique test conditions.
Testing iOS and Android software presents unique challenges. As easily portable devices, smartphones and tablets are used in a variety of settings, and wireless connectivity may widely fluctuate and acutely affect the performance of any applications in use. Unlike with PCs that have wired connections, dev/test teams cannot assume relatively stable network conditions when crafting a mobile game, messaging client or news reader.
Moreover, despite enormous leaps forward in CPU and GPU design since the iPhone’s debut in 2007, mobile hardware still is considerably less capable than desktops or laptops, especially when it comes to device memory. In practice, this can means suboptimal performance when working with mostly interpreted languages such as JavaScript (in contrast, PCs often have RAM to spare and can accordingly overcome flaws in language design), as well as frequent crashes.
Still, the difficulties of have not discouraged shops from trying their luck. There are more than 1 million apps in both the Apple App Store and Google Play, and Microsoft has revealed that the count for the Windows Phone Store is now at 300,000. With the market moving toward mature software that takes advantage of increasingly powerful endpoints and addresses functionalities once reserved for PCs, will be instrumental for fostering collaboration and coordinating both manual and automated tests.
How can developers and QA engineers deal with so many mobile devices and platforms?
Creating software for mobile devices has never been simple or easy. In the early days, there were incredible constraints on hardware as well as relatively few APIs and toolkits for expediting development. Over the years, some of these challenges have been overtaken by new ones surrounding sustainable monetization and consistency across a wide range of platforms.
Teams have to address users who may delete an app if it crashes even once, but how can they do so when there are so many device/OS combinations to account for? Native vs. HTML5 development is a conversation for another time – let’s look at how an application developed with either of these methodologies might be tested. Many of the issues that apps face in the wild originate from overlooked mobile testing conditions, which if implemented may have produced a more polished product. Here are a few to keep in mind:
Too much manual testing: Manual tests aren’t bad – they’re critical to many QA workflows. But teams can easily become over-reliant on them, which doesn’t scale well given how fragmented the mobile ecosystem is. Android KitKat, for example, only runs on 20 percent of Android devices as of August 2014. Automated processes are needed.
Insufficient simulation of real-world conditions: As discussed earlier, smartphones and tablets don’t exist in a vacuum. They’re carried inside buildings with poor reception, or packed along into remote regions with only 2G or 3G coverage. Tests have to account for these realities as well as limitations on memory, screen resolution and battery life.
Low attention to region/language settings: This one flies under the radar since many developers target only specific sets of users. For apps with an international or multilingual audience, it is important to see if the platform in question has a translation option and whether app performance is affected by switching from setting to another.
Overall, mobile testing is about scalability for many devices and consistency despite constraints. A blend of automated and manual tests is usually the best way forward.
“Manual testing is a definite need, however, there are so many devices and combinations in the market today that it is necessary to use automated mobile tools as well,” stated a software engineer from CallFlow, in a post on LinkedIn. “User expects (sic) the application to stay on, connected, and perform at all times. To meet these expectations, the mobile testing strategy should include real device testing under various real world conditions. That includes various signal strengths, networks, speed and more.”
The stakes for mobile testing: Even big companies can miss bugs as apps scale
Facebook, with its 1 billion users, is obviously an outlier in the software world, but its recent battle with a bug in its iOS app illustrates how mobile testing requires tremendous time and effort as well as top-notch tools. The social network’s engineers were noticing an issue related to the Apple CoreData System, but due to the size and rapid evolution of the Facebook codebase, parsing the crash reports proved a monumental undertaking.
“[C]ertain fundamental programming challenges inevitably become more difficult with scale,” explained Slobodan Predolac and Nicolas Spiegelberg, engineers at Facebook. “Debugging, for example, can prove difficult even if you can reliably reproduce the problem – and this difficulty increases when debugging a highly visible but nondeterministic issue in a rapidly changing codebase.”
Ultimately, the Facebook team was able to identify the issue through close collaboration and a focus on programming fundamentals. The fix may have reduced the app’s iOS crash rate by 50 percent.
Users often have little patience for app crashes, so this is an important development. While most other shops won’t operate at Facebook’s scale, they’ll still have to deal with similar performance issues that could manifest due to adverse real-world conditions and/or other flaws in the code. A test management solution enables developers and software testers to scale their workflows and find defects early and often at low cost.

Related

Who is planning to stick with WinMo7?

I made this poll last time, but this was around when the news of WP7 was just getting out. I'm sure that from then and now, we've learned a lot more about the OS and MS has released a lot more info regarding the OS. So with that being said, I was just curious to see if there were any change of hearts.
Vote on!
I plan on buying a windows phone whenever some nice looking hardware comes to Verizon. I might have to wait a while since ill have to buy one at full price because my upgrade isn't until 2012.
Never will I ever choose anything besides Windows 7 or their webcam for my products.
Ad notifications? What kind of nonsense is this?
And here is the real nail in the coffin:
"At launch, Windows Phone 7 will not have the ability to cut, copy, and paste. It will recognize telephone numbers and addresses, but Microsoft says the majority of users don't need 'cut, copy, and paste'."
With that attitude, do I trust this company for phones? No. The iPhone 2G had more features than this!
I hope they die in the mobile arena. Their efforts have been haphazard and poor. If it does turn out to be good (doubtful since I've used Windows Mobile since the Blackjack) I don't see anything it offers that Android or iPhone doesn't already do, and better.
Fun phones are the iPhone and Android systems. They're also very good for work as well.
Blackberry handles business as usual.
And Microsoft, your best move was investing in Apple.
Dratini said:
Never will I ever choose anything besides Windows 7 or their webcam for my products.
Ad notifications? What kind of nonsense is this?
And here is the real nail in the coffin:
"At launch, Windows Phone 7 will not have the ability to cut, copy, and paste. It will recognize telephone numbers and addresses, but Microsoft says the majority of users don't need 'cut, copy, and paste'."
With that attitude, do I trust this company for phones? No. The iPhone 2G had more features than this!
I hope they die in the mobile arena. Their efforts have been haphazard and poor. If it does turn out to be good (doubtful since I've used Windows Mobile since the Blackjack) I don't see anything it offers that Android or iPhone doesn't already do, and better.
Fun phones are the iPhone and Android systems. They're also very good for work as well.
Blackberry handles business as usual.
And Microsoft, your best move was investing in Apple.
Click to expand...
Click to collapse
Sounds like a guy who is been around for a long time !!?. I respect your opinion but it is windows mobile what made this forum what it is today. So let it die?
It depends what kind of user you are, I have always been a fan of windows because its customizable, what is for me an added value. Now with the coming of mobile7, I dont know, but I´m sure we can support and make the OS better around here.
Iphone is in my opinion a hyped phone (especially the iphone4) and clearly is not as good as the previous versions because of its hardware malfunction.
Respecting Andriod, I like the phones and they are great but still I´m staying old fashioned and try and stick to WinMo.
As you can notice I will buy a phone with the new OS because I´m just curious and its flawless integrated with windows platforms in private and corporate perspective. What i believe is the advantage of Microsoft software.
I will buy a WP7 device in Germany as soon a device similar to the HD2 is released. For me are a display around 4 inch, arround 448 MB RAM, at least 16GB flash memory important. An amoled display is prefered.
Why WP7? As a developer I have with Silverlight much more fun and I have no fun to flash my device regularry to get the rom to a quality level that should be out of box. Is's a shame but big thanks to this board for making the good HD2 roms
Just waiting on what T-Mobile USA will bring us
Dratini said:
With that attitude, do I trust this company for phones? No. The iPhone 2G had more features than this!
Click to expand...
Click to collapse
Sure it did.
Main difference between WP7 and other mobile OSes, that it is being complex. iOS has just core stuff - kernel, some core APIs and few built-in apps like mail or safari. Android adds some wannabe support for integrating facebook, today widgets. WP7 comes as latest one with around 2 year development as of now, including full facebook integration at launch, combining and integrating your contacts into facebook. This was just an example, that WP7 is way more complex system, than any other mobile OS we have now. It allows integration into hubs, ... while all you can do on iOS is just add your icon on app launcher. No integration into core apps.
Also the biggest fun will begin shortly. Possibility to develop for PC-Xbox360-WP7 with one source code (and just optimizing user input for mouse, joystick or touchscreen) is f...in promising. And Silverlight, C# and XNA are awesome to play and create with, compared to native coding.
I will be getting WP7 as soon as I get the opportunity. Love the UI (I'd just say more colors into icons in the applist). Love the possibilities. Love MS!
OndraSter said:
Sure it did.
Main difference between WP7 and other mobile OSes, that it is being complex. iOS has just core stuff - kernel, some core APIs and few built-in apps like mail or safari. Android adds some wannabe support for integrating facebook, today widgets. WP7 comes as latest one with around 2 year development as of now, including full facebook integration at launch, combining and integrating your contacts into facebook. This was just an example, that WP7 is way more complex system, than any other mobile OS we have now. It allows integration into hubs, ... while all you can do on iOS is just add your icon on app launcher. No integration into core apps.
Also the biggest fun will begin shortly. Possibility to develop for PC-Xbox360-WP7 with one source code (and just optimizing user input for mouse, joystick or touchscreen) is f...in promising. And Silverlight, C# and XNA are awesome to play and create with, compared to native coding.
I will be getting WP7 as soon as I get the opportunity. Love the UI (I'd just say more colors into icons in the applist). Love the possibilities. Love MS!
Click to expand...
Click to collapse
what?!!
xbox-wp7-pc game integration is a possibility? but how is a phone going to be as capable as the three cores plus graphics core of a 360?
As soon as Sprint gets a killer 4G enabled one. Bamn! I'm there.
Gota get on the leading edge again and start promoting the thing to my friends/family/co-workers/etc.
theomni said:
what?!!
xbox-wp7-pc game integration is a possibility? but how is a phone going to be as capable as the three cores plus graphics core of a 360?
Click to expand...
Click to collapse
First of all, WP7 has a lower target resolution than XBox and PCs. You also can use a lower resolution than the native resolution of WP7 and the phone will resize the image "for free" using a dedicated chip. To target the different input formats, you have to tweak the code and use conditional compilation (like #If Xbox; #If WP7; #If Windows). If you want to utilize the full potential of each platform, there may be many conditional compilation instructions, but it is possible. Depending on the architecture, the main game logic can remain the same and does not need (many) changes.
Ima stick with it. WP7 is nice.
Yep, just as Reihnold described it.
The main logic and core is the same, you just optimalize it for different input and ofc slower HW (but with coming Hummingbird etc we will see reaching Xbox on WVGA screen in few years I bet). You disable some cool effects etc, but you do that with those #If Xbox360 fxRainbow.Enable = true; #Endif etc, so nothing huge. Compared to Linux-Android it is something quite easy. Mostly because of awesome IDE.
Wouldn't consider anything else.
I will definitely buy one. Love MS products and services and using them all integrated on my phone is the biggest thing they could ever made!
Cloud is the future
I'd be more interested to know what percentage of people would switch to wp7 in an iphone and/or android forum really. That to me is a better indicator of how well wp7 will do at launch.
I eventually want to switch, but ill do it further down the line when the OS matures.
Sent from my SAMSUNG-SGH-I897 using XDA App
I voted for sticking with WP7, all the latest videos I've seen show how super smooth it is so I wont be switching to clunky Andriod anytime soon
I am waiting to actually see how well the office, RDP and other apps integrate into windows before I pull the trigger on one. I really could care less about facebook integration or twitter or any social networking. Sure I use facebook, but I want to keep my contacts seperate from my social networking. I want a business device first. Not to say I won't try one out, but I intend on keeping my Tilt2 around unless they release a WM6.5 handset with a keyboard and a faster processor and more RAM! like that will happen...
And if it comes to switching platforms, android is next in line. No apple products ever in my house.
kdj67f said:
No apple products ever in my house.
Click to expand...
Click to collapse
I second that
I am so ready to purchase one of Windows Phone 7 phones! Why? please... for those ppl who say WP7 is not as great as their beloved WM 6 series, you gotta let your ego go. And yes, i have HD2. So this is a customer with experiences with hacking my device and use cooked ROMs. And yes i hate using cooked ROMs. Althogh i use cooked ROMs that looks like stock version atm. But i am planning to purchase it in this holiday or wait for htc to announce HD3 the beast! I really want my phone to have 1.5ghz or something downgraded clocked duo cpu.

Why Windows Phone 7 doesn't desperately need more powerful devices this year

I take no credit for this, ita a great article i came across that made the most sense in a while related to hardware :
http://www.mobiletechworld.com/2011...erately-need-more-powerful-devices-this-year/
As you have probably already noticed I was at Mobile World Congress this week so I had the opportunity to play around with some of the latest and most powerful handsets ever created. This year was obviously dominated by Google’s Android platform which took center stage at the convention with essentially every OEMs demonstrating or unveiling products running the immensely successful OS. What does it have to do with Windows Phone 7 hardware ? Well if there’s one thing that really garbed my attention it is the fact that not a single Android device I played with was as snappy and smooth as the Samsung Omnia 7 device I had in my pocket (or any iPhone model). Yes some of the devices on display were running non finalized software and probably hardware too but this has already been the case with retail devices like the Galaxy S and Desire HD which feature more powerful hardware than all the currently released WP7 devices.
I will repeat what I have been saying for a while: Android is the new Windows Mobile. OEMs want to differentiate their the products and one of the best way to do this is to use the latest and greatest chipsets, screen technology or other fancy hardware components. But as an end user, why should I care about the newest Exynos 4210, TI OMAP 4430, Tegra 2 if it can’t provide me with the same user experience as the now nearly 3 years old QSD8250 found in my Windows Phone 7 device? Similar to the old Windows Mobile days; OEMs are using Android’s “openness” as a test bed for their new CPUs and chipsets and are pumping out devices with crazy hardware specifications to show themselves in the press and sell device purely based on check list features: Dual-Core CPU ? Check. XX Mpix camera ? Check. 3D Cameras? Check. Huge Screen? Check etc. The issue here is that device manufacturers are more interested in time to market so optimizing the software to work with the hardware is just an afterthought. It’s not Google’s job to code the driver for the Samsung Exynos or for TI’s OMAP4. Google doesn’t even want to get the browser to use GPU acceleration for smoother scrolling and panning so the device manufacturers shouldn’t even count on the big G to give them any kind meaningful help in this department (Samsung has apparently implemented GPU acceleration to the browser in some unreleased Galaxy S firmware builds).
HTC has apparently learned the lesson a long time ago and has instead decided to milk the same SoC for while and instead just improve it’s Sense software layer every time it releases a new batch of devices. The end user is in both cases being presented with less than optimal solutions / offerings: On one hand you have new hardware that goes totally unused (Samsung, LG) and on the other you are buying exactly the same hardware but with an updated software layer (HTC).
Now let’s go back to Windows Phone 7 for minute. Take a Google Nexus One/ HTC Desire and compare it to the similarly speced WP7 devices. Which one is the snappiest and offers the smoothest UX? Same for the HTC HD2 running WM6.5 compared to the same device running Windows Phone 7. Microsoft has several big advantage with WP7 compared to Android. First, the have enforced strict HW guidelines and are currently only supporting Qualcomm’s Snapdragon SoCs and their Adreno GPUs. Secondly the Adreno GPUs are closely related to the Xenos GPU found in the Xbox360 so the company was already quite a bit familiar with architecture. Thirdly they control the APIs (Direct3D Mobile through DXGI and probably Direct2D for IE9 Mobile) unlike Android which relies on OpenGL ES and the drivers developed by the chipset manufacturers. The Windows Phone 7 ecosystem is like a console ecosystem with one set of drivers and APIs all controlled and certified by Microsoft while Android is more like a PC ecosystem filled with tons of different hardware configurations, driver versions controlled by nobody (Qualcomm even told me that OEMs don’t really bother including the latest drivers in the devices just because they are more concerned by the shipping date of the handset than with the end user experience. For example, as of right now the SE Xperia Play is the Android handset that has the latest Adreno 205 drivers).
Who would have thought that Microsoft would be able to easily port IE9 (which requires a DX10 GPU on the desktop) to Windows Phone 7 which only runs on a relatively old Adreno 200 GPU (DX9 capable) ins such a short time? Now take a look at the current state of the Webkit on Android: Yes it’s blazing fast at loading web pages on those super powerful handsets but after that the UX is simply anticlimactic because of the lack of HW acceleration. This is supposed to be fixed in Honeycomb on the tablets right? But where’s the smartphone version? From what I have seen at MWC the touch responsiveness of the Android 3.0 tablets varies greatly from one device maker to another. So once again Google’s lack of control of the hardware and drivers is going to hurt the end user.
This is not to say that Windows Phone 7 should be stuck with the current QSD8250. New high-end WP7 devices are going to be announced later this year because technology evolves at a rapid pace and Microsoft will obviously want to support higher resolution screens and video formats (and yes they are working on new Chassis but the Nokia partnership which was decided only last Thursday changed some of the plans), more graphically intensive 3D games and applications but the point here is that they are in no rush to do this because they can squeeze a lot more out of the first generation Snapdragon SoC than what is possible with Android. Everything I just said so far also applies to Apple’s iPhone which is quite similar to Windows Phone 7 and I personally think that there’s no need for Apple to switch to a dual-core SoC for the upcoming iPhone 5 given that the A4 is still powerful enough for 99% of the tasks (but if they do then you can be sure that they will have the software to take advantage of it). Android is obviously a really great OS that I enjoy using it on a daily basis thanks to all the features it supports but Google should really stop the madness and take over control of what should or shouldn’t be done on the platform. OEMs are loving it right now because they are free to do whatever they see fit but I really think that it will hurt the platform in the long run when people start to realise that they paying for hardware that most of the time isn’t used all or just paying for a software update (HTC..).
What Windows Phone 7 is in desperate need of is software updates filled with differentiating features and thrid-party access to more APIs so they developers can create more exciting and advanced applications.
Click to expand...
Click to collapse
Discuss...
Pretty much the facts.... I mean that is just an astounding article... spot on.
As an Android user who is otherwise impartial to OS wars, I wholeheartedly agree. For months now, I've been telling people that Android reminds me of the old Windows Mobile. Every WM7 device I have ever played with has exhibited exemplary smoothness and snappyness compared to any Android handset you care to name. It's a shame because Android is really good otherwise.
Sent from my HTC Desire using Tapatalk
IMO, although it would be nice to have, WP7 doesnt have to go overboard like Android is doing when it comes to specs as to dual core cpu's, 3d displays and such. I believe that they should improve hardware based on features such as front facing camera to add video chat functinality, perhaps a video output via 3.5mm jack (since requiring hdmi might be pushing it a little across all oem's) etc.
Im positive that if they bump up the cpu to support at least second gen snapdragon with its 45nm architecture, improved 205 Adreno GPU and much faster clock per clock compared to first gen, i have no doubt that besides the inmensly graphical stressing situations, WP7 would run circles round any dual core Android device since it being used to its full potential and proper optimization and drivers makes it not have a elephant on its back to carry
I think it is a given that we will eventually see more powerful Qualcomm SoCs show up in WP7 devices, and possibly other manufacturers' SoCs. This generation might become the "budget" chassis in 2012...Who knows?
What I do like, and want it to remain the same, is the fact that Microsoft needs to certify whatever hardware specs is used, so when updates are pushed out, Microsoft wouldn't need to run to each manufacturer and ask for drivers...
I'm sold where can I buy one? I kid, I kid. I have a Focus.
One thing is for sure, the overall opinion of the phone UI is excellent for all the listed reasons. Thanks for the post.
I compare this current experience to my experience with Windows 7 rc. Much like the day I installed Windows 7 to my lowly Dual Core (e2150, 2gb, 7200 HDD), it was good but not great in terms of speed, quick but not fast. Then, the cycle moved on and new hardware at low prices came into my life...
Now at Quad Core, 8 gb, Dual GPU, SSD, it is like driving a Buggati Veyron, downhill, on a 5 lane speedway, with no traffic. Life is instantaneous, the only limit...my ability to click as fast as it acts. ha! It happens as if I had on a thinking helmet and it sucked the idea out of my head!
I can only imagine wp7 on the set of phones that will come out...8 months...1 to 2 years from today...oh yeaaaaaa
close your eyes, think about it. Did you think about it? Think again, that's right. Amazing.
Wasn't that nice? Ahhhh yeaaaaaa
With dual core and a 2x faster GPU...oh my...it will get smoother and faster...hard to imagine and exciting at the same time. :splooge:
All in due time, I am happy with my phone today and happily have put my development time into other projects and not Wm6.5. Like this one from Johnny http://hackaday.com/2011/02/09/low-cost-video-chat-robot/
The current WP7 devices are fine. Just make sure you get one with 16G Storage and 512+ RAM or hope you're gonna be lucky enough to find a big SD Card that works well the first time. Data loss due to a bad/incompatible SD Card months down the line is... Unfun!
I want my next phone to have the IBM Watson OS
I don't really expect to see WP7 handsets with faster processors. It isn't needed. Every app or game being made will be aiming for a certain minimum standard.
I do see improvements coming in extra features (like a front facing camera). And I do expect to see handsets with more and more memory.
If the end of 2011 brought WP7 devices with the current processor, but also offered 768 MB RAM, 32 GB storage and a front facing camera, that would be one hell of a competitive device.
Then in the holiday of 2012 we could see WP8 push the hardware limits by launching with some really high minimum specs. But at the same time, still support WP7 for "budget" handsets.
They need sexier devices. I must admit the three buttons on the front do look classy.
Reflexx1 said:
I don't really expect to see WP7 handsets with faster processors. It isn't needed. Every app or game being made will be aiming for a certain minimum standard.
I do see improvements coming in extra features (like a front facing camera). And I do expect to see handsets with more and more memory.
If the end of 2011 brought WP7 devices with the current processor, but also offered 768 MB RAM, 32 GB storage and a front facing camera, that would be one hell of a competitive device.
Then in the holiday of 2012 we could see WP8 push the hardware limits by launching with some really high minimum specs. But at the same time, still support WP7 for "budget" handsets.
Click to expand...
Click to collapse
The minimum specs must be maintained and they must be maintained at a level that ensures user experience will not be compromised for people who bought launch devices. In the holiday season of 2012 people will still be stuck on contract with current devices, probably for months to come.
All of a sudden apps will be updated in a way that their phones will choke running these apps.
Just upping the minimum specs because you think it sounds cute is a dumb idea. I doubt Microsoft will do it, and if they do, people will sort of laugh at them and they will lose a ton of customers. By then RIM will have QNX Blackberries and WebOS may be well-developed. There will be even more choices than we have today...
They really have to take an "Apple" approach to hardware support, IMO. It's the only thing that makes sense sort of overspeccing your devices and enticing a bunch of geeks to upgrade their phones every year for major software updates/bug fixes every 9 months to a year.
Yeah but is it partially due to room? I mean, Sense ROMs running slower than the cleaned up and simpler AOSP ROMs? I get the lack of acceleration ... a d understand the end result and why people might complain ... but my phone is snappy even though at times I notice slow down .. but that is hardly reason to ignore stability updates, even others. I mean , while my phone might be running smooth here ... it may slow down there. I see the choppy scroll .. but I've seen friends WP7 - uh, phones? - slow down at times too.
I get sick of this WP7 is constantly butter because its not. More often than not? Sure. But I rarely get agitated at the speed of mu device and most don't either ... sure I can see it, but I've also seen my.phone jump as much as my friends WP7 devices. It all depends. Overall, sure ... but it still doesnt touch iOS. To think you are major steps ahead is hype. More overhead here .... lack of acceleration here ... it's not shocking when you think about it. Android uses more resources and overhead ... you have such q standardized system. Its almost not surprising. And it's NOT suggestive of you being "good" at the moment.
Sent from my PC36100 using XDA App
That's a great article. I agree 100%. I had a Samsung Galaxy S and with it's freshest time it had the most powerful chips int the markets, but even today it is not lag free, because of crappy Samsung optimizations to the software. That's why I really don't believe the new Galaxy S II will be any better with it's dual core. You could see it from the videos, that it's laggy at the moment and I don't believe Samsung will get it lag free ever.
fast hardware = bad ?
this smacks of hardware envy something terrible.
surrrrre, android + quad cores will suck... but wp8 will be perfect. whatever, if ever.
N8ter said:
The current WP7 devices are fine. Just make sure you get one with 16G Storage and 512+ RAM or hope you're gonna be lucky enough to find a big SD Card that works well the first time. Data loss due to a bad/incompatible SD Card months down the line is... Unfun!
I want my next phone to have the IBM Watson OS
Click to expand...
Click to collapse
Why is 512+ RAM important, I was thing about getting the HTC 7 Pro, which only has 448 RAM and also is 16gb necessary if I don't use my phone as a media player as HTC 7 Pro only has 8gb as well?
Beesneazy, you're either completely full of crap or just delusional. I mean wow. Android fanboyism at its ugliest. Yeesh.
Ohgood, did you read the article? If you did, perhaps it's time to go back to Hooked on Phonics to work on word comprehension...
Anyhow, on topic, I completely agree with the article posted by OP. Kiddies like these Android fanboys love to deny the truth but it is what it is. Did everyone really think Microsoft would just sit back and be pummeled in the mobile phone market forever? With the right moves in the future WP7 will be huge. Maybe knock Android back down to third or fourth place and setup a head to head with iOS...
Sent from my HD7 using Board Express
ohgood said:
this smacks of hardware envy something terrible.
surrrrre, android + quad cores will suck... but wp8 will be perfect. whatever, if ever.
Click to expand...
Click to collapse
Yes, and when you get your quad core phones that are still lagging, and still dont recieve the latest updates, and are still running a version of android that is essentially a pallet swap of 2.1 and still looks like a low end iphone we'll be happy with our maybe dual or maybe quad-core phones that run smoother, have better games (because aside from iphone ports and maybe 1-2 other games androids selection is just terrible), have a decent media player, have oustanding integration with business and personal matters, and we'll actually have a NEW OS not just an overhyped pallet swap of the previous version.
Fact WP7 will never catch Android or IOS.
Sure WP7 is nice. Serious competitor, nope.
Think realistic and remove your love affair. Maybe WP7 can be 5th place or if things go well 4th place.
Now flame on.
N8ter said:
The minimum specs must be maintained and they must be maintained at a level that ensures user experience will not be compromised for people who bought launch devices. In the holiday season of 2012 people will still be stuck on contract with current devices, probably for months to come.
All of a sudden apps will be updated in a way that their phones will choke running these apps.
Just upping the minimum specs because you think it sounds cute is a dumb idea. I doubt Microsoft will do it, and if they do, people will sort of laugh at them and they will lose a ton of customers. By then RIM will have QNX Blackberries and WebOS may be well-developed. There will be even more choices than we have today...
They really have to take an "Apple" approach to hardware support, IMO. It's the only thing that makes sense sort of overspeccing your devices and enticing a bunch of geeks to upgrade their phones every year for major software updates/bug fixes every 9 months to a year.
Click to expand...
Click to collapse
I'm not sure what you're attempting to address when you quoted me. I never mentioned changing the minimum specs of WP7.
And I think it's pretty much guaranteed that WP8 will have a completely different set of minimum specs. Do you expect it to never change?
vetvito said:
They need sexier devices. I must admit the three buttons on the front do look classy.
Click to expand...
Click to collapse
Exactly! I agree they don't need more powerful devices but they do need more appealing hardware (for a start a 32GB device would do no harm).
vetvito said:
Fact WP7 will never catch Android or IOS.
Sure WP7 is nice. Serious competitor, nope.
Think realistic and remove your love affair. Maybe WP7 can be 5th place or if things go well 4th place.
Now flame on.
Click to expand...
Click to collapse
Sad but true. WP7 is quite late and if you think about it the real launch will be with Nokia, I doubt they'll sell anything before that as nothing has changed since October.
vetvito said:
Fact WP7 will never catch Android or IOS.
Sure WP7 is nice. Serious competitor, nope.
Think realistic and remove your love affair. Maybe WP7 can be 5th place or if things go well 4th place.
Now flame on.
Click to expand...
Click to collapse
this is true only because the majority of cellphone owners are complete morons.

What We Want In Next Windows Phone Handset

Windows Phone 7 has been a fresh change from the millions of rows and columns of icons we have seen in smartphones in the recent past. Although the operating system is super fast and effective, it does lack in a few areas, when compared to Android and iOS. Here’s what we would love to see in the next Windows Phone 7 handset.
Guest Mode
Everybody has personal stuff on their phone. From stored passwords, to ‘logged-in’ social networks, to credit card details, to personal images and documents. There’s a constant fear of spilling out ‘classified information’ when somebody wants to view your new smartphone. What do you do then? Enter guest mode.
I’ll quickly explain this once, if you’ve not understood it already. Guest mode allows you to hide your personal data like e-mail, social networking updates, files and login info. You have two passwords on your smartphone. Password A enables guest mode, while password B enables your normal phone functionality. It’s an extremely simple to implement feature, but somehow hasn’t been included. No longer do you have to stay worried about showing your latest WP7 handset to your friends, as you’ll have guest mode! C’mon Microsoft, please do this for us and everybody else.
Media formats and Zune
The single most irritating feature in Windows right now is Zune and how it greatly limits media formats for your smartphone. Why do all videos have to be transcoded by Zune? It’s similar to iTunes for iOS devices, but we’d have loved a free approach by Microsoft. Anyway, all is still not over and removing Zune dependency would definitely be a ‘feature’ we’d all love to have. And while we’re at it, more media format support out of the box would definitely be a brilliant addition. After all, they’re all ‘smart’phones, aren’t they?
No more Zune!
To think of it, everything in their user interface is slick and fast. From sending emails to updating your Facebook status, to clicking pictures, to accessing music - the whole experience is a breeze. Why doesn’t the same outlook have to be carried over to connectivity to the PC, data transfer and playback? Playing any video format is definitely on our priority list and transferring music files using mass storage is an easier task to accomplish as well. Even phone updates currently require you to connect your phone via Zune, whereas OTA it's quicker, faster and sexier!
More UI customization
Not particularly happy with the look of the user interface? Too bad, you can’t do a thing about it. Like iOS, WP7 is a closed system and while i ain't particularly complaining out here, how you feel about the interface from the word go, will clearly decide your overall experience and satisfaction with the phone. WP7 is as rigid as iOS. The best you can do at the moment is change tiles, add or remove them or simply change the background and tile colour.
I’ll reiterate this again, we aren’t complaining about the user interface. There’s absolutely nothing wrong with the UI, but sometimes you might want that slight amount of customization that might alter the look and feel of your phone. A desktop wallpaper, an alternate launcher, or simply minor tweaks in the layout mean that you’ll never get tired of the tile interface and you’ll have one more option to choose from.
1080p recording support
So, the UI is fluid, the phone can do all your basic tasks efficiently without too much of a hassle. But, for WP7 to stay in the hunt for the top spot, it’s the ‘small’ things that need to be maxed out, starting with 1080p video recording. Take, for example, the Nokia Lumia 800. It’s one of the top smartphone offerings, it competes with the likes of the HTC Sensation and the Atrix 2, two relatively older phones. The 800 can do ‘only’ 720p, while the other two are capable of ‘1080p’. True, this isn't a major deal, because on a screen that small, there’s absolutely no visible difference. but hey if you’re paying big bucks for your smartphone, you might as well get the best of everything!
This could also be due to the fact that Microsoft has been extremely restrictive with OEMs so far. Single core CPUs, max 480 x 800 pixel resolutions are frustratingly low-end specs. That may change however, but we’re hoping the transition is quicker than their updates!
External memory card support
Another simple addition that we definitely would want in the next Windows Phone 7 device is support for an external memory card. Depending upon your phone, you may either get 8 or 16 gigs of storage, and that is definitely enough for a lot of people, but as of now, most of the handsets don’t have a microSD card slot, with a few exceptions like the Samsung Focus.
How difficult is it?
There’s a certain trend with the increasing use of cloud services and the elimination of memory card slots, and there are chances that more and more devices in the near future would come with ‘just’ the internal memory. For personal reasons, ease of use and poor operation of cloud services in the country at the moment, we’d definitely want the next-gen devices to have an external memory card. It’s just - convenient and easy! For the record, even the Nokia Lumia 900 isn’t going to have an external memory card slot, just like the Galaxy Nexus and the Sony Xperia S. With cloud becoming more and more popular, can you see the trend? Give us back our ‘microSD card support up to 32GB’ spec!
NFC support
In the year 2012, 100 million NFC-enabled smart-phones are going to be sold, according to a study. We can bet that most of them won’t be Windows Phone 7 devices. Why? Because NFC hasn’t still come to Windows Phone 7 devices. According to a Microsoft spokesman, “While NFC is not currently supported on Windows Phone 7.5, it is coming. We expect NFC-enabled Windows Phone devices to ship within the next year.” This statement was recorded in 2011, so hopefully we will get to see NFC this year.
100m in 2012, none will be WP7??
Though NFC is still in its nascent stages here, it’s quite the future of a lot of mobile related services. So, for the love of those of us who don’t change our devices for a long, long time, could you please have that option in your next WP7 phone, Microsoft ? At the moment, it’s not up to the OEMs to include or exclude this feature, so we know who’s got to buck up.
TV Out
Want to show your videos and photos from your WP7 device on your swanky new HDTV? Well, it’s not easy as 1 - 2 - 3. You’ll have to get them onto your laptop or another device and then showcase it to your friends and family. TV out via HDMI or MHL is definitely an option we would love to have. Nokia Play To is coming soon, so that limitation might have a workaround in the future, but not all HDTVs are equipped with Wi-Fi or an Ethernet port.
Well I would say more freedom to devs so better apps can be made possible.
Thanks A Lot Sir For Your Opinion
lamborg said:
Well I would say more freedom to devs so better apps can be made possible.
Click to expand...
Click to collapse
Thanks Sir,
Agree
I think they should improve the software of the camera. Lumia Nokia 800 has a great sensor, but the picture quality leaves much to be desired
davidwar said:
I think they should improve the software of the camera. Lumia Nokia 800 has a great sensor, but the picture quality leaves much to be desired
Click to expand...
Click to collapse
but, it's been claimed by WPcentral the Titan 2 has a much better sensor than ever the Lumina 900 and pictures have been great (read into the reviews on WPcentral)
As with the OP.
UI customisations- YES !! No question, the option for simple but, advanced features.
1080p recording- No brainer, everyone else is doing it but, a 1080p camera that actually looks like a 1080p recording (a good quality lens and sensor standard)
NFC and TV out, sure that would be nice.
I would also like
1. New battery tech so devices can last a TRUE 4-5 days with out a charge (I'm dreaming)
2. Better graphics upgrade TO take gaming to the level of Android and the iPhone. Just compare the videos of Spinter Cell for WP7 and look at Rage for the iphone (and that's not a new game), you'll see what I mean. They are not even in the same class. To take the Xbox Live brand serious...

The Eye Tribe [Copenhagen]: Lead Android Developer

About The Eye Tribe
The Eye Tribe is an exciting startup based in Copenhagen developing eye tracking technology that can be integrated into a wide range of products like mobile phones, tablets, computers, monitors and cars. The Eye Tribe has been named Cool Vendor 2012 by Gartner, and has won numerous awards since the company was founded in 2011.
About the job
The Lead Android developer will be responsible for leveraging our technology to the Android platform, working together with our eye tracking algorithm experts to build the next generation Human-Computer Interaction technology for the Android platform.
We seek a professional and dedicated engineer with demonstrated ability for building elegant and efficient solutions. You will be part of an international team in a rapidly growing company set for global expansion. This is a unique opportunity to join early and grow with the company.
Required Expertise/Experience
Professional software development experience (5+ years)
Relevant Android and Linux software development experience
System architecture and Object Oriented design
Excellent verbal and written communication skills
Technical skills – Required
Experience building Android applications and/or subsystems
Strong experience in C/C++/Java programming
Development of kernel modules and/or system libraries
Android ROM development
Technical skills – Desired
Development of Linux device drivers
Hardware acceleration (e.g., Renderscript, OpenCL, OpenGL ES, Tegra, ARM)
Hardware integration (CMOS camera sensors, MIPI, I2C)
Image processing/analysis (preferably using OpenCV)
Education
Bachelor or higher in Computer Science or similar.
Apply
Submit resume and a cover letter to jobs(at)theeyetribe(dot)com and we will contact you ASAP.

Advice, developing a high end video compression codec on Shield Android TV for Camera

Advice, developing a high end video compression codec on Shield Android TV for Camera Acquisition and HQ video.
Hi
Aims
I am researching doing a high end streamlined video compression/decompression codec that can be installed and registered under Android, and be available to third party camera, editing and video apps.* Shield seems like a good top end development target.* I am hoping it will be able to compress 4k+ video streams, with small file sizes and reduced processing overheads.
Even though it is meant to be more for high end camera acquisition on Android in general, it also has other uses on the web.
I am trying to find out general, and detailed, information to see what I need to address.* I'm a newbie to all this, from back in the days that C++ was new and untaught in my college. I'm going to have to reteach myself programming, but have a lot of knowledge on the design side due to previous work.
Codec Programming?
So basically, I need advice on broad programming info on programming and registering a codec on Android and gp-gpu use?
But with Android things seem a bit more complicated to get performance due to the way things are structured:
Backend Camera Streamlining?
Previous high level camera projects have failed due to the underlying restrictions of the android camera interface and customisations from phone to phone, but also Android's slow nature. This is an attempt to bypass this with a high performance codec section.* L and M, reportedly address the deficiencies somewhat, but for the codec I realise the data rate of video data coming in might be poor, and* I might have to write a back end to acquire the frames from the hardware to the codec quick enough, which I don't want to do, but if I can't get frame data delivery fast enough I will have to look at it. I want to use mainly the GPU or other processing units instead of the main processor, for power efficiency and speed, but realise nothing is simple. All that sort of stuff that you have to do because it was not done right in the first place. So, avoiding going through slower high end camera interfaces as much as possible. I understand it is all based on a standard Linux camera API. If the camera software does not have to be rewritten and it can deliver frame data at streamlined timely speeds to a codec, then I can avoid much of this. So, I probably need advice in these things too.
Backend Storage Streamlining?
Now, on the other side we have storage**Hopefully the data rate can be small enough to avoid issues, but that is unlikely on a 4k-8k frame and would need advice on this too.
JavaScript to Android, Android to JavaScript transportability?
I actually want to develop the core of it within JavaScript primarily, for transportable use on the web and Firefox OS, so will have to find out the best way to transfer it to Android for compilation? As I know next to nothing about these new languages, it will be an uphill learning curve. As I understand, JavaScript syntax is separate from Java, and not a even a logical subset, which makes life hard.
----------
Anyway, it is a shame we don't have a kick starter like funding scheme, to pay a good programmer to do most of the background stuff, and upgrade the Linux code and drivers, so anybody can use the new code with any codec and camera app combination. My main interest is my own codec, not all the other stuff, that is really fixing Android and Linux camera code, which would help everybody.
This is not an official project start, just implementation research.
If anybody knows of anybody that can contribute, please direct them here?
Thanks.
Stevio2 said:
Advice, developing a high end video compression codec on Shield Android TV for Camera Acquisition and HQ video.
Hi
Aims
I am researching doing a high end streamlined video compression/decompression codec that can be installed and registered under Android, and be available to third party camera, editing and video apps.* Shield seems like a good top end development target.* I am hoping it will be able to compress 4k+ video streams, with small file sizes and reduced processing overheads.
Even though it is meant to be more for high end camera acquisition on Android in general, it also has other uses on the web.
I am trying to find out general, and detailed, information to see what I need to address.* I'm a newbie to all this, from back in the days that C++ was new and untaught in my college. I'm going to have to reteach myself programming, but have a lot of knowledge on the design side due to previous work.
Codec Programming?
So basically, I need advice on broad programming info on programming and registering a codec on Android and gp-gpu use?
But with Android things seem a bit more complicated to get performance due to the way things are structured:
Backend Camera Streamlining?
Previous high level camera projects have failed due to the underlying restrictions of the android camera interface and customisations from phone to phone, but also Android's slow nature. This is an attempt to bypass this with a high performance codec section.* L and M, reportedly address the deficiencies somewhat, but for the codec I realise the data rate of video data coming in might be poor, and* I might have to write a back end to acquire the frames from the hardware to the codec quick enough, which I don't want to do, but if I can't get frame data delivery fast enough I will have to look at it. I want to use mainly the GPU or other processing units instead of the main processor, for power efficiency and speed, but realise nothing is simple. All that sort of stuff that you have to do because it was not done right in the first place. So, avoiding going through slower high end camera interfaces as much as possible. I understand it is all based on a standard Linux camera API. If the camera software does not have to be rewritten and it can deliver frame data at streamlined timely speeds to a codec, then I can avoid much of this. So, I probably need advice in these things too.
Backend Storage Streamlining?
Now, on the other side we have storage**Hopefully the data rate can be small enough to avoid issues, but that is unlikely on a 4k-8k frame and would need advice on this too.
JavaScript to Android, Android to JavaScript transportability?
I actually want to develop the core of it within JavaScript primarily, for transportable use on the web and Firefox OS, so will have to find out the best way to transfer it to Android for compilation? As I know next to nothing about these new languages, it will be an uphill learning curve. As I understand, JavaScript syntax is separate from Java, and not a even a logical subset, which makes life hard.
----------
Anyway, it is a shame we don't have a kick starter like funding scheme, to pay a good programmer to do most of the background stuff, and upgrade the Linux code and drivers, so anybody can use the new code with any codec and camera app combination. My main interest is my own codec, not all the other stuff, that is really fixing Android and Linux camera code, which would help everybody.
This is not an official project start, just implementation research.
Click to expand...
Click to collapse
I wish you all the luck in your endeavour, as this sounds really interesting, and different........
Saying that, i dont think your suppose to post anything in the dev thread that is'nt an actuall work, im just giving you a heads up, incase a moderator might come along............also i could be wrong, if this has changed recently
Your best bet i reckon, is to post in this thread
http://forum.xda-developers.com/general/general
Its the main general thread of the entire xda, so you'll have more eyeballs.........and maybe a better chance of getting a "start in the right direction" from someone knowledgeable
Ive also read many android technical question being asked at the "stackexchange" website, by devs working on their projects, so that might be another avenue to explore if your unlucky here
Anyways, wish you luck with this
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Click to expand...
Click to collapse
Thanks. From forum discussion rules. I mistook this to mean development research discussion as well. If it actually should, then I'm happy for it to be moved to general.
Stevio2 said:
Thanks. From forum discussion rules. I mistook this to mean development research discussion as well. If it actually should, then I'm happy for it to be moved to general.
Click to expand...
Click to collapse
The Shield is based on the Nvidia X1 chip. Nvidia also just released the Jetson TX1 development board which is similar. If you register as a developer with nvidia (which is easy) you get access to all the dev docs (including video codec docs) for the TX1, which boots Ubuntu. That should be a good start.
Sounds good, it was an andriod development related question though (using shield hardware under android so it can be shared with different platforms, you just can do more on the shield hardware. Maybe there is a Linux overlap with andriod in codec support but I doubt it isva full story. I am interested in dealing with 8k content too. There is a way to do a 8k over HDMI 2, but muchntoo involved at this stage, the display has to also be modified or an adaptor made to interface to a future 8k interface.
I have just realised the shield might be good for touch table work (not so good on the software side as there are no established software base to work on). I located a new good cheap fine grained more transparent touch surface overlay technology a little while ago that is being used to do cheap touch tables in Asia. Using a 4 subpixel screen I can do a semi 8k display out of a 4k (though you can't directly access the white pixel through hdmi, which is useless). There is also now 6 color pixels. A firmware change might allow a display to sub pixel address. However, you can get panel frames without the internal section and get direct access to the internal panel interface (why hdcp is probably useless). Anyway, 8k would yeild 16k, a nice minimum for a 80 inch table, with OLED, or projector. Reprogramming a display to use display port/thuderbolt interfaces on a display would be more useful. I tried to negotiate access to a 16k projector chip once to connect up to a low powered processing array, but got nowhere. Henceforth I've been dealing with embedded machine code level concerns for decades off and on and let the newer high level language and OS stuff (like C# and Linux) go, due to health issues.
Another intetesting thing that can be done with a shield, is it can be hooked up to a camera head and rigged up to be a camera (or the next version). Problem is that USB 3 is useless compared to Thuderbolt 3 etc (though camera head computet interface standards take a while to catch up). My codec could be used for recording. We used to do this with PC's but the Shield offers a much better power consumption. There is Linux software around to do this, but the development board is half powered and expensive.
Bump
Well, when I said bump, I didn't really mean to move it to a third subforum
Seriously, I want to do a less than 20mbit/s 8k visually lossless codec. But at the moment I'm waiting to get checked out for dementia, which explains a lot about the last few decades and my decreasing amount I can do (beta amyloid in particular builds up for 10-20 years with low grade symptoms before it gets seriouse enough that it is can be picked up on older scanning, by then it has permanent problems. Apart from other types of dementia). At this stage I can't do much much of the time.
Anyway, as the thread has skipped to a second forum in two days, any more short cut advice is welcome.

Categories

Resources