yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] boazal:
Hi

i'm from the part of the world that uses in multi-language BIDI + RTL,

for us ICS is huge blessing.

therefore i tried "CM9/ICS for Droid 3" from:

http://xdaforums.com/show....php?t=1425026

and "XT860 Sub-Patch" from:

http://hash-of-codes.blogspot.com/p/...nloads_24.html

but... no data

after that i tried "Android 4.0.4[Beta #3]" from:

http://xdaforums.com/show....php?t=1497884

and "XT860 Sub-Patch"

but unfortunately, in both cases the same result NO DATA

(needless to i format, wipe data, cache dalvik and re-wipe all again and again)
[Motorola Droid 3] Rick#2:
You may need to make a few changes to your /system/build.prop file. Here's a copy of what I'm currently using; it is a pretty good base for you to test and see if it helps:

http://db.tt/2yWRAYg2

Try replacing your original build.prop with this one, again in /system. Let me know if this works!
[Motorola Droid 3] boazal:
its work,

ONLY if you leave the default APN settings (what come with the zip file) you can get Data,very slow connection but still you have it

if i try to set to my carrier settings, the data connection disappear...
[Motorola Droid 3] static416:
Worked well for me. CM9 seems pretty awesome. Far better than Liberty IMO.

Key detail: Make REALLY sure you have the correct version of Safestrap that he mentions in this post. I tried it with an older version and didn't have the "install from zip" under "Advanced". This led to another unrelated problem and I had to start all over.
[Motorola Droid 3] The-Captain:
I have the Verizon Droid 3, but your work was great on this. Nice work man!
[Motorola Droid 3] morcego.surf:
Work on xt860 Brasil

Amazing ! About the signal strength GSM.

I use the mod to working camera too.

http://www.grupoandroid.com/topic/72049-si-o-si-android-4x-para-nuestros-mm3-con-camara-on/

Thanks!
[HTC Wildfire S] meanmug:
I edited the icon and pull ring backgrounds on the Sense 3.0 Lockscreen. There are 3 flashable .zips to choose from: #1 no backgrounds at all, #2 no icons backgrounds with Sense style pull ring background, and #3 black ring with black ring icons background.

Credit goes to jikantaru for the black pull ring, found here http://xdaforums.com/showthread.php?t=1293119.

Tested and works on deodexed roms.(It may or may not work on stock odex roms.

USE AT YOUR OWN RISK

).

Instructions:

Flash zip in recovery.
[HTC Wildfire S] uruh:
thanx useful...
[HTC Wildfire S] Aef 101:
I like the look of your icons, what rom are you using?

Sent via Tapatalk
[HTC Wildfire S] meanmug:
I'm using m1ndh4x8r's rom with my custom theme from uot kitchen.
[HTC Wildfire S] Adam_J_T:
I know it's been a while, but the Aria is a similar phone to the Wildfire S, and I tried it on my Aria and it's not present. I'm running CM7.2. Any tips?
[HTC Wildfire S] loveVII:
Installed the black lockring. Looks sexy, but for some reason my ROM won't let me access the "Personalize" menu to adjust the shortcuts. Any idea what might cause this?

Using Simon's MarvelUSc Stock ROM 2.0
[HTC Wildfire S] Nightshadow931:
Dude, it's for sense.

Anyway, @op, your theme looks awesome, great job.
[HTC Wildfire S] davidang:
i love it
[HTC Wildfire S] mud_f1:
Nice. Im going to test if it works in stock rom.
[HTC Wildfire S] mud_f1:
It works in stock rooted rom
[HTC Wildfire S] Alaadragonfire:
I like the black one does it work with 3.5 sense ROM ?
[HTC Wildfire S] Alaadragonfire:
Well it didn't work well after you move the ring instead of showing "draw a pattern to unlock" numbers appeared :confused:

Restored ROM ;) thanks anyway!
[HTC Wildfire S] majkyman:
i really like the black one
[HTC Wildfire S] Relogeiro:
Hi everyone. I've got a problem... the customized lockscrn isn't work very we well... it's very very slow... If i would like to unlock my phone, i must waiting 2-4 seconz... Could you tell me where can I find an uncustomized lockscreen :confused:
[G2 and Desire Z Q&A, Help & Troubleshooting] Delta105RUS:
I was trying to change to DZ Hboot. I have the recovery installed, but no matter what i try to flash it won't get past HTC screen. this is getting frustrating

Edit: Fixed
[G2 and Desire Z Q&A, Help & Troubleshooting] OriginalGabriel:
What recovery and which version of it?
[G2 and Desire Z Q&A, Help & Troubleshooting] pven:
I had about the same problem. It was fixed by flashing to stock 1.34 by using hboot. After this I was able to install any ROM I like. :)
[G2 and Desire Z Q&A, Help & Troubleshooting] Barry://:
If your migrating from a differnt hboot and flashed a new one your phone will stay in the htc logo screen after the flash..just go the the pc and enter adb rebooot recovery and thier ull be redirected to the recovery
[Galaxy 3 Q&A, Help & Troubleshooting] dansager385:
why dont you migrate to newer soft as jpu or so there is no such extreme drainage
[Galaxy 3 Q&A, Help & Troubleshooting] deepash:
it happns wid the stock versions since there are no battery saving and other tweaks.u should switch to custom rom if u r really an internet frenzy :)
[Galaxy 3 Q&A, Help & Troubleshooting] dansager385:
people just dont know what they are missing on stocks and unrooted g3

cm7 is just a piece of beauty
[Galaxy 3 Q&A, Help & Troubleshooting] i_rnb:
it s ur battery !! had d same prob.. buy a new battery from ebay.. see hardware sec..

-tapatalked by rnb
[Galaxy 3 Accessories] M_247:
Hi all,

I'm on ddjp6 rooted.

Battery stand by is good.

But during using internet, fully charged battery expires in just 20 minutes or less...

The phone immediatly shuts down after showing low battery warning. (in 5 seconds)

Is this a rom problem?

Because I think on official eclair , the battery was good.

Can a custom rom solve this?

Please suggest me...

Thanks in advance...

With best regards...

:banghead::confused:
[Galaxy 3 Accessories] bioniclizard:
By internet you mean wifi or 3G? I have the same problem, just with mobile data, though. Don't know how to fix it... Anybody has a solution?
[Galaxy 3 Accessories] kipariss:
eats the battery on the definition of network towers ... are constantly sending requests to the network location to determine the location of the ...
[Galaxy 3 Accessories] artifex21:
Try battery calibration,if that doesn't work try flash some other ROm and finally if that doesn't work buy new battery.There's no other solution:D
[Galaxy 3 Accessories] mathias1xxX:
I use Indroid v6@1.3GHz ROM and my battery lasts quite a long time
[Galaxy 3 Accessories] srikanth.S:
Guys ,how much time the battery stands with mobile data on.. i.e, on edge network
[Galaxy 3 Accessories] cs_k:
Battery Problem

I am also facing the same problem ,while using internet, fully charged battery expires in just 20 minutes or less...

The phone immediatly shuts down after showing low battery warning. Please suggest any solution.
[Galaxy 3 Accessories] ghpk:
How old is your battery ?

This may be indication of battery is about to get worse and die

During stand-by battery doesn't needs much power so it sustains standby.

A new battery should be around 500/599INR. at samsung service center.
[Galaxy 3 Accessories] VAMGDroidFan:
My battery is 20 months old, but still lasts for 3-4 days easily. :):):D

I'm using Custom OC ROM.

Drain battery to "0" and charge it continuously for 3-4 hours, keeping phone switched off. Do this once a month. This fixes problem.

If u've rooted then do battery calibration...
[Galaxy 3 Accessories] klncdc:
Hello,

My battery expires in one day with 3G only activate... If you want to use 3G all the time like me,'re trying to install a firewall (avast mobile for example) to choose only the apps that need to communicate on the internet... Thank you for keeping me informed...
[Galaxy 3 Accessories] cs_k:
Please Let us know which ROM u r using?

I am using Kyrillos 10.5. Is there any other ROM where the battery is much stable.

---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------

Yeah I am planning to change my battery.I hope the new one will give better Battery life. Can u suggest me any good battery? Is there any other alternate battery or is it advisable to take at samsung service center.
[Gen9 Android Development] gen_scheisskopf:
Hi

Archos G9 devices are quite new so we should create some developement guidelines/standards to avoid total mess.

This thread is meant to be the place to create those, feel free to contribute.

1. Firmware file name- archos.ext4/squashfs/img

as propposed by letama (source) and agreed by suduru_petru (source)

2. Firmware updating

letama in his builds added a mechanism to painlessly update system image: new image is called [...].update, kernel initrd deletes "old" file and renames new one- there is no need to boot or install stock firmware.

My opinion- this should be the standard but subject is to be discussed

However updating/downgrading firmware may cause problems so-

3. Recovering from problems (bootloop, FC's etc)

This subject is to be discussed.

Archos G9 has specific system structure and "non-standard" Recovery. For now the only way to fix app FC's or a bootloop is to wipe data (Reset Android option in recovery) but this deletes all system data. Better solution is to wipe dalvik-cache- this deletes some files used by system but they are rebuilt during boot- but there is no way to do it now.

After talking with letama we've come to an idea: kernel init looks for .update files and

-if it's archos.ext4/squashfs/img.update kernel updates system image

-if it has another but predefined name- .update file is a shell script that is executed

This would give us a substitute for a "standard" recovery. Best way would be to use external SD-card for this task but first we have to check if there are any problematic cards (seems that letama has such card)

Please post your opinions/ideas/suggestions but keep in mind that this is not a system/app feature request topic

And if you have a better idea for the topic title- let me know
[Gen9 Android Development] gen_scheisskopf:
My idea how .update files should be handled:

during boot check if external sd card is present

1)yes- check for .update files

a)archos.[...].update present- delete current system image from /data/media, copy new one, delete archos.[...].update files from card AND from /data/media

b) .update script file present- run script, delete script .update from sd AND /data/media

2) no- check /data/media for .update files

a)archos.[...].update- delete current system image, rename update file

b).update script- run script and delete .update file

Notes:

-both types of .update files should be handled if found- when updating firmware wiping dalvik-cache (rm -r -f /data/dalvik-cache) is always advised and this can be done using a script since we don't have a "standard" recovery

-using external sd as the first choice- if adb can't be accessed (no PC, no USB cable, bootloop etc) there is no way to access internal storage
[Gen9 Android Development] surdu_petru:
First...Thanks @gen_scheisskopf for your idea....ofcourse is very important for us to have a standard "language".....and you are rigt ( is also my opinion ) - is very unpleasant to take it from zero for an future update or custom rom , considering that many users have installed many custom applications ( games, contacts-data, calendar-data and other personalizated-data....or other stuff).

I hope that together , we'll found the right way for this inconvenience ......and what you began is a necessary and welcome environment to improve programming and use.

Without portability not succeed to have its own development !

I hope in a close collaboration among you especially as you have one of the best developers (Thanks @LeTama) .. but I hope to help us and other developers ....See you soon ! and you started a great job anyway ! :D
[Gen9 Android Development] gen_scheisskopf:
Problems like bootloop or FC's can occur even if firmware wasn't changed but there is no *easy* way to fix this yet- so we should make one :)

One more thing from my side- system@ext4 image should be mounted RO by default:

-system RO is a standard (also in official firmware)

-nobody can do any harm to system by accident- any changes will require remounting RW first and no app does this by itself

-all root apps that can make changes to system (TitaniumBackup, RootExplorer, Abslute Root Tools, SUFBS etc) will function properly for remounting RO/RW
[Gen9 Android Development] letama:
Agreed, it would be nice. However, Archos has not the android standard way of managing partitions, they don't mount a /system partition on top of initrd , they mount a root partition that contains a system directory and chroot it. In short, we mount /dev/loop0 on /new-sys then chroot /new-sys, we don't /dev/block/mmcblkp1 on /system.

More, /dev/loop0 is becoming /dev/block/loop0 when android is booted, so it's a bit tricky to remount r/w after that. I think most root applications are confused with this layout and can't remount properly, that's why I left default to r/w in my build.

It would be good to test it a bit more with few root apps to see if some are working, I didn't do much tests.
[Gen9 Android Development] gen_scheisskopf:
I understand.

How about "ln -s /dev/block/loop0 /"? This can be done in init.rc (both kernel initrd and in system image init), not sure if this will work properly

Another idea about .update files- possibly safer way would be to add a predefined set of scripts to initrd- like it's done in recovery- and to use .update files with a different names (like wipe-dalivik.update).
[Gen9 Android Development] gen_scheisskopf:
TitaniumBackup has problems with integrating updated apps into rom- device rebooted during Maps.apk processing (2nd of 4) and now Market is missing from /system/app

Can't say however what caused this- system img file location (loop0) or RW by default. Ext4 is not the cause, I've used ext2 and ext4 for /system on the other device before and there was no problem.

EDIT:

TB restored Market from backup straight to /system/app and it seems that manual integration works fine. Maybe that was just a system error.
[Gen9 Android Development] gen_scheisskopf:
Dalvik-cache wipe in init:

# Do updates if need

if [ -e /data/media/archos.ext4.update ] ; then
rm /data/media/archos.ext4
mv /data/media/archos.ext4.update /data/media/archos.ext4
[B]rm -r /data/dalvik-cache[/B]
fi

if [ -e /data/media/archos.squashfs.update ] ; then
rm /data/media/archos.squashfs
mv /data/media/archos.squashfs.update /data/media/archos.squashfs
[B]rm -r /data/dalvik-cache[/B]
fi

[B]if [ -e /data/media/wipe-dalvik.update ] ; then
rm -r /data/dalvik-cache
rm /data/media/wipe-dalvik.update
fi[/B]

-when archos.ext4/squashfs.update file is found dalvik-cache wipe is mandatory

-file /data/media/wipe-dalvik.update also triggers wipe (and dalvik-wipe.update file is removed

Tested, works fine :)
[Gen9 Android Development] surdu_petru:
Thanks...good job ! ;)
[Gen9 Android Development] gen_scheisskopf:
Another test, possibly will work for HDD models:

mount_p data
mount_p storage_`$GET_INFO p` #this should return product name and use correct storage mountpoint

#Check if system image is present, if not- copy from storage
if [ ! -e /data/local/archos.ext4 ] ; then
cp /mnt/storage/archos.ext4.update /data/local/archos.ext4
fi

# Do updates if need

if [ -e /mnt/storge/archos.ext4.update ] && [ -e /mnt/storage/system.update] ; then
rm /data/local/archos.ext4
cp /mnt/storage/archos.ext4.update /data/local/archos.ext4
rm /mnt/storage/system.update
rm -r /data/dalvik-cache
fi

if [ -e /mnt/storage/archos.squashfs.update ] && [ -e /mnt/storage/system.update ] ; then
rm /data/local/archos.squashfs
cp /mnt/storage/archos.squashfs.update /data/local/archos.squashfs
rm /mnt/storage/system.update
rm -r /data/dalvik-cache
fi

if [ -e /mnt/storage/wipe-dalvik.update ] ; then
rm -r /data/dalvik-cache
rm /storage/wipe-dalvik.update
fi

umount_p storage_`$GET_INFO p`

# Now boot
if [ -e /data/local/archos.ext4 ] ; then
$LOSETUP `get_mount_info d rfsext4` /data/local/archos.ext4 || log_and_die "Mounting system partition failed"
mount_p rfsext4 || log_and_reboot "Mounting system partition failed"
umount_p rawfs
rootfs_path=`get_mount_info p rfsext4`
umount_pseudo_fs
log "SWITCHING TO REAL ROOT"
exec switch_root $rootfs_path /init
fi

$LOSETUP `get_mount_info d rootfs` /data/loacl/archos.squashfs || log_and_die "Mounting system partition failed"

mount_p rootfs || log_and_reboot "Mounting system partition failed"

umount_p rawfs

rootfs_path=`get_mount_info p rootfs`

umount_pseudo_fs

log "SWITCHING TO REAL ROOT"
exec switch_root $rootfs_path /init

Changes

-system image file is mounted from /data/local (not /data/media)

-archos.ext4.update file is preserved on storage (/data/media or hdd) in case of data wipe- init copies it to the right place if file is not present

-updating firmware requires two files- archos.ext4.update and system.update- second one is an empty file, it is removed after system update (archos.ext4.update is not removed)

-I did not add checking for archos.squashfs file

Prequisites

-minimum 512 MB free on /data for hdd models- they have much smaller /data- about 1.5GB

This works fine on 16GB model- file is copied without any problem and possibly will work on HDD models too- I've sent test version to philmein (he was willing to test)

Android does not touch /data/local/archos.ext4 file (/data/local belongs to shell, not system so it's a safe place)

Other thoughts:

-maybe we drop archos.squashfs support?

-archos.ext4 can be made smaller- 191 MB is free so 400 MB should be more than enough

-maybe add mounting official system file (.squashfs.secure) if there is no custom one present and no archos.ext4.update on storage?

-other possible location can be /data/customization but I didn't test it
[Gen9 Android Development] surdu_petru:
Hi @gen_scheisskopf...

I think ( not sure ...) , that until we find a way for mount proper HDD into initramfs , we can't load any files system ( .ext4, .squashfs, .update ) for Archos HDD !

Your test it's work great because for flash 8/16G , @letama modified initramfs

for mounting (.ext4, .squashfs ) -proper !

I believe the solution to root version Archos HDD,is just find a solution to change something in initramfs for a proper mount , after that I do not think it matters where you are place the files system ( /data/media, /data/local , /data/customization - is the same way )

Still believe that /data/media was not chosen at random - when we connect the tablet to the computer we see just Internal Storage ( ..or + SD Card), which is equal to /data/media/....you don't need root, you don't need any other app for look into Internal Storage....
[Gen9 Android Development] gen_scheisskopf:
All proper mountpoints are stored in /etc/mountpoints- init reads device name and uses correct mount. The only thing that possibly can be required is

wait_blk_device storage_$DEVICENAME

(I'm not sure if it's wait_blk_device, will check)

Problem is that after android boots all mountpoints change.

Using /data/media may not work- on HDD there may be problems with mounts if /data/media belongs to hdd.

I've chosen /data/local not by mistake:

-android does not touch files placed there (as they may be vendor specific)

-/data/local is chmoded to shell while most of other /data folders are chmoded to root

-running system form HDD may decrease battery life greatly while /data/local is for sure flash memory

-modified initrd check for required files/updates on storage (/mnt/storage) and does not delete possibly necessary archos.ext4.update file (in case of data wipe) so copying those files doesn't change at all- just drag'n'drop on PC
[Gen9 Android Development] gen_scheisskopf:
It seems that modified init works for HDD models but more tests are required: http://xdaforums.com/showpost.php?p=22309411&postcount=72

Modified part of init:

mount_p data
mount_p storage

#Check if system image is present, if not- copy from storage
if [ ! -e /data/local/archos.ext4 ] && [ ! -e /mnt/storage/archos.ext4.update] ; then
cp /mnt/storage/archos.ext4.backup /data/local/archos.ext4
rm -r /data/dalvik-cache
fi

# Do updates if need

if [ -e /mnt/storage/archos.ext4.update ] ; then
rm /data/local/archos.ext4
cp /mnt/storage/archos.ext4.update /data/local/archos.ext4
mv /mnt/storage/archos.ext4.update /mnt/storage/archos.ext4.backup
rm -r /data/dalvik-cache
fi

if [ -e /mnt/sdcard/wipe-dalvik.update ] ; then
rm -r /data/dalvik-cache
rm /mnt/sdcard/wipe-dalvik.update
fi

umount_p storage

# Now boot
if [ -e /data/local/archos.ext4 ] ; then
$LOSETUP `get_mount_info d rfsext4` /data/local/archos.ext4 || log_and_die "Mounting system partition failed"
mount_p rfsext4 || log_and_reboot "Mounting system partition failed"
umount_p rawfs
rootfs_path=`get_mount_info p rfsext4`
umount_pseudo_fs
log "SWITCHING TO REAL ROOT"
exec switch_root $rootfs_path /init
fi

$LOSETUP `get_mount_info d rootfs` /data/local/archos.squashfs || log_and_die "Mounting system partition failed"

mount_p rootfs || log_and_reboot "Mounting system partition failed"

umount_p rawfs

rootfs_path=`get_mount_info p rootfs`

umount_pseudo_fs

log "SWITCHING TO REAL ROOT"
exec switch_root $rootfs_path /init

Changes:

-support only for archos.ext4

-after update a backup file is created in case of data wipe (archos.ext4.backup)

Works on flash model, to be tested on HDD models:

http://dl.dropbox.com/u/14106051/archos/kernel_hdd_test7.zip

EDIT:

As it was just reported- G9 80 HDD does not have SD card slot so earlier idea to use external SD has to be dropped.
[Gen9 Android Development] gen_scheisskopf:
Backup & restore of archos.ext4 without wiping data (in case something went wrong with merging changes into the system).

#backup & restore of system image

if [ -e /mnt/storage/backup.update ] ; then
rm /mnt/storage/archos.ext4.backup
cp /data/local/archos.ext4 /mnt/storage/archos.ext4.backup
fi

if [ -e /mnt/storage/restore.update ] ; then
rm /data/local/archos.ext4
cp /mnt/storage/archos.ext4.backup /data/local/archos.ext4
rm -r /data/dalvik-cache
fi

umount_p storage[...]
[Galaxy S I9000 Q&A, Help & Troubleshooting] H83:
Hi everyone.

I have the teamhacksung's ICS rom (build 14) that I have installed above the onecosmic's rom.

I would like to know how I sould proceed to install THIS new kernel.

Should I just have to flash the zip in recovery mode?

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] rahimhn:
If you are flashing from another rom.

1. Reboot into recovery using button combos.

2. Flash RC3.1.

3. Reboot into recovery, wipe data / factory reset.

4. Wipe cache.

5. (optional) flash new kernel

6. Reboot.

If you are upgrading from an earlier build.

1. Flash the newest build in CWM.

If you have rebooted and your phone will not go past the kernel screen.

1. Boot into CWM and wipe data/factory reset and wipe cache partition.

2. Reflash the appropriate kernel.

3. Reboot.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ottili81:
If u just want to flash a new Kernel, it's not neccessary to reflash the whole ROM. Put the Kernels ZIP into internal SD-Card, go to CWM via boot or 3-Button-Combo, head to the zip-file and install it.

It could be useful, to flash the Kernel-cleaning-script that u will find here:

http://xdaforums.com/showpost.php?p=13224453
[Samsung Galaxy Nexus] Janzomaster:
Hi there,

I noticed that the backups made with CWM are quite big, and if I compress them on my computer using 7zip, they lose about half their size.

Is there any way to get CWM to increase the compression it uses?
[Galaxy S I9000 Q&A, Help & Troubleshooting] komir:
hello guys,

I installed latest Saurom jvu and in SMS app didn't find checkbox for delivery report for text SMS (for MMS there is checkbox), so I`m not getting delivery reports!is it possible to activate somehow? Do i need to install third party SMS app (GO SMS, PANSI ot something...) to enable it?:confused:
[Galaxy S I9000 Q&A, Help & Troubleshooting] lirik0:
The truth is I don't see that option, the application mms.apk of jvu Saurom is AOSP 2.3.7. you can put the original jvu 2.3.6 in system/app
[Galaxy S I9000 Q&A, Help & Troubleshooting] komir:
ok, thanks for information, I`ll try to put stock mms.apk in rom. Maybe you should note that on official Saurom thread...