Database Develop

Why my cpuinfo is wrong?

Hi, I would want to ask a developer, why my cpuinfo show me that i have only one processor?
Sent from my LG-P990 using XDA App

Marsou77 said:
Hi, I would want to ask a developer, why my cpuinfo show me that i have only one processor?
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
It shows both your processors just fine...
See, there is proccesor 0, and processor 1. The naming might seem a tad strange, but that's because of how data formats work

My Atrix show me that it have 2 and my mini x10 pro show me that it have 1...
So, WTF ?

Marsou77 said:
My Atrix show me that it have 2 and my mini x10 pro show me that it have 1...
So, WTF ?
Click to expand...
Click to collapse
I don't get what you mean... They are both obviously showed in you cpuinfo.

Well... first, sorry for my English and I try to do my best... second, I want to know why, my Atrix show me that it have 2 processors in CPUinfo (which is powered by NVidia too) so that my 2X show me 1... because 0 mean nothing, not existing, ok ? I find it very strange...
Btw, I change the value to 2, i'm wrong ?

You fool
It is enumeration which starts at 0 and continues to 1... and 2.. and so on
If you'll have 4 processors (or cores) you'll have here CPU 0, CPU 1, CPU 2, CPU 3...

Thanks for your answers... but another one for the way
How do you make any difference between devices which show in the CPUinfo 0 for 1 core and 1 for 2 cores (like ours 2x) and devices which show in the CPUinfo 1 for 1 core and 2 for 2 cores (like my Atrix)
I think it's a little confused but it's understandable

Marsou77 said:
Thanks for your answers... but another one for the way
How do you make any difference between devices which show in the CPUinfo 0 for 1 core and 1 for 2 cores (like ours 2x) and devices which show in the CPUinfo 1 for 1 core and 2 for 2 cores (like my Atrix)
I think it's a little confused but it's understandable
Click to expand...
Click to collapse
It's implemented somewhere in the kernel code, and could be changed by adding "+1" to a line or something like that

This came from Linux kernel. You get from kernel structure CPU enumeration which starts at 0 and it is on your own how to interpret it. This seems Motorola kernel interpret it in "human readable" form, in other kernel it is interpreted in "machine readable" form. Both are correct indeed

Thank you for your answer Keltek. So, if I understand good, no developers can use this information for their games to detect the number of core and optimize the game ?
My father works on many support such as iOS, (3)DS.... and only begin Android now.
And he wants to do a game with the same code between devices : A same game in full 3D works, in all devices you can imagine, smoothly
http://s3.noelshack.com/uploads/images/144829675584_raj.jpg
(the picture is too big)

I think (and blindly hope) if developers uses Android system API for CPU enumeration function, there is no problem to support more cores.

Marsou77 said:
Thank you for your answer Keltek. So, if I understand good, no developers can use this information for their games to detect the number of core and optimize the game ?
My father works on many support such as iOS, (3)DS.... and only begin Android now.
And he wants to do a game with the same code between devices : A same game in full 3D works, in all devices you can imagine, smoothly
http://s3.noelshack.com/uploads/images/144829675584_raj.jpg
(the picture is too big)
Click to expand...
Click to collapse
Sure he can He'll just have to count lines containg those numbers, instead of using the numbers themselves

Thank you very much guys

[Q] CM7 7.2 by squadzone safe for daily use?

Is cm7 safe for daily use? the one made by sir Squadzone .. "especially for games" cause i really9x like his works..
Do you mind posting your opinions and experiences..
I really would love to hear from you guys.

yes it safe....
but the battery drains faster

chepoz said:
yes it safe....
but the battery drains faster
Click to expand...
Click to collapse
For how long have you been using cm7 sir chepoz..

since i join this forum.
sent from Nokia 3310

chepoz said:
since i join this forum.
sent from Nokia 3310
Click to expand...
Click to collapse
Have you encountered any problem sir on your phone using cm7?
I presume your using overclock kernel by Mr Squadzone ..
Did it fry your processor sire?
Btw thanks very much for your replies .. i really appreciate it...
I'll press your thanks button after i post my reply.
waiting eagerly for your reply...

not much problems.
for me, just the battery, some games doesn't run properly, the camera sometimes shows contrast line, and the radio is sucks.
overall, this ROM is perfect.
the overclock doesn't harm the processor.
it safe.
sent from Nokia 3310

Actually the overclocking kinda hurts the processor. Well since you push it over the limit it is used more so the life of the processor is getting shortened.
Sent from my GT-S5570 using Tapatalk

Whoa...new info for me.
Thanx dude..
But why the other ARM v6 have default cpu more than 600mhz?
It has the same processor isn't it?
sent from Nokia 3310

jrandroid said:
Is cm7 safe for daily use? the one made by sir Squadzone .. "especially for games" cause i really9x like his works..
Do you mind posting your opinions and experiences..
I really would love to hear from you guys.
Click to expand...
Click to collapse
I'm not into 'games' so much.
But I've tried Fruit Ninja, Cut the Rope, NFS Shift. and it runs well.
I've used this ROM for almost a month, and I didn't see any bugs yet.

chepoz said:
Whoa...new info for me.
Thanx dude..
But why the other ARM v6 have default cpu more than 600mhz?
It has the same processor isn't it?
sent from Nokia 3310
Click to expand...
Click to collapse
Give me an example of a phone that has ARM v6 that has more than 600 mhz by default

Netas3k said:
Actually the overclocking kinda hurts the processor. Well since you push it over the limit it is used more so the life of the processor is getting shortened.
Sent from my GT-S5570 using Tapatalk
Click to expand...
Click to collapse
yes absolutely true

Netas3k said:
Give me an example of a phone that has ARM v6 that has more than 600 mhz by default
Click to expand...
Click to collapse
S5830 galaxy ace
sent from Nokia 3310

Netas3k said:
Give me an example of a phone that has ARM v6 that has more than 600 mhz by default
Click to expand...
Click to collapse
Search Google..
O_O

samsung galaxy y its armv6 with 834MHZ....

Netas3k said:
Give me an example of a phone that has ARM v6 that has more than 600 mhz by default
Click to expand...
Click to collapse
Google it... O.-

chepoz said:
S5830 galaxy ace
sent from Nokia 3310
Click to expand...
Click to collapse
true that galaxy ace have armv6..but it's not the same version as us..it is version 11..
Sent from public phone using 10cents.

Netas3k said:
Give me an example of a phone that has ARM v6 that has more than 600 mhz by default
Click to expand...
Click to collapse
hmmm... whether Gio and Ace is overclocked?
they have 800MHz ARM v6.

chepoz said:
S5830 galaxy ace
sent from Nokia 3310
Click to expand...
Click to collapse
they are included in the armv6 family yes but still the do have set lifespan.
think of it as processor of desktop, (same facts actually about OC).
ex:
armv6 v8 = default 600mhz = 5 years lifespan
armv6 v11 = default 800mhz = 5 years lifespan
intel e2200 = default 2ghz = 5 years lifespan
intel e2100 = default 1.8 ghz = years lifespan
now both arms are in the same family and both desktop procies also, the difference is that in the architecture set they do have different default freq which are set by manufacturers to maintain stndard life.
now if you push the v8 to 800 it will lessen the lifespan, yes it will be the same freq as the v11 but due to the design it will not have the same lifespan if you OC'd it.
it can be the same theory on motorcycle engines,
example would be the xrm 125cc engine.
it you would like it to be as fast as a 150cc engine you have to bore the piston hole the same size as what the 150cc has and change the piston size and rings and the carbs. but doing this will also push the engine to its limits. why because the safe design of 125cc engines are set as 125. if you go any further you will have better performance but less lifespan and can cause the engine to break faster even with good maintenance.
like your body, example would be.
by default you can last 4 days without sleeping but all you have to do is watch tv ,but you can't last 4 days without sleeping if you will jog 5 km every morning.

astrayasagiri said:
they are included in the armv6 family yes but still the do have set lifespan.
think of it as processor of desktop, (same facts actually about OC).
ex:
armv6 v8 = default 600mhz = 5 years lifespan
armv6 v11 = default 800mhz = 5 years lifespan
intel e2200 = default 2ghz = 5 years lifespan
intel e2100 = default 1.8 ghz = years lifespan
now both arms are in the same family and both desktop procies also, the difference is that in the architecture set they do have different default freq which are set by manufacturers to maintain stndard life.
now if you push the v8 to 800 it will lessen the lifespan, yes it will be the same freq as the v11 but due to the design it will not have the same lifespan if you OC'd it.
it can be the same theory on motorcycle engines,
example would be the xrm 125cc engine.
it you would like it to be as fast as a 150cc engine you have to bore the piston hole the same size as what the 150cc has and change the piston size and rings and the carbs. but doing this will also push the engine to its limits. why because the safe design of 125cc engines are set as 125. if you go any further you will have better performance but less lifespan and can cause the engine to break faster even with good maintenance.
like your body, example would be.
by default you can last 4 days without sleeping but all you have to do is watch tv ,but you can't last 4 days without sleeping if you will jog 5 km every morning.
Click to expand...
Click to collapse
nice example man..
Sent from public phone using 10cents.

astrayasagiri said:
they are included in the armv6 family yes but still the do have set lifespan.
think of it as processor of desktop, (same facts actually about OC).
ex:
armv6 v8 = default 600mhz = 5 years lifespan
armv6 v11 = default 800mhz = 5 years lifespan
intel e2200 = default 2ghz = 5 years lifespan
intel e2100 = default 1.8 ghz = years lifespan
now both arms are in the same family and both desktop procies also, the difference is that in the architecture set they do have different default freq which are set by manufacturers to maintain stndard life.
now if you push the v8 to 800 it will lessen the lifespan, yes it will be the same freq as the v11 but due to the design it will not have the same lifespan if you OC'd it.
it can be the same theory on motorcycle engines,
example would be the xrm 125cc engine.
it you would like it to be as fast as a 150cc engine you have to bore the piston hole the same size as what the 150cc has and change the piston size and rings and the carbs. but doing this will also push the engine to its limits. why because the safe design of 125cc engines are set as 125. if you go any further you will have better performance but less lifespan and can cause the engine to break faster even with good maintenance.
like your body, example would be.
by default you can last 4 days without sleeping but all you have to do is watch tv ,but you can't last 4 days without sleeping if you will jog 5 km every morning.
Click to expand...
Click to collapse
Awesome explanation.
So, if my arm v6 which is default 600mhz overclocked to 782, how much time left until it's "dead"?
sent from Nokia 3310

[DEV][WIP][KERNEL-PATCH][MSM7x30/8x55 GPU OVERCLOCKING][2d-core done][3d-core][v0.7]

Finally after someone pm'd me I looked back into GPU Overclocking.
New thread created issues with old thread OP permissions (people seem to be asking the same questions over and over again all information will be kept in OP & DO READ THE THREAD, repetitive questions will now be ignored)
Benefits:
Smoother UI
Handle 2d & 3d core GPU intensive applications & games
Currently only 2D core has been overclocked working on 3D core OC
2D-core original value - 192mhz OC to 245mhz DONE achieved 25% performance boost grp_2d_clk outputs 245760000hz
3D-core original value - 245mhz OC to 300+mhz WIP hoping to achieve 40-50% performance boost
2D-core OC only Download: Coming soon...
Download Links for other devices coming soon...
Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)
Note: Don't have internet on PC so providing 3 main files that need replaced for 2D-core OC to work
Download link to source code: http://d-h.st/wbH
3D-CORE OC TESTS Download: Coming soon...
Do check under sys/kernel/debug/htc_clock/clks/ look for file with all clocks & look for GRP_clks (Graphics clock)

OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497

Sound really great, do you have the commits on github? More easy to follow , will test it for Runnymede. Great job
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
Sound really great, do you have the commits on github? More easy to follow , will test it for Runnymede. Great job
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I have github but dont reqlly use it much, only have net on laptop so cannot push commits

Shaky156 said:
I have github but dont reqlly use it much, only have net on laptop so cannot push commits
Click to expand...
Click to collapse
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
Benchmark are not really something that should be taken too seriously but yes antutu reported in 20-25% increase in performance not always accurate but 2d core clk results in 245mhz, user from desire hd reported going from in range of 2x fps to 4x fps and that is without the 3d-core overclock (2d-core is used in 3d graphics afaik)

anders3408 said:
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
diff patch to make life easier
diff --git a/arch/arm/mach-msm/clock-7x30.c b/arch/arm/mach-msm/clock-7x30.c
index 8e97664..5e9bc2e 100644
--- a/arch/arm/mach-msm/clock-7x30.c
+++ b/arch/arm/mach-msm/clock-7x30.c
@@ -2992,8 +2992,8 @@ static void __init msm7x30_clock_init(void)
clk_set_rate(&mdc_clk.c, 1);
/* Sync the LPA_CODEC clock to MI2S_CODEC_RX */
clk_set_rate(&lpa_codec_clk.c, 1);
- /* Sync the GRP2D clock to AXI */
- clk_set_rate(&grp_2d_clk.c, 1);
+ /* Set rate of 2D-core GPU Clock @245Mhz (OC of 53Mhz 25% perf boost by Shaky156) */
+ clk_set_rate(&grp_2d_clk.c, 245760000);
}
struct clock_init_data msm7x30_clock_init_data __initdata = {
diff --git a/arch/arm/mach-msm/devices-msm7x30.c b/arch/arm/mach-msm/devices-msm7x30.c
index d52db55..f428e57 100644
--- a/arch/arm/mach-msm/devices-msm7x30.c
+++ b/arch/arm/mach-msm/devices-msm7x30.c
@@ -1319,11 +1319,7 @@ struct resource kgsl_3d0_resources[] = {
static struct kgsl_device_platform_data kgsl_3d0_pdata = {
.pwrlevel = {
{
- .gpu_freq = 364800000,
- .bus_freq = 249600000,
- },
- {
- .gpu_freq = 245760000,
+ .gpu_freq = 245760000, /*Restore correct GPU frequency and bus frequency (Shaky156)*/
.bus_freq = 192000000,
},
{
@@ -1336,7 +1332,7 @@ static struct kgsl_device_platform_data kgsl_3d0_pdata = {
},
},
.init_level = 0,
- .num_levels = 4,
+ .num_levels = 3,
.set_grp_async = set_grp3d_async,
.idle_timeout = HZ/20,
.nap_allowed = true,
@@ -1372,14 +1368,13 @@ static struct resource kgsl_2d0_resources[] = {
static struct kgsl_device_platform_data kgsl_2d0_pdata = {
.pwrlevel = {
{
- .gpu_freq = 0,
+ .gpu_freq = 245760000, //Set 2D-core GPU Frequency @245mhz (Shaky156)
.bus_freq = 192000000,
},
},
.init_level = 0,
.num_levels = 1,
- /* HW workaround, run Z180 SYNC @ 192 MHZ */
- .set_grp_async = NULL,
+ .set_grp_async = set_grp2d_async, //Set the 2D-core Graphics Clock Asynchronous to the AXI clock (Shaky156)
.idle_timeout = HZ/10,
.nap_allowed = true,
.clk_map = KGSL_CLK_CORE | KGSL_CLK_IFACE,
diff --git a/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c b/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
index e81b025..b8686c0 100644
--- a/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
+++ b/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
@@ -488,10 +488,8 @@ int kgsl_pwrctrl_init(struct kgsl_device *device)
pwr->pwrlevels.io_fraction =
pdata->pwrlevel.io_fraction;
}
- /* Do not set_rate for targets in sync with AXI */
- if (pwr->pwrlevels[0].gpu_freq > 0)
- clk_set_rate(pwr->grp_clks[0], pwr->
- pwrlevels[pwr->num_pwrlevels - 1].gpu_freq);
+
+ /*Removed AXI Sync code (Shaky156)*/
pwr->gpu_reg = regulator_get(NULL, pwr->regulator_name);
if (IS_ERR(pwr->gpu_reg))

For now its an empty oc, meaning it doesn't work
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
For now its an empty oc, meaning it doesn't work
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I was in IRC before you came on, talked to synergy, I've changed the OC code, removed mistake and set GPU OC a different way, guess what? tested on my sisters phone again and benchmark was improved, not majorly but on 2 of the draw tests, consistant results of improvement by 5-8fps and rest were by 1-2fps, but like I said lets see where 3d-gpu OC takes me, as that will definitely show if OC is working
What you guys got and what I got was different in benchmarks, which is weird, I got imrovements, you got the opposite. So can't call it an empty OC lol

Shaky156 said:
I was in IRC before you came on, talked to synergy, I've changed the OC code, removed mistake and set GPU OC a different way, guess what? tested on my sisters phone again and benchmark was improved, not majorly but on 2 of the draw tests, consistant results of improvement by 5-8fps and rest were by 1-2fps, but like I said lets see where 3d-gpu OC takes me, as that will definitely show if OC is working
What you guys got and what I got was different in benchmarks, which is weird, I got imrovements, you got the opposite. So can't call it an empty OC lol
Click to expand...
Click to collapse
your improvements here : 0xbench is very small, and should be higher if it is oc'ed , but yes its a plausble

Okay after looking @ GPU Overclock for 2 weeks, This is the news on GPU OC for MSM8x55/MSM7x30 socs.
My findings...
2D-core OC from 192mhz to 245mhz successful.
3D-core OC will not happen without me obtaining the datasheet (which is proprietary)
The clocks are protected, via Ownership/Permissions, and maybe an RCU/MPU
No Overclocking the CPU does NOT Overclock the GPU, thats the worst thing I've heard in my life lol.
The lowest the GPU can hit is 192mhz or lpxo freq
Bus is not overclockable, it always is 192mhz
EBI_2D_clk will and has always been 0mhz
Modifying kgsl platform data and/or the graphics table with random values or even calculated values from correct pll freqs will NOT OC the gpu
it's ashame the GPU clocks are protected.
IF anyone is looking to continuing this project and is on the right track you're more than welcome to get in contact with me, especially if you have the msm7x30 datasheet.
The QSD8x50 soc is more open than this soc, so I'm doing a few tests on the HD2
Also it is overclocked, wasted my time testing, measured the gpu frequency and output to dmesg tells me it is correct, if it wasnt setting then the dmesg would ouput it failing to set the gpu frequency. just like it does for 3d-core oc

it was said before and ill say it again, the gpu clock is relative to the cpu clock, you cant overclock the gpu, their all part of the soc "system on chip", you can increase the bus bandwidth etc, which is already present in my kernel, but performance increase? not any atall

onejay09 said:
it was said before and ill say it again, the gpu clock is relative to the cpu clock, you cant overclock the gpu, their all part of the soc "system on chip", you can increase the bus bandwidth etc, which is already present in my kernel, but performance increase? not any atall
Click to expand...
Click to collapse
GPU clocks on msm7x30 devices is hardcoded.
Sent from my Find 5 using XDA Premium HD app

Hi plz anyone help me my battery work just 5 and 7 hour I have cm10 plz help me how can I install this and how can I got more battery plz hellp
Sent from my Sensation XL using xda premium

[INFO] Android One Overclocking

Hi guys !
I've been trying to add overclocking to Android One, I'm able to add another frequency (both Overclock and Underclock) but I'm able to test it, the 1391 MHz was the stablest overclock frequency I could get. Decreasing frequency lower than 590 MHz makes booting slower (I don't know why).
Check the screenshot, I'll report more news once I get things finished.
I have attached the mt_cpufreq.c just in case anyone have a kernel source and want to try the overclock.
EDIT: It seems max frequency can't be changed since it's hardcoded to 1.3 GHz, it keeps jumping to 1.3 GHz when screen is turned off, but the frequency sticks when phone is rebooted, but not on screen off.
Click to expand...
Click to collapse
EDIT2: It seems that mt_ptp also controls DVFS, which is interesting. This means we have to edit two files and disable restoring frequency to its default table.
Click to expand...
Click to collapse
EDIT3: I found this in mt_cpufreq.c :
Code:
static unsigned int g_max_freq_by_ptp = DVFS_F0;
Which is defined in the same file, the DVFS_F0 is :
Code:
#define DVFS_F0 (1300000) // KHz
The DVFS_F0 is 1.3 GHz, this might explain why the max frequency keeps jumping to 1.3 GHz when screen off. But this is just an assumption.
I've added mt_ptp.c just in case anyone want to checkout and help the development.
Click to expand...
Click to collapse

Interesting
I had given up all hopes of low level modifications such as over clocking /underclocking/under volting and kernel level wake gestures like double tap to wake etc... This gives me something to look at. Thank you

It seems that max freq can't be set to other than 1300 MHz / 1.3 GHz.
Can anyone here using CM12.1 confirm this bug ? Since it might be because of the ROM but I'm unsure here, it can be either ROM or my custom built kernel.
BTW, 470 MHz isn't fully implemented, the kernel refuses to use it. It might be because I haven't defined it in the volt switch function.
EDIT: Another possibility, it seems on mt_ptp, the clock are either hardcoded or defined in other file. So I have to say that overclocking might be still far away to be achieved.

Why not Overcloack the GPU ??? (NOOB HERE)

Saurabh K said:
Why not Overcloack the GPU ??? (NOOB HERE)
Click to expand...
Click to collapse
GPU is another thing here, it's still too hard to OC CPU itself.

Does the Android One uses MT6582 or MT6582M?(Are there more differences between them other than GPU frequency? MT6582: [email protected]; MT6582M: [email protected])

hstinscdln said:
Does the Android One uses MT6582 or MT6582M?(Are there more differences between them other than GPU frequency? MT6582: [email protected]; MT6582M: [email protected])
Click to expand...
Click to collapse
MT6582 I believe. I never checked but on kernel the chip folder (/arch/arm/mach-) is mt-6582

Can it be used on a 5" screen and MT6582M?
Sent from my Lenovo A536 using XDA Free mobile app

hstinscdln said:
Can it be used on a 5" screen and MT6582M?
Sent from my Lenovo A536 using XDA Free mobile app
Click to expand...
Click to collapse
Depends, does your phone kernel source exist ? If yes, then you're free to try. If not, then don't.
BTW, please don't think this is just a 'install the .c file and get overclock'. It needs many work, and such, I advise you to have at least some advanced knowledge of Linux Kernel.

F4uzan said:
It seems that max freq can't be set to other than 1300 MHz / 1.3 GHz.
Can anyone here using CM12.1 confirm this bug ? Since it might be because of the ROM but I'm unsure here, it can be either ROM or my custom built kernel.
BTW, 470 MHz isn't fully implemented, the kernel refuses to use it. It might be because I haven't defined it in the volt switch function.
EDIT: Another possibility, it seems on mt_ptp, the clock are either hardcoded or defined in other file. So I have to say that overclocking might be still far away to be achieved.
Click to expand...
Click to collapse
i had overclocked sprout in almost every possible sorts i can do. you have not defined 470mhz freq table properly in the file , pm me if you want to know my experience. :good:

Wow, overclocks must drain battery though .........

Saurabh K said:
Wow, overclocks must drain battery though .........
Click to expand...
Click to collapse
Not really, but yeah, it kinda drain battery more than normal 1.3 GHz frequency.

F4uzan said:
Not really, but yeah, it kinda drain battery more than normal 1.3 GHz frequency.
Click to expand...
Click to collapse
How about the you underclock in order to save battery as 1.3 quad core is not that necessary for mild usage.

Saurabh K said:
How about the you underclock in order to save battery as 1.3 quad core is not that necessary for mild usage.
Click to expand...
Click to collapse
200mhz is the lowest underclock i get in my experiments ,i tried 156 mhz but it didn't boots up ?

roshan77ss said:
View attachment 3269028
200mhz is the lowest underclock i get in my experiments ,i tried 156 mhz but it didn't boots up
Click to expand...
Click to collapse
does the device run smoothly on such low clocks ???

Saurabh K said:
does the device run smoothly on such low clocks ???
Click to expand...
Click to collapse
low clock means less processing power so it lags if i set both minimum and max frequency to 200mhz else it is fine[emoji23]

roshan77ss said:
low clock means less processing power so it lags if i set both minimum and max frequency to 200mhz else it is fine[emoji23]
Click to expand...
Click to collapse
OK, so the device will run smoothly on ~550 MHz without loosing too much on performance and save battery also, ?

Saurabh K said:
OK, so the device will run smoothly on ~550 MHz without loosing too much on performance and save battery also, ?
Click to expand...
Click to collapse
yup 550mhz doesn't affect performance that much

roshan77ss said:
yup 550mhz doesn't affect performance that much
Click to expand...
Click to collapse
So, tell me a safe way in which I can underclock my Sparkle V (Stock 5.1)...

Using trickster mod??

[Q] Undervolt kernel

Hello
I was wondering if there is any kernel available for our moto with undervolt support. I fell my phone is throthling like hell, specialy because we're on summer here in the South hemisphere. If you use camera/Snapchat for 1 minute it gets around 60ºC.
It was a very useful feature in my old Nexus 4, if done properly, would keep the phone real cold. I remember you could subtract 100 ~ 150 mv from some specific frequencies.

No one? please????

sky0165 said:
Hello
I was wondering if there is any kernel available for our moto with undervolt support. I fell my phone is throthling like hell, specialy because we're on summer here in the South hemisphere. If you use camera/Snapchat for 1 minute it gets around 60ºC.
It was a very useful feature in my old Nexus 4, if done properly, would keep the phone real cold. I remember you could subtract 100 ~ 150 mv from some specific frequencies.
Click to expand...
Click to collapse
see if this helps -
http://forum.xda-developers.com/showthread.php?t=1743055

sagar_b93 said:
see if this helps -
http://forum.xda-developers.com/showthread.php?t=1743055
Click to expand...
Click to collapse
Thank you for the reply, but this mod has nearly 3 years old, probably won't work properly due to android version. And UV is complicated. As you see, this mod allows you to subtract mv globally from all frequencies. This is not efficient because low frequencies doesn't handle very well too much undervolt without start rebooting. You need to undervolt frequence by frequence. Some of them supports only -25 or -50 mv (like 300mhz) and other -100 ~ -150 mv.
This is interesting and good because we can have a considerative overclock (maybe 1.5 Ghz) and still keep the battery at good levels and also at a safety temperature.
If any kernel dev get interested on supporting VDD levels, it would be fantastic to our community :laugh:

There was a special build of decipher's kernel I think back in the day, which had undervolting enabled.
However, I tested it myself and many others to conclude that it was too unstable and the power savings were negligible. Also, overclocking is hardware locked in our CPU, so even if we did overclock it with any app, it would not matter as the frequency is actually hardware limited to 1.2 GHz.
Sent from my Moto G 2014