Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

@Nate: I've just test your "GSM Test " and still can not get GSM work, even after I tried to kill rild service. Anything else:
- WiFi also not work
- New sexy recovery still work like charm.

Here is my dmesg

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Yeah this isnt gonna work out. just synced and saw the binaries pop up. I'll remove it but have autobuild generate this exactly like you have it. When i sync bootevn i can have the latest recovery copied over this method is kept intact without ballooning up git. For all the developers, well this should be no big deal.. the noobs can suffer. But not sure if you agreed or not, but are we stripping the busybox or not?

which reminds me, we need a new thread. Or another place to have dev discussions .. lol. some of the posts are getting to be ridiculous so ill leave it up to one of the young guns to man one of these threads ..

Ok so im back home.. tired but im not sure if ill get to work on LK tonight like i hoped.. but i'll definitely run some more test for the gsm folks. Also i started using mountable modules like cyanogen. My only prob is its hard to script which modules to load.

For example this is how my modules are being generated now

2.6.27.46-01267-g6900b6e-dirty.sqsh

We cant leave it entirely up to android to mount since i dont think its able to determine the uname to know which modules to load. So unfortunately either the initrd will have to do the dirty work or the sysinit. Sysinit might load too late so this may not work out.

Also i was thinking about what you mentioned before, and copying this one file to system/lib/modules may not be a bad idea. this way our data restore will work flawlessly. we will have to make a way to do kernel upgrades but thats down the road.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

repost! i'm a noob

Re: NAND Boot Testing - 03-08: Full NAND FRX05 Testing (Data not working for some)
 

i know it was mentioned some pages ago, but i'm not able to move any apps to the SD card. any solutions to this? even using App 2 SD to indicate which apps can be moved, i'm getting "Failed to move application" notifications at every attempt. i'm using a 4gb microSD card and a sprint cdma tp2

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Yeah, sorry about the binary, I wasn't sure what was needed for autobuild and didn't want it to kick off a bad image or something. Should have asked first, and thanks for removing it.

It looks like recovery doesn't need busybox in /recovery/bin. The recovery.tgz I put in the initrd does not have busybox, and it functions just fine. Initially, I had been including it in the recovery.tgz, so it looks like we still have more headroom available in the initrd if we need it for anything else you'd like to include!

I agree about the forming of a new thread for ROM related issues. I'd like to see LMiller write up a post for FRX05 on NAND since I think he did the majority of the work. I'm having a difficult time getting FRX06 working properly, and I don't know what all you guys did to fix it up.

I really would love to see us move modules into system. I wonder if there is a way to reduce the overall size of our modules. They seem so much larger than the modules for other phones.

Re: NAND Boot Testing - 03-08: Full NAND FRX05 Testing (Data not working for some)
 

I believe this is still due to us not having a real root. It looks like when we took /bin out of the PATH, we no longer had access to /bin/busybox. In our initrd, we have /system/bin/sh pointing to /bin/busybox. I'm testing pushing the latest su to /system/bin/su, copy /bin/busybox to /system/bin/busybox during install, and then ln -s /system/bin/sh /system/bin/busybox. We'll see how that works out.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

ahh i was confused. Yes i see busybox is gone but the links are still there. Its cool. dont worry bout it still trying to automate all this. Reason recovery had its own busybox is that it also can serve as an initrd incase you want to boot into a recovery kernel. This way you can wipe kernels in the future, but we are far from that stage so lets not even talk about it until we are there.

Yeah im sure lmiller is cooking up frx6. not a bad idea to create an update tho. Test our update code :-)

for the modules the squashed version brings them down to 6mb. So only 6mb get copied to over system. Best i can do for now. I think once we remove the uneeded ones we can see a reduction in size. Means we would need to go over the defconfig and figure out what we need. (not thrilled about that).

Ok, if we do move modules to the system. Then what do we do about pppd and the other junk in android update so we can get rid of all that nonsense. I think the pppd issue is just bad code on the ril. I can fix that and bring it back to system. not really sure what else we have on android update.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Storage system can not open the file URL?
This：
http://htcdevs.wirelesstcp.net/files/xdandroid/

Wirelessly posted (TP2: Mozilla/5.0 (Linux; U; Android 2.2.2; en-us; MSM Build/FRX05) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

@Nate/ACL,

I have been really busy around the house with spring cleaning! Still have snow in my back yard though... and going to trim my apple trees today! ;)

Ok back on topic! I will try to look at FRXO6 this morning and see if I can getv it working. Nate can you post what you have so far? Save me some time or atleast post what issues you are having.

Thanks for all of your hard work guys! And maybe we can move this over the ACL'S thread and help here with testing and Noobs... Thoughts?

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Its prob best you do it from scratch and try to automate it. I dont think stine will start making us tgz anytime soon, so if we can take the existing imgs and just automate the process, it will make it easier to do updates :-).

i dunno about the threads. i say start a new one just for chatter..