FORUMS

Mysterious GG1 Google Device Stops by FCC. Glass v2?

As the year progresses, we draw further away from Google’s annual I/O … more

Material and Material Dark Hit Samsung’s Theme Store

The latest version of Touchwiz, launched alongside the Galaxy S6 and S6 Edge, … more

Swappa’s New App Helps You Value Your Device

There comes a sad time in everyone’s life where you must part ways with your … more

Xiaomi Sold 34.7 Million Phones In 6 Months

2015 has been a phenomenal year for Xiaomi so far. With a stellar rise in 2014, 2015 saw … more

 View Poll Results: Did the 270 MHz frequency step increase your battery life ?

Yes
 
95 Vote(s)
36.40%
No
 
19 Vote(s)
7.28%
I don't know
 
89 Vote(s)
34.10%
I don't use this step
 
58 Vote(s)
22.22%

[KERNEL][Sony JB 4.3][26.04.15] Williams kernel v9.1

753 posts
Thanks Meter: 854
 
By pec0ra, Senior Member on 13th May 2014, 07:10 PM
Post Reply Subscribe to Thread Email Thread
24th June 2015, 02:44 AM |#741  
sambastrakan's Avatar
Senior Member
Flag Rio de Janeiro
Thanks Meter: 125
 
More
this is the logcat when phone does not wake up:

I/PowerManagerService( 1647): Waking up from sleep...
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
I/sysmon-tsens_tz_sensor3( 1216): sensor_work - read value = 350
I/sysmon-tsens_tz_sensor0( 1216): sensor_work - read value = 360
W/View ( 1803): requestLayout() improperly called by android.widget.TextClock{41ed5cb0 V.ED.... ......ID 104,0-484,213 #7f0a004a app:id/clock_view} during layout: running second layout pass
W/View ( 1803): requestLayout() improperly called by android.widget.TextClock{41f895b8 V.ED.... ......ID 221,0-367,38 #7f0a004f app:id/date_view} during layout: running second layout pass
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
I/WindowManager( 1647): Lock screen displayed!
D/DisplayPowerController( 1647): Unblocked screen on after 4221132 ms
W/ActivityManager( 1647): getAssistContextExtras failed: no resumed activity

Phone is not freezed, I can enter shell command. But if I type: stop and then start commands it does a hot reboot but I will not be able to wake up the phone again. Full reboot needed to solve temporqrily the bug.
Last edited by sambastrakan; 24th June 2015 at 03:16 AM.
 
 
24th June 2015, 08:25 AM |#742  
pec0ra's Avatar
OP Senior Member
Thanks Meter: 854
 
Donate to Me
More
Quote:
Originally Posted by sambastrakan

this is the logcat when phone does not wake up:

I/PowerManagerService( 1647): Waking up from sleep...
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
I/sysmon-tsens_tz_sensor3( 1216): sensor_work - read value = 350
I/sysmon-tsens_tz_sensor0( 1216): sensor_work - read value = 360
W/View ( 1803): requestLayout() improperly called by android.widget.TextClock{41ed5cb0 V.ED.... ......ID 104,0-484,213 #7f0a004a app:id/clock_view} during layout: running second layout pass
W/View ( 1803): requestLayout() improperly called by android.widget.TextClock{41f895b8 V.ED.... ......ID 221,0-367,38 #7f0a004f app:id/date_view} during layout: running second layout pass
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
D/PowerManagerService( 1647): acquireWakeLock: ignoring request from com.google.android.gms
I/WindowManager( 1647): Lock screen displayed!
D/DisplayPowerController( 1647): Unblocked screen on after 4221132 ms
W/ActivityManager( 1647): getAssistContextExtras failed: no resumed activity

Phone is not freezed, I can enter shell command. But if I type: stop and then start commands it does a hot reboot but I will not be able to wake up the phone again. Full reboot needed to solve temporqrily the bug.

Thanks for the log ! However, if it is a kernel problem, the dmesg will be more useful.
Please put this kind of log in a file or between the code tag next time so we can read it better.
24th June 2015, 12:04 PM |#743  
sambastrakan's Avatar
Senior Member
Flag Rio de Janeiro
Thanks Meter: 125
 
More
Quote:
Originally Posted by pec0ra

Thanks for the log ! However, if it is a kernel problem, the dmesg will be more useful.
Please put this kind of log in a file or between the code tag next time so we can read it better.

dmesg log attached. will make an other one when the bug appears again.
it never happened with stock kernel so I think it's the guilty. Happened 3 times in one week with this kernel.
also, if you build a new version, it could be a very good idea to update twrp to 2.8.6 (so good to access sdcard phone and be able to use adb too)
there is also the bug of 1970 dates. there is a workaround: if i use integrated recovery of my rom dates are ok (I can post ramdisk and recovery stuff if you want)

Thanks
Attached Files
File Type: zip dmesg.zip - [Click for QR Code] (24.6 KB, 6 views)
24th June 2015, 09:41 PM |#744  
sambastrakan's Avatar
Senior Member
Flag Rio de Janeiro
Thanks Meter: 125
 
More
"fota partition support". For some reason I'm not able to flash a recovery with fastboot but I did it with dd if=twrp.img of=/dev/block/mmcblk0p11
But at kernel boot I can't enter this flashed recovery. I tried vol+, vol- and camera btn.
Anyone else or just me ??

[edit] also tried flashing with rashr app, nothing.
Last edited by sambastrakan; 25th June 2015 at 02:31 AM.
25th June 2015, 01:04 PM |#745  
pec0ra's Avatar
OP Senior Member
Thanks Meter: 854
 
Donate to Me
More
Quote:
Originally Posted by sambastrakan

"fota partition support". For some reason I'm not able to flash a recovery with fastboot but I did it with dd if=twrp.img of=/dev/block/mmcblk0p11
But at kernel boot I can't enter this flashed recovery. I tried vol+, vol- and camera btn.
Anyone else or just me ??

[edit] also tried flashing with rashr app, nothing.

Thanks for pointing this out. It is highly possible that fota doesn't work. I'm not using it. I'll look at it when I have time.
29th June 2015, 10:50 PM |#746  
sambastrakan's Avatar
Senior Member
Flag Rio de Janeiro
Thanks Meter: 125
 
More
Here is the dmesg log when the phone refuses to wake up.
If I use the stop and start commands in shell, the phone restarts, I can login while lockscreen is on. If I let lockscreen turing off the phone don't wake up, and anyway next time it will sleep it won't wake up. Full reboot needed to solve the problem until next time.
Attached Files
File Type: zip dmesg.zip - [Click for QR Code] (16.5 KB, 4 views)
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes