-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------Build from source------------------------
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.
Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip
----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.
Good job.
Sent from my Nexus 7 using Tapatalk 4
hello
anyone tried this out ?
feedbacks ?
thanks in advance
pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium
Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!
So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app
I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!
It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.
Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Are you going to try to make CM 10.2?
LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.
LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.
Related
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.
CM 10.1.0 RC2 code base has been released and here it is for your flashing pleasure!
DISCLAIMER:
I am new to android development so more of a builder than a developer at the moment. So please do BACK UP your phone before you get started. If you know how to fix an issue in the ROM then feedback is more than appreciated. Bug reports are welcome, however please understand that I probably won't be able to figure out the solution without help. You can expect that CM code updates will be rolled into this ROM as these come out though.
For those of you looking for Skype audio this ROM does not yet fix it BUT I have tried the tinyalsa_audio stuff from Adam77Root and that does get Skype working just fine, but then it messes up your phone audio to where you don't hear anything or send anything out about 3/4 of the time. So we're getting close but not quite there yet... Oh and bluetooth calling was not fixed when skype worked, so there's something else wrong there...
RC1 was accidentally released with the tinyalsa_audio driver.. So this is RC2 with the "correct" libaudio which means skype is broken but calls work...
Using CWM:
1) BACK UP your current ROM!!!
2) Preform wipe / factory reset
3) Flash the ROM: cm-10.1-RC2-20130530-UNOFFICIAL-i927.zip (MD5 = 2e65e45bdc7539d5260062abdf6cd1cd) Mirror 1
4) Optionally flash GAPPS: gapps-jb-20130427-nonneon-tonyp.zip (MD5 = 13fc57e24ead77ec2613efd643af3800)
Stuff that I've noticed that looks to be fixed / has changed since M3:
- Moved over to KickAss kernel and battery life now totally rocks!
- Picture editing in the gallery is also working fine now.
- HDR photo capture looks to be working just fine also...
- Lock screen lag much less noticeable, but I do sometimes need to press the button twice...
Known issues without workarounds:
- Audio in skype is there but plays back at wrong rate (slower than normal, woman's voice sounds like a man's)
- I was not able to get my two bluetooth headsets working but bluetooth GPS works fine
Known issues with workarounds:
- GPS works great and fast but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
- Pictures taken by camera are shown rotated 90 degrees (then can be manually rotated within the gallery app)
Please don't report any of the above known issues. General CM 10.1 bug tracking thread <- Please check here before posting a bug report!
I'm sure there are others but I've not noticed them yet. I don't use a hands free but I can confirm the bluetooth does work with an external GPS for instance.
Change log:
20130530 - Corrected call audio issue and CM 10.1.0 RC2 code base
20130525 - Moved to KickAss kernel and CM 10.1.0 RC1 code base
20130503 - Fixed gallery pic editing, update OTA image
20130502 - Combined LiteKernel built 20130418, broke the gallery pic editing, added OTA support
20130417 - Combined LiteKernel built 20130414 into the ROM, no need to flash kernel seperately
20130416 - New LiteKernel build by bubor
20130415 - WiFi fix by bubor applied
20130412 - M3 code release, still using LiteKernel from 20130222
20130405 - Rolled back non-monthly code updates to revert this back to the original M2 code release. Corrected build environment to generate proper boot.img, No longer using the one from the LiteKernel which means that the LiteKernelManager is not messing around with settings now.
20130404 - Used the 2013/02/23 branch of the device tree and also re-synced with the CyanogenMod source. SD card mappings now match the CM10.1 later builds so recommend wiping and re-installing fresh for this one,
20130402 - Build LiteKernel into the ROM so no need to flash the kernel separately
Credits:
- KickButtowski for the kick ass KickAss kernel
- tonyp for the non-neon GAPPS package
- bubor: WiFi tether fix and new kernel that fixed data usage, image editing in galley and google now hotword detection as well as new GAPPS
- Adam77Root for the libaudio code that fixed the camera audio in video recordings
- yohan4ws for pointing me towards Adam77Root's libaudio stuff
- gtmaster303: CM 10.1 bug tracking thread maintenance
- The-Covenant team: For the device tree and vendor proprietary files
- dman3285: For the tutorial on building CM10 and CM10.1 from source, and all your work getting this setup
- thegreatergood: For the LiteKernel source and binary
If I've missed anyone apologies in advance and just let me know and credit will be added...
And here is the ling to my device tree should anyone want to follow along. Seperate branch available for the tinyalsa_audio for the more adventurous ones.
Reserved...
sweeeet!
wow, another rom i will try it tomorrow, juts 1 question, if i flash lite kernel the wifi will work? and how about ohter mods or skype?
I am gonna try it tomorrow, thanks thanks
Awesome, thanks!
Can you please list the non working things you have already discovered?
lorddavid said:
wow, another rom i will try it tomorrow, juts 1 question, if i flash lite kernel the wifi will work? and how about ohter mods or skype?
I am gonna try it tomorrow, thanks thanks
Click to expand...
Click to collapse
Correct - If you flash the LiteKernel on top of the ROM then the WiFi will work.
braintweaker said:
Awesome, thanks!
Can you please list the non working things you have already discovered?
Click to expand...
Click to collapse
Done...
This is pretty much just a new build with all the upstream commits, correct?
I suggest everyone review my bug tracker thread before posting bugs, as these builds are one in the same rom...
http://forum.xda-developers.com/showthread.php?p=38339702
gtmaster303 said:
This is pretty much just a new build with all the upstream commits, correct?
I suggest everyone review my bug tracker thread before posting bugs, as these builds are one in the same rom...
Click to expand...
Click to collapse
Agreed.
This build is based on:
- CM 10.1 M2 release code base (released 4 Mar 2013 so the Feb ROMs are based off the M1 release)
- The-Covenant device tree and proprietary files which I assume have not been touched since end of Feb
- thegreatergood's LiteKernel binary which is the same as the other ROMs
So any issues that were related to the kernel or device specific stuff will still be there, but CM based issues may have been resolved. Case in point the audio playback lag is now fixed on my phone.
YMMV of course!
I am doing right now a backup of my current rom. I really want to see if skype and magic jack works now. I will post back in some hours.
Is bluetooth handsfree fixed in this build?
Re: [DEV][ROM][JB 4.2.2][Unofficial] CM10.1-M2 3/31/2013
One question. Do i need to flash the keyboard fix? and the rom is compatiblr with the mod to put external sd as internal? i try to flash but never boot. I will try again in a few moment
Sent from my SGH-I927 using xda app-developers app
jzamoras said:
Is bluetooth handsfree fixed in this build?
Click to expand...
Click to collapse
In my test both headsets connected fine but one gave no sound and the other gave me only static. Not sure if the mic was working on either one. I don't usually use bluetooth so can't say for sure but I think this is still an issue on this build at this time unfortunately.
lorddavid said:
One question. Do i need to flash the keyboard fix? and the rom is compatiblr with the mod to put external sd as internal? i try to flash but never boot. I will try again in a few moment
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
You won't "need" to but the crashing keyboard gets annoying fast. So installation of a keyboard from the play store (I used the hacker's keyboard) is a must to make this usable. now if there is a "fix" available for the stock keyboard on the JB builds then let me know what it is and I'll see about adding it to the ROM by default.
As for the memory cards, the internal is mounted as /mnt/emmc and the external is mounted as /mnt/sdcard. Not sure if that answers your question...
spyke555 said:
In my test both headsets connected fine but one gave no sound and the other gave me only static. Not sure if the mic was working on either one. I don't usually use bluetooth so can't say for sure but I think this is still an issue on this build at this time unfortunately.
Click to expand...
Click to collapse
Is the same I got using AOKP. I guess I'll wait then.
spyke555 said:
You won't "need" to but the crashing keyboard gets annoying fast. So installation of a keyboard from the play store (I used the hacker's keyboard) is a must to make this usable. now if there is a "fix" available for the stock keyboard on the JB builds then let me know what it is and I'll see about adding it to the ROM by default.
As for the memory cards, the internal is mounted as /mnt/emmc and the external is mounted as /mnt/sdcard. Not sure if that answers your question...
Click to expand...
Click to collapse
I was talking about these patches http://forum.xda-developers.com/showthread.php?t=2067954
there is a patch for swap the external sd with the internal, and another for the keys in the keyboard.
Edit: i think that the keyboard patch no needed. But the Patch to swap the the external SD as internal, doesnt work. The rom never boot when i install it.
Another thing, its me, or the wifi is very very slow? i am downloading skype from the market and is taking so much.
Sorry if i wrote something bad :/
Just corrected the link to the LiteKernel, you may want to download this new link and re-apply to make sure you have the latest kernel installed. Trying to get this built into the ROM to avoid any further confusion...
Ok, i will try it again, but the skype/magicjack audio issue still exist
Just posted a new ROM build that now has the LiteKernel-20130222 built in. No need to flash separately. CM code is the same so no change there. If you already downloaded the 20130331 version and installed to 20130222 kernel then no need to re-download.
CM10.1-M3 release should be coming out shortly so do expect another update soon...
spyke555 said:
Just posted a new ROM build that now has the LiteKernel-20130222 built in. No need to flash separately. CM code is the same so no change there. If you already downloaded the 20130331 version and installed to 20130222 kernel then no need to re-download.
CM10.1-M3 release should be coming out shortly so do expect another update soon...
Click to expand...
Click to collapse
I'll jump as soon bluetooth thing is fixed
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
tdmcode said:
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
Click to expand...
Click to collapse
Working on bringing this up for the vs920 as that's the only one I've got.
So far I've copied the ijb_skt bits over to ijb_vzw and used a bit of grep/sed magic to replace the skt bits to vzw in the files, and add ||'s for ijb_vzw wherever ijb_skt was a condition. I'm getting successful builds But they won't boot (yet). I'll keep you updated. I'll be pushing to here as I make any changes/progress.
Got past the RPM error with a hack.
In arch/arm/mach-msm/clock.c @ clock_late_init(), remove the list_for_each_entry_safe block.
Obviously, this is just a hack. We need to figure out what's causing the issue.
Next up is the display. The kgsl driver in this kernel does not match the kgsl libs in CM10. I'm going to download the 4.1 flashable rom from this forum and see if I can update the drivers to match.
I think kgsl is happy now. Next up is the msm video driver.
tdmcode said:
I think kgsl is happy now. Next up is the msm video driver.
Click to expand...
Click to collapse
Man, You're a machine... Here I'm still trying to get something that'll boot past the LG logo lol
Got boot animation and home screen. Then it reboots after a minute or so. The shell in adb gets really laggy right before reboot. Likely causes are a kernel hardware driver failing somewhere or a massive memory leak.
I see touch events logged but by the time the home screen shows I think it's too far gone to act on them. Same with hard buttons and capacitive buttons.
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
tdmcode said:
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
Click to expand...
Click to collapse
Nevermind. I thought the link I just posted was for someone working on another 3.4 kernel... it wasnt.
*Edit*
I'm obviously doing something horribly wrong by trying to borrow/reuse the ijb_skt files, because I can't get a kernel that even tries to boot (gets off the first LG logo)... and don't really have the know-how to reconstruct the files.
Didn't get a chance to work on this today I was busy on another project. But I'll be back on it Monday for sure.
@Yoinx: you are going to have a harder time with the vs920 because the hardware is different and it won't boot the su640 kernel.
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
You need to change the kgsl and msm video code to match cm10. See my patch.
tdmcode said:
You need to change the kgsl and msm video code to match cm10. See my patch.
Click to expand...
Click to collapse
The boot.img provided by @navik
Same approach, i.e. stock zImage + cm10 ramdisk
I can boot into home screen with my su640 now.
Signal, wifi work.
but laggy, blinking screen(check hw overlay setting in option can fix), no sound, no bootanimation (black screen)
----------------------------------------------------
edit:
Merged your patch
able to see boot animation
Sent from my LG-LU6200 using xda premium
LU6200 jb source is released
https://wws.lg.com/global/support/opensource/opensourceList?types=ALL&search=lu6200
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
miroslav_mm said:
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
Click to expand...
Click to collapse
is your 3.4 kernel compatible with your previous cm10 builds? a lot less MBs, easier to upload.
tdmcode said:
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Click to expand...
Click to collapse
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
navik said:
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
Click to expand...
Click to collapse
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
tdmcode said:
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
Click to expand...
Click to collapse
Thanks，but I want to build aosp based on LG open sourse instead of porting.
Do you have read the guide of LG offical open sourse？It say we can build stockrom based on LG official open sourse and Google android open sourse，we just need to copy LG open sourse into android open sourse. then breakfast and lunch.but I fail，I think I didn't pick up the guide of LG open sourse 。Do you have some good advices？Thanks again！
Sent from my LG-SU640 using xda premium
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: http://d-h.st/aKr
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Sources:
Device: https://github.com/awid777/android_device_acer_a100 (cm10.2 branch)
Note for the sources: This isn't the source I used to compile the initial build. However, they are almost identical. The credits for the sources for the ROM go to @pio-masaki for his device and commons trees and prebuilt kernel. I would post the sources I used but I never uploaded them because I ended up deleting them early on as I prefer to use a single device tree. All my commits will now be posted to the listed source.
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: Pending upload.
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
po8pimp said:
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
Click to expand...
Click to collapse
This is not a port, thus doesn't need modification. It is compiled (built) from source and the work that needs to be done is in the source code so it can be compiled properly and work without modification
http://wiki.cyanogenmod.org/w/Development
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: [url]http://d-h.st/aKr[/url]
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
Thanks for the link and quick response, will take a look through some of that stuff and see if there is anything I can do to help. Also I noticed while I was typing the first one you put up a download... Did you get it to boot. I downloaded and tried using TWRP and was unsuccessful. I tried a couple times to make sure it copied over from the computer correctly. Still the same result.
4.4 updates different. Latest cwn will flash it. Maybe there's an easy way to do this
Sent from my SPH-L710 using XDA Premium 4 mobile app
Ok so I am stuck right now. I spent a couple hours building an environment and started compiling from source. I am stuck at this point:
$ source build/envsetup.sh
$ breakfast a700
Where a700 is, should be a100. I get errors when doing this because CyanogenMod does not have the device in it's file system. Whoever has successfully done this, please advise. I am over half way with this and would like to complete the build. I have about 20gbs of data sitting on my cpu waiting to compile this so the sooner we can find the solution the better. Thanks in advance.
Need help solving this to move further... There might be a work around, however I have never done this and I am stuck.
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
awidawad said:
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Sounds good. I spent a good part of 3 hours compiling a master build of Kitkat which was complete prior to me leaving for work this morning, however my daughter kicked the power strip under the desk and shut everything down. I will try and find a little time tonight to recompile.
Am I missing something?
Sent from my SPH-L710 using XDA Premium 4 mobile app
TWRP Version?
Is this TWRP new enough for your needs if not what is the newest version you are aware of
a100 TWRP 2.6.1.0 windows installer: as far as I can tell the Twrp image is based of linuxsociety's/GodMachine's work I know for sure the installer is his
http://d-h.st/Rfm
I have flashed this and all seems to work well
I also took the 2.6.1.0 from the above linked installer and put it into a flashable.zip that originaly contained GM's 2.2.2.1 TWRP
I updated the script to show the proper version as well attatched below
AngryManMLS Is responsible for both 2.6.1.0 and 2.6.3.0, "if I am not mistaken"?
His windows/Linux installers can be found here: http://www.androidfilehost.com/?a=show&w=files&flid=9577
and Here:http://forum.xda-developers.com/showpost.php?p=47555451&postcount=109 For 2.6.3.0
I also invited AngryManMLS to build the TWRP needed for this project So We'll have to wait and see if he can help "Break US OFF A PEICE OF SOME KIT-KAT---- Iconia???!!!!!!"
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
AngryManMLS said:
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
Click to expand...
Click to collapse
My Bad I shouldn't have assumed do you know who is doing the compiling?
I'm going to go ahead and compile TWRP. I've educated myself on the a100 (I've never done programming on this device or any other Tegra based device... Used to Qualcomm and HTC) hopefully it will work. Current TWRP branch on GitHub is twrp2.7 and has all KitKat changes in it. I'll have a build tomorrow morning. Tonight I have to finish my essays and other homework. I'll let you all know if recovery boots or not. If it does boot, I'll go ahead and attempt installing and booting KitKat
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
josegalre said:
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
Click to expand...
Click to collapse
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
awidawad said:
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
Click to expand...
Click to collapse
hardslog said:
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
Click to expand...
Click to collapse
thank you! I have to have fun these days!
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
awidawad said:
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Try compiling cwm then.
Sent from my SPH-L710 using XDA Premium 4 mobile app
I'm uploading a build of CyanogenMod 12 for the t0lteatt I've built. This build is still very alpha, so not everything will work as expected, but much of the basic functionality is there and this may be capable of being a daily driver for those who have to live on the bleeding edge. I'm not sure how long I'll work on keeping the build updated, but it looks like I'll be working on it for now. Hope y'all like it.
Known Issues:
Battery life may be shorter than normal (Turning off Adaptive Brightness will greatly help with battery life)
Netflix and other DRM protected apps do not work.
Media sharing services, such as Snapchat, may not work or may have issues.
Twitch may not work.
Bluetooth can be sorta glitchy.
And much, much more (As stated, this build is very alpha, so issues can be expected)
Instructions:
Download ROM here: https://www.androidfilehost.com/?w=files&flid=22696
Download GAPPS here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Reboot into recovery
Full wipe: Wipe cache, dalvik, wipe data/factory reset, clean to install a new rom, format system.
Flash ROM downloaded above.
Flash GAPPS downloaded above.
Reboot into system.
Let the system rest for a bit and settle in. (It seems the system can be a bit temperamental if you try to use it too soon... At times.)
If things don't work after letting the ROM settle, you may need to reboot a couple of times for everything to work properly.
Enjoy the lollipop goodness!
I would like to give thanks to the following:
sbrissen, DerTuefel1980 and all other contributors (I know I'm missing a lot, but they're the only ones I can think of right off hand, so I appologize to anyone who deserves mentioning for not mentioning y'all by name, and swear yall have my deepest respect) for their contributions to developing and maintaining the t0lte and related device trees that eventually allowed lollipop to be built for our device.
Ivan_Meler for the original camera fix http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
mr.nth.na.vn for his work-around to get sbrissen's i605 build to work correctly on t0lte.
Voyebanm for his posts and links which helped me to find the answers I needed.
fkfmfz for his gps fix that I have baked into the ROM and miji2 for cleaning up the fix.
And all the developers, maintainers and contributors of CyanogenMod in their pursuit of advancing and freeing all our android based devices.
If you would like to read more about the development of CyanogenMod, you can find extra information at the following links.
CyanogenMod: http://www.cyanogenmod.org/
CyanogenMod Wiki: http://wiki.cyanogenmod.org/
CyanogenMod Source: https://github.com/CyanogenMod
CyanogenMod Code Review: http://review.cyanogenmod.org/
Other threads on XDA I found useful:
CM12 for T0LTE by Voyebanm: http://forum.xda-developers.com/galaxy-note-2-att/development/cm12-t0lte-t2967836
[Rom] [alpha] [Unofficial] CM12.0, malir3p2 [20141214] by DerTuefel1980: http://forum.xda-developers.com/gal...rom-cyanogenmod-12-0-malir3p2-build1-t2958358
[12/12]{CM12-Unofficial} T0lte-Everything Almost Work+Incall by mr.nth.na.vn: http://forum.xda-developers.com/gal...05/rom-10-12-14-cm12-unofficial-data-t2969067
[ROM][I605]Cyanogenmod 12.0 [12/12/14] by sbrissen: http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
Have a good one!
AzraelsKiss said:
I'm uploading a build of CyanogenMod 12 for the t0lteatt I've built. This build is still very alpha, so not everything will work as expected, but much of the basic functionality is there and this may be capable of being a daily driver for those to have to live on the bleeding edge. I'm not sure if I'll work on keeping the build updated, but it's always a possibility. Hope y'all like it.
Known Issues:
GPS may not work (GPS Test does not see any satellites, but navigation still seems to work, so I don't know)
Battery life may be shorter than normal
Camera issues (see below)
And much, much more (As stated, this build is very alpha, so issues can be expected)
Instructions:
Download ROM here: https://www.androidfilehost.com/?fid=95857557620392172
Download GAPPS here: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Reboot into recovery
Full wipe: Wipe cache, dalvik, wipe data/factory reset, clean to install a new rom, format system.
Flash ROM downloaded above.
Flash GAPPS downloaded above.
Reboot into system.
Skip initial setup.
Go to Settings > Language & input > Current Keyboard.
Check on "Hardware".
Setup Wifi, APN, Google account, etc in Settings.
If you have problems with camera (no back camera/Can't connect to camera):
Download Google Camera from the Play Store.
Download Terminal Emulator (Terminal Emulator for Android) from the Play Store.
Open Terminal Emulator
Type: su
Press Enter
Type: sh etc/init.d/80cfw
Camera may now work (Sometimes, the camera may, again, not connect, but should start working again after a reboot)
Enjoy the lollipop goodness!
I would like to give thanks to the following:
sbrissen, DerTuefel1980 and all other contributors (I know I'm missing a lot, but they're the only ones I can think of right off hand, so I appologize to anyone who deserves mentioning for not mentioning y'all by name, and swear yall have my deepest respect) for their contributions to developing and maintaining the t0lte and related device trees that eventually allowed lollipop to be built for our device.
Ivan_Meler for the camera fix http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
mr.nth.na.vn for his work-around to get sbrissen's i605 build to work correctly on t0lte.
Voyebanm for his posts and links which helped me to find the answers I needed.
And all the developers, maintainers and contributors of CyanogenMod in their pursuit of advancing and freeing all our android based devices.
If you would like to read more about the development of CyanogenMod, you can find extra information at the following links.
CyanogenMod: http://www.cyanogenmod.org/
CyanogenMod Wiki: http://wiki.cyanogenmod.org/
CyanogenMod Source: https://github.com/CyanogenMod
CyanogenMod Code Review: http://review.cyanogenmod.org/
Other threads on XDA I found useful:
CM12 for T0LTE by Voyebanm: http://forum.xda-developers.com/galaxy-note-2-att/development/cm12-t0lte-t2967836
[Rom] [alpha] [Unofficial] CM12.0, malir3p2 [20141214] by DerTuefel1980: http://forum.xda-developers.com/gal...rom-cyanogenmod-12-0-malir3p2-build1-t2958358
[12/12]{CM12-Unofficial} T0lte-Everything Almost Work+Incall by mr.nth.na.vn: http://forum.xda-developers.com/gal...05/rom-10-12-14-cm12-unofficial-data-t2969067
[ROM][I605]Cyanogenmod 12.0 [12/12/14] by sbrissen: http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
Have a good one!
Click to expand...
Click to collapse
Thanks for the hard work! I got navigation but no gps lock but not an issue, camera fix worked for me. The only issue I had was no screen rotation. I flashed a sensor fix and all is good. Here is the link for the sensor fix: https://mega.co.nz/#!1xkSxTDJ!o8DQkNT6UvjNoxfgoxjNq2UnZz_6bO3ivYwMmvRv7dc
I am using this as my daily driver and I am grateful for everyone's time and hard work for giving our phones new life!
Shrek77 said:
Thanks for the hard work! I got navigation but no gps lock but not an issue, camera fix worked for me. The only issue I had was no screen rotation. I flashed a sensor fix and all is good. Here is the link for the sensor fix: https://mega.co.nz/#!1xkSxTDJ!o8DQkNT6UvjNoxfgoxjNq2UnZz_6bO3ivYwMmvRv7dc
I am using this as my daily driver and I am grateful for everyone's time and hard work for giving our phones new life!
Click to expand...
Click to collapse
Thanks for posting the sensor fix. I had forgot all about someone mentioning flashing it to fix proximity sensor issues as well. I don't seem to have the sensor issues myself, so it just slipped my mind. I'm glad ya liked the build. Have a good one!
This is fantastic! Did you port this from the N7100? Was it difficult? Anyone else noticing any major issues?
greddy91 said:
This is fantastic! Did you port this from the N7100? Was it difficult? Anyone else noticing any major issues?
Click to expand...
Click to collapse
This is built from CyanogenMod source with a couple of cherry picks of commits by sbrissen in code review. Many, many other, much more intelligent than me, people worked their arses off to get the t0lte and related device trees brought up for lollipop. All I did was build it with the t0lteatt specific information already coded for CM-11.0. Glad you're enjoying the ROM.
Have a good one!
everything works perfectly
AzraelsKiss said:
I'm uploading a build of CyanogenMod 12 for the t0lteatt I've built. This build is still very alpha, so not everything will work as expected, but much of the basic functionality is there and this may be capable of being a daily driver for those to have to live on the bleeding edge. I'm not sure if I'll work on keeping the build updated, but it's always a possibility. Hope y'all like it.
Known Issues:
GPS may not work (GPS Test does not see any satellites, but navigation still seems to work, so I don't know)
Battery life may be shorter than normal
Camera issues (see below)
And much, much more (As stated, this build is very alpha, so issues can be expected)
Instructions:
Download ROM here: https://www.androidfilehost.com/?fid=95857557620392172
Download GAPPS here: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Reboot into recovery
Full wipe: Wipe cache, dalvik, wipe data/factory reset, clean to install a new rom, format system.
Flash ROM downloaded above.
Flash GAPPS downloaded above.
Reboot into system.
Skip initial setup.
Go to Settings > Language & input > Current Keyboard.
Check on "Hardware".
Setup Wifi, APN, Google account, etc in Settings.
If you have problems with camera (no back camera/Can't connect to camera):
Download Google Camera from the Play Store.
Download Terminal Emulator (Terminal Emulator for Android) from the Play Store.
Open Terminal Emulator
Type: su
Press Enter
Type: sh etc/init.d/80cfw
Camera may now work (Sometimes, the camera may, again, not connect, but should start working again after a reboot)
Enjoy the lollipop goodness!
I would like to give thanks to the following:
sbrissen, DerTuefel1980 and all other contributors (I know I'm missing a lot, but they're the only ones I can think of right off hand, so I appologize to anyone who deserves mentioning for not mentioning y'all by name, and swear yall have my deepest respect) for their contributions to developing and maintaining the t0lte and related device trees that eventually allowed lollipop to be built for our device.
Ivan_Meler for the camera fix http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
mr.nth.na.vn for his work-around to get sbrissen's i605 build to work correctly on t0lte.
Voyebanm for his posts and links which helped me to find the answers I needed.
And all the developers, maintainers and contributors of CyanogenMod in their pursuit of advancing and freeing all our android based devices.
If you would like to read more about the development of CyanogenMod, you can find extra information at the following links.
CyanogenMod: http://www.cyanogenmod.org/
CyanogenMod Wiki: http://wiki.cyanogenmod.org/
CyanogenMod Source: https://github.com/CyanogenMod
CyanogenMod Code Review: http://review.cyanogenmod.org/
Other threads on XDA I found useful:
CM12 for T0LTE by Voyebanm: http://forum.xda-developers.com/galaxy-note-2-att/development/cm12-t0lte-t2967836
[Rom] [alpha] [Unofficial] CM12.0, malir3p2 [20141214] by DerTuefel1980: http://forum.xda-developers.com/gal...rom-cyanogenmod-12-0-malir3p2-build1-t2958358
[12/12]{CM12-Unofficial} T0lte-Everything Almost Work+Incall by mr.nth.na.vn: http://forum.xda-developers.com/gal...05/rom-10-12-14-cm12-unofficial-data-t2969067
[ROM][I605]Cyanogenmod 12.0 [12/12/14] by sbrissen: http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
Have a good one!
Click to expand...
Click to collapse
Everything works perfect , just one little bug ... My contacts from google dont displey when someone calls nor are the showing up in messaging app. Any ideas
And the camrea is working front and back
Tried to get the camera to work sadly I couldn't. Other than that and some graphical glitches on chrome beta(which is probably just not completely ready for lollipop) everything is running great.
I tried to install this an it gets stuck in bootloop.
try ...
mtech5 said:
I tried to install this an it gets stuck in bootloop.
Click to expand...
Click to collapse
Try installing CM 11 First and going through the set up then boot into recovery and install cm12 have fun
Hit thanks if it helped
Joshua Mr PC Repair said:
Try installing CM 11 First and going through the set up then boot into recovery and install cm12 have fun
Hit thanks if it helped
Click to expand...
Click to collapse
What I ended up doing was I was able to boot the rom for the 7105 so I installed it then dirty flashed this one over it. Runs like a charm.
mtech5 said:
What I ended up doing was I was able to boot the rom for the 7105 so I installed it then dirty flashed this one over it. Runs like a charm.
Click to expand...
Click to collapse
Look for the Lolipop shift kernel and install it , it fixes fron and rear camrea
After I did the dirty flash the camera works without doing anything extra.
Got a quick question for you guys. I have flashed this on my note 2 and have an unofficial CM12 I am working on flashed on my Note 4.
I however cannot figure out why Netflix will not work on either build. It is not a lollipop issue, because it works on my tablet, it seems to be an issue on CM12 only.
Would love to know if you guys have a solution, or know what might be missing from the build, so I can bring it back over to the CM12 note 4 thread. Thanks!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
ShrekOpher said:
Got a quick question for you guys. I have flashed this on my note 2 and have an unofficial CM12 I am working on flashed on my Note 4.
I however cannot figure out why Netflix will not work on either build. It is not a lollipop issue, because it works on my tablet, it seems to be an issue on CM12 only.
Would love to know if you guys have a solution, or know what might be missing from the build, so I can bring it back over to the CM12 note 4 thread. Thanks!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Netflix just updated , try it again , i just updated mine and seems to be working ,
Joshua Mr PC Repair said:
Netflix just updated , try it again , i just updated mine and seems to be working ,
Click to expand...
Click to collapse
So this is the error I am getting.
Any ideas
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Everything seems to be working just fine, except for after a few hours it starts rebooting when the screen is turned off. Manually or automatically.
Full charge .. Seems radio is killing my battery
ShrekOpher said:
So this is the error I am getting.
Any ideas
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah other build have the issue .. ROM still work in progress beta
Sent from my GT-N7105 using XDA Free mobile app
I will try this later tonight and see how it is... I just upgraded to the z3. The front speakers were what made me get it... Lol. I will still lurk here once in a while.
Okay... Did a new build... This should fix some soft reboots, the first boot setup keyboard issue, some of the camera issues and maybe a few other issues. https://www.androidfilehost.com/?fid=95863780491132977
There's over 200 downloads for the first build, so it seems a fair few have given it a try. Thank y'all for that. Just keep in mind, this is still an alpha stage ROM, so there will still be issues and errors, but hopefully, they'll be few enough to make it usable. Have a good one!