[Q] Grails is the best for rapid web application development, isn't it? - Design, Prototyping, UI, Graphics

The two reasons why you should choose Grails are :
- Rapid web development: It can help us achieve productivity benefits similar to Rails or Django but without leaving JVM and Java knowledge.
- Powered by proven technologies: Grails underneath uses Spring and Hibernate to power web applications. It can be considered as syntactic sugar over these technologies.

Use Rapid Prototyping Software Development
Turn Your Idea Into a Reality!
http://rozdoum.com/rapid-web-application-development.html

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.

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.

Ubuntu for smartphone!!! Could this be ported to Note II ?

http://www.androidpolice.com/2013/0...on-of-its-os-just-for-your-pocket-superphone/
It seems they are going to release images for Galaxy nexus. lets hope this can be ported soon to Note II when they release it.
Press Release:
Ubuntu comes to the phone, with a beautifully distilled interface and a unique full PC capability when docked
· Leading open PC platform with huge global following announces mobile version for network operators, OEMs and silicon vendors
· Fast, beautiful interface for entry level smartphones
· Unique PC experience on superphones when docked with a monitor, keyboard and mouse
· Ubuntu raises the bar for mobile UI design, for richer and more immersive apps
· A single OS for phone, PC and TV
London, UK, 2 January, 2013: Canonical today announced a distinctive smartphone interface for its popular operating system, Ubuntu, using all four edges of the screen for a more immersive experience. Ubuntu uniquely gives handset OEMs and mobile operators the ability to converge phone, PC and thin client into a single enterprise superphone.
"We expect Ubuntu to be popular in the enterprise market, enabling customers to provision a single secure device for all PC, thin client and phone functions. Ubuntu is already the most widely used Linux enterprise desktop, with customers in a wide range of sectors focused on security, cost and manageability" said Jane Silber, CEO of Canonical. "We also see an opportunity in basic smartphones that are used for the phone, SMS, web and email, where Ubuntu outperforms thanks to its native core apps and stylish presentation."
Ubuntu is aimed at two core mobile segments: the high-end superphone, and the entry-level basic smartphone, helping operators grow the use of data amongst consumers who typically use only the phone and messaging but who might embrace the use of web and email on their phone. Ubuntu also appeals to aspirational prosumers who want a fresh experience with faster, richer performance on a lower bill-of-materials device.
The handset interface for Ubuntu introduces distinctive new user experiences to the mobile market, including:
1. Edge magic: thumb gestures from all four edges of the screen enable users to find content and switch between apps faster than other phones.
1. Deep content immersion - controls appear only when the user wants them.
2. A beautiful global search for apps, content and products.
3. Voice and text commands in any application for faster access to rich capabilities.
4. Both native and web or HTML5 apps.
5. Evolving personalised art on the welcome screen.
Ubuntu offers compelling customisation options for partner apps, content and services. Operators and OEMs can easily add their own branded offerings. Canonical's personal cloud service, Ubuntu One, provides storage and media services, file sharing and a secure transaction service which enables partners to integrate their own service offerings easily.
Canonical makes it easy to build phones with Ubuntu. The company provides engineering services to offload the complexity of maintaining multiple code bases which has proven to be a common issue for smartphone manufacturers, freeing the manufacturer to focus on hardware design and integration. For silicon vendors, Ubuntu is compatible with a typical Android Board Support Package (BSP). This means Ubuntu is ready to run on the most cost-efficient chipset designs.
In bringing Ubuntu to the phone, Canonical is uniquely placed with a single operating system for client, server and cloud, and a unified family of interfaces for the phone, the PC and the TV. "We are defining a new era of convergence in technology, with one unified operating system that underpins cloud computing, data centers, PCs and consumer electronics" says Mark Shuttleworth, founder of Ubuntu and VP Products at Canonical.
Canonical currently serves the leading PC OEMs: ASUS, Dell, HP, and Lenovo all certify the majority of their PCs on Ubuntu and pre-install it in global markets. Over 20 million desktop PCs run the OS today, and Canonical estimates that close to 10% of the world's new desktops and laptops will ship with Ubuntu in 2014. Ubuntu is also wildly popular as a server platform, the number one server OS on the key major public clouds and the leading host OS for OpenStack, the open source IAAS
Just saw this too and at the end of their 20 minute video they said that it would run with the android kernel and drivers meaning it shouldn't be hard at all to port to our current device!
This summer I saw an XDA video of a galaxy s 2 running Ubuntu for Android. It shared the same kernel and worked together with android. As soon as you connected the phone to the dock it turned into an Ubuntu os desktop pc. This is what I'm interested in. I'm not interested in using Ubuntu as my phone os. Is this what is being released by canonical? Because from the videos I saw today it seems its a new operating system.
Sent from my GT-N7100 using Tapatalk 2
this is a brand new OS and i really hope we can get it on the note 2 since its the top of the line phone
slekkas said:
This summer I saw an XDA video of a galaxy s 2 running Ubuntu for Android. It shared the same kernel and worked together with android. As soon as you connected the phone to the dock it turned into an Ubuntu os desktop pc. This is what I'm interested in. I'm not interested in using Ubuntu as my phone os. Is this what is being released by canonical? Because from the videos I saw today it seems its a new operating system.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
That was only ever available to OEM's, and I'm fairly sure none of them took it up. That's probably why Canonical have taken this route instead.
jellydroid13 said:
Just saw this too and at the end of their 20 minute video they said that it would run with the android kernel and drivers meaning it shouldn't be hard at all to port to our current device!
Click to expand...
Click to collapse
Thats the reason why i am so excited. Happy times ahead!!
Actuality there will be a phone released at the end of the year that uses Ubunta as an operating system. The Android Ubunta when docked system is a first step. Ubuntu will compete with all the existing phone operating systems within the next 12 months.
Sent from my GT-N7100 using xda premium
It looks good in theory. As a long time Ubuntu pc user this is something exciting for me but the are few issues having this on note 2 even in the future. I am sure it will have note port down the line. But the os is heavily gesture based. And most gestures are designed to work from edges of the screen. For big device like note 2 this rules out seamless one hand passion for doing even basic things which you can still do on Android with Samsung customisations.
I understand appeal in gesture based OS, but in real world day to day use, point and click approach is most of the times faster.
But o would still like to try it out.
From my Note 2, in your face.
I had Ubuntu on my N2 with Linux Installer. Just C**p.
Edit: Damn... I just watched the Keynote. Looks pretty amazing
Pozdrav
Croatia1
With something as close to perfect as the note 2 + a few tweaks, why would anyone consider using a new mobile Os?
For the hundreds of dollars in apps I would lose, it would take the most amazing mobile os to convince me to change and right now Android does it all for me.
Sent from my Galaxy Note 2 using Tapatalk 2
The only thing that worries me is applications. If ubuntu is able to use apps for Android it world be great. But I doubt it will have access to play store.
Sent from my GT-N7100 using xda app-developers app
But if it's using Android Drivers and Kernel, would it not be possible to tweak it to allow compatibility for Android Apps? Or at the very least the possibility to dual-boot it with a Siyah (or similar) kernel, so you get the best of both worlds, who knows perhaps they will even work out some sort of deal with Google to use the Play store by the time the first Ubuntu devices hit the market
Great clip of it in action
http://www.youtube.com/watch?v=LoXpLUr5WB4
Sent from my GT-N7100 using xda app-developers app
God, that just looks so sleek!
Man I cannot wait! Please post if you know of a way to get the ball rolling on this.
Yeah i know how to get the ball rolling....first you need a flashable image, and since that hasnt been released yet....good luck with that
Sent from my GT-N7100 using xda premium
speedyjay said:
Yeah i know how to get the ball rolling....first you need a flashable image, and since that hasnt been released yet....good luck with that
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yeah I think I'm going to break my F5 key....
Therev86 said:
But if it's using Android Drivers and Kernel, would it not be possible to tweak it to allow compatibility for Android Apps? Or at the very least the possibility to dual-boot it with a Siyah (or similar) kernel, so you get the best of both worlds, who knows perhaps they will even work out some sort of deal with Google to use the Play store by the time the first Ubuntu devices hit the market
Click to expand...
Click to collapse
I don't think it would be in googles interest to give a competing OS a helping hand.
baileyjr said:
I don't think it would be in googles interest to give a competing OS a helping hand.
Click to expand...
Click to collapse
Next you know, Googlux is the biggest player around
Sent from my GT-N7100 using Tapatalk 2
Ubuntu for note2
there are a few devs working on this port... nothing other than the interface works right now... but there's steady progress... so expect it in a month or so...

Overlooked Mobile Application Testing Condition

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.

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