Reply
Thread Tools
Posts: 212 | Thanked: 189 times | Joined on Oct 2010
#21
Had the same (not exactly) issue. Formatted optfs from ubuntu. Then did a cold flash. Flashed with an image with backupmenu. Restored backups with backupmenu. Not sure about order or images.

Last edited by sethkha; 2011-07-09 at 16:59.
 
Posts: 63 | Thanked: 27 times | Joined on Jul 2011 @ Venezuela
#22
Hello again.. Now I think it could be a battery monitor problem. When maemo starts up (in R&D mode) the battery life keeps low and after 5 minutes of use a notification appears telling "battery low" (altough the battery is fully charged --i use a nokia 5800--). However, I can use the phone for like 5 hours using wi-fi, web browser, app manager.
Minutes ago, I installed Nitdroid but when it's booting a red light starts blinking and then shuts down (the android desktop appears telling: "Shutting Down"). I read that this is because a BME problem.
What do you think?
 

The Following User Says Thank You to jvollmann For This Useful Post:
Posts: 63 | Thanked: 27 times | Joined on Jul 2011 @ Venezuela
#23
update: I installed Meego 1.1 and it boots ok (a little slow but i think it's because my sd card is class 4). I tried to charge the battery when Meggo started up, the battery icon showed like it would be charging but the phone led didn't turn on or blink, after some time the phone turned off because the battery drained.
 

The Following User Says Thank You to jvollmann For This Useful Post:
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#24
bq_27200 chip damaged? How do You charge battery anyway, using external charger?
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 
Posts: 63 | Thanked: 27 times | Joined on Jul 2011 @ Venezuela
#25
Originally Posted by Estel View Post
bq_27200 chip damaged? How do You charge battery anyway, using external charger?
I charge it with a Nokia 5800... Do you know if there's any diagnostic tool/app (or a boot log file) to know if the chip is really damaged?
 
Posts: 842 | Thanked: 1,197 times | Joined on May 2010
#26
Go install i2c-tools from extras-devel(ignore the warning).
Here's the charge-script used in backupmenu; should tell you something:
Code:
#/bin/bash
# Reset

#echo -n Reset...
#i2cset -y -m 0x80 2 0x6b 0x04 80
#echo -n Done. Sleep 1...
#sleep 1
#echo -n Done.

#echo "Charger: " $(cat /sys/devices/platform/musb_hdrc/charger)

# Disable charger for configuration:
i2cset -y 2 0x6b 0x01 0xcc # No limit, 3.4V weak threshold, enable term, charger disable


# Register 0x04
# 8: reset
# 4: 27.2mV  # charge current
# 2: 13.6mV
# 1: 6.8mV
# 8: N/A
# 4: 13.6mV # termination current
# 2: 6.8mV
# 1: 3.4mV
# 7-1250 6-1150 5-1050 4-950 3-850 2-750 1-650 0-550
# 7-400 6-350 5-300 4-250 3-200 2-150 1-100 0-50
i2cset -y -m 0xFF 2 0x6b 0x04 0x50;

# Register 0x02
# 8: .640 V
# 4: .320 V
# 2: .160 V
# 1: .080
# 8: .040
# 4: .020 (+ 3.5)
# 2: otg pin active at high (default 1)
# 1: enable otg pin
i2cset -y -m 0xfc 2 0x6b 0x02 0x8c; 
# 4.2 = 3.5 + .640 + .040 + .02 = 8c
# 4.16 = 3.5 + .640V + .020 = 84
# 4.1 = 3.5 + .320 + .160 + .08 + .04 = 78
# 4.0 = 3.5 + .320 + .160 + .02 = 64
# 3.9 = 3.5 + .320 + .080 = 50

# Register 0x1
# 8: 00 = 100, 01 = 500, 10 = 800mA
# 4: 11 = no limit
# 2: 200mV weak threshold default 1
# 1: 100mV weak treshold defsult 1 (3.4 - 3.7)
# 8: enable termination
# 4: charger disable
# 2: high imp mode
# 1: boost
i2cset -y 2 0x6b 0x01 0xc8; 
#0110 1011

# Register 0x00
# 8: Read:  OTG Pin Status
#    Write: Timer Reset
# 4: Enable Stat Pin
# 2: Stat : 00 Ready 01 In Progress
# 1:      : 10 Done  11 Fault
# 8: Boost Mode
# 4: Fault: 000 Normal 001 VBUS OVP 010 Sleep Mode 
# 2:        011 Poor input or Vbus < UVLO 
# 1:        100 Battery OVP 101 Thermal Shutdown
#           110 Timer Fault 111 NA
i2cset -y 2 0x6b 0x00 0x00; 

#echo -n "Charge parameters programmed. Sleep 1..."
sleep 1
#echo "Status: " $(i2cget -y 2 0x6b 0x00)
i2cset -y 2 0x6b 0x00 0x80 # timer reset
cat /sys/devices/platform/musb_hdrc/charger >/dev/null

# Initialize variables
THROTTLE=0
FULL=0
MODE="STANDBY"
WALLCHARGER=0

# Assuming a nice round number 20mOhm for bq27200 sense resistor
RS=20

get_nac ()
{
    NAC=$(i2cget -y 2 0x55 0x0c w)
    NAC=$(($NAC * 3570 / $RS / 1000))
}
get_rsoc ()
{
    RSOC=$(i2cget -y 2 0x55 0x0b)
    RSOC=$((RSOC))
}
get_volt ()
{
   VOLT=$(i2cget -y 2 0x55 0x08 w)
   VOLT=$(($VOLT))
}

STATUS=$(i2cget -y 2 0x6b 0x00)
while true ; do
   sleep 10; 
   STATUS=$(i2cget -y 2 0x6b 0x00)
   #echo $STATUS

   i2cset -y -m 0x80 2 0x6b 0x00 0x80; # timer reset
   get_nac
   get_rsoc
   get_volt

   if [ $MODE == "STANDBY" ] ; then
      if [ $STATUS == 0x10 ] || [ $STATUS == 0x90 ] ; then
         MODE="CHARGING"
         #echo $(date) "standby -> CHARGING. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log
         echo 60 > /sys/class/backlight/acx565akm/brightness
         WALLCHARGER=$(cat /sys/devices/platform/musb_hdrc/charger)
      fi
   fi
   if [ $MODE == "CHARGING" ] ; then
      if [ $STATUS == 0x00 ] ; then
         MODE="STANDBY"
         echo 15 > /sys/class/backlight/acx565akm/brightness
         #echo $(date) "charging -> STANDBY. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log
         WALLCHARGER=0
         # This will stop USB from eating power as long as you haven't plugged it into a PC
         echo 0 > /sys/devices/platform/musb_hdrc/connect
      fi
   fi

   if [ $STATUS == 0xa0 ] && [ $FULL == 0 ] ; then
      #echo "Charge done"
      #echo $(date) "FULL: " $NAC "mAh" >> /home/user/MyDocs/charger.log
      FULL=1
   fi
   if [ $STATUS == 0x00 ] && [ $FULL == 1 ] ; then
      FULL=0
   fi
   echo Status: $STATUS Mode: $MODE Full: $FULL WallCharger: $WALLCHARGER Battery Voltage: $VOLT NAC: $NAC Battery level: $RSOC %
done
Save it as charge.sh (anywhere but mydocs/sd) and run "chmod +x /path/to/charge.sh".
Then run it. Every ~10 or so seconds, you'll get a message telling what's going on.
__________________
My projects: BackupMenu - OS Backup & restore | Video: Flashing your n900(LiveCD)
My devices: N770 + 8GB SD card soldered internally, N900 with 8GB SD card + Custom OC(125-950 typically).
OC freqs: 0:22,90 125:22,90 250:28,180 500:30,360 550:32,400 600:34,430 700:39,430 750:41,430 805:45,430 850:47,500 900:50,500 950:54,500 1000:58,500 1100:67,520 1150:71,520

Last edited by RobbieThe1st; 2011-07-11 at 15:14.
 

The Following 3 Users Say Thank You to RobbieThe1st For This Useful Post:
Posts: 63 | Thanked: 27 times | Joined on Jul 2011 @ Venezuela
#27
Thanks. I will post the log later..
 
Posts: 2,225 | Thanked: 3,822 times | Joined on Jun 2010 @ Florida
#28
To elaborate on Estel's previous post, not only Hawaii, but MohammadAG and I also run our N900s in R&D mode regularly. If you disable the keyboard flickering battery life should be identical.

The only difference, depending on what flags you set, is that sometimes your device might hang instead of spontaneously reboot (as in, some deep system process will crash and normally watchdogs or lifeguard reset would reboot the device - with those disabled, if you choose to do so, the device won't reboot itself during some of those crashes and sometimes you have to pull the battery if it's something important that crashes. The advantage is that sometimes stuff will crash and then restart and while you notice it, your device doesn't reboot on you, which is nice, and the "crucial" process that the system supposedly had to reboot for a lack of just restarts and the device keeps working. Honestly even when it hangs and has to be rebooted/battery-pulled, I MUCH prefer to do that than have the device spontaneously turn off on me. One is just irksome, the other is like a slap in the face with barb wire and poison ivy tangled together.
 

The Following User Says Thank You to Mentalist Traceur For This Useful Post:
Posts: 63 | Thanked: 27 times | Joined on Jul 2011 @ Venezuela
#29
Originally Posted by Mentalist Traceur View Post
To elaborate on Estel's previous post, not only Hawaii, but MohammadAG and I also run our N900s in R&D mode regularly. If you disable the keyboard flickering battery life should be identical.

The only difference, depending on what flags you set, is that sometimes your device might hang instead of spontaneously reboot (as in, some deep system process will crash and normally watchdogs or lifeguard reset would reboot the device - with those disabled, if you choose to do so, the device won't reboot itself during some of those crashes and sometimes you have to pull the battery if it's something important that crashes. The advantage is that sometimes stuff will crash and then restart and while you notice it, your device doesn't reboot on you, which is nice, and the "crucial" process that the system supposedly had to reboot for a lack of just restarts and the device keeps working. Honestly even when it hangs and has to be rebooted/battery-pulled, I MUCH prefer to do that than have the device spontaneously turn off on me. One is just irksome, the other is like a slap in the face with barb wire and poison ivy tangled together.
Ok, I get it,,, I haven't had any problems running in R&D mode actually.
There are only two things that bothers me: 1)I can't charge the battery and, 2) I can't run Nitdroid.

Is there any "hack"to disable or trick the battery monitor?

PS. I will post the log from i2c-tools in a couple of minutes
 
Posts: 63 | Thanked: 27 times | Joined on Jul 2011 @ Venezuela
#30
Also tried with: modprobe bq27x00_battery, the results were all 0 but the voltage, current, temp and design:

cat /sys/class/power_supply/bq27200-0/capacity
0
cat /sys/class/power_supply/bq27200-0/charge_full
0
cat /sys/class/power_supply/bq27200-0/charge_now
0
cat /sys/class/power_supply/bq27200-0/time_to_empty_avg
0
cat /sys/class/power_supply/bq27200-0/time_to_empty_now
0
cat /sys/class/power_supply/bq27200-0/time_to_full_now
0


cat /sys/class/power_supply/bq27200-0/charge_full_design
2056320

Last edited by jvollmann; 2011-07-12 at 03:31.
 
Reply


 
Forum Jump


All times are GMT. The time now is 09:25.