1. DroidForums.net is currently undergoing a major software upgrade. If you are experiencing any problems logging in please: Contact Us

[KERNEL] UPDATE Blazed Release v2.2.3 UnderVoltOC1.2GHz & BLN - Eclair 2.6.29.6 Beta

Discussion in 'Samsung Fascinate Development' started by TAPOUT27, Jan 14, 2011.

  1. TAPOUT27
    Offline

    TAPOUT27 New Member

    Joined:
    Feb 3, 2010
    Messages:
    2,368
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    BRENTWOOD, TN
    All credit goes to SirGatez over at XDA...I'm just reposting this here so more people can mod and enjoy their Fascinate...

    Here's the link to the original post at XDA: [KERNEL] UPDATE Blazed Release v2.2.3 UnderVoltOC1.2GHz & BLN - Eclair 2.6.29.6 Beta - xda-developers

    [​IMG] [KERNEL] UPDATE Blazed Release v2.2.3 UnderVoltOC1.2GHz & BLN - Eclair 2.6.29.6 Beta
    About a month ago some of you may remember my posts that I was working on a kernel. Here is my first public release. The whole thing works at about 95% or so.

    ==============

    The advantages I notice while using it besides the normal issues associated with Eclair are as follows:

    1. Memory management has changed (has good and bad effects) Good: when you fly through 45 websites the browser does not crash as it eats memory. Bad: when you blow through 45 websites the browser will hang (easy fix hit home, and use app killer to free memory from apps you are not using) (Personally I like not losing my place as I get lost in the web, it also will prevent apps from dieing in the background when you are using multiple apps at the same time, if memory gets low enough the OS WILL KILL the offending apps). I personally found Eclair for Fascinate to handle memory available worse than this kernel, and I find this kernel handles memory more like Eclair on the Moto Droid did, and the Moto Droid had far less memory to work with.

    2. UI has a faster response vs stock kernels, the kernel is also running AS scheduling vs BFQ but I updated BFQ to run as well if you want to revert.

    3. Internet Connectivity appears to be faster with those apps that properly use the API. Web browsing, CheezeBurger, youtube etc all load content faster (efficiently? / Maybe related to memory management?)

    ==============

    Issues to fix (ToDo List, I am working to fix these issues):

    1. Camera sometimes FCs, appears to work 4/5 of the time. [Confirmed - Reproducibility varies]

    2. Camera FCs on zoom [Confirmed]

    3. Camcorder FCs when you press record with 720P as format [Confirmed]

    4. FIXED Bluetooth Driver not loading/working. If you are still having any Bluetooth issues please post in this thread, Thanks!

    5. Windows drivers do not recognize the phone, works fine under Ubuntu [Confirmed]

    6. Internet connectivity issues (only certain internet applications have issues, some of which appear in other roms) Known internet issues are Sparse RSS will load only the first three feeds and croak on net connectivity, killing and reloading Sparse RSS appears to resolve the issue. Also Orbot (TOR) sometimes dies mid transmission and requires OS restart to fix. [Possibly Application Related, will investigate]

    ==============

    For those doubting, this IS 2.6.29.6, I personally merged the code myself, IT IS NOT 100% COMPLETE. Some drivers still need merging, and the V4L2 code is not completely converted because Fascinate uses different (updated?) V4L code (compare Fascinate's Eclair to Eclair on AOSP)

    If anyone wants to help bug hunt I will forever be grateful. I would like to finish squashing bugs in this in the next 2 weeks as I really want to attempt to work on a Froyo for Fascinate. Even if it uses Eclair code to run the only RIL code we have.

    I also semi-blindly fixed about 50-100 coding problems in the Eclair Kernel, varied from not returning data from a function that should have, simple void definitions that were returning when they had no data to return and no function collected it. Correcting order of operations in if statements. Declaring data types that were vague (unsigned vs signed). You will notice it compiles a lot cleaner...attempting to fix the camera code nearly kills the camera completely, I am thinking the broken code dumps variables by accident that the corrected code does not.

    Attached is a working kernel, it will have issues using DI01 (such as no vibrations), it works great with DJ05 ROMS and maybe DL09 system roms. At this time I can not recommend a DL09 system rom with this kernel, during my initial tests it appears to drop GPS and cell data connectivity frequently resulting in having to relock on GPS satillites, and losing data connections in networked applications.

    I highly recommend the setup I am running, DL09 Radio, Son Of Skywalker Blackhole v2.4 and this kernel (if you can handle the few bugs that is, it is beta).

    Please feel free to post bug reports please include detailed information about the issues, I AM NOT FIXING APP PROBLEMS. Please remember to only report kernel issues and information specific to the kernel crash. If an app crashes on other kernels and not just this one please do not submit a report. This kernel is NOT setup for debug info, I will post one setup with debug turned on later. Right now, play around with it and report your results! Enjoy and have a great time :-D

    GITHUB: https://github.com/sirgatez/


    Edit 1: I thought I would mention that I originally started with the JT1134 kernel source from late Nov. - mid Dec. and the Samsung Fascinate stock source (from Samsung's Opensource website) then I merged in source from 2.6.29.6 from www.kernel.org and from Cyanogen's 2.6.29.6 Eclair kernel. I stopped on 2.6.29.6 instead of moving higher because of 1 reason, once you step in to 2.6.30 there are major driver changes requiring a lot of double verification and back trekking....In a few words, it is lots and lots of work, and I think that jumping from 2.6.29 to 2.6.29.6 will help transition to the 2.6.30 (Froyo?) series of kernels because then the majority of the work is in restructuring the driver code (which would likely best be done backwards, from the system .h files, to the .c handlers, down to the device drivers) from Samsung to match that in the stock 2.6.30 set. Complexity will be reduced by a measurable amount :)

    Notes 1: Samsung's Android code has some significant differences under the hood from AOSP Android code, I have not sorted it all out yet, but it is possible that without an AOSP stock system that a full kernel update to the current AOSP code may not be possible. There is a built in virtual CD driver for what appears to be hosting the ISO built into the base Samsung system image, I have not opened the image yet but it appears to perhaps be drivers? Also it does not sleep the SD card like standard AOSP does, attempts to do so will disable the SD card from use with no ability to remount without a battery pull. (This is in 3 of 4 lines of code that AOSP had that must be commented out from the Samsung kernel for this SD issue to be prevented). For those wanting it, CIFS and NFS are compiled modules in this kernel. The current kernel is not over-clocked, and does not have voodoo. It does support both with a kernel configuration edit required for voodoo with the proper init scripts, and over-clocking requires changing just a few files and recompiling, I did neither as I wanted a true comparison to compare changes against the original stock kernel. The kernel does have the BLN notification code built in. BLN, Voodoo, and Over-clocking code are not my own creation they are pulled from their respective creators.

    Original Release Download [ REMOVED ]

    Update 2:

    I updated the DI01 initramfs I was using, added to DJ05 (update init & adb binaries). I also imported a few of geeknikbrians config options, important are those related to memory management. From geeknik's config file https://github.com/geeknikbrian/Stup...odoo_defconfig [USER_SCHED/PROFILING/THUMBEE/L2_PLE/CONFIG_HZ=300/IPV6 options/Netfilters DCCP-SCTP-SANE/RFKILL_PM/PMEM Drops/Video MEM Drops UACCESS w/MEMCPY/KSM/PREMPT_VOL] I also fixed the bluetooth issue, it appears to have be related to an fix I did to RFCOMM (I can pair and connect with my computer but not sure on headsets as I don't have one with me). Also tunneling support was added, if you have a VPN to try it on please report if it works or not.

    As a result of the above changes the most recent version feels even faster. Please report any new unusual issues not already on the above list. I will be playing with this for a few days. Remember this is beta [It's got issues *Wink*] So it's likely to drop you like a hot prom date but everything has been running great for me on the last update for over 2 weeks I don't imagine a major change in attitude over this small update.

    For those waiting, I will post an OC version of this release by sometime Monday. Followed by a voodoo version for those you who just gotta have it (I just need to checkout and merge the latest voodoo files/patches to include into this thing).

    What do you think about the name Blazed for this kernel? Everyone's reaction since my first release is that is feels fast...

    FINAL NOTE: Please disable voodoo before using this kernel

    also...even if you think it feels like it These kernels are not Over-Clocked...Just Optimized :)
    Edit: Most recent v2.2 has OC @ 1200Mhz.

    Update v2.2: This is a half update, still having issues with ADB on windows, thought I almost had it and in a fit of insomnia I slipped up and reverted what might have worked, work moves on however. BLN is now properly supported and this kernel boots with 1200Mhz overclock so use setcpu to cut it back if thats too much for you...it will eat battery faster at 1200. I will continue my work on fixing the windows ADB/SD issues and integrating voodoo as my next goal. If you have issues with FC remember to fix permissions and as last resort clear your cache/dalvik cache, I had some issues at one point with all this dev testing and clearing my caches and fixing permissions resolved them all. [ REMOVED ] Due to battery not charging bug.

    Update v2.2.1: Bugfix, charging issue fixed (CONFIG_USB_GADGET_VBUS_DRAW=2, Remember not to change to 500, phone thinks it does not need to enable charging...) [ REMOVED ]

    Update v2.2.2: Minor update, changed voltage settings to undervolt processor by 50mv vs stock, seems to run a bit more stable and saves a little juice (double whammy). If 1200 is too much for you use setcpu to cut back the speed after boot. Seems to work fine, still haven't found the magic switch in the kernel for fascinate to set the default profile's max/min speeds during bootup. Also no luck on ADB/SD for windows yet, it's beginning to be a needle in the haystack. Some minor feature updates as well, double check bluetooth again and make sure all is well I tweaked the driver a little, hopefully for the better. This build rides a little on the high end of the spectrum in speed (as did v2.2.1) hence the quicker battery drain. I will be cutting that back to something more reasonable once I have tested it some more, bad settings make the phone think that the battery is invalid for the phone (reminds me of the days when MotoDroid was first getting some hacking). Personal Notes: Battery seems to charge faster on an outlet charger than on a USB port, maybe do to the overclock settings. It definitely charges alot faster when not in use vs being used like a Portable Internet And Media Device. [ REMOVED - Battery Issues ]

    Update v2.2.3: Overclock remains 1.2Ghz with 7 slots. This is a minor update to address the OC1.2Ghz 7 slot kernel not charging properly. The problem was within vzw_auth (thanks for the pointer nemesis2all) routines from /drivers/power/s5_pc110_battery.c, removing these (safety checks) will prevent charging from being stopped. Things vzw_auth looked for were batteries reporting an unknown status, using more or less amperage/voltage than they should (hence why overclocking caused issues), or failing (security?) Firmware / CRC checks. I also cut back the throttle a bit so the phone should ride the mid-low spectrum of speed more often unless under load. Also the device will now boot at 1Ghz, if you want the 1.2Ghz you gotta use setcpu or the shell to make it happen (so it doesn't kill your battery with unneeded speed). Charging may still be a little slow, particularly where I noticed was when charging from USB, but no issues from an outlet charger for me so far. This maybe related to the source output and not to the above issues, reports will be helpful. Please report any other issues you find, Thanks and have fun! Edit: I'm glad we have the battery issue resolved!

    Update 01/14/10: Due to a flake internet connection when I was updating this article earlier today over half of it went missing for part of today, we have Google's all-seeing all-caching servers to thank for this recovery, next time I'll keep a backup ;-)

    If you appreciate Blazed and enjoy using it, please consider making a donation. Thank you for trying it out and have fun!

    Attached Files
    [​IMG] Blazed-ECLAIR-kernel_update-release 1.zip (6.54 MB, 16 views)
    [​IMG] Blazed-ECLAIR-kernel_update-release 2.zip (7.73 MB, 111 views)
    [​IMG] Blazed-ECLAIR-kernel_update-release-2.2.3-UVOC12-BLN.zip (6.74 MB, 79 views)

    He doesn't have a DONATE link posted but if you wanna donate PM him over on XDA...enjoy :)
    Last edited: Jan 15, 2011
Search tags for this page
adb setup (included all adb binaries in zip)
,
android kernel enable bln
,
bln mod kernel
,

kernel 2gz download

,
kernel stock 2.6.29 htc eris
,
verizon galaxy note 2