Database Info

[Q] liquidsmooth rc9 keyboard has stopped

[Q] liquidsmooth rc9, with the recommended 20121212 singed gapp.
"unfortunately ** keyboard has stopped" keeps popping up. I have tried installing a new keyboard and setting it default, but it stops too.
After searching, I tried going to manage apps-keyboard and clearing data, and going to manage apps-dictionary and clearing data, which did not work.
I have done full wipe and install twice, which got the keyboard working on another install, but that is not working either....
full wipe with cwm-
factory data/reset 3x,
wipe cache 3x,
wipe dalvik cache 3x,
format sytem, data, and cache 3x each...!
Any other ideas? Can I manually delete something?

that version of gapps u are using may be the issue. I recall reading issues about incompatibility with the new 4.2 gapps? give 20120726 a try and see how u fair

icenight89 said:
that version of gapps u are using may be the issue. I recall reading issues about incompatibility with the new 4.2 gapps? give 20120726 a try and see how u fair
Click to expand...
Click to collapse
Thanks, I did try that I should have mentioned it.
I got slimbeam w/ slimgapps working, maybe I should try the slimgapps with liquid smooth??
I am also considering formatting the internal drive, and then installing the OS from Odin.

slimapps is based off the same gapps version I told u to try lol. that being said give it a go with liquidsmooth before u go giving yourself extra work with wiping internal and odi

icenight89 said:
slimapps is based off the same gapps version I told u to try lol.
Click to expand...
Click to collapse
Aha! Yeah I doubled checked, it is gapps-jb-20120726-signed.zip that I also tried...maybe I had not wiped it correctly when switching over. Also that was before I switched over to team recovery, which seems to wipe better.
Thanks again for the advice.

thanks button bro, and ur welcome :good:

[Q] Unable to launch CM 10.1 after flashing the gapps

Hello everyone,
I flashed CM10.1 and the gapps (gapps-jb-20121212-signed.zip).
When I boot the phone it lets me enter my pin code, but after that I get those two messages:
"Unfortunately the process com.google.process.gapps ended."
"Unfortunately the process setup wizard ended."
And I only may click on "ok" ever and ever and ever again.
The only way to get unstuck from this is to remove the battery and restore the phone.
I flashed many times with different builds and different gapps packages too, I ever get the same issue.
I also did it with and without wiping everything.
What am I doing wrong?
Thank you for your time.
Halavus

Did you wipe data/cache completely?

Zulda said:
Did you wipe data/cache completely?
Click to expand...
Click to collapse
Yes I tried with and without wiping. The issue is the same in both cases.
Sent from my Nexus S using xda app-developers app

Wipe again, flash CM again, reboot, recovery, flash Gapps, reboot. Must works

I tried again many times and I had the same bugs.
But since this afternoon I used TWRP instead of CWM and now it just works perfect.
I'm sure the issue came from CWM.

Hey guys, I am new to the forum. I am glad I found this thread, I keep running into this same problem.
I have been flashing CM 10.1.2 with what I think is the wrong Gapps flash, gapps-jb-20121011-signed.zip. That is the wrong Gapps flash, right?
If that is the wrong .zip, how should I restore back to my Titanium back up from recovery?

this is the correct gapps for 4.2.2 20130301

I think I got the wrong gapps

Finally loaded cm 10.1.3 but now I think I loaded the wrong gaps..my asop keyboard keeps crashing and it only started after I installed it. I tried wiping and it's still doing it. Can I delete the gapps somehow?

JPull07 said:
Finally loaded cm 10.1.3 but now I think I loaded the wrong gaps..my asop keyboard keeps crashing and it only started after I installed it. I tried wiping and it's still doing it. Can I delete the gapps somehow?
Click to expand...
Click to collapse
Which gapps do you have installed? Have you tried clearing data for the keyboard? If you are against wiping and starting over again, then your best bet may be to try deleting the individual Google apps from /system with a file explorer or Titanium Backup then flash the right gapps. You may be able to dirty flash the proper gapps package, may work or it may not.
Failing that, you could wipe data and flash CM and the proper gapps package.

Weird custom rom issue

Just got my n5 and decided to unlock and root it, everything went well until I wanted to flash a rom, no matter what rom I flashed I got all kinds of issues from all apps force closing to bootloops, soft keys not working ect. I've tried flashing stock img, factory reseting ect, nothing seems to work. I'm not sure what's going on here, any help?

I am probably already asking you questions you have already done but... Have you reformated the system, data, and cache partitions prior to flashing? Also are you checking the MD5 of the ROMs you are trying?

Yeah tried all of that, md5's are correct, thanks though

what recovery and version are you on?
what wipes exactly are you performing?
you've checked the md5?

Ok. just trying to narrow things down. When you flash the stock image from https://developers.google.com/android/nexus/images#hammerheadkrt16m are you running the flash-all script? And after that before even adding any apps or changing anything does it give you issues?

@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why

Xolith said:
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Click to expand...
Click to collapse
are you flashing a gapps add-on package with your custom roms? the right gapps?

Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?

simms22 said:
are you flashing a gapps add-on package with your custom roms? the right gapps?
Click to expand...
Click to collapse
Yeah, tried a few including banks, PA 0-day, psx gapps

neomorphix said:
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
Click to expand...
Click to collapse
They appear right after I flash the rom, tried with both the included and with a custom one

Tried a few days later and it worked, weird haha. Thanks though

Google Maps reboot my phone on any ROM that I have tried for 7.X

Everytime I try and use Google Maps either flashed with gapps/bean or installed later from play store all reboot my phone. Stock does not have any issue.
Tried:
ASOP-CAF
ASOP-EX
MOTOPURE
Lineage
TESLA
I just wonder why if the stock maps app works on 6.0 why not on 7.0?? The only thing I can think of is the GPS.
Any tips or suggestions?
Thanks!

Tried nano, pico and full for ARM and Android 7
open_gapps-arm-7.1-full-20170523
open_gapps-arm-7.1-nano-20170511
open_gapps-arm-7.1-pico-20170513
also BeansGapps-Full-7.1.x-20170509 BeansGapps-Mini-7.1.x-20170509

Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.

grantdb said:
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
Click to expand...
Click to collapse
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...

acejavelin said:
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
Click to expand...
Click to collapse
Thanks for helping me, do you mean bootloader.img?

Ok done reflash stock, OTA's and checked gps is fine now backing up... going to use the PureNexus rom or ASOP-CAF

ARRRRRGGGGG Same damn issue... Maps crashes the phone.... so frustrating I am going to give up soon and stick with stock.
Going to try an get a logfile maybe someone can take a look at it
Thanks

ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks

grantdb said:
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
Click to expand...
Click to collapse
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?

acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!

grantdb said:
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
Click to expand...
Click to collapse
You can use ADB to get real-time logging of the crash on your PC... Use Google to find the command.

acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
Sent you logcat via pm thanks again!

Well I started getting random reboots in Pure Nexus ROM and so tried LOS and right away I had the reboot from Maps. I give up, staying with stock.
Thanks

Seems like one of my problems could be ASOP-CAF ROM as the version I was flashing uses a custom Kernel that has known issues with 7.1.2 and causes bootloops and crashes. The UltraDev kernel changes some things in the modem and could be why any roms I tried after flashing ASOP-CAF would not change the modem and were 7.1.2 based.
Anyways...

Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.

grantdb said:
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
Click to expand...
Click to collapse
Check out this bug report. It might be your APNs... https://jira.lineageos.org/browse/BUGBASH-248

By messing with my APN settings as per above bug report I can use maps and have no more random reboots. Woop woop