yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] Blittz:
Thanks for this siompz0r, it did fix my navbar problem, however I have a problem I haven't seen mentioned yet. I did a full Overcome re-stock as per the instructions, and it all went exactly as mentioned in the OP. I'm now running on a fresh aokp_p1_build-34 rom. My Baseband version says P1000XXJPZ, and I'm a T-Mobile subscriber, but here is my problem.

With wifi on and connected, my mobile strength indicator shows normal signal, but when I loose wi-fi signal (either go out of range, or shut off wifi in settings) my mobile radio shows an E for Edge. I confirm that my data rate is horribly slow in this mode.

I hope this isn't just me doing something stupid, and thanks in advance for any help!
[Galaxy Tab  Android Development] gwbard:
If you are intending to use the tab as a telephone -- that's just the way it is...

The included JPZ modem will enable the phone, but you only get Edge data with TMobile

To get 3G data with TMobile you need to flash the original TMO modem (JJB)

You can get the TMO-Modem.zip >>here<<
[Galaxy Tab  Android Development] superseagulls:
I wondered why my downloads were so slow this morning, I didn't notice there was no 'H' logo after the flash to 34....

OK, add to the bug list, the baseband, even after flashing remains with the JPZ firmware. I don't need the phone, and never had any problems before, can you do a download with the TMO radio baked straight in? What ever I try the Baseband version in settings remains as P1000XXJPZ

Thanks!
[Galaxy Tab  Android Development] Blittz:
I downloaded the file you suggested, and tried installing it but it still said JPZ modem. Then I tried manually replacing the /radio/modem.bin file with the new one and there wasn't enough room. The JPZ is 12MB and the new one is 16MB. Suggestions?
[Galaxy Tab  Android Development] superseagulls:
Same here, in case you missed my last post.

I think we may need a specific rom with the TMO radio baked in.....
[Galaxy Tab  Android Development] gwbard:
aye, there's the rub...

stimpz0r addressed this a few posts ago:

looks like we'll hafta wait for the next build to enable TMO modem
[Galaxy Tab  Android Development] Blittz:
I saw that, but had hoped I could use the modem anyway :) oh well. So here it is:

USA T-Mobile users, do NOT USE build 34 unless you are ok with 2g data rates.
[Galaxy Tab  Android Development] agustincordoba:
Hi, any comments on the functioning of the camera in build 34, normal and fine modes?

Thanks

Greetings from Spain

Enviado desde mi GT-P1000 usando Tapatalk 2
[Galaxy Tab  Android Development] superseagulls:
Works fine here, Flash and everything......!
[Galaxy Tab  Android Development] salahmed:
First, thank you StimpzOr for you great work.

Here is what I did to install from #31 to 34# mtd without restock.

1- download overcome kernel v4.0.0 .zip

2- reboot in to recovery

3- install overcome kernel v4.0.0 .zip

4- reboot recovery so you will enter in overcome cwm recovery

5- wipe data / factory set .... wipe dalvic cash

6- install #34 mtd and off course hold the volume up key to enter recovery to complete the installation.

7- wipe data / factory set .... wipe dalvic cash again

8- reboot system

9- let it boot completely wait for a couple of minutes, then reboot recovery

10- install gapps, I do these last two steps because for some reason the gapps installation do not stick when I install it together with the rom

Now everything running smooth without bugs

1- gapps OK

2- camera OK

3- wifi (for me I have to install wifix manager because I live in middle east)

4- thanks again stimpzOr will update if I notice anything

Oh I just notice when I want to select text and the two marks appear, I can only move the left mark if I move the right mark it will jump to select one letter, but it is OK. This happened only once in the browser.
[Galaxy Tab  Android Development] yunlin12:
I backed up Overcome 4.1.0 when I flashed Build 31, so I just restored it, figured it should be as good as restocking and reflashing Overcome.

Then booted into CWM recovery, wiped data and dalvik cache, flashed build 34, reboot into ICS, then reboot into CWM recovery to flahs gapps, then reboot and everything works fine.
[Galaxy Tab  Android Development] smali26:
ok. Noob question of the day. i know this has been asked before and links were provided for the explanation.

can someone please clarify the what are the benefits of going to a MTD rom vs a no MTD rom.

I am an idiot so please dumb it down for me and be kind

thanks

cheers!!!

update:

this is by far the best explanation of MTD that idiots like me can understand. thanks Cheatman.

http://xdaforums.com/showthread.php?t=1619423
[Galaxy Tab  Android Development] priyana:
Read post #1 again

[ :: INSTALLATION :: ]

*** FOR INSTALLATION OF BUILD #34 AND ABOVE (MTD) ***

first but foremost, if you are new to MTD, or just need to brush up on the information, then read --> THIS <LINK REMOVED>
[Galaxy Tab  Android Development] brunobbarcelos:
I restocked and installed AOKP 34, the tablet worked as expected but... i´m in Brazil, my P-1000 is an ex-T-mobile and now it just don´t conect to VIVO, 2g or 3g or any g. Suggestions? :-(
[Galaxy Tab  Android Development] mattman83:
If you restocked with the overcome process, what radio did you pick? Prob just need to flash correct radio via odin.

M.
[Galaxy Tab  Android Development] brunobbarcelos:
The old T-mobile radio works with ICS AOKP?
[Galaxy Tab  Android Development] priyana:
It was noted one page before this, that the stock T-Mobile JJB modem is too large for this build.

Wait till the next build gives higher slice for /radio partition.

And no need flashing, just copy the modem.bin there.
[Galaxy Tab  Android Development] agustincordoba:
I did something like this, machine boots up fine, really smooth.

Incidency, I got an error 403 message when I tried to download from Play Store, I really need to have this working as phone in the morning so I am restoring all apps and user data from TB.

BTW it would be handy if any basic file browser could be included with the rom, I had to access a safe copy on PC, mail it to myself then click on install on the tab, very roundabout way..

I did try the camera before anything else and the application closed again... I have no way to find out why? Is there some kind of debug I could run? Can I fire up app from a command line and see output?

Apart from that wifi works fine, other things, we shall see tomorrow.

Thanks for a great rom
[Galaxy Tab  Android Development] qm4n76:
Edit: sorry missleading answer

you can add any file manager apk like OI File manager, by put it to ROM file, open ROM file with winrar or any archive software if you using windows pc, then add apk file to System/app, now when you flashing the ROM file manager will be included..,
[Galaxy Tab  Android Development] droiduzr2:
What is the difference if you add it to system/app vs. data/app?
[Galaxy Tab  Android Development] qm4n76:
ROM file have no data/app folder, there is only system/app folder

some app will not working correctly if you add to data/app, it's bcoz limitation of android framework. infact, File manager like OIFilemanager do not need to add to system/app, you can add it to data/app using cwm zip package like this one from cheatman, if you want. chek it here: http://xdaforums.com/showthread.php?t=1572962
[Galaxy Tab  Android Development] agustincordoba:
Thank you, that will do the job just fine on my next wipe/install

Enviado desde P1000 con Tapatalk

Sent from P1000 via Tapatalk
[Galaxy Tab  Android Development] espionage724:
On CM9, I believe they are using some newer Wifi driver (they started using it somewhat recently), but in any case, is AOKP also using that newer Wifi driver?

There seems to be some power saving thing enable, that when the screen goes off, Wifi speeds significantly slow down. This is bad for USB Tethering.
[Galaxy Tab  Android Development] yosup:
@stimpz0r

I finally got around to set aside some time to backup & restock before jumping into #34 MTD. I've been meaning to restock for a while (just to wipe everything clean), so this was the perfect excuse.

This things flies, man. I like the additional color settings AOKP threw into ROM Control. A few bugs to work out overall, but at this rate it probably won't be long until roman anounces yet another build (lol). The rumor of 4.0.5 dropping for the Gnex has been on-going, but allegedly it's this month or the next. I'm sure AOKP will be ready hat-in-hand to catch that tide ... unless they're working on Milestone #5 already. Hehe. :)

Rest up, dude. Grab a Fosters and throw some shrimp on the barbie. Cheers. :D:D
[Galaxy Tab  Android Development] shadow_empire1:
Installation aborted

I tried to flash over #31:

Wipe factory/cache

flash aokp_p1_build-34.zip

-->

checking state of BML/MTD...

assert failed: run_program ("c:\temp\updater.sh") == 0

E:Error in /sdcard/download/aokp_p1_build-34.zip

(Status 7)

Installation aborted.

any idea?
[Galaxy Tab  Android Development] ipit:
Did you follow the instructions? It doesn't sound like you did.

"IF YOU ARE ON A PREVIOUS BUILD OF AOKP, OR ON A NON-MTD BASED ROM YOU MUST DO THE FOLLOWING:

you need to restock and install Overcome before attempting to install the MTD based rom."
[Galaxy Tab  Android Development] shadow_empire1:
Only difference was wiping data...

(I read in the forum, that for other users it worked without restocking)

->

*** FOR INSTALLATION OF BUILD #33 AND BELOW (NON-MTD) ***

FROM A PREVIOUS ICS BUILD / EXT4 COMPATIBLE ROM ::

(the menus in CWM recovery may be different to the ones listed below)

copy the rom onto your SD card or internal memory

reboot in to ClockworkMod Recovery

go to install -> choose from either internal / external sd card -> navigate and select the zip file

do the same as above for gapps (google apps)

go to wipe menu

select both "wipe data / factory reset" and "wipe dalvik cache"

reboot

---------- Post added at 08:20 AM ---------- Previous post was at 08:14 AM ----------

I will try restocking as required.
[Galaxy Tab  Android Development] yosup:
The Status 7 assert error has already been explained by stimpz0r and HumberOS.

You're flashing from a non-MTD (#31) directly to an MTD (#34) build. There are some (like salahmed) who've been able to make the jump just by flashing the Overcome kernel, but a lot of people will end up with the same Status 7 error you're getting anyways.

Check out the OP, dude. Lots of answers to life's questions ... as well as links & instructions for flashing this new build. MTD partitioning is a major change, so why not give yourself a clean slate to work with and restock? Just make sure to backup your sd card since once you load the pit file, the "repartition" checkbox will be live in Odin - ie. it completely wipes your sd card. Good luck! :)

You're flashing #34 ... so the instructions you just referenced don't apply.
[Galaxy Tab  Android Development] mmjp:
Hi all,

I have a bit straight problem,

After update-cm-9-20120425-NIGHTLY-p1-signed.zip,

I flash #34, then device totally not aware once I add sim card.

All others are working, wifi also no problem.

I worried that I brick 3g feature.:-)
[Galaxy Tab  Android Development] mattman83:
Flash went fine in general, followed overcome restock process. 2 strange things basically.

