Can anyone please without shouting and screaming, explain me what is that "Mali" thingy?
Tried to understand from the Dorimanx thread, and still dont have any idea what is it..
please :]
Do you mean the Mali GPU?
The Mali series of graphics processing units (GPUs) are semiconductor intellectual property cores produced by ARM Holdings for licensing in various ASIC designs by ARM partners. The core is mainly developed by ARM Norway, at the former Falanx company site.
Click to expand...
Click to collapse
It's kind of the equivalent of the graphics card in your pc.
Wikipedia Info
PC? You meant phone?
przemcio510 said:
PC? You meant phone?
Click to expand...
Click to collapse
No, his statement was an analogy. The Mali GPU is for the phone like a graphics card is for your PC.
I misunderstood his post earlier
{
"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"
}
Nevermind.
Why is it the hot topic at the moment? I noticed the name popping up at the same time that cm10 memory leaks were fixed... it seemed like a new version of dorimanx was released that was compatible with this newly updated cm10 and it had mali in the title. How come Mali appears in the title and does it have any relation to the memory leaks fix or am I getting it all mixed up inside in my head? (Most likely scenario)
---------- Post added at 10:53 PM ---------- Previous post was at 10:32 PM ----------
Okay I've done some more searching and I think this is what it's all about... Up until now there has been a memory leak in CM10 due to not knowing how to have the Kernel interact with the graphics hardware (The drivers for the Mali Graphics chip were changed with the jump to Jellybean?) but now this has been fixed (probably as a result of obtaining and analysing the original Samsung jellybean kernel source code). Dorimanx's latest kernel uses this newer source code and as a result it has the name of the graphics chip (Mali) in the title.
Is that fairly accurate?
If you're talking about MALI, yes that's the GPU (graphics processing unit) Something like the equivalent to a graphics card on your computer.
However if you're talking about the smali code thats been altered to fix the memory leak issue, that has nothing to do with the GPU. Its a coding language. To be more precise, an assembler for the dalvik virtual machine your phone runs on.
Sent from my GT-I9100 using xda app-developers app
Related
Found this tread in the General section, and thought it is a good theme to work on.
(Originally posted by Martin4os)
can we somehow, upgrade our version of OpenGL ES-CM 1.1 to OpenGL ES 2.0 ...
cause i found 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"
}
and as you can see, our Optimus One is tested using openGL 2.0, and somehow i think its not a bad score.. And I'm pretty sure, our adreno 200 supports OpenGL
Also I read some threads, (I can't find them at the moment) about a developer, who succesfully applied that on nexus one ...
gocegi said:
Found this tread in the General section, and thought it is a good theme to work on.
(Originally posted by Martin4os)
can we somehow, upgrade our version of OpenGL ES-CM 1.1 to OpenGL ES 2.0 ...
cause i found this ..
and as you can see, our Optimus One is tested using openGL 2.0, and somehow i think its not a bad score.. And I'm pretty sure, our adreno 200 supports OpenGL
Also I read some threads, (I can't find them at the moment) about a developer, who succesfully applied that on nexus one ...
Click to expand...
Click to collapse
Lol, what a haxxed test sheet . Iphone 4 on the buttom of the list says it all . Not to mention the top 3 which is just dumb.
Yes, maybe the results are a bit different than expected, but thats not the point.. the point is that theoretically OpenGL Es can be upgraded to 2.0 since the benchmark uses that to compare the phones ... Also i found this
http://forum.xda-developers.com/showthread.php?t=620598
As you can see, the dev succesfully did that on his nexus one ... And if it can be done, it should
Why do you think that we don't have opengles 2.0?
mik_os said:
Why do you think that we don't have opengles 2.0?
Click to expand...
Click to collapse
I think we do, but I'm not 100% sure.
Me too
In link from Martin4os application developer succesfully used opengles2. Drivers already have opengles2 support.
well i know adreno 200 supports 2.0, but i don't know if it's implemented in the software ... i'll try some opengl es 2.0 apk to see if its working ..
mik_os said:
Me too
In link from Martin4os application developer succesfully used opengles2. Drivers already have opengles2 support.
Click to expand...
Click to collapse
that answers the question than! Thanks Mik
I was flashing rage kernel v2.6 on my st15i. The screenshot below has this S1 partID......... which i pointed out. Does this mean there is something wrong with my ST15i. I'm not new to flashing kernels and roms. Please clarify.
{
"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"
}
Yes there is something wrong. That 179 counts the days that your device will eventually get bricked, it counts down to 0 then boom, you're officially ****ed.
Actually im just trolling No there is nothing wrong, its just the hex address of the specific block in which the boot image is written on the internal memory of the phone.
woof! I would have been runnin around the net if would not have read the last part. Thanks anyway.
So every time I flash a kernel different addresses are used OR a particular kernel uses only particular address ???
iamsuperuser said:
woof! I would have been runnin around the net if would not have read the last part. Thanks anyway.
So every time I flash a kernel different addresses are used OR a particular kernel uses only particular address ???
Click to expand...
Click to collapse
Depends on kernel, but mostly should stay same addresses.
Don't worry, if it is different, nothing bad will happen.
I think its based upon the kernel. CM kernels might have a different address shown on there, Stock ones a different address and so on.
All these are speculations ofcourse, its what i make out of the lines. Its nothing to worry about
iamsuperuser said:
woof! I would have been runnin around the net if would not have read the last part. Thanks anyway.
So every time I flash a kernel different addresses are used OR a particular kernel uses only particular address ???
Click to expand...
Click to collapse
That address was absolute kernel blocks address.
0x00000148 - 0x00000179 = 32 blocks
1 block = 256KB
So kernel partition size :
32 x 256KB = 8192KB
Your device will doomed if you have alot of bad block.
Sent from my ST17i using Tapatalk
This is for anyone who is rooted!!
Lets see those variant's cpu's you have for more undervolting and saving battery:good:.
Where can I find that Variant?
You have to have BLADE kernel by maxwen installed. Then use
Code:
cat /sys/kernel/tegra3_dvfs/cpu_millivolts
and it will be printed on top (process_id) is your variant.
Here is a screenshot from my device:
{
"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"
}
What is a variant, and where did it come from?
This is mainly the type of build quality your chip has and allows a more accurate way to determine how hard you can push you're chip with Undervolting(UV) and Overclock(OC).
Click to expand...
Click to collapse
AP37 have 2 different types (3 and 4) of variant's.Hox has 4 types.
Please note that there are even more variants in each variant. You can easily have a variant 3 and another person has the same but you still have different performance. "They qualified the chips based on random sampling of the wafers and mark the ENTIRE wafers as such. It just means that the "average" performance of that wafer is of certain quality, but it does NOT mean every chip on that wafer would behave exactly the same.... ". Remember the golden rule: No two chips are created equal!
Also people should not blame HTC as they don't test every chip Nvidia made. They only test a few and then the phones will go in to production. So if you want to rage at someone please don't do so at HTC
Click to expand...
Click to collapse
All credit goes to our Blade kernel developer maxwen and timlambo for his poll
I have variant #4 in my HOX+
variant 3. so which is which?
You can try undervolting by using blade kernel.
For example undervolting -50mV:
Code:
echo -50 > /sys/kernel/tegra3_dvfs/cpu_millivolts
For -100 mV just change value:
Code:
echo -100 > /sys/kernel/tegra3_dvfs/cpu_millivolts
My device has variant 3 and undervolted -100mV.Seems stable for my variant.Please just try and post your undervolting results.
Also i will have request for more undervolting support(for now max -100mV supported) for blade kernel from maxwen.
Best regards
4 here
Hello, the main problem is that any app using advanced graphics is crashing on me, so I decided to make a test and downloaded OpenGL ES 2.0 Demo to try.
And the result that I get was unbelievable, there's a gallery of my screenshots.
{
"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"
}
As for my phone, I already had a long story with it, there's the thread, where you can get all the info on the other site, but I'm not able to post links yet, but if you Google " Screwed up my G+ K3" you can find it.
If anyone can help me to get the GPU to work properly, I would be superthankful, I am already starting to lose my mind.
Seems like your GPU is damaged.
abhinavp649 said:
Seems like your GPU is damaged.
Click to expand...
Click to collapse
Can this be a result of bad drivers or something? I don't really know much about drivers on Android, if there are even some. There's a firmware for another GPU installed, so it might be the cause, but I got no idea how to fix it.
WilliamCZ said:
Can this be a result of bad drivers or something? I don't really know much about drivers on Android, if there are even some. There's a firmware for another GPU installed, so it might be the cause, but I got no idea how to fix it.
Click to expand...
Click to collapse
Very VERY likely if it was anything along those lines it would not be general user serviceable by any means.
Sent from my XT1060 using Tapatalk
siccoblue said:
Very VERY likely if it was anything along those lines it would not be general user serviceable by any means.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Well, if I'm getting it right, there's actually nothing to do it that just by my hands then. Since the firmware thinks, that there's another CPU and GPU installed, would flashing to the other firmware (some MT6572 one) work? I had a bad time when trying to port another firmware to it, it didn't boot or I just wasn't able to flash it - was getting errors.
Now, I know for a fact that this phone does NOT have OEM support for Android 4.4. However, LG provides a lovely open source program, so I do have two sets of files.
One is for building the kernel for the phone, with all of the OEM-specific files for doing so, including drivers and such.
The other is I believe to be the device tree for the US760, with a bunch of propitiatory code. I'm not sure what exactly is important there.
The latest version of Android this device natively ran on was Froyo, and then didn't receive updates because the device didn't do very well sales wise.
My main question is if using that code is worth it, or if I should just go with basing off of a generic AOSP device tree for the processor and seeing how things go. There's little to no documentation on this phone (GSM/Phone Arena don't have almost any info, doesn't even exist on Wikipedia) so it's a bit difficult to get accurate specs for the device, but here goes.
(From HardReset.info)
Chipset: Qualcomm Snapdragon S1 QSD8650
CPU #1 Type: Scorpion
CPU #1 freq.: 1000.0 MHz (1-core)
GPU Type: Qualcomm Adreno 200
RAM Memory: 512.0 MB
Are those specs even enough to run Android 4.4? I don't mean run well by any means, but would the device even work?
My biggest concern is the dual screens. I don't know if it's a hardware switch or something baked into the kernel or something, but I'm not sure how well it would work if I based off of AOSP, or if only one screen would work, or if the phone just wouldn't boot. Here's a picture or two so you know what I mean.
{
"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"
}
Interested to see if anyone has any wisdom to bestow upon me.
Bit of an update.
Found out that the HTC Droid Incredible would be a great base for a Cyanogenmod rom.