yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] titanic_fanatic:
If your able to pull a logcat it would be awesome since I can't get this to happen on my device.

Open terminal, then su and then

logcat -v long > /sdcard/camlog.txt

This will start the logcat recording to camlog.txt on your sdcard. Do not close the terminal, instead hit your home button to let it continue to record then cause the camera bug. After phone reboots, post the log here or email it to titanic.fanatic.xda@gmail.com.
[Galaxy S II General] fozax:
jnj

yes no bisi bilmiyore
[Galaxy S II General] RukusX7:
Found this link about Skyrocket battery life.

[HOW TO] Fix Your Skyrocket's Battery Life

It was really helpful for me, and especially relevant if you are running the custom kernel, where you can enable FAST CHARGE (AC). Which is awesome, and you will see again on new kernels soon I imagine. ;)

Its a good read! enjoy!
[Galaxy S II General] Tronith:
I'm enjoying carbon. It runs well. Great job!
[Galaxy S II General] omar.kassam97:
Im currently running CM11 but want to switch to carbon, is there a new update thats going to be released soon or should I flash the one in the post right now?
[Galaxy S II General] titanic_fanatic:
You should wait, I'm uploading a new build in an hour ;)
[Galaxy S II General] titanic_fanatic:
New Build is Up!

New build is up. It includes Slim Recents, omniswitch (app in app drawer) and the omni performance settings now replace the old performance settings which has a slide out menu to access customized controls for all sorts of things ;)

Download

As usual, take your nandroid before flashing and enjoy ;)
[Galaxy S II General] manfromgta:
Flashed latest release. I was having display flicker, black screen and random reboots until I disabled hw overlays. Now its running smooth. I will enable overlays and try to grab a logcat later. Thanks for all your effort. :)

Edit: flicker and black screen are still present with hw overlays disabled.

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] big_biso:
Thanks TF. Do I attempt to switch on ART or it is not fixed.

it seems most of the issues still exist. one thing that is resolved is the pocket mode, it seems they added new tab in carbon fiber that have pocket mode and I unchecked it and it seems this one works. they one in Active display does not matter.

I also noticed that the screen navigation and pull down notification is much slower than the previous build

(Update1: seem the phone is responsive as usual after few minutes)

(Update2: the long press key is also fixed. but it seems the menu button long press programming in lock screen is still not working. Home button work though!!)
[Galaxy S II General] formercontra:
Loving the omni performance menu, now I only need my other kernel apps for advanced governor/io settings and editing sysctl. Really nice to have it all together in one menu, & everything else is running great so far
[Galaxy S II General] RukusX7:
Real nice work! Lots of new features. Dirty flashed over my own carbon build. Lost init.d folder. And hardware overlay glitches are present with this build. I must click to disable each boot
[Galaxy S II General] omar.kassam97:
The new update ran great at first but then I had to reboot and I was not able to pull down the status bar, the home key did not work at all, and the haptic feedback was gone. I rebooted multiple times after that and it remained the same.
[Galaxy S II General] big_biso:
i am having the same issues with the latest build. also couple of system crashes (system reboot from carbon logo not from samsung logo). i am getting more screen flickers than usual specialy when typing message in keyboard . then i get black screen for few seconds as if the launcher crashed and restarted
[Galaxy S II General] titanic_fanatic:
Well this is disappointing, some change since last build has screwed up the hw overlays again. Good news is that I think we might be on media-caf in about a week. I read that in the review system today.

Omar, is there any way for you to pull a log for me if it's still happening? Maybe try wiping dalvik.

There were many changes to the build this time. Many options were enabled that were not enabled before such as qcom bsp and qcom bionic optimizations. This may have been what caused this glitching.

More good news, xda senior developer Sultanxda, seems to know a lot about this kernel and is working on a fix for this very issue. He's already increased the available physical ram for the skyrocket by almost 100mb I think (my memory eludes me at the moment). This is something I'm looking into as more physical ram is awesome.
[Galaxy S II General] titanic_fanatic:
I think I might suggest going back to the last build for now. The changes to come over the next week may fix some of this.
[Galaxy S II General] RukusX7:
I second all these quirks
[Galaxy S II General] RukusX7:
I might suggest a "milestone " carbon build before moving onto these major changes. Might be helpful to less experienced users or new users who want to try carbon. This being said, when the issues are all ironed out... And I know u hope next week, but what I've learnt from building android is that you eventually learn to live with at least one or two bugs. Lol. We just try to minimize them ;)
[Galaxy S II General] Arodg25:
TF, I just sent you a log cat on Google+ for a freeze and reboot. I've never shared a file on Google+ before,so I hope it works.
[Galaxy S II General] titanic_fanatic:
I have to tell everyone cause I'm very excited. I have our kernel running with 803MB of physical ram. This is up 70MB from 733MB. This is excellent news, although the glitching is still happening.

