yashsingh1/xdaforums huggingface dataset:
[Android Software Development] RED_:
Thanks for replying, managed to find a solution in the end without using ListView. Thought about moving to a RelativeLayout as its more effcient but as my app is very small anyway in the end i've just gone and used nested LinearLayouts with a textview and imageview in each one.

Ridiculously simple when you look back on it.

I was actually going to use this tutorial which does what you explained i think: http://www.anddev.org/iconified_textlist_-_the_making_of-t97.html but it left me with a force close error so that went out the window.
[Galaxy 3 Android Development] Gsam101:
Here is a simple tweak for your phone for having the "ANDROID" logo at boot:

get bootanimation from emulator

push it to sdcard (adb push bootanimation /sdcard/)

mount system read-write (mount -o remount,rw /dev/stl6 /system)

copy bootanimation (cp /sdcard/bootanimation /system/bin)

chmod bootanimation (chmod 777 /system/bin/bootanimation)

Change playlogo (or samsunglogo if you have lagfix) to something with nothing but header on it (like #!/system/bin/sh).
[Galaxy 3 Android Development] Ulqiorra:
Will the trick work on 2.1 ?
[Galaxy 3 Android Development] Gsam101:
Maybe, maybe not. It will work if you get a bootanimation from 2.1 ;).
[Galaxy 3 Android Development] marcioddf:
Work on gt-i5500?

it "says" : "cp: not found"

Regards form Brazil,

@marcioddf
[Galaxy 3 Android Development] ilendemli:
works well, thank you

@marcioddf type in cmd adb shell and then type the commands

if you have rooted your phone, you also should type su
[Galaxy 3 Android Development] Manium:
Hello,

Thank you for your work!

But I don't understand what to do with this:

(I have lagfix v2 installed.)
[Galaxy 3 Android Development] FadeFx:
Is busybox installed propperly?
[Galaxy 3 Android Development] Gsam101:
Install busybox :).
[Galaxy 3 Android Development] madhuranand007:
Awesome it work but....

Can we have more different boot animations, other than these two (Samsung & android).
[Galaxy 3 Android Development] ilendemli:
of course you can use custom bootanimation.

search for bootanimation.zip files on google for android and copy the file to

/system/media/ or /data/local/ you can also create your own animations, or just a picture.
[Galaxy 3 Android Development] Overlord_4:
When replacing this file in system/bin/

in your Clean JPA ROM it shows that there is insufficient space to carry out the paste.

It worked fine in JPF, but since I wanted the lock screen I reverted to JPA. :)

Help, please?
[Galaxy 3 Android Development] Gsam101:
Did you remount /system rw ?
[Galaxy 3 Android Development] Overlord_4:
Yes. :(

I followed all your instructions, let me try it once more...

Oh, damn, flashed the phone to JPF clean. :P

Alright will do it in the near future.

EDIT: Tried it in JPF, and it did not work.

Weird, I had it work just a few hours ago on the same firmware... O_o
[Galaxy 3 Android Development] ilendemli:
it works for me without problems on JPF
[Galaxy 3 Android Development] pokosik:
don't understand where should i write this commands? can i do something with root explorer? or should i write all commands in emulator in my phone?

EDIT:

So i copied bootanimation to system/bin, then removed original bootanimation, then renamed downloaded bootanimation from bootanimation.bin to bootanimation and now everything is working. All done with rootexplorer.
[Galaxy 3 Android Development] ilendemli:
WTH? you are copying tje file, and deleting it then? take a screenshot pls
[Galaxy 3 Android Development] pokosik:
i am deleting stock bootanimation and copying new one to same direction. only bootanimation name witch i downloaded was bootanimation.bin so i had to rename it to bootanimation without bin words.

So what we need to do is (all this i did with rootexplorer):

1) download new bootanimation to sdcard

2)rename bootanimation.bin to bootanimation

