NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[natemcnutty]

Originally Posted by joshts0

I actually tried a car charger too.. I thought I was making progress. but in the end I wasn't.

I accidently set out to install android with a low battery... bad idea.. MAKE SUR EYOU HAVE A FULL BATTERY BEFORE YOU TRY THIS. You dont want it going dead in the middle!

Shouldn't matter really. I've actually tested doing just about everything wrong that you possibly can with this phone. I have never had an issue getting it to charge back up by doing the following:

1) Remove any charger and pull out the battery
2) After a few minutes, put the battery back in
3) Plug in and let it charge. It will vibrate like it is turning on which is normal.
4) After 5 - 10 minutes, remove the charger and pull the battery again.
5) After a few minutes, put the battery back in
6) Turn it on and go to town

[siraloz]

The boot loop trap called the "MassStash Syndrome" happened to me as well. Nothing I did even after following the suggestions here really seemed to work for me. I used my friend's TP2 battery to boot to normalcy. Having an external battery charger would certainly help and I am sure these can be had from ebay or alike for relatively cheap. Aaargghhh says NAND is not for the faint of hearts, so, if you want to be in the game, you might as well have things to save your day.

I think in my case, the reason I got the boot loop trap was because I tried to boot up the phone when the charge was really really low and like joshts0 here, the battery ran out before the boot up process was done and so the phone kept thinking the the boot process must go on.

I am not sure whether the same boot trap will exist while reboot after the phone is left out to drain completely.

Originally Posted by Lmiller1708

Pull the battery. Put the battery back in. Connect it to the charger, it will boot but let it. Do not touch it for a while. Atleast 30 minutes if not longer. It will charge.

Once that time has expired pull the battery and turn it back on. You will have a working phone again. If it does not boot then just put it and bootloader and reflash.

Originally Posted by [ACL]

There is a strange issue i need to look into, and i will since i ran into it before. When you shutdown and leave the phone plugged in via usb, it looks like arm9 may still be running. So the phone does not actually charge and continues to drain batt.

only way to break this cycle is to pretty much unplug the phone from usb and pop the battery out to make sure arm9 is completely down. Then you can pop back in and charge. If not, then it will drain. Issue may stem from the fact that we arent killing usb during shutdown as we should.

This does not happen when i shut down without usb plugged in. So i'm pretty sure its usb related.

Originally Posted by manekineko

Actually Windows Mobile does do that too. This was a post of me running into this issue a ways back on a Haret phone.

http://forum.ppcgeeks.com/tp2-androi...boot-loop.html

Still, there are an awful lot of reports about this coming up all of a sudden.

Originally Posted by natemcnutty

OK, you have to yank the battery when it runs out of juice, then put the battery back in, then plug in the charger. If you just plug it in without pulling the battery, it will continue to try to start and do what you are talking about. My phone dies on me just about every day thanks to the broken USB pins, and I never have an issue charging it as long as I yank the battery first, then charge it. It will vibrate a bit, but the screen should not come on. It will charge, then after about 5 minutes, I pull the battery again, put it back in, and turn it on.
Read the first post...

Originally Posted by joshts0

I actually tried a car charger too.. I thought I was making progress. but in the end I wasn't.

I accidently set out to install android with a low battery... bad idea.. MAKE SUR EYOU HAVE A FULL BATTERY BEFORE YOU TRY THIS. You dont want it going dead in the middle!

[jortiz12885]

I had to take it to the nearest sprint store so they can charge my battery and after 10 mins i plugged my phone to my car and it was back to normal.

Originally Posted by siraloz

The boot loop trap called the "MassStash Syndrome" happened to me as well. Nothing I did even after following the suggestions here really seemed to work for me. I used my friend's TP2 battery to boot to normalcy. Having an external battery charger would certainly help and I am sure these can be had from ebay or alike for relatively cheap. Aaargghhh says NAND is not for the faint of hearts, so, if you want to be in the game, you might as well have things to save your day.

I think in my case, the reason I got the boot loop trap was because I tried to boot up the phone when the charge was really really low and like joshts0 here, the battery ran out before the boot up process was done and so the phone kept thinking the the boot process must go on.

I am not sure whether the same boot trap will exist while reboot after the phone is left out to drain completely.

[natemcnutty]

This is going to be a fairly long post, so please bear with me. I have been slowly putting this together ever since we got NAND up and running, and I believe we have ironed out almost all of the NAND bugs as they pertain to FRX05. Through that, I have been logging some of the changes that we had to make so that I can put together a nice and easy to follow post for chefs that want to start building ROM's. That post will be coming in the following week, but I want to work with ACL and LMiller on drafting that up probably through our Google Docs.

Status of NAND Development
First and foremost, [ACL] is still our only real developer for the NAND kernel. Without his hard work, there is no way we would be where we are, so if you can, please show your appreciation by donating to him: https://www.paypal.com/cgi-bin/websc...=Y8RGAN4VEEV2Q

ACL feels we are getting very close to finished with FRX05 for now, and after that is done, he will start committing some of the new updates to the kernel. Lmiller and myself are pretty good with testing and scripting, but the kernel code is outside of our comfort zone. Since we cannot really help him, the updates are going to be a little slower until he either gets more help or has more time to spend on this project.

Status of FRX05 ROM
Because we got rid of the rootfs on NAND, quite a few changes had to be made to get FRX05 working properly on NAND. LMiller and ACL did the brunt of the work on this while I tried to make minor fixes here and there when we found issues.

Later this week, we will be pushing out the release candidate of FRX05 for NAND. Hopefully we can iron out the rest of the bugs that are caused from running FRX05 on NAND and let the chefs start going to town with their customizations. Again, I will have more details on this later.

Available Space
Right now, we aren't using the NAND as efficiently as we could be. Some of the NAND does not like to be formatted, and it took a lot of testing to find where we could start and finish. I know LMiller was working on this as well, but we could always use more help with this if anyone is interested.

In between hex editing the partition layout and messing with mtdparts, I've probably flashed around 500 times in the last few weeks, and I still haven't gotten it perfected yet. Unfortunately, I've got so many bad blocks of flash, I can't say what is my device causing issues versus what it would do on other phones. I should be getting a GSM rhod some time, but that person is waiting for the Droid Bionic before I can get it from them.

Other ROM's
Once FRX05 is finished, we will work on getting XDAndroid's Gingerbread up and running. ACL has also mentioned getting cyanogen mod 7 working as well. He has also worked on sense builds in the past, but I understand this is much more difficult to do. Might need to make it worth his while

I will be updating the second post to keep track of each ROM along with known bugs for each one. We love getting feedback from you guys, but please include detailed information for us. If we don't get logs or steps to reproduce an issue, it will be ignored. Seriously, we aren't even going to bother responding to it. Our time is limited, and trying to figure out how to reproduce an issue is not an effective use of our time

Donations
As I stated earlier, ACL deserves all the credit for the time he has spent working on NAND. I put up his donation link earlier, and you can find it in his signature block. You can also help keep XDAndroid going by donating to them here: http://xdandroid.com/w/donate.php

There are a lot of others who have been involved in this project like Wozzer, myself, LMiller, and others from the XDAndroid crew. I can't link to all of them, and some of them don't take donations, but please remember that these people are giving their personal time to help you all have some fun with your phones

Thanks everyone,

Nathan

[arrrghhh]

Originally Posted by natemcnutty

...I have been slowly putting this together ever since we got NAND up and running
...
Thanks everyone,

Nathan

Thank you sir! Can't wait to see the first post updated, and get to actually start making some builds of this awesomeness. You guys have done a great job squashing bugs, keep it up!

Hope I can contribute even 1/10th as much as you guys have .

[siraloz]

Thanks for the informative post and, of course, your altruistic dedication to the project.

Originally Posted by natemcnutty

This is going to be a fairly long post, so please bear with me.
....
Nathan

Hmm... arrrghhh... get busy working then!

Originally Posted by arrrghhh

Hope I can contribute even 1/10th as much as you guys have .

Well, you do help. We all appreciate it.

[m4f1050]

Bug: Swap Call or Merge Call doesn't work on Call Waiting. If you answer with Call button (screen is off you can't do anything but Call button) you can't switch back, not even with Call button.

EDIT: Here is the log for Pandora and XIIA Live....

[joshts0]

Originally Posted by [ACL]

i cant seem to replicate this. Well its because i cant really drain my batt that fast since i'm always ADBd in. So i need your help

First, when your batt is dead. Is the phone completely off? did you take the batt out and just make sure its really dead.

Ok once you are sure its off, put the batt back in. And when you do this, the phone boots on its own ? i cant see how this is even possible

Ok so lets say it doesnt turn on on its own. So batt is in, you plug it in, then the phone goes on on its own ? randomly? or as soon as you plug in.

I dont have an AC charger so maybe i need one to replicate..

So if I take the battery out, and wait for a while.. put the battery back in, plug the phone in, the amber light will come on, I will not touch the power bottom, but after a couple of minutes, the phone will at some point make that one little vibrate thing, and a few mins after that it will start to boot up, but it wnt make it through the boot cycle of course and die again.. then the whole process starts over . Does that make since? I could prolly video tape the whole thing if needed..

[vistazifta]

Originally Posted by joshts0

So if I take the battery out, and wait for a while.. put the battery back in, plug the phone in, the amber light will come on, I will not touch the power bottom, but after a couple of minutes, the phone will at some point make that one little vibrate thing, and a few mins after that it will start to boot up, but it wnt make it through the boot cycle of course and die again.. then the whole process starts over . Does that make since? I could prolly video tape the whole thing if needed..

same xact problem and thats with puling the battery ten minutes before plugging it in and pulling it again before rebooting when i think its about to boot sometimes

[[ACL]]

Originally Posted by m4f1050

Bug: Swap Call or Merge Call doesn't work on Call Waiting. If you answer with Call button (screen is off you can't do anything but Call button) you can't switch back, not even with Call button.

EDIT: Here is the log for Pandora and XIIA Live....

Thanks or the log. Can you get me one more? get me a dmesg when you are trying to use pandora. Just to make sure its not kernel related.