Related
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.
Please, can somebody provide compiled kernel modules for kernel 2.6.32.9-00001-g41bc3e0 or compatible? Specifically cifs.ko, slow-work.ko, fuse.ko
Thanks a lot.
If you just want cifs, you can use a kernel by faux123, all of them have built in cifs support.
I'm kinda in the same situation, i don't want faux's o/c, so im in the process of getting sources to compile my own without any cpu o/c. but i like the cifs support, and the slqb/bfq optimization
Girgizzlemuf said:
I'm kinda in the same situation, i don't want faux's o/c, so im in the process of getting sources to compile my own without any cpu o/c. but i like the cifs support, and the slqb/bfq optimization
Click to expand...
Click to collapse
My source is available via GitHub, you can download it any any time and compile yourself without oc. Just don't enable fakeshmoo option
Sent from my LG-P999 using Tapatalk
turl1 said:
If you just want cifs, you can use a kernel by faux123, all of them have built in cifs support.
Click to expand...
Click to collapse
Well, this is exactly, what I was trying to avoid. I would really prefer downloadable kernel modules.
And yes, I can compile them from the source, I just hoped, that somebody already did that and can share.
Thanks anyway.
Android 2.3 is based on Linux 2.6.35, but Arc is using 2.6.32. Any background story we know? Discuss.
hi
just to correct : this is not linux, only the kerner version .
tiborprogmed said:
hi
just to correct : this is not linux, only the kerner version .
Click to expand...
Click to collapse
Well, it's not just linux's Kernel. Android changed a lot the linux kernel and that's why we aren't using the new 3.1 kernel (that's a shame :S).
I don't know why SE is using an outdating kernel but they may have build their drivers with the X10 kernel (or something like this)?
I don't really see the significance of this, there is very little performance related going on in the Linux kernel. Userspace is where it's at now..
why wont my cm10.1 rom boot i compiled it with ubuntu 10.04 and features linaro 4.7.3 krait and bionic tweaks
edit: is there a way i can logcat
extremetempz said:
why wont my cm10.1 rom boot i compiled it with ubuntu 10.04 and features linaro 4.7.3 krait and bionic tweaks
edit: is there a way i can logcat
Click to expand...
Click to collapse
Does the default CM10.1 work? I would check to make sure first the default CM10.1 works, then I would check it the addons are compatible. The question for me is why the Bionic tweaks. I am inclined to say it's not going to work. Also, you could flash some of these addons after installing CM 10.1. Finally, check to see if there is a compiling error.
Hello all, and befor all, sory for my poor english.
I just want to ask you for some help. I was trying to build my oun kernel for the nexus 7 (ba dum tsss) and want some information about this, since I never compile anithing for android.
I have knowledge about programming, and if I fin something I don't know, learn about it and try, like everyone I assume
I have readed a lot of guides here and there, but I can't find anything specific about how to create a custom kernel, mod voltages, frequencys, and the most important, create a recovery flashable zip.
So, if somebody can point me with some instructions on how to do it, I will be very thankful.
Thx for the help and have a nice day
Download the source and a toolchain in a Linux distro. Unpack the source, and navigate to the folder in Terminal. Type this:
Code:
export ARCH=arm
export CROSS_COMPILE=/path/to/toolchain/bin/arm-xxx-xxx (figure this part on your own)
Edit your defconfig from arch/arm/configs. Then type in
Code:
make xxx_defconfig (where xxx is the name of your defconfig)
make -j# (where # is the number of cores + 1)
This will take some time. Patiently fight out errors, and I'd recommend you start with a vanilla build.
After it's done, grab the zImage from arch/arm/boot/. Grab a flashable kernel that does not use boot.img. Delete the zImage from there and rpaste in your zImage. It should be flashable now.
Let me know if you need more help.
Thx for the info, I have some questions
How or where can I download the kernel source? (Yeah, I want to work with the google vainilla one for the stock rom)
Do you recomend the linaro toolchain or the google original one?
Sory, I work with eclipse and svn repos for years, never work with other programs or source code sistems xD
Sent from my Nexus 7 using xda app-developers app
http://source.android.com/source/building-kernels.html
This link's got much more details. Plus if it supports Linaro, go with Linaro toolchain.
Im stuck in the defconfig making part, how can i know the name of my defconfig file?
Sent from my Nexus 7 using xda app-developers app
If I rember correctly to build the kernel its
make grouper defconfig
But its been a few months since I've touched my source codes
But the defconfig is just the codename of the device your building for (aka WiFi nexus 7 is grouper gsm is tilapia)
Sent from my Nexus 7 @1.60 GHz on Stock 4.2.2
Ok, when I try to run the make grouper command, it say defconfig not found or something like that (sory, I am not om the dev ,achine right now xD).
Apart, any help about adding frequency to cpu steeps and gpu steeps (oc support for 1,7 single core, 1.6 quad and 520 gpu with 1.7 default frequency).
Yeah, I know, it's a lot of information, but I never touch linux kernel on the past, and don't know anything about it some directory info will be great xD
Sent from my Nexus 7 using xda app-developers app
All of it is found in the /arch/arm/mach-msm directory. Some files are linked so you'll have to update both. And for the defconfig, navigate to the /arch/arm/configs directory (not in Terminal) and note down the name of the defconfig you want to use. It varies with different kernel sources.
THX for all, I viewthe faux123 kernel source for reference, and found the files I need to edit to allow cpu and gpu oc, and the defconfig for nexus 7 are the tegra3_android_defconfig, strange name jaja
I am installing ubuntu x64 12.04 LTS because of compatibility things over 13.04 Thx for all the info and all the help guys
Sent from my Nexus 7 using xda app-developers app
Actually for faux kernel it's better to use faux_grouper_defconfig if you want your kernel to have features that faux-kernel has.