Android OS Forum banner

[Kernel] Aeroevan Vivow Kernels (For Aosp)

123K views 504 replies 78 participants last post by  sjpritch25 
#1 · (Edited by Moderator)
I have been playing around with merging jdkernel and tiamat kernels. I basically merged in tiamat changes into the mainline cm kernel and then git cherry-pick'd lots of goodies out of jdkernel's (mostly backports from the mainline kernel and bfs).

The only real work I did was to fix the build for gcc 4.6 Okay, I've done some real work now


v0.3: http://min.us/lbgIXdCeZTE9ks
v0.4: http://min.us/lb0IdbUB4zSO4E
v0.5: http://www.multiupload.com/0TNP5TQQ8E
v0.5.1: http://www.multiupload.com/20PS2Q4A2N
v0.6: http://www.multiupload.com/4CF8DCS38I or http://www.multiupload.com/ZOAMV7NQBI (with BFS)
v0.7: http://www.multiupload.com/T2OCG21D8R or http://www.multiupload.com/V958PHM33D (with CFS)
v0.8: http://www.multiupload.com/UGIHGFYAR9 (BFS) or http://www.multiupload.com/GOZOC62USW (CFS)
NOTE: Only use 0.8 if you are on a current CM7.2 build or ROM based off of current CM (i.e. not MIUI). Also there is a bug with multitouch that I'll track down soon.

Changelog:
v0.3: First stable release (mostly tiamat with some jdkernel backports).
v0.4: Change to jdkernel voltage table. Seems to be more friendly to overclocking.
v0.5: Add zram module for compcache support + fixes to enable CONFIG_USB_ANDROID_ACM, CONFIG_USB_ANDROID_MTP, CONFIG_DOCK_ACCESSORY_DETECT, and CONFIG_USB_HUB (so if you have any usb issues let me know).
v0.5.1: reverted some usb changes, hopefully fixes usb mounting on windows.
v0.6: Switch to CFS + other small fixes. This should "fix" the data issue. Still have BFS option, but the default CFS is recommended until I can track down the issue in cyanogenmod.
v0.7: Back to BFS by default. Updated camera driver from CyanogenMod. More compiler optimizations. Also rewrote updater script.
v0.8: Upstream CyanogenMod changes + small touchscreen driver update from HTC. Only tested on my CM7.2 Kang build.

source: https://github.com/a...-kernel-msm7x30

Let me know if there are any issues; I've only had my dinc2 for a few days, so I don't really know how it compares to other kernels and I have only been testing on cm7 nightlies.

I'm usually on IRC in #inc2root on andirc.
 
See less See more
1
#4 · (Edited by Moderator)
fixxxer2012 said:
glad you posted your own thread man. is this build newer than your 10/18 or 10/20 builds? did you fix the led not lighting when charging?
Yeah, charging and adb/usb mounting should work now. I think I had merged in wireless charging from both trees or something, I basically started from scratch today and tried to make sure nothing broke after each patch.
 
#20 ·
Not sure what's wrong there, but I went back to Tiamat 1.1.5 and the .apk I found for daemon controller wouldn't start either. It looks like it's similar to cpumaster which seems to work for me. But I usually just use CM7 CPU settings. I don't actually have setcpu, so I don't know what it could be doing differently for the settings on boot but I'll try to look into it (does it use init.d scripts or something?).
 
#17 ·
"jbarcus81 said:
Now I'm on the latest miui and of this kernel, I can't get daemon control to work, sticks on the loading screen..
Does it try to load a kernel module? There might be some issues since I used gcc 4.6 instead of 4.4 (which is more common). A dmesg output might be useful, or I can give the app a try to see what's going on.
 
#21 ·
\"aeroevan\" said:
Not sure what\'s wrong there, but I went back to Tiamat 1.1.5 and the .apk I found for daemon controller wouldn\'t start either. It looks like it\'s similar to cpumaster which seems to work for me. But I usually just use CM7 CPU settings. I don\'t actually have setcpu, so I don\'t know what it could be doing differently for the settings on boot but I\'ll try to look into it (does it use init.d scripts or something?).
I wanna say daemon control uses init.d scripts. And installs something into xbin also.
 
#30 · (Edited by Moderator)
I can't recreate the issue, maybe try to remove and re-add setcpu in the superuser apps and check the superuser log. I had a superuser notification on boot that setcpu had been given root permissions or whatever. This is with setcpu 2.2.4.

I didn't change any profiles, just bumped up max to 1.2GHz and min down to 245MHz (which seems to be fairly stable for me).

But since I hear that the voltage table in jdkernel is better for most people, so I'll probably use his voltages in my next version.

EDIT: I just reflashed a CM7 nightly, then my kernel, and setcpu even worked after that, so I don't have a clue. Maybe try redownloading and reflash? And/or get a logcat for me to look at since I can't recreate the problem.
 
#27 · (Edited by Moderator)
I tried bumping up all the voltages +25 to get an OC higher than 1305. On jdkernel I can get to 1800. Anyways I bumped them up one and it froze quicker than normal. This kernel makes my phone super quick with light tasks, but benchmarking isnt very good. I couldn\\\\\\\'t get over 2600 performance gov 1305/192. My max benchmark on jdkernel was over 4000 at I think 1766. Probably going to either go back to jdkernel, or use incredicontrol to set the voltage of this kernel to the jdkernel voltage table to see if I can get a higher OC.

Edit: ok so I was going to change the voltages but they are so similar at the higher frequencies where I was having problems. Turns out smartassv2 is limiting my OC by freezing above 1305. No problems with smartass or performance. At 1497 I went from smartass to v2 and it froze instantly.

Another thing I noticed is that when calling people sometimes they can\'t hear me. Happened with 2 of my last under 10 calls. Never had this problem until I started using this kernel.
 
#31 ·
I don't OC that much, and prefer better system responsiveness over benchmarks since hopefully you use your phone more than you benchmark it


The only call volume changes that I included are the same ones in the tiamat kernel, and I haven't had any issues (but I don't actually make too many calls from my phone...).
 
#28 ·
I'm having a touch time compiling this kernel.
I pulled the config.gz from my phone after installing this kernel (0.3), ran the make oldconfig, make, but compile errors out almost immediately.
Any pointers?
I noticed that there are much fewer options in the menuconfig than I'm used to seeing (say, from jd's kernel).
 
#29 · (Edited by Moderator)
I would start with
Code:
<br />
make aeroevan_vivow_defconfig<br />
to use the config I started with, and then make menuconfig as usual. I have a simple build script at http://www.prism.gat.../files/build.sh that I use to point to where I have my arm toolchain. Hope that helps.

EDIT: I also use the gcc 4.6 android arm toolchain from linaro; let me know if you have any other issues.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top