Develop Bugs

[DEV] Camera tests - Now testing for Blackstone!

New libraries and kernel for TESTING camera including Blackstone. They need testers!
[UPDATED 01/21][DEV - Camera (Diamond, Blackstone, Raphael, Rhodium) ] Camera
ATT! Kernel and libraries updated 02/21. Check first post.
Now cam works as well as you could expect under WM! Autofocus and every app I tried.
You can try it or wait untill changes get commited, and if things go this way that will be soon (in my opinion).
---------------------------------------------------------
Logs will be more helpful if you add this info:
Platform:
XDAndroid/other release: (FRX03-04, etc):
Kernel:
Modules:
And helpful details like modifications to startup.txt or if it's not a clean install, for example. Thanks!
---------------------------------------------------------
Notes (instructions in first post of linked thread, here for fast reference):
-If using FRX03, use the new libGLES_qcom and gralloc - better 3D performance.
-If using FRX04, those libs are included in the new kernel, so don't add/remove that lines from froyo.user.conf
---------------------------------------------------------
How to make logs - easy way
Please post logs in the main thread, it'll be easier for devs to use them.
How to make logs - command line way
1.- If you're in Android, reboot to WM (clean start)
2.- Launch Haret, let Android set down
3.- Enter Settings - Dev tools - Terminal Emulator
4.- write: "su", hit enter, "dmesg > /sdcard/dmesg.txt", hit enter
5.- write: "logcat > /sdcard/logcat.txt", hit enter
6.- Start Camera, mess with it, including taking photo if it works
7.- Exit to Home (via red buton), shut off device and get both txt's from root of sdcard.
8.- Attach them to the dev thread!
(Sorry for the multiple edits, I'm learning meanwhile)

GREAT NEWS.....
Love it very much .

@Eodun Hi, I hope this logs help. Thank you for your work on this.
As you can see in the log, in the end camera app freeze, did not like something in the hardware.
Regards

how to make logs?

In the future use search function.
http://forum.xda-developers.com/showthread.php?t=502010

Hi
Great news!! camera went open and i can take picture but it says "please insert SD card before using the camera".is it possible change that camera pic saving place ?

xdmcdmc said:
@Eodun Hi, I hope this logs help. Thank you for your work on this.
As you can see in the log, in the end camera app freeze, did not like something in the hardware.
Regards
Click to expand...
Click to collapse
Could you please post the log in the linked thread? Also add
Platform:
Kernel:
Modules:
And helpful details like modifications to startup.txt or if it's not a clean install, for example. Thanks!

xdmcdmc said:
@Eodun Hi, I hope this logs help. Thank you for your work on this.
As you can see in the log, in the end camera app freeze, did not like something in the hardware.
Regards
Click to expand...
Click to collapse
Please, read the main thread pointed in the first post. As you can see in your logcat, the detecte library version is the BASIC_LIB (which means dream library). For camera to work on the blackstone, you need to have the NEW_LIB detected, which is the legend one.
Use the Lib_package on my thread and use the froyo.user.conf file that is in this package. It will automatically bind the camera library to the one needed for blackstone.

I have upgraded Android to FRX04 and with kernel and latest files for camera posted on dedicated thread I was able to have camera working. I will post details to camera main thread.
Thanks,
xdmcmdc

I've managed to get the camera working on FRX04 aswell . Used newest modules, zImage, rootfs and camera lib from the thread in first post.
In 5MP mode I seem to be able to take one picture (which doesn't get saved), and after that I'm not able to take another one. The app doesn't freeze; the camera buttons do still rotate when the phone is turned, but the image does freeze.
In 3MP mode taking pictures WORKS FINE .
Switching to video crashes the camera, but that was to be expected
If more logs are needed I'll be happy to provide them

accountabc said:
I've managed to get the camera working on FRX04 aswell . Used newest modules, zImage, rootfs and camera lib from the thread in first post.
In 5MP mode I seem to be able to take one picture (which doesn't get saved), and after that I'm not able to take another one. The app doesn't freeze; the camera buttons do still rotate when the phone is turned, but the image does freeze.
In 3MP mode taking pictures WORKS FINE .
Switching to video crashes the camera, but that was to be expected
If more logs are needed I'll be happy to provide them
Click to expand...
Click to collapse
You've got the same results as xdmcdmc and me Seems viruscrazy has located the 5mp bug, let's see!

camera works but lost wifi
Hi. I'm very new to Android but love playing with gadgets (I'm 49 so bare with me) I managed to do the camera updates to FRX04 (which works) but for some reason when I add the zimage from the kernel_modules_01232011_topaz_fix package I lose wifi, it just says "error" when I try and turn it on, can anyone help ? I've obviously done something wrong - Paula

paulabutler said:
Hi. I'm very new to Android but love playing with gadgets (I'm 49 so bare with me) I managed to do the camera updates to FRX04 (which works) but for some reason when I add the zimage from the kernel_modules_01232011_topaz_fix package I lose wifi, it just says "error" when I try and turn it on, can anyone help ? I've obviously done something wrong - Paula
Click to expand...
Click to collapse
That's because viruscrazy couldn't build modules to work with that kernel. Stick to previous viruscrazy's kernel (the 01/23 update) or main branch one.

is the latest version dated 07-Feb having the same issue with the Wifi?
Also noted that there are updated Krenel and Roofs 10-Feb, is the camera working with them?

ypsmav said:
is the latest version dated 07-Feb having the same issue with the Wifi?
Also noted that there are updated Krenel and Roofs 10-Feb, is the camera working with them?
Click to expand...
Click to collapse
Camera only works with viruscrazy's kernels. The last one (AF) doesn't work for blackstone, though.
Wifi works as far as you have the modules that work with the matching kernel

Tried the Viruscrazy's Kernels and works like a charm. Camera 3M pixels + Wifi Ok + audio working perfect. Video not working.
The thread seems to be a bit complicated to read, but it's easy, just follows the following steps:
1. download lib packages dated 23/Jan from point 1 of the viruscrazy's thread, previous backup, unzip the contents on your android SD folder.
2. if you are using FRX4 modify the config as indicated by viruscrazy. I used notepad2.
3. Download Kernel + module package dated 28/Jan from point 2 of the thread and, unzip on your android folder.
4. download the new haret.exe from the thread, modify the start.txt
5. enjoy your camera.

Did you solved your problem with "Please insert an SD card before using the camera" message??
/olme

olme said:
Did you solved your problem with "Please insert an SD card before using the camera" message??
/olme
Click to expand...
Click to collapse
Never got that message
Which kernel are you using? Which build?

olme said:
Did you solved your problem with "Please insert an SD card before using the camera" message??
/olme
Click to expand...
Click to collapse
At Neopeek's they've got the camera working with the Camera360 app... I have the app, but not the right kernels... Maybe you should give it a try...
Thought tha you could change the saving location with Camera360.
Here is the marketlink: https://market.android.com/details?id=vStudio.Android.GPhoto

Bunnybugs_007 said:
At Neopeek's they've got the camera working with the Camera360 app... I have the app, but not the right kernels... Maybe you should give it a try...
Thought tha you could change the saving location with Camera360.
Here is the marketlink: https://market.android.com/details?id=vStudio.Android.GPhoto
Click to expand...
Click to collapse
As you say, it's not an userland (app) problem, it's the kernel support that it's still in debug process. Viruscrazy is getting a great progress atm.

"GBX0A_Full_Bundle_11.3.2011" Ginger Bread is cool

http://htcandroid.xland.cz/GBX0A_Full_Bundle_11.3.2011.zip
This build have keyboard issue but you can:
1st activate the "Japanese IME" in the input method just to type and do your google account and get you to android market then find and install the "Better Keyboard 8" for free.. Enjoy...

Better Keyboard 8 apk file
Better Keyboard 8 apk file

like it allot however there is still the classic battery issue .. if it wasnt for that i would run it as my main OS instead of win mobile

error
i get an error "cannot open script file \storage card\default.txt"
any idea?
thanx
edit-problem solved

First impressions, after ~ 1 hour of digging:
- seems to run smoother than previous version;
- battery drainage better even than FRX05`s;
- WiFi works OK;
- camera OK;
Using 01277 kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=536877&d=1299597262

Always freezes on my Blackstone with "Using 01277 kernel from here: http://forum.xda-developers.com/atta...7&d=1299597262" this kernel

I need help!
I was waiting the haret to be done, I calibrated the blackstone, and then it turned on as ginger bread.
The Led was orange and i thought it was problem of android, but I realised that I havent battery and it closed and it couldnt turn on again.
I removed battery and put it back again and when I turned it on, it was back at windows, without any sign of android.
I have to do the haret again or what?

mitikos said:
Always freezes on my Blackstone with "Using 01277 kernel from here: http://forum.xda-developers.com/atta...7&d=1299597262" this kernel
Click to expand...
Click to collapse
Strange. It works for me but I use original GBX0A bundle with 11.3 system and my own kernel/rootfs.
Kernel: http://forum.xda-developers.com/showpost.php?p=11936968&postcount=37
RootFS: http://forum.xda-developers.com/showpost.php?p=12066475&postcount=24
AlexandrosNic said:
I was waiting the haret to be done, I calibrated the blackstone, and then it turned on as ginger bread.
The Led was orange and i thought it was problem of android, but I realised that I havent battery and it closed and it couldnt turn on again.
I removed battery and put it back again and when I turned it on, it was back at windows, without any sign of android.
I have to do the haret again or what?
Click to expand...
Click to collapse
Haret doesn't delete Winmo from your device. Haret just loads Android while removing Winmo from RAM. You need to run Haret every time.

Hi, I installed and it works and has a good look and feel. But i'm stucked on the keyboard problem. Each time I try to write, the keyboard doens't show the keys and I can't proceed. Any help (for dummies) about how to activate the Japanese IME? Thanks

pmachado99 said:
Hi, I installed and it works and has a good look and feel. But i'm stucked on the keyboard problem. Each time I try to write, the keyboard doens't show the keys and I can't proceed. Any help (for dummies) about how to activate the Japanese IME? Thanks
Click to expand...
Click to collapse
on any text input, press longer until there's a menu pop-out to select "Input method" option then choose "Japanese IME"

g3rm0 said:
Strange. It works for me but I use original GBX0A bundle with 11.3 system and my own kernel/rootfs.
Kernel: http://forum.xda-developers.com/showpost.php?p=11936968&postcount=37
RootFS: http://forum.xda-developers.com/showpost.php?p=12066475&postcount=24
Haret doesn't delete Winmo from your device. Haret just loads Android while removing Winmo from RAM. You need to run Haret every time.
Click to expand...
Click to collapse
tnx i'll givi it a try

mitikos said:
Always freezes on my Blackstone with "Using 01277 kernel from here: http://forum.xda-developers.com/atta...7&d=1299597262" this kernel
Click to expand...
Click to collapse
Same here, freeze after a while...

Navigation
Anyone know which Navigation program that is installed with the Froyo version?

Works smooth overall, but got some 3g issues. Anyone else with such problem?

how i can instal this ?

g3rm0 said:
Strange. It works for me but I use original GBX0A bundle with 11.3 system and my own kernel/rootfs.
Kernel: http://forum.xda-developers.com/showpost.php?p=11936968&postcount=37
RootFS: http://forum.xda-developers.com/showpost.php?p=12066475&postcount=24
Haret doesn't delete Winmo from your device. Haret just loads Android while removing Winmo from RAM. You need to run Haret every time.
Click to expand...
Click to collapse
But this means is temporary?
Is there a permanent android rom for blackstone? Or i have to wait?

AlexandrosNic said:
But this means is temporary?
Is there a permanent android rom for blackstone? Or i have to wait?
Click to expand...
Click to collapse
Android now works off the SD card and is not touching Winmo ROM on your device. However it saves settings and stuff and is very usable (I use it on a daily basis). We're working on full NAND rom that will replace Winmo but it's difficult - so no ETA yet.

g3rm0 said:
Android now works off the SD card and is not touching Winmo ROM on your device. However it saves settings and stuff and is very usable (I use it on a daily basis). We're working on full NAND rom that will replace Winmo but it's difficult - so no ETA yet.
Click to expand...
Click to collapse
Ok... Thanks man

Elpoet said:
Works smooth overall, but got some 3g issues. Anyone else with such problem?
Click to expand...
Click to collapse
Can't wake the device up after going to sleep while mobile data is on. Is this a known bug? Also sometimes is not connecting to mobile data at all. Other than that, it's really usable.

g3rm0 said:
Android now works off the SD card and is not touching Winmo ROM on your device. However it saves settings and stuff and is very usable (I use it on a daily basis). We're working on full NAND rom that will replace Winmo but it's difficult - so no ETA yet.
Click to expand...
Click to collapse
I would be so happy if I could use Android on my Touch HD on a daily base, too!
In these threads there are many users as myself experiencing random freezes of the device, in particular if not used for a while.
I have this problem with Froyo version, both X-Red and FX05 builds...
Any advice to avoid the mobile freezes and/or doesn't wake up?
I also tryed changing the sleep parameter to "2", instead "1" but no hope!

Questions [Still Need Answers]

so i have a bunch of questions
1. Is HDR hardware Related or Framework [or what?]
2. how would i Center the clock after Decompiling the SystemUI.apk (ps i added A seconds timer to the clock if that makes a difference)
i managed to get battery and everything on the left but the clock stayed on the right :S
3. how is the XS Rom booted? scripts or apps
4. is it possible to set the Hardware to something that is discoverable by Ubuntu [for example], and then booting ubuntu [for example] as a primary rom
5. is it possible to flash SP Firmware on to the XS
XSP rom does need some modifying to work on XS
--please ignore any Grammar mistakes
Useful Info
things are best explained to me Directly and simply otherwise i don't/find it hard to understand (dyslexia or something)

1st Q ans - Well that part people still don't know because mostly Xperia with Exmor RS camera got HDR,but Xperia C got HDR with Exmor R camera...maybe software and hardware related
Last Q ans - You flash SP rom to XS,then your device will have serios problem mate,I mean it
Sent from my SK17i using xda premium

??
UchihaDareNial
Click to expand...
Click to collapse
what do you mean, if i was to flash just the SP rom and not the kernel , would it not boot would things crash , what?

You will end up bricking your device. You need to go to your devices specific page, you can do that near the top and just type your device model in the type to find your device.
May also suggest using the search function it can be more specific related to your questions.
But yeah, using a ROM from another device to another device will brick it and it will not boot.

Would it work
Android_UK
Click to expand...
Click to collapse
Well me and ForzaFerrariLeo have been working on a port to the xs
the Ram disk didnt need any edditing for it to kind of boot, we both Assume that there are some Configs and build.props that need editing for it to boot but ill have to wait till around 11PM my time for FFL to wake up

[dev][cam][improvements & auto-focus dev][other aosp issues]

Hi, I've spent some time looking @ our camera since there is no evidence of sony breaking camera or not and people seem to be doing alot of guessing, some say DRM keys some say binaries causing issues etc. Enough of guessing and lets take a look at what really is going on.
This thread will look at both improving the camera & auto focus issue along with current AOSP errors
Our camera HW =
What our device currently supports: (to be filled in)
Yes Google is working on RAW camera support (We cannot enable it for our devices)
Apparently unlocking the bootloader breaks camera?????????
Build.prop modifications:
persist.camera.feature.cac (value = 1/0) (not sure what this does yet)
persist.camera.dumpimg (stores to data/img.jpg)
persist.camera.snapshot_raw (
persist.camera.preview_raw
persist.camera.zsl_raw
persist.camera.zsl_yuv
persist.camera.opt.livepic
persist.camera.zsl.interval
persist.camera.zsl.backlookcnt
persist.camera.zsl.queuedepth
persist.camera.snapshot.number
persist.denoise.process.plates
persist.camera.snap.format
persist.capture.burst.exposures
persist.debug.set.fixedfps
persist.debug.sf.showfps
persist.camera.thermal.mode
persist.camera.mem.usecache
persist.camera.longshot.save
persist.camera.dumpmetadata
pretty much self explanatory, but will give more indepth information later on these, what to set these values to and what they do...
Installed Carbon ROM which is pretty awesome but I came across errors in general and ones that are related to camera...
General Errors:-
Kernel:
SPKDRV supply cdc-vdd-spkdrv isn't defined
timeout while setting prog bit, ETMSR: 0x0
Cache ERP
ROM:
Missing binarys
Camera Errors:-
Kernel:
AVC
ROM:
Errors - IDD-API: IDD_SET_SDATA : SEND FAILED Socket 34 Errcode 2 (No such file or directory)(IMPORTANT ERROR)
Error - QCOM_SENSOR_HAL
LIBCAMERALIGHT - Sys Interface Error (this errors can be fixed by giving it write permission)
Error from Focus detector
LIBALS-SYSALS /dev/input/uevent8 (PERMISSIONS DENIED)(IMPORTANT ERROR)
CREDMGRLIB Send/Recieve socket failure Error!! (Important) (CREDMGR_RESULT_GENERIC_ERROR
Ckb create failed
Ckb is not ready
Note:
Camera Focus Distance = Infinite???? :s
Cam parameters before param fixup is called: focus-areas=(0,0,0,0,0)
Cam Parameters after param fixup is called: focus-areas=(-510,30,-398,230,1)
The above is only to identify the current errors with AOSP, when I have more free time and hopefully an upgraded PC I will be able to compile, diagnose and hopefully fix some of these...
I have a rough idea on what is going on with the camera now, will take alot of testing and patience thank you
1080p 60fps will be released soon after more testing....
1080p 60fps:

If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?

Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.

kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app

cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
I was thinking about that, will test it too
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
krabappel2548 said:
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app
Click to expand...
Click to collapse
@everyone this isnt a [letshaveaguesswithnoevidence] thread... Its a [dev] thread, dev posts which include debugging/evidence will be taken seriously.

Hope you guys reach a solution soon.
Good luck.
Sent from my C6903 using Tapatalk

i wouldn't say, that the camera issue is a binary problem.
i would say it is the DRM-partition ... BUT ... i was thinking about that issue and tried a lot ... ONE thing was to flash a rooted and deodexed STOCK rom on unlocked bootloader. cam wasn't working, but that was, what i expected ... then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
don't know, what exactly is the problem with the cam, but i think we have to be more focused on that, because that is one reason, why people will not flash our roms and withot people trying our roms, the bug reports will not be very much ...
so if we will be able to get the camera working, there will be much more users testing our roms and kernels on their devices and we will get better feedback.
So i think the cam is the NUMBER ONE problem of our nice devices ....

I think your initiative is something to be praised here.Maybe if more devs pitched in, you could work together on this and at least come up with a few more ideas so we have a better understanding of what's actually going on (which is a start).
I'm sure that Sony would also follow your work and I'm sure they will release a fix sooner than later (it's their flagship). I was very dissapointed by this bootloader unlocking bug and I really hope this will get fixed because I for one love this phone (been using it for a month now).
I wish you good luck in this endevour! )

DJ_Synergy said:
then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
Click to expand...
Click to collapse
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.

cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...

Shaky156 said:
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...
Click to expand...
Click to collapse
Maybe we can plant a ta-dump on credmgr somehow? Maybe we can find the start-address where credmgr looks for TA, place the dump in ram und modify the address in the binary to point it there.

When the bootloader is unlocked, what is altered? Certain things stop working, like DRM content, I believe this is the main cause of the camera not working, I'm thinking is there a way to spoof the system, forcing it to believe that that specific part of the DRM (for the camera) is still intact, when the bootloader is unlocked? Perhaps if the app / program used to unlock the bootloader could be obtained and modified to allow the specific part of the unlocking to leave the camera intact ??? Just an idea.
Of course that would mean isolating it, which i can't see being easy.
Really bad on Sony's part for letting this happen, surely they would have tested it prior to releasing it ?
With that in mind it would seem that it was Sony's intention to have the camera not work if you unlocked the bootloader, really don't understand this approach.

Yes sony wanted to break camera, with all the stuff ive seen today contained within our devices... Breaking camera was no mistake by sony
4k wont happen unless Sony allow it, camera only passes 1080p, have to use specific yuv(Venus) format for 4k afaik, max fps available is 60 on both 720p & 1080p, no HFR(90. 120, 150fps mode available)
Will update OP with more information regarding what our cameras can support
Also i see the light at the end of the tunnel... Regarding kexec

Yeah, Kexec would be the workaround for that. The Keys would stay untouched cause of the old kernel and the new kernel will boot the system ... if the system then read the key, it will get correct values out of the partitions ... just in theory ...
So if we can get kexec to work, it may not break the camera and we have a good workaround for that ...
will try to help on kexec ... hopefully we can get it to work ...
---------- Post added at 11:37 AM ---------- Previous post was at 11:26 AM ----------
Desperanto86 said:
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.
Click to expand...
Click to collapse
TA backup had been the first i have done so yeah, for sure BEFORE unlocking ...
haven't tried to wipe camdata so that was the fault ^^ ... will try it again

Just a thought... not sure if it is possible (since I'm not that familiar with embedded systems and such)..
but could it be possible that only certain parts of the TA-partition are restored when restoring the backup after unlocking, so the DRM-stuff is retained?

Guyz just want to know, camera will be back (from Sony or anothers) ??

kartal172 said:
Guyz just want to know, camera will be back (from Sony or anothers) ??
Click to expand...
Click to collapse
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app

cursordroid said:
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app
Click to expand...
Click to collapse
Just asking that is confirmed from Sony possible fix or any news?

kartal172 said:
Just asking that is confirmed from Sony possible fix or any news?
Click to expand...
Click to collapse
There is no confirmation. There is no news.

I have twitted them several times without answer

[Q] Common problems of cm9, cm10 and cm11 already known?...

Hello,
I detected the following systematic problems of cm9..11
1.) Skype cannot be started at all. It does not even react on a click of its icon. And no error message appears.
2.) the akku load status is shown incorrect during load process. E.g. after 4 hours load it shows 37% instead of true 100% (which is shown after reboot).
3.) The wonderful app 'lgCamera' runs very slow and jerky. This was fine in Android 2.x versions.
4.) the FM radio app for the WFS radio tuner (no internet radio!). How can I find it (and flash it into the system folder as a system app)?
I suppose that everybody can confirm my problems!?...
Are those already known by the development team? Cause I wonder that they are not fixed in ALL CyanogenMod versions yet!
Will there be a chance to expect their fix soon?...
5.) Furtheron I have big compatibility problems when flashing cm9..cm11 ROMs and others. Error message: "cannot load volume /misc. Can't partition non-vfat: /storage (vfat)". For nearly each ROM I have to change the recovery. Currently I change between the following recoverys (one of them allways works):
twrp-2.2.2.0, twrp-2.7.1.0, Phil-Z 6.43.7, cwm-5.0.2.8, cwm-6.0.5.3. Nobody else having that problem?...
Is there any recovery version that can read all 'formats' of zip files?...
Will there be compatibiliy at least at the backup files between all of them?...
Thank you VERY much for a quick help!

1.) not compatible anymore, say Thanks to Skype
2.) This is probably problem with battery not reading voltage correct anymore on charger (happens) for me on all roms even stock. (After 100000 of flashes and almost 3years old down sucked battery
3) ics and up isn't made for this phone, slow downs and other incompatibility can happen.
4) There is a solution called spiritfm(free) Google it, you will find the xda thread.
5) twrp 2.2.2.0 and cwm 5 is working on all ROMs beside newer kk builds (needs recovery compiled with TLS support, newest ones available)
Greetings Kevin

Hallo Kevin,
I am so glad that you answer! Thank you very much!!
to 1.) Yes, I realised meanwhile that Skype 4 ist still running fine. So the reason why the new Skype 5 version does not work on Wildfire S (or even on all CM versions of all devices??) you don't know!?...
to 2.) So this is a general Andrid 4.x problem of Wildfire S device only?... (cause e.g. on Galaxy S4 stock (of my girl-friend) it works fine!...
to 4.) Thank you. I installed this free version '0918fr.apk' but I get the error message (su rights confirmed): "Error: No FM accessible. SU: 0 Fm:BC2 SU:0 Bt:3 Ht:0 Mo:BCU". It does not seem to be compatible although I have read everywhere that it should work. Is this maybe antoo old version? Or what can be the reason?...
to 5.) So I used newer version 'cwm-6.0.5.3' and 'twrp-2.7.1.0', as I mentioned, but then these versions do not support older version than KK. E.g. 'CronMod-INT2EXT+_signed.zip'. This is the problem. Any solution?...
Is TLS ment as 'Thread-local storage'?...
Another short request:
a) Video recording with cm11 on Wildfire S works now without any patch. But if I record a video longer than about 5 seconds and I want to watch it directly after having stopped recording (timeframe about 7 seconds) then the camera app crashes. Can you confirm that on Wildfire S? What can be the reason?...
If Olivier's camera patch will help here as well I have not tested yet...
b) Management of Launcher and App screen is somehow circumstancial or not even possible. This is why the option 'Homescreen' is missing in 'Personalization' ('cm-11-20140816-Nightly') although the related screenshots of cm11 in XDA show this option!! E.g. App icons cannot be sorted alphabetically or cannot be manually moved within the screen. Or the home panel is the most left one instead of the middle one. Etc.
Any reason why the option 'Homescreen' was deleted (in XDA cm11 screenshots for Wildfire S still show it!! S. http://forum.xda-developers.com/showthread.php?t=2735775 )?...
c) CM11 OTA update suggests me 'cm-11.0.0-RC9' as the first in the list. Is this really more actual than the installed 'cm-11-20140816-Nightly' (version 11.0-20140816) ?...
d) In this version the Email system app is missing. Why?
Any zip to flash it anywhere? Or do I have to use one of the market?...
e) No warm reboot option available anymore in cm versions?...
Thanks for your help again, Kevin!
Many greetings, Falk

to 5.) I could solve that problem meanwhile by myself. I downloaded a modified version of cwm 6.0.5.3 here:
http://click.xda-developers.com/api...5.0] - Post #52 - XDA Forum&txt=the new build
But I still do not know what was modified! You?...

6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention

Beeefalo said:
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Click to expand...
Click to collapse
Because it does not exist? I never faced any bug like that.

aWFSuser said:
Because it does not exist? I never faced any bug like that.
Click to expand...
Click to collapse
oh, its super present .
It was a "common" problem in cm9, cm10 based roms, at least judging from the various threads dating back to 2013. And as I discovered yesterday its also present in CM11 RC9 for me.
Occurence of the bug is very random and seems to be bound to certain providers which makes it hard to debug/fix i guess.
Sadly, from what I've read "deal with it and toggle airplane mode when you need mobile data" or "install cm7" are the ways to handle this bug.
cheers
Beefalo