yashsingh1/xdaforums huggingface dataset:
[Sony Xperia Z Ultra] LordManhattan:
Hmm, i have no idea. I think it "pops up" when you activate tablet mode. I know that CM supports it though, but since GPe build is strictly made for the ZU, Sony may have removed the feature (i can't prove it though).
[Sony Xperia Z Ultra] megapimp:
I just switch from a samsung galaxy note 2 and I was telling the people that know me with phones then I think I just found the perfect phone and rom. So far I love the Sony rom and phone. I

don't know what people see in half ass samsung products. Even the little things as just adjusting the cursor with the magnification glass is so awesome
[Sony Xperia Z Ultra] golfinggino:
Not me I couldnt leave the Sony ROM fast enough and have no intention of going back - currently running the gpe ROM and it is almost perfect
[Sony Xperia Z Ultra] golfinggino:
Lol yes it is my opinion and I'm sticking to it
[Sony Xperia Z Ultra] shaolin95:
No idea what you found so wrong with it..but oh well, thats life....
[Sony Xperia Z Ultra] dannejanne:
I agree with OP.

Sony is the only Android software design that does actually look very professional, modern and clean. No CM ROM (or any other manufacturer skin), and I mean no one looks as good and fresh in my opinion even counting the countless themes available for CM.

Sony has done it all right. Bright and right in time. I will keep stock forever on this beautiful beast.

It's also add fluid as my G2 is with Vanilla KitKat. Definitely impressed.
[Sony Xperia Z Ultra] shaolin95:
I agree with you on every point! I dont have anything against CM or AOSP, in fact, I run that on my tablet as it is by far better than the stock rom there.
[Sony Xperia Z Ultra] ronald_loulan:
The battery life is good too... :highfive:
[Sony Xperia Z Ultra] dannejanne:
Yep seems so =)
[Sony Xperia Z Ultra] iBuzman:
Agreed. Sony better than cm.. And not only that, timely too (how many other devices are on their third update of 4.3 with 4.4 already in testing? Conceivablely we may be on 4.4 before cm irons out it's 4.4 bugs).
[Sony Xperia Z Ultra] blueether:
that would be nice, although slimkat and GPe are pretty good
[Sony Xperia Z Ultra] jutley:
I have been up and down like a flaming yoyo changing roms climbed the highest mountain in search of the ultimate rom you know the GPE rom but i still came back to official sony rom i quite don't know why but i do know that i feel more comfortable with it.
[Sony Xperia Z Ultra] Ryland Johnson:
From a medical observation I can but write that you are suffering an acute case of 'good taste syndrome' and there is no cure for this. As to your mental state any of us who purchase a mobile phone this size has to have some sort of issues but then again they are not contagious so we are fine. :silly:

Ryland :good:
[Sony Xperia Z Ultra] brashmadcap:
haha I'm just really big and tall so it suits me. Not nearly this big, but it should give you an idea of what I'm talking about: http://www.reddit.com/r/shaqholdingthings
[TouchPad Development] _Dorregaray_:
I'm creating this thread to let you know about the progress of getting the camera to work on 3.x kernel.

I'm using 3.4 kernel but the changes should be easily applicable for 3.0 kernel as well.

The goal is to have a functional camera driver using ION memory allocator. Unfortunately the Qualcomm's proprietary libs we have for Touchpad relies on now deprecated PMEM allocator.

What is working:

- preview,

- taking pictures,

What is not working:

- panorama,

- video recording,

- skype.

Sources:

https://github.com/Dorregaray/android_kernel_hp_tenderloin/tree/kitkat-cam

https://github.com/Dorregaray/camerahal/tree/cm-11-ion
[TouchPad Development] _Dorregaray_:
reserved
[TouchPad Development] nikos5800:
dorregaray you are the man!!

many thanks for the amazing work
[TouchPad Development] puhleez:
As a Rezound owner, I follow the xda community for it and they came up with a hybrid situation where they were still able to use the pmem blobs/drivers for the camera while running under an ion based 3.0 kernel. Worked really well. Something to consider for the short term?
[TouchPad Development] _Dorregaray_:
I have such configuration right now, but after I'll fix some issues I have I want to get rid of pmem and get it working fully using ION if possible. That will require replacing some proprietary Qualcomm libs with the ones supporting ION.
[TouchPad Development] nevertells2:
Just want to be clear. If you get this working, it should work on any 3.xx kernel including J.C. Sullins CM10.1 experimental 3KERN build?
[TouchPad Development] _Dorregaray_:
If I will get it working it shouldn't be hard to apply the changes to the 3.0 jcsullins kernel.

In fact the reason I'm working on 3.4 kernel is that the flintman has released a kitkat no data/media build with this kernel.
[TouchPad Development] nevertells2:
That's interesting. I thought I read that he was switching over to data/media. Where did you see that he is not doing data/media?

I found this that he posted Jan.7th:

"I have moved the development to a new forum as i have changed over to data/media and don't want confusion on what is what. Posted a new update remember requireds data/media now."
[TouchPad Development] flintman:
That is true in order to fix the Play store issue i was having.
[TouchPad Development] _Dorregaray_:
Yes, but I'm running his old build and just replacing the kernel and camera driver with the ones I have built. I just don't want to switch to data/media images to be able to easily switch back to the CM9 or CM10 builds not losing anything
[TouchPad Development] nevertells2:
Smart move! I personally don't see enough benefit in data/media to endure the hassle of setting up my TP to be able to install a data/media build.

J.C. Sullins CM10.1 with the 3.xx kernel works great for me. Getting the camera and bluetooth working would be awesome!
[TouchPad Development] _Dorregaray_:
i'm proud to announce that I got taking pictures working
[TouchPad Development] googlephone:
Dorre, congrats, you are the man..

Jcsullins got BY working with 3.0 kernel and now you made big progress on camera which means we can have fully working touchpad with the new 3.0 kernel. Thank you for your continuous work on the touchpad.
[TouchPad Development] woodytrain:
WooHoo! Good job. Hope camera functionality will be coming to CM11 soon.
[TouchPad Development] hack4er:
ohh! sir you are really doing great job

hey touchpad users you are very lucky guys for having great dev like sir tomasz

with my best regards :good:also sorry for bad english :o

EDİT: ı send to pm sir maybe you can look
[TouchPad Development] _Dorregaray_:
There's problem with recording - the recorder stops receiving video frames after processing 5 of them. As workaround I'm enqueing the preview frames for recording. Bu the resulting record is in blue tint.
[TouchPad Development] suzib6sw:
Dorregary.. you are the man! Well done Sir.

Look forward to seeing your results.. Congratulations!
[TouchPad Development] k4ever:
Bluetooth already works on J.C. Sullins' latest CM10.1 3.xx build...
[TouchPad Development] woodytrain:
Replying to a post two weeks old, I suspect you meant "now works", rather than "already works". And the same is true now in most the other recent tenderloin builds (including CM11.x) as jcsullins BT fixes have been merged.

So next up is camera support in kernel 3.x builds.
[TouchPad Development] k4ever:
Oops! Did not notice the date.
[TouchPad Development] nevertells2:
Yup, that's usually what happens when I post something like that. A few days later, J.C. surprises is all with an update. Although the Bluetooth is not perfect, certain devices don't get along with it and for some reason, I can only receive files sent to the TouchPad, not send any to other devices. I have tried to send to a Samsung GS3 and Asus Infinity. It finds and pairs with them fine. I can send files back and forth between the Infinity and the GS3 just fine. Limited Bluetooth is not a deal breaker for me. All we need now is Dorregaray's camera commits merged. And BTW, I did see around a 30% increase in my Quadrant score from around 7000 to 11000.
[TouchPad Development] woodytrain:
Camera status on CM11-3.0 kernel vs other KitKat ROMs?

Anyone aware if the new camera code has been integrated into any of the TouchPad 4.4.x ROMs and is working?

Curious at what might be holding back camera support in CM11-3.0 kernel? If I'm reading it right, Github shows the camera code in Milaq's device and kernel repository, but as of 2/10 nightly much of it yet to be committed?
[TouchPad Development] _Dorregaray_:
I've posted the code for 3.0 kernel to milaq. I haven't tested it - just verified if it compiles. Unfortunately the camerahal is not working on milaq's build and I have no possibility to debug this issue on my device.

So you can check if you have /system/lib/hw/camera.msm8660.so (or /system/lib/hw/camera.tenderloin.so) in your build and check the logcat from your device startup (look for a camera word) and check the /dev/pmem_adsp existance and permissions. Maybe you will find the reason why it's not working there.
[TouchPad Development] vshzR:
I will try and see if I can get all of that for you since no one has replied... Try
[TouchPad Development] suzib6sw:
[MENTION=2459574]dorregaray[/MENTION]

/system/lib/hw/camera.tenderloin.so exists on my TP but /dev/pmem_adsp does not.. only pmem_audio. Am checking the logcat once I can finf out how to do it in catlog..

Edit..

Ok.. from the Catlog logcat.. im seeing

02-12 09:54:05.579 I/run-parts(136): Could not get context of /data/media/0/DCIM/Camera: No data available

02-12 09:54:06.320 I/CameraService(148): CameraService started (pid=148)

02-12 09:54:06.360 I/CameraService(148): Loaded "Tenderloin CameraHal Module" camera module

02-12 09:54:06.360 I/CameraHAL(148): camera_get_number_of_cameras: number:0

02-12 09:54:35.178 W/PackageManager(482): Not granting permission android.permission.BIND_WALLPAPER to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)

02-12 09:54:35.178 W/PackageManager(482): Not granting permission android.permission.PREVENT_POWER_KEY to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)

02-12 09:54:37.050 W/PackageManager(482): Not granting permission android.permission.BIND_WALLPAPER to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)

02-12 09:54:37.050 W/PackageManager(482): Not granting permission android.permission.PREVENT_POWER_KEY to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)

Does this help at all ?
[TouchPad Development] _Dorregaray_:
so it probably does not work because of missing /dev/pmem_adsp...
[TouchPad Development] woodytrain:
I also do not have /dev/pmem_adsp

Attached is a related Catlog snippet

(CM11-3.0kernel-tenderloin 02-10-14 Nightly)

Note: Catlog is recording (and NovaLauncher is running) when launching camera (and wifi disabled):

Side question as to the contents of the log snippet...any idea as to source of the references for "Awesome Player". I have MX Player installed but not AwesomePlayer app. Is that something related to the camera app, which I assumed is bundled with CM11?
[TouchPad Development] _Dorregaray_:
Probably my kernel patch has missed something and there's no /dev/pmem_adsp created. Unfortunately I'm not able to debug and fix this issue. Sorry guys.
[TouchPad Development] marcustaz:
build.board: tenderloin

build.bootloader: unknown

build.brand: HP

