Develop Bugs

a100 and windows 8

will this be possible eventually when fully realeased ??

whaaaaa? windows 8 on the a100 or being able to use mtp/mass storage with windows 8? if its the first i want to say HA good luck with that be easier to compile ubuntu 12 arm compared to any windows os. If its the second well i have no clue.
Personally if i was gonna put windows 8 on a acer tablet i'd done it with the w500 which runs windows7 natively an has a keyboard dock (that will never mount right to a a100/a500 because its a normal usb port on the bottom of the w500 >.>)

terryok said:
will this be possible eventually when fully realeased ??
Click to expand...
Click to collapse
No, not possible. No one will be installing W8 on their Android tablets; guaranteed.

FloatingFatMan said:
No, not possible. No one will be installing W8 on their Android tablets; guaranteed.
Click to expand...
Click to collapse
If you are speaking the Acer A100 tablet ONLY I would say yep you are correct. However you are saying "No one will be installing W8 on their Android tablets" which is false. Yes you will be able to have an ARM device with Windows 8 and Android in a dual boot. Windows 8 is being writen for both x86 and ARM and manufacturers like Asus have already talked about releasing a dual boot.

NoSudo said:
If you are speaking the Acer A100 tablet ONLY I would say yep you are correct. However you are saying "No one will be installing W8 on their Android tablets" which is false. Yes you will be able to have an ARM device with Windows 8 and Android in a dual boot. Windows 8 is being writen for both x86 and ARM and manufacturers like Asus have already talked about releasing a dual boot.
Click to expand...
Click to collapse
Microsoft just aren't going to allow that... They have VERY strict requirements for the ARM version of Windows 8, one of which is a tightly locked and sealed bootloader and NO dual booting capability.
Plus, no existing tablets on the market meet the spec requirements for resolution or available RAM.

FloatingFatMan said:
Microsoft just aren't going to allow that... They have VERY strict requirements for the ARM version of Windows 8, one of which is a tightly locked and sealed bootloader and NO dual booting capability.
Plus, no existing tablets on the market meet the spec requirements for resolution or available RAM.
Click to expand...
Click to collapse
Thanks, and my previous point still stands true. You are too vague most of the time in your responses and it leads to miss informed people. It also causes you to give responses that may have some validity, but are wrong because you don't properly address what you wish to point out.

I agree with you there is actually news about ARM based tablets having to have a secured boot loader by the manufacture no if ans or butts if its a intel/amd based machine the secure boot is optional.
Hope nobody minds but here is a link on some info on that http://www.bit-tech.net/news/bits/2012/01/16/microsoft-blocks-linux-arm-hardware/1

Hi,
Still no solution to install W8 on A100?
Tnks

I wont say it'll never happen, I'll say its extremely unlikely, for a few reasons i can see.
Devs needed to work on getting w8 working on a tegra2 anything, let alone an a100
W8 itself being modified to run on the a100 specifically, there is next to no dev support for this device for android let alone another os.
Did I mention devs needed to do this stuff?
IMO i wouldn't wait on this, its extremely unrealistic to expect. But I could be wrong, it happens quite often.
Sent from my Galaxy Nexus using Tapatalk 2

Ruben13 said:
Hi,
Still no solution to install W8 on A100?
Tnks
Click to expand...
Click to collapse
The Surface is held back even by Tegra 3, so I don't think its possible. And this tablet just doesn't have enough dev support.
Sent from my A100 using xda app-developers app

[Q] What would be involved in porting Windows Phone 8 to the Lumia 900?

Ignoring the secured bootloader in the Lumia 900 for a while, what would be the major barriers to getting Windows Phone 8 running on the Lumia 900? If the bootloader could be unlocked (and the registry somehow modified to support a single-core chip), would it just be a matter of flashing the Windows Phone 8 emulator hard drive onto the Lumia 900, or is it a lot more complicated than that?
Sorry if I'm overlooking something huge, I'm not very experienced in these matters

Honestly until it drops we won't know but IF we got an unlocked booloader I doubt it would take long or a ROM to surface. Unfortunately we will probably never get ROMs on the 900

