• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Hroark's Warp Kernel Source

chevanlol360 said:
Lol the higher the overclock is set to the more battery you lose. The lower your frequency i set to the better the battery life. When i first tried out the overclock kernel for the Ultra the higher i would go with the frequency the more battery you lose and the lower its set to the better the battery life. The Ultra takes a good 4-5 hours from a dead battery to charge up to a full battery, and i have realize whenever i underclock to about 700 or 600mhz the phone charges within 3-4 hours. Regular battery life with the Ultra is about a good 7 hours with moderate use including 3g and gaming. Whenever i underclock to about 700mzh i would get up to a good 9 hours. Thats a 2 hour difference and horstly i rarely saw lag. I dont have much apps taking up all my ram.

Shinru once you get the frequency up to stable 1.8 i wouldnt suggest you go any higher lol thats where the Ultra starts to get hot and total battery drain within 2 hours tops even with little use .
Click to expand...

I don't plan on going any higher, as long as you set profiles in SetCpu then your golden for charging and idle time, i have my screen off idle frequency under-clocked to 245-500Mhz, in call is 460-600Mhz Charging is set to 245-500Mhz, normal use is scaled to 1.7Ghz Ondemand

EDIT: Hroark, any way to gain access to this? http://10.67.16.51/svn/7x30-Gingerbread

EDIT 2: Might have freed up some ram by removing some unused pmem values, building then testing

EDIT 3: Hroark check out this kernel source : https://github.com/freexperia/semc-kernel-msm7x30 its pretty close to the warp, its what i used for the overclock

EDIT 4: Freed about 30Mb of ram through the kernel pmem values, audio playback and speaker phone still work, it was unused pmem audio values I now have a total of 372Mb of ram

EDIT 5: lol been busy looking through files, this files calls an "in call state" could have something to do with the handset speaker

kernel/arch/arm/mach-msm/include/mach/qdsp6v2/audio_dev_ctl.h

shot000001r.png
 
warpuser25 said:
Do you know when your going to post an update on your Kernal? could you post the latest zip please
Click to expand...


it is not usable yet, it is only for testing


I posted my latest a few posts above


it does not have shinru2004's OC or performance tweaks
 
shinru2004

do you think we have a better chance getting that new Blade Plus source working, or continuing with what we are working on
 
Well since the handset audio doeant work on either one, i would say we are in a stale mate right now. The OC can just be copied over same as the pmem values. Its up to you. Blade plus source seems cleaner. Does key vibration work right with it?
 
shinru2004 said:
EDIT 5: lol been busy looking through files, this files calls an "in call state" could have something to do with the handset speaker

kernel/arch/arm/mach-msm/include/mach/qdsp6v2/audio_dev_ctl.h
Click to expand...


you can probably delete all the qdsp6 folders, they are not being used

we are using the qdsp5v2
 
Ok good to know, we should go through and delete everything unused to clean it up a bit, unless we are going to support multiple devices with the source

Oh, i changed the gpu freq and bus speeds. Will test after building
 
shinru2004 said:
Well since the handset audio doeant work on either one, i would say we are in a stale mate right now. The OC can just be copied over same as the pmem values. Its up to you. Blade plus source seems cleaner. Does key vibration work right with it?
Click to expand...

Blade Plus source does not work out of box, we do have to make some mods to it before it works


I have been messing with both, hoping I would get lucky

I think I will try to stick to the 2.6.35.11

I think it has a better implementation of KGSL, which will be important, once we start trying to get CM9 working
 
shinru2004 said:
unless we are going to support multiple devices with the source
Click to expand...

too hard to do that

there are a lot of folders not being used

basically if a .o file does not show up in the folder when you do a build, there is a good chance it is not being used
 
Anyway to get the updated adreno 205 driver source? That will be important for CM9 as well

I will continue combing over the source hopefully we will get lucky with the sound issue. Been looking through the svn files but havent found anything significant yet
 
shinru2004 said:
Anyway to get the updated adreno 205 driver source? That will be important for CM9 as well

I will continue combing over the source hopefully we will get lucky with the sound issue. Been looking through the svn files but havent found anything significant yet
Click to expand...

i looked at the .svn files

most difference between those files and the the files in the main directory are just ZTE comments in the files

but

the .svn folders do have quite a bit of files that the main folders do not have which look important

and yes I did try using those files in both sources, and they did not fix the audio issue
 
hroark13 said:
don't know to be honest


you asked about key vibrations

is key vibration working for you in the .11 source ?
Click to expand...

Yeah just was wondering if it worked right off on the blade plus source, as for the audio im not sure if we will find a fix or not. i resorted to looking at other source similar to this one. the experia is pretty close
 
Yea, same here believe it or not im about 4 months in. Im comparing some files from the warp source with your source to see if we missed something. although testing kindda sucks 9 times out of 10 the files don't work when added lol

You think Koumajutsu would be interested in taking a look?
 
I just wanted to say thank you for all the time and effort that you all are putting in for making the cwm for us. I check back every few days. Take care and good luck shinru2004 and hroark13
 
I updated to the newer version of your source with the tianma fix and hit an issue. when running make menuconfig of make ARCH=arm i get the output

~/kernel$ make menuconfig
make: *** empty variable name. Stop.
make: *** [scripts_basic] Error 2

~/kernel$ make ARCH=arm
make: *** empty variable name. Stop.
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.

Nevermind it been resolved, archive manager must have extracted the kernel wrong

I'm having issues with adding in these governors. They are programmed different so i am going to rewrite them so they are compatible with our phones
 
ok I decided to look at the original ZTE Warp source code to see if I could fix it by using the least amount of files as possible

This is what I have come up with

kernel_patch.zip

These files come from the Blade Plus source

These are only a few files, and if you use them to overwrite the files in the ZTE Warp source, it will produce a bootable kernel, with the LCD fix and LED updated stuff


The problem is Handset Audio still does not work, when making a phone call

speaker phone and head phones does


and if you install Skype, and use that, both handset, and speaker phone works

crazy stuff

I am spending a lot of time on this, and I am starting to hate ZTE for not releasing working code


maybe it could be the baseband version, i am gonna try to downgrade if possible and see what happens
 
Hroark im planning on emailing ZTE we really need this open source im behind you guys 100% its unbelievable because most companies will release the working kernal bit ZTE wont
 
hroark13 said:
ok I decided to look at the original ZTE Warp source code to see if I could fix it by using the least amount of files as possible

This is what I have come up with

kernel_patch.zip

These files come from the Blade Plus source

These are only a few files, and if you use them to overwrite the files in the ZTE Warp source, it will produce a bootable kernel, with the LCD fix and LED updated stuff


The problem is Handset Audio still does not work, when making a phone call

speaker phone and head phones does


and if you install Skype, and use that, both handset, and speaker phone works

crazy stuff

I am spending a lot of time on this, and I am starting to hate ZTE for not releasing working code


maybe it could be the baseband version, i am gonna try to downgrade if possible and see what happens
Click to expand...

I'm running the kernel on my rom which is B08b it has baseband version N860B01 so what version baseband does your phone have. I'm not sure but there might be an N860B00 baseband but, don't hold me to it

EDIT: Maybe sebastian can get one of his contacts at ZTE to look at your source, if where lucky they might fix it for us?
 
another thing with testing the built kernels with Skype

if you do that echo test thing

your voice does not get recorded when using handset, but it does get recorded if you use speaker phone
 
shinru2004 said:
I'm running the kernel on my rom which is B08b it has baseband version N860B01 so what version baseband does your phone have. I'm not sure but there might be an N860B00 baseband but, don't hold me to it

EDIT: Maybe sebastian can get one of his contacts at ZTE to look at your source, if where lucky they might fix it for us?
Click to expand...

i am starting to think that my source might just have to much stuff mixed up in it

that is why I am messing with the Warp source again

and as you can see in those files for that patch, there is really nothing in there audio related


my baseband is N860B01
 
try the kernel with the cm7 you built? can you make calls in it? if so test to see if audio gets passed off to the handset speaker. you might be able to check out the baseband info within cm7 to see whats going on if thats possible

Found some info, this folder contains drivers for the diff. audio chips on msm7x30 architecture, and some are different from the warp source

kernel/drivers/mfd

Im working on some of the files in this folder, will re-build and test

The warp uses the pmic8058-core.c and pmic8058.c, i think it also uses bahama-core.c as well which wasn't configured to build before
 
You must log in or register to reply here.
Back
Top Bottom