AOKPCB Broccoli ROM - UPDATE! R3 Beta 6/13! Camera Fixed!
With this headline, I thought ICS camera issues are resolved. I installed R3, still same old story, even with manual flash on, I do not get camera flash at all.
Is there a patch or am i missing something ? OR CM9/ICS camera flash issue is not yet resolved on any ROM yet? Several times, I am giving ICS port a try, only revert back to one of GB flash due to camera flash issue.
Plz help
Flash works on RemICs-UX.
http://forum.xda-developers.com/showthread.php?t=1705503
paluinfusion said:
AOKPCB Broccoli ROM - UPDATE! R3 Beta 6/13! Camera Fixed!
With this headline, I thought ICS camera issues are resolved. I installed R3, still same old story, even with manual flash on, I do not get camera flash at all.
Is there a patch or am i missing something ? OR CM9/ICS camera flash issue is not yet resolved on any ROM yet? Several times, I am giving ICS port a try, only revert back to one of GB flash due to camera flash issue.
Plz help
Click to expand...
Click to collapse
Flash doesn't work on any ics roms. "Camera fixed" means it doesn't freeze when taking pics and ffc isn't distorted looking.
Sent from my SGH-I997 using xda premium
fukanigaup said:
Flash works on RemICs-UX.
http://forum.xda-developers.com/showthread.php?t=1705503
Click to expand...
Click to collapse
Flash works on this ROM also, Thanks.
---------- Post added at 04:48 PM ---------- Previous post was at 04:43 PM ----------
paluinfusion said:
AOKPCB Broccoli ROM - UPDATE! R3 Beta 6/13! Camera Fixed!
With this headline, I thought ICS camera issues are resolved. I installed R3, still same old story, even with manual flash on, I do not get camera flash at all.
Is there a patch or am i missing something ? OR CM9/ICS camera flash issue is not yet resolved on any ROM yet? Several times, I am giving ICS port a try, only revert back to one of GB flash due to camera flash issue.
Plz help
Click to expand...
Click to collapse
This is a known issue. You must manually change the flash options and change the flash to on before taking picture. It will not automatically flash if you have it set to auto. Even with it being set to "on", it is still flaky and it is with EVERY ICS ROM.
On a side note, There really was no need for you to start a new thread for this. We have a separate Q & A thread for this ROM, and we Also answer questions on the actual ROM thread and the 'Camera Fix" was specifically explained NUMEROUS TIMES. It fixed a previous issue with the camera in earlier releases. The actual flash issue has not been resolved. You still need to manually set it to ON
These kernels are for CyanogenMod 10 - Alpha 4.
The goal of these builds is to fix the issues with phone signal, which is not properly working with the stock kernel. Nothing was changes, no extra features, no nothing.
There won't be any more "development" now that the bug is fixed.
The experimental sync bug fix, as the name says, it's a new sync bug fix I was testing. It's here because it partially fixed the missing signal issue at first, but it's not the real fix.
Downloads:
kernel-cm-10-A4-signal_fix.zip: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-exp.zip: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore.zip: stock alpha 4 kernel.
Note: I forgot to change the "name" of the kernel, so you'll get [email protected]_CM9. Don't worry, it's for CM10
Even though I marked V2 as experimental build and I added it as alternative choice, it's the most downloaded version.
As I reported several time ago, mobile data is maybe less stable with it and I think it's because the PDA state is controlled with early suspend instead of the regulr suspend, as it was in the old Samsung releases. In case of problems, flash V1.
If you noticed anything, please report
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patches attached, applied as indicated above.
I verified that when a stock ROM is used, GPIO 126 is normally set to 0.
UPDATE
Click to expand...
Click to collapse
If you are stuck at Samsung splash screen and you are unable to reboot in recovery (I don't know why some users are facing this issue), so you are not able to flash another kernel or restore a backup, you can try to flash one of the kernels with ODIN.
Downloads:
kernel-cm-10-A4-signal_fix-ODIN.tar: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-ODIN-exp.tar: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore-ODIN.tar: stock alpha 4 kernel.
Reboot in Download mode and flash as PDA.
Kernel modules are not included in the PDA. They are not necessary if you were using dhiru's CM with no custom kernels. If you are not sure, do as follows:
Flash kernel as PDA with ODIN (assuming you are stuck at Samsung splash screen and can't reboot in recovery)
Reboot in recovery (pull the battery if nothing works and use the three-keys combo)
Flash CyanogenMod 10 zip (your data will be preserved)
Flash once again kernel as PDA with ODIN
_____
Older posts:
Update: Now I know what stock ROMs use (GPIO 126 = 0). I'll soon update the kernel.
I already wrote that this won't be a custom kernel, no extra features, overclock etc. I opened this thread simply to test a fix, that's why I opened it in the general section, even though the dev section would have been more appropriate.
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
Very old post:
Click to expand...
Click to collapse
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Question
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
jsp1984 said:
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
Click to expand...
Click to collapse
I could, but I don't have LUBKPD modem.
All you have to do is to take modem.bin from the PDA of your ROM (as you may know, you can open it as a normal tar), copy it in /radio overwriting the existing one and reboot. Permissions will be automatically set on reboot.
If you want, here two (different) flashable zips I made for myself. You have to replace modem.bin inside of the zip with yours and then flash.
radio-cm-XXLE4-galaxysl-signed.zip (will erase /radio and then copy the modem)
radio-cm-KPU-galaxysl-noerase-signed.zip (will simply copy the modem)
Works perfectly. Thank you dear Sir :thumbup:
Sent from my GT-N8013 using xda app-developers app
Ok, I think I almost fixed the problem. sec_get_param_value is an exported symbol defined in param.ko (yeah, brilliant...), but we don't use that module anymore in alpha4. The consequence is that the function that turns on the modem is never executed completely.
It still needs some improvements. switch_sel is never set or initialized, but at least the connection is immediately enstablished now. The problem is that I'm not sure which is the best option, so I'll wait for more opinions about it.
In the meanwhile I built two new kernels:
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
V2 is a little bit more "experimental".
OP updated with the new patch.
__
Maybe this is not the right place for this thread, but I opened it here because there won't be any development.
I flashed the V2 and I got the signal instantly after flashing
Sent from my GT-I9003 using xda app-developers app
Thanks man it works great for me...flashed v2 and boom it turned on
Sent from my GT-I9003 using CM10 alpha4 Tapatalk 2
It works so good thank you so much I hope you will continue your very good job
Envoyé depuis mon GT-I9003 avec Tapatalk
Its working fine till now, Thanks alot!. I just wanted to say would you please add move governers in the subsequent release
This thread should be moved to development section.
So that people are aware of the fix.
And it works perfectly, thanks to losconsiuoto
Sent from my GT-I9003 using xda premium
hi
loSconosciuto said:
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Click to expand...
Click to collapse
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
rahul_rocks3 said:
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
Click to expand...
Click to collapse
I wrote some of the original instructions on the i9003 forums, so procedure/method is not a problem here.
I think the issue is I flashed the v2 kernel over the ParanoidAndroid latest 2.54 Alpha4 assuming that as the base is this ROM, the kernel would work. But got a soft brick. Its all fine now, had to go through the whole KPE, LF2 process and now flashing CM10 Aplha4.
If you could just tell me if replacing the modem.bin from LF4 is enough for the signal issues or do I still need to flash the V2 kernel?
Thanks in advance!
EDIT: Flashed V2 but got a 2nd soft brick. Went through the whole process again () My signal and data are working but the indicator is greyed out.
resolved problems
I had problems relating to signal strength and storage.
Thanks and its now working perfectly.
---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------
rahul_rocks3 said:
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Click to expand...
Click to collapse
+1
Flashed V2... It's working great. Thanks.
Sent from my Nexus 7 using xda premium
Thanks works like a charm.
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
arindammanidas said:
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Click to expand...
Click to collapse
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
spacebar2011 said:
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
Click to expand...
Click to collapse
I'm doin' good!
I'm still on CM9.... but v2 seems to work for some people including loSconosciuto himself....
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Hi all,
I have been updating my wife's Infuse with the unofficial CM10.1 build by Scott. When I first installed my wife's 7/14 build (CM10.1, JB 4.2.2) we have NOT experienced any audio crackling. Several nights ago, my wife encountered the crackling noise in videos she's taken using her camera.
I know the issue has been fixed in 4.3, but since this is the first 4.3, I am not very sure that my wife will be able to deal with a few instabilities here and there (which has been the approach I've been following for my wife's installations; waiting a month or so for each version until it stabilizes a bit).
My question is: Is there a manual way of fixing the audio crackling issue (change a setting, edit a config file, flash a ZIP, etc.) that I can perform in the 07/14 build? Or is it a code change and I'm SOL?
Thanks in advance!
dashrendar said:
Hi all,
I have been updating my wife's Infuse with the unofficial CM10.1 build by Scott. When I first installed my wife's 7/14 build (CM10.1, JB 4.2.2) we have NOT experienced any audio crackling. Several nights ago, my wife encountered the crackling noise in videos she's taken using her camera.
I know the issue has been fixed in 4.3, but since this is the first 4.3, I am not very sure that my wife will be able to deal with a few instabilities here and there (which has been the approach I've been following for my wife's installations; waiting a month or so for each version until it stabilizes a bit).
My question is: Is there a manual way of fixing the audio crackling issue (change a setting, edit a config file, flash a ZIP, etc.) that I can perform in the 07/14 build? Or is it a code change and I'm SOL?
Thanks in advance!
Click to expand...
Click to collapse
The problem is caused by viper audio. You'd need the app removed and the lib file...it would have to be built without it included ahead of time.. If you have to stay on 4.2.2 downgrade to the first version without viper. If you don't care then just update to 4.3
Sent from my SGH-I997 using xda premium
FauxAffliction said:
The problem is caused by viper audio. You'd need the app removed and the lib file...it would have to be built without it included ahead of time.. If you have to stay on 4.2.2 downgrade to the first version without viper. If you don't care then just update to 4.3
Click to expand...
Click to collapse
When you say it would have to be built without it ahead of time do you mean this isnt a modifcation that can be made once the rom is installed?
I would like to use Unofficial CM10.1 - 4.2.2 - 7/14/13 version of this rom http://forum.xda-developers.com/showthread.php?t=1776129 and not have choppy audio.
I cant upgrade to Unofficial CM10.2 - 4.3 - 8/5/13 because -
Cannot send or receive MMS because of crashing mms aplication
Front facing camera images with high ambient light crashes the camera (crashes or freezes whichever app your using)
Cannot use Titanium Backup to "modify" system applications (a bug in Titanium that only happens on Android 4.3)
Thanks for your help
braschlosan said:
When you say it would have to be built without it ahead of time do you mean this isnt a modifcation that can be made once the rom is installed?
I would like to use Unofficial CM10.1 - 4.2.2 - 7/14/13 version of this rom http://forum.xda-developers.com/showthread.php?t=1776129 and not have choppy audio.
I cant upgrade to Unofficial CM10.2 - 4.3 - 8/5/13 because -
Cannot send or receive MMS because of crashing mms aplication
Front facing camera images with high ambient light crashes the camera (crashes or freezes whichever app your using)
Cannot use Titanium Backup to "modify" system applications (a bug in Titanium that only happens on Android 4.3)
Thanks for your help
Click to expand...
Click to collapse
No, it unfortunately isn't something you can modify on your own. As far as the MMS crashing problem I saw a commit earlier by slimroms that fixes that so Scott will probably add it in by the next build. The other problems will also be fixed in time, 4.3 hasn't been out long...just give it time
Sent from my SGH-I997 using xda premium
Is it possible for someone to create a zip containing the audio crackle fix that can be flashed via CWM? Or is that out of the question?
If someone can pinpoint the library that needs to be updated and with what version (i.e. grabbing a version from a later build), I can look into how to create a flash-able zip to fix the issue. I would appreciate it even more if someone else did it.
Hello all,
Ever since updating to the leaked release of JB for the One SV (with the, at the time, newer sense) I have had in-call audio issues. This was a known issue at the time, and I flashed back to an older release (the default, factory one).
But since I have upgraded to ViperSV 1.1.0, the issue is back. I've seen people talking about different kernels and such, but I have no idea how to do so. I have re-flashed the boot.img contained in the ViperSV 1.1 ZIP file, but this has not resolved the issue.
Any ideas how I can get my in-call audio back?
(I am using the non-lte european HTC One SV)
Thanks in advance!
- Kyentei
Need to update your firmware in respect to your current available android OS.
Sent from my C525c using Tapatalk
I recently updated mt elementalx kernel to version 3.14 through the app, but it appears to make the camera not work with any application.
For now i've downgraded back to 3.06 and the camera works fine. Does anybody know why it's happening or is it just a bug that's gotta be fixed?
MachCoyote said:
I recently updated mt elementalx kernel to version 3.14 through the app, but it appears to make the camera not work with any application.
For now i've downgraded back to 3.06 and the camera works fine. Does anybody know why it's happening or is it just a bug that's gotta be fixed?
Click to expand...
Click to collapse
Read the thread and make sure it's compatible with your update (such as March if that is what you're on).
Folks, I realize that this is an older thread, but it wasn't brought to my attention until recently, so I've sent the posts to their rightful place and will be locking this one.