Database Develop

[Q][ICS 4.0.4 / MTD] AOKP for P1000/L/N - Camera App

Hello!
I have been using the ICS 4.0.4 [MTD] AOKP for P1000 ROM for sometime now and am on the latest build B#36 (as on 17/05). The Camera App with that build is not stable and does crash randomly. This is mentioned in the Bugs List. However, in the following post --
http://forum.xda-developers.com/showpost.php?p=25102133&postcount=876
I have installed the 'CameraUpdates.zip' and have not faced any issues with the Camera App after that. Further, the GUI is also different from the Camera App present in the B#36.
My question is why not update or include the Camera App listed in the link above with the next build of this ROM?
(Unfortunately, I cant post in the Dev Thread due to the number of posts.. Could someone look into this and pass it on to the Dev Thread -- http://forum.xda-developers.com/showthread.php?t=1523174)
Thanks.

Yes I mentioned that and Stimpz0r will fix it in the next build, it was included in the previous build. Thanks
Sent from my GT-P1000 using XDA

Couple things:
I would've posted this in the dev thread, but, you know the rules about new accounts :/
Just one day since coming from build 35 to 37, have noticed significant power drain, still quantifying it, will keep my eye on it, but initially lost 30% over the course of 5 hours in idle mode, constant drain, 3g off, wifi off when screen not active, BT off, GPS off.
Also, the whole app rotation on home screen thing comes up when trying to move/delete/uninstall, even with allow 180° rotation turned on. After activating rotation, one has to restart before it takes affect.
More importantly, the main camera still acts up quite a bit for me. Quite a few fc's, which is to be expected, i guess. Strangely if i turn off the shutter sound in settings, it crashes, every time. Like, always and without fail. Panorama and video, front camera all working well, just the main camera. Tested with stock camera, instagram, vignette, and procapture, same effect, fc's with shutter sound off. I did a factory reset/wipe and went through settings systematically, so I'm reasonably sure this is the problem. Wonder if anyone else has encountered this, or has a work around. I hate that shutter noise.
Don't know if it's intentional but when i try to turn off menu button in top right corner through menu location in rom control settings, the button isn't removed, and the nav bar back/home/recents/menu buttons become larger and more spaced out instead. Not a problem, just weird. Resetting nav bar options and rebooting reverts it back to smaller keys again.
Finally i just want to give some recognition to devs like stimpz0r, humberos, cdesai, dizgustipated, alroger, chainfire, and sbrady, who seem to consistently add to and improve these builds tirelessly, as well as take the time to answer questions and field comments from noobs and more experienced members alike with a degree of patience and humour. And of course thanks to all the aokp and cyanogenmod mates, my sgt works so far better than when i bought it. The teamwork and support is amazing to see. It's impressive, what all of you guys have been able to do. I thought we were all well and truly screwed by Samsung, i couldn't believe it when they left all of us early adopters out in the cold, but you have really come through for all of us. This is a seriously nice piece of work.
FF
Sent from my GT-P1000 using XDA

By batt hasn't been great, but yesterday I downloaded Battery Calibrator by Damo Software and did calibration according to its instruction and seems to improve.
Shutter sound is a known bug, I thunk mentioned in the known bugs, did you read it?
Sent from my GT-P1000 using XDA

Now that you mention the camera thing, yeah. But I'm a johnny come lately to aokp. It takes a serious time investment to read through all the posts with the issues scattered throughout, it's easy to miss one. And while there is a lot of info in the op and changelog posts, particularly about mtd/non-mtd (which is great) these common problems seem to be under-addressed, so i thought to just gather them together here for someone to find. I know it must be a pain to update the changelog posts thoroughly after every new build.
Cheers
ff
Sent from my GT-P1000 using XDA

p1000
Sir, can you please help me how i do upgrading my tab p1000 to ics 4.0
the existing ver 2.3.3 , and i hope if i get for ics or any upgrading ver above 2.3.3
[email protected]
if you have time

subroma said:
Sir, can you please help me how i do upgrading my tab p1000 to ics 4.0
the existing ver 2.3.3 , and i hope if i get for ics or any upgrading ver above 2.3.3
[email protected]
if you have time
Click to expand...
Click to collapse
Assuming yours is GT-P1000
Read this
http://forum.xda-developers.com/showthread.php?p=27500461
Sent from my GT-P1000 using xda app-developers app

If it might help you
go to this forum http://forum.xda-developers.com/showthread.php?p=23097605

[Q] Home Button (Capacitive and Software) not working with CM9 / AOKP?

Hi folks,
Apologies if this question has been asked on the Bionic forums elsewhere; I did a search and didn't find anyone with an answer.
I've been experimenting with custom ICS ROMs on my Droid Bionic, and of the four I tried, three of them leave me in a situation where my Home button doesn't work. This applies to both the capacitive key on the Bionic bezel as well as the soft key which is native to ICS in phones that don't have capacitive or hard buttons (but can be enabled for the Bionic in custom ROMs).
Let me break down what I mean by "work". When I press or long-press Home, I get the appropriate visual and and haptic feedback as expected. But nothing happens in the OS. I expect it to take me to my home screen from any app; it does not. I expect the capacitive button long-press to bring up the Recents for multi-tasking, and it doesn't. I've assigned different behaviors to the soft key in the launcher, both press and long-press, and none work. All other capacitive and soft keys work just fine, and CM10 on my Iconia A100 doesn't exhibit any home button issue.
Here are the ROMs I tried which exhibited this issue for me:
CyanogenMod 9 (CM9 20120725 build, unofficial)
AOKP (Targa 20120725 Milestone 6 build)
LiquidSmooth MR 2.6 (Jester's JMOD modification of LiquidSmooth v1.5)
Currently I'm running on LiquidSmooth v1.5 MR 1, and it works perfectly. One thing I noticed is that CM9 runs the Trebuchet launcher, and AOKP and the JMOD of LiquidSmooth both run Nova Launcher. Meanwhile, the Liquidsmooth build I'm on is running what looks like LiquidSmooth's own modified Launcher (forgive me as I betray my n00b roots). I can only assume that the launcher is the issue and that perhaps if I just ripped LiquidSmooth's launcher APK I could run/use it in any other ROM, but this is just an assumption. I'm just wondering if anyone else experienced what I did, because from the looks of it I haven't found anyone who has.
Thanks for any insight anyone can provide!

This issue with the Home Button is not Bionic specific. I have had this issue with both Bionic and OG Droid. It has more to do with the OS I believe. I know I've read about this somewhere but I don't remember where. Usually it happens when you upgrade your phone with a custom rom and for some reason it disables the home button. In my case I just reinstall said rom until it works. It's happened a few times with my OG Droid considering I would switch roms always weekly due to the unlocked bootloader. Not so much on the Bionic since it's locked. Waiting for Motorola to release the bootloader unlock for our Bionic...hurry up Motorola or Google...I know I didn't really answer your question but that's my experience.

amageus said:
This issue with the Home Button is not Bionic specific. I have had this issue with both Bionic and OG Droid. It has more to do with the OS I believe. I know I've read about this somewhere but I don't remember where. Usually it happens when you upgrade your phone with a custom rom and for some reason it disables the home button. In my case I just reinstall said rom until it works. It's happened a few times with my OG Droid considering I would switch roms always weekly due to the unlocked bootloader. Not so much on the Bionic since it's locked. Waiting for Motorola to release the bootloader unlock for our Bionic...hurry up Motorola or Google...I know I didn't really answer your question but that's my experience.
Click to expand...
Click to collapse
Even though it wasn't a direct answer I definitely appreciate the insight! It's good to know what's happening out there and I now have some more context around the situation... It's weird because Liquid is really the only one that works for me. I just now tried a CM9 update just for kicks and again the Home button doesn't work. (Using Trebuchet natch.)

MrCHUPON said:
Even though it wasn't a direct answer I definitely appreciate the insight! It's good to know what's happening out there and I now have some more context around the situation... It's weird because Liquid is really the only one that works for me. I just now tried a CM9 update just for kicks and again the Home button doesn't work. (Using Trebuchet natch.)
Click to expand...
Click to collapse
I know that the Bionic and the OG Droid are not the only ones who experience this dreaded dead home button issue. It exist in a lot of android phones. You could google it and get a lot of hits on different phones. I know I have the first time I experienced this issue with the OG Droid. Could have something to do with the coding in the roms you are installing and it seems to be a hit and miss. Apparently your phone is picky about which rom it wants you to install lol. Maybe a developer could chime in and explain a bit more? Or someone with a lot more knowledge?

t
amageus said:
I know that the Bionic and the OG Droid are not the only ones who experience this dreaded dead home button issue. It exist in a lot of android phones. You could google it and get a lot of hits on different phones. I know I have the first time I experienced this issue with the OG Droid. Could have something to do with the coding in the roms you are installing and it seems to be a hit and miss. Apparently your phone is picky about which rom it wants you to install lol. Maybe a developer could chime in and explain a bit more? Or someone with a lot more knowledge?
Click to expand...
Click to collapse
Ino developer but I had this problem as well but once I flashed the latest gapps all was well.
Hope this helps

[Q] Various issues with Cyanogen Mod nightly 10.1

Hello everybody,
I have been waiting a bit until posting this issue to see if future nightly builds of Cyanogenmod solved the problem but to no avail, I already posted on their forums but so far no one has been able to figure out the problem... not that they tried.
I'm using an international Galaxy note (n7000) and these issues have been popping up since last month.
The main problem comes up when using the android keyboard and listening to music at the same time, the phone just seem to struggle a lot, music begins to stutter and usually the phone just becomes unresponsive and I have to force reboot the whole thing. A pain in the neck. Lately the phone just hangs whenever it feels like it and I have to reboot it, it usually happens twice a day.
Sometimes you're able to come back to normal after a few minutes but rarely.
The problem was even worse while using SwiftKey, now I'm back to just using the normal android keyboard but still the issue pops up almost every day. I already did a wipe data/factory reset, no avail.
Any thoughts on this?
Thank you in advance.

Post a log. Which ROM where you on before flashing CM.

sounds like a memory leak, try newer versions or trace down the issue. Check which apps consume most and cpu when it occurs.
Check as previous poster said logfiles
Sent from my GT-N7000 using Tapatalk 2

CM 10.1.3-N7000 bluetooth issues
Hello,
I'm using CM 10.1.3-N7000 and I really love it, but I'm forced to use another ROM, just because of the carkit compatibility via bluetooth. The sound is extremely bad.
Does anyone know if it's fixed in later versions or earlier versions?
Are there other ROM's, ot based on CM without the bluetooth problem?
I'm really searching since two days now to find a bluetoothfix, but can't find it.
Pairing and so on is no problem at all, it's just the soundquality that is terrible. (it was not the case with my stockROM)
thank you for giving me some advice!

I switched to Omnirom and I think the problem has been solved now.
If I see that the same problem is back as it was with CM, I will come back to that.

Left speaker issue

I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound

vwmaniacx said:
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
Click to expand...
Click to collapse
I have the exact same issue. Tried million ROMs, sound patches and tricks but nothing change. The easiest way to see the difference between the two speakers is to run the Audio Test using HTC Function Test by dialing *#*#3424#*#*
Finally, I managed to get S-Off and now I'm going to get back to 100% stock flashing RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe, I'll do the test again and update the post.
EDIT: I'm full stock and it didn't fix it I guess I have to send it back...
BTW, what did you do? Did you fixed yours?

Running Sinless 5.1.5 now with elemental, everything works 100%. I guess for some reason my phone just didn't like TD, we all know they have a personality of there own..
Sorry for the long wait before response, I don't pay attention very well.

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you

Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really

tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up

delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?

Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!

Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good

tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?

I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.

LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?

Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.

sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values

Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk