Originally Posted by arrrghhh

Hrm... I don't know, other than I don't experience this issue on other ROM's.

And no, unfortunately I did not find a fix yet. Haven't dug that deep either to be honest...

I did come across an issue that effected other roms. Basically the sd card driver response time by default and some standard was set to 250ms before it times out. However for some cards they need just a little bit longer, and when patched for more ms it resolved most of the issues. I wonder if that could be related.
Look at the comments line 537

Detule. Any chance that you could look at the timeout setting on the sd card? Maybe compile a kernel where the timeout is bumped up to 500ms from the 250, so we can see if it resolves the sd card removed issue?
Thank you.

Originally Posted by wizardknight

Detule. Any chance that you could look at the timeout setting on the sd card? Maybe compile a kernel where the timeout is bumped up to 500ms from the 250, so we can see if it resolves the sd card removed issue?
Thank you.

There really is no time-out setting per-se, to be tweaked. Oh, I see what you are talking about.

I was curious about these reports when I was using my tp2, but I never could reproduce them so it was hard for me to debug.

One of you guys that has a vested interest will have to sit down and try to figure this out. What better way to learn about kernel/android hacking than to have an open problem to tackle?

Hi master Detule, exist anyway for go into the EPST config in any rom NAND? i do this question for change the service number, well i roll back to winmo becase the battery life for me with data on was 4 hours life left; i hope you can find any twaeks for this, thanks for this great work..!

Originally Posted by imohtep

Hi master Detule, exist anyway for go into the EPST config in any rom NAND? i do this question for change the service number, well i roll back to winmo becase the battery life for me with data on was 4 hours life left; i hope you can find any twaeks for this, thanks for this great work..!

It will not work. You have to have a Sence based rom for EPST to work. We have an AOSP I believe. Sorry.
So you will have to do a nandroid backup and load WM to get EPST changes loaded, and then load android back again.

---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------

Originally Posted by detule

There really is no time-out setting per-se, to be tweaked. Oh, I see what you are talking about.

I was curious about these reports when I was using my tp2, but I never could reproduce them so it was hard for me to debug.

One of you guys that has a vested interest will have to sit down and try to figure this out. What better way to learn about kernel/android hacking than to have an open problem to tackle?

Is there a how-to guide to building out these nand kernels anywhere?

Originally Posted by wizardknight

Is there a how-to guide to building out these nand kernels anywhere?

Same instructions as building the xdandroid kernel (make sure you use 2011.q3 codesourcery toolchain). To create a flash-able package you'll need to splice my boot.img and append the new zImage you compile to the ramdisk.

There is a bit of a learning curve, but the beginning is the steepest part.

P.S. You have more logs of this failure? One where you are not using wifi. Also an older post of yours seemed to suggest that building an gbx0c-for-sdcard card, and using that card for nand solved your problems.

Originally Posted by detule

Same instructions as building the xdandroid kernel (make sure you use 2011.q3 codesourcery toolchain). To create a flash-able package you'll need to splice my boot.img and append the new zImage you compile to the ramdisk.

There is a bit of a learning curve, but the beginning is the steepest part.

P.S. You have more logs of this failure? One where you are not using wifi. Also an older post of yours seemed to suggest that building an gbx0c-for-sdcard card, and using that card for nand solved your problems.

Sadly it does not sound like a learning curve, but a a learning cliff for me.

I have two recently purchased TP2 that both show this behavior. If I use a SD based android I do not see the sd card removed error. If I use the nand version all but one card I have causes the issue.

Ok. Pulled out the spare TP2, put in my 32gb cl4 sandisk card that is very good at causing this issue. Booted, let it go to sleep, and then I got the sd card removed error (vs the unexpectedly removed error I see sometimes)
I put in an 8gb card I have that has slightly less issues, and did a get logs. Let me know if this has what you need, or what else I can do.

I was able to get an unexpected removal error log too. So I uploaded that too.

Originally Posted by wizardknight

Ok. Pulled out the spare TP2, put in my 32gb cl4 sandisk card that is very good at causing this issue. Booted, let it go to sleep, and then I got the sd card removed error (vs the unexpectedly removed error I see sometimes)
I put in an 8gb card I have that has slightly less issues, and did a get logs. Let me know if this has what you need, or what else I can do.

PM'ed.

Originally Posted by detule

PM'ed.

Yo... I can only assume you PM'd him the kernel you threw me. It's been running solid for a few days now - but the battery is pretty awful. It's not charging to 100% (even tho it says it is) and the phone just dies at random...

So perhaps one last hurrah and port ACL's battery code? I'd love to do it, but I'm sure I would be so very lost... I'm getting the hang of building kernels and making boot.imgs/flashable zips... but porting battery code is a bit above me at this point.

I know ACL has given his graces, so no worries there mate. As he always said, we're all on the same team...

I have been playing with Bluetooth lately. I noticed that if I left the Bluetooth running, and rebooted the phone that it would hard lock during the boot animation. I had to wipe and reload the phone to get it working again. Is this a known issue, or had anyone else seen this issue?

*edit*

Been working on the problem some more, and I found that if the ril update is not installed everything boots as expected if the phone is rebooted with bluetooth enabled. I tried the one from the first post, and the updated 8-15 one also. Same results.
I would be happy to pull any logs I can if someone could tell me how to get them from the phone in this state.

Do CDMA devices have to have the ril update? I am not that familiar with it.