VPNC works wonderfully on both the stock kernel and this kernel. I tested both WIFI and Bluetooth tethered VPN. Looks like advanced routing is also working. Thank you! I hit the thanks button.
[GT-P6210][KERNEL][UV/OC]garyd9's GT-P6210 kernel (updated 2012-01-23)
- Thread starter garyd9
- Start date
-
- Tags
- development
VPNC works wonderfully on both the stock kernel and this kernel. I tested both WIFI and Bluetooth tethered VPN. Looks like advanced routing is also working. Thank you! I hit the thanks button.
Hi Gary,
I wanted to share with you some observations on my usage hoping they are helpful. I am running your kernel on a GT-P6210 16GB running UEKL1. Starting with the 0105 version I am also running a custom boot animation and SetCPU at 1400MHz.
When I upgraded to 0107 I noticed some difficulty switching wifi access points. I primarily bounce between two access points (my house and my dad's house) and my iPhone (using the built in tethering). I found that it would not recognize a new access point when I moved or when the Tab went to sleep (I have Wifi turning off when sleeping), requiring me to turn off wifi and turn it on again. That fixes the connection problem.
As a test I reverted back to the 0105 kernel and the connection problems went away. The Tab recognizes the new access point, and even coming out of sleep it attaches to my iPhone with no issues. Is there something between these two versions that could cause this, or do you think I have something else that is causing my problem?
Thanks!
I wanted to share with you some observations on my usage hoping they are helpful. I am running your kernel on a GT-P6210 16GB running UEKL1. Starting with the 0105 version I am also running a custom boot animation and SetCPU at 1400MHz.
When I upgraded to 0107 I noticed some difficulty switching wifi access points. I primarily bounce between two access points (my house and my dad's house) and my iPhone (using the built in tethering). I found that it would not recognize a new access point when I moved or when the Tab went to sleep (I have Wifi turning off when sleeping), requiring me to turn off wifi and turn it on again. That fixes the connection problem.
As a test I reverted back to the 0105 kernel and the connection problems went away. The Tab recognizes the new access point, and even coming out of sleep it attaches to my iPhone with no issues. Is there something between these two versions that could cause this, or do you think I have something else that is causing my problem?
Thanks!
When going back and forth between kernels, are you changing anything else at all?
The problem is that the wifi stuff is actually isolated from the kernel in a precompiled module that I can't get the source for. There are actually two parts to it: ar6000.ko and wpa_supplicant. Neither is being touched by the kernel change (and can't be - I don't have the source for either to even recompile them.)
I'm looking at my commit log, and nothing changed between 05 and 07 that would have any impact whatsoever on wifi. There's a change with the j4fs module (file system module), adding a parameter for a reboot commandline, and a change with the logging done by the graphics driver. That's it.
One thing that MAY help (or may not) is to get back to the 07 kernel, and delete and reconfigure the wifi AP's. That shouldn't have any impact, but... it'd be interesting if it did!
Take care
Gary
FYI, I don't think there is anything Samsung-specific in wpa_supplicant - Dropping compiled ones from AOSP source is fairly common on other devices (usually for the purposes of adding adhoc wifi support).
The version on this tablet has a proprietary AR6003 driver compiled in... Not sure if they put anything samsung specific in it, but there's certainly atheros specific stuff in there.
Posted on the 24th:
20120123: (actually posted on the 24th)
These are mostly small changes that are working towards stability. They've improved my own stability, and at least one other person who had a microSD card related SOD issue.
Take care
Gary
20120123: (actually posted on the 24th)
- Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
- Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
These are mostly small changes that are working towards stability. They've improved my own stability, and at least one other person who had a microSD card related SOD issue.
Take care
Gary
Is anyone using init.d folder? Thought the kernel supported init.d but can't seem to find a way to get it work. Any tips?
Thanks,
Sent from my GT-P6210 using xda premium
Thanks,
Sent from my GT-P6210 using xda premium
It does support it... Well, it should.
I'm assuming that you are trying to do something that isn't working? If you tell me what that is, perhaps I can try to repeat and figure out what's going wrong. Take care
Gary
It does support it... Well, it should.
I've been using System Tuner Pro for CPU tweaks with built in init.d scripts function. The app gives me options in applying the tweaks between on boot complete and init.d. However the init.d option ws not available, so I manually created the folder in /system/etc/ which made the init.d option appear, but kept getting error message and doesn't create the script.
Thanks,
Sent from my PG86100 using xda premium
Ah, so it's not a matter of the kernel support, but something else. I still may be able to help. What error are you getting from "System Tuner Pro"?
(As a test, I just manually created the init.d directory and put a script in there - and it worked fine when I rebooted.)
take care
Gary
OK I'm not pointing the finger completely at this kernel but I have a feeling what happened to my tablet today has to do with the recent changes.
I was sitting class today and I used my tablet a couple times. At one point it froze so I restarted it be holding down the power button and continued what I was doing (which was putting a date on the calender). About an hour later I went to go check my facebook only to find my tablet on the screen when it starts where it just Says Samsung Galaxy Tab 7.0 Plus. NOT the animated loading screen.
It just sat there doing nothing. So I went into recovery only to find it couldn't access anything on the internal SD card. I'm assuming the internal SD card is E: since at the bottom of the recovery screen it was trying to mount E: or something along those lines. I did a Dalvik cache clean and still nothing. I then did a data/factory reset and still nothing.
Then just to verify my assumption I went to install from SD card and selected select zip from sd card (which would be the internal one) and it couldn't access it.
So at this point I'm going to try Odin and go back to the previous kernal from the 7th since that was stable and I wasn't getting SOD's.
Edit:
Just to add my apologies. I'm assuming you would want some files from me and I would love to contribute but unfortunately I use this tablet for school use so this thing needs to work. I would try working with you but my main concern is getting this thing up and running again.
Again my apologies.
Edit number 2:
Well this isn't good... Odin flash didn't work and I still somehow am having trouble accessing E: (which I am still assuming is the internal SD card) trying other things now :/
Last edited:
Well I'm kinda screwed...
OK in terms of the problems (and my previous post) I think your kernal change corrupted my internal SD card. I haven't been bbale to do anything with it and now it just automatically goes into recovery.
I have done multiple odin flashes using various settings. I was going to put up pictures but they were blurry beyond belief. so I'm going to type out everything...
Beginning: (note the blue text is normally yellow on the tab but on here you can barely see it so I made it blue)
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
-- Updating application...
E:failed to mount /efs (No such file or directory)
instal_application_for_customer:Can't mount /efs
copy application failed.
--Appling Multi-CSC...
E:failed to mount /efs (No such file or directory)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (no such file or directory)
I'm already trying to get into contact with Samsung since I don't think much can be done :/ Strange that it happened out of no where though
OK in terms of the problems (and my previous post) I think your kernal change corrupted my internal SD card. I haven't been bbale to do anything with it and now it just automatically goes into recovery.
I have done multiple odin flashes using various settings. I was going to put up pictures but they were blurry beyond belief. so I'm going to type out everything...
Beginning: (note the blue text is normally yellow on the tab but on here you can barely see it so I made it blue)
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
-- Updating application...
E:failed to mount /efs (No such file or directory)
instal_application_for_customer:Can't mount /efs
copy application failed.
--Appling Multi-CSC...
E:failed to mount /efs (No such file or directory)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (no such file or directory)
I'm already trying to get into contact with Samsung since I don't think much can be done :/ Strange that it happened out of no where though
te same thing happened to mine a couple weeks ago. I was on an earlier version of the kernel and am pretty positive it played no part. I had progressively frequent sod's first. Did you have any other issues? I had to exchange mine. Never could get it to mount the memory.OK in terms of the problems (and my previous post) I think your kernal change corrupted my internal SD card. I haven't been bbale to do anything with it and now it just automatically goes into recovery.
I have done multiple odin flashes using various settings. I was going to put up pictures but they were blurry beyond belief. so I'm going to type out everything...
Beginning: (note the blue text is normally yellow on the tab but on here you can barely see it so I made it blue)
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
-- Updating application...
E:failed to mount /efs (No such file or directory)
instal_application_for_customer:Can't mount /efs
copy application failed.
--Appling Multi-CSC...
E:failed to mount /efs (No such file or directory)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (no such file or directory)
I'm already trying to get into contact with Samsung since I don't think much can be done :/ Strange that it happened out of no where though
Thanks
Jason
Not I did not. Like I said I was using it a couple times during class then an hour later when I went to use it again this started. Though it did freeze once before when I opened the calender but I just restarted and continued what I was doing THEN that happened.
I think that is certainly your best bet. While I don't think that the kernel has corrupted your internal flash memory, obviously something is going wrong.I'm already trying to get into contact with Samsung since I don't think much can be done :/ Strange that it happened out of no where though
If something had corrupted your internal flash, ODIN should have corrected it, as I believe it will completely repartition the flash, reformat the partitions, etc. I can only take wild guesses as to what may or may not be going on. Your boot loader partitions appears to be working, as does your recovery partition.
As a side-note, there is no drive "e" on the device. If you see "E:" on the recovery console, it indicates an Error. (You might also see W: for warnings, etc.)
I wish you luck and hope things work out for you.
Take care
Gary
Hey!
Just found this thread. Flashed the kernel and everything seems fine. I'm wondering though - is it possible to enable USB fast charging on this kernel? Like from a computer? I tried a method they suggest for the 10.1 but it didn't work. Of course that said to use pershoot's kernel too, but there isn't one for this tab that I could find.
Does anyone know anything about enabling that for this tab? Its so hard to search, I keep getting results for the other galaxy tabs!
-Taylor
Just found this thread. Flashed the kernel and everything seems fine. I'm wondering though - is it possible to enable USB fast charging on this kernel? Like from a computer? I tried a method they suggest for the 10.1 but it didn't work. Of course that said to use pershoot's kernel too, but there isn't one for this tab that I could find.
Does anyone know anything about enabling that for this tab? Its so hard to search, I keep getting results for the other galaxy tabs!
-Taylor
That would be nice. I have a non-Samsung 2A charger and the tab charges really slow on it. I have tried 5 cables with it none of them will fast charge because it is looking for the feedback form the samsung charger.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
18USE THIS AT YOUR OWN RISK.
I am not installing this kernel on your device. I've even gone out of my way to not give clear directions on how to install it yourself. If you decide to install this kernel, you are assuming all risks involved with it.
WARNING: THIS KERNEL IS NOT FULLY COMPATIBLE WITH THE LA3 FIRMWARE UPDATE. USING THIS KERNEL WITH THE UPDATED VERSION WILL RESULT IN WIRELESS ETHERNET BEING DISABLED.
Welcome to my custom compiled kernel for the Samsung Galaxy Tab 7.0 (wifi only.) This kernel will ONLY work for the GT-P6210 model.
The kernel should be compatible with any stock firmware or anything custom that's derived from the stock firmware. (I refuse to call it a ROM. It's not Read Only.)
First, proper credit should go to Entropy512 and his SGH-i777 kernels. It's from that work I was inspired to do this, and from that work where I'm pulling ideas and changes (when compatible.) I'd give some credit to Samsung, but they only bothered to post partial source code, and didn't even bother to post it with the proper config flags.
The idea behind this kernel is and will be to make the device more efficient. Longer battery life while running more smoothly is a Good Thing. I don't care about benchmark scores. In case someone missed that, I DO NOT CARE ABOUT BENCHMARK SCORES. Anyone can tweak a system to get a better benchmark, but that doesn't mean it'll actually work better. Concern #1 is and should always be stability. While some tweaks will be added that allow a user to make the system unstable, they won't be the default.
Differences from stock currently include:
- Very slight speed increase in bootup, possibly in other areas
- Support for init.d script parsing on bootup
- A real busybox (with proper links) installed to /sbin (and therefore available to the system)
- Undervolting and minor overclocking support (via SetCPU)
- android ram_console support (useful for post-mortem of crashes.)
- standard boot animation support
- quicker charging with iphone chargers
If you choose to tinker with the processor voltages and/or clock speeds, there will be no support in this thread. None. Yes, I'm using it myself, but I won't even support myself if I screw things up. If you find an issue with this kernel, BEFORE you post about it here, re-test after reverting all the voltage and clock speeds back to default. If it works with the default clocks/voltages, then don't waste your time or mine by posting about it to this thread. It's not supported. You can destroy your tablet by messing with the voltages and clocks.
You'll need a separate tool for voltage and clock adjustments. The one I see most frequently used is "SetCPU" (http://xdaforums.com/showthread.php?t=505419.) I'm in no way affiliated with the author of that tool. You should be warned that SetCPU does not seem to be fully compatible with our tablets: There seems to be no way to bring up the menu in the program. If the program is "honeycomb compatible", this is likely due to the author making assumptions about screen dimensions on tablet devices (fairly common error.) Don't tell me about it. It's not my program.
ToDo:
- Find source for the ethernet module and replace it (which will also allow adding more generic optimizations to the kernel.)
- ethernet adhoc support (not really kernel specific, but not possible without the ethernet module...)
- Figure out what samsung changed in the LA3 kernel (and didn't publish) so I can get the kernel working with the firmware update.
- Probably not compatible with stock firmware updates. (won't fix.)
- NOT COMPATIBLE WITH LA3 FIRMWARE UPDATE!!
This is being released as an installable "update.zip" style installer. Stick the .zip file on your device, reboot into recovery, and install it from there. If this isn't enough information, please search and read the forums before changing your device kernel. (Flashing a .zip in recovery is a very basic skill that should be mastered early.)
Firmware Developers:
If you want to use it, please link to this thread and give clear indication of which version of the kernel you are including.
Legal:
This is based on the linux kernel, and therefore I'm including links to the modified source for the kernel (https://github.com/garyd9/linux_kernel_GT-P6210) and contents of initramfs (https://github.com/garyd9/initramfs_normal_GT-P6210)
PLEASE DO NOT MIRROR THE DOWNLOADS. IF YOU WANT TO REFERENCE THE KERNELS, PLEASE ONLY LINK TO THIS THREAD.4Change Log
20120128:
- Support for iphone charger detection - pull up to 750mA from detected iphone chargers (1500mA from the samsung charger, and 500mA from everything else including a computer USB port.)
- Testing USB "high current" charging. This is currently not enabled by default (and until I'm happy that it's stable and safe, I won't be documenting it.)
- Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
- Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
- disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
- add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
- Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
- added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
- It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
- added android ram_console support. After installing this kernel, if you reboot/crash, it should leave a file in /proc called "last_kmsg" that will show the last several kernel messages from before the reboot/crash.
- undervolting and overclocking support (only up to 1.4GHz)
- Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://xdaforums.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
- build compatible with stock ar6000.ko module
- init.d script support
- busybox in /sbin
- cleanup of kernel config to remove excess debugging (when possible)
4Weekend update. There might not be any more kernel updates for a week (unless there's something critical to do) as I want to spend time time trying to completely replace samsung's ethernet module...
20120107:
- disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
- add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
- Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
3updated...
20120105:
- added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
- It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
2new version:
20120101:
- undervolting and overclocking support (only up to 1.4GHz)
- Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://xdaforums.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
