yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] yann2:
Thanks, cas_xp - I think their server that was hosting the file (something like DL8.fileswap.com) died - i could try to open servers 1, 2, 3, but of course none of them had the file requested. So, if it crashed, it lost all the stats as well. VERY precarious host. :(

Will send it to Files.Inbox.lv once my download completes, and post a Mirror link for it as well.

Cheers! :)

EDIT : Just finished uploading my copy - Mirror copy of CM7 Beta 6.1 file HERE. (file renamed slightly for clarity - named LePan-TC970-CM7-Beta6.1.7z)
[Android Software/Hacking General [Developers Only]] jerrystake:
Kernel Information

never mind
[Android Software/Hacking General [Developers Only]] jerrystake:
Boot from SD

Has anyone put together a bootable sdcard for tc970? I am ready to test the kernel I've been working on and would prefer to use sdcard for testing and really don't want to have to start another project.
[Android Software/Hacking General [Developers Only]] yann2:
A few people have mentioned charging problems with their LP1 tablets after installing Beta 6.1. One example here, as posted at LPL Forums, on the CM7 Release and discussion thread:

[quote='RamMan' ]

Since I did the latest upgrade released by cas_xp I have only noticed one issue. If I power down completely and try to recharge the battery, it will eventually just die. (Ie. No charging even though the battery charge indicator does flash) The only way to charge is in sleep mode or while I am using it. Any thoughts ? I followed the instructions including the reset to factory defaults. I did not delete all caches as it was not part of the instrucrions ....

[/quote]

I checked and the charger_man binary included in Beta 6.1 is the exact same one, CRC match, to the Beta 3.1 Charger update.

If other people can confirm this, there might be an issue. Thanks for any information, ;)
[Android Software/Hacking General [Developers Only]] GnatGoSplat:
I don't recall anyone ever being able to make a bootable SDcard for the 970.

However, I'm anxious to know if you ever get your custom kernel to boot, so let us know if you do!
[Android Software/Hacking General [Developers Only]] jerrystake:
How about a short tut on how you compiled cm7 from your git tree?
[Android Software/Hacking General [Developers Only]] jerrystake:
iBoot

For any that are interested it turns out that the uart3 to usb interface is not supported by iBoot. To gain an iboot prompt you have to use the TP UART enable which is uart3 anyway (UART4 and the JTAG interface is supported also). USB UART3 allows shell access without the need for ADB while in normal boot mode but not recovery. IBoot, it appears, is very limited in scope and supports only a few commands mostly, nand read and write; .jffts, .i, .e, .yaffs etc., fatload, mmc init, reset, run, boot and printenv. It seems scripting is not supported from command line but run using environment variables is.

The nand used by the tc970 is an Embedded 2G standard MLC NAND flash memory, with an e.MMC 4.41 interface by SanDisk and 512Mib POP.

Anyway, I am close to being able to test kernel now I have some comfort knowing I have a chance to recover if it all goes wrong. I could sure do without Innocomms screwy image headers though.... If anyone wants a copy of IBoots env variables, let me know
[Android Software/Hacking General [Developers Only]] nbvtd:
Help!

I was previously running beta 6, and used CWM to flash the 6.1 updates over. I factory reset, wiped dalvik and cache, and after flashing 6.1 im stuck at the Le Pan into loading screen, and will not continue. Reset button while holding volume down doesnt return it to CWM to reflash, and it wont connect usb to my pc to use odin to force it back to the previous update.

Help
[Android Software/Hacking General [Developers Only]] jerrystake:
Try holding down the Vol+ then hit reset while continueing holding vol+ until either the tablet vibrates or downloader screen appears. Once in downloader screen use vol keys to select boot into recovery. Should work....
[Android Software/Hacking General [Developers Only]] nbvtd:
Managed to get back into CWM with that, thanks. Any idea why it wont boot? Or just i just redownload 6.1 and reflash?

update: redownloaded, and reflashed. works now, whew. Life is good again
[Android Software/Hacking General [Developers Only]] jerrystake:
The first time I installed I had same problem. I simply re-did by 1. factory wipe 2. run cm7....griffin.zip 3. run griffin-core.zip 4. then gapps and lastly reboot system from menu ...
[Android Software/Hacking General [Developers Only]] yann2:
CyanogenMod 7 Release Discussion Threads reach 50 Thousand Views!

