Related
Hello Everyone,
I had this random reboot problem and posted it in various forums on the web but had not found the root cause of the problem.
But now I seemed to have completely solved it. Here is how for those experiencing similar issues.
1. If you are having it from just few days, then it is surely got to do with the phone trying to fetch data when the signal strength is very low. I found out that -113dbm is the least signal possible and the phone displays a '+' mark in the signal status notification bar. Hence when the signal goes to somewhere near -112dbm and -102dbm the phone goes into a reboot.
So if this is your problem, then you need to download "Shutupbatterymanager" from the market and set the phone to turn off data connections when the signal is below a certain threshold. It is also attached in this post below. For example you can slide the signal bar in the app and set it to -102dbm cutoff after which it will disable the data connections. This is one way of solving the issue if you have had reboot problems occur very recently.
2. The best way to solve this issue is to compromise on your 'downgradability'. For me the above option did not work well after a few test runs and then I accidentally found out that flashing this file (thanks to Higgsy for making this) is the best way. Maybe motorola found out the issue after numerous posts in their support forum and has solved it with a change in the kernel. So just download the file and flash the froyo 2.2 GB UK sbf file with your RSDlite.
It would be helpful if someone can post their kernel version. The flashed one after using this file that seems to solve the problem is [email protected] #1
Hope it solves all your reboot issues. Google you can please index this for some much needed help for desperate Defy owners.
Thanks to: Higgsy and Sorensiim
PS: Important point i forgot to mention is that the change in the kernel is reflected when you get into recovery by holding Vol down + power button. Here if you are on newer and changed version, touching the corner of screen does not work. Instead pressing the volume rocker simultaneously up+down will enter recovery functions.
Substantially is the UK 3.4.2-117 sbf that have you flashed?
alezzandro said:
Substantially is the UK 3.4.2-117 sbf that have you flashed?
Click to expand...
Click to collapse
Yes, but it is not the complete sbf. Some segments have been knocked off and it has been repacked by Higgsy so that there is no locked bootloader and downgradability problem.
Which means the complete SBF already has this fix built-in?
Yes it should.
Sent from my MB525 using XDA App
okidoki - thanks good to know
I would verify the change by going into stock recovery.
Sent from my MB525 using XDA App
How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?
OK before I get confused with the build numbers do this. Power off phone and boot with power button and volume down. Once recovery appears tell me if you are able to enter recovery using the corner of the screen or is it through pressing the volume rocker up and down simultaneously.
It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.
mrt3k said:
It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.
Click to expand...
Click to collapse
OK then you are already on the newest froyo kernels and not on the eclair ones which had the problem.
Now tell me, is your rebooting problem still there?. When do you face it? What is your observation?.
i think if you are using pays rom, then you must've flashed the whole sbf already. you don't need to flash this partial old sbf, since the new sbf should include the old fix (of course some assumption here, hehe) you probably can't downgrade using official sbf either...
mrt3k said:
How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?
Click to expand...
Click to collapse
Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.
mrt3k said:
Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.
Click to expand...
Click to collapse
OK then. Continue your observation on the sim card and come back again to report if this occurs again. All the best.
Ok I will do so. Thanks for your help!
But apart from the hint on the sim-card (which is not yet proven) - Any idea? Do we know that the brand new kernel does not have the error anymore? Or could it still be part of the release if Moto did not realize and fix it?
So, do you see any other thing that could cause all the reboots?
Every rom out there has ways by which you can still maintain downgradability. I did the same. I loaded chinese sbf and then tried various roms by restoring it by nandroid backups. Also people like jboogie and higgsy give boot only and safe sbfs which can be tried. For me flashing the above attached sbf from higgsy and restoring the rom posted by Iaoa PL deblur solved the problem totally.
Sent from my MB525 using XDA App
Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!
mrt3k said:
Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!
Click to expand...
Click to collapse
Yeaaah, thats some good news. Enjoy your Defy
After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?
mrt3k said:
After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?
Click to expand...
Click to collapse
This is exactly the same problem I had. Why dont you do this. Flash the new poland leaked sbf and then restore nandroid backup from Iaoa. He has a rom for the same poland version.
This solved my problem. Hope it works for you too.
And please remember that you can get back to 2.51 roms and nothing below that if you flash this sbf.
[Q] Issue with 1.47.401.4 : often get "Limited Service" and hard to get signal back
Hi there,
Since 1.47.401.4 (and never before with 1.28.x), I'm experiencing issues with the radio, especially voice:
1/ I often get a "Limited Service" warning in places where I could easily get a decent signal to give a call.
2/ Each time I got the "Limited Service" warning, it can take ages before the signal gets back (after I moved to some other place).
3/ Sometimes, I need to reboot the terminal to get the voice signal back.
I did perform a full wipe (factory reset) on my phone and install the rom again (using the roms.zip method within the bootloader) but it didn't really solve this issue.
I also cleaned the sim card contacts, just in case, but this was useless.
I also chose "GSM auto (PRL)" in the phone settings, this helped a bit, but still this annoying issue remains.
If someone got a clue, I'm interested ! And if anyone is experiencing such weak/bad signal issue, I'm interested in your feedback.
Cheers.
Hboot: 098.002 S-ON
Radio: 20.28I.30.085 AU_3805.06.02.03_M
~babel said:
Hi there,
Since 1.47.401.4 (and never before with 1.28.x), I'm experiencing issues with the radio, especially voice:
1/ I often get a "Limited Service" warning in places where I could easily get a decent signal to give a call.
2/ Each time I got the "Limited Service" warning, it can take ages before the signal gets back (after I moved to some other place).
3/ Sometimes, I need to reboot the terminal to get the voice signal back.
I did perform a full wipe (factory reset) on my phone and install the rom again (using the roms.zip method within the bootloader) but it didn't really solve this issue.
I also cleaned the sim card contacts, just in case, but this was useless.
I also chose "GSM auto (PRL)" in the phone settings, this helped a bit, but still this annoying issue remains.
If someone got a clue, I'm interested ! And if anyone is experiencing such weak/bad signal issue, I'm interested in your feedback.
Cheers.
Hboot: 098.002 S-ON
Radio: 20.28I.30.085 AU_3805.06.02.03_M
Click to expand...
Click to collapse
I have the same problem! 1.28.x was OK, bet the newest one in terms of receiving signals is just terrible!
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
~babel said:
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
Click to expand...
Click to collapse
In complete contrast to what you two are saying..(see my old thread where I had this problem with the older radios http://forum.xda-developers.com/showthread.php?t=1133785)
I'm now running on the latest radio but not the latest ROM (as I use LBC MOD which is currently based on a 1.36 ROM) and I no longer experience this problem.
My conclusion being that the newest Radio is better.
Thanks for your feedback.
Would you then say that the "Radio_20.28I.30.085 AU_3805.06.02.03_M" was the answer to your phone bad signal issues ? Then, I might need to use another rom an check if that helps...
Anyway, did you try to change/update phone/radio settings mode (__http__www_google_com_support_forum_p_android_thread_?tid=42655c79e5837499&hl=en) ?
~babel said:
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
Click to expand...
Click to collapse
I have this problem as well and have emailed HTC but received no reply yet.
Also sometimes it all looks okay and allows calls out but incoming calls go straight to voicemail.
Well, HTC will probable ask you to send your phone for repair.
Actually, this is what they've just replied to my email. But I won't send my phone for a simple flash that I could do my-self !
It seems this is a known issue of the HTC phones (there are plenty of such reports on the internet).
Although this problem hasn't effected my calls on the latest radio version, I do agree that I've often seen what looks like severe signal fluctuations, from zero bars to full bars etc, I've also read about this being an issue on the incredible s
I'm hoping that further rom and radio upgrades will improve this.
Sent from my HTC Desire S using XDA Premium App
It seems that the "Limited Service" issue is caused by a signal loss (i.e. using the elevator for instance) that is never followed by an automatic "good signal" retrieval (i.e. after leaving the elevator and going to a place where signal is usually very good).
~babel said:
Thanks for your feedback.
Would you then say that the "Radio_20.28I.30.085 AU_3805.06.02.03_M" was the answer to your phone bad signal issues ? Then, I might need to use another rom an check if that helps...
Anyway, did you try to change/update phone/radio settings mode (__http__www_google_com_support_forum_p_android_thread_?tid=42655c79e5837499&hl=en) ?
Click to expand...
Click to collapse
I'm afraid that I don't understand what this question? could you PM me?
did it mean did I switch my phone to WCMDA only? if so the answer is NO, mine is set to Auto as around where I live and work there is reasonably good signal.
ben_pyett said:
did it mean did I switch my phone to WCMDA only? if so the answer is NO, mine is set to Auto as around where I live and work there is reasonably good signal.
Click to expand...
Click to collapse
yes, this is what i wanted to know anyway, this didn't change anything for me.
Have you progressed any?
I tried flashing to 1.28 via the RUU at http://forum.xda-developers.com/showthread.php?t=1002506 but it doesn't appear to want to do a downgrade.
I don't seem to get getting the no service at the moment but I am having problems with incoming calls going to voicemail when the phone claims to be connected.
I put my SIM (giffgaff, a MVNO on O2-UK) into my old phone (an XDA Zest) and put an O2-UK SIM into the HTC. At times I could call the XDA with no problem but calling the HTC went to voicemail - two phones next to each other on the same network....
Of course I can't say if this was a problem with 1.28 as I wasn't looking for it but I suspect 1.47 is the problem.
As expected HTC want me to send the phone back which I think I might do and try and persuade them to downgrade it for me.
yes some progress, at last ! I followed the step by step procedure to s-off the rom 1.47.401.4 rom (http://forum.xda-developers.com/showthread.php?t=1194488) and then downgrade to the 1.28.401.7 rom that I was using originally. And now everything works fine...
i could say that once again i learnt that newer doesn't mean better
~babel said:
yes some progress, at last ! I followed the step by step procedure to s-off the rom 1.47.401.4 rom (http://forum.xda-developers.com/showthread.php?t=1194488) and then downgrade to the 1.28.401.7 rom that I was using originally. And now everything works fine...
i could say that once again i learnt that newer doesn't mean better
Click to expand...
Click to collapse
What method did you use to do the downgrade?
I was thinking of trying the method here http://forum.xda-developers.com/showthread.php?t=1190992 which I don't think needs s-off.
Update: I tried the non S-OFF method and have downgraded to 1.28 - I'll see how it behaves now.
I used the PG88IMG.zip method. Basically, you need to copy the roms.zip extracted from the RUU installer to the root of your /sdcard and then reboot your phone to the bootloader.
~babel said:
I used the PG88IMG.zip method. Basically, you need to copy the roms.zip extracted from the RUU installer to the root of your /sdcard and then reboot your phone to the bootloader.
Click to expand...
Click to collapse
I ran the RUU exe directly which seemed less involved. It's looking good so far but I'll need to get out and about and see how it behaves in different locations.
I'll not be in such a hurry to install an OTA next time...
ercm03 said:
I'll not be in such a hurry to install an OTA next time...
Click to expand...
Click to collapse
i see what you mean
solved using the first steps on http://forum.xda-developers.com/showthread.php?p=16796075#post16796075
-------------------------------------------------------
same problem here... tried the PG88IMG.zip method but it said "main version is newer" or something like this... so it didn't work..
do I have to do something before that? I used this ruu:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
and currently installed is this:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed
where can I get a rom.zip that works?
After earlier saying that I'd not experienced this limited service problem, I have now witnessed this a couple of times.
Although, since I applied this
20.4130.0818U_3817.07.00.19_M RADIO I haven't, will re-update post if I do!
This is the Radio that came with the recently leaked Sense SAGA Sense v3.0 ROM and appears to work fine with LBC mod.
does anyone know if one can install this radio over 1.47 with s-off and no root? and if yes - how?
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App
The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...
SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?
I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.
I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.
Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..
Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...
I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.
This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.
And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...
I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?
Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.
I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.
Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.
there were a lot of posts (including one of mine) where people complained that when data network mode was activated and they tried to answer / make a call, they couldn't. and if they did try to, it wouldn't answer and the network bars would become grey (that is, no bars) and it would take a couple of minutes for network to come back (or until you restart, whichever comes first).
anyway, i had some issues with my phone and i gave to the service center. i told them of it and they flashed the stock ROM + kernel. i had some other issues as well, so they said they'll keep the phone for two days.
so i'm getting my phone back tomorrow. now i want to know if flashing the stock firmware did in fact solve anyone's issues. if it did, i'll continue with the stock rom / kernel (please tell me which was causing you the problems). if not, i'll flash a custom ROM / kernel again. please let me know.
also, does anyone know why this happens? is some app causing these problems? because after flashing a new custom ROM (without any user apps installed) i can call / receive properly without deactivating the data network mode.
but, no user apps (and no google account sync either) = no internet traffic.
i'd request the expert devs (ROM makers, kernel developers, testers etc) to please leave their opinion as i'm not the only one who faces this issue. a few of us do and this is one of the few unsolved issues on this forum.
thank you.
Mohit12 said:
there were a lot of posts (including one of mine) where people complained that when data network mode was activated and they tried to answer / make a call, they couldn't. and if they did try to, it wouldn't answer and the network bars would become grey (that is, no bars) and it would take a couple of minutes for network to come back (or until you restart, whichever comes first).
anyway, i had some issues with my phone and i gave to the service center. i told them of it and they flashed the stock ROM + kernel. i had some other issues as well, so they said they'll keep the phone for two days.
so i'm getting my phone back tomorrow. now i want to know if flashing the stock firmware did in fact solve anyone's issues. if it did, i'll continue with the stock rom / kernel (please tell me which was causing you the problems). if not, i'll flash a custom ROM / kernel again. please let me know.
also, does anyone know why this happens? is some app causing these problems? because after flashing a new custom ROM (without any user apps installed) i can call / receive properly without deactivating the data network mode.
but, no user apps (and no google account sync either) = no internet traffic.
i'd request the expert devs (ROM makers, kernel developers, testers etc) to please leave their opinion as i'm not the only one who faces this issue. a few of us do and this is one of the few unsolved issues on this forum.
thank you.
Click to expand...
Click to collapse
ur last custom rom??? wer u using 3g turbocharger??
frankly i don't know what 3g turbocharger is :/
i was using kyrillos' ROM 8.0 (updated to 8.1) and i did run the supercharger script, but i don't think that's what you're talking about. i wasn't using the 3g network.
i've been facing this issue for a LONG time now. i've changed a few ROMs but same effect in all of them. maybe it's something to do with the european firmware (i live in mumbai, india) or something, i'm not sure. are you on vodafone? where in india do you stay?
Well even i am facing this strange network problem but only indoors!!
Outdoors the range is full!!
Since we all flash custom roms that are based on european base, i thought that the problem is related to the modem.bin AKA baseband!!
So i was thinking of just flashing the modem.bin again from any asian firmware.
But before doing that i flashed the old ddjg6 (eclair) rom just to see if baseband flashing is worth it.
Well the network problem was still there!! so the conclusion was that baseband/modem.bin flashing wont affect anything!!
stay happy!!
I cant remember if kyr8 had 3g turbocharger tweaks on build.prop.. But yes with 3g turbocharger on , I hav sum issues with data connection...
-tapatalked by RnB
Btw did u get phone.apk force close while happenin this??
-tapatalked by RnB
phone.apk force closed often. but never because of the weird data connection. i think it just generally force closed.
and i have been facing this problem since kyrillos' 6.0 or 7.0. one of the two. can't remember. also, please look for my "a request for a custom lock screen?" thread in galaxy 3 general and let me know if you can help. thanks!
also, people who are facing such issues please leave your name and "symptoms" here.
yes i also face the same problem of network,no solutions found yet.but i am not sure whether this prob happens to all the network or just VODAFONE,as i am using VODAFONE only.
okay please visit this thread :
http://forum.xda-developers.com/showthread.php?t=1229423&highlight=data+network+mode&page=2
also, here's a bit of my network story if it helps anyone understand this issue :
i bought the phone when it was running Eclair. it worked fine for a few days then i started to face the issue. when i tried sliding the green answering thing to the right, it just wouldn't answer. it would go back in it's place. when people called me, it said it was unavailable. my network used to restart, and calls would randomly get cut and i couldn't call back immediately. i had to wait for 10-15 seconds before i could make / receive any call again. within this time, the calls would dial, but not connect.
so i upgraded to froyo (JP2) from the samsung gallery. my phone worked PERFECTLY for two months or so. no call drops, no nothing. then all of the above started happening again.
i tried flashing different ROMs, kernels etc but nothing helps.
and neo, i face this problem everywhere. indoors and outdoors.
okay so i'm getting my phone back tomorrow. does anyone have any tips for me? something that i should or should not do? like flash a european ROM or just the kernel or not to install a specific app or something?
i do have the same situation. it worked very good by me, till marcellusbe released his cm7 alpha4 i think. i installed it, and since then i have got that network problem, during calls f. example i lose the communication. i dont hear amything, it freezes, and turns back to menu after a few seconds. then i notice that its in the flight mode automatically. and this just happens me when i have got the data connections on. if i deactivate it i dont face any problems like that. i also noticed since i once installed cm7 alpha4 , i have got a strange battery drain. i charg the phone till its fully cjarged, after 3 hours i do not have any battery any more.. help me in that ... PLEASE
i really become frustated the whole time when this happens to me, pls find a solution!! ....
Sent from my GT-I5800 using the XDA mobile application powered by Tapatalk
Try fixin permissions from cwm recovery..
Btw do u use adfree ??
-tapatalked by RnB
Mohit12 said:
okay please visit this thread :
http://forum.xda-developers.com/showthread.php?t=1229423&highlight=data+network+mode&page=2
also, here's a bit of my network story if it helps anyone understand this issue :
i bought the phone when it was running Eclair. it worked fine for a few days then i started to face the issue. when i tried sliding the green answering thing to the right, it just wouldn't answer. it would go back in it's place. when people called me, it said it was unavailable. my network used to restart, and calls would randomly get cut and i couldn't call back immediately. i had to wait for 10-15 seconds before i could make / receive any call again. within this time, the calls would dial, but not connect.
so i upgraded to froyo (JP2) from the samsung gallery. my phone worked PERFECTLY for two months or so. no call drops, no nothing. then all of the above started happening again.
i tried flashing different ROMs, kernels etc but nothing helps.
and neo, i face this problem everywhere. indoors and outdoors.
okay so i'm getting my phone back tomorrow. does anyone have any tips for me? something that i should or should not do? like flash a european ROM or just the kernel or not to install a specific app or something?
Click to expand...
Click to collapse
Well if flashing customs roms and kernels is not helping, you need to try only flashing the stock modem.bin!! I really dont know how to do that safely but people do it!! If you can update the OP like "Please help in flashing just modem.bin" then maybe someone makes and give you an update.zip or a tar containing just modem.bin.
If that too fails to solve your problem, then you must demand a replacement of the handset from samsung! Thats all i can say man!!
Well, the same is happening with me. Even i have vodafone and i live in pune, india. I didnt use eclair for alot of of time so I don't know whether it is a froyo-eclair prob.
The problem that happens with me is that, when i go to my classes (which are in a damn closed area) i dont get any signal. Even though the network bars are zero i still get messeages and phone calls. but when i call someone or message it does not reach. It only happens in some places like my classes and school, but not at my house.
I found a way (not quite conventional but works). I have found that when i flash a rom; irrespective of whether stock or custom; the signal catching is quite stong. But after a month or two it is becomes laggy again. So i flash another rom and again it's good. I dont know whether it is a correct method but works for me.
ak700 said:
Well, the same is happening with me. Even i have vodafone and i live in pune, india. I didnt use eclair for alot of of time so I don't know whether it is a froyo-eclair prob.
The problem that happens with me is that, when i go to my classes (which are in a damn closed area) i dont get any signal. Even though the network bars are zero i still get messeages and phone calls. but when i call someone or message it does not reach. It only happens in some places like my classes and school, but not at my house.
I found a way (not quite conventional but works). I have found that when i flash a rom; irrespective of whether stock or custom; the signal catching is quite stong. But after a month or two it is becomes laggy again. So i flash another rom and again it's good. I dont know whether it is a correct method but works for me.
Click to expand...
Click to collapse
Same place!! Pune!! But i get the problem only in some areas!!!
okay so i've been using the stock firmware for two-three days now. and i've been facing absolutely no network problem as such.
when i press *#1234# here are my results :
PDA : i5801DDJP2
phone : i5801DDJP2
CSC : i5801DDJP2
build info : 2011, 04
now can someone interpret this for me? i mean tell me what exactly this means. which of those is my ROM build, my kernel build, or baseband or whatever.
tell me if there are any custom ROMs / kernels built on these builds (or updated ones, but still indian updates) so that i can test if those work for me?
thanks.
Mohit12 said:
okay so i've been using the stock firmware for two-three days now. and i've been facing absolutely no network problem as such.
when i press *#1234# here are my results :
PDA : i5801DDJP2
phone : i5801DDJP2
CSC : i5801DDJP2
build info : 2011, 04
now can someone interpret this for me? i mean tell me what exactly this means. which of those is my ROM build, my kernel build, or baseband or whatever.
tell me if there are any custom ROMs / kernels built on these builds (or updated ones, but still indian updates) so that i can test if those work for me?
thanks.
Click to expand...
Click to collapse
There is no custom rom build on this build as this build is lot buggy than the other european firmwares.
And that phone is the baseband responsible for the network and all!!
Some people face network problems some dont!!
Here is the phone of i5801ddjp3 firmware
http://www.mediafire.com/?34yrw4b7fe63tri
If you unzip this file, you get the modem.bin
Now there has to be a way to flash this modem.bin over custom firmwares!!
here is the sgs version of it!! This thread contains of all modem.bin of stock firmware to be flashed over custom rom to get better baseband for samsung galaxy s!
Even I used to face similar problem but only on custom rom's not on stock ones.. but using the stock rom's is too boring so now I have flashed with purungrit's rom v.1.0, kernel G3 mod 2.0, and its working fine, no network issues. The theme is good with extended power menu and 5 lockscreen.. u can try this. we can flash custom rom's based on Indian firmwares and face no network problems, problem is only with European or other countries firmwares..
Sent from my GT-I5801 using XDA App
pavankadam said:
Even I used to face similar problem but only on custom rom's not on stock ones.. but using the stock rom's is too boring so now I have flashed with purungrit's rom v.1.0, kernel G3 mod 2.0, and its working fine, no network issues. The theme is good with extended power menu and 5 lockscreen.. u can try this. we can flash custom rom's based on Indian firmwares and face no network problems, problem is only with European or other countries firmwares..
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
But the problem is that indian firmwares are a bit inferior as compared to european firmwares.. If you compare any indian firmware with jpq or jpu you will feel the difference..
I really want someone to try that modem.bin method
Tapatalked from my awesome G3 aka apollo
Ask some of the devs that whether this method can be used n is it safe.. than we can go for it.
Sent from my GT-I5801 using XDA App
pavankadam said:
Ask some of the devs that whether this method can be used n is it safe.. than we can go for it.
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
Yup!! right now i am fighting my exams!!
If somebody can do it!! ;-)
Hi,
Since ICS 4.0.3 and now on 4.0.4, I can't hear my contact and my contact can't hear me on the first call.
I tried to use the speaker, the headphones or a Bluetooth earpiece but none of these work.
The second call is always alright, regardless the output (earpiece, speaker, headphone, ...).
This is not an operator issue, since I changed and had the problem before.
Does anyone encounter the same issue?
The only workaround I found yet, is to call voicemail on the first call so that the second call is alright.
I tried to factory reset the phone while on 4.0.3 and hoped the 4.0.4 update change something on that matter but it didn't.
Thank you for your replies.
Some things to try:
-Flash a different radio (can find all of them in the dev section)
-Full wipe (data/factory reset, format /system, format /boot) and reflash your preferred ROM
I've never had the problem, good luck getting it fixed though.
Thank you for your answer. I might try these when I found out how.
I've seen this bug on many many NEXUS S (4.03 & 4.04)
I think ALL NEXUS S have this bug with all mobile carriers.
Sometimes, particularly if the phone was idle, when you call someone : there is no sound.
It's like the speaker and the microphone were off.
You can raise this bug very easily, maybe 20% of the calls.
Hi,
I have the same issue, in France, with Orange.
Does someone has an idea, even a piece of solution ? It's my work phone, and it's very annoying when a client calls me or when I have to call him in return.
I can test, try .... I need a quick solution
Thanks
Sylvain
Are you using a custom ringtone at all? I remember reading somewhere that if you use a format other than .ogg sound file this can happen. I had it happen a few times in the past. If you're using a different format there is Online Audio Converter to convert to .ogg here: http://media.io/
Hope this helps
Conversion of my ringtone done .. waiting for some calls now
Sylvain_D said:
Conversion of my ringtone done .. waiting for some calls now
Click to expand...
Click to collapse
Don't forget to go into sound settings and choose your new ringtone, otherwise it will be unknown. I forgot after just moving the file over to my phone and couldn't figure out why it wouldn't ring.
Sent from my Nexus S using xda premium
Converting the ringtone is not a solution. I'm still having the same problem ...
I'm sorry, I misunderstood the OP. I thought you were saying there was no sound as in not ringing on the first call after reboot. Tells me not to browse XDA after working 22 hours lol. What rom/kernel are you using?
No problem.
I have the official 4.0.4 ROM.
The problem was the same with the 4.0.3 .. actually, after the update to 4.0.4, the issue is more imporant.
Someone suggested to flash another radio ROM. I check the topic on that matter and wonder if I need to be rooted to do that. There's no mention you need to be but saving /efs folder suggests you must be.
Also, instead of flashing the radio, can I tried to fully wipe the phone? I heard the factory reset do not reset everything on the phone, is there a way to do this?
Thank you
Hello,
I'm back from a week-end in spain (I'm french). I didn't have any sound problem. So it seems that it really linked to the provider (I have a contract with Orange).
I'll try to look at the post to change the radio ROM.
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
pmpollet said:
Someone suggested to flash another radio ROM. I check the topic on that matter and wonder if I need to be rooted to do that. There's no mention you need to be but saving /efs folder suggests you must be.
Also, instead of flashing the radio, can I tried to fully wipe the phone? I heard the factory reset do not reset everything on the phone, is there a way to do this?
Thank you
Click to expand...
Click to collapse
I tried to wipe the phone ! Same issue
Sylvain_D said:
Hello,
I'm back from a week-end in spain (I'm french). I didn't have any sound problem. So it seems that it really linked to the provider (I have a contract with Orange).
Click to expand...
Click to collapse
Hi, I'm french too and have the same problem but with a different provider (Bouygues). In my opinion, it's not related to the provider.
Like already said, it seems that the phone cannot get out the speaker and microphone from idle for the first call.
Note that today i've got twice the problem and success on the third call...
If someone find a solution, let me know
Hi,
Is this bug only encounter by people from France?
try to change radio you can search which radio suits on your place.. or flash another rom you can choose bunch of good rom with 4.0.4 and kernel
heres the link of nexus s radio http://forum.xda-developers.com/showthread.php?t=1116884
Someone already suggested that. Unfortunately, to my understanding, to proceed you have to be rooted and save some folder (/efs or so). Since I don't know how to root the phone and don't want to loose the warranty, i did not take that option yet.
I have the same problem (in France too). In my case the problem is even worse: call failure reaches nearly 100% when connected to a wifi network.
Hello,
I've the same issue.
my phone: Nexus S I9020a / ics 4.0.4 / Radio:XXKL1 / Carrier: Orange in France.
I used this page to try different radio : Radio GUIDE.
I was unable to flash UCKJ1 : fastboot say write error, and CWM say ok but the baseband wasn't changed. maybe because it was unsigned
I then flashed with success XXKF1. (this one was signed).
I'v tested with two call, and that's worked (I'll have to wait to be sur it's realy worked).
On the Radio page there is a "Warning do not flash on 9020a" for the XXKL1 radio : maybe the explanation for 9020 owner.
after deeper test : XXKF1 radio doesn't fix the problem.
I've swtiched to GB 2.3.7 / CM 7.1 / Lucid-Kernel-blue and the problem is gone away.
I've still the XXKF1 radio, so the radio doesn't seem to be the problem. It's an ics 4.0.3 problem (the radio of ics 4.0.3 is OK).
GB 2.3.7/ CM7.1 is far more responsive for me (and have a kernel with pre-2.3.3 color driver ), ics don't miss me. I've my phone from only a month and haven't tested GB before the sound problem.