yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 Android Development] DooMLoRD:
seems most ppl either didnt realize the power of this special update.zip OR they are not sure how to use it!

in anycase i am providing two example files which will make it a bit more clear on how this special update.zip can be integrted into existing ROM installer update.zips and smaller update.zip for patches..

Examples of existing update.zip which are conveted into an update.zip (which has the special code) to flash it directly inside DualBoot ext2 files using recovery of MAIN OS

modded ROM installer

ROM used : X10x EWJet xKernel X.ex based on SE stock FW 2.1.B.0.1

Download : X10x.2.1.B.0.1.EWJET.XKernel.Xex_DB.zip

modded PATCH installer

PATCH used : ewX.tweaks.xkernel.X7

Download : ewX.tweaks_DB.zip

P.S.: these files are Amend syntax files to be flashed by xRecovery v0.0.3 OR FreeXperia Recovery

I highly recommend that u check the update-script of each update.zip which i have linked to!

Few considerations (FOR modded DUALBOOTING ROM's update.zip):

remove chargemon & recovery files from the update.zip of the ROM installers cause they will affect the booting of the embedded DUALBOOT rom

replace the chargemon with original SE chargemon (some roms keep it at /system/bin/charger)... just rename /system/bin/charger to /system/bin/chargemon

remove custom kernel folder (/system/kernel/) from ROM's update.zip cause anyways anything within it will never be used

Where can this be used?:

obviously this can be used to flash ROMs into the embedded dualboot ext2 files

the existing patches (baseband patches) can be modified to include these changes so that u can change basebands of the embedded dualboot OS

WARNING!

when u make ur own update.zips based on this BE VERY CAREFUL that REMOVE ALL FORMAT LINES from update-script AND THE mounter script get executed before the rom specific files start getting copied ELSE u will flash the ROM onto ur MAIN ROM and may need to relash to stock se FW using flashtool!!!
[Eee Pad Transformer General] moo99:
Plugged my droid 2 into the dock and nothing has happened on the tablet side. Droid says it's in usb mode. There's nothing in /Removable, just the sdcard in the tablet.

When I switch Droid from Mass Storage mode to PC Mode, "Preparing External Storage" blinks in the TF's notification bar for a second, but still nothing happens.
[EVO 4G Q&A, Help & Troubleshooting] GuestX0011:
I was wondering what recording format do you use out of the three. I would like to use the 720p but it seem when playing to stutter when playing back using the mp4 format?

Anyone else having this. Anyways what format do you people think is a better one to use.

And i searched but couldn't find much info about this :/
[EVO 4G Q&A, Help & Troubleshooting] taygutta:
what rom are you running? That can have alot to do with it. I dont have this problem and im on a rooted stock GB
[EVO 4G Q&A, Help & Troubleshooting] GuestX0011:
I use Mikfroyo 4.62.
[EVO 4G Q&A, Help & Troubleshooting] davidv001:
ive always used 720p on mp4 and works fine to me
[EVO 4G Q&A, Help & Troubleshooting] GuestX0011:
No stuttering? hmmmm I shall see.
[EVO 4G Q&A, Help & Troubleshooting] jadden:
Good News for us bad news for Epic Users :p

Our troll (hes been banned 6 times) is now gone the one that kept on asking for root hes moving to the epic forums since he now has an epic http://xdaforums.com/showthread.php?t=1127065

YEAH :D:p
[EVO 4G Q&A, Help & Troubleshooting] tgruendler:
Looks like a 7th ban and the thread was deleted. When will these people learn.
[EVO 4G Q&A, Help & Troubleshooting] mmegalodon:
LOL

I love it.
[EVO 4G Q&A, Help & Troubleshooting] xchompondizx:
Yeeeee about time

Sent from my butt
[EVO 4G Q&A, Help & Troubleshooting] dirkyd3rk:
Dude just ignore him like every one else, why give him what he wants? Stop accepting the troll bait and he'll go away.......you're giving him ammo dude he's still here.

Sent from my PC36100
[Motorola Droid X2] wdenker:
Is there a way to create an SBF file by combining other files? If so I believe I can get whatever files we need. Is there a way to extract the SBF or do we have to get a leak from Motorola or Verizon? I really want to get development started on this as I am itching for a custom rom.
[Motorola Droid X2] kgbrown247:
Leak from vzw or moto. Id pay if someone knew someone
[Motorola Droid X2] wdenker:
I think I would pay as well. This phone would be amazing on a custom rom.
[Motorola Droid X2] malianx:
likewise ^

Sent from my DROID X2
[Motorola Droid X2] Terri M:
+1 Would definitely pay!!!
[Motorola Droid X2] holytotemic:
I just want a rom without all the bloatware...this phone would be AMAZING without all the un-necessary crapware!
[Motorola Droid X2] spr0k3t:
I would donate for a custom rom as well. Should get a bounty going on this somewhere, just don't know where to set it up.
[Motorola Droid X2] MrWilliams2:
I'd throw some money at it.
[Motorola Droid X2] smkmeup:
sbf

Well im am actually going to an interview tomorrow for a Verizon wireless store sales rep and given the opportunity I will most definitely slap an shy file or 2 on a flask drive and get it to the power at b:De so they can do what they so best !
[Galaxy Tab 10.1 General] zaphyr:
According to Telias homepage, they'll get the 10.1 as early as the 29. June

I did preorder one, and was given an estimated delivery date 30. June.

I am doubtful though...anyone know anything about these dates?
[Galaxy Tab 10.1 General] UKseagull:
Yes there was some info posted about the 29th, I'll have a look for it.

Edit: I'd posted on Samsung UK's Facebook page.

https://www.facebook.com/SamsungUK/posts/232602220088700
[Galaxy Tab 10.1 General] zaphyr:
Sweet! It's confirmed then! :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] Szaky:
Hey guys! I would like to ask something...i was using official froyo firmware from samsung kies but about a week I changed my opinion about official firmwares because they are too laggy...and i wanted finaly Gingerbread...so i started to look up on internet and i found somehow darky's rom...i watched some videos on youtube and i've read that it is one of the best ROMs for Galaxy S...so i found one guide how to flash Ficeto's JVH along with Darky's v10.1....so after a couple of hours studying what to do i flashed it....everything was perfect...my SGS was never before so fast,smooth and laggfree...but i have one problem...i can't connect to my home or school wifi...it keeps writting authentificating and then disconnected...before on froyo i didn't have any problems with wifi...i tried to reflash it 3 times....nothing...i wrote on darky's group on fb and they told me that i should change my modem...so after hours of looking up what the modem exactly is...i flashed ZSJV5....didn't help...i tried out Ficeto's JVP too...nothing...so i went back to darky's v10.1 because it was the best in my opinion...my brother got a new Sony Ericsson Xperia ARC and he can connect to the wifi,my sister can connect to it with her symbian and we have also 2 laptops and 1 PC on this network...in the school my friend with his iPhone can connect but i can't...i could connect to the wifi before but after i flashed Ficeto's i can't...i had this mobile since christmas and i never had any problems with wifi...i tried to unplug the wifi,reboot the phone and i used static ip too but nothing changed...can u guys help me please? i know that i can't solve it myself so i would appreciate any help...thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] makaka11:
personally i do not found Darky's v10.1 good , there still many bug on it and crash , i would highly recommend that u try Darky's v9.5 last 2.2 firmware , it is very stable and it is same on speed as Darky's v10.1 . i Used it for over a month no big problem at all.

2.3 still need some fix ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] slaphead20:
you could try turning radio off then on again(airplane mode):)
[Galaxy S I9000 Q&A, Help & Troubleshooting] Hidr0*:
flash a stock 2.3.3 + cf root... wit till darkys release FINAL 2.3 the RC its buggy
[Defy General] rogier666:
The Froyo gallery app adds eye candy at the expense of function:

- The Eclair gallery is faster,

- The Eclair gallery shows long folder names that the Froyo gallery cuts off;

- When I move pictures from one folder to another, my Froyo gallery shows "ghost folders." The Eclair gallery doesn't have this problem.

Does anyone have an Eclair gallery.apk that works on Froyo?
[Defy General] SeaFargo:
I am interested too

Will be really nice ...

Have you tried to copy the Eclair gallery app to the Froyo system/app??

I attach the Eclair apk + odex ...

Try ... ;)

View attachment 628462
[Defy General] rogier666:
Thanx for the files, but they didn't work, Copied them to system/app, rebooted phone, and then nothing. The Eclair gallery didn't even show up in the app drawer.
[Defy General] account1:
did you change permissions to the file?
[Defy General] rogier666:
Nope. I just launched Root Explorer, renamed the original gallery files, copied the Eclair files, and rebooted my phone. And then I didn't have any gallery app at all.

The Froyo gallery came back after I restored it with Titanium.

Do I have to change permissions after copying?
[Defy General] SeaFargo:
Did you try to install it by. ADB?

With mass storage copy the installation files to /sdcard/Temp/ than:

adb shell

su

mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system

cp /sdcard/Temp/BlurEmailEngine.apk /system/app/MediaGallery.apk

cp /sdcard/Temp/BlurEmailEngine.apk /system/app/MediaGallery.odex

reboot

Otherwise I do not know. In any case if you'll need some more file from 2.51.1 Eclair just let me know ;)
[HTC Sensation] slsSpeC:
http://mobilesyrup.com/2011/06/16/b...ion-4g-will-be-available-in-the-coming-weeks/

I thought this was worthy of a thread.

Bell just announced they'll be releasing the HTC Sensation in Canada, which means it should work on AT&T 3G.

ETA is "in the coming weeks".
[Xoom General] Asurea:
The Verizon XOOM LTE upgrade will not be hitting before July, when it is currently scheduled. This date, as loose as it is, had the specific caveat that it is very possibly subject to further delay.

For obvious reasons, I won't name the source, but I will state that they are within Verizon, and are in a position to have accurate information.
[Xoom General] timrock:
Its not coming. Just like the sd card fix. I've already given up. Lesson learned: never buy from Motorola.
[Xoom General] Brenardo:
I believe it is coming my friend.... when? Prolly not soon but if never I believe VZW and Moto will be slammed with lawsuits from us sue happy Americans.
[Xoom General] dubie76:
The SD card issue is joke already. There is NO REASON as to why they cany have it working for us.
[Xoom General] JFMFT:
Sadly, those of us who gave Motorola one last try (on the Xoom, after we were all burned with locked boot loaders on the Droid X and subsequent phones) have been shown, once again, to not trust Motorola.

Yeah, some of the things that come with the Galaxy Tab 10.1 are limited/annoying, but Samsung is proving to be a monster of a manufacturer/designer. Thinner than iPad2? Yes please. OPTIONAL Tablet Touch Wiz UI? Doesn't bother me, it's OPTIONAL. Sure, it was probably Google's call on that one, but that's actually a good thing. Sounds like Google is headed in the right direction regarding Android skins.

Anyway, my Xoom is fine for me for now - and it was great as a first-adopter product. But NEVER again will I buy Motorola. EVER. This was the nail in the coffin. But I got my Honeycomb first, which was worth one last chance on Motorola.
[Xoom General] ZanshinG1:
As an Android developer who has to deal daily with multiple APIs across android revisions to store files on the sdcard, I pretty much want to punch you right now.

The sdcard situation is a huge mess. I'd rather have a final decent API, not another half-assed hack.

It's not "no reason", bub.
[Xoom General] csseale:
There is ABSOLUETLY NO REASON WHY
[Xoom General] keitht:
I can understand from a developer perspective but the damage is already done with all these other tablets releasing with working SD cards. It is too late now. Google/Motorola should have had this working before any other tablet released with a working SD card and they failed. I am also in the group where I will never buy a Motorola device again. My first and last.
[Xoom General] csseale:
Yea.....agreed..they robbed 800 from me. I will never even by so much as a Bluetooth from moto again. I know it will impact nothing. But the4g and SD card is just 2 much...lawyer said in 2 months there would be a leg to stand on if no lte and SD by then...not so much SD as it was never really advertised but lte def.
[Xoom General] keitht:
Good. I bought this thing on day one... almost 4 months ago. I have never seen anything like this before. Add me to the lawsuit please.
[Xoom General] gqstatus0685:
What's the SD card issue anyway? I'm not understanding how ref's can get it to work but a multi-million dollar corporation can't.
[Xoom General] ZanshinG1:
Thing is, you'd be the first person screaming if a majority of your apps started force closing due to the sdcard hack that'd have to be used until Google finalizes the new API.

Also, I wish people would stop making absolute statements they lack the qualifications to make.
[Xoom General] Arun01:
Just saw over at Droid world that 4g and SD card slot will be done in mid July but get this you will have to box up your Xoom and send it off.I'm happy to see the updates coming but jeez sending off my xoom and waiting for god knows how long is absurd
[Xoom General] hammer4203:
Hey just hack ur xoom! No but seriously, not one honeycomb tablet has a functioning sd card slot. Google did not have support for it in honeycomb. I would settle for powering down and being able to just load my files the old fashion way, if it would just read the sd card! And 4G ain't really tha important to me. Not like i'm gonna be streaming a moving dtiving down the road any way. It will get fixed, just give it some time. The xoom rocks no matter how you look at it. And just be happy not buying one those crapple knockoffs from samsung! That thing looks like a kids toy.
[Xoom General] keitht:
Sorry but you are incorrect. There are several honeycomb tablets released that have working microSD card slots.
[Xoom General] jeston:
We've always known we were going to have to send it in...
[Xoom General] Divine_Madcat:
BUT.. here is the thing... why did the SD card need a new API in the first place? SD cards have been working since 1.X; apps to SD since 2.2. None of this functionality is new, so why the sudden inability to keep it?
[Xoom General] JanetPanic:
When Android first came out internal storage was meant for apps and data only. Things like music and movies were stored on external storage (i.e. sdcard). When an application requests access to external storage it is in reality given access to /sdcard.

Now devices, like the xoom, have much larger internal storage and so can store what historically been kept on an sdcard internally. The problem is that applications are still (correctly) requesting external storage for the storage and manipulation of large files. This access points to /sdcard still. If you look on your xoom you will see all your music, movies, dropbox, etc... are stored in the /sdcard folder.

One problem. The xoom does not have an sdcard in it.

So now, with more modern devices Android needs a way to be able to intelligently allocate access to both the internal storage as well as a sdcard. This can not be done well if both point to /sdcard and thus a solution must be made.

Does that help to explain why this was not a problem in the past but now is?
[Xoom General] marctronixx:
this is without a doubt, the most well written easy to understand post i have seen on this forum in regards to why the SD card feature has been delayed. This explains it well for the laymen. thank you for the thought out post.
[Xoom General] Divine_Madcat:
Not really, but probably because i am just a nook owner. ;)

See, them pointing the internal storage to /sdcard is just silly. In the past (and other current devices), devices with large on-board storage give generous amounts of the storage to the /system and /data, with extra space mounted as /emmc (or the like). Then these devices would make the /emmc mount visible on a computer when you plugged it in, and the stock applications were programmed to be able to see this partition (or did so without fixing). This behavior can be seen on many devices like the HTC incredible, and the B&N Nook, and would have been a better solution for Moto.

Had they done this, i see no reason why the /sdcard could not be used then, as it always has been, and everyone would be happy...
[Xoom General] JanetPanic:
I am discussing in terms of internal components, not at a level that Android applications are supposed to work. Android apps, under normal circumstances, can access internal or external storage but they are not supposed to be aware of the mechanics of the storage. There is no concept of multiple external storage locations. Nor did it make sense to need this functionality early on. The nook color (which I also own) tackles it by partitioning and allocating storage based on digital media, something a generic android device can't do.

Now the question is how to detect and handle multiple storage locations. Personally I would approach it much like apps to SD. Default it to a specific storage location (internal storage for the xoom, the sdcard for something like the nexus one) and allow the user to move a specific applications storage to any storage available at the time of the request. This could be internal storage or any number of other mounted volumes. This puts the onus on the user to decide where to store info, but on android to track where each application stores its data.

Google has people far smarter than me working on the problem though.
[Xoom General] Gorgonesh:
How do phones do this then? My Atrix has 16GB of internal memory and the ability to support expansion in uSD card. The internal mem is partitioned into applications space (couple GB) and the rest storage which would seem to mimic the app space and MMC from older devices. Now we have the ability to access an SC card as well so it seems that this has been handled in Android 2.2+ already.
[Xoom General] Divine_Madcat:
As you correctly point out Gorgonesh, this was a non-issue that became an issue. Many other android devices had large scale internal storage, with a user accessible partition, that did not lose the ability to mount an SD card. I still fail to see what is different about the Xoom, in that it HAD to mount its internal storage as /sdcard, instead of /emmc (or something else).

If there is an actual technical reason why this happened, i would love to see it. Of course, this is almost impossible right now, since the source code is still under lock and key, and that won't change soon. But as it is, i have not seen a reason that the internal storage HAD to go to /sdcard...
[Xoom General] tomcrown1:
As far as SD card support is concerned I beliee this will happen in Icecream Sandwich and not Honeycomb. Google is within three months of releasing Icecream Sandwich if rumors about Samung Nexus being released in November are true.

I do not belive that Google will spend anymore time on honeycomb since they stated that Icecream will be the only operating system they will support once it is out.
[Xoom General] JanetPanic:
I am afraid I do not know, I am sorry, I do not have any Android devices with large internal space and external storage other than the nook. The nook, as I mentioned earlier, uses the space based on its specific purpose though, not in a way conducive for a general Android device. All I can tell you is that the Android API has no concept of multiple external storage devices at this time. So my question in return is "How do individual programs that are installed differentiate between the partitioned app space and external storage?" By convention (but not absolute requirement) anything beyond operational files is stored in external storage due to the fact that on most devices internal storage is limited. For instance copilot could store the 9GB of maps it uses on internal storage, but most phones would not have the space and this would break the app. As devices have progressed and internal storage increased the difference became less profound; The problem still exists in that there is no way for an application to decide intelligently at runtime which to use (internal or external storage). You could add a preference in the app itself but then the app becomes responsible for "plumbing" which is generally something to avoid.

http://developer.android.com/guide/topics/data/data-storage.html

If you want to read up on the subject. It is not an overly technical page, just a bit long. Skip down to using internal/external storage.

EDIT: Keep in mind that the Xoom currently uses internal memory for "external storage" so do not get confused by the term. With a functional SDCard slot the Xoom would effectively have 2 locations for external storage.
[Xoom General] JanetPanic:
The location of /sdcard is arbitrary, though it made it easier for people with rooted devices or file browsers to find. The point is that applications designate to put files to either internal or external storage. You can not specify which external or internal storage however. So to make intelligent use of multiple large storage locations either the API or the application management interface needs to be updated, otherwise the device is just guessing as to where to put files for applications. Shared folder locations, such as Music, Movies, and Pictures are a little easier in that the user can be given 2 mountable locations. This does not solve application access though. Nor does it solve access to the shared folders by applications where they do not use the shared folder functions.
[Xoom General] Gorgonesh:
@JanetPanic Thanks for the link, will read when I have time.

Just wanted to comment that so far it seems that all pure Google device only use/support one external storage location. In the Nexus One it was the uSD card, the Nexus S it's the internal 16GB with no expansion capability and now the Xoom which uses the internal 32GB as external storage. All devices that currently support large internal storage and external expansion are modified by the OEM. So the question is, how are they handling it in a way that works for apps that are installed? It would have to be done in such a way that apps such as media players could access both locations.
[Xoom General] JanetPanic:
For reads the problem is easily solved. There are functions to access the public folders. So if a music player accessed "getExternalStoragePublicDirectory(DIRECTORY_MUSIC)" then Android could simply merge the 2 Music directories (internal and external) to appear as a single location. That paradigm breaks down though when you want to write to "getExternalStoragePublicDirectory(DIRECTORY_MUSIC)"... And therein lies the problem in my eyes. Where to write a file....

There are work arounds to be sure, but nothing I have seen in a Google Experience Device, which is pretty much all I own (not counting the nook).