[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

djmatt604

Senior Member
Aug 1, 2012
1,756
1,847
Vancity
Re: [Kernel/Recovery/MOD][P75XX] A1 Kernel V1.8.4/TWRP2.3/Simple Mods

Alot of talk about TWRP in this thread. I wasnt sure if this was required.

Ive flashed it in cwm and it works fine. Thanks.

No problem! AA compiled twrp and it is available I'm the thread but isn't a requirement to use the kernel. Enjoy!

Sent from my Infamous Tab.
 

MrBrightside

Senior Member
May 8, 2009
75
4
Salzburg
I have a little problem: I installed twrp, but now when I try to install an update(cm 10.1) via recovery I'm unable to find the zip file in the storage. It seems that every folder is empty and I'm not even sure in which internal storage is located.

Thx in advance
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Re: [Kernel/Recovery/MOD][P75XX] A1 Kernel V1.8.4/TWRP2.3/Simple Mods

I have a little problem: I installed twrp, but now when I try to install an update(cm 10.1) via recovery I'm unable to find the zip file in the storage. It seems that every folder is empty and I'm not even sure in which internal storage is located.

Thx in advance

/data/media/0 that's where your sd card is.
 
  • Like
Reactions: MrBrightside

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
If someone still has the TWRP 2.3.3.0 for 3G can you please post it. I was cleaning up my hard drive a little while ago and accidentally kept v2.3.2.3 instead of V2.3.3.0 which caused that bug about having to manually navigate to /data/media/0. I still have the wifi on my tablet but I lost the 3G one.

Also, I'll probably put updated jars and the apk for the classic tablet ui mod sometime this weekend. Had another experiment I wanted to try last weekend. (No I didn't forget about this mod).
 
Last edited:

k1mu

Senior Member
Apr 11, 2011
1,945
1,620
Virginia
AAccount,
I have a patch that I'd like you to consider for your kernel builds.

There's a problem with the touchscreen chip in the Galaxy Tab where a firmware update fails. This leaves the chip in firmware update mode, meaning that it's not responding to screen updates. When this happens, you can recover from the problem by restarting the firmware update.
It's a simple fix to the mxt1386 driver - patch is available from http://www.rickmurphy.net/atmel_mxt1386_diff.txt

There's unfortunately a very easy way to get the chip broken - a simple
# find /sys -exec grep foo {} \;
command triggers the firmware update to start, then almost right away powers off the tablet. When you power it back on, the touchscreen is dead. Samsung claims that fixing this requires the main board to be replaced.

Would you please consider including this change in your kernel builds for the Gtab? It's a harmless change that could allow people to fix their broken tablets easily. Thanks.
 
  • Like
Reactions: AAccount

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
AAccount,
I have a patch that I'd like you to consider for your kernel builds.

There's a problem with the touchscreen chip in the Galaxy Tab where a firmware update fails. This leaves the chip in firmware update mode, meaning that it's not responding to screen updates. When this happens, you can recover from the problem by restarting the firmware update.
It's a simple fix to the mxt1386 driver - patch is available from http://www.rickmurphy.net/atmel_mxt1386_diff.txt

There's unfortunately a very easy way to get the chip broken - a simple
# find /sys -exec grep foo {} \;
command triggers the firmware update to start, then almost right away powers off the tablet. When you power it back on, the touchscreen is dead. Samsung claims that fixing this requires the main board to be replaced.

Would you please consider including this change in your kernel builds for the Gtab? It's a harmless change that could allow people to fix their broken tablets easily. Thanks.

Most definitely will do when I don't have school work or real work. Until then, avoid ""grep" against /sys/devices/virtual/sec_touch". which pretty much comes down to not using grep to search for text in the sysfs directory. I don't think most people would have a reason to text search the sysfs directory though so while a serious bug, it shouldn't be a problem for most people.

--------------------------------------------------------Added Opinion----------------------------------------------------------------------
Samsung seems to do a fairly sloppy job in their kernel. First, there's the eMMC brick bug which is patched in this kernel. Then there's the touch screen dieing that will be fixed in the next release. Also, my S3 had a memory bug in it which was patched by cyanogenmod.
 
Last edited:

xanmanz31

Senior Member
Mar 21, 2010
439
68
Anyone used this on Bindroid 5.0.1? I used A1-p4-1.8.4-wifi-cm I lost all touch response. I have a wifi gt-p7510 w/ clockwork mod recovery so I assume I got correct kernel. I wanted to see if anyone else had any issues.
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Re: [Kernel/Recovery/MOD][P75XX] A1 Kernel V1.8.4/TWRP2.3/Simple Mods

Anyone used this on Bindroid 5.0.1? I used A1-p4-1.8.4-wifi-cm I lost all touch response. I have a wifi gt-p7510 w/ clockwork mod recovery so I assume I got correct kernel. I wanted to see if anyone else had any issues.

You need the stock based version, not the cm one. Bindroid is based on stock ics not cyanogenmod.
 

xanmanz31

Senior Member
Mar 21, 2010
439
68
Re: [Kernel/Recovery/MOD][P75XX] A1 Kernel V1.8.4/TWRP2.3/Simple Mods

You need the stock based version, not the cm one. Bindroid is based on stock ics not cyanogenmod.

So I tried the stock version before I saw this reply and it ran a bit longer and still froze up. I re flashed the cm version and set oc to 1.4 seems to be doing fine now. I had it set to 1.6 the first 2 times which was what I thought was the issue. Also thought th "cm" was for clockwork mod recovery bc I saw the "twrp" versions in there but now I know "cm" is cyanogenmod. Thanks for the answers.

Sent from the Galaxy of Ice Cream Sandwich
 

AAccount

Senior Member
Sep 8, 2010
1,005
1,909
Tablet UI Mode Update3

I updated the 2 jar files and apk file for the tablet ui mod. They should be current with the January 26 nightly (that will come out tomorrow).
 

Attachments

  • SystemUI.apk
    1.7 MB · Views: 119
  • android.policy.jar
    260.5 KB · Views: 95
  • services.jar
    1.1 MB · Views: 97

hanspampel

Senior Member
Dec 7, 2011
2,140
3,128
How-to install this MOD

So how do i install this? i've installed the.apk file, but what do i do with the .jar files?

Dont install the systemUI.apk. Push it to System-->App and give the correct permissions. Its 644 or
x x -
x - -
x - -

But before rename the old SystemUI into "oldSystemUI" for example.

Now go to System-->Framework and push the files android.policy.jar und services.jar into it and give the same permissions like you did it with SystemUI. But before rename the two excisting files like SystemUI.

If you did all of them, reboot you Tab and enjoy the old Tablet UI. Maybe you can make a Nandroid before.

Any screenshots please :)

Here is one pic
 

Attachments

  • Screenshot_2013-01-27-10-59-23.jpg
    Screenshot_2013-01-27-10-59-23.jpg
    44.2 KB · Views: 444

stefpaul

Senior Member
Jun 27, 2010
354
33
bucharest
hmm

Dont install the systemUI.apk. Push it to System-->App and give the correct permissions. Its 644 or
x x -
x - -
x - -

But before rename the old SystemUI into "oldSystemUI" for example.

Now go to System-->Framework and push the files android.policy.jar und services.jar into it and give the same permissions like you did it with SystemUI. But before rename the two excisting files like SystemUI.

If you did all of them, reboot you Tab and enjoy the old Tablet UI. Maybe you can make a Nandroid before.



Here is one pic

Can you make a .zip that we can flash..the problem is that i didn't do things like this so it is kind of creepy to me... I'm kind of new to this things so this is why i prefer i flashble .zip to get things more easy done :d. Thanks in advance!

Stefan
 

hanspampel

Senior Member
Dec 7, 2011
2,140
3,128
Sorry mate. I cant do this. But its very easy. You do this with Root Explorer or the Explorer from CM10.X which is included.

You open the CM10 Explorer, go to settings in there and go to "extended", make a hook at "Root Accessmode". If you accept the SU inquiry tab in the adressline of the explorer. You see there storage-->emulated-->0. Tab in there an go on the 2 dots. You see emulated and usbdrive0 files. Tab another one on the 2 dots.
Now you are in that area you should be. Here you see the file of system if you scroll down. Go in and now follow the instruction which i posted above. Its very easy.
If you will change a file, tab and hold that file. Now you can change what you want.
 
  • Like
Reactions: AAccount

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.