yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] sreinst1:
Thanks for the info. Any idea how I can check what goes wrong? The logcat doesn't seem to show anything special. I do see the small dialog at the bottom, with the default icon for the caller picture, but that's about it; other than that icon, the dialog is blank. And while the dialog is on the screen, the phone does not respond to anything - no touch and no hardware buttons. I hope I won't need to actually debug the code to get it working...

EDIT: I GOT IT!!! Finally, the mystery is solved. The problem is with the resources of the dialer... I use Hebrew as language. When I switch to English, it works fine... And provided that I had this problem with all CM-based ROMs, the missing resources are in CM, not just in Carbon. Thanks guys!

EDIT: Jokes on me... tried to report this in CM, but it's not in CM... it's an OMNI feature :)
[Galaxy S II Android Development] Karpfenhai:
Thx in advance mate [emoji2]

"Mein Paul" is simply my son....10 years btw...

Yes, I'm freaking old...

He owns of course a carbonated SIII mini, which also has non intrusive call feature working, but the guy above solved the mystery on it's own already [emoji14].

Tapatalked from my Galaxy SII
[Galaxy S II Android Development] sreinst1:
Well, I solved the mystery, but I can't fix it on my own. I hope Carbon devs will fix it (and even better, forward this to Omni to fix since it's their own bug I believe).

---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------

Are you referring to JustArchi's optimizations? That sounds impressive. Does this require some manual work, or is it a simple Git merge?

I am going to try and build Carbon myself, for the following reasons:

1. Fix the problem with the non-intrusive call in Hebrew.

2. Replace the CWM with a swipe-enabled one from CM.

I might as well try the optimization too, if it's not too complex.
[Galaxy S II Android Development] Karpfenhai:
Afaik omni has a bugtracker, all why don't you submit it by yourself?

What happens if you set your dpi to 200 for a test, does it persist?

Tapatalked from my Galaxy SII
[Galaxy S II Android Development] sreinst1:
Well, just checked their JIRA, and it seems that it's already fixed in Omni (for a few months now).

So, it's only a matter of Carbon team merging their fix.

Haven't tried to change dpi. But I guess now I have all the info I need. Thanks.

Edit: I was mistaken. This was fixed in Omni just about 10 days ago.
[Galaxy S II Android Development] Myself5:
[MENTION=5630829]sreinst1[/MENTION] You need these 4 commits:

https://review.carbonrom.org/#/c/11/

https://review.carbonrom.org/#/c/165/

https://review.carbonrom.org/#/c/341/

https://review.carbonrom.org/#/c/12/

But building does not work ATM as caused by the 4.4.3 update which are not completely merged to our source yet (That's why there were no Nightlys today too)

Tell me when you build it with swipe support, and also how you did it, I'm interested in the way you did this.

[MENTION=4355376]Karpfenhai[/MENTION]: Hum, I'm only 6 years older than your son lol.
[Galaxy S II Android Development] sreinst1:
Ok, I will wait with the build. I can tell you how I did it in the other 2 ROMs: After getting the source tree (with repo sync), I also got the source tree of CM-11, and copied device/samsung, vendor/samsung and the kernel from the CM-11 source tree to the ROM's source tree. That's about it - this gave me the kernel and recovery that CM-11 uses for the device (i9100).

.. And BTW, if you're just interested in trying out the optimizations, you don't have to build the latest version from Git, you can take yesterday's version for example.
[Galaxy S II Android Development] Myself5:
The i9100 device tree for Carbon is based on CM11 ones. I always keep it up-to-date with Omni as also with CM as also adding my own commits. I would know if there were a commit for this touch recovery on CM tree, there was not.

Your suggestion about that optimization testing stuff is obsolete because I know that it works. The build I'm currently running and which I'm writing from is it. It's just some days old and so I wanted to build a new one on 4.4.3 base instead of Uploading the old one from my phone here ;) Still thanks for the tip.

Greetings

Myself5
[Galaxy S II Android Development] cdaarif:
Bug report in 3-6-14 build

1. Mobile network I prefer 3g( H) bt sometimes network go to 2g ( E).

2. Autorotation isn't work

3. After mobile hang n reboot wallpaper go to default

4. When delta updates in recovery after update shows installation abroad robots logo n reboot system. No auto catch or delvic wiped like omni.

5. Battery life is too worth. In half n hours I got 100% to 94% so go to dori kernel10.112

Omni go to marge 4.4.3 next nightly+ update twrp 2.7.1.0 for open delta. http://omni.cmxlog.com/4.4/i9100/
[Galaxy S II Android Development] Gigahawk:
OTG?

As far as I can tell, USB OTG isn't working, using USB Host Diagnostics shows that the kernel supports it, but it doesn't detect both my OTG drive or my wireless mouse plugged into an OTG cable. Does anyone else have the same issue?
[Galaxy S II Android Development] sreinst1:
We have a misunderstanding. It's a fact that I had touch recovery when I just copied vendor, device, and kernel from the CM 11 tree to the ROMs I built for the i9100 (AOSB and Beanstalk). And I've always been told that on the i9100, it's the kernel that contains the recovery, so that touch recovery must have come from the CM 11 kernel. If your *kernel* for Carbon ROM is up to date with CM's kernel (the rest of the source tree is irrelevant for this), then you should have a recovery that is touch enabled, too.

*** NOTE, this touch-enabled recovery is not like TWRP. It is almost the same as the non-touch CWM - the only visible difference from the non-touch CWM is that there's a line on the screen that says something like (I don't remember the precise text): "Swipe up or down to move between items; swipe left to go back, or right to select". I didn't even notice that line on the screen during the first 1-2 months. Everything else is exactly the same as the non-touch version, and the only touch supported are these swipes. It doesn't support touching an item to select it. Maybe you have a swipe-enabled recovery but haven't noticed?

I didn't suggest anything... I was really interested to see how much this optimization improves the ROM, it's the first time I hear about it, and I thought you wanted to build with this optimization for the first time.

Is there a noticeable difference in speed? What about battery life? I'd expect an improved battery life if tasks are completed in shorter time (so the cpu can sleep more).

Finally, is there a down side to this optimization? If not, I suggest to ask Carbon devs (are you one of them?) to put this optimization into their code, so the nightlies will include it.

Thanks!

---------- Post added at 04:50 AM ---------- Previous post was at 04:46 AM ----------

3-6-14 build, are you referring to the official Carbon nightly? In the 3-6-14 official nightly, auto-rotation works fine.
[Galaxy S II Android Development] cdaarif:
Ya officially 2-6.14 to delta update 3.6.14 n after clear catch n delvic autorotation works f9 ;)

---------- Post added at 09:06 AM ---------- Previous post was at 09:03 AM ----------

Im out side. I'll report diz issue later. Anyone else?
[Galaxy S II Android Development] Myself5:
Well, the recovery is build outside of the kernel and gets buils in it later, so it should be no matter that we use OmniRom's kernel but maybe the set the TARGET_RECOVERY flag somewhere in the kernel directory and use their CM recovery (new since the One+One) I am part of the Carbon team and already suggested this. The downside is that said modifications do not work with every device (some of our moto's break terrible when compiling for example) so I need to get it activated per device and we need to do lots of tests. I currently wait till the sea calms down a bit cause we are busy updating our source to 4.4.3 (only 6 repos left :) (sadly some big ones lol)) For the battery part: I'm not sure about it, on my experience the batterie lifetime gets a bit worse but it also could be cause by some of the apps I have installed or by a old battery.

Don't have a OTG cable so I can't test it.
[Galaxy S II Android Development] sreinst1:
Thanks for all the info! Carbon team seems to provide great support, also in the G+ page. However, I have one request; I wrote it on the G+ page to, but haven't received a final answer (maybe I should assume it will be done): Please make sure to merge the fix from Omni for RTL support in the dialer's "non-intrusive incoming call" option: https://gerrit.omnirom.org/#/c/7668/

I've been waiting a long time for this fix, it didn't work in any of the ROM's I've used, and I'd very much like to have this feature working.
[Galaxy S II Android Development] sreinst1:
BTW... what's the difference between the Omni kernel for i9100 and the CM kernel? Do they use different base kernels, or just different versions of the same kernel?
[Galaxy S II Android Development] Myself5:
Basically their kernel is both based on the stock sammy one, they just applyed their own patches to it. (as far as I know but I'm not a kernel dev).
[Galaxy S II Android Development] sreinst1:
Well, I finally have the whole Carbon tree, so I compared the kernel source code with that in CM-11. Turns out it's the same kernel, except that Carbon has a somewhat newer version. There's some more code in the Carbon kernel than in CM-11. The copyright in CM-11 says 2012, and in Carbon it's 2012-2013. It seems like the Carbon kernel supports more devices.

That said, I will try to see what triggers the swipe-enabled CWM in CM-11. I think most users would benefit from having a swipe-enabled CWM vs. the current one.

TWRP may be more user-friendly, but its display looks awful on i9100 (unless they fixed it) - i.e. the labels are somewhat messed up, as if it was written by first time programmers (I know it's not like that). I'd rather have the fine-looking swipe-enabled CWM than the ugly-looking user-friendly TWRP.
[Galaxy S II Android Development] sreinst1:
No sound (music and movies)

There's no sound in my phone for music and movies. Notifications and ringtones work fine.

The slider of the music volume seems disabled, can't move it.

Edit: Went back to nightly of 2/6 (I was on 3/6), and now sound works fine. Glad I didn't have to ditch Carbon for another ROM, as it's my favorite.
[Galaxy S II Android Development] Karpfenhai:
[MENTION=3816568]Myself5[/MENTION], any particular reason, why we still stick with 4.4.2 while almost any Rom else already has a working 4.4.3 iteration?

I'm just curious, don't see issues on git.

And btw, your g+ link isn't working anymore [emoji2]

Regards

Tapatalked from my Galaxy SII
[Galaxy S II Android Development] Myself5:
[MENTION=298569]sreins[/MENTION]1 I hope that issue is fixed on the next upcoming nightly (either 7 or 8 of June), also your ordered fix for this call thingy is up on our gerrit, we just need to test it and we will merge it.

[MENTION=4355376]Karpfenhai[/MENTION]: It's not that easy to update everything to 4.4.3 as we also currently have 2 devs working on it it takes its time ;) I'm currently compiling a testbuild, if this one works we just need to patch 2 repos and we are fully 4.4.3 (external/skia and the Dialer to have its new features)
[Galaxy S II Android Development] Karpfenhai:
Thx mate for the info, from a cm11 point of view 4.4.3 works flawless with -O3 flags ;D

Take your time.

Tapatalked from my Galaxy SII
[Galaxy S II Android Development] lovegurulavdev:
Heymate can u tellme what is gastavo kernel ?? And found where link please and its battery friendly ??
[Galaxy S II Android Development] Opuske:
The kernel that is included in this rom is awesome for battery life.

I did not find any other kernel that performed this good on my phone.......maybe on other phones its different but for me the included one is awesome.
[Galaxy S II Android Development] scorpion.hbs:
iwant BLN

---------- Post added at 10:59 PM ---------- Previous post was at 10:54 PM ----------

this is the kernel for kitkat roms.

and this is link:

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

i test it with omni rom and battery life is amazing
[Galaxy S II Android Development] metalgearhathaway:
You want Apolo Kernel.

It is pretty much stock based, with more choice of govenors and of course bln! It is even more battery friendly that stock kernel, always best left on its default settings for 100% stability and battery performance. I get almost 4 hour screen time in a 24 hour period, the phone will also last 48 hours with about 3 hours screen time used across the days. Bluetooth power usage is minimal!

XDA page: http://xdaforums.com/showthread.php?t=2291756

Download page for compatible kernels for this rom (Please only use light version, all others undervolt and in my opinion cause instability!): https://www.wuala.com/pedestre/Prue...d 4.4)/BETA2/BETA2 OMNI TWRP?key=sOgZD3lrpfq2

---------- Post added at 08:38 PM ---------- Previous post was at 08:31 PM ----------

@CarbonDev Is there an issue with the main website? Over subscribed or the files showing up prior to upload completing?
[Galaxy S II Android Development] nitrounit:
i really like apolo and been using it for a while but on kitkat roms im absolutely unable to make bln work (it works only in the apolo configurator test)

and as you can guess bln doesent work for me on carbon rom and it bothers me, maybe you know a fix? i wasnt able to get a good answer in the main kernel thread there:confused:
[Galaxy S II Android Development] metalgearhathaway:
Use root explorer, delete the apolo folder in sys on device memory, run the memory wipe as well in recovery and reflash apolo and then use configurator :) You could always settle for non blnww and go for regular bln, chances are you don't save all that much battery anyway!
[Galaxy S II Android Development] saskrider:
Is carbon updates being maintained consistently?.I am currently on 2\15 build and again carbon updates show no new updates!!,yet the newest one is today!
[Galaxy S II Android Development] Myself5:
Carbon Update (CarbonDelta called correctly :p) is not working yet. Our server died on us and at the moment it's really important to set up the rest before CD. However, the most is done, it should not take much longer by now (i guess in one week you already use it).

Greetings

Myself5
[Galaxy S II Android Development] aceian:
Sending files from internal to external memory doesn't seems to work.. Anyone else having this problem?
[Galaxy S II Android Development] metalgearhathaway:
Donwload links for latest nightly now working! :good:
[Galaxy S II Android Development] nitrounit:
you mean the "Apolo" folder in root>system right?

and what wipe is it exactly in recovery? not sure what you mean

thanks
[Galaxy S II Android Development] AndyCosmos:
Wow thank you for the nice ROM , I finally installed it and run well so far, anyway I was wondering if there's a kernel that supports dt2w for this ROM for our s2 ?
[Galaxy S II Android Development] Apocalypse Now:
Doesn't this rom need google apps? is it included inside the rom zip file or what?
[Galaxy S II Android Development] Opuske:
Its not included u need to download a GAPPS package.

I suggest the PA mini GAPPS cause they work perfectly and are not to big.

Do not use the bigger GAPPS packages as there is not enough room for it.
[Galaxy S II Android Development] metalgearhathaway:
nightlie 19022014 is up people!
[Galaxy S II Android Development] Apocalypse Now:
Could you plz give me the link? or at least tell me where can I find it? tnx.
[Galaxy S II Android Development] Opuske:
Here u go :)

http://goo.im/devs/paranoidandroid/roms/gapps-mini
[Galaxy S II Android Development] metalgearhathaway:
Better still use yourzgapps, so small and has the essentials you need!

http://d-h.st/Ate
[Galaxy S II Android Development] Visual Focus:
Is the external Microsd card recognized properly ?

In the last build that I attempted to run while using solid explorer to browse my files I couldn't access the external sd card.

Also when I chose to move an app to the microSD card instead of moving to the internal memory it moved to the external one.

Any similar experience ?
[Galaxy S II Android Development] Opuske:
I do not seem to have any problems with the MicroSD that i put in.

Works good and i can move files around from one to the other and the other way around also.
[Galaxy S II Android Development] sreinst1:
[MENTION=3816568]Myself5[/MENTION]: My brain keeps lagging behind... as I'm slowly learning the topic. Are you the one providing the official nightlies (available on the Carbon ROM website) for our device (i9100)? And have these nightlies (at least the recent ones) been built with JustArchi's optimizations? (in which case, that's what I have on my phone right now, but I didn't realize).
[Galaxy S II Android Development] Myself5:
I dont compile them on my local rig and upload them to out website if thats what you mean. We have some of our rigs connected together using jenkins and compile all our Nightlys on them. (My pc is not in it as it is connected using wifi which would somehow screw up jenkins). These JustArchi script optimizations we talk about are some currently unmerged commits on our code review I cherrypicked and build with for some testing purpose.
[Galaxy S II Android Development] sreinst1:
Thanks for the reply. I'd find it strange to be using the optimizations without knowing - that would mean that the optimizations don't change the user experience at all... :) Thanks for clarifying that.

---------- Post added at 10:03 AM ---------- Previous post was at 09:41 AM ----------

There are a few pages on the Carbon ROM website that are broken, in particular the "The Team" page, and the GitHub link to the ChangeLog.

Fortunately, to whoever interested, the team can be found in the ROM, in "About phone" -> "About Carbon" -> Pressing the "C" icon at the top left.
[Galaxy S II Android Development] Myself5:
As these optimizations are not used atm, it's clear that you can't feel a difference. You'll see a difference as soon as I upload my next test build :P (You can find the link in this thread then).

Oh and BTW: I shall tell you from BionicBeast (Our awesome PR guy) that the Team page is working fine again.
[Galaxy S II Android Development] sreinst1:
Are these optimizations included in the SaberMod toolchain, which is used to build SlimSaber for i9100? I once tried it, it was fast but didn't notice any significant change from the other ROMs.
[Galaxy S II Android Development] Myself5:
No, JustArchi Optimizations are flags telling the SaberMod toolchain how to compile. For the toolchains: Duude, check the 4th post of this thread...
[Galaxy S II Android Development] sreinst1:
How many times do I have to repeat this *to myself*: RTFM! :)

