User-agent: Mediapartners-Google Disallow: User-agent: * Disallow: /search Allow: / Sitemap: http://nox4developper.blogspot.com/sitemap.xml Nox 4 developper: CM12
Affichage des articles dont le libellé est CM12. Afficher tous les articles
Affichage des articles dont le libellé est CM12. Afficher tous les articles

[Q] CM12 - Link2SD ? topic






Anyone please confirm whether Link2SD is working on Lollipop (CM12) ?
I tried but it endedup linking base.apk files instead of Folders !! :confused:






[Q] script link2sd cm12 topic






I've the problem for the create script of link2sd in the cm12, have you?
Is it non compatible with android 5 or is it a problem of cm12?
I've try to do all format, ext2, ext3, ext4 and fat32 too, but i'ive always a problem.






[FIX] CM12 I9100 Camera Video Recording Fix topic






Hi!
Camera Recording Is Needed In My Case So I Managed To Fix It .
I Modified Old AOSP Camera Apk.
Just Some Changes, :p
Done




Bugs :
* Some Times You Will Have Force Close
* Tell Me

Link To CM12 I9100: http://forum.xda-developers.com/gala...od-12-t2955551



Notes: This Is KK Aosp Camera
Just Install As Normal App


Enjoy














Attached Files





File Type: apk CameraLollipop.apk -
[Click for QR Code]
(3.95 MB)










CM12 for Note 3 SM N900 (Exynos) topic






Hi everyone (especially devs)...

Some devs (Thanks to all!) are trying to port CM11 to Note 3 SM N900.
There is lag problem and it's not solved yet. It is not convenient for daily usage.
Also, there are little bugs (but these are not important problems).

Now, I am curios about is there anybody who thinks to port CM12?
We, all Note 3 SM N900 users, are waiting an AOSP ROM and I think we deserved it.
Please, do it and make us happy.






[Q&A] [CM12] [Lollerpop] JFLTESPR Nightly Kangs topic






Q&A for [CM12] [Lollerpop] JFLTESPR Nightly Kangs

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 [CM12] [Lollerpop] JFLTESPR Nightly Kangs. 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! :)






Titanium Backup Not Restoring in CM12 topic






Hello All

I am having trouble restore apps to CM12 Unofficial with Titanium Backup.
I moved from CM11.

I could restore calls and messages fine, but general apps get stuck restoring.
Any ideas?

I've tried using all the modes etc but no luck.
I searched but could not find anything.

Merry Christmas
Scott






Minfree settings in CM12 Roms topic






As there are again and again discussions concerning the minfree settings in CM12 roms, I decided to open this thread. If a moderator thinks, this is the wrong place for this thread, just move it, to where it belongs.

Obviously, since the last builds of CM12, the settings for minfrees cause some trouble. After a clean install of any rom, the minfree settings in trickstermod and in fauxclock are completely empty. In fauxclock the settings for OOM (out of memory) Score as well. Some people entered them manually, but I'm afraid, this won't help.

To really solve this, you have to do the following steps: open your file explorer, go to sys/module/lowmemorykiller/parameters. There you will find 5 files. Two of them do not have correct permissions. The first one, called adj, is for the OOM Scores. The other one, called minfree, is, you won't guess it, for the minfrees. :fingers-crossed:

As you see, both of them have only write permissions, but no read permissions. So I guess, the system will ignore these settings completely. I checked this, using cool tool from play store, very nice tool to show for example the actual free ram in your status bar. And in deed, the ram went down to 25MB, after I had opened a handful apps, and then my phone stopped working. I only could do a reboot.

Now the solution, which is quite easy: change the permissions into rw-rw-rw (666), and maybe change the group under owners into root (I'm not sure, if this is necessary, but it does make no problems, so why not).

Et voilà - if you now open trickstermod or fauxclock again, you will see the preset parameters. As you can see also, the minfrees there are really high. In another thread, there have been suggested the following settings, which are a good standard:

trickstermod 48/60/72/84/96/120
fauxclock 12288/15360/18432/21504/24576/30720

Important: In fauxclock, the minfree settings are not made in MB. You have to enter the so called "pages" for minfrees, which I can't explain exactly, what this is. In general, if you want to change minfrees in fauxclock, just take the settings in MB, you want to, and multiply by 256. This will give you the correct values.
BTW I don't think, it's a good idea, to change the OOM Scores, as long as you do not know exactly, what you're doing.

So, hopefully I could help a bit and clear some things up. But the final question to the CM devs remains:

is this a bug or is this a feature? :confused:






Problem with CM12 based ROMs topic






One issue that I have is that sometimes the speaker cuts out during a call so I can't hear anybody. I have to put the call on loudspeaker and then off again so I can hear them. It also seems to cut out if I bring the number pad up as well. I've had this on 2 CM12 based ROMs - Candy5 and AICP - and it happens with both of them. I've just flashed a stock based ROM - I don't like stock based ROMs - and I don't have the issue.
Does anybody else have this problem? I'm using a D855.






[Q] Error when compile cm12 topic






When i compile cm12 for s5312 devices we had error:
Install system fs image: /home/karthick/ROM/*cm12/out/target/*product/corsica/*system.img
/home/karthick/ROM/*cm12/out/target/*product/corsica/*system.img+/home/*karthick/ROM/cm12/*out/target/product/*corsica/obj/*PACKAGING/*recovery_patch_interm*ediates/*recovery_from_boot.p maxsize=1023356928 blocksize=135168 total=380108490 reserve=10407936
#@echo -e "3[33m""Package target files:""3[0m"" /home/karthick/ROM/*cm12/out/target/*product/corsica/obj/*PACKAGING/*target_files_intermed*iates/*cm_corsica-target_fil*es-da94839291.zip"
building image from target_files RECOVERY...
building image from target_files BOOT...
Traceback (most recent call last):
File "./build/tools/*releasetools/*make_recovery_patch",* line 53, in <module>
main(sys.argv[1:])
File "./build/tools/*releasetools/*make_recovery_patch",* line 49, in main
common.MakeRecoveryP*atch(input_dir, output_sink, recovery_img, boot_img)
File "/home/karthick/ROM/*cm12/build/tools/*releasetools/*common.py", line 1167, in MakeRecoveryPatch
td_pair = GetTypeAndDevice("/*boot", info_dict)
File "/home/karthick/ROM/*cm12/build/tools/*releasetools/*common.py", line 1118, in GetTypeAndDevice
return PARTITION_TYPES[fsta*b[mount_point].fs_ty*pe], fstab[mount_point].d*evice
KeyError: '/boot'
build/core/*Makefile:1422: recipe for target '/home/karthick/ROM/*cm12/out/target/*product/corsica/obj/*PACKAGING/*target_files_intermed*iates/*cm_corsica-target_fil*es-da94839291.zip' failed
Please help us to solve this problem. Thank you






[Q] add another button to navigation bar cm12 topic






How to add another button on the nav bar on cm12,? im using blisspop rom. I need to add more button because my softkeys is not working..






[ROM] Unoffcial CM12 for d2tmo topic













In short this is simply a early look as to what CM12 will have to offer. You will be experiencing lollipop the way Google and the Cyan team has set fit. Please keep in mind that these are still early development so there will be issues.


Small note of features up to latest build
· Quick Pull-down
· Brightness Control from Status bar
· Notification count
· Option to turn on Nav Bars (if you want the full Lollipop look)
· Ambient Display
· under the hood stuff
· Many more...(soon?)


!!! Flash on your own risk !!!
We can and will not take any responsibility for bricked devices or lost data. So please watch out!


Installation
- Make a (Nandroid) Backup of your current ROM
- Full WIPE (wipe data/factory reset + wipe cache partition + wipe dalvik cache)
- Select ROM from sdcard
- Install ROM
- After flashing, reboot device (First reboot will take a while)
- Enjoy CM12 on your device!











BETA 1 [17/12/14]
- First release
-Note: Stock Camera dose not work but third party ones have been find useful and data may be lost













To stay updated on the original post and see what is happening when it happens see my Google Plus






Attempting to Build Beanstalk from SkiWong's CM12 device tree topic






Hi all,

Moderators: If you feel this doesn't belong here, I apologize now, but based on the sticky, it feels like this is the right forum.

I have been working on a Beanstalk LP port for the Nexus 6. I am trying to figure out if anyone has seen this build error before, as Google and forum searches have found nothing relevant. I have worked through a number of issues, but am now stuck. SkiWong has been very very helpful. I have been able to build a complete image build, but when I run make bacon after selecting the device in the lunch menu, I am now getting this message at the end as it is building the ZIP file.

raceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 1652, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 1609, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files", line 589, in WriteFullOTAPackage
""+input_zip.read("SYSTEM/bin/otasigcheck.sh"))
File "/usr/lib/python2.7/zipfile.py", line 935, in read
return self.open(name, "r", pwd).read()
File "/usr/lib/python2.7/zipfile.py", line 961, in open
zinfo = self.getinfo(name)
File "/usr/lib/python2.7/zipfile.py", line 909, in getinfo
'There is no item named %r in the archive' % name)
KeyError: "There is no item named 'SYSTEM/bin/otasigcheck.sh' in the archive"
build/core/Makefile:1642: recipe for target '/home/pwn3r/beanstalklp/out/target/product/shamu/aosp_shamu-ota-eng.root.zip' failed
make: *** [/home/pwn3r/beanstalklp/out/target/product/shamu/aosp_shamu-ota-eng.root.zip] Error 1

#### make failed to build some targets (02:17:52 (hh:mm:ss)) ####

I can't tell if something didn't sync some required files or if something isn't there. Based on what I see it looks like the file SYSTEM/bin/otasigcheck.sh is missing. That said, I don't know why or where to get one.






CM12 bootanimation (HDPI only) topic






Excuse me, i want to share bootanimation extracted from cm12
it's really awesome:D

how to use
-backup your current ROM
-copy my attachment to system/media and replace
-reboot
-done

credit:
Alloh SWT :good:
@Mardon :good:
@Mike :good:
CyanogenMod Team :good:

NB : tested only on Xperia Arc S (HDPI devices) cm12








Attached Thumbnails


Click image for larger version<br/><br/>Name:	148.png<br/>Views:	N/A<br/>Size:	14.6 KB<br/>ID:	3071778
 











Attached Files





File Type: zip bootanimation.zip -
[Click for QR Code]
(1.15 MB)










Can't copy Rom to Internal SD when on CM12. topic






Hey guys i have a small problem. I can't copy Cloudy rom(or anyother rom for that matter except CM12/PA) to my LG G3's internal SD. It says that the file is to big. What should i do? CM12 is a bit to buggy for my taste so i need a stable custom stock rom.






How to Downgrade from CM12 to 4.4.4 stock topic






If you hate Cm12 and you want to go back to 4.4.4 and had no computer?? This the right guide for you!
Thanks from the stock flashable zips by lost101 :)

Let's get started!
1 - Download the flashable zips for:
XT1032:https://docs.google.com/uc? id=0B6RNTe4ygItBMGdkTGE2R2JXQlU&export=download
XT1033:https://docs.google.com/uc?id=0B6RNT...xport=download
XT1034?:https://docs.google.com/uc?id=0B6RNT...xport=download

Iv'e fixed the links for mobile users that cannot download this (if you know that i mean):)

Reboot to recovery via cm12's advanced reboot or the manual method (Turn off the phone and hold power and volume down and choose recovery). I choose CWM!

You do is wipe data/factory reset, wipe cache, dalvik cache, system and flash the zip.
P.S. It will take a while to flash so don't panic :D
If the flashing is completed reboot your phone and the warning disable recovery flash, say yes to disable it and let it boot up and youre done:):) you have downgraded!

Press the button THANKS! if it helped you a TON! :p






[GUIDE][CM12] Compiling CM12 for Moto G and cherry picking features. topic






Here's a little something for the guys (and flashaholics) who don't like to wait for devs to release new CM12 builds.

AFAIK ROMS CAN'T BE COMPILED ON 32 BIT SYSTEMS. ONLY 64 BIT.

We start with setting up the build environment:
First, start with installing this:

Code:


sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

Once that is done, we go about installing JDK-7 since that's the one that works for lollipop :p


Code:


sudo apt-get install openjdk-7-jdk

Then we install the Android SDK for some useful stuff:


Code:


sudo apt-get install android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers android-tools-adbd androidsdk-ddms  android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview

Once all that is dealt with, we can move on to the repo tool. That's what will get your CM repos syncing:


Code:


mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo


and then, reboot to apply the changes.

Now for the interesting part
Not really, actually.

Time to yank the CM source code.

Create a working directory where you're going to sync all the sources and do the dirty stuff.
For this guide, we'll call the working directory "cm12"

Create the directory by running

Code:


mkdir cm12

enter your working directory by typing

Code:


cd cm12

Inititialize the repo by throwing in:


Code:


repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0

Wait for all the activity in the terminal to cease. And then type in:


Code:


repo sync

while the stuff is downloading, grab a ginger ale, or a cup of coffee and admire your handiwork. If you're the impatient type, find a generous dose of your favourite sedative, and knock yourself out for a few hours. When you're up again, you'll be faced with one of two things. Either your repos have synced successfully (yay!), or you get some nasty fetch errors. If it's the latter, then, Voila! You've just faced your first ever compiling frustration. Take some time out and break a few things, drive the neighbours crazy and then return to the PC and knock in:


Code:


repo sync -j1

This should (hopefully) work perfectly as long as you have an internet connection worth paying for. If not, then compiling probably isn't for you anyway.

Once all the repos have been synced, you need the device specific sh*t. To do that, run:


Code:


. build/envsetup.sh && breakfast falcon

It will create the falcon local manifest. Once all the stuff has been downloaded, and the terminal returns to normal, you still have one more modification to make. You need the proprietary stuffs.

Go to the working directory, and press ctrl+h this should reveal the secret land of the .repo folder.

Double click on the folder, and you will find more folders. Go to the one named local_manifests and you'll find something called "roomservice.xml" right click on it and open it with gedit.

There, right at the bottom, before the <manifest/> past this in:


Code:


  <project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" />

save the file and return to the terminal.

run another repo sync and then get the prebuilts by typing in:

Code:


repo sync
cd vendor/cm
./get-prebuilts


Then cd back to your working directory

Code:


cd ~/cm12

YOU'RE READY TO ROLL!

Finally, to build, type in:


Code:



. build/envsetup.sh && brunch falcon


If you have a really powerful PC, then use:


Code:


. build/envsetup.sh && brunch cm_falcon-userdebug -j8

And if you have a really really powerful PC, then use:

Code:


. build/envsetup.sh && brunch cm_falcon-userdebug -j16

Wait for the build to compile. Usually takes about 2-3 hours on an okay PC. You'll find your completed build in cm12/out/target/product/falcon.

The next time you want to build, run:


Code:


make clean
repo sync
. build/envsetup.sh
brunch falcon
.. and so on.


Happy Building!






CM12 for G900FD topic






Hi, looking int development thread i see there are 5+ different CM12 roms for 1sim version of S5. No much difference for now between all these roms. May be someone could do more inteeresting job and build CM12 for 2sim device ? No much difference in hardware, same CPU/RAM/etc, kernel sources are avialable for latest firmware version. As i know CM is available for other 2sim devices, so it's not impossible. Will appreciate any work in that direction and can be a tester (i think many people around agree to be a tester).

PS. Yes, i'm also developer and can that myself, but currently i'm busy with my primary work. It may be next year will get some time to do that. Or may be join other team if there will be some :).






CM12 - Just sharing - D850 - Nightlies topic






Disclaimer: I did not contribute or help with development of this build so don't thank me, don't donate to me, and don't ask questions concerning problems with the build/ROM. My builds are pure CM12 no cherry-picks and no flare. I literally run three commands in a window and out pops the build in 20 minutes so no hard work on my end. Mods is this a problem are not helpful delete this.

My builds
--->CM12 Builds here <---

Thanks,
SupaAvenger79






[ROM][KERNEL] CM12 Unofficial hammerhead with Gapps [ODEXed|Linaro] topic






This is my personal build of CM12 with the latest GApps (minimal). This unofficial ROM is odexed and compiled with Linaro 4.9.
I'm been using this as my daily driver and it's getting better each day as the base ROM (CM12) continues to grow and mature at a level
comparable to its earlier siblings (CM11, CM10, etc) . BTW if anybody deems it unwise for me to post this build with GApps, then I will
stop this thread immediately.

Disclaimer

Code:


Your warranty will be VOID after installing a custom ROM.
Get notified yourself that 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.


ROM Features:
  • Latest nightly build from CM12 source (Changelog)

  • Minimal GApps just sufficient for installing apps from the Play Store

  • MultiROM Support (Primary and Secondaries)

  • Fully odexed for battery saving during frequent upgrades (nightlies)

  • Compiled with Linaro 4.9 ("Performance")


Kernel Features:
  • Gamma Control/Color Display

  • FauxSound/Franco Sound

  • Kexec Patch for MultiROM

  • Fast Charging with USB

  • Voltage Control

  • Others will be added in the future as I see fit


Downloads:
Instructions: (Tested only with MultiROM TWRP)
  • For initial installation, backup and wipe data/cache/dalvik-cache

  • For nightly upgrades, simply wipe cache/dalvik-cache


Credits: