BACK FROM THE DEAD
This kernel is intended to be stable yet fast. has many goods (OC UV ect.) but yet its main goal is to be stable. THIS KERNEL IS INTENDED FOR USE ON CYANOGENMOD (but if u would like to try on other aosp roms feel free)
i decided to bump my old thread to give testers a place to discuss the kernel and point out possible issues. before its moved into CyanogenMod.
u can get the kernel via Kernel Manager in the android market.
direct link: http://kernels.teamw.in/files.php?fid=565&kid=237
all source can be found on my link in my signature.
thanx for the support and please leave feedback
as of v9:
-edid code and hdmi driver bug fixes
-bump minor version
-config changes
as of v8:
revert edid code that borked audio in HDMI
as of v7:
minor version change, staying up to date with linux stable release
as of v6:
minor version change, keepin us up tEh date
as of v5:
-updated minor version to .5
-misc other changes
as of v4:
-fixed issue in atmel touch driver
-updated usb gadget driver
-add platform data for USB accessory function
-update config
as of v3:
-updated EDID code via tEh #teamwin
-changed config
-fixed light sensor
known issues:
-hdmi audio out not working
-possible bug switching cams (needs tetsing and debugging works for some while some seem to have issues)
faq:
q: does this kernel have SBC?
a: no
q: will this kernel ever have SBC?
a: no
q: kernel manager gives error when updating, what do i do?
a: make sure you have the latest version of the app. if you do, clear the app data and try again
q: after flashing the ladies look at me more, how do i make it stop?
a: flash another kernel
q: can i discuss other kernels in this thread?
a: no... post only posts that are on the topic of this kernel.
q: i cant feel my legs, any way to fix?
a: get off the toilet and stand up naowz
q: what is GoDm0dE?
a: http://forum.xda-developers.com/showpost.php?p=13405012&postcount=204
Awesome! can't wait to try this
we can just flash on top of Fresh right?
want to install now!
guys, it's a source, not a flashable kernel yet. it's for other people to make changes to and improve on at the moment.
justinisyoung said:
guys, it's a source, not a flashable kernel yet. it's for other people to make changes to and improve on at the moment.
Click to expand...
Click to collapse
that's what I thought, but was making sure... thanks
Could we please have epson panel fix (30 fps, touch lag) implemented asap?
Thanks.
great love to see community kernel.
going to be forking soon
TrevE said:
great love to see community kernel.
going to be forking soon
Click to expand...
Click to collapse
thats the spirit welcome aboard lol
once first commit finishes, ill start doing the normal magic. OC,compcacheaand such. ill prolly fork for BFS for now. im gonna try and forward port to .34 here in a bit once i get some of this up
ps first commit is up finally. pull away
yeah prolly best to keep bfs sepearate havent played yet myself but from pokin around on n1 boards read its not too stable but like i said havent touched it myslef.
29 - 34 shoudlnt be too bad, not like 27 - 29 :|
just finishin up a movie then ill fork away thanks ofr getting this goin toast id love to see 1 community kernel instead of 3029849203842093 like the n1 has
TrevE said:
yeah prolly best to keep bfs sepearate havent played yet myself but from pokin around on n1 boards read its not too stable but like i said havent touched it myslef.
29 - 34 shoudlnt be too bad, not like 27 - 29 :|
just finishin up a movie then ill fork away thanks ofr getting this goin toast id love to see 1 community kernel instead of 3029849203842093 like the n1 has
Click to expand...
Click to collapse
Any forking in the movie you are watching? haha -
instead of BFS di like to try playing around with this
http://lwn.net/Articles/352889/
> [...]
> # echo NO_NEW_FAIR_SLEEPERS> /debug/sched_features
>
> Btw., NO_NEW_FAIR_SLEEPERS is something that will turn the scheduler
> into a more classic fair scheduler (like BFS is too).
Click to expand...
Click to collapse
>> (mainline)
>> Averages:
>> ------------------------------
>> Max 50 usec
>> Avg 12 usec
>> Stdev 3 usec
>>
>>
>> (BFS)
>> Averages:
>> ------------------------------
>> Max 474 usec
>> Avg 11 usec
>> Stdev 16 usec
Click to expand...
Click to collapse
In fact, I liked this setting so much that I went to
kernel/sched_features.h of kernel 2.6.30.5 (the kernel I use normally right
now) and set SCHED_FEAT(NEW_FAIR_SLEEPERS, 0) (default is 1) with
absolutely no other tweaks (like sched_latency_ns,
sched_wakeup_granularity_ns, etc.). It pretty much behaves like BFS now
from an interactivity point of view. But I've used it only for about an
hour or so, so I don't know if any ill effects will appear later on.
Click to expand...
Click to collapse
just need to get debugfs enabled.
and no no forking in the movie pandorum on netflix
TrevE said:
instead of BFS di like to try playing around with cfs
http://lwn.net/Articles/352889/
and no no forking in the movie pandorum on netflix
Click to expand...
Click to collapse
may be promising. i did some work with Con the creator of BFS on the HeroC had him look over my dirty backport to .27 and then used his suggestions on my .29 heroC port. i only had like one or two issues that came about from BFS in the end. mostly app related at that. i really never had time to look further into the issues because of other projects and the awesome sauce EVO's arrival. but yeah im gonna go with a fork and work out the bugs. i like the idea behind BFS and feel its best suited for devices like ours. that said... .34 has a major CFS overhaul, which many have said fixes a lot of issues CFS had in previous kernel versions. so getting to .34 and playing around i guess is the goal i have ATM.
ps. look at this lol
http://pastebin.com/h7TQiv5a
htc is some dirty coders lol
probably not the place to ask, but what the heck..
does anyone have any idea why touch input is broken on froyo when using this kernel?
ffolkes said:
probably not the place to ask, but what the heck..
does anyone have any idea why touch input is broken on froyo when using this kernel?
Click to expand...
Click to collapse
oh do i need to fix that? htc prolly destroyed it again. i can look at it here in a bit. i bet i know the issue.
A proper backport of BFS and i really want to test SIO I think the results will be very good.
toastcfh said:
oh do i need to fix that? htc prolly destroyed it again. i can look at it here in a bit. i bet i know the issue.
Click to expand...
Click to collapse
awesome!
What's BFS? I remember always hearing about it on the HTC dream boards but never came across an actual explanation to what it actually is/does
madunix said:
What's BFS? I remember always hearing about it on the HTC dream boards but never came across an actual explanation to what it actually is/does
Click to expand...
Click to collapse
Brain **** Scheduler
madunix said:
What's BFS? I remember always hearing about it on the HTC dream boards but never came across an actual explanation to what it actually is/does
Click to expand...
Click to collapse
It's the Brain F**k Scheduler
http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Related
This is just a thread to offer a consolidated place for update notifications and such for alternative kernels. I will try to keep the most recent versions in this post but you should always check the end of the thread just to make sure.
Consider these experimental, use at your own risk, no ones responsible for anything, blah blah blah.
For best results, always use cyanogenmod roms
Most recent kernels:
pershoots Kernels
http://droidbasement.com/db-blog/
ezterrys kernels
http://forum.xda-developers.com/show...&postcount=670
dumfuqs OC (Requires setting scaling_max_freq in order to boot)
cm-5.0.8
32B/32A
cm-6.0.0
32B
32A
newest (10/14/2010):
2.6.35.7 32A/B (only oc710 so most of you will need to set your max frequency in init.d or whatnot)
archive:
http://www.mediafire.com/?6paej1h9tpkif
dumfuqs github
hey dumfuq, can you create a blog, I like following your work, would be nice to see it all elsewhere. Are you on github?
thanks, your work is appreciated
thx for posting this
Nice to see this here.. It would be nice to further explain, I searched else where but could not find....
I know
OC---IS OVER CLOCKED
UV---IS UNDER VOLTED
FP---????
Not to be rude but this is the third kernel thread on Page 1 of G1 Android Development. Hope a mod consolidates the three into one.
On another note, thanks for your kernels.
dumfuq said:
This is just a thread to offer a consolidated place for update notifications and such for alternative kernels. I will try to keep the most recent versions in this post but you should always check the end of the thread just to make sure.
Consider these experimental, use at your own risk, no ones responsible for anything, blah blah blah.
For best results, always use cyanogenmod roms
Most recent kernels:
pershoots Kernel 2.6.34-OC-UV-FP – Dream/sapphire(32B/A)
http://droidbasement.com/db-blog/?p=538
dumfuqs OC -Dream/Sapphire(32B) (requires setting scaling_max_freq in order to boot)
oc825-cm-2.6.34-8t3-signed.zip
Click to expand...
Click to collapse
with oc825-cm-2.6.34-8t3 im not getting full multitasking, im able to multitask 3-4 apps but the kernel isnt utilizing all the swap before killing processes
I think it's rather nice to have an OC kernel that doesn't require swap though.
just updated with changes from cm-5.0.8-t4
defconoi said:
with oc825-cm-2.6.34-8t3 im not getting full multitasking, im able to multitask 3-4 apps but the kernel isnt utilizing all the swap before killing processes
Click to expand...
Click to collapse
They make it use all the swap, and people complain, they tone it down, and people complain.
Seriously though, adjust swappiness and perhaps use AutoKiller to set the settings LOWER than default. That should keep more apps around. Note that doing that may cause extreme slowness, so if it breaks, you get to keep both parts.
When I fool with those types of settings, I like to disable "set on boot" type options so that a reboot clears them if I screw something up. Then I can tune away till I get what I want, then set them on boot. Of course, just as I figure out how I like it, a new release comes out. owell, I do so love flashing my phone. I feel like I need a .sh file with "adb shell "reboot recovery"" in there on my computer's dock.
new dream/sapphire kernel images posted - http://droidbasement.com/db-blog/?p=546
Any chance on someone uploading the oc xtra v4 with lower frequencies please.. I don't know how to change the userinit or resign =P thank you. Last time with test2 cyanogen, it booted up fine leaving the frequencies on my old settings but now test4 it just won't boot because frequencies got over written this time and set825 which I know why but I don't know how to resign and stuff..
rahuljj said:
Nice to see this here.. It would be nice to further explain, I searched else where but could not find....
I know
OC---IS OVER CLOCKED
UV---IS UNDER VOLTED
FP---????
Click to expand...
Click to collapse
FP = floating point optimized
32a test
I have no way to test this myself but...
It looks like it is fairly trivial to make a 32A port (since cyanogen has already patched the source). So here is a version of my latest that might work on 32A. If you try this, please let me know if it works or not.
Same as my others in that it requires you to set the scaling_max_freq in order to boot.
oc825-32A-cm-2.6.34-8t4-signed.zip
2.6.34 BFS kernel. I found it in the cyanogen forums.
http://www.4shared.com/file/BmZU6db6/BFS508t4.html
I went from 23 to 24 fps on neocore benchmark. Not really that much of an increase but 5% is 5%. I know some people hate BFS with a passion but I like the extra frame=p.
Link to OP
So I tried you kernel (was too lazy to make my own) and everything works (it boots) except the wifi, either due to the fact that I'm running 5.0.7 or the slight possibility that you put the wrong kernel module for wifi because 32A and 32B don't use the same one, will compile my own to see if it's just the kernel module...
rps13 said:
So I tried you kernel (was too lazy to make my own) and everything works (it boots) except the wifi, either due to the fact that I'm running 5.0.7 or the slight possibility that you put the wrong kernel module for wifi because 32A and 32B don't use the same one, will compile my own to see if it's just the kernel module...
Click to expand...
Click to collapse
This might fix the wifi.
yup wifi is fixed, so was it the kernel module?
rps13 said:
yup wifi is fixed, so was it the kernel module?
Click to expand...
Click to collapse
Yup...that wass it. Thanks.
825 isnt stable for me , how about turning out a optimized 710 or 670 build ?
mejorguille said:
2.6.34 BFS kernel. I found it in the cyanogen forums.
http://www.4shared.com/file/BmZU6db6/BFS508t4.html
I went from 23 to 24 fps on neocore benchmark. Not really that much of an increase but 5% is 5%. I know some people hate BFS with a passion but I like the extra frame=p.
Link to OP
Click to expand...
Click to collapse
Why do people dislike BFS? I don't really see much of a reason for the hate (but I also don't really know the difference)
Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food
Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file
You sir are an absolute saint
Thanks so so much
5 STARS!
very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks
How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance
cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod
i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply
Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do
can't wait and i'll try it now
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it
cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...
cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks
thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..
PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.
DEAD
I will try it today and let you know
thank you for the ROM
Sorry for slow download guys! When I finish my build, I upload to ge.tt which allows end users to instantly download while I upload. R3 is also broken -_- ; will upload fixed again
Please stick with r2 atm until r4 is done uploading.
Why the mandatory 96MB Swap and 512MB Ext4?
Wow...this rom is so horribly slow. Amazing how Roms can still get worse.
Slow UI, no improvements over 2.2.1, Market doesn't download anything. No Superuser installed. No busybox installed either. Commands such as a simple "cp" doesn't work.
Horrible.
Honestly with EzTerry's odex'd Asop and Richies F4T 182 de-odex asop build you are a long long long way off lads, nice effort but there is a lot better available already. And as for it being Danger SPL or custom mtd patch needed for what 90% of people are using 2708 with 14mb extra ram then this is a massive home goal.
Sorry just speaking the truth.
No, thats allright, I haven't applied much stuff to it yet.. I just uploaded it the day I compiled.
i'm impressed, just needs a little work. Also, those figures you have for free ram is with or without swap??
do you include a 2708 kernel? is that the default one? that could be a little clearer.
Sorry for the bugs, it is my first native phone rom.. Those figures are for free ram (physical) with the stock system without google apps with 2708 kernel. I did not include 2708 kernel yet but I will very soon! With the google apps and without the 2708 spl/radio, i got around 30 mb of free ram.
The mandatory ext4 partition and swap is for the R5 (uploading now) with a2sd but su still does not want to work. The "su" file was not included in the aosp compile for some reason and it messes everything up..
I like the fact you have changed the OP now about it being fast or faster
Look forward to see where you go with this fella, maybe a look at EzTerry's Froyo Parts.apk if it can help you out. I ported it with Terry's permission to F4T 182 and may be a useful additional update for your rom in the future to add additional functionality.
shadowch31 said:
I like the fact you have changed the OP now about it being fast or faster
Look forward to see where you go with this fella, maybe a look at EzTerry's Froyo Parts.apk if it can help you out. I ported it with Terry's permission to F4T 182 and may be a useful additional update for your rom in the future to add additional functionality.
Click to expand...
Click to collapse
Yeah sorry I overestimated
35 MB of free physical ram with market, pinyin IME, and google messaging running DangerSPL and stock radio, no 2708.
Well, I'm curious to see Froyo 2.2.2 on my G1 anyway. I have it on my TP2 and the major difference I noticed is that 2.2.1 doesn't have wifi tethering in its Wireless and Networking settings but 2.2.2 does. (Not really a big deal I suppose, since I already have a tethering app.)
I'm kinda curious about why Lazlo or the others haven't merged 2.2.2 yet.
highlandsun said:
Well, I'm curious to see Froyo 2.2.2 on my G1 anyway. I have it on my TP2 and the major difference I noticed is that 2.2.1 doesn't have wifi tethering in its Wireless and Networking settings but 2.2.2 does. (Not really a big deal I suppose, since I already have a tethering app.)
I'm kinda curious about why Lazlo or the others haven't merged 2.2.2 yet.
Click to expand...
Click to collapse
Simple answer - Go ask them
My guess is nothing more than a reduction in memory footprint??? And Wireless tethering is so easy using the google code website (just for those that don't know) http://code.google.com/p/android-wifi-tether/ last time I remember wireless tether included in a rom was back in Donut days.
shadowch31 said:
Simple answer - Go ask them
My guess is nothing more than a reduction in memory footprint??? And Wireless tethering is so easy using the google code website (just for those that don't know) http://code.google.com/p/android-wifi-tether/ last time I remember wireless tether included in a rom was back in Donut days.
Click to expand...
Click to collapse
link is broken, tried chrome and IE thinking it was the site...
Link works for me... Using Google Chrome
Updating rom soon (this week) with EVERYTHING fixed. No more lags and bugs..
jcarrz1 said:
link is broken, tried chrome and IE thinking it was the site...
Click to expand...
Click to collapse
Nothing wrong with the link, works fine. I suggest taking a closer look at your pc
i was using an adblocking hosts file. who the hell doesn't? especially on xda... LOL i guess some people like ads
Ok, R5_Stable released. It is COMPLETELY STABLE with 97% bugs fixed. The UI is smooth and fast after all dalvik-cache has caught up on first boot. I have already messed with odexing and it works but will be in next release(s) because I still like my themes!
Note:
-DO NOT use QuickBoot application as it shuts down android incorrect (at least on this build), it works, but after you press "reboot" and android loads, up, android immediately crashes, and then reboots again and works fine..
-Now includes Live Wallpapers
-Launcher pro is default launcher
-seperate google apps for legal reasons (yeah again)
-On first boot, please wait until dalvik-cache has caught up (about 2 min) or until the phone has received radio signal for rom to run at full speed
-Pershoots .11 kernel added now
- 30+ MB of free physical ram with danger spl!! 60+ with 2708+ radio/spl/kernel.
-Requires Danger SPL now
- battery life is good but does not last 2 days
- setCPU recommended with ondemand at 122mhz-614mhz s (lower if you want to save battery but still runs fine @ 528mhz)
- usb tethering does not work unfortunately (the one built into rom)
jcarrz1 said:
i was using an adblocking hosts file. who the hell doesn't? especially on xda... LOL i guess some people like ads
Click to expand...
Click to collapse
Fella just because you use a host file please don't blame the links or assume no-one else is using them when links work for them. Not my fault you blindly use the host file and have no clue of how to configure it to allow certain things. The fault is the user because a computer works on a simply principle of it can only do what YOU tell it too.
smooth but on the mytouch wen using any other kernel it breaks wifi and the stock kernel doesnt support the new radio
JARVIS Kernel for LGP999
Only for CM/Miui or AOSP roms
Deceided that XDA needs a thread too. I won't look through it really often. I hope that other more experienced members can answer some easy questions, so I can focus on developing things.
Features:
3.0.y Kernel
Interfaces to control a bunch of Features (Like vibration strength)
Overall optimized parameters to provide a smooth user experience
working UMS - thanks Harsh
App which controls all the interfaces (will be released later for P999)
Disclaimer:
I'm not responsible if your phone is fried by the kernel or you miss some important phone call! I'm not forcing you to install this Kernel and so it isn't my fault.
Download:
Download
Or Update via my app
Don't use profiles, because they can lead to instabilities.. and they're unnecessary.
Stay away from SetCPU or any other app. Could lead to problems because of the customizable OC. Wait for my app until it's not ready use command line coupled with a init.d script.
You don't need to optimize any values in the ram disk. It should work perfectly without any other tweaks.
When you experience problems like random reboots, SODS, etc. try to go back to stock settings. And apply my 1 GHz frequency table. If this isn't fixing your problems report a bug with detailed informations. Like ROM, Settings, etc.
If a person reported a bug and you experienced it too, +1 this bug report or whatever. In this case I know that the bug isn't only happening on one specific device.
Changelog:
I'm damn lazy. So just use my github commit history (here).
Source Code:
Github
Thanks to:
Dekudan/Victor Von Zeppelin - for creating awesome icons for the app
Arcee - Setting up CyanogenMod and everything.. Just awesome
wkpark - for his cherry-pick marathon.. This guy really has endurance hehe
Ezekeel - Really innovative dev with impressive ideas.
Everyone who open sourced their work
Interfaces:
CPU Control:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Used to set the minimum frequency.
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Used to set the maximum frequency.
Fsync Control:
/sys/class/misc/fsynccontrol/fsync_enabled (Read and Write)
Enable/disable single file/filessystem sync.
WARNING: This could lead to potential data loss after a unwanted reboot (battery pull)
enable=1, disable=0 (default enabled)
Vibrator Control:
/sys/class/misc/vibratorcontrol/vibrator_strength
Set the vibration strength.
possible values: 1500-3600
Force Fast Charge:
/sys/kernel/fast_charge/force_charge_mode
changes the usb charging mode. We have 3 modes:
Fast - Forces fast AC charging. Disable data transfer!
Slow - Always charges slow (like on a normal PC USB bus)
Auto - automatical detects which mode should be set.
Possible values: fast=1, slow=2, auto=0
Example
Use adb to connect to your device and then in adb shell (with su) (you can setup a init.d script to auto apply everything)
We want more vibration because we can hardly notice it and want to pwn our friend with benchmarks. Additionally we want to charge our device faster.
Code:
echo 3500 > /sys/class/misc/vibratorcontrol/vibrator_strength
echo 1 > /sys/kernel/fast_charge/force_charge_mode
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
And that's it
reserved2
Awesome! Can't wait to try it.
Sent from my LG-P999 using xda premium
Oh and can somebody can tell me if you guys have a init.p999.rc file in the root dir (/init.p999.rc)?
Needed for app support. App nearly ready for P999.
Nope I don't have one, screenshot attached.
Sent from my LG-P999 using xda premium
fadownjoo said:
Nope I don't have one, screenshot attached.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Is this a recent ICS rom?
Not sure if that file is the one you're referring to, I'm using AOKP B38
Sent from my LG-P999
Benee said:
Is this a recent ICS rom?
Click to expand...
Click to collapse
Mine is and there is.
On 3.0.y kernel too. Built a few days ago.
Thanks guys awesome.
One question: is the kernel working fine? I don't have a p999 but it should work well.
Benee said:
Thanks guys awesome.
One question: is the kernel working fine? I don't have a p999 but it should work well.
Click to expand...
Click to collapse
Haven't flashed yet. Will do when I'm home.
Benee nice to see you have ported this kernel from p990
i shall try in a few
If it's working I will need a tester who wants to test the app. He should be capable of getting me a logcat. I will send him a special debug version and later he will receive the app for free
Benee said:
If it's working I will need a tester who wants to test the app. He should be capable of getting me a logcat. I will send him a special debug version and later he will receive the app for free
Click to expand...
Click to collapse
It boots! I'll test. Everything seems to work fine. Haven't tested all the features yet though. I'm no noob as you can see from my previous posts. But I'm not an expert either.
Sent from my LG-P999 using Tapatalk 2
I'll second that, it boots fine. Got it clocked to red line and purring like a kitten. I can get you that logcat, I'm an XDA News writer, so I'm qualified. Thanks for your work.
[email protected]
Benee said:
If it's working I will need a tester who wants to test the app. He should be capable of getting me a logcat. I will send him a special debug version and later he will receive the app for free
Click to expand...
Click to collapse
I can test for you, it boots and running smoothly. Going to start changing frequencies. I can also provide ample log cats of needed
Benee said:
Oh and can somebody can tell me if you guys have a init.p999.rc file in the root dir (/init.p999.rc)?
Needed for app support. App nearly ready for P999.
Click to expand...
Click to collapse
Thanks for your work Benee. Nice to have another option and can't wait for the app.
I likewise can test for you. Web/Android dev and some playing with kernels here and there.
Yes, we do have that file on root dir
Also, I PM'ed you about your app and log request
[email protected] -Developers
awesome
i'm luvin the good work had the kernel for a while exactly what i expected smooth and fast. keep up the good work.
It was bound to happen, so here it is. The Grouper running Android 6.0!
What works:
- WiFi
- display
- audio
- Bluetooth (partially)
- Multiwindow
- Auto-rotate
What's broken:
- OTG
- surfaceflinger*
What's untested:
- camera
- NFC
I will not offer a ROM zip at this point due to the fact that the rootfs is inherently insecure for the time being. However, the sources are available below and should be bootable.
Sources:
http://github.com/Grouper-aosp
CREDITS:
@dolorespark - ramdisk fixes, sepolicy fix (3.1 compatible)
@Ziyan - kernel work and device tree
@GtrCraft - device tree help, testing and support
I highly encourage the use of the stock 3.1 kernel. I've modified sepolicy to allow old kernels to run.
Wow ☺
what does it mean, broken surfaceflinger*?
Thanks dude! Will try to flash when rom is linked and when I can access my Nexus 7!
TheXorg said:
what does it mean, broken surfaceflinger*?
Click to expand...
Click to collapse
For some reason, surfaceflinger isn't looking in the /system for the GPU binaries. To bypass this I had to symlink them to the rootfs.
Wow. Though, it would be great if anyone -- or the OP -- could cook the ROM and share the link. Looks good enough.
itskapil said:
Wow. Though, it would be great if anyone -- or the OP -- could cook the ROM and share the link. Looks good enough.
Click to expand...
Click to collapse
A link will be posted as soon as we fix Surfaceflinger and a couple bugs in the 3.4 kernel.
@Motorhead1991 thanks a lot for the heads up! Waiting patiently.. pls tag once it's up. :good:
Having done this already, let me add:
most likely also you have gps broken, and nfc broken
i am guessing selinux is also not doing all it should
also the issue is not with surfaceflinger (that is just the symptom)
I was hoping someone could port 6.0 to this device. Waiting for the OP to show ready to rock and roll !
@Motorhead1991 awesome work @dmitrygr saw a reddit post where you said you are working on nexus 7.... patiently waiting for it after trying your nexus 4 build
2012katas said:
@Motorhead1991 awesome work @dmitrygr saw a reddit post where you said you are working on nexus 7.... patiently waiting for it after trying your nexus 4 build
Click to expand...
Click to collapse
Other way around, friend . @dmitrygr did the N4. I started on the N7 (2012) myself and received assistance from him and others .
Excellent work! I'll be watching this with interest.
Thanks! I'm waiting for your release
Camera, NFC and OTG is not important for me right now.
dmitrygr said:
Having done this already, let me add:
most likely also you have gps broken, and nfc broken
i am guessing selinux is also not doing all it should
also the issue is not with surfaceflinger (that is just the symptom)
Click to expand...
Click to collapse
For NFC, we need to revert this commit - adding it to the device tree is way too problematic, and this shouldn't cause problems for other devices anyways....
For SELinux on 3.1, we need these commits, and we need to remove three recovery-related neverallowed rules from the device tree (not a huge deal really) - these commits are already included in my 3.4 kernel (thanks to the android-3.4 merge), but it's not ready to be shipped... posting a screenshot of M running with 3.4 was a mistake.
For EGL, I use this workaround, which fixes that particular problem without modifying the system libraries - it would be really nice if you knew another, nicer solution, also without modifying the system libraries
Right now, GPS, camera and audio is broken (thought audio might be broken because of camera - I experienced similar symptoms while working on 3.4).
dmitrygr said:
Having done this already, let me add:
most likely also you have gps broken, and nfc broken
i am guessing selinux is also not doing all it should
also the issue is not with surfaceflinger (that is just the symptom)
Click to expand...
Click to collapse
The NFC propably needs the NXP NFC stack which had been dsiabled building by google and can be reverted: https://gerrit.omnirom.org/#/c/14956/
My Optimus G needed relocations for the nfc hardware lib, but I think it might be not needed, anyway this is hacky change to make relocations warnings again: https://gerrit.omnirom.org/#/c/14955/
Ziyan said:
For NFC, we need to revert this commit - adding it to the device tree is way too problematic, and this shouldn't cause problems for other devices anyways....
For SELinux on 3.1, we need these commits, and we need to remove three recovery-related neverallowed rules from the device tree (not a huge deal really) - these commits are already included in my 3.4 kernel (thanks to the android-3.4 merge), but it's not ready to be shipped... posting a screenshot of M running with 3.4 was a mistake.
For EGL, I use this workaround, which fixes that particular problem without modifying the system libraries - it would be really nice if you knew another, nicer solution, also without modifying the system libraries
Right now, GPS, camera and audio is broken (thought audio might be broken because of camera - I experienced similar symptoms while working on 3.4).
Click to expand...
Click to collapse
In hindsight, yeah showcasing 3.4 was jumping the gun a little bit. I just got ahead of myself and wanted to bring hope to people that still use such an "old" device.
Update: I was able to fix gps in a similar way. Also, it seems like 3.1 + M isn't going to play together (serious memory management issues), so I had to switch back to 3.4 (me and @sheffzor are working on 3.4 day and night). So, only camera and audio remains
Sweet! @Ziyan, @sheffzor and all the other devs for the win!