Database Info

[Q] fitting a custom-built cmos sensor to a host running android.

Hi
I work for a company that is in the business of private-security,and recently we decided to test the feasibility of creating a new product line of hand-held personal security recorders that will make use of RGB+IR channels image recording (reproduced from an in-house,custom built back camera based on one of the world's biggest manufacturers of raw cmos imaging sensors fitted with a proprietary bayer filter).
The host device is expected to be based on the ARM architecture and a powerful GPU chip (such as the the Adreno or Power VR latest chips) and although we haven't decided yet of the smart-phone brand that we'll be interested in converting,the model will probably belong to one of the biggest players in the market such as Samsung/HTC/Motorola etc.,and for the obvious reasons...
And here is the question...although we don't see any significant problems with fitting the custom-camera module instead of an original(,non-soldered,ofc...) camera box that comes with the OEM host device while maintaining the same footprint,power & heating envelopes and signaling interfaces (we have some great ASIC engineers here,I fully trust their abilities in that respect ),we're still unsure of our abilities to tweak the ROM of one of today's latest smartphones to include a custom driver (we'll probably hand to one of our affiliate software-house companies to do its coding...for a hefty fee ,not to mention re-writing a camera app,hopefully not from scratch...).
I'd be happy to hear from you,techies of your opinion regarding this project,and considering that some amount of reverse engineering here is a given (right ?),will it be possible to achieve the design goal of the software part of the project in (roughly) 6 months time-frame,and with a budget that should not exceed 250-300 K USD ?
Thanks in advance
David B.

still working on the camera app?
Sure.
Have you looked at other Android applications, which have partially achieved this? They exist.
From the sound of your inventory, you've talented engineers, resources and business sense. Specific issue is to do with variants in hardware and being able to support multiple devices, in most cases not at all 'generic'.
Sony IMX046 found within Xperia X10 models - 8.1MP and the IMX081PQ 16.1MP found in the Arc after debuting as a Cybershot. Both quite different devices, one having double resolution, back lit CMOS sensors and other features, radical enough to place it in a league of it's own. Now try to make that work with a HTC 5MP camera and conjunction it with the front facing camera when video conferencing...
Consider details like pixel arrays, focus, aperture, transistor gates, photo cathodes, anti-reflective coatings, firmware versions, available resolutions (not just desired), operating modes, effects... filters... all different for each device, each manufacturer, each version or release of Android.
To build an database of hardware, sensors, modes, focus sets, image formats, firmware and drivers itself is not hard but is the backbone of what you have in front of you. Provide a platform able to identify the package driver and hardware provider (the right 'glue') itself not overtly difficult or impossible.. perhaps a challenge!
Each driver, device, firmware has significant differences which can not be evaluated on 'one size fits all' method. A highly flexible architecture is required, modular in so far as to analyze and detect variations fail safe, apply the correct logic and driver for base provider as a structured and autonomous instance.
Consider this code from a Gingerbread firmware, designed for a Sony X10. SE will not release Gingerbread (2.3.x) for the X10 as they declared that 2.1 (Eclair) is suitable for the hardware and the software upgrade provides no value.
static const camera_size_type picture_sizes[] = {
{ 3264, 2448 }, // 8MP
{ 2592, 1944 }, // 5MP
{ 2560, 1920 }, // 5MP (reduced)
{ 2048, 1536 }, // 3MP QXGA
{ 1920, 1200 }, // WUXGA
{ 1920, 1080 }, // HD1080 - HDTV
{ 1600, 1200 }, // 2MP UXGA
{ 1680, 1050 }, // WSXGA+
{ 1600, 900 }, // HD+
{ 1440, 900 }, // WSXGA
{ 1280, 768 }, // WXGA
{ 1280, 720 }, // HD720 (HDTV)
{ 1152, 864 }, // XGA+
{ 1024, 768}, // 1MP XGA
{ 800, 600 }, // SVGA
{ 800, 480 }, // WVGA
{ 640, 480 }, // VGA
{ 352, 288 }, // CIF
{ 320, 240 }, // QVGA
{ 176, 144 } // QCIF
};
If you know what you are looking at, you can see some of these resolutions are not supported by the camera and will generate errors in software, leaving unhappy customers! Considering that this is an extract from an active AOSP project to port Gingerbread for the X10, for the love of doing it with no real benefit to the developers involved... it's not bad at all but will become refined into something more like this;
static const camera_size_type picture_sizes[] = {
{ 820, 616 },
{ 3280, 616 },
{ 3280, 2464 },
};
Reason the camera itself only supports 3 possible modes and these have to be defined exactly in the right way for it to work, for a single device and a single pixel out will error, even the order of the driver.. notice bold emphasis on resolution.
0.5Mp - 4X Horiz & Vert. | 2Mp - 4X Vertical Elim. | 8MP - Full Resolution​
Saying it simply, it's not impossible but it's not easy!

The overclock modules for HTC One XL, should be applicable on our One S

It can apply on phones running with Qualcomm MSM 8960 chipset.
Quoting from the OP:
One XL/AT&T/Rogers One X 1.8GHz overclock module
Please let me know about the module's compatibility with your phone. It has been reported to work on the latest AT&T version kernel, and I have a Rogers device myself.
Hey guys! I've created a kernel module that overclocks the MSM8960 Qualcomm Krait to over 1.8GHz. It also allows you to specify a custom voltage and frequency instead of 1.8GHz. This method works on ANY MSM8960-based rooted HTC One X, even on locked bootloader devices. This allows AT&T users to overclock, and others to overclock without necessarily needing to unlock the bootloader. This overclock makes the already tremendously fast MSM8960 about 20% faster.
Note that this mod is ONLY for the Qualcomm MSM8960-based Krait HTC One X and HTC One XL. This includes the AT&T HTC One X, Rogers HTC One X, and any phone branded as the HTC One XL.
The module is loaded using this command: insmod /data/local/krait_oc.ko pll_l_val=67 vdd_uv=1300000
The pll_l_val parameter determines how high the overclock is. Multiply this number by 27 to get the final clock speed in MHz. For example, 67*27 is 1809000, which is what the module defaults to.
The vdd_uv parameter determines the voltage used at the overclocked speed, in microvolts. The default for 1.5GHz is 1200000, and I was able to get a stable overclock at 1300000 at 1.8GHz. Raise the vdd_uv parameter if the overclock is unstable. The current maximum for this field is 1300000, so don't go higher than this. If your system crashes or is unstable at this frequency/voltage, lower the pll_l_val one by one until you reach stability. You can run rmmod krait_oc and then insmod krait_oc.ko with different parameters without having to reboot.
You'll also need a custom, tweaked thermald.conf. This thermald.conf raises thermal tolerances slightly (I've found that they're a little too strict, even at stock clocks and voltages). I've included this in the package, and instructions for installing it are below.
Video, demonstrating the overclock on a Rogers HTC One X:
YouTube Video
Screenshots
Source code is included in the package. If anyone has an HTC One S, this method will work on that, too. Please post below a dump of /system/lib/modules and I should be able to add support for any MSM8960-based HTC device with just that.
Instructions
First, determine which kernel module to use. Do an adb shell cat /proc/version and choose a ko file that matches your version number (these instructions assume you've renamed it to krait_oc.ko). 21/05/2012: If you don't see your kernel version here, try loading the module anyway. If it fails to load, please post a file from /system/lib/modules (any file) here and I will add support.
Install the overclock (only once):
1. Push the kernel module to your device:
adb push krait_oc.ko /data/local
2. Install the new thermald.conf, making sure to back up the old one, and reboot. The thermald.conf is included in the download. If you want to target a frequency other than 1809000 KHz, you should edit the thermald.conf and replace "1809000" to whatever frequency you want to target.
adb push thermald.conf /data/local
adb shell
su
mount -o rw,remount /system
cp /system/etc/thermald.conf /system/etc/thermald.conf.bak
rm -r /system/etc/thermald.conf
cp /data/local/thermald.conf /system/etc
reboot
Load the overclock (every time you reboot):
1. Load the kernel module (replace pll_l_val and vdd_uv with your desired voltages and L value as explained above. It defaults to 67 and 1300000 if you don't give it any parameters):
adb shell
su
insmod /data/local/krait_oc.ko pll_l_val=67 vdd_uv=1300000
2. Bring core 1 temporarily offline so it gets updated with the new max frequency:
echo 0 > /sys/devices/system/cpu/cpu1/online
3. You'll now have an additional CPU frequency! SetCPU can configure your maximum frequency up to this speed. You can also choose to keep running at 1.5GHz at any time - this method doesn't eliminate any available frequencies. Set the max at 1.8GHz to verify it's stable here.
4. Restart thermald by running "ps". Look for "thermald" in the list, and find thermald's pid (it's usually a number in the low hundreds, higher up in the list). Run "kill [thermald's PID]" in adb shell. The kernel does not currently have kernel-level temperature throttling turned on, so thermald is important for now.
Remove the overclock by restoring your backup of thermald.conf:
adb shell
su
mount -o rw,remount /system
rm -r /system/etc/thermald.conf
cp /system/etc/thermald.conf.bak /system/etc/thermald.conf
rm -r /system/etc/thermald.conf.bak
reboot
Rebooting clears any kernel modules that are loaded, so you're now clean. You can then delete anything left over in /data/local, but it doesn't matter.
If the module loads but the overclock doesn't seem to have any effect, even after putting max and min at 1.8GHz, your device might use a different SoC bin than the "nominal," and the kernel module is looking at the wrong place. Please reboot your device and post an adb shell dmesg right after the reboot so I can look at it.
Download current pack of modules:
http://www.setcpu.com/files/krait_oc_v2.zip (current)
http://www.setcpu.com/files/krait_oc.zip (old)
Finally, it'd be great if we as a community tried to work harder to encourage HTC to hurry up and 1. Release kernel source on time, all the time and 2. NOT cave into carrier pressure and stick to their written bootloader policy! S-OFF would be nice, too. 
Sent from my HTC One S using xda premium

LETS DO THIS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It also allows you to specify a custom voltage and frequency instead of 1.8GHz
Hehe... I'll test it tonight and undervolt a bit...

Is there any additional modification is needed in order to make it work on One S?
Sent from my HTC One S using xda premium

I tried this on my T-Mobile US One S and the frequency shows up in SetCPU. My Antutu score jumped 500 points, so if it did actually do something it was only an 7-8% gain. Antutu does recognize the cpu as having 1809 MHz. All other benchmarks that I ran have improvements as well.
Also, on step 4, you can locate the thermald process easier by doing the following:
ps | grep thermald
Nice post btw!

Overclocked to 1.8 GHz just now. So far stable. Running Antutu Benchmark right now.

Works - it's here. Now let's see...
Ahhh, and for the guys not on Linux: Copy the thermald.conf to sd card via usb and from there to its destination folder e.g. with root explorer.

Not to be Capt. Obvious here, but is there a point to overclocking the One S?
We're at about as fast as you can get before your eyes start bleeding. At the stock speed, my phone goes as fast as my eyes and thumbs can possibly move.
This is where all that quad-core Exynos crap goes right out the window. Seriously though, whats the point of OC'ing a phone that's already ridiculously fast?

nickmv said:
Not to be Capt. Obvious here, but is there a point to overclocking the One S?
We're at about as fast as you can get before your eyes start bleeding. At the stock speed, my phone goes as fast as my eyes and thumbs can possibly move.
This is where all that quad-core Exynos crap goes right out the window. Seriously though, whats the point of OC'ing a phone that's already ridiculously fast?
Click to expand...
Click to collapse
I think it's purely 'because we can'
Like you said, not really any need to, or tangible benefit in doing so

nickmv said:
Not to be Capt. Obvious here, but is there a point to overclocking the One S?
We're at about as fast as you can get before your eyes start bleeding. At the stock speed, my phone goes as fast as my eyes and thumbs can possibly move.
This is where all that quad-core Exynos crap goes right out the window. Seriously though, whats the point of OC'ing a phone that's already ridiculously fast?
Click to expand...
Click to collapse
IMHO we can benefit from undervolting in manners of battery life. The OC thing is a nice "side effect"
Gesendet von meinem HTC One S mit Tapatalk 2

hi i have tried to do this thing and i have gotten it to over clocked. the only thing i cant seem to find is the thermald thing to kill. all i see in the list ins system/bin/thermald. Is this the one im looking for or not?

I think I'd be more interested in slightly underclocking + altering voltage for a battery life boost

shinkinrui said:
I think I'd be more interested in slightly underclocking + altering voltage for a battery life boost
Click to expand...
Click to collapse
+1... even stock frequencies but with an undervolt possibility
I'm afraid we should wait a bit to get some sources...

Original OP here. You can undervolt more frequency steps with this method too, but you need to modify the sources. Most phones should have a "nominal" chip, but there's also a "fast" spec with lower voltages at each step.
I will write a proper tweakable undervolting driver for the 8960 when sources come out.

coolbho3000 said:
Original OP here. You can undervolt more frequency steps with this method too, but you need to modify the sources. Most phones should have a "nominal" chip, but there's also a "fast" spec with lower voltages at each step.
I will write a proper tweakable undervolting driver for the 8960 when sources come out.
Click to expand...
Click to collapse
As I'm not a dev... Could it be possible to override stock values in this struct, by specifying them manually?
Current one (in the source) :
/* Frequency-Voltage table */
static struct freq_voltage freq_vdd_table[] = {
{ 1620000, 1200000 },
{ 1728000, 1200000 },
{ 1809000, 1250000 },
{ 1917000, 1300000 },
{ 0, 0 },
};
Exemple "overriden" one :
/* Frequency-Voltage table */
static struct freq_voltage freq_vdd_table[] = {
[...]
{ 1512000, 1000000 },
{ 1620000, 1200000 },
{ 1728000, 1200000 },
{ 1809000, 1250000 },
{ 1917000, 1300000 },
{ 0, 0 },
};

Hi, can you add support for the EVO LTE?
kernel version is:
adb shell cat /proc/version
Linux version 3.0.8-01360-g3fd0422 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 S
MP PREEMPT Sat Apr 28 05:10:07 CST 2012
here's a random file in case you still need it.

Correct me if Im wrong but the One S packs a MSM8260A.. No? The 8960 was mainly made for LTE capabilities

mmdl1001 said:
Correct me if Im wrong but the One S packs a MSM8260A.. No? The 8960 was mainly made for LTE capabilities
Click to expand...
Click to collapse
I don't know. My One S is using MSM 8960 and LTE connection is present in my phone as well. May be only Asia version use MSM 8260A?
Sent from my HTC One S using xda premium

plakers said:
As I'm not a dev... Could it be possible to override stock values in this struct, by specifying them manually?
Current one (in the source) :
/* Frequency-Voltage table */
static struct freq_voltage freq_vdd_table[] = {
{ 1620000, 1200000 },
{ 1728000, 1200000 },
{ 1809000, 1250000 },
{ 1917000, 1300000 },
{ 0, 0 },
};
Exemple "overriden" one :
/* Frequency-Voltage table */
static struct freq_voltage freq_vdd_table[] = {
[...]
{ 1512000, 1000000 },
{ 1620000, 1200000 },
{ 1728000, 1200000 },
{ 1809000, 1250000 },
{ 1917000, 1300000 },
{ 0, 0 },
};
Click to expand...
Click to collapse
Well, it may be possible, but modifying that table won't work. The module needs a little modification.

fxzy said:
I don't know. My One S is using MSM 8960 and LTE connection is present in my phone as well. May be only Asia version use MSM 8260A?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
In Europe it´s the MSM8260A too with no LTE.
I´m from Spain. !

[PATCH]GPU OC 450->544MHz

After playing with GPU voltages and frequencies i noticed that default GPU voltage on my GT-I9505 is way too high for 450MHz operation.
Now i noticed, nobody really published any working GPU-OC (sorry if i missed)..
So, here is the patch:
PLL15 used exclusively for GPU top frequency.
GPU frequency = PLL15 / 2
PLL15 = 27MHz * ( l(least significant bits) + m / n ) [ 27*(0x28+1/3)=1089 ]
Code:
--- a/arch/arm/mach-msm/clock-8960.c
+++ b/arch/arm/mach-msm/clock-8960.c
@@ -6570,8 +6570,8 @@ static void __init reg_init(void)
/* Program PLL15 to 975MHz with ref clk = 27MHz */
configure_sr_pll(&pll15_config, &pll15_regs, 0);
} else if (cpu_is_apq8064ab()) {
- /* Program PLL15 to 900MHZ */
- pll15_config.l = 0x21 | BVAL(31, 7, 0x620);
+ /* Program PLL15 to 1089MHZ */
+ pll15_config.l = 0x28 | BVAL(31, 7, 0x620);
pll15_config.m = 0x1;
pll15_config.n = 0x3;
configure_sr_pll(&pll15_config, &pll15_regs, 0);
I used 544.5 MHz for about a week, playing mostly real racing 3 and NFS:most wanted.
Maximum OC could be much higher.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The score is form Antutu 3D test only.

pushistiky said:
After playing with GPU voltages and frequencies i noticed that default GPU voltage on my GT-I9505 is way too high for 450MHz operation.
Now i noticed, nobody really published any working GPU-OC (sorry if i missed)..
So, here is the patch:
PLL15 used exclusively for GPU top frequency.
GPU frequency = PLL15 / 2
PLL15 = 27MHz * ( l(least significant bits) + m / n ) [ 27*(0x28+1/3)=1089 ]
Code:
--- a/arch/arm/mach-msm/clock-8960.c
+++ b/arch/arm/mach-msm/clock-8960.c
@@ -6570,8 +6570,8 @@ static void __init reg_init(void)
/* Program PLL15 to 975MHz with ref clk = 27MHz */
configure_sr_pll(&pll15_config, &pll15_regs, 0);
} else if (cpu_is_apq8064ab()) {
- /* Program PLL15 to 900MHZ */
- pll15_config.l = 0x21 | BVAL(31, 7, 0x620);
+ /* Program PLL15 to 1089MHZ */
+ pll15_config.l = 0x28 | BVAL(31, 7, 0x620);
pll15_config.m = 0x1;
pll15_config.n = 0x3;
configure_sr_pll(&pll15_config, &pll15_regs, 0);
I used 544.5 MHz for about a week, playing mostly real racing 3 and NFS:most wanted.
Maximum OC could be much higher.
Click to expand...
Click to collapse
how i can use it?

geiti94 said:
how i can use it?
Click to expand...
Click to collapse
Don't take this thread serious! Look at antutu score. Way to low for our device. Some copy post I think

boterkaaseneieren said:
Don't take this thread serious! Look at antutu score. Way to low for our device. Some copy post I think
Click to expand...
Click to collapse
The score is form Antutu 3D test only. At default GPU frequency its ~6600.

boterkaaseneieren said:
Don't take this thread serious! Look at antutu score. Way to low for our device. Some copy post I think
Click to expand...
Click to collapse
You shold really start thinking before you post that non sense things
Lähetetty laitteesta GT-I9505 käyttäen Tapatalk 2:sta

Possible to make a cwm flashable zip?

luuranko3 said:
You shold really start thinking before you post that non sense things
Lähetetty laitteesta GT-I9505 käyttäen Tapatalk 2:sta
Click to expand...
Click to collapse
Yep its not the fist time he postet before he think.

jakemog said:
Possible to make a cwm flashable zip?
Click to expand...
Click to collapse
+1

Chronic kernel can be overclocked To 500mhz
How the hell you can See or change GPU voltage?

hanspampel said:
Yep its not the fist time he postet before he think.
Click to expand...
Click to collapse
Blabla that's what you think.

nadejo said:
Chronic kernel can be overclocked To 500mhz
How the hell you can See or change GPU voltage?
Click to expand...
Click to collapse
I would not bother to create an entire topic if there was a working source code published somewhere (Chronic sources dont change the frequency to 500, it stays 450)...
You can track how much people using this particular patch (or high GPU frequency) at
Triangle throughput: Textured - Offscreen (1080p)
Results of Samsung GT-I9505 Galaxy S4
Multiple entries at the end of the list are mine:
Code:
72 MTriangles/s 8 unregistered androidcommunityuser 2013.06.02
I didn't have any success with changing/programming VRM tables, i just noticed that VDD_DIG_NOMINAL is enough for 450 MHz (instead of VDD_DIG_HIGH).
P.S. Im sorry i answered this off topic nonsense.
Chronic kernel doesnt change PLL15 configuration, and entries for 450 and "500" are exactly the same:
https://github.com/Team-Hydra/android_kernel_samsung_jf/blob/cm-10.1/arch/arm/mach-msm/clock-8960.c
Code:
F_GFX3D(450000000, pll15, 1, 2),
F_GFX3D(500000000, pll15, 1, 2),

GPU OC to 500 Mhtz (450Mhtz default - configurable though 89chronic init script)
I can even overclock it without touching the script. I simply Use trickster mod APP.
And it works for me, no matter screen of or on. The GPU overclocking is almost perfect With its own 2governors.
im right, you're wrong!

nadejo said:
I simply Use trickster mod APP. And it works for me, no matter screen of or on. The GPU overclocking is almost perfect With its own 2governors.
Click to expand...
Click to collapse
No GPU options appear for me with trickster on the stock rom...?

XTCrefugee said:
No GPU options appear for me with trickster on the stock rom...?
Click to expand...
Click to collapse
i talk about chronic kernel for cm10.1 aosp rom. and it works

[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: http://d-h.st/woG
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: http://d-h.st/IbC
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/showthread.php?t=2368497
Diff Patch:
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))

Please anyone can benchmark it?
cant wait for your commit!

Here is Benchmark from AnTuTu Benchmark v3.3.2
Rom: SVHD v1.7.3
With Shaky Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With PachaRS v2.9 Kernel

mygamers said:
Here is Benchmark from AnTuTu Benchmark v3.3.2
Rom: SVHD v1.7.3
With Shaky Kernel
With PachaRS v2.9 Kernel
Click to expand...
Click to collapse
I get 509 (2d) and 1774(3d) stock cpu, stock gpu (with SmartASSv2 governor) and SIO as I/O scheduler(performance get a bit better when CFQ is in use).
We are talking about Sense rom? ..I'm wondering why the "Overclocked" versions get lower score than me
P.S. I can provide pictures if someone want some proof(I'm just lazy that's why I didn't to it already hahaahhaah)

XxXPachaXxX said:
Please anyone can benchmark it?
cant wait for your commit!
Click to expand...
Click to collapse
please see below...
mygamers said:
Here is Benchmark from AnTuTu Benchmark v3.3.2
Rom: SVHD v1.7.3
With Shaky Kernel
With PachaRS v2.9 Kernel
Click to expand...
Click to collapse
Hi, if you have used the last few kernel releases they shouldnt be benchmarked as I am working on 3d-core GPUOC, which fails to set above 245mhz resulting in both 2d/3d core running @192mhz which is underclocked afaik, once 3d-core gpu is achieved then you can benchmark.
Previous kernel where a user benchmarked in previous gpu thread only 2d-core was overclocked benchmark went from 400 range to 500 range, consider I overclocked by 50mhz thats roughly 1/4 of 192mhz, benchmark score is accurate as its performance improved by 1/4 of total previous 2d-core gpu score
and 2d core clk outputs 245mhz which is basically saying its overclocked
so with 2d-core OC results will be higher, working on 3d-core overclock which will make benchmark go even more higher
now onto 3d-core gpu

OP updated with correct link for 2D-CORE GPU ONLY

current 3d-core gpu states this within log:
<3>[ 404.075866] [CLK] clk_set_rate: failed to set clk: GRP_3D_CLK, rate=256000000, flags=0x200, rc=-22
<3>[ 404.379058] [CLK] clk_set_rate: failed to set clk: GRP_3D_CLK, rate=256000000, flags=0x200, rc=-22
<3>[ 404.527404] [CLK] clk_set_rate: failed to set clk: GRP_3D_CLK, rate=256000000, flags=0x200, rc=-22
<3>[ 404.910766] [CLK] clk_set_rate: failed to set clk: GRP_3D_CLK, rate=256000000, flags=0x200, rc=-22
I have a fix soon

evronetwork said:
I get 509 (2d) and 1774(3d) stock cpu, stock gpu (with SmartASSv2 governor) and SIO as I/O scheduler(performance get a bit better when CFQ is in use).
We are talking about Sense rom? ..I'm wondering why the "Overclocked" versions get lower score than me
P.S. I can provide pictures if someone want some proof(I'm just lazy that's why I didn't to it already hahaahhaah)
Click to expand...
Click to collapse
see my answer above
to double check flash 2d-core GPUOC then benchmark & check under sys/kernel/debug/clks/grp_2d_clk

My result
Rom: SVHD v1.7.3
Pacha-Kernel 2.9
2D-core OC only

before I can continue any further I need someone to get me the value of grp_3d_src_clk from 3dgpuoc test I can then drop a fixed 3d GPUOC
if someone cannot provide that value then I cannot OC 3dcore gpu

i can't find nor grp_3d_src_clk nor the file with all clks listed

Going to flash your kernel to help out. Do you want both Logcat and DSMG?

Is the main problem that 3d OC can't be set on boot?I used to flash it and after rebooting the benchmark fell from 18xx to 17xx(but still higher than that before flashing).I guess if it can be applied by init.d scripts .Thanks a lot for your aaaaaaaaaamazing work!

forzaferrari0 said:
i can't find nor grp_3d_src_clk nor the file with all clks listed
Click to expand...
Click to collapse
I'll see if I can temporarily get my hands on a Desire HD for this
EDIT: no access to device

hacktrix2006 said:
Going to flash your kernel to help out. Do you want both Logcat and DSMG?
Click to expand...
Click to collapse
no log or dmesg just the value under the grp_3d_src_clk (should be a folder with values in there)
sys/kernel/debug/clk/grp_3d_src_clk/

i found this:ebi_grp_3d_clk,
his value switch continuously from 0 to 192000000
with pacha kernel is firmly 0

forzaferrari0 said:
i found this:ebi_grp_3d_clk,
his value switch continuously from 0 to 192000000
with pacha kernel is firmly 0
Click to expand...
Click to collapse
nope only grp_3d_src_clk

OK Shaky156 will do just thought i ask first before hand as sometimes logcat and dmsg can be handy to have.

hacktrix2006 said:
Going to flash your kernel to help out. Do you want both Logcat and DSMG?
Click to expand...
Click to collapse
edit: He replied.Deleted.

[Q] Stock mi 4i downloaded phish.tmp and pattern.tmp - Malware?

Hi,
I received my phone yesterday and immediately after setting up my Google account on the phone, I updated it to latest version of MIUI [6.5.3.0(LXIMICD)] [Android version 5.0.2(LRX22G)].
After that I updated all preinstalled Playstore apps. Installed Google camera also. No other new apps were installed, no file was copied on to the phone, no file was downloaded.
After some time, I noticed that two files were automatically getting downloaded - "phish.tmp" and "pattern.tmp". It is available in the 'Downloads' folder.
It seems like people have noticed this behaviour on other miui phones, but no conclusion has yet been drawn.
http://en.miui.com/thread-83338-1-1.html
http://en.miui.com/thread-103122-2-1.html
http://en.miui.com/thread-86991-1-1.html
Can somebody throw some light on this?
Any way to find out which app downloaded it?
Anybody else noticed this, or am i the only one with this problem?

I also noticed it.. Didn't took it so seriously though [emoji14]
Will do some research and reply

I am also getting the same.

You can open both files as Text.
Phish.tmp is an endless list of Websites
Code:
mobile.28365365.com
www.yixingjia.com
avbbs.me
www.87654.com
www.gegeshe.com
ccc36.bjh868.net
gfw74.tk
msb.188bet.com
m.h367.com
www.ddaa44.com
mobile.yu8k.com
www.baiavbbs.com
m.youjizz.com
75515.com
www.axxbbs.com
www.new56.net
www.11xxzz.com
www.12ddd.www.avbbs.me
www.avbbs123.com
www.0820.com
174.139.109.38
m.jumeiouhua.net
baixxx789.com
www.viidii.info
www.5566889.com
666.hulingo.net
go.kk186.cn
www.h367.com
yk997.com
www.1144qq.com
www.yixingjia.info
jk7775.com
www.22444.com
www.8568888.com
www.zlvc.net
enhmm.com
www.14000.com.....
Pattern.tmp looks like this
Code:
{
"version":"1.1",
"features":[
{
"name":"Fei_xin",
"abstract":"Start with 12520",
"sms_type":1,
"address":{pattern:["^12520"]}
},
{
"name":"sms_body_length",
"sms_type":1,
"body":{body_len:["0-15"]}
},
{
"name":"bracket_title_not_personal_address",
"assist":true,
"address":{type:[1,2,3,4,5,6]},
"body": {
"or_pattern":[
"^(\\s)*【[\\u4E00-\\u9FFF|a-z|0-9|０-９| | |\\.]{2,12}】",
"【[\\u4E00-\\u9FFF|a-z|0-9|０-９| | |\\.]{2,12}】(\\s|\\u0000)*$",
"^(\\s)*\\[[\\u4E00-\\u9FFF|a-z|0-9|０-９| | |\\.]{2,12}\\]",
"\\[[\\u4E00-\\u9FFF|a-z|0-9|０-９| | |\\.]{2,12}\\](\\s|\\u0000)*$"
]}
},
{
"name":"important_info_body",
"assist":true,
"body": {
neg_pattern:["恭喜.*幸运.*奖品"],
"or_pattern":[
"尾号.{0,1}\\d{4}",
"券.{0,4}\\d{6,20}",
"验证码.{0,4}\\d{4,8}",
"密码.{0,4}\\d{6,10}"
]}
},
{
"name":"important_addr",
"assist":true,
"address":{type:[1,5]}
},
{
"name":"important_info",
"sms_type":1,
"combi":["bracket_title_not_personal_address&important_info_body",
"important_addr&important_info_body"]
},
{
"sms_type":1,
"name":"linking_up",
"body": {"or_pattern":[
"^(\\s)*\\(接上条\\)",
"^(\\s)*（接上条）",
"^(\\s)*(接上:|接上：|接上条：|接上条:)",
"^(\\s)*\\([1-9]/[1-9]\\)",
"^(\\s)*（[1-9]/[1-9]）"
]}
},
{
"sms_type":0x08000000,
"name":"fa_piao",
"body": {
num_types:[2],
body_len:["15-55"],
or_pattern:[
"(发|發|fa)(.|\\n)*(票|飘|漂|嫖|缥|螵|瞟|嘌|piao)",
"票发"
]}
},
{
"sms_type":0x08000000,
"name":"fa_piao_1",
"body": {
struct_types:[1],
num_types:[2],
body_len:["15-55"]
}
},
{
"sms_type":0x08000000,
"name":"bank_card_remittance",
"body": {
num_types:[0],
body_len:["15-55"],
or_pattern:[
"[工|农|侬|建|中|交|招|邮政].{0,14}行"
]}
},
{
"sms_type":0x08000000,
"name":"phish",
"body": {
struct_types:[2]
}
},
{
"name":"subscription",
"sms_type":0x00000100,
"body": {
"or_pattern":[
"^(\\s)*[\\[|【][\\u4E00-\\u9FFF]{0,8}(早报|晚报|手机报|快报|播报|预报|战报|晨报|新闻|奇闻|快讯|短讯|刊|阅读|百科|所学|小学|中学|小米)[\\u4E00-\\u9FFF]{0,4}[】|\\]]",
"[\\[|【][\\u4E00-\\u9FFF]{0,8}(早报|晚报|手机报|快报|播报|预报|战报|晨报|新闻|奇闻|快讯|短讯|刊|阅读|百科|所学|小学|中学|小米)[\\u4E00-\\u9FFF]{0,4}[】|\\]](\\s|\\u0000)*$",
"^(\\s)*[\\u4E00-\\u9FFF]{0,8}(早报|晚报|手机报|快报|播报|预报|战报|晨报|新闻|奇闻|快讯|短讯|刊|阅读|百科|所学|小学|中学|小米)[\\u4E00-\\u9FFF]{0,4}[:|：]"
]}
},
{
"name":"all_chinese",
"sms_type":0x00000100,
"body": {
"neg_pattern":[
"[^\\u4E00-\\u9FFF|，|。|\\n| | ]"
]}
},
{
"name":"multi_semicolo",
"sms_type":0x00000100,
"body": {
"or_pattern":[
"\\W1\\..{6,}\\W2\\..{6,}\\W3\\..{6,}",
"\\W1,.{6,}\\W2,.{6,}\\W3,.{6,}",
"\\W1、.{6,}\\W2、.{6,}\\W3、.{6,}",
"\\W1:.{6,}\\W2:.{6,}\\W3:.{6,}",
"\\W1：.{6,}\\W2：.{6,}\\W3：.{6,}",
".{6,};.{6,};.{6,};",
".{6,}；.{6,}；.{6,}；",
"(.|\\r){6,}\\n{1,}(.|\\r){6,}\\n{1,}(.|\\r){6,}"
]}
},
{
"name":"telephone_fee",
"sms_type":1,
"address":{"type":[1]},
"body": {"pattern":[
"[1-9][0-9]?元话费",
"(送|赠).*(移动|联通|电信)"
]}
},
{
"name":"official_phone",
"sms_type":0x00004000,
"address":{"type":[2]}
},
{
"name":"important_phone",
"sms_type":0x00001000,
"address":{"type":[1,5]}
}
]
}