[Kernel/Recovery][P75XX] A1 Kernel V1.9/TWRP2.6.3.0

Stuck After 1.3 on Samsung Screen?

  • No, and hope I never do.

    Votes: 179 82.9%
  • Yes, but I solved it by reflashing

    Votes: 8 3.7%
  • Yes, but I solved it by flashing V1.3 or older

    Votes: 8 3.7%
  • Yes, and had to reflash full stock

    Votes: 21 9.7%

  • Total voters
    216
Search This thread

Albertotuchi

Member
Jan 7, 2011
32
2
All ok

congratulations and thanks for the work, I flashed over my stock Ics rooted, and all working ok for this afternoon. After flashing the kernel the governor is interactive, and i don't know why but min and max working frequencies are set to 1000 mhz both. Changed then to 216 min and 1200max and all ok.

thanks again.
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
I used the package list from here for Ubuntu 12.04. The toolchain I downloaded from Google but I tried the toolchain on pershoots git and it's still the same. I use these commands before running make:
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=$PATH:~/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

For the config file I used samsung_p4wifi_defconfig and then manually edited it to enable Voodoo.
For the zip I just replace the modules and the zImage in one of pershoots old zip files.

Oh, goodness, that source.android.com page looks quite overwhelming. You don't really need anything from that page. I think that page is for if you're interested in building the entire android os from scratch and customizing/tweaking the os itself. I think that's beyond me. Here's how I did it.

1: Download the p7500 source from samsung
2: Extract the kernel.tar.gz somewhere. I just put it in my ~/Downloads folder
3: In the kernel source root look for a file called "Makefile". Open it and look for the line that says "CROSS_COMPILE ?=" (around line 196). Change the path after ?= to tool_chain_root/bin/(common prefix). In the case of the tool chain that I downloaded all files in toolchain/bin start with arm-none-eabi-blah,blah,blah. In this case, the prefix is arm-none-eabi-. In my make file the line reads: "CROSS_COMPILE ?= /home/Daniel/Downloads/arm-2010.09/bin/arm-none-eabi-"
4: Go to your kernel source directory and issue make samsung_p4_defconfig or make samsung_p4wifi_defconfig
5: Use pluma or any other text editor to open kernel_source_root/.config and copy the voodoo stuff related lines in from my config file. You will also need to make sure that wifi driver gets built in and not compiled as a module. Search for the line "CONFIG_BCM4330=m" and change it to =y. One last thing you need to edit is to make sure you build the p3 sound and not p4 sound. If you check the voodoo sound makefile it depends on p3 sound, not p4. Look for the line "CONFIG_SND_SOC_WM8994_P4=y" and change the P4 to a P3. Now, look at the line above or below called "# CONFIG_SND_SOC_WM8994_P3 is not set" and change that P3 to P4. This tells make that you had a change of heart and are no longer interested in the P4 module. DO NOT USE MENUCONFIG!!! This file must be edited by hand.
6: Do "make -jX clean" where X is the number of CPUs you have. My Core2 P8800 mobile has 2 cpus so I do "make -j2 clean"
7: Finally, make the kernel by issuing "make -jX". Same X as step 6.
8: Lastly, download one of my zip files and open it with some kind of zip utility and go to the kernel directory. Drag your zImage (found in kernel_source_root/arch/arm/boot) into there to replace mine.
9: Flash it and hope it works.
 
  • Like
Reactions: XTeK2 and Toldo

CazeW

Senior Member
Nov 14, 2008
869
457
Nope, still no luck. I'm starting to think that there's something wrong with the tools I installed. Or maybe the fact that I'm compiling in VirtualBox messes it up.

UPDATE: Got it to finally boot, the problem seemed to be with the packages I had installed as it started working after I reinstalled Ubuntu and the packages.
 
Last edited:

jaswinky

Senior Member
Jun 24, 2009
730
134
USB Charging not working

Firstly, thanks a lot for this kernel... finally we have an overclocked kernel!!

I can confirm that it is true that USB charging from any charger/port doesn't work, it just changes the error charging icon by the normal charging icon.

At first i thought that mayby the people had tested it tried in a PC port with only 0,5A and it just saved the charge, but I tried it in a 2A port from a external travel battery which I usually use with a small USB wire adaptor to use with the samsung tab to simulate a samsung charger. I connected the tab (at 75% bat) to the battery directly (without the samsung-sim adapter) and after 30 mins it still had 75%. After this I conected it to the battery using the adapter (same effect as if you connect it to the original samsung charger) and in only 5 mins it got 78% bat...

Anyway, we have our tab at 20% faster, so thanks!!
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Firstly, thanks a lot for this kernel... finally we have an overclocked kernel!!

I can confirm that it is true that USB charging from any charger/port doesn't work, it just changes the error charging icon by the normal charging icon.

At first i thought that mayby the people had tested it tried in a PC port with only 0,5A and it just saved the charge, but I tried it in a 2A port from a external travel battery which I usually use with a small USB wire adaptor to use with the samsung tab to simulate a samsung charger. I connected the tab (at 75% bat) to the battery directly (without the samsung-sim adapter) and after 30 mins it still had 75%. After this I conected it to the battery using the adapter (same effect as if you connect it to the original samsung charger) and in only 5 mins it got 78% bat...

Anyway, we have our tab at 20% faster, so thanks!!

Just wondering, has anybody tried the usb charging with the tablet turned OFF?
 
  • Like
Reactions: jaswinky

jaswinky

Senior Member
Jun 24, 2009
730
134
Just wondering, has anybody tried the usb charging with the tablet turned OFF?

My test was with the tablet turned on but the screen off, so in 30 mins from 75% to 75%... something wrong...

Anyway, I'm just making the test again, the tab turned off (69% bat), connected to the external travel battery (2A port) without the wire-adaptor (samsung charger simulator), it is, directly as any non samsung charger. I'll tell you the results in 15 mins (at least 1% should be charged!!)

Thanks for your work!

EDIT: After turned off, when the connector was pluged, the charging battery figure appeared ok in the center of the screen... lets see if it really charges.

---------- Post added at 03:32 AM ---------- Previous post was at 03:08 AM ----------

Just wondering, has anybody tried the usb charging with the tablet turned OFF?

YES, it charges with the tablet turned off from any non samsung USB charger !!!!! From 69% to 77% in 20 min...

Thanks my friend!!!

But why it charges with the tablet turned off and not with the tab turned on??? Maybe any other firmware check that cannot be made with the tab turned off???
 
Last edited:

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
YES, it charges with the tablet turned off from any non samsung USB charger !!!!! From 69% to 77% in 20 min...

Thanks my friend!!!

But why it charges with the tablet turned off and not with the tab turned on??? Maybe any other firmware check that cannot be made with the tab turned off???

I just got the idea, turned off my tablet and came back after a little while. I left it plugged into my trusty laptop that compiles these kernels. Went up from 80% to 93%, so nice to confirm that somebody else is getting these results.

Could be several reasons why. I reexamined the code, downloaded the honeycomb sources and pershoot's p3_battery.c and ran a diff. Pershoot seems to have added an extra function that I'm not sure what it does. However, I think I got most of the changes related to usb charging. Here are several reasons why I think it only works turned off:

1: Could be that powered on it uses as much energy as the usb charging supplies making a net gain of 0% for the battery. I let my tablet watch a few episodes of TMNT for its own enjoyment with the screen on full brightness. % didn't go down but didn't go up either. Not sure if that's conclusive evidence but it's something to keep in mind.

2: There is some other code in the rom that overrides my bypass of the disabled usb charging. What motivation could be behind this? I can think of only 1 reason: if you loose your adapter or you accidentally step on it or some other unfortunate event breaks it you're forced to buy a new one and not go cheap and use another adapter. Can't really confirm this one.

3: Some other kernel driver code prevents usb charging that is only active during regular mode and not charging mode. I could confirm this one but that would require an awful lot of comparing. Somebody else bored (almost to the point of death) and want to verify this?
 

CazeW

Senior Member
Nov 14, 2008
869
457
I managed to get Voodoo working but my overclocks were unstable. 1.2GHz seemed to work at first but the tab refused to wake up after it went to sleep (this was with the 1.4GHz code) and 1.4GHz crashed the tab the instant I tried overclocking to it. I checked your broken 1.4GHz code and it was exactly the same as mine so we're stuck at the same place.

UPDATE: Got 1.4GHz running for a while so that I could do some very quick benchmarks. Still very unstable but should be now down to just finding the correct voltages.
 
Last edited:

Ziq666

Member
Jun 11, 2010
16
1
I had the same issue with not charging with pershoots kernel on 3.2 (Tasks rom)..

Skickat från min GT-I9100 via Tapatalk 2
 

jaswinky

Senior Member
Jun 24, 2009
730
134
I just got the idea, turned off my tablet and came back after a little while. I left it plugged into my trusty laptop that compiles these kernels. Went up from 80% to 93%, so nice to confirm that somebody else is getting these results.

Could be several reasons why. I reexamined the code, downloaded the honeycomb sources and pershoot's p3_battery.c and ran a diff. Pershoot seems to have added an extra function that I'm not sure what it does. However, I think I got most of the changes related to usb charging. Here are several reasons why I think it only works turned off:

1: Could be that powered on it uses as much energy as the usb charging supplies making a net gain of 0% for the battery. I let my tablet watch a few episodes of TMNT for its own enjoyment with the screen on full brightness. % didn't go down but didn't go up either. Not sure if that's conclusive evidence but it's something to keep in mind.

2: There is some other code in the rom that overrides my bypass of the disabled usb charging. What motivation could be behind this? I can think of only 1 reason: if you loose your adapter or you accidentally step on it or some other unfortunate event breaks it you're forced to buy a new one and not go cheap and use another adapter. Can't really confirm this one.

3: Some other kernel driver code prevents usb charging that is only active during regular mode and not charging mode. I could confirm this one but that would require an awful lot of comparing. Somebody else bored (almost to the point of death) and want to verify this?

Ok. I've reviewed your code p3_battery.c and I saw your changes with info.batt_improper_ta and others. It should be correct, this var never will be 1, so, the problem maybe is in other place... I've seen that depending of the port, it enable 2A max or 0,5A, this is, if it detects a dedicated charger, will enable 2A charging; if it detects a data USB port (as PC USB port), will only enable 0,5 A, maybe enought for maintain the charge but not enought to charge the battery (I think this is the situation I suffer yesterday). Because any reason, I think when we connect a external battery or maybe a non-samsung wall charger, it detects as a USB port and only enable 0.5A charging instead of 2A. This is also in p3_set_chg_en function you edited, some few lines down your //battery->info.batt_improper_ta = 1; line, when battery->current_cable_status is not CHARGER_USB, p3_set_charging(battery, 2); should be changed also to p3_set_charging(battery, 1);, it is, where it says:

static void p3_set_chg_en(struct battery_data *battery, int enable)
{
...

else if (battery->current_cable_status ==
CHARGER_USB) {
pr_info("USB charger!!");
p3_set_charging(battery, 1);
//gpio_set_value(charger_enable_line, 0);
} else {
pr_info("else type charger!!");
p3_set_charging(battery, 2);
gpio_set_value(charger_enable_line, 0);
}
...
}

change by this:

static void p3_set_chg_en(struct battery_data *battery, int enable)
{
...

else if (battery->current_cable_status ==
CHARGER_USB) {
pr_info("USB charger!!");
p3_set_charging(battery, 1);
//gpio_set_value(charger_enable_line, 0);
} else {
pr_info("else type charger!!");
p3_set_charging(battery, 1); /* the change here */
gpio_set_value(charger_enable_line, 0);
}
...
}

I haven't any compiler (I'm using wordpad to read the code!!), so I cannot test it... If you want to compile this changes (from ver 1.2 trial 19), I'll test it.

Regards,
 
Last edited:

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
I managed to get Voodoo working but my overclocks were unstable. 1.2GHz seemed to work at first but the tab refused to wake up after it went to sleep (this was with the 1.4GHz code) and 1.4GHz crashed the tab the instant I tried overclocking to it. I checked your broken 1.4GHz code and it was exactly the same as mine so we're stuck at the same place.

UPDATE: Got 1.4GHz running for a while so that I could do some very quick benchmarks. Still very unstable but should be now down to just finding the correct voltages.

What voltages did you try? I tried to keep in on stock and I tried the pershoot ones starting at 900mv cpu but neither one worked for me.
 

CazeW

Senior Member
Nov 14, 2008
869
457
What voltages did you try? I tried to keep in on stock and I tried the pershoot ones starting at 900mv cpu but neither one worked for me.

Pershoots voltages crash instantly. I'm currently trying with stock for core and different ones for cpu. At best it has stayed stable for about 2mins when running the stress test in SetCPU.
 

jaswinky

Senior Member
Jun 24, 2009
730
134
Pershoots voltages crash instantly. I'm currently trying with stock for core and different ones for cpu. At best it has stayed stable for about 2mins when running the stress test in SetCPU.

In my setcpu i have no options for voltage settings...

Enviado desde mi GT-P7510 usando Tapatalk 2
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
In my setcpu i have no options for voltage settings...

Enviado desde mi GT-P7510 usando Tapatalk 2

Voltages are hard coded in. This is what sucks about trying to find the right voltage. You edit the file for a few seconds and wait 10 minutes for it to compile. Doesn't work? Repeat the cycle... :(
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
change by this:

static void p3_set_chg_en(struct battery_data *battery, int enable)
{
...

else if (battery->current_cable_status ==
CHARGER_USB) {
pr_info("USB charger!!");
p3_set_charging(battery, 1);
//gpio_set_value(charger_enable_line, 0);
} else {
pr_info("else type charger!!");
p3_set_charging(battery, 1); /* the change here */
gpio_set_value(charger_enable_line, 0);
}
...
}

I haven't any compiler (I'm using wordpad to read the code!!), so I cannot test it... If you want to compile this changes (from ver 1.2 trial 19), I'll test it.

Regards,

Coming right up...See version 1.2.1. Now the same kernel should work on 3G and wifi.
 
Last edited:
  • Like
Reactions: jaswinky

jaswinky

Senior Member
Jun 24, 2009
730
134
Coming right up...See version 1.2.1. Now the same kernel should work on 3G and wifi.

Lets try... ill tell you in a few minutes...

1.2.1 Installed in wifi only tablet. Everything ok I think... Now testing the change in p3_battery.c code, 81% bat, the tablet tunred on with screen off and no user activity... I'll tell you in 10 min...

Thanks!

Enviado desde mi GT-P7510 usando Tapatalk 2
 
Last edited:

jaswinky

Senior Member
Jun 24, 2009
730
134
Coming right up...See version 1.2.1. Now the same kernel should work on 3G and wifi.

Sorry man... :crying: The minor change in p3_battery.c code didn't work for me... it doesn't still charge with the tablet turned on from a non-samsung charger...the change apparently haven't any effect... the issue must be in a different point... Maybe you should prefer to undo the minor change for this or the next version.

Everything else working fine...

Thanks!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 187
    :good: First of all :good: Thank you for your patronage!!! :D:cowboy::laugh::victory:

    Before you do anything: This is purely at your own risk and I will not be responsible for anything that happens to your tablet. I flashed it on mine at my own risk.

    Compatibility Information: There are 2 different versions. 1 for stock and 1 for Cyanogenmod. Even though the kernels are intended for the 3G tablet it will work just fine on a WiFi only tablet (like mine). This makes the build process less messy.

    **Sources Fully documented v1.9 beginner friendly sources now available including the build script. If more explanations are required, please say so. However, remember that the explanations are not intended to be a blind step by step instructions of going from samsung source to A1.

    TWRP V2.6.0.0: Please read: do not worry about any kind of "E:A: Render Error". This is a side effect of removing some image files to save place on the recovery image so it will fit on the 5MB. The error simply means it failed to show (render) and image file that it is looking for. This is not harmful at all. If you can't flash the recovery please try the dd method.

    TWRP V2.6.3.0: There are no more E:A Render errors. All graphics that were removed are there. Also, the recovery will install supersu if no root is detected. That feature has also been restored. The kernel has been stripped of anything not recovery related to shrink it down. It also has selinux support which allows the "set_metadata" zip installation to work. The download is in the attachments below.

    Changelog:
    Changelog:
    • Voodoo sound <-- new to version 1.0
    • USB charging enabled as well as charging from other chargers *** fixed V1.5.4 thanks to pershoot
    • Overclock to 1.2GHz <-- new to version 1.2
    • NTFS modules enabled, ondemand default frequency scaler, noop default disk io scheduler <-- new to version 1.2.1
    • GPU overclock from 333MHz to 400MHz. <-- new to version 1.3
    • Overclock to 1.4GHz <--new to version 1.4
    • Support for Current Widget <-- new to version 1.5
    • CIFS enabled in kernel config, 1.4GHz attempted stability fix (thanks to jaswinky) <--new to version 1.5.2
    • Wifi driver compiled as module <--new to V1.5.3
    • More voltage anomalies fixed, updated battery driver to pershoot's 3.1 <-- new to V1.5.4 and V1.5.5XE
    • Fixed charging boot bug <--new to V1.5.6SE
    • (In case you were wondering 1.5.7 had an issue in it.)
    • Disabled frequency lock, added 1GHz default max (you can change it to 1.2GHz or 1.4GHz after boot), 216MHz default min CazeW's suggestion <--new to 1.5.8SE+XE
    • Enabled pershoot build/vfp optimization commit, added 150MHz minimum frequency <-- new to 1.5.9SE+XE
    • Boot script support (put yours as /data/local/a1init.sh) <-- new to V2.0
    • Smarter ram disk that only initializes 3G on 3G tablets<-- new to V2.1
    • 1.5GHz && 1.6GHz OC available, cifs utf8 kernel module available <-- new to V2.2
    • Support for CM9 <-- new to V2.2CM
    • Enabled xbox controller module as xpad.ko <--new to V2.2.1
    • NTFS moved to kernel module instead of built in, CIFS moved to kernel module instead of built in, enabled option.ko and usb_wwan.ko for connection of 3G dongle, all nls charsets/codepages built as modules <--new to V2.2.2
    • V1.6.3 is pretty much V2.2.2 but without my custom ram disk. I've also tried a boot script method proposed by Toldo but haven't had time to test it yet. Please flash the CM9 stock kernel or Samsung stock kernel before trying V1.6.3.
    • Applied git patch to disable mmc_cap_erase <-- new to V1.6.4
    • Voltage control, cifs built in again <-- new to V1.7
    • Galaxy Tab 8.9 specific fix <--new to V1.7.1
    • Cyanogenmod charging mode fix <--new to V1.7.2
    • Galaxy Tab 8.9 specific feature <--new to V1.7.3
    • CM10 compatibility fix, enabled Samsung's powersaving governor <--new to V1.7.4
    • followed pershoot's "-defconfig: jb: unset TEGRA_CONVSERVATIVE_GOV_ON_EARLYSUPSEND" change to fix odd 450MHz capping issue <--new to V1.7.4b
    • Copied in pershoot's keyboard dock driver <--new to V1.7.5
    • 801MB RAM enabled <-- new to V1.8
    • Rebased on pershoot's November 17 source <--new to V1.8.1
    • Back to samsung base, follow pershoot's suggestion of Nexus7 mtp drivers to fix mtp, enabled zRam <--new to V1.8.2
    • Reduced RAM to 785MB to prevent intense 3D games issue, enabled KSM (check in settings --> performance --> memory management)
    • (CM Version only) works on CM10.1 <--new to V1.8.4
    • Incorporated touchscreen death fix. Thank the user who reported it. <-- new to V1.8.5
    • Used part of pershoot's kernel config to get data usage working in CM <--new to V1.8.6
    • Added CM's version of the ROW (read over write) disk IO scheduler for GT-I9300<-- new to V1.8.7
    • Added XDA's grzwolf's solution to the hsic wakeclock problem <--new to V1.8.8
    • Added frandom kernel module <-- new to V1.9
    Credits:
    Supercurio: voodoo sound
    Pershoot: voodoo port, usb charging, flashable zip, OC template, current widget setup
    XDA forum's CazeW: used your replace suggestions to patch up wm8994_voodoo.c and wm8994_voodoo.h so it will compile properly, and finding the missing link for 1.4GHz OC, and disabling frequency locks
    Task650: providing a nice, clean deodexed rom for me to try this on
    XDA forum's RaymanFx: OC instructions
    Me: GPU OC
    XDA forum's jaswinky for valuable hints and checking my work over.
    Xoom ICS kernel: for getting an approximate idea of voltages
    (If I missed any credits, please forgive me as this is my first attempt at any kind of development)
    XDA forum's motley for voltage control
    XDA forum's Unknownzd for mmc_cap_erase patch
    XDA's grzwolf for the hsic wakelock fix
    11
    Very Good News

    So it looks like CM10.2 is actually alive and in testing on my tablet. Big thank you to user epinter for helping me with the graphics issue. I will play with CM10.2 to see how it is. First 10 seconds impression: buttery smooth, wifi works, bluetooth works, sound works, A1 kernel with SELinux firing on all cylinders! Unfortunately it has the 2 bar UI... time to search for that post on how to make tabletui.

    Please donate to epinter for CM10.2. He gets the credit for making it work. I just did some minor tweaking to the fstab and audio flinger.

    Gotta go to bed. Just check out the screenshot zips to see it working. I have no time adjust the sizes for xda.

    THE ZIP IS THE SCREENSHOTS, NOT THE ROM. I will post the rom later this week after testing.
    10
    Honeycomb Tablet Mode Partial Fix

    Hey everyone,

    I managed to figure out how to get the classic honeycomb tablet mode to work in CM10.1 (mostly). You know, the one where you get 1 status bar for the soft buttons and tray. Simply move the jars to /system/framework and the apk to /system/app. Do this with any root explorer or the terminal.

    I tried to make a flashable zip, but I managed to screw the permissions in the process and accidentally pull the plug on my computer, corrupting its data partition. I did setup my Linux install to have a system (/) and data partition (/home) like android.

    The only down side is that you can't customize the power widget but, on the upside, the UI seems noticeably less laggy than the stock CM10.1 UI with the 2 bars. Why??? Who knows. I think this benefit more than justifies the small annoyance of unchangeable toggles.

    Here are the instructions I followed: http://xdaforums.com/showpost.php?p=28957307&postcount=1, http://xdaforums.com/showpost.php?p=36319776&postcount=974.

    Last gotcha, it's for wifi only since that's what I have and I don't really want to wait for my computer to compile a whole other rom for the 3G version. (Have mercy on the Core2 mobile).
    8
    Great to see someone else kernel developing, could be the start of something here... Lol, I wanna give this a try but I think It'll stop 3G working if I flash the 7510 kernel.

    Sent from my GT-N7000 using Tapatalk 2

    Care to try the 3G version I just uploaded? I don't own the 3G version but I followed the same idea for compiling the 3G kernel.
    7
    Please do not advertise your roms in my kernel thread. This thread is mainly for bug reports and feature requests. Thank you for your understanding. (I did not advertise my A1 in pershoot's kernel thread saying "hey you want some of these features on stock rom, try my kernel". ) I will fix V2.0 to use a 3G ramdisk so 3G tablets will be able to use boot scripts later today.