15 replies to this topic

[Turing]

I installed 7.1.0-GalaxyS via the following guide
http://wiki.cyanogen...ll_Update_Guide
I have chosen "Method via Recovery".
The installation worked without any unexpected behaviour.

Unfortunaly after every touch on the display there is a 70% percent chance that a window with the following error message pops up. (The process is not always com.android.launcher)

Sorry!

The application ADW.Launcher (process com.android.launcher) has stopped
unexpectedly. Please try again.

Force close

Sometimes this message does not occur and Cyanogenmod does instead a reboot (not reboot of the whole phone, just a reboot of this "desktop"). It was also never possible to power down the phone. Because during the power down Cyanogenmod always either popped up this window or rebootet.

I tried an update according to the guide with and without Google Apps (20110828).
I also tried the lasted nightly build cm_galaxysmtd_full-181.

I blamed this "hardcore's Kernel with the ClockworkMod Recovery 2.5" and installed DarkyROM 10.2.
Afterwards I tried again to install 7.1.0-GalaxyS and ended up with the same problem.

Now, I run out of ideas. Do you have any suggestions?
Have a usual Samsung Galaxy S GT-I9000 and the modification of the Firmware I did so far was an update to Gingerbread with Samsung Kies.

Edited by Turing, 12 March 2012 - 01:11 AM.

[SocceR-5]

Hi,
Have you tried clearing the phone's cache using the recovery mode?

[Turing]

Yes, between two installations I always did

• wipe data/factory reset
  
• wipe cache partition

and sometimes also wipe dalvik cache.

Maybe I should ask a more precise question:
How can I analyze this problem further?
Are there any logfiles I can access? A problem that for every application I start there is a high risk that the application crashes. Hence, it is nearly impossible to so something that requires several actions.

It is really confusing that these applications are not always but only most of the time.
Afterwards I also installed team hacksungsalpha version of CM9 an there I did not had these crashes. However I had different problem still prefer to install CM7.

[Turing]

I really would like to give CyanogenMod another try.

Any suggestions how I can analyze my problem any further.

I didn't had an externel SD-Card. Could this have been a problem for CyanogenMod?

[bassmadrigal]

No, a lack of an sdcard shouldn't cause any app crashes. Most likely this is due to a corrupted install. Try downloading 7.2 RC2 (or a later CM7 nightly) and verifying its MD5 hash (verifies the file isn't corrupt). Then reboot into recovery and under the Mounts and Storage menu, select Format /system. Then go back to the main screen and select Factory Reset/Data Wipe (this also wipes your cache and dalvik, so there is no need to do it separately). Now you can reinstall CM and gapps.

Also, make sure if you are restoring apps with something like Titanium Backup that you aren't restoring any system-related settings as that could be causing bring any problems right back.

[Turing]

Thanks for your suggestions.

I checked the MD5 checksum of the .zip I installed the last time - it was correct.

I downloaded the new 7.2RC2 and installed it according to the wiki (http://wiki.cyanogen...ing_CyanogenMod) additionally I did select Format /system before Factory Reset/Data Wipe. (and of course checked the MD5 checksum)
Unfortunately I had the same problem again: after each touch there was a high risk that an application crashes

Afterwards I booted again in the recovery mode and selected this Fix Permissions
Unfortunately I has not helped


Do you have any further suggestions?

I did not select Format /boot because this was not mentioned in the wiki and I was afraid that this might destroy my recovery mode or delete something which is not installed with the cyanogenmod zip.

Edited by Turing, 26 May 2012 - 05:02 PM.

[bassmadrigal]

And you aren't restoring any apps or data after you install it?

[Turing]

No, I do not restore anything after the installation of cyanogenmod.

The last time, I even removed everything from the internal SD card except for the zip files needed for the installation.
I also removed the SIM card to be sure that this has nothing to do with the problem.

[bassmadrigal]

Have you checked logcat to see if anything stands out ?

[Turing]

If I open the Terminal Emulator and type logcat I get the following

Unable to open log device '/dev/log/main': Permission denied

[Turing]

Ok, I first have to type su to get root rights, then I am allowed to read the log.

There are a lot of errors: http://heizmann.name...ogenmod7log.txt

I have no Idea yet and will start searching, but any suggestions are welcome...

Edited by Turing, 27 May 2012 - 10:26 AM.

[bassmadrigal]

I don't see how you could be having all these permission issues with a brand-new install. It just doesn't make any sense as the permissions are set automatically when it is installed. Have you tried running fix_permissions?

EDIT: Just re-read the thread and you had done it earlier. Maybe try out RC3, but if that doesn't work, then I am completely out of ideas. With a clean install, there should be absolutely no permission issues. Those files don't even exist until Android creates them (with the proper permissions).

[Turing]

Ok, I gave it another try.

I booted ClockwordModRecovery and formated every possible partition, including the sdcard.

Then I used Odin to flash the "original" firmware I9000XWJW1. I checked this installation, everything worked fine.

Afterwards, as suggested in the wiki, I used Heimdall to flash this speedmod-kernel.

Then I booted into ClockwordModRecovery, formated again /system and the sdcard. Afterwards I checked mount USB to transfer the Cyanogenmod 7.2 RC3 .zip.

Afterwards I continued as suggested in section Method via Recovery in the wiki


Cyanogenmod booted and guess what: It was as bad as when I tried it first. Nearly every click caused a crash. It was not even possible to reach the terminal and type su logcat in a few minutes.



Is there some compatibility problem between this speedmod-kernel and cyanogenmod 7? Are there other kernels I could use?

What old data is still there which might cause this problem? Could there be a problem with the partition table? Is this not reset while flashing back original firmware?

Is there some packed cyanogenmod 7 ROM that comes along with a kernel?


During the last days I also tested several other ROMs including some cyanogenmod 9 (from the open kang projekt) none of them had any problems with crashing applications. It seems to be a problem only related to my phone and cyanogenmod 7.

Edited by Turing, 28 May 2012 - 03:42 PM.

[bassmadrigal]

Have you tried it with the kernel recommended in the wiki? Also, you didn't mention whether or not you did a Factory Reset/Data Wipe after you installed CM. You did it before you restored the stock ROM, but never mentioned whether or not you performed that after you installed CM.

[Turing]

Yes, this speedmod-kernel I mentioned is the one suggested and linked in the wiki.
I did the Factory Reset/Data Wipe as recommanded in the wiki (directly) before the installation of CM. Not afterwards.

Btw. Thanks for your suggestions.

[bassmadrigal]

I honestly have no idea why you are having the problems you are. You could try an alternative kernel (not sure what all is available for your phone, but the xda forums probably have a few to choose from).

You could also post this in the bug report section, maybe they will get a chance to figure it out before the final 7.2 release is finished.