Good work

I see a few people is having problems... Not sure if anyone is able to use it long enough to see if fixes the most annoying bug - 'sleep of death'

amazing!!!!!

---

i flashed it and it was very awesome, i flashed back to stock and once the sd storage works and sound and camera work, i will falsh back to cm7. are the developers working on fixing the bugs right now?

Bootloop fixed

---

If you are caught in a bootloop after pressing the button on the back of the Le Pan TC970 follow these instructions.

First make sure you have either the the CWM recovery provided in this thread or the Manufacturer OS image on your SD card.

Once those are on your SD card you need to have downloaded the ADB.

After downloading that you must have the SuperOneClick package found here: http://forum.xda-developers.com/show....php?t=1353951

Now you must navigate to the directory you saved the above SuperOneClick and find the files

adb.exe (or apropriate Mac or Linux adb file)
AdbWinApi.dll
AdbWinUsbApi.dll

Once you have those you need to copy them in to the folder for your Android ADB installation.

Back up your old ADB files and then paste the ones from SuperOneClick into that folder to replace the original files.

Once this has been done bring up the command prompt/terminal and navigate to the ADB directory
then type
adb reboot recovery

and then the file you have on your SD card will load.

The ADB files in the special SuperOneClick are not the normal ones, as DerKoch (the guy who made that SuperOneClick version) said they are special ones that he "procured from somewhere".

Originally Posted by brandonnichols360

i flashed it and it was very awesome, i flashed back to stock and once the sd storage works and sound and camera work, i will falsh back to cm7. are the developers working on fixing the bugs right now?

We can only assume so... I hope they work on finishing this custom ROM before trying to move on to CM9...

Originally Posted by brandonnichols360

i flashed it and it was very awesome, i flashed back to stock and once the sd storage works and sound and camera work, i will falsh back to cm7. are the developers working on fixing the bugs right now?

Yes, for sure - cas_xp and the others already put in a lot of work to get this far, to have a public Beta test version.

Cas_xp reserved the first 3 posts in the thread, for updates, changelogs, etc.

The bugs will be ironed out, one at a time, until there's a Stable release.

Originally Posted by sburns90

You need to go into the build.prop and then you will find rotation settings in there. I believe you need it set at 90.

Well, I was intrigued by that. Imagined cas_xp wouldn't have missed something so simple, and shipped Beta1 with the screen upside down.

180 degrees seemed more like the rotation we needed, so I went build.prop editing. The line was even already there, just commented out with a #.

Gosh - BAD idea........

DO NOT edit the build.prop line.

It's a nightmare - the screen WILL rotate as you expect, 180 degrees, and it will appear normal.

BUT - the undelaying touch coordinates are NOT rotated. You click here, and it flashes across the screen. I had a hell of a time just trying to rename the build.prop.bak file created by ES File Explorer. You will have to think about an upside down keyboard (which you cannot see), and try to guess whre the keys you want to use would be. Nightmarish.

Gladly, I managed to feel my way, and rename the .bak file; posting this here in case someone else has the same idea.

Audio playback is working, but I didn't test capture.

Originally Posted by yann2

BUT - the undelaying touch coordinates are NOT rotated. You click here, and it flashes across the screen. I had a hell of a time just trying to rename the build.prop.bak file created by ES File Explorer. You will have to think about an upside down keyboard (which you cannot see), and try to guess whre the keys you want to use would be. Nightmarish.

We need to get the G-sensor (accelarometor) working, that is what will change the coordinates as well.

Originally Posted by sburns90

We need to get the G-sensor (accelarometor) working, that is what will change the coordinates as well.

That is low priority to me. After all, we do have a lot functionality are not working. But screen up-side down really doesn't bother me.
I have my priority list in Post#2

thanks for all your work casxp. greatly appreciated