phone debugging

[Russ]

This is from my device hopefully with no sig, I like to stay anon anyway. If resetting the parent to utf-8 is what drop's my noise i'll be happy.

I note the following from the link's you sent. I copied them in order to test the pattern buffer. Perhaps apache has something say re: line 811 raw mode {@link


** @param is the stream to parse.* @throws IOException on I/O errors.

in raw mode all future entities* (messages or body parts) in the stream will be reported to the* {@link 

ContentHandler#raw(InputStream) handler method only.* The stream will contain the entire unparsed entity contents* including header fields and whatever is in the body.

ARM architecture looks pretty raw to me. I'm now going to try and forward a link from the news app which gave rise to this thread and hope some obscure forking expect isnt running off the stack and clobbering parts of the buffer on send.


Jamon Camisso <jamon.camisso at utoronto.ca> wrote:

>On 11/20/2011 12:28 PM, Russ wrote:
>> This is from my device prefered gmail app. Changed my sig. Got all you quoted but didn't see your sig.
>> 
>> Jamon Camisso <jamon.camisso at utoronto.ca> wrote:
>> 
>>> this is from my nexus s, with a signature which follows. running 2.3.6.
>>> test
>
>'test' was my signature. Here's the log that seems related to the issue
>we're seeing.
>
>D/Email   (  811): Upsyc triggered for message id=373
>I/ActivityManager(  111): Starting: Intent { flg=0x4000000
>cmp=com.android.email/.activity.MessageList (has extras) } from pid 811
>
>I/ActivityManager(  111): Displayed
>com.android.email/.activity.MessageList: +278ms
>
>W/Email   (  811): Line 8: Unexpected end of headers detected. Boundary
>detected in header or EOF reached.
>
>W/Email   (  811): Line 8: Body part ended prematurely. Higher level
>boundary detected or EOF reached.
>
>D/Email   (  811): *** synchronizeMailboxGeneric ***
>
>The "Line 8: Unexpected end of headers detected" section seems relevant.
>However, that message doesn't reveal much online beyond folks commenting
>that their email app crashing all the time.
>
>It looks like it is coming from the org.apache.james.mime4j package,
>specifically MimeStreamParser.java. See:
>
>http://hi-android.info/src/org/apache/james/mime4j/MimeStreamParser.java.html
>
>It sounds like folks opt for one of two suggestions: 1) use the K9 email
>application since it is supposed to behave better, not sure if that has
>been suggested here or not.
>
>2a) Otherwise, clearing caches is supposed to help, though that will
>require putting in your account details again:
>
>Applications>Manage Applications>All>Gmail>Clear data.
>
>2b) Or if you have root, you can rm the cache files manually without
>having to recreate the account. But I leave that as an exercise to the
>reader to figure out.
>
>Of course in the case of the latter options the issue will likely
>reoccur unless you keep your inbox and folders clean.
>
>Jamon
>--
>The Toronto Linux Users Group.      Meetings: http://gtalug.org/
>TLUG requests: Linux topics, No HTML, wrap text below 80 columns
>How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists