yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] jerrystake:
UGH

I have had no problems since I did a full install after my first attempt. Have you looked at performance settings to be sure they are reasonable?

Just to be sure I flashed ICS alpha then did a fresh install of gingerbread with no problems. Can you be more specific about what freeze means and when it freezes? I will try to duplicate on mine if I understood a little more about how you get into your problem. Are you plugged into the charger when updating, if so, don't. Charge to 100 percent then unplug, wipe battery, reboot.

This is how I updated afer charging to 100 percent.

1. Boot into recovery

2. reset wipe & battery wipe

3. flash from sd beta5 rc1

4. flash beta 5.1_skype

5 flash beta 6_gps

6. wipe dalvik

7. wipe cache

8. power down

9. power up

If it hangs on power up go into recovery and wipe dalvik again and reboot.

Last thing, I originally started with the first update.zip then went to beta 5 and I have never had any problems wiping the battery stats as long as you charge to 100 percent then wipe the battery....
[Android Software/Hacking General [Developers Only]] wachoface:
Yea, it's all correct. I guess I should copy my files to PC, reformat card in android, put files back, and try again? By the way, I made my old backup with the old upside down CWM recovery. I, of course, now have the newer one. I don't know if that's why the boot.img is gone but, yep.

Update: I copied everything over, reformatted, put files back, and tried again. Funny thing happened, I had to hold vol + and power for recovery, lol. It told me the firmware was no good when I went with vol -. To the point; it didn't work.
[Android Software/Hacking General [Developers Only]] BoostedEK:
Well I never touched them but when I looked over it, they seemed fine.

Could you explain to me what ICS alpha is and what was the purpose of you flashing that then gingerbread?

By freezing I meant that the screen becomes unresponsive and whatever I was doing just froze. Although, the back, search, home, and menu buttons light up when I touch it. Sometimes it freezes if I immediately start performing tasks quickly right after it boots up after a restart and most of the time it freezes after performing tasks quickly as well or sometimes if I open up an app that requires loading.

I was not plugged into the charger while I installed everything. Right now my tablet is plugged into the charger and is fully charged. Its been working with the charger plugged in at full charge for a couple of hours now and I've been using it for quite some time. Usually it never lasted this long if i use it for a long period of time. So maybe that should tell me its battery related? Hmm...
[Android Software/Hacking General [Developers Only]] jerrystake:
ICS Alpha is a test rom for Android 4.0.3 that cas_xp ( provider of the gingerbread rom ) put together to test with while he waits for some driver and kernel source before he can finish the port. I was hoping I could use it for an application using wifi direct I am working on. So I was simply testing and does not have anything to do with your problem. As for your problem, after reading this last post I seem to remember having a similar problem but can't put my finger on any one thing I did to resolve. I do know if you don't exit clean from apps, such as using home button to exit and start another task, over time memory fills up and slows gui while memory is freed or swapped. Have you installed apps or running just the default apps? It is possible you have an unruly app. Have you looked at battery status to see if an app may be using more resources than expected. Try an os monitor app from google play and see if you can pinpoint what is slowing you up. I don't think the issue is your battery and sometimes you just need to let the device run a couple days of use. You also might try a different launcher. I like lightning launcher as a minimal launcher to see if default launcher is a problem. Anyway, I am testing mine after re-install from ics and see if I encounter what you are seeing.

I'm sorry I have not been more help but I am still willing to try if you are.

11am 7-4: I did a default install using the process outlined previously and now have an issue similar to what we have discussed. Seems scrolling at times is hesitant and touch is overly sensitive ie swipe and display starts to scroll only to stop. Also, sometime have to tap several times to select an item etc.. I've seen this in froyo before as well and believe I fixed by a reformat of SD. I will let you know what I come up with.
[Android Software/Hacking General [Developers Only]] whatid:
Are you happens to be using WEP? I had the same problem, it connect and disconnect continuously.

But once I changed to to use WPA2 (btw, router running DD-WRT) it works like a charm.

Also this http://www.androidtablets.net/forum...gingerbread-step-step-installation-guide.html (which is what I use.. thanks yann2!!)

This sums it up.. This is pretty much what I did except the battery wipe. And to expend the 'reset wipe' actually is

step 1: from the main CWM menu, select the 'Wipe Data/Factory Reset' option. Do it, nothing to worry here.

step 2: from the Main menu, select 'Wipe Cache Partition', do that as well.

step 3: From the Main menu once again, select 'Advanced', then 'Wipe Dalvik Cache'.

Now here is MY experience.... During the first time, everything went accordingly and boots. But it didn't start in virgin mode (new-user mode). Also the 'play store' icon just show a generic one but didn't do anything (and not listed in the application). Also wifi is giving me trouble (was using WEP with static IP eventually) but connection still iffy.

So I went into setting and do a factory reset... it reboots into CWM recover mode (?) I thought that was odd... so I re-do all the steps again (include wiping all 3 caches) flashed beta5->beta5.1->beta6. And this time I also go 'fix permission' (just an experience from my Samsung with CM7) to see if it 'fix' some weirdness...

Well it boot like last time, but this time the play store icon shows correctly on first boot. But still not started in virgin mode. No biggie, after setup WiFi (now using WPA2), run play store the first time, setup my account and everything is good to go.

GPS WORKS! (I use GPS Test)

The only annoyance (I thought I saw it somewhere but can't find it now) is the home button doesn't seems to work other than light up the LED. Soft home button is fine... I guess I just need to get use to that.

Default resolution is great.

GO Launcher works OK, with a few glitches. GO Weather widget for some reasons can't get update (but my network connection is OK, as I can access fb or flipboard)

Camera works.

Still playing with it... so far I am happy and recommend other to try!

THANKS cas_xp, chinabull, yann2 and others to make this possible! keep up the good work!!
[Android Software/Hacking General [Developers Only]] BoostedEK:
Well usually I always clear the cache and free up CPU memory usage via 2 apps called DroidSail Super Apps2SD and Super Tool Box 10+.

I've tried to run it on the default apps right after a fresh install of the ROM and I think it froze when I started performing tasks quickly after it booted up. I thought it could've been an app that was causing this but I'm not sure. I only downloaded the apps I used on a regular basis such as Facebook, Dolphin Browser, and a couple more other ones.

I just tried out OS Monitor and there wasn't anything there slowing me up. When i first started using this rom, I was using beta 5.0 for about a day with no problems other than the home and search button on the tablet only lit up but didn't perform anything. This problem started to happen after I updated to beta 6 but I did not update to beta 5.1 before I did it because I didn't realize there was a 5.1. The home and search button did start working after I flashed the beta 6 update though.

Then that's when I reinstalled everything again but still encountered the same problem. I'm using the beta 5.0 right now and I think it froze about 2 times after I flashed it. The home and search button is working as well. It still didn't freeze yet so I'm not sure what's causing this.

Update: About 2 hours later it force closed an app I was trying to open and randomly rebooted. After it rebooted, I tried to open up another app on my home page and I touched it once but it didn't open then I touched it again and it looked like it was going to open but it froze and I had to reset it via the reset button. And this is when I'm on 84% of battery, which it worked pretty good fully charged until now.
[Android Software/Hacking General [Developers Only]] MichaelBrock:
My son and I are working to put the latest beta on his 970. Somehow we missed the fact that 5.1 is an update and not the full beta. We succesfully got CWM installed, did the nandroid backup, and flashed from the zip file...however, that zip file was for 5.1 and needless to say did not work. The tablet is now stuck on the lepan logo after rebooting. Volume - + power button does nothing. We let the battery die, charged it back up and still Volume - + power button does nothing. The reset button does reset it but it always just returns to the same lepan logo screen. Unfortunately, the tablet was brand new and we had not enabled the debugging so ADB recovery doesnt' work (tried it anyway but it wont' find the tablet).

Any suggestions?
[Android Software/Hacking General [Developers Only]] jerrystake:
Try holding the Vol + and power button down the press the reset. After you release the reset, release the power while still holding the vol +. After a few seconds you should feel the tab vibrate then release Vol+. This will get you to the stock bootloader menu and from there you can boot into recovery. If not try using fastboot instead of adb at the lepan logo. I assume your win drivers are installed... Let me know if this does not help and I will help you get adb and fastboot working...
[Android Software/Hacking General [Developers Only]] MichaelBrock:
I'll that as soon as I get home for lunch.

I'm not familiar with fastboot but I'll look it up. Whether or not the drivers are installed is a good question. I am using Windows (vista). When I plug the tablet into the computer it does find the hardware and installs the drivers...however it doesn't prompt me for them. This could be the drivers that I originally installed back when I first got my original 970. I'll try uninstalling those and adding the hardware again (unless there is some other way to install the drivers than letting Windows do it when adding hardware).

Thanks for the help! I'm feeling bad for screwing up my son's tablet.
[Android Software/Hacking General [Developers Only]] jerrystake:
Don't feel too bad, you are only trying to give him a better tablet and you will find this rom does improve the experience greatly. It is worth the effort as far as I'm concerned. Many have experienced the issue you are having and in the end it will work out. Fastboot is the utility for working in the boot loader which generally is the state the tab is in at the Lepan logo.

I suggest you uninstall the Android ADB driver from the device manager by right clicking the existing adb driver, select properties..uninstall ( be sure to tick the delete driver box ) then manually install the drivers from the cmw root zip ''LePan_TC970_SuperOneClickv2.2-ShortFuse-modForTC970'. If the driver is not installed then go ahead and install manually. If widows doesn't give you the opportunity and installs whatever driver it finds, go ahead and uninstall and install so you know the correct drivers are installed. When using adb or fastboot be sure to use out of the directory created when you unzipped the Shortfuse mod. These drivers have the correct device Id for the Lepan and life is much easier when the correct drivers are used. There are several excellent guides on this site for correctly setting up the device and using adb and fastboot. Good luck...
[Android Software/Hacking General [Developers Only]] jerrystake:
BoostedEK

I am still interested in some of the issues you are having, not that I can or can not fix them but, they are things I have seen from time to time and can't put my finger on. My problem is that I am constantly installing Rom's or test app's I am working on that I don't generally have a stable system for any length of time any more. Still, I will relay any issue duplication I come across. I am really interested in how the state of the battery effects system performance. I am suspicious of power management handling and am looking at what the code has to say.

---------- Post added at 12:14 PM ---------- Previous post was at 11:54 AM ----------

Has anyone been able to connect to router using DHCP and not static using cas_xp ics alpha rom. I have try several different routers ( D'Link and Trendnet ) in most any configuration you can think of. My Kindle Fire running Energy's ICS 4.0.4 Rom works fine with bit rates of down loads running up around 8 Mbps and 135 Mbps to N router. I have not looked into the wpa_supplicant configuration yet but hope to save time in case anyone has already solved.
[Android Software/Hacking General [Developers Only]] BoostedEK:
Well I kept getting random freezes so I used your method that you mentioned earlier to reinstall the ROM and it only froze one time. After that I downloaded another launcher and its been working pretty good since then. The only problem I have right now is sometimes the screen is overly sensitive or I have to tap several times to select something, as you mentioned earlier in this thread as well.

I'll keep you updated if I experience the same issue again.
[Android Software/Hacking General [Developers Only]] jerrystake:
I notice the same screen problem especially in froyo but not so much in gingerbread. I have noticed that it is much worst when I use the dolphin browser. At any rate glad to hear you are making progress.
[Android Software/Hacking General [Developers Only]] MichaelBrock:
This worked like a charm! Even while charging it brought me to the stock bootloader. From there I booted to recovery and that took me to the CWM boot loader. I copied over the correct zip file and cm7 looks like it is installed. However, after rebooting it just turns off and requires a reset (after which it reboots and turns off again). Might be a battery level issue. I'll let it recharge a bit.

Thanks a bunch!
[Android Software/Hacking General [Developers Only]] jerrystake:
Great, you may need to re-calibrate your battery but lets wait 'till you get a full charge and go from there. I firmly believe that the battery history causes most the problems we see after updates but I can't prove that .. yet. I am working now to get a better idea of how the power management in Android works. Hope your son enjoys.
[Android Software/Hacking General [Developers Only]] BoostedEK:
Okay well after using it for a couple of days with no problems, it's starting to happen again.

At first, every application that I opened started force closing so I rebooted. After it rebooted, I tried to open an app and it froze. I had to reset this thing about more than 10 times because it kept freezing. I couldn't get it to power down or restart by pressing the power button because it would freeze at 'powering down...' or 'rebooting...'

Then I left it sitting for about 5-10 minutes after resetting it and it worked when I tried to power it down. So I booted it up into recovery and fixed permissions (I fixed permissions when I installed this ROM but I decided to do it again).

I powered it down then up and left it sitting for about 5 minutes because every time I reboot it freezes if I immediately start doing something. Tried opening up applications and it worked fine. Then tried to open up another app to clean cache and it froze again. -_-

Pretty annoying.
[Android Software/Hacking General [Developers Only]] cas_xp:
Hmm, it is a pretty annoying issue. Any log of it?
[Android Software/Hacking General [Developers Only]] BoostedEK:
Well I never looked to see if any issues showed up on any logs. How would I go about doing that?
[Android Software/Hacking General [Developers Only]] jerrystake:
You can use this: adb logcat -d -v time > recentlog.txt or use something like catlog from google market.

If you try to start apps or use the device too soon after boot you can have problems if the sdcard has not finished mounting. You may see a sdcard icon on the status bar until done. Some times it is slower then other. I suspect your sdcard but, maybe a log will show something.
[Android Software/Hacking General [Developers Only]] BoostedEK:
So when should I check the log? When this issue happens I have to reset it and won't that clear anything that shows up if I check it after it boots back up?
[Android Software/Hacking General [Developers Only]] cas_xp:
Whenever you see issues or find freezes, you can use 'adb logcat' to see what happens.
[Android Software/Hacking General [Developers Only]] BoostedEK:
I appreciate the help and responses I've been getting.

Well I'm new to adb logcat or any other logcat so I'd appreciate some assistance on that part. What I have done was typed in adb logcat on Terminal Emulator but it said permission denied. I tried out CatLog from the play store and I'm not sure what to look for when this issue occurs as there are so much writing.
[Android Software/Hacking General [Developers Only]] cas_xp:
No, not in Terminal Emulator. You should connect your tablet with USB cable to a PC and your PC must have adb program (which can be installed from android.com SDK), then you run "adb logcat" by a terminal window (Linux) or command line window(Windows).
[Android Software/Hacking General [Developers Only]] jerrystake:
What Kernel Version?

Help me out. Through all the updates and rooting, has the kernel ever been reflashed by any updates? My kernel version is 4561 so maybe some problems some are seeing and others are not with gingerbread could be because of different kernel versions. Anyway this is what uname - r reports on my tablet. All along I was under the impression that the kernel binary was modified for ginger bread but it appears to me only the griffin header was patched to allow a cwm recovery to be added. Am I wrong and if not what version kernel is others using? adb shell uname -r will tell ya..
[Android Software/Hacking General [Developers Only]] whatid:
I have been using Beta 6 for some time now... In general it is all good and thanks everyone for the hard work and lead to this point... Just a few minor issues mostly related to UI. But there is one slightly annoying issue with WiFi, it seems to be not as sensitive as the stock firmware during initial connection.

With stock firmware, I can initiate connection everywhere in my house. Even at the far end from the AP without problems. However with beta 6, it sees the AP sometimes but it just keep trying and won't connect. I have to walk all the way very close to the AP to get it connected. But once it is connected, I can move back to my original position and use it with out problem until I turn off wifi and need to reconnect. (note: wifi doesn't not drop once it is connected) The problem seems like in order to have wifi connected it need to have a pretty strong signal...

beside that, the 'hard button' 2 out of 4 sometimes stopped working until a reboot. Oh, how do I get the 'status' bar on the bottom back? Sometime it just disappear when I turn it on.. normally that's not an issue, but when the hard buttons are not working, it become annoying.

Thx
[Android Software/Hacking General [Developers Only]] along1968:
I have the same wifi issue. Plus mine freezes up occasionally when I charge it. Apart from those 2 things, its great.
[Android Software/Hacking General [Developers Only]] jerrystake:
What kernel version are you on? I recently upgraded mine to the 4749 version that is floating around and have better wifi and touch screen performance. I cant seem to find any change logs on any lepan updates so it is hit and miss. I do know that I will never do business with lepan or innocomm again. They are making millions off the back of the open source community and not contributing anything in return. TI is just as bad by not holding lepan to their own lic. agreements. Anyway, try long touch on home screen and select launcher actions then show/hide status bar. On some full screen apps the status bar will get hidden and the show status icon will get it back...

I have been working on compiling a new 3.0 base kernel for the LP 970. I have so far been able to gather most the driver sources needed but lately have lost interest as my 30 pin usb cable connector is intermittent and has been since I bought it. I just dont know if it is worth opening up the device or buying a connector and wiring up jtag or uart3. If anybody has any device hw io or memory mapping figured out Ill take whatever info I can get...Right now I am looking at the hynix pop H8KES0UU0MER-4EM init.

Also for those interested here is link for 4749 lepan update thanks to yann2 who has hosted the file: http://files.inbox.lv/ticket/a57a38da011048ec0e261a49f0febe35a19c1cc7/LePan_TC970_FW_4749.zip

To use you may have to install 4749 then re-root and re-install beta 5,5.1 and 6. or flash directly which I would be sure you are sure you know how to do.
[Android Software/Hacking General [Developers Only]] BoostedEK:
What do you mean flash directly? Directly from CWM? I would like to try this out but if you mean flash directly, I won't lose anything right?
[Android Software/Hacking General [Developers Only]] 769151238:
When is the time beta 7 will show up?
[Android Software/Hacking General [Developers Only]] yann2:
I hear you, and have mentioned to cas_xp in the pastt about the wifi being less than it could be. I made a detailed bug report back in Beta 2.

In my opinion, wifi was quite improved in the 4749 firmware, compared to the older stock versions; I did quite a bit of testing with file copying from a machine inside my network, and it worked much better than CM7 Betas.

The CM7 Betas were built based on the Le Pan 4626 firmware, and cas_xp tried to use the 4749 wifi files at one point, but had some problems. Since there were other things needing work at the time (video playback for example), it was not pursued further.

Cas_xp has spent months working on this project, and from the last Edit in the Original Post, I have the impression he's not planning to spend more time into it.

Would love if he did try once again to use the wifi files from 4749 firmware, and maybe make a final Beta 7 release with a complete ROM, like Beta 5 was.
[Android Software/Hacking General [Developers Only]] cas_xp:
OK, I will try to re-integrate 4749 WIFI firmware with beta6, but I can't promise when.
[Android Software/Hacking General [Developers Only]] yann2:
:)

Thanks, cas_xp, that would be great. Look forward to it, no rush.
[Android Software/Hacking General [Developers Only]] jerrystake:
cas_xp is git://github.com/cas-xp/device_lepan_griffin.git, cm7 branch, device tree the one you are using to build the current rom?
[Android Software/Hacking General [Developers Only]] cas_xp:
yes, it also contains some patches of components like framework etc.
[Android Software/Hacking General [Developers Only]] jerrystake:
What am I missing? The framework patch acts on /core files that are not in git tree. Where is the core and media source files? If they are generated somewhere I don't see where...
[Android Software/Hacking General [Developers Only]] cas_xp:
The framework patch(and other patch) acts on CM source tree, you need sync it. Read this
[Android Software/Hacking General [Developers Only]] cas_xp:
I did try 4749 kernel with Wifi firmware, but it failed again.

1) There is new WIFI calibration introduced in android framework in 4749, but I don't know how to implement it.

2) Once I switch to 4749 version, there are a lot wifi doCommand error with -1 value, and I double check it, it can't get RSSI value and it was unable to associate with any AP

3) Also, the kernel 4749 is not very stable on my tablet, the ADB connection most of time is offline state.

So, I will stay in 4431 kernel and WIFI firmware in CM7.