yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile General] psdos:
It is true, anyone to know how disable this notifications from bluetooth connect/disconnect?

Thanks.
[Touch Pro2, Tilt 2 Windows Mobile General] GordonTGopher:
Use the cab that is linked to in this thread. There is also discussion in the cabs, tips and tweaks... sticky thread

Gordon
[Touch Pro2, Tilt 2 Windows Mobile General] Ramsfan_Jim:
It doesn't seem to work (for me anyway).:(
[Touch Pro2, Tilt 2 Windows Mobile General] zehn:
Hmm,

is a cooked rom without this damn notification aviable ?

regards
[Touch Pro2, Tilt 2 Windows Mobile General] Ramsfan_Jim:
Yes ! Use any of the Energy ROMs recently, my preference is :- http://xdaforums.com/showthread.php?t=553506

or you can use hAndyUtils:-

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

Cheers,
[Touch Pro2, Tilt 2 Windows Mobile General] zehn:
@Ramsfan_Jim

Thank You so much for this :)

many many thanks

i have used the handyUtils but they worked not for me, on my new 6.5 german t-mobile rom.

But in this thread http://xdaforums.com/showthread.php?t=563592 i found hAndyNotify.cab that works on my rom :-)

regards zehn
[G1 Android Development] Darkstrumn:
Hi All,

Here is my second contribution to the Android community, android2sd!

I tried to make the installation a bit more straight forward and the readme very verbose.

There is NO going into recovery and wiping of the Android to install this construct. (Of course you can if you want to have a clean slate to build from but it is by your choice only!)

Remove .zip from filename, then unrar (sorry to zip users, zip was too big:() the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.

Execute the script {where ever you installed it}ie:

/data/local/android2sd.sh and follow the instructions.:)

Included are several of my scripts (updated from the ones in data2sd) and the rules still apply, adjust or remove as you see fit. The readme explains them all.

I have noticed an improvement in speed based on the install, but you can judge for yourself and tweak as you see fit!

The construct uses Overlay Profiles to overlay the Android system and thus any changes to the Android once loaded, are actually done to the overlay profile thus you have like a safe mode which is the untouched Android under the overlay.:D

Hope you find it useful!

Darkstrumn
[G1 Android Development] ccyrowski:
Damn man. Good work.
[G1 Android Development] PsychoKilla666:
sounds interesting, what is this all about?
[G1 Android Development] innerspace:
brilliant?!? I think.

So basically, this is a non-destructive method that enables us to run new roms on the G1 without flashing? Am I reading this right? If so... wow.

edit: or, erm... maybe not... i think i've been up too long. Gonna have to watch this thread to get a better grasp on this. interesting nonetheless.
[G1 Android Development] LucidREM:
Rename To RAR

very interesting .. at first i failed to see this part as i'm sure many pay skip over the whole "rename to rar" thing - LOL - so this loads profiles from the SD to the phone

for anyone having trouble with the whole "rename" process try this:

http://files.lucidrem.us/jf/android2sd.rar

as i know windows with hidden file extensions does not allow a rename easily
[G1 Android Development] tr.slate:
So what exactly does this do? I see install instructions, but no description.
[G1 Android Development] Darkstrumn:
Overlay Profiles...

Well,

I've worked up the natural progression to this XXX2SD business, and have made an Android2SD construct which can expand the Android similarly to the the previous constructs, but puts /system, /data and /cache on sd.

So let me explain the overlay thing:

An overlay profile is a snapshot of the Android file system, namely /system, /data, and /cache.

The initial profile is called 'android2sd' and is a snapshot of your android at the time of install, plus the file system structure as explained in the readme adding the mnt/ dir structure and additional scripts in bin/ (which you can remove or adjust as you need).

Typically I reckon folks would only have the one profile and under it your original Android. But you can create additional profiles and set them up however you like. The overlay is overlayed on top of the Android file system with any changes or edits to the system affecting the profile and not the Android under.

The effective change is that the /system /data/, cache are moved to the sdcard thus expanding them to however large your sdcp2 is; on a class 6 card also improving access time.:D

A second benefit is that the underlying Android is safe from alteration and can be booted into like a 'safe mode'. (It can also serve as the base for new profiles, or you can make new profiles from active overlays. These snapshots can serve as a form of backup, but that is a fringe benefit.

It cannot protect the Android from update.zip installs exactly, as those will modify the Android directly, but say you try a theme and it gafs your 'droid...you can reapply the firmware update to clean out the theme, then copy the desired profile back to the Android and restore the Android to the state of the profile. (I would recommend having a 'base' profile of the Android but not using that as an active profile which will thus serve as a backup) Note: To restore the Android as described above, you cannot restore using a profile with 250+ apps in /data as the Android doesn't have the space for it! :eek:

Originally I used unionfs for the overlays but it was too slow.:(

Hope that explains things here; the readme has far more detail.

I've gotta go, but if I see that I've been as clear as mud, I'll try to explain better when I have more time.:)
[G1 Android Development] MarcusMaximus04@gmail.com:
Hmm just out of curiosity: What are you using now? Bind mounts?
[G1 Android Development] brandenk:
I got a little bit lost in setup, I am not sure if I had problems because I was using Cyanogens latest or something else but either way Im going back to JF to try this.

I installed it using the "-COMMIT" addition

But when I made it to installing/linking apps things wouldnt link

Maybe I will let a few other people try it first.
[G1 Android Development] Darkstrumn:
More info...

Yes. Originally it was to have a multi profile layered system using unionfs: union0 the ro base snapshot and union1 the rw profile containing the copy-on-write data. But as the tests went on, the unionfs was too slow to use for /data; Android is unforgiving of unresponsiveness and was ANR'ing the apps that didn't respond fast enough.:(

The faster bind mount means that union1 is now not used and union0 is rw.

The reason I wanted the union0,union1 path was that the union0 could serve as base and various profiles could be layered over any part of the file system granting "Lego" like flexibility in how the user could adjust their a2sdLoader.sh script (the android2sd loader which controls the overlay process).:)

You could have a pristine base and several "change" profiles that you layered to your liking and could change any sub layer to different effect.

While you still can under this paradigm, it is not as compact.

But the unionfs option is not completely done away with. It can still be used for the above layering but shouldn't be used for that apps and package system.

An example of the layering I'm on about:

The Android 0-layer which the base layer is a snapshot of.

The base layer is pristine (fully configured settings, but minimal apps loaded, maybe a particular base launcher layout and wallpaper).

A change profile containing my apps and package system

A change profile containing a version of etc with reconfigured bluetooth settings.

A change profile with a theme (manually installed, or snapshot to profile and restored to pristine)

Now I could take these 4 profiles and arrange several different setups:

'base' with all apps loaded, themed with custom bluetooth

'base' with all apps loaded, themed with normal bluetooth

'base' with all apps loaded with custom bluetooth

'base' with all apps loaded with normal bluetooth

'base' with all apps loaded

'base' themed with with custom bluetooth

'base' themed with normal bluetooth

'base' with custom bluetooth

'base' with normal bluetooth

...

Those would be set to serve as the ro union0 and the rw union1 which will hold the copy-on-write changes to the overlay (which preserves the sub layers)

You could have several more theme profiles and have a script that randomly chooses one at boot...:cool:

You could simply use the overlay to protect a favored configuration. Should anything untoward happen such as accidentally damaging the packages.xml file while experimenting with the system, you could simply delete the change profile, make a new blank change profile and the damaged files are undone.:)

The things one can do with the overlay concept are limited only by your imagination and need (and if they slow down app processing too much causing ANR's:rolleyes:)

It vary well could if done correctly allow one to have multiple roms as profiles and switch them based on the selected profile, but I have yet to experiment on that...I reckon that is my next move!:D (Note that this path would have a high space cost as the roms are about 40MB zipped!)
[G1 Android Development] Darkstrumn:
Taken from [Rom] CyanogenMod:http://xdaforums.com/showthread.php?t=518851

"DO NOT RUN ANY OTHER APPS2SD APPLICATIONS ON THIS BUILD. YOU WILL BREAK YOUR SYSTEM. THEY ARE NOT NECESSARY BECAUSE THIS ROM WILL DO A2SD AUTOMATICALLY AND BETTER!"

The android2sd construct pretty much falls into the A2SD category and thus is likely the reason you had issues with the install.

My Android is based on JF 1.51... and thus your mileage will vary based on the rom you are using.:) I reckon with a rom derived from theh JF roms, the install may work as intended.

As I go into the next construct build process, I will see if I can't make it multi-rom compatible (to support multi-rom profiles:D) I'm sure it will take some time to do as I would have to use my actual Android to test with, but no worries!:cool:

Hope that helps a little. Sorry it's not better news though.:(
[G1 Android Development] twistedumbrella:
An excellent "misuse" of this concept would be to run ion (picking it for its speed and almost stock nature) with a hero overlay (picked due to known instability as we are still developing it) so that ion would serve as a "safe mode" for when you crash hero.

I have a spare phone if i crash this and a secondary sd for if that gets corrupted. Let me know if you need help testing.
[G1 Android Development] overground:
Interesting thought, and if this could be done, I suppose it would be possible to have bluetooth working in ION while using a Hero overlay?
[G1 Android Development] Darkstrumn:
Request for feedback...

Hi All,

Those who've installed android2sd, how is it going?

Can you give some pros and cons of your experience so I may improve things going forward? (Hopefully no cons exists!:p)

I know that roms that already make use apps2sd will encounter issues as the apps2sd and android2sd function similarly and thus step on each other. I may be able to detect this condition and adjust for it going forward...we'll see.

Thanks in advance for your input!

Darkstrumn
[G1 Android Development] Darkstrumn:
Thanks for putting the rar up, XDA wouldn't take the .rar and I didn't want to signup to a file-share site just yet.:)

And it being seemingly natural to make windows show file extensions, it didn't cross my mind to make a note about that.:o

Thanks again!
[G1 Android Development] njuncos:
How come no one is trying this? It seems to me an excellent idea and would be really cool to boot mutipe roms if someone figures that out. I'm not testing this because I'm using appstosd and didn't want conflicts...but no one else with jf1.51 Rom is testing this idea?

Just curious
[G1 Android Development] Sirus20x6:
so wait a second. let me get this straight ... if I have a class 6 8gb card i might be able to install a hero build without rosie or widgets with the original launcher on the sd card that might actually come sorta, kinda, a little close to a speed that might be bearable? at least for like 5 minutes? ;)
[G1 Android Development] B-man007:
Can this be adapted to install bigger roms such as hero without the dangerspl :D.

XD

Ill try this with ion later tonight
[G1 Android Development] Drizzy Drake Rogers:
wow this is beautiful work! now to test it!
[G1 Android Development] Shaquiel Harris:
Im trying so hard to understand this lol.. Correct me on my errors but from what i read this is my hypothesis on what i think this does..

This is like a apps2sd but with data and that type thing from the build we are using? And you Said this takes snapshots So we can create several profiles of the phone? Like for example have a profile with some apps loaded and another profile with all removed and be able to switch between them at will?
[G1 Android Development] madunix:
i would love to try this, but i am a person of following instructions when it comes to this, i know just the basics and if there were anything to go wrong, i wouldn't know what to do. and given the fact that ur the one that came out with this, i'd be buggin u for answers n i don't wanna be that n00b =/ lol, but honestly man, this seems like it took alot of research and time for u to cook up, and i'm sure this goes for everyone else on this forum as i would like to say thanks for ur time n effort. this really is great stuff :)
[G1 Android Development] raznalab:
I see that you say to update the "a2sdLoader.sh" file to configure how the different overlays load, but could you give an example of your a2sdLoader.sh file as I do not understand exactly how everything is setup. More specifically, what changes do you make in order to have the "apps" profile load on top of one of the theme profiles. Thanks.
[G1 Android Development] Darkstrumn:
More on the example...

Interesting you should ask, based on the example I gave, I actually implemented the change. I don't have any themes exactly, but I've structured the overlayEnv to account for them, added a theme loader (based on my continuing experiments on themes, and moved the apps into a container profile. a2sdLoader.sh has been updated to accommodate the updated structure.

This is a snippet of what is currently loading Wintermute' overlay profile environment. It is the bit that loads the contailer profiles such as the "app" profile.

First we make the container profile:

buildNewA2SDProfile.sh app -BLANK; This make a blank profile which we then cp our apps to:

cp -a /system/sd/overlayEnv/android2sd/data/app* /system/sd/overlayEnv/app/containers/data/;

This will copy both app and app-private to our container in the correct location.

Now, we can remove the files from the "android2sd" profile (which will also recover some space)

We update the a2sdLoader.sh script to load the containers after all the other mounting work is done as this is a layered mount...

And the loadTheme.sh script:

While this is not layman, it's not too complex either. I've only highlighted the bit that handles the advanced profiling I talked of previously.

Once in place, you would only need to modify minor bits to change themes, containers and such because variables hold the profile settings.

Once I get more into Android Apps, I may make a front-end that will allow the user to do such changes from a GUI and a few field prompts...;)

Hope this answers more than it makes one question!:D
[G1 Android Development] raznalab:
You are definitely right, this is not for layman which is exactly what I am as far as scripting goes. I really don't know how to handle/change variables to make the construct load what I want. I may have to wait until you create an app that can provide a GUI for this process, unless you'd like to help me out and maybe break it down with real world examples. Sorry I'm such a noob, but everyone has to start somewhere and I may have bite off more than I can chew. This is great though, I just wish I knew how to manipulate the scripts. Thanks for everything.
[G1 Android Development] Darkstrumn:
Just because you can do a thing...

No worries!

The advanced stuff is "advanced" You don't need to do all the script manipulations unless you want to change how android2sd works. I am showing that those with the know-how can do so if they choose, and this is some of the more complex things that can be done.

This is all similar to Themes and Roms and such in general. If this scripting makes your head-spin, stick to the defaults until you are more comfortable with changing them, just as you've done flashing a new rom to your Android. You're not customizing how the new rom works right out of the gates as a "noob" are you? Well, this is as much a system mod as a new rom save that you don't need to flash anything.:D

Also, don't get lost in what android2sd can be used for as it was primarily meant to expand the Android' usable storage space and tweak speed similarly to app2sd and data2sd. Android2sd simply has potential to do more complex modification of one' Android while not actually changing the Android itself.:cool:

As far as "real" world examples go, what I've given, was. Wintermute is currently so customized; I simply shared. However a GUI app would really make it more "user" friendly as currently changing things is more modder\\hacker friendly. The only problem is that a GUI is limited in what can be edited, where as the modder has full power to customize the a2sdLoader.sh into what ever they can imagine and make work.:D

Well, hope that cleared up that the complex bits are what you can do with it, not what you must do with it!:)
[G1 Android Development] raznalab:
I have setup the overlayEnv directory, following your instructions and I seem to be having problems getting the container apps to load on top of the android2sd base. I am almost certain that it is because I have not setup the a2sdLoader.sh correctly eventhough I copy and paste the scripting from your post. My ultimate goal is to get the container apps to load on top of the base. I was hoping you could post a a2sdLoader.sh file for me to download that is setup properly. If that is too much to ask for I apologize. Thanks again for everything you have done, and for your time. I really appreciate it.
[G1 Android Development] Darkstrumn:
Something to work with...

Oh, no worries! I was gonna post that fist, but reread what you had posted and figured I was being too verbose ( I do that from time to time:D).

I'm working on the theme'ing bit and what not, so the theme kit is not fully operational; you can ignore it for the time being.

New Kit:

Attached is the updated a2sdLoader.sh that will handle container Profiles (specified in the script) ensure you give it the proper permissions and such.

for the loadTheme.sh sript, execute the following:

touch /data/local/bin/loadTheme.sh&&chown system.system /data/local/bin/loadTheme.sh&& chmod 0750 /data/local/bin/loadTheme.sh;

This will put a stub in place for that script, for now.

New OverlayEnv Strucure:

The overlayEnv structure has been updated as follows for the new a2sdLoader.sh:

/system/sd/overlayEnv/

/system/sd/overlayEnv/bases/ <<--location of base profiles (main profiles)

/system/sd/overlayEnv/themes/ <<--location of theme profiles (layered on top of the base profile to apply themes)

/system/sd/overlayEnv/containers/ <<--location of container profiles (typically the last layer(s) that often provide commonality across profiles)

Example Setup:

Here is Wintermute' current configuration:

/system/sd/overlayEnv/bases/android2sd (you can make the dir structure and move the android2sd profileinto the bases dir(mv /system/sd/overlayEnv/android2sd /system/sd/overlayEnv/bases/))

/system/sd/overlayEnv/themes/ (currently 'empty'\\in development)

/system/sd/overlayEnv/containers/apps

What's Happening...:

When the profiles are loaded, 'android2sd' is overlaid on Android supplanting the base Android functionality with whatever is in the overlay.

Then any theme is overlaid on top to grant me the wonders of the selected theme.

And finally any specified containers are layered on top to grant unity to the overall profile, in this case the 'apps' profile is layered over /data/app and serves as global app-storage for any profile setup I conjure up.:D

Hope that helps!:D
[G1 Android Development] raznalab:
I got it working! This is an awesome idea and I like having the "safe mode" option it actually can in handy because I accidently wiped the data when I really meant to flash an update.zip. I am thinking of trying it out on ROM's other than JF1.51 US CRB43. I tried it on the ADP version of JF1.51 and it wasn't working out, but that was probably because of something I did.

One thing I did find out though is that for some reason, the profiles created by the buildnewA2SDProfile.sh script do not allow me to overlay the "apps" container. So what I'm doing is after I apply a theme, using the update.zip method, I would re-run the android2sd.sh which creates a new android2sd directory and then I would rename that and put it into the bases folder. Flash the ROM to clear the theme and repeat.

Thanks for helping me with this, I really appreciate it.
[G1 Android Development] Darkstrumn:
Maybe this can help make android2sd play well with app2sd...

Awesome; glad you got it to work!

It is likely the issue with overlaying the apps profile is that /data/app in the new rom is a symlink and not a dir; ie app2sd is installed as part of the rom.

(I know the formatting of the script will be jacked, but here goes)

Try updating the a2sdLoader.sh script with the following logic replacing the code between the

do

done;

of the Loading Container Profiles routine at the bottom of the script.

As far as the ADP rom, Android2sd will work on it as that was the ROM I originally built android2sd on. (I got the MyFaves option, but could only get the apk to work on the US ROM, but now the stk.apk complains on the US ROM... I will likely make a hybrid profile which allows me to use the apk's of both systems without issue.:))
[G1 Android Development] raznalab:
The ROM I was using is JF1.51 US CBR43 and I don't have app2sd setup, so that is not the issue unless the theme I applied through update.zip can somehow modify it to use app2sd. It works fine if I create the new base/profile by going through android2sd.sh, but if I create it through the buildNewA2SDProfile.sh than the overlaying of the apps profile fails. Not a big issue, but I thought I should make you aware that at least for me the buildNewA2SDProfile.sh is creating profiles that aren't allowing the use of the apps overlay. I will try the new scripting you posted and let you know the results.

UPDATE: I have found that overwriting the data folder of the base created by the buildNewA2SDProfile.sh script with the data folder from the android2sd base seems to solve the problem of not being able to apply the apps overlay. I have also tried to install android2sd on several different ROM's with no luck as JF1.51 is the only one that seems compatible. The ROM's I've tried have been JACHeroski 2.7.3, CyanogenMod 3.6.8.1, TMO's US OTA CRC1 + Root + App2sd etc., and Soulife's ION Remix (current). I would imagine it has to do with App2d.
[G1 Android Development] Darkstrumn:
You are correct. The overlay fails on the symlinks because they are not true directories.The newest revision handles that now, but the next revision is not yet ready for release.

I'm working on perfecting the overlays to handle roms that the teeter app detects as an 'htc' device, and those it does not. As well as some other theming issues (themes intended for other roms).

Hope to have this sorted soon!:)