Hello everybody,
i have two different problems.
The first is that i have jack 3.5mm hearphones with mic. (4 points connection) wich is recognized by the SE Xperia X10 with FeraLab 30.0 but with a dirty song. I have to keep the mic. activation button pressed to get a good song. Theses hearphones are produced by phillips and meant to work with Sony smartphone (i think, if it works for Sony, it might work for SE ).
When looking for a fixe, i noticed that there is an update avaible for FerLab and so applied the update by following the exact procedure (Kernel update by flashing, manualy formating all partitions by CWN Recovery, wiping datas by CWN-R and then installing the new ROM by CWN-R "Install from Zip" option).
The first launch went good, the phone is pretty stable and smoother than before but my audio problem is still the same.
But the huge problem for now is that the SuperUser just crash (Force-Close) every time an app. request SU rights.
Then, i can't use root apps. anymore.
PS: Sorry if my use of the english language isn't perfect at all but i'm french and currently learning english
Audio problem is not software but hardware one...
Regarding superuser... try to re-update binary from superuser app... or just reinstall rom again.. it have to work perfectly
For the audio problem: i tried with other hearphones and it's still not working.
I know theses other ones can work with my X10 because i used them when i had SEMC Debrand Engine (theses are my brother's hearphones so i can't use them everyday and i prefer FeraLab because it feels smoother than SEMC Debrand Engine).
About the SU FC problem, i allready re-installed the ROM 2 times and it didn't help.
IDK how to force update of the binary because the binary is up to date.
How can i force the update ?
Today I was testing the Great New Version of FeraLab 30.5 and I have the same problems. If I have time, I would post it in the
"Feralab Wishlist and Feedback" Thread Thank you FeraVolt, anyway !
For the audio problem, i finnaly bought new hearphones (without mic) and it works.
About the SU FCissue, i figured out how to force update of the binary (was so obvious that i missed it ...) but i doesn't help.
Its says that the binary is sownloaded and when it comes to auto-test the binary, it crash.
I hope the 30.6 update will fixe this huge issue (^_^);
Again, thank you VERY MUCH for your AWESOME work, FeraVolt.
This bug doesn't change the fact that your work is awesome.
Related
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
benoitm974 said:
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
Click to expand...
Click to collapse
I have same problem in zombie panic kernel v 1.59 and v 1.61.
after i update to v 1.62, i don't had problem reboots. and everything it's ok.
Problem occurs usually when:
I use the phone for 10/15 minutes, that is running music or radio, or using the phone, like surfing and installing app from market.
I'll try the new 1.63 ...
Benoit
Sent from my U20i using xda premium
Hi, No reboots for me 4 days into 1.63+2.1, I did similar process only difference is I use clockworkmod, someone else will have to confirm but I remember a while back all the roms where coming out with "no longer supporting xrecovery". As said dont know might be nothing but everyone seems to use clockworkmod now for flashing.
Sorry assuming you used xrecovery to flash rom since you mention installing it.
Well strangely, the update to 1.63 did it, no more reboot and I can even OC the phone ! It works great no reboot, even with wavy usage of GPS navigation with CoPilot live over the week end ! this is perfect !
I only have an issue with the radio FM app which is buggy : sound start on the hp instead of head phone, favorite station are not kept, frequencies are written in green on black which is not visible and RDS name is overlapping frequencies ...
Another issue, I'm still not able to fine tune auto brightness to have good reactivity when phone get out of standb by on shiny day it take 1/ 1.5 second for the screen to detect it need to boost lightness ... Same when I'm in a call and I want to use the keyboard to dial, it takes 1/1.5 second for the phone to adjust brightness... I've tried several tutorial from forum but it still have this small lag in brightness reactivity.
Other the phone is now perfect to me in 2.3.5 ! Thanks very much slade87 ! One note I don't like the boot animation some less shiny would have been welcome ...
Cool you got it all working, yes there where instabilities with cross ROM/kernels.
I like the new bootanimation but you can allways change it out if you dont..
(update 7/7/11)[Boot Animation]more bootanim
Bootanimation Installer v3.3
Hello, all ROM makers, developers, hackers and advanced users.
I have a problem and hope you can give me some good advice.
Here is my sad story
You can read the full description if you want. Or you can skip it - the main question in the end of this post..
I have bought a new Sony ericsson Live! with walkman (wt19i) phone during my newyear holydays in Prague. It seemd to be working fine.
It is from rev.3, manufacture date 11/49 (mounth/week)
When I came back home and started using it, I saw that after some inactivity period (about couple hours or maybe more) the touch screen, back and menu snsor buttons stops any responsing. Hardware buttons (home, volume, camera, walkman and power) are still working. The system also continues to work as usual, so I can turn it on (but can not slide to unlock), I can hear if somebody calls me (but can not answer). Alarms, notifications and all another functions are still working.
Once or twise it started to work again (by itself, without any actions by me) but after few time the problem repeated. I was very unhappy and sure it was a hardware problem (and of course the Czech warranty does not work in Russia), but now i'm not so sure.
The phone had 4.0.2.A.0.58 firmware (android 2.3.4) from the box. First of all I tried to install SE PC Companion software, connect phone with usb and make factory reset... touchscreen started to work! But soon I saw this problem again.
The next day a new update was released and installed it (firmware .62). My phone was working again, but with the same result after some time.
You shoud know, that simple softreset (or ejecting and inserting battery) has absolutesy no effect on problem. After system starts I can not even unlock it. But flashing a new (or even the same) firmware (with flash tool or SE PCC) makes touchscreen and buttons working for some time. Have no idea why, but installing ROM with CWM (even with full wipe) does not make touch working.
Then I tried to use another custom kernels and ROMs. I unlocked the bootloader with fastboot tool, flashed one of custom ROMs from this forum (pre-rooted and with CWM). Then tried to use CM7.2 ROM... then another kernel and another ROM. Official, official-based, totally unofficial. The problem was with me each time after couple hours
I thought it is because some troubles in lock screen. Tried to install "no lock" app, so my phone did not use lock... but after some time touch freezes in home screen.
I disabled screen off while charging in settings and tried to leave the phone "wired" for some time... actually it worked fine all the time, and when I dicsonnected it it was still working... for couple hours.
I tried to install "no sleep" applications that does not allow CPU and screen to suspend. But it have no influense.
I even flashed CM9.0 ICS (very) beta ROM with the same result.
If it is just hardware problem - why it solves (for some time, but solves) with flashing? If it is a software problem - why it doesnt solve with new kernels and ROMs? My brain is ready to explode.
Now I have only one last idea and ask you to help me.
The question is:
How can I use adb or adb shell comands to get more information about the problem with touch?
I saw there is some log (logcat, stderr) tools, debug tools. I saw working lsmod, dmesg and mount commands in shell.
I think I shoud get all this information when all is ok. And then get it again when touch stops working and then compare, is it a good idea?
Where exactly shoud I see? How to test or get some touch input device info with adb? Is there any item in /dev that i can explore? Or something in dmesg? Where are touch driver located and how can I check if it is working?
I have some basic linux and andriond skills, but have not enought expierence.
I very (VERY) hope somebody can give me any useful advice to continue solving the problem. Where to see, what to do?
Thank you
P.S.: and sorry for mistakes, of course. English is not my native language.
P.P.S.: i am not sure where is the best place for this question: here or in xperia subforums. But I decided that this question is not xperia-specific and can be useful for other people in future.
Anybody? I have Lenovo Yoga B6000 with touchscreen problem and will be good if anyone know how can i test TS through ADB or shell.
Hello. Guy's please help me. Two days ago i enabled cam app ant it showed error, then I enabled it again, and it worked normal... If i reboot phone it hapens again... Im on DonutHD rom without updates, i tried flash via recovery other rom, and in other ROM, it was XPERIA-S port rom, it showed error every time i enabled cam app, its not worked... Then i flashed back to DonutHD, that bug is still her like I said it shows error once, than it normaly works... Sorry for my english, im still learning it Please help, is this hardware or software? Camera 360 captures strange green color at first time, then works perfactly, after camera360 stock works, if i didnt enabled it first. Today i flashed MIUI by cobrato, camera works perfectly, and camera 360 too, no errors and other s**t... Is this issuse with stock rom's or something? Strange. Please HELP!
hi guys.. just want to ask whether how to solve the bugs that happened in my phone - N7000 Galaxy note
What happened is , I've successfully rooted my device with using cwm and super user installer, flashing them at the power + vol up + menu button ( i forgot what they called that as, im a noob... :S )
Then I start to use those application that needs root access. Like lucky patcher , root explorer and beats audio
One day when i restart my device, before going into the launcher it shows that " Android is upgrading " and restarting the apps. But after i enter to the launcher there isn't any update at all. And this time onwards everytime my phone restart it will shows that my android is upgrading.. and nothing happens , repeatedly.
I've updated to the latest beats audio and the problems starts here :
in the latest beats audio there's an uninstaller inside the installer. I was trying to upgrade my phone to jelly bean via kies. and I go to uninstall that beats audio with using the uninstaller inside the installer.
And after it auto restarts it seems like haven't clear the application, but it says that my phone is not installed with beats audio. ( I think that app itself remained as an installer ) so i go and uninstall that installer.
And then i was checking in xda's forums bout how to unroot my phone. Before that I've seen inside my super user, there's a "Unroot" services provided at the back of the setting. And since i don't understand what are the forumers talking about because im a noob... I tried to unroot using that since it looks easy ( just one click and its done i guess ) then I press on it...... and my phone's super user had been removed.
After I restarted my note, whenever i try to input text or type using swype, it HANG non stop then suddenly shows up , process system not working or something.. ?? And then i keeps on restarting my phone but the problem still exists. Then i got fed up and do hard reset at the startup android there.. wipe away all datas and all.
But, after i enter again the problem still exists. which is Process system not working and whenever i wanted to key in texts, ( whatever keyboard it is, stock or swype ) the phone HANG,
Can anyone help me with this ??
i have an xperia mini pro (sk17i) and i installed by cyanogenmod, version 10-20130428 unnoficial mango. My problem is with acoustic drivers. Is not hear so loud like version 4.1.b.0.587 version. I installed also audio hack v 2.1 and is working very well with that program, but after somebody call me, the volume is back to normal (is hear very slow); or even if i shutdown or restart thhe phone the volume is back to slow, and again i must do the same operation with the application audio hack. I wiped all things, i reinstalled the firmware again, i installed some times ago also exmiui version, and is same with volume. What can i do?
op3n said:
i have an xperia mini pro (sk17i) and i installed by cyanogenmod, version 10-20130428 unnoficial mango. My problem is with acoustic drivers. Is not hear so loud like version 4.1.b.0.587 version. I installed also audio hack v 2.1 and is working very well with that program, but after somebody call me, the volume is back to normal (is hear very slow); or even if i shutdown or restart thhe phone the volume is back to slow, and again i must do the same operation with the application audio hack. I wiped all things, i reinstalled the firmware again, i installed some times ago also exmiui version, and is same with volume. What can i do?
Click to expand...
Click to collapse
really? no one dont know how to solve this problem?:silly: