yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] danarama:
Not sure if this contains what you're looking for. It usually takes me over night to notice slow charge
[Galaxy S III Original Android Development] AndreiLux:
It's charging at 200mA in that log, and your battery is at 9.35%. There's definitely something wrong. What kind of cable is it? 4 or 5 pin?

Would be interesting if somebody can measure the resistance between all pins on these "buggy" cables against proper ones.

The ****ty thing is that I don't have the 77693 data sheet, if we had the same documentation as with the 17047 fuelgauge we'd solve this in a breeze.

I'm had a totally different issue myself last night:

It kept being stuck in CDR mode and staying in an endless loop for a while until I reconnected it:

After which the MUIC code just kept ****ing around endlessly:

Another thing which happened is that the state of charge exceeded 10000 by the end of all this, which should not happen, the charger logic is supposed to stop at 10000. This thing is overcharging the battery if the fuelgauge readout is correct.
[Galaxy S III Original Android Development] sonic76:
My Nokia N97 charger caharges the Samsung S3 more then doubble

so fast like the original Samsungcharger

Regards
[Galaxy S III Original Android Development] AndreiLux:
I just took out my old S2 charger and did a bit of testing.

The S2 charger rated also at 1A just as the S3 charger; the charger chip detects unstable power at 1A (Might be on the limit of the charger, understandable) and is stable at 900mA, and further reduces it by a 100mA safety margin (I might decide to remove that) down to 800mA. It enters soft-regulation at 800.

The S3 charger ****s all over itself and gives me unstable power until it gets down to 300mA and then reduces itself again to 200mA. Up until yesterday this didn't seem to happen.

I searched the forum and there seems to be some members having some feedback from the service centers:

So from the empirical evidence right here it seems it's because of the charger. I for one am heading over to eBay to get myself some new one.
[Galaxy S III Original Android Development] mamba720027:
Must be why I'm not experienceing this slow chargeing since from day one I never used the Samsung original charger that came with my phone. The design dident look appealing an I think the USB cable was too short and made me dislike it. Since then im using an old Nokia charger from approx 8years ago with a nice long usb cable,works good.:)

Sent from my GT-I9300
[Galaxy S III Original Android Development] Frag1le:
Haha same here. Using 3 original HTC USB cables and chargers around the house/work. No slow charge issues. I don't like the side usbport design.

Sent from my GT-I9300
[Galaxy S III Original Android Development] danarama:
It is a 5 PIN. Its from a batch I bought at work to supply to our Blackberry users. I have used this cable successfully on my HTC desire and the S3. I suddenly noticed when I woke up after a full charge, it was still on 83% (had worked fine previously) so after a few nights of this I bought a replacement. I assumed that (although there was no sign of weakness or lack of integrity) that it may have a faulty cable inside.

All this happened before I used Perseus by the way. I had used Siyah for a long time before moving to Perseus and it was on that kernel, the issue started. I suppose its possible this is something that happened once the JB sources were released.

Although I cannot promise to make a test quickly, but if you can supply me one of your old ICS releases please, I could output a dmesg on an ICS ROM to rule out JB Sources? If the issue still happens, its definitely the cable?
[Galaxy S III Original Android Development] maopaopao:
delete, find answer before
[Galaxy S III Original Android Development] ballmead:
I'm probably talking out of my arse here but a lot of Sudden deaths occurred when on battery charger.

Do you think this could be related?

Sent from my SG3
[Galaxy S III Original Android Development] AndreiLux:
Mmmh. No idea. Technically it shouldn't be possible as the charger chip has protections built in.. but then again last night my charger really went crazy and even woke up with the phone frozen in the boot screen. It's just speculation for now until we see what Samsung changed in their code.
[Galaxy S III Original Android Development] Anakha56:
Just something to add into this conversation about battery charging issues. I have had this problem with multiple kernels so for me it's not a problem with Perseus kernel but more hardware and up until now I assumed it was my phone (could still be) but I am going to try a different charger and cable just to be sure. Something I have noticed is that a reboot sometimes sorts out the issue other times I need to switch the phone off and leave it to charge while it is off then it charges fine for the next couple of weeks. No idea what to make of it...

*edit*

Screenshot of my charging over night.
[Galaxy S III Original Android Development] AndreiLux:
I decided to release 30 as it is now because the other changes I had in mind will take too much time.

The changelog is small but the changes themselves are very big, especially the hotplug related runqueue logic.

The internal voltage and memory voltages are a feature first. Please keep in mind that all other kernels who tried to do this were broken and just placebo, so please ignore any of those voltages. I will do another in-depth explanation about this in the 3rd post in the following days, until then, just read the STweaks descriptions. Lowering internal voltage too much will have a very funny effect when crashing the phone...

I also dealt with that /dev/random entropy thing. It should not cause any problems anymore, and without using any of those stupid fixes like the Seeder app.
[Galaxy S III Original Android Development] 0asis:
What's your app please?

Sent by an anonymous flashaholic
[Galaxy S III Original Android Development] mamba720027:
Search playstore "battery monitor widget".

Sent from my GT-I9300
[Galaxy S III Original Android Development] jmajuri:
It seems to be Battery Monitor Widget
[Galaxy S III Original Android Development] sohail667:
Installed persues 30 working well thnx
[Galaxy S III Original Android Development] yhrn:
I just woke up to find my phone having decided to commit suicide. Phone was charging but I was using a charger I got with a ZTE Blade two years ago. This is the charger I've used almost exclusively and I never experienced slow charging with it. Only used the included charger a handful times. From reading the Sudden death thread this seems to happen to people all all kinds of firmware combinations, stock and custom.

Now I'm off to some corner where I can curl up and cry.
[Galaxy S III Original Android Development] RovG:
Hi Guys,

Regarding the charger issue, the folks over on the Skyrocket thread seemed to have problems with their chargers too http://xdaforums.com/showthread.php?p=28456520. It makes for intetesting reading. Please note that the test App referenced in the OP is for the Skyrocket and not any other device. Maybe Andrei could do a similar test app for S3 / Note if he so chooses.
[Galaxy S III Original Android Development] habylab:
Oooo, I thought the new voltage controll was as a result of the feedback we gave on it? Good update regardless.
[Galaxy S III Original Android Development] EViollet:
So you've also been following that thread? ;)

Haven't read it yet this morning, but what did you do to fix the problem?

Edit: sorry, it's written in the op...

With the new version, I see you've changed hotplug logic. I've been using scripts that reconfigure the hotplug logic for some time now (I found them on the Siyah thread) and am wondering if they are now moot?

I have a script that configures "extreme battery saving" when the phone screen is off and "extreme performance" when the screen is on.

Do you have any recommendations on how to configure the CPU hotplugging/etc with your kernel?

Thanks

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] mydonose:
Hi at all, I install the alpha 30 and then the exynos mem bug Checker app. It says still "this device have a mem bug" I thought, it was solved already:confused:
[Galaxy S III Original Android Development] habylab:
Have the settings for GPU up threshold changed? Mine now says 75% all of a sudden.

---------- Post added at 10:05 AM ---------- Previous post was at 10:05 AM ----------

The app checks for the old "fix". Look at the size of the app, did you think it would be that good anyway?
[Galaxy S III Original Android Development] MuertoKo:
Hummmm not trying to sound a bad news bringer but I've been following the SDS thread lately and some people reported this behaviour before their devices died O.o hope it's just the charger

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] danarama:
FYI,

I've had this lots of times. My alarm hadn't gone off and when I look, it's frozen at the boot splash. It did this intermittently until one day the screen was black and wouldn't wake. "Sudden Death.

At the time I was using Siyah. So I got the motherboard replaced/repaired, rooted and nandroid restored, flashed ALF sboot.

...it happened again 1 time in a week. I switched to Perseus. Happened 1 time in a week. I realised I had the same voltages set that I used on ICS so I raised them a bit higher (800mV for 200mHz) and so far (2 weeks), it's not happened again yet.

This is on the new cable too btw.

I have a Tasker profile that outputs to logcat whilst on charge though so hopefully if it happens again, I will capture it.

If anyone else getting this has Tasker, i'll happily upload my profile for you.... after trying several methods this was the best
[Galaxy S III Original Android Development] yahyoh:
i don't know what such big company doing :/

GS3 one of their best selling devices and they still don't conform any fix for SDS and now slow charging problem :silly:

on my Gnote2 i noticed the usb port become hot when i use 220v socket ( when i use the 110v its still cold without problem )

BTW i remember some people said the slow charging problem start with 4.1.1 update ( so maybe its kernel bug not the charger :confused: )
[Galaxy S III Original Android Development] Tatsuya79:
Could someone explain me how to change the mdnie values?

I'm not asking for what the values mean, I understand I'll have to do a lot of testing and reverse engineering, just that I don't understand if I have to make an init.d script or changing a file somewhere.
[Galaxy S III Original Android Development] burner07:
what is stock gpu maximum frequency? in siyah is 533 in your kernel is 440 and stock ?
[Galaxy S III Original Android Development] Frag1le:
Just flashed Perseus 30.

AndreiLux, thanks for the update.

Still i have a question, ARHD 18 (based on XELLA) doesn't recommend custom kernels until Mike1986 sorted out his tweaks (so i won't test it) but won't the Samsung Exynos exploit fixes in XELLA conflict with your exynos exploit fixes from Kernel 29 and up?
[Galaxy S III Original Android Development] Anakha56:
Pretty please? I would love to try it out and see what I get. :)
[Galaxy S III Original Android Development] danarama:
Ok.

Unzip the attachment to /sdcard so you end up with /sdcard/bash/log*.sh

There are 2 scripts. One to start the logcat and one to kill it (because it runs forever otherwise).

The profile to import into Tasker is also in the bash folder. It includes one task and one exit task, triggered by state > power > AC

The logcat_run.sh supposes that /sdcard/zlog exists
[Galaxy S III Original Android Development] GrayJack:
Possibly it was already mentioned in this topic, but crt-off from JKay works perfectly with Perseus.

Sure it's not very important but whatever.
[Galaxy S III Original Android Development] danarama:
Anyone on A30 having an issue with /extSdCard mounting as read only? I try to copy files there and I get an error that its read only. I can mount as R/W via Root explorer for a while and write files for a while until it reverts,

I have had this issue before but I forget what I did to fix it. I went back to 29.2 for now to see if it continues to happen. I am not sure flashing the kernel did this, but its the only change I made so if it doesn't happen on 29.2, it may have been the trigger.
[Galaxy S III Original Android Development] qwerty12:
Sure the card is not corrupted? By default, vold is configured to mount the card with errors=remount-ro, which means if an error on the card is found, it gets remounted RO. You can check if this is actually happening by looking at dmesg's output. I'd backup my data and run a scan on the card from a computer (you can use SGS3 Easy UMS if you don't have a card reader at hand).
[Galaxy S III Original Android Development] danarama:
I've just reformatted it. FolderSync backs up to my NAS anyway. Easy UMS doesnt work too well in Linux
[Galaxy S III Original Android Development] habylab:
I'll ask again, what are peoples GPU up thresholds in 30? Mine changed to 75.
[Galaxy S III Original Android Development] mamba720027:
Mines also 75%.

Sent from my GT-I9300
[Galaxy S III Original Android Development] AndreiLux:
Maybe we're onto something... at least I got paranoid enough to charge my phone only on my pc from now on until new sources find out. I'll check how it behaves closely from now on.

I lowered the GPU threshold in 29 to 75%, maybe I forgot to remove that value injection in STweaks.
[Galaxy S III Original Android Development] danarama:
Yeah. The information we have so far is all over the place but if I get the boot splash freeze, I'll share the logcat. My logcats run on a 5MB file limit (before wiping) so easily should catch enough info if it happens again
[Galaxy S III Original Android Development] AndreiLux:
I caught my own boot splash freeze kmsg but it was corrupted (happens).
[Galaxy S III Original Android Development] danarama:
My problem was with kmsg and last_kmsg that they were modified on boot it seemed so I couldn't trust the output was accurate because I was booting to get to them. Sometimes the date at the top was months old too so I found it best to logcat. If I trigger logcat when plugged into AC, it is always accurate for me, but I havent had the issue since doing this so no info :(

I suppose I could adb pull but first thing in the morning I need my phone on and dont have time to do that
[Galaxy S III Original Android Development] tezukaryoma:
hello,i just found that when using latest alpha30,each time recording video failed by using camera,n i try reflash stock kernel,the camera recording worked again,anyone having the same problem as me? n currently using wanam 5.3
[Galaxy S III Original Android Development] AndreiLux:
last_kmsg is a circular buffer always being populated with the kernel log from before the current boot, it can actually contain several boot cycles if none of them is big enough in log data to kick out the information on the others. You can have a crash and do two quick reboots and the log will still have information on the crash.

I don't think I'd get anything useful from a logcat since that's just OS information, it's not aware of the kernel.
[Galaxy S III Original Android Development] yahyoh:
Andrei did u test the new kernel that come with XXELLA if has the fix for slow charging with stock charger ?? or anyone test it ?
[Galaxy S III Original Android Development] danarama:
Oh ok then.
[Galaxy S III Original Android Development] MuertoKo:
At least you are now looking into it, hard to do without the issue happening yo yourself as it's impossible to reproduce, just hope it leads to some good at the end!

Guess he needs sources to check properly but maybe it's worth the try checking if he can reproduce it with new stock kernel...

We do really need some sources... come on Sammy give us those goodies!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] d_jaxx:
Same here. On LL5.

★ ★ ★ tapatalked ★ ★ ★
[Galaxy S III Original Android Development] ceo.mtcl:
+1
[Galaxy S III Original Android Development] AndreiLux:
Updated.
[Galaxy S III Original Android Development] SirCanealot:
Wow, flexi thingy majigamabob looks really interesting! Will have to try this out finally! :D
[Galaxy S III Original Android Development] knights.JayTana:
Nice update Andrei... Thanks...

Would you mind scanning thru "music quality thread"? We have some problems there regarding the crackling/clikcing sound in music playback when screen is off... we can only guess that it has something to do with cpu idle status since setting it "idle only" temporarily fixes the issue... Hope you can shed us some light there... Thank you...
[Galaxy S III Original Android Development] AndreiLux:
LPA causes the CPU to be clock-gated, meaning the clock to the CPU is cut-off. I imagine that when power resumes, or actually is cut, it either causes a drop or spike in the power supply which interferes with the DAC and amplifier. This is inherently a hardware problem; they could have prevented it if they had put adequate filters on the PMIC, or whatever is in-between them which causes the interference. LPA is idiotically power-efficient and turning it off can cause worse idle battery life, so turning it off it in my opinion not a very viable option. The only options to fix it are already available to everybody already through changing of the idle states. If there's something to be done on the DAC-level itself, I don't know. CPU noise is a pain in the ass and wide-spread (Think about on-board sound on computers) and sadly there's not much to do about it if it's badly designed.
[Galaxy S III Original Android Development] knights.JayTana:
Thanks for the word of wisdom... ill quote your post there...
[Galaxy S III Original Android Development] Ariozo:
Looks like an intressting update, Andrei..:)

Had some problems with high battery drain and some small "stutter" on last one but gona flash this one and try it out for sure.

Thx again for your nice work
[Galaxy S III Original Android Development] rlorange:
Bummer. Miniature Faraday cage? Lol!
[Galaxy S III Original Android Development] currydude:
Issue Report: Just like every other 3rd party kernel, this kernel has problems with latest LFB update (Videos being pushed up - evident in YouTube app, portrait > landscape > portrait, the video is pushed up - Occurance; Always, in Camera app, preview is pushed up towards SAMSUNG logo - Occurance; Sometimes)

Everything else seems good at the moment :)
[Galaxy S III Original Android Development] ascariz:
This man really pissed off with s3 kernel development. All kernel thread he posted
[Galaxy S III Original Android Development] GabrielSousa:
this kernel work on AOSP ?
[Galaxy S III Original Android Development] knights.JayTana:
Only for Sammy base:)
[Galaxy S III Original Android Development] GabrielSousa:
can you update to work on aosp ?
[Galaxy S III Original Android Development] knights.JayTana:
First of all, im not the Dev. Second is; if its not too much to ask from you, can you show some courtesy;-)
[Galaxy S III Original Android Development] onslaught86:
Wow, alpha 17 has made a massive difference to UI navigation and general performance, amazingly responsive vs. the stock XXBLFB kernel. The notoriously finicky XDA app is resuming more often than it realoads, too.

Love your work.
[Galaxy S III Original Android Development] Chillz88:
Same here.. responsive..everything looks good.. no lag at all in the stock gallery.. most of the other kernels have a little lag there..
[Galaxy S III Original Android Development] vegeta1:
man this kernal is just like THE AMAZING SPIDERMAN for me ,

works flawlessly awsum change in battery consuption

love your work man ..

keep'em coming man
[Galaxy S III Original Android Development] qwerty12:
Stupid question, I know, but is adb actually running as root for anybody else or is my device being a PITA? ro.secure is set to 0 by Perseus so I can't see why it wouldn't be root.
[Galaxy S III Original Android Development] AndreiLux:
Works with no problems here, must be something with your setup.
[Galaxy S III Original Android Development] knights.JayTana:
Originality @ best... Thanks Andrei... Any plan of injecting cool features from other Kernel into yours?;)
[Galaxy S III Original Android Development] AndreiLux:
Confirmed, I'll look into it.
[Galaxy S III Original Android Development] tincmulc:
Video recording works for me (I even tried the front camera and it works too), XXELL5 (WanamLite Stock), Perseus Alpha30.
[Galaxy S III Original Android Development] Lither:
This kernel audio quality is the same as Siyah? Also Perseus default settings in STweaks are good enough to save battery as my main use is Facebook, Viber, Internet, Music and Games?
[Galaxy S III Original Android Development] ArbiterGR:
Thanks for the new update! I only want to report some minor grammar errors in the new Memory/Internal tab in stweaks :P :P. Also camera recording is working fine here for both rear and front camera sensors without any problems.

Apart from that, i started toying with the internal memory voltages and it seems stable at -100mV ! /me likes!:cyclops:
[Galaxy S III Original Android Development] habylab:
Hmm, so setting shave been altered in new version?

---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------

Okay, thank you!
[Galaxy S III Original Android Development] stanley08:
I have this question too. :)
[Galaxy S III Original Android Development] Anoobossi:
With v.30 I can't take videos, too.

ARHD 18
[Galaxy S III Original Android Development] habylab:
It's personal guys, try yourself.
[Galaxy S III Original Android Development] inzaghi75:
Andrei could you please answer our questions in the 9305 kernel thread. We love your work so please don't stop to work for 9305.

Gesendet von meinem GT-I9305 mit Tapatalk 2
[Galaxy S III Original Android Development] www1:
Problem with video too. Stock kernel working well.

Wanam 5.3 ELLA here.

Inviato dal mio GT-N8000 con Tapatalk 2
[Galaxy S III Original Android Development] psyntific:
Sand here... video recording is broken with lla

Sent from my GT-I9300 on ARHD 18 with perseus 30
[Galaxy S III Original Android Development] jayden2009:
Maybe u should flash the old 4.1.1 video libs http://db.tt/wOBcdYan
[Galaxy S III Original Android Development] psyntific:
Works fine with 29'2.. do you think it's still the libs

Sent from my GT-I9300 on ARHD 18 with perseus 30
[Galaxy S III Original Android Development] iridaki:
On stock 4.1.1 video rec works fine.

iR¡D@k!* ? from i9300 via Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Perseus Alpha 30, wanam lite 5.3 (LLA), hyperX note 2 camera, video fine front and back
[Galaxy S III Original Android Development] AndreiLux:
I already said that I confirmed it, I'm working on it. No need to repeat it 10 times.

Edit: I fixed it. It was a stray \ character in the firmware makefile causing the camera firmwares not to be embedded into the kernel.

30.1 includes this fix plus a few typo fixes in STweaks.
[Galaxy S III Original Android Development] danarama:
Sorry I thought telling you that mine works may help you
[Galaxy S III Original Android Development] AndreiLux:
There's a lot of ROMs and also the HyperX camera which use older camera libraries and people give false positives because of that.

30.1 is up.
[Galaxy S III Original Android Development] Tenacious:
Tab opened too long nwm.
[Galaxy S III Original Android Development] MuertoKo:
Video recording fixed on 30.1 as you already know :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] :
Yeah, I noticed that the kernel size from 30 is 500KB lighter than 29.x. I was going to ask what caused this, so nevermind.
[Galaxy S III Original Android Development] danarama:
Thanks but being told once is enough.
[Galaxy S III Original Android Development] AndreiLux:
I updated the changelog to provide a bit more info in regard to the new busfreq controls.
[Galaxy S III Original Android Development] F.M.K:
hi ... before a wile i just flashed the new perseus alpha 30 kernel , but after that the camera just stuck when i recording something and stop responding .... how can i fix this ?

thank you