Issue #1167: Samsung Galaxy Note 2 N7100 - Screen rotation not working - Replicant

Actions

Copy link

Issue #1167

closed

Samsung Galaxy Note 2 N7100 - Screen rotation not working

Added by Olivier Mondoloni over 9 years ago. Updated about 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Framework

Target version:

Replicant 4.2

Start date:

01/06/2015

Due date:

% Done:

Estimated time:

Resolution:

Device:

Galaxy Note 2 (GT-N7100), Galaxy Note 2 (N7100)

Grant:

Type of work:

Description

Hi,

I have a Samsung Galaxy Note 2 device ( N7100 ) with the lastest Replicant image on it .
I am happy with it but I have one problem : the screen rotation doesn't seem to work ( K9 Mail, Lightning ... ) .
My settings are good in Settings > Display > Rotation .
I attached screen_rotation.log file aka main log buffer from adb command ( adb logcat -b main ).

Thank you

Files

Download all files

screen_rotation.log (204 KB) screen_rotation.log		Olivier Mondoloni, 01/06/2015 09:48 AM
dmesg.log (130 KB) dmesg.log		Sam Sung, 02/27/2016 12:39 PM
main.log (98.1 KB) main.log		Sam Sung, 02/27/2016 12:39 PM

Related issues

Related to Replicant - Issue #1755: GT-N7100 sensors don't work

Feedback

CyberLeo Kitsana

10/03/2016

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Paul Kocialkowski over 9 years ago

Description updated (diff)

The relevant part in the log is the following:

D/smdk4x12_sensors( 2252): smdk4x12_sensors_open(0x59f53200, poll, 0x50d48e00)
D/smdk4x12_sensors( 2252): lsm330dlc_acceleration_init(0x59f5334c, 0x5e585ae0)
E/smdk4x12_sensors( 2252): lsm330dlc_acceleration_init: Unable to open input
D/smdk4x12_sensors( 2252): akm8963_init(0x59f532bc, 0x5e585ae0)
E/smdk4x12_sensors( 2252): akm8963_init: Unable to open device
D/smdk4x12_sensors( 2252): orientation_init(0x59f5328c, 0x5e585ae0)
D/smdk4x12_sensors( 2252): cm36651_proximity_init(0x59f532ec, 0x5e585ae0)
E/smdk4x12_sensors( 2252): cm36651_proximity_init: Unable to open input
D/smdk4x12_sensors( 2252): cm36651_light_init(0x59f5331c, 0x5e585ae0)
E/smdk4x12_sensors( 2252): cm36651_light_init: Unable to open input
D/smdk4x12_sensors( 2252): lsm330dlc_gyroscope_init(0x59f5337c, 0x5e585ae0)
E/smdk4x12_sensors( 2252): lsm330dlc_gyroscope_init: Unable to open input
D/smdk4x12_sensors( 2252): bmp180_init(0x59f533ac, 0x5e585ae0)
E/smdk4x12_sensors( 2252): bmp180_init: Unable to open input
D/smdk4x12_sensors( 2252): smdk4x12_sensors_get_sensors_list(0x59f53200, 0xbe93e454)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_activate(0x5e585ae0, 1, 0)
D/smdk4x12_sensors( 2252): lsm330dlc_acceleration_deactivate(0x59f5334c)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_activate(0x5e585ae0, 2, 0)
D/smdk4x12_sensors( 2252): akm8963_deactivate(0x59f532bc)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_activate(0x5e585ae0, 3, 0)
D/smdk4x12_sensors( 2252): orientation_deactivate(0x59f5328c)
D/smdk4x12_sensors( 2252): lsm330dlc_acceleration_deactivate(0x59f5334c)
D/smdk4x12_sensors( 2252): akm8963_deactivate(0x59f532bc)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_activate(0x5e585ae0, 5, 0)
D/smdk4x12_sensors( 2252): cm36651_light_deactivate(0x59f5331c)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_activate(0x5e585ae0, 8, 0)
D/smdk4x12_sensors( 2252): cm36651_proximity_deactivate(0x59f532ec)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_activate(0x5e585ae0, 4, 0)
D/smdk4x12_sensors( 2252): lsm330dlc_gyroscope_deactivate(0x59f5337c)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_activate(0x5e585ae0, 6, 0)
D/smdk4x12_sensors( 2252): bmp180_deactivate(0x59f533ac)
D/smdk4x12_sensors( 2252): smdk4x12_sensors_get_sensors_list(0x59f53200, 0xbe93e4fc)

Which indicates that the sensors module fails to open any of the nedded devices. Are you running the Replicant kernel or have you installed something else?

You might want to attach the output of adb shell dmesg fresh after boot. Did the sensors work on another Android version, that was installed before Replicant?
This could be a hardware issue.

Actions

Copy link

Updated by Olivier Mondoloni over 9 years ago

The command adb shell dmesg output is : klogctl: Operation not permitted
Before Replicant installation, screen rotation worked on Android 4.4.2 .
Is there a way that usb cable default could be impact Replicant installation process ?
Is there a way to reset completely the Replicant installation to do a fresh new installation ?

Actions

Copy link

Updated by Paul Kocialkowski over 9 years ago

Description updated (diff)

The command adb shell dmesg output is : klogctl: Operation not permitted

Please make sure you run:

adb root

beforehand and submit what you get then.

Is there a way that usb cable default could be impact Replicant installation process ?

That's doubtful.

Is there a way to reset completely the Replicant installation to do a fresh new installation ?

You could perform the install process again or simply select "wipe data" in recovery to have a fresh system.

Actions

Copy link

Updated by Olivier Mondoloni over 9 years ago

I fix my problem after running several tests .
First I installed the last stable version of Cyanogenmod for the N7100 device ( Cyanogenmod 10.3 ) .
On it, screen rotation worked .
Finally, I reinstalled Replicant 4.2 0003 and screen rotation is now operationnal .
I didn't know what's happened before but now everything is working fine .
Thank you

Actions

Copy link

Updated by Paul Kocialkowski over 9 years ago

Category set to 129
Status changed from New to Closed
Target version set to Replicant 4.2

Perhaps it was a firmware update that was needed. In any case, too bad you didn't grab the logs in time.

Actions

Copy link

Updated by Pep tide about 9 years ago

I also experienced this, which was fixed after flashing CM 10.1. Didn't get any logs either though, sorry.

Actions

Copy link

Updated by Denis 'GNUtoo' Carikli over 8 years ago

Category changed from 129 to Framework
Device Galaxy Note 2 (N7100) added

Actions

Copy link

Updated by Sam Sung about 8 years ago

File dmesg.log dmesg.log added
File main.log main.log added

I have the same problem here. Please reopen this ticket or tell me to create a new one.
I've the same sensor deactivation in logs and I attached the output of adb shell dmesg after a fresh reboot.
Please take a look. Of course, I want to get this working and have a workaround in place.

Actions

Copy link

Updated by Wolfgang Wiedmeyer about 7 years ago

Sam Sung wrote:

I have the same problem here. Please reopen this ticket or tell me to create a new one.
I've the same sensor deactivation in logs and I attached the output of adb shell dmesg after a fresh reboot.
Please take a look. Of course, I want to get this working and have a workaround in place.

See #1755 for further updates. Your dmesg output is missing the initial part. You need to capture it earlier. Then you probably will see output like this.

Actions

Copy link

#10