yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Just copied the 3 files (downloaded from my github repo), manual set the permission to 644 and reboot, my camera and hardware acceleration still works! It's strange, CM updater script will always be set proper permission for files.

Yea, NEXT 2.0 feel so smooth so far. Overclock code is no longer needed :D Samsung kernel team have done a very good job :good:
[Galaxy Tab 2 7" Android Development] kendragon:
With last build titanium backup doesn't works
[Galaxy Tab 2 7" Android Development] kenundrem:
Working for me...did you check to make sure you gave root access under developer settings to apps and adb? I just did a full batch backup/restore with ti backup...check your settings sir
[Galaxy Tab 2 7" Android Development] kendragon:
try but doesn't works :( It starts but doesn't restore backup
[Galaxy Tab 2 7" Android Development] CodyF86:
It must just be the permissions [MENTION=4021423]ketut.kumajaya[/MENTION], I can just adjust my installer-script if it's being weird, you rock! :good: :)
[Galaxy Tab 2 7" Android Development] CodyF86:
Hmm, it wasn't the file permissions it seems to be the actual files, but

Ketut merged the new 3 files into the github repo like 20 minutes before

I synced it, so tonight I'll just manually drop the 3 files in my build directories

to make sure for now.

I think there was just some wonkyness with syncing last night.

[MENTION=4021423]ketut.kumajaya[/MENTION] you know how I told you the battery percentage

wasnt there with your preview when I tried it, but it was there with

the stock updated kernel when I tried it. Well I turned my tab

on today after charging it last night and the percentage was gone,

but reflashing brought it back on stock updated kernel.

Seems plugging your tab in to charge is what triggers the percentage

going away. It's just the circle with percentage that does it, all the other

types are fine. :)
[Galaxy Tab 2 7" Android Development] CodyF86:
Bam! Like Emril! haha :)

Fixed it, (the 3 file thing), were back to one file now.

Here are the updated 0824, but all this does it make it

so you only have to flash the rom. If you already have 0824

up and running with the second file flashed don't worry about it,

0825 will be a single file also.

Kenundrem, I already uploaded the fixed rom, but starting with

0825, ill give you some props too in the rom flash header, thanks

for saving me. :) (Ketut your name is already in it. :good: )

20130824-

p3110 / p3113 /wIR: http://d-h.st/Giq

p3100: http://d-h.st/F86

Nothing changed with the actual system, TabletUI patch is the same.

If you use the battery style circle with percentage, and at some point

the percentage goes away, just use a different style for now, gonna

try to look into that also, reflashing will bring it back.
[Galaxy Tab 2 7" Android Development] sorullo_xgrx:
Just FYI guys my extsdcard is dead while using build 0822.. Maybe is my bad luck or some went wrong but yesterday while using my tab it went dead battery I plug in to charge I let it charge when I turn it back on my extsdcard was not mounted I try rebooting, flashing ROM again.. It was not recognize as mounted in recovery either.. PC same thing not mounting or rewarding .., my guess is completely dead... I assume it happen for letting the battery to go dry.. :confused:
[Galaxy Tab 2 7" Android Development] CodyF86:
No it happened to someone a day or two ago, wasn't anything with the rom,

SD cards just get wonky sometimes. You'll need to download a program that

will let you reformat and check the sd card for errors and it should come back to life

at least it did, for....it was Kenundrem or F3AR maybe, they posted a link to the

program that will fix it like 4 or 5 pages back..ish. :)

Sounds like your ext SD card was being written to when the battery died,

and it didn't like that, it is recoverable.

You can bring it back to life, check a few pages back on this thread until you run into

the person that, that happened to.

[MENTION=4289544]F3AR420[/MENTION] your post on page 51 says you used a program

/ command line program to fix your SD card, can you tell ^^ exactly

what you did. :)
[Galaxy Tab 2 7" Android Development] sorullo_xgrx:
i defintly need help on this as i already try a program but that cant find my sdcard either.. im lost:eek:
[Galaxy Tab 2 7" Android Development] CodyF86:
Let me see what I can find, F3AR will respond at some point today also im sure.

When you let your battery die all the way with your tablet on, your external

SD card was being written to, then it lost power and corrupted your external

SD card.

Never let it die all the way when its turned on. :)
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=4428595]sorullo_xgrx[/MENTION]

Put your sd card in a windows computer and open up a command line.

Issue this command: chkdsk /X /F <SD card drive letter>

That should fix it for you, let me know.

EDIT: Open your command line up as administrator also.

If that doesn't work you can try this also: https://www.sdcard.org/downloads/formatter_3/

Also check out this thread: http://xdaforums.com/showthread.php?t=367912&page=1

Because I'm getting all this from there. lol :)

Here's another one: www.squidoo.com/freeware-for-sd-card-recovery-problem2

Another last resort is: "chkdsk /X /F /V DriveLetter:" "for a semi-destructive repair (lost chains will be cut)"
[Galaxy Tab 2 7" Android Development] sorullo_xgrx:
I try everything .. Thanks for all the help. Hope I'll get it running.. I just install the latest build ;) I know is not ROM relating and I'll stick with your ROM and maybe get another SD :)
[Galaxy Tab 2 7" Android Development] CodyF86:
I know, I just mean't not to let it die while its on and doing stuff. :)

One of the programs I listed should recover it for you just fine.

Let me know. :)
[Galaxy Tab 2 7" Android Development] trmitche2:
Another dumb problem I'm having with this excellent ROM:

I downloaded the themechooser fix zip file from the OP, and flashed it from CWM recovery, but even after doing so, when I try to apply any of the BetterBean CM10.1/2 themes from settings/themes (which are compatible with Android 4.3), I'm still getting the error message: "This theme is improperly compiled and cannot be applied.", without the option to "install anyway".

As I understand it, the zip I downloaded and flashed changes my DPI from 160 to 159 in my build.prop file, so why wouldn't this work, and let me apply my beloved themes? If it matters, I'm on the 08092013 build with Nova launcher & TabletUI installed, and I'd like to keep it that way if at all possible.

Thanks button waiting for any helpful replies as always, even if said posts contain bad news about my ability to keep TabletUI and still use the BetterBean themes I like so much....

Thanks again for all your work just for our P3113 IR-capable devices. We'd be lost without you bro!
[Galaxy Tab 2 7" Android Development] CodyF86:
I've honestly never messed around with DPI, so someone else might

be able to answer better, but try to change the DPI manually in the

build.prop like you said.

It sounds like its still just saying no because the DPI isn't right,

there is no actual reason why the theme wouldn't work, so yeah

try it manually first, and i'm sure some other people will have

a few ideas. :)

Use a program like system tuner to edit your build.prop.

If you do it manually (with a text editor) you will need

to make sure it has rw+r+r permissions when your done

with it, or it will hang on the first samsung screen if the

build.prop permissions are wrong.
[Galaxy Tab 2 7" Android Development] CodyF86:
Here is another present for you guys. :)

A new recovery 6.0.3.7 that allows you to make

your nandroid backups in compressed tar + gzip

format and restore from the compressed format also.

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

You can choose the format by going to backups and restore

then choose default format option at the bottom. :)

p3110 / p3113: http://d-h.st/x33

p3100: http://d-h.st/j1v

Will update with p3100 shortly.
[Galaxy Tab 2 7" Android Development] kenundrem:
I found the thread where I got the original zip from here http://xdaforums.com/showthread.php?t=2258012

as per the dev he says "dont forget that themes for hdpi or xhdpi still not optimized for your device dpi so this may be the price we must pay when using it!"

I always had success when flashing themes and using this mod - however I didn't go crazy and flash a bunch only tried a couple free ones. Lately I have been using Nova Launcher with Icon Packs and really just like to leave everything else as it is - nice and clean. So...it is possible that even with this mod there are themes that will not work.

EDIT

Also I find this in most theme description on the play store this is from Betterbean CM10 Theme https://play.google.com/store/apps/details?id=com.blackout1911.theme.BetterbeanThemeGreenFree

### HOW TO ###

1. Make sure you have CYANOGENMOD 9/10/10.1/10.2 , AOKP, PARANOID ANDROID, CNA, CARBONROM or any other custom rom installed that supports T-Mobile Theme Engine! (otherwise it wont work!)

2. Install Theme!

3. Goto Settings -> Themes -> Apply it

### PLEASE READ IF YOU HAVE PROBLEMS ###

- 'improperly compiled'-Error: Apply system theme, reboot your phone, apply this theme! (for tablets: Set DPI from 160 -> 240 temporary. then apply theme. then change back dpi.)

If this doesn't fix, try: uninstall theme -> apply system theme -> reinstall and apply theme!

====

- "Missing Assets for device's screen size."-Message: Ignore it! Apply anyway!

====

- Please send me an email before leaving a negative comment! I will try to help you!

====

I would say some of it just has to do with all the different screen size/resolution on Android it's hard to make a universal theme that will work for all device without something funny happening somewhere...just my 2 cents? Anyone Else?
[Galaxy Tab 2 7" Android Development] Android-Andi:
Flashable zip uploading :) - Finished you´ll find at #603
[Galaxy Tab 2 7" Android Development] trmitche2:
Good not know Cody (all of that), so I'll err on the side of caution, & check out the "System Tuner" app you mentioned, while awaiting further replies with other suggestions from folks more familiar with DPI-related issues. I still cant help but wonder if themes built for the theme chooser built into CM just don't know what to make of TabletUI... Anyone else think that's possible? Or, more to the point, does *anyone* out there have themechooser themes running properly *with* Nova Launcher AND TabletUI also installed?

Thanks as always....

trmitche2
[Galaxy Tab 2 7" Android Development] Android-Andi:
Recovery as flashable zip:

GT-P3110_ClockworkMod-Recovery_6.0.3.7-V6_Non-Touch-UNOFFICIAL.zip

MD5: 71B5E4DB15B982B9F393B6F85F66A0C1

GT-P3100_ClockworkMod-Recovery_6.0.3.7-V6_Non-Touch-UNOFFICIAL.zip

MD5: 13DE5C71478A4B0428E24BE7FFD7E911

Use on your own risk ;)
[Galaxy Tab 2 7" Android Development] trmitche2:
OK, so I installed System Timer, and all I can say is... Woah. There are so many settings in this app that I'm afraid to touch a single thing, for fear of bricking my tablet, and ending my love affair with it in the worst possible way. Talk about a bad break up. I'm already in withdrawals from the True Blood season coming to an end after only 10 episodes (think I may need to find a support group forum for that), so I'd prolly have to just off myself entirely if I lost the tablet too, especially if I lost it to to "Hep-B" ("Hepatitis-Brick". Fellow Truebies: insert LOL here. Everyone else, please disregard the preceding sentence entirely.)

So, all joking aside, does anyone here have enough experience with the System Tuner app to direct me to the screen where I can check my DPI settings? For context, see my ongoing dialogue w/Cody over the past couple of pages about DPI size in relation to the ability to apply themes from the native theme chooser built into CM settings. Specifically the BetterBean CM10.2 color variants. All I really want here to be honest is to have NO apps with white backgrounds, so if there's another, easier way to achieve that, inn all ears. Thanks everyone who went to the trouble of reading all of this, and I honestly hope I made 1 or 2 True Blood fans chuckle out loud with the Hep-B joke. ;)~
[Galaxy Tab 2 7" Android Development] CodyF86:
If you use system tuner to open up the build.prop, the build option in tuner.

You can look for a setting called ro.sf.lcd_density= and it should be

set to 160 I think, you can just change it to 159, by pushing the pencil

looking icon next to it, if that's what the themes need to work DPI wise. :)

The setting is prob toward the bottom of the list.

Then reboot. :)
[Galaxy Tab 2 7" Android Development] trmitche2:
Gonna try it right now, wish me luck. If I come back posting from my phone or laptop, then you'll know I'm officially in hell, although even then I'll still be hoping for someone to laugh at my True Blood joke...
[Galaxy Tab 2 7" Android Development] CodyF86:
Theres nothing you can do to the build.prop that reflashing the rom won't fix. :)
[Galaxy Tab 2 7" Android Development] kenundrem:
[MENTION=1529917]trmitche2[/MENTION] here is a screenshot in system tuner
[Galaxy Tab 2 7" Android Development] trmitche2:
OK, I just changed it to 159 and exited the app, but when I go back into the app, the number 159 is in blue text. Is that normal, or is there a save button In missing?

Also, still getting the the same error when trying to apply a theme. Do I need to reboot the tablet for the DPI change to take effect?

Sorry... Never mind, you already said: "then reboot". So... Here goes nothing...
[Galaxy Tab 2 7" Android Development] CodyF86:
It saves as soon as you make the change and yes you need to reboot first, make sure its at 159 then reboot.
[Galaxy Tab 2 7" Android Development] Skazzy3:
You don't acutally need System Tuner. You can just download a build.prop edior from the play store. Download the one my jrummy apps.

Edit: I see you already solved your problem. Nevermind.
[Galaxy Tab 2 7" Android Development] trmitche2:
That just worked dude! I SOOOO LOVE YOU right now! Couldnt give a sh1t how gay that sounds either. Do you have a donate setup?

Now, if I can just get someone other than Cody to acknowledge my True Blood joke, even if only to say it wasn't funny, this'll be a perfect day.
[Galaxy Tab 2 7" Android Development] CodyF86:
Lol it's fine, don't worry about it....and no one thinks your funny. =P lol j/k :)
[Galaxy Tab 2 7" Android Development] kenundrem:
[MENTION=1529917]trmitche2[/MENTION] sorry man I don't watch true blood but I would feel like offing myself if I had to sit thru it...
[Galaxy Tab 2 7" Android Development] trmitche2:
Lololol
[Galaxy Tab 2 7" Android Development] Jiangyi:
Thanks for the heads-up, already informed Cody. Let's see what happens, but it might take a while since cody's really busy and I don't actually have a Tab 2 to work with.
[Galaxy Tab 2 7" Android Development] CodyF86:
Hey Ji,

It's actually at the point now, where it could literally be merged back into

the CM github and work fine. One line needs to be added to a file

in the muppets samsung blob common make file, that I'm going to

confirm makes a completely happy rom without doing anything to the zip file.

The correct libon_ti.so wasn't being copied to the rom once it was made,

but adding that line, should fix it and im going to confirm tonight.

Look over in Ketuts thread for the addition that would need to be made,

then the updated kernel source could be merged back also from Ketuts fork.

and it would just work, its already working on this rom.

The reverts to some 4.2.2 file would need to be done also, in

the muppets, but those changes are already merged into ketuts

fork of the muppets.
[Galaxy Tab 2 7" Android Development] CodyF86:
Hey guys,

Here is 20130825 for p3110 / p3113 w/IR: http://d-h.st/5VY

TabletUI: http://d-h.st/93U

I have a nice suprise for you guys, along with only needing to flash the

normal rom and were still using the updated kernel. I have included

the CMAccount app, that has been announced, but not rolled out on

nightlies yet.

http://www.cyanogenmod.org/blog/cyanogenmod-account

It allows you to, as I understand, track your tablet if it were to

ever get stolen, and even wipe its data if it gets stolen. Setting

up an account is optional. You might get a surprise right after you

boot up, it's pretty cool. :) You can skip making an account if you

scroll to the right once or twice if you don't want to atm, and reaccess

it in settings I believe.

You can add an account under settings, to make

an account at anytime if you skip it at the first bootup.

Please read the link above to understand wtf I'm talking about. :)

Also, if you get some flickering between the first samsung screen

and the lock screen, the bootloader on some devices of our

devices will need an update at some point to fix it, but if you

do experience that, it always boots fine, but might flicker once or twice

before the messed up CM boot screen lol. :)

But it does not effect anything, always boots, and the updated kernel runs way better! :)

I haven't had ^^^^ happen on 0825 yet, so knock on wood tho, maybe its just happy now. :)
[Galaxy Tab 2 7" Android Development] CodyF86:
If you do make a CM account you can go here:

https://account.cyanogenmod.org/login

To login and track your device to see how it works, if you

use it and your device got stolen, you can track the people down

and beat them, haha. :)
[Galaxy Tab 2 7" Android Development] CodyF86:
Pretty cool:

Street names removed to prevent stalkers. haha =P

Ill build p3100 with this tomorrow also. :)
[Galaxy Tab 2 7" Android Development] anjaykumar:
Just a question I am next 1.8.3 do I need to flash old vendor blobs to update to the new espresso kernel :confused:

You can't control the wind, but you can adjust your sails

Sent Form My Galaxy Tab 2 GT-P3100 ,Dual booted using Black Hawk Kernel:)
[Galaxy Tab 2 7" Android Development] CodyF86:
If you want to use the updated stock espresso kernel, you just flash the rom.

Or if you want to use 1.8.3 just flash the kernel, you don't need to flash either

blobs, they are included in this rom.

You can try ketuts 2.0 preview also, which is based off the updated stock

kernel.
[Galaxy Tab 2 7" Android Development] NMCBR600:
Flashed the latest rom and could not put the tab to sleep. P3113. Flashed kernel 1.8.3 and can now use the power button to put the tab to sloop.

Since going to 10.2, I cannot use my favi Bluetooth keyboard. The pairing appears not to complete.
[Galaxy Tab 2 7" Android Development] hkjr:
there's a 2.0 preview?
[Galaxy Tab 2 7" Android Development] NMCBR600:
I've tried the preview 2 kernel and the keyboard still dose not work. Alocat is not showings any info so I cannot provide additional log data. After entering the pair key number, the keyboard looks like it has not received the final pairing sequence.
[Galaxy Tab 2 7" Android Development] CodyF86:
What logcat command are you using? adb logcat -C *:W

will give you all the warnings, errors and fatal

errors in color.

Might have to look at the debug logs too so:

adb logcat -C *:d

Can you try pairing the keyboard to another device or a computer to see if it will pair.
[Galaxy Tab 2 7" Android Development] CodyF86:
Hey guys I also mis-spoke about a previous post.

IF you want to use NEXT 1.8.3 on this rom now, because

of the 3 files that changed to make the stock updated kernel

work you might have to install the new vendor blobs on ketuts

second post if you use 1.8.3 for video to work. :)

gonna confirm in a sec.
[Galaxy Tab 2 7" Android Development] NMCBR600:
I've paired it to my phone running 10.2. Alogcat app is not showing any logs. /dev/log/* does not exist.
[Galaxy Tab 2 7" Android Development] CodyF86:
Whats the date on the 10.2 rom because I haven't changed anything with bluetooth. :)
[Galaxy Tab 2 7" Android Development] Android-Andi:
[MENTION=5337314]CodyF86[/MENTION]

I tried to write openrecoveryscript to update the recovery using a batch. I don´t got it work... any ideas?

openrecoveryscript

set tw_signed_zip_verify 0
install /sdcard/recovery/recovery.zip
wipe cache
wipe dalvik
set tw_signed_zip_verify 1

batch

adb.exe shell mkdir /sdcard/recovery
adb.exe push "openrecoveryscript" /cache/recovery/openrecoveryscript
adb.exe push "recovery.zip" /sdcard/recovery/recovery.zip
adb.exe reboot recovery

----

I can´t get it work with PhilZ Touch. But it takes my "openrecoveryscript"

I:Script file found: '/cache/recovery/openrecoveryscript'
I:Running openrecoveryscript....
I:script line: 'set tw_signed_zip_verify 0
'
I:command is: 'set' and I:value is: 'tw_signed_zip_verify 0
'
Setting function disabled in CWMR: 'tw_signed_zip_verify' to '0
'
I:script line: 'install /sdcard/recovery/recovery.zip
'
I:command is: 'install' and I:value is: '/sdcard/recovery/recovery.zip
'
Installing zip file '/sdcard/recovery/recovery.zip
'
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard

-- Installing: /sdcard/recovery/recovery.zip
Finding update package...
I:Update location: /sdcard/recovery/recovery.zip
I:setting up /data/media(/0) for /sdcard/recovery/recovery.zip
.
I:using /data/media/0 for /sdcard
Opening update package...
[COLOR="Red"]E:Can't open /sdcard/recovery/recovery.zip
(No such file or directory)
Installation aborted.
E:Error installing zip file '/sdcard/recovery/recovery.zip
'[/COLOR]
Done processing script file
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
Log copied to /sdcard/clockworkmod/philz_recovery.log
Send philz_recovery.log to Phil3759 [MENTION=243864]xda[/MENTION]
[Galaxy Tab 2 7" Android Development] CodyF86:
[MENTION=5153662]Android-Andi[/MENTION]

Yeah recovery uses 2 different directories and they are almost identical.

One is /data/media/0 the other is just /data/media/

looks like /sdcard is going into /data/media/0 and not /data/media

For example nandroid backups go to /data/media

but your actual internal sdcard is /data/media/0, try the opposite

directory. :)
[Galaxy Tab 2 7" Android Development] Android-Andi:
On PhilZ Touch:

/sdcard not working

/sdcard/0 not working

/data/media/0 not working

/data/media/ not working

Your unofficial cwm didn´t try to start the script...
[Galaxy Tab 2 7" Android Development] CodyF86:
Sorry, you've confused me, your issue seems to be with directories,

/sdcard is /data/media not /data/media/0 I believe. If you script

won't start then somethings wrong with it =P, let me look at it

some more.
[Galaxy Tab 2 7" Android Development] CodyF86:
clockworkmod uses a directory called clockworkmod in /data/media

and a directory called clockworkmod in /data/media/0, put the file

in both those directories.

and if it works, remove one from one directory to see which one it needs to be

in.

/sdcard/recovery is either going to be, /data/media/recovery or

/data/media/0/recovery, just try both see which one it actually is.
[Galaxy Tab 2 7" Android Development] CodyF86:
Also,

my bad guys if you use blackhawk 1.8.3 you need to flash his new vendor blobs

now for the video to work on 1.8.3 since we've updated to the updated stock kernel.

Once NEXT 2.0 comes out then you won't have to, as 2.0 and the stock updated kernel

use the same blobs.
[Galaxy Tab 2 7" Android Development] Android-Andi:
adb.exe push "openrecoveryscript" /cache/recovery/openrecoveryscript

adb.exe push "openrecoveryscript" /data/media/clockworkmod/openrecoveryscript

adb.exe push "openrecoveryscript" /data/media/0/clockworkmod/openrecoveryscript

openrecoveryscript not starting in recovery... (CWM 6.0.3.7-V6)
[Galaxy Tab 2 7" Android Development] CodyF86:
All the patches I compiled into that recovery is now merged into the CM github, so thats

cwm how it is from CM, what do you mean its not starting, you mean the error you got

on the other page?