Related
I think being a Open Source Code and Openness in Architecture, API Google Should Ship Different Firmware for Developers, Software Builders, Codec Programmer etc.
Better for Google / T-Mobile / HTC
They can restrict Developer Device to get Back Normal Shipped Firmware.
Developer Device Activation Method can be Introduced so Once you Activate that IMEI for Developer Edition you could get only Limited Warranty from HTC for that IMEI.
Once you load Different Firmware, company may not allow you to Flash Normal Shipped / OTA Firmware signed by Different Signature.
Developer Edition of Firmware can have Test Key or Developer Key based Recovery Partition. But can not Erased the way we did it before.
Developer firmware must be only available via SDCard Method
No OTA should be given except for some killbits Urgency.
Their should be Disclaimer and Agreement for Warranty Issue
Better for Developers
Rather then Fighting for root this could be Straight Access to Device
No More Hacking and Exploits needed.
Building Firmware, API, Services, Codes which need Root Access can be Tested with Device rather then Emulator.
Customizing OS and using it for Self and Distributing it to user who can take risk may get easy Access to Mods.
Google Should Protect Recovery Image and Boot Image from being Flashed this will reduce Bricking Issue.
Please report your Comments here
http://code.google.com/p/android/issues/detail?id=1266&can=4
This won't happen. They will plainly tell you to build your own version and thats logical too. G1's version of Android is T-Mobile's, they paid for it, so it has everything that T-Mobile wants, and its for the average user who doesnt care about root etc. If you want a developer version, you can always compile it with default root access n stuff, thats the beauty of Open source.
Building Customized Firmware that's what i am saying unless you don't have root access you can not Build and Flash Customized Image. and in RC30 Release they have removed root access and telnetd.
Means they have stopped all door for Customizing firmware and flash it.
hetaldp said:
Means they have stopped all door for Customizing firmware and flash it.
Click to expand...
Click to collapse
I would not say that the stopped or closed all doors for customizing. Yes they took aways root but it does not mean we wont find a new door. With hacking any device its all about finding the newer better way to get in.
If you look at the amount of time that has been spent on Android since it was originally announced the development time is incredibly short. For that reason I could see Google wanting to restrict root access until they are more certain of the potential complications of allowing access to the various parts. Perhaps we'll see a gradual releas of root access as the error handling capability of Android is improved.
Or that could just be wishful thinking. At this point I'm wishing that I hadn't taken the official RC30, but too late now
Rather then sitting idle and wishing for Google to rethink and give us root access gradually is not enough we should sign the link above and suggest them for that requirement.
benmyers2941 said:
If you look at the amount of time that has been spent on Android since it was originally announced the development time is incredibly short. For that reason I could see Google wanting to restrict root access until they are more certain of the potential complications of allowing access to the various parts. Perhaps we'll see a gradual releas of root access as the error handling capability of Android is improved.
Or that could just be wishful thinking. At this point I'm wishing that I hadn't taken the official RC30, but too late now
Click to expand...
Click to collapse
Android was under development for 5 or 6 years before they announced it. It wasn't as rushed as you make it sound.
RyeBrye said:
Android was under development for 5 or 6 years before they announced it. It wasn't as rushed as you make it sound.
Click to expand...
Click to collapse
Five or six years seems terribly long. I know they did a lot of work on the dalvik VM but still.. I wouldn't be surprised if they had lost of lot of time in legalese and negotiation with hw maker and providers. I work in telco, although not the mobile industry and you can barely imagine the bully tactic employed by the big names to keep challengers out.. Ya don't wanna lose yar winmo 6 preferred pricing ar righ'?
Anyway, if it's true I'm even more surprised at some of the current shortcoming of the platform. Internationalization and lack of support for bluetooth comes to mind first.
But anyway, it's a young platform in terms of "days in the wild" and it's already quite good. What I'm a little bit afraid of is that T-Mo might not keep the update coming to bring new features to the phone in order to get people to upgrade their handset. We'll see.
As for developer build, Google has said that they would release Android so you could build your own device not that every device would be open.
I believe your demand should have been addressed to T-Mobile, not to Google nor HTC. Having an open device would be a tremendous benefit for Google as it would attract more qualified hobbyist developers to the Android platform. HTC probably doesn't really care either way, they're in the business of selling hardware, once you bought it they won't see any of the additional revenue stream, so if they can move ten thousand more unit because some people would like to use them as development device, I'm pretty sure they'd be for it. Assuming they don't have to support the cost of technical support for those "customized" devices.
RyeBrye said:
Android was under development for 5 or 6 years before they announced it. It wasn't as rushed as you make it sound.
Click to expand...
Click to collapse
Where did you get your information? I doubt that the entire OS was under development for 5 or 6 years. Maybe they started the idea of making a mobile OS but I don't think they actually have been coding it. I think it has been more product development not software. Things like (capacitive or resistive) or (mini USB or proprietary) and of course (on screen or hardware keyboard... or both)
Think about it they have to have a device in mind or a general lay out of the device before making the OS for it.
neoobs said:
Where did you get your information? I doubt that the entire OS was under development for 5 or 6 years. Maybe they started the idea of making a mobile OS but I don't think they actually have been coding it. I think it has been more product development not software. Things like (capacitive or resistive) or (mini USB or proprietary) and of course (on screen or hardware keyboard... or both)
Think about it they have to have a device in mind or a general lay out of the device before making the OS for it.
Click to expand...
Click to collapse
Hehe... That is most peoples understanding aswell.
Android is NOT Google's property (at least that I know of). Android has been in development for 5-6 years WITHOUT Google.
Android did not get the time of day UNTILL Google joined.
Then it wasn't being developed... it was staleware that google dusted off... I understand it isn't google's software but honestly you can't build something without knowing what devices it will be on. If built 6 years ago... it would have been built for devices from 6 years ago using resistive screens, proprietary connections, and most likely an onscreen keyboard. Mobile devices have changed a lot in 5 years and that would mean android was rebuilt from the ground up, if it was made 5 years ago. I think there may have been development and ideas 5 years ago but nothing even close to a working model(alpha software)
Being based on Linux, it is already extremely flexible with regards to hardware requirements. The only real requirement I am aware of is an ARM processor > 200 mhz...
Google bought Android in August of 2005, at that point in time, the company had existed for 22 months. So definitely some design elements of the OS have existed that long.
Yea but you have to write new code for each piece of hardware to interface with the OS... and things like resistive and capacitive screens are the big ones because of how the UI will be... Think about how WM6 would be if you had to use the center of your finger instead of a stylus? The UI for WM7 (whatever it will be called) has to change because it is supposed to be used on capacitive devices. Same goes with other things like how it will interface with USB and the keyboard(easiest) But each thing needs to interface into the OS and each of those are what takes time and all of those look rushed. I am also guessing that Google spent time recoding the email app and calendar and contact apps to interface with their servers as well. So what is left from android before google started? Does anyone have any proof or should I just say citation is needed?
neoobs said:
Yea but you have to write new code for each piece of hardware to interface with the OS... and things like resistive and capacitive screens are the big ones because of how the UI will be... Think about how WM6 would be if you had to use the center of your finger instead of a stylus? The UI for WM7 (whatever it will be called) has to change because it is supposed to be used on capacitive devices. Same goes with other things like how it will interface with USB and the keyboard(easiest) But each thing needs to interface into the OS and each of those are what takes time and all of those look rushed. I am also guessing that Google spent time recoding the email app and calendar and contact apps to interface with their servers as well. So what is left from android before google started? Does anyone have any proof or should I just say citation is needed?
Click to expand...
Click to collapse
That is what I am saying. Android is specifically designed to abstract all of those things. Want to add a new method for input? Fine, make a kernel module for it... Want to add a new interface port? Fine, make a kernel module for it. The modules are provided by either the device manufacturer (depending on how they've licensed the particular technology) or by the chipset manufacturer... This is no different than how the same distribution of Linux can run on x86, ARM, PPC, & Itanium with hundreds of different chipsets, network cards, etc.
From the very beginning Google has been saying that Android will run on a wide variety of phone hardware, even going so far as saying it could run on flip phones.
Yes but google had to create all of those for the G1 and it didn't have 5-6 years to do it.
Although I doubt it would work well on resisitive screens would be weird as its interface is meant for capacitive.
neoobs said:
Yes but google had to create all of those for the G1 and it didn't have 5-6 years to do it.
Although I doubt it would work well on resisitive screens would be weird as its interface is meant for capacitive.
Click to expand...
Click to collapse
Yes and that is why Linux kernels are sweet.
The kernel is set, done, finished (of course with room for upgrades).
All you need to do is create kernel modules ("drivers" for the rest of us, [I use Windows & Fedora]) for hardware to comunicate with the kernel.
The kernel has been there for a while, being developed by people who wanted an open phone OS. You can develope an OS regardless of what hardware is out there right now.
If you want to think of it in Windows terms, it's exactly the same. XP was writen years ago and that Kernel is still the same, but all you need is drivers for new hardware to comunicate with the windows kernel.
Actually now that I think about it, I beleave the XP kernel is still based on the 2K kernel. I'll look it up.
Google made Dalvik, and a couple of the applications, the members of the Open Handset Alliance provided the kernel level modules.
I found an article from earlier this summer that briefly goes over the timeline and what Google had in mind with this whole thing: http://www.wired.com/techbiz/media/magazine/16-07/ff_android?currentPage=all
quedijo said:
Yes and that is why Linux kernels are sweet.
The kernel is set, done, finished (of course with room for upgrades).
All you need to do is create kernel modules ("drivers" for the rest of us, [I use Windows & Fedora]) for hardware to comunicate with the kernel.
The kernel has been there for a while, being developed by people who wanted an open phone OS. You can develope an OS regardless of what hardware is out there right now.
If you want to think of it in Windows terms, it's exactly the same. XP was writen years ago and that Kernel is still the same, but all you need is drivers for new hardware to comunicate with the windows kernel.
Actually now that I think about it, I beleave the XP kernel is still based on the 2K kernel. I'll look it up.
Click to expand...
Click to collapse
XP was built on the NT kernel along with Vista and everything else made since 2000. Although that kernel is not the same at all anymore... sure it has all the same features but has been tweaked to all heck.
One thing I don't understand is where is the developer version or at least updated emulator package?
neoobs said:
One thing I don't understand is where is the developer version or at least updated emulator package?
Click to expand...
Click to collapse
http://source.android.com/
The emulator doesn't have to be updated. It's just QEMU with a fancy GUI. Assuming they're keeping the repo over there up to date, you should be able to check out the latest version, build the images, fire it up in the emulator, and be on your way... and if you have a rooted G1, as long as you include the proprietary stuff from HTC (kernel modules that I'm sure they can't GPL), you should be able to boot it up... which, unless I am mistaken, is exactly what JesusFreke did in the first place.
Everybody Please make Comment on this Issue with Official G1 Suggestion Thread i opened
http://code.google.com/p/android/issues/detail?id=1266&can=4
Hetal
I have never owned a cell phone before (yeah, I'm one of the last three who never has), and now am wanting to buy one. My preference is Android. I have some questions about this whole space:
* I don't want a contract. Is it generally true that I can buy any unlocked phone, and a prepaid SIM from Amazon or somewhere, and use them together?
* I'm old (early 60's) and have some generational cultural differences from many (but not all) of you that grew up with and accept social networking. Specifically, I have a zero tolerance policy towards my phone leaking ANY data, under any situation, and a zero tolerance policy for any outside control of the device. That is to say, I will not accept remote updates of software, nor any software which "phones home". I will only accept a phone that is 100% under my control. This seems to create complications, even under Android. If I run a custom firmware such as CM7, is this a goal that I can reasonably achieve? Perhaps with a local firewall on the device?
* I want to use the GPS for wilderness hiking, specifically, to retrace my (approximate) path in the unlikely event I become lost. Is the onboard GPS on phones adequate for such a purpose? I don't need meter-accuracy, but 10 or 15m accuracy would be nice, along with software that would sample my position every (say) 60 seconds and overlay this on a map that MUST be stored locally on the device. I will be out of cell tower range.
* These devices can carry a lot of data, but this seems dangerous on a device that may be lost or stolen. I know there can be a numeric code to unlock the device, but that provides no real security in practice. Is it possible for me to use encryption at the block level with a filesystem on an SD card? Conceptually, I want to mount that card through an encrypted loopback device, with a timeout that will unmount it after a period of inactivity. Possible?
* Specific phones: I liked the LG2X, but it seems many people have big problems with it. I liked the Sensation, but it has a locked bootloader -> nonstarter. So I'm looking at the Mytouch 4G. How big a limitation is GSM in practice, within the continental US?
* When 802.11 is available, will I be able to use my existing VOIP provider instead of a cell network to make voice calls?
Thanks for any help that anyone might give a complete phone newbie.
Is there perhaps a more suitable forum for me to ask "hey, I've never even owned a cell phone before" type questions? If someone could point me to a better place to ask my clueless questions, that'd be wonderful.
Maybe you will buy HTC HD2?
It's a good phone for start, and it has all of the things what you need
Thanks Rafal.Sw, but that seems to be a Windows Mobile phone, and I'd prefer to stick with open source operating systems.
In any case, I'm more after information here than specific phone recommendations. Thanks for your reply though.
But you can always install android on this Phone, i have it and it's wonderful for me
The specific phone model is really not my primary question. I'm looking for information on my questions above, or failing that, a place more appropriate for novices to ask such things.
Thanks...
Research is key. Search button is your friend and essential. friendly reminder as always
Yes unlocked GSM devices are able to connect to a compatible carrier / sim card. For instance I have an unlocked GSM from att but i hate contracts and burning a hole in my pocket. So.. i went to best buy and grabbed an h2o sim kit and poppeed. It in VOILA. Service= no contract = more money. Of course there are plenty others. With different. Pre paid plans. That's just one of many i use.
Alot of these devices will work around the world ESPECIALLY an unlocked GSM device. Of course they will have to have the WORLD phone type basebands. To achieve this if traveling the world.
GPS has come along way since eclair, and is getting signifucally better all the time. However this really depends on your device and its hardware/software When you see a phone you like find the oppropriate forum and thread and learn about that device. Here on xda.
As far as security with android its great and getting better and better. They stay up to date with the latest. The biggest RISK/ ONLY common are with an OPEN all wifi access connection. Also The problem lies when someone( the user) puts bad apps or pirate apps and files in the device making it vulnerable.
To keep data safe on your phone can be achieved in a number of ways, to name a couple, numerous locks can be applied on apps files even before the device boots up, there are also apps that will wipe every thing on your device if lost or stolen by using your computer to control it. Also apps that will track your phone so you can find it
I to are very strict on the control of my device and with that there are great apps with the kind of extra protection you look for ex. Firewalls, malwate spyware blockers etc. There is no need to unmiunt an SD card. Do you take out your harddrive on your computer when not in USE? "Rhetorical "
CM7 is built AOSP from the ground up. They are in no way or have anything to do with the carrier or its original manufacture. Its totally custom build. Extremely knowledgeable developers who take pride in their work for all of us for free. This is not for your average user. These builds are still in ongoing development and not available for every device. However these builds are very stable for and a daily driver
YES YOU CAN, For VOIP calls, there are apps for that and I've used it for a couple years now, alot of devices can and have already support it, and takes a litle tinkering to get them to work. Now days the Devices coming out have VOIP already ready for setup out of the box. With easy setup
If you want the the best bang for your Buck,
Samsung Galaxy S 2. Is what i recommend. It's truly the best of the best. Along with EVO 3d. And Motorola D3
Sent from SGS Captivate CM7 or MIUI with Escapist orTKGlitch using XDA premium app.
Search button is your friend and essential
Click to expand...
Click to collapse
<nod> I've done some, but there are things I can't quite find anyone discussing, like the use of GPS for wilderness hiking, or the details of block level encryption.
I agree with you 100% about contracts. I'm not sure why they're so popular. They seem more expensive overall, and less flexible.
There is no need to unmiunt an SD card. Do you take out your harddrive on your computer when not in USE?
Click to expand...
Click to collapse
Well, no, but I don't carry the whole machine around in my pocket, either. Somehow the only thing I really trust to keep my data secure is encryption, but then there's this issue of how long the data stays decrypted. You have to be able to use it, but if you lose the device, no one else should be able to see it.
CM7 is built AOSP from the ground up.
Click to expand...
Click to collapse
Yeah, which is why I'd trust it more than the carrier supplied software. I'm pretty much restricting my device choices to ones that CM7 supports, which does rule out several otherwise attractive phones.
Thanks - the Galaxy S2 does look interesting. Is it supported by CM7? Their "devices" page only lists the Galaxy S.
Thanks for the insights, rwells813!
YES, Samsung has sent a SGS2 over to an Cm7 dev. To play with. So i assume in do time it will be a supported mainline. I believe he has test builds for it already . I haven't tried them yet with mine yet. I stick with one dev. Phone at a time. My captivate is the Guinea. Pig. Good luck mate.
Sent from SGS Captivate CM7 or MIUI with Escapist orTKGlitch using XDA premium app.
I have an unbranded tablet running Android 2.3.4 that is unlocked but not rooted (I can't get superuser to work or busy box to install) that I trying to do some hardware/OS related work with and need help. In specific, I am trying to get a USB keypad to work (recognizes keypad but keys do random things and doesn't really work). I believe this requires some ICS libraries (official support added in ICS). I am also having difficulty getting the unit to find a GPS lock using a 3g network (no on board GPS support, but it should be able to find a rough lock using 3g and/or wifi and I don't know why it isn't). In general the hardware is decent but the software is buggy crap, making what could be a decent device crap. I also need some of the default functions for the onboard buttons changed (I think this is build.prop?) We have a kinda random and specific use for these tablets and I have hunted all over for someone to help me and have found a lot of JAVA programmers and not true blue linux/android hardware devs. I understand this is such a specific piece of hardware and unfortunately the work we do won't be able to be shared by a lot of people. If anyone can help me though, I will gladly donate to their cause and/or buy them a few cups of coffee. I would also perhaps be willing to let you keep one of the tablets to play with (they're actually pretty cool). If this is something you can help me with PM me and we can go from there. I am in Dallas, so someone near by wouldn't hurt! Thanks!
PS Please let me know if I have broken any XDA rules here. I have 3 cell phones and a rooted nook color, so needless to say I'd rather not get banned...
Yes, there is one post that follows the process that I used for my SK17i Mini Pro a couple months ago.
I'm new to Android. Yup a Noob. I don't mind saying as we all have to start to learn somewhere and somehow.
Long story short. I've damaged my Very well liked SK17i. Physical is what I mean here.
I rooted it according to some instructions along the lines of:
1. upgrade to firmware xxx.
2. grab image xxx. etc.
3. use the tool to root it.
I diverged... I just installed Doomloards Custom Kernel after step 2 or so and installed it as it was already rooted! It has overclocking though I didn't use it and of course it had Boot recovery. Plenty of other useful tools aready in the .img.
I basically want the same thing for my Pro.
My whole purpose of rooting is for the rights root grants, and to use aps2sd. Sufficient for my functions. (CM mod etc, will have to be a lot more stable for me to consider them which is going to be some time down the road for this device.)
I kept everything else stock. I don't do custom roms etc. This is a daily phone and I need it to function and work for communication.
bboof posted something like what I'd prefer to do. I'm waiting for a reply as to whether his kernel will support aps2sd. (I do mean the XDAversion not anything from Android apps store unless there has been something wonderfully new there in the last 2 months since I bought my Mini Pro.)
I was fighting the Internet here and a machine with HDD problems making for a serious dog dog slow experience here. I'm in CHINA. Censorship and random sites blocked for the fun of it.
I have searched and searched. I have broken out my little 10in Computer here cause it's at least not so mind numbingly painfully slow. (haha Now just fighting the internet. At the moment XDA is not blocked! Started out that way earlier? Had to use a proxy.)
I have been at this for several hours. About 7 so far.
I have FOUND no info on a Custom Kernel for the Xperia Pro MK16i? SO other than bboofs, is there none? Yet I've found comments in others that there are? Even that doomlord has made one. I can find no link? I found such a comment in his one step guide and someone said, why? We already have kernels with root available to be flashed to the device? (Please I want this kernel? how to find it?)
I've googled any number of search parameters i could think of. I can't find.
If there's a Doomlord kernel, just like with my SK17i, I would guess specific firmware is needed? Please tell me which and where to get it... Thank you to any and all who can shed some light here. I live in a different time zone and if I can get an answer that enables me to do what I want... I might be able to order this MK16i tomorrow.It seems a great piece of kit with some nice 'upgrades' compared to my SK17i. (It was not available in Oct.)
What I have found so far. CM7 or was it 9? There's a custom kernel that seems to be required to be installed before trying the CM7 ROM.
So anyone with more experience in Android. Can I use that CM7 Kernel for MK16i? What does it support? (I read back with my SK17i some problems with CM and aps2sd. Something about scripts clashing and all that.) I will not install CM Rom. I will keep stock ROM and I am guessing there may be some conflicts? Yes, no? Maybe?
As I'm asking about using custom kernels... WE all know that the Neo and Pro are the same unit. Just like the Mini and Mini pro were. With the physical difference of a keyboard.
Anyone have a clue or has anyone even TRIED! (Someone adventurous perhaps?) the Kernels for the Xperia Neo on the Xperia Pro? I am a noob, and I do use linux 98% of the time. I don't really work in Windows anymore. However, I'm not a coder or script writer. Also Android for lack of a better term has a few mods.
More or less, in Android, from my simple understanding and yes, correct me if I'm totally wrong or even partially, so I can gain understanding, the ROM is basically where all your program functions and such are. SO when we're talking about the keyboard for example. Parameters and such I would guess are in the ROM?
If all else being equal, I should be able to use a Neo Custom Kernel on my SK16i to achieve my simple result? Or do I have it confused?
What I understand is at least with aps2sd, a ramdisk mod is needed? Does the bboof kernel not only offer root but the modded ramdisk to support other features with everything else being stock? (Actually I'm guessing it should because of mods that should still have been made to allow for the recovery. Though everything else is 'stock'. Of course totally not sure or I wouldn't be here asking.)
Anyone know? I'm more or less sitting here spinning my wheels. I want to order the replacement and at the price difference, it seems silly not to buy the MK16i. (However basically want to be 100% certain I can manage my same little basic setup.)
Also, if anyone with more experience has some idea, I'll be happy to use another tool to gain the ability to put aps on my SD card and not take up the limited space on the device. So please recommend a tool that isn't too complicated.
How about link2sd? Does it also require a modded ramdisk space?
I just want to keep it simple. I don't often need so far, any great mods on my devices. Just root so being in CHINA I can actually use the appstore.
My SK17i does work despite the damage. SO I have ROMmanager the back up program. I haven't really used it yet. (Unable to pay for paid version again other limitations of CHINA. Including an inability to pay for VPN at the moment to stop fighting with the internet. Last time to work with my SK17i took me about 5 days! Coz every link to download the files was blocked!! It only took me about 3min following the instructions to actually update firmware. unlock bootloader, add Doomlords custom kernel. ) Hoping I can use Rom Manager to back up just my programs and shift them right over to the MK16i. Can I do that? Anyone with a bit more experience using the program and does this work with the unpaid version?
Hoping to do the same here... if there's no custom kernels or such available. Please tell me. If there are, links where to download etc.
All those who use various ways to put aps on your SDcard please let me know what works well and stable. Also the real way, not like some of the app store aps. I'll make a ext partition, that kind of approach, on my SD card.
THis is likely by far an advance question... what about running debian or some linux image in chroot on Android and obviously an Xperia. In particular the pro but has anyone tried with anything else? I saw a few links about it a few months ago and even someone has an app in appstore supposed to automate it. (Uh not so important as the primary. Getting root in a kernel and aps2sd support.)
Sorry if this post is long. I'm trying to save you guys wondering what I want, and having to ask me more questions.
In case it's important. I am buying a sim unlocked non carrier specific unit. I buy from Expansys. I live in China so buy from HK. Their products are good and stuff not made for CHINA! Which is the absolute must to avoid. Unless you like fiddling and trying to bypass the limitations they put on their products. Android units sold in CHINA of course are locked by carrier. of course remove Android app store!
Not even going into the necessity to have root so I can 'pretend' I'm in some other country to reach apps that google censors from China anyway.
I hope I've been detailed enough and someone can point me in the right direction.
I've got flashtool and other tools from when I did my SK17i back in October. (Fortunately. I dread to think of the internet fight if I had to try to get them all over again. I'll only need the files specific to MK16i and links to them.)
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I cannot believe the state of JB. Its beta software at best, IMHO.
Example, when typing in a gmail body, if you backspace, the cursor loses its position in the text. And there are issues with inserting new paragraphs and such. These are elementary programming bugs. How long did they test JB before they pushed it to the servers ?
Someone needs to push out an upgrade for JB ASAP. I suspect that ASUS pushed JB out prematurely to capture better Christmas sales. If they don't issue an update its going to backfire on them.
Is there an Android repository somewhere that has global updates, not just ASUS updates ?
I'm new to the whole Android scene. I'm an experienced Linux user.
Why is Android not rooted from the get go ?
Why does hardware come locked down ?
I think Android would be a lot better OS if Google et al opened things up and made it easier for developers to contribute to it, especially prior to the major releases.
Companies want to sell devices. Why do they need to lock the OS to the device ? They already have the OS locked to the device by only supplying proprietary drivers to the OS of their liking. I understand that you might get users harming the hardware by doing illegal things, turning up the cell radio transmitter power, anyone ? But short of that, how is a smart phone different from a PC or laptop where you can easily do what you want with the OS ?
I think JB would be a better product if it was more open and everyday people contributed to its development. Imagine how much better it would be if it followed the Fedora development process whereby a few rcs were released prior to putting it into "stable".
And we could spend our time logging and fixing bugs instead of fooling around with figuring out to unlock, root and flash devices. It would be a win-win for everyone. What Google is doing now is akin to if Fedora (Ubuntu) closed their development process.
I think that Google is afraid that Android is going to get forked in some direction it doesn't like. However, if they keep going the way they are, its almost certain that will be the case anyway.
/rant
I find the wireless router industry fascinating. What does Cisco have to lose by allowing users to flash whatever they want on their hardware ? They have the best of both worlds right now... sell routers locked down for the average person and yet everyone knows how to flash them to build super routers. I think this is the direct the open handset people need to go.