Database Develop

Compass and Accel sensors not working, Please Help!

I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.

gigawatts said:
I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.
Click to expand...
Click to collapse
I think your using the pre-cupcake apps. Did u download the apps after you updated or did you install them from a back up?
Best way to check, You should got to settings and then sounds&display and check off orientation. You phone should switch from portrait to landscape when you rotate any program (except homescreen). If that works then nothing is wrong with your phone. If it doesn't then something happened somewhere weird

any apps i have installed have been after i flashed a rom (after a wipe) and not from a backup. Plus, something as simple as Google Maps or the Browser App should just rotate without opening the keyboard.
Best way to check, You should got to settings and then sounds&display and check off orientation.
Click to expand...
Click to collapse
By that I assume you place the check mark (lit green) next to the option, not "check it off" (not lit green). I have tried both checked and unchecked in pre-installed apps like maps and browser, and still nothing.

Small update. I just flashed JF's v1.43_RC33 with root, keeping the same more recent radio, and both sensors work there, as they do in RC29. It seems to be ONLY cupcake based roms where they don't work.
Any other suggestions anyone has for me? I might try a hero build next, to see if they work there, but I'm not sure how stable they are yet.
Any help/suggestions would be greatly appreciated!

Accelerometer fix
http://forum.xda-developers.com/showpost.php?p=4081673&postcount=4885

I tried your suggestion, and it did not work. Unlike the other user reporting that the sensors would work for a short time after reflashing, mine has never worked after a cupcake flash. Only after a pre-cupcake flash.
Although ideas like that are what I am looking for, possible corrupt config files that need to be cleared or maybe a mod probe command of some sort to activate or wake up the sensors.

Upon some more inspection, I get the feeling something is wrong with my akmd process, or whatever executable generates the akmd_set.txt compass and accelerometer calibration data. I tried to follow some instuctions to purge the akmd_set.txt file to clear any bad config, but the file is no where to be found. My phone doesnt seem to generate one at all when it's booting.
The akmd process does remain running in the background, as here is its ps output:
Code:
# ps | grep akmd
compass 77 1 1320 328 c020d268 afe0c45c S /system/bin/akmd
This is the output I get from logcat when I try to manually run the /system/bin/akmd process or when it restarts automatically after being killed:
Code:
D/AKMD ( 362): akmd 1.6.4 START
D/AKMD ( 362): library version: 1.2.1.1129
D/AKMD ( 362): Compass OPEN
D/AKMD ( 362): No calibration data
D/AKMD ( 362): Can not initial compass parameters error: -5
and this is the output I get when I run a program like Orienteer:
Code:
I/ActivityManager( 90): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.deafcode.android.Orienteer/com.deafcode.android.Orienteer.Orienteer} }
I/ActivityManager( 90): Start proc com.deafcode.android.Orienteer for activity com.deafcode.android.Orienteer/.Orienteer: pid=363 uid=10041 gids={}
D/SensorManager( 363): found sensor: AK8976A 3-axis Accelerometer, handle=0
D/SensorManager( 363): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1
D/SensorManager( 363): found sensor: AK8976A Orientation sensor, handle=2
D/SensorManager( 363): found sensor: AK8976A Temperature sensor, handle=3
D/dalvikvm( 363): GC freed 920 objects / 64320 bytes in 92ms
D/LocationManager( 363): Constructor: service = [email protected]
D/Sensors ( 90): sensors=00000005, real=00000005
D/GpsLocationProvider( 90): setMinTime 2000
W/IInputConnectionWrapper( 145): showStatusIcon on inactive InputConnection
I/ActivityManager( 90): Displayed activity com.deafcode.android.Orienteer/.Orienteer: 1313 ms
D/dalvikvm( 145): GC freed 795 objects / 45896 bytes in 165ms
D/GpsLocationProvider( 90): TTFF: 7203
Maybe this will give someone some more insight as to the problem I am having.

hello,
i me french and i have the same problem.
No akmd_set.txt on my phone.
If you are a solution could you partage it ?
I think it's a driver problem but i'm not sure.
JEEP

Unfortuantly I have still not found a solution, but continue to look for one. I will let you know here if I do manage to solve it.

I am also having the same problem. Wiping does not fix it and the method stated by Cyanogen didn't work either. I don't know if this will be any help, but I do know the accelerometer issue started about 3 or 4 days ago for me. Maybe if I list things I've done to my phone in the last few days, it might help narrow down the cause if others with the same issue compare their experiences to each other.
I have a US T-Mobile G1 and I have been rooted since February. Since that time I have upgraded to (and currently use) the latest radio from HTC, Haykuro's SPL, and a class 6 4gb card. I've also been through more roms than I can count in that time, all without an accelerometer issue till now.
Now that I've got all that out of the way here's the more relevant stuff:
Within the last week I have upgraded to Cyanogen's 1.3.1 recovery boot and installed the latest JAC Hero build. I repartitioned my card into 3 partitions with the directions given in JustAnotherCrowd's thread using parted in the recovery's console.
Code:
#parted /dev/block/mmcblk0
rm 1
rm 2
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
This is the first time I've ever used apps to sd. After using that rom for about a day, I switched to Cyanogen's build and wiped my user data without wiping the ext partition of my sd card and I continued to use the swap partition on my Cyanogen build. I'm fairly sure but not 100% certain that the accelerometer was still working at this point. Soon after installing this rom, Cyanogen released an update including the compcache modules to replace the linux-swap setup. I installed the custom userinit.sh script to system/sd to activate compcache. Then Cyanogen released another update (immediate bug fixes) almost as soon as I got this rom working. I flashed the update.zip, but then it started to boot loop. I wiped the phone (not the ext partition), still boot looped. I took out the sd, still boot looped. I put the sd card back in wiped again, reflashed, and then clicked "repair ext file system". STILL BOOT LOOPED! (Don't say I just wasn't giving it enough time to boot because I acctually watched the boot animation flicker in and out for a second and start over.) Next, I used fastboot to restore only the user data from a nandroid backup of an older Cyanogen rom. This time it worked. Next, I installed the audio resources to system/sd/media and linked them using the userinit.sh file. The next day, I realized that the accelerometer was no longer functioning.
I hope this description helps to figure this out.

I'm having the exact same issue.

testing567, can you post the userinit.sh file you are currently using, and possibly you or someone else post their userinit.sh of a phone with a working accelerometer and compass here?
I am thinking that one of my init scripts may not be calling the akmd service properly, as in not with the correct permissions or something, and thus not calibrating itself on boot. I was planning on upgrading to the latest cyanogen update today, as i am running 3.6.5 right now. I was also considering upgrading my SPL to a dev SPL so i can use nandroid to backup (getting a little tired of loosing everything when attempting different roms to fix this issue).

I got my userinit.sh from this post.
http://forum.xda-developers.com/showpost.php?p=4140826&postcount=74
I also decided to take advantage of the media symlinking already in this script and pushed the audio resources to system/sd/media/.

I've always had the same issue when upgrading to a cupcake based rom. Nobody else until recently seemed to share my misfortune (sorry for everyone else). There is an exception though, JF 1.5 (T-Mobile) build the sensors work (although miscalibrated). I haven't found any other solutions or any other way to generate the settings file. My process output appears to be the exact same as you've posted.
I'll keep trying some things but I just want to keep this alive incase anyone else needs a fix and one of us comes up with a solution.

RemoteDJ, I may actually have a solution to your miscalibrated problem. In the process of going through and trying to get my sensors working, I created an empty akmd_set.txt file with chmod 777 permissions (just so it wouldnt ***** about some user permissions when trying to edit it), and then rebooted the phone. Upon looking at the file after reboot, it was filled with calibration data.
Although this has not fixed my problem, it may help you. Also, the application "Bubble" has a calibrate sensors menu option, which may help you too. I may have to try reverting back to JF 1.5 to see if I have better luck there. Was that JF 1.51 you were using? If not, please advise.

Yes it was JF 1.51, it's funny because I just got done making a blank chmod 777 akmd_set.txt lol. Of course i'm on the latest stable cm-3.6.8.1 currently and the sensor doesn't work at all.
Just so we stay up to date with each others findings, I also pulled the akmd app from Haykuro's ION, JF 1.43, JF 1.51, Official RC33 and the current CM build. I have only tried replacing the current one with the ION app (in recovery), so far no change, but I think the only file difference I noticed out of the files I pulled was that the JF 1.43 and Official RC33 seemd to be the same (haven't hashed them to verify) and different then the others which seem to be the same but since I haven't hashed any of them to verify yet I can't say for sure.
I am calling it a night right now but will let you know if I find anything tomorrow.
Just a followup with the hash info.. looks like I was correct:
517a87a4e6caa5e66f0520c68dcb7c0e - Official RC33
517a87a4e6caa5e66f0520c68dcb7c0e - JF 1.43
c3a80124ab072f9bf12cc9e4155a0f9f - JF 1.51
c3a80124ab072f9bf12cc9e4155a0f9f - ION
c3a80124ab072f9bf12cc9e4155a0f9f - CM 3.6.8.1
Another Edit: I am apparently not good at going to sleep.. Good News! (semi).
I left the akmd_set.txt in place (it got filled with data just like yours)
replaced ion/cm akmd with jf 1.43 and now the sensor appears to be working (although still miscalibrated for me, this might be a hardware issue.. lots of drops).
step by step.
copy jf1.43 akmd to sdcard (i just pulled it out of the update zip).
reboot recovery
mount /system
rm /system/bin/akmd
mount /sdcard
cp /sdcard/jf1.43_akmd /system/bin/akmd
then umount (probably not required)
reboot.
It still didn't work, but I deleted the akmd_set.txt via adb and then rebooted and voila!
Let me know if any of that works for you
Edit: I was able to fix my calibration by reverting to the rc30 akmd, I have absolutely no idea why my device is so picky, but it only has ever had correct calibration with accelerometer on the rc29/30 builds (this includes all official t-mobile ota releases). Anyway just wanted to through that out there incase anyone else uses the jf1.43 and is miscalibrated.

RemoteDJ,
Thank you so much for that suggestion! That totally worked for me! I flashed cm-3.6.8.1 tonight and replaced its /system/bin/akmd binary with the one from jf 1.42. After messing around with some permissions (I failed to realize the akmd binary was not set as executable when i moved it over ) i was able to create a blank akmd_set.txt, chmod 777 it, and then restart the akmd service (stop akmd, followed by start akmd).
I can not thank you enough for this suggestion! Guess it just took another similar brain bashing away at the same problem to solve it. I just wonder why this is not a problem for a lot of other people out there. It's the same hardware, so you would think everyone upgrading to cupcake would have an incompatible akmd binary. Strange...

Sweet, I'm really glad it worked for you!
I can't imagine for the life of me why other people don't have similar problems, but then again I've had a few problems that seemed indivualized to my device lol. Its only recently that I discovered a few other people were having problems with the accelerometor.
Oh well, all in all just glad this worked.
Maybe we can get Cyanogen to include this in his FAQ as an alternative for sensor repair for the people like us. I might reply on the latest build thread later, anyway have a good one.

So far I haven't had any luck with this. I'm actually tempted to send my unit back to HTC with the ota 1.5 cupcake on it and see what happens. I'm not sure if it was working when they sent it to me or not. It doeswork with the rc29 though.

I'm having the same issue, no compass apps seem to work, google sky maps doesn't work , the level app doesn't work, all are froze.
How can I fix it?

[Help, please] GTalk won't sign in

This comes up first in my log:
com.google.android.apps.gtalkservice has no signatures that match those in shared user com.google.uid.shared
Then:
Unable to start service Intent { cmp=com.google.android.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService }: not found
I've tried clearing dalvik-cache, pushing gtalkservice.apk to system/app/, fix_permissions from Terminal Emulator and Console (recovery mode), Later: reflashed the ROM, reflashed the theme, flashed another theme. Still no go.
Later: Wiped, reflashed ROM. Still getting the signature error.
I was running Dragon theme for CM 4.2.11.1 , with Enoch's Advanced Launcher (also for CM 4.2.11.1), and the 10mb ROM Hack. I can't imagine that these things would affect gtalk service, or have an effect on uid signatures, although I'd think the latter is more likely.
There are a few things that are dependent on this, like downloading from Market.

I had a similar problem yesterday, where I kept getting a crash when I would open up GTalk. Then I wasn't able to download any apps from the Market, it would give me a gapps.com error. I was on 4.2.11.1, so I downgraded to 4.2.9.1, and everything worked, then updated back to 4.2.11.1, and don't have any of those problems anymore.
Before I downgraded, I had done a wipe, reinstalled the 4.2.11.1 rom, cleared my ext2 partition, and none did the job.

Janis said:
This comes up first in my log:
com.google.android.apps.gtalkservice has no signatures that match those in shared user com.google.uid.shared
Then:
Unable to start service Intent { cmp=com.google.android.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService }: not found
I've tried clearing dalvik-cache, pushing gtalkservice.apk to system/app/, fix_permissions from Terminal Emulator and Console (recovery mode), Later: reflashed the ROM, reflashed the theme, flashed another theme. Still no go.
Later: Wiped, reflashed ROM. Still getting the signature error.
I was running Dragon theme for CM 4.2.11.1 , with Enoch's Advanced Launcher (also for CM 4.2.11.1), and the 10mb ROM Hack. I can't imagine that these things would affect gtalk service, or have an effect on uid signatures, although I'd think the latter is more likely.
There are a few things that are dependent on this, like downloading from Market.
Click to expand...
Click to collapse
Did you try wiping the data from the Google Talk app and service? That might force you to log in again, and may clear your service launch and intent issue. Just a guess. If you did a full wipe, it would also clear these (as indicated by having to log in again).

I fixed it
I traced it to The Dragon theme for 4.2.11.1 by going back to the CM defanged (I almost said toothless) base, reflashing 1.4 recovery image, wiping, flashing the radio, and flashing 4.2.11.1, then trying various themes, watching the log every time. The 1st time I got these:
Code:
12-29: WARN/ActivityManager(154): Unable to start service Intent { cmp=com.google.android.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService }: not found
Code:
12-29: ERROR/PackageManager(154): Package com.google.android.apps.gtalkservice has no signatures that match those in shared user com.google.uid.shared; ignoring!
was when I flashed the Dragon theme.

Cannot install K9 after installing ROM, help!

Last night I installed Enom's 2.11.3 ROM, GApps, and a blackbar circle battery theme (just the notification bar, not a system wide theme kind of thing). I also moved dalvik cache to /cache and enabled old style apps2sd.
Reinstalling apps, most worked fine, but several failed, and most importantly, K9 Mail won't reinstall.
When I try to install from the phone (from card, Market, etc) logcat has the following:
D/PackageManager( 486): Scanning package com.fsck.k9
I/PackageManager( 486): /data/app/com.fsck.k9-1.apk changed; unpacking
D/installd( 468): DexInv: --- BEGIN '/data/app/com.fsck.k9-1.apk' ---
W/dalvikvm( 1377): partial write in inflate (8152 vs 32768)
W/dalvikvm( 1377): DexOptZ: extraction of classes.dex from /data/app/com.fsck.k9-1.apk failed
W/installd( 468): DexInv: --- END '/data/app/com.fsck.k9-1.apk' --- status=0xff00, process failed
E/installd( 468): dexopt failed on '/data/dalvik-cache/[email protected]@[email protected]' res = 65280
W/PackageManager( 486): Package couldn't be installed in /data/app/com.fsck.k9-1.apk
If I try from adb:
1257 KB/s (1235200 bytes in 0.959s)
pkg: /data/local/tmp/k9-3102-release.apk
Failure [INSTALL_FAILED_DEXOPT]
Anyone have any ideas? Googling I've gotten the idea that it needs an odex file, but why is it failing for this ROM or configuration, and what can be done about it? Several results I found mentioned full filesystem (/system, /data, dalvik cache, etc) but those are all fine.

Okay so Enom answered in his thread on this as well, suggested I don't restore everything from Titanium so I didn't, but I'm still having problems specifically with Nook, AndroZip, and who knows what else... I've installed about a dozen random apps off the market with no problems but these two fail same as the original post.
Anyone seen this before or have an idea what might be going on?

After JesusFreake was so kind to chat with me, his opinion was that the problem was a disk full or permissions. /cache was 100% after moving dalvik-cache there, so seems like a lot of apps installed /cache is not big enough.
I wiped the system, enabled apps2sd, set up the system and my apps again, did not move dalvik-cache, and so far I've had no problems with the apps I normally install, the above apps, or any others I've tinkered with.
Hopefully my weekend experimentation helps someone else down the line.

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Buzz] (01/29/2011)

Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.

Very nice m8,
i'm using it on my CM7 Build #0, with much apps i have 156MB free..

cool man sounds orsum will have to add this to my new rom

Would you say this is better than the normal Froyo App2sd? is it any faster at loading the apps one the sd card loading from **** drive mode?

Froyo app2sd sucks, this one is heaps better as apps are stored on ext partition, so you save way more internal phone memory. And yea its fast.
Sent from my HTC Wildfire using XDA App

nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms

I have now installed this, how do i know apps are being moved to the sd card?

I would love to for those roms. I'll have to look at the roms. Unfortunately, I don't have a ZTE Blade, but I don't own most of these phones that Darktremor works on (I only have a Sprint Hero and a Sprint Evo).
The more roms, the better.
danne_jo said:
nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms
Click to expand...
Click to collapse

Run a2sd check. That will check the configuration and tell you if everything is setup correctly.
-Howad- said:
I have now installed this, how do i know apps are being moved to the sd card?
Click to expand...
Click to collapse

You can also just start "Titanium Backup" and check memory in the main screen

I installed Darktremor app2sd on Modaco custom rom (Froyo), and must say its excelent, I got internal memmory of 160 mb free, and now with 100 apps installed have 155 mb free. My ext3 partition is 512 mb and Dalvik cache is on ext3. With zipalign phone work well, no issues about stability, widgets work normal (its not case with Froyo a2sd).
Thanks Tkirton for this.

bump---new version available.

is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)

rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse
I want to know about that too. Can we flash the new version on top of the original one? Will it harm the installed apps?

"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???

how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.

Just flash on top of it.
rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse

Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
WackyWookie said:
"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???
Click to expand...
Click to collapse

Describe the steps that you went through in installing it, including any commands you ran after the install.
vilks said:
how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.
Click to expand...
Click to collapse

tkirton said:
Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
Click to expand...
Click to collapse
Ah good I was starting to doubt my phone's installation, good to know it's a bug...
Sent from my HTC Wildfire using XDA App

[Q] GTalk closes upon launching ("failed to get GTalk connection!")

Context:
- T-mobile G1
- CyanogenMod 6.1.0-DS
Whenever I try to launch GTalk, the application starts and then instantly closes itself. I tried looking at the phone using LogCat in Eclipse and got the following line:
06-05 17:00:55.967: E/talk(710): signInAccount: failed to get GTalk connection!
What can I do to make GTalk work?
I've already tried:
- Rebooting the phone
- Reinstalling the Google Apps ZIP

... logging in with your Google account?
Sent from my Gingerbread on Dream using XDA

How would I log in? The phone already has a Google login for my account; that's why it can get my e-mail and contact information.

I'm seeing this same issue with CM 7.2.0.1 on an HTC Desire (GSM). I'd only recently (about a week ago), upgraded from a CM 7.1, but gtalk had been working for a while since that upgrade, it stopped working yesterday with the "closes very quickly after starting" behaviour.
Full logcat excerpt for an attempt (fresh after a reboot to install the latest gpapps as I'd not done that before, assuming Google Play would have updated all necessary):
Code:
I/ActivityManager( 173): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.talk/.SigningInActivity bnds=[0,732][96,800] } from pid 277
I/ActivityManager( 173): Start proc com.google.android.talk for activity com.google.android.talk/.SigningInActivity: pid=937 uid=10058 gids={3003, 1015}
D/szipinf ( 937): Initializing inflate state
I/ActivityThread( 937): Pub com.google.android.talk.SuggestionProvider: com.google.android.talk.SuggestionsProvider
D/dalvikvm( 937): GC_CONCURRENT freed 412K, 51% free 2765K/5639K, external 0K/0K, paused 3ms+6ms
D/ViewConsistency( 937): AbsListView [email protected] enabled= true
D/ViewConsistency( 937): AbsListView [email protected] enabled= true
D/GTalkService( 261): AcctMonitor.auditGTalkConnections: not starting any connections since shouldTryToConnect is false
I/ActivityManager( 173): Starting: Intent { dat=content://com.google.android.providers.talk/accounts/1 cmp=com.google.android.talk/.SigninActivity } from pid 937
W/GTalkService( 261): blockingCreateGTalkConnection failed due to low storage!
D/dalvikvm( 261): GC_CONCURRENT freed 490K, 49% free 3290K/6407K, external 0K/0K, paused 3ms+14ms
E/talk ( 937): signInAccount: failed to get GTalk connection!
W/InputManagerService( 173): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 173): No longer want com.android.providers.calendar (pid 503): hidden #16
W/ActivityManager( 173): Duplicate finish request for HistoryRecord{40b9e8e8 com.google.android.talk/.SigninActivity}
Note that was an in-place upgrade from 7.1.? and I'm constantly fighting with low phone internal storage on this device, although right now it shows 11MB free.

[SOLVED] Bad default partition sizes ?
It seems likely now that this was just one symptom (also had Twitter app Force Closing, Google Reader unable to auth/connect, Browser Force Closing etc) of the bad default partition setup on an HTC Desire.
I managed to get S-OFF and then use the 'CM7r2' partition setup from alpharev.nl (I've too few posts to be able to post actual links) and so far everything's working without issues. Basically the default setup has a /system way too large for CM7's needs, and using that space in /data instead gives a lot of breathing room whereas with the default /data kept on filling and causing apps problems (and, yes, this was with as much as possible APP2SD'd).
It's possible I could have solved this using SD-EXT (partition your SD card to have 2 partitions, one of ~1GB for SD-EXT, the rest for SDCARD as usual), but I didn't try that.

Athan said:
It seems likely now that this was just one symptom (also had Twitter app Force Closing, Google Reader unable to auth/connect, Browser Force Closing etc) of the bad default partition setup on an HTC Desire.
I managed to get S-OFF and then use the 'CM7r2' partition setup from alpharev.nl (I've too few posts to be able to post actual links) and so far everything's working without issues. Basically the default setup has a /system way too large for CM7's needs, and using that space in /data instead gives a lot of breathing room whereas with the default /data kept on filling and causing apps problems (and, yes, this was with as much as possible APP2SD'd).
It's possible I could have solved this using SD-EXT (partition your SD card to have 2 partitions, one of ~1GB for SD-EXT, the rest for SDCARD as usual), but I didn't try that.
Click to expand...
Click to collapse
Since I have no idea what you mean by "S-OFF" or "CM7r2", could you post the search engine keywords you used to find the instructions to use the 2 things?

S-OFF is 'security off'. It refers to a HTC phone feature where some bits of the boot sequence can't be changed whilst it's on, so you need to go from S-ON to S-OFF in order to then be able to change that part of the boot sequence. This I did using the 'AlphaRev 1.8 HBOOT reflash utility' from alpharev.nl , I applied it using VirtualBox to boot the image.
A small guide to doing this is at: http://forum.xda-developers.com/showpost.php?p=8590461&postcount=31
In turn that part of the boot sequence is where you can tell the following part that the partition table has been changed.
The 'CM7r2' simply refers to "CyanogenMod release candidate 2". Note I mentioned with regards to changing partition layout it when referring to the alpharev.nl site which contains the necessary files to change the partition setup. Just put alpharev.nl into your web browser's address/search bar to go to the site (again, I can't link because THIS site only lets you after a certain number of forum posts, the minimum of which I've not yet reached).
Hope this helps.

So you are saying that alpharev made a patched bootloader that won't check for secure flags on the g1 or you just posted in e wrong thread?
Sent from my Nexus 7 using xda premium

Ah, sorry, I forgot I originally posted about the GTalk problem in a forum not about the HTC Desire, which is what I have.
Still, anyone having such an issue may still find it's due to 'bad' partioning of their phone, whatever the model. The same basic problem may apply: /data is too small, such that it (near-)filling causes apps to randomly fail, both in the manner GTalk can (closes as soon as it opens without being able to auth, logcat suggests some problem with authing), or just simply force closing.
If your phone has enough storage that a change of partition sizes (with the HTC Desire the method I outlined reallocated some un-needed space from /system to /data) will result in a larger /data without compromising functionality then it may solve such issues.