Database Info

[ROM-DEV] Android 2.0.1-r5v0.6 (Dead)

Android 2.0.1-r5v0.6
Dead:
==============
After spending some time and looking over this rom and ways to make it work with out any legal issues. The most viable option was to build something like what cynanogen has built. His process takes the proprietary bits (all google apps including sync) and copies them off onto the SD card before doing a update. After the update it copies them back to the newly installed rom. This method basically does a automated backup/restore of your licensed applications. I can't do this for several reasons including that we are supposed to be coming from a 1.5 OS to a 2.0.1, which isn't compatible with the older application set.
Temporarily Offline:
==============
I am sorry to have to do this but we are now having more then just a small handful goofing with this ROM and I need to take this offline while I inspect each of the parts and make sure all licensing is in order since its a bit more then the google Opensource framework. I know that several other ROM creators have not paid much attention to it as I am going to now but I really don't want to upset any IP holders like what happened to Cynanogen a couple months back.
I will put it back up but I want to make sure that I am totally covered and don't have any issues.
version 0.6: download (offline)
==============
-fixed wifi thanks to http://forum.xda-developers.com/showthread.php?t=593620
-Now starts up with Android stock keyboard. (No longer needs HTC_IME.apk for second keyboard)
A few have asked for this ROM so I thought I would put it up here for anyone that wants to contribute to or take from it.
This ROM is only compatible with the Sprint CDMA HTC Hero. It is not finished and still requires some work but its good enough for my day to day use and I am sure others may find the same potential.
This ROM is vanilla android and what it takes to actually get it running on a CDMA phone. It is built off of this GSM variant. I am going to try and work to remove the google bits so that you can use Cynanogens method of extracting your own and then doing a follow up update to install them. My efforts for this is not to build a better rom but to build a cleaner base that has limited to no proprietary IP.
Credits to all on this forum how have helped or contributed in any way to building the roms that are here. I would point out names but there are to many to name. I am positive that anyone that pays attention to this forum will know who you are. I used many parts of these ROM's and many others on XDA to build this one.
This is my first ROM and was primarily made for myself to help me learn how to create a custom ROM.
Here is the link to my blog where I originally posted about this and a video of it booting.
Here is the Youtube video of it booting: http://www.youtube.com/watch?v=tRTh-rXKe-E
*Warning*: Don't attempt to flash this ROM onto anything else unless you know what you are doing! I am not responsible for any device malfunctions or "Bricks".
Notes on Installing:
- Run a Nandroid backup before you do anything.
- Make sure you do a full wipe first. (Sorry )
- Run the update zip found * Version 0.6 *(offline) from the recovery console.
To get the HTC keyboard installed: (Now Optional as of Version 0.6)
- Follow the instructions here.
Things that don't work:
- Gallery some times has issues.
- Camera
- Wired or Wireless Tethering (Now Testing)
- Orientation
- Trackball light
- Trackball click (Rolling and moving are fine)
- (Let me know if something else needs to go here.)
Possible issues that are not repeatable:
- speaker not working on out bound calls? I made 30 test calls to my home phone and was not able to replicate this issue. Needs to be verified (see here)

Awesome! Thanks! disregard my PM lol.. Great timing.

VoXHTC said:
Awesome! Thanks! disregard my PM lol.. Great timing.
Click to expand...
Click to collapse
LOL I was just getting to replying to you!

im trying it now nice work

Let me know if any of you have issues flashing. I still have it all right here in front of me if I need to make a change.
FYI: The first boot takes for ever as it registers all the APKS.

i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this

thorracing1 said:
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
Click to expand...
Click to collapse
So you installed both the HTC_IME.apk and the Clicker.apk? Did you do a adb push or a adb install?
Try and go into settings --> Language & Keyboard --> Touch Input --> Text Input?
I think its a force of habit with out really thinking to go there and calibrate but just going there may help.
Try that and let me know.

i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!

2.0t03speed said:
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
Click to expand...
Click to collapse
Awesome, keep the feed back coming as you have it!

