[Q] How to decrease sensitivity of touchscreen? - Defy Q&A, Help & Troubleshooting

[Q] How to decrease sensitivity of touchscreen? - Defy Q&A, Help & Troubleshooting

Am i mad or what?
Actually it's for very simple reason. As i like to dip my phone into water to end endless discussions about iPhone 4 vs SGS II , drops of water that stay on touchscreen make false presses and touchscreen becomes unresponsive. It can be reset with power button (sleep/wake up) but that's not nice solution.
After some thinking about how Sony Ericsson Xperia Active manages to work with moist touchscreen i sticked clear foil onto my Defy and it worked! After first test i added another layer and it improved result, just very big drops of water caused "press" but they are easily shaked off. But i really don't like screen protectors.
There is an app for SGS, SGS Screen Booster and it doesen't work on defy but it's a good starting point for solving sensitivity problem

Increase the multi touch points
Btw wrong section
Sent from my MB526 using Tapatalk 2

Questions go in the Q&A section

That isn't solution. It only makes it worse because more points generate more false presses. One touch point (no multitouch) would be better solution in terms of determining which press is real and which is caused bu water drops.
I posted this in development because this isn't supported by android system itself, so it isn't question for "users". Someone of ROM developers may know or may be interested to modify system configuration in touch driver or touch configuration of system

I searched kernel source and found that board-mapphone.c contains data for touch behavior:
static struct qtouch_ts_platform_data mapphone_ts_platform_data = {
.flags = (QTOUCH_SWAP_XY |
QTOUCH_USE_MULTITOUCH |
QTOUCH_CFG_BACKUPNV |
QTOUCH_EEPROM_CHECKSUM),
.irqflags = (IRQF_TRIGGER_FALLING | IRQF_TRIGGER_LOW),
.abs_min_x = 20,
.abs_max_x = 1004,
.abs_min_y = 0,
.abs_max_y = 960,
.abs_min_p = 0,
.abs_max_p = 255,
.abs_min_w = 0,
.abs_max_w = 15,
.x_delta = 400,
.y_delta = 250,
.nv_checksum = 0xb834,
.fuzz_x = 0,
.fuzz_y = 0,
.fuzz_p = 2,
.fuzz_w = 2,
.boot_i2c_addr = 0x5f,
.hw_reset = mapphone_touch_reset,
.key_array = {
.cfg = mapphone_key_array_data,
.keys = NULL,
.num_keys = 0,
},
.power_cfg = {
.idle_acq_int = 0xff,
.active_acq_int = 0xff,
.active_idle_to = 0x01,
},
.acquire_cfg = {
.charge_time = 12,
.atouch_drift = 5,
.touch_drift = 20,
.drift_susp = 20,
.touch_autocal = 0x96,
.sync = 0,
.atch_cal_suspend_time = 0,
.atch_cal_suspend_thres = 0,
},
.multi_touch_cfg = {
.ctrl = 0x0b,
.x_origin = 0,
.y_origin = 0,
.x_size = 12,
.y_size = 7,
.aks_cfg = 0,
.burst_len = 0x40,
.tch_det_thr = 0x12,
.tch_det_int = 0x2,
.orient = 0x00,
.mrg_to = 25,
.mov_hyst_init = 5,
.mov_hyst_next = 5,
.mov_filter = 0,
.num_touch = 4,
.merge_hyst = 0,
.merge_thresh = 3,
.amp_hyst = 0,
.x_res = 0x0000,
.y_res = 0x0000,
.x_low_clip = 0x00,
.x_high_clip = 0x00,
.y_low_clip = 0x00,
.y_high_clip = 0x00,
.x_edge_ctrl = 0,
.x_edge_dist = 0,
.y_edge_ctrl = 0,
.y_edge_dist = 0,
},
.linear_tbl_cfg = {
.ctrl = 0x01,
.x_offset = 0x0000,
.x_segment = {
0x48, 0x3f, 0x3c, 0x3E,
0x3f, 0x3e, 0x3e, 0x3e,
0x3f, 0x42, 0x41, 0x3f,
0x41, 0x40, 0x41, 0x46
},
.y_offset = 0x0000,
.y_segment = {
0x44, 0x38, 0x37, 0x3e,
0x3e, 0x41, 0x41, 0x3f,
0x42, 0x41, 0x42, 0x42,
0x41, 0x3f, 0x41, 0x45
},
},
.comms_config_cfg = {
.ctrl = 0,
.command = 0,
},
.gpio_pwm_cfg = {
.ctrl = 0,
.report_mask = 0,
.pin_direction = 0,
.internal_pullup = 0,
.output_value = 0,
.wake_on_change = 0,
.pwm_enable = 0,
.pwm_period = 0,
.duty_cycle_0 = 0,
.duty_cycle_1 = 0,
.duty_cycle_2 = 0,
.duty_cycle_3 = 0,
.trigger_0 = 0,
.trigger_1 = 0,
.trigger_2 = 0,
.trigger_3 = 0,
},
.grip_suppression_cfg = {
.ctrl = 0x00,
.xlogrip = 0x00,
.xhigrip = 0x00,
.ylogrip = 0x00,
.yhigrip = 0x00,
.maxtchs = 0x00,
.reserve0 = 0x00,
.szthr1 = 0x00,
.szthr2 = 0x00,
.shpthr1 = 0x00,
.shpthr2 = 0x00,
.supextto = 0x00,
},
.noise_suppression_cfg = {
.ctrl = 0,
.outlier_filter_len = 0,
.reserve0 = 0,
.gcaf_upper_limit = 0,
.gcaf_lower_limit = 0,
.gcaf_low_count = 0,
.noise_threshold = 0,
.reserve1 = 0,
.freq_hop_scale = 0,
.burst_freq_0 = 0,
.burst_freq_1 = 0,
.burst_freq_2 = 0,
.burst_freq_3 = 0,
.burst_freq_4 = 0,
.idle_gcaf_valid = 0,
},
.touch_proximity_cfg = {
.ctrl = 0,
.x_origin = 0,
.y_origin = 0,
.x_size = 0,
.y_size = 0,
.reserve0 = 0,
.blen = 0,
.tch_thresh = 0,
.tch_detect_int = 0,
.average = 0,
.rate = 0,
},
.one_touch_gesture_proc_cfg = {
.ctrl = 0,
.reserve0 = 0,
.gesture_enable = 0,
.pres_proc = 0,
.tap_time_out = 0,
.flick_time_out = 0,
.drag_time_out = 0,
.short_press_time_out = 0,
.long_press_time_out = 0,
.repeat_press_time_out = 0,
.flick_threshold = 0,
.drag_threshold = 0,
.tap_threshold = 0,
.throw_threshold = 0,
},
.self_test_cfg = {
.ctrl = 0,
.command = 0,
.high_signal_limit_0 = 0,
.low_signal_limit_0 = 0,
.high_signal_limit_1 = 0,
.low_signal_limit_1 = 0,
.high_signal_limit_2 = 0,
.low_signal_limit_2 = 0,
},
.two_touch_gesture_proc_cfg = {
.ctrl = 0,
.reserved0 = 0,
.reserved1 = 0,
.gesture_enable = 0,
.rotate_threshold = 0,
.zoom_threshold = 0,
},
.cte_config_cfg = {
.ctrl = 1,
.command = 0,
.mode = 3,
.idle_gcaf_depth = 4,
.active_gcaf_depth = 8,
.voltage = 0,
},
.noise1_suppression_cfg = {
.ctrl = 0x01,
.version = 0x01,
.atch_thr = 0x64,
.duty_cycle = 0x08,
.drift_thr = 0x00,
.clamp_thr = 0x00,
.diff_thr = 0x00,
.adjustment = 0x00,
.average = 0x0000,
.temp = 0x00,
.offset = {
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
},
.bad_chan = {
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00
},
.x_short = 0x00,
},
.vkeys = {
.count = ARRAY_SIZE(mapphone_touch_vkeys),
.keys = mapphone_touch_vkeys,
},
};
Click to expand...
Click to collapse
Do anyone have idea how this can be altered on device itself? And what value is for sensitivity, I suspect that is .atch_thr = 0x64, under .noise1_suppression_cfg?

GoranNSW said:
I searched kernel source and found that board-mapphone.c contains data for touch behavior:
Do anyone have idea how this can be altered on device itself? And what value is for sensitivity, I suspect that is .atch_thr = 0x64, under .noise1_suppression_cfg?
Click to expand...
Click to collapse
Presumably a kernel dev could make a kernel with altered values. This wouldn't be a great solution though, as it would be permanently like that for as long as you used the kernel. Something toggle-able would be far better, for times that you know your phone is going to get wet (e.g. if you're using it as a gps on a bike mount). Additionally, I'm not sure how many devs would be interested in a relatively niche requirement.
I'd personally be satisfied with something which temporarily disabled the touchscreen - when my map is running, I generally don't need to zoom or pan - it tracks via gps. Having said that, I cycled through what felt like a monsoon, and it was relatively rare for my screen to register false presses.

flibbble said:
Presumably a kernel dev could make a kernel with altered values. This wouldn't be a great solution though, as it would be permanently like that for as long as you used the kernel. Something toggle-able would be far better, for times that you know your phone is going to get wet (e.g. if you're using it as a gps on a bike mount). Additionally, I'm not sure how many devs would be interested in a relatively niche requirement.
I'd personally be satisfied with something which temporarily disabled the touchscreen - when my map is running, I generally don't need to zoom or pan - it tracks via gps. Having said that, I cycled through what felt like a monsoon, and it was relatively rare for my screen to register false presses.
Click to expand...
Click to collapse
And there is a catch, locked bootloader. I could compile it myself but can't boot it. Now I'm left hoping that Kexec hack would be released for Defy http://forum.xda-developers.com/showthread.php?t=1819496 . I'm just hoping that someone have idea for making something toggle-able as you said
All summer I knew when my phone is going to be wet, when I'm outside, unlock phone with (just little) sweaty finger, screen get unresponsive. Then when I finish talking, sweat from head get to the phone touch start to jitter, and that's the moment when I lock my phone with lighting speed preventing it from calling random person from dialed list
When I'm cycling my phone is in my pocket, it tracks satelites from the dark
Probably my phone isn't properly factory calibrated as electronics have tolerances and when they meet you got this.
If someone (anyone here? ) wants to read about touch technology and wet finger tracking I attached pdf below

GoranNSW said:
And there is a catch, locked bootloader. I could compile it myself but can't boot it. Now I'm left hoping that Kexec hack would be released for Defy http://forum.xda-developers.com/showthread.php?t=1819496 . I'm just hoping that someone have idea for making something toggle-able as you said
All summer I knew when my phone is going to be wet, when I'm outside, unlock phone with (just little) sweaty finger, screen get unresponsive. Then when I finish talking, sweat from head get to the phone touch start to jitter, and that's the moment when I lock my phone with lighting speed preventing it from calling random person from dialed list
When I'm cycling my phone is in my pocket, it tracks satelites from the dark
Probably my phone isn't properly factory calibrated as electronics have tolerances and when they meet you got this.
If someone (anyone here? ) wants to read about touch technology and wet finger tracking I attached pdf below
Click to expand...
Click to collapse
Ah, I use my phone for navigation, not just tracking. It does sound like your ts is way more responsive than mine; I don't have any of those problems.
I had no idea that it wasn't possible to flash a custom kernel on the Defy; I've not quite got that far, given that I only use it for outdoor use, and stock is mostly ok for that. Well, I suspect we're out of luck then :/
By the way, you mentioned that a screen protector reduced the issue; any particular brand? Previous screen protectors I've tried on different phones haven't changed the screen's sensitivity, but I imagine water might be more affected differently...

You aren't out of luck yet
See this Link

It wasn't really screen protector, it was security film for windows, glass windows, not Microsoft
It is thicker than normal screen protectors (0.2mm Technical Data) and it helped just a little bit, not as much as I hoped. Let's say sensitivity is normal with it. Without it I have first case on page 11 of qtan0062.pdf, just hovering finger is enough for "touch". Now I made protector, again (which I hate, again).
In electrical language (refering to qtan0062.pdf page 8), I stepped down capacitance, but voltage and resistance (Rsmp) are same. I think there is no way to alter voltage of touch panel. Changing resistor is out of question because I don't know where it is and don't want to compromise waterproofness.
hsrars-d said:
You aren't out of luck yet
See this Link
Click to expand...
Click to collapse
Thanks for the info! Now I'm very excited and can't wait!
P.S. Sorry for so much detailing, I got a little obsessed with it

Related

TF101 screen keeps coming on at random when docked

Hi there...I was directed here from the transformerforums.com to ask about this issue. I have a B50-vintage TF101 with keyboard dock. Since the 2nd ICS update, my Transformer has developed the annoying habit of the screen randomly popping on for no reason. I know on that other site there were users seeing this happen, but I tried my best to search here and didn't see it in the search (at least not for the Transformer).
So, I did some playing around and noticed a few things. The annoying "screen coming on for no reason" issue happens only when the tablet is docked in the keyboard. The screen will come on for 10 seconds and then go off again (my default screen timeout is 5 minutes). It is almost as though some kind of notification is coming in, waking up the tablet for a moment.
I believe the issue is the "Charged" notification. I did the following experiment several times: I undocked the tablet, allowed it to discharge to about 95%. Then I plugged it back into the keyboard dock, and waited. The tablet goes into "charging" mode (with the little bolt icon on the battery). If I hit the lock button and wait, the screen goes off and stays off..it does not randomly pop back on again. Not until "Charged" has been hit. After that, the screen randomly comes on again as before.
Further, I noticed that whenever it comes on, it activates WiFi as well. I have my WiFi set to only come on when I am using the tablet. This explains the tablet waking me up in the middle of the night with new email notifications.
Not sure if this helps any...it seems reproducable to me, and definitely a regression (especially from Honeycomb).

I have the same issue, but it's not because of the charge notification. I don't charge it while using it, so when I'm doing something and using my docked tablet on the side for research and neglect it for a while, I notice it'll turn on by itself. This happens pretty consistently, so I don't have to do any weird combination of activities to produce it.
Listen to music?
Chat using Google Talk?
Browse the web?
All of them produce the same effect if I let it sleep. I have wifi set to always on but the transformer docked. I'll try keeping it undocked to see if it happens.
In every instance I didn't have it plugged in.
This is among a few other issues I have that I hope is resolved with the representative allowing us to log our devices so they can replicate the problem.

I'm having the same problem: link

Just a thought; have you got WiFi on?
Mine does this too sometimes, doesn't really bother me because it turns off by itself at the lockscreen and when closed it should also. No negative effect on battery life, it does as expected.

Hah, this is funny. I wanted to check if the screen wake-ups would occur without the dock, so after a while, I realized I didn't notice the screen turning on at all. Just as I was about to check, the Asus logo popped up, so my tablet rebooted.

It is same here.
After update to 9.2.1.17. Only in dock. Without dock, this never happen.
If someone is interested, here is log from another user from another forum:
Code:
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/AlarmManager( 166): Triggered Alarm 4144aa18 RTC_WAKEUP IntentSender{41804ce8: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=1117631ms Battery<C,V>: <35,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1204K, 16% free 7160K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 462K, 17% free 7115K/8519K, paused 2ms+2ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 83K, 13% free 7435K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 130K, 10% free 7706K/8519K, paused 3ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 216K, 8% free 7888K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 245K, 6% free 8038K/8519K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 445K, 7% free 8026K/8583K, paused 2ms+7ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{419f6e40 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:23
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5286ms Battery<C,V>: <35,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/dalvikvm( 166): GC_FOR_ALLOC freed 1136K, 22% free 17763K/22727K, paused 82ms
V/alogcat (20906): save instance
V/alogcat (20906): paused
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/dalvikvm( 5588): GC_CONCURRENT freed 2094K, 39% free 17346K/28295K, paused 2ms+9ms
D/BatteryService( 166): level:34 scale:100 status:4 health:2 present:true dock_status:1 dock_level:0 dock_ac_online:false voltage: 7 temperature: 255 technology: Li-ion AC powered:false USB powered:false icon:17302840 invalid charger:0
D/FlexLabs(20141): Widget count: 1
I/power ( 166): *** set_screen_state 1
D/AlarmManager( 166): Triggered Alarm 419f6e40 RTC_WAKEUP IntentSender{413f93a0: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9727ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
I/alogcat (20906): new intent: android.intent.action.MAIN
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1244K, 16% free 7275K/8583K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 581K, 18% free 7114K/8583K, paused 1ms+2ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 80K, 14% free 7442K/8583K, paused 3ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 113K, 10% free 7739K/8583K, paused 2ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 251K, 8% free 7905K/8583K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 244K, 7% free 8051K/8583K, paused 2ms+2ms
D/dalvikvm(20906): GC_CONCURRENT freed 451K, 7% free 8020K/8583K, paused 1ms+5ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/AlarmManager( 166): Added alarm Alarm{419341d8 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:23
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5283ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
V/alogcat (20906): save instance
V/alogcat (20906): paused
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/TaskWidgetDataUtils(20018): In trigger refresh list utils
D/TaskWidgetDataUtils(20018): getWidgetData()
D/AlarmManager( 166): Triggered Alarm 419341d8 RTC_WAKEUP IntentSender{415b2b60: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
I/power ( 166): *** set_screen_state 1
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9741ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1247K, 15% free 7356K/8647K, paused 1ms+4ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 580K, 17% free 7223K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 97K, 13% free 7551K/8647K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 167K, 11% free 7780K/8647K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 227K, 9% free 7948K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 310K, 8% free 8025K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 473K, 9% free 7945K/8647K, paused 1ms+7ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{41b76e60 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:24
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/FlexLabs(20141): Widget count: 1
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5288ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
V/alogcat (20906): save instance
V/alogcat (20906): paused
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 1
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
D/AlarmManager( 166): Triggered Alarm 41b76e60 RTC_WAKEUP IntentSender{412e2dd0: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9725ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1226K, 17% free 7259K/8647K, paused 1ms+4ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 470K, 17% free 7229K/8647K, paused 2ms+2ms
D/dalvikvm(20906): GC_CONCURRENT freed 55K, 13% free 7586K/8647K, paused 2ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 144K, 10% free 7834K/8647K, paused 3ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 256K, 8% free 7979K/8647K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 271K, 7% free 8096K/8647K, paused 2ms+3ms
D/OpenGLRenderer( 166): Flushing caches (mode 0)
D/PowerManagerService( 166): @PowerManagement: 'keyguard' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
I/TabletStatusBar( 361): DISABLE_CLOCK: no
V/TabletStatusBar( 361): setLightsOn(true)
D/dalvikvm(20906): GC_CONCURRENT freed 499K, 8% free 8034K/8647K, paused 2ms+7ms
I/TextType( 465): TextType = 0x0
W/InputManagerService( 166): Window already focused, ignoring focus gain of: [email protected]
W/IInputConnectionWrapper(20906): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): endBatchEdit on inactive InputConnection
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{41a6bd00 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:34
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/FlexLabs(20141): Widget count: 1
V/ ( 166): void cb_onMotion(uint16_t)

Same issue here after second ICS update (17) (also reboots but this is not the thread)
bye!

Very interesting...on the other forum, someone else confirmed the same behaviour, but it only seems to happen with certain models (B50, B70, B80...but NOT B90).
Quite annoying...I'm a bit concerned this continual on/off cycle is going to damage the backlight. I have my WiFi set to only come on when the screen comes on, so the random screen-on issue keeps activating the WiFi as well.
On my B50 I can make the problem "go away" for a while if I discharge my tablet to about 95%, and then re-dock in the keyboard.

Ya know, since the second ICS update my TF101 has rebooted by itself twice. Both time while I was not at home and both times it appeared to freeze at the Asus boot screen forcing me to have to hold down the power button and force a reboot. Also, more distressing, when the system locks hard it gets REAL hot. The first time it happened I had it on my bed under a pillow and felt the heat. Scared me. I now leave it on the table when not in use. I dont want it blowing up. I hope Asus fixes this as I am sure the extreme heat cant be good for it.

Mine does it too along with random reboots and wont wake after a long deep sleep of 3 to 4 hours

I've had the "really hot" thing happen to me once as well. And recently I noticed the back of the tablet, right near the SD slot, the casing has bulged out a small amount (however I don't know if it's always been that way and I only just noticed it)...I hope that's not where the battery is located.
I haven't had a random crash on my B50 since I disabled the Asus Quick Setting. It's been stable all week in that sense, but I doubt my experience will match anyone else.
Oyeve said:
Ya know, since the second ICS update my TF101 has rebooted by itself twice. Both time while I was not at home and both times it appeared to freeze at the Asus boot screen forcing me to have to hold down the power button and force a reboot. Also, more distressing, when the system locks hard it gets REAL hot. The first time it happened I had it on my bed under a pillow and felt the heat. Scared me. I now leave it on the table when not in use. I dont want it blowing up. I hope Asus fixes this as I am sure the extreme heat cant be good for it.
Click to expand...
Click to collapse

Oyeve said:
Ya know, since the second ICS update my TF101 has rebooted by itself twice. Both time while I was not at home and both times it appeared to freeze at the Asus boot screen forcing me to have to hold down the power button and force a reboot. Also, more distressing, when the system locks hard it gets REAL hot. The first time it happened I had it on my bed under a pillow and felt the heat. Scared me. I now leave it on the table when not in use. I dont want it blowing up. I hope Asus fixes this as I am sure the extreme heat cant be good for it.
Click to expand...
Click to collapse
The same thing happens to mine, except I haven't noticed the overheating (thankfully). The reboot-->freeze at logo happened again today while listening to music. I'm hoping I hear from Gary and get that logging program so they can fix it.

Mine did that a live wallpaper once I installed a regular wallpaper it stopped

I tried that just now; set a static wallpaper instead of my live one. Didn't make a difference...
Edit:
I ran a test with and without the dock now as well. I can confirm the issue only occurs when the TF is docked.

I can confirm it does it regularly with out the dock as well.

i believe the screen comes alive each time the tablet charges to 100%, whether docked (with and without usb charging taking place, but dock battery is >100%, ie. not flat out yet), or when usb connected to charger or pc. it seems that the product is designed that when the tab is docked, the battery on the dock will transfer charges to the tab until the dock is flat out. once flat out and no usb charging taking place, the tab doesnt get charged and will not hit 100% again.
i dont think the screen comes alive when the tablet is docked and closed instead of opened position.
after 2weeks on ics, experienced 1 time screen freezes in boot up ASUS logo. and the back is hotter than normal.

I've turned my TF101 off permanently until the next update is released in fear that this constant crash and freeze and battery drain is doing some physical damage to the batteries / hardware
Its basically unusable anyway

*Detection* said:
I've turned my TF101 off permanently until the next update is released in fear that this constant crash and freeze and battery drain is doing some physical damage to the batteries / hardware
Its basically unusable anyway
Click to expand...
Click to collapse
Ditto
Unusable after ICS update

This is my concern as well. There's something funny going on with the charging and I'd hate to think the batteries are getting damaged. I'm not at the point of turning my tablet off but I will say...it's getting quite annoying!
*Detection* said:
I've turned my TF101 off permanently until the next update is released in fear that this constant crash and freeze and battery drain is doing some physical damage to the batteries / hardware
Its basically unusable anyway
Click to expand...
Click to collapse

I got my keyboard Thursday and witnessed this problem until Sunday. It would occur almost every few minutes. Sunday morning I installed Codename Android ROM and have been constantly watching my screen ever since. It has not turned on once by itself. Dock battery is fully drained now and tab is just now dropping below 100%. Will post if status changes.

[INFO] All things to do with battery (life)

Battery current file (for some reason, battery monitor widget doesn't read it properly even though this file looks accurate (~251mAh on idle low brightness, 400 on high brighness, 800 on gaming)
Code:
/sys/class/power_supply/battery/current_now
looks like this is the mapping between voltage, temperature and battery % reporting by the system...
(basically, take your temperature and voltage mapping... look at the column(temperature) that contains your voltage. the row corresponds to the % left...)
eg at a temperature of 30deg, voltage of 3900, it's roughly 55% left
Code:
static struct pc_temp_ocv_lut pc_temp_ocv = {
.rows = 29,
.cols = 5,
.temp = {-20, 0, 25, 40, 60},
.percent = {100, 95, 90, 85, 80, 75, 70, 65, 60, 55, 50, 45, 40, 35, 30, 25, 20, 15, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0},
.ocv = {
{4330, 4329, 4303, 4281, 4301},
{4233, 4251, 4237, 4219, 4239},
{4161, 4189, 4181, 4164, 4183},
{4100, 4132, 4127, 4113, 4129},
{4027, 4082, 4077, 4063, 4078},
{3968, 4028, 4027, 4017, 4030},
{3924, 3968, 3981, 3975, 3986},
{3886, 3923, 3944, 3938, 3946},
{3855, 3882, 3897, 3896, 3909},
{3829, 3848, 3855, 3853, 3860},
{3807, 3821, 3827, 3825, 3830},
{3789, 3801, 3805, 3803, 3807},
{3774, 3787, 3789, 3786, 3789},
{3760, 3775, 3776, 3773, 3774},
{3746, 3764, 3767, 3762, 3755},
{3732, 3750, 3754, 3747, 3735},
{3715, 3729, 3729, 3721, 3711},
{3690, 3704, 3695, 3687, 3673},
{3656, 3683, 3678, 3669, 3661},
{3646, 3678, 3675, 3662, 3659},
{3634, 3672, 3671, 3654, 3656},
{3621, 3663, 3662, 3644, 3645},
{3602, 3648, 3639, 3626, 3616},
{3577, 3620, 3597, 3594, 3574},
{3544, 3576, 3542, 3544, 3525},
{3493, 3515, 3473, 3485, 3464},
{3419, 3429, 3391, 3409, 3381},
{3292, 3299, 3271, 3295, 3251},
{3000, 3000, 3000, 3000, 3000}
}
};
TODO: Map the wattage usage to cpu frequency to find sweet spot for power efficiency(i.e. 500mhz requires 100mW, 250mhz requires 40mW -> 250mhz is more power efficient)
this way, we can use the governor to be more greedy on particular frequencies
Current discharge usage per hour in mAh
Code:
Experiment
384mhz 1 core idle, wifi on, brightness lowest: ~180mAh
384mhz 1 core idle, wifi on, brightness highest: ~380mAh
benchmark (i.e. all 4 cores), wifi on, brightness lowest: max ~ 1500
intellidemand governor, brightness lowest, GPS ON: ~260<->350 (lock<->searching for lock)
intellidemand governor, brightness highest, GPS ON: ~460<->550 (lock<->searching for lock)
Code:
Extrapolating results
difference between lowest brightness & highest brightness - 200mAh
GPS usage: 80-150mAh, plus whatever CPU cycles your GPS app uses
idle CPU <-> full CPU:

Nice it looks like development is off to a great start! I originally posted information here but it is now in your kernel thread. I don't know if the information that I posted in your kernel thread, will be of any help to you but I figured it was worth a shot.

[Q] On battery time didn't refresh when unplug.

When my Nexus 10 is not fully charged, plug the cable to charge, it will say Charging. Then unplugged it, the on battery time did not recount from 0s. Only when it’s fully charged(100%), unplug it, the time will be reset to 0s. how about yours. Is it normal

heliumhgy said:
When my Nexus 10 is not fully charged, plug the cable to charge, it will say Charging. Then unplugged it, the on battery time did not recount from 0s. Only when it’s fully charged(100%), unplug it, the time will be reset to 0s. how about yours. Is it normal
Click to expand...
Click to collapse
It's what my HTC One does. My Nexus 10 is at home, but I can check against other tablets/phones I have as well when I get back. Seems to be default behavior though.

OK, I got it.
Check here: android.stackexchange.com/questions/26369/reset-battery-history-after-unplugging-charger (I can't post outside link now)
Code:
if (onBattery) {
// We will reset our status if we are unplugging after the
// battery was last full, or the level is at 100, or
// we have gone through a significant charge (from a very low
// level to a now very high level).
if (oldStatus == BatteryManager.BATTERY_STATUS_FULL
|| level >= 90
|| (mDischargeCurrentLevel < 20 && level >= 80)) {
doWrite = true;
resetAllStatsLocked();
mDischargeStartLevel = level;
}
the
Code:
mDischargeCurrentLevel
is
Code:
battery levels (1-100) at the last plug event and the last unplug event.
I test it on my old Defy, when unplugging at 28% battery level, the On Battery Time did not reset either.
With regard to the source code above, the Android has it's own mechanism of resetting battery level when unplugging.

where to find this?
heliumhgy said:
OK, I got it.
Check here: android.stackexchange.com/questions/26369/reset-battery-history-after-unplugging-charger (I can't post outside link now)
Code:
if (onBattery) {
// We will reset our status if we are unplugging after the
// battery was last full, or the level is at 100, or
// we have gone through a significant charge (from a very low
// level to a now very high level).
if (oldStatus == BatteryManager.BATTERY_STATUS_FULL
|| level >= 90
|| (mDischargeCurrentLevel < 20 && level >= 80)) {
doWrite = true;
resetAllStatsLocked();
mDischargeStartLevel = level;
}
Click to expand...
Click to collapse

sha2nk7 said:
heliumhgy said:
OK, I got it.
Check here: android.stackexchange.com/questions/26369/reset-battery-history-after-unplugging-charger (I can't post outside link now)
Code:
if (onBattery) {
// We will reset our status if we are unplugging after the
// battery was last full, or the level is at 100, or
// we have gone through a significant charge (from a very low
// level to a now very high level).
if (oldStatus == BatteryManager.BATTERY_STATUS_FULL
|| level >= 90
|| (mDischargeCurrentLevel < 20 && level >= 80)) {
doWrite = true;
resetAllStatsLocked();
mDischargeStartLevel = level;
}[/QUOTE]
https://github.com/android/platform_frameworks_base/blob/master/core/java/com/android/internal/os/BatteryStatsImpl.java
line 4751
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Thanks for the reply I meant where I can find this code or "BatteryStatsImpl.java" on my android.
"if (oldStatus == BatteryManager.BATTERY_STATUS_FULL
|| level >= 90
|| (mDischargeCurrentLevel < 20 && level >= 80)) {
doWrite = true;
resetAllStatsLocked();
mDischargeStartLevel = level;"
using samsung mega 5.8..

[Q] Constant shutting down

Among other problem, my phone has started shutting down randomly after 5-15 minute. Here is the last_kmsg :
Code:
[ 1502.022310] batt_temp_monitor_work: stop charging!! state = 7 temp = -300 mvolt = 3990
[ 1502.022432] batt_temp_set_current_limit: value = 900
[ 1502.022523] batt_temp_charger_disable
[ 1502.036227] healthd: battery l=49 v=3881 t=-30.0 h=3 st=4 c=142 chg=u
[ 1502.042514] adjust_soc: ibat_ua = 142200, vbat_uv = 3901515, soc = 86, batt_temp=-300
[ 1502.093300] healthd: battery l=56 v=3897 t=-30.0 h=3 st=4 c=142 chg=u
[ 1504.182267] mdm_status_change: unexpected reset external modem id 0
120 Corrected bytes, 1 unrecoverable blocks
Boot info:
Last boot reason: hw_reset_or_poweron
Any idea ? Also the charging port is not working, I get the lightning icon but it says not charging. The only way I can charge the phone is by wireless charging

[Q] No space for installing apps - how to install to SD card

Hi,
This is my first post to this forum. Please forgive me if this question has already been answered ad-nauseum but I haven't been able to find an adequate answer to it after what seems like exhaustive searching on this forum or on google.
I have successfully rooted my nook simple touch running firmware 1.2.1 (multiple times now, that part is simple). I have access to the google play store and the android store, but I still would like to have the ability to sideload .apk files.
The problem that I run into is that I seem to have almost no space for applications on my device. I can manage to get opera mini, dropbox, kindle, and ES file explorer going, and I might be able to install several other small apps if I tried, but I haven't been able to install EZPDF reader due to what appears to be space limitation.
I have tried the following:
- installing through the play store - installation fails
- installing by tapping on the .apk file while browsing my SD card using either ES file explorer or relaunch - out of space error
- installing by running the ADB install command - install failed due to insufficient storage
- I have also tried the [-s] command with adb install and prompt does not recognize that qualifier
- installing by simply copying the .apk file to the /system/app folder (this actually gets the application into my applications list and I can open it but then it claims it can't access my SD card and closes down
I really am starting to feel frustrated, especially since it seems like others are able to install large numbers of apps without running into this type of problem. How limited is the space on the NST and is there any way to install applications to the SD card to prevent running out of space so quickly? Perhaps I simply need to forgo the idea of having more than a small handful of applications? Thanks very much in advance.

First thing to check.
Code:
adb shell df
...
/data: 808292K total, 87864K used, 720428K available (block size 4096)
...
Then in two different windows do:
Code:
adb logcat
Code:
adb install [i]whatever.apk[/i]

Renate NST said:
First thing to check.
Code:
adb shell df
...
/data: 808292K total, 87864K used, 720428K available (block size 4096)
...
Then in two different windows do:
Code:
adb logcat
Code:
adb install [i]whatever.apk[/i]
Click to expand...
Click to collapse
So for the first (and that's after I have deleted as many apps as I can stand. Left amazon app store, market search, google apps, kindle, es file explorer and dropbox):
ben$ adb shell df
/dev: 116448K total, 0K used, 116448K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16344K total, 400K used, 15944K available (block size 8192)
/system: 396656K total, 221551K used, 175105K available (block size 1024)
/data: 146735K total, 135842K used, 10893K available (block size 1024)
/cache: 198321K total, 9335K used, 188986K available (block size 1024)
/media: 856404K total, 44K used, 856360K available (block size 4096)
/sdcard: 15335680K total, 57248K used, 15278432K available (block size 32768)
ben$ adb install /Users/ben/Downloads/EZPDF.reader-2.5.0.3-signed.apk
failed to copy '/Users/ben/Downloads/EZPDF.reader-2.5.0.3-signed.apk' to '/data/local/tmp/EZPDF.reader-2.5.0.3-signed.apk': No space left on device
rm failed for /data/local/tmp/EZPDF.reader-2.5.0.3-signed.apk, No such file or directory
Logcat output (during and immediately after the install command):
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 12 msecs
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
I/wpa_supplicant( 891): CTRL-EVENT-STATE-CHANGE id=1 state=6
V/WifiMonitor( 807): Event [CTRL-EVENT-STATE-CHANGE id=1 state=6]
I/wpa_supplicant( 891): WPA: Group rekeying completed with 00:19:e3:fb:a1:27 [GTK=CCMP]
I/wpa_supplicant( 891): CTRL-EVENT-STATE-CHANGE id=1 state=7
V/WifiMonitor( 807): Event [WPA: Group rekeying completed with 00:19:e3:fb:a1:27 [GTK=CCMP]]
V/WifiMonitor( 807): Event [CTRL-EVENT-STATE-CHANGE id=1 state=7]
V/WifiStateTracker( 807): Changing supplicant state: COMPLETED ==> GROUP_HANDSHAKE
V/WifiStateTracker( 807): Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/WindowManager( 807): CALLING monitor
D/WindowManager( 807): mHomeKeyHeldAt =1403064346572; mFlip = false
I/WindowManager( 807): interceptKeyTi(): KEYCODE_HOME
I/WindowManager( 807): interceptKeyTi(): KEYCODE_HOME + (down && repeatCount == 0 && !mDisableInput) == true ==> recognize home key pressed
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/WindowManager( 807): CALLING monitor
D/WindowManager( 807): toggle quicknav95
I/WindowManager( 807): interceptKeyTi(): KEYCODE_HOME & mHomePressed
W/WindowManager( 807): Unable to find ITelephony interface
D/EPD#StatusBar( 807): set region 3 1 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 807): epd_set_region: 3 (0,0,600,800) 1,0 1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 22 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
E/TC ( 1100): KPICollector: 1403064347424 platform qn_home_press
D/EPD#ActivityResume( 807): Disable EPD for 250ms!!!!!!!!
I/ActivityManager( 807): Starting activity: Intent { act=com.bn.intent.action.home flg=0x14400000 cmp=android/com.android.internal.app.ResolverActivity }
E/TC ( 1100): KPICollector: 1403064347454 ActivityManager background {"component":"com.rockolabs.adbkonnect/.AdbKonnectActivity"}
E/TC ( 1100): KPICollector: 1403064347456 ActivityManager foreground {"component":"android/com.android.internal.app.ResolverActivity"}
D/EPD#StatusBar( 807): resetRegion 3
D/NATIVE-EPD( 807): epd_reset_region: 0x08
D/EPD#StatusBar( 807): Disable EPD for 150ms!!!!!!!!
V/Activity( 807): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
I/ActivityManager( 807): Displayed activity android/com.android.internal.app.ResolverActivity: 73 ms (total 73 ms)
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 13 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/ActivityManager( 807): Starting activity: Intent { act=com.bn.intent.action.home flg=0x17c00000 cmp=com.harasoft.relaunch/.Home1 }
I/ActivityManager( 807): Starting activity: Intent { flg=0x4000000 cmp=com.harasoft.relaunch/.ReLaunch (has extras) }
W/ActivityManager( 807): Activity is launching as a new task, so cancelling activity result.
V/Activity( 1113): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
E/TC ( 1100): KPICollector: 1403064349494 ActivityManager background {"component":"android/com.android.internal.app.ResolverActivity"}
E/TC ( 1100): KPICollector: 1403064349498 ActivityManager foreground {"component":"com.harasoft.relaunch/.Home1"}
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 14 msecs
D/dalvikvm( 807): GC freed 37230 objects / 2142120 bytes in 85ms
V/Activity( 1113): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
D/ReLaunchApp( 1113): --- onResume(ReLaunch)
D/dalvikvm( 1113): GC freed 8125 objects / 546704 bytes in 45ms
I/ActivityManager( 807): Displayed activity com.harasoft.relaunch/.ReLaunch: 563 ms (total 593 ms)
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 28 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 66 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 44 msecs
I/ActivityManager( 807): Starting activity: Intent { cmp=com.harasoft.relaunch/.AllApplications (has extras) }
V/Activity( 1113): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
D/ReLaunchApp( 1113): --- onResume(AllApps)
D/dalvikvm( 1113): GC freed 9179 objects / 464984 bytes in 55ms
I/ActivityManager( 807): Displayed activity com.harasoft.relaunch/.AllApplications: 430 ms (total 430 ms)
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/ActivityManager( 807): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.estrongs.android.pop/.view.FileExplorerActivity }
V/Activity( 1212): performResume()
D/EPD#ActivityResume( 807): resetRegion 4
D/NATIVE-EPD( 807): epd_reset_region: 0x10
D/EPD#ActivityResume( 807): resetRegion 5
D/NATIVE-EPD( 807): epd_reset_region: 0x20
D/EPD#ActivityResume( 807): resetRegion 6
D/NATIVE-EPD( 807): epd_reset_region: 0x40
D/EPD#ActivityResume( 807): resetRegion 7
D/NATIVE-EPD( 807): epd_reset_region: 0x80
D/EPD#ActivityResume( 807): Disable EPD for 350ms!!!!!!!!
E/TC ( 1100): KPICollector: 1403064353853 ActivityManager background {"component":"com.harasoft.relaunch/.AllApplications"}
E/TC ( 1100): KPICollector: 1403064353879 ActivityManager foreground {"component":"com.estrongs.android.pop/.view.FileExplorerActivity"}
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
D/dalvikvm( 1212): GC freed 17357 objects / 969872 bytes in 72ms
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 21 msecs
D/dalvikvm( 1820): GC freed 1111 objects / 76976 bytes in 34ms
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 11 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 34 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 36 msecs
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 39 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/dalvikvm( 1100): GC freed 1599 objects / 78840 bytes in 33ms
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 42 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 35 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 14 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/dalvikvm( 1212): GC freed 17489 objects / 1116816 bytes in 73ms
D/dalvikvm( 1212): GC freed 6279 objects / 603384 bytes in 61ms
D/dalvikvm( 1212): GC freed 594 objects / 203872 bytes in 58ms
D/dalvikvm( 1212): GC freed 697 objects / 211904 bytes in 59ms
D/dalvikvm( 1212): GC freed 825 objects / 218136 bytes in 59ms
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 34 msecs
D/dalvikvm( 1113): GC freed 4876 objects / 294608 bytes in 57ms
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 36 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 11 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 36 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 46 msecs
D/SurfaceFlinger( 807): Frame buffer posted; elapsed time = 40 msecs
I/PowerManagerService( 807): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiService( 807): ACTION_BATTERY_CHANGED pluggedType: 0
Thanks for your help!

Something has gotten screwed up with either the partitioning or else the formatting of the /data partition.
It should be showing somewhere near 840 Megs for the partition or 800 Megs on a df command.
You are showing 150 Megs.
Step 1: Do a complete, ~1.9 GB backup using noogie and Win32DiskImager
Step 2:
Code:
C:\>imagefix [i]mybackup.img[/i]
Image is partitioned as stock NST
...
This will tell you instantly if the partitioning is stock.
If it's not, stop here.
Step 3: Get ClockworkMod Recovery running as either a recovery image on internal storage, on external storage or through USB boot. Connect to it with ADB.
Step 4:
Code:
# e2fsck /dev/block/mmcblk0p8

@Renate ... @nmyshkin ...
noogie boot
Code:
lsblk
gives the following partition structure
Code:
sdc 8:32 1 1.9G 0 disk
├─sdc1 8:33 1 76M 0 part /media/muz/boot
├─sdc2 8:34 1 16M 0 part /media/muz/rom
├─sdc3 8:35 1 190M 0 part /media/muz/factory
├─sdc4 8:36 1 1K 0 part
├─sdc5 8:37 1 288M 0 part /media/muz/18216b6d-59fc-4b61-b9db-652bbb5e848d
├─sdc6 8:38 1 240M 0 part /media/muz/NOOK
├─sdc7 8:39 1 240M 0 part /media/muz/cache
└─sdc8 8:40 1 802M 0 part /media/muz/userdata
but the ReLaunch shows only ... Total : 227MB / Free: 118 ... but the above partition table shows
Code:
/userdata
of 802 MB ... Where did almost 600MB vanish in between ?
Is there any way I can reclaim almost 600 MB of user data space ?
thanks.

aiamuzz said:
Where did almost 600MB vanish in between ?
Is there any way I can reclaim almost 600 MB of user data space ?
thanks.
Click to expand...
Click to collapse
Where indeed? I am not familiar with noogie and its output, but I have seen this kind of complaint before. You've been really busy with flashing one thing after another on your device, including cloning a device running FW 1.1.5. I think you need to slow down and re-start from the cleanest configuration you can get.
You said you had a complete backup of the device as received from the seller. Here is what I would do:
1. Restore that backup.
2. De-register offline (boot, as soon as "Read Forever" appears, press and hold the lower hardware buttons until the prompt appears). Proceed to delete user data.
3. Make a NookManager card (BE SURE to use the updated version. The old version will not work properly with FW 1.2.2) and use the "rescue" option to initiate a factory re-image of the device. This is your best bet to getting things back to the way they should be before trying out modifications.
4. After the re-image is done you will be left at the "Welcome" screen. Connect your device via USB to your PC and drag the 1.2.2 update zip onto the "Nook" drive. Let the device sleep and it will install the update.
5. Register the device.
6. Root with NookManager.
7. Customize as desired.
I'd be surprised if this did not make the issue you describe disappear.

This morning I just did an update to my Onyx Poke 3. Since they are pretty obtuse, it's a full update, 1.4 GB. Good luck finding space for that.
I have a whole recovery/update install system which can access a USB flash drive. It worked just fine.
Oh, wait, you're still talking about the NST??? How about sticking it on an SD card in the slot? Hmm?

nmyshkin said:
Where indeed? I am not familiar with noogie and its output, but I have seen this kind of complaint before. You've been really busy with flashing one thing after another on your device, including cloning a device running FW 1.1.5. I think you need to slow down and re-start from the cleanest configuration you can get.
You said you had a complete backup of the device as received from the seller. Here is what I would do:
1. Restore that backup.
2. De-register offline (boot, as soon as "Read Forever" appears, press and hold the lower hardware buttons until the prompt appears). Proceed to delete user data.
3. Make a NookManager card (BE SURE to use the updated version. The old version will not work properly with FW 1.2.2) and use the "rescue" option to initiate a factory re-image of the device. This is your best bet to getting things back to the way they should be before trying out modifications.
4. After the re-image is done you will be left at the "Welcome" screen. Connect your device via USB to your PC and drag the 1.2.2 update zip onto the "Nook" drive. Let the device sleep and it will install the update.
5. Register the device.
6. Root with NookManager.
7. Customize as desired.
I'd be surprised if this did not make the issue you describe disappear.
Click to expand...
Click to collapse
I have done the following ... booted into nook manager, rescued through th factory zip ... that returned my device to 1.1.5 ... isn't this as clean as it gets ... cleaner than i received from the seller which had 1.2.1 ???
Right now as i type this ... I have built a device coming the factory zip way out of the Nook Manager(Stealth version) ... I've removed RelaunchX after mapping the button to the app drawer(a very clean implementation minus the overheads of a full fledged lancher i hope), thanks for this implementation as it just gets the job done, its not like our low spec'd device required a full launcher, a launcher was only to access the app drawer, and the standalone app drawer implementation does that job giving it a clean experience.
Some advice ?
1. Would you recommend installing CWM recovery to the above setup ? ...
ABOUT reclaiming the userdata partition ...
---------------------------------------------------------------------
2. I was wondering if i could somehow format/clear the /userdata partition somehow(CWM recovery ? or gparted with a noogie boot that mounts partitions on my linux desktop - I hope gparted does not corrupt the other partition structure/information proprietary to B&N) ... can I ?
3. If that's doable i was wondering what will be the repercussions of doing it ...
- Will i lose the B&N Nook Store registration ?
- Will i be able to re-register from that point onwards ? ... or ...
- Coming clean from the start is the only way to register the device at B&N(If so then that's of no use)

aiamuzz said:
but the ReLaunch shows only ... Total : 227MB / Free: 118
Click to expand...
Click to collapse
The /data partition is ~800 M (for apps, system & /data/media/B&N Downloads for B&N books)
The /media partition is ~250 M (for sideloaded books)
There is no 600 M discrepancy.

aiamuzz said:
1. Would you recommend installing CWM recovery to the above setup ? ...
Click to expand...
Click to collapse
Absolutely not. It will replace the stock recovery and you may come to regret that. If you want CWM, make an sdcard following the directions in that thread. That's how I use it.
aiamuzz said:
ABOUT reclaiming the userdata partition ...
---------------------------------------------------------------------
2. I was wondering if i could somehow format/clear the /userdata partition somehow(CWM recovery ? or gparted with a noogie boot that mounts partitions on my linux desktop - I hope gparted does not corrupt the other partition structure/information proprietary to B&N) ... can I ?
3. If that's doable i was wondering what will be the repercussions of doing it ...
- Will i lose the B&N Nook Store registration ?
- Will i be able to re-register from that point onwards ? ... or ...
- Coming clean from the start is the only way to register the device at B&N(If so then that's of no use)
Click to expand...
Click to collapse
If you must go into this (see reply by @Renate above), there is a thread that describes repartitioning with gparted: https://forum.xda-developers.com/t/...ch-resize-partitions-non-destructive.1279091/
Fooling with the partitions is a recipe for disaster, IMHO, so unless a previous owner has done some damage you need to repair and your device is a doorstop, I would not go there for all the used NSTGs in Romania.
Edit: FWIW, here is a df of one of my registered devices with stock partitioning. Yours may vary slightly but should be similar in terms of 1K-blocks:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 115644 0 115644 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mmcblk0p2 16116 218 15899 1% /rom
/dev/block/mmcblk0p5 285583 165242 117393 58% /system
/dev/block/mmcblk0p8 808292 277164 522916 35% /data
/dev/block/mmcblk0p7 237987 6259 229271 3% /cache
/dev/block//vold/179:6 245484 504 244980 0% /media
/dev/block//vold/179:17 13721336 790072 12931264 6% /sdcard

Database Users

welcome