Database Info

[Q] Upgrading from CM 7.0.3 stable to nightly without losing anything

I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?

Elbob10s said:
I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?
Click to expand...
Click to collapse
Going from 7.0.3 to the new nightlies is a big jump. They've changed from Gingerbread 2.3.3 to 2.3.4 as well as several kernel changes, and tons of other stuff. In this case it's probably best to do a full wipe before installing the nightly. Then restore your user apps in Titanium, however DON'T restore system data, as this will cause big problems. Any ROM settings that you customized in 7.0.3 (in Settings or CyanogenMod settings) you'll have to manually set again.
edit: One thing to note, if you're a heavy corporate Exchange email user, you'll want to hold off on the nightlies for now. There is an email issue that seems to be occurring on the Inspire only, that causes all email apps to crash when viewing messages on an Exchange server. The problem's been around since nightly 88 and hasn't been fixed yet. However, if this is no big deal to you, then the nightlies have otherwise been working well.

I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now

Elbob10s said:
I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now
Click to expand...
Click to collapse
If you flash a new nightly you'll definitely want to upgrade to the newer LorDModUE kernel as well. It is specifically designed for the newer nightlies.
edit: He's got a new smartass2 cpu governor in v4.0 so be sure to check it out.

+1 for LorDMod UE kernel on CM7 nightlies! Kicks butt!

@Elbob10s,
One more thing I forgot to mention. Once you've installed the new nightly, then it's usually OK to flash subsequent nightlies directly on top of the previous one without wiping. When you do this, you'll need to reinstall LorDMod again, since the kernel will get overwritten back to default.

I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.

Elbob10s said:
I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.
Click to expand...
Click to collapse
Yes that was a known issue on LM 5.x kernel on the newer nightlies. You want to move up to LM UE kernel, the link is in my sig. It was designed for the newer nightlies.

The UE with smartass2 is working great. I fixed the contact icon issue by adding my phone number in the phone settings.
Everything seems to be working great now.

[Q] paranoid cm10 no camera or google now

After I clean flashed Paranoid Android cm10 there is no camera and google now does not work. I flashed gapps 7/26 and even tried the gapps hybrid Google Now but still no camera. Is there a zip or another way to install the camera?
Edit: I flashed everything over the ROM and everything seems to be there.

Try Re-downloading the rom, Gapps, and re-installing the rom with a full wipe. I got everything working on my P999 with the CM10 PA Rom (Build 3). Hope this helps.

maybe a bad flash,
Like yuvin said, Redo the whole process.

I've been having the same problem with PA CM10 (Build 12) from tonyp.
After a clean wipe, I flashed the rom and gaaps, and the camera is there and working. But for some reason, when I change the Paranoid Settings (lowered dpi from 240 (stock) to 190), my camera app mysteriously stops working ("App is not installed").
I've redone the process twice already and was wondering if anyone had any hints as to what's going on. I tried to search in the actual development forum and someone just "re-added the widgets" which seemed to fix the problem. I can't post in the actual development thread to try to ask however (due to low number of posts), so I thought I might try here.
EDIT: I also read that if Gallery is disabled/uninstalled, the Camera would be also. But my Gallery app still works just fine.

[ROM][OFFICIAL] CyanogenMod 9 (ICS) for SGH-T769

CyanogenMod 9 is a free, community built distribution of Android 4.0 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This phone isn't my daily driver, so I only tested a few things, and only slightly:
Known Bugs:
BLN is wonky. This is a CM9 thing and applies pretty much to all the msm8660 devices that use the cypress-touchkey BLN driver. Unlikely to be fixed
Other things maybe? Discuss in the thread...
How to get it:
Download: http://get.cm/?device=t769 (ChangeLog)
Or download it directly through ROM Manager or CM Updater.
Google Apps:
Make sure to download and install the ICS GApps
http://goo.im/gapps/gapps-ics-20120429-signed.zip
IF YOU ARE COMING FROM ANOTHER ROM, PLEASE MAKE SURE TO DO A FACTORY/DATA RESET BEFORE USING THIS. This isn't up for debate. A reset of the dalvik cache helps too. If you do a dirty flash, please make sure to do a dalvik cache wipe. If you have searched this forum for a problem and haven't found it, please do a nandroid backup, then a full factory/data reset and check to see if you still have the problem. If it still persists AFTER the factory/data reset, then report it here.
Thank You!
CyanogenMod Team (all of you, seriously, you guys are awesome)
SGH-T989 Devs (all of you, cuz I basically stole all your configs)
ShabbyPenguin & PlayfulGod for encouraging me when times looked grim.
UberPinguin and others on #jb-dev-e4gt for helping me get all of this work into CM proper
Oreo, my dog, for licking me whenever I needed it.
Older/Unofficial Versions (don't use if you can help it).
For older/legacy/test/unofficial versions of my work, you can find them (for a while at least) here: My Funhouse. Please take care and all necessary steps to verify MD5 sums before installing any zips.

Since CM9 is not a moving target like CM10, it may be some time before we get a point release. Therefore the occassional CM9 Nightly will have to do.
I'm not creating a Q&A thread for this one. Please behave yourselves and be nice to your neighbors.
That is all

Nice work getting it official man
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol

erikmm said:
Nice work getting it official man
Click to expand...
Click to collapse
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work

does cm9 have wifi calling?

Bradlees said:
does cm9 have wifi calling?
Click to expand...
Click to collapse
no it doesnt.

dr4stic said:
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work
Click to expand...
Click to collapse
Lol yea that's true I got aokp-jb and ics almost complete so again thanks for the work
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol

I've been using this due to the stability over cm10. Good stuff!

Hardkeys illumination
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?

lnxzilla said:
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?
Click to expand...
Click to collapse
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.

dr4stic said:
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.
Click to expand...
Click to collapse
I see, tnx for the clarification as it was my understanding the issue only occurs when the lights are actually used for notifications hence the BLN name. Oddly enough I didn't notice this happening when I was running the unofficial build, must have been a coincidence then I suppose.

CM9 after 11/2 will contain WiFi Random MAC fix
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run

dr4stic said:
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run
Click to expand...
Click to collapse
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......

boulos said:
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......
Click to expand...
Click to collapse
This is why swiching mounts is not great. The kernel flash replaces the boot.img.
Your best bet might be to wait till the next CM9 nightly comes out and modify that one.

Nightly build
CM9 downloads seem to go to internal storage but CWM was directed to perform update from external sd (ie microsd card). Unless I'm missing something, it doesn't look like the location can be changed manually.

Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?

creeve4 said:
Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?
Click to expand...
Click to collapse
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.

Which cm9 version are you using?
Sent from my SAMSUNG-SGH-T769 using xda premium

lnxzilla said:
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.
Click to expand...
Click to collapse
I've found that CLEAN flashes eliminate this for me on all ROMS. I think multiple dirty flashes like flashing updates over previous versions will eventually mess things up expecially when changes r made to the kernel
-I'm not a Dev, I just flash alot-
-If I've helped you the Thanks button is only 2 clicks away!

@woodzx67: Currently latest official cm9 20121125
@johnb380: Started fresh with a full wipe a few times already, makes no difference in this case as the data connection issue has always been there for me with cm9 in particular. I've only used cm10 briefly, don't recall that happening but then again the SOD issue prevented it from running for too long.

[Q] Strange slider behaviour

Hi all,
I am using team OES 4.2 Nighties ROM with KAT Kernel and I have installed the KAT audio ap.
My issue is that I only have one digital slider available under the top right menu (when i slide down the top right section of the screen).
Sometimes it is the brightness slider, and sometimes it switches to the Volume slider.
I cannot find any setting that would allow me to choose what is available in this section.
I would like to find there the Volume and brightness sliders, on top of each other.
Can anyone help me fix that?
Thank you in advance.
D

Deazo said:
Hi all,
I am using team OES 4.2 Nighties ROM with KAT Kernel and I have installed the KAT audio ap.
My issue is that I only have one digital slider available under the top right menu (when i slide down the top right section of the screen).
Sometimes it is the brightness slider, and sometimes it switches to the Volume slider.
I cannot find any setting that would allow me to choose what is available in this section.
I would like to find there the Volume and brightness sliders, on top of each other.
Can anyone help me fix that?
Thank you in advance.
D
Click to expand...
Click to collapse
Revert back to your nAndroid backup and or start fresh.... could just be a bad flash or a confused mod lol make sure you wipe dalvik caches before starting from scratch
sent from
TF-101 A.R.H.D Harmony Kernel w/KingBeatz
Samsung Galaxy S3
AOKP 4.2.2 Kt747 kernel w/KingBeatz

Thank you for the response.
The solution you propose is rather drastic...
I have finally found a rom/kernel combination that works, my tablet works pretty well and this is the only issue I am having really.
What is a "bad flash"?
When installing I have wiped everything twice, and even wiped cache and datsik after install.
Is there not a way to get into system files and replace what is broken?
Just a shot in the dark, I am no android expert...
Thanks again

Deazo said:
Thank you for the response.
The solution you propose is rather drastic...
I have finally found a rom/kernel combination that works, my tablet works pretty well and this is the only issue I am having really.
What is a "bad flash"?
When installing I have wiped everything twice, and even wiped cache and datsik after install.
Is there not a way to get into system files and replace what is broken?
Just a shot in the dark, I am no android expert...
Thanks again
Click to expand...
Click to collapse
Replacing system files through device never recommend unless you know what your doing that's just method for bricking
By bad flash means when the mod/kernel etc when being downloaded isn't complete or is missing small sections that causing a portion not to work ..
AOKP 4.2.2 by Task650
Ktoonz Kernel w/KingBeatz
TF101 A.R.H.D ICS w/KingBeatz

[Q] Random visual flashes/errors while using fresh PA

Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck

Turn off the corresponding setting in the developer options.

Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.

Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel