Develop Bugs

WP7 Install on N1

Dear Members,
It's a wierd thought but can WP7 be installed on NexusOne. I would live to test out the WP7, but i have the N1 unit.
Any thoughts ?
Sam

Ask again in a half year.
... but it's the correct CPU architecture (Snapdragon) iirc.

I doubt it would be possible...
There are no drivers for it, and I dont think it meets the minimum spec for WP7.

That's what i think, its the same processor, i dunno the Jargin for the detailed tech comparison, but from the looks of it, it shoudl be do-able, but is it worth the effort ?

Depends how much effort is required. To get started someone need to buy a WP7 phone, which isn't possible for another 3 months. (Or someone from Redmond to leak one).
Ask again in a half year.

You bought Android device that has Android bootloader and Android radio and what not hoping you would run WindowsCE base on it? Are you serious? Chance of getting WP7 or any WinCE kernel running on this (without any emulation or software like haret, even that would be hard to boot CE6 (I prefer "CE6.5" ) kernel) is like... Zero. Only HD2 (mostly TMOUS version due to 1GB ROM) has way bigger chance of getting unofficial update (since our top CE platform expert here aka DaG is working on it).

To general!
~~Tito~~

Maybe, depending on the driver coding for the N1 when compared to shipping HTC WP7 devices.

How Many APPS will be in Marketplace OCT 21st 2011???

Ok so there will be about 1000 APPS at Launch but in one years time how many APPS do you guys think the Marketplace will have and which 3 top tier APPS do you think will have been ported to WP7???
I predict 20,000 APPS and SKYPE, TOMTOM and Angry Birds will be in the Market Place.

It's not about quantity, it's about quality and applicability.
I only use about 6 apps, so as long as the 6 I need are on there, and they're good, I'm happy.

You are right Quality and the right Apps are important but so is Choice and this is where the number of APPS is important. Also if WP7 has sold millions of units there will be 000`s of APPS if it bombs there will be few APPS I think thats obvious..

Choice is fine but why would you choose an app that didn't do what you wanted or wasn't good enough?
What's the point in 300,000 apps if you only need 6? Especially if 299,000 of them are crud.
It's like going into an ice cream stall that has 5,000 flavours when all you want is a decent strawberry ice cream. The ice-cream stall just down the road might only do 10 flavours but may still have a better strawberry flavour than the stall with 5,000 flavours (4,900 of which are awful anyway).

I dont actually see the need for 300,000 APPS but equally 30,000 would probably be about right to cover the needs of all customers with an element of choice.
What ever you say about the Iphone its true that whatever you need there appears to be an App for it... Personally I think 5000 APPS would be way to few..
I trust : I trust Microsoft to keep an eye on Quality unlike Android where there is alot of nonsense APPS.
Equally some APPS just need to be ported as they are the Gold Standard.. this includes SKYPE,TOMTOM PANDORA/SPOTIFY and OPERA etc....

I see quite alot of useful app's on the android store. I'm new to android, having a galaxy S for just over 3 days now. Having come from symbian, over tens years, i feel a bit overfaced when i browse the android market. Lol.
Sent from my GT-I9000 using XDA App

Point taken I was probably not being fair on Android with 90,000 APPS there must be loads of good ones but maybe the percentage of good APPS on Iphone is better because of the control ???

I think there is meant to be between 1,000 and 2,000 applications when the phones launch tomorrow.

i agree with those guys who only need 6 apps and the rest are curd.... i only use parlingo app...the rest are from HTC... if the WP7 apps will be cheap as apple apps, only than there will be tons of apps on the marketplace...

Will GPU handle the UI smoother than the cpu ?

I am having a little argument with an iPhone sheep, and I told him the future Android phones will be much smoother for one main reason, they will change the UI acceleration to be handled by the GPU, instead of the cpu now. He said no way, Apple's iPhone will still be smoother, GPU or not, Android will still be choppy, compared to the iPhone.
How do you answer a Apple die hard like that ?
Is there an interview somewhere with Google developers talking about changing to GPU acceleration ?

You were right, leave it be.
Sent from my PC36100 using Tapatalk

There's absolutely no reason why Android couldn't run as smooth as the iPhone with the right optimizations and the right hardware. The Evo has two problems. The first is, as you said, that Android isn't using GPU acceleration in the interface, at least not effectively. That's on Google to fix.
The second problem is that the Adreno 200 GPU that's part of the Snapdragon processor we have is not as powerful as what the iPhone has, or even what other Android phones have, such as the Samsung Galaxy S. Even without whatever shifts to the GPU future versions of Android might have, the Galaxy S's Hummingbird is unquestionably smoother than the Evo's Snapdragon. I bought the Evo after the Epic was out and am happy with the choice, but on performance, the Epic was clearly better and arguably comparable to the iPhone in smoothness. So even without any software changes, the next generation of system-on-a-chip platforms (CPU + GPU) will narrow the gap significantly.
Combine both optimized software and better hardware, and it should be able to match the iPhone without a problem.

bkrodgers said:
There's absolutely no reason why Android couldn't run as smooth as the iPhone with the right optimizations and the right hardware. The Evo has two problems. The first is, as you said, that Android isn't using GPU acceleration in the interface, at least not effectively. That's on Google to fix.
The second problem is that the Adreno 200 GPU that's part of the Snapdragon processor we have is not as powerful as what the iPhone has, or even what other Android phones have, such as the Samsung Galaxy S. Even without whatever shifts to the GPU future versions of Android might have, the Galaxy S's Hummingbird is unquestionably smoother than the Evo's Snapdragon. I bought the Evo after the Epic was out and am happy with the choice, but on performance, the Epic was clearly better and arguably comparable to the iPhone in smoothness. So even without any software changes, the next generation of system-on-a-chip platforms (CPU + GPU) will narrow the gap significantly.
Combine both optimized software and better hardware, and it should be able to match the iPhone without a problem.
Click to expand...
Click to collapse
speaking of the hummingbird, isn't the A4 processor that apple uses a custom built hummingbird processor?

nosympathy said:
speaking of the hummingbird, isn't the A4 processor that apple uses a custom built hummingbird processor?
Click to expand...
Click to collapse
They're similar. Samsung makes both, but Apple had some hand in the design of the A4. More accurately, a company called Intrinsity, which Apple acquired.

Isn't the official use of the GPU to handle the UI acceleration going to be standard in "Ice Cream Sandwich" update ? And what OS # is Ice Cream going to be ? And approx release date ? 2nd half of 2011 I believe ?

Zorachus said:
Isn't the official use of the GPU to handle the UI acceleration going to be standard in "Ice Cream Sandwich" update ? And what OS # is Ice Cream going to be ? And approx release date ? 2nd half of 2011 I believe ?
Click to expand...
Click to collapse
Honeycomb has it.
http://code.google.com/p/android/issues/detail?id=6914#c197
It's unclear exactly what this means for phones right now. Honeycomb is for tablets, but they've also introduced API improvements and behind the scenes enhancements (like this one) that are unquestionably needed for phones.
It's sounding like Ice Cream may be that release, and it's probably going to be announced at Google I/O in May (speculation). It's possible we could see a scaled down version of Honeycomb for phones released before then. It's more a question of timing and names though -- whatever the next release of Android is for phones, I would expect it to have it.
It's even possible folks here will find a way to get Honeycomb working on phones in some form before we see anything official. That might be tough, since we'd want to keep the smaller screen UI of Gingerbread and just pull in the API and implementation improvements we want. But I'm always impressed by what people pull off here.

i altered a line on my old hero to use hw rendering for the ui and junk-it seemed to help a little. perhaps the same line can be tweaked/added for the evo. it was in the build prop i believe...

official GEN 10 : Jelly Bean

Version 4.1.0 - December 5th, 2012
Android Jelly Bean 4.1.1 firmware release
Archos Video: major upgrade with simplified video information retrieval and media indexing, new network shares infrastructure
Archos applications: future updates of Archos Video, Music, File Manager, System Monitor applications (embedded in the firmware) will be carried out through Google Play
http://update.archos.com/10/gen10/gen10_4.1.0/firmware_archos_it4x.aos
Great the mapping tool is here

Wow. I wonder if this means we might get Jellybean on our Gen9 devices?
/me crosses fingers.
Sent from my ARCHOS 101G9

Extreme_One said:
Wow. I wonder if this means we might get Jellybean on our Gen9 devices?
/me crosses fingers.
Sent from my ARCHOS 101G9
Click to expand...
Click to collapse
one day..perhaps

cajl said:
one day..perhaps
Click to expand...
Click to collapse
Personally, I hope it never happens. There is absolutely nothing about 4.1 or 4.2 (other than maybe a slight increase in touch screen operation) that I can see of any real need/use.
Heck, on the Archos G9's there are really only 3 things worth moving up from the Archos 3.2.80 to 4.0.7:
1) Google added and option in the stock Android browser to "request desktop page".
2) Archos made some improvements to their HDMI output.
3) Added Xbox 360 USB controller functionality.
If it were not for those 3 things I would happily stayed back with 3.2.80. It was already a mess before Archos ever got 4.0.7 anywhere near working right (and it still had Wi-Fi connection flaw that were not there in 3.2.80)... and now, they've made a total disastrous mess with the 4.0.2x firmware releases.
Just think about how horrible things would get if they tried to release 4.1 or 4.2? Not to mention, even Google now has to fix things in 4.2 to start with even for their own flagship Nexus products. Why do so many people want the NEXT thing before anyone even gets the current thing to work correctly?
Sorry, don't mean to be rude. It's just that I do not understand the concept of wanting the next new piece of garbage that comes out before they fix the crap they already have out there?

The G9 ist unresponsive / laggy especially with only 512 MB RAM. Jelly Bean is a step forward and I want it ASAP with a lot of butter

Part of me wants to see Jelly Bean running with "butter", but then again...my device is running incredibly smooth to begin with, so why mess that up.
decisions, decisions.....

I want Butter and Google Now
Sent from my ARCHOS 101G9

DeeDroid said:
The G9 ist unresponsive / laggy especially with only 512 MB RAM. Jelly Bean is a step forward and I want it ASAP with a lot of butter
Click to expand...
Click to collapse
If Archos release Jelly Bean for the G9 devices (and I have real doubts about that happening), I think you will be very disappointed with the performance on the old outdated hardware of the G9. But first, let's look at how the Google "hype' is very similar to the "hype" Microsoft used over the years...
They both "claim" each new OS is better and faster than the previous one. I know for a fact that is not true with Microsoft Windows. Just try to install Windows XP, Vista, or Windows 7 on an older computer that originally came with Windows 98... it does not run faster at all (actually slower) simply because each newer OS came out on newer, better, and faster hardware in the newer computers.
Android Honeycomb came out when tablets still had slow, single core CPU's with only 256 or (if you were lucky) 512MB of system RAM.
Android Ice Cream Sandwich came out on devices that had faster dual core CPU's with 1Gig of system RAM. Even though it can run on older devices with only 512MB of RAM it runs slower on those devices than Honeycomb did.
Jelly Bean first came out on the Nexus 7 which has a quad core CPU and a 12 core graphics processor. So, even if Archos could make the "butter" stuff work on a G9 (which I doubt they can)... there is simply no way it can ever run as smooth and fast as it does on the Nexus 7 simply because the G9 hardware is no where near the same level as newer devices have now.
And, some companies are already making devices with 2Gig RAM just to be able to stay ahead of any newer Android version requirements.
The Archos 101 XS has both a newer and better CPU and graphics processor. While the even newer Archos GamePad and 80 XS have an even faster (1.6Ghz) CPU and a quad core graphics processor and come with Jelly Bean installed from the factory. And even those are still no match to the performance of the Nexus 7.

[REQ] Firefox OS

I know this is my second but I thought it would be nice to see some variety.
This OS looks a lot like MIUI but has some different looking features and abilities. I think it would be worth looking into.
https://www.youtube.com/watch?v=g6oLUmc2iOQ&feature=youtube_gdata_player
Here is a downloadable simulator, if you know how to install it, to get an idea of the look and feel. Or you can simply install it in your version of Firefox web browser under "add-ons".
http://people.mozilla.org/~myk/r2d2b2g/
This is Mozilla's webpage talking about their idea on mobile OS. I think the articles actually kind of weak.
https://www.mozilla.org/en-US/firefoxos/
Hope you guys like this.
--------------------UPDATE-------------
Here's an article about the specs of the Firefox OS.
94
Mozilla reveals Firefox OS Developer Preview Phone
By Jamie Rigg posted Jan 22nd, 2013 at 6:33 AM
Mozilla said it won't be launching its own hardware to run the in-development Firefox OS when it's finished, but the company has just announced a "Developer Preview Phone" for putting the OS through its paces. It's not quite the same as the mystery device we saw sporting Firefox OS at CES, but its specs seem almost as basic. The handset will feature a 3.5-inch HVGA touchscreen and 3-megapixel camera on the outside, with a 1GHz Snapdragon S1 CPU, half a gig of RAM, 4GB of microSD-expandable storage and WiFi, 2G and 3G antennae inside. Sure, that processor isn't a beast, but an 800MHz S1 does just fine in the Lumia 610. A 1580mAh battery will keep the carrier-unlocked phone running, and Mozilla is promising OTA updates to Firefox OS to keep devs, well, up to date. At the moment, we have no idea how much the phone will cost, but the first units are expected to be available next month.
The developer handset is called the Keon, according to creator Geekphone's website, and while not mentioned in the Mozilla Hacks blog post, it appears to have a more powerful cousin called the Peak. It's got a 4.3-inch qHD screen, 8-megapixel back-facing camera (with flash) and 2-megapixel shooter round the front. A 1.2GHz dual-core Snapdragon S4 CPU and larger 1800mAh battery are within, but storage, RAM and connectivity specs are the same as the smaller Keon. Mozilla may not be formally promoting this as its own dev handset, but it was still included in the picture which accompanied the announcement (see above: the Keon is in orange, the Peak in white). We're getting in contact with Mozilla to clarify, and will update you when we hear back.

A mix of IOS and MIUI iiii liiiikkkee it
I'm trying to learn java I've made a basic plugin for bukkit ( a minecraft server thing lol don't judge me ) and if anyone can help me while I take on this task like guide me through some stuff like git hub and other stuff, I will take the challenge.
Buut if some doubt me and think they can do it....go ahead.
Sent from my EVO using xda premium