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?

[mostly fixed] my froyo issues, hope I find some answers

I installed Pauls FRF50 rooted image+Cyans Kernel after wiping eveything (factory reset)
First thing I did after installing was run the following command to set the default install location to the sd card:
pm setInstallLocation 2
Click to expand...
Click to collapse
Here are the top issues.
1) tried to install all my backed up apps (140) via a dos for loop containing an "adb install command" (which has worked on eclair numerous times)..... It installed about 120 of them "successfully" but then got stuck after sending an .apk to the phone.
Weird thing is NONE of the "successful" apps show up in the launcher or under widgets. Application Manager shows them all with a "Computing" status in all fields.
Rebooted multiple times.
Now no apps will install, either via the adb command line or via the market. (after downloading via market the app gets stuck in the "installing" stage.
Sample:
C:\>adb install net.pixelpod.typefresh.apk
916 KB/s (29333 bytes in 0.031s)
pkg: /data/local/tmp/net.pixelpod.typefresh.apk
Click to expand...
Click to collapse
Nothing bad or errors on logcat at all. just this:
D/AndroidRuntime( 1707):
D/AndroidRuntime( 1707): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1707): CheckJNI is OFF
D/dalvikvm( 1707): creating instr width table
D/AndroidRuntime( 1707): --- registering native functions ---
Click to expand...
Click to collapse
Notes:
-Have rebooted multiple times.
-Dont have any market updates
-have tried clearing the market cache.
-same issue for root and non-root applications.
-have now set the default install location back to 0 (auto)
2) Exchange works! (finally), but absolutely kills the battery in 4 hours flat with minimum phone use. (69% usage by Exchange). Tried all settings, push, sync only one day, check every hour only.
3) My contacts are still not getting to my phone. Contact sync shows an error "will be back shortly". This has been the case for almost 24 hours now.
Heres my disk usages:
/dev: 208180K total, 0K used, 208180K available (block size 4096)
/mnt/asec: 208180K total, 0K used, 208180K available (block size 4096)
/system: 148480K total, 125180K used, 23300K available (block size 4096)
/data: 200960K total, 101860K used, 99100K available (block size 4096)
/cache: 97280K total, 2324K used, 94956K available (block size 4096)
/mnt/sdcard: 14898512K total, 8319592K used, 6578920K available (block size 8192)
/mnt/secure/asec: 14898512K total, 8319592K used, 6578920K available (block size 8192)
Click to expand...
Click to collapse

ok, I did another factory reset and flashed pauls image again.
Contacts are back!
Apps install again!

I am having the same problem. market keeps installing and never finish.
britoso said:
I installed Pauls FRF50 rooted image+Cyans Kernel after wiping eveything (factory reset)
First thing I did after installing was run the following command to set the default install location to the sd card:
Here are the top issues.
1) tried to install all my backed up apps (140) via a dos for loop containing an "adb install command" (which has worked on eclair numerous times)..... It installed about 120 of them "successfully" but then got stuck after sending an .apk to the phone.
Weird thing is NONE of the "successful" apps show up in the launcher or under widgets. Application Manager shows them all with a "Computing" status in all fields.
Rebooted multiple times.
Now no apps will install, either via the adb command line or via the market. (after downloading via market the app gets stuck in the "installing" stage.
Sample:
Nothing bad or errors on logcat at all. just this:
Notes:
-Have rebooted multiple times.
-Dont have any market updates
-have tried clearing the market cache.
-same issue for root and non-root applications.
-have now set the default install location back to 0 (auto)
2) Exchange works! (finally), but absolutely kills the battery in 4 hours flat with minimum phone use. (69% usage by Exchange). Tried all settings, push, sync only one day, check every hour only.
3) My contacts are still not getting to my phone. Contact sync shows an error "will be back shortly". This has been the case for almost 24 hours now.
Heres my disk usages:
Click to expand...
Click to collapse

Set the install location back to default, reboot to recovery, wipe dalvik cache, reboot again and it'll probably work.

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.

Reboot when update/install apps cm7-dta2sd

I was using micromod's CM7 build, using dtapps2sd, everything worked fine until yesterday i tried to flash cm7-rc1. I noticed gmail and facebook were missing and would not install, so i reverted back to the previous nandroid. All my apps were missing, i had read that clockworkmod 3.0.0.5 has been screwing with people's phones.
So i backed up my SD card, wiped it and repartitioned it, and wiped and reflashed cm7. It installed fine, but if i try to install an app, either from market or from .apk, the phone will simply freeze then reboot.
after i downgraded my recovery, i was able to get my last nandroid to work fine, i am now back on micromods cm7 build. But i am still getting this reboot, which means i can't even update my apps.
So i am on :
Micromod v.1.4 (cm7-grh78)
dtapps2sd-2.7.5.2-1
Here is a logcat, but i have no idea whether it captured the important point, i really can't read these things.
Code:
W/DownloadManager( 4573): Aborting request for download 1600: http error 416
E/vending ( 4640): [21] DownloadManagerBroadcastReceiver.handleDownloadCompletedAction(): content://downloads/my_downloads/1600 state is INSTALLED
E/TalkProvider( 4408): replaceContactWithContactId: contactId==0!!! liam.lah(at)gmail.com, acct=1
E/TalkProvider( 4408): insert presence failed for account=1 username=liam.lah(at)gmail.com client_type=0 status= cap=15 priority=0 mode=5
W/dalvikvm-heap( 4392): Attempted recursive GC
W/ResourceType( 4303): Skipping entry 0x7f040000 in package table 0 because it is not complex!
W/ResourceType( 4303): Skipping entry 0x7f040001 in package table 0 because it is not complex!
E/vending ( 4640): [22] DownloadManagerBroadcastReceiver.handleDownloadCompletedAction(): content://downloads/my_downloads/1600 state is INSTALLED
W/Service ( 4532): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/Service ( 4532): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/Service ( 4532): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/IInputConnectionWrapper( 5051): showStatusIcon on inactive InputConnection
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 4421): No keyboard for id 131074
W/KeyCharacterMap( 4421): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/IInputConnectionWrapper( 5051): showStatusIcon on inactive InputConnection
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 4421): No keyboard for id 131074
W/KeyCharacterMap( 4421): No keyboard for id 131074
W/KeyCharacterMap( 4421): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 4421): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
On a final note, the closest i could find to my problem was this.
http://forum.xda-developers.com/showthread.php?p=11214755#post11214755
Would that likely be it?
Thanks for your help in advance

1) Yes, that's probably the reason. Another reason would be Cache2SD not working correctly as a result of something (and by default, it fails on CM7).
2) "Fix uid mismatches" in Amon_RA's recovery. Does wonders.

Having the same issue coming from the same Rom going to the same Rom.
UID did not fix the problem.

Ok, once my CM7 build compiles, I'll try to find some time for the following - back up my ROM, wipe everything, flash CM7, DT's A2SD and post the exact steps for making it work.

I run CM7 with dt, and don't have any problems. I use both the RC and nightlies, CWM 2.5.1.4 (because 3.x screwed up my SDcard, and wouldn't run dt properly), and I use the 2.7.5.2 version of DT...
Sent from my Nexus One using XDA App

Jack_R1 said:
1) Yes, that's probably the reason. Another reason would be Cache2SD not working correctly as a result of something (and by default, it fails on CM7).
2) "Fix uid mismatches" in Amon_RA's recovery. Does wonders.
Click to expand...
Click to collapse
Tried "fix UID mismatches, no luck,
I'm not using cache2sd, my card is too slow, so thats ruled out.
I'm assuming the command to change ownership of /data/app would be something like this in the android terminal.
Code:
su chown user /data/app
except, i don't know what the user is called on android.
Code:
ls - l
brings up root and system as owners. It may be, but i wouldnt expect 'system' is the correct answer.

Or perhaps it is the /sd-ext that is the problem, i noticed when i mounted it on my computer the other night, there was a Lost+found directory, the computer said it was owned by root, and i could not change that to anything else, the file did not go away, or change owner even after reformatting with Gparted. The file reported itself to be 1.1TB, (on a 512) partition, and since then when i have tried to nandroid backup, it hangs on backing up the ext.

Is it safe to say this was cause by clockwork ?
I couldnt find much related in the thread.
Ive never had a single issue with Ext partitions until yesterday using clockwork for the first time.
I wish I could be of more help ... I wiped twice , re flashed back to original Rom stated above apps are now installing but Ext partition doesnt mount or remains unseen.

At this stage, after all the reading and fiddling ive done, i would be very surprised if it turned out to not be caused by clockwork 3.0.0.5
Can everyone else who has this problem, go to your /sd-ext in root explorer, and ask to change permissions. It should come up with a dialogue box indicating that /sd-ext is a read only file system. This, i assume is the heart of the problem. Just to make sure, can people who aren't having this problem do the same?
I think it might be as easy as using chown command, but i don't know what the standard username:group is on android. So i can't try that.
Can any more advanced linux nerds help out?

liam.lah said:
At this stage, after all the reading and fiddling ive done, i would be very surprised if it turned out to not be caused by clockwork 3.0.0.5
Can everyone else who has this problem, go to your /sd-ext in root explorer, and ask to change permissions. It should come up with a dialogue box indicating that /sd-ext is a read only file system. This, i assume is the heart of the problem. Just to make sure, can people who aren't having this problem do the same?
I think it might be as easy as using chown command, but i don't know what the standard username:group is on android. So i can't try that.
Can any more advanced linux nerds help out?
Click to expand...
Click to collapse
Have you tried to use "fix permission" right after you install your rom?

Lost+found IS owned by system (root), but should be empty. If it's bigger than the partition size - it means your EXT is corrupted. You could try deleting this file and checking the partition for data consistency (mounting in Linux).
It couldn't happen when flashing, only if your recovery is bad.

Gparted was acting up while i was trying to wipe all and start again. So trying with new sd card, backed up everything to computer, and will restore the nandroid again, keeping away from 3.0.0.5.
I'll keep everyone posted, it looks like a complete wipe of sd card may be the only choice.

liam.lah said:
Gparted was acting up while i was trying to wipe all and start again. So trying with new sd card, backed up everything to computer, and will restore the nandroid again, keeping away from 3.0.0.5.
I'll keep everyone posted, it looks like a complete wipe of sd card may be the only choice.
Click to expand...
Click to collapse
I've had the exact same problem for a couple of weeks now, never thought of the connection between my ext-problem and clockworkmod, but after reading this thread, i decided to try and change to AmonRa, and voila, everything is now back to normal! cm7-RC and DT a2sd are now playing nice again. All it took was a complete sd-wipe (after I copied everything to my pc), and a new sd partitioning in AmonRA!

Ok, have Re-done the partitions, and restored a nandroid. I can install .apks again.
But i'm getting a market force close, at the initial loading screen, it doesnt bring up a force close dialogue, just goes straight back to home screen. no cache to wipe. If i try flashing gapps again, i lose gmail for some reason, and don't get market working.

I've just tried installing freshly compiled CM7 build of my own - equal to CM7RC1 w/ Gapps compiled into it (somehow the compilation requests unneeded Gapps from Froyo, and fails to insert LatinIME, leaving me w/o keyboard - but it's another matter).
Steps (using a good SD card with EXT2 and Amon_RA's 2.2.1 recovery):
Wipe EVERYTHING, including SD-EXT.
Fresh install, formatting /system (verified in updater-script).
<you'll need to flash Gapps here>.
Flash DT-A2SD 2.7.5.3-beta04 (newest).
Reboot - it bootlooped twice, and booted well on third time - didn't touch it. Might be some build issues of my own.
Open Terminal.
Run "a2sd check".
See that everything works well, Dalvik-cache is on /data.
Tried opening Market, everything worked.
In Terminal, wrote "a2sd cachesd", waited until it did its job (+ several FCs) and rebooted the phone.
Tried opening Market, everything worked.
Conclusion - DT-A2SD works with CM7RC1.

So i grabbed the vending.apk out of the latest gapps, and replaced the other one and set permissions, for some reason it started working later.
So with a new repartitioned SD card, carefully avoiding clockworkmod 3.0.0.5. Everything works fine now.
Thanks for all your help, guys

Having the same problem.
I have HTC chacha running CM7. My phone reboots when I install an app.
Did not read the whole thread but is there a good fix for this problem?
thanks in advance

I had the same problem and the solution for me was format and repartition my sd card. I did an ext3 partition because i read it was the most stable with almost all scripts.
I hope i had helped you
Enviado desde mi Nexy usando xda premium

[Q] [Problem] Force close on dialler

Background:
I updated to JVB though Kies when it became available (code: XEE). Before that I was on Voodoo, but on RFS.
After the update, it ran for some time but suddenly a week or so ago I got quite a number of problems with the phone acting up (not wanting to hang up after calls -the green status bar would remain, I could not even hang up it in the notification area). Generally the phone was also using a lot of RAM.
I thought, let's do a factory reset. When I did this all my user apps did not seem to get deleted although I did get the "New phone" startup sequence. I
Finally, I booted into CWM recovery but trying to do the reset there, I got some errors
Code:
Formatting /data…
E:format_volume: rfs format failed on /dev/block/mmblk0p2
Formatting /dbdata…
E:format_volume: rfs format failed on /dev/block/stl10
Deleting Meta Data
Formatting /cache…
E:format_volume: rfs format failed on /dev/block/stl11
When this failed to work a reflashed the firmware (Code: NEE) with repartition and everything and everything was clean. I rooted via CF-Root and restored all users apps + data for these. I also restored some "system" data such as call logs, smses, etc.
After a day I started getting force closes when I used the dialler. I.e. I start typing e.g. "253" and the phone tries to match this against contacts and after 1 sec, I get a force close. OK I thought, maybe I should not have restored system data.
I restored from a Nadroid backup (that had root) and started all over with user apps. I did not touch any system data this time.
I still get the force closes often when I try to find a contact using the key pad.
From aLogCat:
Code:
5-06 16:15:51.855 E/JavaBinder( 482): !!! FAILED BINDER TRANSACTION !!!
05-06 16:15:51.859 E/InputDispatcher( 482): channel '40c41cb8 com.android.contacts/com.sec.android.app.contacts.PhoneBookTopMenuActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
05-06 16:15:51.859 E/InputDispatcher( 482): channel '40c41cb8 com.android.contacts/com.sec.android.app.contacts.PhoneBookTopMenuActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-06 16:15:51.878 E/JavaBinder( 482): !!! FAILED BINDER TRANSACTION !!!
05-06 16:15:52.871 E/libBlurEffect(23357): AndroidBitmap_getInfo() failed ! error=-1
05-06 16:15:54.562 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:15:58.742 E/InputDispatcher( 482): channel '40dcbd58 com.sec.android.app.dialertab/com.sec.android.app.dialertab.DialerTabActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
05-06 16:15:58.742 E/InputDispatcher( 482): channel '40dcbd58 com.sec.android.app.dialertab/com.sec.android.app.dialertab.DialerTabActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-06 16:15:59.574 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:16:04.617 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:16:05.898 W/InputMethodManager(23566): Ignoring onBind: cur seq=987, given seq=986
05-06 16:16:09.644 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
Does anybody have any idea what may be the cause of this?
BTW I use e-mail and Nitrodesk Touchdown to get contacts on my phone.

you should install another rom.. easiest solution. have you tried customs?

Well, no, but should I not be able to use the standard Samsung Rom fit for my device and area?

No clever people can help out here?
If at all prossible, I'd like to prevent sending in the phone for service since this will take at least 2 weeks.

FINALLY I have found someone having the same problem as me.
I have a Samsung Exhibit 4G and have this same issue with the contact list closing when I don't want it to. I sometimes (not always) get kicked back to the home screen when viewing a contact list, call logs, or when starting to dial a number via the keypad. The "force quitting" or whatever you call it seems to happen in relation to an activity that searches the contacts in some way.
I recently discovered aLogcat and immediately after this happening I saw the same "DialerTabActivity" error that fjelsten was seeing.
My phone was finally rooted recently, and I can't wait for a custom rom to come out so I can be rid of this B.S. stock ROM.