FORUMS

Analysis & Opinion

Top Forum Discussions

[KERNEL][19FEB] SiyahKernel v6.0b5

3,744 posts
Thanks Meter: 25,757
 
Post Reply Subscribe to Thread Email Thread
5th May 2012, 06:19 PM |#7681  
ChilliBo's Avatar
Senior Member
Flag Cologne
Thanks Meter: 346
 
Donate to Me
More
Quote:
Originally Posted by Cristiano Matos

NStools from Google play.

same result,

status: enabled,
LED Timeout: 0 sec
CMLED Timeout 0 sec

BLN doesnt work when sms recieved or missed calls...
 
 
5th May 2012, 06:22 PM |#7682  
Senior Member
Flag Lisbon
Thanks Meter: 70
 
Donate to Me
More
Quote:
Originally Posted by ChilliBo

same result,

status: enabled,
LED Timeout: 0 sec
CMLED Timeout 0 sec

BLN doesnt work when sms recieved or missed calls...

Using CM9 and only extweaks, in my case, bln is workin with missed calls and received sms
5th May 2012, 06:24 PM |#7683  
ChilliBo's Avatar
Senior Member
Flag Cologne
Thanks Meter: 346
 
Donate to Me
More
Quote:
Originally Posted by PedroMRP

Using CM9 and only extweaks, in my case, bln is workin with missed calls and received sms

using VK rom as u can see in my signature, using latest siyah 3.2b7 and extweaks, but missed calls and sms doesnt work :/ doesnt work with nstools too. but whatsapp works ...
5th May 2012, 06:25 PM |#7684  
Cristiano Matos's Avatar
Senior Member
Flag Nibiru
Thanks Meter: 11,855
 
More
Quote:
Originally Posted by ChilliBo

same result,

status: enabled,
LED Timeout: 0 sec
CMLED Timeout 0 sec

BLN doesnt work when sms recieved or missed calls...

Still with BLN control? I If yes, try to uninstall and reboot into recovery and reset extweaks profile.
Reboot and configure extweaks again.
The Following User Says Thank You to Cristiano Matos For This Useful Post: [ View ]
5th May 2012, 06:45 PM |#7685  
bleuxeon's Avatar
Senior Member
Flag Near COGNAC (FR)
Thanks Meter: 264
 
More
Quote:
Originally Posted by tolis626

Gok,strange problem here.I tried to make a nandroid backup(a normal one,not of the secondary rom) and after backing up data it gave me an error message saying that there was an error when backing up .secondrom/data or something.Dafuq?

EDIT:What chance is there that the kernel panics I was and am still getting(although not nearly as often now) are related to overclocking while having changed the internal voltages?
With a little higher that stock internal voltages,my phone is much stabler than it was with low voltages at high frequencies,but if kernel panics are related to that in any way,I will return to my previous quasi-unstable setup.

Could you please give me a sample voltage you did use at a given frequency and the same frequency voltage now with increased internal voltage?
5th May 2012, 07:17 PM |#7686  
Senior Member
Thanks Meter: 552
 
More
Quote:
Originally Posted by ChilliBo

BLN works with EXTweaks but not for sms or missed calls, tried with extweaks and bln pro... doesnt work.. any fix for that?? (3.2b7)

how many times does this have to be repeated? There's a search function for every thread. If it works on one place it's not kernel related. If you want bln for sms use gosms or smspopup. For calls install nstools.
Your screen has to stay off when you receive a sms.
Sent from my GT-I9100 using xda premium
Last edited by rauschkugl; 5th May 2012 at 07:19 PM.
5th May 2012, 07:28 PM |#7687  
ChilliBo's Avatar
Senior Member
Flag Cologne
Thanks Meter: 346
 
Donate to Me
More
Quote:
Originally Posted by Cristiano Matos

Still with BLN control? I If yes, try to uninstall and reboot into recovery and reset extweaks profile.
Reboot and configure extweaks again.

doesnt work
5th May 2012, 07:38 PM |#7688  
squall458's Avatar
Senior Member
Flag Brampton
Thanks Meter: 27
 
Donate to Me
More
I am on vk rom too! I struggled for weeks to get bln to work. This is how u solve our prob. If the screen turns on when u receive a txt bln will not work. So use sms popup or go sms and disable notifications from stock messaging app. Sms popup has a setting where the screen will NOT turn on. It also will handle the notifications. Problem solved.

Sent from my GT-I9100 using XDA
The Following User Says Thank You to squall458 For This Useful Post: [ View ]
5th May 2012, 07:54 PM |#7689  
Senior Member
Flag Moscow
Thanks Meter: 19
 
More
Quote:
Originally Posted by ChilliBo

using VK rom as u can see in my signature, using latest siyah 3.2b7 and extweaks, but missed calls and sms doesnt work :/ doesnt work with nstools too. but whatsapp works ...

Missed calls & SMS both work with 3.2b7 using nstools & Milestone 5 rom. Deep sleep also works if you don't have any notifications.

Sent from my GT-I9100 using xda premium
Last edited by steve17360; 5th May 2012 at 07:58 PM.
5th May 2012, 07:55 PM |#7690  
Senior Member
Thanks Meter: 57
 
More
Trigger the led with Tasker when you gave a missed call or sms...

Sent from my SGSII CM9 with Tapatalk 2
5th May 2012, 08:04 PM |#7691  
droidphile's Avatar
Senior Member
Flag Bangalore
Thanks Meter: 7,073
 
More
Quote:
Originally Posted by AndreiLux

As said, ondemand based governors do not visit steps so in an ideal situation there will be no increased transitions at all; if the governor decides to stay at the same frequency. But I doubt this is a real-world situation, the governor would jump either way or another to another frequency unless under heavy load. You have a transition time of 100ÁS compared to a default sampling rate of 100000ÁS or minimum 20000ÁS so we are talking about a loss of computing time two orders of magnitude smaller than a sampling period, versus a possible power gain in clocking of in the most optimistic case of 50% and worst case 7%.

I was thinking of only the time as summed up sampling intervals of each frequencies, rather than transition time of a mere 100uS. That make sense for a large frequency table. But if an heavy op was to be considered where freq has to stay really high, tightness of freq table doesn't matter. Table is big or small, it's all the same. We're talking w.r.t power gain and not performance gain right.
Quote:
Originally Posted by AndreiLux

I did not say they jump to the highest frequency too much, they jump as much as they need to. You have smoothing of load spikes through larger sampling periods and as you said through smooth scaling. I think interactive governors are a bad choice for this device and I haven't seen the point in using them; they may be good for battery use but the lags they introduce even with a tight frequency table is too noticeable for my taste. Use a smaller frequency table for all you want and then use them and disregard the whole discussion. I will be sticking with ondemand though. Frequency steps in the GS3 have no correlation with the number of cores, so I don't know why you'd bring that up, it doesn't change anything in terms of scaling, as in that regard Pegasus has the same logic as classic ondemand.

I'm not using interactive governors either, but ondemand. Anyway original interactive governor doesn't lag compared to smartass2 or luzactive. I brought GS3 just to say that pegagusq should handle a large freq table better. As in, there's a better chance for a freq F and F*2 to exist in a large freq table - When a multi core aware governor tries to hotplug in second core by setting a frequency F instead of clocking at F*2. I'm not here to upset anyone or disregard discussion. Even though i have no ammeters, i'm also an enthusiast always looking to learn more.
Quote:
Originally Posted by AndreiLux

100mV is almost guaranteed for 100 and 200MHz, the rest depends on the device. I wrote it just as an example of measurement, it's up to the user to decide what to do with it. I also measured underclocking and undervolting GPU, it has almost not measurable difference in light load. The Mali GPU also has internal power management that I think clock-gates part of the digital core when under low load, you can see this in the drivers. Undervolting GPU under load in games will bring a big decrease in power though, undervolting 200mV will bring down the total power consumption down 15% (that includes the whole device, screen on, CPU locked at 800), so the percentage is even greater I one would be able to solely measure the GPU.

Hmm, there are devices which doesn't guarantee 100mv UV on lower freqs. You said it yourself - under heavy GPU load, GPU UV could bring in power savings. If someone is into tasks that involves a lot of GPU, the best they can do is uv GPU and reduce screen brightness.
Quote:
Originally Posted by AndreiLux

I don't see what you want to say. The W/GHz value is only a theoretical calculation derived from his measurements under full load which is not realistic in a low load scenario. For playing music our devices don't even hit deep idle, ever. At least mine didn't, no matter what frequency you'd be playing music at, 100, 200 or 500MHz, the load is too fine-grained to let the CPU enter any clock-gating. There is no case in which 100MHz stays at high load because the governor will simply up the frequency and that situation will never realistically happen.

I didn't say device can hit didle while playing music. What i meant to say was - a) CPU idling on screen off - we're bound to hit didle very soon. So what's the point of using 100 instead of 200. b) CPU idling on screen on - How many tasks are there where CPU can stay low loaded at 100mhz. Like you say, 100% load on 100 mhz is not possible since governor will jump it to higher freqs. Then why use 100.
Quote:
Originally Posted by AndreiLux

Static power consumption is completely irrelevant in our device, it varies from 55mW to 60mW from 200MHz to 1400MHz. I'm getting the best W/GHz measurements at 800MHz so 800 is more efficient than 500.

800 may be sweet. But atleast, dynamic power consumption increases about 60% between 500 and 800 mhz. So 500mhz or lower running single core during screen-off is not bad.
Quote:
Originally Posted by AndreiLux

500MHz uses up 488mW power in screen-on idle versus 400mW for 200MHz, so you're wasting almost 20% power for "snappiness", which I honestly don't get since when you touch the screen it clocks to 500MHz anyway...

We can skip a transition if min is 500. Since every screen touch clocks CPU to 500, if an usage scenario involves too much of screen-touches, what's the point of having a frequency step below it. I like 500-1200 with 200-500 scr-off. Another thing to note is that 500mhz uses the core voltage of 800mhz if 500 was clocked from a frequency below it. And uses it's own core voltage if frequency was clocked from a frequency above it(500). When i'm using 500 as minimum, after a clock-up, 500 could be met only by clocking down from a higher frequency. This means i will have core voltage of 500 itself whenever it's used. This is not true if scr-on min was 200. So there's some power saving from one side when there's power dissipation on the other.

Past midnight here. Good night.
The Following 4 Users Say Thank You to droidphile For This Useful Post: [ View ]

Read More
Post Reply Subscribe to Thread

Tags
battery life, cwm touch 6.0.1.1, dualboot, extweaks with sound booster, ics, jelly bean, kernel that walk in the path of heaven, legendary, stable, stweaks
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes