Database Users

Too many issues so few roms

3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.

if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.

The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems

if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband

thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot

Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App

thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone

Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.

im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.

thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....

i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?

thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine

damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated

I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved

i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox

thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...

i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.

thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....

maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.

lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?

had lite'ning 1.4, updated to 6.1, now wifi issues

ok basically i bought the phone second hand with lite'ning 1.4 on it and the wifi worked perfectly ok all the time. Since it was very old i updated it to 6.1. ever since then I have had issues with the wifi. it will connect perfectly fine to the router but i have no connectivity from it, nothing will get any net access at all. This is also not 100% of the time, its MOST of the time but not all, i do have moments where it does work fine. very very odd.
I have since tried updating the kernel to ninpho 2.1.3 from the 2.0.5 that comes with lite'ning 6.1, but that made no difference.
Someone suggested i try a wifi fix app from the market so i downloaded "FXR wifi fix and rescue" and ran that. It ran ok, wiped all my wifi settings and i restarted, but it has not solved the problem at all.
i find it very very odd since if it was a problem with the kernel OR the rom then everyone would surely have exactly the same problem. I know some people report wifi issues but most dont seem to.
anyone have any other ideas?

The odd thing is that it worked before the update. That means that it will most likely be software related.
You could try flashing something totally different like MIUI or CM. They provide kernels too, so this might resolve it, if your kernel and rom don't "like each other". This usually shouldn't happen, but updates breaking wifi shouldn't too. So it might be worth a try.
Sent from my GT-I9100 using XDA App

if i went to something completely different i assume i would have to factory reset the phone to wipe it first? (or factory reset it AFTER installing the new rom?)
was trying to avoid wiping it as i dont want to spend endless hours setting up everything again. i have backed it up with the free titanium but id still like to not have to find out whether the restore actually puts everything back properly
its very odd as its not completely broken, sometimes it does actually work, and it always connects to the router itself without any problem.

Probably wrong modem for you, flash another one. You can find modems in the developement section.

ok thanks I will have a look at that. It is currently on XXKH3 which is what came with lite'ning 6.1. i am confused though, all SGS2 hardware is identical so if this modem in 6.1 is causing this issue, wouldnt it affect every sgs2 that uses that modem?
I found the "shipped modem collection" post in the original development thread so have asked in there which modem i should try.
ok apparently i should try XXKI3. for o2 UK provider.
although i have now read that wifi is not managed by modem but by kernel only. if this is true then modem will not help me

Well, if the wifi is not managed by the modem, try what I proposed you earlier. The simplest would be to flash CM. Make a backup of your current rom, then do a full wipe and install CM.
As for your data:
1. Titanium backup restores your apps with their data (if you wish). That means that, for example, your games will keep their saves, other apps their settings and so on.
2. Assuming that you have a google-account, you don't have to worry about your contacts, calender,... Just sync it before you flash.
3. The backup you make in CWM will backup everything in case CM doesn't work for you.
In case it does work and you'll want to keep it, the other two other parts of your backup will minimize the remaining work. Note that you shouldn't restore "standard"-apps like the media-player or the SMS-app if titanium backup tells you that the app is not currently installed on your fresh CM. This means that CM uses it's own media player or SMS app. It could lead into problems to mix TouchWiz apps with CM.
A side-note:
Don't use the "stable" version. It had more bugs than expected and they made it a RC again. However, it is still in the stable folder. Get the latest nightly.
Sent from my GT-I9100 using XDA App

yep i think it is kernel. just noticed that 1.4 had cf-root, 6.1 had ninph 2.0.5 and i then tried ninph 2.1.3 and both ninph's have had the issue. i just tried speedmod k2-13 as i already had that downloaded and so far the wifi has been ok so hopefully thats it fixed. i guess it was something to do with ninph (i am thinking that because i have it set to sleep the wifi when the screen is off that somehow ninph is not handling this properly).
possibly one good thing to come of it all, ive updated the modem to KI3 which is supposedly the best one for o2 UK so i may even save more battery and speedmod is meant to be really good for battery too. I still have lite'ning on it at the moment.
i might have a look at CM anyway but i do kinda like lite'ning (although i havent actually used anything else since the phone came with it!)
also need to look at wakelocks to see if i can save some more, although not sure how i go about 'fixing' them at the moment

The choice between CM, MIUI and the stock mods is the choice between three different UI's.
I've had all three of them for some time. As you got CWM, you can just create a backup and do a sightseeing tour through the world of custom roms. Believe me, it's absolutely worth it. To get an idea of the main differences, I've written a short overview for you:
Stock mods use Samsung's TouchWiz. The default user interface that you get when buying a Samsung Android phone. So it mostly looks and "feels" the same and you can't do much about it.
CyanogenMod gives you the pure Android user interface. It's the closest to the Nexus phones by google, but gives you some extras. It is much more customizable than stock roms. It's sleek and fast.
MIUI is a whole different story. They're "Redefining Android". I think calling MIUI an "Android custom rom" is an understatement. It's an entire OS. The result of putting the best from iOS and Android into one powerful OS. It adds tons of useful(!) features. If you've ever used Windows Phone 7 or an iPhone, you know what a big step forwards Android is when it comes to features. Switching from Android to MIUI is just like that. There is just so much more. It is BY FAR the most customizable Android you can get.
Wow. If I look at how long the texts are, I see that I'm pretty biased. :O
Well maybe because I've switched so often between them. The stock roms had no chance, because after I used one of the others I found out that TouchWiz doesn't cut it anymore. I hate how "iPhone-ish" MIUI is, but if I flash CyanogenMod I just miss so much. Giving you a list of what MIUI adds would be another long post of this length.
Sent from my GT-I9100 using XDA App

cool thanks will have a look at MIUI at some point.
spoke too soon earlier, the wifi is maybe slightly better on this speedmod kernel BUT when i wake the phone from sleep, it takes about 30 seconds before i can connect to the net with anything. the phone connects to the wifi straight away, but i have no connectivity for a good 30 seconds and then it starts working. (its not the router, i am getting a connection and an IP pretty much as soon as i wake the phone). also the 30 seconds or so only STARTS once i try to connect to something. if i wake the phone and do something that does not want net access for a few mins and THEN try to get on the net via wifi (which shows as connected the entire time) then again i have to wait about 30 seconds from when it first tries to connect before it will start working.

ok slightly confused again.
I have lite'ning 6.1, speedmod k2-13 kernel and XXKI3 modem. I am trying to get cwm installed so i can make a full backup image of the entire phone while i try to sort out the wifi issues. i downloaded rom manager from market, and selected the firstion option in the app 'flash clockworkmod recovery'. it brings up a menu saying 'confirm phone model' with AT&T galaxy S2, a coulpe of i9000s and a plain "Samsung Galaxy S2" which is the one i selected. it downloads something and says successfully downloaded clockwork mod recovery.
i then choose reboot into recovery. when rebooting it attemps to install something but then says "failed to verify whole-file signature" and aborts. so im just stuck with the standard recovery instead.
so now im confused, have i missed something?

Ehhhhm, you don't need to do it.
Have a look at the features of the speed-mod-kernel:
Current features:
Root and CWM:
- Automatically installs root (su)
- CWM 4.0.1.5 recovery
It already installs it right away.
Just in case you messed something up. You should flash the kernel again.
Besides that you don't need the RomManager at all. Just shut your phone down and boot into the recovery with the key-combo. Create and restore backups from there.
Sent from my GT-I9100 using XDA App

!!!Stop SAMSUNG GALAXY S3 FREEZING Problems!!!

Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.

Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom

kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:

Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...

what?
i havent got this

Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.

jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?

Read the freezing thread sticky .
Delete this non working fix as well .

JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?

Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.

Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.

[Q&A] [ROM][Official] CyanogenMod 11

Q&A for [ROM][Official] CyanogenMod 11
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

i have lag on multitasking for this rom anyone have lag same as me ? can i fix that ?
sorry for my bad english

Unable to flash CM11 onto Moto XT905 (moto_msm8960_jbbl)
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice

timhowes said:
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice
Click to expand...
Click to collapse
Does your XT905 have official KitKat? If not, please fall back to moto_msm8960_jbbl and use a different recovery (made for JB BL).
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

timhowes said:
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice
Click to expand...
Click to collapse
The error message is quite clear. When installing ROM (e.g. CM11) signed with keys different from what is currently running on your device (stock Motorola firmware), you have to wipe data / factory reset.

I have installed the 11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl after doing a rsd lite flash of VRZ_XT907_9.8.1Q-94-1_CFC.xml with the downgrade script provided in another topic. I have noticed that the WiFi has had severe bandwidth issues regardless of whether bluetooth is enabled etc. Optimization is off and i also tried setting the frequency to 2.4GHz only.
I have done multiple clean reflashes incase it was an underlying bootloader bug but I haven't had any luck. Any help would be greatly appreciated.

kabaldan said:
The error message is quite clear. When installing ROM (e.g. CM11) signed with keys different from what is currently running on your device (stock Motorola firmware), you have to wipe data / factory reset.
Click to expand...
Click to collapse
Thanks for this kabaldan. However on every attempt I wiped system, data, cache and did factory reset (data & cache I believe) before flashing CM11 and got the same error message. Do you know why this would be? In each case, recovery said the wipe had been successful.

timhowes said:
Thanks for this kabaldan. However on every attempt I wiped system, data, cache and did factory reset (data & cache I believe) before flashing CM11 and got the same error message. Do you know why this would be? In each case, recovery said the wipe had been successful.
Click to expand...
Click to collapse
See what I said and check if that's the reason. I'm not so sure because I don't own a XT905.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