build.cpu_abi: armeabi-v7a

build.cpu_abi2: armeabi

build.device: tenderloin

build.display: cm_tenderloin-userdebug 4.4.2 KOT49H 08a8f489c6 test-keys

build.fingerprint: hp/hp_tenderloin/tenderloin:4.4.2/KOT49H/937116:user/release-keys

build.hardware: tenderloin

build.host: exnet.me

build.id: KOT49H

build.manufacturer: HP

build.model: TouchPad

build.product: touchpad

build.radio: unknown

build.serial: H6LG9OIH85IHTB0J793TDCGUFPAD477O

build.tags: test-keys

build.time: 1392261539000

build.type: userdebug

build.user: jenkins

version.codename: REL

version.incremental: 08a8f489c6

version.release: 4.4.2

version.sdk_int: 19

02-13 08:44:00.271 E/com.amazon.mp3/com.amazon.identity.auth.device.utils.DeviceTypeHelpers(4485): Device code is invalid. Device appears to be configured incorrectly.

02-13 08:44:14.625 E/AwesomePlayer(146): LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec

02-13 08:44:14.635 E/AwesomePlayer(146): LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec

02-13 08:44:14.725 E/AwesomePlayer(146): LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec

02-13 08:44:14.735 E/AwesomePlayer(146): LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec

02-13 08:44:14.975 E/CameraService(146): CameraService::connect X (pid 4952) rejected (invalid cameraId 0).

02-13 08:44:14.975 E/CameraHolder(4952): fail to connect Camera:-1, aborting.

02-13 08:44:14.975 E/CAM_PhotoModule(4952): Failed to open camera:0

Not sure this will help. My knowledge is limited. Dorregaray, thank you for all your hardwork!!
[TouchPad Development] shumash:
AwesomePlayer

It's part of the Stagefright playback engine:

http://freepine.blogspot.com/2010/01/overview-of-stagefrighter-player.html
[TouchPad Development] koalala:
Hi, there is a point that I don't understand, why do you keep this in board-tenderloin.c in reserve_pmem_memory function:

#ifdef CONFIG_ANDROID_PMEM
#ifndef CONFIG_MSM_MULTIMEDIA_USE_ION
reserve_memory_for(&android_pmem_adsp_pdata);
reserve_memory_for(&android_pmem_smipool_pdata);
reserve_memory_for(&android_pmem_pdata);
#endif
reserve_memory_for(&android_pmem_audio_pdata);
msm8x60_reserve_table[MEMTYPE_EBI1].size += pmem_kernel_ebi1_size;
#endif

According to your other modifications, it should be:

#ifdef CONFIG_ANDROID_PMEM
#ifndef CONFIG_MSM_MULTIMEDIA_USE_ION
reserve_memory_for(&android_pmem_smipool_pdata);
reserve_memory_for(&android_pmem_pdata);
#endif
reserve_memory_for(&android_pmem_adsp_pdata);
reserve_memory_for(&android_pmem_audio_pdata);
msm8x60_reserve_table[MEMTYPE_EBI1].size += pmem_kernel_ebi1_size;
#endif

No ? It would explain "pmem: Cannot allocate from reserved memory for pmem_adsp" since the memory is not necessarily reserved. However this is strange because it would mean that the value of CONFIG_MSM_MULTIMEDIA_USE_ION is different when compiling your kernel and milaq's one.
[TouchPad Development] _Dorregaray_:
The CONFIG_MSM_MULTIMEDIA_USE_ION value is the same - I have it defined as well. On the kernel I've been using for the camera work it has been working even when not reserving the memory for pmem_adsp.

You can try this change and see if it will solve the problem for you.
[TouchPad Development] koalala:
I don't I have time to try it but if someone can try compiling 3.0 firmware with this change. I would be grateful to know the result. Maybe 3.0 is not able to allocate the memory if the area is not reserved, contrary to 3.4. But I think it would be more logical to reserve the area in the 3.4 kernel too, even if it's working without it.
[TouchPad Development] woodytrain:
Anyone here know of someone with abilities to generate a test build? Getting the camera to work on CM11-K3.0 and CM11-K3.4 would be the cats meow. I sure hope Milaq is aware of this thread :fingers-crossed:
[TouchPad Development] invisiblek:
FYI: 3rd party camera apps work, the built in cm camera app is doing something that our HAL doesn't like.
[TouchPad Development] woodytrain:
Am I corect to assume you only are referring to your CM11-3.4kernel ROM build, and not Milaq's CM11-3.0kernel ROM build?

I have installed latest CM11-3.0kernel nightly and tried six third party camera apps, as well as the included camera app, but none work. Same message "can't connect to camera". Any ideas?
[TouchPad Development] invisiblek:
Oh, yea. Lol
[TouchPad Development] suzib6sw:
[MENTION=2606483]dorre[/MENTION]gary

With Milaq's 3.0 2/20/2014 build, the /dev/pmem_adsp is now present which it wasnt before. The permissions are permissions crw-rw----
[TouchPad Development] koalala:
Can you provide a logcat please ? My patch fix the generation of /dev/pmem_adsp on kernel 3.0 but apparently there is still another problem.
[TouchPad Development] suzib6sw:
[MENTION=621394]koalala[/MENTION]

Hopefully , i have attached a logcat that contains the info you need.. :)
[TouchPad Development] woodytrain:
Below are common catlog entries after lauching camera and then observing "Camera error: Can't Connect to Camera"

02-20 14:59:26.811 E/CameraService( 147): CameraService::connect X (pid 2029) rejected (invalid cameraId 0).

02-20 14:59:26.811 W/CameraBase( 2029): An error occurred while connecting to camera: 0

02-20 15:15:30.597 E/CameraService( 147): CameraService::connect X (pid 2942) rejected (invalid cameraId 0).

02-20 15:15:30.597 W/CameraBase( 2942): An error occurred while connecting to camera:

More complete catlog excerpts attached.
[TouchPad Development] _Dorregaray_:
You need to get the logcat from start of the system - it seems that the camerahal library is not being loaded during startup.
[TouchPad Development] woodytrain:
02-21 00:30:47.444 I/CameraService(147): CameraService started (pid=147)

02-21 00:30:47.484 I/CameraService(147): Loaded "Tenderloin CameraHal Module" camera module

02-21 00:30:47.484 I/CameraHAL(147): camera_get_number_of_cameras: number:0
[TouchPad Development] koalala:
It would be really better with a complete logcat from the boot. A complete logcat looks like that (not the same rom here):

http://pastebin.com/MyfU2DDU

You can see occurences of the camera at different places.
[TouchPad Development] woodytrain:
The above and what was presented in my previous catlog excerpts (from when I launch the camera app) are the only catlog entries containing "camera".

From your example:

My catlog doesn't show these entries.
[TouchPad Development] suzib6sw:
Hopefully this time

Its quite long
[TouchPad Development] woodytrain:
FYI: I play it safe and avoid posting full catlogs. If I have to I can go thru the 3000+ line file and remove personal identifiable info, but wish to avoid.

In the meantime, below are catlog entries which may be relevant, including ALL entries flagged as "error" within the first 400 lines of catlog:

Note the entry with "camera_get_number_of_cameras: number:0".

Invisiblek stated third party camera apps are working on his CM11-Kernel3.4, maybe can get some ideas from him?

See the ROM info in this post: http://xdaforums.com/showthread.php?t=2579431

Maybe those guys can provide a few hints.

Wish I could be more help on this.
[TouchPad Development] _Dorregaray_:
ok, so what returns:

ls -l /dev/msm_camera

ls -l /system/lib/hw/
[TouchPad Development] koalala:
Actually, /dev/video20 is not created in the milaq ROM... This device should be generated when loading MT9M113 sensor. I checked for /dev/msm-camera but I don't remember ... I think this device is not here but I'm not 100% sure.
[TouchPad Development] suzib6sw:
there is no msm_camera in /dev

there is a /system/lib/hw/camera.tenderloin.so with -rw-r--r-- permissions and its 108196 bytes
[TouchPad Development] koalala:
I spent some time checking the patches,

In, https://github.com/milaq/android_kernel_hp_tenderloin/blob/cm-11.0/arch/arm/mach-msm/board-msm8x60.c

is not called for tenderloin.

There is no specific structure for tenderloin like in 3.4 (static struct platform_device *tenderloin_devices[] __initdata). The current patch only adds camera support for rumi and sim platform. Tenderloin seems to use the devices from surf (see line 14170). I have commited a patch, waiting for milaq to try it.

I'm not really sure since the code in board-msm8x60.c is a real mess compared to 3.4 or 2.6 ... It should really be cleaned to progress faster (but i'm not volunteer).
[TouchPad Development] woodytrain:
Ditto.
[TouchPad Development] _Dorregaray_:
You're probably right. I've just checked if the patches compiles but didn't check if the driver actually works - I'm using 3.4 kernel. Thanks for finding it.
[TouchPad Development] woodytrain:
Were the new commits included in Milaq's 02-23 nightly? I installed and no change. Also after installing the nightly my nexus camera icon is now missing. See my report here:

http://xdaforums.com/showpost.php?p=50553888&postcount=1027

Would another catlog excerpt help?
[TouchPad Development] woodytrain:
Had some issues with milaq's updater install process. Anyway after I did a manual flash of 02/23 nightly, the same camera issues occur. And the catlog shows exact same entries as previously posted.
[TouchPad Development] koalala:
I'm patching little by little, I found another problem today. The I2C device wasn't registered. In kernel 3.4, I2C_SURF is used. In 3.0, I2C_TENDERLOIN devices are used. The camera was registered only for I2C_SURF and not I2C_TENDERLOIN on kernel 3.0.

