[Kernel] Image + startup.txt for 384mb based on Cotulla's Source - HD2 Android Q&A, Help & Troubleshooting and Genera

Kernel version: 2.6.32.9 [email protected] #1
Base: Cotulla's Source Tree w/ latest drivers enhancements
Instruction:
- Delete zImage
- Unpack/replace my files in your sd
Please refer to this kernel as "michyprima's build" for not making people confused.
Ram Patch from Manus Freedom (http://git.linuxtogo.org/?p=groups/...it;h=65276d5b73d2de9e446cc379c76f03c7e4f8f914)
File up!
I'd appreciate a thanks
EDIT: This is an experimental build. Something maybe will not work for you, or worse this kernel will not be stable on your device. For daily use use a kernel from cotulla's tree

michyprima said:
Kernel version: 2.6.32.9 [email protected] #1
Base: Cotulla's Source Tree w/ latest drivers enhancements
Instruction:
- Delete zImage
- Unpack/replace my files in your sd
Please refer to this kernel as "michyprima's build" for not making people confused.
File up!
I'd appreciate a thanks
Click to expand...
Click to collapse
nevermind ;D

Great, but you forgot to add the modules. I'm not able to enable Wifi.

michyprima said:
Kernel version: 2.6.32.9 [email protected] #1
Base: Cotulla's Source Tree w/ latest drivers enhancements
Instruction:
- Delete zImage
- Unpack/replace my files in your sd
Please refer to this kernel as "michyprima's build" for not making people confused.
File up!
I'd appreciate a thanks
Click to expand...
Click to collapse
wifi is working?

Well, compiled it myself.
It belongs into: /system/lib/modules
Thanks for your kernel. The 384mb patch from manusfreedom works great!

is 384mb max right now? or is there a way to bump it further to 512mb using the same method to bump it to 384mb?

is this only for ubuntu.or i can us for android,too.

ElBartoME said:
Well, compiled it myself.
It belongs into: /system/lib/modules
Thanks for your kernel. The 384mb patch from manusfreedom works great!
Click to expand...
Click to collapse
Thanks for remembering me to give credit...
Wrote the post too fast

ElBartoME said:
Well, compiled it myself.
It belongs into: /system/lib/modules
Thanks for your kernel. The 384mb patch from manusfreedom works great!
Click to expand...
Click to collapse
Great work Michiprama.
By the way how to push this ko file to /system/libs/modules?
If you can tell me a way using the Terminal emulator in the device it would be great.
Thanks

arifqur said:
Great work Michiprama.
By the way how to push this ko file to /system/libs/modules?
If you can tell me a way using the Terminal emulator in the device it would be great.
Thanks
Click to expand...
Click to collapse
Isn't it better to change the file directly in android file system?
On Debian distribution...
Code:
sudo su
mount system.ext2 /MountPoint1 -o loop
rm /MountPoint1/lib/modules/bcm4329.ko
cp bcm4329.ko /MountPoint1/lib/modules
umount /MountPoint1
exit
Otherwise if you have write access directly on the phone you can do the same here.

thx Micy for Kernel
an thx ElBartoME for fix
adb shell mount -o remount,rw /system
adb push "your Path" /system/lib/modules/bcm4329.ko
edit
anyway had sleep of death!! always! for me at least

michyprima said:
Isn't it better to change the file directly in android file system?
On Debian distribution...
Code:
sudo su
mount system.ext2 /MountPoint1 -o loop
rm /MountPoint1/lib/modules/bcm4329.ko
cp bcm4329.ko /MountPoint1/lib/modules
umount /MountPoint1
exit
Otherwise if you have write access directly on the phone you can do the same here.
Click to expand...
Click to collapse
Thanks man

I keep getting errors trying to unpack the .rar file in various ways. Anyone else? Is it corrupted?

michyprima said:
Isn't it better to change the file directly in android file system?
On Debian distribution...
Code:
sudo su
mount system.ext2 /MountPoint1 -o loop
rm /MountPoint1/lib/modules/bcm4329.ko
cp bcm4329.ko /MountPoint1/lib/modules
umount /MountPoint1
exit
Otherwise if you have write access directly on the phone you can do the same here.
Click to expand...
Click to collapse
Can you tell me how to do this for shubCRAFT's build? =)
I got the ram working but I can't overwrite the bcm4329.ko file in module.

3G aint working, wont connect but says connected

RaiderX303 said:
3G aint working, wont connect but says connected
Click to expand...
Click to collapse
Yes, can confirm, no mobile connection possible
Wlan was working fine with the fix, also no SOD within first hour.

tried it, the ram worked but the Wifi didn't work and it gave me SOD
using TMOUS

Downy said:
Yes, can confirm, no mobile connection possible
Wlan was working fine with the fix, also no SOD within first hour.
Click to expand...
Click to collapse
Yes, i confirm this too: Wlan is working with the patch, but mobile connection doesn't works.
Sent from my HTC Desire using XDA App

Well our leo is not ready for more ram right now
Adding on first post an "experimental" warning...

michyprima said:
Well our leo is not ready for more ram right now
Adding on first post an "experimental" warning...
Click to expand...
Click to collapse
unfortunately yes......

Related

VPN over android on HD2 ?

I wonder if there is anyone that tried to use any type of VPN over recent android builds for HD2?
Actually the problem resides in a missing kernel module "tun.ko".
I have tried to get the file from the internet to the same kernel and load it using "modprobe tun" or "insmod tun.ko" command but it is always giving me the same error: "modprobe: 'tun.ko' : invalid module format.
If anyone has a working module, that will be great.
hhhawasly said:
I wonder if there is anyone that tried to use any type of VPN over recent android builds for HD2?
Actually the problem resides in a missing kernel module "tun.ko".
I have tried to get the file from the internet to the same kernel and load it using "modprobe tun" or "insmod tun.ko" command but it is always giving me the same error: "modprobe: 'tun.ko' : invalid module format.
If anyone has a working module, that will be great.
Click to expand...
Click to collapse
I will update the kernel to include tunneling
EDIT:
http://git.linuxtogo.org/?p=groups/...it;h=17b1cb194c76267cae097241aea7a9f47ced7283
done.
tun.ko is present in all module autobuilds from today on.
check http://forum.xda-developers.com/showthread.php?t=719646#2 for the official GIT autobuilds
please let me know if it works for you
thanks
dcordes said:
I will update the kernel to include tunneling
EDIT:
http://git.linuxtogo.org/?p=groups/...it;h=17b1cb194c76267cae097241aea7a9f47ced7283
done.
tun.ko is present in all module autobuilds from today on.
check http://forum.xda-developers.com/showthread.php?t=719646#2 for the official GIT autobuilds
please let me know if it works for you
thanks
Click to expand...
Click to collapse
Thank you very much, with this module it should then be possible to have openvpn functionality.
Update: Ok, I am now using latest kernel with tun support.
With this kernel I am able to load the module tun.ko with insmod.
There are no errors and lsmod shows me the module as active.
Where to put an entry to load this module by default on boot?
I have tried the latest kernel build, on SHUBCRAFT CM6 froyo build, the module is loaded successfully and the device /dev/tun is also created successfully.
Thanks a lot.
Anyway I couldn't try the VPN functionality since the Wireless/3G didn't work after kernel upgrade! although I have successfully loaded the wireless modules.
--------
BTW, it didn't work with mattc Leo android build.
After some time of trying my openvpn is running very well with the new kernel and tun module. Thanks once again.
Downy said:
After some time of trying my openvpn is running very well with the new kernel and tun module. Thanks once again.
Click to expand...
Click to collapse
What Andriod build are you using?
Can you please tell us how did you manage to run the WIFI on the new kernel?
hhhawasly said:
What Andriod build are you using?
Can you please tell us how did you manage to run the WIFI on the new kernel?
Click to expand...
Click to collapse
try 1.3. VPN is enabled - not tested.
hhhawasly said:
What Andriod build are you using?
Can you please tell us how did you manage to run the WIFI on the new kernel?
Click to expand...
Click to collapse
I am running mattec release version 1.5 with the most current kernel (zImage) and the most current modules bcm4329.ko and tun.ko extracted from http://oe.netripper.com/files/htcleo_autobuild/modules-htcleo-latest.tgz.
For wifi it is very important to always use the correct bcm4329.ko according to your currently used zImage file.
So when I update a new kernel I also always download the newest modules and extract bcm4329.ko.
To get wifi working, I have extracted the bcm4329.ko out of the modules-htcleo-latest.tgz file and then used adb (I am using ADB Magic GUI to make things easier) to push the file to /system/lib/modules. Changed permissions at the end.
So
step 1:
I boot to wimo and replace zImage in my android folder.
step 2: boot back to android and connect via adb
step 3: extract bcm4329.ko out of modules-htcleo-latest.tgz
step 4: using adb I push this bcm4329.ko file to /system/lib/modules (command: adb push bcm4329.ko /system/lib/modules)
step 5: last but not least I change permissions, but dunno know if its really neccessary. (command: adb shell chmod 777 /system/lib/modules/bcm4329.ko)
Thats it. And thats what I am always doing when I am using a new zImage.
If you have further questions, just ask!
Currently I am running the latest kernel from today, 08/13/10 without any wifi or openvpn problems.
Unfortunatly the kernel module "tun" was not included with the 1.3!
Anyway I have managed now to run the new kernel and the tun module with 1.3.
And OpenVPN and wireless are now working fine.
hhhawasly said:
Unfortunatly the kernel module "tun" was not included with the 1.3!
Anyway I have managed now to run the new kernel and the tun module with 1.3.
And OpenVPN and wireless are now working fine.
Click to expand...
Click to collapse
vpn module is in first post
shu8i said:
vpn module is in first post
Click to expand...
Click to collapse
Oooops
I need a glasses for my eyes
I have tried the ROM and the module and everything was running smoothly.
Thank you all very much
Sorry To Bump This Post Up
But I AM NOt Able To Connect To Vpn PPTp On Any ANdroid Cyanogen Mod
What Should I DO Is There Update Or Solution Or ANything Around ?

[SOLVED] CIFS support

A noob question support. Is there a CIFS support in the 2.6.32.21-gbe90714 kernel or a suitalbe cifs.ko file that one could use with the Cifsmanager app?
I am a bit lost here. I downloaded the DHD kernel source released, but had no luck locating the cifs.ko file. And I have no idea how to compile one myself. Can someone pinpoint me in the right direction?
update:
found some instructions here http://forum.xda-developers.com/showthread.php?t=783117 so I will see if I can get it working
update 2:
i have been able to build cifs.o (no cifs.ko was produced ) from the kernel provided by HTC, but it fails with insmod. The problem might be (besides that I have only a vague idea what am I doing) that the downloaded kernel is 2.6.32-g5ed1769 and my phone is running kernel 2.6.32-gbe90714.
Also compiling the kernel ends with this error
make[3]: *** No rule to make target `drivers/input/touchscreen/ntrig.o', needed by `drivers/input/touchscreen/built-in.o'. Stop.
Thats where I got stuck.
I have attached the file cifs.o produced.
Updare 3: Solved - see attachment in post http://forum.xda-developers.com/showthread.php?p=8865419#post8865419
Support/Troubleshooting forum sub section is needed, this Desire HD general is becoming a Desire HD trashcan..
M_T_M said:
Moved to general. Not a DEV thread.
Cheers,
Click to expand...
Click to collapse
I placed in DEV since it deals with kernel compilation. Maybe it should be moved to theme and apps as I am trying to get Cifsmanager app working on DHD.
Small update: I have managed to get a cifs.ko from kernel 2.6.32.17 from G2 partially working. I have HEX edited the file and changed to my kernel version.
I can insmod the file and mount drive without a problem. I can than access the mounted drives a browse the folders, but when I try to open the file I get an error.
I do not seem to be able to find a 2.6.32.21 kernel compiled cifs.ko which I believe might work with HEX updating "-gbe90714".
*push*
looking for the right cifs.ko as well :\ would be really nice to be able to mount cifs shares without custom rom...
anyone got CIFS working on stock ROM?
CIFS working on 2.6.32.21-gf3f553d
here is a working cifs.ko for DHD kernel 2.6.32.21-gf3f553d
Code:
su
insmod slow-work.ko
insmod cifs.ko
insmod nls_utf8.ko
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Works fine on my DHD (samba access and video playback with V Player).
nxtwrld said:
here is a working cifs.ko for DHD kernel 2.6.32.21-gf3f553d
Code:
su
insmod slow-work.ko
insmod cifs.ko
insmod nls_utf8.ko
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Works fine on my DHD (samba access and video playback with V Player).
Click to expand...
Click to collapse
Thanks for this, it works fine when I insmodded all the .ko's you zipped (that I placed in system/lib/modules/). On reboot though I cannot use cifs manager unless I insmod again. Do I need to insmod everytime i reboot?
Sent from my Desire HD
nxtwrld said:
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Click to expand...
Click to collapse
I understand the hex edit - would you mind telling me how you did the --strip-debug - I'd like to do the same.
They were compiled on a headless PII 400 MHz running Ubuntu Edgy Eft server.
-Mike-
You just need to have the android ndk, which I supposed you have since you have bee able to compile the kernel. So just run
Code:
/path/to/android-ndk-r4b/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-strip --strip-debug /path/to/cifs.ko
you have to modify the path to cifs.ko a and android-ndk-r4b
I have bee trying to compile the kernel my self on kubuntu, but always finished with an error, so I just ended up hexediting other files.
Thanks for your files. I have been waiting for a working samba mount to stream my videos from NAS!!
keemyb said:
Thanks for this, it works fine when I insmodded all the .ko's you zipped (that I placed in system/lib/modules/). On reboot though I cannot use cifs manager unless I insmod again. Do I need to insmod everytime i reboot?
Sent from my Desire HD
Click to expand...
Click to collapse
I am afraid it has to be insmoded every time on boot. You can automate it with Gscript or Tasker apps.
Thanks @Nxtwrld for the strip-debug advice. The HTC kernel never compiled with my phone's config.gz - after each failed compile I would have to edit .config and disable the item responsible for the build failure. I ended up compiling the module by itself.
Sent from my Desire HD using XDA App
Final compile - optimised versions against NDK R5.
Against the new Android NDK R5 I have just compiled:
* tun.ko - 18 KB
* slow-work.ko - 16 KB
* cifs.ko - 269 KB
* nls_utf8.ko - 4 KB
I have also debug stripped them - resulting in a total module size of 304 KB instead of 3.2 MB.
This time I compiled them on Ubuntu 10.10 instead of the ancient Ubuntu 6.10 I had been compiling on.
Again, these are for 2.6.32.21-g66cfb7a - feel free to hex edit them. I have tested both tun & cifs and they work.
Thanks again nxtwrld for the strip-debug advice.
Can you do the same for kernel 2.6.32.21-g3d0aaf ?
here you go.
thank you! Works very good!
nxtwrld said:
here you go.
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App
I've tried for hours so far to understand more about the android and how to install the files inside 2.6.32.21-gf3f553d.zip.
I have the Desire HD with stock Orange rom and that kernel, i literaly have no idea how to install thease moduals onto the phone.
My desire hd is rooted and is S-on I've tried things like Kernel Update Utility and also just trying to simply copy and paste the files into system/lib/modules didnt work since astro didnt let me paste.
If it wasnt nearly 1am and i wasn't trying for the past 3 hours i would have done more reading. I know its something simple im missing, just can't figure out what the process is to installing thease modules is. First Android phone, first day with it as you can probebly tell.
Any help will be apreciated.
Thanks
arielc said:
I've tried for hours so far to understand more about the android and how to install the files inside 2.6.32.21-gf3f553d.zip.
I have the Desire HD with stock Orange rom and that kernel, i literaly have no idea how to install thease moduals onto the phone.
My desire hd is rooted and is S-on I've tried things like Kernel Update Utility and also just trying to simply copy and paste the files into system/lib/modules didnt work since astro didnt let me paste.
Click to expand...
Click to collapse
There's a free app in the market called "mount /system (rw / ro)" that can make your /system read-write (rw) or read-only (ro). After setting rw - you should be able to copy the *.ko files into /system/lib/modules.
Another alternative is to copy the *.ko files onto your sdcard (/mnt/sdcard).
You can then use an app (i.e. "Terminal Emulator") to enter these commands:
Code:
su
insmod /mnt/sdcard/slow-work.ko
insmod /mnt/sdcard/cifs.ko
insmod /mnt/sdcard/nls_utf8.ko
Alternatively, you can open CifsManager, open the Settings and specify a custom path to your kernel modules (i.e. in /mnt/sdcard). The recent version allows you to specify multiple modules, separated by colons. e.g:
Code:
/mnt/sdcard/slow-work.ko:/mnt/sdcard/cifs.ko:/mnt/sdcard/nls_utf8.ko
Hope this helps.
You should also check you kernel version and verify, that you are really running pin this kernel. I have no idea what the kernel for Orange branding is....
Amazing thanks, i did it with the terminal emulator method. First time i tried it, it wouldnt work. A restart later and i've rentered the comands and my computer drive is mounted. Works like a dream, thanks loads for th hex edited files and the walkthrough with diffrent options was so very helpful.

[Q] Trying to recompile Hastarin for SuperRAM with CIFS: Issues

*EDIT*
Solved, new thread with download here: http://forum.xda-developers.com/showthread.php?t=887567
*/EDIT*
Hey everyone,
I'm trying to re-compile the Hastarin kernel for DarkStone1337's SuperRAM 1.5 to include CIFS support. I've compiled many a linux kernel, but never for Android, so can anyone point out what I'm doing wrong? Here are the commands I've run through:
Added android-ndk-r5/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin to PATH
git clone git://gitorious.org/~hastarin/linux-on-wince-htc/hastarins-linux_on_wince_htc.git
Grabbed DarkStone1337's patch from: http://pastebin.com/6qjkb4Hh
Renamed hastarins-linux_on_wince_htc to "a" to match the patch
patch -p0 < patch.txt (This did report a pre-mature ending on the patch, but everything appears to have patched OK)
make
The result:
arch/arm/mach-msm/built-in.o: In function `dex_cb_interrupt':
/files/Software/Android/hastarin/source/a/arch/arm/mach-msm/dex_comm.c:248: undefined reference to `notify_vbus_change_intr'
make: *** [.tmp_vmlinux1] Error 1
Click to expand...
Click to collapse
Any ideas?
Thanks,
B.
Hi!
Try using this toolchain instead! http://www.codesourcery.com/sgpp/lite/arm/portal/release1293
Then follow these commands to build the kernel:
make clean
make ARCH=arm htcleo_defconfig
Then change what is necessary to add the CIFS support
make ARCH=arm CROSS_COMPILE=/path-to-toolchain/bin/arm-none-linux-gnueabi- zImage
Taken from: http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel
Then follow the same guide I linked to, to create the modules.
Hey Darkstone i saw the thread for SuperRAM 1.5 has been closed requested by you. Was there a major reason? Are we not supposed to use it anymore or was it put on hold. just asking because Im still testing it out and its been rock solid after several reboots.
PENKO956 said:
Hey Darkstone i saw the thread for SuperRAM 1.5 has been closed requested by you. Was there a major reason? Are we not supposed to use it anymore or was it put on hold. just asking because Im still testing it out and its been rock solid after several reboots.
Click to expand...
Click to collapse
prob due to folks refusing to read and do a little research before posting common problem Roth common fixes...
DarkStone1337 said:
Hi!
Try using this toolchain instead! http://www.codesourcery.com/sgpp/lite/arm/portal/release1293
Then follow these commands to build the kernel:
make clean
make ARCH=arm htcleo_defconfig
Then change what is necessary to add the CIFS support
make ARCH=arm CROSS_COMPILE=/path-to-toolchain/bin/arm-none-linux-gnueabi- zImage
Taken from: http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel
Then follow the same guide I linked to, to create the modules.
Click to expand...
Click to collapse
First off, thanks a ton for responding, this was very helpful. Secondly, sorry for the threadjackers. Lastly, this both works, and doesn't. The following works fine:
# git clone git://gitorious.org/~hastarin/linux-on-wince-htc/hastarins-linux_on_wince_htc.git
# make CROSS_COMPILE=/files/Software/Android/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm clean
# make CROSS_COMPILE=/files/Software/Android/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm htcleo_defconfig
# make CROSS_COMPILE=/files/Software/Android/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm zImage -j 4
Click to expand...
Click to collapse
But when I try to make an exact copy of the kernel you created for SuperRAM 1.5 (without modifying for CIFS), it doesn't, so I must be doing something wrong. Here was my process there:
# git clone git://gitorious.org/~hastarin/linux-on-wince-htc/hastarins-linux_on_wince_htc.git
# mv hastarins-linux_on_wince_htc a
# cd a
# patch -p0 < patch
(Stripping trailing CRs from patch.)
patching file a/arch/arm/mach-msm/qdsp6_1550/q6audio.c
(Stripping trailing CRs from patch.)
patching file a/drivers/video/msm/gpu/kgsl/kgsl_ringbuffer.c
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 786:
# make CROSS_COMPILE=/files/Software/Android/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm clean
# make CROSS_COMPILE=/files/Software/Android/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm htcleo_defconfig
# cp ../../config ./.config (This config was pulled from SuperRAM 1.5's /proc/config.gz)
# make CROSS_COMPILE=/files/Software/Android/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm menuconfig
# make CROSS_COMPILE=/files/Software/Android/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm zImage -j 4
arch/arm/mach-msm/built-in.o: In function `dex_cb_interrupt':
/files/Software/Android/hastarin/source/a/arch/arm/mach-msm/dex_comm.c:248: undefined reference to `notify_vbus_change_intr'
make: *** [.tmp_vmlinux1] Error 1
Click to expand...
Click to collapse
Any additional help would be appreciated. Also, is there a reason (performance, size, etc) CIFS is not included by default? I've noticed a lot of other builds are like that, too.
*EDIT* Is it possible I need to checkout a specific version of Hastarin's kernel?
Thanks,
B.
I posted this in the main thread before it was closed -
insmod: init_module 'cifs.ko' failed (Exec format error)
and I looked in dmesg -
cifs: version magic '2.6.32.15r8.6-gb02686c preempt mod_unload ARMv7' should be '2.6.32.15-g2ef5752.dirty preempt mod_unload ARMv7'
Looks like this might be a side effect of the custom kernel and the magic not matching up with the cifs.ko from hastarin. Could this be recompiled with the correct kernel?
Looks like the cifs.ko that was included in the build was the stock module from hastarin - so when you do recompile it, could you post the module as well? I'd love to help, but I don't have a whole lot of experience with compiling kernels.
Thanks.
indecided said:
I posted this in the main thread before it was closed -
insmod: init_module 'cifs.ko' failed (Exec format error)
and I looked in dmesg -
cifs: version magic '2.6.32.15r8.6-gb02686c preempt mod_unload ARMv7' should be '2.6.32.15-g2ef5752.dirty preempt mod_unload ARMv7'
Looks like this might be a side effect of the custom kernel and the magic not matching up with the cifs.ko from hastarin. Could this be recompiled with the correct kernel?
Looks like the cifs.ko that was included in the build was the stock module from hastarin - so when you do recompile it, could you post the module as well? I'd love to help, but I don't have a whole lot of experience with compiling kernels.
Thanks.
Click to expand...
Click to collapse
Hi indecided,
This is the post I'm looking to resolve for everyone. Once I figure this out, I'll post how to patch the SuperRAM 1.5 to support CIFS.
Thanks,
B.
this is great news and i'm looking forward to this - i hope your efforts can accomplish this - it probably won't be easy, which is why hastarin and darkstone might have needed to focus their efforts on other things first -- i'm not being negative, i'm just saying that if you guys get this to work it might be an impressive thing you did. I need it bad too.
OK, unfortunately I've hit a bit of a roadblock. I've got the kernel to compile using nearly all the same config settings as DarkStone with CIFS added, but upon booting the kernel the phone acts as if there is 0% battery and instantly shuts itself off. I'm guessing it has to do with the one problem I had in compiling explained below.
The only difference in the configs for compiling were (removed CIFS info):
# diff MY.config DARKSTONES.config
119,120c119
< CONFIG_SLOW_WORK=y
< # CONFIG_SLOW_WORK_DEBUG is not set
---
> # CONFIG_SLOW_WORK is not set
241,242c240
< CONFIG_HTC_BATTCHG=y
< # CONFIG_HTC_BATTCHG_SMEM is not set
---
> # CONFIG_HTC_BATTCHG is not set
Click to expand...
Click to collapse
So basically, DarkStone's version had SLOW_WORK and HTC_BATTCHG disabled. I have no idea how he accomplished this. No matter what I set SLOW_WORK to, the compilation always changes it back. And if I try to disable HTC_BATTCHG, the kernel errors out with the message from my previous posts.
I'm also not entirely sure the patch DarkStone posted is complete (unless he responds otherwise) because it does end prematurely and was perhaps cut off by pastebin.
I wish I knew what else to try, but I'm not knowledgable enough to know why it thinks the battery is at 0%. I'm guessing it has something to do with the BATTCHG config, but I have no way around it at the moment.
Thanks,
B.
sorry to disturb here, but if you where to successfully recompile, what will be the benefit?
thanks you
there should be tons of warnings though correct?
Fmstrat said:
Any additional help would be appreciated. Also, is there a reason (performance, size, etc) CIFS is not included by default? I've noticed a lot of other builds are like that, too.
*EDIT* Is it possible I need to checkout a specific version of Hastarin's kernel?
Thanks,
B.
Click to expand...
Click to collapse
Hi! Sorry to hear you're having issues with building the kernel.
Here is a properly formatted patch that I've made: http://www.multiupload.com/FDJ4FXZ4L9
I used the eb_oldcam branch (or was it oldcam_eb? I've forgotten )
Try using the htcleo_hastarinconfig as the defconfig file.
I recommended that toolchain because Hastarin and myself have experienced issues with other toolchains causing the proximity/light sensor to eat up more battery during standby.
Hope this helps!
-------
Oh and Merry Christmas folks!
dapoharoun said:
sorry to disturb here, but if you where to successfully recompile, what will be the benefit?
thanks you
Click to expand...
Click to collapse
Ability to mount shares computers over wifi for playing media.
Fmstrat said:
Ability to mount shares computers over wifi for playing media.
Click to expand...
Click to collapse
It's like having a 4 terabyte sdcard. If you have say a 30,000 song collection, and you connect to your home computer via wifi at home you click the songs and they play instantly. For me, I click any one of my 3000 movies and they play on my hd2 in 10 seconds, and I can fast forward and rewind almost instantly.
If you are on the road and have a vpn to your computer and you 'mount the home share remotely' you now have a "virtual sd card" with 30,000 songs that play when you click the songs after about a 6 second lag.
DarkStone1337 said:
Hi! Sorry to hear you're having issues with building the kernel.
Here is a properly formatted patch that I've made: http://www.multiupload.com/FDJ4FXZ4L9
I used the eb_oldcam branch (or was it oldcam_eb? I've forgotten )
Try using the htcleo_hastarinconfig as the defconfig file.
I recommended that toolchain because Hastarin and myself have experienced issues with other toolchains causing the proximity/light sensor to eat up more battery during standby.
Hope this helps!
-------
Oh and Merry Christmas folks!
Click to expand...
Click to collapse
Good news everyone. It's working.
Thanks DarkStone for all your input, using the default config and eb_oldcam worked with the new patch you provided on the first try this time (Btw, I am using the toolchain you recommended now). I do have one last question though, how do I get it to load cifs.ko on boot? Android doesn't appear to have any modprobe.conf or anything similar that I see, so I must be missing something. I have to insmod it manually right now.
*EDIT*: I ended up rebuilding it directly into the kernel instead of a module for now, which works. I know that's not "proper" but that will ensure CIFS is always loaded even if the build doesn't load it by default. If you know a better way, I'm all ears Thanks again! */EDIT*
For everyone else, this is not an EXACT copy of the SuperRAM kernel that DarkStone used, but it's pretty close and seems to be the config they recommend going forward. Rather than post it here right now, I'll give it out as a Christmas gift later today in the Development forum since it will really apply to any RAM release going forward that uses Hastarin's kernel and post a link here. This will give me some time to test and ensure nothing goes weird.
Thanks,
B.
OK, it's all done: Download, installation instructions, and FAQ
I've also opened a thread back in the Android Development section since this is no longer a Q&A: http://forum.xda-developers.com/showthread.php?t=887567
Thanks,
B.

[Call for Help] Kernel Parameters - ro.secure

Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
bobjbain said:
Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
Click to expand...
Click to collapse
This is a question. [Q&A]
yz.hd said:
This is a question. [Q&A]
Click to expand...
Click to collapse
Thanks for the useful and insightful response
FYI - I realised that it might be after I submitted it! Which is why I caveated the post at the end.
this parameter is in the initrd.gz in the kernel in the boot folder of the ROM.
You should extract it and inside there is a file called default.prop
extract
mkdir initdir
cd initdir
zcat ../initrd.gz | cpio -i -d
compress
cd initdir
find . | cpio -o -H newc | gzip -9 > ../initrd.gz
Each line in the file default.prop is an attribute assignment. There we need to
Note the two properties: ro.secure, and ro.debuggable. . If ro.secure = 0 is allowed us to run the adb root command.
Usually we put the core ROOT refers to the ro.secure = 0. ROOT permission to refer to the general said on the phone
A license management program (Superuser.apk) procedures for the root user can grant permission.
bobjbain said:
Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
Click to expand...
Click to collapse
look here this great kernel should have ro.secure set to 1
Bologna said:
look here this great kernel should have ro.secure set to 1
Click to expand...
Click to collapse
it doesn't, it's based on Tytung's Kernel, Tytung's doesn't so I'm not suprised that dorimnax's "greatest ever" (sic) doesn't teither
big thanks to magnus48, have decompressed the kernel, changed ro.secure to 1, recompressed, copied to /boot
Phone booted (which suprised me) and my SkyGo App now works.
Yay
magnus48 said:
The easy way is use root explorer and edit /default.prop on your device but is not free.
ro. means read only you can't change it's value after rom is loaded
Click to expand...
Click to collapse
So, I can either change the value in my kernel OR I can edit default.prop and reboot??
Won't the values in default.prop get overwritten on boot??
bobjbain said:
it doesn't, it's based on Tytung's Kernel, Tytung's doesn't so I'm not suprised that dorimnax's "greatest ever" (sic) doesn't teither
Click to expand...
Click to collapse
First question : Why of this sarcastic reply?
Second question : Can you please share your skygo working app, telling us what's the kernel you're using to have it working?
Thanks in advance
bobjbain said:
So, I can either change the value in my kernel OR I can edit default.prop and reboot??
Won't the values in default.prop get overwritten on boot??
Click to expand...
Click to collapse
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The change should be done inside initrd.gz
magnus48 said:
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The shange should be done inside initrd.gz
Click to expand...
Click to collapse
You should be able to pull it, make changes and push it back to phone via adb. Useful if you don't want to reflash
Sent from my HD2 using XDA
jwchips said:
You should be able to pull it, make changes and push it back to phone via adb. Useful if you don't want to reflash
Sent from my HD2 using XDA
Click to expand...
Click to collapse
default.prop is in the initrd.gz, this is extracted when the phone boots, so any changes you make to default.prop WILL be overwritten when the phone boots.
You have to make the changes inside the initrd.gz file.
Bologna said:
First question : Why of this sarcastic reply?
Click to expand...
Click to collapse
I don't quite hold dorimanx in quite the high esteem that others do, his work is good but it can be rushed as shown by his 5.x series of Kernels.
Bologna said:
Second question : Can you please share your skygo working app, telling us what's the kernel you're using to have it working?
Thanks in advance
Click to expand...
Click to collapse
Here although this is an app for UK Sky only and won't work for non-UK subscribers.
bobjbain said:
default.prop is in the initrd.gz, this is extracted when the phone boots, so any changes you make to default.prop WILL be overwritten when the phone boots.
You have to make the changes inside the initrd.gz file.
Click to expand...
Click to collapse
Any chance you could post the modified kernel? I am running R14 on GB3.2a so it would drop right in
CR5N said:
Any chance you could post the modified kernel? I am running R14 on GB3.2a so it would drop right in
Click to expand...
Click to collapse
yertiz.
Take a backup of your current initrd.gz first though to be on the safe side.
bobjbain said:
yertiz.
Take a backup of your current initrd.gz first though to be on the safe side.
Click to expand...
Click to collapse
Thankyou. This works on Tytung GB3.2a. F1 channel now working on this old HD2
What about SD builds?
magnus48 said:
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The change should be done inside initrd.gz
Click to expand...
Click to collapse
I can access and edit default.prop on my SD build after the phone has booted. This seems to give me access to Sky News at least. But I still can't get premium channels. Do you think I still need to edit initrd.gz as well or is that now redundant?
johnkst said:
I can access and edit default.prop on my SD build after the phone has booted. This seems to give me access to Sky News at least. But I still can't get premium channels. Do you think I still need to edit initrd.gz as well or is that now redundant?
Click to expand...
Click to collapse
No, you will need to edit your initrd.gz
Before I did I could access Sky News only, afterwards the Sky world was my Oyster!!
bobjbain said:
No, you will need to edit your initrd.gz
Before I did I could access Sky News only, afterwards the Sky world was my Oyster!!
Click to expand...
Click to collapse
Thanks Bob. Is there anything else I should edit while I'm at it?
Currently after booting, my default.prop contains the following attributes:
ro.secure=0 (need to change this to 1)
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
I'm particularly suspicious of the last one!
Also... what should I use to edit default.prop within initrd.gz? I tried unzipping it with 7zip, editing the initrd file with a hex editor and re-zipping but it created a significantly smaller file...
johnkst said:
Thanks Bob. Is there anything else I should edit while I'm at it?
Currently after booting, my default.prop contains the following attributes:
ro.secure=0 (need to change this to 1)
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
I'm particularly suspicious of the last one!
Also... what should I use to edit default.prop within initrd.gz? I tried unzipping it with 7zip, editing the initrd file with a hex editor and re-zipping but it created a significantly smaller file...
Click to expand...
Click to collapse
I only ever changed ro.secure, don't have the phone any more so can't check the other values.
To edit the default.prop you need to uncompress the initrd.gz then recompress it using the following linux commands
Code:
extract
mkdir initdir
cd initdir
zcat ../initrd.gz | cpio -i -d
compress
cd initdir
find . | cpio -o -H newc | gzip -9 > ../initrd.gz
As I run windows I downloaded and installed cygwin and used that to uncompress and recompress the kernel.
I edited the default.prop in windows but you can use vi within cygwin if you want.
If you're uncomfortable doing this then attach your kernel to a post and I can do it for you.

Pac-Rom + Pink kernel 20140319: WiFi not working: workaround

Hello,
Sorry, I have to post this workaround here because I'm new on xda and I can't post an answer on the development forums. So if someone see that, please post a link to this thread on PAC ROM or pink kernel topic
It seems there is a new file in the modules directory which is a symbolic link named wlan.ko. As an easy workaround, simply replace this file (/system/lib/modules/wlan.ko) by this one: /system/lib/modules/pronto/pronto_wlan.ko (move this file to the parent directory and rename it). Then reboot, you should have the WiFi working now
PS: I guess it's maybe better to modify the symlink or load the correct module but it's harder to write command lines with a smartphone
According to some people, this bug should be fixed now.
Doesn't work!
Sadly, doesn't work on PA/C-RoM.
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Mycroft-Dev said:
Sadly, doesn't work on PA/C-RoM.
Click to expand...
Click to collapse
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
matttbe said:
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
Well, Wi-Fi still refuses to work after removing the symlink!
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Cheers, mate!
Mycroft-Dev said:
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Click to expand...
Click to collapse
No :-/
Maybe you can try to reinstall the latest nightly version of your rom (released after March 20th -- I think it's the case for C-RoM), reboot and check if the WiFi is working. If yes, don't disable it now then reinstall the latest version of Pink kernel.
But if the WiFi is still not working, it's annoying... You can reformat /system where kernel modules are installed but I think it's automatically done when installing a rom. Maybe they are not using the latest version of the kernel?
Mycroft-Dev said:
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Click to expand...
Click to collapse
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Clarification
matttbe said:
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Click to expand...
Click to collapse
As in, I repacked the kernel, and then flashed it.
I'll try tweaking a bit here and there, and let you know how it goes.
And yes, I flashed the latest C-RoM.

Categories

Resources