yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] JohnCorleone:
Your latest in the OP, I dont even know what to say. I was doing some final testing on my friend's odex app. I flashed Omega 35 with Motomoto theme snd switched in several inverted apps. I was all set to odex I hit start on the app and nothing. It just sat there and eventually rebooted. I guess init.d not functioning properly. Anyhow, I knew from my Note 2 that you had updated. I wiped cache and dalvik and flashed. Sure enough a new bunch of apps are upgrading. The phoune booted totally odexed framework/jars and system/apps and damn this kernel just flies!!! Irs not just the speed but the responsiveness! I cant imagine it getting any better!

Sent from my GT-I9300 using Xparent ICS Tapatalk 2
[Galaxy S III Original Android Development] mamba720027:
So this is what light usage is like for me on v29.2 kernel. Undervolted cpu -100 and GPU -50 with rom settings, powersave mode on except for cpu and screen mode set to movies.

Edit: and where theirs no WiFi is where I leave home and use mobile. Also prior to my other posts with extreme usage,this one to my understanding proves to myself that with this kernel the phone saves energy evin while the phone is not much in use,otherwise I guess I won't have had such good screen time with device usability over 24hrs.:)

Sent from my GT-I9300
[Galaxy S III Original Android Development] 0asis:
You tempt me to give a try to this kernel again. The last time I did it I had a big drain and couldn't get a decent battery life. Maybe it was because I changed my rom and kernel too often. I guess that you need some stability to get a great performance.

Can I ask you which rom do you run?

Envoyé depuis mon GT-I9300
[Galaxy S III Original Android Development] mamba720027:
:p I'm using Omega V35. Just need to run it for a while and see how it goes.

Sent from my GT-I9300
[Galaxy S III Original Android Development] 0asis:
But with the great work that the developers are doing on this forum it's very hard. Lot of temptations. Some days ago I used to flash a new rom after every charge of my phone lol.

Envoyé depuis mon GT-I9300
[Galaxy S III Original Android Development] mamba720027:
That's being a flashoholic or crackflasher :D. I used to do that on my nexus s and theirs this great dev Morfic who develop the Trinity kernel over their who used to bring an updated version every 3 days or so and it was fun Fashing n testing cause of all the different variations. Gets addictive but now I know better to just flash one and run it for a week at least and if I like the result I don't bother with the rest. Good old days.

Sorry for the off topic peeps :p

Sent from my GT-I9300
[Galaxy S III Original Android Development] JohnCorleone:
Morfic used to bring like 3 builds every other day except there was never a changelog. Rather he was tweaking voltages and using us as a large test base.

But back on topic, I do feel that this is most responsive JB kernel I have tried...and I don't play favorites. I have donated to Gokhanmoral, AndreiLux (I better have anyway), Faux, Imoseyon, Ezekeel etc. As far as battery goes, I never say a word until at least 48 hours or 2 full battery cycles

Sent from my GT-I9300 using Xparent ICS Tapatalk 2
[Galaxy S III Original Android Development] Infy_AsiX:
I've got a peculiar bug. If cpu max is set to under 1400 and the phone reaches 45 degrees or so, it gets stuck in dual core mode.

edit: actually happens on 1400 too. Must be related to a setting

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] mamba720027:
I tried to reproduce it with cpu at 200-1200mhz but dident happen,must be your settings.

I did a CPU stress test using setcpu app to increase the temp and monitor it with system tuner app and works normal.

Here's the screenshot showing graph of temp spikes and shows the 3 cores goes to sleep.

And I attached my STweaks settings if you wanna try. With Stweaks defaults under "cpu hotplug" menu and "cpu online load bias count" setting change to 1 it should keep 1 core online most times with light load.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Striatum_bdr:
People must keep in mind that all chips are not the same. There are infinitesimal differences between pieces coming out of the factory, that lead to different behaviors.

That's why some can UV and some other not, some can OC up to 1800 and some other not and so on...
[Galaxy S III Original Android Development] Infy_AsiX:
Thanks for the help but I figured it out. Not undervolting related. All I've changed under cpu settings is load bias settings. It was the result of having the bias down setting too high. Set it down to 75 from 90 stops the bug. It occurred when playing an intensive game that to idles to load quickly and it would stop hotplugging back up after awhile.

?????? Galaxy S3 ??????

---------- Post added at 05:48 PM ---------- Previous post was at 05:36 PM ----------

To Andrei about undervolting how come your 400mhz step has a larger difference than your 200-300. Your settings were for me also ASV3 but started freezing. Raising that 400 step by 12500 fixed it.

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] and8res:
Hi

How can I restore the original sound * without loud volume *

??

Thanks
[Galaxy S III Original Android Development] mamba720027:
Use the slider where it says "speaker amplification offset" to set to 0 for phone speaker.

For headphone set "headphone Amplifier " to 0.

To disable equalizer where it have "EQ Preset" choose "Flat" to disable.

Sent from my GT-I9300
[Galaxy S III Original Android Development] psyntific:
Hot plug freq from 3 core to online.. does this value mean the frequency the cpu will switch to when bringing all the 4 cores online from 3? Or is it the frequency at which the 3 cores are to switch to 4

Sent from my GT-I9300 on ARHD 17 with perseus 29.2
[Galaxy S III Original Android Development] omniwolf:
no, it's the frequency the 3 online cores have to get to before turning on the 4th core

if you increase this it will require more load to bring the 4th core online. if you reduce it the 4th core will come online quicker than it otherwise would.
[Galaxy S III Original Android Development] mamba720027:
Deleted.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Simone:
Hi AndreiLux,

I was a user of Perseus Kernel on the Note 2.

Why was the thread gone? :eek:
[Galaxy S III Original Android Development] yahyoh:
it's really gone :eek: :(
[Galaxy S III Original Android Development] AndreiLux:
What the hell. Let me check out with the moderators.
[Galaxy S III Original Android Development] Andy:
It was deleted in error. For that we apologise.

It has now been fully restored.
[Galaxy S III Original Android Development] Scarface1991:
Since a day or so I have a really weird issue with this Kernel. When I listen to music and turn the screen off, the music becomes very stuttery. It happens with all music players I tried so far (PowerAmp, Google Music and a couple of Radio Apps). Kernel worked fine over one week and then I rebooted and had this issue. Afterwards I flashed the latest Siyah Kernel and it works fine again now. Tried to flash the latest Perseus Kernel and the problem was there again, so it must be somehow related to the Kernel.

When screen is on, everything works fine again, it`s only when screen is off music becomes stuttery.

I tried to delete Cache, dalvik cache and resetting S-Tweaks settings but that didn`t help. Anyone else with that problem?

I`m on UltimaROM v7.1
[Galaxy S III Original Android Development] danarama:
Got any screen off profiles running in setcpu?
[Galaxy S III Original Android Development] mamba720027:
Assumeing u don't have any undervolting set,in STweaks try raise your min cpu frequency to 300mhz or 400mhz then play same song with screen off to see if stutters still occurs.

Can also try use "poweramp" and go "settings/audio/advance tweaks/audio buffer size" and change that to 750. Turn the screen off and let the music play.

If none of the above works then I'm out of ideas,had that stuttering problem one time on another phone and raising the min CPU freq solved it for me,I did not had the option to raise min frequency voltage so that was all I did and it fixed.

Sent from my GT-I9300
[Galaxy S III Original Android Development] vacheldai:
I saw in other local forum, someone says the recorder app doesn't work anymore after applied alpha29.2. Please check. Thanks!
[Galaxy S III Original Android Development] habylab:
Try power amp and increase priority, if that does not work try to increase the priority of the amp within the settings also, under audio.
[Galaxy S III Original Android Development] inzaghi75:
Andrei are you working on the update for 9305 version?

Gesendet von meinem GT-I9305 mit Tapatalk 2
[Galaxy S III Original Android Development] cletusarrarr:
is it possible to add fast charge to this ? would be awesome if it could.
[Galaxy S III Original Android Development] mamba720027:
If I rember correctly its already hardcoded into the kernel,the option just not available in STweak.

Sent from my GT-I9300
[Galaxy S III Original Android Development] snekkarn:
Just wanna share my experience with you guys. Im one of those who always search for the best rom+kernel combo for battery life and performance. Im using latest perseus kernel+wanam xxelkc 5.1+jkay framework mod.. and been using it steady since the release. Battery is amazing.. no tweaks. Getting over 1day of battery on every charge. And the charging is fast.. And im using face, youtube, and browser alot. No freezes and no reboots. Just awesome experience.
[Galaxy S III Original Android Development] baris_76:
+1

GT-I9300 cihazımdan Tapatalk 2 ile gönderildi
[Galaxy S III Original Android Development] Highlander11:
Well, I have last charged my phone 2 days ago - am currently sitting at 61%, so it should last me for the rest of the year (and well into next year). O, and before you request kernel settings: I have an extended battery installed :D

Happy New Year! ;)
[Galaxy S III Original Android Development] amirsh77:
Happy New Year :)
[Galaxy S III Original Android Development] The Broken:
Since I'm using this kernel I got Wi-Fi problems.. Even though it has a connection, it does nothing.. if I want to keep this kernel, what do I do?
[Galaxy S III Original Android Development] mamba720027:
If you have already tried various troubleshooting techniques such as enter *#0011# in dialer to enter service mode and switching WiFi power save mode off to maximize WiFi performance. Resetting your router and modem, checking in rom system/etc/init.d folder for WiFi tweaks scrip that may also be related. Bark like a dog,hollar like a cat,stand on one foot etc.

Then use a free logcat app from the Google playstore to record a logcat when you're turning on your WiFi and experiencing the problem so that you can post it here for the dev or someone to help you further with solveing the problem.

Sent from my GT-I9300
[Galaxy S III Original Android Development] habylab:
Something weird happened just now for me.

When I started my phone up it was fine, and then these tiny blue lines appeared, almost dotted, near the bottom of my screen, horizontal. Seemed to happen in black surfaces, and coke in pairs. Very odd.
[Galaxy S III Original Android Development] The Broken:
Disabling power save mode and some tweaks worked, thanks.
[Galaxy S III Original Android Development] nop56773:
Hi Andrei,

By any chance is it possible to have 29.2 version for i9305?

Thanks in advance
[Galaxy S III Original Android Development] Prominence19:
When I'm using the latest kernel my CPU Scaling settings and CPU Hotplug settings change to the lowest values. Even after resetting all settings this occurs. Anyone else having this problem? I'm circumventing it at the moment by using Set CPU, but I pretty much like everything about this kernel.

[EDIT]

After reflashing the kernel, it doesn't seem to boot. When I flash Siyah it all works again, but when I then try to revert back to perseus it won't boot. I'll try installing an older version for my i9300.
[Galaxy S III Original Android Development] omniwolf:
try and redownload the kernel, it may be corrupted
[Galaxy S III Original Android Development] bl4ckdr4gon:
Bad download.

Sent from my Wanam-ish Galaxy S III
[Galaxy S III Original Android Development] _andrea_:
Are these useful?

http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-N8010_EUR_JB

An Italian tech-site notify it as a new release.. Link
[Galaxy S III Original Android Development] MuertoKo:
Waiting to know if the famous exploit is fixed or not on last stock release... But meh, no sources so still...

Hope Andrei brings some light :D

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] mamba720027:
Sounds like your phone got a case of wrinkles :p. If you have the GPU undervolt too much it maybe the cause for screen artifacts appearing.

Sent from my GT-I9300
[Galaxy S III Original Android Development] privat75:
My battery life :thumbup:

http://xdaforums.com/showthread.php?p=36225988
[Galaxy S III Original Android Development] Prominence19:
Is there a way to reset all settings related to perseus? Something went wrong and when I install the perseus kernel, my phone won't boot up completely.
[Galaxy S III Original Android Development] mamba720027:
not bad considering the standby time. You can add your STweaks settings in same post just in the event anyone wanna try it out.

In the link below you can download and flash the zip in cwm mode to reset STweaks profile.

Thanks to Gundal for creating the flashable zip to reset STweaks.

http://db.tt/OuLkjEfx

Sent from my GT-I9300
[Galaxy S III Original Android Development] privat75:
Stock settings
[Galaxy S III Original Android Development] danarama:
I have searched the thread...

Can anyone tell me which /sys file (assumed sys/devices/cpu?) the Stweaks option "Hotplug lock" interfaces with please? So that I may toggle between 0 and 0-3 via script
[Galaxy S III Original Android Development] mamba720027:
Doesn't STweaks have the option for that exact samething you're trying to do with a script. Look in my screenshot below.

Sent from my GT-I9300
[Galaxy S III Original Android Development] danarama:
Yes I know it does, hence my reference to "stweak option" in my question ;)

Do you know the answer?
[Galaxy S III Original Android Development] mamba720027:
I think the path in my screenshot below is it. If am wrong then someone is free to correct me.

And I was reading up on a page to get some info on what you're looking for and here's a link, maybe u will understand this more if its any help.

www.kernel.org/doc/Documentation/cpu-hotplug.txt

Edit: link looks like its computer related rather than smartphone,oh well,reading is good if only I could make out everything and understand :p

Sent from my GT-I9300
[Galaxy S III Original Android Development] danarama:
Yep thanks. I assume its that directory. You can bring a cpu online manually by putting a 1 in /sys/device/system/cpu1/online for example but the kernel will allow it to change back... so the option to lock must do something more.
[Galaxy S III Original Android Development] qwerty12:
Look at /data/.perseus/customconfig.xml and you can see the XML that STweaks (through uci.sh) looks at to generate the interface - you should find the filename in there
[Galaxy S III Original Android Development] danarama:
Thanks. Its where I said + /cpufreq/Pegasusq/hotplug_lock
[Galaxy S III Original Android Development] Prominence19:
Thank you! That fixed my problem.
[Galaxy S III Original Android Development] orangerot.:
Hey Andrei,

Can you please tell me the mountpoints of your Kernel? I'm using a Script provided in this Forum to mount my internal as external SD and my 64 Gb external as internal. If I use the Script with your Kernel only my 64gb Card is mounted as internal AND external. If I switch to the Siyah Kernel everything works fine. So I see the Problem in the Kernel. Does it use other mountpoints than other Kernels like the Siyah? If yes can you maybe tell me the mountpoints your Kernel uses that I can adjust the Script to work with your Kernel? The mountpoints in the Script are 179:49.

Thanks in advance!
[Galaxy S III Original Android Development] AndreiLux:
Right. /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock

It's the only place you should change the core count in, all other methods like echo'ing 0 or 1 to the CPU's online sysfs will do nothing as the logic isn't aware of that.

Just check /proc/partitions. 179:49 is the SDcard partition for me. Or are you asking about internal?
[Galaxy S III Original Android Development] habylab:
That would be it! Thank you, fixed. Upped the minimum from 106 to 180

---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------

Why wouldn't the reset button just do the same?
[Galaxy S III Original Android Development] mamba720027:
Cause if u mess up and your phone is stock on boot loop cause of various tweaks or a tweak u just applied and cannot get past the boot sequence to push that STweaks reset button then that's where that flashable zip comes in to reset STweaks from cwm.:)

Sent from my GT-I9300
[Galaxy S III Original Android Development] orangerot.:
I was asking about both. As the SD Card is mounted correctly I think its mount points are correct. What are the mount points of the internal?
[Galaxy S III Original Android Development] original21:
AndreiLux, i tried this app, "exynos mem bug checker", from playstore and its says that my s3 has still got the memory bug.

I am using your latest kernel (24/12) and neatlite V1.4.

Is this correct? I thought the 24/12 kernel (29.2) solves this problem?
[Galaxy S III Original Android Development] AndreiLux:
It's a shítty app. It's also fixed in 29 from 18/12. 29.2 fixes something else.
[Galaxy S III Original Android Development] original21:
Great kernel by the way. Only problem i found was when i unplug the headphones. I cannot hear the person on the other line. The problem its fixed with a simple reboot.

So if i use the latest XXELLA release and your kernel my phone is not vulnerable in any way! Is this correct?
[Galaxy S III Original Android Development] _andrea_:
The fix is in the Perseus kernel or in the stock XXELLA Kernel. So you're protected in both these cases:

1) Every JB Rom with Perseus kernel (29 or greater)

2) XXELLA with stock kernel
[Galaxy S III Original Android Development] yhrn:
The headphone problem has been reported many times in this thread. The workaround is to disable "DAC Direct" in the Audio tab in STweaks.
[Galaxy S III Original Android Development] habylab:
Ah yes, of course. The zip would have to be updated every kernel update, in case of new changes though. Thanks for your help.
[Galaxy S III Original Android Development] sohail667:
battery charging is very slow using this kernel plz help.
[Galaxy S III Original Android Development] yuriza:
I have no problem of slowness in charge ...:confused:
[Galaxy S III Original Android Development] siavash_Skh:
Use a 5 pin cable instead of 4 pin original one. Just change the cable not charger.
[Galaxy S III Original Android Development] adamski123:
I can flash this kernel if im running XXELLA right?
[Galaxy S III Original Android Development] habylab:
Ignore!
[Galaxy S III Original Android Development] sohail667:
have u check how many % charge in one hour

mine is charge 55% in one hour
[Galaxy S III Original Android Development] siavash_Skh:
It is very good, so how many % do you want to be charged in an hour?
[Galaxy S III Original Android Development] nfsmw_gr:
Andreilux,i don't know if it's related to kernel or not but isn't sysctl.conf supposed to be in /system/etc directory?

I can't seem to find the file...
[Galaxy S III Original Android Development] sonic76:
With my charger from old Nokia 97 i charg my phone fully in 1h 20min

with original samsung travellcharger (usb adapter)

chargin needs a bit more than 2h, thats really not so funny

Regards

Sonic76
[Galaxy S III Original Android Development] AndreiLux:
Since last night I'm able to reproduce the slow charging bug for the first time. The charger chip is reporting unstable power source and is constantly trying to reduce current by 100mA steps down to 100mA. I don't know the cause of it yet.
[Galaxy S III Original Android Development] mamba720027:
Your Nokia 97 have a smaller capacity battery comparing to the Samsung galaxy S3 2100mah nice big battery :). So its natural that your N97 charge faster with its own charger. I think you should invest in another battery as a backup and maybe your battery life is degrading causing that long time its takeing to charge.

Side note:: offtopicish :p

Depending on where you plug your phone in also affects chargeing speed, USB (DC) charge vs AC Charge. Also depending on how constantly u use the battery it will start degradeing battery performance and hold less of a charge.

The principle of keeping a Lithium-Ion battery cool will increase the amount of power that it delivers to your phone. Li-ion rechargeable batteries generate heat when in use, something that is mitigated by internal resistance,this is also why charger voltages are so low.

A high voltage would result in a faster charge but also a higher temperature ,like above 30 degrees Celsius/86 degrees Fahrenheit thus reducing the life of the battery. This causes the battery to discharge more quickly while simultaneously providing energy for the normal functioning of the device.

So keeping the battery at a slow charge improves battery life and at cool temperature holds its charge.

But pissoff with slow charge,battery is cheap these days.

Sent from my GT-I9300

---------- Post added at 08:33 PM ---------- Previous post was at 08:30 PM ----------

Ahhh, so their is a bug in their. Is the bug on both when on USB charge and also on AC charge?

Sent from my GT-I9300
[Galaxy S III Original Android Development] rowlers:
I plugged in yesterday and noticed it was taking longer than usual to charge. I checked battery stats and it showed USB, even though I was plugged into mains.

Unplug/replug and it was back on AC and normal speed.
[Galaxy S III Original Android Development] danarama:
I can reproduce slow charge with 1 specific cable. The new one I bought cannot reproduce it. Perhaps the tolerance to determine if a source is stable is too fine?
[Galaxy S III Original Android Development] shaarky:
Here it is - hopefully it contain part where AllShare Cast is experiencing a problem, wasn't sure which part to select....

http://pastebin.com/TpQa1FER

@ AndreiLux, do you have a clue where could be a problem ?

Thank you.
[Galaxy S III Original Android Development] mamba720027:
Hopefully your log is usefull to the dev to help solve your problem or someone with experience reading logs.

Would be good if you mention what kind of problems you're experiencing with Allshare cast.

Edit: forgot u mention it already a long time ago :p

Sent from my GT-I9300
[Galaxy S III Original Android Development] The Broken:
He wasn't taking about a N97, but over the N97 charger he uses for his sgs 3

Nice story about the battery though!
[Galaxy S III Original Android Development] AndreiLux:
Can you please share a dmesg while charging with that cable? For me the charger gets stuck in charge detection run mode which is a chip register.
[Galaxy S III Original Android Development] danarama:
Yep I'll have a look tomorrow....

---------- Post added at 09:37 PM ---------- Previous post was at 09:30 PM ----------

Is it possible to monitor the mA to ensure its reproduced without waiting all night?
[Galaxy S III Original Android Development] AndreiLux:
The charging rate is shown in the kernel log. Anyway you just need to plug it in for 2 minutes and that's all.
[Galaxy S III Original Android Development] adamski123:
Anybody got any tips for better battery life and are running this kernel?
[Galaxy S III Original Android Development] shaarky:
It's fine :

1.Turning on the AllShare cast

2.It starts connecting

3.Connected

4.About 20 sec.later - disconnected

(not happening eg.on Syiah)

...and the same from beginning.