https://github.com/milaq/android_kernel_hp_tenderloin/pull/5/files

I hope that one day it will work. Maybe I should start cleaning board-msm8x60.c to remove useless parts... But I can't really do that since I don't have a powerful enough computer to compile and I can't commit big changes without testing.
[TouchPad Development] marcustaz:
I don't know anything about coding but I certainly have the hardware to compile. If no one more knowledgeable than I can help, let me know and I'll do my best to help out. Thank you for trying to get it working.
[TouchPad Development] koalala:
Hi, my last patch is still not enough to get the camera working but we are very close. Now, the kernel tries to load the camera sensor :)

<6>[ 1.039642] i2c /dev entries driver
<6>[ 1.040802] Linux video capture interface: v2.00
<6>[ 1.040924] usbcore: registered new interface driver uvcvideo
<6>[ 1.041015] USB Video Class driver (v1.1.0)
<4>[ 1.041412] +++ config_camera_on_gpios_web_cam_mt9m113
<4>[ 1.041809] config_camera_on_gpios_web_cam_mt9m113:enable the regulator votg_lvs0 succeed
<4>[ 1.042480] config_camera_on_gpios_web_cam_mt9m113:enable the regulator votg_vreg_l11 succeed
<4>[ 1.042572] --- config_camera_on_gpios_web_cam_mt9m113
<3>[ 1.087982] qup_i2c qup_i2c.1: QUP: I2C status flags :0x1343c8, irq:185
<3>[ 1.088073] qup_i2c qup_i2c.1: I2C slave addr:0x3c not connected
<4>[ 1.088165] mt9m113_i2c_rxdata Addr:0x3c failed 0 times!
<3>[ 1.098358] qup_i2c qup_i2c.1: QUP: I2C status flags :0x1343c8, irq:185
<3>[ 1.098449] qup_i2c qup_i2c.1: I2C slave addr:0x3c not connected
<4>[ 1.098510] mt9m113_i2c_rxdata Addr:0x3c failed 1 times!
<3>[ 1.108703] qup_i2c qup_i2c.1: QUP: I2C status flags :0x1343c8, irq:185
<3>[ 1.108825] qup_i2c qup_i2c.1: I2C slave addr:0x3c not connected
<4>[ 1.108886] mt9m113_i2c_rxdata Addr:0x3c failed 2 times!
<3>[ 1.119079] qup_i2c qup_i2c.1: QUP: I2C status flags :0x1343c8, irq:185
<3>[ 1.119171] qup_i2c qup_i2c.1: I2C slave addr:0x3c not connected
<4>[ 1.119262] mt9m113_i2c_rxdata Addr:0x3c failed 3 times!
<3>[ 1.129455] qup_i2c qup_i2c.1: QUP: I2C status flags :0x1343c8, irq:185
<3>[ 1.129547] qup_i2c qup_i2c.1: I2C slave addr:0x3c not connected
<4>[ 1.129638] mt9m113_i2c_rxdata Addr:0x3c failed 4 times!
<4>[ 1.129699] mt9m113_i2c_rxdata failed!
<4>[ 1.129730] mt9m113_sensor_probe mt9m113_i2c_read failed
<4>[ 1.129821] /home/android/cm11/kernel/hp/tenderloin/drivers/media/video/msm/mt9m113.c mt9m113_sensor_probe:878 failed
<4>[ 1.130462] +++ config_camera_off_gpios_web_cam_mt9m113
<4>[ 1.130798] config_camera_off_gpios_web_cam_mt9m113:disable the regulator: votg_lvs0 succeed
<4>[ 1.131195] config_camera_off_gpios_web_cam_mt9m113:disable the regulator: votg_vreg_l11 succeed
<4>[ 1.131317] --- config_camera_off_gpios_web_cam_mt9m113
<3>[ 1.131408] msm_sync_init: failed to initialize mt9m113
<4>[ 1.131469] msm_camera_mt9m113: probe of msm_camera_mt9m113.0 failed with error -5
<6>[ 1.132080] msm_gemini_init gemini: success

I'm doing some tests right now. This bug already occured in CM9 and was related to hardware at that time. I have bought a new computer yesterday so it's easier now but thanks for your offer marcustaz.