yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] xfaceman:
what is the torch and swagger togglers

somebody help me//....
[Galaxy Tab  Android Development] gwbard:
torch is the flashlight (camera led)

swagger is... um... well... if you don't know, you don't have it :p
[Galaxy Tab  Android Development] ash99:
Thanks for all the useful information ;-)
[Galaxy Tab  Android Development] xfaceman:
is it ok when you have build 36 as your current rom and your gonna install build 37 or i'm gonna restock to 2.3.3 gingerbread again....???

sorry for my bad english
[Galaxy Tab  Android Development] mjrshark:
No you dont have too , download and flash
[Galaxy Tab  Android Development] xfaceman:
thanks:):):)
[Galaxy Tab  Android Development] rikiau123:
to 36 for 37 only wipe cache and dalvik cache? thanks :confused:
[Galaxy Tab  Android Development] xfaceman:
i think wipe data and factory is include
[Galaxy Tab  Android Development] droiduzr2:
@Stimpz

Can we just flash ove B36r or will this wipe data also.

Yes, to wipe cache and dlvik cache first.

---------- Post added at 05:33 PM ---------- Previous post was at 05:23 PM ----------

btw- I noticed in Build 36 my caller id started working. It did not show the info in Build 35 or Milestone 5.
[Galaxy Tab  Android Development] 123Kage:
how about cm-9-20120526-NIGHTLY-p1 to this AKOP build 37.

Do i need to restock with JQ1?

Thanks
[Galaxy Tab  Android Development] salahmed:
I read the installation in the first page over and over and couldn't get an answer about that, so I wiped only cache and dalvic cache, and so far everything is ok, I loved the new toggle layout with the additional toggles, hiding nav bar in shadow mode is working again but if you enable this feature and use the camera"which is working smooth now" and want to exit then either enable nav bar toggles in power button and use back button or just hold power button the nav bar will appear then quickly press back in the bar twice.
[Galaxy Tab  Android Development] hinirang:
former aokp user here!

minor questuon: is the spacing between the navbar buttons still too close apart?
[Galaxy Tab  Android Development] droiduzr2:
I see a lot of questions with the Navbar stuff.

I don't use it at all. We have buttons.

I use Go Launcher Ex and along with turning off the Navbar.

It is pretty damn cool plus I don't have any of these Navbar issues.

What is the purpose of using the Navbar to take up screen space just to display what your built in buttons do?
[Galaxy Tab  Android Development] droiduzr2:
2 Questions

1. How do you make the icon text larger? Just the text under the icons.

2. How do you make the Power Widget smaller?

@Stimz or anyone other Dev

Can you make the stock power widget bar thinner. It's too tall for no good reason. Is there a better Power Widget bar you suggest from the market?

thx

I installed B37 and it's working just fine. The soft buttons lights turn off:D
[Galaxy Tab  Android Development] D.O.C:
We cannot possibly read all open threads in xda, just use the report button when you find a post violating our forum rules and we will take care of it. We do need your (all users) cooperation. :)
[Galaxy Tab  Android Development] yappoe:
Nope it looks very nice with smaller buttons.

1. We can have up to 5 buttons of Nav bar with 10 different commands (including long press).

So it takes less space than using dock in the go launcher.

2. Some people prefer soft button over the capacitive because the way kids accidently press them while playing games.

I personally use both the capacitive and soft buttons. I just replace the back, home and menu buttons with phone, messaging, browser, dtc. With other commands for the long press (such as if I long press the phone, I go to the contacts).

So if you can be creative, this customize nav bar is very useful and powerful. No more dock is needed.
[Galaxy Tab  Android Development] Assimilated Android:
LOL! Coming directly from Overcome 4.1.0 and very thankful! Everything is settling now, but was pretty wild to start. First flash got stuck in a wicked boot loop. Tablet acted possessed then was able to get into recovery, ha! Re-flashed and B-I-N-G-O! Thank you guys for all your good, hard work!
[Galaxy Tab  Android Development] nemory:
Should I still wipe/factory reset if I install Build #37?

Should I still wipe/factory reset if I install Build #37?

Please guys. I already downloaded a lot of apps on my tab using Build #36.
[Galaxy Tab  Android Development] mattman83:
If you read the install instructions you would know the bootloop was expected.

M.
[Galaxy Tab  Android Development] Assimilated Android:
Yeah, but I got stuck in it and my Tab did not respond to anything.. So yeah, I read all the instructions prior to flashing bro. Thanks for caring tho..
[Galaxy Tab  Android Development] stimpz0r:
you should be fine installing it over the top (though a dalvik cache wipe shouldn't hurt), but if you have any problems, always factory reset / dalvik cache wipe before reporting them here.

as mattman83 stated, it states that a bootloop will occur in the installation instructions. the only way to get out of it is to use the recovery button combo (power + volume up - and you have to hold it from the second the power goes on, to the point where recovery starts), otherwise it will get stuck in that loop until you do. this is part of the conversion to MTD.
[Galaxy Tab  Android Development] stimpz0r:
as in a scroll bar and a fixed size instead of so many it goes out of the screen? thats actually something i plan to do. we have too small a screen space (at 160 dpi) for too many notifications. i will attempt that one for a later build. :)

... nothing for you to worry about really. torch doesnt work (supposed to use the camera flash as a torch) and swagger is something specific to the galaxy nexus i believe (either way we dont have it, and its now disabled as a toggle in build #37)

you shouldnt need to restock at all, just make sure you do a factory reset / wipe dalvik cache and you should be fine.

too close how? i personally think the spacing and fact you can have 5 buttons in the navbar as a much better feature than 3 overspaced buttons, but thats personal opinion.

personal opinion / taste. some people find it better with soft buttons, some people prefer hardware buttons. thats why ive got it so the user has the choice to do what they please. :)

you are exactly right there, itd take a team of 100 people to spend every waking hour of their day to patrol XDA and read over everything. my method to help this is starting a website for this rom, with a bug tracker, and detailed install instructions / FAQ section to help everyone get the answers they are looking for. this should help cut down on the excessive amounts of posts that appear in threads like this, and make it easier on the moderators (in theory!)

though it is good to know that the moderators occasionally drop in here to check up on things. thanks for taking some time to stop by again D.O.C! ;)

EDIT: look at the length of the last 2 posts i have done just to answer under 24 hours of posts... thats practically a page in replies. all the more reason i hope the website takes off for this one and helps answer everyones questions! :D
[Galaxy Tab  Android Development] yosup:
stimpz0r covered torch above, but as for Swagger (lol) ... :what:

roman (from AOKP) reveals the truth behind the Swagger Toggle mystery in this episode of RootzLive Ep#2.

RootzLive! Episode #2 (Andy's Threads And Roman Birg From Team Kang!) ~ By RootzWikiTV

http://www.youtube.com/watch?v=5ivVwCEbo9c&feature=youtube_gdata_player

* 33:30 ... interview with roman starts

* 44:30 ... swagger toggle truth is revealed :cool:

Btw ... he really does look 17 in the vid (definitely the haircut) ... tho he's 21 at the time of this interview. :D

Anecdote ... the first time I used the Swagger Toggle was on my phone (Samsung Vibrant), and I was kinda freaked 'cuz I couldn't turn it off!!! Lol. They got me. :rolleyes:
[Galaxy Tab  Android Development] AllInTheKnowledge:
Thanks for releasing this MOD. I've been waiting for something of this quality before taking the plunge on my P1000.

Will install tonight over the Stock ROM. Will report back any issues.

Thanks again.
[Galaxy Tab  Android Development] xfaceman:
my problem is the music player always duplicate the song after reboot .....

and titanum back up when i restore my app ....there no app on my drawer

anyone know how to fix this
[Galaxy Tab  Android Development] Bad2hold:
Came from #B36 just flashed it in recovry plus Gapps, no wipe at all, works just fine. Thanx for your great work i just hit the paypal buttons ;-) Doesnt shut down anymore and i love apollo in combination with the DSP Manager, could play with the bass for hours... i removed superuser and installed SuperSu to play movies in googles play movies app.

One thing: i noticed that i can to turn on Direct Wifi in #B36/37. (Shut down or crashing issues in previous builds) but thats all, no settings or found devices for wifi dircet. Iam able to find it with other devices but cant connect. Is it supposed to work so far? Nothing mentioned about it... thats the last feature iam missing!! :)

Once again, thanx a lot guys!!
[Galaxy Tab  Android Development] linux150:
Hi !

i did restock my tab, then install overcom rom and now i want to update to B37

I did download twice but all i get in recovery when i try to install the zip is

Can´t open /sdcard/aopk_p1_build-37.zip (bad)

Any help what i´m doing wront :confused:

lg

linux150
[Galaxy Tab  Android Development] cdesai:
Re-download the zip, bad zip indicates a failed download | corrupt zip
[Galaxy Tab  Android Development] agustincordoba:
Really good build.This can only get better. Installed build 37 this morning so far everything is working perfectly, though haven't tried USB mass storage yet.

Congrats to one really great developer who brings this new life to our old tabs

Enviado desde P1000 con Tapatalk

Sent from P1000 via Tapatalk
[Galaxy Tab  Android Development] 123Kage:
Wow! Now in 37 Build, bluetooth works well with Skype. haven't test with other VOIP yet.

NB.. i personally prefer Adw launcher.

Thanks for bring me such cool ROM. Hope camera will be worked in next build. :)
[Galaxy Tab  Android Development] droiduzr2:
The camera IS working in this build.

I discovered that IF TORCH IS ON then the camera will NOT work.

Turn off torch. I also used another camera app and it worked fine (procapture).

The front and rear cameras work.
[Galaxy Tab  Android Development] agustincordoba:
To take photos with the camera apk I now let it autofocus, whereas before I had the focus fixed in infinity. The trick is to release the shutter just glancing the onscreen button VERY slightly, it then focuses and takes the shot.

Enviado desde P1000 con Tapatalk

Sent from P1000 via Tapatalk
[Galaxy Tab  Android Development] 123Kage:
Yeah.. it's worked. Thanks agustincordoba for your tips. :)
[Galaxy Tab  Android Development] ejgutierrez:
some questions

Im newbie with galaxy tab, and i have build 34 with mtd.

1 - Do i have to restock to update to #37 ? Or just wipe is enough?

2 - Possibly bugs as i dont know:

- Cant use magnifier apps ( means it doesnt work zoom in camera). Perhaps a known bug...

- I cant play to games like riptide or air penguin or coin flip...It doesnt work the tilt in order to move the characters ( ex: in riptide i cant move right, left the moto, in air penguin i cant move left, right the penguin...). Just another known bug or perhaps in development stil ?

3 - The best rom settings in overcloquing is 1200 max, 200 min and governor ondemandx ?

4 - Why these roms havent an ota update like oficial roms ? Just curious, when a rom gets a certain madurity and stability.

Thanks in advance...
[Galaxy Tab  Android Development] droiduzr2:
:D:D:D:D:D
[Galaxy Tab  Android Development] mao_red:
just to report:

When searching for music file in Apollo, search results text become distorted in gray color. Tried to reboot unit, same result.
[Galaxy Tab  Android Development] mattman83:
Here's a link for you. It contains all the information you need to get everything working and also get ota updates for ics.

http://lmgtfy.com/?q=galaxy+tab+2+7in

M.
[Galaxy Tab  Android Development] slyv3:
That's a neat feature!! So if we really like a lot of docked shortcuts like, we can even use the dock functionality for more additional shortcuts, that way we have the physical buttons (4 buttons), nav bar (5 buttons, 10 commands), plus dock -- maximum 9 buttons -- Total 23 unique commands in 18 buttons!!! Thanks for the hint, Bro! -- Thanks!
[Galaxy Tab  Android Development] priyana:
1) No need to restock. But reading your next questions, seems like you need to restock. Your accelerometer isn't working.

2) don't know...didn't use those.

3) there is no one best setting for all. Depends on usage and what you use it for.

4) who says AOKP is a mature ROM? It is still being developed. Maybe when Jelly Bean arrived, the ICS version could be abandoned.

BTW, as a newbie, use the right tone when asking questions.

People are not so forgiving to demanding newbies (or to demanding whoever, really)
[Galaxy Tab  Android Development] nemory:
Anyone knows how to fix my problem? I can't do anything with it, I can only dial. please?
[Galaxy Tab  Android Development] priyana:
put your SIM in another phone to make sure you can make call.

We have one guy who has expired SIM card and didn't realise it.
[Galaxy Tab  Android Development] nemory:
I have tried using different sims, still the problem is there. even I make it airplane mode or not. I still have a signal and the text messages come in. I hope this can be fixed without restocking or wiping data???
[Galaxy Tab  Android Development] hinirang:
what baseband are you on?
[Galaxy Tab  Android Development] nemory:
you mean modem? JPZ modem. I am in Asia. I really don't have any idea how did this happen. the tab was perfect for 5 days using Build #35, then suddenly when I woke up, I can only see the emergency calls,
[Galaxy Tab  Android Development] droiduzr2:
get a new sim card.

My phone did the same thing.
[Galaxy Tab  Android Development] nemory:
I tried a lot of sim cards already. did that happen when you're in Build #35? or ICS?

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

I even had no simcards for 1 year already. with different ROMS, I never got this emergency call problem before. Even I put a simcard, and has a signal, even 3g signal. still emergency call. now I am backing up my data using adb. and I'll try to factory reset. Hope it works.
[Galaxy Tab  Android Development] priyana:
you posted both in AOKP and CM9 thread of the same issue.

The same issue in both ROM? and with many SIM cards, I think it must be hardware.

Unless you can restock to JQ1 and show differently.
[Galaxy Tab  Android Development] xfaceman:
hey ...again .....is the battery drain faster..in .build 37
[Galaxy Tab  Android Development] legedug:
Downloaded and installed from overcome 4.1 series using wipe because I want a fresh install.

Running well on the booting but I should put the from in internal memory (can not locate on external memory). Loop booting occurred and should flash twice on CRM and now still testing apps; default camera working but made gadget locked in orientation (working again after rebooting).

Thanks to the team.

Legedug
[Galaxy Tab  Android Development] ejgutierrez:
Thanks for your answer... I dont understand what you said about the tone of the questions, i think ive been polite and respectous, but as you may noticed my english is not good and im translating from spanish. Sorry if something has disturbed you.
[Galaxy Tab  Android Development] stimpz0r:
hahahaha yes unicorn porn is good for a couple of minutes, or for a females tablet, but i personally cant stand all the pink. :p

in other news, i've found a problem with the rom package / cwm flashable kernel zips. i will be rebuilding them and reuploading. if anyone is in the process of having bootloop problems, hold off until i reupload the packages.
[Galaxy Tab  Android Development] Che Guevara:
Hello dear, i really appreciate your great work, honestly .. this rom is the best ever i have test ..Thank you so much.

Ihave 2 question please:

1 - The LCD Density menu is not appearing not form general ui nor from performance, any advice?

2 - How to get into the external SD Card from the PC? I can access the SD Card only from the root explorer program.

Thank you again & keep up the great work.
[Galaxy Tab  Android Development] espionage724:
Not entirely sure what you mean, but:

If LCD Density changing apps aren't working, you'll have to manually add the entry to build.prop (it doesn't exist by default)

If the Compatibility button isn't appearing, you may want to see if the Compatibility Mode option is ticked in SpareSparts(+)

Also, I seem to be getting EGL-related issues when I try to start some app I'm beta testing. I can't recall if such an issue existed on CM9 with this app or not.

03-12 02:23:49.308: D/libEGL(1678): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
03-12 02:23:49.312: D/libEGL(1678): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
03-12 02:23:49.421: E/SurfaceTexture(109): [SurfaceView] connect: already connected (cur=2, req=1)
03-12 02:23:49.421: E/libEGL(1678): EGLNativeWindowType 0x2ec7e8 already connected to another API
03-12 02:23:49.421: E/libEGL(1678): eglCreateWindowSurface:362 error 300b (EGL_BAD_NATIVE_WINDOW)
03-12 02:23:49.425: E/libEGL(1678): eglMakeCurrent:678 error 3009 (EGL_BAD_MATCH)
03-12 02:23:49.433: E/libEGL(1678): eglMakeCurrent:678 error 3009 (EGL_BAD_MATCH)

Was anything changed with EGL at all?
[Galaxy Tab  Android Development] Che Guevara:
Nothing at all! i can't find spare parts, i cant find anything to change the dpi!

Thank you :)
[Galaxy Tab  Android Development] espionage724:
I just changed the screen DPI on my tab to 240, but I manually added the setting (I think ro.sf.lcd_density=240) to the build.prop via Rom Toolkit
[Galaxy Tab  Android Development] stimpz0r:
i have no idea... unless they have changed something on CM9, then i doubt it... i personally haven't removed or changed anything with EGL.

ok, it seems that the LCD density switcher built in to AOKP only shows up if the below line (or a line with any lcd density) is in the build.prop. anyway, to change the LCD density use a root enabled file explorer or adb and add the build.prop line:

ro.sf.lcd_density=160

or whatever you wish the density to be. mind you, changing this will result in some apps not being available on play/market unless you wipe play/market's data ( settings -> apps -> "all" tab -> google play store -> clear data ). it is also advised to set it to either 240, 160, or 120 (i personally prefer 120dpi as it gives you a "full" tablet experience with many apps). once its been entered into the build.prop, and you have given ROMControl superuser privileges (best way to do this i find is to increase the max cpu threshold to 1200mhz in the performance menu, and a few seconds later it will ask you to allow it to use root privileges) .

if you want to install swype, you need to set the LCD density to 240 to install it, then you can change it after you have installed.
[Galaxy Tab  Android Development] stimpz0r:
ok everyone, milestone #4 and new flashable kernels have been re-uploaded with the updated "updater-script" that should now flash the kernel properly, and hopefully resolve the bootloop issue. if anyone could please test this and get back to me with an update on how its going, i would be most appreciative. sorry people for this, it completely slipped past me. :(
[Galaxy Tab  Android Development] Che Guevara:
Alright will do that later on .. just still wondering How to get into the external SD Card from the PC? I can access the SD Card only from the root explorer app

Also voodoo sound control is not compatible with Humberos CM9 kernel, any suggestion?

Thank you.
[Galaxy Tab  Android Development] espionage724:
If I heard right, a filename was changed recently with CM9, and I guess that filename changemakes Voodoo Control not detect Voodoo Modules? Something like that maybe...

In any case, you can use DSP Manager from either CM9, or here (from slim_build_02202112.zip)

As for the SD card, I have no idea :/
[Galaxy Tab  Android Development] hot_dew:
Got bootloop.

Flashed with HemberOS kernal. then it booted finally. and works fine.

Angel camera works fine.

THANKS !!!

only problem im facing , my tab is getting hot if i use it like 10 mins.

anyone have any comments ?
[Galaxy Tab  Android Development] Che Guevara:
Thank you :)

Will give it a try.
[Galaxy Tab  Android Development] espionage724:
If you have a live wallpaper, disable it.

I also disabled (froze) a bunch of apps that I didn't need running, and my tab doesn't run too hot anymore.

Another option is to undervolt, but this requires time and patience :)
[Galaxy Tab  Android Development] Che Guevara:
Any one is facing a very low sound? (comparing to other roms)
[Galaxy Tab  Android Development] espionage724:
Nothing sounds strange on my end. The notification sound seems different then CM9's default, that's about it
[Galaxy Tab  Android Development] Che Guevara:
I never tried CM9, I tried Boca, Overcome .. etc. The sound or volume was higher in general.
[Galaxy Tab  Android Development] espionage724:
Hmm, well the default Notification sound in CM9 and icedBoca i think was "Pixie Dust" but AOKP's is "Proxima". I don't know if normal Boca uses the same or not.

I can't recall what the default is on Gingerbread-based ROM's though
[Galaxy Tab  Android Development] cja1972:
MTP

I cant find how to enable mtp in the settings . Can anyone help. I want to transfer my samsung movies back on..
[Galaxy Tab  Android Development] stimpz0r:
you are absolutely right. it seems that the TE4M have changed the sound codec to fix up DSP manager incompatibilities, therefore breaking voodoo sound control from working. i swear i saw this reversed somewhere, but it mustve been on another project.

i have attached a copy of DSPmanager (CwM flashable), copy it on to your SD card, and flash it in recovery, then when you reboot it should be in your app drawer.
[Galaxy Tab  Android Development] stimpz0r:
as in my above post, they actually changed the code in a codec, so its not as easy as changing a filename. also, DSPManager.apk alone isn't enough for DSPManager. use the above zip as it includes the lib / config file as well.

when did you download the release? before or after i fixed up the zip files?

mtp settings may have been added by the TE4M in their build, if that is the case then it wont show up on this release. i will look further into it and try to add it to the next build.

AOKP uses different default sounds to ICS/CM9, which is why it is different. Gingerbread roms probably don't have the sounds it uses (as i believe they are ICS sounds).
[Galaxy Tab  Android Development] cja1972:
Cheers .Thanks for the excellent work on this.
[Galaxy Tab  Android Development] schmoo:
Soft Button Suggestion

Since the default soft button setup is being tweaked, may I suggest the following default (have the soft buttons match the four physical buttons):
[Galaxy Tab  Android Development] yosup:
stimpz0r made changes to the MTD partition table at Milestone #5, and he instructed to restock. Since you are using the first MTD build #34 (prior to MS#5), you may consider restocking. However, I believe others have done it without restocking. Personally, I restocked when I upgraded from B#34. Your call. Cheers. :p

From stimpz0r's OP:
[Galaxy Tab  Android Development] linux150:
Bug Report

Hi !

I´m on B37 after restocking:

When i go to

Rom Control- General UI - Point 5. Change densitiy to what i want

and then i try to change to a custom density i get a FC on GERMAN LANGUAGE !!

When i switch to english all work fine !

lg

linux150