Thomas.Raines presents
The Lightning Zap! kernel for the Blaze 4G
ATTN:
I thomas.raines, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise mess up your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I revamped the Lightning Zap! kernel across the board. Since I have so many of them I was loosing where I was on each one. So I have now broken it down into 3 phases:
Phase 1: Introduction of LZ kernel to device
Phase 2: Fine tuning of tweaks, values, etc
Phase 3: Implementation of OC/UV
Phase 4: Continue updating and adjusting as necessary
From now on I will name the .zip accordingly as well:
Blaze_p2.1
On a good note, I think this latest update will finalize phase 2 and now I can work on OC/UV...
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Instructions:
Make a backup
Download .zip to PC
Transfer .zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Phone will automatically reboot after install**
Wait 10 minutes
Enjoy the Lightning Zap!
This kernel was tested on CM10 nightly. This kernel and tweaks will work with any version of CM10.
See 3rd post for further instructions on improving and customizing your Lighting Zap! experience.
**The first boots always takes the longest especially after a fresh install. If you pull a logcat during the first boot, you may see a few errors with the vacuum script. This is normal, and will be "fixed" after the phone has built the databases for the apps.
Please allow 24 hours after install and 1 full charge cycle before reporting results. Always provide me with a logcat with any issues you may experience.
Source Code:
kernel
msm8660-common_lz_kernel
vendor_lz-kernel (LZ vendor files for ROM compiling)
LZ Flashing Packages (For those of you just compiling the kernel)
Includes flashing script, binaries, etc for the Blaze, Nitro and Skyrocket
Special thanks to:
dr4stic for patching he cm kernel to work with our devices
xan for Voltage Control app
jenbek for donating
Download links and changelog
Download links and changelogs here:
Blaze_p4.4-5.zip
Nothing super spectacular here, just upstream maintenance
NOTE** Since we don't have a supported recovery, and I can't find enough info about it, I cannot add the dual boot feature.
Anybody that has some knowledge on making a custom recovery, particularly TWRP with dual boot, help me (KTEMP!)
Moved source to LightningZap github
Blaze_p4.4-4A.zip
Removed topology and mpdecision in 4.4-4, but found all the gov's work best with mpdecision so I added it back.
Adjusted CONFIG_NR_CPUS (number of cpu's) to cm default 999999 which causes the use of a CPU mask array. Small performance hit initially, but an overall vast improvement especially when multi-tasking.
p4.4-3
Merged from upstream
Added missing msm_mpdecsion blobs
All governors and schedulers seem completely stable now (Keep testing please)
Added True CD-ROM emulation interface (Not fully working on my computer. Need testers to verify with windows and linux) here is how to use it! (Special thanks goes to DooMLoRD and his doom kernel for the Xperia Z)
init.d scripts updated with new mount params
Enjoy!
p4.4-2
Raised vm_max_readahed to 4096.
Lowered default max cpu freq to 1512.
Changed min cpu freq to 384 to fix Lionheart and Gallimaufry instability.
p4.4-1
Fixed ability to change cpu frequency. Your changes now stick after closing app.
Used userdebug lunch option. Now if you have red border on screen, it's more than likely in the ROM. Talk to your ROM dev.
Possible fix for loss of su/root. (Let me know if you still loose it after flashing. I didn't have any issues this time.
Archived Changelog
Enjoy the Zap!
Exhilarate Download links
**ATTN** If you get an error about disabling flash recovery and/or fixing root(su), ignore them. It is a false error in recovery. Disabling flash recovery broke root (super user), but fixing root had no effect
If for some reason your root gets borked, flash this.
BTW, this should be fixed in the final update
Exhilarate_4.4-6.zip
**Note-- This is just a preview. Full 4.4-6 will be done soon. I just wanted to get something out for you guys.
It's been a long time, but I finally got it!
Fixed updater-script thanks @ ns17
This update is for cm-11.0/KitKat 4.4
OC'd to 1512
Complete revamp of the kernel including voltage and frequency tables
Dropped VoltageControl app support
The ability to control voltages isn't working right now, but I will have it fixed shortly
With this revamp, there are some minor bugs, but I'll be working thru them. I just wanted to get this out to you guys. It's been long over due.
Moved RootBrowser to /data/app for easier removal (if you don't want it that is)
Enjoy!
Exhilarate_p3-cm-10.2.zip
For changelog, refer to post above...for now...lol
Source code notes
just add this to your local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="https://github.com" name="LZkernel" />
<project name="TeamFahQ/msm8660-common_lz_kernel" path="kernel/samsung/msm8660-common" remote="LZkernel" revision="jellybean" />
<project name="TeamFahQ/vendor_lz-kernel" path="vendor/lz-kernel" remote="LZkernel" revision="master" />
<project name="TeamFahQ/lge-kernel-iproj" path="kernel/lge/iproj" remote="LZkernel" revision="android-msm-3.0-jb" />
<project name="TeamFahQ/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jellybean" />
<project name="TeamFahQ/android_device_samsung_t769" path="device/samsung/t769" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="jellybean" />
</manifest>
You MUST use my repo for the devices (as noted above) in order for LZ to build correctly. You will also need to manually copy the /scripts and modules to your directory where you zip things up. /system/etc/lzbp.sh is gone so make sure you remove the perms from your flashing script (Working on fixing this now)
Or (in terminal):
Code:
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/TeamFahQ/Paranoid_manifest/master/local_manifest.xml
And remove the devices that you do not wish to use. Then repo sync. If you are using this as a basis for another device, make sure you check out the commits.
I hope this isn't a stupid question but if I continue to download nightly updates after installing will I have to re-install this kernel after each update?
Sent from my Samsung Galaxy S Blaze.
^ Yes, I believe so
Thanks for sharing.
Here is a good app to show you how your CPU is behaving.
I use it daily. http://forum.xda-developers.com/showthread.php?t=1740622
Chitown021 said:
I hope this isn't a stupid question but if I continue to download nightly updates after installing will I have to re-install this kernel after each update?
Sent from my Samsung Galaxy S Blaze.
Click to expand...
Click to collapse
Unfortunately, yes...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Is there any chance that this will work with cm9?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
KrimsonChin said:
Is there any chance that this will work with cm9?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Quite possibly... the one I made for the sgs4g was reported that it does work on both cm9 and 10...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
thomas.raines said:
Quite possibly... the one I made for the sgs4g was reported that it does work on both cm9 and 10...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Didn't work. Just stayed on a black screen after the Samsung wording appeared.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
I'm running this right now and everything definitely moves faster and smoother than stock cm10 kernel. However it does have its moments where its choppy a bit lagy. Is this the same on everyone else's? By the way. Thank you so much for building us a kernel. We really appreciate you showing the blaze some love
Edit: Also, it gets extremely hot while charging. Have you tested it during overnight charges or have an idea what I can do to prevent it overheating?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Tried it on ICS Rom and stuck on black screen after reboot...
..
jbats said:
I believe this only works with gingerbread.
Click to expand...
Click to collapse
No, I believe this only actually works with JB/CM10
Absolutism flawless. Another TFQ hit!!
T so much Thomas.
So it's officially a no go for ICS/CM9... CM10 only guys... sorry... I'll see if I can get one made for ICS as well after I finish the ROM I am building for you guys...
As for the device getting hot while charging:
Is it on or off?
If it is on, try closing any open apps.
Try a different charger/wall socket.
I left mine on the charger overnight with it on and no additional apps installed, and it didn't get hot at any point. I was using a charger for my old blackberry, but it has the same voltage, amperage and wattage as the stock charger for the blaze.
thomas.raines said:
So it's officially a no go for ICS/CM9... CM10 only guys... sorry... I'll see if I can get one made for ICS as well after I finish the ROM I am building for you guys...
As for the device getting hot while charging:
Is it on or off?
If it is on, try closing any open apps.
Try a different charger/wall socket.
I left mine on the charger overnight with it on and no additional apps installed, and it didn't get hot at any point. I was using a charger for my old blackberry, but it has the same voltage, amperage and wattage as the stock charger for the blaze.
Click to expand...
Click to collapse
Yep cm9 and cm10 use a different kernel well mine and dr4stic are different also flyers miui is based on my cm9 and the next two roms I'm releasing are based on my own changes for ICs kernel so until I can upload my source the Lz won't work on it :/ lol
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
thomas.raines said:
So it's officially a no go for ICS/CM9... CM10 only guys... sorry... I'll see if I can get one made for ICS as well after I finish the ROM I am building for you guys...
As for the device getting hot while charging:
Is it on or off?
If it is on, try closing any open apps.
Try a different charger/wall socket.
I left mine on the charger overnight with it on and no additional apps installed, and it didn't get hot at any point. I was using a charger for my old blackberry, but it has the same voltage, amperage and wattage as the stock charger for the blaze.
Click to expand...
Click to collapse
Yea sorry. I don't know what was going on that one time but no more overheating probs anymore. Thanks again. Can't wait to try your master piece when it drops!
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Ltitus8900 said:
Yea sorry. I don't know what was going on that one time but no more overheating probs anymore. Thanks again. Can't wait to try your master piece when it drops!
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
That's good... keep me posted if it happens again. As for my masterpiece, I'm working out the last few kinks so it will build...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Presents
bhundven's
Subtly Modified Stock CWM 5 KJ6 KernelTHIS KERNEL HAS BEEN DEPRECATED. USE BHUNDVEN'S BLASTOFF KERNEL INSTEAD.
http://forum.xda-developers.com/showthread.php?t=1828171
NOTES
Need help with BLN? Check here: BLN Support
This kernel is still in beta! Please help us test for stability. Logs are always welcome
This is still Bryan's kernel, the only changes I have made were to the initramfs and a few changes here and there to the kernel itself.
Bryan is developing again! This thread will continue to be open to discuss the new releases here unless he decides to open his other kernel thread for XDA.
FEATURES
In addition to the changes bhundven has made:
SuperSU instead of Superuser (adds root support using the kernel alone, regardless of which ROM you install this on)
BLN support added (thanks to neldar and our newest Team Acid member m4xm4n) MARKET LINK
Includes a Team Acid boot splash and recovery image (courtesy of theexel and Tablador)
Cleaned up voodoo extensions directory to remove zipalign for TW launcher
Forcing an ext4 conversion by default regardless of lagfix option
Enabled cifs, fuse and tun kernel modules
NOTES
Want to change your boot splash image? Here's a git repo that helps you do just that:
https://github.com/morfic/Samsung-logo
(Thanks to tablador who linked me to this!)
INSTRUCTIONS
Download the kernel zip file
Flash it using CWM
Wipe the Dalvik Cache before you reboot! (CWM > Advanced > Wipe Dalvik Cache)
If you are already rooted, you can also use the SGS Kernel flasher
DOWNLOADS
kernel-sms-kj6-v0.2.0-bml.zip (MD5: 9cc2278d0d00c61210e1311181de0b67)
Older Versions: Sourceforge
SOURCE CODE
Android SGS4G Kernel at GitHub
Android SGS4G Initramfs at GitHub You might want to use the voodoo branch, not master!
Want to learn how to build the kernel from source? Look at these instructions:
Building From Source
CHANGELOG
Apr 11, 2012
v0.2.0
Enable SVNET_WHITELIST to fix wakelock reboot problems
Bump version to '-sms-kj6-v0.2.0-bml'
Integrated lights.s5pc110.so into the initramfs to add BLN support
-- The kernel itself now copies the file to the rom instead of doing it via CWM
The CWM zip should no longer cause your phone to reboot after the kernel flashes
April 8, 2012
v0.1.1-rc3
Now using SuperSU instead of Superuser
BLN support added (thanks to neldar and our newest Team Acid member m4xm4n)
You need the BLN Control app from the market to use BackLightNotifications! MARKET LINK
February 24, 2012
v0.1.1-rc2
Now using Team Acid's changes to voodoo initramfs
Removed a lot of unneeded checks and their included files since we're only dealing with the sgs4g
Added battery capacity check before voodoo lagfix
Modified the ext4 conversion process to use the bonsai defaults
Forcing an ext4 conversion by default regardless of lagfix option
Removed check for froyo anti_boot_glitch since this is a GB kernel
Enabled cifs, fuse and tun kernel modules
Click to expand...
Click to collapse
Here is Bryan's OP, at the link below
http://forum.xda-developers.com/showthread.php?t=1380331
Flashing.. thanks team acid!!!!!
Sent from my SGH-T959V using Tapatalk
Gasps holy snizzap thanks for this man!!!!!
Sent from my SGH-T959V using XDA App
FB,
I have had to revert both my wifes and my phone to version 2d because of random reboots and locking up with the last 2 of Bhund's releases. Been back on 2d for 6 days now, not a single reboot or lock-up. Do you believe any of the changes you have made will prevent this happening? Or should I stay on 2d for now?
As always, thanks for the contribution.
At the moment it's essentially the same as Bryan's kernel. I've only changed some of the voodoo files right now but you can test if you wish
htaak said:
FB,
I have had to revert both my wifes and my phone to version 2d because of random reboots and locking up with the last 2 of Bhund's releases. Been back on 2d for 6 days now, not a single reboot or lock-up. Do you believe any of the changes you have made will prevent this happening? Or should I stay on 2d for now?
As always, thanks for the contribution.
Click to expand...
Click to collapse
Sent from my SGH-T959V using XDA App
FB you are the man!
Awesome work.
I've looked at Bryan's commits between 0.1.0 and 0.1.1 and actually there was not much. The changes were only to the config file to disable DMA, DIDLE, and some serial interface that got there from aries config. Bigger changes that brought in some kernel code happened before 0.1.0. But the 0.1.0 does not make my phone reboot, and the latest changes don't seem to be significant enough to cause reboots.
I'm going to try this build and see how it behaves. Maybe it was something silly like Bryan's 0.1.1 build was somehow damaged during compilation/linking/packaging.
Good job FB!
Can we do a FULL nandroid restore with this?
Jerry D said:
Can we do a FULL nandroid restore with this?
Click to expand...
Click to collapse
Well its basically Bryan's kernel so I'm pretty sure u can.
-Sent From My Amazing SGS4G-
iHelper said:
Well its basically Bryan's kernel so I'm pretty sure u can.
-Sent From My Amazing SGS4G-
Click to expand...
Click to collapse
Ya. And I did before.. I'm embarrassed to admit that I forgot the issue that made my stop using the CMW 5 version. I probably should've posted in the stupid questions thread.
Thank you for your reply
Big Thanks FB! And Team Acid!
Just flashed and love your new logo..sorry for the stupid question about full restore. I kinda fell behind a little and even forgot some stuff lol.
Hell yeah Team ACID
Looks like that freenode session had some results. I'll give it a go. Thanks.
Pure awesome.
Freaking Brilliant 251
So did cleaning up voodoo scripts allow faster boots.
Sent from my SGH-T959V using xda premium
I had some random reboots when I first flashed Valhalla Black but not sure if it was from the kernel or the ROM. Either way, it was most likely something I screwed up.
Just flashed this new update on my phone and it seems like everything transitions way faster than it used to. And all my apps seem to load faster. I'm mostly sober so I'm reasonably sure I'm not seeing things
Anyway, I don't talk on here much cuz I only get half of wtf you guys are talking bout. Plus there's too many lazy ingrates. But FB, you and the other actual decent people who spend hours working for free have made owning this phone a blast. Thanks for everything you all do and if there's ever anything I can do that doesn't require hard work of any kind, lemme know.
Sent from my A500 using xda premium
Thanks FB, working great.
Sent from my SGH-T959V using XDA App
airfluip1 said:
So did cleaning up voodoo scripts allow faster boots.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Not yet. I'm gonna be doing some more work on the scripts tonight since the kernel takes WAY too long to boot. What I noticed from a quick logcat inspection I did before I left home in the morning, it's zipaligning everything every time. I'm thinking it'd be better to only force the zip align once a week so that way you still get speedy apps and you don't have to suffer every time you reboot .
AntonX said:
I've looked at Bryan's commits between 0.1.0 and 0.1.1 and actually there was not much. The changes were only to the config file to disable DMA, DIDLE, and some serial interface that got there from aries config. Bigger changes that brought in some kernel code happened before 0.1.0. But the 0.1.0 does not make my phone reboot, and the latest changes don't seem to be significant enough to cause reboots.
I'm going to try this build and see how it behaves. Maybe it was something silly like Bryan's 0.1.1 build was somehow damaged during compilation/linking/packaging.
Click to expand...
Click to collapse
Hmm. Has it been only certain ROMs giving you reboots? I haven't had issues so far but I have my phone in my pocket all day so I haven't noticed if it does reboot.
Modified kernel (Fb) + VB (Raver) + Adrenaline shot VB with scroll cache tweak (dsexton) = Triple acid burn!
Nibbles Kernel v0.1.4
Base: Team Fah-Q's Lightning Zap (Original Version)
Linux Version: 3.0.61
Overview:
I originally made this exclusively for the Nibbles ROM just to see if I could do it. I've had countless messages asking to release this as a separately supported Kernel for the SR. So, here it is. This is the version currently included in the Nibbles ROM and I intend to keep them in sync. To those of you that bugged the crap out of me about this new thread ... here you go ... enjoy.
Compatibility:
AOSP / CM10 ROMs / JellyBean / Non-Touchwiz ROMs
Samsung Skyrocket, Hercules and T-989 (you will need rotation fix for 989 - don't ask me for it)
Features:
CPU Speeds up to 1.782GHz
Under/Over Voltage Support
GPU Over Clocked (based on which you choose to download)
ARM big.LITTLE Topology
1.5GHz Fast Boot
USB Fast Charge
Added Governors
Added I/O Schedulers
MSM mpdecision
Lots of other changes and tweaks.
CPU Governors:
intellidemand, pegasusq, gallimaurfy, interactivex, smartassv2, wheatley, interactive, conservative, userspace, ondemand (tweaked slightly), performance
I/O Schedulers:
noop, deadline, cfq, sio, vr, bfq, zen
Init.d Scripts:
smart zipalign at boot
governor (ondemand tweaks) - edit as necessary
systweaks
vacuum sqlite db optimization
Notes:
First boot may be slow as zipalign and sqlite tweaks run for the first time.
Installation will wipe cache and dalvik.
***DOWNLOAD Nibbles Kernel v1.4 HERE!***
Download:
http://tinyw.in/wURw
MD5:
9ed630cbf86cb51cfe0cea86bacade0e
Click to expand...
Click to collapse
***DOWNLOAD Nibbles Kernel v0.1.3 HERE!***
The difference between the downloads is only the GPU speed. You can download and flash either of these at any time without wiping your system. Note that the installation will wipe your cache and dalvik, so after you reboot, let the apps setup and settle for a few minutes.
Stock GPU Speeds: http://tinyw.in/JOmM
MD5: 4dbdfc9322a7f27db97b32a8bb1cc0c4
GPU Clock Moderate (3D @ 300MHz / 2D @ 228MHz): http://tinyw.in/Answ
MD5: 7a4e8793e9ce1838185d3dd4c07c8af6
GPU Clock Nibbles ROM Default (3D @ 320MHz / 2D @ 228MHz): http://tinyw.in/ULPG
MD5: 25e2e0a436e402ee305e18e051c21245
GPU Clock Insanity (3D @ 320 / 2D @ 266MHz): http://tinyw.in/u0Rx
MD5: 5e1534efc1b410411123a363ade0507c
* This isn't stable, I only published this because I got bored. Your phone will likely piss fire and crash after you flash this. But, it's fun.
Click to expand...
Click to collapse
A brief guide on how to include this in your own CM10 ROM.
Add the following to your local_manifest.xml:
<project name="carvsdriver/msm8660-common_nibbles" path="kernel/samsung/msm8660-common" remote="github" revision="jb-nibbles" />
<project name="carvsdriver/vendor_nibbles-kernel" path="vendor/nibbles-kernel" remote="github" revision="master" />
Next, you'll need to update your cm.mk file with this:
$(call inherit-product, vendor/nibbles-kernel/nibbles-kernel.mk)
Github: https://github.com/carvsdriver
Click to expand...
Click to collapse
Special Thanks:
thomas.raines & Team Fah-Q for the original LZ kernel, answering tons of my questions and for being a good guy in general.
Team ROOK for being awesome
Team Cyanogenmod for CM10
m4570d0n
Stuff in the works:
Revamped GPU clocks... I found that 3D @ 320 / 2D @ 228 seems to work pretty well and has a relatively good balance. The 2D GPU doesn't like being clocked beyond 228 at all.
Some governor work - likely will remove ondemand and conservative since they're effectively pointless with the other governors present.
And anything else I feel like screwing with ...
First!!!!!! Oh yes I'm cool. Pffft bwahahahaha looks good enough to flash. Will report later
Just flashed the moderate gpu oc version on Slim Bean. Very fast and smooth with smartassv2/sio and 1.62ghz oc. Thanks for all you do, sir.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
best kernel so far . the only reason i didn't switch to tw ROM. interactiveX and smart V2 are the best two
Been on this kernel for a while, just finally made the decision to uv - 50mv on every clock speed, no stability problems so far, gotta say I'm really liking how my phone feels running this kernel though
Sent from my Nexus 7 using XDA Premium HD app
bearclaw7380 said:
First!!!!!! Oh yes I'm cool. Pffft bwahahahaha looks good enough to flash. Will report later
Click to expand...
Click to collapse
I use this kernel on blinky, it's a good kernel!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
car vs driver said:
First boot may be slow as zipalign and sqlite tweaks run for the first time.
Installation will wipe cache and dalvik.
Special Thanks:
thomas.raines for the original LZ kernel, answering tons of my questions and for being a good guy in general.
Team ROOK
Click to expand...
Click to collapse
Nice work. The wipes in the updater script is a great.
Since this is based off of LZ did you keep the voltages that Thomas was using(-50) or did you return them to stock? Just wanna know what I'm really UVing by.
hechoen said:
Nice work. The wipes in the updater script is a great.
Since this is based off of LZ did you keep the voltages that Thomas was using(-50) or did you return them to stock? Just wanna know what I'm really UVing by.
Click to expand...
Click to collapse
They were stock when I started uving it.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
They were stock when I started uving it.
Click to expand...
Click to collapse
That's the thing. I can't find a stock voltage table. I looked in Faux old kernel thread and he has a voltage table but I don't know whether it's for the base of his kernel or stock values. Of course system tuner won't let you check until you have a kernel flashed that allows user defined voltage. So if the DEV already dropped the stock values that's what you'll see. Anyone know the stock voltages? Or an app that let's you check stock voltage?
hechoen said:
That's the thing. I can't find a stock voltage table. I looked in Faux old kernel thread and he has a voltage table but I don't know whether it's for the base of his kernel or stock values. Of course system tuner won't let you check until you have a kernel flashed that allows user defined voltage. So if the DEV already dropped the stock values that's what you'll see. Anyone know the stock voltages? Or an app that let's you check stock voltage?
Click to expand...
Click to collapse
I remember the first few off the top of my head so I know it was stock.
You can use a terminal emulator to check them.
Faux used stock values
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
I use this kernel on blinky, it's a good kernel!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
+1
Using this kernel on my CM10 and it is very good.
Thanks CvD!
Sent from my SAMSUNG-SGH-I727 using xda premium
Great work! Smooth and quick! I am beginning to think that the problem I have with incorporating this kernel into my PACman ROM has to do with this building smoothly with CM ROMs. I realize that PAC has CM in it, but for some reason, the build does not compile Nibbles or LZ in the process, no matter what I do. Somewhere in the process, it reverts back to CM stock. I've altered dependancies and everything else, and always the same result. But, I digress. You are putting out top-notch work and everyone appreciates it! Be cool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wish we could use a custom kernel on the un-official Miui Android rom port for the Skyrocket.
having amazing results with my -50 uv everywhere so far, completely stable, ondemand/sio/1.51or1.72Ghz everything is smooth as can be thanks, gonna start experimenting with a bit more uv and other governors and comparing performance/battery life
JimmyD_92 said:
Just flashed the moderate gpu oc version on Slim Bean. Very fast and smooth with smartassv2/sio and 1.62ghz oc. Thanks for all you do, sir.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
So this will work on jb roms?
Edit: I meant touchwiz but read op and figured it out. Sorry for wasting space.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
smoeki said:
So this will work on jb roms?
Edit: I meant touchwiz but read op and figured it out. Sorry for wasting space.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Not for tw.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
This kernel is amazing. Performance is great with moderate gpu oc, 1.62 oc interactive/noop, and -25mV. Battery life is as good or better than the stock Slim kernel. Thanks again CvD!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Added a new version, the Nibbles v1.6 default GPU 320/228. Enjoy!
car vs driver said:
Added a new version, the Nibbles v1.6 default GPU 320/228. Enjoy!
Click to expand...
Click to collapse
using the stock gpu clock version, besides frequency changes any new code commits or governor/scheduler changes ?
Hello everyone!
First of all, let me say that customizing the kernel requires a custom kernel! Second, it requires an app if you are on the stock ROM - NoFrills, SetCPU, ROM Toolbox Lite - they all have the ability to change voltages, clock speeds, I/O schedulers, and governors. If these words are unfamiliar, please keep reading!
I would like to use this thread as a Q&A about kernels, the options provided with custom kernels, and how they can help (or hinder!) your device.
If you would like to download a custom kernel, see my thread in the original android dev section. Kernels for stock ROM's or CyanogenROM are available in that thread. Currently the kernels for CM are testing well on Carbon.
In addition, pir8man's post is a great guide on how-to get the most out of your kernel tweaking experience .
Please let me know how I can improve this thread. Thanks!!
Governors
So far I have added a few governors, and I am planning to add more.
A governor in the kernel is used to adjust the clock speed in response to load. This can affect battery life, and performance - depending on what you choose.
Want more information? This thread has a TON of information on kernel governors.
I/O Schedulers
First, I am going to bring the I/O schedulers up to speed with the CM kernel - as it already had additional I/O schedulers over the stock kernel.
The I/O scheduler is just like it sounds - simply, it schedules how input and output is queued throughout the system.
If you want more information on schedulers, see this Wikipedia article. In addition, here is a great post from another forum member.
Custom Voltages
Right off the bat, people were asking for custom volting - I didn't realize this was not available, but I have enabled the ability since v0.14.
In tinkering with voltages, it seemed lockups were all over. So I started looking around, and I stumbled across a great post:
FYI, my dmesg said 'nominal', but take it with a grain of salt... you might want to check your processor before using these tables. Note - if you get a failure on GREP, then you probably don't have busybox tools installed. Please find it on the Play Store, thanks.
x714x said:
Your cpu is probaly a "slow" pvs. Flash leankernel then in a terminal do ...
Code:
su
dmesg | grep ACPU
This will tell you what type you have and where you can start off on undervolting.
Per imoseyon....
imoseyon said:
Here are the recommended starting point voltages (kernel default) for each PVS type. Format: frequency (in Khz),voltage (in kV).
Code:
SLOW
Code:
384000,950000
486000,975000
594000,1000000
702000,1025000
810000,1075000
918000,1100000
1026000,1125000
1134000,1175000
1242000,1200000
1350000,1225000
1458000,1237500
1512000,1250000
1620000,1250000
1720000,1275000
1809000,1300000
1900000,1325000
Code:
Nominal
Code:
384000,900000
486000,925000
594000,950000
702000,975000
810000,1025000
918000,1050000
1026000,1075000
1134000,1125000
1242000,1150000
1350000,1175000
1458000,1187500
1512000,1200000
1620000,1200000
1720000,1250000
1809000,1250000
1900000,1300000
Code:
FAST
Code:
384000,850000
486000,875000
594000,900000
702000,925000
810000,975000
918000,1000000
1026000,1025000
1134000,1075000
1242000,1100000
1350000,1125000
1458000,1137500
1512000,1150000
1620000,1200000
1720000,1250000
1809000,1250000
1900000,1300000
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Running Jelly Bean along with newest kernel. Max is 1.026, min is 96, smartass v2 and deadline. Smooth as can be and battery life is great. I am a heavy user (phone calls, 2 emails updating every 15min, lots of texts and even navigation). Thanks again Arrrgh, although you did take my user name. I toast a shot of rum to you
Sent from my XT897 using xda app-developers app
Aaargh! said:
Running Jelly Bean along with newest kernel. Max is 1.026, min is 96, smartass v2 and deadline. Smooth as can be and battery life is great. I am a heavy user (phone calls, 2 emails updating every 15min, lots of texts and even navigation). Thanks again Arrrgh, although you did take my user name. I toast a shot of rum to you
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Yea, but I had it first
Glad you like it! I'm going to try and finish up adding schedulers to the stock kernel to bring it on par with the current CM kernel. Then there's a few more governors I heard about, and then...? Perhaps I'll take another crack at overclocking - the 8960 should be able to do 2.1ghz.
Thanks for the post arrrgghh! Running the terminal command, my phone also returned 'nominal.' I've been running the corresponding baseline settings all day without a hiccup. Next up I'll try to ease them down a bit. I think my problem before was getting too aggressive with undervolting the upper frequencies. Can't say I've got enough use to comment on battery life, but the phone seems to be running cooler. :thumbup:
I ran the terminal command and got like a bazillion lines displayed. Is that normal or did I do it wrong? If that is normal, is there an easy way to find the cpu type?
Edit: Disregard ... I think its cuz of the kernel I'm on since I'm still on ICS. I reverted because there's a few apps I use that haven't been updated for JB yet. I'll definitely come back to this once undervolting is an option for me.
sixxt9 said:
I ran the terminal command and got like a bazillion lines displayed. Is that normal or did I do it wrong? If that is normal, is there an easy way to find the cpu type?
Edit: Disregard ... I think its cuz of the kernel I'm on since I'm still on ICS. I reverted because there's a few apps I use that haven't been updated for JB yet. I'll definitely come back to this once undervolting is an option for me.
Click to expand...
Click to collapse
Did you use the GREP command on the end?
Pipe ( | ) is a very powerful character in the command line, it redirects output to another program basically. So GREP will find all instances of 'ACPU' so you won't have a bazillion lines .
But yes, I would need to update the ICS version of my kernel in order for you to be able to undervolt on ICS...
arrrghhh said:
Did you use the GREP command on the end?
Pipe ( | ) is a very powerful character in the command line, it redirects output to another program basically. So GREP will find all instances of 'ACPU' so you won't have a bazillion lines .
But yes, I would need to update the ICS version of my kernel in order for you to be able to undervolt on ICS...
Click to expand...
Click to collapse
I'm assuming I mis-typed something somehow. Just tried it again and it displayed...
Code:
grep: no such tool
write: Broken pipe
Not quite sure what that's about. Running ASA-14 with v.10 of your kernel.
sixxt9 said:
I'm assuming I mis-typed something somehow. Just tried it again and it displayed...
Code:
grep: no such tool
write: Broken pipe
Not quite sure what that's about. Running ASA-14 with v.10 of your kernel.
Click to expand...
Click to collapse
Huh, perhaps you don't have busybox installed? (It usually "comes with" root...)
Not sure why else you would get that error.
arrrghhh said:
Huh, perhaps you don't have busybox installed? (It usually "comes with" root...)
Not sure why else you would get that error.
Click to expand...
Click to collapse
Hmm ... I don't remember ever installing busybox. I unlocked bootloader, flashed custom recovery and flashed SuperSU and that's more or less all I've done from a rooting standpoint. I'll see about installing busybox and see if that makes a difference. I wanna have a good idea of what I'm working with so once I finally make the jump to JB I can hit the ground running. I'll post up my results shortly.
EDIT: No dice ... confirmed I have busybox installed. Even reinstalled it, but same error code. I wonder if it's due to this kernel version not supporting undervolting? I have no idea ...
Not having grep is usually the symptom of the lack of busybox... why don't you try installing it again, and reboot. ACPU did come up after reboot in my case.
Mine was 'FAST'...
I'll give it a shot and see what I can come up with. Does busybox need to be installed in ..../bin or ..../xbin? Or does it matter? Also ... what version of busybox are you running?
HI I tried it on CM10.1 but did not get any lines from grep.
sixxt9 said:
I'll give it a shot and see what I can come up with. Does busybox need to be installed in ..../bin or ..../xbin? Or does it matter? Also ... what version of busybox are you running?
Click to expand...
Click to collapse
I just found one from Play market, and let it install them for me...
Yeah I confirmed I have busybox installed and everything. Tried both install locations and still nothing from grep. I'm thinking sincethe kernel I'm running doesn't support undervolting that's why I don't get any results. No worries. Once I can officially move to JB, I'll try again and go from there. Not unless arrrghhh wants to make another ASA-14 version of the kernel with all of the 0.18 changes. No rush from me either way.
sixxt9 said:
Yeah I confirmed I have busybox installed and everything. Tried both install locations and still nothing from grep. I'm thinking sincethe kernel I'm running doesn't support undervolting that's why I don't get any results. No worries. Once I can officially move to JB, I'll try again and go from there. Not unless arrrghhh wants to make another ASA-14 version of the kernel with all of the 0.18 changes. No rush from me either way.
Click to expand...
Click to collapse
I don't see any reason to, why would anyone stay on ICS? There's JB now
As for why grep isn't working, not sure. You can always just run the dmesg command, redirect it to a file, then search that file.
Any hint/ why i wont get any lines from grep?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
arrrghhh said:
I don't see any reason to, why would anyone stay on ICS? There's JB now
Click to expand...
Click to collapse
I have a couple apps that I use that haven't been updated for JB yet. All the ones similar to them I just don't like. So I'm just willing to wait until that gets updated or until I have time to learn how to code and update it myself.
EDIT: btw ... the main developer for one of the apps in question is in the military currently overseas and won't be back til the fall. That's the main reason I'm in no hurry. We'll hopefully have a fully functioning 10.1 by then lol
What happens when you combine mind-blowing speed and talent?
You get VANIR, b*itches.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
-Halo 2.0
-Android 4.3 (JSS15Q)
-PIE
-AppBar
-Freaking insane speed
-Custom toolchains, -O3, OptiPNG, bionic, krait, and dalvik performance commits, -fstrict-aliasing, custom CFLAGS, and MORE!
-A Vanir performance on/off toggle
-UI mode switcher
-Tablet statusbar split
-etc (But seriously, this frickin' thing is PACKED with features).
Screenshots
Download:
You can get the latest builds from HERE
Gapps are available HERE
Vanirs GitHub:
https://www.github.com/VanirAOSP
--
Vanirs Gerrit code review:
http://vaniraosp.goo.im/
Thanks:
Team Vanir @papi92 for Droid-Hive
Google
GitHub
PA
Carbon
PeterAlfonso
CM
AOKP
TeamBAKED
GPL
https://github.com/CyanogenMod/android_kernel_bn_omap
So, from this announcement, are we to assume that they finally got it to work on the HD/+? I know that for a while now, we've been told that it wouldn't boot and that they are working on it. Should we take take this announcement as evidence that it is now working?
Just curious, cause I'm lazy and don't want to flash it if it won't work.
Thanks for confirming.
Sent from my Nook HD+ with unofficial Slimbean on emmc using Tapatalk 4
Tried it this morning, no go, I get a dark screen at reboot and nothing else. I did a full wipe as usual. Going back to Carbon.
GenghisKhan67 said:
Tried it this morning, no go, I get a dark screen at reboot and nothing else. I did a full wipe as usual. Going back to Carbon.
Click to expand...
Click to collapse
Working on it =)
nolinuxnoparty said:
Working on it =)
Click to expand...
Click to collapse
I initially spoke with Prime Directive when I saw the first build for Ovation by nuclearmistake and informed him that it wouldn't boot past the bootloader. He told me to get in touch with DHO and DHO said he was working on it.
Anyway, I notice that the builds you have linked are from nuclearmistake and not DHO. So, going forward, which builds will we see and are you going to be the maintainer for this device?
Looking forward to getting this going, as it's an awesome rom on my N7 grouper.
Thanks,
Mike T
Going to look further into it after work, can't get far enough for adb to recognize the device though.
Sent from my Galaxy Nexus using xda premium
killersloth said:
Going to look further into it after work, can't get far enough for adb to recognize the device though.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same for me, DHO asked me to get him a logcat but being unable to get past bootloader prevented device from being recognized. I hope you can get further. Btw, just for the heck of it, I tried substituting the boot image from CM 10.2, Carbon 4.3 and your Slim rom but it still failed to boot.
Although I figured that the boot image was the same( same filesize) for those 3 roms, I tried all 3 anyway.
Mike T
i got the same black screen also. hope to see it running, sounds interesting.
@killersloth: Lemme know if you can fix it
Still nothing? Or has this been working and I just never heard about it yet?
Sent from my Nook HD+ with unofficial Slimbean on emmc using Tapatalk 4
I have been using the Vanir rom on my GS3 for a couple days and I love the speed and smoothness. I look forward to using this on my Nook HD if it gets working. Any updates?
natefish said:
I have been using the Vanir rom on my GS3 for a couple days and I love the speed and smoothness. I look forward to using this on my Nook HD if it gets working. Any updates?
Click to expand...
Click to collapse
Here is an unofficial build I did that boots up fine:
vanir_ovation-UNOFFICIAL-20131023.zip - 151.04 MB
However, the ROM is very glitchy on our devices. In addition to the usual rotation bugs (and the Wi-Fi bugs introduced by a recent CM commit), there seems to be a whole new batch of graphical issues.
If anyone wants to start bug fixing this, you can PM me for some suggestions on how to resolve some of the typical problems our devices have.
If you want to build this yourself, you only need to replace Vanir's proprietary vendor repo with the proper one from TheMuppets, like so (this is pulling from my fork on github):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github_kimjisoo"
fetch="git://github.com/kimjisoo" />
<remove-project name="vendor_bn" />
<project path="vendor/bn" name="proprietary_vendor_bn" remote="github_kimjisoo" revision="cm-10.2" />
</manifest>
Vanir's build system is a little odd, and took me a few tries to figure out. Basically, you need to run "make -j# otapackage" after lunch, or it doesn't give you a flashable zip. There was no brunch option...
How's the lag compared to other available ROMs? Thanks!
YevOmega said:
How's the lag compared to other available ROMs? Thanks!
Click to expand...
Click to collapse
I wouldn't be worried about lags, as the only bootable version of this rom is the unofficial one posted one post above yours by jisoo. LOL It's very glitchy and quite unusable, also with the OP nolinuxparty's account currently disabled, I don't think we'll see anything too soon from Vanir...if ever.
Mike T
webdroidmt said:
I wouldn't be worried about lags, as the only bootable version of this rom is the unofficial one posted one post above yours by jisoo. LOL It's very glitchy and quite unusable, also with the OP nolinuxparty's account currently disabled, I don't think we'll see anything too soon from Vanir...if ever.
Mike T
Click to expand...
Click to collapse
Ok Thanks.
nolinuxnoparty said:
Download:
You can get the latest builds from HERE
Click to expand...
Click to collapse
Current link:
http://www.vanir.co/nuclearmistake/VanirAOSPRelease/ovation/
Check the Development thread here:
http://forum.xda-developers.com/showthread.php?t=2792697
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice. I'd put it on mine, but my mother-in-law is now using it. She likes it on stock GB.
sent from the frost god
Just an update:
One flash from BML is now working, so if you have a stock rooted KJ6 with CMW5 on your SGS4G, you only need to flash the ROM zip once for it to install.
I'm using TWRP 2.6.3.0 in the builds, although I guess I can release a CWW version of the boot.img too.
Huge thanks to @sunsurfer42 (for the two (2) dev phones he sent me) and @daothanhduy1996 (for his source trees) for making this happen.
Hang tight, I'll have a public release soon. PM me for testing.
Wow this mammoth is bigger then beanstalk. I like it. I really like it. I wanna know how u were able to build it. Should move it to dev section soon for others to feast on. Two thumbs way up!!
I flashed straight from bs too. Fyi
Sent from my SGH-T959V using XDA Free mobile app
This is great...thanks for continuing to work on this phone. Just out of curiosity, what differences from Beanstalk can we expect?
CM11 is its own beast.
Just some features, these are not necessarily different from beanstalk since both roms use very similar source trees
Android 4.4.3 (released just a few days ago)
You can flash directly from BML
TWRP 2.6.3.0
* You can now do backups of EFS directly in the TWRP interface. These get made by default when you do a regular backup.
Compiled with Linaro 4.7
All source code will be easily available so you can do your own build
GPS, bluetooth (I have only tested file transfers), video playback, camcorder, camera
Luckily for us, with the 4.4.3 release the CM team made sure that their rom would run great on devices with only 512 mb of RAM (like ours). So this should feel fairly smooth.
Somewhere down the line I'm gonna release a trimmed rom that has removed apps (like wallpapers) that aren't necessary to keep the ROM working but I have a lot of other plans before this.
WHOA IS THAT A DOWNLOAD LINK?
https://www.fernandob.com/files/android/sgs4g/cm11/cm-11-20140610-UNOFFICIAL-galaxys4gmtd.zip
You should install minimal GAPPS to go wit that ROM:
http://www.androidfilehost.com/?fid=23501681358541495
FBis251 said:
CM11 is its own beast.
Just some features, these are not necessarily different from beanstalk since both roms use very similar source trees
Android 4.4.3 (released just a few days ago)
You can flash directly from BML
TWRP 2.6.3.0....
Click to expand...
Click to collapse
Thanks a lot for this. I'll download and test as soon as I can.
I'm not gonna post the manifest file until I've done some more testing, but if you're too impatient to get a build going, follow the vibrant cm11 from source guide here:
http://wiki.cyanogenmod.org/w/Build_for_vibrantmtd
Complete the guide until you do the "Initialize the CyanogenMod source repository" part.
You're gonna then need to add the team acid local manifest file:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Use JustArchi's Linaro compiler branches -->
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" name="JustArchi/Linaro" revision="4.7-androideabi" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" name="JustArchi/Linaro" revision="4.8-androideabi" />
<!-- Use TWRP as the recovery -->
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="TeamWin/Team-Win-Recovery-Project" revision="twrp2.7" />
<!-- Use Cyanogenmod's Aries and Samsung hardware common files -->
<project name="CyanogenMod/android_device_samsung_aries-common" path="device/samsung/aries-common" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<!-- SGS4G Specific Edits -->
<project path="device/samsung/galaxys4gmtd" name="teamacid/android_device_samsung_galaxys4gmtd" remote="github" revision="cm-11.0"
<project path="vendor/samsung" name="teamacid/proprietary_vendor_samsung" remote="github" revision="cm-11.0" />
<project path="kernel/samsung/aries" name="teamacid/niltmt_kernel" remote="github" revision="cm-11.0" />
</manifest>
Do these steps to get it working (from the root of the source tree)
Code:
mkdir -p .repo/local_manifests/
editor .repo/local_manifests/teamacid.xml
Paste in the manifest xml from above and save the file
Then do another repo sync
Continue the guide but replace all the steps that say vibrantmtd with galaxys4gmtd
You SHOULD get a working cm11 zip in an hour or two on a fast computer.
Any mirrors?
The Link says:
An error occurred during download. Please try again.
Details:
An error occurred while creating security connection to www.fernandob.com.
Awesome FB, so very much appreciated. If you had not run across it yet, it seems Development Settings in the Settings menu is borked. Anyone else getting a FC when you attempt to open? Advanced Settings FCs too under Settings -> Display & Light -> Advanced Settings
DerPuGNa said:
Any mirrors?
The Link says:
An error occurred during download. Please try again.
Details:
An error occurred while creating security connection to www.fernandob.com.
Click to expand...
Click to collapse
What are you using to download the file? If you're using a fairly recent browser (like firefox) you won't have any problems.
I have disabled a lot of ciphers on my site's SSL config. I think I may just make a subdomain with no SSL to host the files to prevent this though. Hang tight I'll have some links that will work for everyone soon.
For now a recent version of Android with a recent browser (chrome, naked browser, firefox) will let you download it straight to your phone.
FBis251 said:
What are you using to download the file? If you're using a fairly recent browser (like firefox) you won't have any problems.
I have disabled a lot of ciphers on my site's SSL config. I think I may just make a subdomain with no SSL to host the files to prevent this though. Hang tight I'll have some links that will work for everyone soon.
For now a recent version of Android with a recent browser (chrome, naked browser, firefox) will let you download it straight to your phone.
Click to expand...
Click to collapse
IDM sir, uhm, so i disable this first and try to DL it via web later, Thanks anyway.:highfive:
DerPuGNa said:
IDM sir, uhm, so i disable this first and try to DL it via web later, Thanks anyway.:highfive:
Click to expand...
Click to collapse
Hmmm, that's weird coz I did always download w IDM from fernandob w/o any problem tho :/ have u updated it or so (even tho I haven't updated it for ages but it might help somehow I guess )
Anw, glad to be #UNITED (@acid-ers)
Sent from my GT-I9300 using Tapatalk
daothanhduy1996 said:
Hmmm, that's weird coz I did always download w IDM from fernandob w/o any problem tho :/ have u updated it or so (even tho I haven't updated it for ages but it might help somehow I guess )
Anw, glad to be #UNITED (@acid-ers)
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I made a new domain name (http://files.fernandob.com/) that will contain all the files without using SSL.
Whatever she was trying to download it with didn't like the ciphers my web server had available so she got that error. Anyway the new domain doesn't use SSL.
works better than every rom ive used before this besides F4k, which it equals performance/smoothness wise. even for some retarded games i play lol. good frikin job dude. made this account just to tell you that. but was an avid visitor previously
Finaly Thank You For Porting CM 11.0 For This Incredible Device
FBis251 said:
Click to expand...
Click to collapse
Thanks man to porting this awesome rom, finaly i have cm 11.0 on my device and really is a great rom with cm 11 m7 branch
i loved, thanks and sorry for my bad english :good:
FBis251 said:
I made a new domain name (http://files.fernandob.com/) that will contain all the files without using SSL.
Whatever she was trying to download it with didn't like the ciphers my web server had available so she got that error. Anyway the new domain doesn't use SSL.
Click to expand...
Click to collapse
HE*
hi buddy, this rom is amazing and works great but I think grace was gone when you remove the cyanogenmod native apps in the build 20140612-UNOFFICIAL-galaxys4gmtd, about performance is so perfect, but please add back the cyanogenmod native apps because this is not cyanogenmod without original apps in another i will back to the bored and slow slimsaber rom :'(
DerPuGNa said:
HE*
Click to expand...
Click to collapse
Your icon and username are misleading
Mafworld said:
hi buddy, this rom is amazing and works great but I think grace was gone when you remove the cyanogenmod native apps in the build 20140612-UNOFFICIAL-galaxys4gmtd, about performance is so perfect, but please add back the cyanogenmod native apps because this is not cyanogenmod without original apps in another i will back to the bored and slow slimsaber rom :'(
Click to expand...
Click to collapse
I don't plan on putting them back. I'll probably make a separate zip file with them but I believe they're not essential for the rom to function.
As a temporary work around flash the first zip that's available from the downloads page, then flash the latest version, that way you get the apps that would've been missing.
Just to make sure...
Currently on Beanstalk 4.4.2...I'm assuming I can do full wipes, then flash with TWRP. Don't need to go back to GB and start over, right?