Originally Posted by GJSmith3rd
I think I ran into the Samsung internal SD problems I've been seeing so much in the forums...
03-09 00:03:48.315: E/connfw(2782): connect error:2
03-09 00:03:48.370: E/DTT(2783): connect error:2
03-09 00:03:48.445: E/SMD(2781): connect error:2
I have some weird error in my logcat for some time now. Searching Google for "connfw connect error" returns nothing usable except this particular post by GJSmith3rd
, and using XDA search returns two posts, including this (actually three but this post is listed twice) but both were not specific to this problem. The other post is here
My logcat has the same error, shows every two seconds with a few differences:
- "connfw" and "DTT" both shows
- "Kies" instead of "SMD"
- "connect error 111" instead of "connect error 2"
My logcat shows this:
03-19 00:06:28.150: E/DTT(1843): connect error:111
03-19 00:06:28.270: E/Kies(1841): connect error:111
03-19 00:06:28.355: E/connfw(1844): connect error:111
The PIDs are almost/or sequential or near, probably means a same process might trigger the three errors.
The error number (111 on mine) are always the same even after reboot.
I don't know what or where all this processes are except Kies, freezing/unfreezing Kies doesn't change anything.
My device is Samsung Galaxy S2 international variant (GT-I9100) on leaked stock firmware Jellybean 4.1.2 I9100XWLSD.
- All stock, rooted, removed some bloatware (ChatON, SocialHub, VideoHub, nothing else)
- Installed around 600+ apps/games using Link2SD on a 32GB Class 10 MicroSD
Doesn't seem like the removed bloatware, or any root tools, that caused it because I tested with those removed or bloatware reinstated (except root and SuperSU, obviously because I need to adb logcat and this is jellybean) with same result, even in Samsung Safemode the error still shows in logcat.
I can say that my old device is almost problem-free except sometimes the external SD disappeared after several long hours or days (or got too hot after extended games playing) and all I need is a reboot.
Does it indicates a bad/broken flash or something? If so is there a way to fix it?
If anyone have any idea and/or direction I am very much appreciate it, TIA.
I don't know where else to post this, since no one else ever posted a logcat with this error(s).
If any admin/mod feels like this should be moved to other Topic/Thread, feel free to do so, the reason that I posted this here is because the guy above have the same errors that I have, that seems no one else on XDA have.
P/S: Nandroid backup/restore, ROM flash, factory reset is not an option right now, I'd like to try something that is less brutal option first if possible.