yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] marcogtt:
Andrei I've a question concerning the necessity to format the ext SD in ext4 .

Will I loose the possibility to mount it as UMS on winxp?

Thanks

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] Tenacious:
Yes you will because windows can't read ext4, you can format it to fat32 instead.
[Galaxy S III Original Android Development] momosa:
well, waiting your new work... ;)
[Galaxy S III Original Android Development] psyntific:
Thanks alot andrei.. Incredible work... You're a super genius...

Sent from my GT-I9300 on ARHD 17 with perseus 29
[Galaxy S III Original Android Development] DirkStorck:
Why do you have to format your ext SD as ext4?

Thanks.

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] Frag1le:
Perhaps he doesn't want to have exFAT and needs to store files larger then 4 GB on the extSD.

(I would use exFAT then cause that does work with UMS)
[Galaxy S III Original Android Development] LaZyDood:
Tested Perseus 29 with official Samsung MHL.works fine.first i tested MHL with stock kernel,noticed some barely noticable lags when gaming.then flashed perseus 29,with default settings,it was the same with stock.then i OCed the GPU to 533 and 600(just to test out everything),still the same.set back GPU to defaults and OCed CPU to 1.6ghz,lags gone.now im guessing its got something to do with the CPU since while the TV had lags,the phone itself was totally smooth.

in general,just wanted you to know that MHL is fine. :)
[Galaxy S III Original Android Development] mamba720027:
What TV, u mean as in television? The TV is probably too old,buy a new HD one for Xmas :p

Sent from my GT-I9300
[Galaxy S III Original Android Development] www1:
Andrei

You have see it?

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

I have to flash in version 29 or not?
[Galaxy S III Original Android Development] GrayJack:
Using 29 with 4.1.2 - and actually today I have updated 4.1.2 - no problem with cam!
[Galaxy S III Original Android Development] Highlander11:
Using v29 with ARHD 17.0 (4.1.2) - no camera problems...
[Galaxy S III Original Android Development] AndreiLux:
I added a line to the OP description to clarify that. No, you don't need that. My security fix doesn't break the camera. You don't need to bother with any of the posted "fix applications", or worry about the camera.
[Galaxy S III Original Android Development] www1:
Thanks Andrei now is perfect ;)

Inviato dal mio GT-N8000 con Tapatalk 2
[Galaxy S III Original Android Development] Frag1le:
To me it seems kernel 29 drains the battery a bit more then 28.2 when decive is sleeping. Haven't changed anything since coming from 28.2, no app installations or updates done. Betterbatterystats also shows the same awake time comparing to other days. Will report again after more charge cycles.
[Galaxy S III Original Android Development] DirkStorck:
Hi. I have the problem that sometimes my phone freezes after a reboot and I unlocked the phone. After several reboots it finally works. Does someone has an idea why.

Thank you :)

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] mamba720027:
If you have over clock or under volt could be any of these or something that you have changed.

Sent from my GT-I9300
[Galaxy S III Original Android Development] davelyh:
after update 29.1, very lag when running MC4 :p
[Galaxy S III Original Android Development] hur8111:
Same here. with 29, it drains more battery than 28.2 while in standby..
[Galaxy S III Original Android Development] DirkStorck:
I didn't undervolt or overclocked anything :(

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] erto90:
Let the kernel to settle.. I noticed too higher battery drain, but is too early to make conclusions:D
[Galaxy S III Original Android Development] angelnaina:
hii..i ran the demo app of chainfire and result was "Exploit Successful " and then i flashed Perseus kernel ... an then again i ran Demo app and now status is "Exploit Fail"...

so its mean before flashing the kernel my device was infected and now the problem was cure by perseus kernel ???:confused:

and i read before posting,but didn't find the answer..:angel:
[Galaxy S III Original Android Development] mamba720027:
Have no idea,make sure to check any old settings u had in previous apps if any and that they weren't set to apply on boot. Could be anything, always try to pull a logcat,so someone can review the log if its kernel related.

Means the security exploit was fixed by the patch Audrei made and added into the v29 of his kernel.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Highlander11:
29.1????? You mean 29, surely? ;)
[Galaxy S III Original Android Development] eden1988:
If you read OP you would get your answer, Andrei included the exploit fix (without breaking camera) to his latest Perseus alpha v29, so yes now your phone is exploit-free.