But seriously, who looks this deep into the first posts of the thread...
[Galaxy S II Android Development] sreinst1:
[MENTION=3816568]Myself5[/MENTION]: Do you perform some minimal testing on the i9100 nightlies before they are published? (I'm referring specifically to the nightly builds, not to the optimized test versions you create).

Soon enough, 4.4.3 will probably be out. And as a version with many changes, it should probably be tested before everyone downloads it to their phones. Most likely, some users will download it the moment it becomes available.
[Galaxy S II Android Development] Myself5:
Trust me, we do our tests. Currently I can spoiler only one thing: 4.4.3 WITHOUT JustArchi Opt. has the same performace as 4.4.2 WITH JustArchi Opt.

Only 1 repo to go (Dialer) so we plan on publishing 4.4.3 Nightlys tomorrow.

Silas is a good friend of mine who let's me use his server for compiling (as also for Jenkins btw) when I am to lazy to boot into Mint on my rig.
[Galaxy S II Android Development] sreinst1:
Very nice, and surprising. I didn't know 4.4.3 was meant to be a performance enhancer...
[Galaxy S II Android Development] sreinst1:
The reason I asked about testing is that in the 3/6 nightly (the most recent one available currently), there was no sound when playing music (or videos). The volume window has 4 sliders, with the topmost one controlling the volume of music - and that one was at 0 and was disabled; the other 3 worked fine, but the topmost one could not be moved. I almost moved to another ROM because of that. Fortunately, the build from the 2/6 was okay so I went back to it.
[Galaxy S II Android Development] Myself5:
Sound's working fine, also on testbuild 2 I just flashed.

[MENTION=5630829]sreinst1[/MENTION] These 2 commits are just for you :P :

https://review.carbonrom.org/#/c/494/

https://review.carbonrom.org/#/c/500/

Nightlys will come tommorrow hopefully. Our code was ready this morning already but a upstream change of cm screwed us up.
[Galaxy S II Android Development] attack11:
Great! Im waiting for the new release and the improvements that 4.4.3 have!

Also saw that PA release a stable HOVER do you know if they are plaining to release that sources so every ROM can have it?

I saw a test build un your site ! but is for a LG device.. Hope to see one for us too! Anyway Awesome Work Dev, Im glad that se have you as manteiner!

And [MENTION=5630829]sreinst1[/MENTION] Im on latest build and dont have any problems!
[Galaxy S II Android Development] Myself5:
Dunno about PAs plans to make Hover OpenSource. I think we just need to wait patiently :P

Yeah, the vs980 build was made for a carbonteammember as he had no time to build lol.

For the JustArchi Optimizations stuff. 4.4.3 without his Optimizations has the same performance as 4.4.2 WITH them. However 4.4.3 WITH them somehow has the same performance as 4.4.2 without them. So 4.4.3 without has better performance than with JustArchi's build optimizations. So, theres no need to do some unofficial builds anymore lol.

Oh and [MENTION=5630829]sreinst1[/MENTION]:

Make it 3 commits just for you:

https://review.carbonrom.org/#/c/447/
[Galaxy S II Android Development] sreinst1:
Thanks! What do you mean by "3 commits"?
[Galaxy S II Android Development] Myself5:
Commit Nr:

1: https://review.carbonrom.org/#/c/447/

2: https://review.carbonrom.org/#/c/494/

3: https://review.carbonrom.org/#/c/500/

All done because of requests/bugreports from you side ;)

BTW: the thanks button is there for a reason :PPP
[Galaxy S II Android Development] sreinst1:
The thanks button goes unnoticed frequently - and I guess not only by me.

So, besides the thanks button - BIG THANKS! And I hope for some more of these commits (and even more, maybe I'll be able to push some of these for your review and merge into the ROM).

How is the battery on 4.4.3? I temporarily switched to another ROM to try 4.4.3, and the battery is much worse than any ROM I've ever installed. It loses 1% in every 5-10 minutes, with the same settings and apps as I usually use (and I should add, when most of the time the phone is put aside and the screen is off).
[Galaxy S II Android Development] Myself5:
I think that it got a bit worse, but if I were you I would not trust my battery lifetime results as I have only 2 Stock sammy batteries, both under heavy usage since 2 years so I don't know if their lifetime is really reliable. I look foward to see you commits on gerrit :P
[Galaxy S II Android Development] sreinst1:
Well, I guess I better wait for others to comment about the battery life. What's strange is, many users have posted that their battery with my temporary ROM is great. I don't experience the same thing, unfortunately. My battery's not new either (1.5 years, not heavy usage though), but I wouldn't expect it to suddenly drop in performance.
[Galaxy S II Android Development] FPSUsername:
[MENTION=3816568]Myself5[/MENTION] I get a status 0 when I try to install "CARBON-KK-Myself5-20140607-1906-vs980.zip" from myself5.tk
[Galaxy S II Android Development] Karpfenhai:
[MENTION=3816568]Myself5[/MENTION], it can be used on i9100 right? Going to test tonight and will report on battery tomorrow then, is it plain carbon or fully -o3?

Thx for sharing anyway [emoji106]

Tapatalked from my Galaxy SII