This is all thanks to xda senior developer [MENTION=4800121]Sultanxda[/MENTION] who is a talented 17 yr old developer ;)

Check out the screenshot of my ram.
[Galaxy S II General] Sultanxda:
Ouch, Samsung screwed you guys over :p To achieve the full 870MB of RAM I have on the Skyrocket, you need to move the kernel's start address from 0x48000000 to 0x40400000 (which will give 50MB of RAM, assuming there isn't anything already mapped to those areas), and disable kernel debugging & debug fs. Assuming your heap sizes are the same as mine, you should get around 870MB of RAM after that.
[Galaxy S II General] titanic_fanatic:
I was wondering about that. I know that we no longer use pmem, so I'm guessing I can turn off CONFIG_REBASE_FOR_PMEM_OPTIMIZATION, and I'm assuming that I can move the kernel's start address so I'll give that a try. Thanks for the tip.

On the issue of the graphical glitching, do you think that cm review #54635 (Marked as abandoned) might be related?

EDIT: I just noticed you back ported the new ion drivers. I'll build with your changes tonight and test. I'll know for sure if it made any difference since I'm having to disable hw overlays or the glitching causes a reboot. I'll let you know how it goes ;)
[Galaxy S II General] big_biso:
Could the glitches be related to the OMNIswitch? Since yesterday morning I turned it off, so I am getting much less problems. I got one freeze in FB that FCed. the screen still flickers from time to time but not as much as before when it was flickering when typing anything in keyboard.

Update: spoke too soon. phone just froze on drop down notification.
[Galaxy S II General] RukusX7:
This. This is what perplexed me about the custom diablo kernel I was working on. The kernels start address! This has something to do with the camera too right? Thanks for all the great work. You and titanic_fanatic are achieving everything I hoped to but didn't understand or have the time for! Really appreciated!

---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------

Every time I'd move the start address and copycat as much as i understood about the skyrocket to our celoxhd, I'd end up with a rom that couldn't get past the kernel splash screen. (Samsung,logo).
[Galaxy S II General] Sultanxda:
Boot.img needs to be rebuilt with the altered base address (--base 0x40400000), so the ramdisk can load properly.
[Galaxy S II General] Sultanxda:
The glitches are not related to upstream in any way, as I have no glitches on my HTC Sensation (MSM8660). Also, the issue you pointed out was in the media HAL, which does not affect display in any way. Glitches are either being caused by our old Ion drivers or by the framebuffer drivers. I tried backporting newer framebuffer drivers but I wasn't successful; however, I was using these framebuffer drivers for weeks on a different device with no issues, so I don't think that's the problem either. Personally, I think it's being caused by the old Ion drivers (or by the combination of old Ion drivers with display-caf). If you are getting the glitches very often, then could you test a patch in display-caf for me?

Apply this patch to display-caf and see what happens: https://github.com/sultanxda/androi...mmit/eb49e021f8f894350f22fc8e79ff0a1fe31c0dfd
[Galaxy S II General] titanic_fanatic:
I'll definitely test this for you. I'm just building right now and should have the results in about an hour ;) Thanks for the help!

