yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] Shaky156:
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 :D
[Xperia Z1 Original Android Development] DJ_Synergy:
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 ----------

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 :)
[Xperia Z1 Original Android Development] Chillout:
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?
[Xperia Z1 Original Android Development] kartal172:
Guyz just want to know, camera will be back (from Sony or anothers) ??
[Xperia Z1 Original Android Development] cursordroid:
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.
[Xperia Z1 Original Android Development] kartal172:
Just asking that is confirmed from Sony possible fix or any news?
[Xperia Z1 Original Android Development] gladiac:
There is no confirmation. There is no news.
[Xperia Z1 Original Android Development] Poesini:
I have twitted them several times without answer
[Xperia Z1 Original Android Development] kartal172:
and now?? :confused:
[Xperia Z1 Original Android Development] DAddYE:
I think we should all together start to bug [MENTION=1346574]SonyXperia[/MENTION] every day. I don't like having an unlocked phone which really is unlockable, add slow roll outs (on android versions) so if nothing is gonna happen soon I'm going to sell this device.
[Xperia Z1 Original Android Development] kartal172:
+1
[Xperia Z1 Original Android Development] dagrim1:
Really? Are you going to ask this every day?

Let the developers work at their own speed and if it is fixed it will be hard to miss but please don't start asking every day.
[Xperia Z1 Original Android Development] Kingcool88:
They do know about it, and has also commented about it on oct 17:
[Xperia Z1 Original Android Development] Poesini:
Yeah lol October 17 it's already December xD
[Xperia Z1 Original Android Development] guddu2011:
i hope it will be fixed with 4.3 update... any1 can confirm if dx10/dx100 works on unlocked bootloader?
[Xperia Z1 Original Android Development] kartal172:
I see that.... just ask Sony :silly:
[Xperia Z1 Original Android Development] mirhl:
Of course
[Xperia Z1 Original Android Development] zeppelinrox:
Motorola Milestone had CM6, CM7, CM9 and CM10 ROMs all running stock Froyo kernel and overclocked with a loaded overclock module.

They finally got a custom kernel to work via 2ndboot, which was successful on other Moto devices as well - all of which have locked bootloaders.

I made a couple of posts regarding this here http://xdaforums.com/showthread.php?p=48003282#post48003282http://xdaforums.com/showthread.php?p=48009704#post48009704
[Xperia Z1 Original Android Development] kholk:
Getting kexec to work here without a custom kernel behind it is really difficult.

I've been developing hard to make something like kexec for the Motorola RAZR XT910.. it was a really hard and totally frustrating work... but yeah, it's true that I've succeeded... fact is, it took 6 months of 24/7 work.. and it was just a dualcore, TOTALLY OPEN chip, with all of the datasheets etc available to the public.

I mean, at that time, there was no custom s$£t in that chip (that was an OMAP4430)... and it was total pain to reset the registers into a known state to let the new kernel to boot "flawlessly" (new kernel which required a small patch in the last version of the "kexec" bootloader).

Now, you know, with Qualcomm it's a pain.

