strange behavior battery

use stock rom 5.1.1 kernel with zombies my battery to 85 % when you reboot into recovery and 17 % tried clean install with dual kernel but it is always the same . my question and the dead battery ?:confused:

Samsung Galaxy Note 3 strange behavior

Some weeks ago I was riding my motorbike down the highway and at some point my phone mount decided to break and fall. The Note 3 didn't seem so have any other damage other than glass and screen so I had them replaced with original spare parts and now my phone is overheating, unable to connect to any kind of cellular network and the camera is not working. I already tried to install different ROMS, kernels and recoveries but nothing seems to change. Temperature doesn't rise too much while doing stuff in the recovery but as soon as Android is loaded the CPU gets up to 80C while the battery stays at 40C. The phone also shuts down when I put it on standby and powers up by itself, especially when it's charging. The battery is draining so badly that it's hard to get to 100%. Here is a logcat.

Code:

---

E/WindowState( 1484): getStack: Window{1bb1716 u0 com.android.settings/com.android.settings.settingssearch.SettingsSearchActivity} couldn't find taskId=3 Callers=com.android.server.wm.WindowState.computeFrameLw:1050 com.android.internal.policy.impl.PhoneWindowManager.layoutWindowLw:4914 com.android.server.wm.WindowManagerService.performLayoutLockedInner:10946 com.android.server.wm.WindowManagerService.performLayoutAndPlaceSurfacesLockedInner:11814
--------- beginning of main
E/LocSvc_ApiV02( 1484): I/<--- void globalEventCb(locClientHandleType, uint32_t, locClientEventIndUnionType, void*) line 99 QMI_LOC_EVENT_INJECT_POSITION_REQ_IND_V02
E/LocSvc_ApiV02( 1484): I/<--- void globalEventCb(locClientHandleType, uint32_t, locClientEventIndUnionType, void*) line 99 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
E/mm-camera(  350): mct_bus_sof_thread_run: SOF freeze; Sending error message
E/mm-camera(  350): msg_bus_post_msg: Received HW error bus msg
E/LocSvc_ApiV02( 1484): I/<--- void globalEventCb(locClientHandleType, uint32_t, locClientEventIndUnionType, void*) line 99 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
E/SMD    (  317): DCD ON
E/LocSvc_ApiV02( 1484): I/<--- void globalEventCb(locClientHandleType, uint32_t, locClientEventIndUnionType, void*) line 99 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
E/mm-camera(  350): isp_axi_streamon: ISP_CFG_STREAM error = -1, start_straem = 0
E/mm-camera(  350): isp_axi_stop_stream: isp_axi_start_stop error = -1
E/mm-camera(  350): stats_action_buf_config: cfg = 0, stats_mask = 0x7b8
E/mm-camera(  350): isp_pipeline_util_reset: module id = 0, action = 0xb6e6c0a9
E/mm-camera(  350): isp_pipeline_util_reset: module id = 1, action = 0xb6e700a5
E/mm-camera(  350): isp_pipeline_util_reset: module id = 2, action = 0xb6e6a35d
E/mm-camera(  350): isp_pipeline_util_reset: module id = 3, action = 0xb6e80461
E/mm-camera(  350): isp_pipeline_util_reset: module id = 4, action = 0xb6e6ea85
E/mm-camera(  350): isp_pipeline_util_reset: module id = 5, action = 0xb6e68561
E/mm-camera(  350): isp_pipeline_util_reset: module id = 7, action = 0xb6e6e0e1
E/mm-camera(  350): isp_pipeline_util_reset: module id = 8, action = 0xb6e7ea49
E/mm-camera(  350): isp_pipeline_util_reset: module id = 10, action = 0xb6e81eb5
E/mm-camera(  350): isp_pipeline_util_reset: module id = 11, action = 0xb6e7ba59
E/mm-camera(  350): isp_pipeline_util_reset: module id = 12, action = 0xb6e790f5
E/mm-camera(  350): isp_pipeline_util_reset: module id = 13, action = 0xb6e82a65
E/mm-camera(  350): isp_pipeline_util_reset: module id = 14, action = 0xb6e77389
E/mm-camera(  350): isp_pipeline_util_reset: module id = 15, action = 0xb6e8118d
E/mm-camera(  350): isp_pipeline_util_reset: module id = 16, action = 0xb6e74cf5
E/mm-camera(  350): isp_pipeline_util_reset: module id = 17, action = 0xb6e785d9
E/mm-camera(  350): isp_pipeline_util_reset: module id = 18, action = 0xb6e60931
E/mm-camera(  350): isp_pipeline_util_reset: module id = 19, action = 0xb6e73a55
E/mm-camera(  350): isp_pipeline_util_reset: module id = 20, action = 0xb6e77db9
E/mm-camera(  350): isp_pipeline_util_reset: module id = 22, action = 0xb6e65e39
E/mm-camera(  350): isp_pipeline_util_reset: module id = 23, action = 0xb6e7630d
E/mm-camera(  350): isp_proc_async_command: X ISP_ASYNC_COMMAND_STREAMOFF = 2
E/mm-camera(  350): isp_proc_async_command: X, session_id = 2, async_cmd_id = 2
E/mm-camera(  350): isp_streamoff: X, session_id = 2
E/mm-camera(  350): port_isp_mct_ctrl_cmd: X, identity = 0x20002, isp_streamoff
E/mm-camera(  350): ispif_proc_streamoff: Enter
E/mm-camera(  350): ispif_proc_streamoff: Make ISPIF_CFG IOCTL!
E/mm-camera(  350): ispif_proc_streamoff: ISPIF_CFG IOCTL returns!
E/mm-camera(  350): ispif_proc_streamoff: X, rc = 0
E/mm-camera(  350): ispif_streamoff: session_id = 2, active_streams = 0
E/mm-camera(  350): release_isp_resource <------
E/mm-camera(  350): release isp0 rdi
E/mm-camera(  350): release_isp_resource: isp_id = 0, camif_session_bit = 0x0
E/mm-camera-sensor(  350): module_sensor_is_ready_for_stream_off:1220 any bundle started 0
E/mm-camera-sensor(  350): sensor_util_change_state:1116 STATEDBG Enter
E/mm-camera-sensor(  350): sensor_util_change_state:1123 STATEDBG Enter cur state 4 new state 0
E/mm-camera-sensor(  350): sensor_util_change_state:1162 STATEDBG Exit cur state 0 new state 0
E/mm-camera-sensor(  350): sensor_util_change_state:1166 STATEDBG Exit
E/mm-camera-sensor(  350): module_sensor_module_process_event:3557 X STATEDBG MCT_EVENT_CONTROL_STREAMOFF
E/mm-camera(  350): main: return true, return type 0
E/mm-camera(  350): main: return true, return type 2
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera-intf(  325): mm_stream_fsm_reg: invalid state (5) for evt (8), in(0x0), out(0x0)
E/mm-camera-intf(  325): mm_stream_unreg_buf: fd=70, VIDIOC_REQBUFS failed, rc=-1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/QCameraStream(  325): int32_t qcamera::QCameraStream::putBufs(mm_camera_map_unmap_ops_tbl_t*): map_stream_buf failed: -1
E/QCameraChannel(  325): start: m_camOps->start_channel failed
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): server_process_hal_event:__DBG__ E event id=3
E/mm-camera(  350): server_process_hal_event:__DBG__ X sucess event id=3
E/mm-camera(  350): mct_pipeline_process_set:command=800000b
E/mm-camera(  350): main: return true, return type 0
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): server_process_hal_event:__DBG__ E event id=3
E/mm-camera(  350): server_process_hal_event:__DBG__ X sucess event id=3
E/mm-camera(  350): mct_pipeline_process_set:command=800000b
E/mm-camera-sensor(  350): port_sensor_unlink_func:662 ide 20002
E/mm-camera-sensor(  350): port_sensor_caps_unreserve:220 ide 20002
E/mm-camera(  350): port_isp_unlink_func: E, identity = 0x20002, port = 0xb4cb0460, direction = 2
E/mm-camera(  350): port_isp_unlink_func: X, ret = 0, identity = 0x20002, port = 0xb4cb0460, direction = 2
E/mm-camera(  350): port_isp_unlink_func: E, identity = 0x20002, port = 0xb4cb08e0, direction = 1
E/mm-camera(  350): port_isp_unlink_func: X, ret = 0, identity = 0x20002, port = 0xb4cb08e0, direction = 1
E/mm-camera(  350): cpp_port_check_caps_unreserve:170, identity=0x20002
E/mm-camera(  350): cpp_port_check_caps_unreserve:179, identity=0x20002, unreserved
E/mm-camera(  350): module_faceproc_port_unlink:758] E
E/mm-camera(  350): module_faceproc_port_unlink:785] X
E/mm-camera(  350): cpp_port_check_caps_unreserve:170, identity=0x20002
E/mm-camera(  350): cpp_port_check_caps_unreserve:179, identity=0x20002, unreserved
E/mm-camera(  350): module_faceproc_port_check_caps_unreserve:914] E
E/mm-camera(  350): module_faceproc_client_destroy:1159] state 1
E/mm-camera-img(  350): faceproc_comp_deinit:79]
E/mm-camera-img(  350): faceproc_comp_abort:549] state 1
E/mm-camera-img(  350): faceproc_comp_eng_destroy:1856] faceproc engine clean
E/mm-camera-img(  350): faceproc_comp_eng_reset:1880]
E/mm-camera(  350): module_faceproc_client_destroy:1184] X
E/mm-camera(  350): module_faceproc_port_check_caps_unreserve:963] X
E/mm-camera(  350): mct_stream_check_name:mod=sensor, name=isp
E/mm-camera(  350): mct_stream_check_name:mod=iface, name=isp
E/mm-camera(  350): mct_stream_check_name:mod=isp, name=isp
E/mm-camera(  350): mct_stream_get_module: module: 0xb4c1be10
E/mm-camera(  350): port_isp_unlink_func: E, identity = 0x20002, port = 0xb4cb0760, direction = 1
E/mm-camera(  350): port_isp_unlink_func: X, ret = 0, identity = 0x20002, port = 0xb4cb0760, direction = 1
E/mm-camera(  350): q3a_port_unlink X refcnt 1
E/mm-camera(  350): asd_port_ext_unlink E
E/mm-camera(  350): asd_port_ext_unlink  X refcnt 1
E/mm-camera(  350): stats_port_unlink: X
E/mm-camera(  350): stats_port_check_caps_unreserve E
E/mm-camera(  350): q3a_port_event: Stream type change event received!
E/mm-camera(  350): stats_port_check_caps_unreserve X
E/mm-camera(  350): main: return true, return type 0
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): main: return true, return type 1
E/mm-camera(  350): server_process_hal_event:__DBG__ E event id=3
E/mm-camera(  350): server_process_hal_event:__DBG__ X sucess event id=3
E/mm-camera(  350): mct_pipeline_process_set:command=800000b
E/mm-camera(  350): mct_stream_streamoff: Enter
E/mm-camera(  350): mct_stream_streamoff: STREAMING OFFstream_type = 3
E/mm-camera-sensor(  350): module_sensor_module_process_event:3542 ide 20003 MCT_EVENT_CONTROL_STREAMOFF
E/mm-camera-sensor(  350): module_sensor_module_process_event:3545 E STATEDBG MCT_EVENT_CONTROL_STREAMOFF
E/mm-camera-sensor(  350): sensor_util_change_state:1116 STATEDBG Enter
E/mm-camera-sensor(  350): sensor_util_change_state:1123 STATEDBG Enter cur state 0 new state 4
E/mm-camera-sensor(  350): sensor_util_change_state:1162 STATEDBG Exit cur state 4 new state 4
E/mm-camera-sensor(  350): sensor_util_change_state:1166 STATEDBG Exit
E/mm-camera-sensor(  350): module_sensor_stream_off:3097 ide 20003 MCT_EVENT_CONTROL_STREAMOFF
E/mm-camera(  350): port_isp_mct_ctrl_cmd: type=2
E/mm-camera(  350): port_isp_mct_ctrl_cmd: E, identity = 0x20003, STREAMOFF
E/mm-camera(  350): stats_port_event stream_on_counter is negative -1 !!!
E/AF_PORT (  350): af_port_handle_control_event: stream_on_refcnt -1
E/mm-camera(  350): port_isp_mct_ctrl_cmd: E, identity = 0x20003, isp_streamoff
E/mm-camera(  350): isp_streamoff: E, session_id = 2
E/mm-camera(  350): isp_proc_async_command: E ISP_ASYNC_COMMAND_STREAMOFF = 2
E/mm-camera(  350): isp_proc_streamoff: E, session_id = 2, stream_id = 3, stream_type = 3
E/mm-camera(  350): isp_proc_async_command: X ISP_ASYNC_COMMAND_STREAMOFF = 2
E/mm-camera(  350): isp_proc_async_command: X, session_id = 2, async_cmd_id = 2
E/mm-camera(  350): isp_streamoff: X, session_id = 2
E/mm-camera(  350): port_isp_mct_ctrl_cmd: X, identity = 0x20003, isp_streamoff
E/mm-camera(  350): ispif_proc_streamoff: Enter
E/mm-camera(  350): ispif_proc_streamoff: X, rc = 0
E/mm-camera(  350): ispif_streamoff: session_id = 2, active_streams = -1
E/mm-camera-sensor(  350): module_sensor_is_ready_for_stream_off:1211 can't find bundle with id=7936
E/mm-camera-sensor(  350): sensor_util_change_state:1116 STATEDBG Enter
E/mm-camera-sensor(  350): sensor_util_change_state:1123 STATEDBG Enter cur state 4 new state 0
E/mm-camera-sensor(  350): sensor_util_change_state:1162 STATEDBG Exit cur state 0 new state 0
E/mm-camera-sensor(  350): sensor_util_change_state:1166 STATEDBG Exit
E/mm-camera-sensor(  350): module_sensor_module_process_event:3557 X STATEDBG MCT_EVENT_CONTROL_STREAMOFF
E/mm-camera-sensor(  350): port_sensor_unlink_func:662 ide 20003
E/mm-camera-sensor(  350): port_sensor_caps_unreserve:220 ide 20003
E/mm-camera(  350): port_isp_unlink_func: E, identity = 0x20003, port = 0xb4cb0460, direction = 2
E/mm-camera(  350): isp_unlink_sink_port: ad hoc sink port unlinked, session_id = 2
E/mm-camera(  350): port_isp_unlink_func: X, ret = 0, identity = 0x20003, port = 0xb4cb0460, direction = 2
E/mm-camera(  350): mct_stream_check_name:mod=sensor, name=isp
E/mm-camera(  350): mct_stream_check_name:mod=iface, name=isp
E/mm-camera(  350): mct_stream_check_name:mod=isp, name=isp
E/mm-camera(  350): mct_stream_get_module: module: 0xb4c1be10
E/mm-camera(  350): port_isp_unlink_func: E, identity = 0x20003, port = 0xb4cb0760, direction = 1
E/mm-camera(  350): port_isp_unlink_func: X, ret = 0, identity = 0x20003, port = 0xb4cb0760, direction = 1
E/mm-camera(  350): af_thread_handler: af thread returned
E/mm-camera(  350): q3a_port_unlink X refcnt 0
E/mm-camera(  350): afd_thread_en_q_msg thread -1282028928 is set to inactive
E/mm-camera(  350): asd_port_ext_unlink E
E/mm-camera(  350): asd_port_ext_unlink: asd_data=0xb39a4000
E/mm-camera(  350): asd_thread_stop E
E/mm-camera(  350): asd_thread_en_q_msg:78 Message Stop Thread
E/mm-camera(  350): asd_thread_handler: asd thread returned
E/mm-camera(  350): asd_thread_stop joined
E/mm-camera(  350): asd_port_ext_unlink  X refcnt 0
E/mm-camera(  350): stats_port_unlink: X
E/mm-camera(  350): stats_port_check_caps_unreserve E
E/mm-camera(  350): stats_port_check_reserved_stream: private->reserved_id=0x20000
E/mm-camera(  350): stats_port_check_caps_unreserve X
E/mm-camera(  350): main: return true, return type 0
E/QCameraStateMachine(  325): int32_t qcamera::QCameraStateMachine::procEvtPreviewStoppedState(qcamera::qcamera_sm_evt_enum_t, void*): CAM_EVENT_TYPE_DAEMON_DIED
E/SecCameraCoreManager(  325): notifyErrorCallback(1, 100, 0)
E/SecCameraCoreManager(  325): CAMERA_MSG_ERROR from under SecCameraCoreManager - 100
E/SecCamera-JNI-Java(10666): Error 100
E/WindowState( 1484): getStack: Window{1bb1716 u0 com.android.settings/com.android.settings.settingssearch.SettingsSearchActivity} couldn't find taskId=3 Callers=com.android.server.wm.WindowState.computeFrameLw:1050 com.android.internal.policy.impl.PhoneWindowManager.layoutWindowLw:4914 com.android.server.wm.WindowManagerService.performLayoutLockedInner:10880 com.android.server.wm.WindowManagerService.performLayoutAndPlaceSurfacesLockedInner:11814
E/WindowState( 1484): getStack: Window{1bb1716 u0 com.android.settings/com.android.settings.settingssearch.SettingsSearchActivity} couldn't find taskId=3 Callers=com.android.server.wm.WindowState.computeFrameLw:1050 com.android.internal.policy.impl.PhoneWindowManager.layoutWindowLw:4914 com.android.server.wm.WindowManagerService.performLayoutLockedInner:10946 com.android.server.wm.WindowManagerService.performLayoutAndPlaceSurfacesLockedInner:11814
E/WindowState( 1484): getStack: Window{1bb1716 u0 com.android.settings/com.android.settings.settingssearch.SettingsSearchActivity} couldn't find taskId=3 Callers=com.android.server.wm.WindowState.computeFrameLw:1050 com.android.internal.policy.impl.PhoneWi

---

Strange image and video rotation problem

My girlfriend has an M8 and everything she photographs and posts on Facebook to me shows up rotated on it's side. When she views it on her phone, it rotates to the proper orientation automatically. It's only when she posts them on Facebook that everything goes 90 degrees off-kilter. I'll post a picture once I'm ALLOWED to. Silly anti-spam rules....

[Q] Mate 7 Strange Problem

Hello
I buy a huwaei ascend mate 7 two or three months ago.
after someday i notice that phone goes to a mode with gray background that shows a viewpager with one clock and musicplayer on each page and the phone doesn't allow to do anything else. there is no button to exit this mode, after reset or full wipe the phone stay in this mode too.
even after flash the official firmware the phone stay on this mode.
in this mode mobile rings and i can answer calls, but i can call to anyone, and cant do anything but play music and see the watch.

at first this happen one time in a day and handset goes off this mode quickly, but now in a day just two or three hours the phone is available.
the phone randomly goes off this mode and then get back to that.

anybody have any idea about this problem?

thanks

Strange brick or what???

Hi there
Got strange problem with my friend's Galaxy S2 I9100.

One day it gone hot and then turned off. Now it stucks in Samsung Galaxy SII logo and when I get into recovery I have a lot of red warnings (photo below):
Attachment 3475964

I tried to flash stock ROM, but Odin can't flash it:

Code:

---

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XXMS7_I9100OXAMS7_I9100XXMS2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

---

Tried on Odin 1.3, 1.83, 1.85 and 3.09 - all the time the same error.

Tried to flash PIT file with KI3 3-file firmware but..

Code:

---

<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKI3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!

---

And nothing else.......

Phone gets into Download Mode or stucks in Samsung Galaxy SII logo.
Now I can't get into recovery :/

As my friend told me, he had Android ICS on it so I think he had insane chip with brickbug.
But.. he didn't flash any custom roms, custom kernels etc. He only upgraded his i9100 from GB to ICS.

Any ideas? :crying: :crying: :crying: :crying:

Attached Thumbnails

 

Help required on strange UI Icons

Hello, my friends,

Greetings from a old timer. I am a Nexus 5 user and my OS is 5.1.1

I have a LG Adaptor and I have a LG Cable to charge my phone.

Last night when I was plugging in my phone (I was quite sleepy), I saw (or I think I saw) the following:

- A charging ICON (saying Speed or Fast or something like that) and a 15% number
- On touching that pop up it vanished

Has anyone ever seen that ? I am trying to reproduce that and I am failing.

I have a factory build LMY48B and the Baseband version is M8974A-2.0.50.2.26

Please, can someone shed some light or was I seeing things ?

I just connected my charger cable to charger and the other side to the Nexus 5. Properly, I might add.

Thanks and best wishes

Sudipta Sen

Strange behavior

I'm using Google keyboard and yesterday started going crazy where the m was being pressed repeatedly. It kept trying to go in my mail app and open the top email and respond. It took a couple of reboots and then it stopped. Why do you think this happened? I've never dropped or had any issues whatsoever with it since day 1. Any ideas?

Very strange background data behavior

I have had the WD 2 Go app installed for a while and hardly used it at all, but today I got a notification that my device was too hot and would shut down. I then checked and saw that WD 2 Go had used something like 40% of my battery, and had used 2152 mb on LTE! (I did confirm this was billed by ATT and not just indicated by my device) So somehow the app opened itself and started a download or a stream. My internal storage is now 100% full and I cannot find any files on my internal storage that would correspond to this. (My microsd slot is currently not working).

And a little while after I stopped the WD 2 Go app and restricted background data I noticed Google Play music started something similar except this time I was on wifi. And I find it odd because I have rarely if ever used Google Play music and definitely not recently.

Yes, I have installed ATT's most recent update from 9/10.

See attached screenshots.

Attached Thumbnails

 


 

N910T3 Strange Problems. Please Help!

Ok so I get a brand spankin' new warranty swap and its a N910T3 with 5.1.1 etc. Awesome right? Well not so fast.
I seem to be encountering several strange problems I wanted to see if anyone else had these issues.

First off I started having some issues with the fingerprint scanner. Not reading or scanning as its has been flawless. It occasionally has thrown a "Scanner not working" error and makes me use my backup.
Next occasionally there's some strange lag here and there. I don't mean usual android or sammy lag I mean like something just isn't right lag.
Not sure if the lag is the same but on occasion in the middle of doing something like texting or emailing it will just show the background wallpaper freeze for a few secs and then eventually lock itself.
Also if my phone screen is off and locked and I get some form of notification unlocking the phone acts strange.
All of the issues seem to be more annoying then anything. I have not had any kind of FC at all just pauses and freezes and lags.
This is night and day from my old phone that I used for almost a year. I am just trying to find out if this is perhaps a hardware defect or bugs in this Android version. I am kind of hoping its bugs this phone is squeaky new and it would be a shame to lose this shiny new phone for a old refurb.

Has anyone experienced any issues with their N910T3 while on the latest stock?

Strange issue after screen replacement (See screenshots)

Hi all,

I've just replaced my screen on my Nexus 6, boots fine but when Android starts to load the resolutions/screen is all messed up.

