Alright, may seem like a stupid question to some. I've searched trust me. Whats the difference between flashing a new version of android and using a new zimage?
For instance, Im using "FROYO BUILD BY dan1j3l" and using the 25/7 zimage. Whats the difference between using that and the for example "Froyo 2.2 Android Build by Parad0XUA" with the same zimage or darkstones's 26/7 new froyo build?
Im guessing that functions wise, it depends on the zimage but stability wise on the version of android? can anyone enlighten me?
Julian2103 said:
Alright, may seem like a stupid question to some. I've searched trust me. Whats the difference between flashing a new version of android and using a new zimage?
For instance, Im using "FROYO BUILD BY dan1j3l" and using the 25/7 zimage. Whats the difference between using that and the for example "Froyo 2.2 Android Build by Parad0XUA" with the same zimage or darkstones's 26/7 new froyo build?
Im guessing that functions wise, it depends on the zimage but stability wise on the version of android? can anyone enlighten me?
Click to expand...
Click to collapse
Look at it this way:
New ROM=new UI
New Zimage=new version
Basicaly...when you update ROMS you are giving a total update to your phones UI and when you update Zimage...you are only updating the file that tells your phone wich version of Android to use.
Hope this answers your question
this means theoretically speaking, darkstone's newest build with the same zimage would be better than dan's froyo(one of the earlier ones) with the same zimage?
I hope I'm right. Thanks, it has cleared some of the doubt in my head about this matter
Julian2103 said:
this means theoretically speaking, darkstone's newest build with the same zimage would be better than dan's froyo(one of the earlier ones) with the same zimage?
I hope I'm right. Thanks, it has cleared some of the doubt in my head about this matter
Click to expand...
Click to collapse
yeah thats right mate, plus prob has better drivers or new things that have been solved so it will be smoother
Demon_man said:
yeah thats right mate, plus prob has better drivers or new things that have been solved so it will be smoother
Click to expand...
Click to collapse
Oh alright, thanks guys
but how can i solve the robotic voice problem in android?? :S i cant talk with android...
Julian2103 said:
Alright, may seem like a stupid question to some.
Click to expand...
Click to collapse
LOL, was wondering the same thing myself
just to add something...
have you ever heard, when speaking about linux, the words "distro" and "kernel"?
well, a distro (like ubuntu, mandriva, red hat) is the "whole world" built around the kernel, that is the same in all distros (if you keep it to date and recompile it).
The kernel is "the real thing", the way the os can "speak" to the machine and the HW.
Well, the Zimage is the kernel, the "rom" is the distro.
In other words, once you have chosen the "distro" (the rom) you like, you could only keep the kernel (the zimage) up to date, in order to have the newest features and the hw working (eg the last zimage solves the panel problem, it was not "slleping" while in sleep mode. One of the future zimages will add the gps support)
Hope to have semplified ...
@victorbd :
have you run crlcad?
it usually solves the sound problem.
Have you the right radio (.50 and better above .08)?
if yes to the previous questions, try a different ROM (WM ROM)
Very helpful,
Thanks
devilman said:
just to add something...
have you ever heard, when speaking about linux, the words "distro" and "kernel"?
well, a distro (like ubuntu, mandriva, red hat) is the "whole world" built around the kernel, that is the same in all distros (if you keep it to date and recompile it).
The kernel is "the real thing", the way the os can "speak" to the machine and the HW.
Well, the Zimage is the kernel, the "rom" is the distro.
In other words, once you have chosen the "distro" (the rom) you like, you could only keep the kernel (the zimage) up to date, in order to have the newest features.
Hope to have semplified ...
Click to expand...
Click to collapse
Very well put. Thanks
devilman said:
just to add something...
have you ever heard, when speaking about linux, the words "distro" and "kernel"?
well, a distro (like ubuntu, mandriva, red hat) is the "whole world" built around the kernel, that is the same in all distros (if you keep it to date and recompile it).
The kernel is "the real thing", the way the os can "speak" to the machine and the HW.
Well, the Zimage is the kernel, the "rom" is the distro.
In other words, once you have chosen the "distro" (the rom) you like, you could only keep the kernel (the zimage) up to date, in order to have the newest features.
Hope to have semplified ...
Click to expand...
Click to collapse
Wonderful and simplicity example.
Thanks!
Sent from my HTC Desire using XDA App
right boba, i was tempted to add something like this to my explanation, but i decided it would have confused more...
so, just to summarize everything, what boba is rightfully saying is that the right combination is a rom written for the zimage that it uses, so that it can really make "usable" all the features the zimage is able to "drive"
this said, usually (but not always) updating the zimage is enough to have the new features
The android version used in these buids, extracted from other pdas like the Desire, in fact, is able to use all the feature the phone has, but sometimes it cannot use them because of the zimage that is not able to drive the hw (think about the gps at the moment)
So, when speaking about android and hd2, usually updating the zimage is enough (the developers tell us when it is not enough)
victorbd said:
but how can i solve the robotic voice problem in android?? :S i cant talk with android...
Click to expand...
Click to collapse
Well Victorbd, since day one I have also had the robot voice problem. Today I flashed a different WM rom onto the phone, and now the robot voice is gone. Volume is rather low, but I am sure this will be resolved sometime in the near future.
Here are my settings, hopefully they will help.
#1 The Phone is a US T-Mobile HD2
#2 The WM ROM is OzROM 4.40 WWE
#3 The Android build is Darkstone HD2 Froyo V.1
#4 The zImage isCotulla zImage 7.25.10
Now I just have to find a solution to the sleep of death.
Good luck boss.
intoxic8ed said:
Now I just have to find a solution to the sleep of death.
Click to expand...
Click to collapse
You might want to trying the previous zimage 7/23. The 7/25 gave me wierd wake-up issues. I could still wake it up, but it required two power button presses.
Now, here's another stupid question... I'm using the 7/23 zImage as I've heard of all the problems people are having with the 7/25. When the next zImage is released, assuming it's as stable as 7/23 (which has been perfect for me), when I replace the zImage, do I essentially have to re-setup my Android build? Because I've literally gotten it to where I use it as my daily ROM. I'm literally having no problems other than VERY occasional 3G/Data loss but even that works most of the time. Will just updating the zImage leave all my settings/apps/etc...?
You just to back to WMo, plug in to your PC, take out the old zimage and put in the new one, restart Android. Should things work worse than they did with the old zimage, just reverse the procedure.
Related
Hi everyone
What is peoples oppinion on full winmo roms like VBN or Energy and also using Android? Or do you go for the lite versions which should be more Android friendly?
Currently i am running VBN Droid Rom but i am missing a few features in the lite versions... Wondering to go back to the full roms but just thought i would ask around what your experience is with the full winmo roms compared to the lite ones
Thank you all
radio and rom
http://forum.xda-developers.com/showthread.php?t=651729 is a great full tweaked rom that works perfect with android!! give it a try youll love it!! i used lite roms for android and the elegancia works just as good! more important than the rom is the radio it will make all the difference! 2.12.50.2_02 works best for most http://forum.xda-developers.com/showthread.php?t=611787!!!
i use a full windows rom and dont see any need to swap
Richy99 said:
i use a full windows rom and dont see any need to swap
Click to expand...
Click to collapse
Ditto here.
Always been an Energy Rom user, but thought I would give ChuckyDroid a go, as basically using Android as my day to day OS.
I found that with ChuckyDroid I was having more screen freezes and hard freezes (pull the battery), so switched back to Energy.
I believe there isn't much difference between the full and lite roms when running Android, its just down to personal experience and what works for you best.
As long as the Rom is Android friendly, and has the correct files cooked in to stop Robovoice etc, you won't see much difference apart from mainly the boot up speed if your booting straight into Android. As there was a considerable difference booting to Android using ChuckyDroid compared to Energy. ChuckyDroid was lightening quick.
Energy Aug 28th Radio 2.12
Bangsters 1.4
bobmarsh72 said:
Energy Sept 28th
Click to expand...
Click to collapse
Quick, what were the lottery numbers for tomorrow? Or did you not jot them down while you were in the future. J/P, I had to.
bobmarsh72 said:
Always been an Energy Rom user, but thought I would give ChuckyDroid a go, as basically using Android as my day to day OS.
I found that with ChuckyDroid I was having more screen freezes and hard freezes (pull the battery), so switched back to Energy.
I believe there isn't much difference between the full and lite roms when running Android, its just down to personal experience and what works for you best.
As long as the Rom is Android friendly, and has the correct files cooked in to stop Robovoice etc, you won't see much difference apart from mainly the boot up speed if your booting straight into Android. As there was a considerable difference booting to Android using ChuckyDroid compared to Energy. ChuckyDroid was lightening quick.
Energy Sept 28th Radio 2.12
Bangsters 1.4
Click to expand...
Click to collapse
Please define "Android friendly", or is that what chef just saying to make you feel comfortable, more confident to use with Android?
I cooked my own rom from the kitchen, I just unchecked this, unchecked that....then... you know....,I know nothing about Linux, Android, and my rom just run perfect with any Android build.
oh, I put a line says " this rom specially made to run Android", maybe that make my homemade rom "Android friendly".
juggs said:
Quick, what were the lottery numbers for tomorrow? Or did you not jot them down while you were in the future. J/P, I had to.
Click to expand...
Click to collapse
My bad lol Aug 28th....
justwonder said:
Please define "Android friendly", or is that what chef just saying to make you feel comfortable, more confident to use with Android?
I cooked my own rom from the kitchen, I just unchecked this, unchecked that....then... you know....,I know nothing about Linux, Android, and my rom just run perfect with any Android build.
oh, I put a line says " this rom specially made to run Android", maybe that make my homemade rom "Android friendly".
Click to expand...
Click to collapse
There are several .dll files that need to be in your build.... Im searching for the thread, as Im no expert but have read on this.
These files may already be in your base ROm when uploading, but the Roms that were having the problem with Robovoice I believe these files were added and if not fixed the problem were part of the reason it was fixed.
Edit....given up searching for the posts (so many to look through with key words such as robovoice, files, rom, android etc) but from what I can remember it was dll files taken from a stock 2.10 rom, which helped with the problem.
Edit again....Found the thread http://forum.xda-developers.com/showthread.php?t=757914 Actually reading back it doesn't give a definite answer if theses files did work, but it sounds like they did for pkoper.
I've tried ChuckyDroid & it was very good if you're running Android 24/7, but it's VERY lightweight. I'm using VBN now because I wanna have a usable WM rom just in case something happens to my Android installation(card dies, gets corrupted, etc.) & I'm not able to fix it right away. I've noticed no difference in performance upon switching roms. That said- I got robo-voice BAD on the stock WM rom, and it went away as soon as I flashed a custom rom.
bobmarsh72 said:
As long as the Rom is Android friendly, and has the correct files cooked in to stop Robovoice etc, you won't see much difference apart from mainly the boot up speed if your booting straight into Android. QUOTE]
I'm using a pre-Android EnergyROM for WinMo and it works fine. So not so sure about the correct files being cooked in?
One thing I've found is that Sense will get corrupted for some reason. So make sure you disable Sense (and then restart) before jumping into Android.
It'd work a few times, then on my 4th or whatever reboot into Android, Sense would decide to die. Not sure why, as Android isn't meant to interact with WinMo, but it would.
Click to expand...
Click to collapse
1. [BUILD][04.11.2010] [Core Droid V0.6][SUPERSONIC (EVO 4G)][Kernel Hastarin #R8]
Instructions:
- Make Sure you have a Windows Build and Radio Compatible with Android you can use any of my ROMS since they are the ones i use too test Android so they are 100% compatible.
- If you already have an Android folder on your SD Card DELETE IT OR RENAME IT, because this version MAY BE INCOMPATIBILE with other builds.
- Extract the Android folder (with all files in in) to root of your SD Card. THIS IS IMPORTANT.
- After copyng everything to your SD Card ensure you have at least 1200 Mb free space for data store.
- On first run when there is “Creating a new data.img” just give it time to complete, and on first boot be patient and give it time to load everything.
Builder - Sergio76
Click to expand...
Click to collapse
2. [BUILD][02.11.10] HD2ONE 0.2.4 & 0.3 [CM6.1][Multi-kernel][RMNET+PPP][FM][Solid]
Test Environment
WinMo: ChuckyDroidROM 23139
Radio: Leo_RADIO_2.15.50.14
Builder - Kouno.Takaaki
Click to expand...
Click to collapse
3. [UPD][BUILD](29.10.2010)New Customize (iphone,sense,galaxys) in one Build mccm SE 3.0
If having problem try to flash other ROM and Radio
Try This: OzDROID ROM(Bare WM ROM With Bootloader)
http://forum.xda-developers.com/showthread.php?t=774417
or
Core Cell EVO's custom rom
http://forum.xda-developers.com/showthread.php?t=617142
I'm using : Elegancia Rom - Miri colored by Steve0007 v9.5
My Radio Leo 2.15.50.14
http://forum.xda-developers.com/showthread.php?t=611787
Builder - mccmjoon76
Click to expand...
Click to collapse
4. [UPD][BUILD][11-5-2010][JDMS 1.5][Hastarin R8][PPP+RMNET][Themed+Stock]
If that does not help, I suggest you to change your rom and radio with those
- OzDROID ROM(Bare WM ROM With Bootloader)
- Leo Radio_2_10_50_26. Check My siggy..
Builder - atoore
Click to expand...
Click to collapse
5. [BUILD][TMOUS ONLY][05.11.10] Desire Sense - BlueTopia v0.6.1 [kernel:hastarin R8]
I use Radio 2.15.50.14 and VBNROM RELOADED 2 Alternate WM Rom.
http://forum.xda-developers.com/showthread.php?t=776971
Builder - cmylxgo
Click to expand...
Click to collapse
6. (BUILD)(Nov.3.2010) BiffMod-HD2 v1.1 - Vanilla Froyo (Kernel-hastarn 7.7)
*****I'm using ChuckyDroid lite with the latest 2.15 radio and have no issues. If you don't have this setup and are having issues....that might explain it Also be sure you are using clrcad.exe before EACH boot and have the android folder on the root of your sdcard. If you have "bugs" try running fix_permissions and clearing market cache from settings.*****
Builder - infinitybiff
Click to expand...
Click to collapse
AND THE BEST OF ALL
FROM darkstone HIMSELF
7. FroyoStone Sense - Version 3.2 (17-October-2010)
If you are having issue with audio, whether if it is high pitched or you are hear robot noises during calls, then I recommend you switch over to a new Windows Mobile rom.
I use this rom: kwbr HD2
My radio is 2.12.50.02_2
Click to expand...
Click to collapse
its up to anyones interpretation,
but the above says it all
****USE RECOMMENDED WINMO ROM AND RADIO****
the main purpose for the threads' creation is brought about by my reading and posting
through the threads and encountering a lot of people having problem Installing
Android and that a proven and tested method of using the builders recommended
winmo ROM and Radio is mainly being ignored due to the fact that a lot of people
are able to run Android on stock ROMs even without HSPL. although I am not
contradicting this, but as almost all of those people posting problems which are
perplexing dont receive a definitive answer, the only other option really is
to use what's been recommended.
Click to expand...
Click to collapse
jigners said:
1. [BUILD]
AND THE BEST OF ALL
FROM darkstone HIMSELF
Click to expand...
Click to collapse
Hmm, I can think of 10+ builds better than darkstones
Seriously i have no clue wat you are trying to tell us here.
Are you promoting using the ussage of roms that these builders use ?
If so why open up a topic for it its already in every post of the builders build.
shuntje said:
Seriously i have no clue wat you are trying to tell us here.
Are you promoting using the ussage of roms that these builders use ?
If so why open up a topic for it its already in every post of the builders build.
Click to expand...
Click to collapse
the main purpose for the threads' creation is brought about by my reading and posting
through the threads and encountering a lot of people having problem Installing
Android and that a proven and tested method of using the builders recommended
winmo ROM and Radio is mainly being ignored due to the fact that a lot of people
are able to run Android on stock ROMs even without HSPL. although I am not contradicting this, but as almost all of those people posting problems which are
perplexing dont receive a definitive answer, the only other option really is
to use what's been recommended.
Most people are just to lazy to do any searching to find the answers. They will still have issues will the simple layout you have provided. I've noticed they don't even know that the down loads appear in the first couple of post on every thread. I mean how simple is that.
cwsmall said:
Most people are just to lazy to do any searching to find the answers. They will still have issues will the simple layout you have provided. I've noticed they don't even know that the down loads appear in the first couple of post on every thread. I mean how simple is that.
Click to expand...
Click to collapse
Yeah that is too true.
Why are u promoting youre opinions to us? I have tried almost all of those, and found out that the best one for me is mdeejays froyo revolution 1.5!
This is your top 7. Good for you, but everyone should try mdeejay builds, and you dont even mention him.
Rom opinions are subjective!
Sent from my HTC HD2 using XDA App
dashrink said:
Why are u promoting youre opinions to us? I have tried almost all of those, and found out that the best one for me is mdeejays froyo revolution 1.5!
This is your top 7. Good for you, but everyone should try mdeejay builds, and you dont even mention him.
Rom opinions are subjective!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
You totally got the wrong point. My aim in this thread is not to promote the builds
Quoted herein, but I quoted them as a means of getting my message across, so
Anyone testing Android builds should be using recommended winmo Roms and radio.
The builders of these all recommends a particular custom winmo Rom, so to miniimize
Incidence of problems along the way. BTW am a big fan of mdeejay, now am
Using Clean 2.3 sense.
"subjective" you're telling me ay!
I get your point. And it is a good one. The environment of the cooks is the best way to duplicate their smooth running builds.
Ha, looks like this thread went over a LOT of heads. Of course I do see that many don't read the first post on the Builds once they find the download link.
J
JonSolo said:
I get your point. And it is a good one. The environment of the cooks is the best way to duplicate their smooth running builds.
Ha, looks like this thread went over a LOT of heads. Of course I do see that many don't read the first post on the Builds once they find the download link.
J
Click to expand...
Click to collapse
Quite right!
You got my point right on.
jigners said:
You totally got the wrong point. My aim in this thread is not to promote the builds
Quoted herein, but I quoted them as a means of getting my message across, so
Anyone testing Android builds should be using recommended winmo Roms and radio.
The builders of these all recommends a particular custom winmo Rom, so to miniimize
Incidence of problems along the way. BTW am a big fan of mdeejay, now am
Using Clean 2.3 sense.
"subjective" you're telling me ay!
Click to expand...
Click to collapse
Wel according to bodybuilder27's post i aint the only one that 'misunderstood' the point.
Sent from my HTC HD2 using XDA App
dashrink said:
Wel according to bodybuilder27's post i aint the only one that 'misunderstood' the point.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
a very common problem in forums is misunderstanding and a major contributing
factor to this is people failing to read the whole thread or post.
It seems as if a lot of the reason people are hesitant to switch to froyo is the lack of custom kernels. custom kernels provide much better battery life as well as the ability to overclock as well as many other very useful features that create faster and more efficient operating system functions. From personal experience with froyo roms i have noticed the system to be quite slow compared to 2.1 and also i have noticed absolutely horrid battery life. We all know that these leaks may be far from complete but thats not to say that we shouldnt be making them better. It is obvious that Firon and noobnl have the correct information on this matter seeing as they have rooted all of the froyo releases inside of the zImage. If they were kind enough to share the information they have it would be very easy to either port our drivers to a i9000 froyo source or to use backported eclair libraries and use our current kernels. With this being said, I am very sure that this information could be the dealbreaker for froyo roms. With a good kernel comes a good functioning phone.
TO FIRON OR NOOBNL:
Please share your method of extracting the initramfs in order to quickly advance the development of froyo roms and to prolong the necessity for an updated source code
https://github.com/atinm/initramfs-utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
bubby323 said:
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
Click to expand...
Click to collapse
THANKS A lot man
You have tested this on froyo kernels? And technically if we used a correct froyo initramfs combined with a 2.6.29 kernel with backported eclair libraries for certain hard/software aspects we should be able to acheive an eclair kernel on a froyo rom. Ive done it before on other phones
the jump from .29 to .32 is a massive one, but all the power to ya...
shabbypenguin said:
the jump from .29 to .32 is a massive one, but all the power to ya...
Click to expand...
Click to collapse
Ive done it on evos/nexus' and i can confirm that its been done on galaxy s phones. it may be a massive jump in version number and overall base code. but as far as android and our devices go it really hasnt changed too much. actually i can almost guarantee that it will boot just by swapping the kernel inside the zimage. but to get camera and other functions requiring updated drivers we would need older libraries. or we can just patch our board specific files onto a i9000 kernel. but hey. doubting is more fun than doing
bubby323 said:
https://github.com/atinm/initramfs- utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
Click to expand...
Click to collapse
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
help
EnVolved said:
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
Click to expand...
Click to collapse
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
If you want better battery life editing the initram isn't going to do it.Your gonna need kernel source to play with to be able to do anything about battery life.
justlovejoy said:
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
Click to expand...
Click to collapse
There should be only one way to use that script to extract.
./extract_initramfs.sh zImage
and here's the header from the repack script.
usage : ./repack.sh [kernel] [initramfs_direcotry] [kernel source dir] "title of build"
example : ./repack.sh /data/android/initramfs-utils/zImage /data/android/captivate-initramfs /data/android/linux-2.6.32 "title of build"
These are fairly simple shell scripts that only appear complicated because of the use of grep.
I do not have a PC Reader, so I can not install Kernal 8.5.1, is there build with at least 8.5 built into it? Every build I have tried so far, drains the battery really fast, even when I just text all day. I heard that the build's with sense drain the battery, but I can not find a Froyo build without Sense UI, can anyone help? I wish I could install this Kernel without having a PC Reader
use your usb cable
That is not very specific. I have Hastarin Kernel 8.5.1 on my Desktop right now, but how do I install that kernel onto my phone, also are there any builds with 8.5.1 already built in? Please give step by step instructions, I have my phone plugged in via usb, but I do not know how to go about installing the Kernel.....
Don't you think you should be asking this question in the thread were you got the kernel from? Instead if opening up a new one.
mattfmartin said:
Don't you think you should be asking this question in the thread were you got the kernel from? Instead if opening up a new one.
Click to expand...
Click to collapse
Give him a break, it's the Q&A section after all.
@TS: boot into WinMo, and just transfer the kernel files to your SD card with the usb cable. More info on which files should be moved where, check the first post of hastarin's thread.
Thank you Stephan. I found a Build desire HD2, by Cedesmith, it seems the build already has Kernel 8.5.1 built in it, I could be wrong, please verify that, because I would install that build and just be fine with it.
Gv2004 said:
Thank you Stephan. I found a Build desire HD2, by Cedesmith, it seems the build already has Kernel 8.5.1 built in it, I could be wrong, please verify that, because I would install that build and just be fine with it.
Click to expand...
Click to collapse
Just read whats in cedesmith's thread, I'm really not gonna check that for you. Most people here are glad to assist but you're gonna have to learn to figure some things out for yourself.
StephanV said:
Just read whats in cedesmith's thread, I'm really not gonna check that for you. Most people here are glad to assist but you're gonna have to learn to figure some things out for yourself.
Click to expand...
Click to collapse
Does flashing a Custom Rom such as Energy, help runt the phone faster, and would it help the battery life while running Android?
Gv2004 said:
Does flashing a Custom Rom such as Energy, help runt the phone faster, and would it help the battery life while running Android?
Click to expand...
Click to collapse
Yes it does.
Hi, as the topic states, does anyone know where i can download one and flash? my setup on my sig is current.
thanks
So you're trying to run the official kernel with a custom ROM? Why?
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
nomadman said:
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
Click to expand...
Click to collapse
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link. - http://www.filedropper.com/update3-e3671133717dsigned-opal-frg83-from-dmd64e3671133
Phateless said:
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link to my dropbox. - http://db.tt/XHrvInZ
Click to expand...
Click to collapse
IMO, the current ROm im using (TheOfficial) is working wonderfully. I care less about overclocking since I don't play games and dont find the need for the applications I use to be overclocked. Also the UI response on the ROM is incredible.
You are right, until the other ROMs iron out the random battery drain, which I have experiences in both CM7 and pershoot kernels, i wont be using them because i do not like having to restart the phone every time after i charge. ezterry's current kernel always gives me the green screen. however, ez's older kernel doesn't, but I prefer running the latest unmodified kernel.
I'm satisfied using a non-oc kernel and would rather set the mim clock freq. to ~177.
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Phateless said:
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Click to expand...
Click to collapse
lol, thats my problem. I don't. I also have athe official OTA Froyo image for mt3g. but i have no idea how to extract and apply it to the current OS. Thanks for the offer though. i'll try to find a way to do it. was just hoping someone had a flashable official kernel laying around they'de like to share.
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
nomadman said:
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
Click to expand...
Click to collapse
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Phateless said:
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Click to expand...
Click to collapse
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
nomadman said:
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
Click to expand...
Click to collapse
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Shouldn't been since the kernel code is open source, but I'm not sure either. I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Phateless said:
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Click to expand...
Click to collapse
The kernel is open source. I dont think i have a problem there. Its gapps that we can not redistribute. i read that from CM forum.
DonJuan692006 said:
...I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Click to expand...
Click to collapse
thanks! if u can find the link again, i'd be grateful. im on a unix (Mac) environment, so i might be able to do it. if not on Mac, I already have vmware fusion installed and its not a problem slapping on the latest Ubuntu.
I did find a how-to on CM wiki that required a boot.img and fastboot to flash. also found one requiring zimage from a rom. but i could not find the zimage file from the TMO Froyo OTA. lol.
Here's what I was reading. Which is doing the boot.img method.
DonJuan692006 said:
Here's what I was reading. Which is doing the boot.img method.
Click to expand...
Click to collapse
nice! androidcentral was down for maintenance the whole time i was researching yesterday. thanks for the link!
nomadman said:
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
Click to expand...
Click to collapse
Glad I happened to go back a page...
The official kernel is meant to go with 0013 and 28.25 so yes, you should still have the additional RAM, which this phone desperately needs.
2.6.32.9-g94b855e
[email protected]#1 is what my phone says and I just received the OTA update a few days ago. Hope this is what you were looking for!
I've been trying to figure this out all day. I actually have a linux installation already but none of the download links for the perl files work. If you have them please upload them somewhere and I'll make us a flashable AnyKernel update.zip.
I've been trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=667923 but none of the android-dls.com links work