[SeaMonkey76]

After flashing a 7" netbook with the M001 ROM the battery indicator is reading incorrect. Is this set in the scriptcmd file on the line that reads "setenv battvoltlist 6774,6889,7377,7498,7538,7599,7650,7698,7763,7821,7939"?If I read the battery voltage both charged and at the point where the netbook turns off can I edit the above and recompile the file?Thanks

 

[enotar]

interesting idea!I am interested too!

 

[h8isgr8]

How many cells does the netbook use?

 

[vtpad]

Seems likely that those are the actual representative battery capacity voltages x 1000 for two Lipos in series. Therefore probably correct as reference voltage levels. Changing them would mean you are using an arbitrary range instead of a standard lipo voltage range. The greater likelihood is that some sensing logic is reporting a wrong value to compare with these numbers, or the display logic is wrong, or even possibly your batteries are starting to fail.Since we don't know yet how the charge circuitry logic works and whether the machine has a firmware cutoff possibly in addition to hardware safety voltage cutoff and monitoring, it is not a good idea to mess with values arbitrarily. Lipos can be damaged, burn, or even explode if not very precisely charged. When someone comes up with a full analysis of the Eken charge circuitry and logic, then it will be easier to say that customization is reasonably safe to do. Without that knowledge, you risk more than just a broken tablet. You risk your life and those of people around you.I don't want to repeat the lipo fire and explosion urls here that I posted elsewhere in this forum, but you can find them under another one of these battery topics. Please read that before altering any aspect of battery monitoring, circuitry, battery firmware, or even replacement batteries.Ye,s it is possible to work on Lipo charging circuitry, or firmware, or replace batteries with proper in depth technical knowledge of Lipos, their requirements, the dangers, and full details of the Eken's charging system. But I haven't seen that from anyone here yet. Maybe it will come. I would welcome it. Knowledge is good.

 

[SeaMonkey76]

@vtpad Excellent notes on the batteries.Some observations about the netbook.1. When powered off and charging the charging light does go off after about 4 hrs (Possibly indicating full charge)2. When fully charged the machine runs for about 2 hrs. The battery level starts at 25% and goes down from there.

 

[SeaMonkey76]

Swapped batteries for a known good one and I get the same results. This Netbook (WM8505) was originally 1.5. Could going to 1.6 throw the battery gauge off?Does anyone have a copy of 1.5 for a WM8505? I have one that is supposed to be for WM8505 (DL from that bento linux site), but the file inside looks to be labeled as 8510 and hangs at the point where it upgrades the file system.ThanksUpdate - Going to Win CE 6.0 and then to Android 1.5 allowed Android to load. Going to see if this resolves the battery issue.

 

[vtpad]

Could going to 1.6 throw the battery gauge off?

Yes, conceivably. But the real question is, did it?If others who have gone from 1.5 to 1.6 do not have the same problem, then it probably didn't.Also do you in fact have 1.6? Did you do a checksum before installing the new version?Also, what do you mean by continually saying netbook? This is an Eken M001 tablet, right? You're in the Eken M001 forum.

 

[SeaMonkey76]

The device is a "netbook" running M001 ROM.

 

[rizapn]

[quote name='SeaMonkey76;9726]After flashing a 7" netbook with the M001 ROM the battery indicator is reading incorrect. Is this set in the scriptcmd file on the line that reads "setenv battvoltlist 6774' date='6889,7377,7498,7538,7599,7650,7698,7763,7821,7939"?If I read the battery voltage both charged and at the point where the netbook turns off can I edit the above and recompile the file?Thanks[/QUOTE'] Yes, battery indicator is depend on these environtment : battvoltlist and basevolt ... To correct it, you must read the original value of those environment (from the same device), and write it to the modded device.I did that before, and it works perfectly ...If you have the (original) value, you can use setenv command using Better Terminal to write it to your modded device ...

 

[SeaMonkey76]

@ rizpn - Thanks! That was the answer I was looking for

 

[ffxx68]

Hi. I also have a 7'' netbook which I flashed with a WinCE ROM that must have been derived from one of the Eken versions... no one knows the exact origin of these ROMs which are found on the net. Sorry to post here a WinCE question, but I think it goes beyond OS level.

Anyhow, I already exposed my problem on http://www.slatedroid.com/index.php?topic=13555.0, but let me copy it here again.

With a "8505.rar" (WinCE) ROM (build: Dic 2009; board_name WM8505_PuZhi), battery indicator is constantly at "Low" level even right after a full recharge, unless while charging, and there's no warning for shutdown in 60 sec with very low battery (as my original firmware used to do). It just shuts down when battery is totally down. In scriptcmd I can read these:

setenv board_name WM8505_PuZhi
setenv TouchIC 0
setenv NoBootProgressBar 0
setenv NoBootInformation 0
setenv battvoltlist 6774,6889,7377,7498,7538,7599,7650,7698,7763,7821,7939
setenv bLowVoltShutdown 1
setenv audio.recordselect LineIn
setenv audio.gpio 3
setenv audio.ic VT1613
setenv pwmparam 0,25,100,90,98,38,8,0,27
setenv EthernetIC 1
setenv WIFIGPIO 2
setenv gpiostate 3
setenv regop D8110064|C,D811008C|C,D81100B4&~4,D81100B4|8,D8130054|1

With the "WINDOWS CE 6.0.7z" ROM (newer build: Feb 2010; board_name WM8505_JinLanYu7) the interface looks more "evolved". It looks like "feeling" the actual battery level and gives "good" status while plugged to power and fully charged. The power saving handling is better too, as the screen lamp switches off, after a while in standby (in just dimmed down with 8505.rar) but when I unplug it from power, battery goes immediately to "very low" level and the shutdown in 60 seconds is called. It's unusable like this. The scriptcmd reports:

setenv board_name WM8505_JinLanYu7
setenv TouchIC 0
setenv NoBootProgressBar 0
setenv NoBootInformation 0
setenv battvoltlist 6774,6889,7377,7498,7538,7599,7650,7698,7763,7821,7939
setenv bLowVoltShutdown 1
setenv audio.recordselect MicIn
setenv audio.gpio 3
setenv audio.ic VT1613
setenv pwmparam 0,233,1028,514,1000,100,90,0,27
setenv EthernetIC 1
setenv WIFIGPIO 2
setenv LowVoltConfig 12
setenv gpiostate 4097
setenv FakeBattDetect 4
setenv ThreshholdCnt 520000
setenv regop D8110064|C,D811008C|C,D81100B4&~4,D81100B4|8,D8130054|1

I'm afraid that pwmparam doesn't have to do with this problem. Indeed I flashed my smartbook with JinLanYu7 ROM, but pwmparam from PhuZi, and it didn't change the battery behaviour. I returned to PhuZi then.

Unfortunately, the battvoltlist are identical on these two ROMs, so I guess something else must control battery charge level.

Other parameters are different, or missing (e.g. FakeBattDetect, LowVoltConfig). Does anyone know what they control?

thanks
Fabio