Database Develop

Pengus CM10 - 0% battery shutdown fault

I have a thing. Would someone please give me some pointers?
I'm using Pengus NewBL CM10 and has happened for all kernel updates. Currently V30a BB and default RIL on Pengus.
When I wake my phone (still on lock screen) the battery gauge jumps to 0% and the phone will perform a clean shut down.
Seems to only happen when battery is below 40%, and most regularly happens when I'm on 2G only. Has not happened on WiFi yet.
It is not BB specific. Have freshly wiped, recreated standard NewBL partitions, reloaded the bootloader....
I've attached my last_kmsg, the same fault is mentioned here but I can't see any further discussion.
Code:
[13:02:12 17:18:31.954] SysRq : Emergency Remount R/O
[13:02:12 17:18:31.974] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[13:02:12 17:18:32.114] EXT4-fs (mmcblk0p9): re-mounted. Opts: (null)
[13:02:12 17:18:32.154] Emergency Remount complete
[13:02:12 17:18:32.164] star_reboot_notify
[13:02:12 17:18:32.164] star_reboot_notify : rsbuf = wrm [3]
[13:02:12 17:18:32.164] muic_reboot_notify : 3
[13:02:12 17:18:32.174] muic_reboot_notify : disable_irq
[13:02:12 17:18:32.184] ENTER : mpu3050_power_terminate
[13:02:12 17:18:32.184] mpu3050_power_terminate..
[13:02:12 17:18:32.224] [Max8952]max8952_shutdown
[13:02:12 17:18:32.334] aat1270_shutdown
[13:02:12 17:18:32.334] [BATTERY] : battery_shutdown : Shutdown Sequence : Battery No Longer Exists.
[13:02:12 17:18:32.344] Wake9 for irq=338
[13:02:12 17:18:32.344] Disabling wake9
[13:02:12 17:18:32.344] gpio bank wake found: wake9 for irq=87
[13:02:12 17:18:32.344] Disabling wake9
[13:02:12 17:18:32.364] [CHARGER] : charger_ic_disable : Charger Disabled.
[13:02:12 17:18:32.384] Disabling non-boot CPUs ...
[13:02:12 17:18:32.384] Power down.

[ROM] [DEV ONLY] Ubuntu Phone [TEST] [Xperia T]

This is a port of Ubuntu for Phones for the Xperia T.
THIS IS VERY EXPERIMENTAL STUFF. NOTHING REALLY WORKS AS OF NOW. IT IS A HEAVY WIP.
It's based on the CM10.1 sources and kernel. Those can be found at:
https://github.com/CyanogenMod/android_kernel_sony_msm8x60
https://github.com/CyanogenMod/android_device_sony_blue-common
https://github.com/CyanogenMod/android_device_sony_mint
Also the sources for Ubuntu are at:
http://phablet.ubuntu.com/gitweb
I will be putting up my own modified sources soon.
This is nothing like Android at all. It's nowhere near being a daily either. YOU NEED ADB ACCESS BEFORE YOU CAN EVEN RUN UBUNTU.
PLEASE BACKUP BEFORE INSTALLING THIS ROM.
THIS NEEDS AN UNLOCKED BOOTLOADER.
Installation instructions:
Wipe data
Install the device specific part of Ubutnu
Install the generic Ubuntu part
Reboot to a black screen
Do adb root
Do adb shell and then the following commands:
ubuntu_chroot shell
ubuntu-session
Enjoy the testing!
Screenshots:
Coming up
Download links:
Device specific: http://goo.im/devs/tilal6991/roms/mint/ubuntu/cm-10.1-20130222-UNOFFICIAL-mint.zip
Generic: http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip

Reserved.

wow.keep up awesome work

I shall test this soon, nice work.

Nice, very nice! Congrats tilal6991, I can't wait to get my hands on this device to flash it

Which branches did you build it off?
cm-10.1 or cm-10.1-test (talking about device specific repositories)

cdesai said:
Which branches did you build it off?
cm-10.1 or cm-10.1-test (talking about device specific repositories)
Click to expand...
Click to collapse
Both work. The one I put up was built off cm-10.1-test.

tilal6991 said:
Both work. The one I put up was built off cm-10.1-test.
Click to expand...
Click to collapse
I know, but at this moment cm-10.1 is in a better stage than cm-10.1-test.

cdesai said:
I know, but at this moment cm-10.1 is in a better stage than cm-10.1-test.
Click to expand...
Click to collapse
TBH the only thing worse in test than normal is RIL. And RIL is broken either way in Ubuntu so I thought - oh well...

Cant wait for screens.thanks again Tilal

Good job.
But I prefer the LK bootloader(have a single recovery partition) with Multirom support.
If Xperia T have multirom support, the development and test will be much easier.

I've followed your instructions and the ubuntu session does not start.
This is is the error I get:
Code:
$ adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# ubuntu-session
Redirecting output to local session logs
/usr/bin/ubuntu-session: line 21: /home/phablet/.ubuntu-session/logs/ubuntu-session.log: No such file or directory
Error, do this: mount -t proc proc /proc
grep: /proc/cpuinfo: No such file or directory
Device=
Starting session bus
Started pulseaudio with pid 455 (0 secs start delay)
Started maliit-server with pid 460 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 460 Aborted ${service[1]} $arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started qml-phone-shell with pid 468 (2 secs start delay)
Got Shell pid = 468
Started chewie_messaging_populate_menu with pid 473 (0 secs start delay)
Started friends-service with pid 478 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 468 Aborted ${service[1]} $arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started manage-address-books.py with pid 509 (2 secs start delay)
Started ofono-setup with pid 551 (12 secs start delay)
Stopping services...
Stopping pulseaudio
/usr/bin/ubuntu-session: line 38: kill: (455) - No such process
Stopping maliit-server
/usr/bin/ubuntu-session: line 38: kill: (460) - No such process
Stopping qml-phone-shell
/usr/bin/ubuntu-session: line 38: kill: (468) - No such process
Stopping chewie_messaging_populate_menu
Stopping friends-service
Stopping manage-address-books.py
/usr/bin/ubuntu-session: line 38: kill: (509) - No such process
Stopping ofono-setup
Killing session bus...
Session stopped.

lilstevie said:
I've followed your instructions and the ubuntu session does not start.
This is is the error I get:
Code:
$ adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# ubuntu-session
Redirecting output to local session logs
/usr/bin/ubuntu-session: line 21: /home/phablet/.ubuntu-session/logs/ubuntu-session.log: No such file or directory
Error, do this: mount -t proc proc /proc
grep: /proc/cpuinfo: No such file or directory
Device=
Starting session bus
Started pulseaudio with pid 455 (0 secs start delay)
Started maliit-server with pid 460 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 460 Aborted ${service[1]} $arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started qml-phone-shell with pid 468 (2 secs start delay)
Got Shell pid = 468
Started chewie_messaging_populate_menu with pid 473 (0 secs start delay)
Started friends-service with pid 478 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 468 Aborted ${service[1]} $arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started manage-address-books.py with pid 509 (2 secs start delay)
Started ofono-setup with pid 551 (12 secs start delay)
Stopping services...
Stopping pulseaudio
/usr/bin/ubuntu-session: line 38: kill: (455) - No such process
Stopping maliit-server
/usr/bin/ubuntu-session: line 38: kill: (460) - No such process
Stopping qml-phone-shell
/usr/bin/ubuntu-session: line 38: kill: (468) - No such process
Stopping chewie_messaging_populate_menu
Stopping friends-service
Stopping manage-address-books.py
/usr/bin/ubuntu-session: line 38: kill: (509) - No such process
Stopping ofono-setup
Killing session bus...
Session stopped.
Click to expand...
Click to collapse
Try this:
Download https://github.com/Dazzozo/android_...rebuilt/libubuntu_application_api.so?raw=true
adb push it to /system/lib/
Download https://github.com/Dazzozo/android_...lob/ubuntu/prebuilt/ubuntuappmanager?raw=true
chmod 777 it
adb push it to /system/bin/
adb reboot
Then try the commands on the OP again.

can we install it on locked bootloader ?

sahil00150 said:
can we install it on locked bootloader ?
Click to expand...
Click to collapse
No
Sent from my LT30p using Tapatalk 2

feeling sad cause my bootloader is not unlockable

Is there any plans for full working/stable release ?
I wantto try it(maybe later) but i am noob :silly:

leonidas_s1 said:
Is there any plans for full working/stable release ?
I wantto try it(maybe later) but i am noob :silly:
Click to expand...
Click to collapse
It's only a preview build so there is only so much devs can do at the moment. It's more of a proof of concept currently
Sent from my LT30p using Tapatalk 2

matt4321 said:
It's only a preview build so there is only so much devs can do at the moment. It's more of a proof of concept currently
Sent from my LT30p using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your answer!
I hope someone can try to fix it sometime..
To be able to try it!

tilal6991 said:
Try this:
Download https://github.com/Dazzozo/android_...rebuilt/libubuntu_application_api.so?raw=true
adb push it to /system/lib/
Download https://github.com/Dazzozo/android_...lob/ubuntu/prebuilt/ubuntuappmanager?raw=true
chmod 777 it
adb push it to /system/bin/
adb reboot
Then try the commands on the OP again.
Click to expand...
Click to collapse
I get teh same issue. But i cant download the files.Page is not found

[Q] [help]build AOSPA 4+ for mi3 tegra edtion

Hi,everyone! I got into trouble when I tried to build AOSPA 4+ for mi3 tegra endtion.I successfully complied a *.zip,and successfully flash it to my device,but it always show the boot animation can not get into launcher.I have got logcat,but I am a beginner and have no knowledge about JAVA.
There is a part of locat
Code:
--------- beginning of /dev/log/main
E/nvaudio_modem(25458): Failed to get phone service!
W/AudioFlinger(25458): Thread AudioOut_2 cannot connect to the power manager service
E/AudioFlinger(25458): no wake lock to update!
I/r_submix(25458): adev_open(name=audio_hw_if)
I/r_submix(25458): adev_init_check()
I/AudioFlinger(25458): loadHwModule() Loaded r_submix audio interface from Wifi Display audio HAL (audio) handle 3
I/AudioPolicyService(25458): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
E/memtrack(25457): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug(25457): failed to load memtrack module: -2
I/SamplingProfilerIntegration(25457): Profiling disabled.
I/Zygote (25457): Preloading classes...
D/idmap (25596): error: no read access to /vendor/overlay: No such file or directory
D/TextLayoutCache(25457): Using debug level = 0 - Debug Enabled = 0
I/dalvikvm(25457): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
D/MtpDeviceJNI(25457): register_android_mtp_MtpDevice
I/dalvikvm(25457): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm(25457): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm(25457): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
E/EmojiFactory_jni(25457): Failed to load libemoji.so: dlopen failed: library "libemoji.so" not found
V/NatController(25456): runCmd(/system/bin/iptables -F natctrl_FORWARD) res=0
V/NatController(25456): runCmd(/system/bin/iptables -A natctrl_FORWARD -j DROP) res=0
V/NatController(25456): runCmd(/system/bin/iptables -t nat -F natctrl_nat_POSTROUTING) res=0
V/NatController(25456): runCmd(/system/bin/ip route flush cache) res=0
V/NatController(25456): runCmd(/system/bin/iptables -F natctrl_tether_counters) res=0
I/LibraryLoader(25457): Loading: webviewchromium
E/dalvikvm(25457): dlopen("/system/lib/libwebviewchromium.so") failed: dlopen failed: empty/missing DT_HASH in "libwebviewchromium.so" (built with --hash-style=gnu?)
W/WebViewFactory(25457): error preloading provider
W/WebViewFactory(25457): java.lang.RuntimeException: Cannot load WebView
W/WebViewFactory(25457): at com.android.org.chromium.android_webview.AwBrowserProcess.loadLibrary(AwBrowserProcess.java:31)
W/WebViewFactory(25457): at com.android.webview.chromium.WebViewChromiumFactoryProvider.<init>(WebViewChromiumFactoryProvider.java:87)
W/WebViewFactory(25457): at java.lang.Class.newInstanceImpl(Native Method)
W/WebViewFactory(25457): at java.lang.Class.newInstance(Class.java:1208)
W/WebViewFactory(25457): at android.webkit.WebViewFactory$Preloader.<clinit>(WebViewFactory.java:43)
W/WebViewFactory(25457): at java.lang.Class.classForName(Native Method)
W/WebViewFactory(25457): at java.lang.Class.forName(Class.java:251)
W/WebViewFactory(25457): at java.lang.Class.forName(Class.java:216)
W/WebViewFactory(25457): at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:307)
W/WebViewFactory(25457): at com.android.internal.os.ZygoteInit.preload(ZygoteInit.java:247)
W/WebViewFactory(25457): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:581)
W/WebViewFactory(25457): at dalvik.system.NativeStart.main(Native Method)
W/WebViewFactory(25457): Caused by: com.android.org.chromium.content.common.ProcessInitException
W/WebViewFactory(25457): at com.android.org.chromium.content.app.LibraryLoader.loadAlreadyLocked(LibraryLoader.java:135)
W/WebViewFactory(25457): at com.android.org.chromium.content.app.LibraryLoader.loadNow(LibraryLoader.java:87)
W/WebViewFactory(25457): at com.android.org.chromium.android_webview.AwBrowserProcess.loadLibrary(AwBrowserProcess.java:29)
W/WebViewFactory(25457): ... 11 more
W/WebViewFactory(25457): Caused by: java.lang.UnsatisfiedLinkError: dlopen failed: empty/missing DT_HASH in "libwebviewchromium.so" (built with --hash-style=gnu?)
W/WebViewFactory(25457): at java.lang.Runtime.loadLibrary(Runtime.java:386)
W/WebViewFactory(25457): at java.lang.System.loadLibrary(System.java:526)
W/WebViewFactory(25457): at com.android.org.chromium.content.app.LibraryLoader.loadAlreadyLocked(LibraryLoader.java:123)
W/WebViewFactory(25457): ... 13 more
V/NatController(25456): runCmd(/system/bin/iptables -X natctrl_tether_counters) res=0
V/NatController(25456): runCmd(/system/bin/iptables -N natctrl_tether_counters) res=0
W/Zygote (25457): Class not found for preloading: java.lang.UnsafeByteSequence
I/System (25457): Loaded time zone names for "" in 35ms (32ms in ICU)
E/Netd (25456): Unable to create netlink socket: Protocol not supported
E/Netd (25456): Unable to open quota2 logging socket
D/MDnsDS (25456): MDnsSdListener::Hander starting up
D/MDnsDS (25456): MDnsSdListener starting to monitor
D/MDnsDS (25456): Going to poll with pollCount 1
I/System (25457): Loaded time zone names for "en_US" in 22ms (18ms in ICU)
I/Zygote (25457): ...preloaded 2777 classes in 775ms.
I/dalvikvm(25457): System server process 25738 has been created
I/Zygote (25457): Accepting command socket connections
D/SensorService(25738): nuSensorService starting...
I/Sensors (25738): path open /dev/input/event1
I/Sensors (25738): path open /dev/input/event0
I/Sensors (25738): path open /dev/input/event6
I/Sensors (25738): path open /dev/input/event5
E/Sensors (25738): HAL:could not open trigger name
E/Sensors (25738): HAL:could not open current trigger
I/MPL-storeload(25738): Bytes read = 4340
V/Sensors (25738): HAL:MPL:inv_compass_was_turned_off
I/Sensors (25738): path open /dev/input/event1
I/Sensors (25738): path open /dev/input/event0
I/Sensors (25738): path open /dev/input/event6
I/Sensors (25738): path open /dev/input/event5
I/Sensors (25738): path open /dev/input/event4
I/Sensors (25738): path open /dev/input/event3
I/Sensors (25738): path open /dev/input/event1
I/Sensors (25738): path open /dev/input/event0
I/Sensors (25738): path open /dev/input/event6
I/Sensors (25738): path open /dev/input/event5
I/Sensors (25738): path open /dev/input/event4
I/Sensors (25738): path open /dev/input/event1
I/Sensors (25738): path open /dev/input/event0
I/Sensors (25738): path open /dev/input/event6
I/Sensors (25738): path open /dev/input/event5
I/Sensors (25738): path open /dev/input/event4
I/Sensors (25738): path open /dev/input/event3
I/Sensors (25738): path open /dev/input/event2
I/SensorService(25738): Ambient Light Sensor
I/SensorService(25738): Proximity Sensor
I/SensorService(25738): Barometer Sensor
I/SensorService(25738): Temperature Sensor
I/SensorService(25738): Gyroscope Sensor
I/SensorService(25738): Raw Gyroscope Sensor
I/SensorService(25738): Accelerometer Sensor
I/SensorService(25738): Magnetic Field Sensor
I/SensorService(25738): Orientation Sensor
I/SensorService(25738): Rotation Vector Sensor
I/SensorService(25738): Linear Acceleration Sensor
I/SensorService(25738): Gravity Sensor
D/SensorService(25738): Max socket buffer size 1048576
D/SensorService(25738): nuSensorService thread starting...
E/Sensors (25738): HAL:ERR Full data packet was not read
E/Sensors (25738): HAL:ERR Full data packet was not read
I/installd( 201): new connection
I/powerHAL::common(25738): input device id:0 present with name:tegra-kbc
I/powerHAL::common(25738): input device id:1 present with name:atmel-maxtouch
I/powerHAL::common(25738): input device id:2 present with name:bmp180
I/powerHAL::common(25738): input device id:3 present with name:lightsensor
I/powerHAL::common(25738): input device id:4 present with name:proximity
I/powerHAL::common(25738): input device id:5 present with name:compass
I/powerHAL::common(25738): input device id:6 present with name:fsa8108_sw
D/PackageManager(25738): No files in app dir /vendor/overlay
W/ResourceType(25738): Failure getting entry for 0x7f050000 (t=4 e=0) in package 0 (error -75)
W/Resources(25738): Converting to boolean: TypedValue{t=0x3/d=0x1a9a "false" a=2 r=0x7f120876}
W/ResourceType(25738): Failure getting entry for 0x7f0d01bf (t=12 e=447) in package 0 (error -75)
W/ResourceType(25738): Failure getting entry for 0x7f0d01bf (t=12 e=447) in package 0 (error -75)
W/ResourceType(25738): Failure getting entry for 0x7f130310 (t=18 e=784) in package 0 (error -75)
W/ResourceType(25738): Failure getting entry for 0x7f130310 (t=18 e=784) in package 0 (error -75)
W/ResourceType(25738): Failure getting entry for 0x7f1302f3 (t=18 e=755) in package 0 (error -75)
W/ResourceType(25738): Failure getting entry for 0x7f04000f (t=3 e=15) in package 0 (error -75)
W/ResourceType(25738): Failure getting entry for 0x7f04000f (t=3 e=15) in package 0 (error -75)
D/PackageManager(25738): No files in app dir /vendor/app
V/tspdrv (25738): opened device /dev/tspdrv
V/tspdrv (25738): TSPDRV_MAGIC_NUMBER success
V/tspdrv (25738): TSPDRV_GET_NUM_ACTUATORS success, actuators = 1
V/tspdrv (25738): TSPDRV_SET_DEVICE_PARAMETER success
V/tspdrv (25738): timeout_ms: 0
V/tspdrv (25738): TSPDRV_DISABLE_AMP success
E/ConsumerIrService(25738): Can't open consumer IR HW Module, error: -2
W/libsuspend(25738): Error writing 'on' to /sys/power/state: Invalid argument
I/libsuspend(25738): Selected autosleep
I/powerHAL::common(25738): Enabling input device:1
I/powerHAL::common(25738): Enabling input device:2
I/powerHAL::common(25738): Enabling input device:3
I/powerHAL::common(25738): Enabling input device:4
I/powerHAL::common(25738): Enabling input device:5
I/powerHAL::common(25738): Enabling input device:6
I/powerHAL::pisces(25738): average current for last screen off is 206971
D/SurfaceFlinger( 196): Screen acquired, type=0 flinger=0xc0b450
D/SurfaceFlinger( 196): screen was previously acquired
D/EventHub(25738): No input device configuration file found for device 'atmel-maxtouch'.
D/BluetoothManagerService(25738): Loading stored name and address
D/BluetoothManagerService(25738): Stored bluetooth Name=null,Address=null
W/EventHub(25738): Unable to disable kernel key repeat for /dev/input/event1: Function not implemented
I/EventHub(25738): New device: id=1, fd=135, path='/dev/input/event1', name='atmel-maxtouch', classes=0x15, configuration='', keyLayout='/system/usr/keylayout/atmel-maxtouch.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=false
D/EventHub(25738): No input device configuration file found for device 'tegra-kbc'.
W/EventHub(25738): Unable to disable kernel key repeat for /dev/input/event0: Function not implemented
I/EventHub(25738): New device: id=2, fd=136, path='/dev/input/event0', name='tegra-kbc', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/tegra-kbc.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=false
D/EventHub(25738): No input device configuration file found for device 'fsa8108_sw'.
W/EventHub(25738): Unable to disable kernel key repeat for /dev/input/event6: Function not implemented
I/EventHub(25738): New device: id=3, fd=138, path='/dev/input/event6', name='fsa8108_sw', classes=0x81, configuration='', keyLayout='/system/usr/keylayout/fsa8108_sw.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=false
D/EventHub(25738): No input device configuration file found for device 'compass'.
D/EventHub(25738): No input device configuration file found for device 'proximity'.
D/EventHub(25738): No input device configuration file found for device 'lightsensor'.
D/EventHub(25738): No input device configuration file found for device 'bmp180'.
I/InputReader(25738): Device added: id=-1, name='Virtual', sources=0x00000301
I/InputReader(25738): Device added: id=3, name='fsa8108_sw', sources=0x80000101
I/InputReader(25738): Device added: id=2, name='tegra-kbc', sources=0x00000101
I/InputReader(25738): Touch device 'atmel-maxtouch' could not query the properties of its associated display. The device will be inoperable until the display size becomes available.
I/InputReader(25738): Device added: id=1, name='atmel-maxtouch', sources=0x00001103
I/InputReader(25738): Reconfiguring input devices. changes=0x00000004
I/InputReader(25738): Device reconfigured: id=1, name='atmel-maxtouch', size 1080x1920, orientation 0, mode 1, display id 0
I/PackageManager(25738): No secure containers on sdcard
D/WifiController(25738): isAirplaneModeOn = false, isWifiEnabled = false, isScanningAvailable = false
D/BluetoothTethering(25738): startMonitoring: target: Handler (com.android.server.ConnectivityService$NetworkStateTrackerHandler) {41d2e7e0}
D/BluetoothTethering(25738): startMonitoring: mCsHandler: Handler (com.android.server.ConnectivityService$NetworkStateTrackerHandler) {41d2e7e0}
D/BluetoothManagerService(25738): Message: 20
D/BluetoothManagerService(25738): Added callback: [email protected]:true
D/BluetoothManagerService(25738): Message: 30
D/Tethering(25738): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
I/VolumePanel(25738): changeOverlayStyle : 1
V/nvaudio_hw(25458): nvaudio_dev_set_voice_volume : vol 0.800000
D/nvaudio_hw(25458): send volume to telephony:0.800000
D/nvaudio_modem(25458): Set modem volume to 0.800000
E/nvaudio_modem(25458): Failed to get phone service!
E/SELinux (25738): SELinux: Loaded file_contexts from /file_contexts
D/Atlas (25738): Computing best atlas configuration...
D/Atlas (25738): Running Atlas Worker #1
D/Atlas (25738): Running Atlas Worker #2
D/Atlas (25738): Running Atlas Worker #3
I/com.android.server.ThemeService(25738): Spawned worker thread
I/WindowManager(25738): SAFE MODE not enabled
V/tspdrv (25738): opened device /dev/tspdrv
V/tspdrv (25738): TSPDRV_MAGIC_NUMBER success
V/tspdrv (25738): TSPDRV_GET_NUM_ACTUATORS success, actuators = 1
F/libc (25738): invalid address or address of corrupt block 0xbed47420 passed to dlfree
F/libc (25738): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 25738 (system_server)
I forgot to filter the log ,sorry...
And when I am building,it always showed that: The API version is out of date,use Xlint to recomplie(In fact I am a Chinese and the massage is in Chinese,I translate it you to understand it),but the JDK version is 1.6.0.33,it is suitable to build kitkat,right?
I hope you answer,please.

[INFO] Nexus 5 booting kernel 4.11

Hi,
i just wanted to give some information on my latest attempts to boot kernel 4.11 on the Nexus 5.
This is just for fun or at least a proof of concept to boot mainline kernel.
Have a look at bootup text file attached to this post.
You may first see my other post here:
https://forum.xda-developers.com/showpost.php?p=72681973&postcount=13
As i already stated this "project" is of no real practical use, other then learning about latest kernel and getting used to DTS files.
Many parts are missing and booting into Android would be a very dusty and rocky road... it is more that this will never happen!
Anyway i decided to switch to kernel 4.11, as there'd been some improvements on some SoC internals (e.g. USB).
So i took this kernel:
https://git.linaro.org/landing-team...shot/kernel-release/db820c/qcomlt-4.11.tar.gz
After some first tests i decided to check out more options in the kernel config file to get little nearer to the 3.4 kernel config we all know.
You'll find the config file below.
In order to do some testing easily i decided to use TWRP recovery as an initrd here.
To make it more handy i simply added a service to get a console shell.
In other words, there's busybox and some other tools to examine the system.
The image uses the serial debug console as the user interface.
To interact with the system you'll need an earjack debug adapter.
See the image (debug_3.5mm.jpg) for some information... or search the web.
To boot the image, unzip hammerhead-4.11.zip go into bootloader mode and use fastboot:
fastboot boot hammerhead-4.11.img
EDIT: Updated the attachments, as there'd been some progress (see post #7).
EDIT2: YAU (Yet Another Update)
Have fun!
scholbert

Nice job!
Some time ago I tried to build from scratch 3.10 kernel, you can find the code here.
From the log look like that the internal memory is missing, maybe due incomplete device tree entry. The related documentation should be this.

Hi 95A31!
95A31 said:
Nice job!
Some time ago I tried to build from scratch 3.10 kernel, you can find the code here.
From the log look like that the internal memory is missing, maybe due incomplete device tree entry. The related documentation should be this.
Click to expand...
Click to collapse
Thanks for your reply. Any hints and ideas are higly appreciated
Basically the sdhc entries look o.k. to me.
I already compared many parts of the DT entries in kernel 4.11 with the ones in kernel 3.4 as well (and yes they slightly changed their style).
There might be some issues with DT in general here, but i suspect some basic stuff is missing to initiate the power supply (PM8841 & PM8941) correctly.
Maybe i'll dig a little deeper... maybe not :angel:
Anyway, leave some comments here if you like!
Cheers,
scholbert

scholbert said:
...
There might be some issues with DT in general here, but i suspect some basic stuff is missing to initiate the power supply (PM8841 & PM8941) correctly.
....
Click to expand...
Click to collapse
What make you think this?

Gonna test it on my phone.

95A31 said:
What make you think this?
Click to expand...
Click to collapse
See those snippets from bootlog of kernel 3.4:
Code:
...
[ 0.143223] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.144749] socinfo_print: v8, id=126, ver=2.2, raw_id=1968, raw_ver=7, hw_plat=150, hw_plat_ver=65536
[ 0.144755] accessory_chip=0, hw_plat_subtype=0, pmic_model=65537, pmic_die_revision=196609
[ 0.158993] gpiochip_add: registered GPIOs 0 to 145 on device: msmgpio
[ 0.175335] msm_watchdog f9017000.qcom,wdt: MSM Watchdog Initialized
[ 0.194446] 8841_s1: 675 <--> 1050 mV at 0 mV normal idle
[ 0.194895] 8841_s1_ao: 675 <--> 1050 mV at 0 mV normal idle
[ 0.195357] 8841_s1_so: 675 <--> 1050 mV at 675 mV normal idle
[ 0.195859] 8841_s2: 500 <--> 1050 mV at 0 mV normal idle
[ 0.196322] 8841_s2_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.196785] 8841_s2_corner_ao: 0 <--> 0 mV at 0 mV normal idle
[ 0.197235] 8841_s2_floor_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.197723] 8841_s3: 1050 mV normal idle
[ 0.198201] 8841_s4: 815 <--> 900 mV at 0 mV normal idle
[ 0.198675] 8841_s4_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.199145] 8841_s4_floor_corner: 0 <--> 0 mV at 0 mV normal idle
[ 0.199630] 8941_s1: 1300 mV normal idle
[ 0.200131] 8941_s2: 2150 mV normal idle
[ 0.200614] 8941_s3: 1800 mV normal idle
[ 0.201146] 8941_l1: 1225 mV normal idle
[ 0.201627] 8941_l2: 1200 mV normal idle
[ 0.202120] 8941_l3: 1225 mV normal idle
[ 0.202608] 8941_l4: 1225 mV normal idle
[ 0.203117] 8941_l5: 1800 mV normal idle
[ 0.203599] 8941_l6: 1800 mV normal idle
[ 0.204088] 8941_l7: 1800 mV normal idle
[ 0.204588] 8941_l8: 1800 mV normal idle
[ 0.205066] 8941_l9: 1800 <--> 2950 mV at 2950 mV normal idle
[ 0.205554] 8941_l10: 1800 <--> 2950 mV at 2950 mV normal idle
[ 0.206025] 8941_l11: 1300 mV normal idle
[ 0.206520] 8941_l12: 1800 mV normal idle
[ 0.206982] 8941_l12_ao: 1800 mV normal idle
[ 0.207462] 8941_l13: 1800 <--> 2950 mV at 2950 mV normal idle
[ 0.207961] 8941_l14: 1800 mV normal idle
[ 0.208434] 8941_l15: 2050 mV normal idle
[ 0.208930] 8941_l16: 2700 mV normal idle
[ 0.209418] 8941_l17: 3000 mV normal idle
[ 0.209909] 8941_l18: 2850 mV normal idle
[ 0.210405] 8941_l19: 3000 <--> 3300 mV at 3300 mV normal idle
[ 0.210917] 8941_l20: 2950 mV normal idle
[ 0.211414] 8941_l21: 2950 mV normal idle
[ 0.211907] 8941_l22: 3000 <--> 3300 mV at 3100 mV normal idle
[ 0.212411] 8941_l23: 3000 mV normal idle
[ 0.212898] 8941_l24: 3075 mV normal idle
[ 0.213387] 8941_lvs1:
[ 0.213821] 8941_lvs2:
[ 0.214265] 8941_lvs3:
...
...and these messages from kernel 4.11:
Code:
...
[ 0.213352] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.215005] cpuidle: using governor menu
[ 0.215647] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.215657] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.216665] irq: no irq domain found for /smp2p-adsp/slave-kernel !
[ 0.232062] irq: no irq domain found for /soc/[email protected] !
[ 0.251356] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
[ 0.251635] reg-fixed-voltage vreg-boost: could not find pctldev for node /soc/[email protected]/[email protected]/[email protected]/boost-bypass, deferring probe
...
Regards,
scholbert

Hey,
short update... found something to get the messages from PMIC :victory:
There was a missing option in my configuration. We need CONFIG_RPMSG_QCOM_SMD to be set.
Unfortunately still no sign from the eMMC ...
EDIT: grrrrr... still some issues here.
If RPM shared memory driver gets activated, this seems to change some setup in clock unit of the chip, which as a result disables RTC or destroys something else.
So in the end i'm not sure if shared memory driver should be used here
Anyway will play around with all this in the next weeks... but remember it's summer... so it may all take it's time!
EDIT2: yeeeessssss.. some issues solved!
I forgot that i made a change in dtsi which seemed to block the interrupt to smbi... in the end reverted it, applied new configuration, and there it is.
We got eMMC now :highfive:
See new attached files and have anice weekend!
EDIT3: Moved the attachments to the first post!
BTW, there's a guy at the fairphone forum who does similar experiments with the FP2 (MSM8974 based as well):
https://forum.fairphone.com/t/kernel-hackers-upstream-kernel-for-fp2-openos/28628
Here's his github repo:
https://github.com/z3ntu/linux
Regards,
scholbert

scholbert said:
Hey,
short update... found something to get the messages from PMIC :victory:
There was a missing option in my configuration. We need CONFIG_RPMSG_QCOM_SMD to be set.
Unfortunately still no sign from the eMMC ...
[...]
Click to expand...
Click to collapse
Good job!
Look like system can not access to memory:
Code:
[ 1.800624] init: /init.rc: 66: invalid command 'load_system_props'
Code:
[ 1.995481] init: /init.recovery.hammerhead.rc: 17: invalid command '/sbin/ln'
Maybe the change msm_sdcc.1 -> f9824900.sdhci had broke something. Before the kernel messages I have this part in my logs:
Code:
[7040] use_signed_kernel=0, is_unlocked=1, is_tampered=1.
[7040] Loading boot image (9416704): start
[7380] Loading boot image (9416704): done
[7380] Found Appeneded Flattened Device tree
[7380] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[7390] get_display_kcal = 0, 0, 0, x
[7390]
Booting Linux
[7440] vibe
[7540] splash: boot
[7580] splash: unlocked
[7620] cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 msm_watchdog_v2.enable=1 mdss_mdp.panel=dsi androidboot.bootdevice=msm_sdcc.1 uart_console=enable gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emmc=[7640] Updating device tree: start
[7650] Updating device tree: done
[7660] booting linux @ 0x8000, ramdisk @ 0x2900000 (1115413), tags/device tree @ 0x2700000
[7660] Turn off MIPI_CMD_PANEL.
[7660] Continuous splash enabled, keeping panel alive.
Uncompressing Linux... done, booting the kernel.
Can be the value of androidboot.bootdevice related with this problem?
Here a Linaro guy is working on Nexus 7 (APQ8064 based unfortunately).
EDIT:
Moreover fstab.hammerhead use msm_sdcc.1 and this is wrong for sure.

Hi 95A31,
thanks for your comments and information about the Nexus 7 project.
The errors you find in the logs are related to the TWRP initrd and setup stuff.
Please refer to these messages i grabbed some time ago from the standard TWRP image:
Code:
...
[ 5.341167] init: /init.rc: 66: invalid command 'load_system_props'
[ 5.346559] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
[ 5.353919] init: /init.recovery.hammerhead.rc: 17: invalid command 'ln'
[ 5.362647] healthd: wakealarm_init: timerfd_create failed
[ 5.863315] android_usb: already disabled
[ 6.134887] init: Unable to open persistent property directory /data/property errno: 2
[ 6.141831] init: Unable to open persistent property directory /data/property errno: 2
...
As you see it's barely the same stuff printed out (independent of the kernel you use).
You may modify the initrd as you like to
The partitions can be mounted and accessed from serial console with this kernel now:
Code:
~ # mount -t ext4 /dev/block/mmcblk0p28 /data
[ 237.878280] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: (null)
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 968568 28 968540 0% /dev
tmpfs 968568 288 968280 0% /tmp
/dev/block/mmcblk0p28
27971732 10849488 17105860 39% /data
~ # cd data
/data # ls
adb backup data media security
anr bootchart drm mediadrm ss
app bugreports fdAlbum misc su
app-asec cam_socket1 local nfc system
app-lib cam_socket2 lost+found property tombstones
app-private dalvik-cache maru resource-cache user
/data #
Please check out the expermimental image and try yourself.
Be careful what you do at anytime though, because your dealing with your phones file system from within an experimental ramdisk.
So please do not brick your phone, while playing around :angel:
BTW... speaking of memory is more common for RAM, while storage may be used for eMMC and mass storage devices.
Of course a lot of tweaks and fixes are needed as this is all very experimental, so anyway thanks for your hint.
EDIT: ... and yes as for the numbering and naming this has to be corrected somewhere in time.
The eMMC is detected as device mmc0 (controller sdhci1) for now, because WLAN SDIO (using controller sdhci2) is not implemented yet.
Same for the fstab file.
Someone may try to rename some entries and see what happens, but as far as many parts are missing, there's no need for this right now.
Regards,
scholbert

scholbert said:
[...]
The errors you find in the logs are related to the TWRP initrd and setup stuff.
[...]
Click to expand...
Click to collapse
You are more skilled than me about this topic
scholbert said:
[...]
Someone may try to rename some entries and see what happens, but as far as many parts are missing, there's no need for this right now.
[...]
Click to expand...
Click to collapse
Which should be the next thing to fix?
I attached the list of commits commited by LG in aosp kernel

95A31 said:
You are more skilled than me about this topic
Click to expand...
Click to collapse
Thanks for the flowers
95A31 said:
Which should be the next thing to fix?
Click to expand...
Click to collapse
I would like to get a working usb connection and use adb to communicate with the phone.
This would possibly increase the amount of interested people to check out a console based system on their phone and do some experiments.
I guess there are only a few people who got this earjack adapter or something.
At least the Nexus 5 is an interesting piece of embedded hardware to play with, even if the display got crashed.
95A31 said:
I attached the list of commits commited by LG in aosp kernel
Click to expand...
Click to collapse
Nice! Thanks for the list.
As this refers to AOSP kernel 3.4 it gives a good overview of the patches fixes and changes of course.
For mainline kernel 4.11 this is list would look very different though.
I still concentrate on fine tuning of the kernel configuration, as there are still many things to discover.
To get some Nexus 5 specific device drivers integrated would be nice as well (e.g. check BQ24190/2 code and implement it to DT).
Anyway... always remember this is a just for fun thing.
Could be some educational project if your like, but without all the binary blobs adopted to kernel 4.11 there will never be a working Android.
EDIT:
As for the educational purpose (my very own )
We can sample some interrupts from the PM8941 subsystem very well:
Code:
~ # cat /proc/interrupts
CPU0
18: 8925 GIC-0 20 Level arch_timer
20: 0 GIC-0 39 Level arch_mem_timer
22: 0 GIC-0 194 Edge adsp
23: 0 GIC-0 190 Edge smp2p
24: 0 GIC-0 59 Edge smp2p
25: 0 GIC-0 175 Edge smp2p
26: 1181 GIC-0 139 Level msm_serial0
27: 80 GIC-0 155 Edge mmc0
28: 0 GIC-0 170 Edge f9824900.sdhci
176: 0 GIC-0 127 Level i2c_qup
178: 0 GIC-0 271 Level bam_dma
179: 0 GIC-0 166 Edge msm_otg
186: 0 pmic_arb 6357309 Edge pm8xxx_rtc_alarm
187: 2 pmic_arb 524325 Edge pm8941_pwrkey
188: 0 pmic_arb 1050408 Edge chg-done
189: 0 pmic_arb 1049896 Edge chg-fast
190: 0 pmic_arb 1049640 Edge chg-trkl
191: 0 pmic_arb 1179946 Edge bat-temp-ok
192: 0 pmic_arb 1179690 Edge bat-present
193: 0 pmic_arb 1245739 Edge chg-gone
194: 4 pmic_arb 1245483 Edge usb-valid
195: 0 pmic_arb 1311020 Edge dc-valid
197: 2 pmic_arb 12648535 Edge volume_up
198: 2 pmic_arb 12714072 Edge volume_down
243: 0 GIC-0 188 Edge adsp
244: 0 GIC-0 57 Edge modem
245: 47 GIC-0 200 Edge rpm
246: 0 GIC-0 58 Edge smsm
247: 0 GIC-0 189 Edge smsm
248: 0 GIC-0 176 Edge smsm
249: 0 smp2p 0 Edge adsp
250: 0 smp2p 1 Edge adsp
251: 0 smp2p 2 Edge adsp
252: 0 smp2p 3 Edge adsp
IPI0: 0 CPU wakeup interrupts
IPI1: 0 Timer broadcast interrupts
IPI2: 652 Rescheduling interrupts
IPI3: 5 Function call interrupts
IPI4: 0 CPU stop interrupts
IPI5: 0 IRQ work interrupts
IPI6: 0 completion interrupts
Err: 0
To be more precisely:
volume_up, volume_down, pwrkey and usb-valid are detected and working.
Unfortunately no reaction from the host and no kernel message, when micro usb cable is attached or detached...
Whatever...
Regards,
scholbert

scholbert said:
[..]
I would like to get a working usb connection and use adb to communicate with the phone.
This would possibly increase the amount of interested people to check out a console based system on their phone and do some experiments.
I guess there are only a few people who got this earjack adapter or something.
At least the Nexus 5 is an interesting piece of embedded hardware to play with, even if the display got crashed.
[...]
Click to expand...
Click to collapse
Nice, I hope to have time to seriously play with it and maybe make something work.
scholbert said:
[...]
Anyway... always remember this is a just for fun thing.
Could be some educational project if your like, but without all the binary blobs adopted to kernel 4.11 there will never be a working Android.
[...]
Click to expand...
Click to collapse
I know, I know, sometime I follow my enthusiasm . Yes, blobs are a big problem for a working Android and when I think about how address it, and how much time it will require I die inside

Wow!!!
Hey there,
i just wondered how time goes by
I'm still using my hammerhead for daily use and from time to time i'm searching the web how things are evolving.
This is the coolest project i've seen for a while:
https://github.com/flto/linux/wiki/hammerhead-upstream
Need to do some research who's behind it
Have a nice day!
scholbert

Wi-fi and BT Failing to Start after Rooting Issues - No solutions worked till date!

Hi All,
Need some help in getting my wifi and bluetooth back to normal. It's over a month now and all my attempts have failed! I would really appreciate some ideas here. Thank you, and sorry for long thread.
Phone info:
Samsung galaxy S6 SM-G920T (T-Mobile), firmware version: NRD90M.G920TUVS6FRC1, stock OS with root and TWRP recovery
Situation:
Bluetooth does not turn ON at all
Wifi takes a long time to turn ON, and only way to turn it ON is from settings (quick access tile does not work)
Wifi does not remember any password
All other functions work correctly, and the phone is now lightning fast after factory reset
Details and Steps Taken:
Rooted my phone a month ago, and started changing config. Took OS and app backup only, but no EFS/other partition backup.
Turned OFF "Allow OEM Unlock" - don't ask why
This (I believe) resulted in WIFI not remembering passwords, so after reviewing potential solutions, I changed "Secure.Storage" value in build.prop to "0"
Took backup of WPA_supplicant.conf and deleted the file
Problem was not resolved, and I had to restart the phone
Restart resulted in FRP lock - to resolve this I re-installed the OS from stock firmware from Sammobile; Yet - no luck on wifi and bluetooth, error still persisted
I reviewed the system log and found tons of errors (listed below). Based on errors, I tried:
Copying libbluetooth_jni.so library file to '/system/lib' and '/system/vendor/lib' folders
Changing 'semGetAllowBluetoothMode' value to "True" - this reduced some errors (refer below)
Validating file / folder permissions for the /efs partition - they seem to be appropriate, but I cannot confirm since there is no reference
I have also tried using SmartSwitch - but it doesn't recognize phone in download mode. It backups the apps, etc. though
Also wiped the system partition once using TWRP, and re-imaged. Yet no luck.
My hunch currently for these errors is:
The /efs permissions became incorrect or partition became corrupt due to some configuration I performed
The system lost its encryption key when the "OEM unlock" was disabled, and thus cannot read any files from the /system and /efs partition (the device was NOT encrypted, but I am thinking /efs is always encrypted by system - correct me if I am wrong)
System log snippets:
Bluetooth Related Log:
Bluetooth GATT service:
Code:
BtGatt.GattService: [GSIM LOG]: gsimLogHandler: null, msg: MESSAGE_LOAD_PREF
Bluetooth Adapter Service:
Code:
BluetoothAdapterService: onProfileServiceStateChanged() serviceName=com.android.bluetooth.gatt.GattService, state=12, Message sending
semGetAllowBluetoothMode:
Resolved this error by updating the value to "True" in build.prop. Was this the right fix, or is it supposed to get value = 2.
Code:
DevicePolicyManagerService: semGetAllowBluetoothMode - value retunrs : 2
Wifi error log:
Code:
WifiHW : ##################### set firmware type 0 #####################
WifiHW : ==========[WIFI] SEMCO MODULE ===========
WifiHW : TEMP_FAILURE_RETRY complete
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 208 Softap operation succeeded
WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
WifiHW : supplicant_name : p2p_supplicant
WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
WifiWatchdogStateMachine: Unhandled message { when=0 what=135173 arg1=2 target=com.android.internal.util.StateMachine$SmHandler } in state NotConnectedState
WifiMonitor: startMonitoring(wlan0) failed!
WifiStateMachine: Failed to setup control channel, restart supplicant
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0
WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 2
WifiHAL : Event processing terminated
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 219 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 229 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 240 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 248 Softap operation succeeded
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 11
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 256 Softap operation succeeded
WifiStateMachine: Failed 6 times to start supplicant, unload driver
WifiStateMachine: sendErrorBroadcast code:10
WifiController: WifiControllerWifi turn on failed