Tomorrow's build will have this little bigger than usual bug fix / feature tweak addition: https://plus.google.com/+CyanogenMod/posts/41vvE569zr2. (Thanks Rdlgrmpf for the tip)
I just wanted to ask you about that
and..when will be M2 release?
Hi
It seems that on my device, poweramp is not compatible with the lockscreen of Android 4.2, when poweramp plays music, the lockscreen flashes and I'm unable to use the music widget.
Am I the only one who has this issue ? Do you have a workaround ?
Thanks
Nico
Mine works (see screenshot). I had to disable ICS lock screen support (deselect), and got it going
Sent from my Inspire 4G
The CM backuptool script...is that included in the "cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip" files, and runs at flash? Or is it a separate cool script that I need to run?Update installation instructions:
Download Nightlies / M-Series
Put the file on SD card.
Reboot to recovery.
Format /cache
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
No need to flash gapps as CM backuptool script should take care of them.
Reboot and enjoy.
I just now read (I know, I know lol) the first posts instructions for an update (dirty flash):
The CM backuptool script...is that included in the "cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip" files, and runs at flash? Or is it a separate cool script that I need to run?
Nice! Thanks for the info! I will stop formatting /system as part of my dirty flashing then. And yes, I guess I misunderstood the lockscreen issue. A User is 100% correct. That is Poweramp's built-in lockscreen function.it is included in every cm 10.1 rom from here.
if you once have flashed gapps you do not need to flash it again as long as:
you do not wipe /system yourself
flashing the rom formates /system after the backup was performed and resoteres the backup afterwards. though you won't get notified about that. it just happens
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
regarding poweramp and lockscreen:
i think there was a misunderstanding here i am correct.
actually, last time i tried poweramp and the music default music widget on the locscreen i had issue too.
BUT the poweramp's own lockscreen and widget works fine. the picture posted by an user before is the poweramps OWN lockscreen.
Nice! Thanks for the info! I will stop formatting /system as part of my dirty flashing then. And yes, I guess I misunderstood the lockscreen issue. A User is 100% correct. That is Poweramp's built-in lockscreen function.
PS: slightly off topic, but do you know if jellyTime & codefireX builds will also carry that CM script function regarding /system?
Backuptool.sh checks for ro.cm.version and version number which should be 10.1 at the moment. If that matches, then it does the backups, if not it just flashes and you need to apply gapps afterwards yourself. I know for sure it doesn't work in cfX (at least for the moment, I may look into making it work tomorrow) because we have removed ro.cm.version but I don't know about JT. You can check its build.prop for confirmation. It should be something like: ro.cm.version=10.1<anything else>. Modify the beginning and script goes dead unless it's modified too (like I did for my test bench rom).
Very awesome Mustaavalkosta! Here's the build.prop for my JT ROM from my nandroid backups:
If I add that line into my codefirex backup's build.prop file, restore it - and once the new version from synergy is out, theoretically that would mean a dirty flash would run backuptool.sh - and retain /system ?
- ro.cm.version=10.1-20130127-UNOFFICIAL-ace
su [enter]
bmgr transport com.google.android.backup/.BackupTransportService [enter]
Will do! Looking forward to your backuptool.sh work
Man, I HATE to bug you...maybe I'll just PM you about this....but when I full wipe/install your ROM (and JellyTime & PipelinerArd's cm builds) along with the latest gapps, the system uses my google account as the backup account on the phone. Codefirex however, uses a "debug-only private cache", which disables the phone from automatically downloading my apps from the Play store, as well as not restoring my previous wallpaper and wifi settings.
Here's what I mean:
So (bringing it back on topic to your ROM lol), where is this handled in settings that allows the backup account to sync with your build?
PS: This is a work-around for codefirex to enable Google as the backup account. However, once you run the commands in a Terminal app, it's too late to sync:
AT TERMINAL EMULATOR PROMPT:
This enables the backup account.Code:su [enter] bmgr transport com.google.android.backup/.BackupTransportService [enter]
hi guys, i just installed this, been using 7.2 for a long time.
everything works nice and smooth , love it : )
could someone tell me how to clear widgets from lockscreen "slide" ? on the left side is empty screen, on the right is camera, and above unlock is clock, any chance to remove those 3 ?
#include
/*
* 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.
*/
CyanogenMod said:We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
fastboot flash boot boot.img
mkdir cm10
cd cm10/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
mkdir -p .repo/local_manifests
wget https://github.com/Mustaavalkosta/android/raw/cm-10.1/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Flashable zip to copy /proc/last_ksmg to your sdcard, no adb needed: http://downloads.codefi.re/mustaavalkosta/last_kmsg.zipRegarding the reboots, it would be incredibly helpful if someone could get a last_kmsg after an unexpected reboot. To do so, go directly to recovery after the reboot (without booting into android) via the volume key and power button, then run adb pull /proc/last_kmsg on your computer and upload. I thought the issue was stemming from out of pmem errors like on vision which is why I increased pmem allocation again. Without any evidence, it's just guesswork though.