Hey everyone,
I got 4.1.1/JRO03C to compile for Toro no problem, I installed it on my phone, it boots, great. When I make some build.prop changes to change the fingerprint to mirror mysid instead of full_toro or what not, the system gets stuck in a boot loop. Is there something I need to do before compiling in order to make the build.prop work and have the ROM id itself as mysid? I want to do this for market purposes.
If anyone could shine some light on this, I'd appreciate it.
Thanks!
I haven't posted enough on XDA to be able to reply to the appropriate development forum post, so I decided to post here. I'm running CM10 on a Sprint Galaxy Nexus (toroplus), and I had been in need of a way to use NFC while the screen was locked, but couldn't find one for the latest build of CM10. I found this thread http://forum.xda-developers.com/showthread.php?t=1709586 but the latest updates only had one for screen off (which is a little less secure IMHO), and when I used it, I would have to turn NFC off and then back on almost every time I used it, which defeated the purpose. I also saw that someone else was having the same issue, so I decided to compile one myself using the latest CM10 source. This was built from source as of 10/31/2012 and has only been tested on the nightly build with the same date. I figured I'd share it with everyone that might be needing the same.
Disclaimers: This requires a rooted phone! This has only been tested on the Sprint Galaxy Nexus running CM10 nightly dated 10/31/2012, but may work with other versions. Do a backup! I'm not responsible for any problems resulting from these files, so backup first!
To install, copy to your SD card. Reboot into recovery. DO A BACKUP! Install the zip from the SD Card. Reboot.
There are two versions I created. One is for when the screen is on, but locked. The other is for when the screen is off.
Update 1/2/2013:
I compiled a version of the screen locked for CM10.1 (Android v4.2.1) for anyone who would like it. I was getting mixed results with the previous file on 10.1. This one is working on my toroplus with the latest CM10.1 nightly. I'll build a screen off version later. I was having some problems with my build VM, so I didn't get to it yet. The new file for CM10.1 is called NFC_Screen_Locked_CM10.1.zip.
Update 1/3/2013:
The CM10.1 version of the screen off version is now posted. File name is NFC_Screen_Off_CM10.1.zip
Update 1/16/2013:
Previous version of NFC_Screen_Off_CM10.1.zip was not working. Should be working now.
Update 1/16/2013:
Added a patch that can be used against CM10 or 10.1 source code to add an option to the settings to switch between screen on, locked, or off NFC. You must build the entire thing from scratch to use this patch. There are logs of guides for building CM. Here's a link to the CM wiki article for toroplus for example. Before executing brunch, copy this file to the root of where you created the repo (the article uses the ~/android/system/ folder for instance) then execute the following two commands:
Code:
tar -xzf nfc-patch.tar.gz
./apply-nfc-patch.sh
Or in the use package manager to untar all of the files (maintaining the directory structure) and then double click and run the apply-nfc-patch.sh file. This will patch all of the necessary files in the build. Then continue with the instructions in the build guide and flash the resulting ROM.
Disclaimer Again: This could break your phone. I'm not responsible for any damages this may cause. This has only been briefly tested on my toroplus with the latest CM10.1 code from the repository.
Credits: Rick C who originally submitted most of this to the CM repository but was rejected.
Update 1/21/2013:
Looks like a recent commit to the repository broke one of the diffs in the patch. Uploaded a new version.
Update 2/13/2013:
Another update to fix an issue with the patch files. I also added a reset script that will do a hard reset for git repos of the affected packages. Don't use this script if you have made any other customizations to the Settings app, NFC app or the frameworks/base code as you will lose them. Just do things in this order:
1) run reset script
2) run repo sync
3) extract tar again
4) run apply script
5) run brunch again
You can use this sequence every time you want to grab the latest code.
If you get errors when running the apply script you can use this command to delete the error files that come up. These files might show up even if the patch works, but the code wasn't exactly what the patch was expecting, but enough to apply anyway.
Code:
find . \( -name \*.orig -o -name \*.rej \) -delete
This set of commands should do the trick for most people to get the latest code, apply the patch and build:
Code:
./reset-nfc-patch-repos.sh
repo sync
tar -xzf nfc-patch.tar.gz
./apply-nfc-patch.sh
source build/envsetup.sh && brunch <your-device-name>
Update 2/27/2013:
Made some fixes to the notes in the previous update based on feedback from mrplowdan.
Update 3/15/2013:
Compiled a new version of the CM10.1 files for those having issues.
Update 10/21/2013:
Added a test version of the screen locked version for CM10.2 now that toroplus has an official CM10.2 nightly. Let me know if there are any issues. I'll add a screen off version when I have some time.
Update 11/19/2013:
Finally getting around to adding a screen off version for CM10.2. The screen locked version has been running well on my toroplus for the last month with no issues.
Has anyone tested this on Maguro?
Just recently got my phone back from service (after 10 weeks) so i'm not re-rooted yet, hence i can not try this on stock myself. Just wanted to give a big thanks to you for creating and developing this this is really a truly great way to make use of the nfc and the way it should have been done from the very beginning. I.ex if your out running, listening to music and for some reason need to pause your music, just swipe a previosly attached nfc-tag on your sleve over your pocket with the phone in. And again to start music. Awsome work, thank you!
Sent from my Galaxy Nexus using xda premium
It may work on Maguro as long as you're using a fairly recent version of CM10. If I knew anyone with a device, I'd test it myself. It's fairly low risk to test. It only replaces a single file. It's the Nfc.apk in the /system/app/ folder. You could always rename your existing file; install this one; and then reboot and test it out. Also, if you're wary of the zip itself, you can just extract the Nfc.apk and copy it to your /system/app/ folder manually, just don't forget to reboot. Then if it breaks you can just delete the new one and rename the old one back. You could also just backup everything; install the zip; and just restore the backup if anything breaks. Anyway if you decide to be adventurous, let us know how it goes. I'll keep this thread updated if CM makes any other changes that break it again. I use it often, so I'll likely find out pretty quickly. Hopefully, they'll add this as a setting in CM10 some day.
Sent from my Galaxy Nexus using xda app-developers app
could i use it on every rom cm based?
It depends on how many modifications were made by the mod around NFC, if any. Also depends on when the last time was that they merged their code with CM. In theory it should work with most CM based mods. You can always try it out as I mentioned above and revert if it breaks. And post here with your results if you try it, so others can benefit.
Sent from my Galaxy Nexus using xda app-developers app
Locked version tried and working maguro. I'm on latest Jellybro. Good work and thanks
Sent from my Galaxy Nexus using xda premium
CM10.1 Update
I compiled a version of the screen locked for CM10.1 (Android v4.2.1) for anyone who would like it. I was getting mixed results with the previous file on 10.1. This one is working on my toroplus with the latest CM10.1 nightly. I'll build a screen off version later. I was having some problems with my build VM, so I didn't get to it yet. The new file for CM10.1 is called NFC_Screen_Locked_CM10.1.zip.
irotsoma said:
I compiled a version of the screen locked for CM10.1 (Android v4.2.1) for anyone who would like it. I was getting mixed results with the previous file on 10.1. This one is working on my toroplus with the latest CM10.1 nightly. I'll build a screen off version later. I was having some problems with my build VM, so I didn't get to it yet. The new file for CM10.1 is called NFC_Screen_Locked_CM10.1.zip.
Click to expand...
Click to collapse
Great work! - many thanks from me!
I'm waiting so long for the Screen-Locked Version ...
Best regards
JoSch
can it be included in cm10.1?
I was just wondering, can't this be somehow merged with stock cm10.1? Add checkboxes in the settings.apk, lots of warnings when enabling it and people who know can use it.
nice work btw
Screen Off for CM10.1
The CM10.1 version of the screen off version is now posted. File name is NFC_Screen_Off_CM10.1.zip
cthulu said:
I was just wondering, can't this be somehow merged with stock cm10.1? Add checkboxes in the settings.apk, lots of warnings when enabling it and people who know can use it.
nice work btw
Click to expand...
Click to collapse
Yes, actually I've been wanting to do this for a while, but I never seem to have the time to dig into the settings UI and how to read that setting. If you or someone else would be willing to create the settings piece and tell me how to access the setting that you create, I'd be happy to alter the NFC service to look at those settings. Ideally there should be a preference with an integer value of 1 for screen off, 2 for screen on but locked, and 3 for screen on and unlocked (default) as that's the value that the service expects currently.
First of all i would like to thank you posting this, just what I was looking for.
Im running one of the latest cm10.1 nightlies (jan 1st or 2nd) and flashed the NFC_Screen_off_CM10.1zip however it doesn't work while the screen is off, though it does work when the screen is on and the phone is locked. I have a Galaxy Nexus (gsm).
When I logcat the phone I don't see NFC being discovered with the screen of but with the screen on and the phone locked I do see that it discovers an NFC event.
Is there anything that can be done about this?
Thanks!
dannyvanderzande said:
First of all i would like to thank you ting this, just what I was looking for.
Im running one of the latest cm10.1 nightlies (jan 1st or 2nd) and flashed the NFC_Screen_off_CM10.1zip however it doesn't work while the screen is off, though it does work when the screen is on and the phone is locked. I have a Galaxy Nexus (gsm).
When I logcat the phone I don't see NFC being discovered with the screen of but with the screen on and the phone locked I do see that it discovers an NFC event.
Is there anything that can be done about this?
Thanks!
Click to expand...
Click to collapse
That's odd. I didn't have an NFC tag handy when I built the screen off version, so I assumed the same changes I made in CM10 would work in 10.1 since the screen locked version worked. I'll test it on my device and see if I can figure it out as soon as I get some free time. Thanks for letting me know!
irotsoma said:
That's odd. I didn't have an NFC tag handy when I built the screen off version, so I assumed the same changes I made in CM10 would work in 10.1 since the screen locked version worked. I'll test it on my device and see if I can figure it out as soon as I get some free time. Thanks for letting me know!
Click to expand...
Click to collapse
I decided to check the files out myself to try and figure it out and maybe quick fix it myself (which would have saved you the time) by referencing to the 10.0 apk's however I found out they differ a lot more from eachother than I expected so it was a bit too much for my skillz. I found this out using a comparison tool and while I was at it I compared the 10.1 screen lock and 10.1 screen off versions. According to my program they are exactly identical in either file structure as in file contents so I'm guessing something must have gone wrong with renaming or I just don't know how to use the tool? I'm just mentioning this as something I came upon, not to ***** or anything! I really appreciate the work you did!
Anyway.. I had some fun figuring things out and learning about decoding apk's and all of that. Thanks for all the hard word so far and I'll just wait patiently upon the new screen-off version.
The screen off one works perfectly for the Toro running the last stable 4.1.2 liquid smooth rom. Awesome work, thanks a million!
Edit: I'm not sure if it makes a difference but I didn't flash it, I pulled the apk from the zip, copied and pasted and reset permissions then restarted.
Fixed CM10.1 Screen Off
irotsoma said:
That's odd. I didn't have an NFC tag handy when I built the screen off version, so I assumed the same changes I made in CM10 would work in 10.1 since the screen locked version worked. I'll test it on my device and see if I can figure it out as soon as I get some free time. Thanks for letting me know!
Click to expand...
Click to collapse
OK, so I uploaded a new version. I actually tested it this time and this one worked for me on my toroplus. Let me know if there are any other issues, but you should be good to go after flashing this one. Sorry it took so long to get around to it. Enjoy!
Settings Patch for CM Source Code
cthulu said:
I was just wondering, can't this be somehow merged with stock cm10.1? Add checkboxes in the settings.apk, lots of warnings when enabling it and people who know can use it.
nice work btw
Click to expand...
Click to collapse
I did a little digging and found that there was a patch submitted to CM10 to include a switch for this in the settings. However, it was rejected by Steve Kondik and abandoned. I took all of the code and merged it into the latest CM10.1 code and it seems to work. I added a patch to the main post, but you have to compile CM from scratch to use it since it touches some framework components. The good news is it should work on any device that CM supports (that uses the NFC.apk though not devices that use NfcNci.apk like the Nexus 4) and should work on both CM10 and 10.1 in most cases.
The patch is basically just a few diff files and a bash script to automate the patching. If anyone is feeling adventurous, feel free to experiment with it. I can't promise it will work for you, but it's fun to try and learn a bit about building CM source code in the process. Basic directions are in the original post. As always I take no responsibility for anything it might break, but I'll be happy to try to troubleshoot if I can. Enjoy!
Thanks for all your effort.
Unfortunately it doesn't work on the nexus 4 but after some googling I found a working version for the nexus 4 on the forums here on xda. Im guessing there's a difference in chips or something...
dannyvanderzande said:
Thanks for all your effort.
Unfortunately it doesn't work on the nexus 4 but after some googling I found a working version for the nexus 4 on the forums here on xda. Im guessing there's a difference in chips or something...
Click to expand...
Click to collapse
Thanks for pointing that out. I clarified the previous post a bit. I should have said it should work with any devices that use Nfc.apk. Newer devices that use NfcNci.apk will not work with the patch.
Continue thread from here http://forum.xda-developers.com/showthread.php?t=1835285
Please read that before you continue here
Reason for this new thread is that I have taken over from Llor to maintain
those builds now.
CM10 Issues thread
http://forum.xda-developers.com/showthread.php?t=1821783
BOOT IMAGE IS IN THE ZIP
So extract boot.img from the zip BEFORE flashing the ROM and
flash it using fastboot or AIO
This is HELLBOY 201212011716
If there are any kernel updates needed "asynchron" to the ROM updates
I will write this here. So DONT use a different kernel by default
Download:
http://goo.im/devs/maxwen/CM10-primou
Or use GooManager app (you need to have 20121111 build installed)
gapps 20121011
http://www.mediafire.com/?k2cb1trw8s2oio2
Konwn issues - only what I can reproduce:
-panorama mode artifacts
-Continious-AF in video mode dont work very well
------------------------------------------------------------------------------------------------------
ChangeLog 2012/12/08:
-removed camera animation - I am tiered of beeing asked about it
-added sys.keep_apps=com.android.mms,com.android.contacts by default
-fix for VOIP/SIP microphone mute
-updated to latest CM10 sources
------------------------------------------------------------------------------------------------------
ChangeLog 2012/11/28:
-fixed graphical glitch that happens sometimes - e.g. after booting
-added sys.keep_apps property support to keep apps in memory
this should hopefully solve the dreaded "loosing" mms problem.
But I would keep SMS Ghost installed for now just to make sure
To use it add a line to you build.props e.g.
Code:
sys.keep_apps=com.android.mms,com.android.contacts
or for a single app only
Code:
sys.keep_apps=com.android.mms
Requires reboot!
Please keep in mind that flashing a new version will overwrite those changes
so you have to do it again afterwards
-added hwui blacklist support http://review.cyanogenmod.org/#/c/19249/
see also here for more details http://forum.xda-developers.com/showthread.php?t=2014099
To enable add the following line to your build.props
Code:
hwui.use.blacklist=true
AND you must use kernel 201211242348
Requires reboot!
Please keep in mind that flashing a new version will overwrite those changes
so you have to do it again afterwards
There is a new app HwsSettings where you can easily specifiy for which
apps it should be done http://forum.xda-developers.com/showthread.php?t=1766576
-decreased screen turn on time
-updated to latest CM10 sources
------------------------------------------------------------------------------------------------------
ChangeLog 2012/11/22:
-swap script added by default - if you dont want it delete it
-fixed color effect for video recording
-fixed thumbnail creation for videos
-fixed custom button backlight handling - please keep in
mind that our HW is not really capable of doing button backlight
dimming levels so actually there is only off=0 and on!=0
-screen OFF CRT animation - dont ask for on animation
-updated to latest CM10 sources
EDIT: use HELLBOY 201211231230 if you experience screen flickering
during unlock
------------------------------------------------------------------------------------------------------
ChangeLog 2012/11/15:
-working zram (you need BOTH latest kernel AND latest ROM)
-(more) camera fixes
-updated to latest CM10 sources
Nice and first! Thanks for your work!
nice one maxwen. you pushed those patches for camera in? i didn't had the chance to try them..
deleted
I didn't have a software installed much, so I always full wiped and fresh install. All seem fine for me.
Btw, any threads from dev is best from their dev man kind. I love all threads here.
great job~! thank maxwen~
Now I'm on Llior's 4/11. Do I need to wipe data & everything before update to this 12/11/15 version? Or just simple update from cwm?
Bambalazs said:
What is the update method? Full wipe and flashing rom and gapps, or just flashing rom without wipe? Kernel is the latest hellboy, so I don't need to flash it.
Thank you.
Anyway this thread is better than the other one. :good:
Click to expand...
Click to collapse
There is only ONE warning!!!
Those kind of posts belong NOT in this thread but in the corresponding
CM10 thread in the General section
I am a little bit nicer then Lloir in this case and will just ignore them
But - If you stay ignorant this thread will be closed for your posts too
So you can decide
max
1ceb0x said:
nice one maxwen. you pushed those patches for camera in? i didn't had the chance to try them..
Click to expand...
Click to collapse
It includes all "know" patches plus the 2 gerrit commits I have
already told you- Those have not been merged at the moment so
you need to cherry-pick them for now
Sorry. It won't happen again.
The ROM is amazing. Everything works well.
Just one problem. (In Auto Brightness mode) When I go to Display - Automatic Backlight - Use Custom & Edit other levels. And when I change the Buttons values. Either to 0 or any other value. I see no change in the capacitive buttons.
Is it safe to restore data of cm9 backup using twrp? will it be fine? i dont wanna set my phone again to the way i like
harsh.ea said:
Is it safe to restore data of cm9 backup using twrp? will it be fine? i dont wanna set my phone again to the way i like
Click to expand...
Click to collapse
never tried so you will be on your own trying
Sent from my One V using xda app-developers app
maxwen said:
never tried so you will be on your own trying
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Did it when moving from stock to myONEv. Worked fine then
GamingFreak said:
The ROM is amazing. Everything works well.
Just one problem. (In Auto Brightness mode) When I go to Display - Automatic Backlight - Use Custom & Edit other levels. And when I change the Buttons values. Either to 0 or any other value. I see no change in the capacitive buttons.
Click to expand...
Click to collapse
never played with those TBH
will have a look
Sent from my One V using xda app-developers app
Ohk. Never mind that. Otherwise the ROM is amazing.
there seem to be some problem. Home button not working and recent app switcher not working too. I changed it properly from HARDWARE KEYS
harsh.ea said:
there seem to be some problem. Home button not working and recent app switcher not working too. I changed it properly from HARDWARE KEYS
Click to expand...
Click to collapse
Post the issue along with the logcat on CM10 issue thread. This is dev only.
GamingFreak said:
The ROM is amazing. Everything works well.
Just one problem. (In Auto Brightness mode) When I go to Display - Automatic Backlight - Use Custom & Edit other levels. And when I change the Buttons values. Either to 0 or any other value. I see no change in the capacitive buttons.
Click to expand...
Click to collapse
Ok just checked:
Well there is a bug
Its always using the screen brightness value instead of the
button brightness value. Need to check if I can fix this
No lock screen animation
Sent from my One V using xda app-developers app
Yes, I configured my ROMs kernel (current one)... But I Don't want to wipe out the changes I made. I want to install a new ROM, which of course will install a completely new kernel.
So... What I did to my kernel:
Through Ubuntu Terminal ADB, I got the /proc/config.gz and edited my kernel to optimize it for my external USB adapter. (My phone: Galaxy s4 i9505, my ROM: CyanogenMod 10.1 stable)
Here's the ROM I want to install:
http://wccftech.com/update-galaxy-s4-i9505-to-android-4-4/
So if anyone could reply if they know how to do kernel building and configuring and could help me, it would be VERY MUCH appreciated In fact, I might donate!
Try trickster MOD kernel settings from the play store. Use the donate 1 to unlock the ability to save your kernel preferences. Just be sure to have the kernel you are running now in a zip file so you can flash it after your new ROM and then restore your settings through trickster mod. Good luck!!
Sent from my SGH-M919 using xda app-developers app
Hi,
I've successfully rooted my UK galaxy tab pro 12.2 SM-T900 (using a P900 img as the T900 one bricked it), I'd like to try running linux via chroot but I think I need a custom kernel to set SELinux to permissive.
Since there don't seem to be any in existence I think I need to build one from source as described here (I can't post links):
graemehill.ca/compiling-permissive-android-kernel/
The build # on my device is T900XXUANI1
however on the Samsung open source site this particular version is not listed.
opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=T900
I'm not sure if they're supposed to be the same thing - Should these versions match? Will I break something if I download the source for T900XXUANB5 and compile that or is that the right version to download?
Thanks
RealZogger said:
Hi,
I've successfully rooted my UK galaxy tab pro 12.2 SM-T900 (using a P900 img as the T900 one bricked it), I'd like to try running linux via chroot but I think I need a custom kernel to set SELinux to permissive.
Since there don't seem to be any in existence I think I need to build one from source as described here (I can't post links):
graemehill.ca/compiling-permissive-android-kernel/
The build # on my device is T900XXUANI1
however on the Samsung open source site this particular version is not listed.
opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=T900
I'm not sure if they're supposed to be the same thing - Should these versions match? Will I break something if I download the source for T900XXUANB5 and compile that or is that the right version to download?
Thanks
Click to expand...
Click to collapse
You can use bonuzzz's Custom PRO-VTFB. But if you really want to create your own, you can use the B5 kernel. However, that kernel has been followed by two firmware upgrades.
Thanks, so there's no problem using the p900 kernel on the t900? It's not something I've ever done before and I don't really know how much difference there is between various kernels
RealZogger said:
Thanks, so there's no problem using the p900 kernel on the t900? It's not something I've ever done before and I don't really know how much difference there is between various kernels
Click to expand...
Click to collapse
You might loose the automatic screen rotation, but that's the only difference. I use it as an alternative to cm-11, together with bonuzzz's Custom ROM 1.01 the most debloated TW ROM available. There is also a cm-11 kernel with enabled VT, but same thing here you will most likely loose the auto rotation.
If anyone is interested, i sent a request to samsung via their open source website on the day I posted this thread, asking for the XXUANI1 source. Got an email back today to say it's now available on the website. I haven't tried doing anything with it yet though!