I'm running the latest Stock Gingerbread ROM, is there a way to add CIFS support? I get the impression from what I've read that I may have to go back to Froyo if I want CIFS support because the only kernels I see that support CIFS are Froyo kernels. Am I getting that right or is there a way to add it to my kernel?
Thanks,
DrD
Yes, you will have to wait until HTC releases their Gingerbread kernel source before any custom kernels can be made.
Go bug them on facebook, twitter, e-mail, etc.
I'm not trying to rush any projects, just a bump of this thread because it appears the kernel has been open sourced (finally!). That and the fact I do not know anything about cooking kernels so I am at the whim of the devs.. haha
Can't wait to try mounting my home NAS to my phone!
Related
About to flash CM7. Seen some mention of 'kernal' in various threads. What does it do? and do I need to update it?
Cheers.
same question
The Kernel controls things like battery drain and CPU levels for overclocking etc... its not a must do but recommended for best performance. there is probably not a "best" one but more like the best that suits you. If you are running CM7 i would recomend Vork Kernel's or ManU kernels
Richardtrip's kernels are also very good: overcklocking, manual voltage level, Two-way call recording.
plohoi said:
Richardtrip's kernels are also very good: overcklocking, manual voltage level, Two-way call recording.
Click to expand...
Click to collapse
Have you used the call recording? If so how do you "activate" it or listen to the calls afterwards?
CdTDroiD said:
Have you used the call recording?
Click to expand...
Click to collapse
Yes call recording is working fine.
CdTDroiD said:
If so how do you "activate" it or listen to the calls afterwards?
Click to expand...
Click to collapse
There are several apps in http://forum.xda-developers.com/showthread.php?t=993793 thread, I used app by skvalex.
Since I'm new to Desire and HTC- what is the difference between Sense and AOSP kernels?
(before you ask- I know what AOSP is)
Do Sense firmwares require some extra drivers/modules/settings in kernel?
gen_scheisskopf said:
Since I'm new to Desire and HTC- what is the difference between Sense and AOSP kernels?
(before you ask- I know what AOSP is)
Do Sense firmwares require some extra drivers/modules/settings in kernel?
Click to expand...
Click to collapse
Hi there!
Sense is HTC proprietary software built over the top of Android. This code is not open source and is what HTC use to set themselves apart from other manufacturers like Samsung etc. Sense is what they sell as their user experience.
AOSP stands for Android Open Source Project. Since Android is an open source operating system, Google publish all the code and necessary tools to develop Android. Companies like HTC get the code and then write Sense over the top. Devs in this community like Cyanogen take the AOSP code and build their ROMS from scratch.
When you see ROMS that are for Sense 2.1 on Gingerbread for example this means that someone has been able to port software running on other phone models like the Desire HD or Incredible etc to your phone model (Desire)
As for the kernels you will need to make sure that the kernel you run is supported on the device and that's about it. The Kernel has to have some key components or the phone won't work so the ROM you use just uses them.
Having said that, ROM developers usually optimise around one or two particular Kernels. They are usually included in the ROM or the Dev will tell you which one they recommend for certain purposes.
You do have to have apps in the system that can access settings if customising the performance beyond what the dev has already done is what you want to do.
Thanks for the answer but it's not exactly what I'd like to know
Thing is- what makes Sense kernel incompatible with AOSP firmware (and vice versa)
Sorry for not answering what you were looking for. I'll try again.
The Kernels for Sense would have specific code that enables features in the phone that HTC build. LED control, light sensor etc. I assume Sense is quite strict about what it will work on and what it won't.
The AOSP Kernels are built without knowing the exact hardware maps of the internal components and as such won't work with Sense because they simply don't know how due to HTC keeping a lid on all source work for Sense and the handset itself.
The best developers can figure most of it out (certainly I am not a dev, just a geek ) and teams like CyanogenMod have it mostly discovered and configurable.
Is that more helpful?
Isn't Sense a HTC's android framework "mod"? I mean does it "just" provide more/different functionality than AOSP?
AFAIK all kernels must be built knowing exact hardware map, otherwise some devices will not work or kernel will not boot. The only autodetect I'm aware of is display panel type and filesystems (I did mess with kernels @samdroid.net)
i have a question about kernels an such from what i understand is you don't need to update the kernel but its a good idea too do so. couple questions i have.
1. how do you know what kernel you have installed currently.
2. How do you flash or get a new one installed if you need or want it.
3. scene i am using core droid 6.3 gb2.3.3 what kernel would be the most compatible or effective?
I have had my inspire phone for 3 months an finally rooted it 3weeks ago sence then i have used the rom manager too play with different roms an make backups of the 2 i have found i like the most. After reading i have seen it stated too get the most out of these roms though you should install a different kernel.
To know your currently version, you have to go in parametres and then logiciel version and look at build. Sorry for my bad English.
Sent from my HTC Desire using XDA Premium App
I don't want open a new thread, so I will ask here.
Now I have
kernel
2.6.32.15-gf5a401c
baseband
32.49.00.32U_5.11.05.27
Click to expand...
Click to collapse
on stock pre rooted 2.2 Froyo.
I want put this ROM. Can I put this ROM with my kernel and radio or I musst put latest kernel and radio?
GTRSkyR34 said:
I don't want open a new thread, so I will ask here.
Now I have
on stock pre rooted 2.2 Froyo.
I want put this ROM. Can I put this ROM with my kernel and radio or I musst put latest kernel and radio?
Click to expand...
Click to collapse
You will find that many roms contain a kernel in the zip file, so it will often change when you flash a rom. If not, the developer may recommend one.
Radio is independent of rom flash, and unless you start getting connectivity problems there is normally no need to change it. Again, some developers will recommend a radio (and maybe a RIL if they know a particular combination works well with their rom.
There are quite a few ROMs available, but one thing is not entirely clear to me. Why aren't there any clean AOSP ROMs for the Wildfire? I can understand it would be difficult to develop newer Android versions like Gingerbread that were never officially released for the Wildfire, but wouldn't it be relativly easy to compile a working ROM from the 2.2/2.2.1 source code? Or am I completely missing the point here?
It seems to me all the materials are available to pull this off without too much effort, right? The Kernel source is available from HTC and the Froyo source from our friends at Google.
From what I understand there are also some vendor specific issues that need to be solved, but the Cyanogen developers apparently have this solved already.
That pretty much covers everything right?
So my question would be, is it possible to easily build a clean version of Froyo for the Wildfire by doing the following:
1. Grab the kernel source from HTC and compile it (or just fuse a pre-compiled one seeing as there are quite a few available).
2. Compile the Android 2.2/2.2.1 source
3. Apply vendor specific fixes (assuming they don't have to be incorperated in the code directly).
4. Flash kernel + ROM, thereafter Gapps
5. win?
Basically something like Openfire without bugs. Which reminds me, wouldn't the video recording/SIM card issues be fixed with the official HTC kernel? In which case, I see little reason to try and compile the stuff by myself.
Ah well, I really really hope someone can enlighten me on this subject.
TL;DR: I want to create a basic a clean AOSP Froyo 2.2/2.2.1 ROM which should be easy right because we already have the required materials (proper HTC kernel -- or third party one, 2.2/2.2.1 source, cyanogen vendor fixes), so compile = good to go?
there are
- Wildmix http://forum.xda-developers.com/showthread.php?t=1155032
- CM6 http://forum.xda-developers.com/showthread.php?t=822132
- Utmost http://forum.xda-developers.com/showthread.php?t=862561
- Openfire - http://forum.xda-developers.com/showthread.php?t=783024
more here (scroll down) http://forum.xda-developers.com/showthread.php?t=1029318
There is always CM7
Remember you use these at your own risk
Thank you for your reply, but it doesn't really address my questions. I am aware of the custrom ROMs available, none of them really meet my demands.
Cyanogenmod is an excellent ROM, but CM6 has some issues and CM7 is based of Gingerbread.
Utmost and Wildmix are both based on Openfire. The problem with Openfire is that it has a lot of internal stuff I don't really like. Seeing as Utmost and Wildmix are based on it those don't really float my boat either.
My eventual goal would be to create a clean AOSP like this one:
http://forum.xda-developers.com/showthread.php?t=1162656
Unfortunately it's based on Gingerbread and not fully functional (yet!).
That is why I asked the questions that I asked. I'd rather do it myself from scratch, but in order to do any work I could really use an answer to my questions
Thanks anyways.
Trademark225 said:
Thank you for your reply, but it doesn't really address my questions. I am aware of the custrom ROMs available, none of them really meet my demands.
Cyanogenmod is an excellent ROM, but CM6 has some issues and CM7 is based of Gingerbread.
Utmost and Wildmix are both based on Openfire. The problem with Openfire is that it has a lot of internal stuff I don't really like. Seeing as Utmost and Wildmix are based on it those don't really float my boat either.
My eventual goal would be to create a clean AOSP like this one:
http://forum.xda-developers.com/showthread.php?t=1162656
Unfortunately it's based on Gingerbread and not fully functional (yet!).
That is why I asked the questions that I asked. I'd rather do it myself from scratch, but in order to do any work I could really use an answer to my questions
Thanks anyways.
Click to expand...
Click to collapse
Have news for you
We are currently working on a ROM with the aosp ROM you linked as base ...
Stay tuned
Sent from my HD2 using XDA Premium App
He meant a AOSP Froyo, no Gingerbread ;D
nejc121 said:
He meant a AOSP Froyo, no Gingerbread ;D
Click to expand...
Click to collapse
Got that after posting that
But gingerbread is much better than froyo and compatible to nearly all apps you can have
Sent from my HD2 using XDA Premium App
Anyway what's wrong with gingerbread??
I figured since 2.2.1 is the last available official version released it would be easier to get all hardware functioning properly. But if those new ginger AOSP projects fix the video recording bugs and get everything else fixed, ill gladly switch to it. Maybe ill use xdbg's (spelling?) ginger aosp as a base as soon ss the bugs are fixed.
Sent from my HTC Wildfire using XDA App
Does anyone know if there is a stock build of the cifs.ko module for the LTE Galaxy Nexus? I saw there is a 4.0.3 one posted, but that doesn't help with Verizon's since it is still on 4.0.2.
Try faux's kernel. Please post questions in Q & A also
Sent from my Gummy Nexus
My problem is I don't really want to move to another kernel as I want to maintain stock behavior. I simply want to be able to load the cifs.ko module for mounting network drives.
Same here. The only reason why I would explore a non-stock kernel build is for cifs.ko. I'm sure there are other features I'd enjoy, but I haven't ran across a need yet. So for now, I'm looking for a cifs.ko for Android 4.0.2 for LTE Galaxy Nexus.
I'm in the same boat - running rooted stock, haven't had success trying to compile my own kernel/modules in the past, hoping someone who has might have built a cifs.ko. AndSMB works fine for simple file access, but for streaming I need to be able to mount the share. Eventually may have to look at mature ROMs for this hardware, but rather not have to, when a simple insmod would give me everything I need.
+1
I second this request.
I had intended to look into what is involved w/ getting this to work (i.e. is there a reason no such module has been released other than the fact that those that would release have already moved to 4.0.3?) and attempting a build and release one myself. I have many, many projects on my todo-list, though, so this isn't likely to happen any time soon.
I wanted to ask if we can already enjoy Voodoo kernel on our Captivate Glide. I have read that Inception mod implements it "partially", although I cannot post there yet to ask what's meant by "partialy"... I just don't want to spam to reach 10 posts threshold.
Does Osimood implement the Voodoo kernel (partially, or all?)
Hope you can tell me
Cheers
Tony
AFAIK osimood uses the latest dman's kernel. so it has the same kernel functions as inception ROM.
Yup, I am suspecting that too. Maybe dman or CarpeNoctem can chime in at some point, and tell us which features of Voodoo are currently enabled. I take Voodoo improvements are already enabled by default when playing music with my app of choice... Right? Or should I install a separate apk? (like Voodoo sounds plus, from the market)
Cheers
Tony
Is it possible to get dman's kernel separate from either rom?
I would like that too. So people who'd like to keep close to the stock esthetics, could still enjoy dman's wonderful kernel without having to work on Inc3ption rom to undo some of his work.
i already asked that in the inception thread and dman said that you can use the kernel without the dependency of any rom.
Awesome. Where can the link to the kernel be found?
And if there's no link, is it possible to pull the kernel from one if the roms?
So any news as to separately impement the kernel? What further development is there to make?
Has anyone gotten CIFS to work on ICS? Or is that something
That requires kernel source?
Im going to guess this does require kernel source, as my Xoom supports CIFS and we have that source.
You can try to ask Aeroevan though.