Database Info

CyanogenMod 9 v4.0.4 v6.0 + CM Night builds with GAPPS issue!

Hi guys, I just installed the CyanogenMod 9 v4.0.4 v6.0 + CM Night builds, but it has no google apps. So I installed via recovery the GAPPS from the same page I got the ROM.
My problem is, after I installed the google apps, the wallet app just keeps stop working all the time, even without using it, and I don't even need that app!
All I wanted was the gmail app and the play store app!
Anyone knows how to uninstall only the google wallet app, or another solution for this gapp issue?
Thanks in advance!

You can uninstall the app by mounting the system, and deleting it from the system/app folder. I use the root option in ES File explorer.

Can I do that with Astro? I didn't find the option you mentioned!
Sent from my Nexus S using Tapatalk

bjuderas said:
Hi guys, I just installed the CyanogenMod 9 v4.0.4 v6.0 + CM Night builds
Click to expand...
Click to collapse
Edit: Found it in Nexus S (no 4G) forum.
Where is this CM 9 4.0.4 v6?
Sent from my Nexus S 4G using xda premium

CM can be found here: http://forum.xda-developers.com/showthread.php?t=1399035
I use gapps from http://kan.gd/1igc without problems.

Thanks guys, I'll try those gapps!

Problem solved
So, everything is working just fine now!
I did a fresh install of everything.
1st - ROM and gapps.
2nd - 1st boot.
3rd - Kernel install.
Now it's all good, thanks for your help guys!
I read somewhere that after a new ROM install, we should do a 1st boot and then install the new kernel! Seems to work that way!

[Q] Fusion Kernel issue after installing a newer cm build

Trying to install the latest version of aokp(4.1) on the one S..... Prior to 4.1, had no issues with the fusion kernel (2.0)....
Because of the wifi driver being built from source now Fusion ultimate AOSP will break wifi on newer CM builds . Klin1344 suggest using the new kernel since it's much improved and faster...:good:
So I followed the installation instructions on the AOKP Jellybean build 4.1.
Installs great... The kernel switchs from fusion to the new one and WIFI works... as soon as I reboot and it reverts back to the fusion kernel and lose WIFI... I literally need to fastboot the boot.img from rom.zip after every reboot and its driving me crazy.
What do I need to do to prevent the kernel from switching back after reboot? I also tried installing the cm 10 nightly that has a different kernel and it does the same thing. I had a back up( my only backup since my old computer died) with the Fusion Kernel 2.0 with unofficial AOKP Jellybean 4 on it and i have no current issues with this build besides the video glitches.

Cm10 now uses a unified kernel for the one xl ,one s and evo lte. It is also using a open source WiFi module now. Fusion is not using the new kernel source and is not compatible
Sent from my One X using xda premium

So how do I install aokp 4.1 if I have the fusion kernel installed on aokp 4? As soon as install 4.1 , the new kernel works and then as soon as I reboot the phone it seems to revert back to the fusion kernel
Sent from my HTC One S using xda app-developers app

Anyone ? Really want to remove this kernel ... please help
Sent from my HTC One S using xda app-developers app

What you're saying doesn't really make sense. When you flash one kernel, it erases the one installed previously. I'm guessing you are not really flashing the kernel properly in fastboot.

Trying to install the latest version Cm10 ......any build prior to October 1st , had no issues with the fusion kernel...I understand that because
of the wifi driver being built from source now Fusion ultimate AOSP will break wifi on newer CM builds . Obviously I want to update to the latest build and update the kernel ..
my problem is after I install the latest build , The kernel switches from fusion to the new kernel and WIFI works. Then as soon as I reboot and it reverts back to the fusion kernel and lose WIFI completely... I literally need to fastboot the boot.img from rom.zip after every reboot and its driving me crazy.
What do I need to do to prevent the kernel from switching back after reboot? I also tried installing aokp that has a different kernel and it does the same thing. I had a back up( my only backup since my old computer died) with the Fusion Kernel 2.0 with unofficial AOKP Jellybean 4 10 01 on it and i have no current issues with this build besides the video glitches
Sent from my HTC One S using xda app-developers app

Does that make more sense
Sent from my HTC One S using xda app-developers app

So you're saying that without intentionally flashing the fusion kernel it is reflashing itself every time you reboot? Doesn't sound right..
Delete the fusion kernel zip from your phone then reflash the Rom, forget about the kernel.
Sent from my HTC One S using xda app-developers app

Yeah so I've deleted the fusion zip from the SD card, but its installed in the current rom(aokp 01 10) then I follow the installation instructions for both cm 10 nightly 10 09 and aokp 10 08 as usual .... I've tried flashing the boot.iMG in fastboot first then flashing the rom.zip and also flashing the rom.zip then fastboot the boot.img .... the new kernel is there until I reboot and them fusion reappears as the installed kernel and no more Wi-Fi
Sent from my HTC One S using xda app-developers app

2Tone5 said:
Yeah so I've deleted the fusion zip from the SD card, but its installed in the current rom(aokp 01 10) then I follow the installation instructions for both cm 10 nightly 10 09 and aokp 10 08 as usual .... I've tried flashing the boot.iMG in fastboot first then flashing the rom.zip and also flashing the rom.zip then fastboot the boot.img .... the new kernel is there until I reboot and them fusion reappears as the installed kernel and no more Wi-Fi
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Wild guess here... Your'e not confusing fastboot boot boot.img with fastboot flash boot boot.img? The former would just tell your phone to boot using the boot.img, the latter will flash it permanently to the boot partition.

Thanks man.... the things you overlook as a sleep deprived father
Sent from my HTC One S using xda app-developers app

2Tone5 said:
Thanks man.... the things you overlook as a sleep deprived father
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
HEhe yeah, I was just checking how much battery my phone had lost over night and was thoroughly impressed until I realized that it wasnt a very long night

Lol living the dream !
Sent from my HTC One S using xda app-developers app

[Q] Jelly bean on Zeki tablet

Is it possible to install Jelly bean on Zeki 7" tablet? Any instructions would be really helpful...
Thanks!:fingers-crossed:

I'm looking for that too. Idk if it would be worth it though.
Sent from my GT-S5830 using xda app-developers app

Jellybean Zeki TB782B
alex_is_the_1 said:
I'm looking for that too. Idk if it would be worth it though.
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
Im working on polishing up an AOKP JB4.1.2 for the Zeki TB782B at the moment not sure if any one is still interested or not in this. if you do wanna try it when it is done you'll have to flash it through live suite as the system partition on the Zeki TB782B is too small, i should have an alpha release packaged by the end of the weekend.
It is still a 3.08+ kernel from the ICS 4.0.4 update
AOKP JB4.1.2 System
TWRP 2.3.3 Recovery
1st boot takes forever between 5 to 10 minutes on average.
I'm still debating on using the default setup with nandi as the Internal SD or using the newer layout of nandj and adding the databk (nandi) partition if i can get the preinstall scripts working correctly this should speed up boot time after a davik-wipe.
If anyone out there knows the correct way to patch the ft5x_ts.ko we could have a updated kernel but unfortunately the firmware loaded in the touch controller isn't compatible with the open source drivers.

I would love to try it
Check your pms.
Sent from my GT-S5830i using Tapatalk 2

[email protected] said:
Im working on polishing up an AOKP JB4.1.2 for the Zeki TB782B at the moment not sure if any one is still interested or not in this. if you do wanna try it when it is done you'll have to flash it through live suite as the system partition on the Zeki TB782B is too small, i should have an alpha release packaged by the end of the weekend.
It is still a 3.08+ kernel from the ICS 4.0.4 update
AOKP JB4.1.2 System
TWRP 2.3.3 Recovery
1st boot takes forever between 5 to 10 minutes on average.
I'm still debating on using the default setup with nandi as the Internal SD or using the newer layout of nandj and adding the databk (nandi) partition if i can get the preinstall scripts working correctly this should speed up boot time after a davik-wipe.
If anyone out there knows the correct way to patch the ft5x_ts.ko we could have a updated kernel but unfortunately the firmware loaded in the touch controller isn't compatible with the open source drivers.
Click to expand...
Click to collapse
Is it working? I'd like to give it a shot if it is. I've been looking for this for a while but I sort of gave up.

Latest CM 10.1 nightly bug issues for Xoom.

After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD

I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse

Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
RoryPG said:
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
Click to expand...
Click to collapse

sashykanth said:
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
Click to expand...
Click to collapse
So far all my apps seem to be working with cm10.1 20130310 nightly.
Sent from my Xoom using Tapatalk HD

gapps won't flash after reflashing older nightly
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
I had the same exact issue with my Xoom. I reflashed an older nightly and it's working again but now I can't get Gapps to flash properly. Every time it loads no gapps....????
I have tried reflashing the latest gapps 3 times now.
Anyone else have this issue or have Any suggestions? Running twrp if it matters but thinking of switching to CWM to try flashing gapps to see if it will take.

I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD

kevk60 said:
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I did wipe both dalvik and cache before flashing gapps. I was using the gapps 20130301 so it could be that or maybe it's an older version of twrp that's causing the issue because I think I'm on 2.4.1.0.
I saw in another thread that I just read someone else was using a different gapps the gapps unified 20130220. I was thinking of giving that a try but I will try the one you recommended first as we both had the same issue above. I will also try flashing the new twrp to see if that's it as well.
Thanks I'll post back up later whether it worked or not.

If you have goo manager you could just update twrp from there.
Sent from my Xoom using Tapatalk HD

Looks like system ui bug issue has been fixed in the newest cm 10.1 nightly (20130314). Thanks to the devs.
Sent from my Xoom using Tapatalk HD

[Rom]Unofficial-Pacman declared Alpha 8/15 (closed)

PACMAN for New Nexus 7 wifi(flo)
i decide to build PACMAN from Source. it hot and fresh for people to try. the reason why i choose to post in the general area is because one i am not part of Team Pacman. I will do a compile every other day for some builds.
pacman source: https://github.com/pac-man
kernel source: https://github.com/CyanogenMod/android_kernel_google_msm
YOU have to be Unlocked and have a custome recovery installed to flash this.
IF you choose to flash this, in anyway i am not responsible or is XDA responsible if your devices gets damages . the same rules as any other rom. THANK YOU. HAVE FUN
ROM: NEW http://www.mediafire.com/download/r1gvl8l88d2x5dk/pac_flo_4.3-alpha.build.0_20130815-055150.zip
mirror: https://docs.google.com/file/d/0B9qC3vvamytkMDQ3ejhqdWY2ajA/edit?usp=sharing
md5: 71a00ab5b6bc3e2cec501f42a9617aa1
GAPP: any 4.3 package.
Flash rom like normal
changelog
8/3 Intial release
8/4 fixed hybrid properties
8/5 used Pacman Flo vendor trees now
system ui after downloads should b fixed :fingers-crossed:
8/6 Phablet Ui now works..Fixed
8/8 just resync..no big changes.
8/10 small bug fixes
8/12 some more small fixes
8/15 settings apk redone
new bootanimation
some bug fixes in system ui
some bug fixes in framework
bugs:
anybugs found in CM and PA
reboot recovery
wipe system
wipe data
wipe cache
install rom
reboot :victory:
thanks:
Team CyanogenMod
Team Paranoid Android
Team Pacman
Team AOKP
TWRP
Koush
DEV's in general

