[KERNEL & ROM] [RAY] Ray / Stock-based: kernel/rom Repack by 4pda.ru team

[toycz]

rom and kernel install fine. rom is fast stable and reliable, has many languages as stock. Great job done woth kernel. Battery lasts much longer than any other kernel a tried. Best rom and kernel combination. thnaks for your hardwork you made my device even better

 

[[GER]Roxxor]

Is it possible to create a flashable ZIP including the kernel?
From other devices I`m used to flash ZIPs only and to be independent of a computer :/
LG Roxxor

 

[8f86TcLjmt]

Thx for this great kernel and rom.

By default kernel is undervolted, governeur is SmartassV2, CPU is not overclocked. And there are no settings to change it in this Rom, right? (No big deal, just to be sure.)

In CM7 it´s possible that LED blinks even when display is on (for missed calls, calender events etc.). I really like this. In Stock Rom display has to be off for blinking, same in this Rom. May be this CM7 feature can be integrated?

And I´m really not sure (can´t believe my eyes^^), but is the LED darker than in CM7?

 

[ImmortAlex]

Is it possible to create a flashable ZIP including the kernel?

AFAIK, it's not possible on Ray, it is design limitation. Also, CWM doesn't backup kernel by the same reason.

By default kernel is undervolted, governeur is SmartassV2, CPU is not overclocked. And there are no settings to change it in this Rom, right? (No big deal, just to be sure.)

You can change governeur and overclock you phone with tools like SetCPU. Also, you can edit file /etc/init.d/Scpufreq - that settings are applied on boot. Be careful and read comments in this file!
Undervolting is not configurable on-the-fly. This may change in future kernel versions.

 

[37_]

I confirm the battery drain with doomlord kernel is very very very fast, even in flight mode without any activities and default clock of 1 ghz

now I will try your kenel

this kernel is much more battery friendly, droped only 3 percent overnight in flight mode without any activities; with doomlord (same clock setting and govervor), it was 1% per hour

 

[KristianKenneth]

do we need an unlocked bootloader to do this?

 

[hansip87]

do we need an unlocked bootloader to do this?

Yes. Anything about changing Kernel is always about unlocking bootloader. and because the ROM is optimized for the attached kernel, it is needed.

@OP: At last i make myself to be brave and unlock the bootloader without losing DRM, and applying your kernel and it is superb to say the least. Thank you so much.

 

[KristianKenneth]

Yes. Anything about changing Kernel is always about unlocking bootloader. and because the ROM is optimized for the attached kernel, it is needed.

@OP: At last i make myself to be brave and unlock the bootloader without losing DRM, and applying your kernel and it is superb to say the least. Thank you so much.

I saw the process of unlocking bootloader w/o losing DRM and it looks difficult, can we apply this by just unlocking through SE method?

 

[[SIC]]

I saw the process of unlocking bootloader w/o losing DRM and it looks difficult, can we apply this by just unlocking through SE method?

Well yes, an unlocked bootloader is an unlocked bootloader which means that you can use fastboot to flash custom kernels. I've heard good things about the zergrush(?) method being noobfriendly.

Sent from my Ray S

 

[djkah11]

I saw the process of unlocking bootloader w/o losing DRM and it looks difficult, can we apply this by just unlocking through SE method?

SE method isn't easy and you lose DRM with the method. The method of crack bootloader is better than official method.

 

[ImmortAlex]

I saw the process of unlocking bootloader w/o losing DRM and it looks difficult, can we apply this by just unlocking through SE method?

Unofficial method is much simplier than SE one

 

[hansip87]

I saw the process of unlocking bootloader w/o losing DRM and it looks difficult, can we apply this by just unlocking through SE method?

Yes you can, but it erases the DRM keys. Once lost you can't go back to have it again. You can relock but the DRM is lost forever.

The S1 Tool method is not that dificult, you can follow the original tutorial. Don't mind about connecting between test point as a hard thing, in fact, just using paper clip and bam you got it If confused, you can follow my tutorial http://forum.xda-developers.com/showthread.php?t=1426912

 

[vleutmans]

just some findings

@4PDA.ru /aire

I now use this kernel but found the default smartassV2 governor a little "nervous", as it's upping the clock more often than with on-demand governor.

So I set on-demand governor on this one (hopefully saves battery?) and see what happens.

Furthermore I see that the kernel supports NOOP and deadline (= the default io-scheduler). Are there any future plans for implementing SIO,CFQ,BFQ or other schedulers too? Not sure if we "could" benefit a lot as deadline scheduler seems quite good at the moment though

Battery life is OK with this kernel, but I still have to recharge every day without much phone usage. Powertime widget tells me the battery lasts about 23 hours.
I wonder if it's possible anyway to get more battery life out of the Ray, as the CPU is already undervoltaged and most of the time in deep-sleep. I suspect other hardware modules (BT,CDMA/GSM) of the phone itself causes more battery drain, than our CPU.

 

[ImmortAlex]

I now use this kernel but found the default smartassV2 governor a little "nervous", as it's upping the clock more often than with on-demand governor.

So I set on-demand governor on this one (hopefully saves battery?) and see what happens.

It depends on your typical phone usage. Personally, I do not see any difference between this two governors, but I do not test too deeply.

Battery life is OK with this kernel, but I still have to recharge every day without much phone usage. Powertime widget tells me the battery lasts about 23 hours.
I wonder if it's possible anyway to get more battery life out of the Ray, as the CPU is already undervoltaged and most of the time in deep-sleep. I suspect other hardware modules (BT,CDMA/GSM) of the phone itself causes more battery drain, than our CPU.

There are several options:
1. May be your phone doesn't go to deep-sleep, because of some background application. There are number of system utilities an methods to check this situation. Check out corresponding topics.
2. Some users have problems with battery calibration. Check out corresponding topics again .
3. Definitely BT, WiFi and 3G eats energy. I switch them on only when I need to use them. And GPS too. And switch airplane mode on when I go to bed That switches in notification area included in repack4pda are very helpful!
Also, even in 2G mode GSM module can eat more energy in locations with bad signal level.

So my Ray can easily live for three day with
- about 30 minutes of talks (yeah, I'm not very talkative)
- 5 to 10 SMS messages (yeah, I'm not a schoolboy)
- number of software upgrades from Market (yeah, I'm 0-day geek)
- finally, everyday Titanum backup (yeah, that geek has some bad expirience).

And may live more, but I feel nervous with energy level lower than 50%

 

[djkah11]

Which of usb-flashdrive are support kernel?What is the maximum volume ana type?

 

[hansip87]

@4PDA.ru /aire

I now use this kernel but found the default smartassV2 governor a little "nervous", as it's upping the clock more often than with on-demand governor.

So I set on-demand governor on this one (hopefully saves battery?) and see what happens.

Furthermore I see that the kernel supports NOOP and deadline (= the default io-scheduler). Are there any future plans for implementing SIO,CFQ,BFQ or other schedulers too? Not sure if we "could" benefit a lot as deadline scheduler seems quite good at the moment though

Battery life is OK with this kernel, but I still have to recharge every day without much phone usage. Powertime widget tells me the battery lasts about 23 hours.
I wonder if it's possible anyway to get more battery life out of the Ray, as the CPU is already undervoltaged and most of the time in deep-sleep. I suspect other hardware modules (BT,CDMA/GSM) of the phone itself causes more battery drain, than our CPU.

have you tried to recalibrate your battery? i know you're not changing ROM but nothing to lose right? And yeah, i already found a correct way to recalibrate the battery. You cannot just delete the battery_stats.bin, you need to do it from recovery then do a full recharge. Because if you delete it when the phone is online, the copy of old battery_stats.bin still remains in RAM so it won't affect the battery.

 

[8f86TcLjmt]

...
In CM7 it´s possible that LED blinks even when display is on (for missed calls, calender events etc.). I really like this. In Stock Rom display has to be off for blinking, same in this Rom. May be this CM7 feature can be integrated?

And I´m really not sure (can´t believe my eyes^^), but is the LED darker than in CM7?

Because I didn´t get any answer on questions above I tried myself...

So, LED in stock rom and this rom are much darker than in CM7. LED is configured in /sys/class/leds. There are folders for blue, green and red led. I didn´t understand all settings (maybe some dev can explain) but changing the max_current value makes the leds brighter. You have to set it for all 3 colors. I don´t know what values are possible. I tried 20000 for all colors and led was much brighter than in stock rom. But it was much too red. So i tried to change values according to their original (R/G/B - 2400/4200/3000) to 12000/21000/15000 with good results. Still searching for best values.

BUT sadly, after reboot all values are back to original. So I edited hw_config.sh and added following lines:

echo 7000 > $dev/red/max_current
echo 16800 > $dev/green/max_current
echo 12000 > $dev/blue/max_current

And now it works

But I didn´t find a solution for blinking led while screen is on.

May be someone can help.

P.S.: I really don´t know what I´m doing. So try at your own risk.

3rd edit: Tested many values and looked into CM7 values (which are wrong ). These are really good on my ray:
R/G/B=7000/20000/20000. (Hopefully last edit. )

 

[coolkaas]

this is a very good finding! thanx.


btw, we have init.d for this things, 'native' init.d)))


ps. I try, this works, my led is not white with your values but slight pinkish. So, this doesn't matter, your method works. As we know, all leds is some differ one by one. Very very thanx!

 

[pepbcn]

To the creators: is it possible to activate the native SIP settings of Gingerbread? I'm able to access to them, but they don't work.

Thanks for the work

 

[*boy*racer*]

Because I didn´t get any answer on questions above I tried myself...

So, LED in stock rom and this rom are much darker than in CM7. LED is configured in /sys/class/leds. There are folders for blue, green and red led. I didn´t understand all settings (maybe some dev can explain) but changing the max_current value makes the leds brighter. You have to set it for all 3 colors. I don´t know what values are possible. I tried 20000 for all colors and led was much brighter than in stock rom. But it was much too red. So i tried to change values according to their original (R/G/B - 2400/4200/3000) to 12000/21000/15000 with good results. Still searching for best values.

BUT sadly, after reboot all values are back to original. So I edited hw_config.sh and added following lines:

echo 7000 > $dev/red/max_current
echo 16800 > $dev/green/max_current
echo 12000 > $dev/blue/max_current

And now it works

But I didn´t find a solution for blinking led while screen is on.

May be someone can help.

P.S.: I really don´t know what I´m doing. So try at your own risk.

3rd edit: Tested many values and looked into CM7 values (which are wrong ). These are really good on my ray:
R/G/B=7000/20000/20000. (Hopefully last edit. )

Mate this is wicked. I now have pure blue as my default led when soft keys are touched.

Thanks man.

Sent from my ST18i using xda premium