2233 replies to this topic

[ZKK007]

Basically, the Scaling Max and CPU Info Max not displaying the same values is why my "Current Max Clock Frequency" reverts to "1.2 GHz" after my phone idles for about 10 minutes OR is rebooted. The Scaling Speed is controlled by "scaling_setspeed" and the fact that mine says "unsupported" means there is an issue. There is obviously a set speed because my phone will change frequencies on PegasusQ and use the 300, 615, 850, and 1100MHz frequencies, but will not use the 1300.

I believe the Scaling Set Speed is "unsupportive" of custom modules/clocks. If I open it using text editor and delete the "<unsupported>" and then "save and exit", it will fail and say no changes were applied. this will mean that when No-Frills attempts these changes, it will fail as well.

The cpuinfo_max_freq not being the same as scaling_max_freq is why my OverClock seems to work at first and reverts later. Basically, cpuinfo is just an information database that benchmarks and other applications use when you hit "system information". In basic terms, my phone is lying about its capabilities LOL. Scaling Max is the "REAL" value.

I see what you mean. Even Rom Toolbox Pro will set the CPU it to the OC value (1325mhz in my test) and show it, but the CPU Benchmark test reverts back to 1200mhz upon screen off. If I reboot, the values go up to 1325mhz, but then back to 1200mhz after screen off

I know the modules are from ICS so this may have something to do with it. I will look around for solutions In the mean time, if any knows how to get it to stick, let us all know!

[wallacengineering]

I see what you mean. Even Rom Toolbox Pro will set the CPU it to the OC value (1325mhz in my test) and show it, but the CPU Benchmark test reverts back to 1200mhz upon screen off. If I reboot, the values go up to 1325mhz, but then back to 1200mhz after screen off

I know the modules are from ICS so this may have something to do with it. I will look around for solutions In the mean time, if any knows how to get it to stick, let us all know!

Ah yep the modules being from ICS is more than likely the problem. The Kernel was updated when the Jelly Bean OTA leak was installed (ICS runs 3.0.1 or something) to 3.0.8-g67218e8 it says on my device.

Im pretty sure some files were modified/updated compared to the ICS stock OS so I'm pretty sure that means that ICS modules cant run correctly on JB Kernel. Looks like its time to search for a JB Kernel-based Module!

Ill keep you updated

[ZKK007]

Ah yep the modules being from ICS is more than likely the problem. The Kernel was updated when the Jelly Bean OTA leak was installed (ICS runs 3.0.1 or something) to 3.0.8-g67218e8 it says on my device.

Im pretty sure some files were modified/updated compared to the ICS stock OS so I'm pretty sure that means that ICS modules cant run correctly on JB Kernel. Looks like its time to search for a JB Kernel-based Module!

Ill keep you updated

Yes, but most of them work ok with JB. My understanding is that the JB kernel was a hybrid ICS kernel and that is why some of the modules works without needing to be updated. Let me know if you find anything. I have looked and have been looking, but I haven't found anything yet. I think most people are waiting for official JB to make the updates which would make sense

[wallacengineering]

Yes, but most of them work ok with JB. My understanding is that the JB kernel was a hybrid ICS kernel and that is why some of the modules works without needing to be updated. Let me know if you find anything. I have looked and have been looking, but I haven't found anything yet. I think most people are waiting for official JB to make the updates which would make sense

You may want to inform on the Original Post somewhere that OverClocking at this point isn't a good idea. What I'm finding is that because the OC 1300 isnt working, Max clock cant be achieved. No matter how hard I push the phone it wont hit 1200. Probably because right now it isnt a choice (i.e. scales are 300, 615, 850, 1100, and 1300 (not possible due to scaling_max_freq), so I'm stuck with 1.1 GHz Max until I get home tonight. Woops lol.

So, a hybrid Kernel eh? Huh, that would explain why some of the tweaking elements work, such as Governor Selection and I/O scheduler selecion.

However, I think its safe to say that it is a good idea to run Aviator Utility and install "Stock" Modules and just tweak the governors for now. I am enjoying PegasusQ quite a bit as well as SmartAssV2.

Based on what I have personally learned, PegasusQ is a governor which controls the cores much like HotPlug but allows each core to be independent and process its own tasks, like they were two entirely seperate processors in seperate devices that are simply teaming up on one instead. Sounds like the Intel Core i7 in my laptop, simply amazing!

SmatAssV2 is supposively like the stock Interactive but more agressive. When in doubt, use simple and reliable power!

[wallacengineering]

What about this custom module source here:

Please Login or Register to see this Hidden Content

It says he is on device XT909 (I believe that is the international Razr)

It also has GB voltages and OC (Typo, Im guessing he meant JB)

Any possibility of getting in contact with him and seeing if it will work for XT912?

I dont have an XDA account and I know you need to post 10 things to get into the development forums anyway.

[ZKK007]

You may want to inform on the Original Post somewhere that OverClocking at this point isn't a good idea. What I'm finding is that because the OC 1300 isnt working, Max clock cant be achieved. No matter how hard I push the phone it wont hit 1200. Probably because right now it isnt a choice (i.e. scales are 300, 615, 850, 1100, and 1300 (not possible due to scaling_max_freq), so I'm stuck with 1.1 GHz Max until I get home tonight. Woops lol.

So, a hybrid Kernel eh? Huh, that would explain why some of the tweaking elements work, such as Governor Selection and I/O scheduler selecion.

However, I think its safe to say that it is a good idea to run Aviator Utility and install "Stock" Modules and just tweak the governors for now. I am enjoying PegasusQ quite a bit as well as SmartAssV2.

Based on what I have personally learned, PegasusQ is a governor which controls the cores much like HotPlug but allows each core to be independent and process its own tasks, like they were two entirely seperate processors in seperate devices that are simply teaming up on one instead. Sounds like the Intel Core i7 in my laptop, simply amazing!

SmatAssV2 is supposively like the stock Interactive but more agressive. When in doubt, use simple and reliable power!

I'm not sure I understand why you can't get your max cpu freq. As far as I understand by using the OC utility you will get max frequency initially and upon reboot. However, currently there is no way to keep the max freq since it will revert to 1200mhz upon screen off. This is the bug you are mentioning. But, I was still able to hit 1325mhz just as long as I didn't let the phone idle or turn the screen off. (Which really is pointless. So at the moment it is best to be on stock ) Also, the voltage will be increased on all levels making for a higher battery drain than on stock.

There are four values which can be changed. Stock is 300, 600, 800, 1000, and 1200. You can see this in the "modules" script under system/etc/init.d/modules. If you use the CPU Spy app from the Play Store you can see how long your phone is running at each level.

All the modules I've used are from Whirleyes here

Please Login or Register to see this Hidden Content

, so that might help you

This gives a good explanation on what each governor does:

Please Login or Register to see this Hidden Content

Have you experienced any deep sleep issues with the different governors? I've experienced and read about issues with PegasusQ and HotplugX on JB but would like to know if you've had these issues too

[wallacengineering]

I'm not sure I understand why you can't get your max cpu freq. As far as I understand by using the OC utility you will get max frequency initially and upon reboot. However, currently there is no way to keep the max freq since it will revert to 1200mhz upon screen off. This is the bug you are mentioning. But, I was still able to hit 1325mhz just as long as I didn't let the phone idle or turn the screen off. (Which really is pointless. So at the moment it is best to be on stock ) Also, the voltage will be increased on all levels making for a higher battery drain than on stock.

There are four values which can be changed. Stock is 300, 600, 800, 1000, and 1200. You can see this in the "modules" script under system/etc/init.d/modules. If you use the CPU Spy app from the Play Store you can see how long your phone is running at each level.

All the modules I've used are from Whirleyes here

Please Login or Register to see this Hidden Content

, so that might help you

This gives a good explanation on what each governor does:

Please Login or Register to see this Hidden Content

Have you experienced any deep sleep issues with the different governors? I've experienced and read about issues with PegasusQ and HotplugX on JB but would like to know if you've had these issues too

Oh so you used the same Modules I suggested LOL that won't help then. What I may do is try flash installing the modules and scrips from him on top of Aviator from SafeStrap and try again.

So far as deep sleep goes, I don't know how to test it but it seems to me like it works. Basically when my screen is off I get incredible battery life which is one clue, and upon wake I find my clock is in its lowest state (300MHz). So to me it seems like it is working.

Also that is the same exact place I used to learn about Governors (it seems we think alot alike lol).

Finally I have heard reports about HotPlugX issues and so I don't dare try that one (People say that the clock scrips simply do not play nice with the Jelly Bean Kernel), and as far as I can see there hasn't been any issues with PegasusQ so thats good.

I'll let you know how the flash install goes!

[MBRedline]

Please Login or Register to see this Hidden Content

If you use tasker you can use these profiles to see exactly what is wake locking your phone whether android system or a particular app and for how long.

Alternatively, CPU spy takes the uptime and subtracts the time spent at each CPU frequency to get total deep sleep time

[wallacengineering]

Oh so you used the same Modules I suggested LOL that won't help then. What I may do is try flash installing the modules and scrips from him on top of Aviator from SafeStrap and try again.

So far as deep sleep goes, I don't know how to test it but it seems to me like it works. Basically when my screen is off I get incredible battery life which is one clue, and upon wake I find my clock is in its lowest state (300MHz). So to me it seems like it is working.

Also that is the same exact place I used to learn about Governors (it seems we think alot alike lol).

Finally I have heard reports about HotPlugX issues and so I don't dare try that one (People say that the clock scrips simply do not play nice with the Jelly Bean Kernel), and as far as I can see there hasn't been any issues with PegasusQ so thats good.

I'll let you know how the flash install goes!

So the Flash install did nothing lol. Same problems, device hasnt changed one bit. I think we should probably inform the other ROM developers that OverClocking isnt really working. I have tried almost every ROM on this site and havent had any success in getting one to actually stick. Its the same issue everywhere because every single ROM uses the same modules from ICS.

Im not sure if I should just post on one thread and then copy-paste to all the other threads, it sounds like something a Moderator would not appriciate...

Eh I'll do it anyway lol...

On a side note, ROFL I am quoting myself!

[ZKK007]

So the Flash install did nothing lol. Same problems, device hasnt changed one bit. I think we should probably inform the other ROM developers that OverClocking isnt really working. I have tried almost every ROM on this site and havent had any success in getting one to actually stick. Its the same issue everywhere because every single ROM uses the same modules from ICS.

Im not sure if I should just post on one thread and then copy-paste to all the other threads, it sounds like something a Moderator would not appriciate...

Eh I'll do it anyway lol...

On a side note, ROFL I am quoting myself!

I think most of them are aware of this. When I was asking around and learning about the OC scripts it was mentioned that they were from ICS and kind of worked. I doubt any of them will be updated until we have official JB, so most of us are just waiting. You can mention it on the other threads, but like I say, most of the Dev's will know or will read it on this thread

[prstorero]

I think most of them are aware of this. When I was asking around and learning about the OC scripts it was mentioned that they were from ICS and kind of worked. I doubt any of them will be updated until we have official JB, so most of us are just waiting. You can mention it on the other threads, but like I say, most of the Dev's will know or will read it on this thread

I don't even have over clock so no need to post there

[wallacengineering]

I think most of them are aware of this. When I was asking around and learning about the OC scripts it was mentioned that they were from ICS and kind of worked. I doubt any of them will be updated until we have official JB, so most of us are just waiting. You can mention it on the other threads, but like I say, most of the Dev's will know or will read it on this thread

Oh ok then I will just mention it then

[mhotovec]

Oh ok then I will just mention it then

So, you're idea of 'just mentioning it' is all caps red 18 point font underlined?? Gee, I'd hate to see how you handle a 'give a shout'...

[mattkilla]

hey man im having the toughest time with this darn pink floyd theme.. a few days ago, once you released 2.01, I started from scratch created new slot , flashed rom, setup, rebooted, flashed theme. Setup again and reboot. I ran on that rom for about 3-4 days with no problems whatsoever. I decided to give another rom a go for a half a day. It was on an entirely different slot. Now when i am trying to get back to the aviator rom i get " The evil Hammers" i like to call them. Always thought they were a bit disturbing in the movie but now every time i see them i get stuck in a boot loop. This is the same exact problem i was having on 1.8 with the theme. I thought my dirty flashes were a cause of it that's why i started from scratch, but im getting the same problems. p.s. i did do cache and dvalik wipe in hopes the rom would load .. no luck

edit- after an hour of trying i finally got it to load. too much hassle just to switch rom's. would you advise using the utility to remove the theme?

[mhotovec]

Matt, I'm guessing, and ZK may have a different/better answer, but you might try completely deleting and recreating the slot. Sometimes 'junk' seems to be leftover from a previous ROM, even after full wipes. I've seen several instances where the fix was to delete and recreate the slot.

[mattkilla]

reread my post, i did that already, thats what i meant by started from scratch

[wallacengineering]

So, you're idea of 'just mentioning it' is all caps red 18 point font underlined?? Gee, I'd hate to see how you handle a 'give a shout'...

Probably Mega Awesome 100 pt Bolded Italicized Red Death Font lol

[ZKK007]

I just wanted to mention that currently this is not compatible with the soak test JB build (98.72.16).

I quickly built a .16 ROM but it failed I don't have a lot of time, but I will build a ROM for the soak test build eventually

[OldBaldy]

I just wanted to mention that currently this is not compatible with the soak test JB build (98.72.16).

I quickly built a .16 ROM but it failed I don't have a lot of time, but I will build a ROM for the soak test build eventually

Waiting for it with baited breath. (Sounds fishy, but it's not )

Sent from my DROID RAZR

[wallacengineering]

I just wanted to mention that currently this is not compatible with the soak test JB build (98.72.16).

I quickly built a .16 ROM but it failed I don't have a lot of time, but I will build a ROM for the soak test build eventually

That sounds absolutely EPIC! I want to try a ROM on the new Soak Build but have heard that none of them are working yet. Apparently the Kernel has been patched and updated and that will probably mean you will have to start completely from scratch... :/

On a good side note I may have found a way to OverClock these ROMs on the JB leak.

I am working on it and so far my values are sticking but the solution is not what I would refer to as "The most stable soulution available".

I am going to create a thread hopefully under the Droid Razr Hacks (XT912-CDMA) section and I will post a link here for you guys when I have it up and running.