Related
This is a flashable (via Clockwork) zip of the stock Sense kernel for the Vision. It will work on any of the Vision-based phones (G2, DesireZ, etc) but you must be running Sense UI.
Details
Stock kernel binary, nothing touched: 2.6.32.21-gd2764ed
Ramdisk modified with the following:
Property changes: ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Support for /system/etc/init.d scripts.
Conservative and powersave governor modules (loaded automatically on startup). These are not active unless selected, which is why they are loaded.
Overclocking module included, not loaded automatically.
Kineto kernel module included (needed for wifi calling).
CIFS module included.
User Impact (i.e. What does this do for me?)
When using "adb shell", you'll immediately be given a root prompt as opposed to having to "su" first.
"adb remount" works and will remount /system "rw".
You can "adb push" or "adb pull" from any location on the system, once you've remounted.
adb runs during boot up, to help diagnose any issues after applying a change (new kernel, mod, etc).
Mock locations are enabled.
Ability to select 2 additional power governors in SetCPU.
Support for CIFS mounts using supported apps (i.e. Astro).
Support for WiFi calling, assuming other support libs/apps are present.
Disclaimer
As with any modification (ROM, patch, etc), you run the risk of damaging your device. While unlikely, it is important to consider this possibility before proceeding. I take no responsibility for any such damage, data loss or otherwise.
Download Kernel
Fifth haha lol. Dude awesome job on the sense port thanks.
Sent from my T-Mobile G2 using XDA App
mcp2009 said:
Seriously? mad I said first? Don't think your post mattered. I posted to say thnx. What did you post for?
Click to expand...
Click to collapse
Yes. I'm upset you said first because this is supposed to be a serious forum. I posted to point that out. Apparently no one else agrees with me but whatever.
To the OP, thank you for the kernel that I'm sure a number of people are looking for. Sorry for jacking your thread.
not a rom its a kernel, thx OP
Thanks dev I appreciate your work towards Sense UI. Does anyone mind telling me what this kernel will be good for? It says stock Sense, so does that mean, its like the stock kernel but on sense? or that its the desire z kernel?
Phawkes said:
Thanks dev I appreciate your work towards Sense UI. Does anyone mind telling me what this kernel will be good for? It says stock Sense, so does that mean, its like the stock kernel but on sense? or that its the desire z kernel?
Click to expand...
Click to collapse
I presume it's a modified version of the DZ kernel, because the G2 doesn't come with Sense.
Ok, so what exactly do the modifications offer to the end user?
What does this do?
I think by isntalling this kernel it will give you perma root in the rom on a g2.
meaning that root wont get wiped out after reboot.
Even though the emmc is set to s-off the kernel might not have been aware of that.
If i get a bit of time i will give it a shot.
been running the desire rom for a day since i like sense but i noticed i didnt have root even though i could flash stuff (recovery) and hboot was still the eng.
I could be wrong but does the OP refer to setting ro.secure=0 to disable the wp on /system?
so far even though we are perm rooted with an s-off bootloader /system is still set to ro, at least it is for me.
Can someone confirm or deny and explain.
Sent from my HTC Vision using XDA App
what is this? is this desire z with root?
Went back to stock with cyanogen baconbits....it drained too much battery too quick for me
Sent from my T-Mobile G2 using XDA App
Phawkes said:
Ok, so what exactly do the modifications offer to the end user?
Click to expand...
Click to collapse
Here's a rundown of visible changes:
When using "adb shell", you'll immediately be given a root prompt as opposed to having to "su" first.
"adb remount" will remount system "rw".
You can "adb push" or "adb pull" from any location on the system, once you've remounted.
adb runs during boot up, to help diagnose any issues after applying a change (new kernel, mod, etc).
Mock locations are enabled.
You can drop shell scripts into /system/etc/init.d, which are executed at the end of the boot process automatically.
I'll update the OP with this list.
Updated to include several more kernel modules, still the original binary. Check the original post for details.
so.... how do I load the OC-module? Thanks for the kernel
Do you have a public repo I can get the source from? I'd love to compile it with the interactive governor as well, and perhaps BFS.
Novek said:
so.... how do I load the OC-module? Thanks for the kernel
Click to expand...
Click to collapse
yeah i second this. i'm kind of scratching my head here...
To oc you have to:
Insmod /system/lib/modules/z_oc.ko
To get the conservative and powersave scalings you must do an insmod for cpufreq_conservative.ko and cpufreq_powersave.ko in the same folder...
It only oc to 1ghz though
Sent from my HTC Vision using XDA App
Novek said:
To get the conservative and powersave scalings you must do an insmod for cpufreq_conservative.ko and cpufreq_powersave.ko in the same folder...
Click to expand...
Click to collapse
Those are actually loaded for you automatically via initscript in /system/etc/init.d and custom ramdisk which is included with this kernel.
See this thread for more info on the OC module:
http://forum.xda-developers.com/showthread.php?t=813681
Only difference you need to consider from the directions in that thread is the OC module is located in /system/lib/modules rather than /data/local. It will clock all the way up to 1.42ghz if you dare (I don't).
Oki... I just saw that those two weren't in setcpu, and got them loaded by insmod. Thanks
Sent from my HTC Vision using XDA App
cifs Can not be used
cifs Can not be used，File size is also problematic
3200KB?
When using "insmod /sysytem/lib/modules/cifs.ko"
init_module'insmod /sysytem/lib/modules/cifs.ko' failed(On such file or directory)
Why?
I am trying to run the script given here: http://forum.cyanogenmod.com/topic/595-alternative-setcpu-script/
I followed the directions and placed the file in /system/local/bin and got rid of the ".sh" but to no avail.
Then I tried placing the file in /sbin and also /system/bin both of which did not work.
What i mean by "not working" is that I run the "setcpu" command in terminal emulator and get "setcpu: not found" as a result.
Can someone help a noob out?
Your using CyanogenMod right? I am assuming this is the ROM you're running....
Negatron, I'm using MIUI.
M3RK said:
Negatron, I'm using MIUI.
Click to expand...
Click to collapse
It won't work, since it was meant for the CM kernel, so if you're using CM, you'd be fine.
Sent from my girlfriend according to my current girlfriend
RMarkwald said:
It won't work, since it was meant for the CM kernel, so if you're using CM, you'd be fine.
Click to expand...
Click to collapse
Okay, I'm confused. Aren't the bulk of the commands being run independent of the kernel? Basically he's just writing to the /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq, scaling_max_freq, and scaling_governor files, all of which we have. I understand that each kernel has different clock speeds but don't the if statements account for that? Maybe I'm way off...
If this script won't work, would anyone care to share how I can change cpu max and min with a script? I am currently running MIUI with Tiamat.
Oh and thanks RMarkwald for the help so far.
Hey no problems, maybe ask the developer of your kernel if the script would work. If not, maybe things have a slightly different name or something that some simple tweaks would get it to? Just a thought...
Hello. Here's the second version of our ZN Custom Firmware. It is created by ZeroNull and vdsirotkin (4pda.ru). The original post is here.
WARNING - If it works on your device, be careful, as with an unlocked bootloader you can brick you tab faster than you can imagine.
Installation:
1) You'll need to do everything, what is written here or here. If your bootloader is already unlocked, and recovery is installed - you can miss this point.
2) Download the firmware - http://depositfiles.com/files/smnuqxxei
3) Install it using CWM or TWRP
4) That's all!
Features:
Patched 1.014 ICS kernel. Now mounting of /system partition is unlocked
modded boot.img
Better battery saving in standby
Rooted
NTFS SD cards supported
Init.d scripts enabled
bind-dir with autorun support from init.d (not working with NTFS)
Superuser and AcerRing is integrated in system partition
All Acer's and some Google's apps removed
Packages included (in user partition, removable via Apps Manager in Settings)
Adobe flash player
BSPlayer Lite
GPS Test
ES File Explorer
Quadrant Standart
Quick Boot
QuickBoot
Titanium Backup
Touch Recalibrate
"DIGI Clock" and "Weather forecast" widgets
Custom build.prop integrated
Root mode for adb unlocked
AcerRing with corrected background picture
Battery in %
Custom bootanimation: Frosty-Boot [v.Acer] with GEARS for Acer Iconia Tab A100
Screenshots:
First . Anyways, some screenshots would be nice .
Theonew said:
First . Anyways, some screenshots would be nice .
Click to expand...
Click to collapse
And what would you like to see on them?
ZeroNull said:
And what would you like to see on them?
Click to expand...
Click to collapse
The Acer ring for one. Were any modifications done to the UI, or does it have the stock look?
There are no UI changes, all the changes are made "inside" of the firmware
is this just a custom boot image?
If you have changed ro.product.model to A500, the Acer recovery installer app (once I release an A100 version) will think its an A500.
Sent from my SPH-D710 using Tapatalk
no, it's not only the boot.img, there are some other changes.
Well, if someone have installed recovery to install this firmware, so he or she won't need to install it again. Am I right?
I can't figure out how to download this. I don't read rushian (or greek or whatever that is). I entered the captcha and then clicked the link that LOOKed like what I was supposed to and it starting download some file ending with .msi so I canceled it.
Usually, custom ROMs come with their own boot.img, so if someone installs then, then a custom ROM, then this gets overwritten. if they install this, on top of their custom ROM, it'll work, unless the custom rom had a custom boot.img that it was dependant on.
Can you tell me if ro.product.modelalias still says A200 with this patch?
Sorry, tomorrow i'll upload it to some other place. To download this file untick where it's written smth about Яндекс.Бар. And there won't be any .msi file. Or use Google Translate
You are right, there is a custom boot.img, and many features in the firmware depend on it. But boot.img is not the only feature of this firmware. That was what I wanted to say
In build.prop it's written ro.product.modelalias=A100.
ZeroNull said:
Sorry, tomorrow i'll upload it to some other place. To download this file untick where it's written smth about Яндекс.Бар. And there won't be any .msi file. Or use Google Translate
You are right, there is a custom boot.img, and many features in the firmware depend on it. But boot.img is not the only feature of this firmware. That was what I wanted to say
In build.prop it's written ro.product.modelalias=A100.
Click to expand...
Click to collapse
Got it, downloading now. The link dissappeared when I hit the Translate button. But unchecking the checkbox worked. Thanks!
I updated my code to look at both ro.product.model and ro.product.modelalias.
Thanks!
the slowed down cpu is for better battery life? might be installing later
You're right.
What impact would slowing the cpu have on the overall performance? Thanks
utctigers said:
What impact would slowing the cpu have on the overall performance? Thanks
Click to expand...
Click to collapse
Some tasks (especially heavier ones) will not be as snappy (only if the cpu is limited to the slower speed also depending on how slow it is set to). The battery life should be significantly better though.
thanks, any plan on adding USB host mode?
Theonew said:
Some tasks (especially heavier ones) will not be as snappy (only if the cpu is limited to the slower speed also depending on how slow it is set to). The battery life should be significantly better though.
Click to expand...
Click to collapse
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium
ptesmoke said:
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
No, there is nothing stopping the integration of more governors into the kernel. If you do heavy usage on the tab with the cpu underclocked so low (and limited at that point), then yes, it will put more strain on the processor. One would want it set so low for conserving battery (and not really using the tab for anything e.g. While you're sleeping). I usually set profiles on my devices to lower the frequency and set the governor to conservative when the screen is off (never done it on this device though).
Raul77 said:
thanks, any plan on adding USB host mode?
Click to expand...
Click to collapse
Our hardware (motherboard) doesn't support it.
ptesmoke said:
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
The reason is called "kernel sources". Without 'em we can't do anything (overclock, add governors) with our processor.
If you look at the usage of frequences, you'll see, that 80% of the working time the frequence is 200 mgz. And while testing, I didn't meet any problems with 456mgz, all the programs and games work smooth, and still 80% of the usage time is on 200mgz.
If you don't like this slowing down, why on earth you can't disable is? everything is written in the 1st post
thx
Thx to you !!!
Il Will try it today.
Systèm in RW mod ?
The memory swap is integrated ?
Obligation of full wipe before installation ?
And the last question... have we to make a advanced restoration of the unlocked Boot with CWM after flashing.
THANK YOU in advance for your answers to my question.....
samco08 said:
Thx to you !!!
Il Will try it today.
Systèm in RW mod ?
The memory swap is integrated ?
Obligation of full wipe before installation ?
And the last question... have we to make a advanced restoration of the unlocked Boot with CWM after flashing.
THANK YOU in advance for your answers to my question.....
Click to expand...
Click to collapse
Yes, it's included in root access
If it's not written about memory swap, than it's not intergated
No, /data must not be wiped, and /system/ will be wiped automatically, but only in 1.XX versions. 1.XX.X are only a kind of small update to already installed firmware
No, recovery and bootloader are deleted from this package, so they will stay as they were.
As MameTozhio is to busy (or sick and tired ) to answer me, I have to ask my question here...
I was trying to flash Turbo Boost on MiDroid... flash was successful, but swap file won't be created... Mame said that the ROM doesn't set permissions correctly... and i think that with manual instalation will be the same problem :/
Similar problem was with ViperFX cointained in ROM... it was asking to download additional libs, but after download and reboot it was asking the same question...
Additionaly, Turbo Charger script wasn't been loaded on boot, I had to run it manually...
So here's my question:
Is there any workaround for such problems? Changes in some system files or maybe script running on boot, that will repair setting permissions process?
parkourz said:
As MameTozhio is to busy (or sick and tired ) to answer me, I have to ask my question here...
I was trying to flash Turbo Boost on MiDroid... flash was successful, but swap file won't be created... Mame said that the ROM doesn't set permissions correctly... and i think that with manual instalation will be the same problem :/
Similar problem was with ViperFX cointained in ROM... it was asking to download additional libs, but after download and reboot it was asking the same question...
Additionaly, Turbo Charger script wasn't been loaded on boot, I had to run it manually...
So here's my question:
Is there any workaround for such problems? Changes in some system files or maybe script running on boot, that will repair setting permissions process?
Click to expand...
Click to collapse
V4A has been updated. I didn't realize literally until 5 minutes after I uploaded 3.12.6 o-o
I have no clue what's wrong with it loading things.. could you do a clean install and not flash turbo boost and give me the results of cat /proc/swaps?
I'm going to run my ROM through my modded Android Kitchen to see if I can update busybox etc..
Here's the shot of cat /proc/swaps
Because of that full emmc swap ROM gets extremely laggy after 5 min of use, so I have to reboot it by holding power button... I hope it's the only reason why it's so slow and laggy...
parkourz said:
Here's the shot of cat /proc/swaps
Because of that full emmc swap ROM gets extremely laggy after 5 min of use, so I have to reboot it by holding power button... I hope it's the only reason why it's so slow and laggy...
Click to expand...
Click to collapse
okay so init.d is working. that's good.
MameTozhio said:
okay so init.d is working. that's good.
Click to expand...
Click to collapse
so where I have to dig to speed it up and make Turbo Boost work? flash and fix permissions before reboot?
parkourz said:
so where I have to dig to speed it up and make Turbo Boost work? flash and fix permissions before reboot?
Click to expand...
Click to collapse
I'm not sure =/
This is the support thread for the Sprint variant of the StarKissed Note 4 kernel.
This kernel currently supports all North American carriers through the use of specialized release packages that will detect your device version and make appropriate adjustments.
Kernel Development Thread:
http://forum.xda-developers.com/showthread.php?t=2915824
Issues, Reports, & Configuration
Direct installation available via Flashify (for root users) - Android Apps on Google Play
Heimdall with the S5 patch is needed to flash from a computer. Odin cannot flash this kernel.
Additional information for Sprint variant:
Potentially Unavailable:
Potentially Unsafe:
Incomplete / Inactive:
OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk
egodriver07 said:
OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Nothing. It's an issue with the policies. I will be compiling a new version shortly that should address it.
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
still no luck
twistedumbrella said:
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
Click to expand...
Click to collapse
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Thank you very much for the suggestions yesterday, but it looks like not using the _64 toolchain was the problem.
New problem, it boots to the download mode screen saying boot failed. I thought I'd start simple to troubleshoot. If I break apart one of your images (14 MB) and rebuild it with:
Code:
mkbootimg --kernel twisted-zImage --ramdisk twisted-ramdisk.cpio.gz -o boot.img
The resulting boot.img is 11 MB, whereas yours is 14 MB, and it fails to boot. I'm not sure why it's several MB smaller. I looked at your script, but the image generation is in another script it seems. Am I using an old mkbootimg or something? I don't know could account for 3 MB at the mkbootimg stage. I also tried using unmkbootimg to get the other flags shown below, but that didn't help.
Code:
--base 0x1dfff00 --cmdline 'splash=silent console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --pagesize 4096
Thanks again for any suggestions.
ffolkes said:
Thank you very much for the suggestions yesterday, but it looks like not using the _64 toolchain was the problem.
New problem, it boots to the download mode screen saying boot failed. I thought I'd start simple to troubleshoot. If I break apart one of your images (14 MB) and rebuild it with:
Code:
mkbootimg --kernel twisted-zImage --ramdisk twisted-ramdisk.cpio.gz -o boot.img
The resulting boot.img is 11 MB, whereas yours is 14 MB, and it fails to boot. I'm not sure why it's several MB smaller. I looked at your script, but the image generation is in another script it seems. Am I using an old mkbootimg or something? I don't know could account for 3 MB at the mkbootimg stage. I also tried using unmkbootimg to get the other flags shown below, but that didn't help.
Code:
--base 0x1dfff00 --cmdline 'splash=silent console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --pagesize 4096
Thanks again for any suggestions.
Click to expand...
Click to collapse
Kernels now use DTB. The other script handles that. You also may need a new mkbootimg if you have never dealt with DTB. Older binaries don't include the parameters.
In all honesty, most of these questions can be answered just by looking at the commits in the stockish repo. It doesn't contain all of the extra modules and modifications, but it has the same core changes to build it. If 50 commits seems like too much to dig through, you may not want to develop kernels. You will typically be wandering through kernels with 1K+ commits looking for one change.
twistedumbrella said:
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
Click to expand...
Click to collapse
Still no luck with the new version.
fifapro23 said:
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Click to expand...
Click to collapse
fifapro23 said:
Still no luck with the new version.
Click to expand...
Click to collapse
Nothing was changed in respect to that issue as you have noted by replying to the same post both times.
fifapro23 said:
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Click to expand...
Click to collapse
I just read this statement again and realized this is our first real case of PEBCAK
The minimum is the absolute lowest the cpu is allowed to drop.
The maximum is the absolute highest the cpu is allowed to increase.
It is a range, not strictly one or the other.
If you set your min to 268 and max to 2.5, it is not 268 or 2.5 only. It could also be anything between them, such as 1.5 or 422
Yankeractive tends to favor 1.5, but that is in the governor design. It's something that will eventually be adjusted during cleanup.
sorry
I reverted back to 20.47 from 22.12 because it was sticking at 1.4. Also for fast charge options, what does failsafe do? And do we just keep fast charge to disable or force ac?
ryanalan82 said:
I reverted back to 20.47 from 22.12 because it was sticking at 1.4. Also for fast charge options, what does failsafe do? And do we just keep fast charge to disable or force ac?
Click to expand...
Click to collapse
I haven't looked into failsafe. I used the defaults from the Note 3 for that since I never use it.
Depends if you use it or not. Disabled is will not boost USB or wireless charging. Force AC will boost them to emulate an AC charger.
Ok now having the 1.4 sticking on 20.59. Reverting to earlier today.
ryanalan82 said:
Ok now having the 1.4 sticking on 20.59. Reverting to earlier today.
Click to expand...
Click to collapse
The update was only posted about 5 minutes ago. It will show 1.4 when you touch it because that is the touch boost.
How do i download your kernel i csnt figure out how to find it.. it just keeps tskimg me to mega website????
shawn01 said:
How do i download your kernel i csnt figure out how to find it.. it just keeps tskimg me to mega website????
Click to expand...
Click to collapse
Installation Instructions:
Download the image file from Goo or Mega to install via flashify, rashr, etc
Click to expand...
Click to collapse
If you don't feel like looking back at the big discussion in the dev thread on issues with Mega, that is the alternative.
sorry im struggling here. I installed twrp and booted into recovery and now i cant boot my phone back it goes nack to twrp but something comes up saying kernel is not seandroid enforcing set warranty bit: kernel. I never fladhed anything but twrp. So im hoping to find stovk kernel zip so i can flash fro, twrp..
shawn01 said:
sorry im struggling here. I installed twrp and booted into recovery and now i cant boot my phone back it goes nack to twrp but something comes up saying kernel is not seandroid enforcing set warranty bit: kernel. I never fladhed anything but twrp. So im hoping to find stovk kernel zip so i can flash fro, twrp..
Click to expand...
Click to collapse
If it says warranty bit is kernel, that isn't booting back into recovery, that is a normal boot. You just have to be patient until it finishes. The downloads here are not the stock kernel anyway. Both versions are modified kernels.
It goes back to trwp recovery every time