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

Root [Boost Mobile] Hroark Kernel Over-clock bug reports

hroark13 said:
I would like any kernels that I do release with any roms to include Shinru's OC and tweaks, if he is willing to share, but that is up to him
Click to expand...

Android is an Open source project, would be kind of shady for me not to share after all the work you have done to get us to this point. Once i have absolute proof that everything is working right then i will release my source files for OC, which include freeing up about 40ish Mb of ram.
 
shin, just so you know my setup/steps I am taking to test the oc:

my hardware is the original warp from last year in october
I am starting from a restore of woodstock's b08 nandroid, factory data reset, wipe cache, wipe dalvik, fix permissions, then flashing your shinjitsu rom 1.5b and boot, reboot to recovery, next I flash the warp_263511_OC_16.zip that hroark had posted on the kernel thread, wipe cache, wipe dalvik, reboot.

Any possibility that leaves any other software variable out or do you see anything wrong with that process to get to where this should work?

If those steps are right and I still get a freeze, I think we have it narrowed down to hardware, correct?
 
shinru2004 said:
Android is an Open source project, would be kind of shady for me not to share after all the work you have done to get us to this point. Once i have absolute proof that everything is working right then i will release my source files for OC, which include freeing up about 40ish Mb of ram.
Click to expand...


I was pretty sure that you would, I just did not want to assume anything, or make it seem that you have to
 
ok, here is the update: I did what I said, flashed to woodstock's stock b08, then went to shinjitsu 1.5b, then put on the overclock 11 kernel. Phone freezes at default settings for oc. I can use voltage control to turn it down to 1024 max and then no more freezing.

I have a second issue: when wifi is on and the phone locks and I wait for about a minute and then wake the phone and unlock it I have a "no signal" for the cell signal. To get signal back I need to turn off wifi, then the signal will come back for the cell.

I think this confirms that for some of us with the first version of the warp hardware that the oc kernel causes freezing and wifi/cell issues.
 
I bought my phone with b08, but from flashing other roms iam on woodstocks b08 nandroid using 2.6.35.7oc. Voltage control, set at 1401 and no issues.
 
Has anyone with the original warp successfully oc'ed above 1.4ghz?

Sent from my N860 using Tapatalk 2 Beta-5
 
jetx2x said:
Has anyone with the original warp successfully oc'ed above 1.4ghz?

Sent from my N860 using Tapatalk 2 Beta-5
Click to expand...

I have but i don't count >.< i run stable 1.7 all day and night.

@ Mrbobo I havent edited any files that would have a negative impact on signal, any files that have been edited where to the CPU. all i did was bypass the bios limit for the core clock and adjust frequency.

Does the none OC kernel do this? have you tested to see if it happens on the none OC?

I will check the files and see what might be causing this

@ Hroark: Sebastian posted something you may want to see that could pertain to this issue

http://pastebin.com/RBTjfLm3
 
shinru2004 said:
@ Hroark: Sebastian posted something you may want to see that could pertain to this issue

For some reason ZTE change the ident string of the kernel, for example, from the - Pastebin.com
Click to expand...


that is interesting, but the RIL is working


I actually encountered this issue on an OC kernel, but not on the non-OC

If you are running an OC kernel, connect your wifi to a network, then let the phone go to sleep


then try to make a call

i do not remember if it was on .11 or .7


p.s.

I have updated the .11 source to .14 on my github, if you want to try it
 
hroark13 said:
that is interesting, but the RIL is working


I actually encountered this issue on an OC kernel, but not on the non-OC

If you are running an OC kernel, connect your wifi to a network, then let the phone go to sleep


then try to make a call

i do not remember if it was on .11 or .7


p.s.

I have updated the .11 source to .14 on my github, if you want to try it
Click to expand...

B08 2.6.35.7oc connected to android forums let it fall to sleep then made a call. No problem wait. Mip error code 67
 
I don't think so... I think It did that to me on the no oc version but I'm not sure

Sent from my N860 using Tapatalk 2 Beta-5
 
this issue has got me kinda baffled

@Hroark13: I will download and build a new OC kernel from your updated source, I will do it later tonight im working on a new Boot ani. for the release of 1.5.1c
 
MrBobo said:
I think between firmware/hardware we will find the issue somewhere in the middle...

can you guys who have the OC working confirm your phone shows the same hardware revision as mine in the settings/about phone menu? c4tB

also, in voltage control under device info what do you see for the processor, does it match mine:

processor: armv7 processor rev 2 (v71)
Click to expand...

Downloaded voltage control just to check this, but yes I have exactly the same. Still working after over 48 hours of use with 2.6.35.7 oc. I am using No Frills CPU Control, stats show that I have been running at 1.6 for about 70% of the time the phone has been active since last boot. I have governor set for performance for now to see how long it will stay stable at 1.6.

As for any errors I experienced my first freeze up early today while playing Temple Run. I also had a random reboot early this morning while the phone was still on the charger could not find a reason for that. Other than those two hiccups I still have not had any other issues. WiFi working correctly, no signal drops, etc. As I stated previously though I have no way of testing vibration because the hardware for that has been broken for quite some time.

@jetx2x: I have been running oc kernel on B08c stock at 1.6 to answer your question. I bought my Warp on Black Friday of 2011.
 
@Hroark: I just now thought of this but maybe my OC is more stable because i build my kernels with the 4.4.0 Prebuilt toolchain from NDKr5c?

I'm not sure if that would make a difference but if it would then that's the answer.
 
I think i may have found the issue with signal loss while running my OC kernel. so far i havent lost signal with wifi enabled. but i dont want to jump the gun so i am not calling this solved yet. in addition it seems Hroarks audio fix DOES NOT work on ZTE's warp source.
 
shinru2004 said:
in addition it seems Hroarks audio fix DOES NOT work on ZTE's warp source.
Click to expand...

I have not tried building the new kernel source yet, I do not think I am going to. I am a bit tired of looking at kernel source, and gonna take a break for a while

I just can not believe that they released broken source code again, I just do not see the point in it
 
hroark13 said:
I have not tried building the new kernel source yet, I do not think I am going to. I am a bit tired of looking at kernel source, and gonna take a break for a while

I just can not believe that they released broken source code again, I just do not see the point in it
Click to expand...

I don't blame you and im about done with it too lol, oh the issue with signal loss on wifi was in cpufreq.c. i replaced it with the stock file and boom overclock still works and no more signal loss

next step is to declare new voltage for under/over volt
then trying to integrate GPU OC controls
 
You must log in or register to reply here.
Back
Top Bottom