Database Users

[Q] HELP! Custom rom/mod error.

My X10 works fine on the stock X10 2.1A0.435 rom and everything before that.
However, every time I try to flash to a custom rom such as FreeX10 and CM my phone will never have signal. Whenever the signal bars at the top of the screen show up "com.android.phone" force closes and the signal bars becomes a red X.
I've tried to wipe Dalvik Cache, full reset, reboot, reflash, Battery Stats, but nothing has seemed to fix the problem.
Does anyone have any other ideas that I can try?
Thanks

Read the custom Rom threads. This is fairly common and often easily fixed.
Haven't used freex10 for a while, and I never had that issue so I don't know how you would fix it on that Rom. The only time I had that issue I simply crashed the system server via a supplied app called dev tools.
Sent from my X10i using XDA App

You need to have specific kernel so you need to update urs to one of the following 54 -. 55 -. 58
Sent from my X10i using XDA Premium App

shahkam said:
You need to have specific kernel so you need to update urs to one of the following 54 -. 55 -. 58
Sent from my X10i using XDA Premium App
Click to expand...
Click to collapse
If its the wrong kernel wont that just send you into bootloops? You wouldnt even know if you had a signal or not.
I could be wrong.
Anyways, if you flash freex10 and have no signal, go to settings, privacy and choose factory reset....works everytime.
If you flash CM...in the app drawer go to dev tools and choose crash system server.
Sent from my X10a using XDA App

I've tried to crash the system server with no luck, I will try doing a factory reset
Thanks

so none of the options above work
the only way i could get radio was to start up in airplane mode, wait for com.android.phone to crash, and then disable airplane mode.
However, com.android.phone crashs when i turn on wifi =.= and I have to do the whole process again, or turn wifi on before I turn off airplane mode.
Is com.android.phone suppose to crash like that?
The weird thing is that I am using Fido as my carrier but it shows that I am connected to Roger's Wireless.

Flash the correct baseband before installing a certain ROM.
Sent from my X10i using XDA App

PhyzX said:
so none of the options above work
the only way i could get radio was to start up in airplane mode, wait for com.android.phone to crash, and then disable airplane mode.
However, com.android.phone crashs when i turn on wifi =.= and I have to do the whole process again, or turn wifi on before I turn off airplane mode.
Is com.android.phone suppose to crash like that?
The weird thing is that I am using Fido as my carrier but it shows that I am connected to Roger's Wireless.
Click to expand...
Click to collapse
it might be because of ur model no...
is it X10i or X10a?
for the proper basebands go to: http://forum.xda-developers.com/showthread.php?t=960527
if u want to use FreeX10-beta4 then i suggest u use 2.1.5x basebands (which ever ur device is compatible with)

My firmware comes with .54 and when i boot up the custom rom it still shows .54
I have an Xperia X10a, should I tried flashing it to .55 but still didnt help.
Same problem occurs.
Sucks to be stuck on stock rom.

Elelinux-7.0.0-Hero-v2.0 - issues

I am writing on this thread as i still cannot add to the development thread yet
I am using Elelinux-7.0.0-Hero-v2.0. Thanks Ele for a great rom.
So far the only problem i have had is once the unlock screen went invisible on me.
I had to use the patch which worked fine. no black screen. everything else works great so far.
Just trying to contribute to the developers what i can to help.
Any one else has any issue yet.
Elelinux-7.0.0-Hero-v2.0
RADIO VERSION:63.18.55.06SU_6.35.17.03
Kernel: Herokernel-12a

