Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!

[makkonen]

7 files is all the files. I removed the MJG Droid Util in the latest packages, since they didn't seem to be doing any good.

[makkonen]

Originally Posted by sfhub

Is there something special that needs to be done to get adb working?

Hmm. It sounds like you've done just about everything (usb_function_switch is usually the culprit). One thing that comes to mind that you didn't mention, and that I have maybe not made clear enough, is that you need to be connected via USB, in activesync mode, when you start haret, or adb will never come up.

You should not need to shut down usb ethernet, as once you switch to single instance mode, it does not conflict.

I'm currently connected via ssh forwarded over ADB to the RAPH500, running the 6-13 package.

[HotSauce]

Originally Posted by sfhub

If it booted before using the current AIO, try a different card.

If it booted before using an older AIO, replace components until it starts working. Delete data.img for each attempt. Start by replacing zImage, modules-*, startup.txt. Next try rootfs.img, initrd.gz. And so on.

I mean it booted up like a couple days ago, using the same AIO. I changed nothing, but now it is freezing every time I try to boot it.

[hamagc]

Originally Posted by HotSauce

Why is it freezing my phone when I run haret.exe?

where is it freezing? once the bar fills in haret? or once android is booted? or in the blackscreen with text?

you may just have a file that was corrupted. i would delete everything and start over with a whole new package, but this is just a fix-all of sorts. before i can really give any advice i need to know where it is freezing.

[sfhub]

Originally Posted by makkonen

you need to be connected via USB, in activesync mode, when you start haret, or adb will never come up.

Thank you, yes, that was the problem.

This is the sequence I went through:
1) change the setting to "Activesync" mode for USB2PC on the WinMo side
2) connect phone to windows box, don't need activesync process actually running on windows box, but need to hear the usb recognition sound (and make sure activesync is selected in the WinMo popup, if it shows up)
3) run haret.exe
4) usb device removal sound, followed by insertion sound, followed by new device found
5) install android adb drivers
6) adb kill-server (since it was running before, it didn't recognize new device until restart)
7) adb devices

Now everything works.

Thanks again.

[hamagc]

Awesome. Will try tomorrow when I'm back at work. Where do you put the line in eclar.user.config?

Sent from my AOSP on XDANDROID MSM using Tapatalk

[sfhub]

Originally Posted by hamagc

Awesome. Will try tomorrow when I'm back at work. Where do you put the line in eclar.user.config?

Sent from my AOSP on XDANDROID MSM using Tapatalk

It should already be there in the AIO package.

If not:

# custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
}

[makkonen]

Is sleep working on raph800 in recent packages? If not, does anyone happen to know when it went on the fritz? It doesn't seem to be functioning on raph500, and I can't tell if that's due to something device-specific or general.

dmesg suggests that there's a bunch of active wake-locks. LEDEffects (which I had to manually install with the latest package) doesn't give any breathing response, but does seem to be functioning otherwise.

[x4osw0n]

Sleep is 'kind-of' working for me. It does go into sleep normally but takes forever to wake up when a call comes in. I tested it and found it rings about 6 or 7 times before the phone even notices the call, which is usually long enough for it to go to voicemail. going into sleep manually works fine (call end button), and it wakes with the power/home button almost instantly, as if it were a 'real' android phone.

It usually wakes up easily from a home/power button press, then unlock, but its not exactly lightning fast on this phone (the 500).

I tried the latest kernel (from the 14th) but found it to be too buggy. It would 'reboot' to the xdandroid bootsplash intermittently and data was super flaky. GPS turned on (in winmo) would cause it to crash and reboot during the initial boot cycle, but this may not be consistent as I only tried it twice, but it did happen both times.

[hamagc]

makk, gps breaks deepsleep.

what is a wakelock? when i did my dmesg for phh so they can try to figure out the sleep issue with gps i saw a ton of wake locks.

if you want a copy of my dmesg too, let me know.

also they were takling about implementing chamonix's program for dmesg i think. supposed to make it alot easier to get those to the devs i guess?