yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] voorhees13:
Downloading nameless,let you now asap.

Edit:mobile data works andi ;)

Edit 2:Team ub mobile data doesn't work.
[Galaxy S III Android Development] glockaki:
well seems that we all have to give Lord a big thanks for his efforts!im not in nameless rom but nobody would have done this for us!only Lord Boeflla!THANK YOU!
[Galaxy S III Android Development] ziwy:
Hi,

can you upload somewhere else? It's too slow and it's the 5th it drops the connections.

Thank you in advance.
[Galaxy S III Android Development] fcaronte:
[MENTION=947981]Lord Boeffla[/MENTION] Andi what do you think about the possibility to add the battery temperature near the cpu temperature in your app? Yes without any eta and if it don't take to much work ;) I see that my problem with certain game was the temperature... Is possible? I would the possibility to monitoring cpu + battery temp near

Edit : off topic but today I go to run with my friend (with one plus one) and i see a strange problem... My phone fix the GPS immediately and is wait very long time... Is normal? How fix in your 1+1?i try with GPS status and s3 Se 11/12 GPS and fix 4/5 immediately is phone Sì 30/32 GPS and not fix nothing for minutes and minutes....
[Galaxy S III Android Development] fonfox:
+1

This is Lord Boeffla
[Galaxy S III Android Development] philocritus:
It's working Andi!

Thank you for your extraordanary effort and awesome dedication to us!
[Galaxy S III Android Development] andip71:
Team UB also working here, see screenshot.

So I guess it is fixed. Will enable the kernel asap.

Thanks to all testers

Andi
[Galaxy S III Android Development] andip71:
I will think about the temperature thing.

And about gps on oneplus one: it indeed takes ages to get a first fix. But then it is quite stable and subsequent fixes are quick too.

Andi
[Galaxy S III Android Development] Egli.Kasa:
Any suggestion about sound config ? When listenin music from speakers it sounds scratchy .Any mod or how should i config boeffla sound . Running cm12 beta 6 latest boeffla
[Galaxy S III Android Development] zikozoko:
but the screenshot is for Boeffla 3 alpha 1
[Galaxy S III Android Development] voorhees13:
No problem ;) Wifi was working on ub,but not mobile data,or am i wrong?
[Galaxy S III Android Development] andip71:
Selected wrong screenshot. Grrr.
[Galaxy S III Android Development] andip71:
I never use speaker to listen to music, sorry. So I don't have any comments on that.

By nature the s3 speakers always have problems with strong bass.

Both, see corrected screenshot above pls.
[Galaxy S III Android Development] andip71:
All,

Version 3.0-alpha6a is now online for everyone.

Mobile data issues for a few roms should now be fixed [emoji106]

Enjoy

Andi
[Galaxy S III Android Development] fcaronte:
Do you Concorde with Me that the problem, for me, is that my friend switch off the GPS when he not use it... I always stay all on
[Galaxy S III Android Development] fonfox:
V3.0 alpha6.a works fine to on not affectet temasek/ arter97 cm12
[Galaxy S III Android Development] andip71:
Yes, this indeed makes a difference on the opo.

But back to s3 now, to not talk too much off topic.

Thanks

Andi
[Galaxy S III Android Development] fcaronte:
Ok thank for your time :) now go to a update s3 kernel ;)
[Galaxy S III Android Development] fonfox:
Hey Andy do you never sleep you work now the hole day for us

I mean this is excelent. Big Thanks

You let our S3 life
[Galaxy S III Android Development] andip71:
I do... Now [emoji3]

Good night.
[Galaxy S III Android Development] voorhees13:
Found the problem i had with ub,i had to put the apn settings for mobile data to work,now it works.My bad sorry.

Gonna flash the new kernel on temasek now,thx and have a good night rest.
[Galaxy S III Android Development] Gokulbalram:
To the guy who said COC doesn't work

[YOUTUBE]<iframe width="420" height="315" src="//www.youtube.com/embed/zR7sXZ-OKko" frameborder="0" allowfullscreen></iframe>[/YOUTUBE]

Sorry for the low quality, I figured it'd be more smooth at such low res.
[Galaxy S III Android Development] andip71:
:)

If you had created the file already, you would know as it is shown to you after it.

But of course: support@boeffla-kernel.de

Andi
[Galaxy S III Android Development] Moopow:
@ boeffla... I have checked rom settings and realized that it was not ticked by default... See pic below... I am going tick it and reboot and see if it makes a difference
[Galaxy S III Android Development] GTMoraes:
Andi, I posted this, but I think you didn't see

http://xdaforums.com/showpost.php?p=46730618&postcount=595
[Galaxy S III Android Development] Moopow:
@ boeffla... It's working good now...I have also set 'ignore safety margin' and ignore unstable power ' to on.... Thanks for the consultation :thumbup:
[Galaxy S III Android Development] andip71:
I did see, but what should I say?

First:

Charge monitoring apps are not reflecting reality, as they cannot on the S3. There is no sensor built into the S3 to measure charge current. So all these apps do is interpolating battery voltage changes and try to calculate some virtual charge current. This sometimes works good, sometimes not. So I do not give lots on it.

We know, the stock charger is crap. Many USB cables are crap and cannot handle the currents.

The only way to find out which current is really used is: Switch kernel logger on, start charging, look at dmesg what current is finally being used.

After I replaced stock charger with a proper charger that supplies around 2A without issues, all problems are gone for me. And for many others.

Did you ever try to check the "ignore...." functions? I do not recomment it, as it just works around a hardware problem and this is no real solution in my opinion.

If there were a generic kernel fault with it, many... no, all would report the same issue. Including myself.

So, I am 99,99% sure it is the charger, or the cable.

Especially as the charging logic has not significantly changed compared to stock. Only the fix constants were replaced by variables which can be set in the app.

Andi
[Galaxy S III Android Development] Hbohd:
Just got an idea for your conveniency...

What about adding this post to FAQ or sth similar? And then just pointing users to that post? :p

I saw those questions so many times that it's more sad than funny :(
[Galaxy S III Android Development] andip71:
Hbohd, I think it is even time to put some more FAQs into the section on the homepage, and then... as you said rightly... point from the OP to there.

Hope I will find some time today for it :)

Thanks for the idea.

Andi
[Galaxy S III Android Development] andip71:
By the way, one more thing to add on the charging topic:

Even if you purchased a good charger which can supply stable current, it is not a guarantee it will speed up your charging.

Reason is: Many AC chargers register with the S3 as a USB device - thus, the loading rate configured for USB is being taken.

For this you would need to increase USB loading rate in the app as well to higher values.

The easiest way to find out whether a charger registers as a proper AC charger device or USB:

- enable kernel logger

- plug the charger in

- after 1-2 minutes grab a dmesg (or create a debug info file)

In the dmesg output, it will be shown if an AC or USB charger is being recognized. I intentionally put this information in a while ago.

If you are still in doubt, do the steps I described above and send me the debug info file... then I can let you know about what and why :)

Andi
[Galaxy S III Android Development] GTMoraes:
Hey, just a little heads up.

The end user most of the time is the bugged one. I forgot to short the DATA pins from my custom cable (so the S3 would catch it as a AC Charger). Didn't check the dmesg, but it likely was handling as a common USB port. Sorry about that.

Phone is charged, so at the end of the day, I'll post results.

I'll use the Nexus 7 stock charger and cable, as they're working fine here (and seems to have the specs to hold my charging setting just fine)
[Galaxy S III Android Development] andip71:
Glad my second thought on it was maybe of help, GTMoraes :)

Waiting for your report then...

Andi
[Galaxy S III Android Development] Simonna:
Just installed this ROM 30mins ago and you made a great job, so I wish you to keep going. And thanks for that sound mod on your app, it's really awesome.:thumbup:
[Galaxy S III Android Development] JustArchi:
Andi, I was troubleshooting FCs in my build since yesterday (at least 4+ hours) because I'd never guess that your awesome kernel may be the problem.

Thank you for very fast update.
[Galaxy S III Android Development] andip71:
Thanks Archi.

CM team introduced a new framework as of yesterdays nightly. If this is not contained in the BootPath variable during kernel start, it will FC with the known error message.

So it was easy and fast to fix.

Cheers

Andi
[Galaxy S III Android Development] zerosys:
Your fast dude, just flashed newest Nightly of my Carbon ROM with your beta2a kernel and everything workes fine.

Relating to our little conversation about Galaxy S3 and its memory, i will buy the Nexus 5 as soon as it comes out in Germany, i hope you will be develope kernels for that one too dude.
[Galaxy S III Android Development] andip71:
septigation... hm, well. honestly, it is not too likely.

The Nexus 5 will most probably have the same drawbacks than the Nexus' before:

- no interchangable battery

- no sd card slot

If the N5 had that, it would be a direct by for me.

But so, I might watch out for the S5, as many times said in the past.

Andi
[Galaxy S III Android Development] GTMoraes:
I've heard that the S line won't be the Samsung flagship anymore. It's now the Galaxy J role
[Galaxy S III Android Development] fuxmen:
I waited for N5 too but Now i have S3 with zerolemon 7000mah, and can't stand phone with less batttery juice. And If S5 or J can be suported with zerolemon - like S4 and Note 3, then it will be my next choise to :) then It would be good to see U there Andi!!!
[Galaxy S III Android Development] therightperson_630:
Slight problem, installed latest 10.2 temasek rom (v61) and flashed this kernel (latest beta) over it and I'm getting a "kernel version/busybox issue" when starting up boeffla config. Any ideas of how to get past this or if I'm doing something wrong? Thank you
[Galaxy S III Android Development] tisazalay:
You need to use Boeffla Config V2, for latest beta kernel (2.x)

https://play.google.com/store/apps/details?id=de.andip71.boeffla_config_v2
[Galaxy S III Android Development] therightperson_630:
Thanks, didn't see there was an app just for the beta version, tried following the instructions on the main page ! the real problem was that I kept flashing the old boeffla kernel in temasek's pages, no wonder it wasn't working, it's all good now. Thanks!
[Galaxy S III Android Development] exwan:
Are you still using team UB cm as your daily rom for s3?
[Galaxy S III Android Development] andip71:
I don't have a daily rom on the s3 anymore, as my main phone is the oneplus one now.

But when testing cm12 on the s3, I meanwhile more test on cm12 unofficial by JustArchi.

Andi
[Galaxy S III Android Development] andip71:
Out of curiousity... which app did you use to record the videos?

Well, I indeed do not sleep enough. But yes, I wanted to get this sorted first. Otherwise would have kept me awake the whole night anyways.

As displaying the battery temperature was a 5 minute coding in the app only, I put it already in. Will be contained in next official app update. See screenshot.

Andi
[Galaxy S III Android Development] Gokulbalram:
I used SCR screen recorder for 5+

Lol, it feels like you're online 24/7
[Galaxy S III Android Development] viktor92:
You are a great dev and great person. Thank you for your dedication and commitment to your users :good::good:
[Galaxy S III Android Development] andip71:
Naaa. Not 24/7.

I am usually there around 16 hours per day, yes.

But only Monday-Friday, Saturdays and Sundays I try to avoid kernel work and dedicate the time to my family.

Andi
[Galaxy S III Android Development] Gokulbalram:
Ah. So do you do anything besides taking part in this? :D
[Galaxy S III Android Development] andip71:
Unfortunately... yes. Professional work comes on top. Haha.

Andi
[Galaxy S III Android Development] ste22032:
It seems that Boeffla App doesn't display the correct value of free RAM. This has been reported by a user from an Italian forum, running CM12 Unofficial by Temasek (it should be the same also on CM12 by Archi as the sources are the same) and Boeffla Kernel 3.0 alpha 6 NG. On settings - app the free RAM was about 260 MB, but on Boeffla App only 16 MB, same configuration. Could somebody else check this?
[Galaxy S III Android Development] Doppiadi:
I noticed this too, right now boeffla config is indicating 20MB Free, in Settings instead it's 274MB, quite a difference! Latest CM12 (Archi and Moster )and latest Boeffla kernel.
[Galaxy S III Android Development] andip71:
This is by design.

What the user sees in settings - app, is what the rom sees as free ram.

This has nothing to do with what the kernel sees as free and used ram. Of course, Boeffla-Config shows the kernel view of it.

It will always be different and is normal.

Andi
[Galaxy S III Android Development] shivaagarwal1:
Hi. Screen takes 3-4 seconds to turn in when call comes.. Is this kernel specific thing?
[Galaxy S III Android Development] kadopt:
No.
[Galaxy S III Android Development] andip71:
The next one... :)

If you would not mind, search through this thread, search through the general CM threads.

It is a known issue since CM exists on the S3. And there is no general solution.

But many discussions on that.

You can just try to avoid zRam and any energy-saving things that might slow down your phone in order to make it better. So, no underclocking, use standard pegasusq governor, no undervolting etc. etc.

It is a trade off in the end.

Andi
[Galaxy S III Android Development] fcaronte:
Umh for cm12 I see this problem but I fix changing the right voice in build.prop

ro.telephony.call_ring.delay=0

Put =0 instead or original value.... Try it

If work for you too you can think to add in your various setting of app ;)
[Galaxy S III Android Development] sperelli:
Hi there Lord, first of all thank you for your extraordinary dedication and extremely deep support to even unofficial stuff like this beloved cm12 for us s3 addicted!!

I would like to point out a little problem with ringer when telephone connected via BT to Uconnect car system. The phone ringer starts playing the chosen sound, then at a certain point it jumps forward within the music, then again a few seconds ok, then again sound quickens and jumps fast forward...and so on, untill you answer the call (if you are interested in answering... :) ).. Hope to have reproduced by words in such a manner to convey the right idea of the issue. Archi cm12 b6 and Boeffla ng b6. Any idea?
[Galaxy S III Android Development] andip71:
Tried it quickly. Does not make any difference for me. Still takes a few seconds for the screen to show up.

I generally would not like to mix up rom and kernel settings. build.prop is a configuration file for the rom. So I better leave my fingers away from that in a kernel app.

(the wifi scan interval I implemented in the settings also does not touch this file but dynamically change the value during load, this does not work with the ringer delay).

Honest answer - no idea.

BT is something I never touched in the kernel, and it is always a mix of 50% kernel drivers and 50% rom.

Also many people have issues against very specific equipment while it is working fine with another. I do not have Uconnect car system, so I cannot say anything.

I would suspect it is due to CM12 being not even on official status, BT seems to be a big open topic in CM12 everywhere (also on the OPO...)

Sorry

Andi
[Galaxy S III Android Development] fcaronte:
Yesterday I try and seem to work but probably is only a placebo
[Galaxy S III Android Development] RoelD92:
the idle battery usage on the n7100 rebased kernel is absolutely bonkers!

It used 0% - 1% during the entire night (no airplane mode, wifi on). And that was just on the second batery cycle.

Speedwise, i see no major improvement/decrease over the previous kernels so that's also great.

Also, i think some of the artefacts/glitches are gone indeed. I used to notice a little glitch now and then when opening the app drawer, but all is fine now.

My phone does seem to run a bit hotter during usage (hotter than it previous was during usage), but the kernel might need to settle a bit.
[Galaxy S III Android Development] gazou_hb:
dear boeffla,

thanks for your update of your kernel,

the alpha 6 doesn't works with the data connection.

the alpha 6a works fine with the data connection.
[Galaxy S III Android Development] andip71:
Allright. Does not sound bad.

And in terms of graphics, I think this is currently the best we can achieve.

Thanks for letting me know.

That is the reason why I pulled alpha6 completely from the site, so nobody can download and use it anymore, only alpha6a.
[Galaxy S III Android Development] gazou_hb:
for the tethering is ok.

i use the rom wip Beta 6] [2015-01-10] CyanogenMod 12 for i9300.

I wait the update of temasek's rom
[Galaxy S III Android Development] scorpionhd2:
Hi Andi,

Sorry it took me a while to respond. Work and kids keep me busy. I turned off wifi and then went to recovery and flashed 6a on Validus. It booted fine. Data was working. When the screen went dark, the phone would reboot itself. It would boot back up to lock screen. Data and everything works again until screen off (automatic shut off or manual). Then I turned on wifi and the reboots stopped. Turned off wifi and then the screen. All is fine. Turn off wifi and then I rebooted phone again. Problem returns.

In Short:

If phone is booted with wifi off, it reboots everytime the screen turns off. Once wifi is activated, reboots stop, until rebooted again without wifi, then reboot cycle resumes.

Log:

https://docs.google.com/document/d/10_E2DtZ-gfJPIOUO2GsrfV0rJiZlS-QqqVgTeWuFp7I/edit?usp=sharing

EDIT----

Now data is dead again. SS attached
[Galaxy S III Android Development] RoelD92:
That sounds like a ROM problem. Both Nameless as cm12 by archi had this problem, and it was fixed on the ROM side, not on the kernel
[Galaxy S III Android Development] scorpionhd2:
With alpha5 it's perfect
[Galaxy S III Android Development] RoelD92:
hmmm. strange. Which ROM was it exactly? Could be related to the way they implemented the wifi fix
[Galaxy S III Android Development] scorpionhd2:
Validus by GZROMS
[Galaxy S III Android Development] RoelD92:
Actually never heard of that one. I also can;t seem to find a xda thread for it.

I did find some google+ communities and so on.

Is it based on CM or AOSP? Because i found an announcement from them they were switching to AOSP base?

If it is based on CM, it could also be because they are basing it on true CM12 source rather than on the source by Justarchi, Moster2 and arter.
[Galaxy S III Android Development] andip71:
Well, as said... I see the rom has been built 9 days ago.

This is ages ago, the kernel is much newer.

So yes, might be there are incompatibilities meanwhile.

I mean, it is not normal the kernel runs fine on unofficial CM12, Nameless, Team UB, ... but not on Validus.

But, honestly I cannot say for sure. And unfortunately, but I know you will understand, I cannot (and really do not want) take care of each and every rom around. Too many, just impossible.

I am afraid, until this rom gets updated (hopefully to the good), you need to stick with alpha5.

Sorry

Andi
[Galaxy S III Android Development] scorpionhd2:
Of course I understand ;)

No big deal for me, just thought I would inform.

Besides, hopefully I should be upgrading to Shamu soon :fingers-crossed: and the I9300 will be returned to stock and put in the closet to wait for emergencies ;)
[Galaxy S III Android Development] andip71:
Never put a S3 in the closet. That is a capital sin :)

Andi
[Galaxy S III Android Development] scorpionhd2:
Lol.....done, will stay out on the entertainment center as an homage to the durability and goodness (waiting to jump into action) :cool:
[Galaxy S III Android Development] Gokulbalram:
I can confirm that the new kernel gives me 0 glitches. Maybe a little lag (really little).

N7100 or N80xx?

---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------

Use it as a media player or a cast machine :P
[Galaxy S III Android Development] superchandan007:
[MENTION=947981]Lord Boeffla[/MENTION], ur kernel did a miracle today... We just got our dev back...

Thank you [MENTION=947981]Lord Boeffla[/MENTION] and ur awesome kernel...

Sent by Chandan 007 using resurrection remix
[Galaxy S III Android Development] andip71:
N7100 (route from update14 -> n80xx -> n7100)

You got your dev back? Either I am missing a piece or I am too stupid to understand.

What dev did you get back?

Now I am really curious :)

Andi
[Galaxy S III Android Development] Stevica Smederevac:
RR rom dev wanted to quit . rRom didb't boot but it finally boot but only with your kernel
[Galaxy S III Android Development] andip71:
Ahh.... ok. Wow, there are things in the world :victory:
[Galaxy S III Android Development] Gokulbalram:
I didn't really get it, but I shall not irritate you further with it :P

Just an update Touchwake works :D I had a Galaxy S before on which Touchwake meant a touch would wake the device even if you locked it via the Lock button, hence I was baffled.

One more thing, isn't Zram supposed to be Swap?
[Galaxy S III Android Development] f0xy:
And when family gets too much hide away and have time to yourself :)
[Galaxy S III Android Development] andip71:
It is simple.

The NG kernel is not based on cm smdk4412 code basis, but the first NG kernels were based on Samsung Update14 sources for the s3.

As I own a n8000 and a n8010 (Galaxy Tab 10.1) as well, I worked on a kitkat kernel for it after Samsung released the kitkat sources for the Tab.

And then, when the first Android 4.4.x Samsung ports have been done (Archiport, back-to-n00t), I merged the n8000 kitkat kernel code into my existing Samsung kernels to make them work better with these ports.

And 3 days ago, I started to base the CM12 NG kernel not on Update14 anymore, but took my Samsung kernel or these ported roms as a basis, which is then update14+merged n8000 kernel code.

Finally, I then merged the changes of the newer n7100 kitkat kernel code to the n8000 kitkat kernel code into the kernel. And voila, alpha6 was born.

Thats why I say, the base was update14, then I merged n8000 kk kernel (as it was already there due to my Tab kernels), finally I rounded it up with the n7100 update.

Not saying that is in any way a simple task to do, it requires lots of conflict resultion and thinking work. And has a risk of introducing new bugs + it requires some changes afterwards to work properly with CM roms again.

Hope this story made it more clear now.

And yes: Touch wake works, I told you before, hehe. And I think I specifically mentioned I intentionally have the power button disabling it, so people can lock the phone with the power button when they put it into a pocket etc.

zRam and swap are two different things.

Swap is a virtual memory extension to the memory the kernel can use. Swap is usually created on a swap partition or in a swap file. What partition or file you use is up to you: can be a physical device like sd memory, harddisks, etc. But can also be a compressed partition mirrored into the device memory.

And this is how zram works:

There are 1-4 compressed memory partitions created in the phones memory (so it does not wear your emmc sd storage), these partitions serve to create swap devices on them.

Andi
[Galaxy S III Android Development] shivaagarwal1:
I am facing random reboots with the latest 6a, anyone else?
[Galaxy S III Android Development] fonfox:
No nothing like this al run's great. cm12 arter97/temasek what is your Rom?
[Galaxy S III Android Development] rp158:
No reboots /FCs /freezes in NameLess. Thank you, Andi.
[Galaxy S III Android Development] cKenny:
nope, it works fine on my phone, try to wipe cache and dalvik?