Hi,
About 2 weeks ago I downloaded the Android ROM for my HTC HD2, it works great, I really like Android more then Windows Mobile. Although everything works and seems fast enough, i have the feeling my phone can do more. If i look at videos of a HTC Desire HD it runs much faster, though the hardware is almost identical.
As I understood my phone is still running Windows Mobile but it is running in a state that emulates the hardware for a Android phone, so i can run Android. Now for my question, is there a way to run Android directly on my phone, without using Windows Mobile in the background?
Greetz Willem
williamsean said:
Hi,
As I understood my phone is still running Windows Mobile but it is running in a state that emulates the hardware for a Android phone, so i can run Android. Now for my question, is there a way to run Android directly on my phone, without using Windows Mobile in the background?
Greetz Willem
Click to expand...
Click to collapse
this question is in the wrong section
ATM its not possible for none DEVS to run Andriod directly from you phone NAND memory.
DEVS are working on it but there are still some issues to solve before it will be launched you can follow the progression at the link below:
http://forum.xda-developers.com/showthread.php?t=817261
When you switch over to Andriod as a native OS you wont be able to run WM anymore, you can multi boot Android OS and Unbuntu of your SD, so if you want to use WM also then running Andriod of your SDcard is the only option
wilwilwel said:
this question is in the wrong section
ATM its not possible for none DEVS to run Andriod directly from you phone NAND memory.
DEVS are working on it but there are still some issues to solve before it will be launched you can follow the progression at the link below:
When you switch over to Andriod as a native OS you wont be able to run WM anymore, you can multi boot Android OS and Unbuntu of your SD, so if you want to use WM also then running Andriod of your SDcard is the only option
Click to expand...
Click to collapse
Thanks for replying, what do you mean with ATM? and DEVS?
For what I understand from you post, they are working on a native android rom for the HD2, but it's not finished jet... And when I would install it i can't boot windows mobile anymore... Is that correct?
Will there be a posibility to revert my phone back to windows mobile when i would like to sell my phone...
-First winmo is shutdown when booting android.
-At the moment booting right from the hd2 memory is only possible with nand (from internal memory) . Wich is currently not for public release because it contains bugs.
-The reason why it is not at same speed as desire hd is that the kernel for the hd2 is not perfect and maybe nand can do a little speed increase. But it is getting better current kernels are much faster than a month ago.
ATM= At the moment
DEVS= Developers
PS: This is the wrong section.
jan-willem3 said:
-First winmo is shutdown when booting android.
-At the moment booting right from the hd2 memory is only possible with nand (from internal memory) . Wich is currently not for public release because it contains bugs.
-The reason why it is not at same speed as desire hd is that the kernel for the hd2 is not perfect and maybe nand can do a little speed increase. But it is getting better current kernels are much faster than a month ago.
ATM= At the moment
DEVS= Developers
PS: This is the wrong section.
Click to expand...
Click to collapse
Witch section should it be in? Q&A or something? Can I change that right now?
What I understand is that it actually doesn't make a difference when I would boot android without windows mobile, only a minor speed increase because of faster memory? The real speed increase would come from a better kernel, witch the developers here are working on... Is that right?
Do you happen to know a ROM with this newer kernel? (so i can see if i already have it)
williamsean said:
Witch section should it be in? Q&A or something? Can I change that right now?
What I understand is that it actually doesn't make a difference when I would boot android without windows mobile, only a minor speed increase because of faster memory? The real speed increase would come from a better kernel, witch the developers here are working on... Is that right?
Do you happen to know a ROM with this newer kernel? (so i can see if i already have it)
Click to expand...
Click to collapse
You can't change that right know but that is not a real problem. And what you are saying is right. We have to wait for a better kernel.
In terms of rom with kernel newer roms have most of the time newer kernels.
You can select [Everyday Builds][latest linux_on_wince_htc][PPP] CM6.1+ from michyprima this ones has no sense but are really speedy compared to sense builds. They use latest kernel. Anyway if you pickup a build from the last 7 days you can put any kernel that you want of it my favorite kernel at the moment is this. And contains a patch wich resolves screen freeezes wich happen sometimes. The most recent kernels are mdeejay S4 & hastrin r8.2. Or the CM6.1 build I said above because it have the latest kernel. The hastarin where I link you to contains the touchscreen freeze fix. Wich is not included in all hastarin 8.2 kernels.
jan-willem3 said:
You can't change that right know but that is not a real problem. And what you are saying is right. We have to wait for a better kernel.
In terms of rom with kernel newer roms have most of the time newer kernels.
You can select [Everyday Builds][latest linux_on_wince_htc][PPP] CM6.1+ from michyprima this ones has no sense but are really speedy compared to sense builds. They use latest kernel. Anyway if you pickup a build from the last 7 days you can put any kernel that you want of it my favorite kernel at the moment is this. And contains a patch wich resolves screen freeezes wich happen sometimes. The most recent kernels are mdeejay S4 & hastrin r8.2. Or the CM6.1 build I said above because it have the latest kernel. The hastarin where I link you to contains the touchscreen freeze fix. Wich is not included in all hastarin 8.2 kernels.
Click to expand...
Click to collapse
Thnx for the reply, all is much more clear now...
I only have 1 more question, can update only the kernel of a ROM, so i don't have to install a hole new ROM and keep my preferences?
Yes that is also possible.
Is there something like a guide for it? url?
Installation:
1. Copy zImage to the "Android" folder on SD card
2. Copy "root" folder to "Android" folder on your SD card (overwrite files or combine when needed never delete the current one and replace it with the new one always overwrite files if folder structure already exists)
Sometimes the folder root is not included by the kernel then create
root/system/lib/modules
inside put :
tun.ko
bcm4329.ko
cifs.ko
and create:
root/system/lib/hw
lights.htcleo.so
If the file is not inside the package then don't create a folder for it. You should always have this file bcm4329.ko The rest is different for different kernels.
Edit:
You can download a kernel in different threads.
For example: http://forum.xda-developers.com/showthread.php?t=831585
For example: http://forum.xda-developers.com/showthread.php?t=787588
VBN files should also have latest kernel without tweaks but cant find it now.
Related
Since I run Linux systems at home I'm really interested in running it on my phones too. I kinda ordered my new phone since my TYTN is falling apart (does not synch thru USB anymore) so I can wait till late november for HTC to release their phone on Android.
So, do you think HTC will make an Android ROM for the Raphael? (or is there a big probability someone will cook it from another ROM)
I don't think they will do such a Android-ROM for Touch Pro as they will try to sell their new Android-Device. But since the Touch Pro has this Qualcomm-CPU, I hope Android will run on it - Again, made by some community-member, not HTC.
would somebody like to try booting linux on the raphael? I wonder if things will behave in the same way as on the diamond ( http://forum.xda-developers.com/showthread.php?t=402002 )
in that thread, marbalon posted http://forum.xda-developers.com/attachment.php?attachmentid=104265&d=1218018832 a package with latest haret and a build for the halibut machine from the google git.
also you can replace the zImage in the diamond.zip with the zImage builds for vogue from dzo: for example http://it029000.massey.ac.nz/vogue/zImage
or try the kaiser kernel http://linuxtogo.org/~lgorris/kaiser-bootkit/zImage.bin
and report what happens. does haret get further than go go go? Which machine does it detect?
thanks
can a moderator move this to raphael rom development please?
I tried the bootkit for Diamond, the latest builds for the kaiser from igorris and also the latest build for vogue - but all hang up.
i will investigate a bit....
do they hang at 100% / Go Go Go? Do you see console output?
dcordes said:
do they hang at 100% / Go Go Go? Do you see console output?
Click to expand...
Click to collapse
Yep at 100%, Go Go Go i can´t see.
Please take a look in this topic..
http://forum.xda-developers.com/showthread.php?t=402002&page=17
Its about running Android on the Diamond..
And they didnt got it working...
And the Pro got the same proccesor/chipset ast the Diamond..
we created a research page with links to the kernel relevant wiki pages:
http://wiki.xda-developers.com/index.php?pagename=RaphaelResearch
dcordes said:
can a moderator move this to raphael rom development please?
Click to expand...
Click to collapse
Done... and good luck!
As i wrote last time, i didn´t get running the kernel for Kaiser (Latest Build) and Vogue (Latest Build).
Now it seems that the problem is or at least could be related to the storage card. It´s a common problem that sdhc-cards over 4gb won´t work as a android drive. so maybe anyone can try it with a card that fit the needs - i have only a 8gb model?
Good Luck and post every result!
I have tried vogue version on my raphael but it hangs on booting linux... 100% and i it hangs every time.
files are on phone not on sd card.
/Andre'
apokryphus said:
As i wrote last time, i didn´t get running the kernel for Kaiser (Latest Build) and Vogue (Latest Build).
Click to expand...
Click to collapse
It is not a big surprise, because Raphael has a different CPU.
Now it seems that the problem is or at least could be related to the storage card.
Click to expand...
Click to collapse
The SD controller on MSM7200 CPU is located in a different memory area
compared to the MSM7200A CPU.
Edited, I thought you meant a different processor than the G1.
Kinda stupid why people funny toil to try execute a linux on a wm6 device?decide whitch one uu want then buy... 4 my is awful idea have linux on my diamond pro no thx...
seeing forward to try android for this phone.
waiting...
/andre'
norrback said:
seeing forward to try android for this phone.
Click to expand...
Click to collapse
We need the G1 kernel source, and modules (if there would be some closed-source drivers). I have documented many (most?) MSM gpios,
the DRAM config is known too. I'm researching the Hitachi LCD setup
because G1 has a different panel, so it will be necessary to modify
the init/suspend routines.
donottouch said:
awful idea have linux on my diamond pro no thx...
Click to expand...
Click to collapse
Well, we don't post here that virtually everything from micro$oft sux, don't we ?
I'm not a big google fan, but fighting the monoculture is always a good thing.
cr2 said:
Well, we don't post here that virtually everything from micro$oft sux, don't we ?
I'm not a big google fan, but fighting the monoculture is always a good thing.
Click to expand...
Click to collapse
Totally agree.
wm is the best mobile os at the moment unfortunately (if android is not counted), nokia's symbian just plainly.. eh, stinks. and so on.
Android would be really nice, waiting for it to raphael, even as a flashable rom! That would be so awesome! (we dont need WM to flash, it works straight from the bootloader, so why not!)
Rottis said:
Totally agree.
wm is the best mobile os at the moment unfortunately (if android is not counted), nokia's symbian just plainly.. eh, stinks. and so on.
Android would be really nice, waiting for it to raphael, even as a flashable rom! That would be so awesome! (we dont need WM to flash, it works straight from the bootloader, so why not!)
Click to expand...
Click to collapse
You hit my point of view!
I just read in the XDA Portal that someone found a way to dual boot between two different Android Roms on one phone and ,well...i was wondering if this is possible with Windows. i have Miri N Dinik's Rom right now but say i wanted to try out Energy's Rom too...but keep my previous Rom. Is that doable or is there something special in Android phones that makes it possible?
fusion06 said:
I just read in the XDA Portal that someone found a way to dual boot between two different Android Roms on one phone and ,well...i was wondering if this is possible with Windows. i have Miri N Dinik's Rom right now but say i wanted to try out Energy's Rom too...but keep my previous Rom. Is that doable or is there something special in Android phones that makes it possible?
Click to expand...
Click to collapse
Thread moved to Q&A
To answer your question no its not possible to dual boot between 2 WinMo Roms. Android runs of partitions so you can install an Android Rom on different partitions and then select which partition to boot from. WinMo doesnt work like that.
Mark.
oooohhh o.k. thanks ! i need to hurry up and take these IT classes to further my computer and systems knowledge. January can't come soon enough. iv'e learned so much from just this site alone though..i think i'll have a bit of a head start when i do start class.
fusion06 said:
oooohhh o.k. thanks ! i need to hurry up and take these IT classes to further my computer and systems knowledge. January can't come soon enough. iv'e learned so much from just this site alone though..i think i'll have a bit of a head start when i do start class.
Click to expand...
Click to collapse
Just use xda as your reference guide and you will do fine lol.
Mark.
As I understand it, there is a linux kernel that android sits on. I thought the ROM was like a virtual machine running inside of android and then we loaded apps onto that. I read something that indicated that each custom ROM comes with a kernel. Then we can replace that kernel with another one if we wish. I understand that the kernel must be compatible (although I don't know how to tell) but that seems confusing. It would seem that if the ROM is running in android then as long as the kernel can run android, any kernel should suffice. Clearly that is not the case so what exactly is a ROM and why does it interact directly with the kernel?
A ROM in this case is a system image (full or partial) containing the Android operating system, drivers, applications, and/or kernel.
Like with regular PC OS not all kernels are compatible with the larger OS, primarily across major versions.
check this link
http://www.xda-developers.com/android/understanding-android-fr
Rom futures
does anyone know where roms are going? read somewhere 2.3 and 3.0 are forks. that makes sense if 2.3 continues focus on phones, small devices etc and 3.0 continues down the larger tablet track. I am currently running 2.3.3 on gtab and it runs great. it seems to be very tablet friendly. does 2.3 provide much of the functionality of 3.0 for the small screen. can we expect 3.0 to bring additional utility to tabs like the gtab? just curious where we might be headed. keep up the great work. i stay excited about the next build!
Rumbleweed said:
check this link
http://www.xda-developers.com/android/understanding-android-fr
Click to expand...
Click to collapse
This is a GREAT link! Thanks.
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
shadowrelic said:
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
Click to expand...
Click to collapse
You are correct about the ROM, but ROMs also include the kernel (if it didn't, or no kernel was flashed separately, the device would not boot). Yes, other kernels can be flashed on your existing ROM, but it's not necessarily going to be compatible.
Sort of, but there's a lot more than that. See here and here. Later versions of Android will require newer drivers,etc. which the existing kernel won't provide (they'll be outdated). Back porting and additional coding is theoretically possible, but insanely difficult (many times). Even after this some things may still not work.
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
shadowrelic said:
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
Click to expand...
Click to collapse
For both your questions, the Nexus-line devices would be the way to go. They usually have everything working on new Android versions the soonest, and Google always releases their code, etc.
Hi
i can use linux kernel (zimage) to update android kernel if yes ,how ?
thnx
The title says it all.
I don't know if you guys watch the latest news in the Android section (i hope so). One thread made me listening: NativeSD.
As far as im concerned, it comes down to emulating an internal rom space on a (preferably faster) microSD.
So: We have no WM6.5 sd-build. Why not installing a "normal" rom in ths NativeSD-space?
Would this work?
Greetings from Germany,
schousta
schousta said:
The title says it all.
I don't know if you guys watch the latest news in the Android section (i hope so). One thread made me listening: NativeSD.
As far as im concerned, it comes down to emulating an internal rom space on a (preferably faster) microSD.
So: We have no WM6.5 sd-build. Why not installing a "normal" rom in ths NativeSD-space?
Would this work?
Greetings from Germany,
schousta
Click to expand...
Click to collapse
AFAIK it's not possible yet. I know Cotulla posted on Twitter he was working on that. But I think bootloader won't support it, but I'm not sure
I assume that someone would still need to take apart the windows bootloader. That's what many here are waiting for. Haret is for linux build.
But I will jump in as soon as its ready to gogogo!
Sent from my HD2 using the power of Jelly Bean
If I remember correctly, Cotulla was done with making it possible to run Winmo on a SD card. He is just stuck (I guess) about figuring out how Winmo, Android, and I think WP 7 were going to share the same partition. My guess is its not working how he'd like so he put things aside and is working on other projects until new ideas or solutions come about in the future. What I'm wondering is why he just doesn't go ahead and release the Winmo SD by itself as I see he already made a DWI flasher for it already.