Quote:
Originally Posted by wehweh
I'm getting wi-fi grief too, and it's not the kernel. I'm running the 2-8 package with the 2-4 kernel right now, so it's not makk's fault.
I also can't get 3D running. My winmo ROM runs TouchFlo 3D (it's a Calkulin rom), but android doesnt seem to pick it up.
|
Yup. It has to do with how the new system dynamically loads the wifi calibration from nand. Apparently the old way gave every single phone the same mac address. So that's fun. Unfortunately, the tools to extract the calibration from nand... are not working on my end. I tried to get them going, but I'm running into some trouble. When it's fixed, I'll post it up. Until then, if you need wifi, I'd suggest the latest kernel with the Feb 2nd system. That should work for now.
As for 3D, give a try to the hologram program. Someone said on #htc-linux that Touchflo wasn't enough -- it didn't actually consistently initialize the hardware, or something.
Quote:
Originally Posted by chibiushi
You know that's said but true, I feel that this frankenstein'd hacked Android runs snappier and better that WM does, and my phone was made for WM (I am not trying to insult any of the hard work of all of the people that are doing this, I love this and respect all of you that work to make this work.)
|
No insult whatsoever taken. It is a frankenstein'd hacked system. I think the WinMo developers have more reason to take umbrage.
Quote:
Originally Posted by Horace
Great job.
Using 2/08 build
The UI seems a sluggish. Is this normal?
Who is doing work on the GPS?
|
The UI is somewhat sluggish. Better than it was, but still a bit less than totally responsive. Unless it's really struggling, it's probably normal.
Not sure who in particular is working on the GPS now. There are a few people looking at it, I know, but I think they're waiting for inspiration to strike at this point... or some more useful source code to get released. jnadke on the Touch CDMA forums at xda-developers has done a lot of work to get it fully-functioning for the last generation of devices -- hopefully his work will start to filter through to the new breed.
Quote:
Originally Posted by spectator
I took your advice and re-formatted the SD card, and used a fresh boot. Unfortunately, I still have the same issues. Most of the time, it pretty much stay in command-line output, and it doesn't make it to the GUI or startup animation. It just seems to throw endless SQUASHFS errors. My wild guess is that it's tied to enabling the 2nd memory bank, but I have no idea how to use a newer build while turning that 2nd bank off.
|
What device have you got? The 2nd memory bank should be a good thing on any RAPH800. It sounds like you've been careful in your testing, so this probably isn't it, but the tons of squashfs errors sounds like it would be a corrupted system.sqsh file. Try downloading again?
Anyway, since the boot time option doesn't work for some reason, the only way to disable the 2nd memory bank would be to build your own kernel. Sorry; I know that's a bit of a big step.
Quote:
|
Originally Posted by glougloumouth
I am using the FEB08 system.sqsh and the modules-2.6.27-00851-ga10ffed.tar.gz (JAN30) modules. No WiFi: "unable to start Wi-Fi". Using System & Modules of late JAN has working WiFi.
Looks like it is the kernel.
Can someone double-check & confirm?
Another interesting thing: FEB08 system.sqsh and JAN30 modules has the "Power off" phone working (it does turn off). Every build I tried since early FEB, up to FEB08, when I power off the phone, it initiates power off then freezes (the power off spinning wheel stops spinning and the phone is frozen, have to soft reset).
|
That's interesting. the power off stuff is strangely finicky. With the newest system and the newest kernel, it still fails to work on my end. There's a change in code that enables it, but then it messes up other things (but only for some people, apparently). Thanks for the testing, though -- I'll look out to see if it's working intermittently on my end.
To clarify, the kernel is zImage. If you use a different zImage than modules-blah.tar.gz, wifi definitely won't work, since the wireless driver won't load (it's tied to the kernel/zImage version). Not sure if you were doing that, but I thought I'd point it out anyway. The problem is in the way the new system is failing to pull the wifi calibration. Which comes down to both the modules and the rootfs. So, really, it's both sides that are broken.
