Right.
So, these days I had problems with my phone and have been forced to flash a new .sbf on my Defy+.
Now, my main question is: What are the main issues with 2.3.6? As far as I read there weren't issues with some .sbfs. (and there weren't any reported with my .sbf.)
Had read about issues like random reboots and inconsistent Wi-Fi connectivity on 2.3.6. Though i had issues of random reboots only, Wi-Fi was fine on my defy+, when i was on 2.3.6 firmware version ending with 1321.
andr0idfreak said:
Had read about issues like random reboots and inconsistent Wi-Fi connectivity on 2.3.6. Though i had issues of random reboots only, Wi-Fi was fine on my defy+, when i was on 2.3.6 firmware version ending with 1321.
Click to expand...
Click to collapse
what can i do if i have these probelms?is there any way of solving this??
The best you can do, if you want to stick to stock ROM, is to upgrade to the latest version available i.e. 231x. Keep in mind that it has BL7 and it's a bit difficult to root.
The other option is to switch to CM7. I would recommend CM7 builds by FuZZ_. I never had any problems after switching to Cyanogenmod.
Related
Alright, so I'm quite cautious before I proceed with the update but I've been hearing mixed results with the 2.3.5 update. I pretty much have the update ready to go in the ext SD card.
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
As for null IMEI, what significant impact would it have on my phone?
I'm really keen to go on Gingerbread as there doesn't seem to be any OTA updates to 2.3.5 here in NZ...
Current Android Version: U8800 V100R001C00B136
Cheers
I have been upgrading from stock 2.2 and did not have any problems at all. All went smooth and everything is working as it should. I am using 2.3 beta 1 update, because it has unlocked bootloader, otherwise it is preety much the same as final 2.3 release.
oh, do the problems people experience persist in beta 1? or over the official one?
Like I said, I did not have any problems with it and I had stock phone just like you (no costum rom, no costum partition). I know people have reported many problems with these updates but it works for me. If someone has different experience please post it and write in what state your phone was before update ( costum rom, partition, etc...)!
when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.
Wurstwa55er said:
when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.
Click to expand...
Click to collapse
did you update to the beta builds or the 'original' build? I guess I won't have to back up if its only a rare minority experiencing these faults.
Stephen289 said:
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
Click to expand...
Click to collapse
I have a U8800Pro so I can't offer you an answer as to whether you should upgrade, but all I can say is:
If your phone is rooted, use http://forum.xda-developers.com/showthread.php?t=1325036 to back up your IMEI. It's worth it anyway, even if you don't plan to upgrade
From what I've read, touchscreen issues seem to be occuring for those with Atmel screens (and there's a report of an Atmel screen going bad on its own anyway), not those with Synaptics ones. This is what I've gleaned by reading U8800 threads; again, I have a U8800Pro (which all come with Synaptics screens). You can use the tool Elixir from the Market or dial #*#2846579#*#* and navigate through the menus to find out what touchscreen you have
HI guys, I have a big problem with my nexus s i9023, i not have signal,
i'm trying to flash cyanogen 9, cyanogen 7, stock 4.0.4, AOKP build 28, KI1 radio, KB3 radio and KF1 radio, but i haven't found a solution yet....
can you halp me
sorry for my bad english
any one can halpme???
sorry for my bad english
tobyax said:
any one can halpme???
sorry for my bad english
Click to expand...
Click to collapse
Have u tried stock rom?
If the problem still exist maybe it's hardware problem
tobyax said:
HI guys, I have a big problem with my nexus s i9023, i not have signal,
i'm trying to flash cyanogen 9, cyanogen 7, stock 4.0.4, AOKP build 28, KI1 radio, KB3 radio and KF1 radio, but i haven't found a solution yet....
Click to expand...
Click to collapse
First, just try a re-boot, at least. (Sorry if you've tried that already!)
Running a slightly earlier CM9 version, still on 4.0.3 (just went up to 4.0.4 the other day), I sometimes had slight problems going from places with no signal (eg. under-ground transport) back to places that should have signal, but not showing up. I had the phone on deep-idle at that time - great for battery, but a bit experimental glitchy elsewhere...
PS: are you on CM7 or CM9 - you mention both, but must be CM9, right?
now i am on stock 4.0.3 and not have signal... i try other sim card and i have the same problem....
sorry for my bad english
Can you check in Settings/About Phone/Status if your IMEI number is correct?
If you have only zeros, this might be a problem.
the imei is correct it's the same of the one in the behind
hardware problem?
I'm new to the forum and have had my Defy+ since Jan 2011 but couldn't find an answer to the issue I have. My Defy+ ME525 China Retail now has 45.0.2310.MB526.AsiaRetail.en.03 installed and build 4.5.1-134_DFP-231 which has been stable since last December when I loaded it via RSD Lite. My issue is despite getting rid of the mainland China retail version, they denied access to Google Play, many APK files, and ALL social media that wan't Chinese, I am still having issues with Google+ crashing all the time. My MotoBlur is configured for Twitter and Facebook but it won't update them or receive updates when I am out of China (tried when in Cambodia last week and no updates worked either way). When out of China I was able to download and get Facebook to work but not Google+.
I was debating to re-image with DFHKT_U_4.5.2-109_DHT-25-4_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTHKTW_P0 24_A023_HWp3a_Service1FF but am not sure if this would fix that issue or not, not a big issue just a minor annoyance. I have also seen issues with the camera causing the phone to reboot, lockups when turning on the APN and sometimes airplane mode just applying itself out of the blue. Is the above US version more stable and would it work better or should i just deal with the minor issues and leave well enough alone?
I also find the phone is slower and hangs more often now and not sure if I should wipe it and start over or not? The phone is NOT rooted, RDS Lite loaded the Asia Retail version fine, I need that for sending and receiving SMS in Chinese characters. Thanks!
Defy is not region coded. You can use the other sbf, but it will not really increase performance, only your Google problems should be solved(and by a clean install stability issues should disappear). Your other problems should not occur on a clean install, try wiping data and cache to check if the problems recur
Sent from my MB526 using Tapatalk 2
Simple answer - NO.
When a new software release is made for an OS, all the developers would have done is test it on a very few devices within the developers and then roll it out to testers. And after analyzing the bugs identified from these testers, the developers sit on fixing it and finally come up with a release. Now would this release be bug-less? Absolutely not! Remember, its only been tested amongst a very few number of people and the rolling out happens to thousands residing in different parts of the world. If you think about it, what these updates are gonna deal with is a varied number of users, different carriers, sim make etc etc.
Take for example, for Indian users, the 4.4.2 update has been rolled out for quite a while. Lots of bugs were identified since then and the forum managers have been collecting data from the subscribers for quite a while now (Almost 4 months). Still the fix has not happened. And now 4.4.4 is out and issues persist.
I hvae been using 4.3, 4.4.2, then CM11, Mokee ROM etc etc, and now Im finally back to stock 4.3, coz thats the most stable version. So if you are someone who is interested in trying out new releases, please go ahead, but if you are someone who needs a stable ROM with no signal drop issues, please stick to 4.3.
totally disagree. I have european version Moto G with stock 4.4.2 and everything is working perfeclty. Try to wipe you Moto or flash any other rom.
seems like pebkac not buggy firmware . otherwise every single guy would be facing same problems and that's not happening .
ovitz said:
totally disagree. I have european version Moto G with stock 4.4.2 and everything is working perfeclty. Try to wipe you Moto or flash any other rom.
Click to expand...
Click to collapse
Just to clarify, did you receive an update package sometime after the primary update?
4.4.3 works fine on my US GSM moto G. But it might be different for others.
Also, add a warning to the OP that if you're already on 4.4.3+, you can't downgrade anymore. Motoboot from 4.4.3+ doesn't seem to like downgrading anymore, unfortunately.
4.2.2 works great, no signal drops or anything. Waiting for eupean 4.4.4. :good:
Sent from my XT1032 using Tapatalk
Question is whether downgrading is possible from 4.4.4 ?
I totally agree to ovitz. Updates are supposed to fix issues with older versions of the software. My moto came with 4.4.2 and i never had issues with signal drops. I am from India. Btw it's always better to reset phone after the update.
I agree with you OP on some extent. I also recently downgraded to 4.3 from 4.4.2 just for the lulz, because I was getting "image is too large" error but surprisingly today the flashing was successful. The battery timing has improved, dialer app is cooler than that of the 4.4.2. I'm finding these changes quite interesting because I didn't stay with 4.3 for too long; my Moto G received the KitKat update the moment I powered it on for the first time.
techpick said:
Simple answer - NO.
When a new software release is made for an OS, all the developers would have done is test it on a very few devices within the developers and then roll it out to testers. And after analyzing the bugs identified from these testers, the developers sit on fixing it and finally come up with a release. Now would this release be bug-less? Absolutely not! Remember, its only been tested amongst a very few number of people and the rolling out happens to thousands residing in different parts of the world. If you think about it, what these updates are gonna deal with is a varied number of users, different carriers, sim make etc etc.
Take for example, for Indian users, the 4.4.2 update has been rolled out for quite a while. Lots of bugs were identified since then and the forum managers have been collecting data from the subscribers for quite a while now (Almost 4 months). Still the fix has not happened. And now 4.4.4 is out and issues persist.
I hvae been using 4.3, 4.4.2, then CM11, Mokee ROM etc etc, and now Im finally back to stock 4.3, coz thats the most stable version. So if you are someone who is interested in trying out new releases, please go ahead, but if you are someone who needs a stable ROM with no signal drop issues, please stick to 4.3.
Click to expand...
Click to collapse
While I do agree with you for most of what you said, not everyone has bugs or issues with their phones on 4.4.3/4.4.4 upgrade. I myself has had one bug that came with the phone since 4.3 and it's worst now on 4.4.3 and ironically, I've gotten all the bugs on the 4.4.3 that others were getting on 4.4.2. I ended up putting on CM11 because it was getting to me.
P.S. It's impossible to downgrade from 4.4.3/4.4.4. I would love to downgrade back to 4.3. Never got the chance to see how it behaved on my phone because I updated to 4.4.2 the moment I booted for the first time.
Did I mention the "Sign in to WiFi" error on the 4.4.2? That's annoying as hell.
usertag said:
Question is whether downgrading is possible from 4.4.4 ?
Click to expand...
Click to collapse
It is possible!, download the 4.4 official ROM and do a fastboot and install all the IMG files.
Thats how I did it,
chrisdf said:
It is possible!, download the 4.4 official ROM and do a fastboot and install all the IMG files.
Thats how I did it,
Click to expand...
Click to collapse
but you can't downgrade the bootloader, so didn't you get any errors?
Not that guy, Don't touch the motoboot and you should be fine
There's no point of updating your phone unless youare receiving it over OTA. Doing it manually is risky. The only thing that you'll get is new AOSP dialer and few security fixes. There's no reward..no improvement in performance as well as in camera quality. People are reporting bugs all over the globe and they desperatly want to switch back to 4.4.2. Few have them are also facing downgrading issues.
And you want to go through all this for just a minor update? Android L could be a good reason as it is worth updating even after bugs. But a minor update is definitely not.
If some one will ask me which is best ROM for my moto g? I would say Stock 4.4.2. I tried all custom ROMs but no one was as smooth as stock 4.4.2.
Consequences be damn'ed.
Simple answer- yeah, well, that's just like your opinion man.
Indian user. Unlocker my bootloader, Converted to GPE while on 4.4.2. The GpE move was made partly because I had jo desire nor the use if a second sim and mostly because I wanted a clean OS. Period.
Got instant OTA update to 4.4.4 to the day it was pushed.
No issues so far, None in fact and it's been over a week or thereabouts(I admit to the likelihood of me being an isolated case)
Lastly, to each his own.
Android is meant to be taken care of AS WELL tinker every single detail or option if you have the cojones for it. Ciao.
:thumbup:
Sent from my XT1032 using XDA Free mobile app
I have just upgrade to 4.4.4 XT1033 (Malaysian), noted the missing 2 empty simcard icone and new rather flat dialer! nothing much has changed and certainly hasn't noticed any issue mentioned herein!
If one were to go by op opinion then they would be using 4.3 for the rest of the devices life ! I wonder what his comment would be once L comes to our device.
I have to disagree the OP as an xt1033 owner since march 2014.
Android 4.4.4 OTA for moto g helps fix various sw issues and increased performance,new baseband to aid the radio issues. Media playback is improved. The device is more of a swiss-tool now.
GPe edition of Moto G running KTU84P.M003 like a dream and eats more battery,too. I wish i could have flashed it earlier.
Semseddin said:
GPe edition of Moto G running KTU84P.M003 like a dream and eats more battery,too. I wish i could have flashed it earlier.
Click to expand...
Click to collapse
Just curious, if it eats more battery how come you call it a dream?
Hi,
My newly bought S7 edge is having problems. I noticed that after some time, it is not possible to make any calls or use data even though the range is shown as full in the status bar.
After thorough trial and error, found that the issue is coming only if 4G/LTE is enabled. Otherwise, if i switch to 3G, it works. This is the issue for both the sim slots :crying:
Anyone else who has had this issue . I'm running the latest October patch of Android 6.0.1. Is this a software bug or a hardware issue. Any help or suggestions would be much appreciated
U can try reflashing an old firmware to discard that the update caused the problem.
alehawk said:
U can try reflashing an old firmware to discard that the update caused the problem.
Click to expand...
Click to collapse
The problem is since, it is a new phone, I don't know whether it is the update which causes the problem. I upgraded the software immediately after receiving the phone. Is anyone with the latest october update having the same issue?
I checked online, and it seems like some people have had similar issues in past. Just not sure whether it is a software issue or a hardware. And I honestly dread doing the set up again, as unlike past times (i always root my phone, but because of knox tripping, haven't rooted yet), when titanium backup was there, this would mean lots of time on re-setup
MMMmmm I only had that problem on a phone that wasnt 4g capable but had that option enabled but was because I flashed a firm that wasnt supposed to use.
If its new you can go to warranty and exchange for a new one but my curiosity will remail if it was about the october patch...
I have the same issue... it might just be a bug that will be resolved in the next update
amritpal2489 said:
I have the same issue... it might just be a bug that will be resolved in the next update
Click to expand...
Click to collapse
Oh, that's a relief. So, this issue came after updating the software. Before that, it was working for you?
Hrithan2020 said:
Oh, that's a relief. So, this issue came after updating the software. Before that, it was working for you?
Click to expand...
Click to collapse
Yes
amritpal2489 said:
Yes
Click to expand...
Click to collapse
I was finally able to get the 4G mode also working. Not exactly sure what did the trick.
Here's what I did:
1. Flashed an older version (Aug version) which I found on samfirwmare -> Didn't work
2. Flashed an even older version (July version) -> Didn't work
and then updated the software -> started working
The funny thing is the software is the same as before (the same version as was earlier - October build)
Mods, please close the thread
Hrithan2020 said:
I was finally able to get the 4G mode also working. Not exactly sure what did the trick.
Here's what I did:
1. Flashed an older version (Aug version) which I found on samfirwmare -> Didn't work
2. Flashed an even older version (July version) -> Didn't work
and then updated the software -> started working
The funny thing is the software is the same as before (the same version as was earlier - October build)
Mods, please close the thread
Click to expand...
Click to collapse
Great to see your issue is resolved