yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] FadeFx:
Ok, i run stock kernel currently, so gonna give that beast a try later...

tapatalked from lollipopped i9300

---------- Post added at 08:27 PM ---------- Previous post was at 08:21 PM ----------

Installer gives an error at the end, "unmount data failed, device or resource busy."

tapatalked from lollipopped i9300

---------- Post added at 08:46 PM ---------- Previous post was at 08:27 PM ----------

/me sad, no touch2wake yet.... ;)

tapatalked from lollipopped i9300
[Galaxy S III Android Development] ilnessuno4691:
Guys with STweaks how i must to set "battery " profile? just that i select in "profiles" battery or then i tap on "activate profile"?
[Galaxy S III Android Development] duttyend:
Thank you so much JustArchi !!!

I installed it on a fresh CM12 W6 and it seems very promising : I only disabled logging (last tab) and it's already smoother than stock kernel!

Edit: and now using it with weekly 7 and still a lot smoother than original kernel! Thanks again :)
[Galaxy S III Android Development] nkirk:
Test version is working good.:thumbup:
[Galaxy S III Android Development] FadeFx:
[MENTION=5161352]JustArchi[/MENTION] sometimes in zram settings it shows "sSeekBar has failed: ...swapon failed for zram0" or something similar, also, could we have a max of 300mb, so i can set 600Mb on two disks?

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
The issue with swapon failed is fixed already, will be there in next version.

There is no physical limit for zRAM, so I can set maximum to 300 if you wish.
[Galaxy S III Android Development] FadeFx:
May i place a wish for next version? Id love to see touchwake in it, then it would be feature complete for my needs...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] EP21:
As far as our hardware can reproduce it it's available in 1.7.2( at least in kk).
[Galaxy S III Android Development] ramabg:
What is the difference between this and ArchiKernel_V1.7.2-AOSP_LP.zip ? I think the old 1.7.2 is working perfectly and has full feature.
[Galaxy S III Android Development] FadeFx:
I know that, i was talking about the 2.x test builds...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] Mostafa Wael:
ArchiKernel 2.0-test version is working smoothly and blazing fast!!!

Yeah, I need that touch2wake feature but, it is not that annoying for me, since it will be added back to the kernel along with the other features after testing phase. And Synapse is awesome man!! Thanks Archi for such a gift...

I had one question that is OT, but crucial for me. If the Snapdragon 810 is proven to be perfectly working with no overheating issues, will you get it? Or will you get the exynos equipped S6 because it is built with a ahead-of-its-time 14 nm unlike the former, which is built with 20 nm ? And does this UFS storage thing encourages you also ?

Thanks and sorry for interrupting :o
[Galaxy S III Android Development] EP21:
They are test builds for a reason and i wouldn't be surprised if they were added just before stable 2.0.
[Galaxy S III Android Development] Nees3:
I have just clean installed CM12 again, and tried to flash the 2.0. Again I run into the same problem as earlier this week. It shows splashsscreen then a 2nd time and boots back into recovery.

I also get an error saying something like: "unmount of /data failed (-1) Device or resource busy." , after flashing. I haven't had any problems flashing other kernels, but this one, every time the same result. On my last post, noone seems to have answered yet and now same problem.

Any solution?
[Galaxy S III Android Development] FadeFx:
I get the same error, but that is only something cosmetic in the updater script as it flashes and boots correctly for me.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] whatsgood:
It is disappointing on Qualcomms behalf. I think Samsung have outdone themselves on their new chip. The 810 is hardly competition for it. They have a 14 nm architecture, new UFS storage, LPDDR4 RAM, and their new benchmarks for the S6 Edge have scores around 70,000 in antutu. That's crazy for a phone with Quad HD. Compare that to the M9, which has a 1080p display and snapdragon 810 and it's getting around 55,000 on antutu, WHAT? The LG G flex 2? a little lower than the M9's score, but with throttling to prevent overheating the scores can get as low as 37,000. I am underwhelmed. I want to move away from Samsung and their closed sources, but it's stuff like this that makes it difficult.
[Galaxy S III Android Development] Mostafa Wael:
And that is what makes it a real tough question. It is like a trade off. Sacrificing the open-source beauty to gain some cutting edge properties and a more future proof device. Qualcomm will be going to the 14 nm FinFet manufacturing process in late H2 2015, which means according to what we saw from the lazy Qualcomm, phones with the upcoming S820 are going to be sold in Q1/Q2 2016 and that is really a long time for me to wait for.

Anyways, thanks for your answer!

Let's hope that S6 becomes development friendly by the means of a miracle :D :laugh:
[Galaxy S III Android Development] whatsgood:
It really is tough indeed. This time around, Samsung have opted out for a removable back cover. No expandable memory. Their rather mediocre capacity of 2450mAh for their battery seems questionable, as now you can't replace it, I wonder if their new processor is able to be battery efficient enough for that quad HD screen. We say it is future proof, but what happens after the 2 years of Samsung support, will cyanogenmod drop it like they did the S3? Will it be lucky enough to have developers releasing unofficial builds? It's all down to luck :confused: I agree, the S820 seems to be a beast when you look at the leaked specs, but 2016 is quite far away, 3 months from now and I will have owned this S3 for 3 years, which is probably the case for many others. Feeling a bit clueless right now haha :eek:
[Galaxy S III Android Development] RoelD92:
well, we can always wait for the G4 or Z4:D
[Galaxy S III Android Development] Mostafa Wael:
S810 equipped devices again ? Not my cup of tea :angel: .

---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------

BTW, I have realised that the galaxy S6 is not the only exynos-powered device in Sammy's history

The Note 2 was the same, and it was one of the most supported phones in here. So that does not worry me much. What worries me is that we will lose the path that connects us with such wonderful devs like JustArchi.

And btw it is a 2550 mAh battery not a 2450 mAh one. Sammy may have been testing so long to be confident of trimming down the battery and provide a long-lasting battery life ;)
[Galaxy S III Android Development] FadeFx:
The problem with samsung exynos devices is that they will always keep massive parts of the firmware closed and if we want to get rid of pesky bloated touchwiz we can not, because we dont get aftermarket firmware that works. If we use quallcom equipped devices, we are in a better position.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] whatsgood:
You do make an interesting point, now that the S6 has turned fully exynos, no snapdragon variants, development may be more quick, due to developers all working on one device. True, sticking with the same developers for the 2 years is a difficult thing to move on from. I come on XDA every day to learn and contribute, and the community feeling is very strong, almost like family. It'll be like leaving the family :crying:
[Galaxy S III Android Development] JustArchi:
Buhahaha.

Good luck with exynos development. I'd get slow S810 rather than crappy exynos. Can't you see what is happening in Galaxy S4/S5 sections? Go ahead and take a look.
[Galaxy S III Android Development] HaarisTheBoss:
I can't find anything. But we all got to agree that Samsung made the internals a monster of a phone for the s6.
[Galaxy S III Android Development] JustArchi:
Who cares if they can't deliver proper software to make use of that internals?

Today I was at my university. A professor blamed his Galaxy S5 after last lollipop update that the phone has become unusable, slow and annoying. Sad truth.
[Galaxy S III Android Development] Mostafa Wael:
By the way, what's happening for the GS4/5 is because developers are choosing the easier and open-source friendly Qualcomm variant to work on instead of the exynos one, because they have a choice. But what happened to the N7100 and N7105 ? I don't think they have the problems the S4 and S5 are facing now, because developers have no choice except to work on the exynos thing and make it better.

Moreover, from the looks of it, S810 is not a good chip to over clock or undervolt since it has nasty overheating bug and will make it worse. So I guess that what the Note 2 is having now is almost typical to what the S6 will have after 2 years.

Anyway, let's wait for the official release of the devices and see if the performance issue is fixed on S810 or not.
[Galaxy S III Android Development] JustArchi:
Then you're deeply, deeply wrong.

Developers bought devices like S3 and N2 because they were cool, and we had hope in Samsung.

Now there is no hope, nearly all developers abandoned that devices, including codeworkx and Xplodwild, and without them you would use 4.3 Jelly Bean now.

If you like the S6, go ahead and buy it, but don't expect developers like me to follow you, as I'm not interested in samsung and their ****ty policy, and actually every (ex-)exynos4 developer shares same thoughts.

So, yeah, hope you'll build your own CM from scratch then. Or get used to CrapWiz.
[Galaxy S III Android Development] Nees3:
[MENTION=5161352]JustArchi[/MENTION] do you know what it might be? Guess my post got spammed away by the chipset discussion :)
[Galaxy S III Android Development] JustArchi:
After flashing AK, but before rebooting, copy /tmp/archikernel/ArchiKernel.log to somewhere safe (e.g. to /data), then show it.
[Galaxy S III Android Development] Nees3:
Mmmm, I guess I need do do that with ADB? Btw, could it be the recovery? I'm using Philz Touch (used to it) Just in case before we go further :)
[Galaxy S III Android Development] FadeFx:
You never heard of aroma filemanager?

Edit: [CWM-APP][2.00] AROMA Filemanager + TERMINAL :: 15022810 :: Open Source

Edit2: i use philz (arter97's) recovery as well, so...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] Mostafa Wael:
So what is your choice ? Buy a S810 device ? Or wait till S820 ?

And I am sorry for OT (My last question :o )
[Galaxy S III Android Development] Dark_bolt88:
Hii just archii i wanted to know how the zram works does it use internal sd card for swapping or can we use external sd card for zram use...if yes then how can i use my external sd card for using zram function in your kernel :)
[Galaxy S III Android Development] Moster2:
Zram does not use any external device, just the ram. It provides its own swap device in the ram and swaps compressed pages to it.
[Galaxy S III Android Development] arter97:
Great to know that I'm not the only one here to abandon the S6 completely.

Let's go get a S810 device together. ROFL
[Galaxy S III Android Development] Mostafa Wael:
That is a good choice it seems, but what if the S810 is an overheating chip. I am very convinced to Qualcomm, but this issue just worries me. And I know how it feels to own an Exynos device now after our beloved S3, I will feel lonely :laugh:
[Galaxy S III Android Development] arter97:
Go look at AnandTech, while Exynos may perform better in almost every cases, I don't think S810 is bad either.
[Galaxy S III Android Development] St3ve32:
Yes exactly! And I have also never seen any confirmation of the overheating issue. Even LG said that there is no overheating problem....
[Galaxy S III Android Development] FadeFx:
I also think samsung made bad promotiin for the s810 on purpose just to push the exynos chips.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] Dark_bolt88:
monster thank u for your quick reply it means that zram doesn't harm my internal or external storage like swaping :)
[Galaxy S III Android Development] JustArchi:
Personally I'd wait for S820.

I have a feeling that it'll be much better than S810, especially because Qualcomm has more experience with arm64 architecture now.
[Galaxy S III Android Development] myshakugan:
[MENTION=2446031]FadeFx[/MENTION]

Did you flash the latest test kernel on cm weekly or nightly? I flashed it on 03/04 nightly and getting booted back to recovery. Was on stock kernel before flashing.
[Galaxy S III Android Development] FadeFx:
I never use nightlys... ;)

tapatalked from lollipopped i9300
[Galaxy S III Android Development] myshakugan:
Ah. I guess I'll try weekly 7 then. Thanks.
[Galaxy S III Android Development] Mostafa Wael:
I see. S6 has better benchmarks score because of its UFS memory I think. So in general S810 is good!! And if overheating is dealt with as it is said, then I will totally go for it!! Hope to see you guys later
[Galaxy S III Android Development] whatsgood:
Will it be dealt with though? I just saw an article on PhoneArena showing antutu warning an HTC M9 that the device's temperature is too high whilst running a benchmark. The issue is definitely there, first seen on the G flex 2 and now an M9, and you know what annoys me the most? All other companies' flagships apart from Samsung will have an S810 too. Overheating Sony Z4, LG G4, Oneplus Two etc. Why don't they sort the problem out before resuming production?
[Galaxy S III Android Development] JustArchi:
Because nobody gives them money back for doing so.

The main objective of the company is TO MAKE MONEY, everything else is on the second plan. Phones generate money, skipping overheating CPUs does not.
[Galaxy S III Android Development] ramabg:
I think all of SoC will suffer overheating if used constantly under maximum workload. I do not understand why producer build a SoC to run at certain very high frequency but It only able to sustain for a few minutes. It is a cheap dirty tricks.
[Galaxy S III Android Development] FadeFx:
Exynos cpu uses thermal throotling in case of overheating. Just not with custom kernels as this is not in the open source code afaik.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] RoelD92:
Also, overheating happened primarily with benchmarks. This means that the CPU and GPU go flatout. That will actually never really happen in real life. Even the heaviest games don't ask that much. Because why would they make a game that can only run on the newest processors?

Back on topic, the latest 2.0 kernel performs really well on AD3.1. However I do have the feeling that our runs a little hotter than stock or boeffla kernel. It also seems to drain rather fast when listening to music. Again, faster than on other kernel.

Standby time is really good. At least on par already with what I had on boeffla, and I didn't even tune the governor and stuff yet :D
[Galaxy S III Android Development] whatsgood:
Well, I guess this bad press is going to negatively affect their sales somewhat too, not to mention phone manufacturers' trust in them. I'd think they'd be more reluctant when it comes to using Qualcomm SoC's after this fluff up. And to add to that, getting rejected from a huge company such as Samsung, arguably the biggest contributers to android sales, is a big deal.

---------- Post added at 10:26 PM ---------- Previous post was at 10:14 PM ----------

Watch the pocketnow review of the LG G flex 2 and you will see that this overheating problem does affect real world performance due to throttling lagging the phone up. The difference is noticeable in the UI. That's only a full HD screen though. What happens when it's a 2K screen requiring more fire power from the SoC to push those extra pixels?
[Galaxy S III Android Development] RoelD92:
Hmmm, I guess I should do that then. However, the flex 2 isn't available yet right? Only for preorder. Deliveries are scheduled for next week if I'm not mistaken.

Hopefully, they added some software tweaks between review unit and consumer unit.
[Galaxy S III Android Development] Zwulf:
What's wrong with S805? For what purpose do you really need more atm? If there are problems with S810 just don't buy it. My new phone is a Z3 Compact with S801 and it's fast as hell, even when gaming. My girlfriend has a Note 4 with S805 (told her to not buy the Exynos variant because of the pains I've seen the devs got on S3 with that) - I couldn't tell the difference in speed between my Z3C and her device (opening apps, gaming, overall performance...). I wouldn't worry about overheating as it's Qualcomm's problem, but buy a S805 instead - it's a very good SoC imo. I couldn't imagine only one scenario where you would need a S810 over a S805 because you would really need the power. I guess with normal use and even gaming you would hardly feel any difference in real life (left benchmarks aside) between S805 and S810. It's just marketing that tells you to need the latest SoC because, like Archi already mentioned, it's about making money in first place.

Just my two cents.

Edit:

Guess, I'm wrong. Most people would need it for playing Farcry 4 on their phones... ;D
[Galaxy S III Android Development] EP21:
You do know that a smartphone is an investment and what good is an investment if it serves you less then something that is 6 months newer.
[Galaxy S III Android Development] Zwulf:
So you really want to say that if you buy a smartphone now with not the very latest SoC but one that is half a year old it's completely useless? Seriously, this is absurd. Most people actually USE their phone and don't buy it for trading and reselling and that's what my post is referring to.
[Galaxy S III Android Development] JustArchi:
Buying arm32 phone when arm64 is out is a bit stupid right now.

It's not only the "newer processor", because intel is already releasing 5th gen of i7, and I'm still on the 2nd gen (and it's fast already). The thing is that arm64 architecture benefits from other things than only higher clocks, especially access to 64-bit memory. Potentially it can speedup every task by around 33%, just because processor can parse more data at the same time. I'm not talking about Qualcomm quirks right now, but about arm64 architecture. That's why I'm waiting for S820, hoping that it will be shiny.
[Galaxy S III Android Development] FadeFx:
The thing is not what performance we need now, atm having a top notch phone doesnt make too much sense as nothing will fully use its power. But i want a phone that is still good in 3 years, thats why i bought a top notch phone last time and now after nearly 3 years it is still usable, but i guess it wont last too long anymore.

If someone wants to buy a new device every year, it may be sufficient to buy a medium specs device, but this is not the way i live.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] EP21:
It's absurd only when the technology isn't changing that much. Bought the s3 only because it had removable storage and decent hardware (september 2012). The nexus 4 got open gl 3( if i'm not mistaking the names) when the s3 has only open gl 2. That on it's own is something powerful and as archi mentioned there are more abilities with the newer hardware.

Also [MENTION=5161352]JustArchi[/MENTION] does the last post mean you'll be waiting for s820?

+1
[Galaxy S III Android Development] whatsgood:
I agree 100%. You have to live with your choice for the next 2-3 years, you want to make the best choice of smartphone. In my eyes, last years devices don't cut it, and it looks like this year's devices won't either.
[Galaxy S III Android Development] Zwulf:
I'm not such a good consumer. I'll stick with my Z3C next 2 years. :)

Still using my S3 at home as it has a larger screen and it doesn't matter to me if it is a lot slower than my new device. It does what it should do.
[Galaxy S III Android Development] FadeFx:
The z3c is definitely a good device that will serve you for a while, i bought one for my girlfriend two months ago, as her s2 started to act more and more wired after she dropped it into water and left it there for ten minutes half a year ago. However, now the z3c is yesterday hardware and there is the new generation of chipsets coming up and i would rather buy one of these devices so i dont loose one year due to buying a last year device.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
Another test release for biggest ArchiKernel fans.

1. Don't flash on previous line of ArchiKernels (1.X), or any custom kernel. Flash this on stock kernel [ONLY], or previous 2.0 test version (28 Feb+).

2. If you have 2.0 test version (28 Feb+) already, you should clear Synapse's data prior to flashing to avoid conflicts. You can do so through Settings -> Applications -> All -> Synapse -> Clear data

3. Half of the features are still missing.

4. Works with LP only.

5. This is a test release, expect bugs.

6. This is based on N7100 sources.

Fast changelog:

1. Memory: Misc fixes to hardswap, added option to hardswap also on external sd card

2. Screen: Added TouchWake

3. GPU: Implemented GPU control

4. I/O: Added optional entropy setting

Have fun.
[Galaxy S III Android Development] Nees3:
Anyone using it on TEMASEKs rom? I still cant get it to work. Keeps booting to recovery. JustArchi said to copy the log, but I don't have a clue how.

I have wiped whole phone, clean installed Temasek 8.4, then kernel, tried to boot. Nothing, just goes to recovery.

Using Philz Touch 6.48.4/CWM 6.0.5.0.
[Galaxy S III Android Development] katolink:
Not working on cm12 latest nightly (03.07). Keeps booting into recovery.
[Galaxy S III Android Development] JustArchi:
In addition to test release above, I also provide my personal experimental version for you to test.

This version has nearly whole debugging disabled, turned on advanced memory optimizations (such as zcache, cleancache, frontswap, ksm), and skipped most of the samsung debug error checking.

In general it shouldn't cause any issues, but it's called experimental because various exynos quirks may kick in that samsung patched in dirty way. Especially sleep of deaths. If somebody decides to test this one in longer run, I'd be grateful. However if you need ultimately stable kernel, which will wake you up the next day for work/school, use test release above instead.

Notice: This release is much faster/smoother than test release above, thanks to my tweaks mentioned above.
[Galaxy S III Android Development] FadeFx:
[MENTION=5161352]JustArchi[/MENTION], i seem to have one "problem" with zram implementation. Seems system boots up with zram like configured in configure_zram file, then the bootservice of synapse starts up, has to first swapoff and then swapon with its configured values. Wouldnt it be better if it instead overwrites the configure_zram file with its own config, so system boots up with these settings? Also i can not disable synapse from doing zram settings, that means it will do this on every boot. Also this makes synapse freeze for minutes....

Btw, giving the experimental build a run.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] myshakugan:
Running the experimental build, haven't faced any issue yet. All runs smooth. Will give feedback after some intensive use.
[Galaxy S III Android Development] FadeFx:
Oh, and thanx for touchwake...

tapatalked from lollipopped i9300