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

Root [Kernel][Osiris][JB] Serenity kernel 3.4 OC

don't know, I isntalled screenshot ultimate and this is the way that it came out.

Now this one is from screenshoot from kastor soft

shot_000052.png

u kno the phn has a built in screen shot right??? lmao hold power button and volume up key for 3 seconds
 
So far so good with this kernel with working mic. Thanks Downthemachine for fixing this problem.

An update- so I let my 4 yr old play one of the games on the phone yesterday in the car (the one where he paints on trains and is getting chased by the security guard) Anyway, not sure if he happen to click on an ad or what not but about about 8-10min of him playing it, he started complaining that it doesnt work. I took the phone from him, it was still on the game app, but the phone was really hot. It was non responsive so I had to pop the cover off and remove the battery. Heat was from the battery and phone. Like I said, not sure exactly what happened, but I never felt a phone get that hot. Seem to be working fine still after that though :confused:
 
v0.3 - coming soon

v0.2 - fully stable build
Fixed mic
Added 5 governors
Couple other small fixes

v0.1 - Initial test build - not supported anymore
Built from agat's modified source which included smartassv2, lagfree govs and sio, vr I/O schedulers.
OC'd to 1.8ghz

quick question dtm, the test builds that animus and i were doing, the govs you add in v0.2 are those the ones you modified for the warp2 from agat's govs, i remember the one time you said you were going to modify the govs to work with the phone but cant remember if you did. I take this as yes just looking to verify. Remember I had problems with smartassv2 as well as animus lol is that good now?
 
So far so good with this kernel with working mic. Thanks Downthemachine for fixing this problem.

An update- so I let my 4 yr old play one of the games on the phone yesterday in the car (the one where he paints on trains and is getting chased by the security guard) Anyway, not sure if he happen to click on an ad or what not but about about 8-10min of him playing it, he started complaining that it doesnt work. I took the phone from him, it was still on the game app, but the phone was really hot. It was non responsive so I had to pop the cover off and remove the battery. Heat was from the battery and phone. Like I said, not sure exactly what happened, but I never felt a phone get that hot. Seem to be working fine still after that though :confused:


Same here, but I was testing the different governors with AnTuTu when the phone start getting hot, but instead of non responsive it was rebooting every time was trying to run the tests, so, left it alone for like an hour and then start the tests again and after the 5th or 6th test in a row, start it to get hot again and rebooting. Maybe 1.8ghz is too much for this beast :)
 
List bugs like this:
Freq max:
Freq min:
Governor:
I/O scheduler

That way I can look at where an issue might be
 
It would be best on any CPU control app to clear the apps data and cache from settings. Normally I would have you clear dalvik and normal cache in cwm when installing but cwm doesn't work right
 
aight dtm im testing this puppy along with the build.prop tweaks sean82007 posted lets see how my new zte warp sequent performs i'll post if any errors with it
 
If I may make a suggestion us og warp users have the same processor I only use 1.8 for bench marking and when needed only. I drop it down to the 1.4ghz for most things. You need to test the io and gov to see what the best combos are.
 
can someone post a screenshot from quadrant benchmark im not familiar with antutu and want to see how it compares to other phones. I plan on getting this phone in the future
 
i have installed all the adb sdk drivers but still cant get my pc to recognize my phone while in bootloader screen. it is important it does because i am without ftm or recovery modes. i have tried every driver iv found and none of them re working... please help. been this way for days
 
Same here, but I was testing the different governors with AnTuTu when the phone start getting hot, but instead of non responsive it was rebooting every time was trying to run the tests, so, left it alone for like an hour and then start the tests again and after the 5th or 6th test in a row, start it to get hot again and rebooting. Maybe 1.8ghz is too much for this beast :)

I haven't had an issue running this device at 1.8Ghz, It doesn't even get hot for me. i have had pretty good luck with devices made by ZTE. I guess i get the best of the bunch lol. i scored 4318 on Antutu which isnt to bad for having very very few tweaks done to the device. Once we have CWM expect a full on release of my rom with a much much higher score.
 
ZTE is famous for releasing broken source code and not owning up to their obligations of "OPEN SOURCE"
 
I wanted to put this kernel on my phone but cant find a cwm recovery link(that is working) to flash your kernel.

UPdate: nvrmind i flashed it using cmd sooooo easy after you go through all the trouble.
 
im having a problem. i cant get adb to see my phone in bootloader mode so i tried,

C:\>fastboot devices
811bdd48 fastboot

C:\>fastboot flash boot boot.img
sending 'boot' (4556 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.609s]
finished. total time: 1.016s

C:\>fastboot reboot
rebooting...

finished. total time: 0.000s

problem is that whe it reboots it boots right back the same way it was before i flashed. telling me its not working. i tryed with stock as well and got the same thing. any advice or suggestions on how to get this working would be great
 
adb doesnt work in bootloader mode, only fastboot, so that explains that. but what is telling you its not working? i cant fastboot a damn thing so youll have to bare with me here but if you explain how you know its not working i may be able to help
 
im having a problem. i cant get adb to see my phone in bootloader mode so i tried,

C:\>fastboot devices
811bdd48 fastboot

C:\>fastboot flash boot boot.img
sending 'boot' (4556 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.609s]
finished. total time: 1.016s

C:\>fastboot reboot
rebooting...

finished. total time: 0.000s

problem is that whe it reboots it boots right back the same way it was before i flashed. telling me its not working. i tryed with stock as well and got the same thing. any advice or suggestions on how to get this working would be great

Are you sure it didn't work? Go to system settings about phone kernel. What does it say?

Sent from my N861 using Tapatalk 2
 
so i tried flashing the kernel a bunch of times and seemed to just boot with the normal kernel but i just checked and some how after days of the phone being with the normal kernel magically changed to the one i flashed weird but no bs. maybe its because i formatted the phone (did not work). the phone just booted to normal and did not feel like loosing my stuff using the update tool so left the phone alone... now i have the new kernel... any theories??
 
umm, how do you know you have the new kernel? the only way to really tell is to install an overclocking software like cpumaster. if the software wont overclock then you dont have the new kernel, if it will then you do. this is basically just a small collection of tweaks, its not gonna really change anything noticable except the ability to overclock
 
Do you need to root phone before using this?

edit: I need cwm it seems.

as for this, no rooting is not necessary, and clockworkmod is not necessary either. you can fastboot it the same way you would install clockwork mod by removing it from the zip file, and doing

fastboot flash boot (kernelimage).img

as apposed to

fastboot flash recovery (cwmimage).img

also root is not required for cwm or for this kernel, but this kernels main feature requires root to actually use (overclocking)
so installing it without root seems kinda pointless if you ask me

just keep this in mind when overclocking this phone
the stock os uses alot of resources by itself, setting the phone up to run at anything over 1.4ghz on demand will almost certainly make it run at whatever you set as the maximum at all times, making the phone very hot, the battery go very quickly, and if you use it for a long duration like that will almost certainly break it
should you leave overclocking on, and the phone shuts off suddenly without warning or good reason, disable automatic overclocking next time and dont use it unless you actually need it. should it fail to turn back on after that, quickly motion your palm towards your face, and get a new phone
 
Back
Top Bottom