yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] yann2:
Hi, Jerry,

Yes, I like participating in Forums, and could post a question for you in the other ones (lepanlife.com, Androidtablets.net) - but I don't think anyone reading there would be able to help you on the kernel questions. You are most welcome to join these sites and post a thread if you like. :)

The display in the TC970 seems to be a stumbling block, for a while everyone's first bootable compiles were upside down; that was the case with Clockworkmod for TC970, and with CM7 Beta 0. Cas and chinabull managed to get their screens right-side up, but other ROMs projects I have tested did not. :(

(LEWAos and MIUI ports for TC970, both stuck in the upside down video problem).

Maybe send chinabull a PM here on XDA? maybe he can offer some suggestions.
[Android Software/Hacking General [Developers Only]] cas_xp:
I think Jerry is talking about Linux display driver not Android display issue. I can't do anything more without serial port available. Maybe somebody can make one for me, I pay it. And my lepan connector is kind of broken on left side but USB is still working. My old serial cable can not see anything even corrupt char before.

The first step for me is to create a bootable SD with stock kernel and ROOT file system. Then we can try to replace the kernel so it won't hurt NAND image. Ideally we can see DUAL boot but we don't have iboot source either.
[Android Software/Hacking General [Developers Only]] jerrystake:
I can't believe the weather has been great here in Florida until this morning, election day, and it is pouring rain Jeez. Indeed I was speaking of the display driver and have come to the conclusion that the FPGA must be a frame buffer and may kick up the clock to the panel. The spec calls for a 100 mhz clock but the existing driver is clocking at 54 mhz. Half the minimum recommended clock rate and I think omap max out at 75. As for iboot I have used it to read and write to nand from mmc0(sdcard). It does most all that uboot does except I have not been able to save environment varables but can set them and load and exec kernel from memory. Maybe I should try to get a uboot working if I can fool iloader to allow me to start it. In our case I think iloader does most all the grunt setup of memory and nand.

If you could get a root file system to boot on sdcard that would be great. Today, after I cast my wet vote, I am doing nothing but try to get display driver working. As for your cable, I'm not sure what you need. Is it the cable connector that is broken or the connector on the device? However, once you get the signals broke out you still need to convert the signal voltage from 1.8v thus requiring a voltage converter of some sort. Either a mosfet/voltage divider circuit from sparkfun or a serial to usb adapter like bus pirate. You may also be able to configure the kernel to use the usb. I think I saw some write ups on the subject and I believe the twl5034 can also be configured for a 3 pin interface. Much easier to buy the breakout 30 pin connector and use serial uart3 with voltage conversion or serial to usb gadget. Also, if you open up the case the uart3 test pads are right on top of pcb then solder three wires to the pads.
[Android Software/Hacking General [Developers Only]] cas_xp:
My connector on the device is broken on the left side (face to display) it won't affect anything like USB, charger yet. Can you post a photo of your wire with device and some diagram of wire. I just simply connect pin 17/18 as Uart two pins and connect it to USB2Serial port. I am afraid to open my tablet and solder some wires out.
[Android Software/Hacking General [Developers Only]] cas_xp:
GPIO

GPIO 25 (gps_reset ): out hi

GPIO 29 (GPIOB_Q24120_DET ): in lo

GPIO 34 (gps_on ): out lo

GPIO 35 (eMMC_PWR ): out hi

GPIO 37 (speaker_switch ): out lo

GPIO 38 (VBUS_HOST_EN ): out lo

GPIO 39 (GPIOB_Q24120_EN ): out lo

GPIO 53 (GPIOB_Q24120_STATE1 ): in lo

GPIO 54 (GPIOB_Q24120_STATE2 ): in hi

GPIO 55 (fpga-done ): in hi

GPIO 56 (orientation_lock ): in lo, irq-216 bothedge

GPIO 98 (hynix253_reset_gpio ): out lo

GPIO 152 (wifi_irq ): in hi, irq-312 falling wakeup

GPIO 153 (INNOCOMM_TP_IRQ_GPIO): in lo, irq-313 rising

GPIO 154 (INNOCOMM_TK_IRQ_GPIO): in hi, irq-314 rising

GPIO 156 (kim ): out lo

GPIO 157 (twl-msecure ): out lo

GPIO 158 (ext_mute ): out lo

GPIO 159 (headset-hook ): in hi, irq-319 bothedge

GPIO 162 (GPIOB_Q24120_ISET ): out lo

GPIO 163 (VBUS_HOST_FLT ): in hi

GPIO 164 (eMMC-RST# ): out hi

GPIO 167 (hynix253_standby_gpi): out hi

GPIO 177 (YAMAHA_YAS529_RST ): out hi

GPIO 182 (GS_3V3 ): out hi

GPIO 186 (wifi_pmena ): out hi

----------------------------

gpio-25 (gps_reset ) out hi

gpio-29 (GPIOB_Q24120_DET ) in lo

GPIOs 32-63, gpio:

gpio-34 (gps_on ) out lo

gpio-35 (eMMC_PWR ) out hi

gpio-37 (speaker_switch ) out lo

gpio-38 (VBUS_HOST_EN ) out lo

gpio-39 (GPIOB_Q24120_EN ) out lo

gpio-53 (GPIOB_Q24120_STATE1 ) in lo

gpio-54 (GPIOB_Q24120_STATE2 ) in hi

gpio-55 (fpga-done ) in lo

gpio-56 (orientation_lock ) in lo irq-216 edge-both

GPIOs 64-95, gpio:

GPIOs 96-127, gpio:

gpio-98 (hynix253_reset_gpio ) out lo

GPIOs 128-159, gpio:

gpio-152 (wifi_irq ) in hi irq-312 edge-falling wakeup

gpio-153 (INNOCOMM_TP_IRQ_GPIO) in hi irq-313 edge-rising

gpio-154 (INNOCOMM_TK_IRQ_GPIO) in hi irq-314 edge-rising

gpio-156 (kim ) out lo

gpio-157 (twl-msecure ) out lo

gpio-158 (ext_mute ) out lo

gpio-159 (headset-hook ) in hi irq-319 edge-both

GPIOs 160-191, gpio:

gpio-162 (GPIOB_Q24120_ISET ) out lo

gpio-163 (VBUS_HOST_FLT ) in hi

gpio-164 (eMMC-RST# ) out hi

gpio-167 (hynix253_standby_gpi) out hi

gpio-177 (YAMAHA_YAS529_RST ) out hi

gpio-182 (GS_3V3 ) out hi

gpio-186 (wifi_pmena ) out hi

GPIOs 192-209, platform/twl4030_gpio, twl4030, can sleep:

gpio-192 (mmc_cd ) in lo irq-384 edge-both

gpio-194 (h2w ) in hi irq-386 edge-both

gpio-198 (PWMB-EN ) out lo
[Android Software/Hacking General [Developers Only]] jerrystake:
I have all the mux and gpio's setup in board-griffin-coremux.c in source. Also in the griffin-doc sub directory you will find some notes, device io/memory layouts and TRMS. Currently all the regulators are initing and you can see where I documented the individual mux signals for the gpio's. I think I have accounted for all of them and verified most. Such as gs3v3 and emmc regulator init. If you have pins 17/18 broken out and available then you are home free except you will still need to level shift the 1.8v to 3.3v or 5v and connect them to a rs232 serial port. You can't use them directly into usb port as they are from the omap uart and fit the rs232 signaling protocol. So, you still need an rs232 port/adapter on your computer or an rs232 to usb converter. I can draw you a schematic of how to do the hardware but you will need to tell me how you want to go. A. Signal conversion to serial adapter or serial to usb. Either way you need some components and maybe an electronics store near you has what you need.

Heading to the polls now to vote will be back in hour or so...

EDIT I was looking at this and should have said serial and not rs232 as rs232 is a standard. Some adapters will work at 5 volts just depends on the maker.
[Android Software/Hacking General [Developers Only]] cas_xp:
connector and cable

I attach two pictures of device connector and cable I made. USB function of the cable is still working.
[Android Software/Hacking General [Developers Only]] jerrystake:
Okay, looks like you still have problems there my friend. It looks like you have the rs232 to usb adapter and I can only assume you have wired the correct tx,rx signals. You still have to deal with the voltage difference. The rs232 ( the db9 connector ) standard requires + and - 5 to 24 volts. The Lepan puts out 0 to 1.8 volts for signaling. See the problem? You still need to level shift the Lepan signaling, no way around it. What is the model of your usb adaptor? I will verify it's signaling requirements but, even if it is a loose standard, the fact still remains: it wont be compatible in the current configuration. Sorry. If the usb adaptor you have pictured by chance did take ttl signal voltages of 0-.7 volts for logic 0 and 2.5 to 5 volts for logic 1 then still need to kick up Lepans' 1.8 volt logic 1 to 3.3 to 5 volts. I'm using a Arduino http://www.arduino.cc/ that I modified using an op amp circuit I built to power the serial bus on the device at 1.8 volts. I'm only using it because I happen to have one. You would be better off with a bus pirate type device and even then you may need to build a circuit to run at 1.8 volts. There are several web pages that describe your problem which is the Lepan uart3 uses 1.8 volt signaling which you must account for. I also think now you can buy the cable with the conversion built in on mouser or digit key. I hope I have helped ya cas..
[Android Software/Hacking General [Developers Only]] GnatGoSplat:
Could you use a USB to TTL serial adapter and just use pull up resistors connected to VCC to raise the voltage of logic 1 to 3.3V?
[Android Software/Hacking General [Developers Only]] jerrystake:
I see what you are saying and maybe on the Lepan UARTS TX only. The schematic shows the uart is isolated with only a 5.5v over voltage clamping diode. So to read only, it may work. The uart is only sinking logic low so as long as you keep the resistor value high to limit current, I would not be afraid to do it. I'd start at 100k and work my way down. Depends on the receive circuitry as to how much current it needs to detect logic high.

WARNING: Do not hook up to rs232 directly as it may put out a negative sense voltage. Depending on the rs232 device because these days, no one follows standards in the PC world. Get out your multimeter and measure. As a matter of fact, just buy a couple converters from spark fun, a couple bucks, and be safe.
[Android Software/Hacking General [Developers Only]] cas_xp:
Thanks Jerry. I am not good at this, I will find a hardware guy to help me out.

BTW, boot from SD is ready but I don't have to script to create SD image. It needs to press VolumeDN + power to activate. I manually create the SD image/partition.
[Android Software/Hacking General [Developers Only]] jerrystake:
Thats the way I do the startup ie as if booting recovery. With the iboot such as it is that is the only way except loading the kernel into memory from iboot console then setting the environment variables and run in place. Today I did boot into recovery from my kernel and from muscle memory lol (LCD not working) used the vol and power keys to shut down. Really is meaningful that I can boot as far as needed to start android. I just need to get display working and for some reason I get

cannot apply mgr(tv) on inactive device

<4>omapfb omapfb: failed to apply dispc config

omapfb omapfb: failed to apply dispc config

<4>regulator_init_complete: VPLL2: incomplete constraints, leaving on

Why it wants to init tv manager, beats me. This part worked until I moved to encores linux from a previous kernel clone I got a few months ago.Same 3.0.8 version. I'm thinking of moving to a newer base or just working through what I have now. Bottom line is once display works I am pretty sure I can exec from nand.

We may need to adapt a u-boot over to lepan. Life would be easier and I may look into that today. Could you let me know what steps you use to set up sdcard partitions?

I will see what I can come up with to help you get console working to usb.
[Android Software/Hacking General [Developers Only]] cas_xp:
My SD has three primary partitions: FAT32, EXT3, EXT3, the FAT32 will be place of MLO and griffin.ifw, and the first EXT3 is for /system and the second is for /data. See my init.rc for this.

And I guess this one is what I need:

http://www.digikey.ca/product-detail/en/TTL-232RG-VREG1V8-WE/768-1070-ND/2441359
[Android Software/Hacking General [Developers Only]] jerrystake:
Yes, it is perfect but kinda pricey. I still stand by my 10.00 donation to help defray cost. Just be sure to double check on checkout the correct cable part number as I have had problems in the past over such things. Try mouser's, sometimes they are far cheaper on certain items. Thanks for the init stuff. I will download now and take a look. Also, I am considering shifting to 3.0.37 tonight to see if that helps on my DSS woes.. Let me know about cable..
[Android Software/Hacking General [Developers Only]] medievil1:
if it will help get a working ICS in the future, I'll contribute $10.00 as well
[Android Software/Hacking General [Developers Only]] jerrystake:
Do you have to setup symlinks to busybox for the binaries in system?

side note: I've been working on adb and once I can get memory allocate right in kernel and setup a ram console I think it should work. I don't understand why encore doesn't set up ram console unless newer kernels don't require. It seems you can not make many conclusions for newer kernels based on the pre 3.0.0 kernels.
[Android Software/Hacking General [Developers Only]] cas_xp:
Yes, it is pricey and it is almost $40 after shipping and tax. Compare to this less $150 tablet, it is not worth.
[Android Software/Hacking General [Developers Only]] cas_xp:
I have symbol link to busybox in /sbin and /system/xbin.
[Android Software/Hacking General [Developers Only]] GnatGoSplat:
Looks like this guy managed to connect 1.8V serial to a standard USB to TTL serial adapter using resistors.

http://pepijndevos.nl/2012/10/26/sparkfun-18v-usb-to-serial.html

He doesn't provide a schematic, but it looks like it should be relatively easy and very cheap to do.
[Android Software/Hacking General [Developers Only]] jerrystake:
That will work to a point. The voltage divider is wrong and should be a 1/3 ratio. Second, the reason he had to disconnect the led's was not 'voltage leakage' whatever that is, but the current draw from the led's and i/o drops the voltage across his voltage divider causing the i/o voltage to drop. The right way would be to connect the voltage divider to an op amp to supply enough current to run the i/o. If you even use a 1k divider you still would not supply enough current to reliably drive the i/o. But, it is the way I do mine, same ft chip but mounted on an AVR Arduino. Right concept, wrong implementation...
[Android Software/Hacking General [Developers Only]] cas_xp:
I placed an order for that cable from digi-key anyway.

The question is: we probably can fix display issue in new kernel. But do we have enough time to solve all issues before this tablet fades out?
[Android Software/Hacking General [Developers Only]] jerrystake:
Apparently the omap3630 has a chip bug that effects the DSS pclk that was patched in old kernel but not part of current kernel. Drats, what else, this is never ending. Off to find a specific 3630 kernel to work with. Encode uses a 3621. Maybe current zoom3.

EDIT: Just caught your post while doing this one. I don't know, I do it to show it can be done and to feel better about Lepan screwing us on source. I have a Kindle Fire I could fool around with but what point is that. A start to finish kernel without vendor support for hardware configuration is an accomplishment don't you think?

Another Edit: Besides if I don't finish this and get some donations, I won't be able to feed my children in December! lol
[Android Software/Hacking General [Developers Only]] fibregod:
donation

Here's a donation to you Cas to defray costs....hope you and Jerry can work this out, I haven't a clue what you guys are say (wish I did) but I'd love for this to work out for our 970's....hope others donate as well..
[Android Software/Hacking General [Developers Only]] jerrystake:
I think cas wonder's as I do time to time if it is worth all the work on a tablet that is rapidly becoming obsolete by today's standard.
[Android Software/Hacking General [Developers Only]] fibregod:
I hear your frustration. I know it may be obsolete by current standards but it's what a lot of people have and can afford. I wish that I could do the things you and Cas are doing but I'm too old to get even close....just know that while a lot of us lurk...your efforts are most definitely appreciated...don't give up
[Android Software/Hacking General [Developers Only]] jerrystake:
Thanks for the encouragement. Cas doesn't strike me as the type of guy who gives up, just practical.

This latest boot clip is encouraging:

OMAP DSS rev 2.0

*** GRIFFIN LCD panel driver init

*********** dpi-init

**** panel_probe

dsscomp: initializing.

misc dsscomp: display0=griffin_panel

misc dsscomp: found 1 displays and 3 overlays

Now just need to figure out the frame buffer support and ram console.
[Android Software/Hacking General [Developers Only]] cas_xp:
Thanks man. Also to the others whom donated to me before!

The tablet is old and you can feel it in youtube with HD. Even worse there is no support from manufacture and that is the reason I gave up video camera in Gingerbread. And It took me more effort to figure out audio support in Android without Kernel source.

So, the conclusion is: don't buy LePan product (or similar product from the company not following GPL) any more. Let them die.

I bet LePan II will not have any chance to upgrade to Jelly Bean. But Nook Color does!
[Android Software/Hacking General [Developers Only]] cas_xp:
Please commit your change to github so everybody can easily follow you and put effort on something else. Cheers.
[Android Software/Hacking General [Developers Only]] sockbot:
Very happy to see that this is still in development after all this time. Beta 6.3 fixed some issues I had with video artifacts and draining battery when on standby. Chipped in a small donation!
[Android Software/Hacking General [Developers Only]] Mrmikeoxlong:
Just want to make sure

I'm very new to the android OS so I really don't understand exactly which each new update does, but I am mainly pondering is the latest update for the most part, the full version of gingerbread.
[Android Software/Hacking General [Developers Only]] jerrystake:
I need to be committed for even messing with this device. I really don't have anything to commit as I have mostly been placing custom routines all over kernel trying to understand how some of the hardware was configured by innocomm. For instance, I could only get the Hynix MTD NAND to work using the omap-nand driver as if the Hynix is a small block device. It absolutely will not partition the nand using the large block page read and write command sequence. The device reports itself as a large page ONFI 1.0 device but won't let me read the 6 byte advanced ID or the ONFI parameter page. Patching out these checks and setting the driver command routine to small block mode allows the device to partition and is generally happy. I don't know if it is because of the way the device was originally set up or I am missing a piece. Moreover, I can only read the 4 byte O.N.F.I. signature ( not parameter page ) in 8bit addressing mode though this device purports itself as an 16 bit device. Strange isn't it.... Any clues? I am at the point I may as well go ahead and write our own boot loader and re-partition my pop nand. I'm not even sure if old kernel is using the hardware 1bit ECC supported by this NAND. I just don't get it, this chip is used by several other devices using the omap driver and I have taken the gpmc timing registers from the beagleboard, overo, igep xloader so I am pretty sure gpmc is not issue.... onward
[Android Software/Hacking General [Developers Only]] jerrystake:
Cas, This feature of omap concerns me:

In security-enabled production devices, secure flash and secure boot is enforced to achieve

high level of security. Secure flash ensures that the OEM’s OS image is correctly and securely

programmed into flash memory at the factory. Secure Boot ensures that the “authorized”

OEM’s SW (signed by the OEM) and optionally the OS image (optionally signed by the OEM) is

authenticated prior to execution. This prevents the code from being modified by unauthorized

entities or the external memory NoVo from being tampered with. It also prevents the execution of any forged or spoofed software code

What are the chances we are spinning wheels here? I don't know a way to verify what security features are implemented by Innocomm if any but, it is sure strange that every kernel feature I try to implement is a battle.
[Android Software/Hacking General [Developers Only]] D4747:
after updating to 6.1, i ran into some issues with 'phone low on space' notifications. i had to partition the sdcard thru the recovery menu (did 2gb's) and use S2E to move all apps and cache's there to fix it.

i also get issues with the status and softbutton's bar crashing sometimes.

i wanted to update to see if cifsmanager would work with this kernel. unfortunately it didn't. cas_xp, do you think you can somehow include it in an update? it may not be possible, i don't know how these things work. with cifsmanager, one will be able to see a folder on their PC as a network shared folder on their lepan, no more moving files around. it's a feature i've been dying to have since i got my lepan, but found it never supported out of the box. it requires either a cifs.ko file (i've tried using onces for other devices from other threads, hasn't work) or for something to be built into the kernel.
[Android Software/Hacking General [Developers Only]] jessieca:
problem in flashing

is there someone can help me.. im a newbie and i want to try it..

i just extract the griffin and copy the other file to my sd card..

when i hold the -volume and power button in apears the CMW. i made back up, install the gps sign, up-ram sign and skype but when i try to update it.. it failed something appear so i chose to power off..

when i open it again.. its stuck in the logo of le pan

what shall i do??

its a total bricked!!
[Android Software/Hacking General [Developers Only]] GnatGoSplat:
Try holding volume up, then press power for a few seconds while still holding volume up. It should hopefully boot back into CWM. Then you can either try to restore your backup or attempt to flash again and let us know what the error is.

You didn't mention flashing the main ROM, under the "Beta 6.1" link on the main post. It sounded like you were just flashing the updates without the main ROM, maybe that was your initial problem?
[Android Software/Hacking General [Developers Only]] jerrystake:
Probably need to do a reset by using paper clip to momentarily press reset while holding VOL+ until you feel long vibration, then select boot to recovery.

This is best way to recover
[Android Software/Hacking General [Developers Only]] jessieca:
.. battery easy drain

Yes its too late to realize it.. that I missed the file for beta 6.1.

The problem I got it was stucked in le pan logo I wait couple of hour still sticker even I reset the button at the back no use

Even the holding volume and power button. Didn't work..

Wat I did I just download and copy the original firmware from the support of le pan to my SD card

I don't have the back up because I erase it in my panic

But then I found a tread on using superclick one with msdos

so I get back the adb recovery mood without pressing the volume and power button

In recovery mode I choose the power off and put the SD with original firmware

Then press volume and power button and thanked God it worked!

And flashed it to back to original firmware

I don't understand how 6.1 installed about that odexed

So I decided to install beta 5 and luckily

I successfully flashed the beta 5 along with Skype sign and GPS

But I notice that my battery easily drain

Do I need to install the up ram 6.3 charger? Because I'm not sure if it would crash my le pan