3)copy new bootanimation to directory where is our stock bootanimation (don't remember now), and that's all. When you are copying new bootanimation you must get message do you want to replace bootanimation file, if you will get this message it means that everything is ok. restart phone and you should get stock android bootanimation.

sorry for my english
[Galaxy 3 Android Development] ilendemli:
and that worked?
[Galaxy 3 Android Development] pokosik:
yes it worked for me.
[Galaxy 3 Android Development] ilendemli:
are you using JPF? where did you copied the file?

comes the samsung logo at startup?
[Galaxy 3 Android Development] FadeFx:
The first steady white Samsung logo will always be there, it is inside the bootloader...
[Galaxy 3 Android Development] :
i dont mean the white one, you can delete it from the framework-res.apk file, the white one

i mean the animation after the i5800 logo..
[Galaxy 3 Android Development] Gsam101:
Delete playlogo/samsunglogo (if you're using lagfix) ?
[Galaxy 3 Android Development] :
nope, i am not using lagfix
[Galaxy 3 Android Development] Gsam101:
So delete /system/bin/playlogo ?

Or replace it with a stub, like:

#!/system/bin/sh

#Nothing else

Don't forget to chmod 755 it ;).
[Galaxy 3 Android Development] :
deleting removes the animation, thats okey, but the sound at startup, is here, i want to delete it too.
[EVO 4G Q&A, Help & Troubleshooting] EVOKeith:
I have spent the last while searching around here and Google and I have not found an answer to this yet.

I just added my work email to my EVO using Exhange Activesync. It works great for Mail and Calendar. For some reason it will not pull my contacts. I have removed and re-added the account a few times, making sure that Contacts are selected to be synched, and it even shows that it is synching them and it completes.

I also tried connecting to my laptop using HTC Sync and syncing my EVO to Outlook that way and still no joy.

Anyone have any ideas or workarounds or a link to a post that maybe I missed in searching?

Using Outlook 2007 in case anyone needs to know.
[EVO 4G Q&A, Help & Troubleshooting] EVOKeith:
Update: We just set up the same account on my friend's Droid and the contacts pulled immediately.

I am completely stumped.
[G Tablet General] JBlayz:
I got my G Tab today.... :D

Prior to its delivery I did lots of reading here to learn about its capabilities and how to do installs etc... Thanks to all of you that are developing ROMs, etc... to help make it better.

For now my main issues are

(1) Wifi dropping

(2) bluetooth clipping

(3) difficulty moving files on to my MicroSD

(4) Force Close Error Message

I installed Clockwork Mod internal (8 I think) and TnT Lite 3.1 and patch 3.1.4 because it seemed like most users on this site said it was the most stable..

My question is, am I missing a patch or should I be using another Rom to get Bluetooth and WiFi to work without issue?

Is there an easy way to see the MicroSD card when I am connected to the G Tab via USB so I can transfer files directly?

Should I install another ROM in order to avoid the "FORCE CLOSE" error message?

Thanks again for all that hard work.
[TG01 General] fxdjacentyfxd:
Hi.

Forgive me I asked here but it seems to be nowhere explained, maybe I was not able to find.

I try to utilize leeston2379 suggestions about cooking in His tutorial.

Could anybody explain me why newly created ROM from original firmware ( in my case Malezya ROM ) after dumping and building without any changes , differs significantly from original in size.

It is about 20-30MB lesser than original.

I dumped this newly created ROM. It seems to have all packages like original ROM but for example .dsm files are significantly lesser.

Could anybody confirm that such created ROM ( even without any changes ) can be safely loaded to tg01 and what exactly has been changed and why ?

I count on serious and comprehensive explanation.

Regards

fxdjacentyfxd
[TG01 General] mirolg:
hi, sorry for my poor english, but i will help you :D

when you dump a ROM, that has orginal 200 MB and you building a new ROM without any changes, then must your cooked ROM to have also 200 MB. ech oem package folder has one .dsm file. pls tell me: wich kitchen and wich ROM.

regards, miro
[TG01 General] fxdjacentyfxd:
Thanks miro.

1) Kitchen suggested in this thread http://xdaforums.com/showthread.php?t=804529 and with direct link here :

http://xdaforums.com/attachment.php?attachmentid=416649&d=1286711727

2) I did two steps from this kitchen as leeston2379 suggested :

a) "1. dump.bat"

b) "2. build no XIP port_no auto.bat"

The same result ( I mean new ROM lesser than original ) I got when in step b)

I run "2. build.bat" instead of "2. build no XIP port_no auto.bat"

3) Original ROM I took for experiments is Malezya ROM from link :

http://www.toshiba.co.jp/product/etsg/cmt/english/asian/tg01/exe/TG01WP-WM6.5-Malaysia.exe

Currently I use this rom and I wanna to see what cooking is :) and in first step to cook ... nothing so dump and build without any changes.

Regards

fxdjacentyfxd
[TG01 General] mirolg:
one question by side :DO i have noticed, you thank after a helpful post, but not with the thank button. why? :D is not why i like you thank- point- i´m wondering only- and you not the only.
[TG01 General] mirolg:
ok, this kitche i use mostly too.

the result in MB is the same if "2. build no XIP port_no auto.bat" or " 2. build.bat"

different is: 2. build no XIP port_no auto.bat- no new xip building- less time

i don´t know what is wrong- but is wrong and i think this ROM will brick your tg01
[TG01 General] fxdjacentyfxd:
hehe, it was so called "thanks in advance" :) . If You give me answers to my questions I will press "thanks" button :)

Regards

fxdjacentyfxd
[TG01 General] fxdjacentyfxd:
It's too bad :( So I will try the same not with original rom but for example with clean Mangasora rom and will see results.

Anyway is there any other available kitchen/way to use original rom for cooking not special prepared rom like Mangasora rom ?

Regards

fxdjacentyfxd
[TG01 General] mirolg:
no, no problem- but is not the first time. i think you are very critical :D

but :cool:
[TG01 General] mirolg:
the easyst kitchen is that you use. ffboy kitchen is not so easy to understand.

BUT i tell you: no matter ROM or custom ROM- that what you dump out must, when no changes, the same Value in MB and kB!

if you like- one link http://xdaforums.com/showthread.php?t=564130
[TG01 General] fxdjacentyfxd:
Explain me one thing yet. I noticed that even retrieving payload from .tsw and merging it again with the same .tsw to get "new" .tsw gives ROM that is not binary equal to original. Yes, it has the same size but comparing both roms in any editor one can see a lot of similar looking places that has been changed. Could You xplain it to me ?

I tested original ROMs again. English Orange ROM and Malezya. Both after cooking nothing gives .tsw files that differs in size to their originals. Maybe You could ask Your colegues cookers about it ? Is this situation exception for original roms and if not what has to be done additionally after dumping , so that new .tsw files have the same size as their originals. I would really prefer to work on original roms :)

Regards

fxdjacentyfxd
[TG01 General] mirolg:
.. your thread is open for all cooks, to answer you: D

all my knowledge i have from this "best" forum site and his members!

If someone begins to cook, he must be prepared and know that it can so often give problems and that the tg01 brick or not start. ShortPin and tg01 downloader-procedure i must make multiple times (i love and have also afraid for my tg01)

BUT this a way to learn everything and to find a solution.

wish you all succes :cool:

miro
[TG01 General] fxdjacentyfxd:
Maybe someone answer who knows. Anyway thanks for help.

What I found interesting. Such newly created rom form original rom has as You know lesser length. Dumping it again and building new rom without changes, gives at last what we want - new rom size has the same size as original ( not virgin one but this cooked without changes ).

Maybe it is nothing terrible that first rom created from original rom is lesser and as a matter of fact we should take for cooking not original rom but this created from it without changes ? . Maybe original rom has any redudant information ( I mentioned You , .dsm file were shortened after cooking and in my oppinion they are now similar to thouse I can typically see in Novembre or Mangasora roms ).

On the other hand, I have never found anywhere yet, original rom should be treated with any special atention during dumping and cooking.

I know I can use short pin method :) but matter must be worthy to sacrifice tg01. Currently problem seems to be known for some cookers ( some ot them had to use original rom as a base of cooking ) so I will wait.

Regards

fxdjacentyfxd
[TG01 General] leeston2379:
I am dumping the Malaysia ROM now, I will rebuild and flash to my test device regardless of size difference and let you know the result. Give me a few hours though as i am very busy and doing this in 5 minute gaps when I a have chance.

I have dumped the ROM twice and found that "Missing Manifests" are reported.

First time there were 3 missing, 2nd time 5 missing. The manifests are .dsm files so I am assuming that if the .dsm is missing from a package it is no longer a package and won't be included in the ROM by BuildOS causing the size difference. The first dump also failed to separate the OEM and SYS packages but succeeded the second time

I have rebuilt and flashed the ROM and it appears to work, i do not have time to test it fully but it does boot and run with SPB Mobile Shell, HOWEVER as the two dumps had different .dsm files missing it may be something more important missing the next time causing a real brick.

This is purely speculation but I believe this particular ROM does not like to be dumped and you will have to use a different base ROM. I am happy for you to use mine but I would recommend one of Miros clean ROMs as a base.

Hope this is helpful:)

Attached is a photo of the output from the .bat file showing the missing .dsm files (this is from the second dump).
[TG01 General] mirolg:
... As already mentioned: Each folder (if any OEM packages) need a .dsm file. Without it, the package can not be cooked. Ie = if at the end (finished ROM) that those. dsm missing, is missing the complete pakage = Created ROM has less RAM.

if you has nothing doing- but a .dsm file is missing, then is something wrong

what? i don´t know
[TG01 General] fxdjacentyfxd:
You are great ! I am waiting for results.

Maybe You are right but I hope You are not ;)

So Your test will show the truth. I did not pay attention on this "Missing manifest" assuming that any errors stop dumping/building.

Regards

fxdjacentyfxd
[TG01 General] leeston2379:
Updated post #13
[TG01 General] fxdjacentyfxd:
Thanks a lot for Your test. I have this manifest warning too doing dump process to text file. I have found somwhere in internet that some of this .dsm are concerned with XIP . Here if You wanna to see Nokser's thread not concerned with tg01 but mentioning some of the manifest files :

http://webcache.googleusercontent.c...fd3-bd127a05e4de.dsm&cd=1&hl=pl&ct=clnk&gl=pl

Anyway, could You explain me once again what build is running without brick ?

You simply did dump and build on malezya rom and took created .tsw or You dumped created rom again and built again and took this double built rom?

Regards

fxdjacentyfxd
[TG01 General] leeston2379:
I dumped the original ROM rebuilt it then flashed it. I did not double build.

Just dumped the rebuilt ROM and no errors occurred. It may be worth dumping the Malaysian ROM removing the packages you require then adding them to the Orange UK ROM as this dumps OK and both ROMs are in English.

The build of the Malaysian ROM is CE OS 5.2.21840 (Build 21840.5.0.60), just for reference.
[TG01 General] fxdjacentyfxd:
I am not familiar with the matter so far :) but I did simple test as in Nokser's thread about dumping XIP. I took xip.bin created after dumping malezya rom and dumped it via XipPort.exe. All "not available" manifest files are present so in my oppinion it should be possible to avoid this "terrible" warnings and maybe any new dump script is required for such original rom. This time it is my speculation :)

Regards

fxdjacentyfxd
[TG01 General] fxdjacentyfxd:
Hmmm, really ? I dumped English Orange ROM too. I do not remember whether mentioned warnings appeared but I am sure created rom was lesser than original rom like with Malezya rom.

Regards

fxdjacentyfxd
[TG01 General] leeston2379:
I don't remember either, I just remember that it worked after I modified and rebuilt it.

I have just dumped and rebuilt the already dumped and rebuilt ROM, I have flashed it and it appears to work OK. It did not have any of the errors during dumping we first had and the sizes of the ROMs stay exactly the same.

I will upload this rom (takes about an hour) for you to dump and use as your base so you know that the ROM your working with boots not bricks the TG01.

Hope that makes sense and helps.
[TG01 General] fxdjacentyfxd:
Thanks for that.

In the meantime I was trying to do some trick like "monkey" who does not understand what xip and related problems are :). I divided dump .bat file into to parts so that PackageBuilder was able to see "missing" manifest files. What did I see ? Look at the end of packages build:

**********************************************************

5.2.0 5060 Sysapl

5.2.0 5060 OEM_DPI_192

5.2.0 5060 OEM_Lang_0409

5.2.0 5060 OEMXIPKERNEL

- boot.hv is missing!

- boot.rgu is missing!

- cecompr.dll is missing!

- ceddk.dll is missing!

- DAL0DRIVER.dll is missing!

- DALConfig.dll is missing!

- DALSys.dll is missing!

- datamover.dll is missing!

- Diag_LSM.dll is missing!

- kd.dll is missing!

- lmemdebug.dll is missing!

- msm_time.dll is missing!

- nand.dll is missing!

- nk.exe is missing!

- osaxst1.dll is missing!

- pmem_drv.dll is missing!

- QCBPM.dll is missing!

- relfsd.dll is missing!

- rpc_pmem_client.dll is missing!

- smem.dll is missing!

- VMini.dll is missing!

- wce_pmem.dll is missing!

- wce_rex.dll is missing!

- wce_tramp.dll is missing!

Done!

Copy packages to kitchen root

...................

...................

*********************************************************

As You can see it was trying to do package OEMXIPKERNEL . Do we really need it here ? We do of course need it at all because it is kernel but Your test prooved all is working ok so It is attached in build process in other way. Even if I wiil try PackageBuilder will see above missing dll's I do not know whether such bild rom will be ok but maybe You will be so kind and test it again ? :)

Interesting, now I did dump process without warnings. I will see what build process will do

Hmm, it was "blind street" i guess. I got new rom larger than about 2 MB to rom we get when manifest warnings appear so I do not know is it worthy to check it.

BTW. leeston2379 could You check how much memory You have on "good day" after booting ? miro was afraid about it.

Regards

fxdjacentyfxd
[TG01 General] olyloh6696:
hi guys, sorry if this has no revalance to cooking roms but, why does it that we are using rom dumps to make roms for our devices? is it not possible to get an entire different WM build for our devices to run? this is because with the toshiba dump roms, they are not optimozed well for performance and ram. the dlls in them are contantly running all the time in the background (such as powermanagement.exe 12mbs of RAM!!!) there are many other toshiba apps running in the background. we always wonder why we have so little ram to play with. it isn't a hardware limitation. it is badly optimised software from toshiba. out of the available 256mb ram, we can only get up to 90-95mb ram on vanilla plain wm6.5.x roms. other devices are capable of at least 140-150mb.

is there not a way that one day we can get a rom that doesnt have any branding whatso ever and is perfectly clean with no toshiba dlls?

sorry if i am asking a silly questions... i look forward to your responses.
[TG01 General] leeston2379:
The dumped, built, dumped, built ROM can be downloaded

HERE

.

I didn't quite understand what you want me to test, but am happy to give anything a try. just let me know.

leeston2379 could You check how much memory You have on "good day" after booting ? miro was afraid about it.

The ROM I just uploaded has 75.6Mb free after being on for an hour and navigating a few menus.

We use dumped ROMs because we need the OEM (Toshiba) part of the ROM so that it works with a TG01. I could dump a HD2 ROM and remove the HD2s OEM and put our OEM in place. This would give you the HD2s ROM but to make it work we needed the Toshiba OEM which is where all the so called "problems" are.

A good way to think of it is like a desktop PC in that the OEM are your devices drivers and the SYS is your OS. If you have a bad network driver you can update windows all you like but unless you fix the bad driver the problem will still be there no mater what OS you use.

Hope that's what you wanted to know.
[TG01 General] olyloh6696:
thanks for the reply :) i dont really mind the toshiba roms, as long as they are optimised well with more available ram. the biggest problem wirh our devices is lack of free ram. htc devices are good at this. the ram is fery well optimized for them. when we run a plain sense on a plain vanilla wm 6.5 rom we only get 50-60mb on boot. if we disable the start menu etc, we get more ram, but it is not ideal. other htc devices like the touch hd (288mb ram) have lots more free ram (althpugh they have 288mb opposed to 256mb) the difference still shows they have more ram. i just wish there was a way to get more ram :(

thanks
[TG01 General] fxdjacentyfxd:
Thanks for this upload.

hehe :). I was of course thinking about my new strange rom ;) which I created avoiding "manifest missing" warnings during dumping ( simply I was able to create OEMXIPKERNEL package ) . As I mentioned it differs in size both from original rom and rom we can get dumping malezya rom with "manifest missing" warnings. If You would be so kind I could give You such rom for test but I am afraid that with quality of my home network I will be able to download or upload something such big no sooner than on monday being at work.

leeston2379 could You check how much memory You have on "good day" after booting ? miro was afraid about it. The ROM I just uploaded has 75.6Mb free

[/QUOTE]

Hmm, I do not quite remember ( currently I have original malezya rom on my tg01 but with miro "ram enlargement" ) but original rom has few MB more but maybe I am wrong.

Regards

fxdjacentyfxd
[TG01 General] mirolg:
hi olyloh6696,

i will try to cook a ROM with Toshiba OEM`s but without

(such as powermanagement.exe or Com Manager, WLAN, MotioSensor ...)

but i change this System-apps with HTC (witout any System-apps phone will not work)

i will see if i have succes or 2-pin method :D
[TG01 General] leeston2379:
If you upload and provide a link I will test it, would be Monday evening though as I'm at work next week, I'm off sick at the moment, that's why I've got time to test and play.

As I say time for me is short but if you upload it I WILL test it.
[TG01 General] leeston2379:
That's a brave man that is.:D
[TG01 General] mirolg:
without bravery,not one miROM be exist
[TG01 General] olyloh6696:
:D miro you legend! i think that you deserve donations for your hard work. we all respect you! with the donations, you could get yourself another tg01 to help you test more? i would be willing to donate! (need to get a paypal account first though!)

i will see if i can try and test for you too! hopefully we can get more ram..i will post a link where other members have pointed out that powermanagement.exe etc are running im the background!
[TG01 General] olyloh6696:
link to thread about toshiba apps running in background

http://xdaforums.com/showthread.php?t=730557

EDIT: just realised you were involved in that thread too!

how can we discover these hidden apps? is there an advanced task manager? i have seen one to stop certain .exes
[TG01 General] mirolg:
thank you for this post- i will see what i can do :D and thank you for praising!

...donation, i don´t need.

a scratched, damaged- but functional tg01 that would good :cool: