yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] dtrail1:
for coding purpoese including sources, etc, github works well - and of course some local space (about 15 GB) at everyone's home computer (must be runnin Linux of course). Web storage should be fine with 1 GB for OTAs (as each package contains data with 14mb).

Well, I'm also not a "pro-coder", it's more important to understand the code at least and more to know about how the linux kernel is working. I guess it would be the best way if I'd start over merging all the JBX features into a clean CM kernel and then debugging together, fixing what's need to be fixed then.
[Motorola Droid RAZR] OGdroidster:
I have the android sdk for fastboot through terminal use only installed would I need more than that to be installed. Also do I need to install git for your source that is on your git. Your English is fine you had two misspelled words and you are completely understandable, so don't worry about it. Its all good. I could help you debug and fix errors in source.
[Motorola Droid RAZR] i5powa:
Does anyone still have the latest version of this kernel and can kindly upload it please! I'd like to use LSKK + JBX as it seems the best option for our old phone...
[Motorola Droid RAZR] welder73:
Here,I think this is the latest version: JBX-Kernel-3.6-Hybrid-Spyder-4.4_2014-08-21 :)

https://mega.nz/#!YFVh3aoR!eExsTzpXFGjj33zyyT3Gh1swkPvyuJ3H_0WqVbjeeGs
[Motorola Droid RAZR] dtrail1:
It's been a very long time! I know :)

I've been very busy with real life, and now I just decided to have a look into this old thread. Searched my old RAZR and it comes along with good memories.

Anyone still using this phone??

Gesendet von meinem LG-M200 mit Tapatalk
[Motorola Droid RAZR] mithun23:
Nice to see you again [MENTION=3247283]dtrail[/MENTION]..
[Motorola Droid RAZR] dubisz:
Lastest BSE Nightly doesn't boot on my LiquidSmooth 09.05 Nightly :( Did a clean install, but it didn't help.
[Motorola Droid RAZR] mat9v:
It's more like a guideline, you should not do that if you plan to use performance governor or play games regularly - you can "melt" the silicon, for sure high temps will decrease it's lifespan. I mostly like to have highly responsive interface and gaming is done @1400Mhz. That's why I ***** about GPU overclock since I would like higher fps and MPU overclock does little for that. I'm in a process of testing 0.4.4 stable OCE kernel for optimum performance :)

And here are the scores:

I hope my test prove helpful. OCE Kernel 4.4 Stable from 5/12 3.21 AM

All smartreflex disabled.

Governor Performance locked [MENTION=322487]1000[/MENTION]Mhz

Programs: Antutu 3d part, 3dmark, gpumark, nenamark2, bonsai benchmark

307Mhz:

Antutu - 2739 , 3dmark - 2257 , gpumark - 8940 , nenamark2 - 42,1 , bonsai - 1663

384Mhz:

Antutu - 2673 , 3dmark - 2265 , gpumark - 8910 , nenamark2 - 42,2 , bonsai - 1647

512(416)Mhz:

Antutu - 2680 , 3dmark - 2258 , gpumark - 8850 , nenamark2 - 42,1 , bonsai - 1668

And now with Governor Hotplug, still limited [MENTION=322487]1000[/MENTION]Mhz

307Mhz:

Antutu - 2681 , 3dmark - 2266 , gpumark - 8700 , nenamark2 - 42,0 , bonsai - 1665

384Mhz:

Antutu - 2335 , 3dmark - 2269 , gpumark - 8850 , nenamark2 - 41,7 , bonsai - 1664

512(416)Mhz:

Antutu - 2741 , 3dmark - 2260 , gpumark - 8855 , nenamark2 - 42,2 , bonsai - 1666

And now with Governor Hotplug, not limited [MENTION=1466104]135[/MENTION]0Mhz

307Mhz:

Antutu - 2681 xxx, 3dmark - 2343 , gpumark - 8820 , nenamark2 - 42,8 , bonsai - 1665

384Mhz:

Antutu - 2713 , 3dmark - 2333 , gpumark - 8790 , nenamark2 - 42,3 , bonsai - 1650

512(416)Mhz:

Antutu - 2754 , 3dmark - 2367 , gpumark - 8800 , nenamark2 - 42,1 , bonsai - 1656

And now with Governor Hotplug, oc [MENTION=1528666]151[/MENTION]2Mhz

307Mhz:

Antutu - 2769 xxx, 3dmark - 2398 , gpumark - 8880 , nenamark2 - 42,4 , bonsai - 1646

384Mhz:

Antutu - 2831 , 3dmark - 2401 , gpumark - 8850 , nenamark2 - 42,2 , bonsai - 1630

512(416)Mhz:

Antutu - 2788 , 3dmark - 2392 , gpumark - 8880 , nenamark2 - 42,2 , bonsai - 1635

And now with Governor Performance, oc [MENTION=1528666]151[/MENTION]2Mhz

307Mhz:

Antutu - 2826 xxx, 3dmark - 2388 , gpumark - 8940 , nenamark2 - 42,2 , bonsai - 1669

384Mhz:

Antutu - 2798 , 3dmark - 2384 , gpumark - 8820 , nenamark2 - 42,1 , bonsai - 1670

512(416)Mhz:

Antutu - 2734 , 3dmark - 2392 , gpumark - 8910 , nenamark2 - 42,1 , bonsai - 1675

So after few hours of testing, it does not seem that overclocking GPU does anything for the fps.

Antutu is completely unreliable, the program with lowest variation in scores is Bonsai and it does not differ in any substantial way between runs. MPU from 1000 to 1512 and GPU from 307 to 416. It should have made some difference if GPU OC really worked.
[Motorola Droid RAZR] 1droidmod:
I didnt think phone was deep sleeping as much as it should so i wiped dalvic/cache and fixed permissions, after that I experienced "phone shutting down and hit or miss as far as booting up again. Flashed kernel restore to fix. Ahhh, was GREAT until wipes...

XT912 CDMA
[Motorola Droid RAZR] ryankliber:
I installed 0.4.4 OCE stable on a fresh install of carbon 5-11 nightly, and it was running GREAT for a few hours. The first freeze happened as i was turning down the volume. Also i noticed that i was getting 0 deep sleep whatsoever due to the android system keeping it awake. After the first freeze it will freeze up about every 20 minutes. Seems like some sort of memory leak as it just gets slower and slower, and just when i'm going to do a reboot it will lock up. FYI no install of trickster, or changing of any kernel settings.

Thanks so much for your hard work dtrail!!! Performance and stability has greatly improved over the last week. Hopefully that perfect build is right around the corner :)
[Motorola Droid RAZR] dtrail1:
Carbon didn't play well for me...
[Motorola Droid RAZR] dtrail1:
Just reboot. Its a well known phenomen.
[Motorola Droid RAZR] dtrail1:
For me the camera doesn't work on latest OCE... anyone else with that problem?
[Motorola Droid RAZR] Brantuck84:
Yup no camera for me either that sux too cuz everything else was perfect

Sent via Raven

"Dark Wings.....Dark Words"
[Motorola Droid RAZR] dtrail1:
Camera Fixed! I accidently acitvated the new DCE Codec engine (which seems to be a preperation for future HD video recording) but it's not compatible to the camera libs atm. SO I disabled it. The kernel has been updated (same link).

GPU OC IS WORKING! I got scores between 2400 and 2900 for GPU. It depends on silicon I would say, and also the settings.

Keep your custom CPU frequency settings also after screen was off: Just activate the "Frequency Lock" in Trickster Mod. YOu can uninstal No-Frill CPU Control now as it's not needed anymore. Settings will stay forever with the "Frequency Lock".

Just for testing: Now compiling the Kernel again with new toolchain (Linaro 4.7). This should cause an imrpovement in performance too.

BSE Kernel can't be booted...Don't know why. It doesn't like some of the new code I guess...But I tried to find the reason for three days and many hours... WIthout an OTG adapter it's hard to debug when it doesn't boot at all... I have to rewrite the whole OPP table configuration for BSE, maybe remove 2-3 steps so it can handle it. It will take some more time...

OCE is fully stable now! A new official release of Trickster Mod is available at Gplay! It works! THere is no need to set the GPU scaling first before beeing able to set anything else! This as been fixed by me yesterday in kernel! The GPU has now 4 scaling steps with new voltage so it's stable finally and you can set whatever you want in Trikctser without causing a crash!

Changelog will follow later or tomorrow.
[Motorola Droid RAZR] garywojdan81:
I'm on oce4.4 nightly 5 with the latest avatar ROM update & camera works great for me
[Motorola Droid RAZR] dtrail1:
Thanks for the "flowers" :D I have to say that I'm not one of the best devs... I think the best devs in our community - referring to Kexec - are Hashcode, dhacker and of course Kholk and mbm! Without them we'd have no Kexec! Another great dev is (was) Whirleyes (as he's not active anymore) Fortunately STS guys were keeping the good work to make it fully working!! I really thank them a lot for this and many great rom - and never leaving our good old Razr! I am just a guy who is trying to learn more about that stuff... And I love it using customizable kernels on my devices - but nobody else (Bytecode left too..) is working on this. But I'm glad if it works for you guys! I won't leave the Razr! :)
[Motorola Droid RAZR] dtrail1:
Building with GCC 4.7 doesn't work yet..Needs a workaround, so I will let it be for now as the performance became greatly improved with the last few commits.

Found an small issue and fixed it in OCE. Rebuilding again and uploading as the same release.

I used OCE the last days because BSE didn't boot. Now I can uV -75mV stable and lock the frequency with Trickster at 1ghz max. Battery is really good.

But I have reconfigured the BSE OPP table and building it right now, hope it works...Had to remove some OPPs, now it's:

100, 200, 300, 400, 600, 800, 1000

I guess the current smartreflex configuration together with some other changes causes conflicts with the OPP count so it can't handle 10 OPPs, reduced it to 7 - for now. If it works I will reconfigure many features in BSE only for power saving.

I want to know, just interested, how deep can you uV now? After some reconfiguration of smartreflex and the whole PM stuff it seems that it's possible now to uV deeper - I remember the ICS times where I was able to uV down to ~850 mV. Now I can reach ~950 mv (while it was 880 mV some days ago..)
[Motorola Droid RAZR] dubisz:
On BSE 0.4.3 Nightly-1 for now I'm able to go down to 940 mV. Will try to go lower.
[Motorola Droid RAZR] ryankliber:
So I kept running the 0.4.4 stable on carbon even tho it didn't deep sleep (reboot, and cache wipes didn't change anything). If it started to lag I would clear a few recent apps and good to go it never froze up again. Just downloaded and flashed the updated version and deep sleep is working :)
[Motorola Droid RAZR] dtrail1:
New BSE kernel is working and fully stabel! It also includes ther new performance improvements and all fixes. Online now!!

Edit: And to clarify something: Trickster allows you to apply any voltage value you want, in example you could apply 1600 mV (DON'T DO THIS!!!), but in theory the kernel (dvfs and smartreflex) won't allow that high values as the maximum voltage value of 1450 mV is hardcoded (But I'm not sure yet if Trickster is able override it...). But you can raise voltages up to 1450 MAXIMUM when using Live OC to overclock up to 1,5 Ghz. BUT you can leave it on it's default value if 1410 mV! I have tested it, OC up to 1,5 Ghz and voltage was UNTOUCHED - it didn't freeze or something. As Smartreflex usually calculates the best voltage around the set value you can leave it as long as you are not using freqs over 1,5 ghz. But when using freqs above 1,5 Ghz you should turn OFF Smartreflex as it cannot handle them.
[Motorola Droid RAZR] dubisz:
Installed the 0.4.4 BSE JB Stable - it boots, voltage set to 930mV - seems fast and stable.
[Motorola Droid RAZR] dtrail1:
Changelog for BSE / OCE 0.4.4 Stable JB

- Included some stuff for better code generation

- Added optimized CRC32 Algorithm

- lib/lzo: Updated LZO compression for better code generation

- Set build flags and comp. to armv7

- Modified lowmemory killer in some ways to get better handling with freed tasks

- Staging: android: binder: Allow using highmem for binder buffers

- Staging: android: binder: Fix memory leak on thread/process exit

- staging: android: Fix two checkpatch issues in binder

- Fixed GPU OC

- Fixed a bug which forced the user to have to set GPU frequency before beeing able to set anything else in Trickster Mod

- Added 4th GPU scaling step and adjusted higher voltage limit for 416mhz step

- Limited the overall GPU scaling count to 2 steps (min is always 307mhz, max freq can be set by user using Trickster Mod or sysfs)

- BSE: Reconfigured OPP table, removed some OPPs due to SR configuration

- BSE: Removed smartreflex tuning interface

- BSE: Fixed smartreflex on init
[Motorola Droid RAZR] pseudoheld:
Thanks. Will try tomorrow. How my phone finally "likes" one of the kernels ;)
[Motorola Droid RAZR] osval.:
GPU OC indeed works but only 384mhz scoring 2850+ on Antutu 3D; 416mhz scores around 1700+ on my XT910 (for the record stock JB scores 2500-2600+)

Using CM10.1 RC2 / OCE 0.4.4, / MPU 110 keeping other settings as provided

As of now I think that is a hardware limitation, maybe the chipset cannot provide enough power to the GPU to achieve more OC, maybe even with kexec it can't be overriden.

When the first CM9 kexec rom was released, and was so full of bugs that seemed impossible to get rid off, I wouldn't imagine that kexec development would ever get even near of where it is right now; such a HUGE work :victory:
[Motorola Droid RAZR] 1droidmod:
:thumbup:

XT912 CDMA
[Motorola Droid RAZR] dtrail1:
There is no limitation for kexec except some partitions such as the baseband etc. But the kernel has full access to all related devices. In theory it can be possible to use a custom baseband which could be stored on another place - just an idea, maybe this would be a possibility to enable and use the lte chip on gsm devices..? In fact we can access all board settings and features even with a kexec kernel. I guess there are differences between devices and their silicone. My benchmark scores increase a lot with 416mhz GPU speed .. But the overall performance is limited, so a high oc on GPU will cause decreased performance of the cpu, and this can also affect the scores in benchmarks. I guess the cpu power limitation in connection with GPU oc is also responsible for your score decreases.

Gesendet von meinem A101 mit Tapatalk 2
[Motorola Droid RAZR] osval.:
I already thought that and had same results at 100 and 110 MPU for 416mhz so I discarded that idea...

BUT after your answer I made a different approach and tried not only leaving MPU value @ 100 but also undervolting -50mV and indeed it managed to rise to 2900, so at least in my device the bottleneck for GPU OC is the amount of power that the device can provide to the CPU and GPU combined 100% sure, I guess the only way to determine which uV - GPU OC combination works best for each device is experimenting :p

EDIT: following this idea maybe GPU@512mhz is acheivable in a stable way with extreme borderline-stable undervolting of the CPU, just an idea
[Motorola Droid RAZR] 1droidmod:
Hey dtrail, latest stable BSE is working great for me (pac man 4.2.2) deep sleeping like a mutha f$c%er.. Great... I do not mess with trickster or values in any way, just flash and burn.... Thanks for your persistent attitude twords this project.. You are great in what you do so don't belittle yourself when it comes to being a dev... Everyone has their nitch.. Thanks again and i will provide feedback as needed!!! :thumbup::thumbup: too you...

XT912 CDMA
[Motorola Droid RAZR] mat9v:
Antutu is unreliable, I got widely different scores without changing settings, ranging from 2300 to 2800 @ 307Mhz.

If you remember I even tried benchmarking @1000Mhz and various GPU steps and the results in all programs were similar. Try GPUmark, it is very simple and does not vary with runs.

Am I to understand that we can't really force GPU frequency as in setting performance governor for GPU, we must select only max frequency and let it autoselect when to overclock? Dtrail, can you modify the source to, for example, set every step (that is now 307/384) to 416 essentially forcing GPU to always work @ 416?

Which value controls GPU oc via sysfs? It's not mentioned in FAQ. Is it sys/devives/system/cpu/cpu0/cpufreq/gpu_oc ?

With latest stable kernel is I set gpu_oc to 2 I get less then 50% fps then if set to 1 (1200-1300 in antutu 3d)
[Motorola Droid RAZR] dtrail1:
There are two different gpu oc codes in the source, but I think I will remove that one you mentioned. Try sys/class/misc/liveoc/gpu_oc_value (or something like that, forgot the name). This is the one which is used by trickster.

I could force the gpu [MENTION=3026137]416[/MENTION] but it would be a disadvantage. Read the post prior to yours, he managed it to get better scores.

416mhz is a frequency almost out of range of our available cpu power, if I'd set it to always stay on that freq it could cause bad performance on some devices and it would eat battery a lot. And I won't enable 512mhz because it would be hard to handle for most devices

Gnex has better cpu, so it can handle it.

Gesendet von meinem A101 mit Tapatalk 2
[Motorola Droid RAZR] ryankliber:
Been running the latest update to the 0.4.4 stable oce on the 5-11 carbon nightly for 12 hours now and it's been fully stable :)
[Motorola Droid RAZR] mat9v:
delete double post
[Motorola Droid RAZR] mat9v:
Hmm, could you make such a build just for testing if it is not so much work for you? I would like to try that (forced 416) - I have a HTC Sensation and in trickster I can select governor for GPU and so force certain frequency.

I can live with power drain, besides, screen is still much bigger drain than CPU/GPU combo. If you read my tests I tried testing [MENTION=322487]1000[/MENTION]Mhz with 1.2V and various GPU settings and there were no difference in scores. Please explain why is that so if power supply is a problem because [MENTION=322487]1000[/MENTION]Mhz CPU needs less than 1/4 of power that it uses [MENTION=1466104]135[/MENTION]0 1.410V so GPU should fly. Try using GPUmark of Bonsai Benchmark as they are much more consistent than Antutu.

Please understand, I'm not in any way trying to disrespect you or your work, I'm grateful anyone is working on improving this phone. Tell me if I can help in some way (except programming, I'm pants @ that).
[Motorola Droid RAZR] dtrail1:
Sure, I can do if you want that. It's not that much work :)

I didn't mean that power supply is a problem, I meant that the overall available power of our CPU isn't that good that the G-Nex CPU. We have a OMAP4430 CPU while the G-Nex uses a OMAP4460 CPU. The OMAP4460 can run on 1,5Ghz by factory and is overclockable up to over 2,0Ghz. There is a much bigger "space" for OCing the GPU even it is exactly the same (PowerVr SGX540). Silicon is limited, as all devices including the board need energy. YOu may get in touch with Merlinos1, he's an expert for overclocking and might explain that better and more understandable than me :)

However, I will make a build with forced GPU to 416mhz just for ya and PM it to you then. Give me an hour.

Btw: You gave me a new idea! Adding GPU governor support - if available! Besides of other features which are still wip, such like touch wake and BLX...
[Motorola Droid RAZR] dubisz:
In addition to the amount of power available to the chips, the decreased test performance may be caused by chip throttling if they're overheating. These kind of failsafes are usually hardware embedded and almost transparent for software.
[Motorola Droid RAZR] 1droidmod:
ahhhh, hate to say it but stable BSE just malfunctioned when i tryed to make a call.. Had to do volume up/down/power buttons again. Rom wouldn't load so had to use restore.zip... dont know if it is governor or what... was running it for 12hours or less, thought I was good to go.... Any thoughts? am i missing something? I have read thread with no luck.. Tyty

XT912 CDMA
[Motorola Droid RAZR] mat9v:
Did U disable FSYNC? I had that problem when overclocking with FSYNC disabled, it messed up filesystem, happened only when working in some file manager with system mounted RW. OTOH sometimes after bad reboot the system won't boot, stuck on green led - Power+Voldown would get it booting again (sometimes I must do this more than one time).
[Motorola Droid RAZR] dtrail1:
Currently adding a lot of new stuff!

- USB fast charge toggle

- GPU governor pvr backport (EXPERIMENTAL - not sure if it works)

- Deep Idle

- GPU custom Power Management

- OCE DPLL trim override new configuration for very high frequencies

- Added ARM CPU Topology

- Improved OMAP PM handling for more power savings

- Added HYPER governor (configured for our CPU)

- Enabled SCHED_AUTOGROUP

- Enabled ARCH_POWER (ARCH dependant power feature, saves power)

If everything goes well and it boots we'll have great improvements in power consumption!
[Motorola Droid RAZR] mat9v:
Certainly, we have a worse chip, even though the CPU and GPU are separate entities and overclocked independently. I'm quite happy with overall speed, it's GPU speed that's lacking in some games... Benchmarks that load GPU do not care about CPU all that much, test it yourself by observing CPU load while GPU test is running. Maybe there is something wrong with conditions for changing OC states? Is there any way to observe in real-time (or in log even) what is the GPU frequency, and I don't mean gpu_oc file or gpu_performance because they are "settings files" and do not reflect current frequency?
[Motorola Droid RAZR] dubisz:
Great to hear it, keep up the great work. The 0.4.4 JB Stable works great for me, but can't wait if it can get even better. What are the characteristics of the hyper governor? Sounds like a performance one :P
[Motorola Droid RAZR] dtrail1:
Yes, as I already mentioned: use dmesg to see the pr_info about GPU freq stats after changing the GPU OC value. It will show you the current frequency.
[Motorola Droid RAZR] dtrail1:
I can't help you if you:

1. Don't tell me what rom you use

2. Don't check the FAQ in the OP where many issues and possible solutions are explained

Do you guys read that stuff?? Maybe I should stop writing it if nobody reads it... I can remember a statement of DroidTh3ory on twitter:

"Folks always cried for a changelog. Finally I started posting it - but nobody reads it!"

:P
[Motorola Droid RAZR] ricardofago:
A similar thing has been happening with me at least three times a week since I've first flashed this kernel (only tried BSE). The phone dies eventually in its sleep, and if I force a reboot (power + both volume keys) and let it alone it won't boot, it will get stuck after BMM animation and before bootanimation with the green LED on. But if I reboot into BMM and just flash the kernel files again and then reboot, it boots fine.

I'm not sure if it's related to kernel, KEXEC or CyanogenMod base, but it's really annoying. I'm running LiquidSmooth v2.3 right now but I believe it also happened when I was testing Avatar (can't be sure, as I used it a quite a while ago for only a day or two). I don't use Trickster (I used it at first but now I don't even have it installed) and I have SetCPU but not enabled upon boot, I haven't been using it recently. Usually I check pegasusq governor and sio scheduler @ 100-1000 MHz.
[Motorola Droid RAZR] dtrail1:
As I said: This kernel has no guranatee to work well on other roms than CM10.1! For all testers with CM10.1 (GSM) it works very well so far.

BTW: If the phone doesn't boot after the FIRST reboot, just reboot again and it will boot.
[Motorola Droid RAZR] pseudoheld:
latest BSE running pretty stable however the wakeup does take quite some time longer than normal.

i was unable to attend a call because the phone was so laggy and unresponsive coming from deep sleep...

might try OCE next but im a battery whore so yeah...;)
[Motorola Droid RAZR] 1droidmod:
Thanks for the info...

---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------

u know what rom iam on, remember i was able to get previous BSE build to boot and u could not so i posted dropbox link for u...I know, 600++ posts, not ur responsibility to remember, sorry bout that, my bad... Pac Man 4.2.2