please take note orientation doesnt work. please put in first post.
otherwise, great work!

should i do adb install or adb push?

blankd3ckskat3r said:
please take note orientation doesnt work. please put in first post.
otherwise, great work!
Click to expand...
Click to collapse
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
BTW thanks for the feed back!

thorracing1 said:
should i do adb install or adb push?
Click to expand...
Click to collapse
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.

dchadwick said:
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
Click to expand...
Click to collapse
lol well its a common problem, cant wait for a fix. really like what you did with this build

dchadwick said:
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
Click to expand...
Click to collapse
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
removed SDcard.. boots now trying to push.. but where do I push the apk files to?

blankd3ckskat3r said:
lol well its a common problem, cant wait for a fix. really like what you did with this build
Click to expand...
Click to collapse
Thanks, but I really can't take to much credit. Its a "Pick and Pull" from several ROMs. This one actually came from our GSM Brothers and then I used the CDMA tricks in this form to make it work.
I keep watching and playing with the Google Nexus Dumps. I would really like to get one of them up and running.

Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?

VoXHTC said:
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
Click to expand...
Click to collapse
Wow thats allot in a little space.
What I gather is that it originally booted, then after trying to install via droid explorer and then astro it now just dies after the lockscreen.
I am not sure where to start. I would just say to do a full wipe, then a clean install. Then if you have the sdk try the ADB install method as Cynanogen's post talks about.
I am working on trying to get the stock Android keyboard to work. If we can figure out that then we don't have to mess with the HTC one.

ok i got it i just adb pushed them to system/app works great

obelisk79 said:
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
Click to expand...
Click to collapse
Yeah, actually some of your work if I remember correctly, thats why its got the same issues. My first goal when I built this for my self was to get past the blasted google bits sync loop. The more I worked into it the more I moved on to the 2.0.1 build with some of your stuff in it.
Your welcome to anything I have learned, its really not my work.

[ICS][ALPHA][02-03-2012]CM9 with camera support

This is a snapshot of my work on bringing camera support to Tezet's Milestone2 ICS port.
This is continuation of this thread: http://forum.xda-developers.com/showthread.php?t=1520572
- it's based on CM9 snapshot from March 2nd
- it may contain more (or less) bugs from Tezet's builds. It's simply different, newer etc.
- it should be possible to load this without factory reset on top of Tezet's CM9 builds and the other way around, though the last time I've tried this was early February...
- there's no need to wipe dalvik cache - the update script does this
- the fix for SIM lock pin is not included
- there's no Torch and file manager app. Don't ask
Camera notes:
The work is based on Atrix ICS camera support, with added overlay emulation.
What is working:
live preview
zooming
flash
focus
exposure compensation etc
taking photos
some 3rd party apps (Pano, CameraFX, Barcode scanner)
doesn't crash when enterinng video/panorama mode
generally much more stable
... probably not much more
What is not working:
panorama mode
video recording
a lot more
Other stuff: (compared to previous version)
- bluetooth should be OK (please test)
- aGPS should work
I highly recommend to do a nandroid backup before trying it.
Latest version available at http://code.google.com/p/cm9-milestone2/downloads/list
If your phone is stuck on Google logo, it means you have chosen a wrong version and you need to recover your phone from the SBF file.
Repository:
repo init -u git://github.com/rondoval/android.git -b ics
All the credits go to:
- Tezet, for the Milestone2 port
- tpruvot, Quarx2k, for their tremendous efforts on Defy support (and thus Milestone2)
- whole Atrix-Dev-Team, Raviprasad V Mummidi, zivan56 for their tremendous work on the camera driver

Just backing up my MS2 now. Going to flash it over CM7 Tezet and see how it goes.
Cheers for the efforts

omg thanks ! download...
Sent from my MotoA953 using xda premium

mattyt_491 said:
Just backing up my MS2 now. Going to flash it over CM7 Tezet and see how it goes.
Cheers for the efforts
Click to expand...
Click to collapse
its for CM9....

devilbatghost said:
its for CM9....
Click to expand...
Click to collapse
Actually this would be a good test... I did that in december. I had some issues, bu I think that was mainly due to wrong version of gapps.
If you're still planning to try upgrading from CM7 to CM9: You may need to wipe telephony provider data and deskclock after upgrade.
/data/data/com.android.deskclock/databases/alarms.db
/data/data/com.android.providers.telephony/databases/telephony.db
Please tell us how did it go

hi, rondoval.
chrome beta don't work. can you try to fix it when you have free time? thx.

rondoval said:
Actually this would be a good test... I did that in december. I had some issues, bu I think that was mainly due to wrong version of gapps.
If you're still planning to try upgrading from CM7 to CM9: You may need to wipe telephony provider data and deskclock after upgrade.
/data/data/com.android.deskclock/databases/alarms.db
/data/data/com.android.providers.telephony/databases/telephony.db
Please tell us how did it go
Click to expand...
Click to collapse
I know it is CM9 I said I was flashing (upgarding) FROM CM7.
As per your advice I cleared alarms.db and telephony.db and was going well.
I also was unable to find the fix for the SIM PIN lock, so I just disabled it.
I haven't yet tried the gapps for ICS because the download through multiupload.com is not working (seems as though multiupload in general is down).
I can confirm that the camera works (photos only) and was able to upgrade from CM7 with no issues without wiping my data.
The ROM is smooth and seems to handle most tasks I have thrown at it. However, I am finding 3D performance a bit lesser than that experienced on CM7 (not a major issue).
Cheers.

Good work, thx! Glad to see we have one more dev working on our MS2.

This rom is awesome!!! =D
Someone can upload the Gapps 4.0.3 please ? because the link on the other post is dead.
Thanks in advance

tony_the_unik said:
This rom is awesome!!! =D
Someone can upload the Gapps 4.0.3 please ? because the link on the other post is dead.
Thanks in advance
Click to expand...
Click to collapse
Here's the link to gapps http://goo.gl/krVg1

Thanks for the gapps link.
Out of interest is there a fix for the Sim pin code yet?
Sent from my MotoA953 using XDA

Some news:
First 5sec 480p video recorded.
Going to cinema now, so don't expect a build today.

New patch for 1% step battery counter on this build

rondoval said:
Some news:
First 5sec 480p video recorded.
Going to cinema now, so don't expect a build today.
Click to expand...
Click to collapse
thank you. I am glad to see the video recording fixed

Is there any bug for the touch?
Since when I am touching and holding on the screen, it displays I'm swiping horizontally instead of holding it (I enabled "Show touches" in Development Tools)

I believe i might have run into a bug, Im not sure if anyone has note this bug or not. In the apps menu, if you hold a application, you can drag it to Remove which will uninstall the app normally, however at the moment, dragging it to Remove does nothing. Does anyone have a idea whats wrong?

i have a huge problem. when my phone is booting up, it only shows the google logo, and.. nothing happend. only a black screen with backlights.
if i try the X factory reset, the screen with an exclamation mark pops up -
but if i press the @ key, nothing happen.
if i try to the connect my phone with RSD lite, the bootloader is loading but shows 'battery low
cannot program'
when i was trying to load the ROM my battery was ~50%...
what should i do?
after a few times failing with the @ - it works.. one time..pressed the factory reset - booted up - still bugged with the google boot up logo...

hi, aznsniper
i have the same problem,i have no idea to solve it. sorry... maybe rondoval will fix it in next build.

@jimbo0815
Did you factory wipe, cache wipe and dalvik wipe before installing the rom? If you did, is it possible that you installed the wrong version? Just my 2 cents worth.

aznsniper said:
I believe i might have run into a bug, Im not sure if anyone has note this bug or not. In the apps menu, if you hold a application, you can drag it to Remove which will uninstall the app normally, however at the moment, dragging it to Remove does nothing. Does anyone have a idea whats wrong?
Click to expand...
Click to collapse
ylqiu said:
hi, aznsniper
i have the same problem,i have no idea to solve it. sorry... maybe rondoval will fix it in next build.
Click to expand...
Click to collapse
that's a problem of trebuchet, the launcher. so it has to be fixed there.
but i think should be like that.
Sent from my MB525 using XDA App

[APP] GooManager Beta official thread

The official app of Goo.im
We have spent a lot of time getting the server side changes in place to automatically parse our developer's rom files to grab data to make a functional OTA update system without the need for editing manifest files, or other tedious tasks. This is our attempt at creating a way for Android developers to simply publish material, and distribute it to the masses without any hassle.
This app is and will always be FREE!
General Features:
Ability to browse and search all of the files we have on our site, and download directly to your mobile device.
Receive OTA style updates from your favorite rom developers that we have hosted here.
CyanogenMod nightly build update support
Incremental (differential) rom updates for sequential builds
Flashing roms & installing recoveries
Update gApps packages
If you would like to sideload the app on your phone and avoid the market, we distribute the APK by itself, and also as a prebuilt repo maintained by solarnz(github.com/solarnz)
Are you a rom developer wanting to publish your work with our updating system?
To get your rom compatible with our updating system, you should make the appropriate changes to your build.props. For more information on this system, see the link below (sorry it's not clickable but i need 8 posts!)
goo.im/howto-rom-updating-via-our-app (For developers who are curious about how to modify their build prop file for compatibility with GooManager)
GooManager download page (To download the actual app)
KNOWN ISSUES:
DownloadManager API is buggy on Gingerbread
Installing OpenRecoveryScript on devices that do not support flash_image and do not have a /cache/recovery/command supported recovery will fail
FEATURE REQUESTS
Feel free to post them in this thread, but as my time is limited and Goo.im/GooManager's code is just something I do in my free time, there are simply not enough hours in the day to address them all
SHOUT OUTS
Chris Solarnz (For his java advice and contributions)
Mike Wielgosz (For contributing to the rom reordering and listing code)
Dees_Troy for all of his amazing work on OpenRecoveryScript and TWRP
eyeballer (For countless nights of helping test stuff, and awesome suggestions)
Shift (For the market icon)
Drmacinyasha (For all the testing / anal retentive bug reporting)
toastcfh (For helping bounce lots of ideas around)
EVERYONE ELSE I PROBABLY LEFT OUT!
FREQUENTLY ASKED QUESTIONS:
Why is _________ phone/tablet not supported?
In order to offer us flexibility without compromising other software such as rom manager premium, etc we did not want to rely on /cache/recovery/extendedcommands. At the time of developing the flash automation features, extended commands were licensed to RM only and it would have been illegal to use them. Since then, the license has changed, but we still feel it is the best direction to have our own since we can change it to fit our needs.
Why does this not work with my recovery i downloaded from Rom Manager?
CWM and CWM touch builds distributed by rom manager ONLY WORK WITH ROM MANAGER SO STOP ASKING!!!! #@$#@$#
Why are incremental updates only available for some roms?
Incremental updates are enabled on a per rom-device basis. Not all builds are even capable of this, since wipe can be required. It is at the discretion of the developer to toggle this as needed.
If you are a developer and would like to sign up: goo.im/signup
If you are a recognized developer, chances are you will get approved. (Note not all buildbox applicants are approved, and you may get only hosting)

Awesome. Used it to put TWRP2.1.2 easily on my ATT Galaxy Note.

It's Goo time! Been using this to distribute my unofficial cm9 nightlies for the touchpad and nook color for a while now and we've had nothing but positive feedback from users. Encourage your favorite rom developers to sign up

Not only is GooManager a great app, the whole ecosystem is, I believe, second to none.
A fantastic, simple system for developers to upload their ROMs and specify what device that ROM is for.
Easy for device users to find the ROMs that work with their devices.
Notifications of ROM updates for the ROM that you're using.
Easy download and installation of ROMs for devices with a supported recovery.
Differential updates - only flashes the files that have changed from one version to the next - smaller download, less wear and tear on your device, and quicker updates.

Thanks for this free app!
People don't have to donate to automatically check if there is an update to a CM nightly now.

for those of us who are not update-happy (although it is addicting) is there anyway to know from either this app or from Goo notifications in general whether an update requires a full wipe and then the requisite re-setting up of one's device?
I get a notification everyday for the new Gapps and for an update of my ROM (AOKP milestone 5 for Kindle Fire). I've ignored them because I'm just too lazy to spend an hour or two getting everything back up and running.

I've tried repeatedly to download CM9 nightlies and gapps via the latest market version of the app (2.06 I believe) and I always get a "download failed" message no matter if I'm on wifi or 3g. I've tried uninstalling and reinstalling, clearing cache, and clearing app data, and nothing seems to work. Is the download manager problem referenced in the OP a problem with ICS as well as GB? I have a Galaxy Nexus (toro) using BAMF Paradigm 1.25 in case that info makes a difference.
Sent from my Galaxy Nexus using Tapatalk 2

lanceman5000 said:
I've tried repeatedly to download CM9 nightlies and gapps via the latest market version of the app (2.06 I believe) and I always get a "download failed" message no matter if I'm on wifi or 3g. I've tried uninstalling and reinstalling, clearing cache, and clearing app data, and nothing seems to work. Is the download manager problem referenced in the OP a problem with ICS as well as GB? I have a Galaxy Nexus (toro) using BAMF Paradigm 1.25 in case that info makes a difference.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please get a logcat. It will give you a reason why the download failed. If you are on linux, adb logcat | grep GOO
There seems to be issues with some people or devices that I have yet to narrow down. If you can replicate this bug consistently please contact me on freenode IRC in the #goo-inside.me channel and i'll try to look into it. My time is limited these days hunting a bug i can't reproduce so despite the needs of the community -- work and life comes first!

peters4n6 said:
for those of us who are not update-happy (although it is addicting) is there anyway to know from either this app or from Goo notifications in general whether an update requires a full wipe and then the requisite re-setting up of one's device?
I get a notification everyday for the new Gapps and for an update of my ROM (AOKP milestone 5 for Kindle Fire). I've ignored them because I'm just too lazy to spend an hour or two getting everything back up and running.
Click to expand...
Click to collapse
It is up to the developer to state whether it requires a wipe in their changelog. Generally nightly builds will not require a full wipe though

thereals0up said:
Please get a logcat. It will give you a reason why the download failed. If you are on linux, adb logcat | grep GOO
There seems to be issues with some people or devices that I have yet to narrow down. If you can replicate this bug consistently please contact me on freenode IRC in the #goo-inside.me channel and i'll try to look into it. My time is limited these days hunting a bug i can't reproduce so despite the needs of the community -- work and life comes first!
Click to expand...
Click to collapse
I have no clue what I'm looking at, but here is the logcat of a download attempt. At least I hope this is what you meant.
http://db.tt/bpWD2LWo
Sent from my Galaxy Nexus using Tapatalk 2

Anybody can explain how to use with Galaxy note CM9?
I'd li ke to flash nightly in diff mode. First of all do I need to unistall cwm and install the open recovery?
Somebody has already tried?
Inviato dal mio GT-N7000 con Tapatalk 2

I like this app man, Good work...

Great job, it's nice to see such a useful app for no cost.

Raistlin82 said:
Anybody can explain how to use with Galaxy note CM9?
I'd li ke to flash nightly in diff mode. First of all do I need to unistall cwm and install the open recovery?
Somebody has already tried?
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
You simply install goomanager, hit menu -> install openrecoveryscript which will DD over the image to your recovery partition for twrp 2.0.
As far as differential patches go, the feature is still being enabled on a per-rom basis while I make sure there are no bugs CM nightlies in general do not have it enabled yet but some devs do.. the list will improve but i don't want to make any big changes until I am 100% positive the incremental system is perfect

I'm having quite a few failed downloads recently via goomanager, anybody else?
Not sure if this is device related issue or they app/appserver etc.
Using GTAB P1000 btw.

This thing is a piece of crap if you are trying to download on 3g.

superstargoddess said:
This thing is a piece of crap if you are trying to download on 3g.
Click to expand...
Click to collapse
Please keep this conversation constructive. If you have anything relevant to resolving the issue go ahead and post it but complaints are not helpful. If you have a failed download, paste a logcat or simply the line which gives a numerical code for why the download failed. The tag will be "GOO"
We are aware of downloading issues but since this is just a project we do strictly on free time for no profit, we can only get what we can afford which is why we are on all used hardware and frequently have hiccups with our distribution boxes. We're looking into getting more in the rotation to lower the load on the servers but there are not enough hours in the day or dollars in the bank account to handle it right away. We're looking into financing some sexy new servers from dell if we can get approved

thereals0up said:
You simply install goomanager, hit menu -> install openrecoveryscript which will DD over the image to your recovery partition for twrp 2.0.
As far as differential patches go, the feature is still being enabled on a per-rom basis while I make sure there are no bugs CM nightlies in general do not have it enabled yet but some devs do.. the list will improve but i don't want to make any big changes until I am 100% positive the incremental system is perfect
Click to expand...
Click to collapse
Ok so I prefer to wait...I have no rush.
But it is safe to install the openrecovery? I mean 0% of brick over n7000 running CM9
Inviato dal mio GT-N7000 con Tapatalk 2

thereals0up said:
Please keep this conversation constructive. If you have anything relevant to resolving the issue go ahead and post it but complaints are not helpful. If you have a failed download, paste a logcat or simply the line which gives a numerical code for why the download failed. The tag will be "GOO"
We are aware of downloading issues but since this is just a project we do strictly on free time for no profit, we can only get what we can afford which is why we are on all used hardware and frequently have hiccups with our distribution boxes. We're looking into getting more in the rotation to lower the load on the servers but there are not enough hours in the day or dollars in the bank account to handle it right away. We're looking into financing some sexy new servers from dell if we can get approved
Click to expand...
Click to collapse
Sorry, was just being honest! ^^
Edit: I'd totally donate if it were reliable on 3g!

superstargoddess said:
This thing is a piece of crap if you are trying to download on 3g.
Click to expand...
Click to collapse
Then complain to your 3G provider dumbass.

[Q&A] CyanogenMod 12.0 for Photon Q

Q&A for CyanogenMod 12.0 for Photon Q
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.
Before posting, please use the forum search and read through the discussion thread for CyanogenMod 12.0 for Photon Q. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.

I really wanted to know that everybody has no problem at all in logging in Google+ with the latest version of its client.
I'm having trouble the most recent one that I can download from Play Store, : v5.1.0
I had to restore the backed up version of v5.0

I recently got the multimedia dock for this phone and I've noticed that some things don't work. None of the USB ports on the dock seem to interface with the OS, but any peripheral connected by a USB OTG cable (while not in the dock, of course) works just fine. Also, the device doesn't seem to detect that it is in a dock at all; I have it set to daydream when it's docked, but nothing happens.
Does anybody else have these issues? Is there a known or planned solution?
Thanks!

Hei just another quicky:
I had problems with twrp unable to mount /data on encrypted phone. I was never asked for passphrase also it did not detect data was formated as f2fs and assumed ext4.
After factory reset I reformated data and cache to f2fs again (as I think the performance gain is real) and cleanflashed latest cm12 nightly + gapps.
After setting up my phone it became slugish fast again, also battery did drain fast (also the phone did get real hot)
My circumvention so far is limiting Background processes to 2 within Dev options. Since then phone stays much cooler, everything works as expected normal cpu usage shows 2.5/3.2/3.5.
Before that phone was sometimes at 12/9/8 or so and thus bekame unresponsive/sluggish.
Does anyone know the standard count of background processes? Form Q?
Since i did not discover any strange behavior/lags since i switched to only 2 backgroundprocesses anyone knows what kind of usage could result in problems with lower backgroundprocesses?
Thanks in advance!

CM 12.0 nightlies I/O and issues
So I switched over to CM12 because of the ability to switch the filesystems to f2fs. And so far I have seen a pretty decent improvement in the response, speed, and general performance with CM12.
A few issues have come up though:
CM nightly 03232015
-the cLock widget just randomly stopped functioning. Worked for a day or two, then stopped working. I wasn't able to set the alarm and clicking on the time on the home screen does nothing. Disabled cLock and am using the default Deskclock instead (I need to be able to set alarms).
-the messaging app was not working correctly... I was able to receive texts but the send button was greyed out and would not let me click on it. This is both over Wi-Fi and 3G and 4G LTE. Had to revert to 8sms that I was using on CM10...
-the themes are applied inconsistently... not all apps or system dialogs are themed when I use ThemeDIY to create/apply my own theme.
-equalizer doesn't seem to make a big difference...
-doesn't seem to remember wifi logins... keep getting the "sign in to wireless network" notification (I've already signed in)... the sign in page does not open in Chrome, but rather a separate browser or system page that won't offer to save my password (though it does autofill the username)...
-weird issues using adb... even though I've authorized the computer, and have root access on the phone and am running adb root, it won't let me write to certain parts of the file system (I couldn't adb push bootanimation.zip /system/media/bootanimation.zip error was "read-only filesystem")
I know it's a nightly, just wanted to see if anyone else has these same issues and to make sure the developers are seeing this. For the record, I did a wipe and format (since I was going to change the file system,) and this is a clean install of both TWRP and CM12.
Thanks!
---------- Post added at 06:15 PM ---------- Previous post was at 05:58 PM ----------
breakerwaves said:
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
Click to expand...
Click to collapse
I didn't know what to use either so I left it on NV. Haven't noticed a difference in signal or call quality or anything. I am guessing since we're on Sprint and there is no SIM card that RUIM/SIM won't work?

Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.

kecksk0enig said:
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
Click to expand...
Click to collapse
I can't speak to the RUI/SIM issue but I don't know how to switch themes off. As far as my SMS and cLocks idk it is possible that I disabled the wrong app I don't like to run more then the bare minimum. As for the theme I ended up downloading a dark theme from the app store which is wonderful looking!! It is called Nicholas' Dark Material. In case you're looking for dark like me.
Do you have issues with the gallery or camera? I think I saw somewhere on the xt897 forum a link to motorola's camera and gallery apps... are you able to change the save location for pictures or no?
I also had an issue where the navigation bar does not render right when I watch full screen video in landscape mode. May have to do with me forcing GPU render under developer options. I'd take it off but I can't remember how I got there lol
---------- Post added at 11:27 PM ---------- Previous post was at 11:21 PM ----------
I cannot set the custom color for notifications in CM12... but there is a post that says the colors were retained on an upgrade from CM11. Well I wiped and did a clean install rather than an upgrade so is there an .xml file or a settings I can edit? I'm comfortable with file manager and editor and adb and shell...

CM 12 update
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??

nasch007 said:
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
Click to expand...
Click to collapse
If you only apply the update, it will not wipe the device. You would have to wipe it manually in recovery. It will apply a so-called "dirty flash" as you are not wiping any partitions.
CM12-->CM12, should be fine. Of course before you report any issues try a clean flash (or if it's a single app FC'ing, try clearing data on that single app).

I'm having tons of trouble using this with Sprint.
When I lock it to CDMA and/or EVDO mode, Logcat shows that it's trying to connect using a C Spire APN. If I lock it in LTE-only mode and select Sprint APN, it gets a good data connection. The APN menu is foolishly disabled for CDMA/EVDO so I cannot correct the issue. Why is it trying C Spire? How can I fix 3g and MMS settings to work?
CM11 worked great in all conditions, and MMS worked out of the box.

I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:

Alien987 said:
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Click to expand...
Click to collapse
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.

arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks

Alien987 said:
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Click to expand...
Click to collapse
Yes, that's the correct one.
The CM maintainer clearly states the reasoning in the CM12 thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse

arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Adjusting the meta-inf to check for "asanti" instead of "asanti_c" worked perfectly. Thanks for your help!
Now I have to find out why after I flash gapps I start to get multiple crashes related to Google Services and Google Apps.
Edit: Well, just in case someone face the same problem in the future. I updated to the latest TWRP recovery directly from their webpage (initially I used Rashr app) and that solved all my problems, including the initial error when flashing CM12 nightly.

[Q&A] [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST

Q&A for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST
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.
Before posting, please use the forum search and read through the discussion thread for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Where to go from here
Not sure what happened, hope this didn't get posted twice.
Hi,
I am still happily using the Samsung Infuse 4G, and was running the stock GB 2.3.6. No real issues, and although starting to get a sense of it being dated was having no issues and in no rush to go out and upgrade. However, we recently purchased a 2015 Subaru Legacy with their Starlink multimedia system. The Infuse, as it was with the stock GB had no problems connecting via BT for phone and audio functionality. But, the car system reports that the phone is not compatible for messaging. In my endeavors to understand why, I thought, maybe incorrectly, that GB does not support the MAP profile.
So, that led me to, is it possible to add that, and how do you do it, or is it time to upgrade? Flash a new ROM? I can't seem to find much on the specific issue I am trying to resolve and if a new ROM would fix it, but since the phone is way out of warranty I decided to try rooting and flashing a ROM. I am new to this so I went with the Aeon 1.4 ROM based on GB 2.3.6 (I think), hoping that it was a bit less risky. Everything went well and seems to be working fine. But, it did not fix the messaging issue with the car. I assume because it is really still GB.
Am I going about this wrong? Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.

Hi there,
mainwheel said:
Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Click to expand...
Click to collapse
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"

joel.maxuel said:
Hi there,
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.

mainwheel said:
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
Click to expand...
Click to collapse
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.

joel.maxuel said:
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?

mainwheel said:
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
Click to expand...
Click to collapse
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.

Downloadable CM 10.1
joel.maxuel said:
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Click to expand...
Click to collapse
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George

mainwheel said:
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
Click to expand...
Click to collapse
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.

joel.maxuel said:
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
Click to expand...
Click to collapse
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George

mainwheel said:
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
Click to expand...
Click to collapse
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.

joel.maxuel said:
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
Click to expand...
Click to collapse
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George

mainwheel said:
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
Click to expand...
Click to collapse
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George

mainwheel said:
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
Click to expand...
Click to collapse
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Android 4.4 support for two new Bluetooth profiles to let apps support a broader range of low-power and media interactions. Bluetooth HID over GATT (HOGP) gives apps a low-latency link with low-power peripheral devices such as mice, joysticks, and keyboards. Bluetooth MAP lets your apps exchange messages with a nearby device, for example an automotive terminal for handsfree use or another mobile device. As an extension to Bluetooth AVRCP 1.3, users can now set absolute volume on the system from their Bluetooth devices.
Click to expand...
Click to collapse
Gone this far, might as well give it a shot. :fingers-crossed:

joel.maxuel said:
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Gone this far, might as well give it a shot. :fingers-crossed:
Click to expand...
Click to collapse
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George

mainwheel said:
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
Click to expand...
Click to collapse
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.

joel.maxuel said:
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
Click to expand...
Click to collapse
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George

mainwheel said:
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
Click to expand...
Click to collapse
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.

joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I appreciate the help and will try to make some time to install these files. Will let you know. George

joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Hi Joel,
Unfortunately, none of these 4.4.x versions will install, same error. And placing Voodoo/lagfix/ folder doesn't seem to work either, same error. If the problem is the jump to the next version is too great, maybe an earlier version of something, 4.2 or earlier? George