Hello to all of you. Big respect to the community.
I'm facing a really weird problem.
First of all, i own an Xperia neo v with unlocked bootloader (test point method), using Viper Xperia v4.0
by jerrytan http://forum.xda-developers.com/showthread.php?t=2134469 and Vengeance kernel.
Ok, so before i started with all these unlocking, changing kernel, rom etc etc i was using some Sony headset
without any problem. After all the stuff mentioned above, it won't recognise the headset. it says "headset not supported".
The jack is like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried several different headsets from various manufacturers (i have a dozen of them - i don't like any of them) and the device
recognizes ONLY jacks like this
I'm really frustrated. I want the specific headset to work. What the heck could have changed from before and after
rooting, unlocking bootloader, changing kernel and rom ?? Does any of the above affect the behavior of something ?
Anyway, thanks for your time and assistance.
Sony gave us a different points in headset that is why it say not supported. it will be like:
Tip: +
Ring: -
Sleeve: Ground.
what sonny have:
Tip: -
Ring: +
Sleeve: Ground
it is detecting wrong position. it is 100% will work but the only thing is the program they put.
there are more example if you check more in the tread.
Hello, thank you for your answer but i don't think you understood what my problem is.
So, to sum it up, before experimenting with the device, the jack in the 1st picture was recognized flawlessly.
After unlocking bootloader, changing kernel, changing rom, the same jack won't be recognized.
Thanks again.
try another kernel..im using the same combo as you..but Viper V3...nd the jack in the 1st pic works fine for me(i have an aux cable..same jack)
arisremounia said:
Hello, thank you for your answer but i don't think you understood what my problem is.
So, to sum it up, before experimenting with the device, the jack in the 1st picture was recognized flawlessly.
After unlocking bootloader, changing kernel, changing rom, the same jack won't be recognized.
Thanks again.
Click to expand...
Click to collapse
Delete unsupported headset notifier from system/app...wipe cache+dalvik and reboot...hope this solves the prob.
Or if its not present then push it to system/app with correct permissions.
In my case...i use sennheiser px100 without any problem and recently purchased a sony in-ear with mic which can't be used without the adapter supplied.
Sent from my MT11i using xda app-developers app
Hello, I did as you suggested but to no result. The headset isn't recognized
Sent from my MT11i using xda app-developers app
Related
Hey Folks,
I know this question has been around several times, but I already tried searching most threads that were listed with wlan problems: none seems to solve my problem. Most threads deal with router settings and problems with pairing devices with special routers.
However, my problem seems to be more basic: I cannot find wireless lan networks, no matter how insecure (or secure) they are. They simply are not even listed in my device. Not on windows 6.5 (duttys) nor on the most recent Stock rom and neither on android (mdeejay rev. 1.6).
I heard it might be an issue with the radio rom. Currently I use the latest Radio rom 2.15.50.14. My device has HSPL version is (2.08 - afaik).
For your information, what happend: my HD2 was broken after a bike acciddent and I sent it in for repair. After getting my motherboard replaced, I was no longer able to find any wireless lan. So I flashed the 2.15 radiorom (non-tmous). After the fist boot, I saw my wirelesslan at home appear only one glance, then disappearing for good (just flashing for 1 or 2 seconds in the wlan list of winmo 6.5). From then, all my efforts to connect to any wirelesslan were in vain. I cannot find any wireless lan. Trying to add a SSID manually, does not work.
Is there anyone with the same problem, does anyone have clous on how to fix this issue? I appreciate your help. Thanks in advance,
jokeR.
Hey guys, i just fixed the device.
So for others having the same problem my solution:
Obviously the wirelesslan antenna was not connected to the motherboard after I had recieved it from the motherboard replacement.
I had to open my HD2 and ended up like the picture below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On the left side you can see the motherboard/camera/screen-device. Locate the camera. Right to the Camera there is a black cable that is connected from the platine where the camera sits to the motherboard on the lower part of the device with a simple snap.
That cable hang loose on my device, after connecting it to the motherboard, my wirelesslan works properly no matter what radio rom was used.
Hello everybody!!!
I have a little problem with the touch screen but I don't know if it's a bug of the SE rom with the resolution or if my neo have a problem...? Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-
-
-
use STOCK launcher..
it is not BUG from SE..they just make stock launcher to work, nobody realy care about custom launcher...
only thing you can do is to use other launchers or report that problem to creators of this one.
devs wont work for this, as sony aswel...
sorry mate.
raphael.xda said:
Hello everybody!!!
I have a little problem with the touch screen but I don't know if it's a bug of the SE rom with the resolution or if my neo have a problem...? Thanks
Click to expand...
Click to collapse
Did you install a custom ROM or Kernel? Or is it still on stock? If it's on stock then it's a SE matter :/ I had that on CM ROMs and CM Based ROMs..
i'm using go launcher ex. my neo doesnt have this problem!!! touchscreen works perfectly from all parts........but only one bug.....Touchscreen goes mad when phone is connected to a pc via usb!! Anyone faced it??
Andro.Catalyst said:
i'm using go launcher ex. my neo doesnt have this problem!!! touchscreen works perfectly from all parts........but only one bug.....Touchscreen goes mad when phone is connected to a pc via usb!! Anyone faced it??
Click to expand...
Click to collapse
Do you use the stock USB cable? Every cable has a different resistance, thus a different ammount of Amps.
Andro.Catalyst said:
i'm using go launcher ex. my neo doesnt have this problem!!! touchscreen works perfectly from all parts........but only one bug.....Touchscreen goes mad when phone is connected to a pc via usb!! Anyone faced it??
Click to expand...
Click to collapse
I use USB Cable came with my Nokia phone at office & it works fine, without any problem...
In Go Launcher when you make a long touch extactly (not push to hard, but juste with the fingertip) in the middle of the apps icon the options are not here...
Try this
Go to Dialer....
Type *#*#7378423#*#*
Now ull get a menu...
There Go to > Service tests > Touch Screen and test the bottom of u r screen..
If it works then u dont have any problem with u r screen
sdk16420 said:
Do you use the stock USB cable? Every cable has a different resistance, thus a different ammount of Amps.
Click to expand...
Click to collapse
Yess...that cable comes with the phone!!
Sent From My Neo
Today I wanted to move PB AOKP to official 4.0.4, but I can't.
On newest Flashtool 0.8.0 always I've the same bug:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please, help me.
I am not able to flash any rom by seus or pcc.
After flashing any rom I have triagle with "!".
Sometimes, specially the first times, the process gets interrupted. Just try again until the bottom shows 100%!
Eastrider said:
Sometimes, specially the first times, the process gets interrupted. Just try again until the bottom shows 100%!
Click to expand...
Click to collapse
i've tried about 10 times, but only changing PC helped.
Anyone knows what is problem in?
szymko1995 said:
i've tried about 10 times, but only changing PC helped.
Anyone knows what is problem in?
Click to expand...
Click to collapse
If you could flash it correctly on other PC, maybe the issue is the USB port. Even if it works, I could only flash and do the testpoint method in my rear USBs, the front ones didn't work at all.
Eastrider said:
If you could flash it correctly on other PC, maybe the issue is the USB port. Even if it works, I could only flash and do the testpoint method in my rear USBs, the front ones didn't work at all.
Click to expand...
Click to collapse
@eastrider: Lol it would have been really funny seeing you going back and front again and again while unlocking !!
Sent from my Turbocharged Neo V
szymko1995 said:
Today I wanted to move PB AOKP to official 4.0.4, but I can't.
On newest Flashtool 0.8.0 always I've the same bug:
Please, help me.
I am not able to flash any rom by seus or pcc.
After flashing any rom I have triagle with "!".
Click to expand...
Click to collapse
Did you try flashing with an older version of the flashtool ??
Sent from my Turbocharged Neo V
Hi!
I have a problem with my S2.
So, yesterday, I tried to tether through USB and I saw it was't working and I said I'd change the ROM and it will work. I changed 3 ROMs and realised that USB wasn't working (neither in ROM or recovery) An hour ago, I tried connecting it to Odin and after 5 minutes, I succeded in Odin recognising it and I started flashing official software, but phone randomly disconnected. Now, if I try to connect it, I can't and the phone does not boot and does not enter recovery. What can I do?
PS: Sorry for bad english.
PS2: Tried connecting phone to 3 Windows 7 PCs and a Mac and it wasn't recognised at all.
worn out?
I'm not sure but I think the contact/connecter is worn out... I have a similar problem with random disconnects mainly when charging the phone but also sometimes with usb-pc connections. Changing to newer cables helps a bit but not entirely...
If it is not rom related I don't know what you can do more then trying another usb cable or buying a new phone. I guess that's not an option?
You also said your phone does not boot and you can't enter recovery... But what about "download mode"? As long as you can enter download mode you can fix the software in your phone but to do that you need the usb to be working correctly with no disconnects or else odin will mess up every time!
Replace USB board. Has been discussed here many times over the past month or so; search for those threads.
The USB port seems to be the weak point of the S2. It is seemingly the most replaced part for this phone.....I have had to do it myself, and have helped others in a similar situation. If you search my topics, you'll find one called 'video tutorial' which shows a step by step process for 'tearing down' an S2. This will help if you decide to replace the board yourself. Online shopping sites are a good place to source the part you need. But be advised, there are THREE different versions of this part (REV2.2, REV2.3 and REV2.4) see the photo below to find out where to look for the version number....
Make sure you get the same version as you remove, as a mismatch at this point is likely to cause other problems. ....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally....do not attempt to recover your phone until you have replaced this part.......the chances are that you will make things worse.....to the extent that your phone *may* become unrecoverable......
Sent from my GT-I9100 using xda app-developers app
Thanks a lot for the answers. I just had to clean it, and it's working perfecly now.
Hi @ll,
today i revived an old bricked MiniM8S II which i rediscovered in the junk-bin.
I bricked it by flashing an incompatible FW, which led to bootloops and a read-only-serial console. No matter what i tried, i couldn't make it boot from microSD, it kept on booting from eMMC and running into a bootloop.
When i bridged the pads marked in green
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it booted into recovery mode
It looks as if there's supposed to be a pushbutton, so i added one.
I made a burndisk in linux as outlined here using this rom image, inserted the microSD into the device, held the new button down and powered it on.
And then it started flashing :good:
Hope this helps someone, since i haven't found anyone else mentioning this method.
HF @ll
Thank you for your contribution.
lemmz said:
Hi @ll,
today i revived an old bricked MiniM8S II which i rediscovered in the junk-bin.
I bricked it by flashing an incompatible FW, which led to bootloops and a read-only-serial console. No matter what i tried, i couldn't make it boot from microSD, it kept on booting from eMMC and running into a bootloop.
When i bridged the pads marked in green
View attachment 4425163
it booted into recovery mode
It looks as if there's supposed to be a pushbutton, so i added one.
View attachment 4425164
I made a burndisk in linux as outlined here using this rom image, inserted the microSD into the device, held the new button down and powered it on.
And then it started flashing :good:
Hope this helps someone, since i haven't found anyone else mentioning this method.
HF @ll
Click to expand...
Click to collapse
lemmz said:
When i bridged the pads marked in green
View attachment 4425163
Click to expand...
Click to collapse
Hi,
When you say bridged the pads it means soldering ? Or short pin is enough ?
So you do it then power on and it will boot to recovery ?
Do you think it could fix this issue also ? As it is running almost the same board.
Thank you for your help.
Kind regards,
jojoju said:
Hi,
When you say bridged the pads it means soldering ? Or short pin is enough ?
So you do it then power on and it will boot to recovery ?
Do you think it could fix this issue also ? As it is running almost the same board.
Thank you for your help.
Kind regards,
Click to expand...
Click to collapse
Shorting the pads tempratoly to simulate the button