android - Set camera iso on Nexus 4 -

-

when use camparams.set("iso", (string)newvalue); in app , run on nexus 4, preview gets slow , after awhile crash because of high memory use.

when use cameraparameters.set("iso", 100); preview slow when use cameraparameters.set("iso", 1600); works perfectly.

it happens in other camera apps fv-5 when change iso setting.

on samsung galaxy s 2 works perfectly. can do?


Comments

Post a Comment

Popular posts from this blog

Need help in packaging app using TideSDK on Windows -

-
i developed application using tidesdk on windows , when click launchapp works fine. moved package , installed imagemagick , wix 3.0 required packaging on windows. clicked on package runtime , cannot guess packaged app is? found file 'installer' in workspace when click on it says installer not find application path . think application not being packaged properly. here log see in tidesdk: preparing package desktop app runtime. 1 moment... staging trial -> copying contents d:\lab\tidesdk\trial d:\lab\tidesdk\trial\packages\win32\bundle\trial -> copying installer c:\programdata\tidesdk\sdk\win32\1.3.1-beta\installer d:\lab\tidesdk\trial\packages\win32\bundle\trial -> copying runtime d:\lab\tidesdk\trial\packages\win32\bundle\trial -> date: d:\lab\tidesdk\trial\packages\win32\bundle\trial\modules\app\1.3.1-beta -> date: d:\lab\tidesdk\trial\packages\win32\bundle\trial\modules\codec\1.3.1-beta -> date: d:\lab\tidesdk\trial\packages\win32\bundle\trial\mod...
Read more

c++ - boost interprocess mutex in managed_shared_memory -

-
i have thread in process 1 create boost::interprocess::managed_shared_memory segment. in segment allocate boost::interprocess::deque using custom allocator , create boost::interprocess::interprocess_mutex , 2 boost::interprocess::interprocess_condition variables using default allocator. use find_or_construct method create these. i have process (process 2) opens these using find method on boost::interprocess::managed_shared_memory segment have opened in process 2. i understand managed_shared_memory segments have kernel or filesystem persistency , interprocess_mutex/interprocess_condition variables have process level persistency. the scenario getting stuck. 1) process 1 starts thread creates everything. 2) process 2 starts , opens everything, @ stage shared memory , synchronization working well. 3) process 1 restarts thread tries create again (i believe shouldnt though using find_or_construct) 4) process 2 stuck on wait call condition variable though thread in process 1...
Read more