![]() |
Re: NOKIA Rejected Android in Favor of M$ - Eric Schmidt
Quote:
|
Re: NOKIA Rejected Android in Favor of M$ - Eric Schmidt
Quote:
Mind you, I'm not saying it's something inherently bad (after all, changing the UI layer is what we wanted to happen with Symbian), but it's not the super-duper new OS with active mass balance controllinators, mega particle anti Apple cannons and Android de-polaryzers (Ultimate Edition) that MS marketing will want us to believe. |
Re: NOKIA Rejected Android in Favor of M$ - Eric Schmidt
Quote:
I guess it boils down to picking the lesser evil. Or host your own data. As Rop Gonggrijp (subpoenaed by US DoD in Wikileaks fishing exp. put it): "For all these people that were asking: this kind of thing is why people run their own mail servers. Get it now?" |
Re: NOKIA Rejected Android in Favor of M$ - Eric Schmidt
Quote:
|
Re: NOKIA Rejected Android in Favor of M$ - Eric Schmidt
Quote:
If Android was untrusted then there would be elements in the source code that would clearly show this. There is not, in fact its in the apps that 3rd parties make which do this. I am very very concerned at moment regarding these 3rd party apps, M$ Office suit, M$ File Commander to name a couple and i wont even get started on the FailBook app. Manufacturers are building these apps in rather than leaving them in the App zone, this is not Google doing this, it is HTC, Samsung and so on. One should be more worried about the manufacturer rather than a fully open source Apache licensed software called Android. I have studied the code, looked through it nearly with a tooth comb direct from google code and nothing of what you speak of exists in that code. It does exist on the other hand within the 3rd party apps, that is why it concerns me. You cant put the blame on google for that. To build them in so that the user can NOT unisnstall them is a clear problem originating from the OEM's Manufacturer. Fortunately Sony and HTC (to a degree) have unlocked the bootloader as standard to allow the user to remove everything and install a fresh self compiled version of google Android. That does mean the user must git the code configure it and compile it then install it. M$ do not and will never allow you to do this so you say you dont trust google? They clearly open up and have a fully transparent firmware. What kind of trust are you talking about exactly? |
Re: NOKIA Rejected Android in Favor of M$ - Eric Schmidt
Quote:
It was sorted in kernel 2.6.X, if you have ever built your own kernel then you will know some things were in 2.4.X built in so you could not remove them but not any more. The 2.6.X kernels allow you to do what you want with them or whatever suits your needs. No more bloated kernels, fully customized and highly efficiont kernel. The Android runs on a very new kernel version that is NOT bloated in a bad way. The kernel has got drivers compiled in it that depending on certain devies wont be using. The google Android Code usus a genkern (generic kernel) that is precompiled for ease of use. That dont stop you git code the kernel source and building a debloated specific kernel for your particular device. What i like about android is you can pull the normal source from kernel.org and use the rawr code as a kernel, it will make life a little harder but its very possible. Graphic drivers and some others remain closed binaries so they have to be added into the binary folder before you compile the kernel to be included. These 3rd party drivers are a block hole. Black hole software in the free software community are considered dangerous. Not much we can do about that at moment. At least Sony is trying to open source these. Sony seems to be on our side at least, i would like to say same for Nokia but clearly Nokia has turned to the dark side... |
All times are GMT. The time now is 16:28. |
vBulletin® Version 3.8.8