[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

android_htc

Senior Member
Feb 24, 2011
479
223
Is the device actually charging via USB (see pics attached)?

Note: after 36 mins, there was no difference in charge (tab was not used during this time)!?

Voodoo works great, thanks.

Sent from my GT-P7500 using Tapatalk 2
 

Attachments

  • uploadfromtaptalk1345089472514.jpg
    uploadfromtaptalk1345089472514.jpg
    34.7 KB · Views: 1,725
  • uploadfromtaptalk1345089584284.jpg
    uploadfromtaptalk1345089584284.jpg
    34 KB · Views: 1,666
Last edited:

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Is the device actually charging via USB (see pics attached)?

Note: after 36 mins, there was no difference in charge (tab was not used during this time)!?

Voodoo works great, thanks.

Sent from my GT-P7500 using Tapatalk 2

It did work for me while i was watching tv last night. (My tab had the screen off and nothing in the backgroud.) Was there something running in the background or was the screen on? Usb charging in general tends to be slow (.5 amps instead of 2 amps). My battery % stays still and drops a few % after a while when i use my tab as a portable dvd player when being charged by my car charger.
 

durius

Senior Member
May 10, 2004
594
31
59
Peso da Régua
Hi,
I installed this kernel on new deodexed and rooted ICS ROM. all working fine but voodoo that I cannot see where to find the settings.

If a kind soull could point me in the right direction...

Thanks
 

XTeK2

Senior Member
Oct 3, 2010
163
55
Częstochowa
www.modaco.pl

kashortiexda

Senior Member
Jan 12, 2011
1,431
893
usb looks like it's charging but I think it's only the indication, it doesn't actually seem to be charging

Sent from my GT-I9300 using Tapatalk 2
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Samevresults for me, it doesn't actually drop, but it doesn't go up either.

Sent from my GT-P7500 using Tapatalk 2

I had the same results on pershoot's ics kernel around mid June when I used my tablet as a portable dvd player for a few hours. (This screen sure beats the real portable DVD player I have.) I did go back and revise a few more lines of code. I'm currently testing the new changes by letting the tablet run TMNT its own enjoyment while I tinker with OC. I also had it do a few antutu benchmarks since I figure videos/benchmarking should be battery consuming. So far I am just having it not drop.
 
  • Like
Reactions: RavenY2K3

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Can i return to stock kernel if all isnt good? So where can i find a ics stock kernel ?

Yes you can. I had to for trials 1-5 (notice that V1.0 is trial 6, V1.1 is trial 8 and V1.2 will be at least trial 18). Download Task650's ics rom and extract boot.img from the zip file and put it in the sdcard root directory. In the terminal run

Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p3
 

CazeW

Senior Member
Nov 14, 2008
869
457
Can i return to stock kernel if all isnt good? So where can i find a ics stock kernel ?

Yes you can. I had to for trials 1-5 (notice that V1.0 is trial 6, V1.1 is trial 8 and V1.2 will be at least trial 18). Download Task650's ics rom and extract boot.img from the zip file and put it in the sdcard root directory. In the terminal run

Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p3

Or put the boot.img in a tar and flash with Odin or restore boot from CWM if you've made a backup.


I've been trying to compile my own kernel so that I could be of some help figuring out some of the things but so far I haven't been able to get it booting. I don't know if it's because of my config file or because I'm using Ubuntu 12.04 (or something else entirely), but during compiling I get a lot of warnings for some of the tegra files which I'm guessing are the reason why I'm getting stuck at the Samsung logo.
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Or put the boot.img in a tar and flash with Odin or restore boot from CWM if you've made a backup.


I've been trying to compile my own kernel so that I could be of some help figuring out some of the things but so far I haven't been able to get it booting. I don't know if it's because of my config file or because I'm using Ubuntu 12.04 (or something else entirely), but during compiling I get a lot of warnings for some of the tegra files which I'm guessing are the reason why I'm getting stuck at the Samsung logo.

Did you remember to use some kind of arm toolchain and set the path to the compile utilities? I just downloaded the one pershoot recommended on git. Also, I'm not attempting to put the kernel and initramfs together anymore. I just used pershoot's zip flasher which can combine initramfs and the kernel on the fly. Also, DO NOT use menuconfig to edit the .config. Switch the n's, m's, y's by hand. Menuconfig somehow messes up the config. Take a look my configs. Sometimes you need to enable the p3 and not p4 stuff even though the model name of the galaxy tab 10.1 is p4wifi/p4. Warnings are normal. I just ignore them.

PS: you were helpful in getting voodoo sound working. I put you in the credits.
 
  • Like
Reactions: CazeW

enmriley

Senior Member
Mar 11, 2009
150
16
Can someone clarify, if I am running the Sammy push of ICS and rooted with SuperSU, will this kernel work? Some of the threads regarding other custom ROMs has me wondering. Maybe I missing something in the OP.

Thanks
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Can someone clarify, if I am running the Sammy push of ICS and rooted with SuperSU, will this kernel work? Some of the threads regarding other custom ROMs has me wondering. Maybe I missing something in the OP.

Thanks

Yes, this kernel is designed to work with a Samsung stock ICS rom AND NOT a cyanogenmod rom. I have no idea what will happen if you flash it on a cm rom.
 

RavenY2K3

Senior Member
Nov 13, 2006
1,459
439
Well done for getting the 1.2GHz working, it's amazing that there is such a difference made from adding an extra 400MHz to the overall power. Just a quick question, do you know what the default govenor and schedueller is?

Sent from my GT-P7500 using Tapatalk 2
 

CazeW

Senior Member
Nov 14, 2008
869
457
Well done for getting the 1.2GHz working, it's amazing that there is such a difference made from adding an extra 400MHz to the overall power. Just a quick question, do you know what the default govenor and schedueller is?

Sent from my GT-P7500 using Tapatalk 2

For default Samsung configuration it seems to be userspace and CFQ.


EDIT: Tested with a different config file but had no luck booting up. I'm guessing there's just something wrong with my toolchain.
 
Last edited:
  • Like
Reactions: RavenY2K3

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
For default Samsung configuration it seems to be userspace and CFQ.


EDIT: Tested with a different config file but had no luck booting up. I'm guessing there's just something wrong with my toolchain.

How exactly do you compile your kernel and assemble the zip file? I can sympatize with the clear lack of easy to find documentation. I think a lucky google search is important for people starting off new.
 

CazeW

Senior Member
Nov 14, 2008
869
457
How exactly do you compile your kernel and assemble the zip file? I can sympatize with the clear lack of easy to find documentation. I think a lucky google search is important for people starting off new.

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.
 
Last edited:

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.