Just realized something. Looking at the Stats for the CyanogenMod 7 Beta for the TC970 (Le Pan 1 tablet) release discussion threads, which I have started and maintained both at LePanLife.com and AndroidTablets.net.

The number of Views for these threads - adding the LPL, plus the AT forum ones, we are over 50 Thousand views. ;)

Snapshots from both forums as of Today, October 2, 2012 :

AndroidTablets.net (30,018 views) :

LePanLife.com (20,623 views) :

I find that very nice, and a sign that they have done what they were originally created for - spreading the word and helping people getting a BETTER Operating System for their Le Pan 1 tablets.

Credit for the CM7 port for LP1 is all to Cas_xp. Chinabull made a huge advance in providing us a port of ClockWorkMod for the LP1, which makes it all possible. And Franco, aka fv+ at XDA Developers started it all, by creating a firmware authentication tool that made it possible to run CWM in the fist place. Thank you so much, gentlemen. ;)

Besides the Release Discussion threads, whose stats I mentioned above, my own CM7 Step-by-Step Installation Guide has got over 20,000 Views (currently 15,106 and 5,759).

As editor, maintainer, general troubleshooter and cheerleader in these threads, I feel very happy to see them so successful.

Cheers, friends, hope you enjoy your CM7 enhanced LP1. ;)

Huge Thanks to Cas_xp, Chinabull and Franco fv+ who made it all possible.
[Android Software/Hacking General [Developers Only]] jerrystake:
Thanks cas_xp or fixing up the recovery, looks good. I don't know if everyone knows but, the kernel is now being backed up with the other core files. Sometimes folks may not realize the small touches that are not as glaring as a new widget or faster wifi but are just as important for a better tablet.
[Android Software/Hacking General [Developers Only]] yann2:
Yeah, the under-the-hood bits are not visible, unless you have the tools and the skill to go where cas_xp makes it all work. Wish I did, since I really enjoy optimizing things.

Good to know it's looking tidy and nice there, jerry. :)
[Android Software/Hacking General [Developers Only]] jerrystake:
Found a schematic for the LePan Phone which is based on the same hardware as the LP1 save LCD, TP and emmc. I compared the two schematics and gleaned some incite into why the bus setup is somewhat strange compared to other omap devices out there. Just thought some of you might be interested in the hardware..

heres the link: http://wenku.baidu.com/view/74626d3b0912a2161479290e.html

If anyone finds any driver or kernel info I would appreciate a heads-up. I have found a driver I can modify for the camera but still need a driver for the ha2608 touch buttons. I believe a Galaxy device uses it but haven't found it yet or any config info on the chip.

I've been able to get all the basic kernel devices setup and kernel compiled. Just working up the nerve to test on my device :) If anyone has a script already written to sign the zimage with the proper innocomm headers you would sure save me some time. I'm just not sure how the signing and headers are done to work with iboot. maybe I can modify franco's packer to pack just the kernel but would feel better if someone has already tested a utility to do this.
[Android Software/Hacking General [Developers Only]] yann2:
You are making nice progress, jerrystake, congratulations! Hope all goes well with the testing in the tablet itself.
[Android Software/Hacking General [Developers Only]] Jimi Mack:
I can claim to be having the same issue. In Beta 1 it will not charge at all while powered down. It will not indicate charging nor charge when powered off but it will charge while powered on,
[Android Software/Hacking General [Developers Only]] yann2:
We didn't get any comments from cas_xp, so the possible problem is still up in the air. Yesterday I rolled back to Beta 6.0, and tested charging it while tablet off, worked as expected.

The Beta 6.1 charging issue might affect only some people, but I think there''s an issue somewhere. For now, there's the option of downgrading to Beta 6.0 for someone who has thta, or charging only with the tablet on, or in sleep mode (screen off but still running).
[Android Software/Hacking General [Developers Only]] Jimi Mack:
Thank you but I can not seem to find a link to Beta 6 as to 6.1
[Android Software/Hacking General [Developers Only]] yann2:
Beta 6.0 was only a small patch file, same as Beta 5.1. You need to install Beta 5, which is a full build package, then aright after (while still inside CWM), apply the Betas 5.1 and 6.0 patches.

Beta 6.1 was again a full build release, and had some specific install instructions to be followed.

The two small patches for 5.1 and 6.0 are attached to the bottom of the original post in this thread.

Good luck! :)
[Android Software/Hacking General [Developers Only]] jerrystake:
I'm afraid I have seen the same issue with battery charge namely not charging while unit is turned off. Also I have problem with starting tablet after power down if the charger is plugged in. ie wont start until charger is unplugged. Because I am testing the kernel I am working on I have sort of ignored problems on chance I am inflicting my own woo's....
[Android Software/Hacking General [Developers Only]] Jimi Mack:
Thanks I caught them and was not sure if I was missing s complete 6 as opposed to the 5 and patch.

---------- Post added at 07:11 PM ---------- Previous post was at 06:47 PM ----------

Will confirm going back to Beta5 solved the charging issue. Thanks.
[Android Software/Hacking General [Developers Only]] yann2:
Thanks for adding that report, Jerry. cas_xp has not responded yet, but I feel there's too many reports of this issue for it to be a random, odd occurrence.

I checked the charger binary file included in beta 6.1, and it's the exact same one as in the Beta 3.1, which was an emergency patch/fix for serious charging problem with the Beta 3.0 version. So, the file is up to date, I thought maybe an older version might have slipped in by accident.Not the case.

For the time being, it's either charge only with tablet on or in light sleep mode (screen off, but desktop loaded) OR downgrade to Beta 6, which does charge perfectly, just tested it last night. (requires installing Beta 5.0 full package, plus two small add-on, patches, beta 5.1 and 6.0)
[Android Software/Hacking General [Developers Only]] jerrystake:
Can anyone help me out? I can't seem to find the kernel entry point the bootloader is handing off to. I think kernel loads at 0x81000000 and should start there but I get as far as starting kernel then nada.....I've tried several addresses but no joy.

According to kernel messages from 4431 kernel boot .init is at 0xc0008000

Virtual kernel memory layout:

<5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)

<5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

<5>[ 0.000000] vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB)

<5>[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)

<5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)

<5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)

<5>[ 0.000000] .init : 0xc0008000 - 0xc0037000 ( 188 kB)

<5>[ 0.000000] .text : 0xc0037000 - 0xc0510000 (4964 kB)

<5>[ 0.000000] .data : 0xc056a000 - 0xc05af2e0 ( 277 kB)

why is it not at 0xc100000000 or is wrong load address...

I don't get it, maybe kernel is relocating any idea's....
[Android Software/Hacking General [Developers Only]] cas_xp:
I am aware with this power off charging issue and I will provide a fix shortly.
[Android Software/Hacking General [Developers Only]] yann2:
Wonderful, cas_xp - I will spread those, good news. :)

Cheers!
[Android Software/Hacking General [Developers Only]] cas_xp:
I don't what happened. The change should be straight forward, but I tested it, it didn't work. Can somebody try it and give some feedback? Basically I missed a file called init.charge.rc in rootfs. Now I add it back by flashing the attachment.
[Android Software/Hacking General [Developers Only]] jerrystake:
I'll give it a shot in a little while
[Android Software/Hacking General [Developers Only]] jerrystake:
Looks like a bug and one I think has been around awhile. I applied your patch and restarted into GB. Then powered down from menu while charger plugged in. Unplugged charger and plugged back in at which the charge icon displayed and all looked well until I looked at uarts3 console where the tablet was in a boot loop. I attached a log from uart3.

edit: Note that i'm on the 4749 kernel also did you know that after linux 2.6.36 they rename the tty devices from ttyS to ttyO! I guess someone did not like the S=serial and preferred O=out .... which made the iboot moot for linux 3.0.8. Who the heck is watching the ship????? I am going to try a binary patch but in the end I suppose I will have to come up with a new boot loader for LP. I don't know if it is worth trying to upgrade to icecream except that now it is becoming a me against Lepan that this kernel rewrite can be done with out their help.....

Any hardware guys out there willing to trace out some pcb traces to verify some key signaling from the FCC schematic?
[Android Software/Hacking General [Developers Only]] yann2:
I will post in the release threads and ask for feedback, cas. I have a full battery atm, plus Beta 6.0 installed, all tweaked and overclocked. :)

But there were a number of people asking for a fix if possible, Will report back. ;)

Thanks for working on this fix.
[Android Software/Hacking General [Developers Only]] jerrystake:
I found the good stuff finally ... needed the machine ID and couldn't find it anywhere turns out it is 9999, how clever china... figured out how to load and exec kernel from ibootloader via console so things are looking up and should be able to set environment vars for machine params and test boot from loader command prompt rather than nand ... still, I wish they would have included more command support like bootm etc...

Environment size: 1365/131068 bytes

Griffin# mmc init;fatload mmc 0 0x81000000 linux

mmc1 is available

0x2950A4 (2707620) bytes read

Griffin# go 0x81000000

## Starting application at 0x81000000 ...

Error: unrecognized/unsupported machine ID (r1 = 0x86fbef00).

Available machine support:

ID (hex)	NAME

0000270f	griffin

Please check your kernel config and/or bootloader.
[Android Software/Hacking General [Developers Only]] yann2:
We had 3 people at LPL test out this fix, and unfortunately, for all three of them, the fix didn't seem to work.

Their reports are posted on page 47 of the CM7 Release Discussion thread.

Quote of one of the reports :
[Android Software/Hacking General [Developers Only]] zskullz:
I have had my tc-970 for two months and just installed the mod for the first time last week. It has improved the device 10 fold. :good:

I am having the charging issue tho, which is not a big deal i just charge it while it is on. I was going to try the fix or hope to try another if you get one shortly but i have to admit I am a bit of a Noob. i do have a fast learning curve(it only took me 1 try and 20 minutes to mod it in the first place). If someone gives me instructions on what to do with the fix files I will try it and report back if it would be useful. I am not sure what to do with the image file and would rather be clear on what to do then break something. I plan on staying on this version until it's fixed and am happy to help. Wish I could donate to help but I'm a poor college student(the lepan was a gift).
[Android Software/Hacking General [Developers Only]] yann2:
The fix is only a small patch, all you need to do is boot the tablet into ClockQorkMod, just like when you installed the CM7 Beta. once there, select 'Install zip from SD card', then pick the file location, install. Reboot and you are done.

Alas, the fix is not working at the moment, jerrystake reported the tablet seems to be in a boot-loop when you have the charger connect while the power is off. That will need fixing.

In the mean time, if anyone wants badly to have the charge while off functioning, Beta 6.0 works fine, just re-loaded that version and tested - perfect.
[Android Software/Hacking General [Developers Only]] jerrystake:
The kernel is designed to boot into a charge mode when powered down and charger plugged in. I don't know what changed but it appears cpu registers that are passed between the bootloader and kernel are corrupted or the wrong values. The kernel is going into a panic and rebooting. I suspect the charger boot script or init app but I have spent most my time on the kernel and don't know the android side like I should. I will try to look at today and see if I can see where the hick-up is.
[Android Software/Hacking General [Developers Only]] yann2:
Thanks, jerrystake, I had no idea the tablet had a running kernel when charging, powered off. Live and learn. :)

Been following your progress updates with the kernel work, well done; Hope you get your own version working. :)
[Android Software/Hacking General [Developers Only]] jerrystake:
I noticed that system init.rc is calling exec sbin/charger_man on boot-pause but file does not exist in sbin either ramfs or system. Don't know if it ever did but seems strange and will prob need cas to confirm either way..

EDIT: Cas, will you share your script for adding innocomm header to images?

2nd edit: nevermind I wrote one but if you have any other scripts you think would be useful thanks
[Android Software/Hacking General [Developers Only]] jerrystake:
Recovery

forget previous post I think the problems I have had with mount points was caused by me

I believe kernel needs cache mounted on fs instead of post fs

i.e.- mount yaffs2 mtd@userdata /cache nosuid nodev

it seems the kernel panics because the partition table is not setup correctly. The below console messages are cut and pasted to show that system partition ischeckpointed where cache and userdata is not

[ 123.975097] yaffs: dev is 32505859 name is "mtdblock3"

[ 123.975158] yaffs: passed flags ""

[ 123.975158] yaffs: Attempting MTD mount on 31.3, "mtdblock3"

[ 124.075714] yaffs: system: restored from checkpoint

[ 124.076110] yaffs: system: isCheckpointed 1

[ 124.158569] EXT4-fs (mmcblk1p1): recovery complete

[ 124.163757] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode

[ 124.164031] yaffs: dev is 32505861 name is "mtdblock5"

[ 124.164031] yaffs: passed flags ""

[ 124.164062] yaffs: Attempting MTD mount on 31.5, "mtdblock5"

[ 124.276123] yaffs: userdata: block 1294 is bad!

[ 125.659454] BCI: enable external fuel gaudge reset capacity

