[Q] Whish aspect ratios I must consider? - Design, Prototyping, UI, Graphics

[Q] Whish aspect ratios I must consider? - Design, Prototyping, UI, Graphics

Hi everybody,
I'm a new mobile developer, I target android devices.
I have some trouble. It concerns the Aspect ratio and dimensions of the devices. this is important for me because I must give those values to the designer so that he could realize images.
So I want to know The aspect ratio and screen sizes used in android devices.
Thanks for help you can offer.

Android designing should be done with specific ratio so that it vary with different devices and adjust its size according to that. Try to use weight property, wrap content or match parent. Don’t use numeric value, its static so it is only for your device and in other devices it changes

Take a look
I strongly suggest you to visit this page to know basics of android app designing.. developer.android.com/training/multiscreen/index.html
[Note : if you know basics already, take a closer look into the page. Its still inspiring]

Related

So, how many aspect ratios will WP7S have exactly?

Windows Phone Thoughts have noticed something that slipped most people's attention: there was an announcement about two resolutions, WVGA and HVGA, supported by WP7S, which makes two aspect ratios. Hardware scaler or not, this is a problem in terms of UI development. So either this is a strange change in MS's approach, or there's a simple typo/mistake somewhere.

I got the same question because I notice 2 different aspect ratios:
800x480 and 480x320.
Both are different.
And this morning, I found the answer from Microsoft developer Shawn Hargreaves:
http://blogs.msdn.com/shawnhar/archive/2010/03/12/reach-vs-hidef.aspx
Sunday, March 14, 2010 11:56 PM by ShawnHargreaves
# re: Reach vs. HiDef
> Why there are 2 different aspect ratios?
> 800x480 vs 480x320
> Game screen will look different.
If you just program to a fixed resolution, you will get letterboxing (black bars) if the game is played on a device with a different aspect ratio. Everything will still work fine, though, and we will never stretch or distort the image.
If you want to detect the native resolution and adjust your rendering for different aspect ratios, you can do that to. I think it will depend on the game which is the better/easier way to go.
Click to expand...
Click to collapse
So, there you go
vangrieg said:
Windows Phone Thoughts have noticed something that slipped most people's attention: there was an announcement about two resolutions, WVGA and HVGA, supported by WP7S, which makes two aspect ratios. Hardware scaler or not, this is a problem in terms of UI development. So either this is a strange change in MS's approach, or there's a simple typo/mistake somewhere.
Click to expand...
Click to collapse

I think they are really wanting to appeal to the business user with the 480x320 resolution and front facing qwerty. I don't think games with be a big deal on these devices. It's nice to see some diversity hopefully it doesn't cause any issues.

But it's most certainly an issue and it really goes against everything they preach with regard to platform standardization. I also can't quite imagine their start screen working well on a small landscape-oriented screen. What a weird twist.

The second aspect ratio, HVGA 480x320 will be a bit wider on the 320 side compared to the first aspect ratio.
I expect the main gui aspect ratio will not be stretched, but the "cut off" screen will be much more shown.

Well, we know very little about the 480x320 version anyway. Who knows what that one will be like?

They didn't learn sh!t from the past....
In theory, it’s usually considered best to write programs that adapt themselves to any screen
size, but that’s not always possible, particularly with game development. You will probably find
yourself specifically targeting these two screen sizes, even to the extent of having if/else clauses
and different XAML files for layout that is size-dependent.
Click to expand...
Click to collapse

Launch res: 480h/800w = 0.60
Second res: 320h/480w = 0.67
I don't think the hardware scaler is going to have a hard time dealing with this. When I saw them demo it at GDC I couldn't tell a difference. The developer will only have to work on one aspect ratio / pixel count and the phone will do the rest of the work automatically, they said.

change evo screen ppi / pixel density?

i know theres a thousand of these threads but i really want to see this happen so what the hell
is it possible to change the evos screen density from 480x800 to its proper full size via a flashable package or a root required apk? i refuse to believe the true 1:1 density of the evo is the same as the n1 and others yet its AT LEAST .5 INCHES bigger than them all. i think that if we can increase the resolution it will help balance the the bleh factor of its not so vibrant lcd screen.
figures the biggest screen of them all is also be the most dull of them all (they probably did it for battery life or something, oh well).
im looking for the true resolution on the Internet but i haven't found it yet. i know ive seen it somewhere before, but it was forever ago.
if someone finds it before me please post the size and link the source. thanks!

I think you have a critical misunderstanding. The Evo's resolution is 800x480. That means that is has 800 pixels in one direction and 480 pixels in the other direction. The Nexus One has the same number of pixels in each direction, but each one is smaller because it has a smaller display. In general, the smaller the pixel, the more expensive the display because it isn't easy to make very small pixels. There is no application that can magically create more pixels or make your current pixels smaller. The native resolution of a display is absolutely fixed.
You can refuse to believe this or that they sky is blue all you want. It doesn't change the fact that it is true.

can i get some other answers than those of an unhelpful condescending little child, please?
im not a retard i know you cant physically change a screen to have more pixels. what i want is to change the resolution to something along the lines of 720p 1280×720. theres no need to try to put yourself on top of me like your better than me, its a waste of time for you to type me to read and space and bandwidth on xda's servers
close thread

He answered your question and you're just not willing to accept that you have no idea what you're talking about.
The resolution of the screen (and therefore the pixel density) isn't changing. There isn't some magic hack to change it, or optimize it to be something that it's not. Perhaps you could get it to run at a lower resolution, but that would make the problem worse and not better.

you cant make 1280 pixels out of 800. on another topic if a dev would be kind enough to write a script to make my battery life double thankyou.

daktah said:
can i get some other answers than those of an unhelpful condescending little child, please?
im not a retard i know you cant physically change a screen to have more pixels. what i want is to change the resolution to something along the lines of 720p 1280×720. theres no need to try to put yourself on top of me like your better than me, its a waste of time for you to type me to read and space and bandwidth on xda's servers
close thread
Click to expand...
Click to collapse

Aren't you really asking to physically get more pixels on to the screen? The only other way to interpret what you are asking for is if you're trying to get content of higher resolution to fit on the device? Pixels is pixels, if the screen itself was physically 1280x720 native and HTC limited the display resolution to 800x480 for whatever reason, then you can fix it.
As it stands, 800x480 is the native resolution of the panel, any higher resolution content that you try to play will be downscaled to the best of the software's ability so even if you use an app thats designed for the higher res (none that i know of) or a video / picture, it will be downscaled to fit 800x480 when you make it full screen or try to make it fit.
You can buy a 42 inch 1080p screen and a 42 inch 720p screen, and any 1080p content played on the 720p will be downscaled, and vice versa in the other direction. You're asking to transcend physical limits of a device thats not really possible.

daktah said:
can i get some other answers than those of an unhelpful condescending little child, please?
im not a retard i know you cant physically change a screen to have more pixels. what i want is to change the resolution to something along the lines of 720p 1280×720. theres no need to try to put yourself on top of me like your better than me, its a waste of time for you to type me to read and space and bandwidth on xda's servers
close thread
Click to expand...
Click to collapse
He actually answered your question quite well and absolutely correctly. Don't be so defensive. There's a lot of smart guys on here and you're really bringing yourself down by (irrationally) not believing him.

Here's my question: when using our video recorder and set it to 720, that's obviously a higher resolution, so does the fone downgrade the quality until its played on a higher resolution screen? Or do we actually see it in 720 as its being recorded? Sorry if this seems like a weird question, the point I'm getting at is the if the fone is playing back the video that's 1280*720 then it wouldn't it be capable of higher resolution? Just wondering

th3_g00b said:
Here's my question: when using our video recorder and set it to 720, that's obviously a higher resolution, so does the fone downgrade the quality until its played on a higher resolution screen? Or do we actually see it in 720 as its being recorded?
Click to expand...
Click to collapse
It wouldn't be able to be played in 720 so I would assume it is being downscaled when played on the EVO

063_XOBX said:
It wouldn't be able to be played in 720 so I would assume it is being downscaled when played on the EVO
Click to expand...
Click to collapse
Ok thank you

There was an app for windows mobile that would allow you to change the dpi which made the screen look a lot bigger of course everything on the screen was a lot smaller. The way I see it is like the native resolution on a pc monitor usually lower than what it can support aka native might be 800x1024 but you could feed it video at 1280x1600 making everything look smaller but making the screen look much bigger.
So yes he was wrong changing the pixels is impossible but changing the appearance of the screen like stated above is possible. I think that this is what he was trying to say.

063_XOBX said:
It wouldn't be able to be played in 720 so I would assume it is being downscaled when played on the EVO
Click to expand...
Click to collapse
Yeah I would assume it just scales the video in the same way that Windows Media player does when you adjust the size of a video by expanding/contracting the window. The media player on the evo probably has some kind of pixel compensation going on.
Minjin:
I have to agree that you are right, but the 2nd comment was a little condescending. Not all of the people who peruse these forums are quite as technically inclined as some of us.
daktah:
Chill out dude. But to answer your question, no you can't. The size of the pixel is set in the screen, as you get more pixels on the same size display your density increases and the display gets to be more expensive to produce. Screens like the Evo's which are very large are sacrificing resolution for price.
As per your comparison, yes the N1 and Evo have the same resolution, but the N1 has a higher pixel density.
Generally you can't upgrade the resolution of monitors over the native resolution because the driver would have to start to selectively merge or delete lines of pixels to make it fit (or make a scrollable work space). When you downgrade resolution on a display it starts to merge pixels (IE if you put 800x600 on a 1600x1200 display, "1 pixel" is now actually 4 pixels merged to replicate 1

gx1400 said:
Minjin:
I have to agree that you are right, but the 2nd comment was a little condescending. Not all of the people who peruse these forums are quite as technically inclined as some of us.
Click to expand...
Click to collapse
When someone says "I refuse to believe", we're not dealing with a lack of technical knowledge, but instead a lack of maturity. My experience with people like that is that you can make the most logically sound argument in the world and it won't do a thing.

cant fix stupid.

QUOTE=daktah;7150273]can i get some other answers than those of an unhelpful condescending little child, please?
im not a retard i know you cant physically change a screen to have more pixels. what i want is to change the resolution to something along the lines of 720p 1280×720. theres no need to try to put yourself on top of me like your better than me, its a waste of time for you to type me to read and space and bandwidth on xda's servers
close thread[/QUOTE]
There are so many stupid questions on here folks getting really tired of being nice
Sent from my Evo on on the Now network from Sprint
oh and duck Apple

I have another question. Does the resolution have anything to do with how vibrant the color of the screen is? Like how on a desktop u can change the contrast and so forth? It would be nice to have an app to adjust those settings

daktah said:
can i get some other answers than those of an unhelpful condescending little child, please?
im not a retard i know you cant physically change a screen to have more pixels. what i want is to change the resolution to something along the lines of 720p 1280×720. theres no need to try to put yourself on top of me like your better than me, its a waste of time for you to type me to read and space and bandwidth on xda's servers
close thread
Click to expand...
Click to collapse
yes, you apparently are a retard. you know that you can't physically change the screen to have more pixels, yet you still want to change the screen to display more pixels. he gives you the answer to your question and you refuse to believe it. tell me, how are you not being retarded?

daktah said:
can i get some other answers than those of an unhelpful condescending little child, please?
im not a retard i know you cant physically change a screen to have more pixels. what i want is to change the resolution to something along the lines of 720p 1280×720. theres no need to try to put yourself on top of me like your better than me, its a waste of time for you to type me to read and space and bandwidth on xda's servers
close thread
Click to expand...
Click to collapse
He is better than you though.

So apparently you can do this now... There's an app in the Market or you can edit your own build.prop file and reboot. Make sure you nandroid first.

Nokia 900 "Hydra" rumored to have dual-core CPU, Q1 2012 release date

Hey guys this is Saad from Windows Phone Daily,
I thought I'd share this on here since it doesn't look like any of the bigger WP7 sites have picked up on this yet.
A Nokia 900 "Hydra" just leaked from Daily Mobile Forum and it has some really impressive specs: a 4" CBD AMOLED, 1.5 GHz dual-core(!) processor, 720p display, 12MP Carl Zeiss camera, 1080p video recording, and new "swipe gestures" in the OS (maybe something like Windows 8).
More details can be found in our article: http://www.windowsphonedaily.com/2011/10/rumor-nokia-900-hydra-packs-dual-core.html
aaaand here's the original source: http://forum.dailymobile.se/index.php?topic=52961.0
Enjoy!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

too good to be true, but hey

The fact that it claims to have "720p screen resolution" is proof enough that this is not real.

Well there's fake, and then there's this.

First of all the resolution. 720p screen resolution would be a direct violation against all of Microsoft's chassis specifications. The resolution is limited to 800x480 for a reason, to make it easier for developers. If this were true Microsoft would be on the very slippery slope of fragmentation.
To clarify: The platform is currently designed for one resolution and that resolution only. More or less the only possible way to continue from this is screens with the resolution 1600x960, exactly doubled on both sides. This was the way that Apple upgraded the screen between iPhone 3G(S) and iPhone 4 and it was for a very good reason: To keep app compability. If Microsoft were to allow a new resolution almost all apps would need a patch for that new resolution. Would Microsoft kill a majority of their Marketplace? no.
None of the current chassis specifications define any support for a Dual Core processor, so that is not likely at this time, maybe next update.
"Dedicated graphic adapter" sounds a bit fishy. It sounds to a reference to a dedicated GPU chip as opposed to todays SoC chips where everything is integrated on one chip. I'm not an expert in the area but it certainly sounds strange that someone suddenly would design a chip very differently from everyone else.
4 Sterophonic loudspeakers. I think that this certainly sounds strange, not sure what they mean with that.
USB 3.0 and NFC doesn't feel very likely. On the other hand Nokia is able to do this with the special privileges Microsoft gave them. I'm not as certain on this one as the others.
Also, don't you all think that the picture doesn't look very professionally done?
Source post
This was up almost two months ago and a whole load of unresponsible news sites did write the news like this was a fact, absolutely disregarding how obviously fake it is.

Why wont apps be compatible with different resolutions? On Android they work well regardless of what resolution. Whats different in WP?

Interesting how the back and search buttons are missing too. Also, the technical specification seems to include a price.
Looks like the picture was drawn by a kid

If true this may be my next device

Almost no bezel at the corners? No way, that looks fake as hell. The only specs I'm really interested now are expendable memory and screen resolution. And a bit more RAM for extended multi-tasking, maybe.

I can't believe people are actually conversing about this trash.
I also can't believe I typed this reply.
And screen resolution doesn't matter in WP7 as the OS uses a scalar. Things would be automatically upscaled. It's why the phone's UI performs well on the launch specs. The resources the phone displays is actually lower resolution that you'd assume they are. iOS doesn't use a scalar so resources have to be appropriately scaled for the display resolution. That's why developers needed to update for iOS5 and develop new iPad apps. Android is similar.

N8ter said:
I can't believe people are actually conversing about this trash.
I also can't believe I typed this reply.
And screen resolution doesn't matter in WP7 as the OS uses a scalar. Things would be automatically upscaled. It's why the phone's UI performs well on the launch specs. The resources the phone displays is actually lower resolution that you'd assume they are. iOS doesn't use a scalar so resources have to be appropriately scaled for the display resolution. That's why developers needed to update for iOS5 and develop new iPad apps. Android is similar.
Click to expand...
Click to collapse
I don't know what you are talking about. I've looked into a Dumped ROM & extracted the PNG's from the DLL's & they are full size. They are NOT low res images scaled up. If they were, they'd look blurry like early WVGA Titanium Themes that were just edited WQVGA CPR's with no changes to the graphics. The Tiles & Icons are 173x173/62 x 62 pixels. That is full size. The 1st Part Tiles & Icons are a bit smaller only because they are just the Icons inside the Tiles, not the whole Tile like for 3rd Party apps. Developers have been making their Tiles cheaply. You'll notice the Tile image is called Background, meaning it's the background of the Tile Image & there should be a separate Tile Icon that goes "over" it.
To get back on topic, I highly doubt this is real as per resolution unless MS actually gave Nokia special permissions to edit the UIB/UIX files. They are pretty much like the CPR's of Titanium, just compiled so we can't edit them ourselves yet. We have no tools to decompile/recompile them.

Wouldn't be as unbelievable if this was a Q3 device (though, ideally we'll have faster by then), but a Q1? Naaaah

Nearly every spec isn't supported. Fake.

Sir. Haxalot said:
First of all the resolution. 720p screen resolution would be a direct violation against all of Microsoft's chassis specifications. The resolution is limited to 800x480 for a reason, to make it easier for developers. If this were true Microsoft would be on the very slippery slope of fragmentation.
To clarify: The platform is currently designed for one resolution and that resolution only. More or less the only possible way to continue from this is screens with the resolution 1600x960, exactly doubled on both sides. This was the way that Apple upgraded the screen between iPhone 3G(S) and iPhone 4 and it was for a very good reason: To keep app compability. If Microsoft were to allow a new resolution almost all apps would need a patch for that new resolution. Would Microsoft kill a majority of their Marketplace? no.
None of the current chassis specifications define any support for a Dual Core processor, so that is not likely at this time, maybe next update.
"Dedicated graphic adapter" sounds a bit fishy. It sounds to a reference to a dedicated GPU chip as opposed to todays SoC chips where everything is integrated on one chip. I'm not an expert in the area but it certainly sounds strange that someone suddenly would design a chip very differently from everyone else.
4 Sterophonic loudspeakers. I think that this certainly sounds strange, not sure what they mean with that.
USB 3.0 and NFC doesn't feel very likely. On the other hand Nokia is able to do this with the special privileges Microsoft gave them. I'm not as certain on this one as the others.
Also, don't you all think that the picture doesn't look very professionally done?
Source post
This was up almost two months ago and a whole load of unresponsible news sites did write the news like this was a fact, absolutely disregarding how obviously fake it is.
Click to expand...
Click to collapse
Wow you're really out to get me Sir. Haxalot!
I am aware that this is from August, and I apologize for reporting on it as though it was new. However, this is not "obviously fake". Like I said in the article and my reply to you in the comments section, it is very likely that these specs will be introduced in the future. There's no reason why you can rule that out, unless you're Microsoft's lead Windows Phone manager.
It is a rumor and yes there are some things that do stretch the limits of reality--mostly the Q1 release which is completely ridiculous. BUT Nokia hasn't denied it and Microsoft hasn't denied it, so until then I will report on it.

OGCF said:
Wow you're really out to get me Sir. Haxalot!
I am aware that this is from August, and I apologize for reporting on it as though it was new. However, this is not "obviously fake". Like I said in the article and my reply to you in the comments section, it is very likely that these specs will be introduced in the future. There's no reason why you can rule that out, unless you're Microsoft's lead Windows Phone manager.
It is a rumor and yes there are some things that do stretch the limits of reality--mostly the Q1 release which is completely ridiculous. BUT Nokia hasn't denied it and Microsoft hasn't denied it, so until then I will report on it.
Click to expand...
Click to collapse
the problem is you're "reporting" something that isn't real by any stretch of the imagination. fake nonsense rumors like this fly so far below the radar of companies like MSFT and Nokia that they don't even know it exists, much less have the desire to deny it.

looks like kids drawing or someone in the night market drawed it...lol

This is fake. I thought everyone knew that. It's embarrassing that you would post it on your website EVEN with the disclaimer that it's just a rumor. This mockup is brought to you by the same fool that opened up paint for this one too:

Yes it's quite obvious the photo and what not is fake. However, someone email this to Nokia and make it happen for Apollo.

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.

Not very much out there on the 3d Scan capabilities. Resolution? Export formats?

Not very much out there on the 3d Scan capabilities. Any info available about resolution or export formats? Is it even working currently?

it is working sort of, after update it doesn't work for people and faces anymore, it's also very finicky about light, angles etc., but it can be done with patience. According to specs it supposed to be VGA and VGA should be 640x480??, but who knows in reality. It's a new tech, so I'm hoping for 3rd party apps in few months. When I did couple proper scans, it actually looked pretty good and you could probably export the data to other programs for more processing, maybe even 3D builder or 3D paint in Win10, but I haven't tried it yet. Personally I think it has potential, but it will take some time to develop software to take full advantage of it. There is also laser based distance measuring app based on TOF sensor on 10+, but again it has some limitations like max distance and reliability. Bottom line, doesn't bother anything by being there even if never used, but it could be useful in ways difficult to predict right now, so we will see.

Any update on this?

O4karitO said:
Any update on this?
Click to expand...
Click to collapse
I've used it with success to create a 3d scan of a vehicle part that I had mocked up, exported to obj to push/pull points, then offloaded the g code to my cnc.

That's actually quite impressive
Thanks

Develop Bugs

welcome