sammy battery vs cm battery - Galaxy S III Q&A, Help & Troubleshooting

this issue is driving me crazy... no matter what i do i can't get good battery life with cm based roms.... no mater what i try: official, temasek, carbon, paranoid, all have **** battery life that barrely last a day.
i always end up going back to sammy based roms like wanamlite. byt i dont like it!
i greenify apps, disable gps, dormancy, startup apps, what else???
if it matters, i never change kernels..

You aren't experiencing anything new, only Samsung based roms will get good battery life on the S3.

Probably due to a lack of sources
Sent from my GT-I9300 using Tapatalk 4

rootSU said:
Probably due to a lack of sources
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
what do you mean?

Samsung don't release their exynos source code properly, so AOSP developers don't have all the information required to get similar performance out of all the hardware components
Sent from my GT-I9300 using Tapatalk 4

rootSU said:
Samsung don't release their exynos source code properly, so AOSP developers don't have all the information required to get similar performance out of all the hardware components
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
is there any aosp or aokp based rom that will provide good battery life?

They're all about the same
Sent from my GT-I9300 using Tapatalk 4

they last the same for me with custom kernels.
i wont go back to sammy
Sent from my Nexus 7 using xda app-developers app

To me, any CM/AOSP and any kernel included or custom last about the same, and that is about 40% less then stock samsung rom.
Of course depending on situation...
However I won't be coming back to stock samsung rom any time soon

Agreed, custom kernels help a lot but still not quite as much as stock. Similarly, im sticking with aosp
Sent from my GT-I9300 using Tapatalk 4

Probably irrelevant but i tried the Illusion Rom and it gave me 1d 53h of normal usage whereas sammy barely gets me through the day
Just thought id mention it

1 day + 4 days?
Sent from my GT-I9300 using Tapatalk 4

You are confusing things here...
rootSU said:
Probably due to a lack of sources
...
Click to expand...
Click to collapse
You are confusing things here - the lack of sources is somehow relevant to the kernel part, and generally the best kernels in regard to power consumption are the custom ones (like Perseus, Siyah and so on) - which are precisely started from the sources coming from Samsung.
The ROM part only talks to the kernel part, and once you have the same kernel (like Siyah) talking to both a CM ROM and a Sammy ROM and you get better power consumption in Sammy I don't really see how that can be related to "lack of sources".

rootSU said:
1 day + 4 days?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
hahahaha sorry my bad:silly:
1d 13h

AthlonGFX said:
Probably irrelevant but i tried the Illusion Rom and it gave me 1d 53h of normal usage whereas sammy barely gets me through the day
Just thought id mention it
Click to expand...
Click to collapse
Yeah sure, I even got on couple of occasion over 2 day and maybe 3-4hrs...
But however on stock with the the approximately same usage I would still have 30-40% more usage time.

xclub_101 said:
You are confusing things here - the lack of sources is somehow relevant to the kernel part, and generally the best kernels in regard to power consumption are the custom ones (like Perseus, Siyah and so on) - which are precisely started from the sources coming from Samsung.
The ROM part only talks to the kernel part, and once you have the same kernel (like Siyah) talking to both a CM ROM and a Sammy ROM and you get better power consumption in Sammy I don't really see how that can be related to "lack of sources".
Click to expand...
Click to collapse
No im not confusing things - but you're over simplifying things. The kernel sources are complete. Siyah uses the samsung kernel sources as a base and it interacts with touchwiz roms perfectly. The same kernel does not interact with aosp roms in the same way.
Set up a touchwiz rom with basic settings and siyah kernel and compare it to aosp with the same basic settings and kernel and touchwiz will win hands down.
Samsungs kernel source may be complete but the exynos and hardware sources are incomplete. That's why an aosp rom camera is much lower quality than samsungs using the same hardware.
Also its worth noting that these dual purpose kernels are built from a mixture of samsung sources and Google sources. Otherwise they wouldn't be able to support 4.2.2 aosp roms...because 4.1 kernels are different to 4.2 kernels...hence no existing kernels can work on 4.2 sammy roms. We need their kernel sources for that, but they will come unlike complete exynos sources.
If you look at the snapdragon variants of the s3, the chipset is well documented so the developer community have much more scope to get comparable battery performance but this isn't an option for us. This is why the developer community here are so frustrated with samsung and the i9300 to the point where team hacksung decided they no longer wish to support cyanogen on exynos devices. We are unable to exploit the hardware to its full potential as we don't have what's required. Developers need to use a lot of guess work to get things working. Our s3 device tree for aosp roms is incomplete and this is samsungs fault for not being forthcoming with their non kernel sources
Sent from my GT-I9300 using Tapatalk 4

You are still confused
rootSU said:
...
Samsungs kernel source may be complete but the exynos and hardware sources are incomplete. That's why an aosp rom camera is much lower quality than samsungs using the same hardware.
...
Click to expand...
Click to collapse
That is completely irrelevant to what it was discussed - and is also false since for instance your own post is somehow trying to suggest that the AOSP camera works perfectly for non-Exynos S3 and works bad for Exynos S3 - once you get your time to check reality instead of propagating stuff you will see that is just another myth and that:
a) the AOSP camera is about as bad for BOTH CPUs
b) the information that is missing has nothing to do with the CPU from Samsung but instead with the camera itself.
And getting back to what this thread was about - POWER CONSUMPTION - the facts show that most CM ROMs have worse power consumption than most Sammy ROMs when both scenarios are run with the SAME KERNEL compiled from sources. A very remote point might be (maybe) made for device-drivers that are blobs (and where custom ioctls maybe are not documented) - but CPU / power management is not one of those! Debunking even further your childish talking point - with the same Sammy ROM the POWER CONSUMPTION is clearly better when running with one of those custom kernels then when running standard Samsung kernel - so any point that somehow any information relevant to power consumption is missing - when actually the custom open-source kernels are demonstrably better in this regard - now stands forever debunked

xclub_101 said:
That is completely irrelevant to what it was discussed - and is also false since for instance your own post is somehow trying to suggest that the AOSP camera works perfectly for non-Exynos S3 and works bad for Exynos S3 - once you get your time to check reality instead of propagating stuff you will see that is just another myth and that:
a) the AOSP camera is about as bad for BOTH CPUs
b) the information that is missing has nothing to do with the CPU from Samsung but instead with the camera itself.
And getting back to what this thread was about - POWER CONSUMPTION - the facts show that most CM ROMs have worse power consumption than most Sammy ROMs when both scenarios are run with the SAME KERNEL compiled from sources. A very remote point might be (maybe) made for device-drivers that are blobs (and where custom ioctls maybe are not documented) - but CPU / power management is not one of those! Debunking even further your childish talking point - with the same Sammy ROM the POWER CONSUMPTION is clearly better when running with one of those custom kernels then when running standard Samsung kernel - so any point that somehow any information relevant to power consumption is missing - when actually the custom open-source kernels are demonstrably better in this regard - now stands forever debunked
Click to expand...
Click to collapse
Without the exynos source the cm kernels can't take full advantage of exynos power saving features..... Simple.
On another note, I suggest you tone down your attitude, and apologise for calling rootSU childish, and don't treat this place like somewhere you can come to wind people up or I will personally introduce you to the moderators

xclub_101 said:
That is completely irrelevant to what it was discussed - and is also false since for instance your own post is somehow trying to suggest that the AOSP camera works perfectly for non-Exynos S3 and works bad for Exynos S3 - once you get your time to check reality instead of propagating stuff you will see that is just another myth and that:
a) the AOSP camera is about as bad for BOTH CPUs
b) the information that is missing has nothing to do with the CPU from Samsung but instead with the camera itself.
Click to expand...
Click to collapse
Wow, way to take something completely out of context and miss an entire point! I didn't even think this was possible. Impressive.
So firstly, I cited the camera as an example of something that relied on Samsung sources along with the exynos chipset (NOT CPU by the way, I haven't use the term CPU, so I guess you just decided to choose that term yourself). The sources are incomplete and the binaries, libs an patches provided are not enough to get everything running on the device as it should be. I, in know way stated or inferred that the camera was better on snapdragon S3's.
The point was we don't have everything in relation to the camera, ergo the camera is not as good as Samsungs. This is not because of the AOSP camera application. Instead it is down to a lack of documentation /sources for the camera HAL. It was a simple example explaining that if we haven't got everything required to run the hardware properly, we can't achieve the same performance. This is obvious with the camera and it's poorer quality images compared to the touchwiz camera using the very same hardware. This is not the case with just the camera though, this extends to all the hardware where we have incomplete information and sources.
xclub_101 said:
the facts show that most CM ROMs have worse power consumption than most Sammy ROMs when both scenarios are run with the SAME KERNEL compiled from sources
Click to expand...
Click to collapse
It is true, with the SAME KERNEL on both platforms, power consumption is different (That's exactly what my post said). However, the dual purpose kernels are compiled from 2 sets of sources, so AOSP and Touchwiz platforms do not overlap 100% with each other (usage wise) in regards to what is compiled into these kernels. Touchwiz ROMs utilise (random guess number to illustrate a point) 90% of whats in the kernel as does AOSP. Meaning there could be a (fictitious) 10% of the kernel exclusively for each platform.
xclub_101 said:
but CPU / power management is not one of those!
Click to expand...
Click to collapse
I didn't mention CPU power management. I did not say that the kernels on AOSP were any different at *managing* the power. Although thanks for bring that up... because now that you mention it, they are.
xclub_101 said:
Debunking even further your childish talking point
Click to expand...
Click to collapse
I don't understand how you can be so audacious to call my talking point childish when you've managed to avoid applying adult levels of reading to my entire post thus far and have taken every point I made conversely to how it was intended.
xclub_101 said:
with the same Sammy ROM the POWER CONSUMPTION is clearly better when running with one of those custom kernels then when running standard Samsung kernel
Click to expand...
Click to collapse
Say what now? If You're saying you think that custom kernels on a Sammy ROM are better than stock kernels on the same sammy rom for power consumption, you'd be right. I never said anything to the contrary of that. I said these custom kernels on a sammy rom are better that they are on an AOSP rom for power consumtion.
xclub_101 said:
so any point that somehow any information relevant to power consumption is missing - when actually the custom open-source kernels are demonstrably better in this regard - now stands forever debunked
Click to expand...
Click to collapse
I really don't think you are managing to get any point you're trying to make across. You're not even arguing against the point I made. Surely a rebutal must directly address my points. You seem to be meandering aimlessly, taking pot shots at what you *think* is my point.
Again, I never said anything about information pertaining to power consumption being missing. My point is simple and basic, so here it is again. We do not have everything to run the hardware optimally. Whenever this is the case, performance suffers. If it is not running as originally intended because sources are missing to provide proper and full support, things are inefficient. Inefficiencies can lead to more power being used than is needed. That's all I was saying. You seem to be going out of your way to argue points I didn't even make, and not even graciously.
Edit>
Link for reading:
http://www.xda-developers.com/android/samsung-aware-of-exynos-documentation-issue/

slaphead20 said:
Without the exynos source the cm kernels can't take full advantage of exynos power saving features..... Simple.
On another note, I suggest you tone down your attitude, and apologise for calling rootSU childish, and don't treat this place like somewhere you can come to wind people up or I will personally introduce you to the moderators
Click to expand...
Click to collapse
I would just put him on ignore. It won't be the first time he's acting like an obnoxious know-it-all and it certainly won't be his last. For all his talk, I haven't seen him contribute anything remotely useful to any sort of development, just pointless ranting, raving and demanding.

Related

What's the point of custom kernels for CM7/9?

This will likely be a controversial topic, but I'm going to risk it.
Also note that this is not meant to be a jab at kernel developers, or an attempt to lick CM developers' balls.
I have just been thinking. Custom kernels often claim an improvement in battery life or performance with their kernels. With Samsung ROMs, this is believable. The case of the fuel_alerted bug not being fixed with Samsung ROMs is an example that Samsung kernels aren't the best.
However, with Cyanogenmod ROMs you would think that the developers of CM would know best, since they *probably* work far more intimately with the code than custom kernel developers. Has anyone found an improvement in battery life with a custom kernel as compared to the stock CM kernel?
Now, I'm aware that custom kernels offer some features not found in the stock CM kernel, like how dual-booting is available for Siyah. But let's focus on battery life and performance for now.
Again, this is not meant to be a flaming thread. I genuinely wish for a conducive discussion on this topic. Lastly let me express my appreciation for both CM and Kernel developers, for devoting their own free time for our sakes.
Thanks!
I'm not sure if this is what you are looking for as an answer but a tweak i've used to give better battery performance is CPU FREQ_MIN. This is the frequency below which the 2nd core is not used. I don't believe you'd be able to use this tweak without a custom Kernel
puccini said:
I'm not sure if this is what you are looking for as an answer but a tweak i've used to give better battery performance is CPU FREQ_MIN. This is the frequency below which the 2nd core is not used. I don't believe you'd be able to use this tweak without a custom Kernel
Click to expand...
Click to collapse
It helps, thanks Personally I would prefer to try to quantify battery life with different kernels myself. Most phone review sites choose to test battery life by looping a video, however I do not believe this accurately measures battery life.
If anyone knows of an app that loops web browsing I will be happy to test it for myself.
I don't even care for extra 10 minutes battery life. If you want extra battery life don't use the phone. Lol.
Sent from my GT-I9100 using XDA
Alvin Lai said:
I don't even care for extra 10 minutes battery life. If you want extra battery life don't use the phone. Lol.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
But I bought the phone so that I can use it right?

[KERNEL][SENSE]intersectRaven's Kernel - 20130625_10XX

Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
Latest Kernel Here
20130625_10XX:
- updated with fix for more recent 4.1.2 Sense ROMs (should fix camera issue)
*unsure if this becomes incompatible with older 4.1.2 Sense ROMs though
20130602_07XX:
- NTFS support
- compiled using 4.8 linaro compiler
- improved workqueue queueing
- sleeper improvements
- responsiveness patches to the frequency controllers
20130531_09XX:
- fixed earpiece volume during calls
20130528_17XX:
- more optimizations (see GitHub)
20130527_18XX:
- more ARM implementations (see GitHub)
20130527_10XX:
- ARM implementations of kernel algorithms (see GitHub)
20130527_09XX:
- compiler optimization flags
20130526_22XX:
- initial version
- uses Linaro compiler
You can find my kernels at:
intersectRaven's Kernels
GitHub is at:
intersectRaven's GitHub
FAQ or something like that:
1.) Camera doesn't work!
- Try this fix from Golv here. This usually occurs on older ROMs.
*Latest 20130625_10XX version should solve this without flashing older camera libs.
Reserved 2
Reserved 3
Nice to see ir taking interest in the One. Truly a great dev
Sent from my Nexus 4 using Tapatalk 4 Beta
Uhhh nice to see you here
intersectRaven said:
Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
Click to expand...
Click to collapse
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
m0nz said:
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
Click to expand...
Click to collapse
Should have put a qualifier there huh? Anyways, it's pointless from a no tweaking perspective since undervolting may not work for some chips and could cause more trouble (random restarts and the like) than it's worth. It's fun for a tweaker (like when I did something like that for the N1) but not for someone who's the flash and forget type. :fingers-crossed:
Thanks
P.S you missing the ":" on the http link
Really glad to have you here iR. Missed your kernels from my nexus one days with those hybrid AVS kernels.
Camera is buggy
Sent from my HTC One using xda app-developers app
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The camera will problably need som librarys, like most other kernels, I think. There is a zip for this in other threads (couldn't find it right away)
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What is the problem exactly? Also, is this a custom Sense ROM or stock Sense? Just mentioning that it is buggy doesn't actually help me solve it since there are no bugs in my phone.
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Intersect my man. Nice to see u in the HTC one forums!
Sent from my HTC One using xda app-developers app
Camera troubles
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
chourmovs said:
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Can you try the link posted below by Maikeu and get back to us whether it fixes the issue?
Maikeu Locatelli said:
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
Click to expand...
Click to collapse
Posted this in the second post here for future reference.
HI, after fashing this kernel , i cannot hear any sound from call dial ,
008325 said:
HI, after fashing this kernel , i cannot hear any sound from call dial ,
Click to expand...
Click to collapse
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
intersectRaven said:
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
Click to expand...
Click to collapse
Thank you very much i really like this kernel , smooth , cold , save battery

[Q] Difference in Display sharpness [CM] vs [SAMMY]

I have been using L-droid for a month now. Its perfect in every way except the following two.
1 - Display crispness
2 - Camera
1 - Display Crispness
I feel the Stock Sammy ROMs have a much sharper and crisper image with better colors as compared to any CM based ROM I've used. I want to understand why is this difference ?
2 - Camera
Stock Sammy takes Photos way too quickly (from the time you press the button to the time it gets snapped and ready for another) compared to stock CM camera. Again I want to understand why is this difference ?
salimbaba said:
I have been using L-droid for a month now. Its perfect in every way except the following two.
1 - Display crispness
2 - Camera
1 - Display Crispness
I feel the Stock Sammy ROMs have a much sharper and crisper image with better colors as compared to any CM based ROM I've used. I want to understand why is this difference ?
2 - Camera
Stock Sammy takes Photos way too quickly (from the time you press the button to the time it gets snapped and ready for another) compared to stock CM camera. Again I want to understand why is this difference ?
Click to expand...
Click to collapse
You are correct about 1, there's a sharpness fix implemented in some kernels.
No idea about the second one, are we talking AOSP vs samsung camera on AOSP and samsung roms respectively or both on a samsung rom?
If former, it's due to closed sources.
Choristav said:
You are correct about 1, there's a sharpness fix implemented in some kernels.
No idea about the second one, are we talking AOSP vs samsung camera on AOSP and samsung roms respectively or both on a samsung rom?
If former, it's due to closed sources.
Click to expand...
Click to collapse
Sharpness fix in kernels : which kernels have it? Can you name them.
AOSP camera on AOSP ROM vs SAMMY CAM on STOCK SAMMY ROM.
If it's because of closed source then my question comes out to be : developers have figured out the camera driver what's the factor they haven't figured out yet?
My curiosity comes from me being a driver developer for nix for specialized systems . Haven't worked on any drivers for Android yet. But I am curious.
salimbaba said:
Sharpness fix in kernels : which kernels have it? Can you name them.
AOSP camera on AOSP ROM vs SAMMY CAM on STOCK SAMMY ROM.
If it's because of closed source then my question comes out to be : developers have figured out the camera driver what's the factor they haven't figured out yet?
My curiosity comes from me being a driver developer for nix for specialized systems . Haven't worked on any drivers for Android yet. But I am curious.
Click to expand...
Click to collapse
Boeffla has the sharpness fix, that's as much as I can tell you, you're better off doing a quick search yourself.
I don't dig deep into issues since I can't do anything about them, but as far as I know, they haven't found what exactly makes all the hardware camera tweaks work and how to implement them, maybe try searching for codeworkx posts or even justarchi. I believe it's the same with HWComposer.
The only reason I stuck with Sammy ROM, it's camera quality :/
Sent from my GT-I9300 using XDA Premium 4 mobile app

Which ROM do you guys recommend?

So... First of all, I'm not asking for the best ROM.
At the moment, I'm using ArchiDroid v2.5.2 on my i9300, and it's fast, but... Random reboots, and the camera quality it's not the same as in the 4.3 ROM's.
What I want is a ROM with no random reboots, with the best camera quality and of course, as fast as AOSP or even faster
So... Which ROMs (and kernel) do you guys recommend?
I'm tired of switching between 4.4.x ROMs, all of them have bugs. The Note2 ports are laggy (even though everybody is saying that these ROMs are smooth as butter) and AOSP have the problems that I've mentioned before.
Help me, please
Best/Recommend Roms/kernels threads are not allowed on XDA, try them yourself and decide.
If I were to recommend you I would say ArchiDroid or NeatRom
Sent from my GT-I9300 powered by ArchiDroid+ArchiKernel
gabyif said:
Best/Recommend Roms/kernels threads are not allowed on XDA, try them yourself and decide.
If I were to recommend you I would say ArchiDroid or NeatRom
Sent from my GT-I9300 powered by ArchiDroid+ArchiKernel
Click to expand...
Click to collapse
Yes, I know that. But there are SO many ROMs and I've tried lots of them, and none of them are "perfect".
ArchiDroid or NeatROM? JellyBean versions? I've tried both, but the KK version.
emanuelparedes said:
Yes, I know that. But there are SO many ROMs and I've tried lots of them, and none of them are "perfect".
ArchiDroid or NeatROM? JellyBean versions? I've tried both, but the KK version.
Click to expand...
Click to collapse
Yes,Jb versions.
There are no such thing as perfect,you need to make sacrifice
Sent from my GT-I9300 using XDA Free mobile app
andjeomilosrdja said:
Yes,Jb versions.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
I'm going to try ArchiDroid. Is it based on Stock ROM or AOSP?
emanuelparedes said:
I'm going to try ArchiDroid. Is it based on Stock ROM or AOSP?
Click to expand...
Click to collapse
Stock JB
Sent from my GT-I9300 using XDA Free mobile app
Try Imperium KK: stable, smooth and pretty fast! This ROM is based on Note2 porting developed by JustArchi
http://forum.xda-developers.com/galaxy-s3/development/rom-t2842856
broken920 said:
Try Imperium KK: stable, smooth and pretty fast! This ROM is based on Note2 porting developed by JustArchi
http://forum.xda-developers.com/galaxy-s3/development/rom-t2842856
Click to expand...
Click to collapse
Thanks for the suggestion. But I've read the comments and "everybody" was talking about FC and bugs.
Try Imperium 29 based on 4.3 stock deodexed
http://forum.xda-developers.com/galaxy-s3/development/rom-imperium-v26-0-v13-6-t2135852
broken920 said:
Try Imperium 29 based on 4.3 stock deodexed
http://forum.xda-developers.com/galaxy-s3/development/rom-imperium-v26-0-v13-6-t2135852
Click to expand...
Click to collapse
First I will flash ArchiDroid V1.7.18 and if I don't like it, I'll flash this one. Thanks!
Stock debloated
I would use the stock Android 4.3, root it and than remove all the Bloatware from Samsung, install Googy Max2 and you got a pretty fast phone
Abort the Samsung laggy and almost useless world, choose AOSP roms.
I can propose you the only AOSP rom tried: CyanogenMod 11.
Download the latest M release (more stable than nightlies).
Note that there are some minor bugs, a 4.4 "perfect" system for S3 actually doesn't exist.
Then... the better kernel is BOEFFLA, useless to say [emoji6]
Download the related app (the latest BOEFFLA Config-v2 apk), choose zzmove or pegasusqplus as governor, while as scheduler choose sio.
To boost your phone, have fun with all the kernel parameters, CyanogenMod is considered the better rom, all other AOSP roms are based on CM source code, useless to change os.
broken920 said:
Try Imperium 29 based on 4.3 stock deodexed
http://forum.xda-developers.com/galaxy-s3/development/rom-imperium-v26-0-v13-6-t2135852
Click to expand...
Click to collapse
This ↑
Simone98RC said:
Abort the Samsung laggy and almost useless world, choose AOSP roms.
Click to expand...
Click to collapse
A wildly sweeping and inaccurate statement if ever there was one.
There are some exceptional stock based ROMS out there, with very good performance, good battery life and stock features that you don't get in AOSP which many people like to have (also from what i've seen, the stock Camera app gives better pictures too)
hundred_miles_high said:
A wildly sweeping and inaccurate statement if ever there was one.
There are some exceptional stock based ROMS out there, with very good performance, good battery life and stock features that you don't get in AOSP which many people like to have (also from what i've seen, the stock Camera app gives better pictures too)
Click to expand...
Click to collapse
I tried Android Revolution HD: at first was moving better than stock rom, but when I began to use hardly my device... too many lags and terrible slowdowns.
Caused mainly by the unremovable TouchWiz.
Using another launcher, the heavy TouchWiz works ever, for different reasons than the simple use of launcher.
You can remove all the bloatware, make lots of optimizations... but TouchWiz will "eat" your RAM (only 1 GB on I9300 and lots of its variants) and never you'll be able to quietly use so many apps as in AOSP roms.
On CyanogenMod, Trebuchet can be completely replaced by other launchers, unthinkable thing on a Samsung rom.
Simone98RC said:
I tried Android Revolution HD: at first was moving better than stock rom, but when I began to use hardly my device... too many lags and terrible slowdowns.
Caused mainly by the unremovable TouchWiz.
Using another launcher, the heavy TouchWiz works ever, for different reasons than the simple use of launcher.
You can remove all the bloatware, make lots of optimizations... but TouchWiz will "eat" your RAM (only 1 GB on I9300 and lots of its variants) and never you'll be able to quietly use so many apps as in AOSP roms.
On CyanogenMod, Trebuchet can be completely replaced by other launchers, unthinkable thing on a Samsung rom.
Click to expand...
Click to collapse
You tried one other stock based ROM and made your conclusion from that alone?
Each to their own, but I've used enough versions of CM on enough devices over the years to know the pros and cons, and personally on the S3 I can get a most satisfactory level of performance and battery life from a stock derived ROM whilst not losing any of the additional functions.
hundred_miles_high said:
You tried one other stock based ROM and made your conclusion from that alone?
Each to their own, but I've used enough versions of CM on enough devices over the years to know the pros and cons, and personally on the S3 I can get a most satisfactory level of performance and battery life from a stock derived ROM whilst not losing any of the additional functions.
Click to expand...
Click to collapse
A Samsung rom is useful only for a better compatibility with Samsung devices and the 2-way call recording support.
Simone98RC said:
A Samsung rom is useful only for a better compatibility with Samsung devices and the 2-way call recording support.
Click to expand...
Click to collapse
Enough said, this is going off-topic and is not helpful to the OP, and as we both agree on your statement of 'A Samsung rom is useful for better compatibility' that's reason enough on it's own to recommend a stock derived ROM like Imperium as it will address the OP's original request of:
emanuelparedes said:
What I want is a ROM with no random reboots, with the best camera quality
Click to expand...
Click to collapse
hundred_miles_high said:
Enough said, this is going off-topic and is not helpful to the OP, and as we both agree on your statement of 'A Samsung rom is useful for better compatibility' that's reason enough on it's own to recommend a stock derived ROM like Imperium as it will address the OP's original request of (blablabla)
Click to expand...
Click to collapse
Totally agree with the first thing, then you told a bull****, you based your "fictitious reason" on a my partial citation at your leisure.
To prevent misconceptions and "abuse" of what I said in the topic, @hundred_miles_high forget to explain that according to me, the stock roms "compatibility" is limited only to Samsung devices.
With BubbleUPnP and similar (you should know them), stock roms become completely useless... or you need the 2-way call recording? [emoji6]
OP dislikes (as everyone) forced reboots, and need a good camera quality. If the suggested rom is poorer in any other term respect to AOSP systems, it doesn't matter.
Is this your reasoning?
With CyanogenMod 11, the terrible 10.2 camera experience was aborted.
Stability is guaranteed, also if the releases are snapshots, more than 6 months of developing.
Simone98RC said:
Totally agree with the first thing, then you told a bull****, you based your "fictitious reason" on a my partial citation at your leisure.
To prevent misconceptions and "abuse" of what I said in the topic, @hundred_miles_high forget to explain that according to me, the stock roms "compatibility" is limited only to Samsung devices.
With BubbleUPnP and similar (you should know them), stock roms become completely useless... or you need the 2-way call recording? [emoji6]
OP dislikes (as everyone) forced reboots, and need a good camera quality. If the suggested rom is poorer in any other term respect to AOSP systems, it doesn't matter.
Is this your reasoning?
With CyanogenMod 11, the terrible 10.2 camera experience was aborted.
Stability is guaranteed, also if the releases are snapshots, more than 6 months of developing.
Click to expand...
Click to collapse
Why would a Samsung ROM be compatible with anything other than a Samsung phone? This is after all the SAMSUNG S3 forum isn't it, thought it would be pretty obvious to anyone with half a brain the context it was used in.
I don't understand your ramblings about BubbleUPNP but Bubble and Sempervid links work fine on my stock derived ROM - I use them regularly with youtube/tubemate , streaming web content and media on my other devices to play direct to my TV (or xbox or nexus 7 for that matter) through my S3.
Ran out of interest with rest of your post due to your rudeness, but maybe you should check the CM11 M9 thread in regard to complaints of poor sound quality in the camera app...........
hundred_miles_high said:
Enough said, this is going off-topic and is not helpful to the OP, and as we both agree on your statement of 'A Samsung rom is useful for better compatibility'
Click to expand...
Click to collapse
Yes, I was a bit hard in my answer, because you hurted me with your presumption and falsity to report properly my citation.
"This is after all the Samsung S3 forum"
With this stupid aforism you have damned lots of users who run a different rom.
I propose you to browse with brain (I dubt you know how use it, almost in this context) any S3 support forum, and see how many people use, speak and receive support about CyanogenMod, SlimKat, PacRom, etc.
And you are the first user who compare, even consider better a stock rom than AOSP... in terms of performance.
I hope you are joking.
"Ran out (...) Samsung devices"
You won't recognize the mistake (if not intentional) when you reported partially my famouscited my famous citation.
The truth is that you braved me since replying my first post: this is a topic where OP required "suggestions" (do you know this term?) from each user, not debates, nor topic wars.
Reread the topic, reflect about and get out, you told enough.

When will V30 got Energy Aware Scheduling (EAS) supporting kernel?

After seeing these 2 links out there I refuse to buy V30 as long as it has outdated kernel without sched governor support
What do you think?
Then don't get it. I'm going to.
Sent from my iPhone using Tapatalk Pro
Request a dev add it.
We'll have custom kernels.
ChazzMatt said:
Request a dev add it.
We'll have custom kernels.
Click to expand...
Click to collapse
No. I don't want to drop $840 for top-phone and than seek paths to get it hacked, rooted and flash custom kernel in it to get just the same experience which others have in their $400-$550 phones. Like Xiaomis which vendors are fast to deliver modern linux and android kernel enhancements
That's what EAS it for https://forum.xda-developers.com/z5-premium/general/announcement-energy-aware-scheduling-t3620897
I'm willing to bet it doesn't. Pixel devices were the first to launch with it because the code is baked into the AOSP mainline kernel. As much tinkering as every manufacturer does to their device, and the relative newness of this kernel schedule, chances are that it's not.
Sent from my VS995 using Tapatalk
ChazzMatt said:
Request a dev add it.
We'll have custom kernels.
Click to expand...
Click to collapse
Billy Madison said:
No. I don't want to drop $840 for top-phone and than seek paths to get it hacked, rooted and flash custom kernel in it to get just the same experience which others have in their $400-$550 phones. Like Xiaomis which vendors are fast to deliver modern linux and android kernel enhancements
That's what EAS it for https://forum.xda-developers.com/z5-premium/general/announcement-energy-aware-scheduling-t3620897
(This below is a quote from post #1 of that link, so this is what he wants you to read... I'm posting it so you don't have to go there. But feel free to click the link anyway if you wish.)
PDesire said:
In help with @zacharias.maladroit we ported Energy Aware Scheduling (EAS) to our Xperia Z5 Premium
The benefits I already see:
The CPU is really cooler (that what Snapdragon 810 needed)
The idle time has been increased ALOT (like 50% more idle time)
Also it seems battery life has been improved alot
The Port repo:
https://github.com/PDesire/XperiaSatsukiEliteKernel/commits/hotplug
Stay Tuned, this kernel will go online soon
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Too funny. The link you just posted was a dev ADDING it to a Sony Experia Z5 custom kernel -- just like I said could be done easily for our LG V30 (if it doesn't have it already).
You proved my point.
Tbh why everyone wants EAS ? To have a ****ty Scheduler implementation provided by CodeAurora and get disappointed by it ?
The only device which works very well with EAS is the Pixel, and do you know why ? They don't use the CodeAurora implementation, they use their own one. And to use Google's implementation you need Google kernels and not kernels which are based on CAF (like most Snapdragon kernels are).
So keep with HMP, it's not bad like everyone is thinking
Your PDesire
Whats next? To blame the V30 cause it wont include itunes.. (-_-)
PDesire said:
Tbh why everyone wants EAS ? To have a ****ty Scheduler implementation provided by CodeAurora and get disappointed by it ?
The only device which works very well with EAS is the Pixel, and do you know why ? They don't use the CodeAurora implementation, they use their own one. And to use Google's implementation you need Google kernels and not kernels which are based on CAF (like most Snapdragon kernels are).
Click to expand...
Click to collapse
Thanks, mate. I see that you know vastly more than I do in android development space
But please look at that
Even if not look into second run which V30 supposedly loose due to 4Gb onboard vs 6Gb the first round speed is also pathetic. And this link in OP is telling us of very much improved kernel in Galaxy Note 8 compared with all previous generations of Touchwiz and Samsung kernels. Samsung was a beaten boy for it's proverbial lage but it is no more. While LG is becoming the most laughed at Android vendor with it's stutters, lags and hiccups every one complaining about. LG doesn't do nothing to improve in that space, what leads to frustrated and disgruntled customers hence loss continuing for 12 quarters loss of sales and market share. With that pace LG is gonna vanish and be sold to Google as ODM like HTC at best
Does Oreo for V30 support Energy Aware Scheduling (EAS) ?

Categories

Resources