Related
0000000000000000
Well said.
I'm trying to get my Countour Shuttlexpress working with usb host ( using cm7 nightlies )
I've already posted some of this in the usb-host thread but seems there is not much devs traffic there LINK
So I've decided to open a new thread hoping for some interest and maybe info for others who want to write/port their own usb-host drivers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Eventually what I'm trying to achieve is :
Jog Wheel - Controls system/media volume
Shuttle Knob - PREV/NEXT song on PowerAmp app
Buttons - Launch Apps , Jump To Screen #n , Run Terminal Commands
That's on the basic level of things
I don't have any coding skills in Linux ( I do know some java and c/c++ And I'm a fast learner )
In the past few days I've been setting up my first developing enviorment with Ubuntu 10.04 and learned a couple of things about android coding
Lets get back to the device
For now it's recognized as an HID device , and I can use getevent to get each function specific code
But nothing is mapped to any real function on the nook
Here is some info from the nook :
DMESG Log :
Code:
<6>usb 1-1.2: new low speed USB device using musb_hdrc and address 4
<7>usb 1-1.2: skipped 1 descriptor after interface
<7>usb 1-1.2: default language 0x0409
<3>usb 1-1.2: device v0b33 p0020 is not supported
<7>usb 1-1.2: udev 4, busnum 1, minor = 3
<6>usb 1-1.2: New USB device found, idVendor=0b33, idProduct=0020
<6>usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>usb 1-1.2: Product: ShuttleXpress
<6>usb 1-1.2: Manufacturer: Contour Design
<7>usb 1-1.2: uevent
<7>usb 1-1.2: usb_probe_device
<6>usb 1-1.2: configuration #1 chosen from 1 choice
<7>usb 1-1.2: adding 1-1.2:1.0 (config #1, interface 0)
<7>usb 1-1.2:1.0: uevent
<7>usbserial_generic 1-1.2:1.0: usb_probe_interface
<7>usbserial_generic 1-1.2:1.0: usb_probe_interface - got id
<7>usbhid 1-1.2:1.0: usb_probe_interface
<7>usbhid 1-1.2:1.0: usb_probe_interface - got id
<6>input: Contour Design ShuttleXpress as /devices/platform/musb_hdrc/usb1/1-1/1-1.2/1-1.2:1.0/input/input4
<6>generic-usb 0003:0B33:0020.0001: input: USB HID v1.10 Device [Contour Design ShuttleXpress] on usb-musb_hdrc-1.2/input0
<7>drivers/usb/core/inode.c: creating file '004'
<1>##- Data length: 2
/proc/bus/input/devices
Code:
I: Bus=0003 Vendor=0b33 Product=0020 Version=0110
N: Name="Contour Design ShuttleXpress"
P: Phys=usb-musb_hdrc-1.2/input0
S: Sysfs=/devices/platform/musb_hdrc/usb1/1-1/1-1.2/1-1.2:1.0/input/input7
U: Uniq=
H: Handlers=mouse3 event7
B: EV=17
B: KEY=1fff 0 0 0 0 0 0 0 0
B: REL=180
B: MSC=10
*the logs are from different sessions
using "getevent /dev/input/event7" I captured the events and isolated them
Buttons : ( numbered from left to right )
1.
Code:
Press -
0004 0004 00090005
0001 0104 00000001
0000 0000 00000000
Release -
0004 0004 00090005
0001 0104 00000000
0000 0000 00000000
2.
Code:
Press -
0004 0004 00090006
0001 0105 00000001
0000 0000 00000000
Release -
0004 0004 00090006
0001 0105 00000000
0000 0000 00000000
3.
Code:
Press -
0004 0004 00090007
0001 0106 00000001
0000 0000 00000000
Release -
0004 0004 00090007
0001 0106 00000000
0000 0000 00000000
4.
Code:
Press -
0004 0004 00090008
0001 0107 00000001
0000 0000 00000000
Release -
0004 0004 00090008
0001 0107 00000000
0000 0000 00000000
5.
Code:
Press -
0004 0004 00090009
0001 0108 00000001
0000 0000 00000000
Release -
0004 0004 00090009
0001 0108 00000000
0000 0000 00000000
Jog Wheel :
Code:
From -
0002 0007 00000001
0000 0000 00000000
To -
0002 0007 000000ff
0000 0000 00000000
Shuttle Knob :
Code:
Full right -
0002 0008 00000007
0002 0007 00000001
0000 0000 00000000
Full left -
0002 0008 fffffff9
0002 0007 00000001
0000 0000 00000000
So , I have a few ideas on how to do it and I thought you might help me figure out the best way and guide me through it :
Using Tasker and write a script using Locale Execute plugin with getevent & other commands - Probably highly in-efficient and maybe slow?
Write an app to run in the background , intercept the events and execute commands every x ms? How much is needed for a quick response?
Write a driver ( or kernel module? ) for the device
Maybe I can use the HID driver to do that?
Port one of the sources I listed down to Android?
Another thing I haven't thought of?
I have found a couple of things that might help
powermate.c in dalingrin's kernel seems to contain some code for it but I couldn't find any real thing that it does to it besides define the device
GITHUB Link
Here are some source codes for Linux ( which I thought at first to be drivers but they seem to be handlers/applications )
https://init.linpro.no/pipermail/skolelinux.no/cinelerra/2006-March/005665.html
http://www.reynwar.net/gnuradio/epydoc/gnuradio.wxgui.powermate-pysrc.html
Can I use the code from USB Mouse support and adapt it for my own input device? will it even work on CM7 since it's built for Iconia?
I've also looked into usbled.c in the kernel , comparing it to the original code from here http://www.linuxjournal.com/article/7353
It seems pretty much the same , so maybe porting the handler is the best and easiest way?
Any help would be appreciated , in the last 3 days I've read so much on linux/android developing and still feels like I know nothing
Thanks ,
Gutz
will it work with the shuttle pro 2, too ?
There is a code for the shuttle pro and v2 as well here
http://www.reynwar.net/gnuradio/epydoc/gnuradio.wxgui.powermate-pysrc.html
Its an handler written with python , I need to find out if I can port this to Android
If I'll eventually port some of the code from there I'll try to include the v2 code aswell..
Did you get this going? Would be very interested.
oh memories
I did get this going eventually pretty easily using an app called "usb/bt joystick center"
I tried looking for it but it's not on the play store anymore , a google search did came up with some apk sources so just try them out
If you need any help pm me - I haven't touched it in years but I might remember / can dig up some old files to help
Good luck
Any news on that old topic ?
I just bought a ShuttleXpress for a Nexus in car project thinking it would be straightforward, but it seems that its not..
hassbruk said:
Any news on that old topic ?
I just bought a ShuttleXpress for a Nexus in car project thinking it would be straightforward, but it seems that its not..
Click to expand...
Click to collapse
@hassbruk I have written a driver for this, which is implemented in my controller app. Checkout my github (freshollie) for more info.
freshollie said:
@hassbruk I have written a driver for this, which is implemented in my controller app. Checkout my github (freshollie) for more info.
Click to expand...
Click to collapse
Hi Freshollie sorry to wake up this thread after so many years.. Anyway to help how to set this up in an android tablet ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
In the beginning we would like to thank:
cm team
omni team
dior devs
armani-dev
open source community
AICP dev team:
LorD ClockaN
zipsnet
n3ocort3x
semdoc
eyosen
alienmind
Chezbel
Drgravy
DONATIONS:
We are now paying for servers that build nightlies and everything that comes with it, so EVERY DONATION is going there.
Thank you!!
What is AICP?
AICP is known by someone as Ice Cold Project that started on Desire HD and since than evolved as a mature rom with the BEST community you can find!!!
Unfortunately AOKP either stopped development or will make a comeback later this year so we are now CM based when it comes to hardware, drivers and some features.
If there are any bugs, either we will sort them or CM team if it concerns their modifications. This rom isn't CM supported so no need to report errors or bugs to them!!
Install instructions:
Reboot into recovery (latest official TWRP recommended).
Wipe Data, System and Cache if it's a fresh install.
No wipes required if you're updating from a previous version of CM 13.0 (Wipe Cache and Dalvik Cache recommended).
Flash ROM + Gapps.
Reboot.
Download links:
ROM: AICP ROM
Gapps: Banks /Open Gapps
XDA:DevDB Information
AICP, ROM for the Xiaomi Redmi Note
Contributors
audahadi
Source Code: https://github.com/AICP
Source Code: https://github.com/kernel-hut/android_kernel_xiaomi_cancro
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-12-18
Last Updated 2015-12-17
Reserved
Bug's??
Sent from my HM NOTE 1LTE using XDA Free mobile app
razhie22 said:
Bug's??
Sent from my HM NOTE 1LTE using XDA Free mobile app
Click to expand...
Click to collapse
FB fc and maybe some other app too.. Camera not as good as MIUI.. Overall.. Pretty stable to enjoy marshmallow
Sent from my HM NOTE 1LTE using Tapatalk
audahadi said:
FB fc and maybe some other app too.. Camera not as good as MIUI.. Overall.. Pretty stable to enjoy marshmallow
Sent from my HM NOTE 1LTE using Tapatalk
Click to expand...
Click to collapse
I can't change the maximum freq, how can I change it?
richard el renthlei said:
I can't change the maximum freq, how can I change it?
Click to expand...
Click to collapse
No for now.. I'll look into it
Sent from my HM NOTE 1LTE using Tapatalk
Is there any workaround for the FB app crashing? I appears that it's crashing in native code with a SIGSEGV?
Code:
01-08 20:49:56.804 23905 24106 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3d680624 in tid 24106 (Thread-526)
01-08 20:49:56.909 309 309 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-08 20:49:56.909 309 309 F DEBUG : Build fingerprint: 'Xiaomi/dior/dior:4.4.4/KTU84P/5.9.16:user/release-keys'
01-08 20:49:56.909 309 309 F DEBUG : Revision: '0'
01-08 20:49:56.909 309 309 F DEBUG : ABI: 'arm'
01-08 20:49:56.910 309 309 F DEBUG : pid: 23905, tid: 24106, name: Thread-526 >>> com.facebook.katana <<<
01-08 20:49:56.910 309 309 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3d680624
01-08 20:49:56.939 309 309 F DEBUG : r0 b7ec2150 r1 b7ec2bf8 r2 3d680600 r3 3d680600
01-08 20:49:56.939 309 309 F DEBUG : r4 b7ec2150 r5 934a8ef4 r6 b7ec2150 r7 b7ec1a98
01-08 20:49:56.939 309 309 F DEBUG : r8 934a8f94 r9 b6d49d80 sl 934a8ef0 fp 934a8f38
01-08 20:49:56.939 309 309 F DEBUG : ip 935bff08 sp 934a8eb0 lr 93537629 pc 93d7c650 cpsr a00f0030
01-08 20:49:56.953 309 309 F DEBUG :
01-08 20:49:56.953 309 309 F DEBUG : backtrace:
01-08 20:49:56.953 309 309 F DEBUG : #00 pc 00038650 /data/data/com.facebook.katana/lib-xzs/libsslx.so (BIO_push+7)
01-08 20:49:56.953 309 309 F DEBUG : #01 pc 0008b625 /data/data/com.facebook.katana/lib-xzs/libliger.so
01-08 20:49:56.953 309 309 F DEBUG : #02 pc 0005bb75 /data/data/com.facebook.katana/lib-xzs/libliger.so
01-08 20:49:56.954 309 309 F DEBUG : #03 pc 00063d79 /data/data/com.facebook.katana/lib-xzs/libliger.so
01-08 20:49:56.954 309 309 F DEBUG : #04 pc 0006405f /data/data/com.facebook.katana/lib-xzs/libliger.so
01-08 20:49:56.954 309 309 F DEBUG : #05 pc 0005ce53 /data/data/com.facebook.katana/lib-xzs/libliger.so
01-08 20:49:56.954 309 309 F DEBUG : #06 pc 000205e9 /data/data/com.facebook.katana/lib-xzs/libfolly-io.so (folly::AsyncSSLSocket::sslVerifyCallback(int, x509_store_ctx_st*)+168)
01-08 20:49:56.954 309 309 F DEBUG : #07 pc 00072c7d /data/data/com.facebook.katana/lib-xzs/libsslx.so
01-08 20:49:56.954 309 309 F DEBUG : #08 pc 00073b51 /data/data/com.facebook.katana/lib-xzs/libsslx.so (X509_verify_cert+1744)
01-08 20:49:56.954 309 309 F DEBUG : #09 pc 0002479b /data/data/com.facebook.katana/lib-xzs/libsslx.so
01-08 20:49:56.954 309 309 F DEBUG : #10 pc 0001b0b5 /data/data/com.facebook.katana/lib-xzs/libsslx.so
01-08 20:49:56.954 309 309 F DEBUG : #11 pc 0001d857 /data/data/com.facebook.katana/lib-xzs/libsslx.so
01-08 20:49:56.957 309 309 F DEBUG : #12 pc 00027a63 /data/data/com.facebook.katana/lib-xzs/libsslx.so (SSL_connect+18)
01-08 20:49:56.957 309 309 F DEBUG : #13 pc 00018ceb /data/data/com.facebook.katana/lib-xzs/libsslx.so
01-08 20:49:56.957 309 309 F DEBUG : #14 pc 00027a63 /data/data/com.facebook.katana/lib-xzs/libsslx.so (SSL_connect+18)
01-08 20:49:56.957 309 309 F DEBUG : #15 pc 00021c51 /data/data/com.facebook.katana/lib-xzs/libfolly-io.so (folly::AsyncSSLSocket::handleConnect()+88)
01-08 20:49:56.957 309 309 F DEBUG : #16 pc 00021a2b /data/data/com.facebook.katana/lib-xzs/libfolly-io.so (folly::AsyncSSLSocket::handleRead()+82)
01-08 20:49:56.957 309 309 F DEBUG : #17 pc 00026f4b /data/data/com.facebook.katana/lib-xzs/libfolly-io.so (folly::AsyncSocket::ioReady(unsigned short)+90)
01-08 20:49:56.957 309 309 F DEBUG : #18 pc 000310c1 /data/data/com.facebook.katana/lib-xzs/libfolly-io.so (folly::EventHandler::libeventCallback(int, short, void*)+40)
01-08 20:49:56.957 309 309 F DEBUG : #19 pc 00034097 /data/data/com.facebook.katana/lib-xzs/libfolly-io.so
01-08 20:49:56.957 309 309 F DEBUG : #20 pc 0002e68f /data/data/com.facebook.katana/lib-xzs/libfolly-io.so (folly::EventBase::loopBody(int)+630)
01-08 20:49:56.958 309 309 F DEBUG : #21 pc 000306f5 /data/data/com.facebook.katana/lib-xzs/libfolly-io.so (folly::EventBase::loopForever()+36)
01-08 20:49:56.958 309 309 F DEBUG : #22 pc 00028db7 /data/data/com.facebook.katana/lib-xzs/libliger.so
01-08 20:49:56.958 309 309 F DEBUG : #23 pc 00028e81 /data/data/com.facebook.katana/lib-xzs/libliger.so
01-08 20:49:56.958 309 309 F DEBUG : #24 pc 063c5457 /data/app/com.facebook.katana-1/oat/arm/base.odex (offset 0x6384000)
i got a update notification, what's new? changelog?
I will try this rom.
Thanks for your work
Can this rom be ported to Gucci ( Redmi note 4G dual sim)?
I have tried it.Works very well,but the default camera can't work.
rerbin said:
I have tried it.Works very well,but the default camera can't work.
Click to expand...
Click to collapse
Set Selinux to permisive
Sent from my REDMI NOTE 4G using Tapatalk
Nice one!
is it stable? camera working?
Well overall it's pretty good, but there's still some problems what I really mind...
I flashed the ROM twice, and at the first time the camera didn't work (cannot connect to the camera) but it worked at the second(only original camera app, and Google camera FC but it went better after a few times of rebooting)
Google play service FC all the time and I have to disable fc notifications or I just can't use the phone (but actually play store works. If just never stop giving fc notifications)
And it always auto-rotate, even when I turned it off
AlsoProblems with Google sync, it didn't restore my contacts.
I've used it for several days and that's all
Log will be posted later
Dr. Ajay Tripathi
I noticed erlier when i tried to install an old CM 13 bluid tht in marshmallow Folder Mount app do not work and they even dnt support android 6
I use folder mount extensively in Android 5.1 and i do not wnt to format my card as internal in android 6 as it encrypt all card data and make flashing new rom a pain in ass
So overall i need my old trusted way of Folder Mount
Just need to ask u does folder mounting work in android 6 ?
I was in impression that it do not work due to google implementation of memory card as ext3/4.
Wht u guys use for keeping ur big data files like Obb and old app which point to Internal memory?
And wht u guys prefer an Internal Sd or Mount as External in Marshnellow . Internal will encrypt and dont allow card to pc transfer na? And each rom reinstall means whole card data non readable?
Is there any way ro read memory card data mounted as Internal? Can we read it in Ubuntu? Or can we dencrypt to transfer files fast via Card reader?
Overall i do not install Marshnellow due to memory problem it creates . Please . guide me here.
Thank u every1 here
Tc
Sent from my HM NOTE 1LTE using Tapatalk
@audahadi Thanks for the awesome ROM... except Wifi everything is working... any suggestion as to how to make Wifi work on my phone... Thanks again...
Kiranb212 said:
@audahadi Thanks for the awesome ROM... except Wifi everything is working... any suggestion as to how to make Wifi work on my phone... Thanks again...
Click to expand...
Click to collapse
What do you mean wifi not working?
Sent from my ASUS_Z010D using Tapatalk
audahadi said:
What do you mean wifi not working?
Sent from my ASUS_Z010D using Tapatalk
Click to expand...
Click to collapse
Thanks for your quick reply...
did a clean flash...
Wifi doesn't work say's "Connected with no internet".... tried flashing boot.img through fastboot mode but no luck.... however Wifi works after flashing "aries_kernel_v1.7.zip"
Using TWRP Material version 2.8.7.0 & rooted using Super SU
do I need to unlock my phone's boot loader (Redmi Note 4G single sim Indian variant)
Kiranb212 said:
Thanks for your quick reply...
did a clean flash...
Wifi doesn't work say's "Connected with no internet".... tried flashing boot.img through fastboot mode but no luck.... however Wifi works after flashing "aries_kernel_v1.7.zip"
Using TWRP Material version 2.8.7.0 & rooted using Super SU
do I need to unlock my phone's boot loader (Redmi Note 4G single sim Indian variant)
Click to expand...
Click to collapse
Device already came bootloader unlock..
Sent from my ASUS_Z010D using Tapatalk
This is my "Squid Kernel" for the 2016 Moto G4 Play, codenamed harpia. It shares a common codebase with my kernels for osprey, surnia, and lux. It consists of the latest Motorola MSM8916 kernel, with all the latest changes from CodeAurora and Kernel.org merged in, along with select cherry-picks and additions of my own. Flash it using TWRP. Bug reports and contributions are welcome.
This kernel supports both the stock ROM and custom ROMs.
Disclaimer:
This is for the 2016 Moto G4 Play (harpia) only! Versions r22 and up are for Nougat ROMs with modern blobs only! Don't flash it on a previous Moto G, or surnia, or lux. This kernel is provided AS-IS, with no warranties. I am not responsible for bricking your device. Flash at your own risk.
Features:
Moderately undervolted
Updated to Linux 3.10.108
Synced with latest CodeAurora changes
Improved memory management
Improved memory caching backported from Linux 3.15
Improved storage performance
Optimized ARM crypto routines
Updated f2fs and WiFi drivers
FIOPS and BFQ I/O schedulers
Lionfish CPU governor
IntelliPlug CPU hotplug (by faux123)
KCAL MDP5 colour control (by savoca)
Improved zRAM backported from Linux 4.9
Vibration intensity control
Compiled with Linaro GCC 7.3 and optimized for Cortex A53
Stripped down and optimized configuration
Release History:
Code:
r23: August 15, 2018
- More reliable headphone detection on harpia
- Tonnes of security patches
- Updated binder
- Compiled with Linaro GCC 7.3.1
r22b: January 13, 2018
- Audio driver fixes
r22: January 11, 2018
- Security patches
- Updated camera drivers
- Stock Nougat support
- Nougat only, requires modern blobs
r21: December 6, 2017
- Updated to Linux 3.10.108
- Security patches
- Oreo support related patches
r20: August 2, 2017
- Updated to Linux 3.10.107
- Tonnes of security patches from many places
- Updated sdcardfs from Google
- Updated WiFi driver from CAF
- Compiled with Linaro GCC 6.3.1
r19: January 1, 2017
- Added support for Nougat ROMs
- Updated zRAM from Linux 4.9
- Updated (optimized) FUSE from CAF
- Kernel ASLR and many info leak fixes
- ARM PXN support for exploit mitigation
- Tons of security updates
- Some CAF updated from LA.BR.1.2.9_rb1.10
- Fixed kernel panic on VPN disconnection
- Updated compiler to Linaro GCC 6.2.1
r18: November 8, 2016
- Initial release for harpia
Downloads:
Main downloads tab
XDA:DevDB Information
Squid Kernel for Moto G4 Play, Kernel for the Moto G4 Play
Contributors
squid2
Source Code: https://github.com/sultanqasim/android_kernel_motorola_msm8916
Kernel Special Features: undervolted, lionfish, fiops, intelliplug, latest Linux and Qualcomm fixes
Version Information
Status: Stable
Current Stable Version: r23
Stable Release Date: 2018-08-15
Created 2016-11-09
Last Updated 2018-08-15
it is for all Harpia XT16XX?
mario156090 said:
it is for all Harpia XT16XX?
Click to expand...
Click to collapse
Yes, all harpia variants running all Marshmallow ROMs (stock and custom) should work with r18. A Nougat-only version will be coming later once I bring CM14.1 to this device.
I'm trying it now. No issues so far.
Just in case, how I would I could go back to stock kernel?
Frank_s_ph said:
I'm trying it now. No issues so far.
Just in case, how I would I could go back to stock kernel?
Click to expand...
Click to collapse
Flash your stock twrp backup
Sent from my Moto G Play using XDA-Developers mobile app
@squid2, Your kernel is very good, is it possible to overlock?
Just wanted to say this kernel is amazing. Not sure how accurate the seetings for the battery are but it says I have 4 days remaining at 86%. Even if its half that its still a massive improvement, thanks for your devotion and work on the g series @squid2.
You are ruling the harpia forum.
Great job
For whatever it's worth, I installed BaseMark OS II and ran a before and after test of the Nov 8 kernel. It slowed down the memory a bit. The first four columns are stock and the last four columns are with the Nov 8 kernel.
Overall 628 625 628 621 | 542 538 541 539
System 1043 1029 1062 1054 | 1028 1048 1067 1040
Memory 852 853 847 828 | 517 496 503 505
Graphics 315 315 315 313 | 305 304 299 304
Web 554 551 549 545 | 531 533 535 527
For such a big hit to the memory score, it didn't affect the rest all that much. I wonder if there isn't some boost in battery life that I'm not sure how to measure. I didn't notice much warmth from the phone while running the benchmark, but I didn't really make a good test of that. If the battery life is xx% better, then it's a choice of what you value.
Please don't take this as being negative. I really appreciate the chance to try this out. Keep going Squid! I'm dying to see the CM's going on this phone!!
Hello @squid2 sir
I can't find any undervolting commit on github
Can you help me find it ?
Sent from my Motorola Moto E using XDA Labs
Should I be seeing better battery life when compared to stock? Because it looks to be worse (higher consumption when using, like wifi browsing). Do I have to change the governor?
Also, if I switch back to stock kernel, do I have to reset something (like some settings)?
I guess that the kernel wasn't the differentiating factor, as I just got similar performance as with stock - 3 days standby and 10 hours screen on time.
nick_white said:
Should I be seeing better battery life when compared to stock? Because it looks to be worse (higher consumption when using, like wifi browsing). Do I have to change the governor?
Also, if I switch back to stock kernel, do I have to reset something (like some settings)?
Click to expand...
Click to collapse
No need for setting anything when going back to stock kernel.
I'm wondering if this kernel makes it possible to use the white battery LED as notification LED?
To me the G4 Play's only flaw is not having a notification LED, but an "battery is being charged" LED... Very odd.
yeah this would be cool
K.E. said:
I'm wondering if this kernel makes it possible to use the white battery LED as notification LED?
To me the G4 Play's only flaw is not having a notification LED, but an "battery is being charged" LED... Very odd.
Click to expand...
Click to collapse
I second this. I found it really odd how it's charging only, but not for notifications. I really would love to see if anyone could incorporate a notification light setting
Is the carging led somewhere at the bottom left of the phione? I can see something beneath the glass (looks like the proximity sensor), but mine is not lighting up when charging...
nick_white said:
Is the carging led somewhere at the bottom left of the phione? I can see something beneath the glass (looks like the proximity sensor), but mine is not lighting up when charging...
Click to expand...
Click to collapse
It's in the slightly on the bottom left side when plugged in. Surprised me the first time I installed CM after running stock for a little while, I didn't see a setting in the stock rom for it.
VPN disconnect reboot
I found a reproducible bug that causes a reboot with the r18 kernel. When using the built-in Android VPN feature the phone reboots as soon as I click disconnect. I tested with the stock kernel and it works fine, also tested with and without SuperSu. Phone is a xt1607 running stock ROM 6.0.1. The VPN type is PPTP.
Code:
<1>[ 328.175881,1] Unable to handle kernel NULL pointer dereference at virtual address 00000004
<1>[ 328.175928,1] pgd = c0004000
<1>[ 328.175946,1] [00000004] *pgd=00000000
<0>[ 328.175977,1] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
<4>[ 328.175995,1] Modules linked in:
<4>[ 328.176025,1] CPU: 1 PID: 9399 Comm: pppd Tainted: G W 3.10.104-r18-g15931b7-03706-gec43596 #2
<4>[ 328.176046,1] task: c5fa78c0 ti: dc0f4000 task.ti: dc0f4000
<4>[ 328.176081,1] PC is at ppp_unregister_channel+0x200/0x2c0
<4>[ 328.176106,1] LR is at _raw_spin_unlock_irqrestore+0x28/0x48
<4>[ 328.176129,1] pc : [<c06ca324>] lr : [<c0e1b918>] psr: 600f0013
<4>[ 328.176129,1] sp : dc0f5da0 ip : 00000091 fp : d2f00548
<4>[ 328.176153,1] r10: dfdc9a60 r9 : dfdc9a60 r8 : dee68fcc
<4>[ 328.176172,1] r7 : ccafb590 r6 : c15cdc40 r5 : e2d848cc r4 : dee68f80
<4>[ 328.176191,1] r3 : 00000004 r2 : 00000000 r1 : 00000000 r0 : 00000000
<4>[ 328.176212,1] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[ 328.176232,1] Control: 10c0383d Table: a2b2c06a DAC: 00000015
<0>[ 328.176250,1] Process pppd (pid: 9399, stack limit = 0xdc0f4238)
<0>[ 328.176268,1] Stack: (0xdc0f5da0 to 0xdc0f6000)
<0>[ 328.176299,1] 5da0: e1506400 00000000 c2a16d00 e3b61010 dfdc9a40 c06d0934 e1506400 c06d3cac
<0>[ 328.176327,1] 5dc0: dfdc9a60 00000000 dfcadf68 e3b61010 00000008 c0bc2b14 d2f00540 00000000
<0>[ 328.176356,1] 5de0: dfcadf68 c02934a8 00000000 00000000 e2fffa90 c5fa7d44 00000000 c16490b8
<0>[ 328.176384,1] 5e00: c5fa78c0 de508540 de508574 00418004 fffffdfe c015d770 c5fa78c0 002f002f
<0>[ 328.176412,1] 5e20: dc0f4000 c5fa7d64 c5fa78c0 00000001 dc0f4000 c0138c5c 00000000 00000000
<0>[ 328.176440,1] 5e40: 00000002 e1316000 002f002f c0e1e388 c5fa78c0 56e80405 e131601c dc0f5ee8
<0>[ 328.176468,1] 5e60: fffffdfe c013a76c dc0f4000 00000009 c29d4000 dc0f5ee8 c0f01c48 c014d950
<0>[ 328.176497,1] 5e80: 603d2b40 0000004c c151d290 da5e4ec0 c15e1064 da5e53c4 418004fc 00040005
<0>[ 328.176525,1] 5ea0: 00040006 dc0f5ed4 c25ee300 dc0f4000 dc0f5fb0 c151c408 dc0f5ed4 dc0f5ee8
<0>[ 328.176554,1] 5ec0: b6d980f8 b6d980fc fffffdfe c01111a4 0000000a c0e1b418 0000000a c0e1b918
<0>[ 328.176582,1] 5ee0: 0000000a c013d950 00000009 00000000 00000000 00000000 00000000 00000000
<0>[ 328.176610,1] 5f00: c151c408 fffffdfe 00000000 be86a810 00000008 00000000 dc0f4000 c02ac660
<0>[ 328.176638,1] 5f20: dc0f5f4c 00000000 be86a840 00000000 be86a8c0 000006bf 00000807 310fd355
<0>[ 328.176666,1] 5f40: 00000000 000006bf 30898980 00000807 310fd355 000006bf 30898980 000006bf
<0>[ 328.176696,1] 5f60: 2a78fbd9 000006bf 2a78fbd9 56e80405 c010db64 dc0f4000 dc0f4000 dc0f4000
<0>[ 328.176724,1] 5f80: dc0f5fb0 c010db64 dc0f4000 00000000 b6fc7d54 c01116c0 be86a810 00000000
<0>[ 328.176752,1] 5fa0: 000006bf 0000014f c010db64 c010da28 00000008 be86a840 00000000 be86a8c0
<0>[ 328.176780,1] 5fc0: be86a810 00000000 000006bf 0000014f be86a840 00000008 b6f7fbd1 b6fc7d54
<0>[ 328.176808,1] 5fe0: be86a808 be86a7f8 b6d704c9 b6d980f8 40070010 00000008 00000000 00252522
<4>[ 328.176853,1] [<c06ca324>] (ppp_unregister_channel) from [<c06d0934>] (pppox_unbind_sock+0x1c/0x28)
<4>[ 328.176892,1] [<c06d0934>] (pppox_unbind_sock) from [<c06d3cac>] (pppopns_release+0xe0/0x118)
<4>[ 328.176926,1] [<c06d3cac>] (pppopns_release) from [<c0bc2b14>] (sock_close+0x24/0xac)
<4>[ 328.176961,1] [<c0bc2b14>] (sock_close) from [<c02934a8>] (____fput+0x98/0x224)
<4>[ 328.176993,1] [<c02934a8>] (____fput) from [<c015d770>] (task_work_run+0xb8/0xf4)
<4>[ 328.177031,1] [<c015d770>] (task_work_run) from [<c0138c5c>] (do_exit+0x304/0x9c0)
<4>[ 328.177061,1] [<c0138c5c>] (do_exit) from [<c013a76c>] (do_group_exit+0x38/0xb0)
<4>[ 328.177093,1] [<c013a76c>] (do_group_exit) from [<c014d950>] (get_signal_to_deliver+0x324/0x668)
<4>[ 328.177127,1] [<c014d950>] (get_signal_to_deliver) from [<c01111a4>] (do_signal+0x9c/0x458)
<4>[ 328.177162,1] [<c01111a4>] (do_signal) from [<c01116c0>] (do_work_pending+0x74/0xbc)
<4>[ 328.177194,1] [<c01116c0>] (do_work_pending) from [<c010da28>] (work_pending+0xc/0x20)
<0>[ 328.177223,1] Code: e5940064 e2803004 f57ff05b f5d3f000 (e1932f9f)
<4>[ 328.177947,3] ---[ end trace 55110d0257cc6671 ]---
just found these commits - maybe this can be adapted to harpia?
https://review.cyanogenmod.org/#/c/144769/
https://review.cyanogenmod.org/#/c/144770/
https://review.cyanogenmod.org/#/c/144768/
K.E. said:
I'm wondering if this kernel makes it possible to use the white battery LED as notification LED?
To me the G4 Play's only flaw is not having a notification LED, but an "battery is being charged" LED... Very odd.
Click to expand...
Click to collapse
Hello everyone,
I own Wetek Play. I've been playing with software update, but it seems that it went into a bootloop. I conected serial monitor and i get following logs:
HHH
BootFrom SPI
ucl decompress
decompress false
/home/alex/uboot-wetek/arch/arm/cpu/aml_meson/common/firmware/loaduboot.cload_uboot0x0000007f⸮EEEE I3000000032940xf3001103;77520EEEE I400000004294_M6_BL1_3431>2534313
TE : 77476
BT : 22:19:13 Jan 15 2016
CPU clock is 1200MHz
wait pll-0x03 target is 0204 now it is 0x00000203
DDR clock is 516MHz with Low Power & 2T mode
DDR training :
DX0DLLCR:40000000
DX0DQTR:ffffffff
DX0DQSTR:3db05001
DX1DLLCR:40000000
DX1DQTR:ffffffff
DX1DQSTR:3db05001
DX2DLLCR:40000000
DX2DQTR:ffffffff
DX2DQSTR:3db05001
DX3DLLCR:40000000
DX3DQTR:ffffffff
DX3DQSTR:3db05001
Stage 00 Result 00000000
Stage 01 Result 00000000
Stage 02 Result 00000000
Stage 03 Result 00000000
DDR init use : 42463 us
HHH
BootFrom SPI
ucl decompress
decompress false
/home/alex/uboot-wetek/arch/arm/cpu/aml_meson/common/firmware/loaduboot.cload_uboot0x0000007f⸮EEEE I3000000032940xf3001103;77520EEEE I400000004294_M6_BL1_3431>2534313
TE : 77476
BT : 22:19:13 Jan 15 2016
CPU clock is 1200MHz
ait pll-0x03 target is 0204 now it is 0x00000203
DDR clock is 516MHz with Low Power & 2T mode
DDR training :
DX0DLLCR:40000000
DX0DQTR:ffffffff
DX0DQSTR:3db05001
DX1DLLCR:40000000
DX1DQTR:ffffffff
DX1DQSTR:3db05001
DX2DLLCR:40000000
DX2DQTR:ffffffff
DX2DQSTR:3db05001
DX3DLLCR:40000000
DX3DQTR:ffffffff
DX3DQSTR:3db05001
Stage 00 Result 00000000
Stage 01 Result 00000000
Stage 02 Result 00000000
Stage 03 Result 00000000
DDR init use : 42464 us
and so on...
The device does not react to "upgrade" button and SD card inserted.
Can anyone help me what should I do to unbrick my Wetek?
Thank you in advance.