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

Root [Boost Mobile] LEVIATHAN Elegace & Elegance OC Roms Released

Do anyone still lose cmda service while wifi is on? i seem to lose it when the screen turns off with wifi on

Hi Randy, it looks like a problem across several roms, mostly the ones with OC. Hope this helps, but currently I dont think their is a solid fix for all phones. :( Look around the different threads and see what other people have done, different build prop's and stuff like that.:)
 
Hi Randy, it looks like a problem across several roms, mostly the ones with OC. Hope this helps, but currently I dont think their is a solid fix for all phones. :( Look around the different threads and see what other people have done, different build prop's and stuff like that.:)


Yep changing the build prop on mine fixed the wifi and 3g issues i was having..;)
 
OC, install the non OC version or use an app to underclock the version you have. Or go with a different rom altogether.

I am currently re-building the Non-OC version for those that like the rom but have major problems with OC.

Also Tonight iam beginning the process of Building/Compiling my own Kernel from source.
 
  • Like
Reactions: Doc
Alright caise the beta build sorta worked for me, but the home and search button didnt work, and with the latest release it would het past the boot screen load up, and i would would click the android charater and it would freeze. It looked awesome though on the beta one thay worked.
 
Only issue now is camera fcs sometimes and for some idd reason my downloading got cut down by a huge amount. Browsing got slower. Trying to adjust things n see. Thanks for nice rin thiugh.
 
i can put some more tweaks in build.prop to possibly make 3g a little faster.. i cant say how much of an improvement you will see, it all depends on your location from the sprint towers

EXCUSE ME, did you say you can make 3g faster. I have to try it. I saw a post of an updated build.prop further down this page. Is that one that will work for improving 3g or do you have another one?
 
From what I understand, chip manufacturers design their processors to operate in a certain frequency range, and they are tested to be stable within these limits. If this limit is exceeded, the dependability of the chip will be compromised. Even if certain individual chips on the production line can run faster than the next one coming down the conveyor belt, the company has no (easy) way of indicating those specific chips, so they rate the whole family at the lowest common denominator - the highest speed at which every member of that processor family can reliably run. Hence you get some chips that can run at the manufacturer-rated maximum speed, and others that - due to manufacturing process differences - can run significantly higher. This may explain the issue with our phones; you have some Snapdragons that can run reliably at the maximum speed our tweaked kernel allows, and others which only perform to the manufacturer's specifications. I've researched the Qualcomm documentation on our chips, and they are rated at a maximum of 1.4GHz. I wonder if even the people who have trouble running an OC kernel could run at this company-specified maximum speed... a good way to check would be to use Shin's 1.7GHz kernel (which defaults to the stock 1GHz by default, but has the ability to achieve higher speeds after being told to do so by a CPU control app) at the stock speed, and see if it boots and runs as intended. If so, then bump the speed up a notch and try again. This could be repeated until the maximum stable speed is found for your specific phone. I would try this myself, but my phone is happy at all clock speed values that I've thrown at it.

Who knows? Maybe those certain "over-achieving" chips could be pushed to even further than 1.7 if the kernel allowed it :)
 
From what I understand, chip manufacturers design their processors to operate in a certain frequency range, and they are tested to be stable within these limits. If this limit is exceeded, the dependability of the chip will be compromised. Even if certain individual chips on the production line can run faster than the next one coming down the conveyor belt, the company has no (easy) way of indicating those specific chips, so they rate the whole family at the lowest common denominator - the highest speed at which every member of that processor family can reliably run. Hence you get some chips that can run at the manufacturer-rated maximum speed, and others that - due to manufacturing process differences - can run significantly higher. This may explain the issue with our phones; you have some Snapdragons that can run reliably at the maximum speed our tweaked kernel allows, and others which only perform to the manufacturer's specifications. I've researched the Qualcomm documentation on our chips, and they are rated at a maximum of 1.4GHz. I wonder if even the people who have trouble running an OC kernel could run at this company-specified maximum speed... a good way to check would be to use Shin's 1.7GHz kernel (which defaults to the stock 1GHz by default, but has the ability to achieve higher speeds after being told to do so by a CPU control app) at the stock speed, and see if it boots and runs as intended. If so, then bump the speed up a notch and try again. This could be repeated until the maximum stable speed is found for your specific phone. I would try this myself, but my phone is happy at all clock speed values that I've thrown at it.

Who knows? Maybe those certain "over-achieving" chips could be pushed to even further than 1.7 if the kernel allowed it :)

Very Good Information!! idk if i would want to push the chips more than 1.7ghz though, figure thats Running at %170 capacity. opening the door for major heat and instabillity issues. if there was some better heatsink we could put in the phones, then i could see pushing them a little harder
 
EXCUSE ME, did you say you can make 3g faster. I have to try it. I saw a post of an updated build.prop further down this page. Is that one that will work for improving 3g or do you have another one?

New Build.prop has Signal / 3G Tweaks. as much as the kernel will allow, i spent some hours testing, adding, changing, and removing tweaks for this one
 
Yeah I Have But I Read Exactly What Thae Forum Says And It Just Says to wipe dalvik and cache

when installing a new rom it should go like this
Boot into recovery
Wipe Data/Factory reset (CWM)
wipe cache partition
wipe Dalvik Cache
Install zip from sdcard
 
Just finished compiling my Arm-eabi toolchain from source... thank god for having a Phenom II X6 and 8gb ram lol, makes the process alot quicker.... now for the fun part.... getting Kernel source to work, since Zte released broken Source
 
I am currently re-building the Non-OC version for those that like the rom but have major problems with OC.

Also Tonight iam beginning the process of Building/Compiling my own Kernel from source.

Dude that is a very cool thing.........:D
 
Very Good Information!! idk if i would want to push the chips more than 1.7ghz though, figure thats Running at %170 capacity. opening the door for major heat and instabillity issues. if there was some better heatsink we could put in the phones, then i could see pushing them a little harder

That's 170% capacity versus stock. Since our chips are rated for 1.4GHz, running them at 1.7 is actually only 121% capacity. But I still agree... if the phone gets that hot from running at 1.6, I too would hate to see much higher lol
 
this is pissing me off lol, same compile error no matter what i do


make ARCH=arm

CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CC init/main.o
In file included from include/linux/mempolicy.h:70:0,
from init/main.c:51:
include/linux/pagemap.h: In function
 
Just finished compiling my Arm-eabi toolchain from source... thank god for having a Phenom II X6 and 8gb ram lol, makes the process alot quicker.... now for the fun part.... getting Kernel source to work, since Zte released broken Source

OMG!!!! I'm excited for you!!! I really hope you can get a stable kernal built!!
 
Back
Top Bottom