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?

[Q] Help with CarbonRom/TWRP/RazrM?

Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.

mrnathanman said:
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
Click to expand...
Click to collapse
see post #7 here: http://forum.xda-developers.com/showthread.php?t=2355676
this should probably be in the Q&A/Help/Troubleshooting section....

Thank You So Much!!!!!!!!!!!!!!!!!
I know its soon and I am still crossing my fingers, but thank you!

HELP! System UIDs Inconsistent

Hi guys,
ok so basically I asked for help on this in a thread thinking it was ROM related, but now I know it's not. I flashed cm 10.2 after stock 4.3 and what happens is that when I try to restore my backups they don't work (I mean TB installs them, but they FC as soon as I open them). Thinking it was CM related I tried another 4.3 ROM and same issue there (I tried all 4.3 ROMs on xda).
I then decided to go back to 4.2.2 thinking it was 4.3 related and again with yesterday's PAC nightly the issue is still there...
This is what I see when I reboot my phone:
"System UIDs Inconsistent
UIDs on the system are
inconsistent, you need to wipe
your data partition or your
device will be unstable.
I'm Feeling Lucky"
Any ideas guys?

Get the Fix Permissions application from the Play Store.
Sent from my Nexus 4 using Tapatalk 4 Beta

theraf90 said:
Hi guys,
ok so basically I asked for help on this in a thread thinking it was ROM related, but now I know it's not. I flashed cm 10.2 after stock 4.3 and what happens is that when I try to restore my backups they don't work (I mean TB installs them, but they FC as soon as I open them). Thinking it was CM related I tried another 4.3 ROM and same issue there (I tried all 4.3 ROMs on xda).
I then decided to go back to 4.2.2 thinking it was 4.3 related and again with yesterday's PAC nightly the issue is still there...
This is what I see when I reboot my phone:
"System UIDs Inconsistent
UIDs on the system are
inconsistent, you need to wipe
your data partition or your
device will be unstable.
I'm Feeling Lucky"
Any ideas guys?
Click to expand...
Click to collapse
you can find a solution in this post:
http://forum.xda-developers.com/showpost.php?p=9365024&postcount=4
I tried it and it worked.

[Q] Custom ROM Problem with Keyboard and Home Button

I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).

trevorftard said:
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
Click to expand...
Click to collapse
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..

You should also format the /system partition when you flash a new rom.
For some roms the Home button stop working for me and to fix it I had to install gapps, but most CM based roms I use don't have that issue.
As for keyboard, I always delete the default keyboard from the rom and use Google Keyboard.

Andre_Vitto said:
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
Click to expand...
Click to collapse
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.

trevorftard said:
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
Click to expand...
Click to collapse
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..

Andre_Vitto said:
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Click to expand...
Click to collapse
Well, that's unfortunate. I've found that the RevoltHD ROM doesn't have problems, but that's because it's got integrated GAPPS.

Been having the same issue with my Nexus 4, after installing GAPPS the keyboard crashes and the home button stops responding. Did anyone figured it out by any chance? Thanks.

I still don't know what caused it, but I figured out that more recent nightly versions of those ROMs don't have that problem. I'm using AOKP currently and that used to be a problem ROM.

Take off vibration and sound and all the bells and whistles and your keyboard should be fine if the issue isn't Rom specific. Also, it could be kernel related.....try boosting touch input if nothing else
Sent by flying midget

I get the same problem, I factory reset each time I switch ROMs. I was trying with Vanir a couple of days ago and couldn't get the home button to work, tried OmniROM and it worked perfectly, went back to Paranoid it worked perfectly again, went back to Vanir and it didn't work. Was odd.

Hello Everyone,
Nexus 4
Paranoid Android 4.2Beta1
Franco Kernel
I just upgraded to PA 4.2Beta1 from PA 4.1.......
after installing the rom.....when i use my browser or messenger where we require keyboard....the Keyboard doesnt pop up....whats up with this....and also the back button of my navigation bar doesnt work.......this even happened with carbon rom a few days back...when i was experimenting with it.....but then i restored to PA4.1 due to the above given problems....plz offer a solution to this...

The same problem

keyboards not working
please help me my keyboards are not working . i have installed an custom rom.

Specific apps missing after reboot (BasicPlus 2)

Hi,
I use BasicPlus 2 rom by t-shock (http://forum.xda-developers.com/s7-edge/development/rom-basicplus-1-t3402601).
When I reboot my device, specific apps are complety missing and I have to restore them with TB to go on.
This is reproducible with these certain apps, for example Swiftkey, Es Explorer and Google Calendar.
I had this issue before and I fixed it by deleting the 'Android' folder on my external microsd (128GB Samsung Evo Plus), since the missing apps always create an empty folder there. Now this seems not to be working anymore, therefore I'm asking for a permanent solution in this thread.
Unfortunatelly I'm not able to post in the rom's thread since my account is locked for the development section, but I hope I will get some help here.
Thanks!

Did you dirty flash?
If you did, I highly recommend clean wiping after every update to a custom ROM.

iSaitama said:
Did you dirty flash?
If you did, I highly recommend clean wiping after every update to a custom ROM.
Click to expand...
Click to collapse
Yes I dirty flashed from 1.1.1 to 2.0, since this was supported by the developer and he provided a fix to have a stable rom.
I also tried a clean install, but for any reason battery life wasn't that good compared to the dirty flash from 1.1.1.
It seems that no one else has such an issue, that would mean no one else did a dirty flash from 1.1.1, otherwise there would be more reports!?

In the meanwhile I made a clean install in each case of 2.0 and 2.1, but the issue still exists. I also wiped all caches after rom install, but there is no change. All apps survive several restarts but all of a sudden some apps disappeared after restart. I will try now with 3.1 and Prometheus kernel, too bad I cannot post to the main thread of the rom, since the developer doesn't see this thread I think