Hi .. am facing weird problems with my mobile.. It started of yesterday suddenly when i tried to unlock the device . I was using kang's RC1-80 + Etana's 28 march LOC kernel (default values- no undervolting or overclock)
1. doesn't wake after locked (major problem)
2. frequent hang ups
3. accelerometer not working
4. media playing too fast and no sound
I have tried different Roms - Kang's build of cyanogen(GB), Nova-HD, MIUI GB (with and without etana's kernel).
I have also tried raising the minimum frequency to 503mhz but of no avail.
Can you suggest some solution and help trace the problem.
You think maybe it's hardware?
Why not trying to return the phone to full stock with smartflash? If it's still acting weird can you still return it on warranty?
Thanks for the reply.. I tried flashing with smartflash to stock rom but still the same problem persists. I will be taking it to service centre then..
Best of luck to you mate.
Maybe if it starts suddenly it can be something unusually, sdcard, sim card, or try other kernels. Maybe problem with recovery (but stock rom should help).
Sent from Poland
Related
Hi there,
the proximity sensor on my i9000 isn´t working anymore. Everytime I place a call/get called the screen turns black and freezes. I have to pull the battery and restart it.
Testing the sensor on the LCD-test the screen turned green and the i9000 startet vibrating. Here, too only pulling the battery made it stop.
Here is what I tried so far:
- flashing different stock fw (Android 2.2 / 2.3.x)
- applied handicapped settings
- Using Proximity_Screen_Off App and Sanity-App on stock fw
- blowing air into the USB jack/vacuuming the jack
- opened the device to mechanically clean the sensor
All of the above failed!
The only way I can get it to work is when running android 2.3.7 Joker´s MiUi and run the Proximity_Screen_Off App.
Are there any other suggestions as to what can be tried?
Else I will have to get a new motherboard, because wouldn´t want to be restricted to using only one particular rom.
Any input is greatly appreciated
Thanks Christine
if i recall good (but kill me ive drinked some atm) the greensih issue was showing with voodoo color kernels and all the sensor peoblems came with badly assembled kernel.
so i would advice you to reflash pure 3 file firmware (repartition pit and all that jazz)
and if your sensors still would not work just reflash to your carrier or stock formware for your region and push it to repair center with proper dwscription (do no mentions miui or other crap)
Thanks for answering!
I flashed 3-part firmware, pretty much everything available and a CF-Root kernel.
So it couldn´t have been a bad kernel.
Can´t take it back to service, no warranty left.
I just flashed 2.3.5 and CF-Root and now I am fooling around with it some more.
I just think it´s weird that it would work with that and only that MiUi.
impossible unless youve got some other galaxy variaant than i9000
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Cheshire-Cat said:
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Click to expand...
Click to collapse
try in stock rom/eclair about a week ,I think it is about nAa issue !!
just full wipe and flash stock rom..........using flash tools......or try using song update service........
binhari said:
just full wipe and flash stock rom..........using flash tools......or try using song update service........
Click to expand...
Click to collapse
I did, as I stated before. Still not working properly.
What I don't understand is how flashing a new kernel/ROM can break it in a way that not even flashing back stock Eclair solves the problem. I can only think of hardware failure but... it would be akin to a computer failing because you installed a different version of Windows.
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
illusionist.h1 said:
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
Click to expand...
Click to collapse
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Cheshire-Cat said:
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Click to expand...
Click to collapse
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
illusionist.h1 said:
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
Click to expand...
Click to collapse
I don't know exactly how ROM flashing works -- I've seen a "backing up system files" message, and I think that there's a reason why the stock 2.1 image is about 200 MB while CM7 ROMs rarely exceed 100 MB. I guess that some files are kept. Maybe if one or more of those files (say, a driver) is replaced with an incompatible version... but then, flashing stock should solve it. Maybe someone can shed a bit more light on the subject?
Another possibility is software-caused hardware failure, where some kind of misconfiguration physically damages the hardware. It's very uncommon, but who knows.
Hello Everybody ... Am a new member to Xda site but i learned alot through reading your posts long time ago...
anyway here is my problem MY GALAXY NOTE GTN7000 Wifi Is not Working....
Details: I Had The phone since febraury 2012 and it was GB 2.3.6
i Updated to I.C.S 4.0.3 Official Rom and rooted it in july 2012
suddenly in august 2012 the problem started to appear ((( Am Writing Dates so To Avoid the Possibility of Hard Brick or anything because the phone was working great till then )))
THE PROBLEM
1-When I Try To Open Wifi It just Lag and stop responding The ICON GOES TO GREY INSTEAD OF GREEN and stays like that till Reboot and some times stays grey after Reboot
2- when opening wifi from settings tab it says "Turning On Wifi " and stays like that Forever
3- the only Way To restore the wifi icon to white is trying to activate WIFI - Direct
4- Rebooting Used to fix the problem but now NOT
5- Removing the battery Used to fix the problem But NOW NOT
Fixes I Tried
1- Restore Factory Setting & Wipe Cache & Wipe Everything
2- Changing the Rom from (I.C.S 4.0.3 )to (GB 2.3.6 ) to (Paranoid Android ) to (I.C.S 4.0.4)
Sometimes after each format or rom flash wifi worked for 2 hours or even 24 hours normally then problem appear
3- Tried removing Wpa Supplicant ( Helped Sometimes Then NOT )
4- Tried Wifix TO change country code even manually did it
5- Adjusted the Nfram_Semacove i dnt remember the name actually from CC To All ( Worked then later Stopped )
6- Used Wifi Rescue (Worked for a while then Stopped )
7- I Flashed Alot of kernels ((Heared that syiah Kernal Fix this problem but nothing out for NOTE YET )
HELP
I know that many will think that its a hardware ISSUE BUT IF Its hardware then why sometimes it work !!!!!
What i really Think is : Its a BUG Changed some files of the system which are not restored by flashing new ROM !!! for example when i Flashed Roms and Kernels i Found WPA Supplicant unchanged with my router Config !!!!
I SENT THE PHONE TO CUSTOMER SERVICE AND THEY SAID WILL CHECK AND REPLY within24 hrs but for sure its hardware and change Board which means 2800 EGP which is the price of new SGs2 soo am sure its a Bug or Software CAN ANY1 Help MEEEEEE
MOHPHR said:
Hello Everybody ... Am a new member to Xda site but i learned alot through reading your posts long time ago...
anyway here is my problem MY GALAXY NOTE GTN7000 Wifi Is not Working....
Details: I Had The phone since febraury 2012 and it was GB 2.3.6
i Updated to I.C.S 4.0.3 Official Rom and rooted it in july 2012
suddenly in august 2012 the problem started to appear ((( Am Writing Dates so To Avoid the Possibility of Hard Brick or anything because the phone was working great till then )))
THE PROBLEM
1-When I Try To Open Wifi It just Lag and stop responding The ICON GOES TO GREY INSTEAD OF GREEN and stays like that till Reboot and some times stays grey after Reboot
2- when opening wifi from settings tab it says "Turning On Wifi " and stays like that Forever
3- the only Way To restore the wifi icon to white is trying to activate WIFI - Direct
4- Rebooting Used to fix the problem but now NOT
5- Removing the battery Used to fix the problem But NOW NOT
Fixes I Tried
1- Restore Factory Setting & Wipe Cache & Wipe Everything
2- Changing the Rom from (I.C.S 4.0.3 )to (GB 2.3.6 ) to (Paranoid Android ) to (I.C.S 4.0.4)
Sometimes after each format or rom flash wifi worked for 2 hours or even 24 hours normally then problem appear
3- Tried removing Wpa Supplicant ( Helped Sometimes Then NOT )
4- Tried Wifix TO change country code even manually did it
5- Adjusted the Nfram_Semacove i dnt remember the name actually from CC To All ( Worked then later Stopped )
6- Used Wifi Rescue (Worked for a while then Stopped )
7- I Flashed Alot of kernels ((Heared that syiah Kernal Fix this problem but nothing out for NOTE YET )
HELP
I know that many will think that its a hardware ISSUE BUT IF Its hardware then why sometimes it work !!!!!
What i really Think is : Its a BUG Changed some files of the system which are not restored by flashing new ROM !!! for example when i Flashed Roms and Kernels i Found WPA Supplicant unchanged with my router Config !!!!
I SENT THE PHONE TO CUSTOMER SERVICE AND THEY SAID WILL CHECK AND REPLY within24 hrs but for sure its hardware and change Board which means 2800 EGP which is the price of new SGs2 soo am sure its a Bug or Software CAN ANY1 Help MEEEEEE
Click to expand...
Click to collapse
Nobody is Having The Same Issue ???? Any Ideas !!!? Also Reseting Wifi Doesnt Work by #526# says Driver Not Set NG error Please I Need Help ...Thanx
MOHPHR said:
Nobody is Having The Same Issue ???? Any Ideas !!!? Also Reseting Wifi Doesnt Work by #526# says Driver Not Set NG error Please I Need Help ...Thanx
Click to expand...
Click to collapse
I am also facing the same problem for last one month and tried almost all the options tried by you but no relief. Wifi just works some time and other times it stays greyed. Can any one suggest any other solution as i also think it's software problem.
jesus christ, we are not BLIND!
anyway, i have same issues on sgs2
Same issue
@MOHPHR : I am facing the same issue as you.
I tried several ROMs from Original stock ICS to Paranoid to Crisleko's ROM.
Going into the airplane mode and then turning wifi on used to work, not anymore.
3G Data works just fine, not being able to use wifi is frustrating because when I leave it alone, it connects by itself randomly when I am at home for example.
I have done some extensive research and found an article that mentions wifi hardware problems resulting from ICS update on a galaxy S2. (Google: Samsung Galaxy S2 WiFi Issue BY Shaiful Borhan )
I did use the *#*#526#*#* and got the status: "NotSet Driver loaded [NG]".
Anyone can help please ?
WiFi drivers are not installed properly. Flash stock GB firmware
Sent from my GT-N7000 using xda app-developers app
Smokinggun said:
WiFi drivers are not installed properly. Flash stock GB firmware
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i have seen this before and that was a hardware problem.. not saying this would as well be but its a possibility
nokiamodeln91 said:
i have seen this before and that was a hardware problem.. not saying this would as well be but its a possibility
Click to expand...
Click to collapse
I had the same issue with Galaxy S, tired some custom roms but nothing worked and finally tried with stock GB it worked
Any fix?
MOHPHR said:
Hello Everybody ... Am a new member to Xda site but i learned alot through reading your posts long time ago...
anyway here is my problem MY GALAXY NOTE GTN7000 Wifi Is not Working....
Details: I Had The phone since febraury 2012 and it was GB 2.3.6
i Updated to I.C.S 4.0.3 Official Rom and rooted it in july 2012
suddenly in august 2012 the problem started to appear ((( Am Writing Dates so To Avoid the Possibility of Hard Brick or anything because the phone was working great till then )))
THE PROBLEM
1-When I Try To Open Wifi It just Lag and stop responding The ICON GOES TO GREY INSTEAD OF GREEN and stays like that till Reboot and some times stays grey after Reboot
2- when opening wifi from settings tab it says "Turning On Wifi " and stays like that Forever
3- the only Way To restore the wifi icon to white is trying to activate WIFI - Direct
4- Rebooting Used to fix the problem but now NOT
5- Removing the battery Used to fix the problem But NOW NOT
Fixes I Tried
1- Restore Factory Setting & Wipe Cache & Wipe Everything
2- Changing the Rom from (I.C.S 4.0.3 )to (GB 2.3.6 ) to (Paranoid Android ) to (I.C.S 4.0.4)
Sometimes after each format or rom flash wifi worked for 2 hours or even 24 hours normally then problem appear
3- Tried removing Wpa Supplicant ( Helped Sometimes Then NOT )
4- Tried Wifix TO change country code even manually did it
5- Adjusted the Nfram_Semacove i dnt remember the name actually from CC To All ( Worked then later Stopped )
6- Used Wifi Rescue (Worked for a while then Stopped )
7- I Flashed Alot of kernels ((Heared that syiah Kernal Fix this problem but nothing out for NOTE YET )
HELP
I know that many will think that its a hardware ISSUE BUT IF Its hardware then why sometimes it work !!!!!
What i really Think is : Its a BUG Changed some files of the system which are not restored by flashing new ROM !!! for example when i Flashed Roms and Kernels i Found WPA Supplicant unchanged with my router Config !!!!
I SENT THE PHONE TO CUSTOMER SERVICE AND THEY SAID WILL CHECK AND REPLY within24 hrs but for sure its hardware and change Board which means 2800 EGP which is the price of new SGs2 soo am sure its a Bug or Software CAN ANY1 Help MEEEEEE
Click to expand...
Click to collapse
Hi, I have been looking for days now for a forum that will be discussing this exact problem. I ve had this issue fora month or so now. I have restored to factory settings but it has not solved the problem. My galaxy note n7000 is not rooted nor does it have any special rom. I wouldnt even know how to install them. Where you able to find a fix? I am so tired of this problem, Im even contemplating the possibility of getting a note 2 and selling my n7000. I believe as well that it is most likely a software problem and im wondering if the soon to come jellly bean update could fix this issue.
Ps: after the wifi problem started, ive also noticed freezes and restars/ reboots.
Thanks for your help guys.:good:
Lebanesemecrazy said:
Hi, I have been looking for days now for a forum that will be discussing this exact problem. I ve had this issue fora month or so now. I have restored to factory settings but it has not solved the problem. My galaxy note n7000 is not rooted nor does it have any special rom. I wouldnt even know how to install them. Where you able to find a fix? I am so tired of this problem, Im even contemplating the possibility of getting a note 2 and selling my n7000. I believe as well that it is most likely a software problem and im wondering if the soon to come jellly bean update could fix this issue.
Ps: after the wifi problem started, ive also noticed freezes and restars/ reboots.
Thanks for your help guys.:good:
Click to expand...
Click to collapse
I am having the same problem with a n7000. The best rom i have tried is cm 9.1. I still have this problem but it ocurr less times.
I am thinking that it is somthing of harware, i will try to use the guarantee...
Any ideas there?
Fix Wi-Fi not working under ICS 4.0.1 & 4.0.3
Try this fix
http://forum.xda-developers.com/showthread.php?t=1436683
4thdimension said:
I am also facing the same problem for last one month and tried almost all the options tried by you but no relief. Wifi just works some time and other times it stays greyed. Can any one suggest any other solution as i also think it's software problem.
Click to expand...
Click to collapse
Lebanesemecrazy said:
Hi, I have been looking for days now for a forum that will be discussing this exact problem. I ve had this issue fora month or so now. I have restored to factory settings but it has not solved the problem. My galaxy note n7000 is not rooted nor does it have any special rom. I wouldnt even know how to install them. Where you able to find a fix? I am so tired of this problem, Im even contemplating the possibility of getting a note 2 and selling my n7000. I believe as well that it is most likely a software problem and im wondering if the soon to come jellly bean update could fix this issue.
Ps: after the wifi problem started, ive also noticed freezes and restars/ reboots.
Thanks for your help guys.:good:
Click to expand...
Click to collapse
fedetipito said:
I am having the same problem with a n7000. The best rom i have tried is cm 9.1. I still have this problem but it ocurr less times.
I am thinking that it is somthing of harware, i will try to use the guarantee...
Any ideas there?
Click to expand...
Click to collapse
@fedetipito I am still considering the hardware issue, although it seems a compatibility issue with the region/country as @fearkillerr mentioned in this post (http://forum.xda-developers.com/showthread.php?t=1436683)
I tried his solutions, none worked. The script one worked, but only once, then the problem kept repeating.
I upgraded to JB 4.2 then downgraded to stock GB 2.3 still the same issue. I am from the North Africa/Middle-East region, although when I was in Sweden in holidays and using a Swedish sim-card didn't have this issue. Any thoughts ? This problem is really really upsetting as we cannot use the WiFi properly. I am seriously considering simply abandoning my Galaxy Note N7000 and go for an iPhone 5, simply because I cannot even sell it (since no one would like a smartphone that doesn't have a proper wifi working).
I am having almost same problem with WiFi after I installed Custom ROM.
I tried only one method and it worked like a charm.
Go to WiFi connections and tell your phone to forget the network you are connected to, then re log. This problem did not happen after that 3 days now. Good Luck.
@Valium10 we initially cannot connect to any WiFi network, so we can't "forget" them. I don't think it is a "wifi network" problem.
" although when I was in Sweden in holidays and using a Swedish sim-card didn't have this issue"
And if you take SIM card out and power-on phone?Will wifi work?
Sent from my GT-N7000 using Tapatalk 2
Sometimes no, sometimes yes. It's kind of a malicious bug.
I am also facing the same problem and it seems it is hardware problem. May some dust or something else on the hardware or else we have dropped our phone some problem is there. When I gave to service center they asked that the motherboard needs to be replaced. But they refused to check it without that. I told that first try without replacing any parts and just check whats wrong in this if some repair can be done, but the service center people are so busy 50-60 peoples were waiting in line behind me to give there phones for service. They do not listen anything. They have tried by installing latest ROM and nothing else, that we can easily do it and for that also they have taken service charges.
Please someone tell me where exactly the wifi module is there, so we can open and check the problem ourself.
Lebanesemecrazy said:
Hi, I have been looking for days now for a forum that will be discussing this exact problem. I ve had this issue fora month or so now. I have restored to factory settings but it has not solved the problem. My galaxy note n7000 is not rooted nor does it have any special rom. I wouldnt even know how to install them. Where you able to find a fix? I am so tired of this problem, Im even contemplating the possibility of getting a note 2 and selling my n7000. I believe as well that it is most likely a software problem and im wondering if the soon to come jellly bean update could fix this issue.
Ps: after the wifi problem started, ive also noticed freezes and restars/ reboots.
Thanks for your help guys.:good:
Click to expand...
Click to collapse
sO?
Can anybody tell me if there's some new solution?
cause I've tried all you said here. even in the links but it does the same.
the icon returns to gray color after a few secs in green.
I'm on Jellybean galactus 3.3
pls answer me
Having the same issue with wifi and frequent freezes, tried different ROMs, Kernels and Modems. Yet still Wifi disconnects at various intervals. The phones at time hangs too to what seems to be a SLEEP OF DEATH. Ideas please...
juliobahar said:
Having the same issue with wifi and frequent freezes, tried different ROMs, Kernels and Modems. Yet still Wifi disconnects at various intervals. The phones at time hangs too to what seems to be a SLEEP OF DEATH. Ideas please...
Click to expand...
Click to collapse
for Wifi disconnects ..try to change the router wireless settings to b/g...and avoid n... this should keep the wifi stable
Hello. As some of you may remember - I have serious problems with wakelocks and it's related to a "SMSDispatcher" service (for those who are interested - http://forum.xda-developers.com/showthread.php?t=2138980).
I had no issues at all on ICS before I upgraded to official JB. Great battery life, huge screen-on time, ~3 days on battery with small usage was something normal for me.
But after upgrading to JB I started to get wakelocks. Loads of wakelocks. I checked battery stats - the Dialer apk showed up. I installed Better Battery Stats and it showed me that "SMSDispatcher" prevents my phone from goind into deep sleep. I thought it was a bug so I flashed back my .195 4.0.4 FW. And guess what. The problem was still there. It... transfered from JB to ICS?! I have this problem for 3 weeks now and even today I still don't know how can I get rid of this.
I tried wiping every partition on the phone including both SD's. Tried deleting contacts on SIM card. Tried deleting all contacts from GMAIL and manually adding them again. Tried flashing stock JB and use my T without restoring ANYTHING. But I haven't tried one thing:
Yesterday I installed unofficial CM10 (from original android development subforum). Almost clear android could have bringed a peace to me finally. It runs great but not perfect. Why? I still have SMSDispatcher issue. LOADS of wake-ups from the Dialer apk (sometimes it shows as com.android.phone, sometimes as RILD).
What I discovered is that on ICS these wakelocks are shorter than on JB. About 1/1,5h of wakelocks for ~22h on battery. On Jelly Bean it was 3h for 8h on battery.
As far as I remember on 4.0.4 .195 FW there was -19 baseband. Both official JB and CM10 use -33 baseband which may be a problem, I don't know.
So my next step in my long path to get rid of this annoying bug is changing to ICS baseband.
And my question is - which files shoud I pull from .195 stock SONY 4.0.4 FW?
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33. So I probably need binaries/files pulled from ICS and I don't know which ones.
Can you help me? Maybe with your help I could finally get rid of this or at least make the problem less annoying...
Can you just flash an ICS firmware and exclude everything except baseband?
Not sure if it wise but it may help you.
romcio47 said:
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33.
Click to expand...
Click to collapse
I already did that. No result.
Another idea - is it possible to repair software on the phone with unlocked BL?
EDIT:
Ok, found Jozinek's thread with .ftf to relock my bootloader. I will try to repair my software and see if this fix my problem.
Problem solved. It was my old SIM card's fault. It was more than 6 years old and I had to manually cut it from mini-SIM to micro-SIM shape. I probably damaged its inside structure or something. I went to my carrier and requested a new SIM card factory cut to a micro-SIM shape and now everything is ok! No strange wakelocks at all!
Hi mate!
I just was wondering after all that u've experienced what do you thing about JB , which is better for performance and battery life management ICS or JB? I'm just thinking is it worth it to upgrade to JB or stay on ICS
Stay on ICS if you don't like charging your phone once a day (in good scenario). Or twice.
ICS has definitely much better working Extended Standby Mode. It gives you amazing battery life sometimes. I'm on JB because of better multitasking and higher RAM available but speaking about the battery - ICS wins. JB just has to be fixed and tweaked by SONY. It's just a first public release. So bugs are something common. We have to wait.
Hy guys,
I'm facing some issues with my Z3C. I bought it 2 weeks ago, unlocked bootloader, installed twrp, flashed CyanogenMod 12.1 Nightly on day 3. Updated CM twice with OTA since then.
My problem is that the "sim" card (GSM/LTE) is randomly not noticed by my phone, like if its removed. I checked the sim tray, everything is stable and well seated, the sim is also OK, never had an issue with it. I just have it in my pocket or on the desk, pick it up to do something and there is already a No SIM icon on the status bar, and "Emergency calls only" If I lock the phone. Only a restart solves it.
I could not find any noticeable trigger which would lead me to the source of the problem. Sometimes its OK for 2 days sometimes it happens 2 times a day. The really frustrating part is that when the sim "disconnects" the phone starts to heat up significantly. I usually only notice it because my phone is burning my pocket. Also it looses around 20% battery before I notice it. After the restart everything is fine, the phone cools down.
Went to the Cyanogen forums for some possible solution for the problem, they suggested that I should try to update my baseband to the latest version, and if that still doesn't help, do a full wipe / clean install of CM nightly. I tried downloading the latest firmware using FlashTool and XperiFirm, creating an ftf, and flashing only AMSS_FSG, AMSS_FS1, AMSS_FS2 included into the flash ( I only wan't to flash the baseband ?!?).
My question would be: Anyone else had this problem and managed to fix it somehow? If not, anyone could please help me with a small guide how to ONLY update the baseband of my Z3C (D 5803) running CM 12.1 nightly on twrp recovery?
When I tried the flash above, my baseband version did not change. Currently I'm on "8974-AAAAANAZQ-00005-40" Baseband version, and I would like to move to the latest most stable one.
Thanks for the help in advance!
If it were my Z3c, I would flash back to stock completely and then reflash with Cyanogen. This is a device on which you have the freedom to do that, and that gets the job done safely. Backup your CM install, and then flash everything.