I just installed cyanogenmod 10.2 on my tab 2 7.0 and i turned on bluetooth however my bluetooth keyboard which worked in stock doesn't show up when scanning. I'm not sure if bluetooth is even working at all.
Jxt. said:
Hello,
does it scan other nearby devices?
Is your tablet visible to other devices?
Click to expand...
Click to collapse
Ok the keyboard connected after a while. It was actually the keyboard that was having issues since after a while I was able to see my neighbors in the dorm next to me s mac book showing up on bluetooth. The only issue I have still is that the delete key doesn't really function as backspace I have to highlight a chunk of text then hit it to delete. I downloaded an app called delete key as backspace but I can't figure out how to set that up. I looked in the screenshot instructions but cannot find a section for physical keyboard.
Jxt. said:
did you check the keyboard layouts?
Click to expand...
Click to collapse
where is that exactly I looked and all I can seem to fine are languages but I looked and theres nothing in there about delete as backspace
I have a P5113 running cm 10.2 nightly. It seems to be finicky with bluetooth. I use sixaxis to connect my PS3 controller, but sometimes it just won't connect. Have to manually turn on/off bluetooth a few times, wait a few seconds, try again. It eventually will work though.
Jxt. said:
Did you see this in your language input settings?
Click to expand...
Click to collapse
No when the keyboard is connected I still don't see physical keyboard options
Jxt. said:
Nightlys are always buggy, i also use the ps3 sixaxis but i never have trouble getting the bluetooth to stay on.
You should check out Pacman ROMs. :laugh:
Click to expand...
Click to collapse
I'm using a version called cm-10.2-20130919-UNOFFICIAL-p3110 It's not a nightly or even an official cyanogenmod supported version I think. I just ended up with it by following a youtube tutorial. This makes me think that when cyanogenmod for the tab 2 7.0 progresses I won't be able to update through cyanogenmod update.
If this is the case will I be able to just flash a rc version of 10.2 when it becomes available without having to wipe data factory reset? I really hate having to reinstall everything
please tell my you can put the home back and multitasking buttons back to normal in that rom. I really don't like what they have done with hiding them and having you drag your finger up from the bottom to get at them.
Really I just want the lightest rom possible using the least amount of resources on my tablet
Jxt. said:
I don't understand how yours look.. screenshot please
Click to expand...
Click to collapse
Uploaded with ImageShack.us
the home button and back and task switch buttons are normal in mine but they r in that annoying circle you have to swipe up to get in pac rom. I looked at a few roms before jumping on the cyanogenmod bandwagon
Jxt. said:
I don't see a circle...
Click to expand...
Click to collapse
no i am running cm 10.2 and pac rom has a half wheel thing. Look at the screenshots in this thread suggested earlier. I was just stating that I don't really like the way the buttons are in that rom as I looked into it earlier
http://forum.xda-developers.com/showthread.php?t=2202854
mikee286 said:
No when the keyboard is connected I still don't see physical keyboard options
I'm using a version called cm-10.2-20130919-UNOFFICIAL-p3110 It's not a nightly or even an official cyanogenmod supported version I think. I just ended up with it by following a youtube tutorial. This makes me think that when cyanogenmod for the tab 2 7.0 progresses I won't be able to update through cyanogenmod update.
If this is the case will I be able to just flash a rc version of 10.2 when it becomes available without having to wipe data factory reset? I really hate having to reinstall everything
Click to expand...
Click to collapse
I see you switched to PAC Rom already but back to your original question.
There was a Bluetooth keyboard problem with CM 10.2 early versions.
I think you were using Cody's version of CM 10.2 in the latest versions of CM 10.2 they fixed the "Bluetooth Keyboard Bug" so if you want to use CM 10.2 you just need the latest versions or you can install an app to fix the Keyboard problem and keep using the older versions.
https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
hcfte said:
I see you switched to PAC Rom already but back to your original question.
There was a Bluetooth keyboard problem with CM 10.2 early versions.
I think you were using Cody's version of CM 10.2 in the latest versions of CM 10.2 they fixed the "Bluetooth Keyboard Bug" so if you want to use CM 10.2 you just need the latest versions or you can install an app to fix the Keyboard problem and keep using the older versions.
https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
Click to expand...
Click to collapse
thank you I am downloading the app. I have not switched to pac rom I was debating it but I ended up going with cm because its not bloated.
As I mentioned in an earlier post I think I am using an unofficial build of cm 10.2 built sometime in september. Would I be able to flash an official nightly build without having to wipe data factory reset Again the file I have currently flashed is cm-10.2-20130919-UNOFFICIAL-p3110
mikee286 said:
thank you I am downloading the app. I have not switched to pac rom I was debating it but I ended up going with cm because its not bloated.
As I mentioned in an earlier post I think I am using an unofficial build of cm 10.2 built sometime in september. Would I be able to flash an official nightly build without having to wipe data factory reset Again the file I have currently flashed is cm-10.2-20130919-UNOFFICIAL-p3110
Click to expand...
Click to collapse
I think this http://forum.xda-developers.com/showthread.php?t=2391355 is the Rom you are using it's the same one I use on my P3113. When CM 10.2 first came out they had a BT problem and that app worked for me.
I believe CM fixed the problem before Cody's last release and my keyboard has been working again without needing the App to fix it.
I just checked my Backspace button and it works fine on my BT 3.0 keyboard.
I did switch the Kernel to Next 2.1.2 so I don't know if that makes any difference.
I would ask in Cody's thread about being able to flash the latest CM 10.2 over Cody's without doing a clean install.
Related
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
pplayz18 said:
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
Click to expand...
Click to collapse
Which CM10 build are you using? It's my understanding that on the current build of the official CM10 NFC is not yet supported. This could be the case on the unofficial ones as well but I'm not sure.
Relentless D said:
Which CM10 build are you using? It's my understanding that on the current build of the official CM10 NFC is not yet supported. This could be the case on the unofficial ones as well but I'm not sure.
Click to expand...
Click to collapse
A nightly unofficial one released last night. 3.0.39
The only thing that is different about getting GW working on CM10 is you don't need to flash anything (except Google Wallet if you are using the .zip provided by ogdobber) and editing the build prop. NFC is currently broken on the newer CM (and all others based off of CM code) for the time being but I would imagine it would be fixed after the main bugs are all squared away.
The last unofficial build I that had NFC working was InvisibleK's 8/13 but that was before the recent MMS or RIL fixes.
Marcismo55 said:
The only thing that is different about getting GW working on CM10 is you don't need to flash anything (except Google Wallet if you are using the .zip provided by ogdobber) and editing the build prop. NFC is currently broken on the newer CM (and all others based off of CM code) for the time being but I would imagine it would be fixed after the main bugs are all squared away.
The last unofficial build I that had NFC working was InvisibleK's 8/13 but that was before the recent MMS or RIL fixes.
Click to expand...
Click to collapse
I figured it out. I was trying to use the same verizon zip file when I needed to use one specifically for aosp roms.
pplayz18 said:
I figured it out. I was trying to use the same verizon zip file when I needed to use one specifically for aosp roms.
Click to expand...
Click to collapse
Do you have a link to get it working?
pplayz18 said:
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
Click to expand...
Click to collapse
if you took the time to read the notes on the release, you would see that it is not supported yet.
Since you did not, now you will likely have a ton of people telling you to read next time.
NFC DOESNT WORK. THEREFORE NOTHING THAT RELIES ON IT WORKS.
Its a piece of hardware, that does not FUNCTION yet.
did you also figure out that NFC doesn't work on any CM10 build yet so it doesn't matter what you flash?
Not to thread jack... but...
It's been quite a few days without any action on this thread and NFC is one thing I'd really like to try out. With that said I love CM10, currently running the 8-27 nightly without any other issues and love it... NFC isn't that important that I'd go back to a TW/Stock Rom for it.
Any word from the CM guys on when/if the rils and NFC functionality will be fixed up? Patiently waiting and love everyone working on CM10 D2VZW! :good:
Flashed the 8-31 nightly and NFC just greys out after ticking the box still. Wake me up when September comes
Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies
I was reading in the official CM10 thread that someone had developed a fix and that it would soon be implemented into the Nightlies
Edit:
http://forum.xda-developers.com/showpost.php?p=30952627&postcount=1317
hello all running into a issue with the current 29 december build of CM10 i got every thing booted up but there is no app button for accessing any apps. and the home screen is blank. i tryed the last 5113 nightly build but there is no onscreen qwerty keyboard... i am stuck can any one help me?
justin_48 said:
hello all running into a issue with the current 29 december build of CM10 i got every thing booted up but there is no app button for accessing any apps. and the home screen is blank. i tryed the last 5113 nightly build but there is no onscreen qwerty keyboard... i am stuck can any one help me?
Click to expand...
Click to collapse
Same problem here. I've been trying to go back to stock since its not fixed... You wouldn't have a 4.1.1 stock jelly bean for the p5113 would you?
Tyler.Boston1 said:
Same problem here. I've been trying to go back to stock since its not fixed... You wouldn't have a 4.1.1 stock jelly bean for the p5113 would you?
Click to expand...
Click to collapse
Sadly i dont have anything... hell i didnt even do a back up so im screwed my self...
Same issue here. no Apps button in latest nightly
Solution !!
justin_48 said:
hello all running into a issue with the current 29 december build of CM10 i got every thing booted up but there is no app button for accessing any apps. and the home screen is blank. i tryed the last 5113 nightly build but there is no onscreen qwerty keyboard... i am stuck can any one help me?
Click to expand...
Click to collapse
Hey, I have the same problem and i am running it on my galaxy S2- GT-I9100g. it seems that it's a launcher problem so i tried to install NOVA launcher and guess what it worked, so i am running NOVA launcher temporarily till a new version of CM10.1 comes out or find another solution .
Hello,
Here is a build of CM10.2 from repo sync on 11/01/2013 for TAS5713 (Amplifier) outputs:
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited.
TAS5713 (Audio Amplifier):
Download: https://www.androidfilehost.com/?fid=95784891001602458 (168MB)
MD5SUM: 3d817ba4eb918ecaae799c3959d8e9da *cm-10.2-20131101-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF/HDMI: Use stock CM 10.2 nightly build.
Recovery: https://www.androidfilehost.com/?fid=95784891001602450
MD5SUM: e003bea5a89bac797313029b4f0a5206 *cm-10.2-recovery.img
To install:
Boot into recovery mode:
Code:
fastboot boot cm-10.2-recovery.img
When Q has reached recovery mode:
1. choose "install zip"
2. choose "install zip from sideload"
From PC:
Code:
adb sideload cm-10.2-20130910-UNOFFICIAL-steelhead.zip
It is a good idea to wipe data and cache. If coming from my previous cm-10.1 image, it may be possible to avoid wiping data/cache.
Sideload gapps if desired:
gapps-jb-20130813-signed.zip http://goo.im/gapps/gapps-jb-20130813-signed.zip md5sum:
1f51b5cc6370c1f45dc951109b6ce6ed
From within recovery, "install zip from sideload" and:
Code:
adb sideload gapps-jb-20130813-signed.zip
If cm10.2 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu.
Please let me know how these work for you. I'm using these TAS5713 and CM 10.2 seems to be working mostly fine. The only probelm I found so far is that Chrome Browser in Google Play Store says it's not compatible with this device for some reason. Pulling the .apk off a phone and "adb install" to Nexus Q seems to work fine.
Hi,
Just a quick one, there doesn't seem to be a stock nightly build of cm 10.2. Any chance to see a build with optical out support?
Thank you.
Sent from my Nexus 7 using Tapatalk 4
Working very well here, no issues so far. I'm so glad, that there's still some activity in Q's development.
Thank you!
Sent from my Galaxy Nexus using Tapatalk 4
I'm dying to try this out, but I couldn't get CM installed... I can't seem to use the keyboard to input text, so I can't even get it to connect to my router. Mouse works fine, keyboard ( tried two different keyboards) don't seem to work.. some keys work, like home or print screen or something like that, but none of the actual letter or number keys do anything. I get a message that pops up really quick saying that the AOSP keyboard has stopped functioning. again, mouse works fine... both mouse and keyboard work fine with the Quantum Singularity build.. any ideas?
I would just assume that it was something wrong with this particular nightly of CM, but others seem to have got it working?
EDIT: I should specify I am having problems with the TAS5713 build you posted above.
-J
Hello,
I have not noticed the issue with the keyboard. That being said, I am primarily using a Logitech keyboard that came with the Logitech Revue (Google TV) device. It is a decent wireless keyboard also including a trackpad. I have also been using an Apple BT keyboard and it also works fine. I also tried a USB to PS/2 adapter to connect a keyboard and mouse and it also worked.
I have a new CM10.2 build with the latest 4.3 patches which seems to be working well. I will try to post it soon.
One thing I struggled with (again) was that after updating and reinstalling gapps, the sound did not come out, at least no sound except the "alarm" sounds. I had seen this before with CM10.1, and using one of the volume control widgets available in the Play Store seemed to fix the problem. Not so this time, I had to fastboot -w flashall to fix it. Even wiping from recovery didn't do the trick.
-Howard
I have a stock q ..how can i flash this image i don't have recovery or anything like that installed.
Does this allow HDMI audio and analogue output at the same time?
THE_KINGDOM said:
Does this allow HDMI audio and analogue output at the same time?
Click to expand...
Click to collapse
anybody?
Sent from my Nexus Q using Tapatalk 2
THE_KINGDOM said:
anybody?
Sent from my Nexus Q using Tapatalk 2
Click to expand...
Click to collapse
If you use this build, audio signal transfers only through the banana plugs. Since we cannot toggle between this and hdmi audio output, one must install stock cyanogenmod in order to use the latter.
Sent from my Nexus S using Tapatalk 4
ottoemezzo said:
If you use this build, audio signal transfers only through the banana plugs. Since we cannot toggle between this and hdmi audio output, one must install stock cyanogenmod in order to use the latter.
Sent from my Nexus S using Tapatalk 4
Click to expand...
Click to collapse
i really hope somebody finds a way to merge these together soon so that HDMI/TAS5713 can be used at the same time
Sent from my Nexus Q using Tapatalk 2
THE_KINGDOM said:
i really hope somebody finds a way to merge these together soon so that HDMI/TAS5713 can be used at the same time
Sent from my Nexus Q using Tapatalk 2
Click to expand...
Click to collapse
That'd be a cool feature. Another (and less comfortable) possibility would be to have a dual boot enabled kernel. First rom would be the HDMI build, the second one the other. I'm afraid though it won't happen, since - apart from cyanogen's - we don't really have any custom kernels.
Sent from my Nexus S using Tapatalk
I know a little OT but has anybody managed to mount a USB storage device since putting CM10.2 on? I haven't managed to since installing CM10.2
Sent from my Nexus Q using Tapatalk 2
THE_KINGDOM said:
I know a little OT but has anybody managed to mount a USB storage device since putting CM10.2 on? I haven't managed to since installing CM10.2
Sent from my Nexus Q using Tapatalk 2
Click to expand...
Click to collapse
No success on my side either.
Sent from my Nexus S using Tapatalk
Does this build, or any build of CM for that matter support the LED light ring? I personally think that feature was a great and would love to still be able to use it.
ottoemezzo said:
No success on my side either.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
viffer_man said:
Does this build, or any build of CM for that matter support the LED light ring? I personally think that feature was a great and would love to still be able to use it.
Click to expand...
Click to collapse
agree this feature should be utilized.
Just thought folks should know that the new 10.2 nightlies allow sound to come out via HDMI and SPDIF (digital out) simultaneously. I don't know about the amplifier since I don't use that output, but I suspect it does that too.
mahler47 said:
Just thought folks should know that the new 10.2 nightlies allow sound to come out via HDMI and SPDIF (digital out) simultaneously. I don't know about the amplifier since I don't use that output, but I suspect it does that too.
Click to expand...
Click to collapse
Sounds good. Can somebody can confirm that the Amplifier works with the latest nightlies?
If yes, we could always have the latest CM on our Q :good:
At the moment I`m using the Image from this thread with very well AMP support.
But my overall Performance is not the best. Little bit laggy. (screenshot)
You have the same Performance ?!
Edit:
http://i.imagebanana.com/img/038unthe/Screenshot_20131027192313.png
I uploaded a new cm 10.2 build from November 1, 2013 today to the original post. As far as I know, the cm 10.2 nightlies still do not support the audio amplifier.
hharte said:
I uploaded a new cm 10.2 build from November 1, 2013 today to the original post. As far as I know, the cm 10.2 nightlies still do not support the audio amplifier.
Click to expand...
Click to collapse
Excellent, I cannot express how grateful I am.
Sent from my Nexus S using Tapatalk
hharte said:
I uploaded a new cm 10.2 build from November 1, 2013 today to the original post. As far as I know, the cm 10.2 nightlies still do not support the audio amplifier.
Click to expand...
Click to collapse
Thank you hharte :good:
Latest build runs great !
So I'm trying to prolong the use of this tablet but keep it stable and quick, and I think CyanogenMod is the way to go. There are a number of versions available for it, with 10.0 being the last stable build that I can find. I flashed 10.0 and it was quick and stable, except for one major problem: the Google+ app just would not load no matter what, and by searching I found others had the same issues with no fix.
So I'm back to stock 4.1.2 JB now, which is fine but I'd rather move to CM if I can. I flashed the latest nightly, but was having major issues with Gapps closing and the Play Store wasn't even available (even though I flashed the correct Gapps package).
For those that are using CM, which version is the best to use? Any help would be much appreciated, thanks!
Honestly, I use the CM11 builds and they are working great.
XOOM XOOM!
slinky317 said:
So I'm trying to prolong the use of this tablet but keep it stable and quick, and I think CyanogenMod is the way to go. There are a number of versions available for it, with 10.0 being the last stable build that I can find. I flashed 10.0 and it was quick and stable, except for one major problem: the Google+ app just would not load no matter what, and by searching I found others had the same issues with no fix.
So I'm back to stock 4.1.2 JB now, which is fine but I'd rather move to CM if I can. I flashed the latest nightly, but was having major issues with Gapps closing and the Play Store wasn't even available (even though I flashed the correct Gapps package).
For those that are using CM, which version is the best to use? Any help would be much appreciated, thanks!
Click to expand...
Click to collapse
CM10.1 (based on 4.2.x) really great. I used it for the past few months.
Never give me problem. Of course you must install 2/20/13 JB Unified GApps.
Looking forward to try CM11 but having hard time with TWRP (big part) at the moment.
TheMan0790 said:
Honestly, I use the CM11 builds and they are working great.
Click to expand...
Click to collapse
Another vote for CM11, but you do have to install BigPart. That isn't a big deal if you read carefully through the resource thread before proceeding. I'm certainly not a tech wizard (color TV and phones without dials were big deals when I was a kid, VCRs didn't come out until I was in college, and I was in my mid twenties when home computers just started to become widespread) and was able to run BigPart without trouble.
I got BigPart working successfully with no problems on the first go. Merely requires some reading and should work fine.
Break me off a piece of that Kit-Kat ROM!
Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !
Atlantic_Rim said:
Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !
Click to expand...
Click to collapse
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Ok thanks for reply !
Then I think I will wait for the official release, because I want a fully functional version for my moto G
Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I know the great job devs are doing for us before the moto G I had a LG optimus L7 and thanks to cyanogenmod I had kitkat on it.
But as far as this phone just came out, I'm asking myself if it's good to avoid my warranty just to have the same version of android ...
(correct me if I say bad words because I have to train my english :laugh: )
Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks
i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.
Entropy512 said:
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.
Click to expand...
Click to collapse
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.
i_rnb said:
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.
Click to expand...
Click to collapse
There could be risks if you flash an unofficial build from someone who is not at all working on merging a device into CM - they often cherry pick all sort of stuff that causes incompatibilities with upstream to the point where the product really shouldn't be called CM. (I've seen lots of "CM" kangs that had all sorts of extra crap added beyond just doing what is required for device bringup...)
dhacker, however, is an official CM maintainer for many devices, so his builds are the ones that are "on track" for official inclusion.
OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out
U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK thanks, then I think I will flash the unofficial ROM when I have time
Atlantic_Rim said:
OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out
Click to expand...
Click to collapse
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.
Entropy512 said:
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.
Click to expand...
Click to collapse
Ok thanks for the informations ! After one hour of intense fighting with my computer, I finally unlocked bootloader, rooted, and flashed cyanogenmod I prefer this rom to the stock one, I find it more smooth, and more costumization
i think its ok for daily use. At least i use it everyday.
I posted this question in a couple other places, but no reply.
I have the GPE version of the Moto G, and I want to run the CM11 builds on it.
Will the fact that the GPE version has the ext4 fs on it prevent me from getting these to work?
I know there are recoveries available specifically for the GPE, but will getting the CM11 builds to work be just a matter of changing a few entries in fstab?
And finally, do either of the recoveries allow you ro format /data from either f2fs to ext4 or the other way around?
Thanks/
I've replaced stock Rom (4.4.2 US Global Version) for unofficial CM11 (2014-02-16's release) and for now CM works more stable than stock.
I had few reboots or issue with .flac, in CM's everything is OK, for now of course. Very good stuff even that is only nightly's release.