hey,
I installed CM10 stable on my i9000. Since the internal storage in my sgs is broken I had to do the mmc swap. So I did it but it turns out that the swap was not working with a kernel that comes with CM10. So I had to update the kernel to Semaphore 2.6.6. Now changes I did in vold.fstab are being picked up. Is that normal that the mmc swap is not working out of the box with CM10 kernel ?
I do some development on my galaxy and it's almost impossible to do it without a logger working. The logger is ondemand module for Semaphore. I swithed the Logger module on in the Semaphore Manager but it's still not working.
From the console via abg I run
Code:
130|[email protected]:/res/scripts # ./S30enable_logger
cp: can't stat '/system/lib/modules/logger.ko': No such file or directory
What am I doing wrong ? How to enable any logger in CM10 with the sdcard swap ?
EDITED:
I fixed my problem installing CM10.1 + Semaphore 2.9.2
Logger module works for me.
Related
hi. I installed CM6.1.2 for milestone (thanks doshaska) beta on my milstone (not droid) mainly because I really want to use openvpn .
However there seems no tun/tap module in /system/lib/modules (i first looked /lib/modules hoping modules lies in the normal linux module path) and also can't connect to the openvpn server with the default vpn setting program.dmesg says "Cannot allocate TUN/TAP dev dynamically"
Is the missing tun module the reason ? If so , any possiblity in the future that someone can compile the tun module for the CM6 kernel?
btw, I heard something about 2nd-boot . Is there any possiblity to run a complete new kernel avoiding the the damn locked bootload using the 2nd-boot?
PS: sorry for my poor english....
Updated my SD card to CM7.0.3 and want to use an overclock kernel.
Which one is best to use from the downloads available here do you just use the latest 040411 or are some of the test builds good?
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
findmike said:
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
Click to expand...
Click to collapse
how is the battery usage when overclocked?
When I first set up my SD card the following instructions were in the thread concerning overclocking
5a. *Optional* If you want to run an overclock kernel you need to choose and download a compatible kernel for SD (not eMMC).
5b. Move the uImage file from the SD card to your pc as a backup.
5c. Rename the oc kernel you have downloaded uImage copy it to the SD card.
Can I simply take the zip file for the 042411 kernel open it and swap the uImage files. I saw in another thread about flashing it.
Had lots of trouble getting the 7.0.3 update to take, timing the hold the n and power buttons trick.
Also I saw something about using setcpu to overclock, can someone fill me in on that, is it software or somewhere in the CM7 settings?
s52m3 said:
how is the battery usage when overclocked?
Click to expand...
Click to collapse
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
RASTAVIPER said:
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
Click to expand...
Click to collapse
Are you talking about this app
https://market.android.com/details?id=com.teamwin.kernelmanager.free&feature=search_result
Battery life seems to be pretty good right now but I understand the latest CM builds have some fixes that help increase battery life. I don't think the overclock really effects battery life all that much since the vast majority of the time it doesn't need to kick into high speed.
For the install of the kernel, I normally just flash that when I flash the OS and Gapps. If you are running CM7 off your SD card, I can't help much there except to say that it's SOOOO much easier to run off eMMC since I can just use the built in Rom Manager App to jump into Rom Manager and update things without having to have a bootable card or modifying any files.
Regardless of SD / eMMC install, you don't need to use SetCPU with CM7. If you get the kernel installed, just go into Settings / CyanogenMod settings / Performance / CPU settings and you can change. Most people use the OnDemand performance governor with 1300 max and 300 min and set on boot checked.
I leave Set on Boot off in case something goes goofy. I just reset the overclock to 1300MHz when ever I reboot with a new build.
I could never get the 424 OC to load on my Nook (always got the "expected ) error) so I just swap the OC kernel and system folder into each new build. It's a few extra steps but at least it works.
I'm running N67 at 1300MHz from a Sandisk Class 4 16GB card. Works great!
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
GTT1 said:
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
Click to expand...
Click to collapse
You're running CM7 off an SD card, unless you want to mess up whatever you have on internal eMMC, don't go changing scripts or flashing things which don't apply to your install. Whichever way you got your CM7 installed, stick to the original instructions and follow up on the original threads instead of grabbing bits and pieces here and there. You'd save yourself and others a lot of confusion.
I use the kernel : (source)
KERNELS WITH KEYPAD DRIVERS AS MODULES
Duckly's Kernel [Turbo Kernel] [27-3-2011]
Change Log:
**GPU Overclocked (PLL1 Overclocked From 768 To 960Mhz)
Compiled With GCC 4.4.3
Updated Source Code
Compiled With Performance Optimizations (-O2) Instead Of Small Size (-Os)
Added And Modified Battery Driver (From SP3DEV)
No Sleep Of Death
Compcache Driver Added
Tiwlan Wifi Driver Added
Updated Headset Driver (From SP3DEV)
Added compcache driver
Available RAM 200MB
Included Extra IPtable Modules For WiFi Tethering
No Key Freeze
Note:
Add line in startup "acpuclock.force_turbo=1 clock-wince.grp=0xa92"
I've replaced two file "modules-2.6.27.46.tar" and "zImage" in npkboot, but I do not understand the :
(Add line in startup "acpuclock.force_turbo=1 clock-wince.grp=0xa92").
I have to copy add this line anywhere in the file "Startup"? or should I replace this line instead of the "clock-wince.grp = 0xa92" located at the end of file "startup"
At your "startup" file in the npkboot folder, open it and add in acpuclock.force_turbo=1 clock-wince.grp=0xa92. If your startup file already have this command line then no need to add.
add to the problem is where, first, last, middle or where??
this is the file "startup" of me: http://www.mediafire.com/?ll1h96pr3wk7533
Help Me !!!
Replace your startup command with mine:
set ramsize 0x8000000
set ramaddr 0x10000000
set mtype 2006
set INITRD_OFFSET 0x608000
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=npkboot fbcon=rotate:2 ro.sf.hwrotation=180 lcd.density=240 msmvkeyb_toggle=off msmts_calib=0x0366.0x04b.0x0c8.0x038e clock-wince.grp=0xa92 acpuclock.oc_freq_khz=652000 pmem.extra=1 no_console_suspend physkeyboard=kovsq msmsdcc_1bit msmsdcc_fmax=14000000 hw3d.force=1 acpuclock.force_turbo=1 "
boot
Click to expand...
Click to collapse
Hopes it help..
after replacement is complete, copy 2 file "modules-2.6.27.46.tar" and "zImage in npkboot is completed, also be modified with Terminal Emulator ???? (I have to modify more by Terminal Emulator ???)
Ex :
su
mkdir /data/opt
cp /sdcard/autostart.sh /data/opt
chmod 755 /data/opt/autostart.sh
I can't understand ????
if you are using KERNELS WITH KEYPAD DRIVERS AS MODULES then no need to do that step, because using terminal method is for keyboard freeze problem. Your kernel should not have such problem.
but after I replace the 2 files in kernels AS DRIVERS WITH KEYPAD MODULES then start Android, the keyboard does not work. I use the Android Honeycomb Froyo V3
I do this :
- I download 2 file "modules-2.6.27.46.tar" and "zImage on,
- Replace them into the folder npkboot then run harset.exe
This is right ????
Yeap this is the correct way, I'm just curious about why your keyboard still does not work even though kernel as driver with keypad modules already installed.
I see you also use the X1 has a ROM like me, KERNELS WITH KEYPAD DRIVERS AS MODULES not you use?, please guide me how to install. Thankss.
I download this file: HERE then extract and replace them (2 files) into the folder npkboot then start Hartset.exe and Keyboard doesn't work
oh And when I use the kernel include in Honeycomb Froyo V3 6 / 7, then Terminal Emulator not turn up the virtual keyboard ???
I'm using Honeycomb Froyo V3 by Needo and using the turbo kernel ( keypad drivers not as modules ) included in the ROM, so far no keyboard freeze for me.
1. Did you try to lower your CPU speed like 614Mhz or 575Mhz??
2. Did you try this kernel? This kernel is posted by Needo to solve the keyboard freeze problem
3. Or you can try to reinstall the ROM by reformatting your SD card to 4 partition then install Honeycomb Froyo V3 again.
And yes, Terminal Emulator will not turn up the virtual keyboard and you must use the phone keyboard to type in commands, but for you I think it is impossible to do that..
but when I replace it with KERNELS WITH KEYPAD DRIVERS AS MODULES the virtual keyboard is turned on, the keyboard freezing error only happens occasionally one day / one time but instead KERNELS WITH KEYPAD DRIVERS AS MODULES then boot from the keyboard not working
I do not understand, I do to use kernels WITH KEYPAD MODULES AS DRIVERS?, I want to fix complete and use the keypad ?????
My CPU Clock : 600000 in Startup.txt
I can't promise that the keyboard will never freeze after you install the KERNELS WITH KEYPAD DRIVERS AS MODULES. If you are using Honeycomb Froyo by Needo, you can use the Fast Reboot app pre-installed in the ROM to activate back your keyboard, and try to lower the cpu speed to 575Mhz.
thank you very much for your enthusiasm, I want to ask why the kernel included in the ROM Honeycomb Froyo V3 is the virtual keyboard does not work?
And why I have set right all that as soon as the boot keyboard did not work?
Thanks You
h_pro9x said:
why the kernel included in the ROM Honeycomb Froyo V3 is the virtual keyboard does not work?
Click to expand...
Click to collapse
For this you should ask the developer, I'm just trying my best to answer your questions based on my knowledge, and welcome..
Thanks
Oh, by default the Honeycomb Froyo V3 button camera is not Home(it is Standby)?? So my X1!
Yes, Honeycomb Froyo V3 camera button is set as Standby ( turn off the screen ) by default
Hi, I tried to apply ext4 lagfix via CF ext4 Manager (CF-Root-ext4-v1.3-Addon.apk) , data was converted successfuly, system was not converted due not enough free space, which is normal as Chainfire said.
Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed.
Click to expand...
Click to collapse
Running 2.3.4 JVQ stock firmware with CF root.
But after reboot ext4 app have all choices grayed, so I cannot convert system or any other partion to ext4 or back.
It show "No rfs/ext4 partions found" and "unknow ,0.0MB, 0.0MB total"
Any tips appreciated. Thanks in advance
Roman
Which kernel are you running? Try changing kernel eg: Semaphore or galaxian. Then do a wipe cache and dalvik cache
Runnig CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS on stock JVQ without other changes.
Thanks for advice
Problem is, that many kernels have logging disabled, I need logcat, ddms for developing
EDIT: Flashed semaphore, there is greenscreen while lock/unlock screen(minor issue),but other things seems fine, thanks!
semaphore has logging enable script
Quote :
"In order to control voodoo sound and BLN you have to download Voodoo Control and BLN control applications respectively from android market.
The max CPU frequency is by default 1Ghz.
You may use applications like Voltage Control or Pimp my CPU to control OC/UV.
In order to load various modules of the kernel copy the respective script from /res/scripts to /system/etc/init.d directory and give the script executable permissions. This is optional. It is needed only if you want to use this functionality. The scripts:
- enable_conservative (load conservative governor module)
- enable_cifs (load cifs module)
- enable_netfilter (load netfilter modules for firewall or WiFi, USB tethering)
- enable_tun (load tun module)
- enable_deadline (load the deadline I/O scheduler module)
- enable_binfmt_misc
- S05_enable_oc replaces enable_ocuv since 1.6.0 (enable overclocking)
Other scripts:
- enable_sm_cold script for SpeedMod cold preset
- enable_sm_warm script for SpeedMod warm preset
- enable_sm_neutral script for SpeedMod neutral preset (please note that this is enabled by default)
To enable logcat run the enable_logger script in res/scritps and reboot your phone."
Here is the link
Hope this helps.
I just upgrade my cappy from Helly Bean 0813 to 0820. I noticed sometime my memory setting is 375M but I set to XL, so it must 388-390M. After a reboot, it back to 388M, why? I use Devil Kernel Config 0.9. It also happened in build 0813.