yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] _delice_doluca_:
hi,

i am kind of addicted about the GPU performances of the mobile devices because i believe the CPU tech is already way ahead of todays needings for mobile worlds.. and i need your opinons and even -if you wouldn't mind spending some time- your tests to decide..

novadays i am planning to buy galaxy note, it catches my eyes with its beautiful (not huge, but georgeus) screen even though it has black rendering issues :)

anyway the thing is the most beautiful apps and games comes from the apple side and the apple devices has good GPUs with average CPUs.. this is also excatly what a good movie in mp4 format needs.. so this is why i believe GPU has a superior roleplay than a CPU novadays devices..

in the raw power/resolution comparison ipad 2 is first with its PowerVR 543MP2/(1024x768)

i guess SGS3 is the 2nd one with OCed mali-400/(1280x720)

so lets create chart to compare them: take the GL benchmark egypt offscreen results and divide them with their resolutions and multiple the results with 100000 (since the result will be very small) i guess this should tell us about the gameplaying capibilities of a device (correct me if i am wrong)

according to this;

the ipad2 scores; 90x100000/1024x768= 11,444 points

the new ipad scores; 136x100000/2048x1536=4,323

SGS3 scores; 102x100000/1280x720= 11,067

GNote scores; 50x100000/1280x720= 4,882 (50 is what i get from glbenchmark web site, i did not run the test myself)

so my questions are; will we get 74,9 FPS(simply (50 FPS X 400Mhz/267Mhz) points on GL benchmark egypt offscreen by simply overclocking the GPU to 400 Mhz from 267Mhz (i guess this is the stock clock) just like SGS3 and why are we not getting 102 like it? is this the Nm making the difference or the drivers? and can someone with OCed GPU run the test and tell the results?

thanks..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Kangal:
Its all about:

-quality of the SoC (some can handle heavy stress better)

-drivers!

-kernel implementation

...and to a much lesser point, any optimizations/problems affected by high-level data, example the ROM.

Unfortunately, gpu doesn't work the way you think.

Usually benchmark score points show innovation in the gpu performance proceeding in a "Exponential Slope" whereas they're actually increasing in a more "Plateau" slope.

In fact, almost all improvements are software based.

A Exynos 3110 (1st-gen SGX540) can in practice perform as well as the gpu in the SGS3 or EVEN BETTER, depending on its setup.

This is a similar case to the PS3 vs 360. The PS3 has a much much more powerful gpu, however Xbox games look just as well as PS3 games, and even better, because they are encoded in DirectX format compared to SONY's proprietary SDK solution. Then again there is the RAM issue in both consoles
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] psionic11:
60 frame per second cap

Some things to consider in your graphics comparisons:

http://xdaforums.com/showthread.php?t=1169188

http://answers.unity3d.com/questions/32841/is-it-possible-to-get-above-30-fps-on-an-ios-devic.html

This quote explains it best:

Frankly, your opinion is uneducated. The screen of the Galaxy S II has a refresh rate of 60 Hertz, meaning the screen physically cannot display any material higher than 60 frames per second. If you uncap the software frame rate, then the CPU and GPU of the phone will work harder to render as much material as possible - let's say in this case, we have something that has 80 frames to display in a single second. Yet since the screen cannot display 80 frames per second, 20 of those frames will never be shown, and the resulting movement could even suffer from tearing because of the mismatched refresh rate and frame rate. In order to fix tearing, a technique called vertical sync is employed, which would cut frame rates to 60fps in order to eliminate the extra frames which cause tearing.

So, if we remove the frame rate cap on Samsung's version of Android, then what do we accomplish? We increase the workload on the phone's processors, increasing heat output and decreasing battery life. Rendering above 60fps will generate frames which are never shown, and will introduce visual glitches if vertical sync is not used; vertical sync, in turn, would cap the frame rate to 60fps once again. I hope this post has been helpful.
[Galaxy S I9000 Android Development] DerTeufel1980:
This kernel is based on teamhacksung's kernel for Jellybean

Many Thanks to:

Teamhacksung

Zacharias.maladroit

Onecosmic

ytt3r

TK Glitch

Ezekeel

Eugene373

franciscofranco

Sunra

scheichuwe

perka

sztupy, for his great work, to get usb host mode driver

mialwe

stratosk

F4k for the idea to flash bigmem libs

...

Working on this kernel is taking many hours almost every day. With a small donation, you show me, that my work is appreciated by you.

If you like this kernel, please donate to me

Download link and changelog can be found here:

Kernels with VC in the name are coming with Voodoo Color
[Galaxy S I9000 Android Development] DerTeufel1980:
going to be filled soon ;)
[Galaxy S I9000 Android Development] H-Body:
Great work as always :)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] DerTeufel1980:
i am sorry to tell you this, but cwm backups are not working, because i have forgotten to remove the /datadata partition from cwm, but this, of course, can't be mounted :(
[Galaxy S I9000 Android Development] Szighy:
Sorry, I'm confused...so the latest version 1.0.3 shouldn't work on your jb rom because it has /datadata?
[Galaxy S I9000 Android Development] DerTeufel1980:
only cwm backup does not work

edit: i should have read your post better....yes, it doesn't work on my rom. kernel for my rom can by found at my rom thread, where you already found it ;)
[Galaxy S I9000 Android Development] Szighy:
hm...not what i asked :P first i tried to flash a kernel from the link in this thread on your rom, and it wouldn't boot, then i found the ones with /datadata :P now it's working fine...
[Galaxy S I9000 Android Development] malcho:
Fantastic work.Really good combo cm10 and this kernel.
[Galaxy S I9000 Android Development] nikhilonlive:
Great work man.

Thanks
[Galaxy S I9000 Android Development] joeching:
Nice kernel, work with 0723, very smooth n fast...
[Galaxy S I9000 Android Development] alwo1303:
I' ve problem to get the new kernel work on Slim JB V5 ?

the Devil 3.1.00 RC4 ist working good, but when i install the new kernel the i9000 ist always hangin on the devil boot screen!

when i flash back to 3.1 rc4 it works :(
[Galaxy S I9000 Android Development] DerTeufel1980:
i guess the rom is too old, and does not have the new hw composer to use "butter".
[Galaxy S I9000 Android Development] joeching:
Tested, work with 0725.:thumbup:
[Galaxy S I9000 Android Development] kuribo67:
I've got a problem when I install the kernel.

I'm on your ROM V6, and when I flash the kernel it reboot but it's going back to the recovery and say "can't mount SDCARD installation aborted" and it's bootlooping.

I've flashed back the kernel 1.0.2 and it's ok.
[Galaxy S I9000 Android Development] DerTeufel1980:
The op says, that this kernel is not for my rom. You find the link to the correct ones at the rom thread

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] movitum:
installed on 25/07 build and didn't notice anything wrong so far :good:
[Galaxy S I9000 Android Development] leonardoafa:
This Kernel works with the mkalter V6 ROM???
[Galaxy S I9000 Android Development] yahyoh:
thank u for Jb kernel thread :good:

i think this change need to be in kernel ?

http://review.cyanogenmod.com/#/c/20072/
[Galaxy S I9000 Android Development] Kurre:
AFAIK, you can also add that line to init.aries.rc file in system root / :)
[Galaxy S I9000 Android Development] yahyoh:
is elite use datadata or not ?
[Galaxy S I9000 Android Development] BlueFlame4:
May be a stupid question but I haven't found any answer for it. What does Devil Idle exactly do?

Thanks in advance!
[Galaxy S I9000 Android Development] matesc:
search! :)
[Galaxy S I9000 Android Development] Silentbob999:
Stats look good to me.

Just one thing about liveOC, the value stick when you restart the app but the slider always reset to the max... So if I touch it by mistake it will set a value around 150 which makes my phone reboot... Hopefully, when the phone boot it is back to liveOC 100...

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] oscar73:
Huuummm no internal storage after flash Devil's Kernel....is it "normal"?

I'm on Alpha CM10 from pawipt
[Galaxy S I9000 Android Development] BradleyR2010:
Yeh i was working in adding Live OC when i got the PM from DerTeufel1980 with the info about IDLE2, so in a rush to release IDLE2 functions, I left Live OC there and it has a few bugs, Im working on them and ill release a fix later today.

Please update to the latest version, Live OC bug is gone :)
[Galaxy S I9000 Android Development] purpleraintoxicity:
Since I've flashed the latest jb kernel, the screen has some interference... I don't know how to describe it...

Like that thing happened back in the days when we were putting a Nokia phone next to the screen... :)

Anyone else has it?
[Galaxy S I9000 Android Development] djlukas1983:
Hey Der Teufel. TWRP isn't working in Devil 1.1.0. When I try to load it, it hangs at Devil logo. CWM work like it should.
[Galaxy S I9000 Android Development] AlwaysDroid:
+1 Can confirm, I just tried it.
[Galaxy S I9000 Android Development] bhu1:
@derteufel what is the touch sensitivity set ?? It will be really appreciated if touch sensitivity can be set exactly like chain fire's values. Or u can give an option like in semaphore kernel.
[Galaxy S I9000 Android Development] polarstar:
Hi,

I have tried flashing Helly Bean from below URL but phone got stuck in bootloop. Can you tell where I am wrong ?

http://download.rinik.de/android/De...an/rom/20120802/helly_bean_i9000_20120802.zip.

Coming from ZSJW4, rooted with CF-Root-XX_OXA_JW4-v4.4-CWM3RFS, then installed XXJVT modem from CWM recovery.

Finally, JB from CWM recovery but it gets stucked in bootloop with devil's kernel.

I hope I followed right approach, please point me in right direction !

Thanks
[Galaxy S I9000 Android Development] AlwaysDroid:
Format system, cache, data and datadata and then flash hellybean. Do NOT flash this kernel though, it does not support datadata. The one in the hellybean thread will. Good Luck!
[Galaxy S I9000 Android Development] DerTeufel1980:
Thanks. I ll look at it.

It's the same as stock.

How does semaphore change the values? Isn't it an init.d script? If yes, it should work here, too. If not, I'll try to find some time for this.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] bhu1:
Semaphore has default values but semaphore manager has option to set chainfire or mialwe's touch values.
[Galaxy S I9000 Android Development] Kurre:
Is it really working in semaphore? Since I recall looking up those files where values were echoed and found nothing (when i was testing ICS with semaphore) :eek: so I was left with impression that those were working in GB, but not in ICS anymore. I might be wrong and would like to have clarification for this :D
[Galaxy S I9000 Android Development] yahyoh:
its use script to change sensitivity :o
[Galaxy S I9000 Android Development] DerTeufel1980:
confirmed...twrp not working...at the moment idk what's wrong with it. did not touch it since some time...
[Galaxy S I9000 Android Development] .:Crack:.:
Hey Teufel,

I'm Having A Big Problem With The Latest Version...

Whenever My Screen Is Off, The Phone Runs At The user_max, I.e. 800Mhz for me. Tested with no scripts,devil idle whatsoever... additionally lock min freq doesn't stick after screen on off (fixed it with a script for me).

