yashsingh1/xdaforums huggingface dataset:
[Sony Xperia Miro, Tipo (Dual), J, E] dany00711:
hi firends i down this stock kernel ftf also donwload flash tool and sony pc companion but sony pc companion no show me new update co i want do this manually

but after turn off my phone and boot into this mode with volume down i see green light but windows always show me that my mobile is not recognized i also do ADB driver adb driver fastmood also there is i think another one but nothing so what can i do ?

my device is not rooted
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
Hello dany00711,

Well, first of all I want to say something! Please learn to spell correcty, and do you know the meaning of the word grammar?

But I will try to help you. So you can't install the latest firmware for the Xperia E single? Allright. Can you send me the link from where you downloaded the stock .ftf? Maybe it's a incorrect or corrupt file! Please do that, and try to flash again with Flashtool. You don't need any drivers installed for flashing! Only the Flashmode and Fastboot drivers. I know you did this, but check it. and try again. Meanwhile please send the link.

Have a nice day!
[Sony Xperia Miro, Tipo (Dual), J, E] dany00711:
this file is Stock Kernel Xperia E C1505_11.3.A.2.23.ftf 5.6 MB i have all this drivers installed but still not works it show me always your device is not recognized :(
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
Dude... It is a firmware... A firmware can't fit into 5.1 MB...

Here you have a proper .ftf file: https://docs.google.com/file/d/0B8naZAFW2NP3NEJERTZ3aTZJbTg/edit?pli=1. It's 392 MB, that's a proper size for a firmware file! Download, put in in in the Firmwares folder in Flashtool. And just flash it with Flashtool. Many tutorials are circling the internet, so it is very easy.

And make sure to install the the Flashmode and Fastboot drivers again.

Cheerios. Hope it works!
[Sony Xperia Miro, Tipo (Dual), J, E] dany00711:
i make it also intall all drivers but still not work i turn off phone make volume down and put usb and i see always drivers not recognized :(

i see only green LED on phone :(
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
Before I help you any further, do you know the meaning of the word punctuation? Please, try to make proper sentences, because it makes it a lot easier to read your post, and to understand the problem you are facing!

So, have you followed everything in this tutorial? http://xdaforums.com/showthread.php?t=2240614

Just try it oncemore, and if you keep failing to flash, then it's time to use another computer. Perhaps from a friend, or a borther/sister. If this still isn't working, then I'm out of options. Perhaps other people might know other things to do, but we'll see!

Goodluck! And check this site: http://www.wikihow.com/Use-English-Punctuation-Correctly.

Nah, kidding I'm just messing with you! :p

Cheerios.
[Sony Xperia Miro, Tipo (Dual), J, E] dany00711:
still same device not recognized :(
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
Have you tried to use another computer? If that still isn't working, I'm out of options.

Cheerios
[Sony Xperia Miro, Tipo (Dual), J, E] dany00711:
maybe i go try on windows 7
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
Yes! Do that! 90 % chance it'll work! And trying doesn't cost anything, right?
[Sony Xperia S, Acro S, Ion] xperiasblack:
Official sony Torch app

Download

http://sonyandroid.altervista.org/viewtopic.php?f=49&t=522

Please don't mirror files
[Sony Xperia S, Acro S, Ion] vokal1992:
Nice, this even work on Gingerbread ;)
[Xperia Tablet Z Q&A, Help & Troubleshooting] st93:
Good afternoon guys! Does anyone know wether we can expect the Xperia Z1 Keyboard style/GUI style on our Xperia Z tablets?

I will post some screenshots from z1's design asap :)
[Huawei Ascend P6, Mate] Whookid:
Hey everyone,

For some reason I'm having problem with using Tasker on my Huawei Ascend P6 running Android 4.2.2.

I had set up a simple profile that would enable wifi, enable data, turn on auto sync, .. every X minutes. After trying this out it became clear that after a certain period Tasker would simply stop running this profile.

For testing purposes I have:

Double checked that there are no task killers installed

Created a profile of type "Time" that will Vibrate for 1 second from 07:00 every 2m Till 22:30

Enabled the "log to sdcard" functionality

After monitoring the log I have seen that there are no error but Tasker simply stops running the tasks after a certain period.

PS: I must say that I'm having the same issue with all other battery saving applications too (Juice Defender, GreenPower, Deep Sleep Battery Saver). They work perfectly until after a certain time they stop firing their events to enable the connection in the background.

Any help would be really appreciated. How can I trace this problem?
[Huawei Ascend P6, Mate] Ankush menat:
you are using trial or you bought taker?
[Huawei Ascend P6, Mate] Whookid:
I bought Tasker.
[Huawei Ascend P6, Mate] ChristDuNord:
I have same problem!

Have you find a solution?

Thanks
[HD2 Android Themes and Apps] RASHIDDDDD:
Hi i wanted to know that is there any app or widget like HTC sense app in HTC. I have Cynogen 10.1 on my HD2
[HD2 Android Themes and Apps] FCORivers:
There's a really old launcher which makes it look like sense, can't remember its name, sorry.

sent through time and space from my Hercules
[HD2 Android Themes and Apps] lukes91:
hi! you could try to install go launcher and sense theme :) i did it on another rom and worked nice :)
[HTC Amaze 4G] ohgood:
the only thread i've found for the amaze was locked, and has no links to the toolkit, is that the only way to unlock / root the amaze ?

thanks !
[HTC Amaze 4G] ravike14:
Not really it just make things a lil easier.. You can unlock your bootloader through htc dev then flash recovery through a zip with ph85img way or by the 4ext app and to get root access just flash the superuser app through 4ext :p
[Verizon Samsung Galaxy S III] psycdoc:
I had flashed TWRP and LiquidSmooth on my Galaxy SIII several months back and I had also gone into the settings and enabled the encryption functionality. It warned me that the only way to De-encrypt the phone would be to "wipe" or format the phone.

Last week I decided I wanted to look at the Hyperdrive ROM so I wiped my phone and then flashed the Hyperdrive Rom, however when the phone booted up it prompted me for a password because it still see's the phone as encrypted. I have wiped the phone multiple times using TWRP (the Format functionality as well as all of the other wiping functionality available), but I get the same results, it always prompts me for a password when it boots up. Now if I flash LiquidSmooth back to the phone, I do not get prompted for a password when the phone boots up. What do I need to do to completely remove the encryption from the phone so I can flash a new rom on it?

Thanks
[Verizon Samsung Galaxy S III] BadUsername:
I'm a little confused, is twrp asking for a password or the system when you boot it up?

I think your best bet it to Odin back to stock and reroot. This problem comes up occasionally with twrp. I know this will definitely work.

I couldn't find any information on how to get around the password. But I'd guess you may be able to overwrite it my flashing a new recovery from odin or using an app like ez recovery if it's twrp asking for a password.
[Verizon Samsung Galaxy S III] psycdoc:
The system is asking after I flash the Hyperdrive and it re-boots. It is NOT TWRP that is prompting me. However when I flash LiquidSmooth it works fine.
[Verizon Samsung Galaxy S III] BadUsername:
I've never seen that before.

When you try to flash a new rom again, try to format system before you flash. That should erase anything that's making a password prompt appear.

You can always format your internal SD and clean everything out that way.

Or you can Odin back to stock, which essentially wipes and formats everything.
[Samsung Galaxy S Blaze 4G] UberPinguin:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

CyanogenMod 10.2 Nightlies have begun for the Blaze 4G.

Nightlies are available at http://get.cm/?device=t769.

I recommend avoiding the 20130925 nightly. It contains a fstab issue that will interfere with CMUpdater.

I also recommend updating your recovery, either through ROM Manager or manually using the build at http://www.clockworkmod.com/rommanager/ . This build has an associated mount point fix, and is needed for properly functioning CMUpdater.

If you're still using the Hercules/T989 modem, you need to flash back to the T769UVLH5 baseband. Using other basebands is not supported or recommended.

More Information

Please visit the CyanogenMod Wiki page for more details, including known issues. This will allow me to keep the information updated in a single, central location.

Happy CyanogenModding.
[Samsung Galaxy S Blaze 4G] car vs driver:
Well done sir.
[Samsung Galaxy S Blaze 4G] xWolf13:
Congrats on getting it!

Sent from my iPhone 5C (yes, an iPhone)
[Samsung Galaxy S Blaze 4G] Somcom3X:
Congratz
[Samsung Galaxy S Blaze 4G] creeve4:
Can someone running this please confirm if this bug from CM10.1 is still present:

No matter what level the in-call volume is set to, when a new outgoing call is made, the in-call volume is set to the maximum level (although the actual volume slider is still in the same location as previously set).

For example:

In-call volume is set to 60%

An outgoing is call is made and the volume level suddenly jumps to 100%

When the volume of that call is adjusted, the level is shown to be at 60%

Please try this to test for the bug:

1. Set in-call volume to minimum

2. Make an outgoing call

3. Let us know if the volume jumps to the maximum level or stays at the minimum level
[Samsung Galaxy S Blaze 4G] anactoraaron:
Please add speakerphone muting the mic to the bug list. I don't know if everyone is aware of it. Turning on speakerphone mutes the mic (you can hear them but they can't hear you). Also I'm not having any Bluetooth problems and I use it a lot. Well done and thanks to all who made this possible!
[Samsung Galaxy S Blaze 4G] UberPinguin:
I am unable to reproduce that behavior.
[Samsung Galaxy S Blaze 4G] UberPinguin:
I was unaware of that. Thank you, I'll add it to the OP.
[Samsung Galaxy S Blaze 4G] tommyboy8125:
I having the Bluetooth issue connecting to my OBD2 scanner for my car. Would a log help? Also I'm still using the 989 radio with no issues. Can that cause Bluetooth problems?
[Samsung Galaxy S Blaze 4G] UberPinguin:
It shouldn't interfere with Bluetooth, but I am surprised that it works. The vendor libraries we're using should not be compatible with that firmware. shrug

Yeah, a log would be useful. I don't have such a scanner, so it's not something I can debug here.
[Samsung Galaxy S Blaze 4G] tommyboy8125:
I can get a log tonight. My phone sees the adapter but won't pair with it. It says the code is wrong.

---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------

Occasionally a reboot will allow it to pair one time but that's as far as it will go it still won't communicate once I start the app to use the device.
[Samsung Galaxy S Blaze 4G] FourM:
I'm using the latest T989 radio and I'm having no issues with data connectivity with 4G/LTE (whatever you call it). My calls also work. This worked with the 20130925 and 20130926 nightlies.
[Samsung Galaxy S Blaze 4G] creeve4:
Instead of a direct link to download in the OP, could you change it to this: http://get.cm/?device=t769
[Samsung Galaxy S Blaze 4G] UberPinguin:
This makes sense now that there's more than one 10.2 build available. OP updated.
[Samsung Galaxy S Blaze 4G] thepun_g:
Does the gyroscope and other sensors work?
[Samsung Galaxy S Blaze 4G] UberPinguin:
Accelerometer, Magnetometer, Proximity, and Light sensors work.

The phone is able to sense rotation, but I don't get a reading from the Gyroscope.

Application used: Sensor Kinetics
[Samsung Galaxy S Blaze 4G] anactoraaron:
I started a q&a thread in the general section so if anyone wants to ask a question feel free to do so there. Let's keep this thread clean for bugs/logcats. If you don't know how or don't feel like getting a logcat please post your issue in the q&a and I'll try to replicate it and post a log for ya and add it to the known issues list ;)
[Samsung Galaxy S Blaze 4G] Somcom3X:
E/Sensors ( 606): couldn't find 'gyro_sensor' input device
E/Sensors ( 606): GyroSensor:60 CH 20 .
E/Sensors ( 606): GyroSensor: enable open fail. (data_fd < 0)
I/SensorService( 606): K3DH Acceleration Sensor
I/SensorService( 606): AK8975 Magnetic field Sensor
I/SensorService( 606): AK8975 Orientation Sensor
I/SensorService( 606): GP2A Light Sensor
I/SensorService( 606): GP2A Proximity Sensor
I/SensorService( 606): K3G Gyroscope Sensor
D/SensorService( 606): nuSensorService thread starting...

There some clarification if you can't find any gyro related errors.

You gotta enable it in the defconfig to get this.
[Samsung Galaxy S Blaze 4G] UberPinguin:
There's an error in the i2c chip init for the K3G sensor. Working on it, but no ETA.
[Samsung Galaxy S Blaze 4G] creeve4:
Is there a change log for the nightlies? I can seem to find one.

Edit, found it: http://10.cmxlog.com/?device=t769

Has there really been no changes in the last 3 nightlies?
[Samsung Galaxy S Blaze 4G] UberPinguin:
Open CMUpdater, refresh the list, then tap the build name. It will open a changelog.
[Samsung Galaxy S Blaze 4G] ohgood:
i'm prolly doing something wrong:

factory reset twr

flashed via TWR

powered off

booted

either gets stuck at the CM splash, or goes black and unresponsive
[Samsung Galaxy S Blaze 4G] anactoraaron:
Should be in q&a but you need CWM 6.0.3.7 or 6.0.3.8 to flash any version of android 4.3. TWRP is compatible but 2.6.3.0 is needed which isn't available for the blaze. You can get cwm via ROM manager from the play store.
[Samsung Galaxy S Blaze 4G] creeve4:
I've had numerous people tell me that they hear an echo when talking to me, is this a problem anyone else is having? I am using UVLH5.
[Samsung Galaxy S Blaze 4G] Somcom3X:
Its common between the blaze and exhilarate. Try changing your radio.
[Samsung Galaxy S Blaze 4G] UberPinguin:
Still digging here, but the K3G gyroscope sensor has been disabled since at least the stock ICS release. The i2c_smbus_write_byte_data function in drivers/i2c/i2c-core.c is returning an invalid Chip ID.

I'm going to have a look at the Gingerbread releases and see if this sensor was ever enabled.

EDIT: Confirmed that the K3G gyroscope driver is enabled in the generic msm8660 kernel configuration, but has been consistently disabled in all of the Blaze 4G's configurations since the first Gingerbread release.

Hercules and Skyrocket both have working K3G sensors, however I'm fairly certain this falls in the "minor differences between Celox family members" category.
[Samsung Galaxy S Blaze 4G] Cirkustanz:
Where can I find the 4.3 google apps that I should be using?

I found this thread.... http://xdaforums.com/showthread.php?t=2378992 but I would probably feel better someone else confirming where they obtained their 4.3 gapps from before I switch to 10.2

Thanks!
[Samsung Galaxy S Blaze 4G] tommyboy8125:
I just Google 4.3 gapps and get it from the source directly
[Samsung Galaxy S Blaze 4G] car vs driver:
Google Apps Packages: http://wiki.cyanogenmod.org/w/Gapps
[Samsung Galaxy S Blaze 4G] rwilco12:
I've just cleaned up 25 posts here that were not related to the development of this ROM. The OP has asked that we continue all questions/answers/general discussion about this ROM at the following thread: http://xdaforums.com/showthread.php?t=2458825.

Please help us keep this thread clean by posting in the correct threads.

Thank you,

Rwilco12
[Samsung Galaxy S Blaze 4G] sauceboy01:
I've been using this rom for a couple of weeks now and have been updating whenever the newest updates come about. Wanted to report a couple of bugs in case you are not aware of them.

When you turn off the screen and go to turn it on 2 out of 5 times the haptic keys will turn on only the screen will not follow. This happens fairly often.

When I run the stock galley or any gallery for that matter the whole phone will freeze up and reboot. The only way I can access my photos is by swiping through the stock camera apk.

Those are the two major ones I can think of as of now. Thoughts?
[Samsung Galaxy S Blaze 4G] car vs driver:
1. Yes, the screen on is a known issue - I'm currently working on it.

2. The gallery problem is a hit or miss across many of the celox (8660) devices. Seems to be related to the filesystem changes that happened in 4.3 - the culprit has been shown to be a corrupt file. If you format your internal storage it should go away.
[Samsung Galaxy S Blaze 4G] UberPinguin:
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_t769
[Samsung Galaxy S Blaze 4G] car vs driver:
Dammit ... I'm slacking on my wiki. I need to probably post the same thing for the exhilarate.
[Samsung Galaxy S Blaze 4G] sauceboy01:
Excellent! I can attest to the barcode scanner picture issue as well as it also applies to photo banking check deposits i try to make with my phone. The camera in this circumstance also displays a scrambled image and I am unable to make my check deposits. Just wanted to bring up another circumstance in which it doesn't function.
[Samsung Galaxy S Blaze 4G] UberPinguin:
So, a couple of preliminary results:

Camera works for Google Drive's "Scan to Drive" feature

Logcat from ZXing seems to implicate an error in the zoom_calculate function, which could also be what's breaking camcorder's focus.

zoom_calculate is part of liboemcamera.so.

We're using Hercules/T989's JB liboemcamera.so, because T769 and I577's ICS liboemcamera.so segfaults and kills mediaserver.
[Samsung Galaxy S Blaze 4G] :
You might want to check out: "Camera ICS". It's almost the opposite of most 3rd party camera apps I've seen. It works but it glitches in transitions. Like if you hit the menu button or switch cameras...
[Samsung Galaxy S Blaze 4G] UberPinguin:
I downloaded it, and it seems to work OK, but I'm not exactly excited by the idea of an ad-ridden 3rd-party build of the ICS camera app.
[Samsung Galaxy S Blaze 4G] :
No No, that's not what I meant to say at all... The fact that Camera ICS works sort of hints that there is a way to get other third party camera apps to work. Also it does glitch out the same way that the others do but somehow, it's able to recover....;)

I'm wondering if the sdk level of the app is 14 (ICS) and that's why it works...

You can see the glitching if you hit menu or switch from front to back cam. You can really see it if you hold the home button to get the recent list while in the app.

I think the 3rd party camera app problem is also related to this

<6>[ 8251.982299] mdp4_overlay_mdp_perf_upd mdp clk is changed [1] from
59080000 to 96000000
[Samsung Galaxy S Blaze 4G] UberPinguin:
Raising the MDP clock is normal, and isn't an error. The only applications that produce this behavior, log the ION OOM error when doing so.
[Samsung Galaxy S Blaze 4G] :
When I was testing Camera apps, I noticed that the Stock camera app did not raise the MDP clock. Camera MX raised the clock to 96000000 and showed the glitchy screen and Camera ICS raised the clock to 96000000 and immediately lowered back to 59080000.

It was just an inconsistency I noticed and thought it might be relevant...;) If it isn't then... my bad...:good:
[Samsung Galaxy S Blaze 4G] flyers00:
The latest nightly and operation killjoy is working great. The ROM is super smooth and working fine. Great job

In the future is there any chance if adding bln support?
[Samsung Galaxy S Blaze 4G] car vs driver:
Short answer is nope.

Long answer, you can search the Skyrocket forums as it has been discussed there extensively on why it was removed from the msm8660 devices and why it won't likely ever be coming back in stock CM source code.
[Samsung Galaxy S Blaze 4G] Cirkustanz:
I spent a few minutes looking for an explanation, and here is what I got.

dcvito, that feature is called BLN. The driver code to make this happen was removed by the rebase of the kernel. I do not plan on resurrecting that change.

Why, you may wonder? Valid question. Here goes:

BLN hurts battery life since the processor cannot go into deep sleep while flashing the lights.

It took a lot of effort to get it stable last time, and even then some issues lurked.

The changes necessary required me to completely rewrite of the touchkey driver from Samsung. By doing that, I ended up making it harder to upgrade to newer Samsung kernels. It would be in our best interest to leave a change of this magnitude out.

The previous touchkey driver was buggy and needed to be rewritten anyway for stability reasons. This version from Samsung seems to have fixed the problem where the touchkeys sometimes didn't light up. Now there is one less reason to hack up this driver.

I could never get a "half power" mode working. I was hoping, like some other devices, that we could blink that lights at a lower intensity to save power.

I plan to remove the UI configuration options that control BLN since it won't be supported.

Sorry BLN fans. If there is someone out there who wants to port forward the code to the new driver style, please upload the change to review.cyganogenmod.org.
[Samsung Galaxy S Blaze 4G] car vs driver:
Some of that no longer holds true ... Topprospect spent some considerable time fixing the issues with the base driver. Most of it was related to improper mutex protection and device locking.

Honestly, this is a legacy driver in this kernel version and will probably never get updated - so IMHO, that's a moot point.

Mikeyman and I worked on revising BLN for CM10.1 - basically, we faced similar challenges as noted above. One of the key things we addressed was the nature of how it actually worked, we added in proper mutex protection and had it mostly working.

The key problem, one which will never go away, is the wake lock. As long as those LEDs are blinking, the CPU is running and the device is awake. So, we came up with a plan to limit the wake lock to a set time - at which point the LED would shut down and allow the device to sleep, say .. 5 minutes after an alert.

Beyond that, our plan was to leverage the system settings options (which used to update a sysfs) and allow configuration on the duration of the blinking, etc. Clearly we didn't make it this far (see link below for the patch as we left it) because 10.2 came out and we immediately began work on getting that up and running and never looked back at BLN.

Good news ... if you like to tinker, this is about 90% complete and nearly functional. If I recall correctly, you just need to finish up the code that detects a second notification event (while one is active) and either resets the timer or it gets ignored. There were a few other bugs that should be obvious once you look at it.

http://review.cyanogenmod.org/#/c/45646/

Have fun ...
[Samsung Galaxy S Blaze 4G] flyers00:
Thanks for response and link for further info to read. I am trying out the du ROM that KT posted earlier today. Du and pack are using active display. So far that seems to be working fine to wake the screen and provide the user that notifications are coming in

I'm not a dev nor pretend to be. I'm not sure what all is under the hood to make this work but its a nice feature

I appreciate your efforts and everyone else who worked hard to get 4.3 ROMs running on the blaze and exhilarate :D