From what I know (and correct me if I'm wrong, because I could be), we have no detailed TRM and datasheets of our QC chip so, even if we want, it's unlikely to get kexec working AS A MODULE on the original kernel.

We may get it to work on a custom kernel.. that's easy and, ofc, useless as hell.

Getting to the DRM discussion, I tried to crack it but heh, I'm not a cracker. I succeeded to fake the key authentication, but it didn't work still....

... also, I tried to point the credential manager to my TA backup image in a loopback device.

That just made the phone to tell me something like "no, really?".

After trying a couple of things I discovered that (justified as I would develop it the same way) Sony's credential manager is working by using the crypto hardware in the QC chip.

Now, after my research, I can personally conclude (and people may have other ideas -- and if you do, please tell us --) that we have two options here:

1. Rewrite the focuser (etc!) userspace driver to NOT use Sony's image processing and to use our own instead (our own image processing would be built with already existing opensource tools, obviously)

2. Pray Sony to give us a solution for THEIR mess.

I don't think there are other ways sincerely... and that's sad because the Z1 is such a good machine.

Ah, btw, that's totally OT but still needed to say...

...sometimes it may appear that I'm writing a message and then dying somewhere at some point. Just remember that it's not like that. I have lots of things to do.

Anyway, if any developer wants me to try to give a look to some idea, I'm available.
[Xperia Z1 Original Android Development] gladiac:
Oh well, thanks for the heads up! I was really hoping that using a TA backup via a loop-device would work...
[Xperia Z1 Original Android Development] gladiac:
I wonder how the focus in the nexus 5 works. Since it has the same sensor chip (imx135), maybe we can use it's drivers to get the focus working?
[Xperia Z1 Original Android Development] DAddYE:
I know they know but we are approaching the 3th month and IMHO this is just embarrassing

Here my tweet: https://twitter.com/DAddYE/status/407631175230816257
[Xperia Z1 Original Android Development] dagrim1:
Yup, it sucks... Not sure what to hope for either. Just hope they release 4.3 this december (so they at least live up to that 'promise') and who knows, maybe fix the unlock issue with it.
[Xperia Z1 Original Android Development] kholk:
[MENTION=362563]gladiac[/MENTION]

I don't know which sensor is in LG G2 and/or LG Nexus 5.... but surely in Nexus 5 there isn't the same sensor of Z1.

About IMX135, you're right and wrong at the same time: in reality, I'm somewhat confused.

Sony did release three new "Exmor RS" (leaving the Exmor R "low-end" discussion) cameras for handheld device application: two are 8.08MP and one is 13.13MP... and exactly the one who I'm talking about is that 13.13MP camera.

That 13.13MP Exmor RS camera packs a Sony IMX135 sensor and an IU135F3-Z imaging module.

Now, read that carefully:

--- IMX135 is a 13.13MP sensor, 1/3.06 inch, and the IU135F3-Z module's aperture is F2.2. ---

Xperia Z1 contains an IMX135 driver in the kernel but, strangely, the camera specs aren't matching with that!

Compare the specs of that Exmor RS sensor with our Z1 camera:

--- (Unknown?) The one in Z1 is a 20.7MP sensor, 1/2.3 inch, with "G Lens" (marketing name -- model no. unknown) which features an aperture of F2.0. ---

That means that either:

1. Sony fooled everyone (and that's unlikely since we can really feel the difference between SGS4 and Z1, not just by SW rendering)

2. We haven't got a proper IMX135.

The second sentence means that, even if Sony has developed a custom sensor based on IMX135 just for Z1 (sharing the same driver --unlikely--), we still wouldn't be able to use an userspace driver from another similar device with QC chip and IMX135 sensor, because that would lead to uncalibrated parameters for the final image processing.

Uncalibrated parameters for image processing on a closed-source driver means TOTAL MESS and impossibility to fix it... so it's better to not play with these things....

....Anyway, you may say we're talking about the FOCUSER, not about the DAMN CAMERA SENSOR.

Not true.

We're talking about both, since both drivers are "interconnected" (dependant from each other and 99% of the times in the same blob), and since the physical camera module packages both sensor and focuser.

So, getting to the point now..

...IMHO, what you said is totally impossible, even if there was another phone with an IMX135 sensor in it.

[MENTION=3160680]DAddYE[/MENTION]

I replied to your tweet and I also RT'ed it. Anyway, like I wrote, I think Sony will solve that with the 4.4 update... they really don't want to get down like the old Motorola did (prior Google's acquisition).

Oh, otherwise, the Z1 scene will become just a dirty desert, because that's like not allowing to unlock the bootloader. I mean, if I wanted a good device I could have bought an LG G2.

The only thing that came to my mind that made me to choose the Z1 over the LG G2 is exactly that camera (and with that software it isn't a that much stunning experience, since there's lots of noise), otherwise I would have spent like -150/-200 euros for buying a G2 or a Nexus 5, and I think that most users who bought the Z1 made the same reasoning.
[Xperia Z1 Original Android Development] DAddYE:
Thanks [MENTION=489838]kholk[/MENTION], saw and really appreciated, I hope sony will fix that soon, I choose Z1 over LG2 or Moto X (I like a lot the latter) just for the camera but I like to upgrade soon (that why I picked an unlocked bootloader) android due to the fact the 4.3+ improve a lot notifications (which I used a lot) and drain painful my battery.
[Xperia Z1 Original Android Development] kholk:
Well, I was just forgetting to say that I don't want to discourage possible development aside from Sony's solutions on that thing.

Anyway, heh, just repeating, we're everyone on the same boat here, we all bought it because of the camera... and that camera break from Sony, like [MENTION=4802595]Shaky156[/MENTION] and [MENTION=2880355]dladz[/MENTION] said, it was totally intentional and it's clear it is because of how the software is architected.
[Xperia Z1 Original Android Development] Shaky156:
[MENTION=4225567]delewer[/MENTION] has already successfully loaded the kexec module on stock kernel

No.1 there is no point cause we need to use imageproc chip

No.2 is more realistic

We arent using imx135

Intentional it is
[Xperia Z1 Original Android Development] kholk:
Well, I agree that Sony's image processing engine is anyway better than a "generic" opensource thing...

About kexec, sure, loading the kexec module and implementing the required syscall and/or getting around it with an hack is really, really, really easy.

It's also really easy to get kexec to load the new kernel in memory and make it to try to jump to its address.

What's not easy at all is everything else.

If you didn't know, when you enable kexec in the kernel, you will enable various parts of ifdef'ed code all across the arch "internals", so, when you haven't got that kexec code in there you're almost ****ed!

That's mostly because you can't just patch the functions in memory for two reasons:

1. Those are not exported

2. Even if you find the functions "by hand" (by static address I mean), you should remember that the way some things are developed isn't permitting to do that.

Now, when the kexec ifdef'ed code is being enabled in the kernel (so, regular kexec), it makes lots of shutdown jobs prior jumping to the new kernel.

Just remember that at the decompressor stage (so, first bits executed) the kernel wants an 1:1 mapping and obviously expect the L2X0 and the MMU to be disabled, because it will initialize both later.

Think about that: without a saved state, is it possible to cleanly shutdown (turn off, reset to known "zero" state) MMU and L2X0?

Here's the reply: NO.

That's why I said we need the TRM etc etc. Just because, if you want to make a dirty kexec like mine for RAZR or 2ndboot for Motorola's OMAP34xx devices, you need to reset various SoC parts and to put those into a known uninitialized state, otherwise, things will fail.....

....and for "things will fail" I don't mean just a simple kernel panic!

I mean you're dealing with spurious IRQs, hardware errors (including security errors from the TrustZone implementation), AND, last but not least, the familiar kernel panic.

...And that's why I said it's nearly impossible to develop a dirty kexec for our QC chip.
[Xperia Z1 Original Android Development] Shaky156:
Youre correct, there is ifdef kexec within arch so module wont load

I think a exploit needs to be found at bootloader level for us to even take advantage or attempt to fix camera, if we can unlock the bootloader without destroying the drm keys guess we would need to get our devices to read as engineer build, theres a tonne of security though

Ive put a request on dan rosenbergs github for loki on xz1 support that method if successfull can get custom roms & kernel with camera, but need to take a closer look incase it would break our devices
[Xperia Z1 Original Android Development] kholk:
I'm sorry, but with that, you're completely offroad...

It's unlikely we may discover a bootloader bug... but well, it's really more likely we may exploit the credential manager from our already booted Linux system.

Absolutely.

...But, like I already said, I've already tried to patch it, though I'm not a cracker, I've disassembled it and tried some magic, but I was being slapped and owned from the crypto HW.

Ahm, I'm not familiar with Sony devices, and infact, as you can see from my signature, this is practically the first Sony device in my hands... so... what about that XZ1 thing?
[Xperia Z1 Original Android Development] Shaky156:
It may be unlikely but not impossible, dan rosenbergs loki is an exploit within aboot, for our devices it has been patched afaik, but will look if i can find anything, there are more than 1 way to achieve the same thing :)

This is also my first sony device, XZ1 = Xperia Z1
[Xperia Z1 Original Android Development] kholk:
I agree that nothing is impossible.

It's just about putting our efforts in something that's way more likely to happen to not waste our time ;)
[Xperia Z1 Original Android Development] Shaky156:
Phone fell this morning, screens smashed cant do much development just now
[Xperia Z1 Original Android Development] dagrim1:
Ouch, sorry to hear that man... Insured somehow?
[Xperia Z1 Original Android Development] Shaky156:
Nope, will see what i can do, this sucks!!! Sony encrypted/authentication/DRM keys n you cant customize much without unlocking bootloader... Wont purchase sony device again that is a definite...

Also dan rosenberg has closed the issue i opened on his github requesting support for this device, he said this devices bootloader is too much modified to use loki... Makes sense
[Xperia Z1 Original Android Development] guddu2011:
Sony Official Developers Support = Dead from last 3-4 months.. #ShameSony
[Xperia Z1 Original Android Development] DAddYE:
Hi there. I have a little question. Now with the 4.3 we won't break anymore the camera... But why aosp still have problems with the camera? What is needed to get it working properly?
[Xperia Z1 Original Android Development] Miustone:
+1

Yes thats interesting... What have Sony Fixed in the 4.3 Update? Is really a fix for the Camera in the latest Update?

Got my XZ1 last Friday,still on 4.3 without Root + Unlock :crying: Soundsettings gives me FC and i can't fix it ;/

Pleas bring us UP-to-Date Guys :good:
[Xperia Z1 Original Android Development] Alx31:
Check xperia blog...

Link Here

out since about a week ;)

Tapatalked with my Yuga
[Xperia Z1 Original Android Development] Miustone:
I've read this on 10 different Pages ... My Question is: What have Sony really done? :confused:
[Xperia Z1 Original Android Development] B1nny:
They brought out a new software update for the Xperia Z1. Which is based on Android 4.3 and have updated numerous Xperia applications.
[Xperia Z1 Original Android Development] DAddYE:
No idea how but now when you unlock the bl you'll not break the camera.
[Samsung Galaxy Gear] DomZH:
Hey Gents!

Does anyone know about a powerpoint presenter for the gear? this would be totally awesome if i could steer my presentations with my gear :D

i dont need the presentation itself on the watch, only buttons for for- and backwards (like media player remote).

any ideas on existing solutions or possible workarounds?
[Samsung Galaxy Gear] nikkobenson:
I wouldn't try this.

I cannot think of any easy and reliable way to do this. The problem is the phone doesn't have WiFi. So you can't get the phone and computer on the same network. If you could, you could use "Unified Remote" to accomplish this easily.

Possible ways to do this are with Tasker + Autoremote + Null ROM. Or Null ROM + Unified Remote + Tethering (though I'm not sure if tethering would share the device's local network with you or just it's cell network).

Problem is with either of the above 2 possibilities, there are too many parts that can fail, and you wouldn't want that happening during a presentation which is why I recommend not doing it.

---------- Post added at 01:24 PM ---------- Previous post was at 01:21 PM ----------

Actually, having said all that, look at what I found:

https://play.google.com/store/apps/details?id=cz.rozkovec.android&hl=en

If you could pair to 2 devices at the same time PC & your note 3 (null rom?) this could work for you.
[Samsung Galaxy Gear] blazespinnaker:
It'd be easy to do and it'd be pretty cool. Just install NULL rom and communicate via Bluetooth.
[Samsung Galaxy Gear] nikkobenson:
Yeah, I pretty much said that. Though I did have to do research to come to that conclusion.
[Samsung Galaxy Gear] Amdathlonuk:
I've been trying to get this to work, however I cannot get the Gear to communicate with my Laptop, so it looks like you have to play the presentation through the phone only, however you you can't install that software on the phone.

More investigation required I think.....
[Samsung Galaxy Gear] DomZH:
thank you guys for your research and input!

so first way would be to get null rom and sideload a bluetooth remote to controll directly from my watch w/o phone?

is there a way without null?:confused:

thank you so much in advance
[Samsung Galaxy Gear] nikkobenson:
The reason you'd need Null is because it allows you to be tethered to 2 devices at once. Otherwise, you'd lose the connection to your phone.

Don't be scared of Null. I was, but I really wanted tasker and autovoice/autoremote so I dove in. Null comes with the stock launcher so you're actually not losing anything. You have all of the same features you have now, plus much much more.
[Samsung Galaxy Gear] fOmey:
This is possible using tasker & autoremote.. Do some research on the two apps.
[Samsung Galaxy Gear] DomZH:
thank you man!! this helps me a lot, especially that you told me about keeping the stock launche. i was scared because i did not wanted to have tiny icons and fiddly touch controlls on the gear like on a cheap 50 dollar china watch.

i will try it :)
[Samsung Galaxy Gear] nikkobenson:
Yeah. I had the same worries. Good luck. You're going to kick butt switching slides with your watch. James Bond style.
[Samsung Galaxy Gear] kps_foo:
Our product has Pebble support but we are thinking of adding more smartwatch support now that Android Wear has been announced. Check out SlideCinch at www.slidecinch.com.

Disclaimer, I am the Developer of SlideCinch and it is still in alpha.
[G2 Q&A, Help & Troubleshooting] jackBauersen:
Is there any way to change the function of the home button? In the LG stock rom the recent apps is activated by holding down the home button. I can't seem to find anything about it in the CM 10.2 rom. I can only add a recent apps button but I'd rather have it all-in-one.
[G2 Q&A, Help & Troubleshooting] danial.aw:
Use G2 xposed module

Sent using LG D802 on Bell Canada...

Like a Baws!
[G2 Q&A, Help & Troubleshooting] fma965:
wont that not work on AOSP Based roms?
[G2 Q&A, Help & Troubleshooting] danial.aw:
Hmm oh not sure about AOSP actually... depending on the rom they usually have the ability to customize soft keys.... otherwise there are other xposed mods that let as well...

Sent using LG D802 on Bell Canada...

Like a Baws!
[G2 Q&A, Help & Troubleshooting] fma965:
He is using Cyanogen Mod

Pretty sure if you hunt around the settings you will find the option you want.
[Miscellaneous Android Development] Free Radical:
Updated stock firmware based on 4.1.019.P1.131202.7268I

(SPICE_Mi-496_IND_VER9.0_131202_1619)

Disclaimer:

Please note that for all purposes, consider your warranty void after flashing this firmware. This thread is for information purposes only and I am not responsible for any damage/loss due to the use of the information posted herein. When in doubt, DO NOT FLASH.

Make a backup before proceeding with any of this.

This is based on the stock firmware pre-installed on the Indian version of Yulong Coolpad 7268 (7268I).

Changes:

init.d support added to kernel

Bulk message fix

Bloatware removed

Swapped internal and external storage for optimal usage.

External storage mounted as default /sdcard,

Internal sdcard mounted as /sdcard/internal_sd. I have modified the framework so that both can still be used in USB Mass storage mode.

360 degree rotation

Center clock with battery moved to left corner

Startup/shutdown sound disabled

Deodexed

Zipaligned

Prerooted with latest supersu binary

Updated Google Apps installed in /data

build.prop mods

Customized MiHome launcher with xposed mods​

Instructions:

You first need to flash the Chinese CWM recovery

Copy the zip to /sdcard

Reboot in recovery mode (adb reboot recovery)

Wipe /data and /cache (optional since I have added it to the update script as well, so keep a backup of your data) > in Chinese recovery menu, choose option 4 then option 1

Install zip from /sdcard (If you are using an external sdcard like me, from Chinese recovery menu, choose option 2 from main menu and then option 1, locate the zip file in your sdcard and flash it.)

Reboot phone (adb reboot or option 1 from main menu). Please note that the phone will take a minute to reboot from the recovery menu due to some bug in the Chinese recovery)

Stand by and the phone will boot up anew.

All the Spice preloaded bloatware/crapware apps have been removed.

You will have to reinstall play store.

You have got root :)

V9 Firmware

V8 Firmware

Previous firmware

Credits:

[MENTION=2733506]vivek.krishnan[/MENTION] for the link to V8 stock firmware

[MENTION=5565582]Gaurav_007[/MENTION] for the link to V9 cwm backup
[Miscellaneous Android Development] Free Radical:
Updated.

Kindly post any bugs in this firmware here if you want me to attempt to fix them.
[Miscellaneous Android Development] AndroZeek:
Stock Rom

Will you please upload Stock Rom.
[Miscellaneous Android Development] Free Radical:
If by stock you mean in the format Spice has provided, its already uploaded here
[Miscellaneous Android Development] love4chat:
Nice Development On Stock Rom...
[Miscellaneous Android Development] Free Radical:
If anyone has the link to the latest v9 update from Spice dated 02.12.2013 kindly pm / post the link and I would gladly modify it.
[Miscellaneous Android Development] ishan bhanot:
Hey dude google play isnt working in this rom.....
[Miscellaneous Android Development] Free Radical:
Just Google and download the latest version