yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] lagalaga:
Random fun facts:

Z2 SemcPowerSaveModule can apparently limit camera FPS to save power/cope with thermal stress. No such thing in Z1

data/com.sonymobile.cameracommon/databases/camera_status.db stores the camera status, but I believe that is more of a cache and not the camera configuration. The corresponding class is CameraCommon/smali/com/sonymobile/cameracommon/provider/CameraStatusProvider.

...> ;
1|power_off|0|0x0|0x0|0x0|0|0|off|off|off|off|off|off|off|off|off
sqlite> .dump
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE android_metadata (locale TEXT);
INSERT INTO "android_metadata" VALUES('de_DE');
CREATE TABLE status (_id INTEGER PRIMARY KEY AUTOINCREMENT, device_status TEXT, camera_id INTEGER, preview_resolution TEXT, picture_resolution TEXT, video_resolution TEXT, preview_max_fps INTEGER, video_recording_fps INTEGER, burst_shooting TEXT, time_shift TEXT, art_filter TEXT, face_identification TEXT, face_detection TEXT, scene_recognition TEXT, object_tracking TEXT, video_stabilizer TEXT, photo_light TEXT);
INSERT INTO "status" VALUES(1,'power_off',0,'0x0','0x0','0x0',0,0,'off','off','off','off','off','off','off','off','off');
DELETE FROM sqlite_sequence;
INSERT INTO "sqlite_sequence" VALUES('status',1);
COMMIT;
sqlite> select video_recording_fps from status;
0

I decompiled the Z2 apks (all of them) and found nothing interesting. Might just be me.

I looked at some of the .so files again - it would be interesting to have some kind of dependency graph.

Some random strings and greps:

aga@moar:/mnt/vendor/lib$ grep -ri q-fps-range-values *
Binary file lib-imscamera.so matches
laga@moar:/mnt/vendor/lib$ grep -ri preview-fps-range
Binary file lib-imscamera.so matches

strings mm-qcamera-app | grep -i -E '(hfr|fps|frame|rate|high)'

libcammw

laga@moar:~/download/sirius$ arm-none-eabi-readelf -a -D ./lib/libcammw.so | grep NEED
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
0x00000001 (NEEDED) Shared library: [libcutils.so]
0x00000001 (NEEDED) Shared library: [libmmcamera_interface.so]
0x00000001 (NEEDED) Shared library: [libmmjpeg_interface.so]

./lib/libmmcamera_interface.so
doer
libcammw.so

cammw_sensor_get_caps
imx200_get_sensor_param

00009240 T cammw_camera_get_caps
0000b74c T cammw_camera_get_config
0000a8a8 T cammw_camera_get_port_info

cammw_get_info+0xd94

mm_camera_query_capability+0x54
[Sony Cross-Device General] lagalaga:
I have a feeling that the magic is in libcammw.so. Replacing it leads to crashes related to liboemcamera.so and libmmcamera2_isp_modules.so.

In the log, I see this

06-01 08:52:51.084 10074 10135 E somc-camera-driver: SOCAM_ERR: sony_read_parameterfile: sony_read_parameterfile: FILE data_size too large (41152)
06-01 08:52:51.084 10074 10135 E somc-camera-driver: SOCAM_ERR: sony_read_parameterfile: sony_read_parameterfile: ERROR! param_version=0 != 263
06-01 08:52:51.084 10074 10135 E somc-camera-driver: SOCAM_ERR: sony_read_parameterfile: sony_read_parameterfile: cannnot a

Replacing the camera firmware again: no luck. Replacing the related libs: no luck.

In fact, even after removing the modifications, camera won't open anymore. I have to restore the system partition. Weird. So my last trial, replacing liboemcamera.so and libmmcamera2_isp_modules.so might have been irrelevant as the eeprom could have been messed up. Perhaps the camera needs to be powered down longer for that to unstick, but that's just a hypothesis.

Next step: attach a debugger to system/bin/mm-qcamera-daemon - that's where libcammw.so is used.

Next step after that: replace _all_ the *camera*so and *cal*so.
[Sony Cross-Device General] lagalaga:
The GDB build in my NDK6 can't handle the shared object implementation on android. It does not see the libcammw.so.so stuff when attached to the camera daemon. I can't even continue the camera daemon after attaching. This is bull***.
[Sony Cross-Device General] adam20115:
Guys I was wandering if this helps you at all? As this says 120fps :)
[Sony Cross-Device General] olokos:
Check the mediainfo of that file. I bet it's not 120fps if that's from using existing mods. If you can get that overlay or you know at least how to got that overlay just like in the previous mods, then let us know. [MENTION=5491189]xperiaz2[/MENTION] [MENTION=4340984]krabappel2548[/MENTION]

If any of you wonder what would happen if you flash just the Z2 rom without kernel on the Z1,then it's a bootloop.

Wysłane z mojego C6903 przy użyciu Tapatalka
[Sony Cross-Device General] Riyal:
Guys try checking out camera.msm8794.so & camera.qcom.so. Also have a look at this thread.

http://xdaforums.com/showthread.php?t=2548974

It's from a LG G2 thread. They manage to port 4k & 120fps. The exact patch that implemented the feature was v2.0.6 link here. http://d-h.st/QhP
[Sony Cross-Device General] lagalaga:
Won't help, unfortunately. Something deeper in the system does not support 120fps.

Stuff I did today:

I looked at the available implementation of a QCOM camera HAL somewhere in the Android source code: https://android.googlesource.com/platform/hardware/qcom/camera

I traced the methods to obtain the available frame rates.

// Set HFR
String8 hfrValues = createHfrValuesString(
m_pCapability->hfr_tbl,
m_pCapability->hfr_tbl_cnt,
HFR_MODES_MAP,
sizeof(HFR_MODES_MAP) / sizeof(QCameraMap));

In that implementation, the frame rates are queried over the V4L interface directly from the kernel. The camera HAL defines a query_capability method pointer which calls mm_camera_intf_query_capability. This in turn calls mm_camera_query_capability.

int32_t mm_camera_query_capability(mm_camera_obj_t *my_obj)
{
int32_t rc = 0;
struct v4l2_capability cap;

/* get camera capabilities */
memset(&cap, 0, sizeof(cap));
rc = ioctl(my_obj->ctrl_fd, VIDIOC_QUERYCAP, &cap);
if (rc != 0) {
CDBG_ERROR("%s: cannot get camera capabilities, rc = %d\n", __func__, rc);
}

pthread_mutex_unlock(&my_obj->cam_lock);
return rc;

}

I don't know if the code works the same on the Z1, but libmmcamera_interface.so has the same method names. The HAL is in libmmcamera_interface.so, btw, and you can just call query_capability. See the code for mm-qcamera-app:

my_cam_app->hal_lib.ptr = dlopen("libmmcamera_interface.so", RTLD_NOW);

test_obj->cam = cam_app->hal_lib.mm_camera_open(cam_id);

rc = test_obj->cam->ops->query_capability(test_obj->cam->camera_handle);
if (rc != MM_CAMERA_OK) {
CDBG_ERROR("%s: failed query_capability", __func__);
rc = -MM_CAMERA_E_GENERAL;
goto error_after_getparm_buf_map;
}

So, of course, I decided to look at the kernel. I diff'ed doomlords Z1 and Z2 kernels and there is no relevant difference in drivers/media/platform/msm.

So, relevant code in the HAL is in QCamera2HardwareInterface::initCapabilities, which obtains a cam_capability_t struct. The struct contains:

uint8_t fps_ranges_tbl_cnt; /* fps ranges table size */
cam_fps_range_t fps_ranges_tbl[MAX_SIZES_CNT]; /* fps ranges table */

uint8_t hfr_tbl_cnt; /* table size for HFR */
cam_hfr_info_t hfr_tbl[CAM_HFR_MODE_MAX]; /* HFR table */

This is the kernel-side code that handles the IOCTL:

static int camera_v4l2_querycap(struct file *filep, void *fh,
struct v4l2_capability *cap)
{
int rc;
struct v4l2_event event;

/* can use cap->driver to make differentiation */
camera_pack_event(filep, MSM_CAMERA_GET_PARM,
MSM_CAMERA_PRIV_QUERY_CAP, -1, &event);

rc = msm_post_event(&event, MSM_POST_EVT_TIMEOUT);
if (rc < 0)
return rc;

rc = camera_check_event_status(&event);

return rc;
}

The code for msm_post_event looks like it talks to an 'imaging server' in userspace.
[HTC One X] loni90:
Hi all!

Hope u guys could help me out!

Have a HTC One X that got a cracked LCD, so i cant see nothing on it. its all black.

I want to get all my files from it, and save it on my computer, but i have a pattern password on it, so it wont connect to USB mass storage mode.

Ive heard that i can ADB pull the SD card, but would anyone be so kind and write a guide.

Where do i have to start, and what commandos etc. Ive tried once, but the Command couldnt connect with my phone - dont know what i did wrong.

thanks in advance!
[Moto G Q&A, Help & Troubleshooting] Clarkiieh:
I've been having issues with CWM and Philz Recovery. CWM backs up not always fails to restore /data and Philz doesn't even backup /Data and stops the processes. TWRP does back up. And restores perfectly.

Are these known issues?

Also what's the best kernel for stock KitKat?
[Moto G Q&A, Help & Troubleshooting] nardow:
I don't know how to fix this issues with the recoveries...

Btw, if u want performance, flash the faux123 kernel, but if u want battery saving, flash the Aero Kernel.

I'm using Aero right now, and it's the best in my opinion ;)
[Moto G Q&A, Help & Troubleshooting] Clarkiieh:
Can I flash with recovery?

Om using twrp 2.7.7
[Moto G Q&A, Help & Troubleshooting] :
Yeap.
[Windows Phone 8 Q&A, Help & Troubleshooting] Zer0swe:
Dont hate me for this.

My first post here and it's for the reson that i need help with my Ativ s neo i think it's called.

I have a prototype or a non production modell that seems to be unlocked and has diagnosis app on it.

Is there a way to flash this one to basic wp8?

You might wonder why? because i cant change the language on it to Swedish, it's with English (United States) and there is no way to change it,

very hard to write sms in Swedish without Ö, Ä, Å on the phone.

I have tried to put the prewiew for developers app on it but with no success uppdating it to wp8,1.

If i restart the phone the volume goes to 30.

When i start the phone it says factory mode.

Sorry for my English but i'm a Swede, at least i'm trying. :laugh:
[Windows Phone 8 Q&A, Help & Troubleshooting] GoodDayToDie:
First of all, how'd you even get a not-for-sale device?

Second, don't waste its potential by flashing a stock ROM; those things are very handy to use hacker-types!

OK, with that said: you can get accents and diacritics (including all three of the ones you listed, plus many more) by tapping-and-holding on a given letter. There are seven options each just for A and O, which should cover everything you need.
[Windows Phone 8 Q&A, Help & Troubleshooting] Zer0swe:
Thank's for the info GoodDayToDie.
[Windows Phone 8 Q&A, Help & Troubleshooting] Zer0swe:
I got it as a gift from a friend.

Is there any possibility that-WOLF-'s fake rom with CSC would work on my device?

Reason!

I cant uppdate to wp8,1 so i'm stuck on wp8.

APN settings is no go either with my device.

like the phone and i want to use it. :D
[8125, K-JAM, P4300, MDA Vario Software Upgrading] thankins:
Wow...2.26 roms are poping up everywhere! Now the time comes to choose one. As far as your goes does it come with the ability to remove the programs you listed? As well as the ringtones and themes? I hate having all of that stuff on my phone and not using it!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] risidoro:
You cannot remove them BUT they're in ROM so they don't waste any space on your main storage. Moreover, the slipstreamed CF2 SP1 and Flash7 let you save about 6.5Mb of storage (or 2.5Mb if you install CF2 in SD card).

Anyway, choose the rom that best suits you.

Bye bye
[8125, K-JAM, P4300, MDA Vario Software Upgrading] thankins:
Thanks for the quick reply...have you noticed any bugs/problems with your ROM?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] risidoro:
No (fingers crossed).

Basically, it is the T-mobile US 2.26 ROM so it behaves just like any other t-mobile 2.26 ROM. I only added some files (i didn't touch any of the original files).

Try it if you want but remember: if you have a G3 phone then you must have both IPL and SPL version 2.xx to install this rom.

Bye
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Dr Puttingham:
Sounds righteous dude! I'm looking forward to seeing the performance.

Thanks!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gomylle:
Hi guys.

Great work with all the custom roms. I have a problem with these english roms that i hope you guys can help me fix. I posted this in its own thread but i dont know if you guys read that som hopefully you will give me a litle of your valued time and see if you can help me out

I have been messing around with differnt rom versions on my Danish qtek 9100. There has been no new updates out in Danish for a long time and the phone is quite buggy. Anyways, i have tried multiple roms and they all seem to work well but my problem is that i need my danish keyboard to funktion with Æ Ø Å which are one my phone keyboard.

when I install the cab Default_Prodigy_Nordic_keyboard_1102.sa

from

ftp://xda-developers.com/Wizard/Extended_Roms/ExtRom_1030712_121_10410_Qtek_NOR_Ship.rar

The Æ Ø Å buttons on the keyboard works but The 4 point navigation "joystick" with the button in the middle stops working.

What can i do?

Also, how do i go about getting a danish T9

Thanks

Jacob
[8125, K-JAM, P4300, MDA Vario Software Upgrading] anothersmith:
I'm interested in this ROM however I need a refresher regarding loading extended roms such as (ftp://ftp.xda-developers.com/Wizard/Extended_Roms/cingular-ExtROM.zip) I've been spoiled with Roms that have always inculded the Cingular settings (thanks to Summiter).

Looks like this might be a better cingular setting file to run - http://xdaforums.com/viewtopic.php?t=61619

Is it as easy as copying to the SD card and executing?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] yowzator:
Wow, your ROM sounds great. I just flashed the Xelencin ROM, but I may redo it with yours. However, I have a question regarding the Radio version.

I just received a warrantee replacement phone from T-Mobile USA today. When I booted it up, it showed the following:

IPL 2.26

SPL 2.26

GSM 02.26.11

OS 2.26.10.2

I then flashed the Xelencin 2.26 ROM with this filename:

T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe

Upon rebooting, the following was shown:

IPL 2.26

SPL 2.26

GSM 02.25.11

OS 2.26.10.2

Your notes indicate that your ROM includes Radio version 2.25.11. Do you know what the difference is between 02.25.11 and 02.26.11?

I don't think I can get the 02.26.11 back now that I've flashed it. I didn't make a backup of the shipped ROM first.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gomylle:
I just flashed my phone from Cingular 2.26 Aku2.3 w/a2dp FULLY LOADED *BETA* to this one but i guess it did not work correctly. The phone works fine but there are no ekstra ringtone or program or anything like that. What could have happened?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ghostb:
Error 208

The rom looks very promessing, but something goes wrong... I receive an error 208. Anybody any idea what means?

Who can help the newby?

Thanks in advance!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] thankins:
I am very excited to try this, and read above about the Cingular extended rom as well, So i would install this and then run the Cingular Extended ROM to copy over some of the Cingular Settings that I may be missing?

Also what is diifference in this compared to the BETA 2.26 ROM that is out there!?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] risidoro:
I've never heard of a 2.26.11 radio stack. Maybe it was taken from some t-mobile beta rom.

However we'll never know how it performed since you overwrote it :)

Bye
[8125, K-JAM, P4300, MDA Vario Software Upgrading] risidoro:
The rom upgrade process didn't work. The rom was not installed. Try flashing the rom again.

To avoid problems you can try to extract the content of the rom executable in a folder (use winrar: right click on the exe and choose 'extract here') and run newromupdateutility_wizard_noid.exe from there
[8125, K-JAM, P4300, MDA Vario Software Upgrading] risidoro:
Re: Error 208

Sometimes the self-extracting archive doesn't work well. The problem is NOT related to the rom; it's just the self-extracting exe archive.

To avoid the problem you must extract the content of the rom exe in a folder (use winrar: right click on the exe and choose 'extract here') and run newromupdateutility_wizard_noid.exe from there.

Bye,

let me know how it goes...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] shogunmark:
thats the rom i posted, i didnt include any extra ringers or theme's yet, risidoro's rom is different
[8125, K-JAM, P4300, MDA Vario Software Upgrading] thankins:
Should you be at work...and if you are there shouldn't you be working :P
[8125, K-JAM, P4300, MDA Vario Software Upgrading] shogunmark:
i am at work shhhhh......
[8125, K-JAM, P4300, MDA Vario Software Upgrading] KTamas:
Finally a ROM with all bells and whistles. I'll try out soon and looking forward for an AKU3.2 version whenever it will be stable and working :)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] yowzator:
Dangit. I was afraid of that. I didn't even think to backup my ROMs first since when it first booted, I just looked at the number briefly and thought to myself, "Oh, it already has the latest TMobile ROMs". But I did take a moment to jot down the numbers anyway. Then, a while later, after loading the Xelencin ROM, I noticed the numbers were different.

I wonder if the Tmobile download site has an updated download, of if this version only comes with warrantee replacements...

If anyone else gets a warrantee replacement phone, perhaps we can get the new 2.26.11 radio stack. I had my MDA replaced because the stylus wouldn't stay in and kept getting lost. Anyone else with that problem could get TMoUSA to replace theirs too.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] endiz:
Hey risidoro; Great rom again =D

Any chance you will be upgrading to the 2.3 AKU and/or 3.2?

Thanks, and keep up the GREAT work.

*edit*

Stupid me, AKU 2.3 is included in this rom! But what about 3.2? Are you waiting till we get a stable rom?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gribbler:
ok now working..

I had to downgrade to CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE

then run aWizard 1.3 beta 2 to unlock.. For some reason running lokiwiz was n't able to properly unlock the CID. So. All good now
[8125, K-JAM, P4300, MDA Vario Software Upgrading] djblu:
Last chance plea for assistance of anykind!!!

Received the replacement handset today from cingular, and it's a 3g not a 4g chipset.... before I send it back is there anyone with any knowladge of how to save my aparently bricked 4g 8125???
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Mi|enko:
Well, I'm gettin' ready to install this. Downgrading from the 3.2, due to some problems I've been having. Looks like it's 50/50 with this rom. lol Some users report great success, and some report great failure. Hopefully, I'm one of the successful ones. Installin' on a G3 Vario. I'll keep y'all informed.

edit - So far, the only odd thing I notice is that I now have 3 boot screens, as opposed to 2.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] herzzreh:
Had issues with it not installing correctly... device was not CID unlocked. CID unlocked it, everything seems fine.

Most likely a coincidence, but after installing this ROM my data speed slowed to a crawl. Did the ROM cause this or is my carrier just acting up? I don't know.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] zx6r_stoppie:
Tried the install. Then fixed it

So i have not been able to unlock the CID on my G4 8125 (2.25.0001). So i gave installing the rom in 2.26 rom. It came up on the reboot to the 3 colour screen.

Once it was there i was unable to install any other rom's. I tried the one from the HTC page and no-go, as a lot of other people have experienced. I also tried MrClean.

I used the method risidoro described in his post on how to install a 2.xx rom onto a cid-locked phone to get my phone back up and running. i used the latest htc update and set the IPL and SPL to match my original one 2.25.0001 , followed the tutorial, and it came back alive.

I'd like to try and do the same thing with the 2.26 rom (run the typho5 and nb2nf), putting in 2.25.0001 for the IPL and SPL and see if it works.

Has anyone successfully done this? Or have any other suggestions as to how to get my G4 either CID unlocked so i can do this or is there anyother way?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jpmche:
Re: Tried the install. Then fixed it

Can you post a link to the procedure. I'm having the same problem a G4 rebooting to the 3 colour screen.

Thanks

Javier
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jpmche:
Re: Tried the install. Then fixed it

Never mind. I figure it out. It's working now.

Has anyone successfully installed rom 2.26 in a Cingular 8125 (G4)?

Thanks
[8125, K-JAM, P4300, MDA Vario Software Upgrading] herzzreh:
GPRS Speed Issue

I'm having GPRS speed issue with this ROM... Using any other ROM I average 130 kbit/sec but with this ROM I can't get past 10 kbit/sec.

Hmm..
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Chargin:
Well I installed in on my G3 Imate, its all on there and everything works BUT none of the extras are in there... no ringtomes, no extra programs etc etc, there is a different skin on the phone dialer to what Ive seen before but thats about it.

From what Ive read Im not the only one to have this problem, what can it be? Is it worth flashing again?

Before this flash I had the AKU clean rom.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] herzzreh:
To save you from reading the whole thing... CID unlock your device.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Chargin:
Heh, Ive come back to relay my findings and what you say correct..

You need to downgrade to

CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe

Then run the unlock program 2b, then flash to this rom, I now have all the extras from this rom. The OP should update his opening post with these details perhaps??
[8125, K-JAM, P4300, MDA Vario Software Upgrading] RpR:
I upgraded my Qtek 9100 from danish to this english without problems during update, and the ext. rom installed fine.

However, my radio isn't working with this radio rom :(

Any suggestions?

Edit: Just realised this killed my danish keyboard aswell. Any way of patching it to get it back?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] maxshevelev:
Hello,

Not sure if this was discussed before...

I discovered an annoying problem with this rom. If I use GPS software with bluetooth GPS receiver (I guess any software that uses bluetoth port) and make call via bluetooth headset bluetooth turns off. Voice tag is recognized fine but when it switches to phone application to dial number bluetooth turns off and phone sound is redirected to phone. I checked it serveral times. It's 100% repeatable. Incomming calls are received fine though. This happens only when GPS software is running and uses bluetooth port. If nothing uses bluetooth port voice dialing via bluetooth headset works fine.

With my old 2.17 rom I never had problems with this combination.

Anybody knows how to fix this?