ROOT
go to settings/developer options/and root access and choose apps and adb
MTP
settings/storage/menu/choose option MTP
Old Roms:
old: https://docs.google.com/file/d/0B9qC3vvamytkRjVCM0J1cnZ1c28/edit?usp=sharing
old: http://www.mediafire.com/download/d0dedgn2a0h2z90/pac_flo_4.3-alpha.build.0_20130810-100120.zip
old: https://docs.google.com/file/d/0B9qC3vvamytkb1NYaUJpQnF4MHM/edit?usp=sharing
old:https://docs.google.com/file/d/0B9qC3vvamytkVDRsNmlBR1lDVE0/edit?usp=sharing
old:https://docs.google.com/file/d/0B9qC3vvamytkRmZfaURCLU9GT1U/edit?usp=sharing

nice

updated fixed hybrid prop..all should pretty much b working fine

Thank you. Will try this once I get home. Was looking for something with aokp features.
Sent from my Nexus 4 using xda app-developers app

your welcome.. i might look at .
Sent from my Nexus 7 using xda app-developers app

skiwong20 said:
your welcome.. i might look at aokp today.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Only problem i seem to have is computer is not recognizing device.

memphian said:
Only problem i seem to have is computer is not recognizing device.
Click to expand...
Click to collapse
Settings>Storage>Menu button in top right (3 vertical dots)>USB computer connection>check Media device (MTP)
That's how I got mine to work.
Sent from my SCH-I545 using Tapatalk 2

I may have to try this out...

kluster1999 said:
Settings>Storage>Menu button in top right (3 vertical dots)>USB computer connection>check Media device (MTP)
That's how I got mine to work.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. Got it to work. The dots weren't there which is probably why I never thought to do it. Had to force them from rom control. It seems the menu dots aren't on a lot of places, such browser and others. Not sure if it reason from rom or not. Shows on my Nexus 4, but it's rom is 4.2.2.
Not meant as a bug report, because I know this is not a maintained rom. Just curious is this is normal behavior.
Sent from my Nexus 7 using xda app-developers app

i have this three dot menu issue as well. i am not sure if its a issue with my vendor tree or if its a pacman bug for there 4.3 branch which is alpha phase
Sent from my Nexus 7 using xda app-developers app

skiwong20 said:
i have this three dot menu issue as well. i am not sure if its a issue with my vendor tree or if its a pacman bug for there 4.3 branch which is alpha phase
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Good. Not just me. I agree probably a alpha phase thing.
Sent from my Nexus 7 using xda app-developers app

Problems
I flashed this rom, and dont get me wrong it is amazing actually Favorite rom so far.:good::good::good: But i ran into problems when the "system UI" kept crashing randomly, esp when installing, also the paranoid hybrid ui wasnt wotking. I jost want phablet mode really. And save the worst for last, the rom kept breaking my super su root. When i root on this rom it says that it cant find my su binaries....
...ok now i restored a backup and tried both twrp and normal and both cant update the binary. When i tried to use superuser instead it said the root was under "legacy", and highlighted red, so it changed it and tried to root but still failed. idk i think it may be rom but not sure.
but anyway sweet rom.
happy flashing!!!!

yep i am aware of the bugs in the build. i am sorry that system ui is crashing. just for u guys runnjng this. Pacman finally added Flo to source so soon someone from the team will post a official build, but until then i will still try to update'
Sent from my Nexus 7 using xda app-developers app

new update..small updates in source. synced to Pacman Flo vendor tree now. Still no Phablet UI. i think random ui crashes when downloading is fixed.

new update...phablet Ui is fixed

I love Nexus devices.
They get much love from devs.
Must flash, can't resist

The reason we haven't released is because of all the bugs that are getting ironed out with the 4.3 merge. Most of which you have experienced. We're waiting to release a stable build. When ready it will be added to the nightly buildbot.

i knew that. i have mention to BKjolly about this. that is why this was originally in general. i have respect for the pacman team.
Sent from my SCH-I605 using xda app-developers app

cant wait to try!!!