yashsingh1/xdaforums huggingface dataset:
[Touch HD Themes and Apps] clpdj:
yap...(this CAB IT OOOOOOFFF) i have the same problem.... how can this be solved ? i need the portuguese XT9... but i cant get this to work.... any solution ??????????
[Touch HD Themes and Apps] hamkeng:
See if this file helps. It can be uninstalled if not.
[Touch HD Themes and Apps] clpdj:
thank's m8, but I had no luck :( ... still the same problem, when I turn on the XT9 i cant type nothing down (in "normal" mode i can)... thanks for the help m8
[Touch HD Themes and Apps] Txic:
Try this one! Works fine on the HD.

Czech

Danish

Dutch

Finnish

French

German

Greek

Italian

Norwegian

Polish

Portugese

Spanish

Swedish

EDIT: It was the same file as hamkeng. Sorry :)
[Touch HD Themes and Apps] pjp:
I'm using the cab below,download and instal, it works great on XannytechRom wwe,IooDa ptg rom and in MaryOne wwe rom,on flashmore wwe rom don't work.on others roms I haven't try.hope it helps
[Touch HD Themes and Apps] reidar.ostrem:
Anyone tried this on Energy 23541 ?
[Touch HD Themes and Apps] jenotc:
Would anyone have Russian?
[Touch HD Themes and Apps] HelderJr:
This cab works on Energy ROM 26 feb and makes my portuguese keyboard avaiable and functional! It has also other languages. I adivse making a backup before installing.

Good luck for all!
[Touch HD Themes and Apps] drakulinda:
t9

it didnt work for me, please help, how do i go back and uninstall it?

have Touch3G_WM65_2_33_721_32 installed...
[Touch HD Themes and Apps] bmw2320:
Any Indonesian language, please?
[Touch HD Themes and Apps] jalms:
Didn't work for me either.

I let's me choose Portuguese in XT9 options but whenever I press 6, it would be like if I'd press 9 (w,x,y,z), and if I press 5 it responds as if it was 6 (m,n,o), if I press 4 it'd be like 5 (j,k,l). Now how do I unistall it? Thanks!
[Touch HD Themes and Apps] Sir.Floyd:
Hello, any one knows where can I find a sms dictionary for my htc touch 2?

Thanks in advance
[myTouch 3G, Magic Android Development] neoxtian:
i am trying to install the driver for my mytouch.

when i plug in my phone for it to install the drivers, all the drivers install normally except for the adb driver.

this is the error message i get:

"C:\Windows\system32\wdfcoinstaller01005.dll is either not designed to run on Windows or it contains an error. try installing the program again using the original installation media or contact your system administrator or the software vendor for support."

i tried searching for this problem and found nothing, anyone out there have the same problem? it must be some issue with vista, ugh:mad::(:confused:
[myTouch 3G, Magic Android Development] neoxtian:
i also get this screen after it fails.
[XPERIA X1 ROM Development] Euroman28:
I have been in the middle for some time now to cook a Danish Language Rom for my Xperia X1 using WM6.5.1 and Rhodium OEM.

Since we lost the ability to have regional language pack after Da_G was contact by a guy claiming to be a Microsoft Internet Investigator. We lost these files.

I found a WM6.5 Rhodium danish Rom (The official one) and ran extracted a got packages out of it.

Then I thought I got the language pack that I needed. But then I try to compile the rom with the language pack from the HTC rom (WM6.5 build 21xxx) inserted in the SYS folder I get the error "tahombda.ttf" already exists" This error accurs do to something happening in the Base_lang_0406 folder I took from the HTC rom. Don't know what it is cause the folders and their contens are identical.

Any idears? Why SYSTEM_DEFAULT_FRONTS from build 23071 can conflict with Base_lang_0406 from build 21xxx?
[XPERIA X1 ROM Development] maddude88:
I know there's an issue with the danish language on some level, Itje has run in to it aswell with his multilanguage rom. I would ask him if i were you. Don't know much more, but I hope it helps :)
[XPERIA X1 ROM Development] Euroman28:
If I delete default fronts folder the rom build look like sh*t! But I will ask him thanks.
[Touch Pro2, Tilt 2 Windows Mobile General] indianinworld:
Supposing 2.1 GHz (2100 MHz) is allocated for 3G, how will 3G work..

Will it require another frequency slot such as 900 MHz to upload and use the existing 2100 MHz to Download data ???

or use the same 2100 MHz for all types of tranfers viz., both Upload and Download ???

Please Clarify...

Note

: My understanding is that it shall use the same frequency band to UPLOAD / DOWNLOAD Data as well....
[Touch Pro2, Tilt 2 Windows Mobile General] BrokenPixel:
Before your fingers get shot, type the subject on google and check the first link... that way you won't get the, use the search button excuse etc etc.
[Touch Pro2, Tilt 2 Windows Mobile General] indianinworld:
What is this anyway to do with my question anyway... and i didnt understand what you said in the above comment is another thing :D
[Touch Pro2, Tilt 2 Windows Mobile General] skyler17:
3G doesn't need a specific band like 2100MHz to work. Like most other wireless technologies, it can work with many different frequencies. However, carriers have certain bands licensed to them. Obviously they don't wan't to share the same frequencies because conflicts arise.

3rd Generation wireless technologies also don't need one wireless band for upstream, one for downstream... but separating the two makes each piece faster. Therefore carriers usually use HSDPA and HSUPA (3.5G wireless technologies) on different bands... like 900/2100.

But to answer the real butt of your question: no you can't get 3G on your device unless it is specifically designed to work for your 3G network provider. It doesn't matter if it supports only one of your carrier's frequencies, or even both of them (because there are sub-bands as well).

If you need a 3G device, buy it from your carrier or make sure that you know which exact carriers it is designed to work on.
[Touch Pro2, Tilt 2 Windows Mobile General] cookiemon:
I think you ask the wrong forum. :)

I will suggest you to google on the following:

WCDMA

HSDPA HSUPA

UMTS

This will give you a brief idea. If not, there are plenty of books and classes you can take... :)
[Touch Pro2, Tilt 2 Windows Mobile General] Entropy512:
Actually, each of the listed bands is typically listed into uplink and downlink allocations. I think for UMTS uplink is a bit below 2100, and downlink is above. It's been a while.

Either way, Google it.
[Touch Pro2, Tilt 2 Windows Mobile General] indianinworld:
Can you please answer my question instead of asking me to google... Google is not always an answer to everything at everypoint of time..

Thanks for this reply anyway !!!
[myTouch 3G, Magic General] BBNuno:
Hi!

Anyone can tell me how can I add options like "Phone Vibrate" to the menu on the image atached?

Regards
[G1 Android Development] sirocyl:
So I was using Slax. Great LiveCD/USB linux, extremely customizable, modular, fast, and small, and has the capability of either:

- saving changes to its rootfs onto an AUFS mounted on a non-linux FS (FAT32, NTFS) using posixovl (POSIX Overlay FS) with metadata (permissions, etc.) being held in files

- saving changes to a fixed-size loop mount image.

This got me thinking.

If we could insert all the necessary modules, code, etc. for posixovl into the Android linux, and make a modified a2sd script that takes advantage of posixovl, we could effectively do away with the requirement for crazy partitioning.

It should be simple enough for ROM devs to implement, assuming it's ready and installed:

1. Create folder on main partition if it doesn't exist, something like /sdcard/system/[app, app-private, dalvik-cache, app_s]

2. In the init scripts, before the a2sd stuff, mount /sdcard/system with posixovl on /system/sd

3. Run a2sd as normal, it should automatically just work.

I'll hopefully test this once I get my phone to a stable development/testing stage, and I don't need to make phone calls for a while. Anyone else is welcome to try to implement this idea.

My current test environment:

- HTC Dream (T-mo G1) with the deadly SPL of doom

- Cyanogen Experimental, latest build

- Amon_RA's modded recovery

- Wipe /data, move all existing apps to backup, remove a2sd partition, Backup for Root Users to restore some settings and data

Anyone with ideas or improvements, please let me know.

To be tested:

- Feasibility (can it work?)

- Functionality (does it work?)

- Portability (Can it work on other ROMs and devices like Hero, Pulse, Blur etc.? If so, will likely be moved to XDA's new Android board)

- Stability (Will everything Force Close on boot? Does it run fast enough? Does anything get corrupted over time?)

Links:

- http://sourceforge.net/projects/posixovl - Sourceforge page for posixovl
[G1 Android Development] Archont:
In desktop linux you can create a file with the touch command, and mount the file to a mountpoint after formatting it to ext4 for example.

Maybe this is the easier way?

I have done this about 5 years ago, but I will try it today and report if it worked.

edit: ok done already:

1. create a file of the desired size, eg: dd if=/dev/zero of=filename bs=filesize count=1

2. use mke2fs to format the file

3. create a mountpoint and mount the file

thats all. Now I have a 128MB file on my PC, mountable and usable like a partition.
[G1 Android Development] sirocyl:
As far as I know, you can do that on the mobile Android, too, and that does work in theory. This technique involves mounting a loop filesystem, and it too will allow one-partition apps2sd, but it's less flexible, and I would think slower, than the overlay method.

For a 512MB apps image:

Create empty 512MB file

# dd if=/dev/zero of=/sdcard/apps.img bs=1024k count=512

Format it to Ext2

# mke2fs -L Apps2SD /sdcard/apps.img

Unmount existing a2sd

# umount /system/sd

mount new a2sd image

# mount -t ext2 -o loop /sdcard/apps.img /system/sd

Make the usual directories, and a mountpoint for the old a2sd partition

# mkdir /system/sd/app; mkdir /system/sd/app-private; mkdir /system/sd/dalvik-cache; mkdir /system/sd/apps-tmp

Mount the old a2sd partition

# mount -t ext2 /dev/mmcblk0p2 /system/sd/apps-tmp/

Move all files from the old partition to the image file

# mv /system/sd/apps-tmp/* /system/sd/

Unmount and remove the mountpoint, we don't need it anymore

# umount /system/sd/apps-tmp

# rmdir /system/sd/apps-tmp

Finally, you add the following line to the init script where the a2sd auto mount happens, and comment out the old line.

[...]
mount -t ext2 -o loop /sdcard/apps.img /system/sd
#mount -t ext2 /dev/mmcblk0p2 /system/sd/
[...]

This should do what you described, in theory. I can't say whether it will work or not. I can't tell whether it will or won't screw up your phone, I can't be held responsible if you screw something up or overlook the details. Either of us might have made a typo somewhere; apply common sense before doing anything.
[G1 Android Development] lionx:
This sounds great! I think this would also be usefull for someone like me, who has a sd card that doesn't want to be partitioned anymore (cross-linked files??). Only thing possible is fat32 or ntfs.

Am I correct with my assumption?
[G1 Android Development] psychoace:
This sounds a lot harder and more complicated then partioning. Your also talking about a lot of work needing to be done just so people can avoid doing a simple thing like partioning a sd card. I would say it would be very difficult alone to get the os to run a virtual mounting service especially since that will take up resources and slow down the phone. There is a reason they only use this technique on live cds is it works but its slow. most of the computers they are running on have 1gig of ram and 2ghz cpu's. i really dont think the g1 can push this.
[G1 Android Development] Archont:
I do not think that this is great, it definitely is slower than a ext4 partition on a good class 6 microSD card. And it is more vulnerable to data loss since 2 different filesystems including a 20 year old non-journaling fs at the base of this construct are involved.

Another problem that came to my mind: when you mount your SD card as external USB device to a PC, the file containing your apps will no longer be accessible, or Android will make using the phone as external data storage impossible.
[G1 Android Development] lbcoder:
Interesting.

There is, however, a major problem: What happens when you unmount the fat partition on the phone in order to connect with a computer using UMS? Answer: everything on the phone will crash and burn since the apps filesystem will suddenly disappear = BAD.

posixovl is a nice find though...

Note that aufs, loopmount linux filesystems, etc., wouldn't be needed with this since posixovl appears to be vfat with posix extensions, so you should be able to just use posixovl directly on the sdcard.

There are several problems with that though... i.e. how reliable is posixovl regarding users tampering with it?

In any case, a prerequisite for use of it would be certain other changes being planned...

You might want to contribute to this thread:

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

(note: the thread links to a thread at android-platform, the one here has, as expected, gone off on a tangent... just ignore the junk.)
[G1 Android Development] sirocyl:
I kinda overlooked that point. Oops.

Though this same problem does exist on regular apps2sd when you remove the card without dismounting it, killing all apps and their processes, and freezing Dalvik's method of autostarting some apps.

I do tend to swap cards every now and then, but only after a reboot. Dalvik re-enumerates and caches dex, which makes for a slow boot, but it seems to just work in most cases that the apk install doesn't drop the app's functional payload (helper Linux/shell utils, libraries, NDK .so's) in /data/data (like some emulators, the Android Scripting Environment)

As far as I know, the metadata files are marked as hidden and system files, and begin with a '.'. And I haven't tried this, but I think modifying the actual files under Windows has no negative effects, but moving, deleting, or copying files would likely be a no-no.

Also, I don't think there's a 'fsck' for posixovl, meaning that if any metadata files were screwed with the wrong way, the entire overlay FS would be trashed.

I checked that out. It was actually a small inspiration for what I was thinking of.

In any case, Android's package management system needs an overhaul. The package storage needs to be de-Linuxified, as all it is is a bunch of .apk files and .dex/.odex files, the UIDs of apps are in the AndroidManifest.xml, right?

In a somewhat unrelated note, app data needs to be moved to a specified folder structure on the sdcard. My card is full of folders in the root directory with random names.
[G1 Android Development] MarcusMaximus04@gmail.com:
If I'm understanding you correctly, you're talking about storing an image file on the normal SD card partition(which has to be FAT32 as far as I've seen) and then mounting it, correct? This idea has been talked about at length before on at least 3 separate occasions(2 of which were on this very forum) and found to be a bad idea due primarily to massive security risks since FAT32 has no permissions.

Also, I believe cyanogen ended up dumping unionfs/aufs due to rampant memory issues.

If you are talking about mounting an image from the FAT32 partition, please don't endorse this. We don't want to be throwing in security bugs into android, especially ones such as this which can't be plugged up.

As a modification to what I said: If you're suggesting doing this(or something similar) on a separate filesystem, after that project to change the AOSP to support one with permissions is finished, then I'm in full support.
[G1 Android Development] Archont:
If you want to go for a single partition on the sd card, why don't you just make the entire card use ext4? Your linux desktop reads it anyway, it uses journaling and so on, I guess it would be faster compared to fat32 and it is definitely safer to use.

And i guess it is not too complicated to mount this partition and use it for pictures, music and so on.

I have not tried this (yet) and I go to bed in 20 minutes, but maybe I will start testing something in that direction tomorrow.
[G1 Android Development] sirocyl:
UNIX permissions don't do anything in the way of "security" unless you have no access to the actual storage device from another computer (as is the case with the unrooted Dream's internal memory), or unless encryption is used. The posixovl driver OVERLAYS Unix permissions over Fat32 filesystems. But even still, with Unix permissions, nothing's stopping someone else from mounting the Ext2 partition and using chown and chmod.

And the image file on the SD card's Fat32 partition is a complete Ext2 partition complete with Permissions. Nothing is lost.

We'd just have to find the part in the Android that mounts /sdcard/, and change 'vfat' to 'ext2'. The only reason I wouldn't do this, is because it would immediately make it incompatible with Windows and Mac's default FS drivers. As far as I know, the only FS's that are supported universally within Linux, Mac, and Windows, are FAT and NTFS. And NTFS can be made to have crude support for permissions through security descriptors. Although, the Dream SPL, the Recovery images, and most of Android only uses FAT32.
[G1 Android Development] cedricberger:
This is discussed in android-platform Group :

http://groups.google.com/group/andr...read/thread/bf0709c157451cd9/f6aee1830c84620f

The goal is to be able to integrate this in android.

And not having to partition the SDCard is one of the requirements so far...
[G1 Android Development] Archont:
Unix permissions are not stored using fat or vfat, and ntfs is not really supported in desktop linux and i guess it cannot be used in android linux.

I would not use windows anyway so this is no problem to me, and there are drivers around to mount ext systems in windows. As Mac OS is based on unix there will be a solution for this too.

Access usind adb push and pull, via ftp and so on is not touched by using ext4 on the entire sd card I guess.

And if you don't go the easy way using gparted on a live cd or usb device to create 2 partitions, you will have to live with some disadvantages anyway.

Finally I want to say that my ideas are far from being perfect or usable at all, I see this thread as a kind of brainstorming.
[G1 Android Development] rondey-:
im not as linux or android savvy as probably any of you but before the current method of creating a swap partition became the "standard", people used a swap file on the sdcard and linked that. seems similar to what you are suggesting here.

ofcourse when mounting the fat partition elsewhere (ums in windows for example) that swap file could no longer be used within android. i dont see a way to get passed the same issue, but worse here, due to android not having crucial apps when the fat partition is mounted.

then again, i am pretty much over my head in this conversation and could be over looking something...
[G1 Android Development] cyanogen:
I'm kind of fascinated by the FUSE + posixovl method of doing this. In the long run I have a feeling that it's going to perform like ****, but I think it's worth testing.

I managed to get both libfuse and mount.posixovl built and running on Android.

posix-overlay(/sdcard/fuse) on /sdcard/fuse type fuse.posixovl (rw,nosuid,user_id=0,group_id=0,default_permissions)

Giving this a little testing now, it definitely works.

/sdcard/fuse # ls -l
drwxr-xr-x 2 1000 1000 4096 Nov 5 17:17 test
[G1 Android Development] MarcusMaximus04@gmail.com:
Ya, I meant more from the standpoint of a rogue app. Since FAT32 has no permissions, what would prevent such an app from modifying the stored image file to, say, change a trusted app with superuser permissions to some new code of its own making to, for example, watch for credit card numbers and send them back to the person who made the original rogue app? I'm always hesitant with any ideas that suggest storing an image file on the sdcard for appstosd for this reason.
[G1 Android Development] cyanogen:
Forget it, it's useless.

An overlay filesystem prevents you from enabling USB storage.
[G1 Android Development] cyanogen:
If you want to play around with FUSE on Android, here's a repository for my port of libfuse..

http://github.com/cyanogen/android_external_fuse
[G1 Android Development] funbacon:
Hi,

I have an idea. I used symbian S60 of Nokia, Symbian can install app to sdcard. I see that when I mount sdcard to PC, my phone immediately hold all activations of all applications on my phone. And they have a PC sync software that help us access sdcard but not mount sdcard (like that we copy file from computer to sdcard via debug mode on android).

I think we should find out how symbian can do it and we will use their way :D.

I'm not a developer, I'm just an user.
[G1 Android Development] cyanogen:
I talked to a few people about this, and some deep kernel voodoo is going to be needed for this to really happen without partitioning.

Another idea is to forge ahead with this, and ditch the "unmount fs for usb storage" and use RNDIS + Samba or something like that instead to access files on SD. I kind of like this idea.
[myTouch 3G, Magic General] berre:
Hi guys,

I installed Taskiller to close background apps but my question is if this is really needed?

How does android handle background apps, do they really consume battery/memory?

Cheers

B
[myTouch 3G, Magic General] dekeijzer:
I have neverd used a task killer app. And I think my magic just flies!

I am using cyanogen though, he really makes slick roms.
[myTouch 3G, Magic General] phatmanxxl:
The OS automatically kills apps in the background when you open up new ones if the RAM is running low. You don't have to use a task killer, but most people say it helps the phone run faster and saves the battery.
[myTouch 3G, Magic General] phatmanxxl:
I went all day not using task manager, I didn't notice any difference in battery or performance on the phone. I guess thet aren't really needed after all. Its gonna take some getting used to not always checking and closing apps :D
[Touch Diamond2, Pure Themes and Apps] romano19:
now, I'm using TD2? I enjoyed the effect transition. Is there any solution for this idea?
[Touch Diamond2, Pure Themes and Apps] Gio512:
Excuse me, but what transition effect are you talking about?
[Touch Diamond2, Pure Themes and Apps] DaBountyHunter:
I'd like to know as well please... OT: Gio please reduce the size of your signiture it's way too large and just obscures quick browsing of this site whenever I come across it. Something a quarter of the size is big enough! Thanks.
[Touch Viva, MDA Basic General] Azzelio:
hi all

i need a botton on the home for locked my device, i have a standard version but it isen't finger frendly...

known you resolution for my problem?

sorry for my english...:mad:
[Touch Viva, MDA Basic General] TheRem:
update to WM6.5... it has a lock button on the start menu softkey bar.
[Touch Viva, MDA Basic General] Azzelio:
i have wm 6.5, but i want in the home ...not in start menu softkey bar. such as widget.. ...is it impossibile
[Touch Viva, MDA Basic General] eupendra:
I use Homescreen++, it puts the lock button on homescreen, of course apart from overclocking :-)
[Upgrading, Modifying and Unlocking] EclipseX:
I anyone try developer Rom with Touchflow 3d to omnia 2,like Topaz essensials
[Upgrading, Modifying and Unlocking] trebla:
Right now the no cook rom for Omina 2 for now only CFC Manila 1.3. Do watch out for this thread Manila 2.5 CFC might be on the way

http://www.modaco.com/content/i8000-omnia-ii-http-i8000-modaco-com/295162/touchflo3d/
[Touch Viva, MDA Basic ROM Development] xiaomouse:
anyone can answer me that htc touch viva can use the htc touch or touch 39's rom?
[Touch Viva, MDA Basic ROM Development] xiaomouse:
no ppl knowing?
[Touch Viva, MDA Basic ROM Development] jagan2:
I guess its not possible but it can be ported to our device i think.

I wish some one makes it true becoz in their forums lots of rom available
[Touch Viva, MDA Basic ROM Development] blackblooddeath:
not possible those phone got much better hardware than opal and so the roms made for them are more heavy than opal can manage

btw opal can manage those roms but ur phone would be very slow and battery life would be VERY low