yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 10.1" Android Development] ns4g4me:
Na charging through wall charger. Like I said it charged fine before even the cm roms but it's after I flashed this Rom..which I like very much lol... That I got the charging problems. After it charges I'll try reinstalling again and serif that fixes it. Thanks for the replies.... And atleast I'm not only one having this problem.
[Galaxy Tab 2 10.1" Android Development] shakatu:
Maybe back up your files to a computer, then flash the stock ROM over Odin this is based off of, let it boot up and set itself up (you don't need to sign in), then flash a custom recovery via Odin, THEN flash this ROM again. There are some files on your tablet that flashing via recovery never updates, so maybe one of them is messed up IDK.
[Galaxy Tab 2 10.1" Android Development] Skazzy3:
PORTING SUCCESSFUL!

EDIT 2: Problems: Apps (eg. settings) load in phone ui (one panel instead of 2)

Samsung and Google keyboards don't work.

Can anybody help?
[Galaxy Tab 2 10.1" Android Development] nikefreeek51:
Ns4g4me did that work for you? The whole Odin thing?

I just don't want to have to go through that hassle of redownloading my Google play and and game data....
[Galaxy Tab 2 10.1" Android Development] shakatu:
Use Titanium backup and transfer to a computer. Heck, use TWRP or CWM backup and transfer to computer!
[Galaxy Tab 2 10.1" Android Development] PaTr10T:
wireless channel support

Love this ROM but noted no support for Euro wireless channels ie up to 13. Is this something that could be built in?

Thanks for a great work.
[Galaxy Tab 2 10.1" Android Development] shakatu:
Supposably, this doesn't have the newest Android version of Flash Player anymore, which doesn't make sense cuz Adobe doesn't support Android anymore...

To remedy this, use this CWM-flashable zip cuz the adobe installer doesn't work right with this tab.

http://xdaforums.com/showpost.php?p=41894538&postcount=6
[Galaxy Tab 2 10.1" Android Development] shakatu:
A change is coming...
[Galaxy Tab 2 10.1" Android Development] shakatu:
Zap Blaster v2.0

Changelog for v2.0

COMPLETELY rebuilt for 4.1.2

Even more debloat than before! (Less than 500MB for a ROM file?!?)

If you want all the Samsung apps back, install Zap Apps

Updated several built-in apps to latest versions (But not all... more will may come later)

Yes I removed even more apps that I consider useless. However, this time I was kind enough to create my own apps package for people who want all that Samsung crap back!
[Galaxy Tab 2 10.1" Android Development] p3tr0s:
Hell yes! Dude you rock! This just made my night!
[Galaxy Tab 2 10.1" Android Development] brolee93:
thanks shakaku
[Galaxy Tab 2 10.1" Android Development] Rahul721:
Great rom! It's fast, smooth and feature rich. My cyanogen roms were always slower than this...

Even the touchwiz Ui is perfectly smooth. I look forward to future releases.
[Galaxy Tab 2 10.1" Android Development] timboger:
Great Rom

You have managed to improve on perfection. Keep up the good work.
[Galaxy Tab 2 10.1" Android Development] shakatu:
I'm annoyed with the 4.1.2 launcher... Used to be you could tap on the edge to change homescreens rather than swiping, but that doesn't seem to be there anymore...
[Galaxy Tab 2 10.1" Android Development] shakatu:
GT-P5100 build added to OP please test and report.

Zap Apps updated with some apps from the P5100.
[Galaxy Tab 2 10.1" Android Development] irberserk:
Great Work!I really love your Rom. Thanks for your work :laugh:
[Galaxy Tab 2 10.1" Android Development] Und3rtaker:
+1 :)
[Galaxy Tab 2 10.1" Android Development] haaksbergen:
hangouts

thanks for his rom.

I have problems with hangouts. it crashes every time when i videocall try
[Galaxy Tab 2 10.1" Android Development] shakatu:
I'll look into it later. I might have to roll back the app updates I baked into the ROM... I just don't like having 50 updates when I first set my tablet up! LOL
[Galaxy Tab 2 10.1" Android Development] shakatu:
Temporary fix to hangouts:

Sideload the attached Talk.apk which will replace the one in system/app

Update Talk to Hangouts via play store

Future release will include the old talk app to be updated in this manner.
[Galaxy Tab 2 10.1" Android Development] haaksbergen:
thank you very much. it works again
[Galaxy Tab 2 10.1" Android Development] Skazzy3:
I JUST FINISHED PORTING 1.6 YOU FOOL.

JK. I'll download and port once again. And hopefully release this time.
[Galaxy Tab 2 10.1" Android Development] shakatu:
I didn't really make all that many changes to the stock ROM... :confused:

(Oh no!!! People might find out I don't actually know what I'm doing!!!)
[Galaxy Tab 2 10.1" Android Development] Lonedogg:
Hi shakatu,

I would like to try Your Rom.my tab2 10.1 (5110)

is on Stock jb 4.1.2 with Root

Can I use your ROM with jkay ?

possible?

my S3 &S2 runs with OmegaRom &Jkay

But for the fxxx TAB 's nothing to see from Omega :( comparable.

what I read so I like your ROM;)

Btw, the Bloatware only Complete Flash? , and after

via Rootexploer the unnecessary individually delete?

thx
[Galaxy Tab 2 10.1" Android Development] shakatu:
I don't know anything about those but the bloatware is an add-on you still need to flash the correct ROM.
[Galaxy Tab 2 10.1" Android Development] samsgun357:
Hey shak, I saw a thread of yours working on multi window but now I don't see it, where us it and how is it coming?

Cead mile failte
[Galaxy Tab 2 10.1" Android Development] anave:
amazing rom... smooth, clean, fast.... simple what i need...

thanks for the great job

im using gt-p5110
[Galaxy Tab 2 10.1" Android Development] reaverclan:
Great rom thanks for this I'm on P5113. Only thing I added was apex launcher.
[Galaxy Tab 2 10.1" Android Development] shakatu:
Moved to general forums as it isn't a development release. The dev forums are for releases I guess.
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
Hope to see the multi windows become a reality ;)
[Galaxy Tab 2 10.1" Android Development] derride8:
Deleted. ... I got it fix
[Galaxy Tab 2 10.1" Android Development] Und3rtaker:
How do i OC GPU? Installed clean Zap Blaster v2.0 for 5100, but by default system had default Cpu value 1008MHz. For Cpu OC i used No-frills Cpu control.

What do i use for Gpu OC?

Shouldn't this ROM be OC'd by default? Been readin in first post about removing OC by deleting 05zap in init.d folder, but i don't have this file at all..?

P.s. gooood and fast ROM, will stay on this :) thanks for great work.
[Galaxy Tab 2 10.1" Android Development] Skazzy3:
go to /system/etc/init.d and see if the file is there. if it isn't make a new text file called that with these contents

#!/system/bin/sh

echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_max_freq_idx
echo 1200000 > /sys/power/cpufreq_max_limit
echo 2048 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
echo "8192,10240,12288,28342,31041,33740" > /sys/module/lowmemorykiller/parameters/minfree

#!/sbin/busybox sh

# NFS filesystem
insmod /system/lib/modules/sunrpc.ko
insmod /system/lib/modules/lockd.ko
insmod /system/lib/modules/nfs.ko

# NTFS filesystem
insmod /system/lib/modules/ntfs.ko

To overclock gpu add this line to the end of the zap file

echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
[Galaxy Tab 2 10.1" Android Development] bone21121:
Dont work my gt 5100 3g missing sim card
[Galaxy Tab 2 10.1" Android Development] Und3rtaker:
file 05zap wasn't there so i made one. after reboot, CPU Spy shows max freq 1008MHz.? (before reboot i reseted max cpu value in No-frills to default- 1008MHz, just to see if this script works)
[Galaxy Tab 2 10.1" Android Development] rk73:
Same resultat for me on 5100 and the 05zap also broke video playback..

Regarding gpu the default value in gpu_oc file seems to be 1 but i dont how to check acctual gpu MHz.

However this rom is far the best i have tried for my device.
[Galaxy Tab 2 10.1" Android Development] shakatu:
I might have forgotten it in the 5100... :-S

I noticed the 00boot init.d script sets CPU at 1008 GHz. Seeing as 1.6 was the last kkboot kernel, and he's now on to a dual boot kernel, which removes all user scripts anyway, I'll redo the scripts for my next release.
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
[MENTION=4668253]shakatu[/MENTION] Now you can use NEXT 1.4 as your ROM kernel. All required scripts and binaries packaged in one boot.img, except PowerVR 3D vendor binaries. NEXT clean init.d scripts on every update. To make your scripts persistent, place it in /data/local/userinit.d/ .
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
I guess I blindly installed NEXT kernel1.3 not knowing it would work! Whoops! :p
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
NEXT work everywhere :p
[Galaxy Tab 2 10.1" Android Development] derride8:
Do anyone have a link to NEXT 1.4 kernel?
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
http://xdaforums.com/showthread.php?t=2302663
[Galaxy Tab 2 10.1" Android Development] Skazzy3:
Aww thanks.

I guess I'll use the next kernel in the port.

I'll send you a pm. I have some questions.
[Galaxy Tab 2 10.1" Android Development] shakatu:
Cool thanks I didn't want to step on any toes, especially since the Next kernel says not to use in ROMs, but since you've officially given me permission my next update will include it.

Don't anyone expect the update until the weekend. If I decide to work on it sooner, than woo-hoo, but I doubt it. I have other stuff going on. There are a couple things I know of that need fixed (boot script, Talk.apk) otherwise I wouldn't care to update this ROM anymore...
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
I forced my P3100 to use P51xx kernel. It's boot with swapped volume button, not working touchscreen, upscale graphics, a lot of dmesg error message, got full scale 1280x800 screenshots. NEXT 1.4 P51xx port totally based on NEXT 1.4 for P31xx except the kernel zImage and a little change in init scripts related to machine name (from espresso to espresso10). Is it possible to create a single ROM for all Tab 2 family? Maybe with one common flashable zip and one device specific zip.
[Galaxy Tab 2 10.1" Android Development] panda00:
You could use aroma and just allow the user to choosr his device in AROMA, anf ideally only the things that are different in ROMs of either devices are installed accordingly.

Sent from my GT-I9105P
[Galaxy Tab 2 10.1" Android Development] shakatu:
I mean that would be ideal but I'm not really sure how right now I'd have to look into it. My biggest issue is I don't have a 3G version so I can't really check to make sure everything works right if I do that. Plus there are some bigger differences between the 7" and the 10" ROMs, such as the 7" tw-framework.apk file is significantly larger than the 10" for who knows what reason...
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
With a smart flashable zip, no need AROMA at all.
[Galaxy Tab 2 10.1" Android Development] panda00:
Oh you mean using get.prop in the updater script to make a sort of installation script? Good idea.

Sent from my GT-I9105P
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
If there is spare time, I will try P5100 ROM on my P3100 (as 2nd ROM).
[Galaxy Tab 2 10.1" Android Development] shakatu:
I tried that a little bit once. Tried having separate build.prop files in separate folders so the device would have the correct name after install. My tab is a GT-P5113 and it would keep installing the GT-P5110 files for some reason... Even though the latest OTA I have flashed was the GT-P5113 4.1.1

Needless to say, I gave up on that dream. :(
[Galaxy Tab 2 10.1" Android Development] panda00:
I'm going to try something simple now, a zip with an updater script in it... only... The script will check if my ro.product.device is s2vep (GT-I9105P), my phone, or espresso10rf (GT-P5100), my tab... If it's the phone it should print "i9105p" and if it's tab it should print "p5100". Simple script really..
[Galaxy Tab 2 10.1" Android Development] shakatu:
It is a simple script, but like I said, mine is showing up as a GT-P5110 even though I know it's a GT-P5113, so that would cause issues for others as well.
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Parsing default.prop using a script outside updater-script will always work.
[Galaxy Tab 2 10.1" Android Development] Skazzy3:
Would it have to do with the get prop command?

So if get prop got espressowifi then it copy a build.prop from some folder into /system but if it got espressorf it would copy another build.prop in another folder?

Idk. I guess BASIC programming isnt the same as edify.

But in Dark Fantasy Adi makes you swap out the updater script manually.
[Galaxy Tab 2 10.1" Android Development] panda00:
Yes... so you would have another folder in the rom zip, other than META-INF and system... call it "decision" for e.g, and in it there are two folders, espressowifi, and espressorf.

So then you would have to write a getprop command to see if ro.product.device is espressowifi, it will do a package_extract for /decision/espressowifi/build.prop (or any other files) to /system partition. Else it would check if it's an espressorf again using getprop for ro.product.device, and package_extract /decision/espressorf/build.prop (or any other files to /system partition.
[Galaxy Tab 2 10.1" Android Development] shakatu:
Well I'm looking into the Aroma installer now so people can have some control over what happens, such as what kernel to use...

Edit: I got my environment all set up. I have a common folder with all the ROM files, then I have corresponding folders for 5100, 5110, & 5113 set up with their respective files, and lastly I have folders set up for each kernel. All that's left is wading through the Aurora script so it gives appropriate install options... And this is why I shouldn't look at the ROM until the weekend because then I work on it too long and don't get other stuff done.
[Galaxy Tab 2 10.1" Android Development] shakatu:
Zap Blaster v2.1

I should get a nobel prize for this...

Changelog for v2.1

Aroma Installer

- Choose ROM Version

- Choose Kernel

Fix Talk.apk

Fix init.d script & moved to data/local/userinit.d

That's right, I figured out the Aroma scripting and now it's an all-in-one installer! That's why the file is larger than before (but I was able to keep it below 600 MB).

When you install you can choose between 5100/5110/5113 as well as kkboot-nooc/kkboot-oc/next-nooc/next-oc kernels!

I tested several variations of the script itself and it went through them without error, then I installed using 5113 & next-oc and it worked!

If people want to modify my Aroma script for their own ROM/kernel go ahead, but give me credit!
[Galaxy Tab 2 10.1" Android Development] nasty007:
i have tried on P5100 and it did not boot, flashed twice but same thing
[Galaxy Tab 2 10.1" Android Development] shakatu:
No boot as in did not show boot animation at all?
[Galaxy Tab 2 10.1" Android Development] nasty007:
no, it was just black screen, no bootanimation, so I tried one more time, full wipe but same thing
[Galaxy Tab 2 10.1" Android Development] shakatu:
[ROM][4.1.2][GT-P51XX] Zap Blaster v2.1 *Custom*Fast*Smooth*Overclock*Stable*

TouchWiz Base

No where does it say STOCK.

I don't know what to tell you... I just installed on my GT-P5113 using the basic P5100 option and it started up just fine. The install script tells it to wipe the system partition so there aren't any leftovers...

Attached are some pics to show it works for me. In one you can see the power menu with the data enable option, in background you can see it's the 5100 build, in status bar you can see the no signal icon. In the other pic you can see in the multiwindow bar there are messaging and phone apps.
[Galaxy Tab 2 10.1" Android Development] nasty007:
I will try to redownload tomorrow, I also always check MD5 and it was ok, I will report tomorrow how did go, I have used your older versions and ROM was great
[Galaxy Tab 2 10.1" Android Development] panda00:
Perhaps this is the problem there... You're installing a P5100 ROM on a P5113 device... If it works for you, that doesn't mean it'll work for the guy with a P5100...
[Galaxy Tab 2 10.1" Android Development] shakatu:
I get that, but he said the previous version worked, and I literally went through and compared every file from the prior P5100 build to the P5110 build and kept every one that was different. It even uses it's own android.policy.jar, framework-res.apk, SystemUI.apk, and twframework-res.apk but since I don't have a GT-P5100 to test I don't know what else I can do. :(
[Galaxy Tab 2 10.1" Android Development] panda00:
I'll test it for you...

Sent from my GT-I9105P
[Galaxy Tab 2 10.1" Android Development] Und3rtaker:
Just installed 2.1 with 1.4 kernel oc version cpu on 1200MHz on my p5100. It was dirty install. Wipe dalvik cache, install rom, than fly-on v3.0 script. Oh, i installed it over v2.0.

ROM runs excelent. Aroma installer is just amazing.

Thanks for all hard and excelent work :)
[Galaxy Tab 2 10.1" Android Development] shakatu:
Yay! Glad to hear it does work with the p5100. So now I can rest.

My development attention from here on out will be MultiWindow. I'm feeling a little burned out from development right now (seeing as I've put too many hours in recently), so don't expect much for a little while...

BTW for people to troubleshoot themselves: Stuck on Galaxy Tab logo means you have no boot.img

Stuck on black screen after logo means you have no \system

Stuck on boot animation means there's something wrong within the ROM files

Seeing as the installer flashes a fully working \system before it installs your particular flavor means the problem lies elsewhere. I only test with TWRP so I'd try that if you're using something different.
[Galaxy Tab 2 10.1" Android Development] Skazzy3:
Fixed already? Wow. Downwodin'
[Galaxy Tab 2 10.1" Android Development] Skazzy3:
That made me crack up.

Anyways, porting is going fine.

I think I need to copy some modules over, Cuz it won't boot.

Or I think I tried to be a smartass and forgot to add a ramdisk to the boot.img's

Still trying!
[Galaxy Tab 2 10.1" Android Development] yakabud:
Can anybody post the link for V2.0

Sent from my Galaxy Tab 2 GT-P5113
[Galaxy Tab 2 10.1" Android Development] 19cam92:
HERE http://xdaforums.com/showpost.php?p=37596595&postcount=3
[Galaxy Tab 2 10.1" Android Development] xu7jp4:
Ahahahahahahahahahahahah:thumbup:

Envoyé depuis mon GT-P5110 avec Tapatalk
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Was busy making my own ROM (for my personal use only) and play around with Samsung's CSC. CSC has a simple protection that checks the size of every file by the contents of sqlite database /system/csc/contents.db . After changing a file, you have to change the file size definition in contents.db using an sqlite editor otherwise your change will not be applied. Now, my ROM has its own default wallpaper injected to wallpaper selector without editing any apk, default desktop arrangement, languages, etc only based on CSC editing. I hope this information is useful :good:
[Galaxy Tab 2 10.1" Android Development] CSP III:
[MENTION=4668253]shakatu[/MENTION].....You did a heck of a job with this Zap 2.1 Great work start to finish.

Edit: any thoughts as to why "Gallery has stopped" . Upon reboot of 2.1 install, message of unclean shutdown....values not applied. Cant access gallery, images stored on ext sd card if that helps. Same message every reboot with gallery stopped as well

Did normal basic 5113 install

Edit #2 Ok got values applied I think. Max clock was set [MENTION=409989]300[/MENTION] on boot. Not sure why. changed to 1.08 No more notice. However, Gallery is still "unfortunately gallery has stopped" Tried fixing perms, clearing cach and dalvik... no go

---------- Post added at 11:08 AM ---------- Previous post was at 10:36 AM ----------

Hey, upon trying a reflash I checked System info on installer page. Telling me I have GT-P5110. But actually is P5113 Should I be flashing the 5113 or 5110 ROM and what diff would it make?
[Galaxy Tab 2 10.1" Android Development] shakatu:
Try going into Settings>Application manager>All and select Gallery and Clear data

As for which version you install, the only difference between the 5110 and 5113 is the build.prop and the Peel.apk, so that isn't an issue. Mine is really a 5113 but reports a 5110 as well. IDK why it might have something to do with the recovery being build for 5110 idk.
[Galaxy Tab 2 10.1" Android Development] CSP III:
Thanks much. Funny thing though, upon reflash all good. Great work!
[Galaxy Tab 2 10.1" Android Development] ...Awesome...:
-Thread Cleaned

Please stay on TOPIC this is a Development thread don't make me revisit this thread...
[Galaxy Tab 2 10.1" Android Development] MrMagic:
[MENTION=4668253]shakatu[/MENTION]: I tried to upgrade my GT-P5110 to version 2.1 today. Everything seems to work fine, except that I cannot run the game WordOn HD anymore :(

I tried both the GT-P5110 and GT-P5113 builds, but that didn't matter. Also tried adding the bloatware, but that didn't matter either.

I tried a factory wipe which unfortunately didn't solve the problem either.

The game seems to startup ok, but after showing a black screen for a few seconds, I get returned to the start screen or app drawer without any error message.

Any clue as to why this is happening?
[Galaxy Tab 2 10.1" Android Development] shakatu:
No clue. :(
[Galaxy Tab 2 10.1" Android Development] wd5gnr:
I wonder a few things:

1) Do you have the Developer's Settings changed to use hardware accelerated draw? Try reversing that setting.

2) Are you overclocked? Try going to normal speed (1.08)

3) Have you messed with the CPU voltages? If so, maybe you haven't messed with them right. Each box is different. Mine takes a little bump to run reliably at 1.35.

Don't know that any of those things are likely, but worth checking.
[Galaxy Tab 2 10.1" Android Development] timboger:
I also have 2 games that do the same on 2.1. I had to go back to 1.6 to play them.
[Galaxy Tab 2 10.1" Android Development] MrMagic:
Thanks for letting us know, at least I know I'm not the only one :)

[MENTION=4668253]shakatu[/MENTION]: In answer to your questions:

1. I tried a factory reset and as far as I know that option is not turned on by default?

2. I was running the kkboot 0.6.0 OC kernel @ 1200, but I did the same on version 1.6 and never had any problems

3. I have not messed with the voltage settings

Unfortunately I can't experiment much, since this is my mom's tablet and I already went back to a TWRP backup of version 1.6 :)
[Galaxy Tab 2 10.1" Android Development] shakatu:
1.6 is 4.1.1 while 2.1 is 4.1.2

Maybe that makes a difference...
[Galaxy Tab 2 10.1" Android Development] Nicko_lefevre:
I think too...

Envoyé depuis mon GT-N7100
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
OMG! Been away for a few days and come back to Zap 2.1 Custom Install with AROMA (I love the name) Installer.. this is some quite extraordinary! I am really liking this.. recovery mode and installing ROMs is becoming more and more easier for dummies each day.. or so it seems!! I just went through the setup for using this as my secondary ROM on KK's DUAL BOOT and I am really liking this Tab 2 10.1 (p5113) more and more each day that I own one... you devs are really out doing yourselves... the only thing I see missing is the multi-window feature working and Ubuntu Touch to make this seem like a badass little tablet... Thanks! :D

BTW, just wanted to say 2.1 with NEXT kernel is working superbly for my 5113 tab 2 :thumbup::D
[Galaxy Tab 2 10.1" Android Development] samsgun357:
Did you guys restore these games from a backup or redownload? I'm finding more and more apps that behave like that when restoring from a backup.

Lies, spewed poetically from galaxy S3!
[Galaxy Tab 2 10.1" Android Development] CSP III:
Same here. Re-download apps. Try individual data restore. Most work, some just don't. ROM is sweet nevertheless.
[Galaxy Tab 2 10.1" Android Development] -Majkel-:
Anyone have problem with charging? Whenever i have less than 20% sometimes i cannot charge tablet. It has some same issue like when connecting charging throught usb.