5,595,964 Members 31,498 Now Online
XDA Developers Android and Mobile Development Forum

Smartreflex - how to improve the algorithm

Tip us?
 
osm0sis
Old
(Last edited by osm0sis; 27th January 2013 at 04:09 AM.)
#11  
osm0sis's Avatar
Recognized Contributor
Thanks Meter 11457
Posts: 6,778
Join Date: Mar 2012
As I've always seen it, the limitations/problems with SmartReflex are as follows:

- Can't calibrate to a lower voltage than 830mV (problematic when 384MHz generally does fine at 775mV and 192MHz generally does fine at 725mV).

- Does not handle frequencies above 1305 well at all (calibrates them the same as 1228, so it must be an upper limit to its bracketing/range, almost as though it sees it as the same as 1228).

- Could definitely be a bit more aggressive safely when everyone can UV the SR values by another 50-100mV (so I'd say another 50mV safely across the board).

No idea how to proceed on any of those, but I thought it might help to make the limitations a bit more clear. I'm looking forward to following the progress of this thread. Great idea, Francisco.
I do NOT answer technical questions via PM. Post your question in the correct thread if you want a response.




The Following 4 Users Say Thank You to osm0sis For This Useful Post: [ Click to Expand ]
 
Ashtrix
Old
#12  
Ashtrix's Avatar
Senior Member
Thanks Meter 251
Posts: 1,081
Join Date: Dec 2010
Location: Milky Way
Thumbs up Smartreflex improvement

Quote:
Originally Posted by osm0sis View Post
As I've always seen it, the limitations/problems with SmartReflex are as follows:

- Can't calibrate to a lower voltage than 830mV (problematic when 384MHz generally does fine at 775mV and 192MHz generally does fine at 725mV).

- Does not handle frequencies above 1305 well at all (calibrates them the same as 1228, so it must be an upper limit to its bracketing/range, almost as though it sees it as the same as 1228).

- Could definitely be a bit more aggressive safely when everyone can UV the SR values by another 50-100mV (so I'd say another 50mV safely across the board).

No idea how to proceed on any of those, but I thought it might help to make the limitations a bit more clear. I'm looking forward to following the progress of this thread. Great idea, Francisco.
So you mean the Lean's 1.6Ghz SR does also do the same, 1.6GHz calibrates as 1.2GHz range instead of the real application ??
and it would be great if we could overcome the 2nd limitation .

[Kernel] -Testing-
[Device] Nexus Prime
[ROM] SlimKAT 4.4.2 -- v4.4
[Recovery] PhilZ_Touch v6.12.8 CWM
[Bootloader] - PrimeLC03
[Baseband] - XXLA2

[Old devices] -- iPhone 2G > Droid > Galaxy S
Hit thanks if anyone had helped you !

 
osm0sis
Old
(Last edited by osm0sis; 27th January 2013 at 03:46 PM.)
#13  
osm0sis's Avatar
Recognized Contributor
Thanks Meter 11457
Posts: 6,778
Join Date: Mar 2012
Most kernels (probably all but I haven't personally checked) disable SR for frequencies above 1305, but yes I believe that's why it doesn't work. Franco used to have the cutoff for SR be voltage based and on my device 1536 UV's by 100mV stably, so if I left SR on and lowered it too much (75mV) SR would act on it and calibrate it to the same voltage as 1228, which of course was too low and froze and crashed. So yeah, its as though it needs new brackets/ranges added for higher voltages.
I do NOT answer technical questions via PM. Post your question in the correct thread if you want a response.




 
blackhand1001
Old
#14  
blackhand1001's Avatar
Senior Member
Thanks Meter 682
Posts: 1,264
Join Date: Sep 2011

 
DONATE TO ME
Has amazon released the kernel source for the kindle fire hd 8.9? That uses a ti omap clocked at 1.5ghz stock. Maybe a look at the smart reflex code on that would shed some light.
Current: VZW Moto X Dev Edition
Extra (previous): Galaxy Nexus LTE - CM10.2
Droid Incredible AMOLED - CM7.2
Father: HTC Rezound - Stock Rooted
The Following 4 Users Say Thank You to blackhand1001 For This Useful Post: [ Click to Expand ]
 
osm0sis
Old
#15  
osm0sis's Avatar
Recognized Contributor
Thanks Meter 11457
Posts: 6,778
Join Date: Mar 2012
Quote:
Originally Posted by supernova_00 View Post
I might be pointing out the obvious here but sometimes the obvious isn't so obvious...has anyone contacted Nishanth Menon that is named in the code header to see if TI has a latest and greatest SR? I would assume they would since phones are coming out now with higher CPU speeds then what the current SR could handle around two years ago. I see the guy is pretty active online with posting stuff to open source sites and still deals with smart reflex related things as this site shows: http://marc.info/?a=124043331500007&r=1&w=2
I dunno what that site is or know what any of that stuff means but I just stumbled upon it and just wanted to show he is active with TI and smart reflex work, among other things
Quote:
Originally Posted by blackhand1001 View Post
Has amazon released the kernel source for the kindle fire hd 8.9? That uses a ti omap clocked at 1.5ghz stock. Maybe a look at the smart reflex code on that would shed some light.
Both good ideas!
I do NOT answer technical questions via PM. Post your question in the correct thread if you want a response.




 
Ashtrix
Old
(Last edited by Ashtrix; 28th January 2013 at 10:07 AM.)
#16  
Ashtrix's Avatar
Senior Member
Thanks Meter 251
Posts: 1,081
Join Date: Dec 2010
Location: Milky Way
Quote:
Originally Posted by osm0sis View Post
Most kernels (probably all but I haven't personally checked) disable SR for frequencies above 1305, but yes I believe that's why it doesn't work. Franco used to have the cutoff for SR be voltage based and on my device 1536 UV's by 100mV stably, so if I left SR on and lowered it too much (75mV) SR would act on it and calibrate it to the same voltage as 1228, which of course was too low and froze and crashed. So yeah, its as though it needs new brackets/ranges added for higher voltages.
According to SR v1 by Imoseyon & his explanation says he had modified the SR code to override the below limits
1) VDDMIN - 830mV for all three domains,
2) VDDMAX - 1410mV for MPU, 1260mV for IVA, and 1200mV for CORE.

So, i think do already have a better version of SR over the TI's stock SR from Lean but only a few phones can handle the SR calibration for the 1.5+ GHz freq .

[Kernel] -Testing-
[Device] Nexus Prime
[ROM] SlimKAT 4.4.2 -- v4.4
[Recovery] PhilZ_Touch v6.12.8 CWM
[Bootloader] - PrimeLC03
[Baseband] - XXLA2

[Old devices] -- iPhone 2G > Droid > Galaxy S
Hit thanks if anyone had helped you !

The Following User Says Thank You to Ashtrix For This Useful Post: [ Click to Expand ]
 
blackhand1001
Old
#17  
blackhand1001's Avatar
Senior Member
Thanks Meter 682
Posts: 1,264
Join Date: Sep 2011

 
DONATE TO ME
Default Re: Smartreflex - how to improve the algorithm

Quote:
Originally Posted by Ashtrix View Post
According to SR v1 by Imoseyon & his explanation says he had modified the SR code to override the below limits
1) VDDMIN - 830mV for all three domains,
2) VDDMAX - 1410mV for MPU, 1260mV for IVA, and 1200mV for CORE.

So, i think do already have a better version of SR over the TI's stock SR from Lean but only a few phones can handle the SR calibration for the 1.5+ GHz freq .
That's because it doesn't seem to actually calibrate properly for 1.5ghz. That's why I suggested looking at device like the kndl fire hd 8.9 which is 1.5 GHz stock. TI most likely modified the smartreflex code to work with that frequency.

Sent from my Galaxy Nexus using xda premium
Current: VZW Moto X Dev Edition
Extra (previous): Galaxy Nexus LTE - CM10.2
Droid Incredible AMOLED - CM7.2
Father: HTC Rezound - Stock Rooted
The Following 3 Users Say Thank You to blackhand1001 For This Useful Post: [ Click to Expand ]
 
Charmacas
Old
#18  
Charmacas's Avatar
Senior Member
Thanks Meter 699
Posts: 967
Join Date: Jan 2010
Location: Hamburg
Did you guys already give up the discussion or is there nothing more to discuss?

Sent from my Galaxy Nexus with Tapatalk 2
Actually (26.03.2014) using SlimKat 3.10 with Fancy kernel on my Galaxy Nexus (Maguro)

My Trickster Settings (Freshest status and some explanations!)

If you have questions, don't hesitate to ask me.
<<< If I was able to help, don't forget to hit the thanks button.
The Following 2 Users Say Thank You to Charmacas For This Useful Post: [ Click to Expand ]
 
MWisBest
Old
(Last edited by MWisBest; 18th August 2013 at 08:59 AM.)
#19  
Senior Member
Thanks Meter 875
Posts: 330
Join Date: Dec 2010
Location: Green Bay, WI

 
DONATE TO ME
The Kindle Fire has source code released: http://www.amazon.com/gp/help/custom...deId=200203720

Inside the downloaded tar are multiple tars, the kernel is in omap.tar

There appears to be a few difference in the SR code, but it doesn't look like much. EDIT: This was through a simple compare of the 1p5 file, I'll check the other possibly relevant files.

EDIT2: Yeah I didn't notice much of a change in the SR stuff, however I'm not as familiar with this code as some other people here might be, so don't trust my judgement!
VZW Galaxy Nexus (Current):
FML-4.4

LG Vortex (x2) (Retired):
CM-9.0
The Following 2 Users Say Thank You to MWisBest For This Useful Post: [ Click to Expand ]
 
Maromi
Old
#20  
Maromi's Avatar
Senior Member
Thanks Meter 133
Posts: 204
Join Date: Jul 2012
some users were able to run 4460 @1.5GHz with smartreflex enabled. luckily Hashcode had one too and did this http://forum.xda-developers.com/show...5&postcount=93
Amazon Kindle Fire HD 7" (tate)
Recovery: TWRP 2.6.3.1 KFire HD7 Holo Glass
ROM: Unoffical CyanogenMod 11 20140325
Kernel: Linaro 4.7.4 CPU=1.728 GHz GPU=512 MHz

Samsung Galaxy S II (d710)
Recovery: CWM 6.0.4.6
ROM: Official CyanogenMod 10.2 Nightly 20140330
Kernel: CyanogenMod 10.2
Modem: FL24

The Following User Says Thank You to Maromi For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes