Related
http://maemo.nokia.com/n900/
Looks good, wonder if it will run android?
Looks like it probably would.. if it doesn't already. The specs all looks similar to android phones...
Are you retarded? It runs Maemo software designed by Nokia. It could run android but it won't.
looks very nice a little big though
Honestly77 said:
Are you retarded? It runs Maemo software designed by Nokia. It could run android but it won't.
Click to expand...
Click to collapse
Did you read the title of the post? As in someone porting Android. That thing has nice hardware.
plazmagog said:
Did you read the title of the post? As in someone porting Android. That thing has nice hardware.
Click to expand...
Click to collapse
wow reading the specs i was just like "wow" lol ... if someone is able to run android on it successfully i might have to leave my g1 behind... :\
its got an arm processor so it could run android(theoretically) this would run hero sooooooooooooo easily the only thing that would put me off this device is the 3 row keyboard ewww
JJbdoggg said:
its got an arm processor so it could run android(theoretically) this would run hero sooooooooooooo easily the only thing that would put me off this device is the 3 row keyboard ewww
Click to expand...
Click to collapse
I agree, 3 row is inferior. But ya know, I'll take that over on-screen or standard dial pad any day.
I'm hoping that ARM cores are doing the same thing as x86 did in the past, running more cycles at a lower clock speed. May only be a 72 mhz jump over the dream's Qualcomm, but the performance increase may more than you'd expect.... hopefully.
plazmagog said:
http://maemo.nokia.com/n900/
Looks good, wonder if it will run android?
Click to expand...
Click to collapse
Isn't Maemo Linux based? It could be hackable...
NickMl said:
Isn't Maemo Linux based? It could be hackable...
Click to expand...
Click to collapse
The device description says "Linux-based operating system". An Android-Port might be doable.
Plus the N900 has AWS(1700/2100) support... so T-Mobile US release in the next few months?
Very impressive and so kool!
Maemo is linux based device built on Debian system struct with gnome
Any information about system specs requirement?
is there way to hack it to run on another device?
WOW, finally I have found a substitute for my G1... Maemo is a very interesting system, and the hardware is Nokia; yes, when the price will become human (for me 300-350 euros) I consider the idea to buy it.
Asking to get Android on a Maemo device is like saying you want to get windows mobile on your windows UMPC.
zellbz said:
Plus the N900 has AWS(1700/2100) support... so T-Mobile US release in the next few months?
Click to expand...
Click to collapse
Looks like it according to Tmonews.com. The FCC approved it a few days ago, so it shouldn't be long.
Here's the N810 running Android.
http://www.youtube.com/watch?v=xcJYWSe5HRU
And here's something more interesting
http://www.youtube.com/watch?v=UNo6pn-dnSQ
This device is extremely capable, maemo is an an open source OS, more open than Android.
aGoGo said:
Here's the N810 running Android.
http://www.youtube.com/watch?v=xcJYWSe5HRU
And here's something more interesting
http://www.youtube.com/watch?v=UNo6pn-dnSQ
This device is extremely capable, maemo is an an open source OS, more open than Android.
Click to expand...
Click to collapse
Can you please post some good links on which you based your last statement? I'm curious about maemo and would like to see how it's more open than Android. I'm surprised to see another open-source contender already...
opensource till T-mo get their hands on the rom. This IS an impressive phone. I was saving my upgrade for the MyTouch, looks like I might wait for this.
phatmanxxl said:
opensource till T-mo get their hands on the rom. This IS an impressive phone. I was saving my upgrade for the MyTouch, looks like I might wait for this.
Click to expand...
Click to collapse
Yeah, I have an upgrade and was disappointed by the Mytouch, so decided to hold off and see what other Android phones t-mo had in the pipeline. I want something with a hardware keyboard. Anyway, check out this video of the N900 intro by Nokia...my mouth is watering!
It looks like it has flash built in too! AAaaargh!!!
http://www.youtube.com/watch?v=Au_uRmoy8Fs&feature=player_embedded
I want this phone......now!
Hi
Any info on Android for this phone?
Just bought it and i'm looking forward to play with it.
Nicolai
Or WM 6.5.x ROM... would be also great...
I will support Android on wave s8500.
kenkiller said:
It will never happen.
Click to expand...
Click to collapse
What i am more interested in is a bada rom on our android devices, is bada open source ?
yes bada is opensource...
I have a general question. If a mobile OS is open source like Android and Bada, does that mean things like drivers for the antenna and important system level files are subject to being altered? Beyond just device stability, can you alter a device to crash, do harm, or infest the cell network its hooked up to? What about altering the antenna to broadcast and receive prohibited signals that screw with important communications systems? Basically I was just wondering how far you could go with an open source OS and if any dangers like these existed. I guess this would also apply to Linux on a computer as well?
actually, Samsung Wave is very similar to the Galaxy... And BadaOS is based on Linux like Android, so i although thought a port should be not that great deal... but it seems that no developer are interested in Samsungs Wave.
yeah its very similar, might be ported soon
for the next apps for android in samsung s8500 is possible, with the ROM share and security, that enbales to install better safety and good measures for all its use. The use of openoffice with new device that can make more faster, compliant and user friendly.
loosa2k said:
actually, Samsung Wave is very similar to the Galaxy... And BadaOS is based on Linux like Android, so i although thought a port should be not that great deal... but it seems that no developer are interested in Samsungs Wave.
Click to expand...
Click to collapse
Yup
Tis a shame
http://android-developers.blogspot.com/2011/01/android-30-platform-preview-and-updated.html
v0kal said:
http://android-developers.blogspot.com/2011/01/android-30-platform-preview-and-updated.html
Click to expand...
Click to collapse
As of now this is all I would be interested in from 3.0 . Hope cyanogen can pull this into CM7
New types of connectivity: New APIs for Bluetooth A2DP and HSP let applications offer audio streaming and headset control. Support for Bluetooth insecure socket connection lets applications connect to simple devices that may not have a user interface.
Yep seems to be a preview SDK for 3.0 with a final SDK in coming weeks. Simply prep for Honeycomb tablets.
"A built-in GL renderer lets developers request hardware-acceleration of common 2D rendering operations in their apps, across the entire app or only in specific activities or views."
So it seems that 2.3 isn't hardware accelerated...now I want 3.0 on my desire . But here's another quote:
"Android 3.0 (Honeycomb) is a new version of the Android platform that is designed from the ground up for devices with larger screen sizes, particularly tablets."
So Honycomb isn't for phones? I really hope Google can clear things up a bit because I remember Andy rubben saying the Honycomb can adapt to phones & tablets.
Any thoughts or theories?
Weren't there enough thoughts and theories about it?
Jack_R1 said:
Weren't there enough thoughts and theories about it?
Click to expand...
Click to collapse
Yes there was a lot of theories, but now we have something official to discuss rather than hearsay. Anyway, don't discuss if you don't feel like it.
How about the 2.4? really don't know what Goolge is thinking about. Just want a stable version and improve it by other works. Not so much version and make people confuse. It seems that N1 may not flash it~~
mr.r9 said:
Yes there was a lot of theories, but now we have something official to discuss rather than hearsay. Anyway, don't discuss if you don't feel like it.
Click to expand...
Click to collapse
Looking at the new preview SDK, it only big screens by default. And reading through the platform highlights really only mentions tablets. However, a couple Android devs have already stated its for all platforms. Seems to me that they don't want to reveal that its for phones yet, so that they can advertise that it is made for tablets.
The main criticism the iPad got was being a giant iPhone. I think they want to avoid that by having people believe that it isn't the same Android that is on phones.
I guess when they release the full SDK we'll know for sure.
Interesting...the beat goes on!
Honeycomb is also for phones, but we all knew that right?
From the documentation:
Publishing your app for tablet-type devices only
Additionally, you should decide whether your application is for only tablet devices (specifically, xlarge devices) or for devices of all sizes that may run Android 3.0.
If your application is only for tablets (xlarge screens; not for mobile devices/phones), then you should include the <supports-screens> element in your manifest with all sizes except for xlarge declared false.
With this declaration, you indicate that your application does not support any screen size except extra large. External services such as Android Market may use this to filter your application from devices that do not have an extra large screen.
Otherwise, if you want your application to be available to both small devices (phones) and large devices (tablets), do not include the <supports-screens> element.
Click to expand...
Click to collapse
Well, all clear then! The future of Android looks neat!
Nice find
Sent from my Nexus One using XDA App
spamlucal said:
Honeycomb is also for phones, but we all knew that right?
From the documentation:
Well, all clear then! The future of Android looks neat!
Click to expand...
Click to collapse
Hmmmm...good find! Android is getting really interesting visually, which is IMO a milestone it needed to reach a while ago
Anyway, can't wait for an alpha sdk image on my phone to play with if that's possible currently
Forget Ginga and Honeycomb. Havent you all hear of whats ahead of honeycomb? Its called " Chicken Soup". Yup, ik... Weird name. But its only for dual core over 2ghz. So phones arent ready. Its suppose to be completely holographic 3d without glasses. Pretty neat. And requires horsepower of xbox 360 or more. Anything less and its a no go. Its suppose to be the next gen OS and quantum leap from even honeycomb. Remember the name "chicken soup". Its comming next year by christman. Cant wait!
Sent from my SPH-D700 using Tapatalk
SINNN said:
Forget Ginga and Honeycomb. Havent you all hear of whats ahead of honeycomb? Its called " Chicken Soup". Yup, ik... Weird name. But its only for dual core over 2ghz. So phones arent ready. Its suppose to be completely holographic 3d without glasses. Pretty neat. And requires horsepower of xbox 360 or more. Anything less and its a no go. Its suppose to be the next gen OS and quantum leap from even honeycomb. Remember the name "chicken soup". Its comming next year by christman. Cant wait!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
This was a horrible and incredibly illogical troll/joke attempt
spamlucal said:
Honeycomb is also for phones, but we all knew that right?
From the documentation:
Well, all clear then! The future of Android looks neat!
Click to expand...
Click to collapse
It actually does not mean much.
Android application could always define different layouts for different resolutions, orientations, themes or screen sizes. So, it is just one additional form factor, one of many. And the way to say to the market which layouts are supported and which are not.
It also does not mean, that "honeycomb for phones" would be the same as honeycomb for tablets "just smaller".
They only said, that phone version will move in similar direction. Which can mean pretty much anything.
In fact I expect, that honeycomb for phones will be seriously different, since a lot of new honeycomb for tablets features on smaller screens do not make any sense.
My theory:
Honeycomb is currently, Tablets only.
We are going to see a division in Android for Phones and Android for Tablets.
Tablets will be at 3.0 starting off.
Phones are currently at 2.3, and will continue 2.4 being Gingerbread as well with updates that should have happened with 2.3. (Like 2.0 and 2.1 being Eclair)
Once phones have the ability to run such a resource hungry operating system(3.0) the Phone and Tablet versions of Android will merge into one.
Wisefire said:
My theory:
Honeycomb is currently, Tablets only.
We are going to see a division in Android for Phones and Android for Tablets.
Tablets will be at 3.0 starting off.
Phones are currently at 2.3, and will continue 2.4 being Gingerbread as well with updates that should have happened with 2.3. (Like 2.0 and 2.1 being Eclair)
Once phones have the ability to run such a resource hungry operating system(3.0) the Phone and Tablet versions of Android will merge into one.
Click to expand...
Click to collapse
But the hardware of the new tablets is the same Tegra 2 of the new phones, so I think the problem is the adaptability of the OS to smaller screens in a way it is usable for our fingers.
Anyone here used the leaked "honeycomb music player"? It has all the new characteristics we saw on the xoom tablet but worked very nice on my Nexus One with 2.2.1.
I think when honeycomb's source code come out we will get working builds.
Sent from my Nexus One using XDA App
I heard Ice cream is going to be only for refrigerators. You know cause of the thermostat API that very few phones support.
marlonbr said:
But the hardware of the new tablets is the same Tegra 2 of the new phones, so I think the problem is the adaptability of the OS to smaller screens in a way it is usable for our fingers.
Anyone here used the leaked "honeycomb music player"? It has all the new characteristics we saw on the xoom tablet but worked very nice on my Nexus One with 2.2.1.
I think when honeycomb's source code come out we will get working builds.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I believe you are absolutely right. I tried making an AVD for Honeycomb with the screen resolution of my Nexus One. The launcher force closed continuously but you could see that the standard pull down notification bar was there. So I take that to mean that Honeycomb is for all devices and just changes its layout based on screen size.
draugaz said:
It actually does not mean much.
Click to expand...
Click to collapse
A little bit of context: The text I copy-pasted is in a section called "Upgrade or Develop a New App for Tablets and Similar Devices"
In it, is says:
If you want to develop something truly for tablet-type devices running Android 3.0, then you need to use new APIs available in Android 3.0. This section introduces some of the new features that you should use.
The first thing to do when you create a project with the Android 3.0 preview is set the <uses-sdk> element to use "Honeycomb" for the android:minSdkVersion.
Click to expand...
Click to collapse
What does this mean? it means this app won't work on anything other lower than honeycomb. So, the "choose your screen size" text I pasted yesterday applies to honeycomb-only apps.
The documentation in the SDK is a nice read actually
I just finished my app and I'd love it if you all could give it a try! The purpose is simple: bring multi-touch gesture support to Windows.
Check out what I mean on YouTube (I can't post links for some reason...): youtube.com/watch?v=pCorg-ZJVJU
It's called TouchMe Gesture Studio and you can grab it from the Store here: bit.ly/MqnEm7
Or just search the Store for "TouchMe"
Let me know what you think!
looks cool too bad I have an rt but otherwise I would have gave it a spin
buffalosolja42 said:
looks cool too bad I have an rt but otherwise I would have gave it a spin
Click to expand...
Click to collapse
Sorry man- I really wish I could support RT, I have the original Surface myself. During development, I fantasized that I'd create an ARM compiled version for jail broken devices, but I don't think anyone's pulled that off yet. Maybe after the platform's matured a bit, I won't need the desktop component =]
Hmm... do you not control the code for the gesture engine? It should be pretty easy to re-compile, if you have access to it. I'm pretty sure RT supports all the new touch-related APIs added in Win8.
It looks like the Metro app itself could probably be ported easily enough, but it doesn't do much good to export a file that nothing on the system can use...
GoodDayToDie said:
Hmm... do you not control the code for the gesture engine? It should be pretty easy to re-compile, if you have access to it. I'm pretty sure RT supports all the new touch-related APIs added in Win8.
It looks like the Metro app itself could probably be ported easily enough, but it doesn't do much good to export a file that nothing on the system can use...
Click to expand...
Click to collapse
The Metro app runs well in 8.1, the only restriction is that I didn't publish a version in the Store because it'd be nothing more than a tease (and a great way to attract helpful reviews like "this sucks, doesn't work. don't waste your time").
And I wrote it from scratch, so I most certainly have access to the engine's source as well . But even if I did compile an ARM version, it wouldn't be signed by Microsoft, so it wouldn't work. Unless you're suggesting that I compile it for jail broken Win 8 (non 8.1) devices?
Well I am going to follow this development just in case you do the RT. I have a pretty nice laptop/workstation and my RT really fills the void well and with rdp and teamviewer I really haven't needed the full version as of yet. I wish I had the time to learn to code or assist I would gladly help out.
Just FYI- the app has been updated to include rotation gestures =]
In case anyone's interested. The latest update now supports snapped view and a printable gesture list!
ybahman said:
In case anyone's interested. The latest update now supports snapped view and a printable gesture list!
Click to expand...
Click to collapse
Nice app! But the price is too much for something you can definetly live without!
I would consider it for 2$ , but no more...
searchworlds said:
Nice app! But the price is too much for something you can definetly live without!
I would consider it for 2$ , but no more...
Click to expand...
Click to collapse
That's why there's a 32 day trial to change your mind about the "live without" bit
Latest update now includes a sweet feature to help you determine your battery percentage from within a modern app!
Looks like Cyanogen moving towards their Google Services(less) future with Microsoft. Eugh.. will just mean a pile of microsoft app bloat that I dont use to be removed, hopefully we will still just be able to flash a gapps package though?
http://www.marketwired.com/press-release/-2010445.htm
I'm actually happy with this. Microsoft apps are great in terms of quality and design. I wish they'd started earlier so I wouldn't have settled to Evernote back in the days.
Rosa Elefant said:
I'm actually happy with this. Microsoft apps are great in terms of quality and design. I wish they'd started earlier so I wouldn't have settled to Evernote back in the days.
Click to expand...
Click to collapse
To be fair it may make their OS a little bit more consistent/polished/professional, instead of integrated apps from here and there. But I just dont use any MS products anymore (aside from office programs) and so it wouldnt be of any benefit to me.
Cyanogen Inc. can do as they please. As long as they don't lock me down to anything.
This isn't terrible news. The Microsoft mobile suite is actually really nice. I loved my Windows Phone, the only reason I got rid of it was lack of dev support for apps that I needed.
meh, this just means I definitely won't be using Cyanogen ROMS
I'm all for the idea they have on stripping away Google's influence of Android. However, teaming up with Microsoft doesn't seem the way to do it. It's like trading a Mercedes for a Kia. (no offense to those that drive Kia's)
ciwrl @CyanogenMod said:
To highlight the one take away that matters to CyanogenMod users – We are not bundling or pre-installing Microsoft (or any Cyanogen OS exclusive partner apps) into CyanogenMod.
Click to expand...
Click to collapse
Just like they don't bundle Google services and apps into CM11/12 now which is why you have to flash gapps with nightlies if you want them.
ciwrl @CyanogenMod said:
Your nightlies will not see a sudden influx of Microsoft applications – you can put the pitchforks down. CyanogenMod has historically stayed neutral on your services of choice, whether you use Google, Amazon or Fdroid; we leave that decision to you and we have no intention of changing that.
Click to expand...
Click to collapse
How will it affect nightlies?
ciwrl @CyanogenMod said:
What you will see are new APIs available in the source code, using CM as a platform for other developers to do cool things with. Remember when CM 9 had support for Host Card Emulation well before that functionality was available in Android proper? How about adhoc WiFi support? Those kinds of pushing forward of the Android platform are something we have done for years, and will continue to support whenever we can – but do so in a non-’force you into it’ manner. We’re all about options here.
Click to expand...
Click to collapse
Source
itsamoreh said:
meh, this just means I definitely won't be using Cyanogen ROMS
Click to expand...
Click to collapse
+1 Microsoft products arent optimized, function only the way they dictate. Bugs, backdoors and battery eaters.
demographics: worst strategic move ever, there is a reason Cyanogen users dont own a windows phone.
Microsoft seems to be following Blackberry in this
I'm all for Microsoft. I don't use anything google related that's important enough for me. Email, calendar and contacts are all Microsoft for this guy.
Sent from my A0001 using XDA Free mobile app