yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] updateing:
Since Sony has added new v45 Adreno graphics driver in .295,I think it will be good to compile a CM-like kernel and chances are that we can fix the blue flickers in this way.However,when I mananged to get the zImage booting CM properly(no reboot),I found the screen froze at Sony logo.In the logcat I can see the system is waiting for media.audio_policy,and BootAnim,or the whole display system, isn't working.though all the Adreno libs are loaded properly and the screen param is read correctly.

Related logcat:

E/Adreno-EGLSUB( 237): <CreateImage:1837>: Offset beyond buffer size.
W/Adreno-EGL( 237): <qeglDrvAPI_eglCreateImageKHR:4637>: EGL_BAD_PARAMETER
E/GLConsumer( 237): [BootAnimation] error creating EGLImage: 0x300c
W/GLConsumer( 237): [BootAnimation] updateAndRelease: unable to createImage on display=0x1 slot=0
E/qdhwcomposer( 237): Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument

// And there are some "MDP: unknown ioctl (....)" errors in dmesg

I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
W/AudioSystem( 670): AudioPolicyService not published, waiting...
W/libc ( 236): WARNING: generic atexit() called from legacy shared library

I'm using Liquid Smooth 20140223(based on CM).And replaced the following files with stock 295.The other files are untouched.Now logcat shows nearly no error other than the ones mentioned above.

And here is how to update the Adreno libs in the system:

And I will attach my kernel config and the full logcat.I didn't save dmesg...sorry...

I'm new to porting Android...Does that mean we need new HALs or something like that?Thanks!
[Sony Xperia T, TL, TX, V] nnmka:
I do not understand in porting Android. Can ask for help in the team FXP?
[Sony Xperia T, TL, TX, V] updateing:
They should be already working on this...but any help is welcome :)
[Sony Xperia T, TL, TX, V] tilal6991:
I've already got Kitkat running with 4.3 kernel sources - still no dice with the new Adreno blobs however. See the kernel source https://github.com/chirayudesai/laughing-octo-dangerzone/tree/omni/

As for the audio policy errors - they are what's causing the bootloops - you can fix that by either removing the camera HAL or fully updating it.
[Sony Xperia T, TL, TX, V] updateing:
THANKS A LOOOT MAN! :good::laugh:
[Sony Xperia T, TL, TX, V] updateing:
I used your source to compile the kernel.When I delete /system/lib/hw/vendor-camera*,booting process moves forward(the screen dims and Xperia logo gets lit,MediaScanner runs.I can even hear SMS notification sound)but there is "InputDispatcher" log spam,indicating that some window isn't responding so further input events are ignored.But after a reboot,there seems to be no problem in the logcat,except for the MSM_FB_OVERLAY/Invaild Argument error.Still nothing displayed on screen.

One weird problem:if I use Adreno libs from CM11,DDMS will grab screenshots correctly.But if stock updated ones are used,DDMS won't grab scrnshot properly.Just some lines on black ground:the attachment shows that.

If I add back the two files from stock 4.3,audio_policy error shows again.Let's see what else should be changed...
[Sony Xperia T, TL, TX, V] tilal6991:
Well I've released a new omnirom test build which has everything working (except gps). The props repo is on my github and the patches for device configs are on omnirom gerrit.
[Sony Xperia T, TL, TX, V] updateing:
Maybe replacing the whole arch/arm/mach-msm directory with old OmniROM one will do...I fixed GPS on CM by doing so,one and a half month ago.But I'm not sure which file causes this...
[Sony Xperia T, TL, TX, V] updateing:
It occurred to me that if I leave CM11 unchanged and boot on 4.3 source,there will be "Bad OVInfo" log spam,which is the same as CM booting on previous Omni kernel...I should have tested the source with OmniROM.But why does CM change the ioctl/HALs? Related files in the kernel are the same...
[Sony Xperia T, TL, TX, V] updateing:
Well I managed to get 4.3 source working on CM/LS/... roms...Just change "struct mdp_overlay_pp_params" definition in include/linux/msm_mdp.h to

Things will be okay...
[Sony Xperia T, TL, TX, V] updateing:
Now there is the long-lasting problem...ramdom reboots...I noticed there was some Watchdog:Modem Crashed logs in last_kmsg.I tried replacing /system/etc/firmware with stock one,which resulted in a not booting phone.It got stuck after the Recovery amber light with Sony logo still on screen.ADB is not running,or to say the kernel has died - removing battery with USB plugged in doesn't make the phone shut down.Any idea to upgrade the modem software?
[Sony Xperia T, TL, TX, V] updateing:
Well I don't have enough time to test now...schoolwork is busy...sorry..
[Sony Xperia T, TL, TX, V] phhuang:
It's OK. I'll wait for it still... The CM11 is better than stock then the reboot issue would need kernel updated to help.

Sent from my Xperia V
[Sony Xperia T, TL, TX, V] silasje1:
@OP

New source have arrived:

http://developer.sonymobile.com/dow...es/open-source-archive-for-build-9-2-a-1-199/

Maybe these are somewhat easier to port :victory:
[Sony Xperia T, TL, TX, V] updateing:
Thanks~After the busy weeks I'll look into it.
[Sony Xperia T, TL, TX, V] 3clipse:
Doesnt FXP usually incorporate the new kernels after Sony releases the source blobs?

Im not sure how long It usually takes them though...
[Sony Xperia T, TL, TX, V] updateing:
Yes.They are working on fusion3 and rhine devices now.Our devices are not active :(
[Sony Xperia T, TL, TX, V] updateing:
Got a little free time...tried extract-files.sh,and new baseband is working now.Seems more stable than before...but camera & GPS & WiFi is broken.I have added new GPS blobs into proprieatry-files.txt but no use...logcat shows startFix() error...
[Sony Xperia T, TL, TX, V] tilal6991:
You can look my omnirom commits - everything is now working.
[Sony Xperia T, TL, TX, V] updateing:
OK.I will be watching them.Thkx!

(Is light sensor working? Not until I removed /lib/hw/sensors.msm8960.so and pushed stock sensors.default.so did it start to work...no sure if it was my problem only.

And it seems that the stock lights.default.so can take the place of vendor/lib/hw/lights.qcom.so and lib/hw/vendor-lights.default.so. If that's common,we can remove the unnecessary files...)
[Sony Xperia T, TL, TX, V] tilal6991:
There's no point replacing open source stuff with props if we can avoid it. As I said everything is working in OmniROM.
[Sony Xperia T, TL, TX, V] updateing:
I'll try a clean build to see if problems are solved...
[Sony Xperia T, TL, TX, V] updateing:
Okay now WiFi,GPS,light sensor and more things are working.For WiFi,we need to use the exact the same revision firmware_bin files as the driver module from CAF,otherwise there will be CheckParam error.As for the screen not lighting up issue,change two "use_dls" value to 0 in pre_hw_config.sh.And finally for the sudden death of charging LED,echo 0 > /sys/class/leds/pwr-*/use_pattern will do.

Now that's the camera...I extracted files from stock 199,synced with latest Omni source,but there's still "Waiting for service audio_policy" error.

==================

Some small thing: It seems that lights.default.so(or together with some other mandatory blobs) in 295 can work with Omni directly without wrapper.Since the stock light.so is listed in (mandatory)proprieatry files,I think there is no need to keep the wrapper file and the stock file works better(eg. Xperia Logo acts the same as stock - fade effects show properly on TX).But in 199,the wrapper is needed again...
[Sony Xperia T, TL, TX, V] tilal6991:
Well the nightlies are being built and are working fine so something wrong at your end I think.
[Sony Xperia T, TL, TX, V] updateing:
Yes,some of the bugs are device-specific.
[Sony Xperia T, TL, TX, V] updateing:
Finally I got everything working on TX...libqc-opt.so was to blame for the camera problem since it required some mysterious symbol. I replaced stock TX one with OmniROM mint nightly build one and it got fixed.Is this OmniROM one from stock mint firmware?

Thanks tital!
[Sony Xperia T, TL, TX, V] nnmka:
We can see OmniROM firmware for TX? Problem solved with a battery? This was the main problem firmware phone quickly discharged, charge lasted a very long time....
[Sony Xperia T, TL, TX, V] tilal6991:
The qc-opt is from a source I can't name I'm afraid. Its a kitkat lib though which is why it works.
[Sony Xperia T, TL, TX, V] updateing:
Charging seems to be fast...With my mobile power cube,the phone charges at current ~1.1A in flight mode. And after settling,6hrs standby in 3G network without WiFi and mobile data costs less than 2%. That's too surprising...I'll see if it's consistent.
[Sony Xperia T, TL, TX, V] updateing:
Did another test...lights.default.so in 295 is able to do the work without the wrapper,and does the work better...I'd choose it as TX's proprieatry file...
[Sony Xperia T, TL, TX, V] nnmka:
We can see a test version?
[Sony Xperia T, TL, TX, V] updateing:
I can only upload to Chinese file storage. Devhost or mediafire is too slow here...

http://pan.baidu.com/share/link?shareid=4195230183&uk=3674664492

NOTE: I haven't tested this long enough,but it's running stable for 14 hours.And you need to flash the separate elf kernel first,then the ROM,and the kernel again (because the kernel packed with ROM is not the best working one).After the phone boots up,extract all the files in modules.zip to /system/lib/modules.
[Sony Xperia T, TL, TX, V] nnmka:
Thank you, please do not delete the file, I'll upload and see the evening!

I thank you today!
[Sony Xperia T, TL, TX, V] nnmka:
Firmware does not work.

1. ) Ask the kernel via fastboot

2. ) Did wipes and installed firmware.

3. ) Turn off the phone, flashed again kernel.

4. ) Enabled phone logo appears Sony, after the black screen, it is clear that loading OmniRom, but there is no brightness. Waited about 15 minutes, the firmware does not start.

Brightness in TWRP works.

The firmware is not loaded when the lantern shine. shows that

What did I do wrong?
[Sony Xperia T, TL, TX, V] updateing:
You did nothing wrong.The new TWRP didn't save the sideloaded zip...so the file is not the latest build.If you want to get it working now ,go into adb shell and

cd /sys/bus/i2c/devices/10-0040/lcd*1

echo 0 > use_dls

cd ../lcd*2

echo 0 > use_dls

and then the screen should work.If not,press the power button to unlock it.

Thanks for your testing!
[Sony Xperia T, TL, TX, V] nnmka:
For me it is difficult .... I'll wait for the fixed version. thank you

Which mode number should I go to adb shell? Before installing the firmware?

Maybe I should wait for the corrected version. if one is?
[Sony Xperia T, TL, TX, V] updateing:
Network in my dorm is really slow.~30KB/s upload...

The commands should be typed (if you finshed the 3 steps)several seconds after the screen goes blank after the Sony logo.
[Sony Xperia T, TL, TX, V] nnmka:
Thank you! I'll try your way tonight.
[Sony Xperia T, TL, TX, V] updateing:
Or just use "adb push" to push this file to /system/etc

Suppose you download and extracted file to D:\TX\pre_hw_config.sh,run

adb root
adb remount
adb D:\TX\pre_hw_config.sh /system/etc
[Sony Xperia T, TL, TX, V] nnmka:
It is impossible to replace the file before installing pre_hw_config.sh firmware? Or certainly do after 3 stages?
[Sony Xperia T, TL, TX, V] updateing:
You may try replacing the file in the zip,and do the 3 steps again.It should work too...
[Sony Xperia T, TL, TX, V] nnmka:
Thank you, I try

---------- Post added at 09:04 AM ---------- Previous post was at 08:36 AM ----------

Replaced the file in the zip. Installed firmware lights appeared. But the firmware is not loaded. Adnroid blinks ears and not the phone is not loaded, waited 20 minutes.

Creates the appearance that is loaded. But the phone will not turn on even after 20 minutes.
[Sony Xperia T, TL, TX, V] updateing:
I wonder how old the zip is...I'm uploading the new zip,please be patient.It may take hours...
[Sony Xperia T, TL, TX, V] nnmka:
Thank you, I and the team waits 4pda firmware! Thank you for what you do for TX
[Sony Xperia T, TL, TX, V] phhuang:
Is it possible to have XV version coming?

Sent from my Xperia V
[Sony Xperia T, TL, TX, V] nnmka:
The firmware is not loaded yet? :)

No, the author makes a TX
[Sony Xperia T, TL, TX, V] tulen_kobi:
[MENTION=4812336]updateing[/MENTION]

Can you please wrote exactly what you did afterwards?

When I will have free time I would like to compile the kernel for Xperia V using Sony's 4.3 sources.

Thanks :)
[Sony Xperia T, TL, TX, V] updateing:
tsubasa should be officially supported,so maybe there's no need to modify anything in the kernel...

As for the system,you can look at tital's GitHub commits.Firstly update the proprietary file list,then pull the new blobs(except libqc-opt.so - use tital's),compare your device tree with mint's and do some modding.That should work.
[Sony Xperia T, TL, TX, V] XXenoNN:
Hello [MENTION=4812336]updateing[/MENTION]!

As I know everything in your ROM works almost perfect at the moment (nnmka shared his impressions about it with 4pda (russian forum about gadgets and etc.) community). So If you can upload latest version, that would be great :)
[Sony Xperia T, TL, TX, V] nnmka:
I only shared experiences. Download link assembly will be available only on updateing
[Sony Xperia T, TL, TX, V] :
Is this the only change needed to overcome the bad egl parameter error? Any flags in userspace?
[Sony Xperia T, TL, TX, V] updateing:
Seems that the flags have been set already. I'm not sure what are the essential flags. Maybe -DQCOM_HARDWARE -DQCOM_BSP and TARGET_DISPLAY_VARIANT:=caf

As an alternative, you can modify the structure with the same name in (source root)/hardware/qcom/msm8960/include/linux/msm_mdp.h to be like the one in kernel source. Mayby using updateall.py as instructed in that file to do so is better...
[Sony Xperia T, TL, TX, V] :
Same problem has been kicking our ass on d2 since our update came out in December and nobody can fix it :/
[Sony Xperia T, TL, TX, V] updateing:
You can try update_all.py to update all the kernel headers in hardware/qcom/msm8960. I think it's important after a kernel update...

Copy bionic/libc/kernel/tools to hardware/qcom/msm8960, and update hardware/qcom/msm8960/original-kernel-headers with the files from new kernel,then execute update_all.py to get the headers updated (Check the help of that script, you'll need to specific the original kernel header folder).

Then remove the copied tools folder.

There may be better methods to update the headers. If you know any, please let me know :)
[Sony Xperia T, TL, TX, V] updateing:
Tested for a while. One problem appeared: the camera doesn't show ISO,HDR or image stablizer setting. I tried enabling debug flags in Camera Wrapper, only to find that the params list returned by (vendor) get_parameters doesn't contain such settings at all. There are no params starting with "sony-"(e.g. "sony-iso-values", "sony-ae-modes". They exist before bringing up to 4.3.) or ISO/HDR settings(e.g. "iso-values"). Tried adding "sony-iso-values" manually in fixup_capilities in Camera Wrapper, then ISO Setting appeared, CameraParameters got properly set(both iso-value=ISO100 and sony-iso=100 were set) but it doesn't make any difference to camera's bahevior. Adding HDR turned out the same. I don't understand assembly code so disassembling the Sony camera.qcom.so doesn't make sense to me. How can we solve that?
[Sony Xperia T, TL, TX, V] updateing:
If camera HAL from 295 is used, we should give up CameraWrapper. Otherwise when the camera detects faces, camera app will FC... Will try on 205 blobs.
[Android Q&A, Help & Troubleshooting] Dexteron:
Hey,

got my phone (htc desire x) locked again (yes, I am stupid sometimes ;)).

First time it wasn't a big problem to me, just adb into it an set a pattern value to 0 an boom, lockscreen bypassed. Problem : since then, the androidversion got updated from 4.0 to 4.1 and it doesn't work any more.

My situation:

Bootloader locked.

Not rooted.

no custom recovery installed.

USB debugging enabled.

My question now is, is it possible to bypass the google lockscreen on an android 4.1 device? Tried different funny things like pushing home button or calling myself, then some more komplex ways with adb commands and so on, but all of them lead me in the end to either a custom recovery or root.

I'm not sure, if there is a way to get a CR on an locked device?

Or does anyone know how to adb pull some files from the data section?

And I read something about adb'ing into the device in recovery and removing the security settings, what about something like that?

Cheers,

Dex

PS: Hope it's the right section for the post.

PPS: To prevent any questions, yes, it's my phone, I don't want to steal anything, if I would like to steal the phone, I would just resetting it :)
[Android Q&A, Help & Troubleshooting] lenovoOwner:
Have you tried it with this tool?

Hello found this tool on xda:

Have you tried unlock bootloader with this tool? Afterwards you can flash a new rom. Probably this can fix your problem.

http://xdaforums.com/showthread.php?t=2462567
[Android Q&A, Help & Troubleshooting] Dexteron:
Does not work, it gives me an error message, but can't access the logfile :(
[HTC Desire X] aono18:
I need imext9vietnamese.apk for my sense 5 keyboard can anyone help me
[HTC Desire X] KidCarter93:
Thread Closed

Please don't post the same thing multiple times as that's against our forum rules. As you've already asked this question in this thread, you'll need to wait for an answer there rather than getting impatient and posting elsewhere.

Regards,

- KidCarter93

Forum Moderator
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] dssking:
I've managed to root the S4 that is on 4.6 MK6 and installed TWRP.

Am I now safe to go ahead and install ROMS? .... such as Hyperdrive, etc?

Thanks
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] DeadlySin9:
Yes. I337m has an unlocked boot loader so you can flash all you want.

Sent from Black<3's I337 running Foxhound ROM
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] dssking:
Thank you Sir. I've flashed everything imaginable to my S3. Time to move on and get rid of the S3.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] JDM STi:
OP... by having TWRP installed yours is now tripped KNOX 0x1, am I correct? I had an S3 and didn't have such KNOX thingy in my knowledge base.
[General Questions and Answers] l33third:
hello guys please help how tonetwork unlcok my mother's xperia e c1504 from hongkong.. thanks a lot
[Windows Phone 8 Apps and Games] proflo:
Hi everyone!

I have created the Magnetic field detector. It's an app to check objects on their metallic, magnetic and electrical skills.

Check it out: Magnetic field detector

I offered a free trial version extra for you. ;)

I would be very happy for a short feedback.

Here are some pics:
[Windows Phone 8 Apps and Games] Petulinek:
I installed test version. After first run i have call. I run it second time, tried calibration but it shows cca 50 all time. Cannot run a third time :( So uninstalled
[Windows Phone 8 Apps and Games] proflo:
Magnetic field detector

Reinstall the application and hold your device steady.

Than press the refresh-Button, move a metallic object,

like shears, stapler or a pocket knife to the

backround of you phone.

The app should now show other values. ;)

(Don't use objects like a coin. The magnetic value is to low!)

Your Proflo
[PDA2, XDA IIi, 2020i General] mikeadams1985:
I am reluctantly selling my xda 2i :( due to finance reasons.

Its fully working, mint condition comes with everything in the box including an extra charger

includes gps receiver, tom tom 5

3gigs worth of programs on dvd.

Im looking for around 200GBP for it.

Any one interested?

e-mail me on mikeadams1985@hotmail.com

or

u can txt me on 07841919406 - thanks
[Galaxy S III Mini Q&A, Help & Troubleshooting] Jacob869:
Hi Guys,

i have major problem with my phone and i am trying to do everything what i know, but with no result.

My friends blocked my lock screen and i unfortunately dont remember password to my google account. Recovery not work. Even if i flash lot of things. I have now 4th firmware in my phone with no result . Lockscreen still on.

Is there any solution? Or i have to take my phone under shower? :D I am working on it for 3 days now.

Many thanks
[Galaxy S III Mini Q&A, Help & Troubleshooting] mauam:
Which rom!? Do a clean install & it'll be solved or hammering it until it returns to normal:laugh:
[Galaxy S III Mini Q&A, Help & Troubleshooting] oldmen:
Recovery not work

Try by Odin :banghead:
[Galaxy S III Mini Q&A, Help & Troubleshooting] eswarvf:
If recovery wont work take alook in here
[Galaxy S III Mini Q&A, Help & Troubleshooting] Jacob869:
It WORKS!! I cant even describe how happy i am right now!

Many Many Many thanks!

:)
[Galaxy S III Mini Q&A, Help & Troubleshooting] eswarvf:
Ya I know that feeling too :D
[Android Q&A, Help & Troubleshooting] smegheadsteve:
Hi guys, hopefully this will be an easy one for somebody.

I have s-offed and installed amon ra 2.0.1 on my htc desire. Now,when I try and flash a rom it comes up with an error saying missing files,But I have tried 3 different roms.

I have done all the usuall,wiping cache etc.

It is a pvt4,hboot is now 6.93.1002.

Thanks.

Steve.
[Android Q&A, Help & Troubleshooting] smegheadsteve:
Quick update.

I decided to try and install cyanogenmod cm 7-2-0-1 because I had used this on another desire. It worked fine, so the other roms I was trying must have been incompatable with this phone.
[Galaxy Tab 8.9 General] pipechaves:
So I think is time for me to get a new tablet :crying: (ipad no thanks).

So based on aaaaaaaaall the things we have around on the market which tablet could be the upgrade ?

I was searching for something with flash for the camera, not to big not to small.(7" is small, 10" is big)

This tablet was perfect for my needs but I think its time to move one.

Any idea suggestions :)

I dont want to blow off money
[Galaxy Tab 8.9 General] OmarEinea:
Personally Samsung Galaxy Tab Pro 8.4 is the best in size and in performance and it was released in 2014 that makes it very up-to-date

If I wonna replace my tab,, it would be this awesome 8.4 tab:victory::victory:
[Galaxy Tab 8.9 General] pipechaves:
I like that one, I didnt know about the 8.4, ufff 400$ hmmmmm thats expensive :P I was thinking more like 300

Thank you !!!
[Galaxy Tab 8.9 General] jd1639:
Does it have Knox on it? Looking for a new tablet too but won't get anything with Knox on it
[Galaxy Tab 8.9 General] iZLeeP:
Just googled it and it's a good tablet, though price is hefty. I'll wait for the Nexus 8 later this year. In the mean time, I'll stick to my P7300 and P7500.
[Galaxy Tab 8.9 General] jd1639:
That's what I'm kind of waiting for too, the nexus 8. Love my nexus 5
[Galaxy Tab 8.9 General] iZLeeP:
I both own nexus 7 1st & 2nd gens but later sold it as size is too small. The Tab 8.9 is perfect for me, I wonder why Samsung discontinued it. So I'm looking forward to the nexus 8.
[Galaxy Tab 8.9 General] jd1639:
I thought the size was perfect too. I have an i957 but want something newer
[Galaxy Tab 8.9 General] hondax:
I agree the tab pro 8.4 sounds like a good device. Convenient size and good specs. I would also look at the less expensive LG 8.3. Still, I feel my 8.9 LTE with dual core 1.5 GHz is aging with grace. Better performance and UI with CM10 and Nova launcer, great browser performance with UA set to mobile
[Galaxy Tab 8.9 General] iZLeeP:
Yes, it is quite tempting to buy a new device as replacement, but with the way manufacturers roll their products, I may have to put off purchasing a new one until I really get a good deal out of it. So far, my old P7300 and P7500 is still up to the task even games with heavy graphics.
[Galaxy Tab 8.9 General] abadan:
i think that tab pro 8.4 and note 8.0 are the best now,

it has good size and performance!

SEND BY XPERIA HONAMI