EDIT: Sadly, this patch to gralloc did not make any difference :(
[Galaxy S II General] Sultanxda:
Darn :( In that case, have you tested the new Ion drivers?

I originally thought these glitches were isolated only to my kernel; it's nice to know that I didn't cause them with all of my kernel changes :p
[Galaxy S II General] titanic_fanatic:
I haven't tested the new ion drivers yet, I was working through build errors from the new commits that didn't apply cleanly in my repo when I got your last message about gralloc so I went back to my original kernel and built with the gralloc changes.

Were the two supposed to be used together? If so, it will take a little longer to test as I have to work or the build errors first ;)
[Galaxy S II General] Sultanxda:
No, the gralloc patch was made for old Ion drivers. I used it to get PMEM camera working with old Ion drivers in the kernel.

If the new Ion drivers solve the issue then we're going to have to fix the camera HAL to work with the new Ion drivers, which is going to be very hard and frustrating (assuming we're lucky and CAF's open-source camera HAL works).
[Galaxy S II General] titanic_fanatic:
So I finally worked through all the build errors with vidc and will test tomorrow since it's time for me to go to bed ;)

Will let you know how it goes.
[Galaxy S II General] big_biso:
HI TF, you might want to add BLN to the list of broken things with the latest build. For me since this build none of my notification light up even that it is selected in the setup menu
[Galaxy S II General] formercontra:
As long as I've got the options checked in Performance, Display and Advanced I get bln just fine.
[Galaxy S II General] RukusX7:
I'm finding too many places to go to enable backlight notifications....

---------- Post added at 08:59 AM ---------- Previous post was at 08:53 AM ----------

I'm hoping we can merge some features of the diablo/uber kernel. I'd love to see more options available in all ROMs. Build a one size fits all perhaps. Optimize for stability.
[Galaxy S II General] titanic_fanatic:
[MENTION=4800121]Sultanxda[/MENTION], I tested the new drivers this morning, but I get to the lockscreen and everything is locked up then the kernel panics and reboots. I was able to pull a last_kmsg and it's littered with stack traces and errors. Would you mind having a look as I'm not sure where to go from here ;)

SGH-I757M last_kmsg - NEW ION DRIVERS
[Galaxy S II General] Sultanxda:
Revert your compile error fixes in the GPU (kgsl) drivers. Next, grep the GPU drivers for KGSL_COMPAT. Remove all instances of the KGSL_COMPAT flag except for those involving regulator_name and pm_qos. If done correctly then there should be no compile errors in the GPU drivers, and your phone won't crash at the lockscreen.

I made these changes to the GPU drivers in my new-Ion commit. You can use that as a reference for the changes that you need to make.
[Galaxy S II General] RukusX7:
Cl3kener pushed some commits to the diablo kernel in the Hellybean repo in case anyone is/isn't following. This means we should be able to have both titanic_fanatic 's Titanium Kernel and when I'm up and running again in a month or so, I'll start work on the Diabolo kernel again. Hopefully learn how to make it standalone by then.
[Galaxy S II General] titanic_fanatic:
Those are all the commits from the next branch. This means that they are now using media-caf which is what we'll have to use from now on since its been merged into the cm-11.0 branch.

If you use a forked device/samsung/msm8660-common repo make sure that it's updated with the flag to turn on media-caf.

This also means that until sultanxda and I can figure out this ion thing, were stuck using my 91fixoverlays script to keep hw overlays disabled :( the glitches are so bad right now that I guarantee a reboot if you enable them.

I might also send cl3kener a message to point him at the ion backport by sultanxda since he's much more knowledgeable in this field ;)
[Galaxy S II General] Sultanxda:
I believe I fixed my glitching issue by updating mdp4_overlay_mddi. That driver was very out-of-date, and there isn't any iommu crap in there anymore. It would make sense that my problem was in mdp4_overlay_mddi because the Sensation doesn't use MDDI, so it never used mdp4_overlay_mddi (which would explain why I had no glitches with these framebuffer drivers on the Sensation). I also checked through my commit logs for my Sensation kernel and discovered that I was using the old Ion drivers for weeks with these framebuffer drivers, so I don't think the issue was being caused by the Ion drivers. Newer Ion drivers are nice though, because they make graphics and everything else smoother overall :p

Could you post a dmesg/last_kmsg of your glitches? I'd like to see if you have the same issue, because I have hw overlays enabled without any issues. This message is spammed in dmesg when the glitching occurs on the Skyrocket:

<4>[49102.529205] ------------[ cut here ]------------
<4>[49102.529266] WARNING: at /home/sultan/cm11.0/kernel/samsung/skyrocket/drivers/gpu/ion/ion.c:750 ion_unmap_iommu+0xb8/0xe0()
<4>[49102.529357] ion_unmap_iommu: (2,2) was never mapped for d4b4b480
<4>[49102.529418] Modules linked in: dhd vibrator
<4>[49102.529510] [<c004f5ac>] (unwind_backtrace+0x0/0xf8) from [<c00bd884>] (warn_slowpath_common+0x4c/0x64)
<4>[49102.529602] [<c00bd884>] (warn_slowpath_common+0x4c/0x64) from [<c00bd930>] (warn_slowpath_fmt+0x30/0x40)
<4>[49102.529693] [<c00bd930>] (warn_slowpath_fmt+0x30/0x40) from [<c02b5220>] (ion_unmap_iommu+0xb8/0xe0)
<4>[49102.529785] [<c02b5220>] (ion_unmap_iommu+0xb8/0xe0) from [<c0258e90>] (mdp4_overlay_iommu_unmap_freelist+0x7c/0xd4)
<4>[49102.529876] [<c0258e90>] (mdp4_overlay_iommu_unmap_freelist+0x7c/0xd4) from [<c025e4b4>] (mdp4_lcdc_pipe_commit+0x188/0x370)
<4>[49102.529968] [<c025e4b4>] (mdp4_lcdc_pipe_commit+0x188/0x370) from [<c025dbc0>] (mdp4_overlay_commit+0x90/0xac)
<4>[49102.530090] [<c025dbc0>] (mdp4_overlay_commit+0x90/0xac) from [<c025001c>] (msm_fb_commit_thread+0x84/0x420)
<4>[49102.530181] [<c025001c>] (msm_fb_commit_thread+0x84/0x420) from [<c00d72b8>] (kthread+0x80/0x88)
<4>[49102.530273] [<c00d72b8>] (kthread+0x80/0x88) from [<c004a960>] (kernel_thread_exit+0x0/0x8)
<4>[49102.530364] ---[ end trace 0cefca524f5e722a ]---
[Galaxy S II General] RukusX7:
Am I right to understand that the HTC sensation is a similar chip set as our device?
[Galaxy S II General] RukusX7:
I know I've shared this before, but before anyone wants to test for battery life, please read this thread.

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

And install the skyrocket wakelock app so you know how your charger/cable is working properly.

Thank you.
[Galaxy S II General] titanic_fanatic:
I started working on this to try and trick the device into using the usb charge source when an unknown charge source was detected an got side tracked with this graphics glitch. I'll start working in it again after I get this worked out. I'll be posting another log to see if sultanxda might have some insight as to why I can't get ours to boot with his mdp4_overlay_mddi driver backport
[Galaxy S II General] RukusX7:
Oh OK. For the most part, no issues charging with Samsung chargers and cables. Justv after market ones.
[Galaxy S II General] titanic_fanatic:
[MENTION=4800121]Sultanxda[/MENTION], I finally have the new ion drivers running in my kernel. Sadly, the error still persists as can be seen from my latest kernel log starting at line 3882 ;-( Any other ideas?

SGH-I757M last_kmsg - NEW ION DRIVERS - May 12, 2014
[Galaxy S II General] titanic_fanatic:
Hey guys, I had a slight scare today and thought I would share in case it happens to anyone else.

My phone suddenly turned off today and started vibrating every 2 seconds. It wouldn't stop, and taking out the battery and putting it back in would start the vibrating again. I couldn't access recovery and I would be kicked out of download mode after 2 seconds.

I was seriously getting ready to activate my s1 again until I found a post from another user who had a similar issue occur. He played with his power button for a bit only to realize that it was actually stuck and that's what was causing it to vibrate every 2 seconds. Playing with his power button got it unstuck, so I figured I would do the same. I pressed my power button repeatedly until the phone stopped vibrating and then it booted.

So of you run into a similar issue, it might be that your power button is stuck ;)
[Galaxy S II General] Arodg25:
Haha I've had that happen too. I was on the verge of freaking the F out.
[Galaxy S II General] Sultanxda:
I'm going to go through the framebuffer code by hand and diff it against CAF. It seems like ion_unmap_iommu is being called even though ion_map_iommu wasn't used. I was originally planning on porting newer framebuffer drivers from CAF kk_2.7 (which more than likely would've solved this mess), but they didn't boot for reasons unknown :mad: I'll just grep the framebuffer drivers for references to 'iommu' and compare them to CAF kk_2.7.
[Galaxy S II General] titanic_fanatic:
Excellent, I'll be more than happy to test for you ;)

I was also looking at the CAF code and comparing, but haven't entirely figured out their git system yet. Can you tell me how you decided that CAF kk2.7rb1.35 should be the right branch to pull from? There are so many and I don't really know how to choose, I only started comparing that branch since it was the one that you chose.

One last thing if you don't mind answering. My device had the CONFIG_REBASE_FOR_PMEM_OPTIMIZATION and my kernel sits at address 0x40800000 instead of 0x40400000. I tried removing that and placing our kernel at the same address as the other msm8660 devices and I get no boot. I figure it should work since we no longer use PMEM, but I can't figure out why it won't boot. I can't even get a kernel log for that one. Where do I look to see of something else is assigned to that memory space?

Anyways, thanks a bunch for all your help with this and taking the time to answer my noob questions ;)
[Galaxy S II General] Sultanxda:
Did you remember to rebuild the boot.img with the base address changed to 0x40400000?

You can still achieve 867MB of RAM without changing the base address by manually mapping some Ion heaps to available memory regions below 0x48000000, but to get that extra 3MB for 870MB of RAM you need to move the base address.

Also, this should already be covered by the CONFIG_REBASE_FOR_PMEM_OPTIMIZATION, but did you check that CONFIG_PHYS_OFFSET is set to 0x40400000?
[Galaxy S II General] titanic_fanatic:
Yes, changed the address both in the defconfig and my BoardConfig.mk

I think I'll try again, I did just recently have to scrap my repo and resync because something got messed up and was giving me a non-booting stock cm kernel too.
[Galaxy S II General] CS_HCI:
Bluetooth can't play music files, audio files

Hi,

First off, thank you for all your work. It is much appreciated.

I installed the ROM and it works great, although I did have one problem.

It has to do with Bluetooth. My audio application will not play audio files when I am connected to Bluetooth.

As soon as I disconnect from Bluetooth, I can play the audio files.

Erik
[Galaxy S II General] titanic_fanatic:
Hi Erik, and welcome to the thread.

There is a Bluetooth fix that has been applied, but I have not been able to release it yet because there is an issue with the graphics in the kernel right now that I'm trying to fix with sultanxda. I think we might be getting close to a resolution. New builds will be coming out as soon as we can get that all sorted out ;)

I'll get you to test it again after that, but in the meantime, are you able to use an alternative music app like poweramp?
[Galaxy S II General] big_biso:
I have some exciting findings and resolution. I managed to resolve and stabilze the latest build using the omni performance tuning.

In memory setting there are 6 parameters for minimum free memory. The default values that came with the build were higher than aggressive setting. So I think that many background processes were getting killed to clear memory. I used a preset setting ultra light (remember to select apply setting at boot time to keep these changes). My phone is now stable with no lockups and freezes no notification bar freezes and no random carbon reboots for the last couple of days. Did not even happens once. My next test is to go on each parameter and just lower down to 0.

This will not solve screen flickers but I was able to reduce the flickers significantly by selecting force high-end graphics in omni performance advanced setting.

Also this could be a side effect or just a coincidence but battery life seems to be improved

Can you guys try and confirm these findings
[Galaxy S II General] CS_HCI:
MP3 Files Work With Poweramp

Thank you for the quick reply. I can play all of the audio files that I tried in Poweramp using the Bluetooth protocol with this ROM.

With Bluetooth, I cannot play audio files in the native "Play Music" app, and the third party "doubleTwist" app, except for one music file.

The one song that I can play differs from the rest by its duration. It is short at only 39 seconds long.

The other files are 1-1/2 to 4-1/2 minutes long.

By the way, in this post and my last one, audio/music/sound files —> mp3 format.

Are you the main contributor to this fork? I am curious, how did you learn so much about Android development?

Erik
[LG Optimus G Pro] uxmanz:
while surfing LGVIET i found this interesting post. Someone here in XDA got his g Pro updated to Kitkat by Luck.

any comments?...
[LG Optimus G Pro] mandarjoshiin:
Why duplicate topics??

Sent from my LG Optimus G Pro E980
[LG Optimus G Pro] galapagos:
Do you realize that the original post is from xda, few thread right below yours. LGVIET should have included the original link which will come back to xda, a few lines below your post.

http://xdaforums.com/showpost.php?p=50580274&postcount=274
[LG Optimus G Pro] uxmanz:
well sorry every one,.. my mistake,,..
[Samsung Galaxy Fame] andrakon:
I've tried both the deodexed mod by corsicanu that the tecno 1.2 by carlos_yo and i always have the problem of sim blocked, my phone seems forever in offline mode. I seemed to understand from other threads that I'm not the only one but the answers were lost in this discussions. Thanks for help. Cheers
[Samsung Galaxy Fame] Chrisaa63:
Looking into it

From what ive read very briefly (will look alot more into it!) Is that its something to do with the CSC basically SIM locking the phone, but as always there is a way around it! Its just finding the correct method :)
[Samsung Galaxy Fame] jonaaa:
I am having the same problem, i have installed two roms (TECNO ROM 1.3 and UltraDroidRom) and my SIM its always in OFFLINE MODE.