yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 7" Android Development] CodyF86:
:good:
[Galaxy Tab 2 7" Android Development] zeetherocker:
Use next tool to delete the second partition..!
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
NEXT 2.0 preview2

Tested on Samsung Jelly Bean 4.2.2 and CM 10.2. Samsung 4.1.x and CM 10.1 support untested!

Flash this at your own risk! If you flash this on pure stock Samsung 4.2.2, the new vendor blobs from post #2 needed. Flash this on both 1st and 2nd ROM!

Source: https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2

Changelog:

- Hardware acceleration and camera fix for CM 10.2

- Untested CM 10.1 and Samsung 4.1x support
[Galaxy Tab 2 7" Android Development] CodyF86:
I saw you committed that change, along with a few

other things.

Thanks buddy! :) :good:

Here's some thanks your way.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Credit goes to you :good:
[Galaxy Tab 2 7" Android Development] Skazzy3:
Ketut I think you should apply for Recognized Developer.

You seem to meet all the criteria here.

http://www.xda-developers.com/recognized-developer-program/rd-minimum-requirements/

So please fill out this form: http://www.xda-developers.com/recognized-developer-program/recognized-developer-form/
[Galaxy Tab 2 7" Android Development] antutu:
I'm agreed and I've pm him about same thing, but he seems not in a rush:rolleyes:
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

I've fixed the issue with certain devices, depending

on p3100, p3110, or 3113 depending on what version

bootloader they have experiencing those hwcomposer /

surfaceflinger crashes on bootup.

Please make another commit for me, here is the link to

the line and file in your omap4 device repo, the line

highlighted needs to be commented out with an #, and

all is well. :)

https://github.com/kumajaya/android...-common/blob/cm-10.2/BoardConfigCommon.mk#L45
[Galaxy Tab 2 7" Android Development] Chirag_Galani:
I agree with you.... He should go for it...
[MENTION=4021423]ketut.kumajaya[/MENTION], Bro you have done a great job for our TAB 2....

Thanks mate... :)
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

Don't merge in the line comment I posted above,

I'm working on merging in Codeworkx patch for

cm-10.1 that should take care of the problem

with the sysfs vsync enabled.

If it works ill have 2 kernel driver files modified

for you to commit, and also all the def config

files needed 2 lines added, which I did even to

your blackhawk def configs. :) So it will be good

to go, after I test. :)
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

I was successful in merging Codeworkx' update for sysfs vsync

notification for cm10-10.1 into the updated kernel source for cm-10.2

and it fixes the issue, while allowing us to still use sysfs vsync notification.

There is definitely some changes in the updated kernel, just from

looking around when I was merging his patch.

I've been talking to Ji and told him I was going to have you merge

this into your fork, so it will be a plug and play merging it back into CM

source. :)

http://review.cyanogenmod.org/#/c/28068/

This is Codeworkx patch for cm-10.1, but you can't just cherry-pick it

in, I merged it myself, with the updated kernel, and it's working, the file

is at the bottom of this post to merge into your kernel fork. :)

Forget what I said about commenting that one line out now,

like I said this fixes the issue and allows us still use sysfs for vsync.

Here is the file with the updated source files. :)

http://d-h.st/uXs
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
[MENTION=5337314]CodyF86[/MENTION] I plan to reset cm-10.2 branch, no change in code (except remove some files that are not needed and update MTP driver), for more readable commits. Your omapfb fix will be included with little change in the configs file. Thanks.
[Galaxy Tab 2 7" Android Development] CodyF86:
Your awesome man thank you! I've been going over logcats before and after

like a mad man lol. And everything is really happy now. :) There is one warning

im still getting in logcat:

W/dalvikvm( 115): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument

Don't worry it sounds worse then it actually is, Jiangyi showed me a patch

to fix it. I'm going to try to merge it in to the updated espresso10 also sometime in

the next few days. I'll send you the changed files if it plays nicely.

Other than that all the nasty warnings / errors seem to be worked out. :)

edit: actually There is this one also, but I'm going to try and find a fix, and it

doesn't seem to be an actual issue anyway.

E/auditd ( 400): Failed on audit_set_pid with error: Protocol not supported
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
It's SELinux related :D I have no plan to enable SELinux in NEXT in near future. Audit service also disabled in NEXT.
[Galaxy Tab 2 7" Android Development] CodyF86:
Ok cool, I hadn't even looked at what was actually causing it yet, but if it's SELinux related

I won't even mess with it until we get everything all happy and merged back into CM source.

Then a change, if necessary, can be committed to the CM source instead of your fork. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Done!

Done!
[Galaxy Tab 2 7" Android Development] CodyF86:
Thanks! :)

It's finally at a state where it's more or less happy and running as

it should! oh yeah! lol :) :good:
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

I'm building a test build now and I'll let you know. I might

have you turn uevents for vsync on also, like it is in your

blackhawk config. It seems sometimes for whatever reason sysfs is

unavailable to send the vsync notification about 10-15% of the time and

I'm still getting a hwcomposer / surface flinger crash about 10-15% of the time.

That's better then it was at 100% of the time haha, but I'll

let you know here shortly, pretty sure this is going to fix it.
[Galaxy Tab 2 7" Android Development] CodyF86:
Ketut,

nm it did it with uevent enabled also so nm. Seems to still

be something wonky with the sysfs notification, but its

only doing it 10-20% of the time now instead of 100% of the time,

so I guess that's still progress lol.
[Galaxy Tab 2 7" Android Development] DarkStryder:
Dude why dont yoi edit your posts instead of keep replying all the time?

sent from my xperia neo v
[Galaxy Tab 2 7" Android Development] CodyF86:
Does that bother you? lol

lol you just replied to a post for the sole purpose of telling someone,

to edit their post instead of making a new reply. lol

I'll keep that in mind. tho. :)
[Galaxy Tab 2 7" Android Development] iamashwin:
Ketut sir why not update to Linux kernel 3.0.88
[Galaxy Tab 2 7" Android Development] Skazzy3:
That's Cody. :P [MENTION=4021423]ketut.kumajaya[/MENTION]
[Galaxy Tab 2 7" Android Development] CodyF86:
Ketut merged in the new Samsung updates into the current kernel source,

and I've been helping to get the core source, for which the stock updated

kernel and Ketut's Blackhawk 2.0 kernel, that he is working on, happy and

booting without issue at current version with the new updates of version 3.0.31.

The version of the kernel is really dependent on Samsung, in terms

that they updated the stock kernel, but their updates are based upon

the kernel complying with the same version of the linux kernel. To update

the kernel to comply with a higher version in relation to the linux kernel takes

a certain amount of work, and were still trying to make sure it's completely

happy and operating correctly based on the current linux kernel version with

the updates of 3.0.31. :)

I'm not Ketut btw, just helping. :)

edit: [MENTION=4021423]ketut.kumajaya[/MENTION],

I just installed the normal CM nightly with the normal stock

kernel, hwcomposer /surfaceflinger was crashing,

(when I say crashing I mean in the logcat, the tab was

running the entire time and you really couldn't visually tell)

just like the updated one is about 10-15% of the time.

So it's good to know it's not from merging the new updates

and it's actually something that's happening to the normal kernel.

Still trying to resolve it tho. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
[MENTION=5183377]iamashwin[/MENTION] Focus on 3.0.31 Samsung update, as CM and dual boot compliant more important for now.

[MENTION=5337314]CodyF86[/MENTION] I can't reproduce your problem on both Samsung and CM (dual boot). My bootloader already updated to the latest Samsung 4.2.2 release.
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

It seems to be device specific depending on the bootloader version.

I have a p3113 and there isnt an updated bootloader yet, that seems

to be why. p3100 and p3110 might not experience it. :)

You can't even tell unless you look at the log cats after I merged codeworkx

patch into the source, before it was doing it 100% on p3113, now its more like

10-15%. and like I said you can only tell by looking at the logcat, nothing that

a normal user would be able to tell really, visually from just using the device.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
http://samsung-updates.com/device/?id=GT-P3113

On my system, null output by "logcat | grep hwcomposer" :victory:

EDIT: https://github.com/kumajaya/proprietary_vendor_samsung/commits/cm-10.2

With updated P51xx blobs, nothing is prevented [MENTION=3208754]codeworkx[/MENTION] / [MENTION=3503248]Jiangyi[/MENTION] to perform kernel updates :D
[Galaxy Tab 2 7" Android Development] CodyF86:
lol awesome, it just came out it seems. Ill check it out. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
You just too focus on my thread and yours. Take a look at [MENTION=2478576]Tsjoklat[/MENTION] 's MicroDelta thread :D
[Galaxy Tab 2 7" Android Development] CodyF86:
Nah, Ji told me there wasn't one out yet, but guess there is. :)

(But I didn't make it clear I wasn't on the 4.2.2 one, I dont believe.)

I looked through every page in the micro delta thread though, I know you can do it with

heimdall, my question tho, and im sure this might sound like a dumb question,

but I've never done it before, and I have tried to google search.

http://samsung-updates.com/details/13099/Galaxy_Tab_2_7.0_WIFI/GT-P3113/XAR/P3113UECMH2.html

Can I flash the bootloader with odin? Or I guess what is my best option. I don't want to have

to revert to the stock rom to upgrade it if i don't have to, but don't want to brick my tab

rushing into it.

Yes I have google searched lol, and from the microdelta thread yeah I could use heimdall,

but just not really sure.
[Galaxy Tab 2 7" Android Development] hysteria24h:
Mas Ketut, how to enable external sd card - internal media swapper script??sorry for stupid questions,thx
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
[MENTION=5337314]CodyF86[/MENTION]

Always flash it as PDA or you will brick your device! Better backup yours EFS partition first:

busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img bs=4096

To create your own Odin flashable bootloader:

tar -H ustar -c Sbl.bin > P3113_JB_4.2.2_SBL.tar
md5sum -t P3113_JB_4.2.2_SBL.tar >> P3113_JB_4.2.2_SBL.tar
mv P3113_JB_4.2.2_SBL.tar P3113_JB_4.2.2_SBL.tar.md5

Kernel: boot.img

Secondary boot loader: Sbl.bin
[Galaxy Tab 2 7" Android Development] CodyF86:
Thanks Ketut,

Going to flash it in the morning probably, Samsungs site is slow as bricks atm,

but it's downloading. :)

Yeah the kernel seems good to go, it's running very well, this bootloader

update will hopefully take care of the last little bit of wonkyness. lol :)

It could be merged into CM right now like you said and it's

a plug and play solution from your 2 Github forks straight into the CM

repos.
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

For the win! lol :) :good: :victory:

Here is the sbl.bin all tarred up for anyone that would like it.

This is for the p3113 only.

http://d-h.st/O5n

Also have the efs image stashed away too if anyone ever needs it

for p3113. http://d-h.st/iFP

Edit: It's still doing it about 15% of the time on p3113 with 4.2.2 SBL,

it's actually also been doing it on the stock CM pre-update kernel,

before and after the SBL update.

Maybe he meant a 4.3 SBL if one was to ever be released in the future.

lol I love how they misspelled download in the sbls download mode.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
For 4.1.2 only: http://xdaforums.com/showpost.php?p=42630105&postcount=3

How about NEXT 2.0 preview2?
[Galaxy Tab 2 7" Android Development] kinung:
Bli Ketut, next 2.0 preview are nooc version?
[Galaxy Tab 2 7" Android Development] Vishesh:
Exactly Bro.. Ketut is amazing developer.. Google should recruit him.. He can surely extend the android performance to some other level.. M out of words.. Simply awesome..

N ya jus slightly reduction in values freezes the tab.. M sure this gonna b resolved very soon which will vanished the heating issue completely..

¤ Help = Thanked ¤

Sent from Heaven
[Galaxy Tab 2 7" Android Development] Dexxmor:
Undervolt goes here very well (1.2) same values as on 1.0

Sent from my Blackhawk powered device.
[Galaxy Tab 2 7" Android Development] dimfil:
Just tested 1.2 nooc for undervolting.

I can't confirm the problem this time. I was able to undervolt with android tuner by two steps of 25mV and tab is running OK for about an hour without reboot.

I will try to undervolt a little more and if needed I will report back...

Here is a screenshot of the current values:
[Galaxy Tab 2 7" Android Development] Vishesh:
Undervolting works for some, n not for many others..

¤ Help = Thanked ¤

Sent from Heaven
[Galaxy Tab 2 7" Android Development] brolee93:
oh good work 1.2 :) a lot of versions lol .
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Hi [MENTION=1458755]brolee93[/MENTION], send me latest P5100 Sammy and CM boot.img ;)
[Galaxy Tab 2 7" Android Development] brolee93:
seriously ?
[Galaxy Tab 2 7" Android Development] Skazzy3:
I don't mean to be a pest... But i mean't if we can disable boot menu for the ROM. Not the recovery.
[Galaxy Tab 2 7" Android Development] dimfil:
Well, with philz 5.05 + next 1.2 running single boot right now (slimbean), I have no interaction with any menu (either recovery or rom) during boot process.

This is how it is supposed to work to my opinion.

If there is no secondary rom, there is no reason for any menu to interfere.
[Galaxy Tab 2 7" Android Development] Domoo:
These are my undervolt values and it's been stable so far. I'm over clocked to 1.35 ghz. It seems Samsung was very generous in their stock voltages.
[Galaxy Tab 2 7" Android Development] sergio_f:
hi! i flashed blackhawk-next-kernel-1.2-addon-nooc-p31xx.zip but my tablet wont boot, only boot with blackhawk-next-kernel-1.2-p31xx.zip, but i want noon over clocked version
[Galaxy Tab 2 7" Android Development] Dexxmor:
:mad: Read the OP!

....:mad:
[Galaxy Tab 2 7" Android Development] Skazzy3:
Thats an addon. Flash 1.2 forst and then non-oc
[Galaxy Tab 2 7" Android Development] sergio_f:
sorry i missed that! now i understand! thank you!
[Galaxy Tab 2 7" Android Development] daavvis:
hey does anyone know if pacman will boot using this recovery? installed in slot 1?
[Galaxy Tab 2 7" Android Development] sergio_f:
I think yes! only dont work in ICS, CM 9, CM 10
[Galaxy Tab 2 7" Android Development] iamashwin:
yes it does and so does all the rom based on 4.1.2 and above (stock and custom)

---------- Post added at 07:59 AM ---------- Previous post was at 07:58 AM ----------

it did work for cm 10
[Galaxy Tab 2 7" Android Development] d3rm1k:
Still on 1.1 with these voltages ...

edit: CM 10.1 RC2
[Galaxy Tab 2 7" Android Development] Vishesh:
For me.. 1.2 with nooc.. Reduction in voltages causes freezes n reboot.. I try each n every combination..m sure it will b resolved soon..

¤ Help = Thanked ¤

Sent from Heaven
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
http://xdaforums.com/showpost.php?p=41923107&postcount=42
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
No overclock code inside. Almost stock but CM-10.2 compatible, minus SELinux: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2
[Galaxy Tab 2 7" Android Development] CodyF86:
Gonna test it here in a few minutes for ya Ketut.

If I turn sysfs notification off and just use uevent to give

the vsync notification it never crashes or does it at all,

but Ji was telling me how sysfs is the better way to do

it or at least possibly faster way.

Gonna flash your preview and see what the logcat says.
[Galaxy Tab 2 7" Android Development] poppolo2001:
@ Ketut

Hi Ketut, I just looking inside the new 4.22 (P3110UECMH2 from microdelta) it seems that the ducati firmaware is more recent (2013-07-19 17:02:43) than the one provided on your kernel.

Also the sgx540 library are different (smaller...) but I don't know how to look the version or build date to compare.

..... just for info ....
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

I cant get it to do it with your preview. Something you've changed has fixed

it, it seems. I tried with uevents turned on also like you do in your blackhawk def

config. It didn't fix it with my previous bootloader, but maybe I should try it now

with the 4.2.2 bootloader.

Whatever it is we should get it into the stock def config, so we can merge

this code back into CM. :)

Only thing I'm curious about is that I was told you only want to use one or

the other, just curious why you have both set on. :)

stock kernel is:

# CONFIG_FB_OMAP2_VSYNC_SEND_UEVENTS is not set

CONFIG_FB_OMAP2_VSYNC_SYSFS=y

blackhawk def config is:

CONFIG_FB_OMAP2_VSYNC_SEND_UEVENTS=y

CONFIG_FB_OMAP2_VSYNC_SYSFS=y
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
I have to binary compare it, there are no compatibility issues as long the heap size is still 65MB.

From my experienced, stock PVR driver usually better for 2D but slower in 3D. I prefer to use the newer version from CM.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
With CONFIG_FB_OMAP2_VSYNC_SEND_UEVENTS disabled, Samsung 4.2.2 graphic operation become very slow, almost unusable. With CONFIG_FB_OMAP2_VSYNC_SEND_UEVENTS enabled, Samsung original codes almost same as CM patched codes ;) Please remember, my kernel must support both platform. It's multiboot :victory:
[Galaxy Tab 2 7" Android Development] CodyF86:
Ah gotcha,

Then whatever fixed it with your preview must be something else, any ideas? were so close. :)

I'm going to do some fiddling with the def config, poke around a bit lol.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Kernel compiler flags? Someone fork my github for Ubuntu Touch kernel and experienced PVR driver issue, solved by removing my kernel tuning flags.
[Galaxy Tab 2 7" Android Development] CodyF86:
The CM nightlys using the non-updated kernel seems to be doing it also, straight from

CM, but im sure its something silly.

I'm gonna check out the compiler flags.
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION] [MENTION=3208754]codeworkx[/MENTION] [MENTION=3503248]Jiangyi[/MENTION]

Fixed it. It is the SELinux kernel flags, which is weird, but I've confirmed it,

with logcats, and visually.

Ketut, for the time being, can you revert the enable SELinux patch in your

repo for the CM p31xx and p51xx def configs, until a solution can be found,

because CM is going the SELinux route, but no point in having it turned

on, if it's crashing the kernel/hwcomposer/surfaceflinger on bootup.

https://github.com/kumajaya/android...mmit/302a5fa6c39974382f1215fb6151d63c42c7010c

Please don't revert CONFIG_AUDIT=y and CONFIG_AUDIT_DEFAULT=y kernel flags from

that patch, as they aren't the cause, and fix a few errors for the stock kernel. :) wooo! :good: lol
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Strangely , I do not have problems with blackhawk config + SELinux enabled :confused: Please remember, I build the kernel outside CM source tree with Samsung /OMAP4 default compiler flags, Linaro GCC 4.7.

Please try, change https://github.com/kumajaya/android_device_samsung_omap4-common/blob/cm-10.2/BoardConfigCommon.mk PLATFORM_VERSION from 4.0 to 4.1 .
[Galaxy Tab 2 7" Android Development] CodyF86:
Sounds good ill give it a go, but the current CM nightlies are also doing the same thing

on p3113 with the previous kernel, also it could be caused by the bootloader even tho were running

4.2.2 bootloader, you might not experience it on a p3100 or p3110. :)
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION] [MENTION=3208754]codeworkx[/MENTION]

Nope, had no effect. Remember like I said, this is currently happening also on the

CM nightlies on the non-updated kernel with SELinux in permissive mode also.

From what others have said it seems to only be happening on the p3113 and

possibly p3110, but not p3100. Here is the logcat: http://d-h.st/EIL

The tab doesn't crash, but the screen stays black, then the backlight goes

off then back on, then the boot animation like normal, but it seems to actually

crash multiple times, sometimes it doesn't do it at all tho.

Disabling SELinux resolves it.

edit: Also here is a logcat from when it is happy, which is

about 70-80% of the time. http://d-h.st/OOS
[Galaxy Tab 2 7" Android Development] Skazzy3:
Yes?
[Galaxy Tab 2 7" Android Development] CodyF86:
He double posted. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
I had bad experiences with SELinux on Fedora system years ago. That's the reason why I did not rush to adopt it :D
[Galaxy Tab 2 7" Android Development] CodyF86:
Tomorrow I'll enable SELinux flag by flag until I find out if it's SELinux all together, or a certain flag

involved with SELinux, but not SELinux itself. I will track it down!!!, and beat it into submission!!

lol. :) :cowboy:
[Galaxy Tab 2 7" Android Development] codeworkx:
selinux does nothing by default except logging.

permissive = just log violations

enforced= actively prevent violations

can't believe that this is causing problems. the solution is NOT to turn of selinux/audit.
[Galaxy Tab 2 7" Android Development] CodyF86:
I know it's not the solution, I was just saying that turning off SELinux, makes it not happen. :)

I couldn't figure out why it was happening, but then I remembered it was working fine,

after I merged your patch for sysfs notification into the new kernel update, but then after Ketut,

merged your enable selinux patch is when it started happening, so I just turned it off, to see if that

truly was the cause, and turns out it is, or it's at least the trigger that causes it to derp.

Check out my logcats.

edit: [MENTION=3208754]codeworkx[/MENTION] using uevents instead of sysfs also makes it not crash, I know

we want to use sysfs and not uevents, just saying that to maybe help narrow it down. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
As I told before, CONFIG_FB_OMAP2_VSYNC_SEND_UEVENTS must be enabled for Samsung 4.2.2 or Android graphics will be very slow/unusable. This problem began to appear in Samsung 4.2.2, does not occur in 4.1.2 with CONFIG_FB_OMAP2_VSYNC_SEND_UEVENTS disabled.