Related
This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.
O Whoa, Wired Tether works on my stock Eris now Thank You
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it
Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.
Thanks duder, works like a charm...
Sent from my phone.
THANKS!!!!
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.
XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.
I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.
Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.
Here is the initial release of my kernel. I'd like to have some other stuff fixed/working, but for now, this is it. I've made a lot of changes and I tried to list them all below, but I know there is stuff that I missed. Currently, the only issue that I know of is that the boot animation will be out of sync and may skip on boot. I have currently retained the stock boot animation, but custom boot animations are also possible if people would like them.
Also, while this kernel can work for recovery, I currently have not tested it, so recovery will remain what it is (ie. jt1134's CWM). I plan on testing recovery soon and releasing an updated Odin for it, as well as just having the kernel zip re-flash recovery.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0807
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB storage in recovery
0730
Custom boot animation support
Updated recovery
0710
Voodoo Sound V10
Updated CWM Recovery
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Test CWM and flash recovery partition
Smooth out boot animation
Get an overclocking kernel out
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.
Legend
voodoo/novoodoo - voodoo has the lagfix, novoodoo doesn't (I hope this was obvious)
Frequently Asked Questions
How do I install this?
You flash this in CWM. If you need CWM, you can find it here
Can I use ROM Manager to flash this?
If you didn't use Odin to flash CWM, this will not work. Also, ROM Manager is not compatible with CWM when it fully replaces stock recovery.
Can I install this over another Voodoo Lagfix kernel?
Yes. Any kernel that use's supercurio's lagfix can be flashed over any other kernel that uses it.
How do I disable Voodoo Lagfix?
Create a file on the SDCard named disable-lagfix within the voodoo folder (/sdcard/voodoo/disable-lagfix). You can also use the option in the Voodoo Control app (from the market) or the option in CWM Recovery to disable the lagfix.
How do I know if it is installed?
Go to Settings > About Phone and the kernel version should read:
Code:
2.6.32.9
[email protected] #1
Will this work with xxx ROM?
This will work with any currently available ROM that is posted here.
Can I overclock with this kernel?
No. Currently overclocking is not supported. I do plan on looking into implementing this in a future version though.
Can I use SetCPU with this kernel?
You can use SetCPU with this, but do not use profiles. If you have problems and are using profiles, I'm not going to try to fix them as profiles do not work properly on any SGS phone that I've seen.
Does this kernel include xxx feature?
If it is not listed in the first post, probably not. To be sure, check the commits to the source on Github.
Can you add/implement xxx feature?
If you can link to what you want added/changed, I can look into doing so. If you just say something like "I want bigger quadz!" with no information about what you want or where to find it, I'll just disregard your request.
I am having xxx issue, can you fix it?
See the NOTES section above. Failure to provide any steps to reproduce your error, or a log of the issue as it is occurring will not get your problem fixed. I need the output from logcat and/or dmesg to be able to fix problems. Use the following to obtain a log (easiest with ADB).
Code:
adb shell dmesg > dmesg.txt
adb logcat > logcat.txt
Enter one of the commands and attempt to recreate your issue. Logcat will run constantly until you stop it (disconnect the phone, or ctrl+c). Dmesg will dump the current buffer and end. Try to get a logcat first as it will be easier to capture the error. PM me the files once you've collected them and I will look into it. DO NOT POST THEM IN THE FORUM. Logcat and dmesg may both contain identifying information (like your phone number or email address) so PMing them to me will prevent everyone from seeing this info. If you need help, ask or join IRC.
If you would like something added to the FAQ, please post it in the following format:
Code:
[PLAIN][b]Put the question here[/b]
Put the answer here[/PLAIN]
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yes, added installation instructions to OP
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Blanco954 said:
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
If you have lagfix enabled you just flash the voodoo kernel, or disable lagfix and flash non-voodoo kernel if you want RFS file system
Thanks Hopper. I will give this a try.
Sent from my SCH-I510 using XDA Premium App
Worked like a champ for me...thank you!
Sent from my SCH-I510 using Tapatalk
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Flash, flashed!
Thanks again, imnuts!
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
We currently have only one cwm which is jt's, so I don't quite understand what you mean.
froodyo said:
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
Click to expand...
Click to collapse
Thank you very much.
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Click to expand...
Click to collapse
Yes, lagfix is disabled the same way with any kernel that uses supercurio's Voodoo Lagfix.
froodyo said:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
Kernels are almost always independent of the ROM, so yes, you can install this regardless of what ROM you are running (Stock, debloated, something else). If/When we get a non-TouchWiz based ROM, this may change, but for now, you can use this with anything currently available.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
Click to expand...
Click to collapse
I set up novoodoo to try and avoid issues, so if you were on voodoo and didn't disable, the novoodoo should still work, but why risk it if you don't have to?
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Manjews said:
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Click to expand...
Click to collapse
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
hey i come from the fascinate and i love your work can't wait until you get voodoo sound working
i will be rooting a friends droid charge soon and then i will set him up with JT cwm voodoo and your kernel
glad to see some devs i already know working on the droid charge
khanfuze said:
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
Click to expand...
Click to collapse
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Manjews said:
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Click to expand...
Click to collapse
Good to hear Samsung released broken cpu governors again
Galaxy SL I9003 CyanogenMod7 Q&A
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
Hello Everybody..
I made this thread is ONLY for Question & Answer for Galaxy SL i9003 CyanogenMod 7.1.0 development.
Galaxy SL i9003 of CyanogenMod7 developer a.k.a Codeworkx is still working on this CM7 rom and please do not go off the topic in there. He's working alone and cannot answer all your question.
This is the thread to get know about CyanogenMod7 on Galaxy SL i9003
[WIP][ROM][2.3.7][GWK74] CyanogenMod 7 for Samsung Galaxy SL
Anything about your question & answer, you SHOULD post here.
FAQ (Please Read!!)
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSL phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps.
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: My battery life is simply awful, any tips?
A: Wi-Fi, bluetooth, and GPS are major battery killers. Wi-Fi and bluetooth are particularly hungry, so turn them off when you don't need them.
Q: The phone booted but I'm not getting any signal, what gives?
Q: My phone takes a few minutes to establish a 3g signal after I turn it on, what gives?
A: Known issue with polling when staring up the network. Put the phone to sleep by pressing the power button and waking it up a few times and it will usually come up with a signal.
Q: I lost my SMSC information, how to I get it back?
A: Follow these steps to restore.
Q: When will Voodoo sound/color/sharpness be integrated?
A: Maybe some parts will be integrated someday, but there some UNSUPPORTED kernels available on the threads that do this already. Please direct any issues related to these to the appropriate developers, not us.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: How do I go back to a Samsung stock ROM?
A: The easiest way is to go back to stock using Odin and flashing a full firmware (including PIT file) with repartition checked (Odin One-Click does this by default on Captivate)
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes. (not applicable at this time)
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer)
Q: Can I use another kernel like CF-Root with this?
A: MAYBE, but you have to make sure it is compatible. We do not support any kernels except the one we install.
Q: GTalk doesn't work with FFC?
A: We can either have a fully fixed camera without gtalk video chat support (samsung libcamera)
or we can have a buggy camera with gtalk video chat support (opensource libcamera). We went with the fully working camera without GTalk FFC support. Once we have updated libs from Samsung for camera, it'll work.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: You can look through the issue tracker here. If you do not see your issue, please report it. If someone else has it, please star it (but please do not file "Me too!" reports). Try to also attach the logcat output and last_kmsg to the bug report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had a crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
desktop$
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this. Use this to paste the bug:- http://pastebin.com/
Thank you. Im just helping
You are right. This is good topic I think!
AmirolAhmad said:
mate, u can post about cm7 here:- http://forum.xda-developers.com/showthread.php?t=1320125
answer for question, "Root your device and install codeworkx ClockworkMod Recovery Kernel." its mean u should flashing his kernel then u will have pre-rooted device. proceed with CM7 ROM
if ur device didnt boot, remove ur battery, put it back and reboot ur device
Click to expand...
Click to collapse
I did remove the battery, but same problem it's stay in SAMSUNG logo.
Or should I go back to froyo ROM and root my device using superOneClick?
and flash his CWM kernel?
malungkot said:
I did remove the battery, but same problem it's stay in SAMSUNG logo.
Or should I go back to froyo ROM and root my device using superOneClick?
and flash his CWM kernel?
Click to expand...
Click to collapse
Just flash your device with XXKPM, then flash ClockWorkMod by codeworkx. Then apply CM7 by codeworkx. All should be OK.
malungkot said:
I did remove the battery, but same problem it's stay in SAMSUNG logo.
Or should I go back to froyo ROM and root my device using superOneClick?
and flash his CWM kernel?
Click to expand...
Click to collapse
this step work for me:-
1. Flash XXKPE
2. Flash XXKPM
3. Flash Codeworkx Kernel (http://forum.xda-developers.com/showthread.php?p=18593913#post18593913)
- when u on this step, u device is PRE-ROOTED
4. Flash CM7 ROM (http://forum.xda-developers.com/showthread.php?t=1317940)
falex007 said:
Just flash your device with XXKPM, then flash ClockWorkMod by codeworkx. Then apply CM7 by codeworkx. All should be OK.
Click to expand...
Click to collapse
But he said "ROOT first" you mean the CWM of codeworkx is Pre-rooted?..
I tried that procedure also, I Flash KPE, KPM and Flash Codeworkx CWM, but no CWM icon in application list? How I can access CWM?
was thinking abt a creating such thread then i see this..
how abt adding "bug reports" to the title?
also add in ur op that the thread is only meant for members who wish to know current state of cm7 b4 installing it.
N mention not to complain abt bugs demanding to get them solved. only mention them. ur getting my point...
bcoz many will be afraid to flash it, includes me, cause we dont want the phone to screw up during work!!
n also add "codeworkx is not permitted to visit the thread"
OP UPDATE! thanks
use 3 COMBO button!
volume up + home button and then power button
then you will see 1st boot
count 1 2 3
release home button and power button..
you will see recovery..
@AmirolAhmad : Thanks for the thread, bro. really useful FAQ there.
indeed, we all need this thread to keep the original CM7 development thread stay clean.
malungkot said:
But he said "ROOT first" you mean the CWM of codeworkx is Pre-rooted?..
I tried that procedure also, I Flash KPE, KPM and Flash Codeworkx CWM, but no CWM icon in application list? How I can access CWM?
Click to expand...
Click to collapse
your device doesn't need to be rooted first.
just flash Codeworkx Kernel over xxkpm, then install CM7 zip file via *CWM.
the CM7 is pre-rooted.
____
*you can always access CWM by shut down the device then press 3-combination buttons (volume up + home + power), just as usual.
CMIIW
mjbri0613 said:
use 3 COMBO button!
volume up + home button and then power button
then you will see 1st boot
count 1 2 3
release home button and power button..
you will see recovery..
Click to expand...
Click to collapse
Salamat Kabayan!! ).. that will do!! I already flashing CM7 .. Yahooo!!!
Regarding titanium backup, add that same version of titanium backup should be used during restore as the one used during backup.
Sent from my GT-I9003 using xda premium
exctngdude said:
Regarding titanium backup, add that same version of titanium backup should be used during restore as the one used during backup.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Not necessary.
Erahgon said:
Not necessary.
Click to expand...
Click to collapse
It happened to me and many other users, apps force close when restoring with different version
Sent from my GT-I9003 using xda premium
back camera doesn't work for me!
masterchif92 said:
back camera doesn't work for me!
Click to expand...
Click to collapse
Read 1st..
Sent from my GT-I9003 using xda premium
exctngdude said:
It happened to me and many other users, apps force close when restoring with different version
Click to expand...
Click to collapse
In that case, TiB has an option to "create an update.zip". It basically creates a flashable zip which you can use to install TiB onto your device through CWM without the need for the market. Try that.
Sent from my GT-I9003 using XDA App
my notifications doesn't sound even i ticked all the check box in the setting..my ringtone also facing some probs..do u guys having this probs too? or i miss some part to set the sound..pls guide me if u havent got this probs..tq
I have problem with Market.. just flash googles addons.. Market always force close..
anyone have suggestion?
DSP manager work?
Hi there
I got droidwall running on the SGY.
Please first read the whole post. I add changes at the end of it.
Here's what I did:
1. follow this great tut from irfanbagus. Thanks a lot irfanbagus!
2. After running "make bcm21553_totoro_05_defconfig", set this in .config:
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
and continue irfanbagus's steps
3. Install the new boot.img, e.g. via mai77's method as shown here
4. Profit! (as in: use droidwall )
Notes:
Alternatively the changes in .config could be set in cm21553_totoro_05_defconfig or via make menuconfig
If you don't have your boot.img as a normal file, run this in adb, then pull the file:
dd if=/dev/block/bml7 of=/data/local/boot.img
I was surprised that there was no such modified kernel till now. Maybe this is because the TARGET_REJECT option is essential but only XT_MATCH_OWNER is largely discussed when dealing with droidwall.
See attachment (mikstev_SGY_Kernel_netfilter_for_droidwall_boot.img.zip) for a boot.img with only these modifications.
Please test and report. I only tested blacklist/whitelist mode with Google Play blocked/allowed on Wifi connection, but it worked.
Edit 1: I've added the necessary (and probably some more) modules so that droidwall's logging works. Use the second attached file instead the first one.
Here are the changes I made, compared to normal .config:
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
I guess the first two aren't necessary but I didn't bother to check every single module if it's the correct one which droidwall needs for logging. However this shouldn't matter anyway. See mikstev_SGY_Kernel_netfilter_for_droidwall_with_log_boot.img.zip
Edit 2: Due to request I've added init.d support to the latest release. Thanks irfanbagus! See mikstev_SGY_Kernel_droidwall_initd_boot.img.zip
Edit 2.5: Seems only the following modules are required but that only as a side note:
CONFIG_NETFILTER_XT_MATCH_OWNER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
Edit 3: New method for adding init.d support to a (newest) boot.img, with kernel modules for droidwall (+logging) and init.d scripts to load these modules. Please read the readme, if you have questions, post here. Special thanks to irfanbagus See mikstev_add_initd_to_boot.img__kernel_modules_initd_scripts_for_droidwall.zip
Edit 4: Thanks to an idea by irfanbagus and another tutorial to include init.d support by kurotsugi, here's another release. Adding init.d support is now easier with kurotsugi's method plus there's a update.zip (modules_droidwall_signed.zip) which does the other steps for you (copying the modules, init.d scripts and applying the correct permissions for these files). NOTE: this update.zip is yet untested. If you test it please report. See mikstev_add_initd_to_boot.img__kernel_modules_initd_scripts_for_droidwall_v2.zip
Edit 5: The update.zip from edit 4 seems to work. If you're using a kernel with init.d support you only need to install the update.zip and it should work fine.
good job. i know droidwall depend on other kernel features beside CONFIG_NETFILTER_XT_MATCH_OWNER. since i don't have plan to use droidwall, i don't bother to find it.
Profit indeed! It works! Good job, mikstev! I was able to block dolphin HD on my phone just to test if it works and it did, much to my delight!
And to irfanbagus as well for that wonderful guide on how to compile a kernel.
Great job, guys!
Now let's hope that all the other kernel developers include this small bit of configuration in their builts
finally! ive been waiting for this for ages. thank you very muchhhh!
Sent from my GT-S5360 using xda premium
Logging doesn't work yet. I'll try the solution from highlandsun: http://forum.xda-developers.com/showpost.php?p=11110889&postcount=357 tonight and upload new kernel if successful.
No need for so much hassel
Just use "lbe privacy guard" (free in store) it has much more features than droidwall and it doesnt require any special kind of kernel.
Y u no press "thanks"!?
Sent from my GT-S5360 using XDA
Ok, logging works now, I'll upload the new kernel. See first post.
devilrulz4ever said:
No need for so much hassel
Just use "lbe privacy guard" (free in store) it has much more features than droidwall and it doesnt require any special kind of kernel.
Y u no press "thanks"!?
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
It seems that there're at least some people who see this differently. Here're some of my reasons, why I prefer droidwall over LBE Privacy Guard:
- it's a good and easy to use firewall. Not more, nor less. That's what I want.
- no "hassel" (to use your words) with resticting internet access of "trusted" apps
- I did not find a way in LBE to block LBE from using internet. In the iptables rules created by Droidwall I can clearly see that droidwall is not allowed = blocked
@mikstev: I'm just curious...is it based on sgy's newest kernel?
I think so, the source code is the one mentioned in irfanbagus' post (update2) which I linked above.
nice...I can integrate dualboot and data-2sd mod into this kernel easily. thx
i got other option to make droidwall work.
on init.rc i added this line:
service netfilter /system/bin/iptables
disabled
oneshot
this also work with avast firewall..
gear12 said:
i got other option to make droidwall work.
on init.rc i added this line:
service netfilter /system/bin/iptables
disabled
oneshot
this also work with avast firewall..
Click to expand...
Click to collapse
Can anyone confirm this? I can't see how this could replace the missing kernel modules.
mikstev said:
Can anyone confirm this? I can't see how this could replace the missing kernel modules.
Click to expand...
Click to collapse
nope. iptables only a user space application that depend on kernel features. and you can't call iptables without command/params.
the firewall works great, also, I can see the logs but after disconnecting from the internet and a few minutes the log is empty again, is this normal or a bug?
off topic:
and can I make a request? can you make the your boot.img support init.d as well? please...
Adam_Blade said:
the firewall works great, also, I can see the logs but after disconnecting from the internet and a few minutes the log is empty again, is this normal or a bug?
Click to expand...
Click to collapse
Yep, I noticed this too. The droidwall source seems ok at first glance and I don't think it's related to the netfilter modules etc. My guess would be that it's dmesg's fault, maybe the log is truncated or something but this is just speculation. I'll investigate in this in a few days. Maybe someone else knows why this happens?
Adam_Blade said:
and can I make a request? can you make the your boot.img support init.d as well? please...
Click to expand...
Click to collapse
Sorry, I currently don't have the necessary skills, so if you're looking for a quick solution you might better ask someone else for help. (Especially since there're already kernels with this feature and including the modifications for netfilter/droidwall should be trivial). However as I wanted to build up my knowledge regarding android/kernel development anyway, I'll try to add this feature one time, but that surely would take >1 week.
Regarding dmesg: the buffer size is set by CONFIG_LOG_BUF_SHIFT=19 which means 2^19 Bytes = 512KiB. I'll check later if this relatively huge size is really used up.
@mikstev: make init.d support kernel is easy. we only have to add a few script inside init.rc file. we can do it easily by using dsixda's kitchen or put the script manually. you can see my modified init.rc here http://www.mediafire.com/?cc1kg8s7cx27onb
I believe the script that have to be added is
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
Just to get sure: the init.rc which needs to be modified is the one in the initial ramdisk and not in the kernel (zImage), right?
Hi everybody!
This thread is dedicated to containing all the kernel (and some other kernel-related) patches I create/port for our device. So I think it could help our kernel developers to focus on actual SGR-related work without worrying about examining and implementing everything that already have been created for other devices from scratch. I'll update this thread with all information whenever I do something related to the goal. I plan to make this a huge thread so please help us to keep it organized and ask common questions in the Q&A thread (in General section) or in PM (if nobody can answer your question). Thanks in advance!
BLN mod
What is BLN?
- Refer this article for more information.
What do I need to try it out on my device?
- Download my CWM-flashable zip from the following link (This installs my kernel plus my modified liblights (of course it makes a backup of the original one first)):
http://www.mediafire.com/?1cnua9uw3ckoiqk
What features does this kernel have?
version 3.1.10 (for ICS stock firmwares)
eMMC_ERASE_CAP disabled (totally safe to use)
it includes AOSP vibrator fix (it works with my pre-alpha CM10 build too) -> Hybrid kernel
Wi-Fi MAC address changing implemented
Keychord support enabled (start services using hardware keys -> revert to original MAC address by pushing 'volume down', 'volume up' and 'power' buttons simultaneously)
BLN support
- Download 'BLN Control - Free' or 'BLN Control - Pro' app from the Play Store. The pro version has some really nice additional features all of which are supported in my mod.
What do I need to enable it in my kernel?
- Apply my attached patch ('bln.patch') in your kernel source dir with 'patch -p1 < bln.patch'. This patch includes the BLN mod port from SiyahKernel3 (SGSII kernel). I removed its wakelock and earlysuspend dependency, our touchscreen driver has a different structure from that of SGSII touchscreen driver and it works without those quite well. I also added some cleanups regarding the original key led sysfs entries.
- Find 'Device Drivers->Input device support->Touchscreens->Atmel MXT224E Touchscreen Interface' in menuconfig and enable 'BLN Support' under it.
What do I need to enable it in my rom?
- Use a kernel that supports BLN.
- Extract 'system/lib/hw/lights.n1.so' from the CWM-flashable zip (in the link I previously attached) and put it into the appropriate folder.
- Optionally include BLN Control app.
Why do I need a special liblights?
- The original liblights doesn't support notifications since we don't have a led for that purpose. Epsylon3 uploaded the open source version of liblights he uses for CM7.2 to his GitHub. However, that unfortunately doesn't support stock Samsung roms (Button backlight doesn't work.), so I had to hack it a little to make it work. By default, the stock rom can set the brightness of the button backlight according to light conditions. I tried several options but didn't notice any difference in brightness, so my modified version returns 255 (0xFF) as brightness whenever it's set to some non-zero value (zero means turning it off). I also added support for BLN through the common Android notification way.
I uploaded its sources to GitHub:
https://github.com/Adam77Root/liblights_bln
Keychord support
What is it?
- If it is enabled in the kernel, init can start services triggered by hardware keys.
Why should I use it?
- I made a simple yet quite reasonable use of it. I created a service in my init.rc, which runs a script ('/system/xbin/resetmac.sh') that turns Wi-Fi off and resets the original MAC address by writing an invalid one ('13:37:13:37:13:37') into the '/efs/wifi/.mac.info' file. This runs whenever I push 'volume down' (114), 'volume up' (115) and 'power' (116) buttons simultaneously. (I had to disable bugmailer first.) You can find keycodes in '/system/usr/Generic.kl'.
- Example code ('init.rc'):
Code:
service resetmac /system/bin/sh /system/xbin/resetmac.sh
class main
disabled
oneshot
keycodes 114 115 116
- Example code ('/system/xbin/resetmac.sh') (chmod it to 700):
Code:
svc wifi disable
echo 13:37:13:37:13:37 > /efs/wifi/.mac.info
What do I need to enable it in my kernel?
- Simply enable 'Device Drivers->Input device support->Miscellaneous devices->Key chord input driver support' in menuconfig.
- Of course it has advantages only if you enable something in your init files too.
Wi-Fi MAC address changing
Please refer my previous thread for more information and on how to use/implement it.
Every custom modification to devices have risks. Use these at your own risk!
Have fun and enjoy!
---reserved---
---another one---
I'm on Frankenstein ROM 4.0.2 and ardatdat 4.2b4 right now, is it safe to flash your kernel plus bln mod directly,and do I need to mount/system before flashing and clear cache and dalvik cache after???
Sent from my GT-I9103 using Tapatalk 2
khpatel4991 said:
I'm on Frankenstein ROM 4.0.2 and ardatdat 4.2b4 right now, is it safe to flash your kernel plus bln mod directly,and do I need to mount/system before flashing and clear cache and dalvik cache after???
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
I'm on that rom too. It is safe.
Sent from my GT-I9103
I flashed the kernel,wiped cache and dalvik cache, downloaded bln mod pro but not able to understand the patch part,can you explain the procedure in detail,about how to apply the patch
Sent from my GT-I9103 using Tapatalk 2
khpatel4991 said:
I flashed the kernel,wiped cache and dalvik cache, downloaded bln mod pro but not able to understand the patch part,can you explain the procedure in detail,about how to apply the patch
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
You don't have to patch anything. That part id for kernel devs. My kernel already contains it.
Sent from my GT-I9103
This is awesome bud !
I'm yet to try cause I have to use NTFS pen drives during the next few days, will flash it after that. I had a small request if possible look into it.
I was going through dev sicopat's threads & I found that he had enabled BLN for the stock SMS app by modding it. The link to the MOD is currently down as it was uploaded on multiupload which had shut down for some time. But I'm searching for an alternate link, will notify you if I find one.
Here's the link to the ROM's thread: http://forum.xda-developers.com/showthread.php?t=1164516 (Check Post no. 2, Updates: v3.0).
If possible can you MOD the stock ICS SMS, stock ICS Samsung Email app(not Gmail) / Social Hub for enabling BLN in them ? As per Sicopat's thread as of now this can't be enabled even if we download the BLN Control Pro app & we've to use 3rd party apps. Maybe you can get in touch with him to enable the same.
Hope it'll be possible for you to do so. Cheers !
First of all thanks Adam. This is a long awaited MOD; I have been missing notification LEDs since my change from HTC to SGR.
I have installed your zip through CWM, wiped cache and dalvik cache and bought BLN control app.
The test looks fine, but I have yet to get it to work with an SMS application. I still just use the stock application which doesn't give LED notification.
But I experienced an issue with the modded kernel related to touch. It however disappeared after having the screen off for a few minutes.
When I held icons and try to move them to another position, it lost my touch after 1-1½ second. Similarly I couldn't flick halfway to a new page and hold it there for more than 1½ second.
I'll give an update if it comes back, but this is the first time I have experienced such an issue, and therefore I expected it to be related to this modification.
BR, MHCA
mhca said:
But I experienced an issue with the modded kernel related to touch. It however disappeared after having the screen off for a few minutes.
When I held icons and try to move them to another position, it lost my touch after 1-1½ second. Similarly I couldn't flick halfway to a new page and hold it there for more than 1½ second.
Click to expand...
Click to collapse
Hm, I haven't experenced such problem yet. Pls update me on this when it happens one more time and I'll investigate on it.
Sent from my GT-I9103
I'm really happy with BLN. Thanks!
It would be great if merged to a voodoo kernel.
Sent from my GT-I9103 using xda app-developers app
Thanks Adam, you are the one!
May I ask for your permission to add the BLN modification to my kernel? Thanks very much.
---------- Post added at 02:29 AM ---------- Previous post was at 01:53 AM ----------
I will try to implement it in my kernel. Thx.
Sent from my GT-I9103 using xda premium
ardatdat said:
May I ask for your permission to add the BLN modification to my kernel? Thanks very much.
Click to expand...
Click to collapse
Of course! I'm happy that you find them useful.
Sent from my GT-I9103
Adam77Root said:
Hm, I haven't experenced such problem yet. Pls update me on this when it happens one more time and I'll investigate on it.
Sent from my GT-I9103
Click to expand...
Click to collapse
I just experienced issues again. It is quite annoying when trying to hold down a key on the keyboard to type a number instead of a letter. Failed multiple times.
I then tried holding home screen icons and most of the times it just opened the application as if I had clicked them.
I don't know how you will be able to investigate it, such things can probably be hard to replicate.