[Kernel][AOSP 4.3 / CM10.2 NOT NIGHTLIES / M7][experimental] crpalmer | Aug 25, 2013
- Thread starter crpalmer
- Start date
-
- Tags
- development
- Status
What exactly are you looking at? I don't see anything that controls things like force fast charge.
CR its in settings right above above phone. Performance control for cpu and stuff.
Yeah, that's the performance menu, but in there I just have Processor, I/O scheduler, Memory management, 16bit transparency, Surface improvement. Nothing about fast-charge.
I am on Pac in my performance menu at the top there is cpu settings which shows cpu stats and if u scroll the whole screen to the left I get advanced settings and the fast charge is about half way down.
Glad to hear it works on PAC.
I'm running CM10.1 and that's something that they must have added in PAC... I suspect that either the PAC ROM has a script that controls this by default or it 's not reporting it correctly. Can you do:
adb cat /sys/kernel/fast_charge/*
which is what the kernel really thinks are the settings.
not getting a response, maybe user error. if I enable fast charge it will not connect to my computerGlad to hear it works on PAC.
I'm running CM10.1 and that's something that they must have added in PAC... I suspect that either the PAC ROM has a script that controls this by default or it 's not reporting it correctly. Can you do:
adb cat /sys/kernel/fast_charge/*
which is what the kernel really thinks are the settings.
Glad to hear it works on PAC.
I'm running CM10.1 and that's something that they must have added in PAC... I suspect that either the PAC ROM has a script that controls this by default or it 's not reporting it correctly. Can you do:
adb cat /sys/kernel/fast_charge/*
which is what the kernel really thinks are the settings.
No
No Port
Discharging
0
No
It can be toggled in trickster mod though I doubted it did anything if it wasn't added to the kernel.
Tapatalked from my HTC DNA - ReVolt
Not really if its there, just if its doing anything if it is there. I know it shows up on this kernel on revolt in trickster.
Tapatalked from my HTC DNA - ReVolt
adb cat /sys/kernel/fast_charge/* does not work it just gives me the list of valid options(ubuntu 13.04). I did a logcat just for kicks and I notice that I get
I realize my adblocker is redirecting it to 127.0.0.1 but I was wondering if there is a way to find the origin of this? On another note, you reduced the power consumption of the kernel by 40%(gsam battery stats now shows my screen as taking 25-40% of the power as opposed to 5-10)! Great job!
Code:
W/GoogleAnalyticsTracker( 6173): Problem with socket or streams.
W/GoogleAnalyticsTracker( 6173): java.net.ConnectException: failed to connect to www.google-analytics.com/127.0.0.1 (port 80): connect failed: ECONNREFUSED (Connection refused)
W/GoogleAnalyticsTracker( 6173): at libcore.io.IoBridge.connect(IoBridge.java:114)
W/GoogleAnalyticsTracker( 6173): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
W/GoogleAnalyticsTracker( 6173): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
W/GoogleAnalyticsTracker( 6173): at java.net.Socket.connect(Socket.java:842)
W/GoogleAnalyticsTracker( 6173): at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
W/GoogleAnalyticsTracker( 6173): at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
W/GoogleAnalyticsTracker( 6173): at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
W/GoogleAnalyticsTracker( 6173): at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingHits(Unknown Source)
W/GoogleAnalyticsTracker( 6173): at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
W/GoogleAnalyticsTracker( 6173): at android.os.Handler.handleCallback(Handler.java:725)
W/GoogleAnalyticsTracker( 6173): at android.os.Handler.dispatchMessage(Handler.java:92)
W/GoogleAnalyticsTracker( 6173): at android.os.Looper.loop(Looper.java:137)
W/GoogleAnalyticsTracker( 6173): at android.os.HandlerThread.run(HandlerThread.java:60)
W/GoogleAnalyticsTracker( 6173): Caused by: libcore.io.ErrnoException: connect failed: ECONNREFUSED (Connection refused)
W/GoogleAnalyticsTracker( 6173): at libcore.io.Posix.connect(Native Method)
W/GoogleAnalyticsTracker( 6173): at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:85)
W/GoogleAnalyticsTracker( 6173): at libcore.io.IoBridge.connectErrno(IoBridge.java:127)
W/GoogleAnalyticsTracker( 6173): at libcore.io.IoBridge.connect(IoBridge.java:112)
W/GoogleAnalyticsTracker( 6173): ... 12 moreI realize my adblocker is redirecting it to 127.0.0.1 but I was wondering if there is a way to find the origin of this? On another note, you reduced the power consumption of the kernel by 40%(gsam battery stats now shows my screen as taking 25-40% of the power as opposed to 5-10)! Great job!
U know what 127.0.0.1 is right?
Sent from my HTC6435LVW using xda app-developers app
Yes thats why I mentioned it. Its failing because it will obviously not go anywhere. I was asking if I can find the source as in- what app is causing it.
Right now, you have it turned off (the 0 is 0 == off, 1 == on, 2 == on but only if there is no usb device attached).
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
357I run this kernel with my own CM10.2 builds based on Chad's branches. These builds differs slightly from the builds that flyhalf is providing. As such, this is a pretty experimental to run any on ROM. That said, I would expect it to be compatible with all the CM10.2 based ROMs that are being produced by pio_masaki, .torrented, etc..
Finally, do not submit bug reports to ROM developers when running this kernel. If you have a bug that you want to report, please flash the kernel that came with your ROM (easiest is to just dirty flash the full ROM) and reproduce the problem.
Features, Installation Instructions, historic changelog, github link, Etc.
Instructions for configuring boot-time tweaks.
Releases
These kernels will only work with ROMs build with the M7 based kernel / CM 10.2 Nightlies
None
These kernels will only work with ROMs build with CM 10.2 changes from Aug 8, 2013
Version 3.5.1: Aug 25, 2013: Linux, Video
* A couple of small changes I made to the video, pushed to chad's tree but never released in my kernel.
* Updated Linux base from 3.4.54 to 3.4.58
Version 3.4.0: Aug 17, 2013: Video, Bluetooth, Audio, Network, Clocks and Power
* There are no changes here that haven't been pushed upstream to the CM 10.2 kernel.
These kernels are likely to break the camera for 4.2.2 / CM 10.1 based ROMs and only work for ROMs built prior to Aug 8, 2013.
Version 3.1.2: Aug 5, 2013: Video, Audio, Network, Camera
* Video changes pulled from the M7 and the msm-8960 kernels (sent to Chad's branch)
* Audio changes to get us closer to MR2 audio drivers (sent to Chad's branch)
* Chad's camera drivers.
These releases are tested against CM 10.2 builds only. They may or may not work for CM 10.1 based builds. I don't see any reason that they won't work on 10.1 but who knows....
* Note new version numbering: I've started numbering at 3.x.y as I was having a hard time keeping the Sense kernel and this kernel in sync on version numbers and because this is a big transition point anyway...
* Note: new annotation "sent to Chad's branch": I find it is hard to keep track of version to version differences because the majority of the work I have been doing I send to Chad's kernel for everyone to use. With version 3.0.2, I'm going to try to annotate the changes with this notation so that you can tell what is included or not included in each kernel version...
Version 3.0.2: July 28, 2013: Linux 3.4.54, CMU 10.2 (experimental!), clock fixes,
* Updated clock code from CAF (send to Chad's branch)
* Added SELinux support (send to Chad's branch)
* Bluetooth wakelock improvements (not perfect yet), (sent to Chad's branch)
* Added the ability to restore HTC's "color_enhancement" mode, to do so create a file /sdcard/crpalmer-color-enhancement.
* Fixed 2D clocks (send to Chad's branch)
* Fix clock settings during boot (send to Chad's branch)
* Fix display clock "esc_byte_ratio" that changed after we removed the world's biggest hack added by HTC to the video drivers (sent to Chad's branch)
* Regulator: correctly unprepare clocks when disabling them (send to Chad's branch)
* Change display initialization / shutdown to make it nicer and match up better with how the M7 is doing it (sent to Chad's branch)
* Large set of commits from the M7 kernel for the CM 10.2 display compatibility (sent to Chad's branch)
* Fix a dsi clock warning "stuck at off" (send to Chad's branch)
* Fix a warning about HDMI PLL clocks (sent to Chad's branch)
** These two commits may help some flickering screen issues, but you'll have to let it settle for awhile before you know for sure.
These releases require a ROM based on the CM commits on July 7th. Using a ROM with an older CM base will almost definitely fail to boot:
Version 2.0.39-cm1: July 12, 2013: Linux 3.4.52
* Updated clock code from CAF
* Do not let the video driver control our regulator (fixes crash when turning device on?)
* Fix vsync timing issue
* Regulator / voltage / frequency tweaks (closer to CAF / stock)
Version 2.0.38-cm1: July 7, 2013: Linux 3.4.52
* Linux version 3.4.51 / 52 merged in
* Reverted a small change to the PWM values used for the display (it wasn't giving any value so why change ti)
* Includes a major display overhaul from the cm-10.1 tree
These releases require a ROM based on the CM commits on June 23rd. Using a ROM with an older CM base will not necessarily work. Some ROMs released around the 23rd were built by reverting some changes made by the upstream CM committers. These may require an older kernel to work....
Version 2.0.34-cm2: June 24, 2013: fixes, debug messages
* Toned done yet more HTC debugging messages
* Enable UTF-8 codepage support for Windows file-systems
* Fix error in HTC's light-sensor calibration table (overflows the 16-bit number they are using)
These releases require a ROM based on the CM commits on June 6th. Using a ROM with an older CM base will not work.
Version 2.0.32-cm3: June 15, 2013: fix last_kmsg & a guess at crashes
* Fix /proc/last_kmsg
* Revert voltage changes in previous kernel
* Really remove some debugging that I meant to remove last releease
Version 2.0.32-cm2: June 15, 2013: display off fix, linux 3.4.49, scheduler & mutex improvements
* Linux 3.4.49
* Three scheduler performance improvements
* Move to more standard and slightly faster mutex implementation
* Fix for turning the display off
* Removed yet more excessive HTC debugging
* Changed some voltages and frequencies back to stock values to not confound any display problems
* Small audio fixes from CAF
Version 2.0.30-cm3: June 8, 2013
* Linux 3.4.48
* Fix CVE-2013-2595
* Decrease latency in cpufreq frequency changes
* Updated wifi driver to 1.88.21
* Small audio fixes
* Decrease display bandwidth from what chad has
Releases below here will not work CM-10.1 based builds sync'ed after June 6
* Version 2.0.29-cm5: June 2, 2013
* Use dedicated high priority work-queue to make cpufreq transitions faster
* Note: this is the first version that include chad0989's touchscreen fix and is required to fix it
* Version 2.0.28-cm2: May 28, 2013
* Version 2.0.27-cm4: May 26, 2013: This is probably the minimal version that will work on CM based builds including the 5/26 changes that chad0989 has made.
* Version 2.0.26-cm2: May 23, 2013: Initial CM compatible release12New release:
* Version 2.0.29-cm5: June 2, 2013
* Use dedicated high priority work-queue to make cpufreq transitions faster
* Note: this is the first version that include chad0989's touchscreen fix and is required to fix it12New release:
Version 3.4.0: Aug 17, 2013: Video, Bluetooth, Audio, Network, Clocks and Power
* There are no changes here that haven't been pushed upstream to the CM 10.2 kernel.8
Doh! Good question. I forgot to include this in the last changelog.
The 192 slot was removed because chad switched to a different clock driver and it would require some fairly intrusive changes to re-introduce it. According to the tables used for this driver, the 384000 slot uses the same power as the 192000 did in the previous version of the kernel. So, it should use the same power as the 192000 slot but allow more processing to be done before it switches to a higher slot.