- when I reboot, it goes to recovery (hooks not correct?)

- when using apps the navi buttons go super small. Can't see any options in rom control. Bug or am I just not seeing spo,me thing obvious?

Cheers
[Galaxy Tab  Android Development] khrislee:
i also got this wield problem:D
[Galaxy Tab  Android Development] ipit:
going to recovery has something to do with the default reboot option not registering. Someone helped me out earlier with it. When you click reboot, just click on 'recovery' and back to 'reboot' and it works.
[Galaxy Tab  Android Development] Rocheau:
Status 7 o error 7 coming from 33 or 31 is an issue related to the kernel. Just flash overcome kernel 4.0. The process will interrupt in the middle, and Tabi would reboot itself , hold the volume up button and you will enter in recovery again, the process will go on until the end. Then reboot again and you will be able to install the 34 mtd version.
[Galaxy Tab  Android Development] agustincordoba:
My workaround is to turn Tab off rather than selecting reboot. Then I simply start it anew.

In ROM Control I enabled the fourth button and assigned it to "menu" - my buttons are now ok.

BTW, my stock camera is not working, does anyone else have this problem m

Enviado desde P1000 con Tapatalk

Sent from P1000 via Tapatalk
[Galaxy Tab  Android Development] Fenvarien:
Many thanks to the dev for build 34, it works really great! Fast, smooth and stable :-)

Installation was easy, coming from b32 - I used the 'alternative way' via flashing overcome kernel... Thanks to Salahmed for his guide. http://xdaforums.com/showthread.php?p=25351759

... tapatalked
[Galaxy Tab  Android Development] Izachii:
Nope, My stock camera is working. But the problem with mine is that when i change the size of my icon down below the widget is not responding. Try to work around with it.
[Galaxy Tab  Android Development] agustincordoba:
Mine closes the instant I shoot the pic.I don't know why or how to debug this. I imagine there must be a way of running the app while logging what goes wrong, but this is beyond my powers.

Enviado desde P1000 con Tapatalk

Sent from P1000 via Tapatalk
[Galaxy Tab  Android Development] dave52355:
I'm still on #33. My BT was working great for 2 days but now even tho it say's on and paired the BT symbol stays greyed out. Also even tho it is paired there is no use of the paired device.

Does #34 resolve this? Or is this a known issue?

Thanks

EDIT: Never mind, the BT speakers work much better if turned on! :D
[Galaxy Tab  Android Development] Monfro:
The new MTD kernel included in CM official and alroger 's from 25 april had a bug now solved.

Go to cm9 official thread and read latest posts.

Solution to the problem:

Flash JPZ modem from cdesai 's post in that thread. It is one of the latest post.

Then flash official 27april nightly.

Put sim card in the tablet and data is working perfectly.

So the problem is solved.

Now you have new mtd partition. Wait for next aokp release, since build 34 has old mtd layout. For sure next build will have the new kernel.
[Galaxy Tab  Android Development] D-fens:
Is there any option to add extra language dictionary to the keyboard? In my case it is about polish language.
[Galaxy Tab  Android Development] yosup:
Bump ... this workaround works well for me. Thanks. :D:thumbup:
[Galaxy Tab  Android Development] priyana:
You mean flash to cm9 to solve the problem?
[Galaxy Tab  Android Development] smali26:
ok. i took the leap and flashed MTD build #34.

all is working but battery is draining extremely fast. looks like i have 13% before it completely dies!!!! RIP Tab..
[Galaxy Tab  Android Development] priyana:
I have drained off 35% (65% left) in half a day light use.

On build #31 I got 2 days of usage. Will try to calibrate batt.
[Galaxy Tab  Android Development] waazaii:
great rom, thank to all dev.

one problem, change to 240dpi camera force to close. can any one help
[Galaxy Tab  Android Development] racerboy3801:
I just want to report mate that the installation was flawless and the tabs running like a beaut. Thanks a lot.
[Galaxy Tab  Android Development] smali26:
GREAT THANKS TO THE DEVS!!!!

On build #34 MTD rom what kernel is the best or recommended?
[Galaxy Tab  Android Development] lemyzone:
Please help...

What´s the diference between MTD RELEASES and NON-MTD RELEASES ??
[Galaxy Tab  Android Development] hariharan321:
Hey lemyzone, not the place to ask the basics.... Read this http://xdaforums.com/showthread.php?p=25310435
[Galaxy Tab  Android Development] laxanoulis1:
1st of all thanks for you excellent job!

Installed #34. Came from #31.

Things work:

-Wifi

-3G (not tested but it looks working)

-Calls

-Camera with Flash and all the settings

-Gyro

-Maps

-Browser with flash player

-Play Store

-Root Explorer (for file manager)

-Youtube & HD

-Bluetooth mouse pairing (file transfer i didn't try)

The only thing that it is a bug is the navigation buttons on the navigation bar which they be very small on some apps.(pictures with an example)

And now, i have a question. If i do an overclock to 1200, i have to do something on Voltage or i just put it on 1200 and i'm ok?!
[Galaxy Tab  Android Development] Izachii:
The small navigation icon can be resolve by changing the size in ROM Control. But one small bug is that if u change the size of it , it could not place widget in thine home screen. Whenever u wanna place a widget on the home screen, the screen will just rotate. Just hopefully on the next build the dev will solve the problem. One more thing for me is that whenever I wanna reboot my tab, its goes into recovery mode rather that just boot.
[Galaxy Tab  Android Development] salahmed:
It was mentioned many times, in from control just remove the menu and place a fourth shortcut for the menu.

For rebooting just select recovery then select reboot again then ok.
[Galaxy Tab  Android Development] kosmas58:
I fixed the size problem by adding menu as permant fourth button, which also solved the missing menu button problem on some legacy apps.
[Galaxy Tab  Android Development] yosup:
Wonder if anyone else uses Wi-Fi + Airplane Mode and sees tiny icons like this:

Vs. normal icon sizes for Wi-Fi or Airplane Mode separately:
[Galaxy Tab  Android Development] anderin:
Confirmed! I also have such tiny icons !

Enviado desde mi GT-P1000 usando Tapatalk 2
[Galaxy Tab  Android Development] lemyzone:
Thanks hariharan321!!

Now another question... I've intalled on my tab the Build #33. Can I install the #Build 34 MTD the same way I do to install the Build #33 ??

Please help....
[Galaxy Tab  Android Development] ipit:
No, read the instructions on the first page
[Galaxy Tab  Android Development] stimpz0r:
interesting! airplane mode by design is supposed to disable wifi, hence the wifi signal icon is supposed to disappear. (airplane mode for the uneducated is supposed to disable all radios). i will have a look into that and see why it is doing it.

in other news, i've updated the first post with some youtube videos courtesy of laxanoulis1 (sorry it took so long!) and updated the bugs list... though it looks like i now have another to add. :p
[Galaxy Tab  Android Development] mattman83:
When you enable airplane mode it does kill all radios. However you can re-enable wifi/bt as needed after that without leaving airplane. Afaik this is by design as overcome had the same behaviour.

Handy for me since I don't have a sim in mine.

M.
[Galaxy Tab  Android Development] yosup:
Yeah, I've been primarily using it this way (Wi-Fi + Airplane) ever since I first took it out of the box. As mattman83 mentioned, I typically leave it in Airplane Mode (esp. to prevent data leakage during bootup), then toggle Wi-Fi when I need it. A bit paranoid, yeah ... lol. Of all your AOKP builds I've used, this was the first time I got the tiny icons. If anything, it's quite distinctive! :D

Videos and bugs lists are great! Only question remains: How many people will actually watch / read them? Lol. Been like a zoo in here ever since the MTD transition and the same questions reappearing every few pages. Well, guess that means you've got more users jumping on the band wagon! ;)

Can't wait to see how these builds evolve now with MTD in place. Thanks again, stimpz0r! Cheers.
[Galaxy Tab  Android Development] Monfro:
Yes, because the problem is that he flashed cm9 from 25 april, which was the first one with the new mtd layout, but it had a bug concerning modem.bin

Since now he has new mtd layout( 24mb radio partition, bigger system and cache partition, no datadata partition) is better he stays on this new mtd partition.

Cm9 from 27 april has the problem fixed. To fully fix he needs also to flash a modem from cdesai 's post.

After that every mtd rom will have this kind of partition, i am sure also aokp will have in next release, so he can flash what he wants
[Galaxy Tab  Android Development] agustincordoba:
My list:

-3G tested ok

-Wifi works fine

-Calls and SMS send/receive fine

-Stock camera closes on me after shooting pic, image not stored

-Maps ok

-All file browsers and internet browsers I tested run fine

-Play Store ok

-Bluetooth headset fine

Enviado desde P1000 con Tapatalk

Sent from P1000 via Tapatalk
[Galaxy Tab  Android Development] stimpz0r:
i didnt actually know that, as far as i knew airplane mode was inveted for exactly that kind of situation, airplanes (that you aren't allowed to have any radio equipment running on), so i always assumed that as soon as airplane mode was enabled, it would stop all radios, even if you enabled another one. this is actually a rather handy feature. :)

i believe it may be tied in with the legacy menu programs and tiny navbar buttons as well... i also found another bug earlier today where i switched to landscape mode, and all the navbar buttons were in the middle of the statusbar... ill personally take a look into it, but i wouldn't be suprised if the guys at TeamKang beat me to a fix. ;)

i agree with the comment on the updated initial posts, but at least now they are there, so instead of having to reply, i, or others, can simply say "RTFFP" (read the f***in first post(s)!) :p, its expected i suppose, new users aren't necessarily used to all the rules of a forum, but i thank you and everyone else for lending a helping hand in helping our fellow new users. :)

anyway, off to look into some bugs, and port P1Parts over to ROMControl. ;)
[Galaxy Tab  Android Development] smali26:
battery problem.... i am losing charge as its plugged in. if i turn it off then it charges to 100%. when i turn it on it starts at 99% and drains the battery as its plugged in.

i have also wiped the battery, the voltage and its running overcome 4.0 kernel.

i think it may be the kernel since i did not have any issues with aokp before.

everything else works.
[Galaxy Tab  Android Development] laxanoulis1:
Thanks a lot, it worked for me! :))