Database Info

[Q] Xoom error on reboot

Hi,
I have a Wifi only Stock XOOM with 3.0.1
Whenever I power off and then power on my XOOM , after first screen unlock it shows -
The process android.process.acore has stopped unexpectedly with a Force Close button.
Any idea what this process does or why it is happening ?
Ishan

LeapSwitch|Ishan said:
Hi,
I have a Wifi only Stock XOOM with 3.0.1
Whenever I power off and then power on my XOOM , after first screen unlock it shows -
The process android.process.acore has stopped unexpectedly with a Force Close button.
Any idea what this process does or why it is happening ?
Ishan
Click to expand...
Click to collapse
Quite generic. What specific customization you have done? for example, launcher? any other apps that set to set some configurations on boot? more information may be helpful to see what may be going on..

jiwengang said:
Quite generic. What specific customization you have done? for example, launcher? any other apps that set to set some configurations on boot? more information may be helpful to see what may be going on..
Click to expand...
Click to collapse
Firstly, this should go to Q&A forum, I am sorry for posting it here.
No customization other than installing a few apps, like Engadget, Skype, Arseblog, and some games. None of them should require something while booting.
Launcher and background is same, I just got it 2 days ago.

LeapSwitch|Ishan said:
Firstly, this should go to Q&A forum, I am sorry for posting it here.
No customization other than installing a few apps, like Engadget, Skype, Arseblog, and some games. None of them should require something while booting.
Launcher and background is same, I just got it 2 days ago.
Click to expand...
Click to collapse
No no , don't take me wrong. when I said quite generic I meant please describe / include a bit more info for discussion =) that acore process is quite generic one.
Sorry that caused some misunderstanding.
Did you try to flash it back to stock (since you haven't have tons of customizations yet, but still, backup information data you may have).
If you use http://forum.xda-developers.com/showthread.php?t=1052644
to do a stock flash of boot.img system.img recovery.img userdata.img
does this problem still occur? Seems to me it is some minor system glitch. Hopefully it will go away once you flash it to stock.

jiwengang said:
No no , don't take me wrong. when I said quite generic I meant please describe / include a bit more info for discussion =) that acore process is quite generic one.
Sorry that caused some misunderstanding.
Did you try to flash it back to stock (since you haven't have tons of customizations yet, but still, backup information data you may have).
If you use http://forum.xda-developers.com/showthread.php?t=1052644
to do a stock flash of boot.img system.img recovery.img userdata.img
does this problem still occur? Seems to me it is some minor system glitch. Hopefully it will go away once you flash it to stock.
Click to expand...
Click to collapse
I guess I will wait a few days for the 3.1 update and see if it gets fixed. If not, I will try your method.
Thanks a lot,
Ishan

[Q] Clockwork Mod Messed Up?

When I try to wipe data to install another rom my phone stays on the little android guy just saying formatting data. It's been like this for an hour. How long should it usually take? Thanks

That step shouldn't take more than a few seconds. I would try pressing a couple buttons to see if you can get back to the previous screen.
If that doesn't work I'd pull the battery and do the key combo to boot into recovery. I hate doing it this way though, I just can't ever seem to the combination correct. Hope it works better for you.

CrustyMcLovin said:
That step shouldn't take more than a few seconds. I would try pressing a couple buttons to see if you can get back to the previous screen.
If that doesn't work I'd pull the battery and do the key combo to boot into recovery. I hate doing it this way though, I just can't ever seem to the combination correct. Hope it works better for you.
This is where it is happening, when I go through yhe phone it does the same thing.
Click to expand...
Click to collapse

Please reads forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Still haven't figured this out. Would like to try a different rom if any body has any suggestions of how to figure this out. Thanks

That is odd. The only thing that take more than a min is fixing permissions.

king750 said:
When I try to wipe data to install another rom my phone stays on the little android guy just saying formatting data. It's been like this for an hour. How long should it usually take? Thanks
Click to expand...
Click to collapse
What version of CWM are you using? I heard that 6.0.2.9 had issues. Better to stick with 6.0.2.8 or the newest 6.0.3.0. Both are verified working fine.

Stealth111 said:
What version of CWM are you using? I heard that 6.0.2.9 had issues. Better to stick with 6.0.2.8 or the newest 6.0.3.0. Both are verified working fine.
Click to expand...
Click to collapse
I'm running v6.0.2.3. Could that be the problem? It's also the touch version.

king750 said:
I'm running v6.0.2.3. Could that be the problem? It's also the touch version.
Click to expand...
Click to collapse
It wouldn't hurt to Odin/flash up to 6.0.2.8, and then try again what you were having the original issue with.
There have been changes made since 6.0.2.3, and a newer version might offer you correct results.
I use the touch version all the time, so I would say that touch/non touch wouldn't be any different.

Stealth111 said:
It wouldn't hurt to Odin/flash up to 6.0.2.8, and then try again what you were having the original issue with.
There have been changes made since 6.0.2.3, and a newer version might offer you correct results.
I use the touch version all the time, so I would say that touch/non touch wouldn't be any different.
Click to expand...
Click to collapse
I flashed up to 6.0.3.0 and everything is working like it should. Thanks

[Q] Options for CROMi-Xenogenesis 4.4 ODEX

I'm running CROMi-Xenogenesis 4.4 ODEX and have not posted enough to post in the actual development thread...so posting in General. This is a fresh install and the main application I am running after install is Waze (gps location type app for driving/navigation). Running this application results in random system reboots. So I am wondering what options should I select or not select in order to ensure stability? I'm basically tried all the kernel patches with this install. I'm not sure what I should turn off. Any advice appreciated. Thank you.

What options did you select when you installed (other than default ones) and how long does it work before rebooting? Does the back of your tablet get warm while using this app? I know my tablet has had issues in the past when it gets too hot. You could try making sure your tablet is not in performance mode and see if that helps at all.
I just installed it and it hasn't crashed for me yet, although my tablet did get warm (probably because my tablet is overclocked in performance mode at the moment).

bmlarson said:
What options did you select when you installed (other than default ones) and how long does it work before rebooting? Does the back of your tablet get warm while using this app? I know my tablet has had issues in the past when it gets too hot. You could try making sure your tablet is not in performance mode and see if that helps at all.
I just installed it and it hasn't crashed for me yet, although my tablet did get warm (probably because my tablet is overclocked in performance mode at the moment).
Click to expand...
Click to collapse
I remember the Cross Breeder Optimization Patch with virtually everything else enabled as well. Perhaps I'll go back through and bit a more restrictive on my options. I didn't check the back for heat but I'm running in balanced mode and there kernel is not an OC'd one. If anyone has additional suggestions please let me know. I'll probably wait for 4.5 to try again.

I don't understand why you didn't post this in the Q&A section or the cromi-x thread it's self.. You would get a lot more feed back.

FrostByghte said:
Running this application results in random system reboots.
Click to expand...
Click to collapse
After a random reboot, save the file /proc/last_kmsg and post it. It may contain relevant error messages.

Good advice from _that. Also reflash without cross breeder first.

_that said:
After a random reboot, save the file /proc/last_kmsg and post it. It may contain relevant error messages.
Click to expand...
Click to collapse
Great advice -- got it from sbdags bbefoe -- but after most if not all random reboots, somehow, my 700 won't boot into the OS, and hangs at the very first screen with "ASUS" and a lot of smaller white lettering. At that point, I will have to reboot it manually, losing the last_kmsg in the process. Frustrating.

ronniereiff said:
I don't understand why you didn't post this in the Q&A section or the cromi-x thread it's self.. You would get a lot more feed back.
Click to expand...
Click to collapse
The forum software won't allow me to post in the thread I do understand that but I don't have permission until I post 10 posts or some such. Once I'm there I will definitely take part and move my questions to the development thread.

sbdags said:
Good advice from _that. Also reflash without cross breeder first.
Click to expand...
Click to collapse
Thanks for the advice. I'll look at trying this as well. Excellent ROM btw...I'm running the older 3.4.7 on my wife's tf700t. Like night and day speed wise.

FrostByghte said:
The forum software won't allow me to post in the thread I do understand that but I don't have permission until I post 10 posts or some such. Once I'm there I will definitely take part and move my questions to the development thread.
Click to expand...
Click to collapse
Ah ic ic

data2sd
_that said:
After a random reboot, save the file /proc/last_kmsg and post it. It may contain relevant error messages.
Click to expand...
Click to collapse
sbdags said:
Good advice from _that. Also reflash without cross breeder first.
Click to expand...
Click to collapse
I also don't have enough street cred to post in the developers forum, so I thought I'd highjack this.
I just wanted to confirm what a few other people have said in the CROMi-X thread. The odex data2sd mod doesn't work. You have to flash the _that data2sd mod over the top to get it going. I've tried a few times to no avail. I tested write speeds and looked in the root and it definitely wasn't happening. The files are there in /system/boot but no-ones home. I don't understand anything about the inner workings so I can't be of much further help.
Awesome rom and kernel though guys. Seriously, love it!

CiaronDarcOne said:
I also don't have enough street cred to post in the developers forum, so I thought I'd highjack this.
I just wanted to confirm what a few other people have said in the CROMi-X thread. The odex data2sd mod doesn't work. You have to flash the _that data2sd mod over the top to get it going. I've tried a few times to no avail. I tested write speeds and looked in the root and it definitely wasn't happening. The files are there in /system/boot but no-ones home. I don't understand anything about the inner workings so I can't be of much further help.
Awesome rom and kernel though guys. Seriously, love it!
Click to expand...
Click to collapse
That's one of the few things that I didn't attempt to load was the data2sd mod. I have a 64gig device so w00t. Looking back now though, if I had it to do over again I would NOT have purchased the TF700t. I really thought it would be a better device. One thing I look for now is 2 gigs of physical memory. My Note 2 simply runs rings around the TF700t. I still haven't had any reason to put a ROM on the Note2. TF700t doesn't even function properly without something like CROMi.

gallery apk wont work, always stops by turning on. How to fix this ?

hemeyus said:
gallery apk wont work, always stops by turning on. How to fix this ?
Click to expand...
Click to collapse
Clear data and cache on the gallery app

[Q] Strange bootloop issues

Kinda new to this so forgive me if i miss something somewhere and if i need to give more information somewhere just let me know.
With that out of the way I'd like to start with the fact that this is my first rooted device. Currently on C-spire (cellular south) if that matters.
A few days ago before the phone was rooted or even unlocked i went to make a phone call and the screen blacked out and a few seconds later went into a reboot loop where it would get to the Motorola Logo for about 6 seconds or so then shut off and try again ad nauseam until the battery died. After letting the battery die and connecting it to the charger it continued the loop so after a quick gogle search I began fiddling with buttons and realized i could boot into fastboot and recovery modes. I decided i might as well root since it couldnt get a whole lot worse and after a quick look around the forums and a trip to motorola to unlock my phone i was able to flash TWRP recovery, after which i accidentaly wiped the os, managed to find any number of replacement roms none of which solved the boot issue. I eventually found the stock Sprint roms which allowed the phone to boot and work for the most part, but it wont send media messages and has trouble picking up 4g service. I am also forced into using the sprint updater among other things which include having sprint plastered everywhere I have tried flashing several custom roms (pacman, paranoidandroid, and cyanogen) all of which get hung up booting just like the phone did before but the sprint stock rom will reload and work just as before. I'm not sure what would be causing this or if there is a way to fix it and i apologize for the wall of text. If any more info is needed let me know and ill provide ot to the best of my knowledge. Thanks in advance :fingers-crossed:

So all ROM's fail to boot?
Are you doing a factory reset in TWRP before you boot?
Are you flashing gapps? Although that shouldn't cause the phone to fail at booting...

Correct. All roms except the stock sprint rom fail to boot.
Now that i have everything backed up on my external sd I've tried factory reset using twrp as well as wiping everything prior to flashing a ROM as well as after but
Before booting. And the many combinations thereof
And yes i am flashing gapps.

You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.

arrrghhh said:
You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.
Click to expand...
Click to collapse
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though

AMerexican said:
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though
Click to expand...
Click to collapse
Every ROM should include a md5sum with it. If you're on Windoze, use a program like WinMD5 - check the md5sum locally, and compare it to what is on the server. If they match, the download is probably good.

So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?

AMerexican said:
So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?
Click to expand...
Click to collapse
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.

arrrghhh said:
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.
Click to expand...
Click to collapse
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?

AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
I suppose some sort of hardware issue. Like I said, I've flashed most of the newest ROM's here for the Q - all work fine. Hell, some I even ported myself...
I'm kind of at a loss. Can you get adb? Not even sure what to check for next... if you are wiping properly in recovery, that should be sufficient.
Hm, I guess that brings up a good point. Have you tried wiping system, flashing, doing a factory reset, then booting? Most, if not all of the ROM's should wipe /system before flashing... So it probably won't do anything different.

AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.

kabaldan said:
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.
Click to expand...
Click to collapse
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead

arrrghhh said:
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead
Click to expand...
Click to collapse
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot

kabaldan said:
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot
Click to expand...
Click to collapse
Ah, that makes sense - I was not aware of this apanic_console
Thank you!

arrrghhh said:
Ah, that makes sense - I was not aware of this apanic_console
Thank you!
Click to expand...
Click to collapse
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?

AMerexican said:
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?
Click to expand...
Click to collapse
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!

arrrghhh said:
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!
Click to expand...
Click to collapse
Thanks wasnt sure of the forums rules as far as that was concerned
http://pastebin.com/QFq1naK0

Any ideas?
Or anything else i need to do?

[Q&A] ★☆[ROM][4.4.3] NuSenseSIX | Sense 6.0 | 2.21.605.2 | m8vzw

Q&A for ★☆[ROM][4.4.3] NuSenseSIX | Sense 6.0 | 2.21.605.2 | m8vzw
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:

issues
HTC Dot view crashes when adding a new theme, OK GOOGLE detection from any screen not working, infact its not even letting me calliberate by saying OK GOOGLE 3 times.

udmerchant said:
HTC Dot view crashes when adding a new theme, OK GOOGLE detection from any screen not working, infact its not even letting me calliberate by saying OK GOOGLE 3 times.
Click to expand...
Click to collapse
I have no means of testing Dot View.
OK Google works fine for me and so does the calibration.
Did you do a full wipe prior to flashing the rom?
Did you restore apps or data?
Logcat for Dot View?

udmerchant said:
HTC Dot view crashes when adding a new theme, OK GOOGLE detection from any screen not working, infact its not even letting me calliberate by saying OK GOOGLE 3 times.
Click to expand...
Click to collapse
Just tried it...worked for me as well as ok Google and calibration.
santod040 said:
I have no means of testing Dot View.
OK Google works fine for me and so does the calibration.
Did you do a full wipe prior to flashing the rom?
Did you restore apps or data?
Logcat for Dot View?
Click to expand...
Click to collapse
See above ? Also, I have a dot view case. Pretty fancy gimmick, but hopefully in future iterations will be cool.

Haha, totally had the same HTC flash screen for half a hour. Totally forgot to flash the boot.img for 4.4.4 when I did the firmware... That took care of everything

Screen wont turn on after flashing 4.0.1
It is my first time trying NuSenseSIX. I updated the firmware and flashed the ROM to my Verizon One M8 but now the screen won't turn on, but as I press the volume buttons, I hear the sounds and I can somehow turn the flashlight on.
The problem is that I can't get it to turn off so I can enter recovery!
I think the problem might be the "Fast Boot" option which I can uncheck since the screen won't show anything. Any input will be deeply appreciated.

Raneto said:
It is my first time trying NuSenseSIX. I updated the firmware and flashed the ROM to my Verizon One M8 but now the screen won't turn on, but as I press the volume buttons, I hear the sounds and I can somehow turn the flashlight on.
The problem is that I can't get it to turn off so I can enter recovery!
Click to expand...
Click to collapse
Hold Power and Vol Up till it reboots, then power vol down

jsaxon2 said:
Hold Power and Vol Up till it reboots, then power vol down
Click to expand...
Click to collapse
I am trying exactly that, but when I hold Power + vol down after it reboot, it simply takes a screenshot(I hear the sound) and doesn't do anything else evend if I keep pressing the buttons for over a minute.
Is there a specific time I should start pressing Power+Vol Down when it reboots?
Finally did it...I needed to press Pwr+VolDwn exactly when it was about to restart.

Raneto said:
I am trying exactly that, but when I hold Power + vol down after it reboot, it simply takes a screenshot(I hear the sound) and doesn't do anything else evend if I keep pressing the buttons for over a minute.
Is there a specific time I should start pressing Power+Vol Down when it reboots?
Finally did it...I needed to press Pwr+VolDwn exactly when it was about to restart.
Click to expand...
Click to collapse
Did you get the Rom to install? Everything good to go?

Quick question: ready to install 4.4.4 but need to know the following? Install by pc or by twrp? Do I need to update firmware or radio first? Then a clean install means wipe in what order by twrp?

crazysane said:
Quick question: ready to install 4.4.4 but need to know the following? Install by pc or by twrp? Do I need to update firmware or radio first? Then a clean install means wipe in what order by twrp?
Click to expand...
Click to collapse
U would use TWRP to flash Rom. And update to new firmware first. If u haven't do a backup of ur current setup/Rom ur on. Then wipe. I go into advance as well and select data,cache,dalvik cache,and system.
Sent from my Insanely powered M8 using Tapatalk

crazysane said:
Quick question: ready to install 4.4.4 but need to know the following? Install by pc or by twrp? Do I need to update firmware or radio first? Then a clean install means wipe in what order by twrp?
Click to expand...
Click to collapse
If you install v4.2 you should be able to install normally through twrp. Yes, update firmware, factory reset in twrp. Dalvik cache, cache, system, data, etc. Don't wipe internal sd or external sd.
Edit: didn't see your post Holla420

HOOKEDONDROID said:
If you install v4.2 you should be able to install normally through twrp. Yes, update firmware, factory reset in twrp. Dalvik cache, cache, system, data, etc. Don't wipe internal sd or external sd.
Edit: didn't see your post Holla420
Click to expand...
Click to collapse
I cannot seem to get the firmware to flash using TWRP. Is it supposed to be this hard? I have installed the new ROM just not the firmware yet. I have downloaded it and checked the md5 which shows it passed. Please tell me what I may be doing wrong? the file name is 3.28.605.4-firmware.zip.
Just want to have this correct before proceeding further.

crazysane said:
I cannot seem to get the firmware to flash using TWRP. Is it supposed to be this hard? I have installed the new ROM just not the firmware yet. I have downloaded it and checked the md5 which shows it passed. Please tell me what I may be doing wrong? the file name is 3.28.605.4-firmware.zip.
Just want to have this correct before proceeding further.
Click to expand...
Click to collapse
You don't update firmware through TWRP. Save the file to your external sd card and rename.
SD CARD METHOD DIRECTIONS
Download 4.4.3 firmware
Rename file to 0P6BIMG(zero at the start)
Place file on root of SD card*
Reboot to bootloader an click hboot it will auto detect file
Follow the prompts an you will be updated*
Then reboot to boot loader either by holding power+volume down or through the Rom. Select hboot and the update should start. Follow the instructions and you should be good to go

NuSense 4.4.4
Flawless!
Also applied the HK mod from another thread and everything works perfectly.
Thanks, Santod!

Hello everyone. just stared put your Rom. everything seems to be fine, but. Blink can`t get to show my location to display weather. In the setting of location included. Can not find my city of Lviv. how it can be cured?

Go into the weather app and add your city. You should be able to find it or select " current location" it found Lviv when I just searched for it.

I'm sorry, but I could not make friends with your Rom not one keyboard
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
HOOKEDONDROID said:
Go into the weather app and add your city. You should be able to find it or select " current location" it found Lviv when I just searched for it.
Click to expand...
Click to collapse
with etoy problem I figured Wipe helped. but with the keyboard hand, make friends and it could not

publ said:
I'm sorry, but I could not make friends with your Rom not one keyboard
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
with etoy problem I figured Wipe helped. but with the keyboard hand, make friends and it could not
Click to expand...
Click to collapse
Keyboards zip is in post 2 if that helps...for more languages.

wifi still doesnt work
I am on 4.4.4 reflashed the firmware, but certain roms dont work. I am on the latest liquid smooth and wifi does work on this rom, any other ideas?
Thanks