Related
Hello. I have been a "lurker" on these boards for roughly 2 years. I have rooted, flashed and installed custom ROMs, bootloaders, recoveries and radios on the following devices:
Samsung Vibrant (original samsung galaxy S)
HTC Amaze (a.k.a Ruby.... wire trick and all)
ASUS Transformer 1 WiFi Only model ( a.k.a TF101)
Anyway, I am posting for the first time. Because of this, I cannot post directly to the development thread involved with my issue. Never the less, here it is:
I am running RaymanFX's JellyBean Cyanogen 10 V6 (STABLE) with Rayman's custom kernel on my TF101. I was running a Revolver ICS ROM prior to installing this JB ROM.... or Revolution HD, I can't remember... anyway
I am having an issue with the TF101 either 1) involuntary reboot or 2) freeze/lockup/crashing after wakeup from sleep mode and complete loss of WiFi radio.
Yes, I have extensively searched the development threads and I found posts related to this one, but none of them solve the issue and I also noticed a few people have this same problem but have no known solution.
I have wiped and done clean install of this ROM several times always with the same result. I also flashed LiquidSmooth (Rayman worked on this ROM and his kernel is cross compatible) to see if it was ROM-related and discovered it is not.... this is a kernel issue. My wipe procedure is:
Factory Reset (cache/data wipe)
Run Superwipe script for TF101 from Android Revolution HD thread (format cache, data, etc...)
Wipe Dalvik Cache
Flash ROM
Reboot
Flash GAPPS (latest version linked on Cyanogen thread from goo.im)
Reboot
Everything runs buttery smooth and flawlessly, HOWEVER.... "Wake on WiFi fix" solution on RaymanFX's post does not work for me.
The "fix" is to designate WiFi Always On during Sleep. Changing this setting doesn't stick... WiFi still sleeps even with this setting corrected. With one caveat... Changing the setting to "Never" and then modifying WiFi Idle Timeout to "3 hours" and then changing the Keep WiFi on During Sleep to "Always" will delay the WiFi from idling out temporarily unless the tablet is in Sleep longer than 3 hours.... at which it idles anyway and causes a crash or reboot.
Secondly, I have discovered that the CPU Frequency setting under Performance could be part of the reason it crashes. I have "Set on Boot" enabled. Setting a CPU Frequency, regardless of governor, above 1408 Mhz WILL cause tablet to lockup/crash upon wakeup from Sleep as the processor jumps to maximum set frequency. If maximum frequency is set to 1408, it will stutter and lag out the system forcing it to become unresponsive to touch commands but "stable" and useable.... albeit very laggy. If the Max Frequency is set to 1200, it will NOT reduce the maximum frequency set for the CPU unless tablet is put into Sleep mode and then woken again.... it will constantly cycle between the "old" maximum frequency setting and the "new" maximum frequency setting (observed by monitoring the frequency in the Performance setting screen after changing from a higher max frequency to a lower max frequency and staying on the menu screen and allowing the CPU to "settle" without any user input).
I really like this ROM and I hate to give up on it, so I'm hoping someone out there will have an idea about what I can do to make this work... or at least recommend a different kernel that will work with this ROM and also has a way to change CPU frequencies and governers.
Any ideas?
Here is where I'll post my CM10 builds.
qwerty was the name I gave to the kernel I used to post here before I started to post entire ROM builds.
This is based on the amazing dhiru1602's work, big thanks to him.
Dowloads:
Google Drive
You can't resume downloads with GDrive. If you prefer other hosting websites, you can use the direct link of my builds to remotely upload them somewhere else. Dev-Host allows you to do that and allows you to resume downloads. Feel free to mirror my files.
Sources:
Device, kernel, vendor
Misc changes/instruction to build this ROM. The patches not available on Github are here.
Please, read carefully the whole post.
There are two different versions of the ROM. One is using the kernel 3.0, the other the kernel 2.6.35. Read the known bugs and flash the one you prefer.
I did some changes to this CM-10, I updated it and added some extra features such as inbuilt SD swap (Settings > Storage > Use external storage), possibility to show the navbar without rebooting (System > Power menu > navbar and enable it from the power menu. It doesn't work perfectly, keyboards and notification panel can go behind it) possibility to limit the number of background apps and other handy options.
I also backported some performance patches and misc fixes from CM-10.1 and some apps: Trebuchet, Apollo, Gallery (camera), Clock, CM File Manager and Superuser.
CyanogenMod 10 - kernel 3.0
Click to expand...
Click to collapse
Known bugs:
Backlight issues for some users: the screen backlight will automatically turn on when it's supposed to stay off.
Audio/video sync issues while recording videos at 720p, along with frames and fps drops.
Rare reboots. If they happen, post the content of /proc/last_kmsg.
CyanogenMod 10 - kernel 2.6.35
Click to expand...
Click to collapse
Known bugs:
Missing HW composer.
WiFi doesn't work perfectly. Some users report continuous disconnections or problems connecting to netowroks. Try to use a static IP in case you have problems.
Native USB tethering doesn't work. Use a third party app (tested: android-wired-tether).
The inbuilt Wi-Fi hotspot can be used only once, sometimes more, and after that a reboot is required to use it again. You can though use this modified version of android-wifi-tether, reboots are not required.
HD video playback suffer low framerate issues.
The 720p preview framerate is intentionally limited, especially while recording. The recorded video is (almost) fine.
There are sometimes lags in the preview while video calling with the front facing camera
Poor bluetooth headset sound quality. (I don't own a bluetooth headset, hence it's very hard for me to find the problem) - flash libaudio-BT-NR-fix.zip.
Release changes:
Code:
Look for the name of the zip in this thread to find its changes. This is no more updated.
...
20130425: Camera HAL updates. Removed background apps limit. Use the modified dev settings to choose the number of background apps.
20130416: Camera HAL: experimental changes
20130407: Partially working WiFi tethering (perfect with [I]android-wifi-tether[/I])
20130402: Several kernel changes, UMS regression fixed
20130329: Video pillarbox. Regression: UMS requires adb
20130326: Optimized build
20130320: SSID fetch fixed
20130319: Better wpa_supplicant support: WiFi scan and disconnecting bug fixed. Missing WiFi signal intensity fixed.
Instructions
Click to expand...
Click to collapse
Stock ROM / CM7 / CM9 / CM10 Alpha3 (or older):
dhiru1602 said:
IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
This ROM will wipe data due to different partitioning. The device would reboot while flashing and resume again.
Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
Click to expand...
Click to collapse
Stock ROMs only: Make sure you have CWM. Flash a custom kernel otherwise
Download the zip of the ROM and save it into the internal SD or the external one (*)
Reboot to recovery
Flash the downloaded zip
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
optional: Flash Google Apps (for Android 4.1.2, many things will break otherwise)
Reboot
(*) While flashing, the device will reboot and you'll see a different recovery after that.
If the zip is inside the internal SD, the flash will re-start automatically after the reboot.
If the zip is inside the external SD, you have to re-start the flash manually re-flashing the zip. If you don't do that, only recovery will work until you flash the zip.
CyanogenMod 10:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps (if you have already flashed them once, you can skip this step)
Reboot
Data wipes are mandatory only if you are not using CM10, it's not required otherwise.
It doesn't matter if you are going to flash the version with the 3.0 kernel and you are using the other, it should work.
CyanogenMod 10.1/10.2:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
Wipe data/factory reset
Reboot
Downgrades are probably not expected, that's why you need to do a data wipe.
Important note:
The modem is always replaced with XXLE4 modem when this ROM is flashed over a stock ROM, CM9 or CM10 Alpha 3 (or older).
You can easly replace it. Take modem.bin from the tar of a stock ROM, place it in /radio overwriting the existing one and reboot. This is required only once, modem.bin is never replaced while updating the ROM. I9003L must do this, I9003 users can use the included modem, but it's better to use the modem made for your region.
Useful informations
Click to expand...
Click to collapse
The latest versions of Instagram are not working due to a problem with related to the GPU binary blob. Instagram 3.4.0 is the latest working version. Probably every device using the same binary blob is affected (Optimus Black for example). You can download a modified version from here that will allow you to login.
The latest versions of Skype do not work properly, the preview is stretched and wrongly rotated. Use Skype 2.9.0.315 or see this post.
LEDs are not supposed to blink when a new notifcation arrives. They'll light up, but they won't blink. Making them blink would prevent the device from entering deep sleep.
(3.0 kernel) Once the battery is fully charged, it will start discharging and it won't be recharged automatically if at least 90 minutes have passed. You can forcefully charge it by unpluggin and re-pluggin the cable. This is an intended behaviour, charging the battery continuosly to keep it at 100% can shortnmyself toer its life.
This ROM allows you to force two apps to stay in memory. See this post for more info.
I made possible to toggle the navbar state directly from the powermenu modifying the existing expanded desktop feature, however it's not working perfectly. The navbar can go over the notification panel and the keyboard while in landscape. However it works as expected if you enable the navbar by setting qemu.hw.mainkeys or modding framework-res.apk. I have no intention to "fix" this as I can't see the utility of the navbar on our device.
(3.0 kernel) For some reason when the screen is turned off during a call by the proximity sensor, if enough time has passed it won't be turned on automatically. You can wake the screen immediately by pressing the home button or the power button or you can increase the backlight timeout from the settings. That will make the proximity sensor work for longer (I'm not sure, but I think the proximity sensor stops working exactly after this timer has expired). this problem is maybe solved.
FM radio is available through third party apps, such as Spirit FM
"Native" 3G video calls are not supported and most likely never will, flash a stock ROM if you need them. GTalk, Skype and all the other apps works though.
(3.0 kernel) if you lost your IMEI, WiFi will probably not work. See this for more info and instructions to fix the problem. No more required.
(3.0 kernel) part of the RAM is reserved. You'll see that we have 442MB 454MB of RAM, that's fine, the missing RAM is not really lost, it's still used.
If the keyboard keeps crashing, you probably flash the wrong gapps.
The magnetic sensor sometimes reports wrong values. When it happens, the field intensity is very high. This was observed with the 3.0 kernel, but probably the same thing happens with a 2.6.35 kernel.
(3.0 kernel) my SD card (it's probably a cheap SD card) is not working properly and I often have corrupted files. It worked fine with the kernel 2.6.35, so if you often have corrupted files, try a different SD card or use the old kernel.
Weird activity in standby? Read this.
(3.0 kernel) 1.2GHz is not stable on every device. I had to disable SmartReflex because it was causing crashes on my device. This means that the voltage of the OPP5 is locked the value I chose is not universally good. I'd prefer not to increase it more, if you have too many reboots, don't overclock. WARNING: don't tick "Set on boot" unless you are sure your device can handle OC. f you are stuck in a bootloop, flash disable_opp5.zip.
In case the max frequency is 1.1GHz, then SmartReflex is enabled and the option in DeviceParts has no effect.
If you find a bug not listed, please report.
Post as many informations as possible, ways to reproduce it and logs.
You can easily grab (almost) all the logs I need by pressing vol down, vol up and power at the same time ("recent" builds only). LEDs will blink and /storage/sdcard0/logs_qwerty/log_DATE.txt will be created. In case the memory is not ready, you'll find the files in /data/logs_qwerty/log_DATE.txt.
The standalone kernel is no more mantained. Flash the ROM instead.
Click to expand...
Click to collapse
Kernel - 2.6.35
Click to expand...
Click to collapse
After months of use, I decided to publicly release my kernel.
This is for CyanogenMod 10 Alpha 4.
It's based on the GB kernel sources released by Samsung (GT-I9003_GB_Opensource_Update2.zip), modified (mostly by dhiru1602) to work with CyanogenMod.
Because of my lack of fantasy I named it "qwerty". It sucks, but at least it's easy to remember.
Main features:
XDA_Bam's code and fixes:
◦ 5 OPPs
◦ Booting at stock speed (1000MHz)
◦ Slight undervolt (3%) on all OPPs
◦ Home button double presses fix
◦ Lowered processor transition latency
◦ Stable Bluetooth connections
Modified light sensor driver: [1]
◦ Disabled hardcoded filter. CyanogenMod has its own filters, enable it from the settings.
◦ Dynamic polling interval
◦ Code cleanup
Modified battery driver [2]
CPU Governors:
◦ Ondemand (default)
◦ SmartassV2
◦ Conservative
◦ Performance
I/O schedulers:
◦ Deadline (default)
◦ Noop
◦ CFQ
◦ SIO
Toggable FSync
Fixed always ON LEDs bug when used for notifications only
VPN networks support (not tested)
Slightly increased touchkeys sensitivity (from 45 to 35)
Other minor changes and optimizations
Downloads:
version 4.0: kernel-qwerty-cm-10-galaxysl-v4.0.zip: kernel with custom DeviceParts.apk [3], hostap and tiap_drv.ko [5]
clean-qwerty-cm-10-galaxysl.zip: restore zip with dhiru1602's kernel
UPDATE: USB composite is still a bit messed up. Windows can't recognize the phone when RNDIS (USB tethering) is enabled (working fine with Linux).
If you need RNDIS, flash this kernel release or the previous one.
Additional zips:
powerHAL-cm-10-galaxysl.zip: power HAL for boosting the CPU when ondemand is used [4]
libsensor-cm-10-galaxysl.zip: custom libsensor. Read note [1]
Changelog:
Code:
22/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.1...v4.0"]v4.0[/URL]
02/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.0...v3.1"]v3.1[/URL]
01/03/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.1...v3.0"]v3.0[/URL]
12/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.0...v2.1"]v2.1[/URL]
09/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v1.0...v2.0"]v2.0[/URL]
08/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/commits/v1.0"]v1.0[/URL] - Initial release
Notes:
[1] I made it compatible with the prebuilt libsensor included in CyanogenMod, but I'm using my own libsensor and maybe I didn't test this kernel with the stock one for long enough. I hence added my libsensor, just in case. If you want to restore the original libsensor, simply remove /system/lib/hw/sensors.latona.so.
[2] You can modify "samsung-battery" wakelock length through DeviceParts. By default it behaves like the original module. If you see "Android System" or anything else eating your battery with no reasons, increase the delay or restore the default one.
[3] DeviceParts.apk (System Settings > Advanced) is included because of some additional settings useful when this kernel is used. I'm not a Java dev, so it's probably not perfect, but it works quite well. I took pieces of code from other devices (mostly Crespo, Aries and S2). The source code is available, suggestions are more than welcome.
[4] Power HAL will make the CPU jump to a certain frequency (I set 800MHz) whenever Android requires it (when the screen is touched for example). Power HAL will also limit the max freq to 800MHz (my choice, not too fast, not too slow) when the screen is off. You can change the boosting freq from my custom DeviceParts. CPU frequencies changes (See XDA_Bam's thread for more info about variable overclocking) are not expected. If you don't like it, simply remove /system/lib/hw/power.latona.so. Few more lines about power HAL here.
[5] hostap and tiap_drv.ko make WiFi tethering possible using this modified version of android-wifi-tether.
Special thanks to dhiru1602 and XDA_Bam for their awesome work.
Wow. I'll flash it for sure.
Thanks for sharing.
Update:
Flashed and it works just fine. Just changed max freq to 1200.
Deviceparts looks very professional as well.
Hats off to u buddy. Also kernel name is really good buddy. Dont worry about that
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
Re: [KERNEL][CM10] qwerty [08/02/13]
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app
Re: [KERNEL][CM10] qwerty [08/02/13]
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003
imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Works fine for me. Try wiping cache+dalvik cache.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003
Click to expand...
Click to collapse
Are you using SIRI kernel?
Hetalk said:
Works fine for me. Try wiping cache+dalvik cache.
Are you using SIRI kernel?
Click to expand...
Click to collapse
I am just using the signal fix kernel by loSconosciuto before ...........
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.
Re: [KERNEL][CM10] qwerty [08/02/13]
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Sent from my GT-I9003 using xda premium
Re: [KERNEL][CM10] qwerty [08/02/13]
Hetalk said:
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.
Click to expand...
Click to collapse
i post here becoz i wanna flash this kernel will try what u say later, thx
Sent from my U9GT2 from moage.com using xda premium
^ You'll need to wait for users to get thru a battery cycle to report battery drain. I did charge my phone to 100% after flashing qwerty .. so will report my experience tomorrow.
Re: [KERNEL][CM10] qwerty [08/02/13]
just flashed this kernel.. on top of my cracker that i am using previously.. no problem on boot.. upgrading apps as usual.. ive noticed the speed, scrolling and such.. its faster than cracker .. the speed of gb is there..gonna test for some time.. thanks.. via slimbean 3.1 A4..
Sent from my GT-I9003 using xda app-developers app
I am pleased thank you very much !!!
Governor smartassV2 and IO Scheduler deadline (reputable boost daily)
Mini CPU 300/1000 is an exellent choice (I guess the hotboot fix)
it's just what I need ^^
Thank you for taking us solicitous
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
just added a tab (specific options) available in the parameter menu
vishal24387 said:
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
Click to expand...
Click to collapse
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decisions mostly depend on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
vishal24387 said:
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Click to expand...
Click to collapse
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Click to expand...
Click to collapse
All our kernels based on the sources released by Samsung use a prebuilt module for WiFi. Dhiru tried to use the opensource driver, but it didn't work.
This prebuilt module, taken from our stock ROMs, requires a prebuilt and modified wpa_supplicant which is not completely compatible with Android 4.0+ (Samsung didn't give us the changes required to make the opensource one work). To make things worse there's dhcpcd, we have to use an old version because of the old wpa_supplicant.
In other words: it sucks.
With some access point there are no issues, with others WiFi works, but not so well and with some others nothing works.
EDIT:
Now that I think of that, there are maybe some differences when this kernel is used. I took the prebuilt module from XXLE4 instead of taking it from EDIT2: XXKPM
The warning message I get the first time I turn WiFi (maybe it happens even with the other module, I didn't try it) on suggests me that something was changed in XXLE4, but I don't know if this is a good thing or not.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Click to expand...
Click to collapse
I'm starting to think the problem is CWM. For now only you and spacebar2011 had issues. I will PM you something when I'll have some free time to find the problem. If nothing works, I'll just give you the tars to flash the kernel with ODIN as I did with my signal fix kernel.
@Hetalk
Thanks for trying to help, but he is a peculiar situation. The problem is not the updated blob or a wrong flash, he (and spacebar2011) tried to flash my signal fix kernel several times over a clean CM10 with no success.
rodero95 said:
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Click to expand...
Click to collapse
Dunno, battery life had never been exceptional for me. If you use your phone a lot, any kernel will give you a bad battery life. You can see differences only if you keep your phone most of the time in idle, with mobile data disabled.
wee2wee said:
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
Click to expand...
Click to collapse
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.
loSconosciuto said:
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.
Click to expand...
Click to collapse
Thanks...found it...
loSconosciuto said:
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decision mostly depends on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
Click to expand...
Click to collapse
Thanks for ur simplified explaination This means in order to bring smoothness ondemand will keep most of the time freq at 800 mhz (as per ur settings). But definitely its going to affect battery life as just for a simple touch freq will raise to 800 mhz directly. Anyway overall it depends on user who want battery life or smoothness
I have used ur fixed signal kernel for longer time. That kernel really works very well when we use phone (even with 2g net). But surprisingly in deep sleep mode (means with gsm network on on and 2g net off) then there is very heavy battery drain For me its 25% battery drain in 9hr deep sleep mode. But if we keep our phone phone offline in deep sleep mode then it will drain battery just 4% in 9hr. Strange...!!!
I will monitor tonight also with that signal fix kernel. and final tomorrow I will flash this kernel on clean cm10a4 so that I can compare both ur kernels
EDIT : My doubt was right. Your previous signal fix kernel works really good. Yesterday night tested and I found that lost 3% battery in 8 hrs standby. Means my previous 25% battery loss was not a correct observation. Anyway now I will flash this kernel and tell u the results
Re: [KERNEL][CM10] qwerty [08/02/13]
Well, its obvious that keeping a continuous connection with the network costs battery and that when we are connected with mobile network it will eventually change between signal modes (2g, HSDPA, edge, etc) and that also costs battery.
That's why mobile network use to consume more battery than WiFi or offline.
Sent from my GT-I9003 using xda premium
Really nice Kernel with good combination of battery and performance and many good tweaks
Thank you very much Sir :laugh:
Problem Reproduction:
1. Boot the device.
2. No problems during normal usage or when charging.
3. Let the device go to sleep for a couple 2-4 hours
SOD:
When pressing the power button after opening the lid the screen turn on but instead is a black screen, device still seems operational, but screen does not come on, only happened two times since flashing and randomly with nothing I can pin-point it to have a theory from some research, but do not know if it is related.
RR:
Device not reboot unless reboot is initiated, TF101 is rebooting randomly during deep sleeps.
Neither RR or Deep Sleeps occur when the tablet is charging or in active use.
Specifics
Tablet: TF101 Tab and Dock, 16 GB WIFI
Recovery: TWRP 2.3.2.3
ROM: EOS 4 Nightlies Build 99
Kernel: KatKernel_96_JB4.2_Lidpatch
Specific Customization Apps:
K.A.T_V1.2.7 - using KAT Audio, KAT Media Service, GPS fix installed, and adblock hosts file in place.
SetCPU - Profile 1 (screen-on priority 50): Overclocked to 1504Mhz with Smartassv2 govenor, min setting 312 MHZ (read some people do this prevent SOD and RR for the min setting)I/0 Scheduler SIO (also read on XDA others have been very stable with this setup). Profile 2 (Battery less than 38%, priority 75): Stock Max to 312 Mhz Min with conservative governor and SIO scheduler.
**Note: All SOD and RR have occured while SetCPU is in profile 1.
Ram Manager Pro: Minfree setting set to More RAM for devices with over 512MB Memory. JV Heap set to 64MB
Lux Dash: Used to fix auto-brightness setting being too low on transformers. Have it set to dynamic update brightness.
Other settings
Disabled Hotword detection for Google Now fix.
Removed test keys from build.prop and renamed SuperSU to SU in system/apps to get around the Root checks of the TimeWarnerCable live streaming app.
Background: My transformer was in on stock ICS OTA update and was so slow it was barely usable and used battery like crazy. I followed all the procedures on XDA (http://forum.xda-developers.com/showthread.php?t=2063406) and http://public.timduru.org/Android/tf101/eos4/ for wiping, i wiped and formated everything (dalvick, cache, system, factory)besides the externalSD card. Flashed the 99 nightly build and was impressed with how smooth everything was, was like a brand new tab. Did some bench marking and saw the good reviews on KAT kernel, so I flashed KAT kernel and installed KAT app and was even more impressed with performance, benchmarks jumped significantly. Tested everything I could think possible and did not see any major bugs so I figured this would be a good settling point. I did not re-install any of my apps from the Titanium or My Backup Pro or system settings, i installed everything from the market and configured systems settings, after I stopped all the update activities that when I noticed the SOD and RR issues (due to android assistant showing startup times when I had not initiated a reboot). Two days or so ago I installed Reboot Logger to keep track of the RRs. I noticed one SOD on the 18th after 2 hours of inactivity and one on the 19th around the same amount of time of inactivity. There was four RRs on the 19th and two on the 20th. Last night I was doing some digging and saw a bunch of feedback for JB on disabling the location services in setting and app settings, so I implemented that last night as well as removed the dock SD card after before leaving the device in a state of inactivity. After those two changes there was only two RR vs the four the prior day (Although if this is a semi-fix it is a pain not being able to use auto-location for apps) and no SODs again YET.
Let me just say that I love the ROM and KAT Kernel and KAT app, I am extremely impressed with all of it with the way to performs and how buttery smooth it is compared to stock. Lots of Kudos to the developers. If possible I would like to leave KAT Kernel in place because of the performance benefits. If I could get eliminate or minimize the SOD and RRs to an extreme minimum this would be a perfect/Rock solid solution. Attached are the Kmsg and logcats before the last RR and a screenshot of the RR from the Reboot Logger (note the RR/soft boots do not have a restart timstamp next to them, the ones that do are initiated reboots. .
Do you think the latest preview (175) or nightly 100 help the SODs or RRs? Also since the previews are compiled in Linaro and this is the native format for the TF101 be slightly more stable (I did a lot of digging on XDA but could not find a lot one way or the other to justify one direction or another), any empirical data from testing? Just curious. Thanks
Turning on Fsync in KatKernel
pursleyt said:
Problem Reproduction:
1. Boot the device.
2. No problems during normal usage or when charging.
3. Let the device go to sleep for a couple 2-4 hours
SOD:
When pressing the power button after opening the lid the screen turn on but instead is a black screen, device still seems operational, but screen does not come on, only happened two times since flashing and randomly with nothing I can pin-point it to have a theory from some research, but do not know if it is related.
RR:
Device not reboot unless reboot is initiated, TF101 is rebooting randomly during deep sleeps.
Neither RR or Deep Sleeps occur when the tablet is charging or in active use.
Specifics
Tablet: TF101 Tab and Dock, 16 GB WIFI
Recovery: TWRP 2.3.2.3
ROM: EOS 4 Nightlies Build 99
Kernel: KatKernel_96_JB4.2_Lidpatch
Specific Customization Apps:
K.A.T_V1.2.7 - using KAT Audio, KAT Media Service, GPS fix installed, and adblock hosts file in place.
SetCPU - Profile 1 (screen-on priority 50): Overclocked to 1504Mhz with Smartassv2 govenor, min setting 312 MHZ (read some people do this prevent SOD and RR for the min setting)I/0 Scheduler SIO (also read on XDA others have been very stable with this setup). Profile 2 (Battery less than 38%, priority 75): Stock Max to 312 Mhz Min with conservative governor and SIO scheduler.
**Note: All SOD and RR have occured while SetCPU is in profile 1.
Ram Manager Pro: Minfree setting set to More RAM for devices with over 512MB Memory. JV Heap set to 64MB
Lux Dash: Used to fix auto-brightness setting being too low on transformers. Have it set to dynamic update brightness.
Other settings
Disabled Hotword detection for Google Now fix.
Removed test keys from build.prop and renamed SuperSU to SU in system/apps to get around the Root checks of the TimeWarnerCable live streaming app.
Background: My transformer was in on stock ICS OTA update and was so slow it was barely usable and used battery like crazy. I followed all the procedures on XDA (http://forum.xda-developers.com/showthread.php?t=2063406) and http://public.timduru.org/Android/tf101/eos4/ for wiping, i wiped and formated everything (dalvick, cache, system, factory)besides the externalSD card. Flashed the 99 nightly build and was impressed with how smooth everything was, was like a brand new tab. Did some bench marking and saw the good reviews on KAT kernel, so I flashed KAT kernel and installed KAT app and was even more impressed with performance, benchmarks jumped significantly. Tested everything I could think possible and did not see any major bugs so I figured this would be a good settling point. I did not re-install any of my apps from the Titanium or My Backup Pro or system settings, i installed everything from the market and configured systems settings, after I stopped all the update activities that when I noticed the SOD and RR issues (due to android assistant showing startup times when I had not initiated a reboot). Two days or so ago I installed Reboot Logger to keep track of the RRs. I noticed one SOD on the 18th after 2 hours of inactivity and one on the 19th around the same amount of time of inactivity. There was four RRs on the 19th and two on the 20th. Last night I was doing some digging and saw a bunch of feedback for JB on disabling the location services in setting and app settings, so I implemented that last night as well as removed the dock SD card after before leaving the device in a state of inactivity. After those two changes there was only two RR vs the four the prior day (Although if this is a semi-fix it is a pain not being able to use auto-location for apps) and no SODs again YET.
Let me just say that I love the ROM and KAT Kernel and KAT app, I am extremely impressed with all of it with the way to performs and how buttery smooth it is compared to stock. Lots of Kudos to the developers. If possible I would like to leave KAT Kernel in place because of the performance benefits. If I could get eliminate or minimize the SOD and RRs to an extreme minimum this would be a perfect/Rock solid solution. Attached are the Kmsg and logcats before the last RR and a screenshot of the RR from the Reboot Logger (note the RR/soft boots do not have a restart timstamp next to them, the ones that do are initiated reboots. .
Do you think the latest preview (175) or nightly 100 help the SODs or RRs? Also since the previews are compiled in Linaro and this is the native format for the TF101 be slightly more stable (I did a lot of digging on XDA but could not find a lot one way or the other to justify one direction or another), any empirical data from testing? Just curious. Thanks
Click to expand...
Click to collapse
Turned on Fsync in KatKernel for additional testing on SODs and RRs.
pursleyt said:
Turned on Fsync in KatKernel for additional testing on SODs and RRs.
Click to expand...
Click to collapse
1 RR while tablet was asleep, plugged in and charged to 100%.
Solved
pursleyt said:
1 RR while tablet was asleep, plugged in and charged to 100%.
Click to expand...
Click to collapse
After Upgrading to preview version 181 and turning Fsync on with K.A.T kernel the TF101 is 100% stable with no RR or SODs after 48 hours.
pursleyt said:
After Upgrading to preview version 181 and turning Fsync on with K.A.T kernel the TF101 is 100% stable with no RR or SODs after 48 hours.
Click to expand...
Click to collapse
1 RR with SD CARD in dock, know problem with EO4/Kat Kernel removed SD card from dock when not in use, stable again.
pursleyt said:
1 RR with SD CARD in dock, know problem with EO4/Kat Kernel removed SD card from dock when not in use, stable again.
Click to expand...
Click to collapse
using preview 181 kk96 dock sd removed getting RR during sleep, I tried with fsync=on, rr's stopped but that prevented tab from entering deep sleep. now trying with microsd removed. still docked
HEATING:
Heating while charging isn't an issue pls. You can let your phone cool down before charging it in a cool place. You can either power it off or put it on Airplane mode while charging. (This will reduce the charging time and also some activities by apps which slow the charging) Heating is normal while charging owing to the Quick Charge x.0 capability of Qualcomm Snapdragon 617 (MSM8952). It will heat up. Heating is reduced in the latest builds, especially while recording video via the camera. This semi-budget oriented processor isn't designed for heavy gaming pls, despite 3GB of DDR3 RAM available to it. If you're a hard core gamer or someone who likes to overclock stuff, this isn't the right phone.
If you feel your phone is heating with normal usage too, consider removing apps which are useless and clear the cache followed by a reboot. See to it that the apps are updated. You can switch to WiFi instead of Mobile Data (keeps my athene cool idk why). If nothing works, consider a factory reset; else shift to a custom ROM if you can and test.
PERFORMANCE:
General phone performance of Nougat has been better than Marshmallow for sure, but for many, 7.0 has had the notification drawer stuttering issue in some cases and Bluetooth being turned on automatically after turning Airplane mode ON. Overall experience is smooth. But many people do not like stock ROM very much, because of the lack of features. AOSP and LineageOS based ROMs are much better that stock in terms of speed. For god's sake don't use the task killer apps or battery savers like CCleaner / CleanMaster/ DU Battery Saver. Apps staying in the memory (RAM) are good for your device until your phone is lagging. Clearing the things from the recents panel will force them to start again from scratch, consuming the CPU and of course the battery.
BATTERY & CHARGING:
Stock N wasn't very good in terms of battery after all in comparison to MM despite the improved doze mode introduced in Nougat. Well this is the case in almost every android OEM that the battery performance went down in transition from one Android version to another. However, the March 1 update is said to fix a bit of battery and security issues. Android has the habit of collecting garbage (but that makes it smart too) and this can be one of the reasons why battery and performance issues occur after an OTA. The best thing after a "dirty/problem causing" update is to do a factory reset. Anyways, it is advised to clear the cache before and after doing an update. For god's sake don't use the task killer apps or battery savers like CCleaner / CleanMaster/ DU Battery Saver. Apps staying in the memory (RAM) are good for your device until your phone is lagging. Clearing the things from the recents panel will force them to start again from scratch, consuming the CPU and of course the battery.
Battery Saving and charging Tips:
Please understand the difference between Screen On time of a complete cycle and the usage time. People start judging the battery from the estimated time left after the first charge itself. A tip is to fully charge the battery after a clean flash and then let it drain till 15%. Do not let the battery drain completely, Li-ion batteries lose their capacity over time and are designed to run between 20-100 percent. Battery life of your phone is completely dependant on your usage. Turning off Auto-Rotation, WiFi, Bluetooth, Sync, Mobile Data, Location Services and scanning (almost everything ) when not needed can give you the best battery life possible. You can consider using Greenify although you should avoid any such thing. Android learns how you use it, no need to comment about the 2 H SOT you're getting after a clean flash. You might also want to uninstall the useless apps and block the wakelocks (which you understand) if possible. Turn off the SIM card if it's in very low network. If nothing is helping you, you might consider doing a factory reset too.
Checkout this amazing thread by @rirozizo and the video by XDA TV.
https://www.youtube.com/watch?v=3Zt2j8lFbJQ
Ghost Touch: Your touchscreen is at fault. Visit the service center please.
Screen Retention: Your display is defective. Turning the phone off for a while and then setting blue light filter at 5% for Black colour or changing the RGB values is a temporary fix. Visit the service center please.
Random Reboots: Try factory resetting your device, see if you installed something wrong and flash latest stock firmware, just in case, you know. Else the service center only can fix the issue if still present.
For not being called a noob:
1. Read XDA and other forums and think before you do anything to your phone.
2. Ask in the community if you have doubts. (Read Rules and XDA University's New User's guide first)
3. Always make backups before flashing new things. (Use TitaniumBackup and TWRP backups)
Check the videos by XDA-TV and Rootjunky ( @Tomsgt )
https://www.youtube.com/watch?v=_rEsgCrvEqY
https://www.youtube.com/watch?v=nyr3FstDKH0&index=1&list=PLgLZvFga2ml4Atl32E4c_ZslfrTJJDUfr
https://www.youtube.com/watch?v=j-i59R51Cys
4. See this video by XDA-TV:
https://www.youtube.com/watch?v=JmvCpR45LKA
5. Stop using useless apps and be patient pls.
Valar Morghulis!
Good thread, I'll add a couple of my tips here.
- ohmergerd, there's thousands of ROMs for the G4! Which ones are the best???? Nearly every single ROM for the G4 subtracting perhaps GZR ROMs and RevivorOS/optimized stock is LineageOS based (Invicta is basically Lineage with MM kernel blobs and faux/OMS integrated). There's basically no performance differences, just feature differences based on the discretion of the dev.
- If heating is STILL an issue for you, disable the 4 big cores. There isn't a significant difference in everyday use- the LITTLE cluster handles the UI and basic apps anyway.
- Haven't noticed notification bar lag since the 7.1.2 builds. If you have lag (depending on your ROM), using blur or transparency helps trick your eyes into seeing no lag. If lag persists, force enable scrolling cache and speed up the animations.
- If you have a custom kernel and your RAM usage isn't an issue, disable KSM, Adaptive Memory Killer, and/or ZRAM and Kernel Adiutor/EXKM. While useful if you let your memory use skyrocket, if you are conservative in your memory use these memory killers just suck up CPU cycles.
- Build prop tweaks/L Speed/HEBF don't work. Completely placebo, except for governor tweaks.
- USB-OTG is great, I recommend getting a dongle if you're a flashaholic. Much easier and quicker to simply plug in your USB to flash instead of plugging in your phone, transferring the ROM, flashing, etc.
- Use a trickle charger, and save that fast charger for emergencies (camping, flights, etc.).
- Disable a bunch of Google's **** in settings- I advise going through Activity controls as Google takes snippets of keyboard input, voice, web history, video history, etc. This adversely affects battery life especially if you have a weak signal, as Google Play Services continuously attempts to push through their telemetry data. This is also why you get 2hrs of SoT after a clean flash.
- On stock-based ROMs (to eliminate lag), boot the ROM once, then reboot to recovery and flash the latest Aroma GApps package with the apps you want. Then, mount /system, and start deleting all apps in /system/app or /system/priv-app that begin with "3c". This effectively removes Motorola updates and telemetry, and also updates your GApps- the stock GApps are very old, and updating them caused Play Store errors and miscellaneous battery sucking services.
- Mr. Shield Protectors suck. Badly cut-out, misaligned, etc.
Hard reset: A term with the common misconception here in the group. Hard reset means nothing in android smartphones. It is only a term for older computers where you manually had to reset the old electrical parts from the charge they held.
Factory reset via the settings is equivalent to the Wipe Data/Factory reset available in the stock recovery.
Also, always sign out from your Google account before doing the wipe, else chances are your device may enable Factory Reset Protection and lock the device.
Normally my phone was using two BIG cores (and the four LITTLE ones). Each core was utilized around 40-60%.
Withing kernel manager I have set the minimum value for the BIG cores to 1 and I have lowered the minimum frequency value for that core. Now the utilization on that core is close to 100%.
Now the phone is cold all the time (except when charging with the Fast Charger) and I have no lag issues whatsoever.
Oh, btw, on some kernels (EX 1.07, Vegito), workqueue power saving is built in which iirc tries to schedule tasks on the fewest cores as possible, so on these kernels which tend to turn off cores and lower frequencies while asleep the wakeup action, especially while dozing, the wakeup action will be met with significant lag/delay.
If you have a delay when turning on your phone with these kernels (or even stock kernels for some ROMs), disable the setting called wq_power_saving.
I have the solution for random reboots. But only for those devices that reboots 4 or 5 times every day. Just open your device and disconnect the battery for 30 minits. Or also you can change the battery (confirmated it works)
negusp said:
Good thread, I'll add a couple of my tips here.
- ohmergerd, there's thousands of ROMs for the G4! Which ones are the best???? Nearly every single ROM for the G4 subtracting perhaps GZR ROMs and RevivorOS/optimized stock is LineageOS based (Invicta is basically Lineage with MM kernel blobs and faux/OMS integrated). There's basically no performance differences, just feature differences based on the discretion of the dev.
- If heating is STILL an issue for you, disable the 4 big cores. There isn't a significant difference in everyday use- the LITTLE cluster handles the UI and basic apps anyway.
- Haven't noticed notification bar lag since the 7.1.2 builds. If you have lag (depending on your ROM), using blur or transparency helps trick your eyes into seeing no lag. If lag persists, force enable scrolling cache and speed up the animations.
- If you have a custom kernel and your RAM usage isn't an issue, disable KSM, Adaptive Memory Killer, and/or ZRAM and Kernel Adiutor/EXKM. While useful if you let your memory use skyrocket, if you are conservative in your memory use these memory killers just suck up CPU cycles.
- Build prop tweaks/L Speed/HEBF don't work. Completely placebo, except for governor tweaks.
- USB-OTG is great, I recommend getting a dongle if you're a flashaholic. Much easier and quicker to simply plug in your USB to flash instead of plugging in your phone, transferring the ROM, flashing, etc.
- Use a trickle charger, and save that fast charger for emergencies (camping, flights, etc.).
- Disable a bunch of Google's **** in settings- I advise going through Activity controls as Google takes snippets of keyboard input, voice, web history, video history, etc. This adversely affects battery life especially if you have a weak signal, as Google Play Services continuously attempts to push through their telemetry data. This is also why you get 2hrs of SoT after a clean flash.
- On stock-based ROMs (to eliminate lag), boot the ROM once, then reboot to recovery and flash the latest Aroma GApps package with the apps you want. Then, mount /system, and start deleting all apps in /system/app or /system/priv-app that begin with "3c". This effectively removes Motorola updates and telemetry, and also updates your GApps- the stock GApps are very old, and updating them caused Play Store errors and miscellaneous battery sucking services.
- Mr. Shield Protectors suck. Badly cut-out, misaligned, etc.
Click to expand...
Click to collapse
Thanks for the tips.
Using Root explorer I deleted the 3c stuff and updated the Gapps via Aroma installer (never knew this Aroma version existed).
Where do I find the Activity controls thing?
bluegrass55 said:
Thanks for the tips.
Using Root explorer I deleted the 3c stuff and updated the Gapps via Aroma installer (never knew this Aroma version existed).
Where do I find the Activity controls thing?
Click to expand...
Click to collapse
It's in settings>Google, first 3 menus iirc.
i just had to unroot, re-lock my boot, and flash the latest firmware because someone has been hacking my phone. I purchased a Samsung phone and been switching the SIM between phones. I wish custom ROMs were more secure, flashing every ROM available, some took longer then others. After seeing that the Samsung KNOX wasnt able to be hacked, i decided to flash your stock N package. They are yet to get in my XT-1644 since earlier after the flash.
Am i stuck on the Stock ROM or is there a way to keep from getting a rooted with unlocked bootloader, hacked?
Greetings, I have a problem with constant wakelocks on my MI11i phone since the day I bought it. Those wakelocks drain battery by 30% overnight, but also cause increased drain during the day in standby too since they instantly kick in as soon as the phone is locked, overall resulting in poor battery life. Even thou I am not an advanced user and has no need of it, I went so far that I completely factory reset the phone(this was the 2nd time), then reflashed new recovery and new official ROM to see will that sort the issue, then for a good measure I also rooted it with TWRP and Magisk. I tried underclocking the cpu to the lowest but it makes no difference while in standby since obviously that isn't the case. I tried using icebox but there were no processes that had SNS or RMNET in their names, so I just froze some analytics apps. Both wakelocks are gone as soon as I turn on the airplane mode or switch to wifi. Any app that can help me freeze those or edit something in kernel?
I found a rom that fixes the wakelock, listed here https://miuiflash.com/roms/miui-csx/alioth/miui-csx-v13-0-8-0-stable-alioth
But i couldn't find a way to contact the author for more info can i fix the kernel myself