Flashed back to 1.04 and everything is fine (lock min doesn't work either)
[Galaxy S I9000 Android Development] DerTeufel1980:
you mean, if you set user_max to 1000 mhz, it runs with 1000 all the time, while sscreen is off?
[Galaxy S I9000 Android Development] .:Crack:.:
I didn't try 1000 MHz but with 800,400,200 it acts that way,yes.

So the only way to prevent drain is setting user max to 100 for me..
[Galaxy S I9000 Android Development] DerTeufel1980:
please try setting it to 1000, and check again. also, are you using the idle2?
[Galaxy S I9000 Android Development] .:Crack:.:
Wait a sec, I'll flash 1.10 again...

Yes idle was on. BTW which state is "good"?:p didnt vread the idle thread
[Galaxy S I9000 Android Development] DerTeufel1980:
just try devil kernel manger for the stats :) it's showing top=on and top=off, as you know it from deep_idle2

me was asking about idle2, because it uses 800 mhz by entering the idle mode. if you limit the max freq below 800, it uses this freq. this is why i asked to push the limit to 1000. if it uses still 800 then, then it is the idle2....but it should not stay at 800mhz all the time while screen off ;)
[Galaxy S I9000 Android Development] .:Crack:.:
So state2 is top off and state1 top on?

OK after testing I realized it sticks at 800 while listening to music. Otherwise I get deep sleep pretty fast

Edit. Is there a way to reset the idle2 stats? Echoing 0 gives me permission a denied

Edit2 yup, disabled idle and my phone is running at 100 with screen off and music

Edit3 will be back on Monday... no internet til then. Hope you'll fix it!
[Galaxy S I9000 Android Development] purpleraintoxicity:
I don't know if it's related to the kernel or the Rom,

But super user takes long time to give permissions.

Also in dkm, every time I touch some setting, phone stock for a sec till the change activated.

I'm addition, better battery states, ask for permission every freaking time I unlock the phone our disconnecting it from ac....

Using devil 1.1.0jb with cm10
[Galaxy S I9000 Android Development] DerTeufel1980:
i only can tell from hellys_bean with my kernel, but i don't have issues with long waiting for super user.

as superuser is an app, and su binary comes with the rom, it should not be related to the kernel, but of course, you could try if a different kernel changes some thing.
[Galaxy S I9000 Android Development] purpleraintoxicity:
Mmmm no, I use only your kernel... other are either laggy or has bad battery life.

Also I want to have as much control as I can get on the phone haha...

Tell me, what is the best fudgeswap value?

On stock 512, my phone get stuck I've in a while.

Tried -512 but phone was laggy as hell on unlock
[Galaxy S I9000 Android Development] yahyoh:
try to update su binary

and bbs normal everytime u disconnect charger it will get su permission idk why :eek:

---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------

ya devil is amazing kernel to control every single thing can be controlled

i'm still searching about fudgeswap and what really do :confused: but didnt find any thing helpful over the net :o
[Galaxy S I9000 Android Development] AlwaysDroid:
I get the BBS problem to. It asks me about 4 times in a row even if I press remember. So annoying. But the su does that to me sometimes, could always try updating though.
[Galaxy S I9000 Android Development] monjovega:
Does it have to be that the Devil Kernel Config and Settings>Performance has to be the same for overlocking speeds? If both are not the same which settings will the phone follow?
[Galaxy S I9000 Android Development] AlwaysDroid:
You cant overclock with Devil Kernel Config!
[Galaxy S I9000 Android Development] Kurre:
Well, those have only CPU governor and zram settings in common, right? I have used DKC's init.d file and for example CPU governor have been correctly set by it.
[Galaxy S I9000 Android Development] kuribo67:
edit : delete this one, wrong section
[Galaxy S I9000 Android Development] everb00b:
@purpleraintoxicity about superuser.

try binary update and maybe move to SuperSU.

supersu solved my su problems.
[Galaxy S I9000 Android Development] purpleraintoxicity:
I have updated the binaries...

Now, after more then a day with stock kernel of cm10,I didn't had no su problems, I'll move to devil today and see if it's back
[Galaxy S I9000 Android Development] thestudent00:
I know it was mentioned some days before. But wanted to confirm. With IDLE2 on my sgs sticks on 800mhz when screen off and hearing music. With IDLE2 off it sticks on 200mhz. 100mhz doesn't work for me. It's like on the early ics days. There 100mhz didn't work in the beginning.
[Galaxy S I9000 Android Development] AlwaysDroid:
I have that to, but also for me, when listening to music the screen won't turn back on .. very strange.
[Galaxy S I9000 Android Development] .:Crack:.:
Yea still have the problem.

For the 100MHz place this script in init.d (remove the .zip - its not actually zipped, just renamed for the upload). Works fine then :)
[Galaxy S I9000 Android Development] DerTeufel1980:
i have been i contact with the idle2 developer (thalamus), for testing some things for him (his devices is gone to repair service, as it died by pulling the battery...be careful by doing this).

the cpu is wanted to go to 800 mhz while screen off and playing music.

in idle2 mode, the cou jumps to 800 mhz in order to encode the mp3, and then falls back to idle mode, as fast as possible. with 800 mhz encoding is done much faster, and idle2 can be reached faster again.

100 mhz bug is fixed in next build.
[Galaxy S I9000 Android Development] .:Crack:.:
It sticked for 9h at 800Mhz for me, I guess that's not intended :D
[Galaxy S I9000 Android Development] DerTeufel1980:
maybe you were listening to music for 4 days :D

i think, that cpu spy maybe is not displaying correct. i try to make some tests. what i think is, that the cpu is not in deep idle, while idle2 is active. although the cpu is not active during this, cpu spy does not know which state to display, and just takes the last cpu freq state. with previous deep_idle 2 this previous state was changing, because freq wasn't fixed. then cpu spy was using different freq to fill up the stats, and you didn't notice anything.

now that the previous state always is 800, it seems like it was used all the time...maybe i am totally wrong...starting playing music now ;)
[Galaxy S I9000 Android Development] .:Crack:.:
Yeah maybe, you have more knowledge than me :p SetCPU also displayed 9h of 800mhz (over night)
[Galaxy S I9000 Android Development] thestudent00:
Yeah, maybe its how it should work. And our spy apps show it wrong. Wait for your test results.
[Galaxy S I9000 Android Development] yahyoh:
ram here goes down too much and system start to killing apps even with xl ram + 150mb zram the used ram never get restored after closing some apps idk why
[Galaxy S I9000 Android Development] thETImo:
I flashed 1.1.0 over 1.0.4 and got stuck in the kernel boot image..?
[Galaxy S I9000 Android Development] thestudent00:
Can u boot to cwm and try flash again? I flashed without problems. And only for info there is 1.1.2 on server
[Galaxy S I9000 Android Development] thETImo:
No, I was simply stuck to the boot. Had to reflash my JB all the way from the start.
[Galaxy S I9000 Android Development] yahyoh:
3_ 1.1.2 up :)

http://rootaxbox.no-ip.org/derteufel/jellybean/i9000/112/
[Galaxy S I9000 Android Development] MetalPainis:
Works ;) and 200Mhz bug appears to be fixed :)

Ty DerTeufel
[Galaxy S I9000 Android Development] thestudent00:
yes, no 200mhz bug for me with 3_1.2.0
[Galaxy S I9000 Android Development] tenos:
Battery Drain with Idle2

Hello @all,

my battery drain is higer since Devil3_1.1.0.

I think it is IDLE2, with Idle2 I get in the stats Idle results (normal), then TOP=ON results (normal) and TOP=OFF results (abnormal) because bluetooth isn't killed, but this extra TOP=OFF doesn't save me more energy!?

so I flashed back to Devil3_1.0.3 and here I don't get TOP=OFF results but battery life is extremely better.

I haven't changed anything on the Phone just the Kernels, I'm running on Slim Bean 1.0.

CU

tenos
[Galaxy S I9000 Android Development] strickyy:
Am I the only one with lots of "sudden deaths" I believe they're called? When the phone just doesn't wake up and a reboot is needed. I don't even use LiveOC or any similar changes applied, and its still far from stable.
[Galaxy S I9000 Android Development] troyan1988:
I've got the same problem with SoDs. Sometimes when screen is off and I'm trying to wake it up by pressing power button or menu button then screen remains black and smartphone does not repond at all.
[Galaxy S I9000 Android Development] troyan1988:
I've got the same problem with SoDs. Sometimes when screen is off and I'm trying to wake it up by pressing power button or menu button then screen remains black and smartphone does not repond at all.

edit: it happend on 1.1.2 build for JB, CMC version installed by zip file

only touch buttons (back and menu) respond

here you are logcat from such situation (in logcat.zip file)
[Galaxy S I9000 Android Development] 6bloody6eddie6:
Anyone using this kernel with ParanoidAndroid JB?? Is it stable?
[Galaxy S I9000 Android Development] AlwaysDroid:
For all you guys having sods , install ns tools and bump up the voltage for 100MHz by 50, and 50 on int.

If it fixes it, slowly decrease the voltage and use it for a day or two until you find a stable combo. Worked on my friends sgs :)
[Galaxy S I9000 Android Development] MetalPainis:
My battery drain increased a lot on 1.1.0 and 1.1.2 (about x2 I think) reverted back to pre Idle2 and it feels normal again.
[Galaxy S I9000 Android Development] Netmatrix:
Me and yes runs good
[Galaxy S I9000 Android Development] DerTeufel1980:
What other settings are you using? Please also try to grep logcat or kmsg. For kmsg: adb root

adb shell

cat proc/kmsg > sdcard/kmsg.txt

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] yahyoh:
Devil3_1.1.3 is up

http://rootaxbox.no-ip.org/derteufel/jellybean/i9000/113/

changelog :
[Galaxy S I9000 Android Development] jeebspawnshop:
For DerTeufel's info;

I'm using idle2, and have been using it since the first time you introduced it.

Never once have I experienced any SoD's or other issues at all. Besides battery drain being slightly higher than stock, there's nothing wrong with the kernel at all.

FYI, kernel version: 3_1.1.0
[Galaxy S I9000 Android Development] AlwaysDroid:
Why did uksm get deactivated? For battery?
[Galaxy S I9000 Android Development] husamco1990:
I don't know if my question is stupid but can we use datadata partition as a swap partition in the roms without datadata like cm10
[Galaxy S I9000 Android Development] AlwaysDroid:
Won't have enough room. I only have /~40 mb free on /system, and 40mb swap is useless haha
[Galaxy S I9000 Android Development] DerTeufel1980:
It would work in theory, but these roms are using the space for system already

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] oliva94:
you can get ~60 megs if you use both cache and system

swap is not limited to only one file/partition
[Galaxy S I9000 Android Development] AlwaysDroid:
Or use an SD and get what ever you want ;)
[Galaxy S I9000 Android Development] oliva94:
he meant to use system because it is on an chip which can serve about 80MB/s

with an SD card you can only get 10MB/s, and internal sd (and data) is 40MB/s
[Galaxy S I9000 Android Development] AlwaysDroid:
Fair enough, makes sense. Could you use extra space in all partitions then?
[Galaxy S I9000 Android Development] oliva94:
You would need to make swapfiles according to the remaining free space. Check it with

df

and then

dd if=/dev/zero of=/system/swapfile bs=1M count=40

to make the file.

Replace partition (/system) and free space (40) in round MiB.

After that make the file to be swapspace:

mkswap /system/swapfile

And make an init.d file to attach them with lines for each file

swapon /system/swapfile

Also, you could put a file in /data, which is slower for some and even more slower for others, and attach it with less priority (going to edit this post, I forgot the toggle for that)

EDIT:

Sorry swapspace priority not available in busybox swapon.
[Galaxy S I9000 Android Development] jose.celestino:
Swap should be fast or better not have any at all.