Same issue here https://www.reddit.com/r/nexus6/comm...cement_update/

I've re-imaged as well.

Screenshots here
http://imgur.com/a/1jyFy

Any help would be much appreciated

Stu

strange bootloop

my mi4i runs out of battery and turns off itself. The moment i plug it to power, instead of showing charging screen, it stuck on mi logo like a bootloop.
at first i wont boot at all, i cant enter recovery and fastboot mode too.
after i charge it about 5 hours, i can enter fastboot. then i flash it with fastboot rom.
but after flashing the problem persist.
i have a bootloop, i cant get into recovery but i can get into fastboot. but, flashing rom wont do anything.
anyone can help me?

strange

I won't buy it, manufacturer never force it's customers. in this day many device don't have Micro SD and Removable Battery. don't know what the reason ?

Need Help With Strange Problem

Hi all im having a strange problem that i can't figure out my XZ C6603 won't boot properly stock lp won't boot after second boot splash i just get a black screen i have tried flashing diffrent ftfs with no luck so i unlocked the bootloader and flashed CM12.1 but that even won't finnish boot propperly it just hangs on starting apps. I'm at a loss in all my years here i've never encounterd this problem or heard of it so i need some help or advice please. Thanks.

Strange earpiece sound issue

Thanks all for taking the time to read. I have a Verizon Galaxy Note 3, 4.4.2 NC2, Rooted with stock rom. The earpiece sound is playing however, and I know this sounds strange, the sounds is playing mostly opposite to the front side of the phone. It is much louder on the back side. It is as if the normal front firing side of a speaker has been reversed to fire sound in the opposite direction. The sound is neither garbled, nor distorted, it is however to low for me to hear properly from the front which has two effects, the 1st being that calls without headphones plugged in are useless, 2nd and vastly more important, is that I am unable to convince onlookers that I am not entirely retarded as they watch me hold the back side of the phone to my face while the shiny bright screen illuminates, and thereby alerts all in the vicinity to snap photos. Under normal circumstances I would be embarrassed, but 3-5 times a week a few good souls walk by and drop money near me or offer kinds words of encouragement like "Limitations only go so far son, you keep trying" or "You keep playing the hand your dealt, one day you will think the game was worth the while" or my personal favorite " Good job buddy, there are no disabilities, only people with other abilities"

Things have tried so far:

Factory reset - No help
Changed Rom - No help
Changed speaker module - No help

If anyone has any suggestions I would be most appreciative.

Strange earpiece sound issue

Thanks all for taking the time to read. I have a Verizon Galaxy Note 3, 4.4.2 NC2, Rooted with stock rom. The earpiece sound is playing however, and I know this sounds strange, the sounds is playing mostly opposite to the front side of the phone. It is much louder on the back side. It is as if the normal front firing side of a speaker has been reversed to fire sound in the opposite direction. The sound is neither garbled, nor distorted, it is however to low for me to hear properly from the front which has two effects, the 1st being that calls without headphones plugged in are useless, 2nd and vastly more important, is that I am unable to convince onlookers that I am not entirely retarded as they watch me hold the back side of the phone to my face while the shiny bright screen illuminates, and thereby alerts all in the vicinity to snap photos. Under normal circumstances I would be embarrassed, but 3-5 times a week a few good souls walk by and drop money near me or offer kinds words of encouragement like "Limitations only go so far son, you keep trying" or "You keep playing the hand your dealt, one day you will think the game was worth the while" or my personal favorite " Good job buddy, there are no disabilities, only people with other abilities"

Things have tried so far:

Factory reset - No help
Changed Rom - No help
Changed speaker module - No help

If anyone has any suggestions I would be most appreciative.

Strange signal issue

as the tittle speaking , im having a very very strange issue on my note 3 , when i use my main sim card , i get a very low signal ; i have even managed to change it , without any further results , i then decided to use another sim card from another carrier , then i got full signal bars , i have tried to factory reset my phone , but without any results , the only thing i didnt do is flashing my device as i dont want to use lolipop , as it is impossible to go back into an older stock firmware , by the way i did not root my device and im not looking into it , im still not sure if its a hardware issue or software , i am really confused , hope someone could help me
thank you in advance
EDIT : i forgot to mention that when i use my main sim card into another phone i get no problem at all .

A strange kind of BOOTLOOPs I need professional help!

Hi guys!

It is a bit crazy story so I will give you some details about it ...
I have an Ace 3 Duos GT-S7272 crazy device. I used to have so many issues with it but managed to solve it such as when I encrypted the external SDcard and it was the stupidest thing to do in an Android (cause it didn't actually encrypt a shi*) it just caused my phone to stuck in a bootloop as long as any SDcard is in it, remove it and all will work fine

- ((I somehow managed to fix it and it worked with SDcard but it used to reboot once then on the second boot it was almost perfect!))

- one day out of a sudden, stuck in a strange bootloop!! it boots fine to the startup and I can use it normally for 2 to 4 seconds and it REBOOTS again and again!
- I wiped cache didn't work ,,, still bootlooping
- I tried Safe Mode the same bootlooping
- I am leaving the Factory Reset option as my last resort and I am seeking your help guys so I don't lose my really important information on it !
- it is rooted ((but as I googled around I get the stock menu of Vup+M+power))
- I don't have a back up ((I have bad experiences with Backups))
- I strongly think that it can be saved without losing my information, cause it starts up normally for few seconds ((2 to 4)) and I could change things like Airplane Mode on/off

I really appreciate any help guys,,, I have been googling for days about this :(

A strange kind of BOOTLOOPs I need professional help!

Hi guys!

It is a bit crazy story so I will give you some details about it ...
I have an Ace 3 duos GT-S7272 crazy device. I used to have so many issues with it but managed to solve it such as when I encrypted the external SDcard and it was the stupidest thing to do in an Android (cause it didn't actually encrypt a shi*) it just caused my phone to stuck in a bootloop as long as any SDcard is in it, remove it and all will work fine

- ((I somehow managed to fix it and it worked with SDcard but it used to reboot once then on the second boot it was almost perfect!))

- one day out of a sudden, stuck in a strange bootloop!! it boots fine to the startup and I can use it normally for 2 to 4 seconds and it REBOOTS again and again!
- I wiped cache didn't work ,,, still bootlooping
- I tried Safe Mode the same bootlooping
- I am leaving the Factory Reset option as my last resort and I am seeking your help guys so I don't lose my really important information on it !
- it is rooted ((but as I googled around I get the stock menu of Vup+M+power))
- I don't have a back up ((I have bad experiences with Backups))
- I strongly think that it can be saved without losing my information, cause it starts up normally for few seconds ((2 to 4))

I really appreciate any help guys,,, I have been googling for days about this :(

N910F - strange issues with charging

Hello everybody,

- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)

This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.

Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?

Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.

Hope there's still hope for me :)

Cheers,
Fachtal

[Q] Phone suddenly behaves extremely strange (no charging, home button does not work)

I had the phone rooted and suddenly started to behave stranger and stranger as the day passed:
- pressing the volume keys would wake up the phone
- the processor did not enter deep sleep
- charging did not work while the phone was on.

What I did was to re-lock my phone. After that unlock it, flash TWRP and then 100% Pure Stock 5.0.2 7.19.401.22 CL482424 release-keys from http://forum.xda-developers.com/htc-...01-22-t3121417

Unfortunately the phone works even worse now:
- pressing the volume keys would wake up the phone
- the processor did not enter deep sleep
- charging did not work while the phone was on.
+
- can not download any app from play store
- home button does not work at all
- notification area does not appear
- get constant error messages that System UI has stopped

Even if I flash a backup that previously worked I still get this problems.
Could the fact that I had xposed framework installed cause this ? (I thought when relocking the phone for sure any files used there would be deleted)

Unfortunately I have not found the RUU for my phone to download (only on a paid site and really doubt this would work)

Has anyone encountered this problem or have a possible solution ?