I've had the same issue with the lockscreen but like yourself it was a once off.
Generally the ROM is great (however, this is the first ROM that I've flashed to my hero)
The only other issue im getting is with linking facebook with my contacts; for some reason FB keeps crashing. But keep in mind that I'm a retard in comparison to what you lads know about custom roms etc..... but slowly learning!
Sent from my Hero using XDA App

same problems
I have had the same problems as you. lock screen went invisible a couple of times. and my facebook does not work quite right.
Apart from that has been very stable. no problems or reboots. works great.
Running gingerbread with honeycomb theme on my hero. running at 691mhz is well good.
I have got widgets running on every screen to.
Elelinux RC4 version 7.0 V2.0
kernel 12a
691mhz
clockworkmod.
Thanks Ele for a great rom

After installed 2.0 patch, I still get blank screen (wall paper ok, no any widgets).
The only way to solve is restart
Any thing wrong with my installation? (same spec as above post)

The Bug seems to affect some phones and not others. Might be due to different hardware but not sure.
I am a network engineer. Not a developer.
There is a patch that fixes the black screen bug which might help. You might have to delete dalvik cache first though. But as said not a developer.
I just wanted to try some different roms and loaded cronos rom yesterday and is very good. So running that at the moment.
It is really fast and stable. The fastest i have used so far. But i have not tested everything yet like GPS. But admit i am becoming a cronos fan.
Cheers.
P.s i always backup my phone first and do a complete wipe before trying a new rom. Otherwise could get problems.
I use clockwork mod.

Unfortunately the bug your getting with black screens, invisible menus etc.. is an aosp bug that affects some devices which Google are unable to fix, if you had read through the thread you would have seen this. Ele is working hard on a fix for this but as CM no longer support the hero, its unlikely many cm7 roms will see many updates.
Sent from my HTC Hero using XDA App

Everyone is hoping that Google will fix the memleak and invisible manus problem. To fix it, one needs to undersatand the big picture on how these things are managed. I think it can be done only by experienced coder.

It's a real shame. i love gingerbread and did not want to go back to 2.1 or 2.2.
But might have to if they do not fix it.
I know Ele is working hard on a fix. using his rom at the moment. Was using cronos. But suddenly started getting random reboots and battery started only lasting a few hours and could not find out why.
Thanks to all devs and help.

Elelinux 7.0 v2.1 GPS reboot issue
Hi all,
I found Elelinux 7.0 v2.1 to be almost perfect.
The only major issue so far for me is that when running applications such as sportstracker that use GPS and are running in the background, that as soon as the GPS connection is lost (for whatever reason) the phone always seems to crash.
I wonder whether anyone else has seen this issue and whether there's a way to investigate it.
E.g. is it possible ot redirect logcat to the sdcard and then analyze the log file?
Regards,
MJ

Her0 V2.1 - USB problem
This is a weird one...
I flashed to Elelinux 's fab 2.1 the usual way....
I booted into the ClockworkMod Recovery V2.5.0.7
-- wipe cache partition
-- Advanced - Wipe Dalvik Cache
-- reboot
Then again within Clockwork Recovery I choose 'Install zip from sdcard'
I select the Hero rom and it flashes perfectly...
Now the problem ----> I cant get the usb port working to enable transfer of files?
When the phone boots up it shows 'preparing sd card'
Then when i connect usb lead to pc it shows 'usb connected'
When i then pull the screen down, i see 'usb connected - select to copy files to/from your computer'
When i select that tab, it just crashes back to the home page?
I see the icon at the top of the screen but when i pull down the screen and select as above, it crashes back to home screen again?
In settings, i have both USB debugging and USB debugging notify - all enabled.
Can anyone provide a solution to this issue for me..
thank you

The only way around this problem i think is to mount usb storage from recovery.
Sent from my HTC Hero using XDA App

Gingerbread 2.3 problems.

Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks

Frosty1148 said:
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Click to expand...
Click to collapse
Maybe it's a bug in the ROM
Try different rom and see if this problem still persists, if yes, maybe a hardware problem related issue
Cheers

There are a few roms with 100% support for the official extended batteries(s). Your best bet is to go with one of them.
Sent from my HD2 using XDA App

Razr M keeps rebooting

I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).

rocksolidsr said:
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
Click to expand...
Click to collapse
could be a ROM/Kernel pairing. have you tried wiping system/data/internal storage - reboot recovery, then flashing a new ROM?
the static screen is common on custom 4.2.2 ROMs, but it's usually a quick flash. I don't get any random reboots though.

I've tried many different rom's along with the Vanquishkitties kernal but still random reboots

I noticed my phone acting weird, specifically it would not play any audio, I noticed this because when I was in the dialer it was going really slow. Then I tried to play some notifications and none worked. I rebooted my phone and all seemed ok, I've attached two logs the first one being while audio would not work and the second after the reboot. I'm not really sure what to look for in the logs but thought someone here might.

This might be something...
E/AudioStreamOutALSA( 300): pcm_write returned error -5, trying to recover
Or this, just a warning though...
W/AudioTrack( 692): obtainBuffer timed out (is the CPU pegged?) 0x63d72108 name=0x6user=00001000, server=00000000
Sent from my Nexus 7 using Tapatalk HD

Just noticed that when in the dialer and the phone starts working very slow, if I turn the sound all the way off, the phone becomes responsive

two more logcats for anyone interested in helping this time one is when trying to use google voice actions, I actually get an error message that says can't open microphone and the other is when someone called me and I did not have any ringtone but I answered and I could not hear them and they could not hear me, shortly after my phone rebooted, I did not catch the reboot in the logcat.
Also when it reboots it doesn't reboot all the way it boots to the boot logo screen and then hangs and I have to hold all three buttons until it reboots again, is there a way to get it to just reboot on its own?
After the reboot everything seems to be fine until I experience the same issues again

Which ROM are you on right now? That sounds like a kernel level issue
Sent from my XT907 using Tapatalk 4 Beta

I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.

rocksolidsr said:
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
Click to expand...
Click to collapse
Has your issue been resolved? I am almost facing the same issues of random rebooting with my phone and was searching for a solution....

Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?

5318008 said:
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
Click to expand...
Click to collapse
Im having this issue and Im on kitkat.

CM Roms issues

So every CM ROMs I flash (beanstalk and bliss) I cannot dial out.
Every time I try to dial a phone number, the phone reboots into the animation screen (does not completely reboot the phone).
I did a clean install and even went as far as unrooting the phone, flashing stock and rooting it back up.
Still no avail...cannot flash CM ROMs. It was working fine then one day...this happened.
Anyone got any suggestions for me?
I rooted the phone with superuser not SuperSU.
Thanks in advance.
Sent from my Nexus 6P using XDA-Developers mobile app

Ckao said:
So every CM ROMs I flash (beanstalk and bliss) I cannot dial out.
Every time I try to dial a phone number, the phone reboots into the animation screen (does not completely reboot the phone).
I did a clean install and even went as far as unrooting the phone, flashing stock and rooting it back up.
Still no avail...cannot flash CM ROMs. It was working fine then one day...this happened.
Anyone got any suggestions for me?
I rooted the phone with superuser not SuperSU.
Thanks in advance.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Try Resurrection Remix - That's a CM based ROM. Bliss and Beanstalk seem to be experimental at this point. Also try regular CM13 and see if you get the same issue as well as make sure all your partitions are up to date (i.e. Vendor and Radio) Updated Radio isn't required but may help.