yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] livlogik:
I tried to put in my sim card from my phone to test the phone call feature on the tab. Its a tmobile sim.

For some reason it won't work it goes straight to call ended

If I missed something and this was already brought up I'm sorry.

Thanks
[Galaxy Tab  Android Development] kacperek70:
Thx.. It's works
[Galaxy Tab  Android Development] pdppdp:
Is there a way to make the buttons bigger or make the distance between them bigger?
[Galaxy Tab  Android Development] kosmas58:
My experience is, that the phone works, if my BT headset is attached.

If haven't verified, if it's still working in Build #33, because I'm using a data only sim at the moment, but in the previous builds it did. :)
[Galaxy Tab  Android Development] Axelman8:
#34

:eek: OMG Look at this: http://forum.aokp.co/page/releases/_/build-34-r19

Maby it is time for me, if Build #34 gets out here... to change to ICS afterall XD

Waiting patiently...

Regards,

Axelman
[Galaxy Tab  Android Development] lianopbs:
not fixed for me, I still have to press on the speaker button on each call
[Galaxy Tab  Android Development] kosmas58:
Phone definitely works in Build#33, as I've verified now. :thumbup:

One issue remains (as lianopbs wrote): Speakers are off although shown as on. You have to press the speaker button twice to hear the caller. :thumbdown:
[Galaxy Tab  Android Development] livlogik:
Hmmmm i wonder why mine doesn't work... I would dial the number and press call and right away it says call ended.. Also for data if i go on the internet it directs me straight to the Tmobile site and says to please login.
[Galaxy Tab  Android Development] khrislee:
just flash #33

after install around 20+ app quite lag n started force-closing....
[Galaxy Tab  Android Development] stimpz0r:
BUILD #34 - has hit the shelves *** MTD ***

yes people, you have read right. this build (#34) is now MTD.

with it comes not too many changes on the SGT7 front (besides that big one) and some very large warnings:

IF YOU PLAN TO USE THIS ROM THEN READ THE FIRST AND SECOND POST ALL THE WAY TO THE VERY LAST FULL STOP. FOLLOW ALL INSTALLATION INSTRUCTIONS TO THE LETTER!!!

please give me feedback on how it goes, remember, you are my testers but PLEASE TRY TO BE AS DESCRIPTIVE AS YOU CAN! a post saying "thanks for the rom, but calls dont work" or "my camera isnt working" are useless in regards to fixing problems. read the first post and find where i ask for feedback, and follow that instruction too! if it keeps failing then i might ask a few knowledgeble followers to test releases before i give them to the public, and that means delays for all of you.

anyway, another early start for me. enjoy! :)
[Galaxy Tab  Android Development] rock2702:
If I m on a cm9 mtd rom what steps do I follow for flashing this rom?
[Galaxy Tab  Android Development] alroger:
Really? Didn't even read the first post?
[Galaxy Tab  Android Development] stimpz0r:
good question!

i will update the first post with instructions. :)

done! (i hid it to make people read) ;)

EDIT: 1000th POST!!!!! (sorry, never thought it would get this far, had to celebrate!) :D
[Galaxy Tab  Android Development] rock2702:
I read it dude:D Being a newbie I can't afford not to follow every word.

@stimpzor Thanks.
[Galaxy Tab  Android Development] idkidk:
Hi stimpz0r,

you say in 1st post:

I'm little confuse: if i restock an install Overcome i'm over ext4 rigth? So i cannot install MTD #34 build.... :confused: Or i must stop the restocking after install the 001001-GB-Stock-Safe-v5.zip to put the tab into RFS for flashing MTD #34 build? :confused:

TIA

Idk
[Galaxy Tab  Android Development] alroger:
Instructions are very clear.

There are 3 sets of instructions... FROM MTD ROM, FROM non-MTD ROM, and FROM STOCK.

Overcome is needed if you are coming from stock. The first 2 procedures mention nothing about Overcome.
[Galaxy Tab  Android Development] amir_numb:
I have serious problem & i don`t know why ..

I`m on bulid #33 but my wifi doesn`t work at all..

I have same problem with prev builds (29,30)
[Galaxy Tab  Android Development] idkidk:
Hi Alroger,

sure, the instruction is really clear, the question is for me not for the instructions in 1st post :p... i need to understand the macro step, not the instructions itself...

so:

RFS/stock -> overcome -> MTD build

EXT4 - MTD -> MTD build

rigth? thats all...

TIA!

Idk
[Galaxy Tab  Android Development] humberos:
Yeah!

The Overcome is needed on p1l and p1n too because the Machine name too. The new ramdisk works with this name.

If p1l and p1n users restock to the native version then them will get the Machine name like this GT-P1000L or GT-P1000N. This way won't work yet. We need to get "GT-P1000" from Overcome.

New ramdisk works with the name "GT-P1000" and Ext4 (both from Overcome).

#Edit: Restock using ODIN with repartition enabled (P1_hidden_add.pit is needed).

Greetings from Brazil!
[Galaxy Tab  Android Development] salvoplatania:
Installing build 34

The guide should be followed up to step # 9? and then followed

copy the rom onto your SD card or internal memory

reboot in to ClockworkMod Recovery

go to wipe menu

select both "wipe data / factory reset" and "wipe dalvik cache" ** MAKE SURE YOU DO THIS BEFORE INSTALLING THE ROM **

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

after a few seconds, the tablet will reboot and go into a bootloop (you will see a CWM recovery screen flash up). hold down the vol up key and it should go back to recovery.

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

do the same as above for gapps (google apps)

reboot

I have a bulid 33 no MDT:confused:
[Galaxy Tab  Android Development] harvey186:
Can me pleased someone tell where the benefit is between MTD and Non-MTD ?

Is there a MUST have to MTD ?

How do I know if I'm on a MTD based ROM or not ? Where can I look ?

Sorry for dumb questions, but I have read a lot of posts here, but reading 1000 post is to much :(
[Galaxy Tab  Android Development] superseagulls:
Do you ever sleep........?

Now go get a cold one, and go put your feet up!!!!!

Seriously though, thanks for all your work!
[Galaxy Tab  Android Development] ayysir:
So does this include cdesai's new partition change that even mtd users have to restock
[Galaxy Tab  Android Development] Axelman8:
Question: Just to be sure

:D Build 34, ok, im switching to ICS :)

But this MTD isnt to heard to understand isn't it? :confused:....

If i am allready on overcome rom / kernel, iIam ready to go right?

Better to be safe..... and ask... didnt get it out of all the answers (sry)

Bricks are for Chuck Norris to crack with his head! My head will crack if i get a brick!

Thnx in advance

Axelman
[Galaxy Tab  Android Development] D-fens:
Hi folks. Before I'll try #34 installed #33 on recently used #31. The problem is that I don't have navigation bar at all. Tried to change high and saw it appears for a while. Notifications works normally.

Screenshot added. View attachment 1024457
[Galaxy Tab  Android Development] D-fens:
Screenshot again
[Galaxy Tab  Android Development] alroger:
AOKP #34 on P1000N

Just tried AOKP for the 1st time. Very nice details.

I just replaced AOKP #34 boot.img kernel in the ZIP with my CM9 20120424 build's kernel for the P1000N and just flashed it... all good (I was already on MTD).

Someone asked about the partition sizes, and NOPE, #34 still has the same old partition sizes (radio = 16MB, but only 13.5MB free).

Nice work.

Cheers!
[Galaxy Tab  Android Development] ayysir:
Not sure if the op uses same bml to mtd script as cm9 builds bout you have to mount efs then flash the zip
[Galaxy Tab  Android Development] Axelman8:
thank you Ayysir for the respond.

Extent file system: check! and then...... ok, call me a noob or whatever, but I don't understand any of this......

my question:

Overcome ROM is not an MTD based partitioned ROM ... or is it?

Why should I have to start all over again when I'm on Overcome Rom/Kernel. doesnt make sense to me...

Anyway, when I ever get this ROM running, I will be glad to be of testing service....

regards,

Axelman
[Galaxy Tab  Android Development] hariharan321:
Er.. Guess im gonna ask some similar question here.. I do not need any explanations as i don think i have the space in my head to understand MTD and non MTD. I love your ICS .. i just follow what you ask me to do.. and poof.. there it pops with amazing ROM on my tab.. Well, now im on Build #33 (and i just worship stumpz0r for that!) If the developers have come up with MTD it must be good. Somebody just confirm me that i need to follow the below instructions to get to MTD #34 from Build #33. That is all i need to know and ill follow as it is. ;)

Please....

'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
[Galaxy Tab  Android Development] Axelman8:
:D Now thats good enough answer for me! Thnx (just hit the button for you m8)

Also waiting for the conformation now.... :P

Regards,

Axelman
[Galaxy Tab  Android Development] stimpz0r:
The script that is used in cm9 (bml over mtd) is the very same used in the one off cm repo's as of yesterday. (if that helps anyone).

To those asking what instructions to follow, I made it very clear in the first post which ones are to be followed with big bold headings. I suggest if you haven't worked it out to read over it again, (and again, and again, and again...) until it make sense. This will ensure you have a good understanding.

I'm sorry I don't have the time to explain all the other things about MTD but I gotta jet... for explination on MTD though look at first post(s) of cm9 thread.
[Galaxy Tab  Android Development] hariharan321:
I can understand that Stimpz0r..

But honestly, i kinda get different meanings every time i read it.. Ill work on that.. will try again and again.. sorry to bother you with silly questions.. Yet, you are just amazing dude.. I love the ROM till #33. :) Stunning work!

---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------

:(:(:(

We will get there m8...Someday...:D
[Galaxy Tab  Android Development] Axelman8:
LOL,

I think i got it:

When you dont have EXT4 partitioning ( overcome installation ) then you allways do the overcome installation:

When you do have an EXT4 partitioning, you can install this MTD rom.

copy the rom onto your SD card or internal memory

reboot in to ClockworkMod Recovery

go to wipe menu

select both "wipe data / factory reset" and "wipe dalvik cache" ** MAKE SURE YOU DO THIS BEFORE INSTALLING THE ROM **

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

after a few seconds, the tablet will reboot and go into a bootloop (you will see a CWM recovery screen flash up). hold down the vol up key and it should go back to recovery.

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

do the same as above for gapps (google apps)

reboot

Doesn't matter what rom u have, you need the EXT4.

I think the #33 isnt EXT4 installed, so you need to do the Overcome installation.

I am backing up Nandroid and am starting the installation.

Good luck to all! (fingers crossed :D)

Regards,

Axelman
[Galaxy Tab  Android Development] Fenvarien:
You want to install build #34? Then follow the according instructions in the OP under *** For build #34...

What you quoted in your post is written under *** For build #33...

... tapatalked
[Galaxy Tab  Android Development] D-fens:
I think you're wrong. If you wanted to install #33 or below you had to install Overcome first just to have ext4 file system. So build #31 and #33 are on ext4 and all you need to do is flash the new MTD #34 via recovery. Simple.
[Galaxy Tab  Android Development] Axelman8:
Overcome EXT4 installation works

Hi,

I came from overcome 4.0 and followed the instructions to the letter, The Rom is working like a charm (sofar its booting :D)

OK: Booted and up and running..

Works

Google PlayStore:

Wifi

3G

WOW!!!! this is awsome!!!! thanx alot :D

Will be reporting tomorrow

Regards,

Axelman
[Galaxy Tab  Android Development] hariharan321:
That's a good news m8.... I shall try that too.... Thanks.
[Galaxy Tab  Android Development] brunobbarcelos:
I´m running HyperDroid Androidmeda v2.1.0, had all Overcomes intalled before. Can i just copy the zip, wipe wipe and wipe and install ICS 34 or i have to restock?
[Galaxy Tab  Android Development] mattman83:
Restock, that's the point of directing you to the guide :)

I'm finding issues with restocking from ICS. I think because our kernel does not really have full USB function it is not working with odin when i boot to download. Workaround for me is install overcome nowipe via CWM, then I will try download mode again (won't have time until tonight though sorry - 12 hours or so).

M.
[Galaxy Tab  Android Development] brunobbarcelos:
mattman83, as i had Overcome on my tablet, restocked months ago.
[Galaxy Tab  Android Development] jeanhaker:
touch me wait for # 34 I have a p1000n
[Galaxy Tab  Android Development] alroger:
AOKP #34 on P1000N

P1000N user, you can grab a CM9 ROM build 20120424 for P1000N, exctract boot.img (the kernel) from it, and replace in the AOKP #34 ZIP file that it will work.

download post

Cheers.
[Galaxy Tab  Android Development] priyana:
Stimpz0r,

Will you build one for MTD with the resized /radio partition just like in CM9?

As alroger noted, certain modems can't fit into the current scheme.
[Galaxy Tab  Android Development] vasiaeva:
is there some special gapps for 34th build? Asking cause i flashed gapps-ics-20120422-signed.zip and its cause bootloops.
[Galaxy Tab  Android Development] jeanhaker:
Thanks will try it :cool:
[Galaxy Tab  Android Development] ayysir:
I think what's getting many people confused is, if this similar to the old cm9 mtd or cdesai new mtd with re partitions which non mtd and mtd users still have to restock to use
[Galaxy Tab  Android Development] drumstix116:
Auto-rotate seems to be messing up the home screen widgets or something. Can no longer tap and hold on a widget after auto rotating screen. If you tap and hold, the screen will change orientation by itself and then go back to orientation depending if you're holding it in portrait mode or landscape. Need to reboot tab to get it working again.

But if auto-rotate is off, i can move and delete widgets with no issues.
[Galaxy Tab  Android Development] mashimus:
Known issue since I started using it. (Build 28)

A semi-fix is to go into Rom Control > General UI .. and enable "Allow 180 rotation" .. then reboot...
[Galaxy Tab  Android Development] ipit:
Coming from 31. Followed all instructions... Restock>OC>Build34>Gapps. All good!

The only thing that I didn't experience was the bootloop described in the installation instructions so I didn't have to hold down the volumeUP etc.

Thanks again!!

edit: I do have a problem though.

1. When I reboot the system it seems to go into recovery mode. I have to reboot from recovery mode again to go back to system.

2. Using ADW Launcher - The Navigation buttons in the home screen have become tiny.
[Galaxy Tab  Android Development] rock2702:
Currently on 34 I m not able to hide the status bar in full screen apps like youtube or games,it always there:(

Any suggestions?
[Galaxy Tab  Android Development] cleonardo:
I were flash from 34 , then ...aported ???
[Galaxy Tab  Android Development] flamand:
I'm a little embarrassed to say this, but after restocking, then installing 34, my tab is possessed. A heavy metal loop starts with the system and I can't get rid of it. What the...?
[Galaxy Tab  Android Development] gildow:
Rational for "Re-Stocking"

Hi,

I'm not sure if this has been asked anywhere...but can someone be kind enough to explain what's the rational/reason for re-stocking to GB?

I think this will be useful to many newbies....

Many thanks...
[Galaxy Tab  Android Development] mashimus:
1. I have the same issue with the rebooting as well.. A work around would be to select "recovery" and then select "reboot" again in the reboot menu.

2. The tiny buttons happens when an app uses the legacy menu button. To fix: Rom Control > Navigation Bar Width > 42dp (Unfortunately, you have to select that option after every reboot)
[Galaxy Tab  Android Development] priyana:
For one, we know that Overcome kernel 4.0 will apply correctly in a properly re-stocked GB.

And we need overcome kernel to get the correct CWM recovery and ext4 filesystem instead of RFS filesystem.

You will find that if you are already on Overcome 4.1 ROM, likely you can ignore the restocking to GB-stock-safe.

I haven't done restocking since way back before Overcome 3.0
[Galaxy Tab  Android Development] kosmas58:
Thanks for MTD Build and your installation hints. I.was able to switch to #Build 34 instantly.

The system is not as stable as it was in the previous builds. I had been using smartassv2 with 1400 MHz without problems in the previous builds.

After several crashes I'm on the default setting ondemand 1000 MHz.

I'm sure you and Humberos will reach the excellent quality of the past again.

Thanks for your work and time you spent for us to keep our SGT7 alive.

Kosmas
[Galaxy Tab  Android Development] Mathias1:
What are the benefits of MTD-partitions?
[Galaxy Tab  Android Development] gildow:
So from what you are saying is that if our from is build 33(which kernel supports ext4 and I had previously converted to ext4), the step of re-stocking can be skipped?

Hate to restock as I fear my internal SD will be wiped clean.

:-)
[Galaxy Tab  Android Development] priyana:
well, your millage may vary,

and OP has disclaimer that he "will not be held responsible for any damage you cause by not doing as you have been told. this is your only warning. any complaints about something going wrong because you haven't followed these to the letter WILL BE IGNORED."

So you have been warned...
[Galaxy Tab  Android Development] drumstix116:
Thanks! That did it.
[Galaxy Tab  Android Development] rock2702:
I m on aokp 34 too.I noticed that the processor values and governor changes always reverts to default after some time without reboot.Din happen previously.Also the 3 nav buttons become tiny and almost invisible in apps like tapatalk,I have set the nav width to 42dp.
[Galaxy Tab  Android Development] Axelman8:
Back to 2.3.3

Hi,

ICS #34 works perfect, but i cant get used to it

I now am converting back to GB 2.3.3 Overcome v4.0

Tested ICS features:

- WIFI

- 3G

- Navigation

- GPS

- DPI 240 switch

- DPI 160 switch

- Both launchers

- Market

- Gmail

All working perfect... So this build is very good. Just not my preference

Regards,

Axelman
[Galaxy Tab  Android Development] pillo78:
radio partition size

hi, thank you for this wonderful release, i need to know the size of radio partition, i want to install km2 modem but i wish to be sure that it fits (16mb).
[Galaxy Tab  Android Development] Rocheau:
Thank you very much for your release. You are a machine, when do you rest?.

I am still with the 33th, non MTD, and I am quite happy, I do thing this t is your best rom ever. Everything is working perfectly. Indeed is a very smooth rom.

Yesterday, I tried to upgrade to 34 th, the MTD version, but could not. Reading the OP it seems that if you came from an Overcorme Rom ( and I would swear the 33th was) you can install the new rom, just as a normal rom, so making the wipes ( in recovery) and install the zip would be enough. However something went wrong or I did not read properly the instruction, but I could not install the 34 th ( the mesage was something similar to error 7).

No problem at all, as I was able to install again the 33th version - the NON MTD-.

Now, I think that I would need to start from stock, in case I would like to have succes, but I am a bit lazy so I would wait a little more.

Reading what others on the MTD have said , it seems that it would be better to wait until some bugs would be fixed.

Thank you for your hard work
[Galaxy Tab  Android Development] mattman83:
Error 7 is some kind of problem with updater script. Try downloading it again.

M.
[Galaxy Tab  Android Development] stimpz0r:
to all those having issues with the navbar and certain apps, if you read the second post, it explains that there is issues with the navbar buttons and legacy apps (apps that need a menu button to operate).

from changelog of build #33:

people who are having problems with overclocking - dont overclock to 1400. just because the option is there, doesn't mean you should use it, 1400 is a maximum amount you can push the tab, and its unstable on most tablets. i recommend 1200mhz and smartassv2, if you overclock to 1400 you are asking for problems.

if you read the first post carefully you will (nearly) all the answers you are looking for. restocking and upgrading to overcome (or at least up to flashing the overcome kernel) is necessary to ensure that there are no problems with the conversion to MTD (restock ensures a clean system and partitions, flashing overcome's kernel gives us an updated CWM recovery which is needed to flash an MTD rom), and the last thing anyone wants is for their tab to fail and become bricked. i have updated the first post to include a link to further explain MTD; what it is and what its benefits are. for the end user its not a big noticable change, but the possibilities it opens make it worthwhile.

i believe that i just missed out on the revamped partition version (that fixes /radio), and it should be included in the next build. if this becomes a problem for too many people i will rebuild a newer version. i have been reading though that its causing more problems in respect to RIL, and id prefer to hold out until thats sorted properly. note that when this fix is included, restocking will have to happen.

error 7 is the assert check failing, it means you are trying to install it on a kernel that has set the device name to something other than GT-P1000 (as pointed out by HumberOS), and since CWM cant detect that, it errors out to stop any problems caused by flashing the wrong rom on the wrong device. this is another reason you are told to flash the Overcome kernel instead of any other rom, as it sets it to the correct string.
[Galaxy Tab  Android Development] agustincordoba:
Hi all, I'm still on build 33, running very smoothly. There are just a couple of things, one is the mhz and v settings which still go back to default, even when stored as boot settings. The other thing bugging me is the camera, stock closing the instant the shot is taken, and Angel camera not taking the shot on "fine" resolution setting, application closes.

Just wondering how people are faring with either of these issues on both 33 and 34 ?

Enviado desde mi GT-P1000 usando Tapatalk 2
[Galaxy Tab  Android Development] priyana:
I got the error 7 coming from build #31 directly to #34.

So I cheated by not doing gb stock safe restocking,

Instead I just flash overcome kernel + overcome rom.

Then I flash #34 and all wipe and restore from TiB

On hind sight I don't probably only need Overcome Kernel ?

But when new partition size is out, do I need to do restocking from Odin with pit?
[Galaxy Tab  Android Development] kosmas58:
Many thanks to stimpz0r fot the addional info. With a less aggressive clocking smartassv2 is stable, I have to admit.

The legacy menu problem like on Moon+ Reader can be solved with:

Cheers