New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
alteredlikeness
Old
(Last edited by alteredlikeness; 2nd June 2012 at 06:25 PM.)
#1  
alteredlikeness's Avatar
Recognized Contributor - OP
Thanks Meter 2282
Posts: 1,695
Join Date: Mar 2012
Location: reflecting on Indra's net

 
DONATE TO ME
Default [Sovled]Common errors after new build test

I will start this off with "...Accounts (process com.motorola.setup) has stopped unexpectedly. Please try again."

The above is my most common error lately. And, I've tried again, multiple different ways. Only once have I got a half-decent build - meaning I got through setup... and, I have no idea what I did differently that time.

I am on GB 2.3.6 Moto Edison (A2) - locked bootloader - and have been attempting an odexed rom (psuedo-rom, if you will, because of the bootloader thing..), trying to retain most of the moto-blur (stock launcher for sure) - but have added some other features.

As I said, I managed to do it once, but it had a different connection issue (with the moto server - suspect it had something to do with cheesecake and switching servers at one point (but that's another topic)) so, I ditched that version. Also, I have no problem logging into Google - it's the next setup that usually gets me...

I know it's kind of a vague post but I am wondering if anyone has encountered not being able to get past setup? And, any ideas on how to correct it? I have scoured the web and discussed it with folks in my local community to no avail..

Also, I figure this thread could also be used for others with common or reoccurring errors after a test run - so, feel free to post your issues!
Quote:
Originally Posted by doseone/themselves View Post
Code:
watch your hand, the motorized lifestyle likes to bite and grind
A2 Edison | N10 Manta

/-\ |_ T F |2 F |)
 
alteredlikeness
Old
#2  
alteredlikeness's Avatar
Recognized Contributor - OP
Thanks Meter 2282
Posts: 1,695
Join Date: Mar 2012
Location: reflecting on Indra's net

 
DONATE TO ME
Fixed everything.
It was a mismatched signature on my Settings.apk, I believe... causing it to not be recognized by my system. Do not mess with the AndroidManifest.xml unless you want to re-sign all other apks.
Also figured out my moto server connection error - it was cheesecake - must have been using the /etc/motorola folder from a backup or systemdump after changing from the default moto server with cheesecake - it changes a defaults.xml in there...

...But ICS is leaking all over the place - so gotta be checking Cheesecake!

Sent from my mind using XDA
Quote:
Originally Posted by doseone/themselves View Post
Code:
watch your hand, the motorized lifestyle likes to bite and grind
A2 Edison | N10 Manta

/-\ |_ T F |2 F |)