AndyYan said:
See what I said and check if that's the reason. I'm not so sure because I don't own a XT905.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Thanks. Apologies but I am still a little confused... I don't have official KitKat. My system version is 98.21.7.XT905.Retail.en.AU.
I'm not sure what you mean by "fall back" to moto_msm8960_jbbl - I thought these were the CM11 ROM images I can't install. And how do I know if my recovery is for JB bootloader? I have a JB bootloader and have successfully flashed versions of TWRP (currently v2.3.2.3) and CWM. Would these even flash if they weren't compatible with my bootloader?

timhowes said:
Thanks. Apologies but I am still a little confused... I don't have official KitKat. My system version is 98.21.7.XT905.Retail.en.AU.
I'm not sure what you mean by "fall back" to moto_msm8960_jbbl - I thought these were the CM11 ROM images I can't install. And how do I know if my recovery is for JB bootloader? I have a JB bootloader and have successfully flashed versions of TWRP (currently v2.3.2.3) and CWM. Would these even flash if they weren't compatible with my bootloader?
Click to expand...
Click to collapse
You're now on JB BL and *should* flash moto_msm8960_jbbl instead of moto_msm8960, as the latter is KK BL-only.
Dhacker29's site used to have a copy of TWRP 2.7.0.0 for JB BL, but seems like the site is down, so I uploaded a copy: http://d-h.st/MSe , grab this and use it to flash CM11 JB BL mentioned above.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Hi, so my wife's Razr M is on the official Kit Kat Bootloader, and I even did a factory reset and fresh install of the M11 build. Everything seems okay, and stable, but WiFi and Bluetooth refuse to turn on. I'll tap the "on" switch, and it'll say the radio is turning on, and then after a few seconds, returns to the off position. Is this known or common on this ROM, because I swear Bluetooth used to work.
I can try to see if I can pull a logcat or something if this is not common or understood yet, this this the right forum for this now?

bofis said:
Hi, so my wife's Razr M is on the official Jelly Bean Bootloader, and I even did a factory reset and fresh install of the M11 build. Everything seems okay, and stable, but WiFi and Bluetooth refuse to turn on. I'll tap the "on" switch, and it'll say the radio is turning on, and then after a few seconds, returns to the off position. Is this known or common on this ROM, because I swear Bluetooth used to work.
I can try to see if I can pull a logcat or something if this is not common or understood yet, this this the right forum for this now?
Click to expand...
Click to collapse
Did you turn on your Wifi, bluetooth, etc... before installing CM? I didn't have any issue on the test phone at work with the JB BL after installing the latest CM build. Kit Kat on the other hand... well that's why my main phone is on the stock rom until they can fix that issue.

Okay, I take it back, she's on the Kit Kat bootloader, and running CM11 now. I did a full wipe and installed the M11 build, which I believe only works under the Kit Kat Bootloader now. As I wiped, it should not matter how I had set WiFi or Bluetooth before. So my question is, under the KK Bootloader, does WiFi or Bluetooth work for anyone? Because they do not turn on for me.

I've been running CM11 for a long time.
took the 10/25 update Whisper Push, Hangouts and Goggle Play services, I'm getting "Unfortunately, Hangouts has stopped" error msgs
same with the 10/26 update, what's up?

TwoBuells said:
I've been running CM11 for a long time.
took the 10/25 update Whisper Push, Hangouts and Goggle Play services, I'm getting "Unfortunately, Hangouts has stopped" error msgs
same with the 10/26 update, what's up?
Click to expand...
Click to collapse
I too have been having issues with the latest nightlies. I set an alarm from the Clock app and it will skip the first couple alarms I set, then notify me an hour later that I missed my alarms. Also I am constantly getting errors that systemui.process has stopped whenever I try to turn off an alarm and during normal operation. Other things such as random reboots, and web pages not loading, which makes me refresh the page for it to actually load.
I think I'll revert back to around 10/16 because that was when I was having problems at all.

I restored a good running backup from 9/26 and everything is running great.
the 10/27 update was posted, I updated to the 10/27 nightly and seems to be ok so far.

Wifi, Bluetooth, Microphone
Hi,
I have had the following issues with multiple versions of CyanogenMod on the KK bootloader (unlocked).
Wifi only works on 5 GHz
Bluetooth does not connect to any device
Microphone only works when I am on speaker phone
Ear speaker is not very loud
Have to press the power button 2 or 3 times before my phone turns on
Is there something missing from my phone? I know some people have had issues with wifi and bluetooth. I could not find a fix that worked; unless I missed something. I'm going to try installing a stock rom now to see if it works. I don't know what else to do.
If anyone has any fixes or ideas, I would really appreciate it. Thank you.
*EDIT*
No luck with stock. Same issues with wifi and bluetooth
Microphone works

Razr M Telstra xt905 dimmed screen CM11 Snapshot M11
Quote:
Originally Posted by Rufus
... and add this to my build.prob and it seems to fix the 'sleep of death' - JBBL:
ro.mot.ds.fastdormancy.disable=true
Works for me for months on end like that, have to edit after each flash tho.
Although it has only been a few minutes since I rebooted. Not only has the above setting appeared to have stopped the 'sleep of death' (which I took as where the phone takes a number of attempts to wake it up), but it also appears to have fixed the issue with the screen coming back on, overly dimmed!
Of course, now that I have written this, it will all start to behave as it did before, but here's hopping it continues like this."
I have just flashed CM11 snapshot M11 JBBL on my Australian Telstra XT905 Razr M. It's all working well so far except for two issues. The first is listed above where the phone screen will sometimes come on dimmed. How do I enter the above into build.prob to fix this issue. (I'm an amateur)? Is it through the terminal window? Detailed instructions would be great please.
The other thing I've noticed is the battery seems to be draining faster then the Telstra stock 4.1.2 rom. Any feedback would be appreciated especially from Australian Telstra users.
Cheers

inter111 said:
I have just flashed CM11 snapshot M11 JBBL on my Australian Telstra XT905 Razr M. It's all working well so far except for two issues. The first is listed above where the phone screen will sometimes come on dimmed. How do I enter the above into build.prob to fix this issue. (I'm an amateur)? Is it through the terminal window? Detailed instructions would be great please.
The other thing I've noticed is the battery seems to be draining faster then the Telstra stock 4.1.2 rom. Any feedback would be appreciated especially from Australian Telstra users.
Cheers
Click to expand...
Click to collapse
I've tried adding that line to my CM11 Nightly build already, no effect, screen still dimmed after a quick wake in dark places. You can try anyway, but BACK UP BEFORE YOU PROCEED!
Since you don't look like you're familiar with doing this, I think using Root Explorer's inbuilt editor should be a bit easier. Go to /system and find build.prop. Long press and open it in a new window. At the bottom of the file, press enter for a new line and enter the above. Save and reboot.
Stock usually have better battery life than custom ROMs, that's normal.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

AndyYan said:
I've tried adding that line to my CM11 Nightly build already, no effect, screen still dimmed after a quick wake in dark places. You can try anyway, but BACK UP BEFORE YOU PROCEED!
Since you don't look like you're familiar with doing this, I think using Root Explorer's inbuilt editor should be a bit easier. Go to /system and find build.prop. Long press and open it in a new window. At the bottom of the file, press enter for a new line and enter the above. Save and reboot.
Stock usually have better battery life than custom ROMs, that's normal.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Thanks for the reply. I had the same result as you. The screen is still dimmed after waking sometimes. I guess I'll just have to put up with it.

[Q] [solved] GPS Not Working After Cyanogen Mod Install

Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.

MikeDacre said:
Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.
Click to expand...
Click to collapse
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app

ROMANTiC KiD said:
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!

MikeDacre said:
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!
Click to expand...
Click to collapse
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app

ROMANTiC KiD said:
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the confirmation. I did exactly that and I can confirm that it did indeed work.
Thanks so much for the help.

Hi all,
Sorry to resurrect an old thread, but I am having this issue and the stock firmware flash isn't solving the issue. It is all very odd because it doesn't actually retain any kind of lock after flashing. I'm following instruction on here, but after locking gps on stock, then going to CM I cannot get a fix. It either had a massive radius on Maps, or it just locks to my home or work location.
Since trying much more I have managed to get the occasional satellite lock via GPS Locker, but even then as soon as I move from either my house or work, it can't find anything to lock onto and just defaults to a static location.
Is there anything you would recommend? I have 2 Samsung GS4's and they both exhibit the same problem. I have also tried this on an S4 Mini, but that retained lock just fine. I'm really confused as to what to actually try. If you could recommend anything I'd be very grateful.
Again, I'm sorry to res an old thread, but no one has been replying to the one I started for this issue :/

Your problem may be that there is some new issue with the newer firmware. I had success by first flashing the *old* firmware (you can download it from my dropbox here: https://www.dropbox.com/s/o3f3ynyezyy4yw9/L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5?dl=0) and then upgrading to the second to last firmware update for the GS4: which gives you Android 5 but without fixing the MMS bug.
After that I flash TWRP with Odin, and then do a full erase in TWRP followed by flashing the latest CM. That series of steps works for me every time, although I found that large changes to my physical location (e.g. flying to England from California) cause it to break again. I actually had to sit in a cafe in an English airport with my laptop out flashing my phone back to stock just so that I could use Google maps to get to my mother's house. It was pretty ridiculous. Because of that and other issues, I now just use stock. I hate it, but I do it anyway. Good luck.