Laquox said:
Honestly until it drops we won't know but IF we got an unlocked booloader I doubt it would take long or a ROM to surface. Unfortunately we will probably never get ROMs on the 900
Click to expand...
Click to collapse
Is it impossible to unlock the bootloader in a Lumia 900, or just not feasible? For instance, if you could open up the Lumia and replace the Nokia-locked Snapdragon chip with a stock Snapdragon chip, would it work?
Also, one thing that I don't understand (but I'm pretty sure I'm overlooking something huge here), why can't we just take the ROM from the Lumia 920/820 and flash it onto the 900 with this tutorial? Shouldn't the 920/820 ROMs already be signed by Nokia?

Well, the APQ8055 and MSM8960 are both ARMv7. So that's good. (Not like one is ARMv6.) The problem is that the Nokia bootloader is pretty secure, and I'm sure there'd have to be something like magldr created since I'm sure the boot process is different for WP8.
As far as flashing a 920 rom on a 900. No, not at the moment anyway. The signing is unique to each product code. For example, a Rogers rom can't be flashed on an at&t 900 since the product code is different and the signing is different.

exiva said:
Well, the APQ8055 and MSM8960 are both ARMv7. So that's good. (Not like one is ARMv6.) The problem is that the Nokia bootloader is pretty secure, and I'm sure there'd have to be something like magldr created since I'm sure the boot process is different for WP8.
Click to expand...
Click to collapse
sorry, I'm not very experienced with this kind of thing, but if we replaced the part of the phone that contained the secured bootloader (I'm assuming it's the Snapdragon chip, but correct me if I'm wrong) with a stock version of it that would enable any ROM to run, shouldn't that fix the problems people have been having with the bootloader?
Or are you trying to say that even if we could do that a custom bootloader would have to be made to boot WP8?
exiva said:
As far as flashing a 920 rom on a 900. No, not at the moment anyway. The signing is unique to each product code. For example, a Rogers rom can't be flashed on an at&t 900 since the product code is different and the signing is different.
Click to expand...
Click to collapse
Any chance flashing an AT&T 920 ROM onto an AT&T 900 would work? or would the product code mess it up?

[Q] Texas Instrument [TI], GNex & Kitkat

Guys I am non US, GNex Lover, So I want to know is is exact connecttion between TI with GNex Kitkat update?
Anyone?
FYI
There's still no official word on why this is the case, but sources close to the company have pointed the finger at a different hardware issue on the Galaxy Nexus: its Texas Instruments-built chipset. The company is out of the mobile business and as such isn't in a great position to give the support necessary for continuing OS upgrades -- presumably some of those 1,700 employees let go in the shift away from mobile could have helped. Now we'll have to see if the community can pick up where the corporations left off or if this is the end of the road for the Gnex and its other OMAP-based kin like last year's Kindle Fire HD, Nook HD and Droid Bionic.
Click to expand...
Click to collapse
http://www.engadget.com/2013/10/31/google-galaxy-nexus-kitkat/

hirenvasani said:
Guys I am non US, GNex Lover, So I want to know is is exact connecttion between TI with GNex Kitkat update?
Anyone?
FYI
http://www.engadget.com/2013/10/31/google-galaxy-nexus-kitkat/
Click to expand...
Click to collapse
Texas Instruments makes the CPU in the Gnex they no longer make mobile chips for phones and thus 4.4 driver updates are an issue.

cstrife999 said:
Texas Instruments makes the CPU in the Gnex they no longer make mobile chips for phones and thus 4.4 driver updates are an issue.
Click to expand...
Click to collapse
why cant google develop it?
and there may be few good community member who can develop, so what is the problem? Why google doing like this?
Any hope?

hirenvasani said:
why cant google develop it?
and there may be few good community member who can develop, so what is the problem? Why google doing like this?
Any hope?
Click to expand...
Click to collapse
Google doesn't make ti parts and probably has no clue how to. I'm sure devs here will get it done eventually.
Sent from my Galaxy Nexus using xda app-developers app

TI OMAP 4460 is closed-source, there's no documentation about that chip, makes the job really hard.

Money makes the world move, not economical to continue development on a 2 year old device for Google.
Beamed from my Maguro

Loureiro said:
TI OMAP 4460 is closed-source, there's no documentation about that chip, makes the job really hard.
Click to expand...
Click to collapse
With respect, that couldn't be further from the truth -- TI makes a ~6,000 page public Technical Reference Manual documenting the workings of most of the chip, and the kernel and publicly-available Android hardware enablement sources are in excellent shape. That's a lot more than can be said for any other SOC manufacturer.
That said, the difficulties encountered so far in running 4.4 on Galaxy Nexus can be traced back to the closed-source PowerVR GPU drivers -- and because TI's winding down its OMAP division and GPU maker Imagination Technology has moved on to its next-generation Series 6 designs, we're unlikely to get new ones. I suspect Google had the same problem getting new GPU drivers, and elected not to carry forward compatibility code in the base Android system to support the old ones.

Google doesn't seem to want to acknowledge it, but it seems like drivers are becoming the driving force behind stalled updates. It's gotten so bad it's affecting Google's own devices. This should not have been a surprise since anyone involved in Linux knows closed source drivers are always causing problems.
Their dropping support after "18 months" sets a dangerous president since the device was still their "new" phone less than a year ago. Heck Verizon was still selling it until very recently, and we still don't have 4.3.
It's actually discouraging me from getting the nexus 5.
Sent from my Galaxy Nexus using Tapatalk

T-Keith said:
Google doesn't seem to want to acknowledge it, but it seems like drivers are becoming the driving force behind stalled updates. It's gotten so bad it's affecting Google's own devices. This should not have been a surprise since anyone involved in Linux knows closed source drivers are always causing problems.
Their dropping support after "18 months" sets a dangerous president since the device was still their "new" phone less than a year ago. Heck Verizon was still selling it until very recently, and we still don't have 4.3.
It's actually discouraging me from getting the nexus 5.
Click to expand...
Click to collapse
That's a noble sentiment, but reality says that there isn't a single ARM SOC on the market right now that's not afflicted with closed-source driver blobs -- meaning there's quite literally nothing you can buy, or even design and build yourself, that would be an improvement on that front. (Down the road, there may be hope for Intel parts with documentation and fully open drivers, but even that's not a guarantee.)

steven676 said:
With respect, that couldn't be further from the truth -- TI makes a ~6,000 page public Technical Reference Manual documenting the workings of most of the chip, and the kernel and publicly-available Android hardware enablement sources are in excellent shape. That's a lot more than can be said for any other SOC manufacturer.
That said, the difficulties encountered so far in running 4.4 on Galaxy Nexus can be traced back to the closed-source PowerVR GPU drivers -- and because TI's winding down its OMAP division and GPU maker Imagination Technology has moved on to its next-generation Series 6 designs, we're unlikely to get new ones. I suspect Google had the same problem getting new GPU drivers, and elected not to carry forward compatibility code in the base Android system to support the old ones.
Click to expand...
Click to collapse
If there is no drivers, how custom rom is available, I saw 3 rom, out of one, one is exact copy of actual 4.4 but only for verizon.
If developers cam develop rom just day or 2? why Google Cant? And 18 months support policy is just bull****.

hirenvasani said:
If there is no drivers, how custom rom is available, I saw 3 rom, out of one, one is exact copy of actual 4.4 but only for verizon.
If developers cam develop rom just day or 2? why Google Cant? And 18 months support policy is just bull****.
Click to expand...
Click to collapse
You can develop a rom without the proper drivers however there'll be problems. Devs are trying to find a workaround for the GPU drivers but so far, no luck. Aside from that, looks like google tried to work on the GPU drivers but they gave up. Maybe there's nothing to do with the 18 months policy.

Google doesn't want to put money, people and rest of resources into 2 year old device. It never did and it never will. That's the only real reason. The TI **** was posted and reblogged so many times that it became ''truth''. What Google posted in their FAQ about being ''too old'' simply means it falls out of their device update timeline.
End of story.

https://www.youtube.com/watch?v=Gld4RcF0MKc

Sesme said:
https://www.youtube.com/watch?v=Gld4RcF0MKc
Click to expand...
Click to collapse
Rom's actually faster & eventually needs updates though, thanks for the video :good: !

Castro27 said:
You can develop a rom without the proper drivers however there'll be problems. Devs are trying to find a workaround for the GPU drivers but so far, no luck. Aside from that, looks like google tried to work on the GPU drivers but they gave up. Maybe there's nothing to do with the 18 months policy.
Click to expand...
Click to collapse
Well, i would not be so negative about that ! As I said on the other post, I've tried the two 4.4 roms in the Development forum. There is still some graphic glitches, but i'm with "A taste of KitKat" since yesterday, had only 1 random reboot at the beginning, deep sleep is amazing, etc. And it's like 48h since the Nexus5 is on sale !
I think since developper made something very usable after 48h, I believe they can workaround those GPU problems. I mean even if google backed down, you can't know who was working on the GPU back there ... it could have been an intern ! Here I know there is 2 guys that each made a 4.4 ROM usable in 48h that are working on it, so I believe

ericmas001 said:
Well, i would not be so negative about that ! As I said on the other post, I've tried the two 4.4 roms in the Development forum. There is still some graphic glitches, but i'm with "A taste of KitKat" since yesterday, had only 1 random reboot at the beginning, deep sleep is amazing, etc. And it's like 48h since the Nexus5 is on sale !
I think since developper made something very usable after 48h, I believe they can workaround those GPU problems. I mean even if google backed down, you can't know who was working on the GPU back there ... it could have been an intern ! Here I know there is 2 guys that each made a 4.4 ROM usable in 48h that are working on it, so I believe
Click to expand...
Click to collapse
What you don't understand is that it is very difficult to make a build without the software to match the hardware. This same issue happened with my motorola Photon 4G. We were promised ICS on our phones, however motorola took back that promise and we were left in the dust. Enter the wonderful devs in that community. They quickly pounced on the ICS builds and developed one for our devices, but there was an issue... the drivers were outdated and the kernel would not play nice with the old drivers. It was tegra 2, and NVIDIA had stopped supporting that chipset, so what did we get? A build of ICS using the old GB kernel, with constant display and performance issues. That is what will happen with this device.

hirenvasani said:
If there is no drivers, how custom rom is available, I saw 3 rom, out of one, one is exact copy of actual 4.4 but only for verizon.
If developers cam develop rom just day or 2? why Google Cant? And 18 months support policy is just bull****.
Click to expand...
Click to collapse
ericmas001 said:
Well, i would not be so negative about that ! As I said on the other post, I've tried the two 4.4 roms in the Development forum. There is still some graphic glitches, but i'm with "A taste of KitKat" since yesterday, had only 1 random reboot at the beginning, deep sleep is amazing, etc. And it's like 48h since the Nexus5 is on sale !
I think since developper made something very usable after 48h, I believe they can workaround those GPU problems. I mean even if google backed down, you can't know who was working on the GPU back there ... it could have been an intern ! Here I know there is 2 guys that each made a 4.4 ROM usable in 48h that are working on it, so I believe
Click to expand...
Click to collapse
One way to describe this for the simple/non-dev users is the current 4.4 builds you are trying a "new package, with old contents". Or you got a new car but it still has the old engine.
Until the OMAP issues are resolved we are sitting around twiddling thumbs. Which it seems google did when it had no luck in accomplishing and therefore decided to default on their non-fragmentation theology - it's easier to EOL or end support for the device.
I just wish that google would have told us earlier about this rather than wait until release. A simple PR statement months ago when KK/KLP was in development "We have issues getting Gnex/TI OMAP compatibility" would have saved itself from the onslaught of complaints it is getting now.

Why google did not make Android 4.4 backward driver compatible as an option?

TI don't develop new kernel

This situation pushed me to unlock my phone and install custom ROMs. Now I know that i should done it earlier. No drivers for OMAP it's not a problem to developers and CM11 is running very smoothly. No update it's in my opinion only $$ issue.

Flash WP8.1 to Android variants

When the google play edition came out, we got the dump, and worked to making a flashable rom. Now with a Windows Phone variant running on the M8, wouldn't it be relatively easy to port it? I tend to switch between Android and WP phones. Having a phone that could have either would make me want to purchase the phone because I wouldn't have to switch between two phones constantly.
Is hboot on HTC windows phones? Is there a way to dump the system and port it? Make a rom possibly? Maybe possibly RUUs to switch between the OSs factory installs?

bump

The phones have different hardware so don't count to much on it...

From what I have read, the only change will be the OS
"As for specifications, the Windows-based (M8) will run on Windows Phone 8.1 Update 1, but should otherwise be identical to the Android model, from the Boomsound speakers to the 5-inch Full HD display. No word yet on whether or not the device will come to any carriers other than Verizon, but there hasn’t been any indication from any other carriers up to this point."
So I wouldn't go as far as it's not possible. There is always hope.. In the General folder there is a dev working on a Dual Boot M8. Hoping to see the WP8 on one of the boot....

Mr Hofs said:
The phones have different hardware so don't count to much on it...
Click to expand...
Click to collapse
The hardware is identical according to leaks, they just swapped out Android for Windows Phone.
@Oditius, thanks I found it, its called MultiROM.

I currently switch between my M8 and my Lumia 1020. I love the sleekness of Windows Phone and the big screen and awesome speakers of my One. Would be nice to see this happen a-la HD2

Wonder why this thread hasn't been closed by the Android police?

So you care to trust leaks but don't read xda ?
http://forum.xda-developers.com/showthread.php?t=2847466

Mr Hofs said:
So you care to trust leaks but don't read xda ?
http://forum.xda-developers.com/showthread.php?t=2847466
Click to expand...
Click to collapse
So you trust the word of one mod over hundreds of leaks? I am in the WP world as well as android. Ghost may be right, but then again there are too many very trustworthy leaks.
Sent from my AT&T HTC One M8, running the ViperOne M8 ROM via Tapatalk.

Why would i not......Why should i trust leaks even if it would be thousands and spreaded of the word of one man.....same as believing one mod !
I'm not going into discussion about this any further. All WP vs Android M8 are closed down.....this should be the next i guess

But this isn't about WP vs android. I like both OS's. This is about putting WP on an android device to have the best of both worlds
Sent from my AT&T HTC One M8, running the ViperOne M8 ROM via Tapatalk.

BTW WP is coming to the HTC One M8
http://www.wpcentral.com/htc-one-windows-has-cortana-integration-dot-view-case

WINDOWS MOBILE 10 on a Nexus 5X!

GUYS CHECK THIS!
WTF -- https://www.youtube.com/watch?v=FEgvXCsMu1c

Good

How?

fake
Sent from my Q10 using XDA-Developers mobile app

Cool ?

dugu1248 said:
fake
Sent from my Q10 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's 100% real bro. Trust me. Its clever hacking.

I really wish that this is real!

Impossible
Sent from my Q10 using XDA-Developers mobile app

I don't know why it can't be possible?
The Nexus X5 Qualcomm MSM8992 Soc is supported by Windows Mobile 10... and the drivers are part of the Nokia Lumia 950 FFU which can be downloaded on www.lumiafirmware.com. (Maybe this guy even has access to the Windows Mobile BSP pack for this SoC).
FFU file (signed or not) can be flashed on any phone to eMMC using the Qualcomm Firehose protocol.
Nexus X5 supports Secure Boot also.

TristanLeBoss said:
I don't know why it can't be possible?
The Nexus X5 Qualcomm MSM8992 Soc is supported by Windows Mobile 10... and the drivers are part of the Nokia Lumia 950 FFU which can be downloaded on www.lumiafirmware.com. (Maybe this guy even has access to the Windows Mobile BSP pack for this SoC).
FFU file (signed or not) can be flashed on any phone to eMMC using the Qualcomm Firehose protocol.
Nexus X5 supports Secure Boot also.
Click to expand...
Click to collapse
Thank you so much for providing a logic to the nonsensical "fake-fake" battering. Just because people cant comprehend means it is not real. SHeesh..

TristanLeBoss said:
I don't know why it can't be possible?
The Nexus X5 Qualcomm MSM8992 Soc is supported by Windows Mobile 10... and the drivers are part of the Nokia Lumia 950 FFU which can be downloaded on www.lumiafirmware.com. (Maybe this guy even has access to the Windows Mobile BSP pack for this SoC).
FFU file (signed or not) can be flashed on any phone to eMMC using the Qualcomm Firehose protocol.
Nexus X5 supports Secure Boot also.
Click to expand...
Click to collapse
Yes, you are right

X0LARIUM said:
Thank you so much for providing a logic to the nonsensical "fake-fake" battering. Just because people cant comprehend means it is not real. SHeesh..
Click to expand...
Click to collapse
Yep, when people don't quickly find how it's done, they say it's fake; especially when they are aware of some (current) barriers that would prevent it from happening. Most of the time, they forget that other people can know/have things they don't have/know. They also forget that we move on by finding a way to jump over barriers.
But, also, unfortunately, people prefer to think it's fake to protect themselves from the frustration they will build because they would like to know how to do it and, unfortunately, most of the time, never will. On a forum, so many people come and say "yes, it possible: look", you are then excited to find out or try but, finally, the guy vanishes without giving any information on how to do it...

I think its fake

Something wrong with that video...
Hey guys, take a closer look on the video this was showcased..... First, the phone itself doesn't even have a Nexus branding on the back, and second, why is it running 10568??? That's strange....
Sent from Ponyville

X0LARIUM said:
Thank you so much for providing a logic to the nonsensical "fake-fake" battering. Just because people cant comprehend means it is not real. SHeesh..
Click to expand...
Click to collapse
That Video is fake as there is no TH build 10568.00 released

wouldnt say that, maybe based on an early version of the rom for the mi4

TristanLeBoss said:
Yep, when people don't quickly find how it's done, they say it's fake; especially when they are aware of some (current) barriers that would prevent it from happening. Most of the time, they forget that other people can know/have things they don't have/know. They also forget that we move on by finding a way to jump over barriers.
But, also, unfortunately, people prefer to think it's fake to protect themselves from the frustration they will build because they would like to know how to do it and, unfortunately, most of the time, never will. On a forum, so many people come and say "yes, it possible: look", you are then excited to find out or try but, finally, the guy vanishes without giving any information on how to do it...
Click to expand...
Click to collapse
So who's game to try this with a 6p? Same soc as the 950xl...

nate0 said:
So who's game to try this with a 6p? Same soc as the 950xl...
Click to expand...
Click to collapse
Any news on putting W10M on the N6P? I want to try this but not sure what firmware I should install. Any idea on what the product code is for the 950XL on AT&T in the USA?

TristanLeBoss said:
Yep, when people don't quickly find how it's done, they say it's fake; especially when they are aware of some (current) barriers that would prevent it from happening. Most of the time, they forget that other people can know/have things they don't have/know. They also forget that we move on by finding a way to jump over barriers.
But, also, unfortunately, people prefer to think it's fake to protect themselves from the frustration they will build because they would like to know how to do it and, unfortunately, most of the time, never will. On a forum, so many people come and say "yes, it possible: look", you are then excited to find out or try but, finally, the guy vanishes without giving any information on how to do it...
Click to expand...
Click to collapse
nate0 said:
So who's game to try this with a 6p? Same soc as the 950xl...
Click to expand...
Click to collapse
yes its easy game for Nexus 6p if you found any windows 10 device that had same camera place that 6p had.
this video is pure fake by placing 950 single sim display panel cover with nexus 5x body covers,unfortunately it had same camera & flash light points of lumia 950.
even there are more evidence in video that itself says its fake :laugh::laugh::laugh::laugh:

raghulive said:
yes its easy game for Nexus 6p if you found any windows 10 device that had same camera place that 6p had.
this video is pure fake by placing 950 single sim display panel cover with nexus 5x body covers,unfortunately it had same camera & flash light points of lumia 950.
even there are more evidence in video that itself says its fake :laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
It is easy to say it is fake, if you are willing to limit what you want to believe or what you can do. Even if it is the point is to think outside of the box, and thanks for showing your side of the story.
I can't speak for everyone, but as far as I know nobody has proved a W10M port is not possible.