Hi everyone,
I just flashed the ChuckyRom along with Radio v.2.12. I've also been using Android on my HD2 (MUCH thanks to all the talented devs on-board the project) and wondered why I didn't get a phone with Android OS from the getgo. That thought led me to the following super-newbie questions:
1) What's the current status on flashable Android-based rom development? I've been flashing so many WinMo-based roms. Is there an Android-based one, so I can have it as the standard OS on my phone?
(I've heard from quite a few people that I can have Android boot up automatically from start-up using a few tweaks. However, this would still involve booting up from SD card as opposed to having it flashed permanently on my phone.)
2) What seems to be the biggest hurdle to overcome in getting Android OS flashed on an HD2?
Thanks in advance for all of your inputs.
Best,
John
1. It is not a priority, but Cotulla (remember that name) is believed to be working on it, rumour has it it's going to be released even this month. Not seen this confirmed by an official source though, so don't expect it.
2. Not too experienced myself, but from what I've heard it's about decrypting, or making Android compatible with, this filesystem called NAND. A flash-able ROM could probably have been here already, but the devs wanted to focus on delivering quality & bugfree ROMs first, and bonuses such as NAND later on.
Related
Hey,
I've just recently started Android development and I'm keen to learn as much as I can about the whole system, not just about SDK app development. As such I'm interested in attempting to build my own ROM completely from scratch. I've downloaded the Android Source (and Galaxy S source) and would like to try my luck.
First I've been mucking around creating custom ROMs with the emulator, moving apps from the Galaxy S ROM I dumped from my device onto the stock emulator ROM and testing things out.
Anyway I'm at the point where I'm wondering if it's possible to flash the stock emulator ROM onto a Galaxy S phone? I know the Galaxy S source includes a lot of device specific stuff however I'm not interested in getting the camera, bluetooth or anything hardware specific working just yet.
If I flash a ROM with a stock kernel, drivers etc. onto my phone will it work? Has anyone done this? Will it just brick my phone?
Any help would be appreciated.
Cheers,
Ben
Anyone?
Also, I know people have flashed AOSP ROMs on other phones, does anyone know if they required modifications or whether they are in fact stock ROMs?
nje, can't work. why?
1) different bootloaders
2) different partition layout
3) different (kernel)drivers
4) different vendor setup
etc.
it is possible to flash the emulator image onto a dev device (dream/sapphire) but even then a lot will not work properly!
if you want to learn about the android architecture you should start with building a kernel (there is already a thread about that here) and playing around with stuff like the (file)system and utilities...
Thanks jodue.
Yeah my long term intentions were definitely to build the Galaxy S kernel and any necessary libraries and drivers specifically necessary for the apps I decide to include in a custom ROM.
I was hoping that I'd be able to start out by tweaking a minimalistic/generic ROM (the AOSP default ROM) on my Galaxy S. However, as you've pointed out I'll have to start out with the kernel and all the device specific stuff first.
I've got quite a bit of information on building an Android/linux kernel both from the thread you mentioned and also the official AOSP page. However information on putting together a complete working ROM seems a bit sparse. Does anyone know where I can find some information on the topic?
I'm also curious to learn about the list of things jodue mentioned i.e. Android bootloaders, partition layouts and drivers (generic and Galaxy S specific). I assume detailed information about particular devices and drivers probably isn't available but if anyone even knows where I can learn detailed information about default AOSP ROMs I'd be extremely interested know.
Gents,
I need your help about "kernel", as I know when installing Android I need the folder named Android and the data.img.
But the kernel what is that?
Thanks for reading and more for helping.
The kernel is the core of the Android OS. Windows too runs on a kernel. Every build already includes one, and usually the most up-to-date or stable version, so you shouldn't have to worry about it, unless you want to update your kernel some time in the future.
I've been running Android for several months now and I've not updated the kernel once.
Still there is somthing to say
First I want to thank you for giving me some of your time.
The answer is clear, but why there is update always (now is 8.6)?
and what the kernel is including, is it the same of Android folder?
I hope I will find some more time.
Check out here for a bunch of explanations of terms that are commonly used around here
http://forum.xda-developers.com/showthread.php?t=852660&highlight=glossary
The reason that the kernels are updated alot is that the people who build the kernels find flaws in them through testing them, and through the feedback they recieve here on XDA.
Then they work to try and find ways to fix those flaws. Sometimes in fixing one flaw, a new one emerges. Generally it is a good idea to use the latest version of whatever kernel came with the build.
Hi,
Anyone have any success in enabling full device encryption using any of the Android ROMS (CM9, PA, etc?).
The reason I ask is that I flashed the ParanoidAndroid 1.5b NAND ROM but when I try to encrypt the phone it never even begins. It just hangs at the initial screen with the little green android guy.
I've read a lot of posts and there doesn't seem to be much success with ICS encryption and most ROMs. It seems the problem lies with the partitioning used in most ROMs, as can be seen in this excellent post about the subject.
So, given that many users in a corporate environment are required to have full device encryption, the question remains.
Anyone have any experience with ICS encryption on any of the android ROMs? Or does anyone know if there are plans for a encryption friendly CM or PA ROM?
It seems to me that a privacy friendly Blandroid type ROM for the HD2 would be a nice niche to develop. As far as I know, this has not yet been done.
Thanks
Hey fellow former's I have a few questions take time to answer them in a understandable manner. Thank You!
(These questions all involve after rooting my nexus)
1. What is a theme chooser? Is it similar to an the Ipods Winterboard?
2. Would I use device explorer to edit my ROM?
3. Are themes the same thing as a ROM since the change how the device looks/ performs?
4. What is Team Win Recovery Project and ClockWorkMod and what are the used for?
5. What cool ROM would you recommend for me?
Thank you for your time and AMAZING support! You guys rock :good:
Hippxl12345 said:
Hey fellow former's I have a few questions take time to answer them in a understandable manner. Thank You!
(These questions all involve after rooting my nexus)
1. What is a theme chooser? Is it similar to an the Ipods Winterboard?
2. Would I use device explorer to edit my ROM?
3. Are themes the same thing as a ROM since the change how the device looks/ performs?
4. What is Team Win Recovery Project and ClockWorkMod and what are the used for?
5. What cool ROM would you recommend for me?
Thank you for your time and AMAZING support! You guys rock :good:
Click to expand...
Click to collapse
1. It customizes the look of the device; sort of.
2. No.
3. No.
4. Recoveries that you can boot into; flashing ROMs.
5. CM10.
If you want more detailed info, search for it, it's literally all over XDA.
Question 2
Explain number 4 a little more and tell me what a flashing rom is please
lol. Those were some pretty short answers.
A ROM is the operating system of the phone. Android is open source so anyone can customize the OS and make changes. Those can be performance changes, having certain apps installed by default (or removed in most cases since cell companies load Android phones with so much crap), visual changes by modifying the stock theme, or complete re-writes as is the case with MIUI. If you like iOS then you would probably feel very at home moving to an MIUI based ROM
A Theme can usually be installed onto any ROM and it just modified the way the OS looks.
The recovery is where you boot the device into in order to flash a custom ROM or kernel, or some system apps, or things like that. You use TWRP or CWM as a replacement for the limited and locked down stock recovery that the phone/tablet comes with.
Be sure to look at what features come with a ROM before deciding. Many early ROMs are labelled as alpha or beta builds and usually contain lots of bugs and have missing things and some areas that dont even work at all. Nexus devices usually dont have alpha ROMs though since they work 100% with Google source and have no cracking to do because nothing is locked down at all.
Help
By recovery what do you mean like revert it back to factory setting what is it used for, thank you for good awnsers! btw
Hi all,
I see sometimes that there are unofficial ROMs made of official ROMs such as Paranoid Android, that support devices such as our own before the original ROM creator does.
Now I know nothing about making ROMs, I'm guessing there of course is specific firmware and drivers for our phone as one example, unique to us.
Is it a support question, as in the official makers could support another phone (easily?!), but don't, because they don't have the device to confirm it works fine or may carry a brick risk etc?
How hard is it to make an "unofficial" ROM that supports specific devices features/hardware? Is it a case of merging differnt device firmware with another kernel and testing? (I'm sure some will be mad at my naivety)
Sorry for the newb question.