Edit: Slow :P
[Galaxy S III Original Android Development] davelyh:
yes man ~!
[Galaxy S III Original Android Development] Frag1le:
What do you mean with: let the kernel settle?

Does a kernel need settling?
[Galaxy S III Original Android Development] erto90:
yeah, don't know if things changed in last months, but usually a kernel need 1-2 cycles to be settled properly.. also my personal tests confirm that
[Galaxy S III Original Android Development] MuertoKo:
It's common knowledge (at least I've read it many times, but never a reasonable explanation for that...) that a kernel needs some time to work properly, actually I find it has no sense at all, but well... it might be placebo but looks like this...

For me the first 2 - 3 days after a flash wiping cache and dalvik battery is a killer, after that all comes back to normal (or better lol).

Might be placebo, and my (short)knowledge says it must be placebo but...

Wish we had some words from a reputed dev on this some day :P
[Galaxy S III Original Android Development] Stivikivi:
How can i set the core from quad to single? Using stweaks or set cpu? Ty
[Galaxy S III Original Android Development] Rikul:
Think Ill be moving back to the 28.2 due to idle battery drain :(

But kernel is smooth as always :)
[Galaxy S III Original Android Development] mamba720027:
In Stweaks Under CPU hotplug menu can use the slider where it says "hotplug Lock" to change from 0 to 1 to lock in one core.

Sent from my GT-I9300
[Galaxy S III Original Android Development] xukaisheng:
Good battery life with my settings.;)
[Galaxy S III Original Android Development] Frag1le:
Okay, i'm fairly new to flashing kernels but hardware and software normally use a steady amount of power when idling and when properly working.

Hardware can suddenly use more power if the software that's managing the hardware is waking the hardware more then it did before. As i've changed nothing else then update the kernel from 28.2 to 29 and now see a drain that's really noticable it must be the software that has changed.

It makes no sense it won't behave like this in the days to come.

Still like you said, i'm no dev and i don't know if android is that advanced that it has a really good battery usage service or something.

Hopefully AndreiLux can shed some light on this.
[Galaxy S III Original Android Development] AndreiLux:
Kernels settling is a stupid idea and myth, it's not a living being nor does it make any kind of technical sense. You don't need to wipe Dalvik, or battery statistics.

As for "drain", I changed nothing beyond the Wifi drivers that could affect that, and personally I don't see any worse idle.

Actually I have to really force mobile data on and use that to make the phone drain as such that I get less than 7 hours screen on over two days, which is my average normal battery life at maximum usage on how I use the phone.
[Galaxy S III Original Android Development] inzaghi75:
Could you post your setting please?

Which scheduler is recommended?
[Galaxy S III Original Android Development] MuertoKo:
Just same as I expected, glad to hear I was write considering it pure placebo, will keep this post to answer some questions on the time being by quoting your post... guess ppl will trust it more coming from a good dev than from me :P

About drain I'm not having it, but wth of a usage you do with your phone to get that? I can hardly get 17h + 4h screen time with... nearly any kernel, rom or wipe... guess you have such of a great data on your place and I bet underground is killing my bat... damn Radio sucker...

Anyway, the new GPU levels make some sense to me, but I'd like to know if you have any app to on-live control the CPU hotplugging, just like we do with CPU, just curious about it :P
[Galaxy S III Original Android Development] AndreiLux:
Huh, do you mean GPU hotplugging? We already have total CPU hotplug control.

The Mali cores already have internal power management in the common platform driver, it's very dynamic and effective and it shuts off the Geometry- and Pixel- Processors power on a fine grained (10ms) time scale. I already looked into that and its nothing that could be improved. The GPU utilization is actually the amount of time in percentage any of the PPs are online, and not a CPU-like load.
[Galaxy S III Original Android Development] MuertoKo:
Tiped "control" when I ment monitoring, sorry :P But still the answer is that anyway :P

Completly worth reading! So this makes real sense... all frequency jumping that fast can't be properly shown by usual monitoring apps then, that's a good explanation for the lack of monitoring interface in anny usual app for the GPU!

Thanks for the teachy answer :)
[Galaxy S III Original Android Development] siavash_Skh:
+1
[Galaxy S III Original Android Development] Pard0ned:
There is. http://xdaforums.com/showthread.php?t=2027495 ;)
[Galaxy S III Original Android Development] erto90:
Is possible to set a gpu stepping to 600mhz? seems my phone can't handle 640mhz :(
[Galaxy S III Original Android Development] Alex E:
I'm going to say something dangerous...

When I use an iPhone and I press the home button, it simply starts up a lot faster (immediately), even if it's just the iPhone 4. Now, it probably has something to do with sleep-mode or whatever... Is there something I can tweak to improve this on the SGSIII? Without massively reducing battery time of course.

Worth a mention: I use widgetlocker.
[Galaxy S III Original Android Development] MuertoKo:
There are 2 things with home-button function, one on locked device and one whenyou are using it, it's slow in both actually...

The first case, locked device waking up can't be solved in our side, as it's due to hard thingies (I guess Andrei wrote about this some time ago, just can't remember what was the causant, if modem handling, Exynos or whatever...).

Second case can be helped a bit with some mods out there to make it faster to respond and go to home faster, but that's all.
[Galaxy S III Original Android Development] mamba720027:
I rember useing widget locker on another phone and it did made the phone go from sleep to wake take longer like 1 second and sometimes 2. Now with default galaxy s 3 lock screen mine is almost instantly awake wance I press home button. Might wanna try use stock and see if different.

Sent from my GT-I9300
[Galaxy S III Original Android Development] MuertoKo:
It shouldn't be related to that actually, it happens on Galaxy S2 as well :) It's Sammy's way, maybe later Andrei feels like explaining it, or I'll try to search deeply as I remember he said something about this some time ago... won't try searching harded on mobile app, drives me mad...
[Galaxy S III Original Android Development] mamba720027:
I did a search and all I found was this link with a study of it on another device.

xdaforums.com/showthread.php?t=1308883

Sent from my GT-I9300
[Galaxy S III Original Android Development] yahyoh:
dangerous...:silly::silly::eek::eek:

as i remember i read before Entropy512 said the modem inference take forever to wakeup from deep sleep on Exynos 4 devices :(

and maybe iphone don't have sleep mode :laugh:

and is it really annoying to waiting 1-2 sec to use ur device!!!!!!! :laugh:

BTW widgetlocker is battery sucker :p
[Galaxy S III Original Android Development] Alex E:
Dangerous because: I've said such a thing before and the response was a fancy "WELL THEN JUST GET AN IPHONE", so I'm pretty cautious saying these things, because god forbid we might learn something from another system with its own strengths of course...

It is indeed annoying to wait when you have an awesome device but it starts as if it has one 500mHz processor.

I know Widget Locker isn't perfect, I wish it could just be put in place of stock easily. Would help a lot. But hey... To me, it's at least a lot better than stock.
[Galaxy S III Original Android Development] AndreiLux:
#!/sbin/busybox sh

echo 640 600 > /sys/devices/gpu/freq_table

Read the GPU changelog again in the OP.
[Galaxy S III Original Android Development] GrayJack:
There is an update of STweaks to version 1.1 at the market.

Should I update to this version or it will conflict with latest Perseus kernel?
[Galaxy S III Original Android Development] AndreiLux:
Update it if you wish, it just removes the donation links on the extra page.
[Galaxy S III Original Android Development] mamba720027:
I remba read that comment somewhere "WELL THEN JUST GET AN IPHONE" maybe it was in siyah kernel section, lolz that was you? :p:D

Anyways it doesn't sound kernel related problem and maybe its an app like widget locker useing up a large portion of your memory and slows up your device upon wakeingup ,cause like I said before mine wakesup less than half a second.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Frag1le:
Thanks for your answer, from a technical point of view it didn't make any sense for a kernel to 'settle'.

Only really 'advanced' services like for example Windows Superfetch need some settling (learning which programs you start on a regular basis) but i don't think android has anything like this build in.

Well perhaps something did change that affects the wifi then, cause I'm one of those 24/7 Wifi users (wifi always awake in the advanced options) and i just went back to 28.2 cause today the drain of the 29 kernel was just too noticeable compared to 27 or 28.x. Normally my phone sits on my desk @ work for like 4 hours a day idling and then it would drain like perhaps 15% max. Now with 29 it drained 25~30%. So that's really noticeable.

The drain only seems to be while the device is sleeping (standby) cause I also watch a lot of series (usually like 1,5 hours of episodes) in my bed before i go to sleep and the drain while the stock videoplayer was playing xvids @ 0% brightness didn't decrease or increase noticeably.
[Galaxy S III Original Android Development] drakester09:
Hey Andrei

Perhaps the difference in drain between 29 and 28.1 comes from this commit:

bcmdhd: neuter net_os_rxfilter_add_remove

https://github.com/AndreiLux/Perseus-S3/commit/8824f61a361a67709397cf00efba5de8f1bce2ff

Seems that with the wifi driver update it got overwritten by the previous line.

https://github.com/AndreiLux/Perseu...drivers/net/wireless/bcmdhd/dhd_linux.c#L5218
[Galaxy S III Original Android Development] AndreiLux:
No I had that already fixed before I compiled the released 29 versions. The commit came from my second internal repository and I didn't have my stashed changes pushed after. It also doesn't explain the speed differences people were getting between the two drivers. In any way, I reverted it in 29.1.
[Galaxy S III Original Android Development] abelle_abelle:
please fix slow charging :-/
[Galaxy S III Original Android Development] Highlander11:
Thanks for 29.1, Andrei! I will wait for the OP to be updated to see what changes you have in there ;)
[Galaxy S III Original Android Development] siavash_Skh:
If we dont have any problem with 29, should we flash the new (29.1) version ? is it better ? or just for people how has the proble you said andrei ?

Thanks A lot
[Galaxy S III Original Android Development] Frag1le:
I'm just 5 hours back on 28.2 and the drain difference is just so noticeable.

Will try 29.1 to see if the idle drain is fixed.

Thanks
[Galaxy S III Original Android Development] DirkStorck:
I can't confirm that the phone charges slow with this kernel.

From 26% to 100% in 2hr 20 min.

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] GrayJack:
As for me I see no problem with 29. It is perfectly smooth and stable at XXELL4 and XXELL5.
[Galaxy S III Original Android Development] AndreiLux:
Go buy a proper 5 pinned USB cable and don't use the Samsung provided one if you have issues.
[Galaxy S III Original Android Development] GrayJack:
Andrei, don't you want to include charge current tweak in STweaks just like in Siyah to avoid such complains?
[Galaxy S III Original Android Development] AndreiLux:
People having slow charging issues cannot be fixed with just changing the current settings, it's a detection error in the driver and I have not researched it yet, all I know is that it doesn't seem to happen with 5 pinned USB cables.

And if code would magically write itself I would have done it by now. I said I would do it, but for now I made the latest version stable to that everybody is happy. I didn't even plan on releasing 29 if it wasn't for the exploit fix. So you will have to wait some time more for a more feature rich next version.
[Galaxy S III Original Android Development] KennyLegend:
Could u elaborate a little on this slow charging topic Andre pls as I have a few work colleagues on stock carrier roms with this issue since upgrading to ics/jb.

Thx.

Sent from my GT-I9300
[Galaxy S III Original Android Development] abelle_abelle:
well then how come it works fine fast charging on stock kernel same charger?
[Galaxy S III Original Android Development] KennyLegend:
Well firstly u can't fast charge on stock kernel.

Secondly, normal charging doesn't work with all stock kernels. Read my post above yours. It works for some people only since ics..

Sent from my GT-I9300
[Galaxy S III Original Android Development] rowlers:
v.29 (as has all other others) charges perfectly well for me so I understand Andrei's predicament...
[Galaxy S III Original Android Development] siavash_Skh:
I thinks perseus kernel drain more battery in sleep mode compared to stock one.

With stock on for 9 hours at sleep mode the battery status changed only 2 to 3 percent. But this was 4 to 5 in v29 and 10!! For v29.1.

So I thinks the v29 was better in battery.

Thanks
[Galaxy S III Original Android Development] mamba720027:
Those observations cannot be identical situation to compare battery drain with stock and Perseus to make a valid conclusion. Have to put the phone in airplane mode,freeze all background apps and let the phone run.

Sent from my GT-I9300
[Galaxy S III Original Android Development] siavash_Skh:
But all three situtation were same. The wifi was off and the same background apps. I didnt change or install or unistall any app.

You right but in my opnion becase of the same usage of phone in these 10 or 11 hours of v29.1 its not good with battery. Maybe it will be better after some decharging and charhing

How is thr new kernel (29.1) for u ? Compared to 29 and stock one?
[Galaxy S III Original Android Development] mamba720027:
Haven't tried stock and v29 I haven't used my phone good enough to say because v29.1 was released quick. But here's my current usage in the middle of watching a movie. This only random usage,depending on light or heavy tasks,signal and all that battery will vary for everyone.

Sent from my GT-I9300
[Galaxy S III Original Android Development] faddys123:
Does this kernel have Swap support?
[Galaxy S III Original Android Development] gun@id:
yes it is
[Galaxy S III Original Android Development] Frag1le:
Fine that your battery use is good but we were all talking about the drain when the device is sleeping, not when the screen is primarily on.

It's to early to tell really, but the idle drain on 29.1 seems promising.

My SGS3 slept for about 8 hours and the drain was only 8% with wifi on.
[Galaxy S III Original Android Development] mamba720027:
That sounds good 8%. Not sure if I had that prob with v29 cause I use my phone a lot as u can prob tell from screen. So wance I get home I charge. I know v28.2 in 4-5hour sleep I had a 2% discharge. This kernel just gets better.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Frag1le:
Yes that's very good. Here's the screenshot of the history.

As you can see the first part is with 29, then I flashed 28.2 used it a couple of hours and eventually flashed 29.1 and you can see the downwards line is just less steep then with 29.

The line interruptions are when I flashed kernels.

Thanks AndreiLux for your great support

Sent from my GT-I9300
[Galaxy S III Original Android Development] mamba720027:
Yea line look less steep after the last cliff.notice u got something awakening while the screen off also. Should have disabled mobile data,switch on airplane mode freeze those apps u got syncing switch wifi on and do a good comparison. Oh well too late. :cool:

Sent from my GT-I9300
[Galaxy S III Original Android Development] Frag1le:
Yeah but i got gmail, facebook, whatsapp synching, foldersync that uploads my newly taken pictures to gdrive at night. So those few awake moments are normal.
[Galaxy S III Original Android Development] mamba720027:
Ok see what you saying. Check these out,took after I upload those 2 not so long ago. Pounded the crap out of the battery.

Sent from my GT-I9300
[Galaxy S III Original Android Development] ArbiterGR:
I want to report on that too. Using The "Currents Widget" from play store, it reports 999mA when ac charging. When using Stock kernel charging rate is normal and same goes for Siyah's kernel with or without messing with the ac charging rate tunables. But on perseus it takes more than 5 hours to charge from 0 to 100% although the currents widget still reports 999mA. I tried this both on Samsung's included usb cable and, a universal 5pinned usb cable as well as a zenis dock charger:P
[Galaxy S III Original Android Development] MuertoKo:
Afaik Sammy software won’t report actual charing mA but the max. Allowed, on HTC devices it’s different (used to use this app on Sensation). This just means your default current for AC charing is 999mA, it should be 900mA on USB from Perseus changelog
[Galaxy S III Original Android Development] zappoo:
Any chance CRT off will be fixed?
[Galaxy S III Original Android Development] ezechiele2517:
hi all, what is the difference beetween the tar version and zip version? thanks can I flash both from CWM recovery?
[Galaxy S III Original Android Development] MuertoKo:
.zip is for CWM, .tar is for Odin/Mobile Odin
[Galaxy S III Original Android Development] sduford:
The TAR version is for Odin
[Galaxy S III Original Android Development] Frag1le:
It seems the extra batterydrain kernel 29 gave is gone in 29.1, well for me at least.
[Galaxy S III Original Android Development] Alexdream:
This Kernel work in stock XXELL5?

Sent from my GT-I9300
[Galaxy S III Original Android Development] IamIrene:
Why not
[Galaxy S III Original Android Development] GrayJack:
v29 is working now in my SGS3.
[Galaxy S III Original Android Development] mincorp:
first of all, you should go through at least 2 charging cycles to draw any meaningful conclusions.

barring numerous complains from other people regarding high battery drain, i'd be inclined to think that one of your media playing apps is the culprit (either excessive scans or audio2 wakelock)

also, bbs is a good place to start in this kind of situation.
[Galaxy S III Original Android Development] ezechiele2517:
Hi, I flashed the latest Perseus kernel 29.1 with Revolution HD 17.1 ROM and I found a problem: when I active the power saving toggle the phone become very slow and the rendering is slower. With previouse perseus kernel .27 I haven't this problem. Why? Have you tryed it?
[Galaxy S III Original Android Development] GrayJack:
Using stock XXELL5 with cache from XXELL4 - Perseus 29 is extremely smooth in power saving mode. Possibly ROM issue or something wrong with running applications/services.