[ 125.721160] yaffs: userdata: backward scanned

[ 125.724090] yaffs: userdata: isCheckpointed 0

[ 125.869964] yaffs: dev is 32505860 name is "mtdblock4"

[ 125.869995] yaffs: passed flags ""

[ 125.869995] yaffs: Attempting MTD mount on 31.4, "mtdblock4"

[ 125.890472] yaffs: cache: backward scanned

[ 125.890563] yaffs: cache: isCheckpointed 0

I can give you a clean charge boot log if needed or you can see yourself by reverting back to beta6. I think you may need to create a new partition for datadata

Looking at this this morning I realized that though this is a charge kernel boot it looks like a normal boot as the charger init only mounts the system. I dont know I've looked at 10 ways plus sunday at mounts and am just getting confused. I will get a clean charger boot log and post it and just stay on beta6 until cas says if he is going to look at.
[Android Software/Hacking General [Developers Only]] jerrystake:
Just a word of warning.... If you have the original griffin.ifw on your sdcard from when you rooted and installed recovery but are using the lastest beta6.1 cm7 with the newer recovery installed do not use the vol- + power button to boot into recovery as the older recovery will boot off sdcard. There is differences in backup and mounts.. okay
[Android Software/Hacking General [Developers Only]] yann2:
Jerrystake, thanks for your post above - I had to read it a few times, seems you know something I did not :

...so - you mean that CM7 Beta 6.1 is now using a new Recovery method, a Clockworkmod flashed to the tablet itself?

I never knew that, just went to re-read cas_xp's release notes to check:

Which is pretty terse, but he did not mention a built in CWM.

Got to try that, if that's the case, I always have the SD card in, with the CWM files on it, been using it as usual. Have only done one backup of Beta 6.1, but not restored it, will discard it.

Can't wait to go home after work and test this out. :) Thank you.

On another subject - Can someone tell me if the TC970 CM7 Beta would support init.d Tweaks ?

I have been reading and tried out the Pimp My ROM package. It worked in my tablet, although there's so many options that I am note sure what they all do, which ones we can benefit from. Trying to find out, so I can write a Guide for it, on the TC970.

The releaser says it's intended mostly for ICS and JB devices, but Gingerbread is included, and there might be good tweaks for our tablets.

So, init.d works, or not supported? I know it is supported in the LP II tablets, TC979, not sure about the LP1 model. Thanks in advance!
[Android Software/Hacking General [Developers Only]] jerrystake:
I hope I did not mislead as I may have confused the release packages .. The last update that cas put up installs the recovery, ramdisk, iboot as part of the core update. The ramdisk fix is for copy of charger init file which he forgot in the update. The recovery version was bumped from .07 to .08 which you can see on bottom of display when in recovery. The difference in mounts are where cas is using the left over pop nand space which is faster 16 bit storage for datadata. He also cleaned up backup and restore making it much more reliable IMO. So what can happen is if you backup from .8 by opening recovery from the GB power menu then try to restore if you have problems by implementing recovery from boot with vol- plus power you will boot into the older recovery and the restore will most likely fail.

I am closing in on the charger boot issue but have befuddled myself over learning the yaffs file system lol..

I will package up a new griffin.ifw with the lastest recovery for those that wish to use the .8 recovery if requested.

Also note: A restore from an .7 recovery back up did not restore the .7 recovery on the device when I restored back to beta6.0; so curious if I am alone here.. Important for all those looking to restore from beta6.1 back to beta 6.0 be sure to use the same recovery the back up was done with.
[Android Software/Hacking General [Developers Only]] jerrystake:
Recovery

Okay, It looks like after I restored to a previous working beta6.0 back up with the same .7 recovery image the back up was made with, the recovery portion was not restored and the new v5.0.2.8 was still installed. I was under the impression that the original recovery version CWM based v5.0.2.7 restored all the back up; appears not. Not good- To be sure, I would use the sdcard griffin.ifw version recovery to restore a beta6 back up then use advance restore option to restore boot.img i.e (ramdisk) and recovery.img. This is only if your are going back to pre beta 6.1 update. You may want to wait for cas_xp to tell us if he thinks the charge issue can be fixed in the new 6.1. Hopefully yes as 6.1 appears to be worth the effort. For those that wish to stay on beta 6.1 I will post a new griffin.ifw for your sdcard to match the recovery used for 6.1 back ups...