yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 7" Android Development] Skazzy3:
Is it debloated?

Try my script. http://xdaforums.com/showthread.php?t=2370164
[Galaxy Tab 2 7" Android Development] poppolo2001:
I make a clean install of MicroDelta Stock Based ROM (XXDMH1) and since the battery is drain very fast I try to install next kernel 1.8.3 using new ducati bin, so i go to recovery (phil touch) clean cache-clean dalvik cache and install kernel1.8.3 and then new ducati.

When I reboot the tablet (p3110) stop on galaxy tab screen...

can some one help me ?

I don't need double boot (for now) I just wanna try this kernel for battery life.

thanks.
[Galaxy Tab 2 7" Android Development] Skazzy3:
Try my debloat script. In my sig.
[Galaxy Tab 2 7" Android Development] openmatrix:
Yeah it's a debloated one...I debloated it myself. ? Earlier I used

psn stock deodexed rom debloated by myself , but due to the sh***y lags I odexed that rom and pimped it after that thing I am getting an unstable battery life and it's very hot even in stock cpu frequencies.!!!!!:(...
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
If you have problem with NEXT and Samsung 4.2.2, please re-read post #1, WARNING in red!

EDIT:

PLEASE REMEMBER, we used this kernel on different type of ROM. NEXT boot Samsung 4.1.x, 4.2.2, CM 10.1, CM 10.2, CM/AOSP based ROM. No battery drain issue on 4.1.x and CM/AOSP. So what's the logic!
[Galaxy Tab 2 7" Android Development] poppolo2001:
thanks for fast reply, I read the warning (if you have problem ...) but reading your change log seams that only 1.8.3 has the attempt to reduce battery drain... (that is what I need). Is this implemeted also on "

stock-4.2.2-blackhawk-kernel-p31xx.zip (updated, sound fix included)

" ,

Did you check "opensource.samsung.com" seams that they release "GT-P3110_JB_Opensource_Update1" with new kernel source.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
I forgot :(

Yea, my kernel based on CM, GT-P3110_JB_Opensource change applied. As I told before, GT-P3110_JB_Opensource newer than GT-P3100_JB_Opensource_Update2 but no one realized it except me :laugh: Thanks for your info, GT-P3110_JB_Opensource_Update1 must be the newest kernel source, downloading now :good:

From post #1, feature list: "Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target".

EDIT:

GT-P3110_JB_Opensource-GT-P3110_JB_Opensource_Update1.patch attached! This is a patch file for GT-P3110_JB_Opensource kernel source, not a flashable zip! For tracking Samsung changes, for developer only.

UPDATE:

I managed to compile GT-P3110_JB_Opensource_Update1 using gcc-linaro-arm-linux-gnueabihf-4.7, outside the kernel source tree :victory: No overclock, no dual boot, untested :laugh:

EDIT 2:

A patch file for GT-P3110_JB_Opensource_Update1 to build it using gcc-linaro-arm-linux-gnueabihf-4.7, outside the kernel source tree (i.e. "make -j3 O=/home/kumajaya/build/espresso/") attached. exFAT filesystem kernel driver from Samsung OSRC http://opensource.samsung.com/ inside. Credits goes to Samsung, [MENTION=3208754]codeworkx[/MENTION], and me :cool:
[Galaxy Tab 2 7" Android Development] philidor:
This patch can be used on next kernel 1.8.3 on p3100?

Or have to wait a best 1.8.4 kernel?

Inviato dal mio GT-P3100 usando Tapatalk 4

---------- Post added at 07:33 AM ---------- Previous post was at 07:33 AM ----------

Edited

Inviato dal mio GT-P3100 usando Tapatalk 4

---------- Post added at 07:48 AM ---------- Previous post was at 07:33 AM ----------

This battery drain can't be because of the kernel, you have to search with better battery stats to find what app cause it.

Inviato dal mio GT-P3100 usando Tapatalk 4
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
I will make a limited changes to make GT-P3110_JB_Opensource_Update1 as dual boot compliant :good:

GT-P3110_JB_Opensource_Update1 code review:

- Allocated 65MB memory for ducati (same as NEXT)

- Ion allocator updated

- In-kernel omaplfb driver (same as NEXT)

- OMAP framebuffer with vsync support (same as NEXT)

- Sound driver updated, for low latency audio?

- Newer modem and WiFi driver

- Updated sensors driver

- Enhanced Android lowmemorykiller (same as NEXT)

- No zram support?

- etc

With open sourced exFAT filesystem, no limitation to fine tuning our kernel now, for example back activate SLQB :good:
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Booted Samsung 4.2.2 using NEXT 2.0 :victory:
[Galaxy Tab 2 7" Android Development] CodyF86:
We wants this magical 2.0 you speak of. :p
[Galaxy Tab 2 7" Android Development] Android-Andi:
+1 :silly: :eek: :p :D :cowboy: :angel: :good: :cool:
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

Just want to make sure, im understanding correctly. The patches above, are for

the stock espresso10 samsung kernel? And if yes, then the code in the patch

hasn't been made part of the espresso10 cm github yet, correct?

What I'm trying to say is can I try to merge the patch into the kernel source

for when I build, or am I misunderstanding?

If I remember correctly it was changed to 65MB in the espresso10

repo a few days ago, just trying to see what has been committed already

and what hasnt.

Also from what I've been reading, zram increases CPU load

and on our tab the only real advantage is less writes and reads

to flash memory, since we have 1gb (well 815) of ram, I actually have better

performance with zram off.
[Galaxy Tab 2 7" Android Development] d3mondroid:
Anyone else having issues in videoplayback after flashing 1.8.3 on sshd v4? Had to flash stock blackhawk next kernel to correct the issue. ?... sorry no dual boot for me, atleast not till this issue is fixed...:(:(:(:(
[Galaxy Tab 2 7" Android Development] CodyF86:
Did you flash the new blobs if you are using a rom that doesn't have them included? They're on the second post

of the OP.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
I will create a new branch based on P3110 kernel source update. The minimal change needed to make it compatible to CM and dual boot (standard MTP support, runtime MTP mode switch, landscape support, runtime orientation switch, gcc linaro compatibility, etc) is complete. As usual, Samsung has always given problems in the kernel source code but I experienced to handle it :D
[Galaxy Tab 2 7" Android Development] CodyF86:
Thanks! :good::victory:
[Galaxy Tab 2 7" Android Development] jasonyu007:
Hi !! ketut.kumajaya

I really like your dual boot . one question . how could i have auto boot when I do not touch anything ? I found you have .defaultrom file .

it should be had auto boot , right ?

Jason You
[Galaxy Tab 2 7" Android Development] fooiskandar:
When next 2.2 released ...
[Galaxy Tab 2 7" Android Development] Android-Andi:
after next 2.0 and 2.1 were released.
[Galaxy Tab 2 7" Android Development] nokiagye:
Good...:)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
STOP! ONLY for Samsung Jelly Bean 4.2.2 for now, the new vendor blobs needed!

Flash this at your own risk!

Source: https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2
[Galaxy Tab 2 7" Android Development] poppolo2001:
you are very fast to integrate samsung source code...

let me understand, I'm still on MicroDelta Stock Based ROM (XXDMH1) can flash this kernel only, or I have to flash also new ducati ...(on your 2nd post).

This is 3.0.31 original samsung kernel (update1) what you add to this stock ? double boot ? compiled with linaro toolchain ?

I see that you remove some kernel log (DEBUG_PRINT = 0)

thanks for your job.
[Galaxy Tab 2 7" Android Development] nokiagye:
Ketut I need the blobs write? I try now
[Galaxy Tab 2 7" Android Development] poppolo2001:
I try now it seems better, your script remove almost all samsung app... only samsung link remain (i don't know what is it) and play books (that i don't need).

Let me use as is for some day to feel the difference.

thanks
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
As I told before:

1. Landscape support, runtime orientation switch for dual boot

2. Runtime MTP switch for dual boot

3. Linaro gcc compiler

4. Remove kernel log spam

5. Logger as a module

6. CM base kernel config
[Galaxy Tab 2 7" Android Development] nokiagye:
818 ram.

? waou
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
What script :confused:
[Galaxy Tab 2 7" Android Development] nokiagye:
Any overcklocked version on feature will be great thanks ketut
[Galaxy Tab 2 7" Android Development] poppolo2001:
sorry ketut, it's a msg for Luigi2012SM64DS that suggest me his script for debloating the stock samsung...

just need this info:

1) I can flash your kernel (2.0) over "MicroDelta Stock Based ROM (XXDMH1) " ?

2) If yes i need only kernel or i have to flash also new ducati (2nd post)

thanks
[Galaxy Tab 2 7" Android Development] antutu:
Tested on microDelta (secondary Rom) and SSHD v4 (primary rom) without new ducati:good:

Edit:Even dual booted with cm 10.2 unofficial:confused: [MENTION=4021423]ketut.kumajaya[/MENTION] Why next 2.0 work in cm?
[Galaxy Tab 2 7" Android Development] fooiskandar:
Greats ... Thank [MENTION=1434892]ketut[/MENTION].kumjaya
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
1. Yes.

2. From purely stock Samsung 4.2.2 ROM and kernel, you have to flash the new vendor blobs
[Galaxy Tab 2 7" Android Development] Skazzy3:
Samsung Link is Allshare Play. It should be removed. Maybe you downloaded the updates from the play store?
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

Hey Ketut,

Just trying make sure I'm on the same page as you, lol. :)

https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2 Is this forked from the CM github,

then you merged the Samsung updates, or was this just forked and already had the updates.

What I mean is, is your fork ahead of the CM / cm-10.2 espresso10 repo now by applying the Samsung patches

and if it is then you wouldn't mind me syncing it as the stock kernel instead of using CM's repo for the time being.

To build the stock configured espresso10.

I know that's what Github is there for, but figured I'd ask. :)

edit: oohh did some repo comparison, you rock! Thanks for taking the time to apply that

update!
[Galaxy Tab 2 7" Android Development] dollyaja:
So far so good with this kernel
[Galaxy Tab 2 7" Android Development] CodyF86:
opps lol
[Galaxy Tab 2 7" Android Development] d3mondroid:
Yeah, I did flash blobs directly after flashing 1.8.3 ...followed the instructions strictly:(
[Galaxy Tab 2 7" Android Development] poppolo2001:
I make a clean install of "MicroDelta Stock Based ROM (XXDMH1)", and then apply your script (no reboot between rom installation ans your script).

On this condition i still have samsung link (and google playbook).

Since I wipe - format everithing... is a good occasion to test some new ROM;) ...

Anyway I think (if I wanna stay on stock) is better to start from a stock xxdmh1 from samsung flashed using odin ... then root ... then cwm ... then debloted (for battery ...) since on 3110 starting from microdelta I'm still have problem flashing next kernel (both 1.8.3 or new 2.0 with or without new ducati ...:confused:

thanks for help.
[Galaxy Tab 2 7" Android Development] CodyF86:
Hey Ketut,

only issue I see atm is battery displayed as circle with percentage in middle, show as

just circle, the percentage has disappeared, but I built the stock kernel with the source

and its goin good.

edit: actually I was able to fix that.
[Galaxy Tab 2 7" Android Development] jjpita:
This kernel with 4.3 works really nice.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
NEXT 2.0 prepared as CM compatible in mind but CM support untested since both my 1st and 2nd ROM using Samsung stock 4.2.2. First ROM Samsung 4.2.2 for P3100 used for creating my own phone disabler package, 2nd ROM Samsung 4.2.2 for P3110 creating my own phone enabler package. Just flash MicroDelta 4.2.2 as 1st ROM + phone enabler + NEXT 2.0, downloading CM 10.2 :D
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

Your 2.0 preview boots on cm 4.3 and is great only thing I noticed is, the battery with circle and percentage, the

percentage is gone, its the same as just circle.

On stock kernel with your Samsung updates merged, it's not like that, but yeah it's running good! on cm. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Please inform this kernel update to [MENTION=3208754]codeworkx[/MENTION] and [MENTION=3541309]jianyi[/MENTION]. My English not good enough for conversation :laugh:
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Battery percentage works on stock 4.2.2 :D How you fixed it?
[Galaxy Tab 2 7" Android Development] CodyF86:
:good: I'll get in touch with them.

You should release a 2.0 preview with cpu OC. :)

edit: I just pm'ed [MENTION=3541309]jianyi[/MENTION] and let him know, ive talked with him before,

so he should get back to you and/or me in the near future. :)

---------- Post added at 05:15 PM ---------- Previous post was at 05:08 PM ----------

Hey [MENTION=4021423]ketut.kumajaya[/MENTION] ,

the issue with the percentage in the circle was fine on the stock kernel with the updates,

I meant it was just a circle on your 2.0 preview, which I assume has the kernel updates in it.

But I did PM him to see if we can get the kernel updates merged back into the CM github from

your fork.

---------- Post added at 05:22 PM ---------- Previous post was at 05:15 PM ----------

Err sorry for the 3 post guys.

Ketut sorry I was as bit vague when I said I fixed it.

I flashed your 2.0 preview with the updates to see if it would boot, and it did and was fine, but the thing about the

battery percentage. If you choose circle with percentage it just shows the circle, like when you choose just circle.

Then I flashed the stock kernel with the updates to see if it would boot and it did and was fine, but the battery

percentage was working.

That's what I mean't when I said I fixed it, sorry I shouldn't have said it that way lol. I didn't mean I fixed it

on your preview with cm, but I can take a look also.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Just flashed CM 10.2. + NEXT 2.0. Hardware accelerated media and camera failed (as expected :( ) Hardware accelerated media issue fixed using Samsung 4.2.2 libraries but still fighting with camera. Beware!

EDIT: Battery percentage works!
[Galaxy Tab 2 7" Android Development] CodyF86:
Yeah Ketut,

Were having the same problem with stock kernel with updates, let me know what you find out

with the camera, ill poke around also.
[Galaxy Tab 2 7" Android Development] rhycka:
tnx for the rom,ill flash it with mobile odin..what is the SS_DL.dll for?

---------- Post added at 04:00 AM ---------- Previous post was at 03:58 AM ----------

tnx for the rom,ill flash it with mobile odin..what is the SS_DL.dll for?
[Galaxy Tab 2 7" Android Development] Skazzy3:
Who knows, who cares. I just deleted it and everything worked fine.
[Galaxy Tab 2 7" Android Development] Vishesh:
Ketut@ hiii bro.. Can u guide me on this particular issue?? As m facing a big trouble right nw.. m currently with adi's sungsonic v4 with default kernel.. As sungsonic has many tweaks present in ini.d folder, so wenever I flash ur kernel in sungsonic.. It deletes all the scripts present in that folder.. Due to which all audio /video tweaks got vanished.. So is there any way to cure it so that it didn't delete contents of the ini.d folder n we can have ur kernel in every rom.. Pls help me..

¤Help = Thanked ©

Sent from Heaven
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
ROM modder must find a way to make sure this kernel work properly on his/her ROM, just like as I have done to make sure this kernel work on all ROM. Flash this kernel, directly reboot with the default setup. With some improper init.d contents, you switched your system as "unsupported". It's almost impossible to make this kernel work properly on a ROM without a good willing to make it work properly. Redundant script, improper script, not a really work script, junk script, may switch this kernel as a bad kernel. I repeat, my duty to make sure this kernel work on all ROM, that's it.
[Galaxy Tab 2 7" Android Development] Android-Andi:
:angel:
[Galaxy Tab 2 7" Android Development] Skazzy3:
Copy all init.d scripts to /data/local/userinit.d. And then install blackhawk kernel directly after. [MENTION=4021423]ketut.kumajaya[/MENTION] Maybe add a line to the updater script of the kernel to copy all init.d?
[Galaxy Tab 2 7" Android Development] CodyF86:
Ketut,

I'm pretty sure I figured out what was going on. The 3 files in proprietary_vendor_samsung

are correct, but when I compile, it seems its using the libion_ti it compiles from

android_device_samsung_omap4-common, does your fork of the omap-4 common repo

cm-10.2 have the source files for 4.2.2 libion_ti also?

I compiled using the cm github omap4-common, but if your omap4-common has the

libion_ti 4.2.2 source files then I can use that, and won't have to copy that file into my

rom zip file. I got it all working, tho, so the rom can just be flashed.

Gonna look into the battery percentage disappearing sometimes with

percetange/circle battery display option as it was effecting the stock

updated kernel and next 2.0 preview. :) edit: the percentage actually

randomly came back, so I don't know what's going on, its effecting

the updated stock kernel also.

Also Ketut,

Ive noticed with the updated kernel, when you start up from being shutoff.

The screen will flicker on and off a few times then either catch the very

end of the CM bootscreen or just go straight to the lock screen, but when

rebooting its normal. Just pointing out my observations. :) :good:

Working great tho!

Time to run some logcats!!! Gonna dig around. lol :)

Edit: Its intermitent Ketut, it seems like every

4th cold boot or so powervr wants to go wonky, then

powervr will restart (tab stays running entire time, just

a few screen flickers.) and then it makes it to the lock

screen fine. Should we try to use the 4.2.2 powervr?
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
[MENTION=5337314]CodyF86[/MENTION] I have no chance to build CM from source but you can try to update android_device_samsung_omap4_common kernel header to updated version but it will be break android_device_samsung_omap4_common compatibility to another device. Is it possible to set a specific overlay for our device only to use the proprietary libion_ti.so?

For battery percentage, it disappeared when battery reach 100% (full charged) and back appear when down to 99% or lower.

No flicker for me. In dual boot, boot menu always shown first, reset the framebuffer, and then boot the system.
[Galaxy Tab 2 7" Android Development] ken_alpha24:
How do i overclock the gpu? Ty
[Galaxy Tab 2 7" Android Development] CodyF86:
It's no biggie Ketut,

edited: I think I actually have it so its going to copy libion_ti.so and be happy now,

when it compiles, Ketut. :)

As for the battery percentage, I'm not sure yet, I thought it might of had something to do

with it not wanting to display 3 digits, but if you use the other percentage, it shows at 100%,

ketut what version of CM were you using, if it's not happening on a stock rom, then something

in the CM source might have actually just broken at the same time, we've been doing this.

Because it seems like a UI issue, not a kernel issue. :)

I'm going to get another build under the belt, when it comes to the powervr driver wanting

to go wonky, because I think it will just go away. I switched to your omap4 common repo also,

and going to see how it goes tonight.

edit: I'm just building the stock kernel with the updates, so like I said

I've been using the default make config, the cyanogen_def_p3110 or

something like that, if theres something at some point I need to add

to the default config just let me know, but its running really well right now.

---------- Post added at 10:12 PM ---------- Previous post was at 09:30 PM ----------

Sorry for being so long winded guys. [MENTION=4021423]ketut.kumajaya[/MENTION] check this out.

https://github.com/kumajaya/proprietary_vendor_samsung/blob/cm-10.1/p31xx/p31xx-vendor-blobs.mk

Adding:

$(LOCAL_PATH)/common/system/lib/libion_ti.so:system/lib/libion_ti.so \

To anywhere really, but line 41 is good, should fix having to overwrite the file

manually when building CM, I'm going to test it tonight, and if it works if

you wouldn't mind committing that change to your fork. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
No biggie but how about our concern to contribute back to upstream CM?

As an independent - unrecognized - developer, official CM 10.2 :laugh: Don't worry, though I always try to independent, I am always trying to help other developers. With my dual boot setup, it's super easy to try every ROM around here :good:

EDIT: I set cyanogen_p3100/p3110_defconfig as close as possible to CM kernel configs + Samsung update (contiguous memory allocation, enhanced LMK) + exfat.
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

I just meant if it works, commit it to your fork, so that we could have a working fork, that

could get merged back into CM source at some point in the near future. I want to merge

it back, but it will also have to work when we / they merge it back, that's why I said that

about committing it to your fork first. :)
[Galaxy Tab 2 7" Android Development] Skazzy3:
Edit the init.post_boot.sh file in /system/etc and follow the instructions.

btw, [MENTION=4021423]ketut.kumajaya[/MENTION] how to underclock GPU to 153 MHz? Just wondering.
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

I talked to Ji a bit ago, he is going to try and get his stock updated kernel up

and running on his i9100 also to play with it. So it looks like this will be able

to be merged back into upstream CM. We will need to make that one commit

to that makefile in your fork, if you want, just so everything works when setup

to pull from those 2 repos for when it gets merged back.

Ji told me the issue with powervr going wonky sometimes and flickering

a few times before it gets going, is because the boot loader on certain

devices will need to be updated at some point. I guess the same thing

happened when Codeworkx merged kernel updates a previous time.

It happens on my p3113, but depending on p3100, p3110, p3113 it

might not do it on some devices, and on others it will. The kernel

always boots, but like I said after the first samsung screen sometimes (20%)

powervr will go wonk and have to reinitialize itself (screen flicker) and then

it continues booting.

Kernel still running wonderfully tho! :good:
[Galaxy Tab 2 7" Android Development] kenundrem:
I got the screen flicker and no cyanogen boot logo until finished a couple times as well....of course on stock kernel
[Galaxy Tab 2 7" Android Development] CodyF86:
Yeah its the actual boot loader (download mode) is the boot loader interface

you actually see, but the boot loader controls booting normally and into recovery

also.

It will need to be updated at some point on the devices it does that on, but it always boots

so it isn't an issue that breaks anything. :)

There isnt an update atm for the p3113s tho, but im sure there will be

at some point.
[Galaxy Tab 2 7" Android Development] kenundrem:
I don't mind lol ROM is amazing...I was just adding another to the list :)
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4021423]ketut.kumajaya[/MENTION]

Here is the updated blob make file: http://d-h.st/Nlc

It's just a one-line addition and now CM compiles with the updated

kernel and works ;) with no intervention from me, once I use your forked

espresso10 and muppets repo, if you can commit this one line change. :)

And also for when it gets merged back into CM upstream, your forked repos

will be at a state where it just works. :)

The file being changed is an actual CM build make file, so it

won't mess up anything on your end either.

The file goes in root/p31xx directory in your muppets repo. :)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Like a real team :D